From: Borislav Petkov <bp@suse.de>
To: speck@linutronix.de
Subject: [MODERATED] Re: Re: [PATCH 4/4] V8 more sampling fun 4
Date: Thu, 16 Apr 2020 19:49:14 +0200 [thread overview]
Message-ID: <20200416174914.GH21456@zn.tnic> (raw)
In-Reply-To: <20200416172021.rf4l55ci6leimccm@treble>
On Thu, Apr 16, 2020 at 12:20:21PM -0500, speck for Josh Poimboeuf wrote:
> On Thu, Jan 30, 2020 at 11:12:02AM -0800, speck for mark gross wrote:
> > +The possible values contained in this file are:
> > +
> > + ============================== =============================================
> > + Not affected Processor not vulnerable
> > + Vulnerable Processor vulnerable and mitigation disabled
> > + Vulnerable: No microcode Processor vulnerable and microcode is missing
> > + mitigation
> > + Mitigated: Microcode Processor is vulnerable and mitigation is in
> > + effect.
> > + Not affected (TSX disabled) Processor is only vulnerable when TSX is
> > + enabled while this system was booted with TSX
> > + disabled.
> > + Unknown Running on virtual guest processor that is
> > + affected but with no way to know if host
> > + processor is mitigated or vulnerable.
> > + ============================== =============================================
>
> This doesn't match the code.
How's that?
============================== =============================================
Not affected Processor not vulnerable
Vulnerable Processor vulnerable and mitigation disabled
Vulnerable: No microcode Processor vulnerable and microcode is missing
mitigation
Mitigation: Microcode Processor is vulnerable and mitigation is in
effect.
Mitigation: TSX disabled Processor is only vulnerable when TSX is
enabled while this system was booted with TSX
disabled.
Unknown: Dependent on
hypervisor status Running on virtual guest processor that is
affected but with no way to know if host
processor is mitigated or vulnerable.
============================== =============================================
--
Regards/Gruss,
Boris.
SUSE Software Solutions Germany GmbH, GF: Felix Imendörffer, HRB 36809, AG Nürnberg
--
next prev parent reply other threads:[~2020-04-16 17:49 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-16 0:14 [MODERATED] [PATCH 0/4] V8 more sampling fun 0 mark gross
2020-01-16 22:16 ` [MODERATED] [PATCH 3/4] V8 more sampling fun 3 mark gross
2020-01-30 19:12 ` [MODERATED] [PATCH 4/4] V8 more sampling fun 4 mark gross
2020-03-17 0:56 ` [MODERATED] [PATCH 1/4] V8 more sampling fun 1 mark gross
2020-03-17 0:56 ` [MODERATED] [PATCH 2/4] V8 more sampling fun 2 mark gross
2020-04-16 17:15 ` [MODERATED] Re: [PATCH 1/4] V8 more sampling fun 1 Josh Poimboeuf
2020-04-16 17:30 ` Borislav Petkov
2020-04-16 17:16 ` [MODERATED] Re: [PATCH 2/4] V8 more sampling fun 2 Josh Poimboeuf
2020-04-16 17:33 ` [MODERATED] " Borislav Petkov
2020-04-16 22:47 ` mark gross
2020-04-16 17:17 ` [MODERATED] Re: [PATCH 3/4] V8 more sampling fun 3 Josh Poimboeuf
2020-04-16 17:44 ` Borislav Petkov
2020-04-16 18:01 ` Josh Poimboeuf
2020-04-16 22:45 ` mark gross
2020-04-16 22:57 ` mark gross
2020-04-17 12:34 ` Thomas Gleixner
2020-04-17 13:19 ` [MODERATED] " Josh Poimboeuf
2020-04-17 16:46 ` Luck, Tony
2020-04-17 19:22 ` Thomas Gleixner
2020-04-16 22:54 ` [MODERATED] " mark gross
2020-04-16 17:20 ` [MODERATED] Re: [PATCH 4/4] V8 more sampling fun 4 Josh Poimboeuf
2020-04-16 17:49 ` Borislav Petkov [this message]
2020-04-16 22:57 ` [MODERATED] " mark gross
2020-04-20 14:30 ` mark gross
2020-04-20 16:17 ` Thomas Gleixner
2020-04-20 22:30 ` [MODERATED] " mark gross
2020-04-20 21:45 ` Slow Randomizing Boosts Denial of Service - Bulletin #1 Thomas Gleixner
2020-04-23 21:35 ` [MODERATED] " mark gross
2020-04-24 7:01 ` Greg KH
2020-04-27 15:10 ` mark gross
2020-04-21 17:30 ` [MODERATED] Re: [PATCH 4/4] V8 more sampling fun 4 Borislav Petkov
2020-04-21 17:34 ` Andrew Cooper
2020-04-21 18:19 ` Borislav Petkov
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=20200416174914.GH21456@zn.tnic \
--to=bp@suse.de \
--cc=speck@linutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).