All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Hansen <dave.hansen@intel.com>
To: Jon Kohler <jon@nutanix.com>
Cc: Pawan Gupta <pawan.kumar.gupta@linux.intel.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Borislav Petkov <bp@alien8.de>,
	Peter Zijlstra <peterz@infradead.org>,
	Josh Poimboeuf <jpoimboe@kernel.org>,
	Jonathan Corbet <corbet@lwn.net>, Ingo Molnar <mingo@redhat.com>,
	Dave Hansen <dave.hansen@linux.intel.com>,
	"x86@kernel.org" <x86@kernel.org>,
	"H. Peter Anvin" <hpa@zytor.com>, Brian Gerst <brgerst@gmail.com>,
	Brendan Jackman <jackmanb@google.com>,
	"Ahmed S. Darwish" <darwi@linutronix.de>,
	Alexandre Chartre <alexandre.chartre@oracle.com>,
	"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86/its: use Sapphire Rapids+ feature to opt out
Date: Tue, 21 Oct 2025 08:21:54 -0700	[thread overview]
Message-ID: <67cdba64-d1e7-4f18-b790-4ecd2c573bb0@intel.com> (raw)
In-Reply-To: <883EDC14-1A26-46F4-B9E9-C75A6DF07195@nutanix.com>

On 10/21/25 07:39, Jon Kohler wrote:
> For BHI_CTRL, depending on what QEMU the VM was originally *started* on,
> the guest may have access to Sapphire Rapids models, but BHI_CTRL may
> not have existed in the QEMU source at that time, as those were introduced
> into two different timeframes.

I have two solutions for you here, and neither of them involves patching
the kernel.

First, I personally volunteer to travel to your customers' homes to
provide in-person education with my "education stick" about why updating
software is important.

Second, if they continue to be education-resistant, I offer to
personally travel to the datacenters where these VMs are running to
inspect the racks where they run and brainstorm solutions. A warning,
though: I am quite clumsy and I've been known to bump into power cables
and circuit breakers.



  reply	other threads:[~2025-10-21 15:21 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-17  1:12 [PATCH] x86/its: use Sapphire Rapids+ feature to opt out Jon Kohler
2025-10-20 15:48 ` Sean Christopherson
2025-10-20 16:05   ` Jon Kohler
2025-10-20 16:21     ` Dave Hansen
2025-10-20 16:26       ` Jon Kohler
2025-10-20 19:26       ` Pawan Gupta
2025-10-20 19:38         ` Jon Kohler
2025-10-20 19:53           ` Pawan Gupta
2025-10-20 20:29             ` Jon Kohler
2025-10-20 19:44 ` Pawan Gupta
2025-10-20 19:54   ` Jon Kohler
2025-10-20 20:40     ` Pawan Gupta
2025-10-20 21:02       ` Jon Kohler
2025-10-20 22:09       ` Dave Hansen
2025-10-20 22:41         ` Pawan Gupta
2025-10-21 13:40           ` Jon Kohler
2025-10-21 14:01             ` Dave Hansen
2025-10-21 14:39               ` Jon Kohler
2025-10-21 15:21                 ` Dave Hansen [this message]
2025-10-21 15:40                   ` Jon Kohler
2025-10-21 15:27                 ` Konrad Rzeszutek Wilk
2025-10-21 15:35                   ` Jon Kohler
2025-10-21 15:46                     ` Konrad Rzeszutek Wilk

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=67cdba64-d1e7-4f18-b790-4ecd2c573bb0@intel.com \
    --to=dave.hansen@intel.com \
    --cc=alexandre.chartre@oracle.com \
    --cc=bp@alien8.de \
    --cc=brgerst@gmail.com \
    --cc=corbet@lwn.net \
    --cc=darwi@linutronix.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=jackmanb@google.com \
    --cc=jon@nutanix.com \
    --cc=jpoimboe@kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=pawan.kumar.gupta@linux.intel.com \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    --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 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.