From: mark gross <mgross@linux.intel.com>
To: speck@linutronix.de
Subject: [MODERATED] Re: Re: [PATCH 2/2] more sampling fun 2
Date: Mon, 24 Feb 2020 13:39:29 -0800 [thread overview]
Message-ID: <20200224213929.GA100552@mtg-dev.jf.intel.com> (raw)
In-Reply-To: <20200224181734.GB29636@zn.tnic>
On Mon, Feb 24, 2020 at 07:17:34PM +0100, speck for Borislav Petkov wrote:
> On Mon, Feb 24, 2020 at 12:31:21PM -0500, speck for Konrad Rzeszutek Wilk wrote:
> > > This patch:
> > > * enables administrator to configure the mitigation off when desired
> > > using either mitigations=off or srbds=off.
> > > * exports vulnerability status via sysfs
> >
> > I think you also need a Documentation patch, that is a new file in
> > Documentation/x86/srbds.rst
> > and changes in
> > Documentation/admin-guide/kernel-parameters.txt
> >
> > to document the srbds=..
>
> That "srbds" string better be something more human-readable like
>
> "srb_sampling="
The implementation uses srbds_mitigation=.. (the commit comment now updated to
reflect this)
I've been holding on getting the finished white paper to be sure both documents
are are in sync.
--mark
>
> or so.
>
> Thx.
>
> --
> Regards/Gruss,
> Boris.
>
> SUSE Software Solutions Germany GmbH, GF: Felix Imendörffer, HRB 36809, AG Nürnberg
> --
next prev parent reply other threads:[~2020-02-24 21:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-24 17:31 [MODERATED] Re: [PATCH 2/2] more sampling fun 2 Konrad Rzeszutek Wilk
2020-02-24 18:17 ` [MODERATED] " Borislav Petkov
2020-02-24 21:39 ` mark gross [this message]
2020-02-24 23:10 ` [MODERATED] " Borislav Petkov
2020-02-25 1:26 ` Josh Poimboeuf
2020-02-25 10:46 ` Borislav Petkov
2020-02-25 14:18 ` Josh Poimboeuf
2020-02-25 14:23 ` Jiri Kosina
2020-02-25 14:44 ` Josh Poimboeuf
2020-02-25 14:59 ` Borislav Petkov
2020-02-26 20:20 ` Josh Poimboeuf
2020-02-26 21:16 ` Thomas Gleixner
2020-02-26 22:19 ` [MODERATED] " Konrad Rzeszutek Wilk
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=20200224213929.GA100552@mtg-dev.jf.intel.com \
--to=mgross@linux.intel.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.