From: Jon Masters <jcm@redhat.com>
To: speck@linutronix.de
Subject: [MODERATED] Re: [PATCH 5/8] L1TFv7 0
Date: Tue, 12 Jun 2018 14:47:22 -0400 [thread overview]
Message-ID: <e0175998-aacd-8b4c-554a-ed3df6a0e9ea@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.21.1806122039270.1592@nanos.tec.linutronix.de>
[-- Attachment #1: Type: text/plain, Size: 951 bytes --]
On 06/12/2018 02:41 PM, speck for Thomas Gleixner wrote:
> On Tue, 12 Jun 2018, speck for Jon Masters wrote:
>
>> On 06/07/2018 07:22 PM, speck for ak_at_linux.intel.com wrote:
>>
>>> + setup_force_cpu_bug(X86_BUG_L1TF);
>>> + l1tf_init_workaround();
>>
>> You're missing an X86_VENDOR_INTEL check there. Please fix it.
>
> It's after:
>
> if (x86_match_cpu(cpu_no_meltdown))
> return;
>
> so everything is fine.
Ok great. Btw, you said you tested the SMT disable patches on a range of
machines that includes AMD - does that include EPYC?
I'm keen that we test things that affect both vendors like pte !present
changes on the other guy's hardware since they're not here to test for
themselves and I don't want to see it go badly for them. We're working
on getting more EPYC systems within Red Hat to help with our testing.
Jon.
--
Computer Architect | Sent from my Fedora powered laptop
next prev parent reply other threads:[~2018-06-12 18:47 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-07 23:22 [MODERATED] [PATCH 0/8] L1TFv7 3 ak
2018-06-07 23:22 ` [MODERATED] [PATCH 1/8] L1TFv7 1 ak
2018-06-07 23:22 ` [MODERATED] [PATCH 2/8] L1TFv7 4 ak
2018-06-07 23:22 ` [MODERATED] [PATCH 3/8] L1TFv7 8 ak
2018-06-07 23:22 ` [MODERATED] [PATCH 4/8] L1TFv7 6 ak
2018-06-07 23:22 ` [MODERATED] [PATCH 5/8] L1TFv7 0 ak
2018-06-07 23:22 ` [MODERATED] [PATCH 6/8] L1TFv7 7 ak
2018-06-07 23:22 ` [MODERATED] [PATCH 7/8] L1TFv7 2 ak
2018-06-07 23:22 ` [MODERATED] [PATCH 8/8] L1TFv7 5 ak
[not found] ` <20180607232533.A6E2361102@crypto-ml.lab.linutronix.de>
2018-06-07 23:28 ` [MODERATED] Re: [PATCH 5/8] L1TFv7 0 Andi Kleen
2018-06-12 20:58 ` Konrad Rzeszutek Wilk
[not found] ` <20180607232458.6463361106@crypto-ml.lab.linutronix.de>
2018-06-07 23:34 ` [MODERATED] Re: [PATCH 1/8] L1TFv7 1 Dave Hansen
[not found] ` <20180607232537.C80D26114D@crypto-ml.lab.linutronix.de>
2018-06-12 15:02 ` [PATCH 5/8] L1TFv7 0 Thomas Gleixner
[not found] ` <20180607232608.B2E4661189@crypto-ml.lab.linutronix.de>
2018-06-12 15:03 ` [PATCH 6/8] L1TFv7 7 Thomas Gleixner
[not found] ` <20180607232452.BB0E3610FC@crypto-ml.lab.linutronix.de>
2018-06-12 16:13 ` [PATCH 2/8] L1TFv7 4 Thomas Gleixner
[not found] ` <20180607232536.1127561149@crypto-ml.lab.linutronix.de>
2018-06-12 17:35 ` [MODERATED] Re: [PATCH 5/8] L1TFv7 0 Jon Masters
2018-06-12 18:41 ` Thomas Gleixner
2018-06-12 18:47 ` Jon Masters [this message]
2018-06-12 19:03 ` Thomas Gleixner
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=e0175998-aacd-8b4c-554a-ed3df6a0e9ea@redhat.com \
--to=jcm@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 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.