[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <c1b2162f-5a1e-4072-8695-6c663a1ba0c5@intel.com>
Date: Mon, 20 Oct 2025 09:21:41 -0700
From: Dave Hansen <dave.hansen@...el.com>
To: Jon Kohler <jon@...anix.com>, Sean Christopherson <seanjc@...gle.com>
Cc: Thomas Gleixner <tglx@...utronix.de>, Borislav Petkov <bp@...en8.de>,
Peter Zijlstra <peterz@...radead.org>, Josh Poimboeuf <jpoimboe@...nel.org>,
Pawan Gupta <pawan.kumar.gupta@...ux.intel.com>,
Jonathan Corbet <corbet@....net>, Ingo Molnar <mingo@...hat.com>,
Dave Hansen <dave.hansen@...ux.intel.com>, "x86@...nel.org"
<x86@...nel.org>, "H. Peter Anvin" <hpa@...or.com>,
Brian Gerst <brgerst@...il.com>, Brendan Jackman <jackmanb@...gle.com>,
"Ahmed S. Darwish" <darwi@...utronix.de>,
Alexandre Chartre <alexandre.chartre@...cle.com>,
"linux-doc@...r.kernel.org" <linux-doc@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] x86/its: use Sapphire Rapids+ feature to opt out
On 10/20/25 09:05, Jon Kohler wrote:
> Was running into some testing issues with my qemu change internally,
> but I’ll get that out this week once I clear them.
BTW, if there are folks out there that are working on things like QEMU
and want more formal or regular notification from vendors that a FOO_NO
bit has been added, that can probably be arranged.
The real issue here is that nobody cared enough to get QEMU to
comprehend ITS_NO right after the embargo was lifted, right?
Powered by blists - more mailing lists