From: Jon Kohler <jon@nutanix.com>
To: Pawan Gupta <pawan.kumar.gupta@linux.intel.com>
Cc: Jon Kohler <jon@nutanix.com>, Dave Hansen <dave.hansen@intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
"x86@kernel.org" <x86@kernel.org>,
"H. Peter Anvin" <hpa@zytor.com>, Tony Luck <tony.luck@intel.com>,
Andi Kleen <ak@linux.intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Borislav Petkov <bp@suse.de>,
Neelima Krishnan <neelima.krishnan@intel.com>,
"kvm @ vger . kernel . org" <kvm@vger.kernel.org>
Subject: Re: [PATCH] x86/tsx: fix KVM guest live migration for tsx=on
Date: Tue, 12 Apr 2022 18:12:00 +0000 [thread overview]
Message-ID: <94C77C88-D65B-445B-B462-4FB677C99F8C@nutanix.com> (raw)
In-Reply-To: <20220412180452.ityo3o3eoxh3iul7@guptapa-desk>
> On Apr 12, 2022, at 2:04 PM, Pawan Gupta <pawan.kumar.gupta@linux.intel.com> wrote:
>
> On Tue, Apr 12, 2022 at 04:08:32PM +0000, Jon Kohler wrote:
>>
>>
>>> On Apr 12, 2022, at 11:54 AM, Dave Hansen <dave.hansen@intel.com> wrote:
>>>
>>> On 4/12/22 06:36, Jon Kohler wrote:
>>>> So my theory here is to extend the logical effort of the microcode driven
>>>> automatic disablement as well as the tsx=auto automatic disablement and
>>>> have tsx=on force abort all transactions on X86_BUG_TAA SKUs, but leave
>>>> the CPU features enumerated to maintain live migration.
>>>>
>>>> This would still leave TSX totally good on Ice Lake / non-buggy systems.
>>>>
>>>> If it would help, I'm working up an RFC patch, and we could discuss there?
>>>
>>> Sure. But, it sounds like you really want a new tdx=something rather
>>> than to muck with tsx=on behavior. Surely someone else will come along
>>> and complain that we broke their TDX setup if we change its behavior.
>>
>> Good point, there will always be a squeaky wheel. I’ll work that into the RFC,
>> I’ll do something like tsx=compat and see how it shapes up.
>
> FYI, the original series had tsx=fake, that would have taken care of
> this breakage.
Fake sounds way better than compat, which is what I had :)
My RFC code looks similar to your patch, I’ll combine the
approaches and send it out shortly, almost done
>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__lore.kernel.org_lkml_de6b97a567e273adff1f5268998692bad548aa10.1623272033.git-2Dseries.pawan.kumar.gupta-40linux.intel.com_&d=DwIDaQ&c=s883GpUCOChKOHiocYtGcg&r=NGPRGGo37mQiSXgHKm5rCQ&m=AgPWHzCORdn5x5rYXE0QeJ2yf158HOjDA5Bn8udzp-m6i9V9s7S_jtSiLog-dk93&s=kR74kfovpa0zOK0tZ2Ss9xbg2aRLI5oocB_cp_6DLkg&e=
> For the lack of real world use-cases at that time, this patch was dropped.
>
> Thanks,
> Pawan
next prev parent reply other threads:[~2022-04-12 18:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-11 18:01 Jon Kohler
2022-04-11 19:26 ` Dave Hansen
2022-04-11 19:35 ` Jon Kohler
2022-04-11 23:45 ` Dave Hansen
2022-04-12 13:36 ` Jon Kohler
2022-04-12 15:54 ` Dave Hansen
2022-04-12 16:08 ` Jon Kohler
2022-04-12 18:04 ` Pawan Gupta
2022-04-12 18:12 ` Jon Kohler [this message]
2022-04-12 20:40 ` Pawan Gupta
2022-04-13 12:43 ` Jon Kohler
2022-04-11 20:07 ` [PATCH v2] " Jon Kohler
2022-04-12 19:55 ` Pawan Gupta
2022-04-12 20:54 ` Pawan Gupta
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=94C77C88-D65B-445B-B462-4FB677C99F8C@nutanix.com \
--to=jon@nutanix.com \
--cc=ak@linux.intel.com \
--cc=bp@alien8.de \
--cc=bp@suse.de \
--cc=dave.hansen@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=neelima.krishnan@intel.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®