From: Josh Poimboeuf <jpoimboe@redhat.com>
To: speck@linutronix.de
Subject: [MODERATED] Re: [PATCH v6 5/8] L1TFv6 1
Date: Fri, 1 Jun 2018 10:53:57 -0500 [thread overview]
Message-ID: <20180601155357.2by3awwq7fj6nzn6@treble> (raw)
In-Reply-To: <20180524210213.9325561130@crypto-ml.lab.linutronix.de>
On Thu, May 24, 2018 at 02:00:36PM -0700, speck for Andi Kleen wrote:
> +ssize_t cpu_show_l1tf(struct device *dev, struct device_attribute *attr, char *buf)
> +{
> + if (!boot_cpu_has_bug(X86_BUG_L1TF))
> + return sprintf(buf, "Not affected\n");
> +
> + if (boot_cpu_has(X86_FEATURE_L1TF_FIX))
> + return sprintf(buf, "Mitigated\n");
> +
> + return sprintf(buf, "Vulnerable\n");
> +}
Once all the virt pieces are in place (HT disabled, vmexit flush) how
are we going to report the status in sysfs?
For example, if somebody started a (potentially untrusted) VM without
disabling HT, how do we report that?
--
Josh
prev parent reply other threads:[~2018-06-01 15:54 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-24 21:00 [MODERATED] [PATCH v6 0/8] L1TFv6 6 Andi Kleen
2018-05-24 21:00 ` [MODERATED] [PATCH v6 1/8] L1TFv6 2 Andi Kleen
2018-05-24 21:00 ` [MODERATED] [PATCH v6 2/8] L1TFv6 8 Andi Kleen
2018-05-24 21:00 ` [MODERATED] [PATCH v6 3/8] L1TFv6 5 Andi Kleen
2018-05-24 21:00 ` [MODERATED] [PATCH v6 4/8] L1TFv6 4 Andi Kleen
2018-05-24 21:00 ` [MODERATED] [PATCH v6 5/8] L1TFv6 1 Andi Kleen
2018-05-24 21:00 ` [MODERATED] [PATCH v6 6/8] L1TFv6 3 Andi Kleen
2018-05-24 21:00 ` [MODERATED] [PATCH v6 7/8] L1TFv6 7 Andi Kleen
2018-05-24 21:00 ` [MODERATED] [PATCH v6 8/8] L1TFv6 0 Andi Kleen
[not found] ` <20180524210211.7B377610F8@crypto-ml.lab.linutronix.de>
2018-05-24 21:12 ` [MODERATED] Re: [PATCH v6 5/8] L1TFv6 1 Borislav Petkov
[not found] ` <20180524210234.D1EA061155@crypto-ml.lab.linutronix.de>
2018-05-24 22:30 ` [MODERATED] Re: [PATCH v6 6/8] L1TFv6 3 Andrew Cooper
2018-05-24 22:37 ` Andi Kleen
2018-05-24 23:04 ` Linus Torvalds
2018-05-24 23:38 ` Andrew Cooper
2018-05-25 0:27 ` Linus Torvalds
2018-05-25 16:18 ` Andi Kleen
[not found] ` <20180524210148.88D9861100@crypto-ml.lab.linutronix.de>
2018-05-25 17:16 ` [MODERATED] Re: [PATCH v6 1/8] L1TFv6 2 Dave Hansen
2018-05-25 19:05 ` Andi Kleen
[not found] ` <20180524210235.19B9061156@crypto-ml.lab.linutronix.de>
2018-06-01 15:50 ` [MODERATED] Re: [PATCH v6 6/8] L1TFv6 3 Josh Poimboeuf
[not found] ` <20180524210213.9325561130@crypto-ml.lab.linutronix.de>
2018-06-01 15:53 ` Josh Poimboeuf [this message]
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=20180601155357.2by3awwq7fj6nzn6@treble \
--to=jpoimboe@redhat.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 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 read-only IMAP folder(s) and NNTP newsgroup(s).