From: "Tim Mouraveiko" <tim.ml@ipcopper.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Bricked x86 CPU with software?
Date: Mon, 08 Jan 2018 07:58:33 -0800 [thread overview]
Message-ID: <5A539529.10290.130FABDC@tim.ml.ipcopper.com> (raw)
In-Reply-To: <20180106101918.GA22756@amd>
> Hi!
>
> > > Is the sequence available from ring 3, or does it need ring 0?
> > >
> > > Can we get the code? Extraordinary claims and all that...
> > >
> >
> > I did not test privilege level. Are you suggesting that I put the code out there for everyone to
> > see or what?
>
> Yes, that's what I'm suggesting.
>
That would be neither prudent nor practical.
Perhaps you did not consider the consequences. What if it is compatible with your
processor? Would you send me a handwritten thank you card if that processor stops
processing? Would you be a happy replacement-sale customer of Intel? I think you did not
put much thought into why we are talking about it a year later or at all.
Unlike the now-oh-so-scary feature that was in existence for decades, that is only so scary
because of a "clever" idea to "cloud" host different customers on bare metal, without any
consideration to their security, this could affect real people not just oh-so-clever computer
farmers.
next prev parent reply other threads:[~2018-01-08 15:56 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-04 0:47 Tim Mouraveiko
2018-01-04 20:06 ` Pavel Machek
2018-01-04 21:00 ` Tim Mouraveiko
2018-01-04 21:04 ` Andy Shevchenko
2018-01-04 21:31 ` Tim Mouraveiko
2018-01-04 21:23 ` Pavel Machek
2018-01-04 22:13 ` Tim Mouraveiko
2018-01-04 22:40 ` Pavel Machek
2018-01-05 1:21 ` Tim Mouraveiko
2018-01-05 1:29 ` Hector Martin 'marcan'
2018-01-05 18:54 ` Tim Mouraveiko
2018-01-05 9:28 ` Pavel Machek
2018-01-06 1:08 ` Tim Mouraveiko
2018-01-06 10:19 ` Pavel Machek
2018-01-08 15:58 ` Tim Mouraveiko [this message]
[not found] ` <201801081920.21922.arekm@maven.pl>
2018-01-08 19:08 ` Tim Mouraveiko
[not found] ` <1515456557.4423.67.camel@infradead.org>
2018-01-09 21:48 ` Tim Mouraveiko
2018-01-08 23:32 ` Pavel Machek
2018-01-09 0:35 ` Tim Mouraveiko
2018-01-05 1:51 ` james harvey
2018-01-06 1:00 ` Tim Mouraveiko
2018-01-06 15:50 ` Nikolay Borisov
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5A539529.10290.130FABDC@tim.ml.ipcopper.com \
--to=tim.ml@ipcopper.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
/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
Powered by JetHome