From: Waiman Long <longman@redhat.com>
To: Borislav Petkov <bp@alien8.de>
Cc: Pawan Gupta <pawan.kumar.gupta@linux.intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org, linux-kernel@vger.kernel.org,
Josh Poimboeuf <jpoimboe@redhat.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Mark Gross <mgross@linux.intel.com>,
Tony Luck <tony.luck@intel.com>
Subject: Re: [PATCH] x86/speculation: Fix incorrect MDS/TAA mitigation status
Date: Fri, 15 Nov 2019 09:40:56 -0500 [thread overview]
Message-ID: <a924b8f8-7f34-0144-74d1-4d2ba09341dc@redhat.com> (raw)
In-Reply-To: <20191114220924.GE7222@zn.tnic>
On 11/14/19 5:09 PM, Borislav Petkov wrote:
> On Thu, Nov 14, 2019 at 04:58:24PM -0500, Waiman Long wrote:
>>> Maybe delay MDS mitigation print till TAA is evaluated.
>> I will see what can be done about that. However, this is not a critical
>> issue and I may not change it if there is no easy solution.
> Swapping the two mitigation selection calls in check_bugs() might
> work...
Not really. If taa_select_mitigation() goes first and with
"tsx_async_abort=off" only, the mds file is correct, but the taa file
will be wrong.
Cheers,
Longman
next prev parent reply other threads:[~2019-11-15 14:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-13 19:33 Waiman Long
2019-11-14 17:45 ` Borislav Petkov
2019-11-14 17:53 ` Waiman Long
2019-11-14 18:48 ` Thomas Gleixner
2019-11-14 19:11 ` Waiman Long
2019-11-14 20:12 ` Pawan Gupta
2019-11-14 20:35 ` Josh Poimboeuf
2019-11-14 21:48 ` Waiman Long
2019-11-14 21:58 ` Waiman Long
2019-11-14 22:09 ` Borislav Petkov
2019-11-15 14:40 ` Waiman Long [this message]
2019-11-14 23: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=a924b8f8-7f34-0144-74d1-4d2ba09341dc@redhat.com \
--to=longman@redhat.com \
--cc=bp@alien8.de \
--cc=gregkh@linuxfoundation.org \
--cc=hpa@zytor.com \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgross@linux.intel.com \
--cc=mingo@redhat.com \
--cc=pawan.kumar.gupta@linux.intel.com \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--cc=x86@kernel.org \
/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
all inboxes | Powered by JetHome®