From: Sohil Mehta <sohil.mehta@intel.com>
To: Sean Christopherson <seanjc@google.com>
Cc: <x86@kernel.org>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
"Ingo Molnar" <mingo@redhat.com>,
"H . Peter Anvin" <hpa@zytor.com>,
Uros Bizjak <ubizjak@gmail.com>,
Sandipan Das <sandipan.das@amd.com>,
Peter Zijlstra <peterz@infradead.org>,
Vegard Nossum <vegard.nossum@oracle.com>,
Tony Luck <tony.luck@intel.com>,
Pawan Gupta <pawan.kumar.gupta@linux.intel.com>,
Nikolay Borisov <nik.borisov@suse.com>,
Eric Biggers <ebiggers@google.com>, Xin Li <xin3.li@intel.com>,
<linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH] x86/cpufeature: Add feature dependency checks
Date: Mon, 26 Aug 2024 14:47:40 -0700 [thread overview]
Message-ID: <d7a86076-d1e8-418f-a167-e2d16b2dd7f7@intel.com> (raw)
In-Reply-To: <ZszgGxZLDQYIEJpX@google.com>
On 8/26/2024 1:05 PM, Sean Christopherson wrote:
> On Fri, Aug 23, 2024, Sohil Mehta wrote:
>> But I still feel that for the rare case when something like this seeps
>> through it would be better to disable the feature upfront than run in a
>> kernel panic or some other unexpected behavior.
>
> Agreed.
>
Great, I'll wait for a few more days to see if someone says otherwise.
prev parent reply other threads:[~2024-08-26 21:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-22 20:22 [RFC PATCH] x86/cpufeature: Add feature dependency checks Sohil Mehta
2024-08-22 23:27 ` Sean Christopherson
2024-08-23 19:05 ` Sohil Mehta
2024-08-26 20:05 ` Sean Christopherson
2024-08-26 21:47 ` Sohil Mehta [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=d7a86076-d1e8-418f-a167-e2d16b2dd7f7@intel.com \
--to=sohil.mehta@intel.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=ebiggers@google.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=nik.borisov@suse.com \
--cc=pawan.kumar.gupta@linux.intel.com \
--cc=peterz@infradead.org \
--cc=sandipan.das@amd.com \
--cc=seanjc@google.com \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--cc=ubizjak@gmail.com \
--cc=vegard.nossum@oracle.com \
--cc=x86@kernel.org \
--cc=xin3.li@intel.com \
/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