Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Jonathan Morton <chromatix99@gmail.com>
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] KASLR: Do we have to worry about other arches than x86?
Date: Thu, 4 Jan 2018 05:59:26 -0800	[thread overview]
Message-ID: <CAA93jw62WPik7XU_54Rw_jz8kua=nT=G3AJ3ea2URcnCE+R+8w@mail.gmail.com> (raw)
In-Reply-To: <2D7460E1-C724-4DAE-86CA-2D48AB2DAFE5@gmail.com>

Alan cox has been doing a good job of finding the good stuff. Power
and the IBM z-series are also affected.

https://plus.google.com/u/0/+AlanCoxLinux


On Thu, Jan 4, 2018 at 5:48 AM, Jonathan Morton <chromatix99@gmail.com> wrote:
>
>
>> On 4 Jan, 2018, at 3:38 pm, Dave Taht <dave.taht@gmail.com> wrote:
>>
>> I lay awake last night trying to figure out what the impact of these
>> bugs would be on the market. What I think will happen is everybody's
>> stock is going to go up as there is a mad rush to replace now 10-30%
>> slower hardware just to meet existing loads.
>
> I think *AMD's* stock is going to go up a lot more than Intel's, because they have pretty good server/workstation hardware now, and no vulnerability to the most serious variants of this attack (which means no performance impact from mitigation).  Apparently there are also mitigations for Spectre v1 and v2 which have minimal performance impact; Meltdown is the one which has a big performance cost to deal with.
>
> Probably some ARM and PowerPC server vendors could get a boost too, but only after their exposure to these attacks has been properly assessed.
>
>  - Jonathan Morton
>



-- 

Dave Täht
CEO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-669-226-2619

  reply	other threads:[~2018-01-04 13:59 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-01 23:08 Dave Taht
     [not found] ` <CAJq5cE23bbiPE0a_9zd1VLnO7=c7bjmwwxVwaD2=to3fg5TOjA@mail.gmail.com>
2018-01-01 23:27   ` Jonathan Morton
2018-01-02 19:06 ` Jonathan Morton
2018-01-04 12:09   ` Jonathan Morton
2018-01-04 13:38     ` Dave Taht
2018-01-04 13:48       ` Jonathan Morton
2018-01-04 13:59         ` Dave Taht [this message]
2018-01-04 14:49           ` Jonathan Morton
2018-01-04 14:53             ` Dave Taht
2018-01-04 20:28               ` dpreed
2018-01-04 21:20                 ` Jonathan Morton
2018-01-04 21:40                 ` Dave Taht
2018-01-04 21:51                   ` valdis.kletnieks
2018-01-04 21:44     ` Joel Wirāmu Pauling
2018-01-04 21:47       ` Dave Taht
2018-01-04 21:52         ` Joel Wirāmu Pauling
2018-01-04 21:54           ` Dave Taht
2018-01-04 21:57             ` Joel Wirāmu Pauling
     [not found]           ` <1515103187.670416570@apps.rackspace.com>
2018-01-04 22:02             ` Joel Wirāmu Pauling
     [not found]       ` <1515103048.715224709@apps.rackspace.com>
2018-01-04 22:00         ` Joel Wirāmu Pauling
2018-01-04 22:09           ` dpreed
2018-01-04 22:13             ` Joel Wirāmu Pauling
2018-01-04 22:15             ` Dave Taht
2018-01-04 22:26             ` Jonathan Morton
2018-01-04 22:35               ` Joel Wirāmu Pauling
2018-01-04 22:58                 ` [Cerowrt-devel] Spectre and EBPF JIT dpreed
2018-01-05  4:53                   ` Dave Taht
2018-01-05 14:07                     ` Jonathan Morton
2018-01-05 15:35                       ` dpreed
2018-01-05 19:18                         ` Jonathan Morton
2018-01-05 20:15                           ` David Lang
2018-01-04 22:02 [Cerowrt-devel] KASLR: Do we have to worry about other arches than x86? dpreed
2018-01-04 22:02 dpreed
2018-01-04 22:04 ` Dave Taht
2018-01-04 22:12   ` dpreed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAA93jw62WPik7XU_54Rw_jz8kua=nT=G3AJ3ea2URcnCE+R+8w@mail.gmail.com' \
    --to=dave.taht@gmail.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=chromatix99@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox