From: Dave Hansen <dave.hansen@intel.com>
To: Borislav Petkov <bp@alien8.de>,
Sathyanarayanan Kuppuswamy
<sathyanarayanan.kuppuswamy@linux.intel.com>
Cc: "Kirill A. Shutemov" <kirill@shutemov.name>,
Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Andi Kleen <ak@linux.intel.com>,
x86@kernel.org, linux-kernel@vger.kernel.org,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
Juergen Gross <jgross@suse.com>, Deep Shah <sdeep@vmware.com>,
"VMware, Inc." <pv-drivers@vmware.com>
Subject: Re: [PATCH] x86/paravirt: Fix build PARAVIRT_XXL=y without XEN_PV
Date: Wed, 17 Nov 2021 11:11:31 -0800 [thread overview]
Message-ID: <b867f002-bb62-94b0-1e13-f2b8520011e6@intel.com> (raw)
In-Reply-To: <YZVOfGtHyiZg1pIP@zn.tnic>
On 11/17/21 10:48 AM, Borislav Petkov wrote:
> On Wed, Nov 17, 2021 at 10:46:30AM -0800, Sathyanarayanan Kuppuswamy wrote:
>> TDX has a requirement to use HLT paravirt calls (which is currently
>> listed under PARAVIRT_XXL). Once we submit a patch to move it
>> under CONFIG_PARAVIRT, we will drop this dependency.
> You already have this patch in some set:
>
> https://lore.kernel.org/r/20211009053747.1694419-2-sathyanarayanan.kuppuswamy@linux.intel.com
>
> So what's this churn for?
The churn is my doing. It occurred to me that we could toss the
aforementioned patch out of the set by using:
depends on PARAVIRT_XXL
instead of:
depends on PARAVIRT
Especially since PARAVIRT_XXL seems pretty common in distro kernels.
But, I didn't realize quite how reviled PARAVIRT_XXL was.
So, first of all, _this_ patch is a proper cleanup. We should merge it
or something like it either way.
As for TDX, my preference (obviously) is to keep the "depends on
PARAVIRT_XXL", reviled as it may be. It's the literal truth at this
point: TDX guest support depends on PARAVIRT_XXL functionality. There
is no shortage of ways to remove that dependency (expand PARAVIRT or
custom idle), which makes me very confident that we are not painting
ourselves into a corner here.
next prev parent reply other threads:[~2021-11-17 19:11 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-17 18:14 [PATCH] x86/paravirt: Fix build PARAVIRT_XXL=y without XEN_PV Kirill A. Shutemov
2021-11-17 18:35 ` Peter Zijlstra
2021-11-17 18:42 ` Kirill A. Shutemov
2021-11-17 18:46 ` Sathyanarayanan Kuppuswamy
2021-11-17 18:48 ` Borislav Petkov
2021-11-17 19:11 ` Dave Hansen [this message]
2021-11-17 19:13 ` Sathyanarayanan Kuppuswamy
2021-11-17 19:57 ` Dave Hansen
2021-11-17 20:54 ` Sathyanarayanan Kuppuswamy
2021-11-17 21:09 ` Borislav Petkov
2021-11-17 23:04 ` Sathyanarayanan Kuppuswamy
2021-11-17 23:23 ` Peter Zijlstra
2021-11-17 23:57 ` Sathyanarayanan Kuppuswamy
2021-11-17 23:33 ` Dave Hansen
2021-11-18 1:26 ` Sathyanarayanan Kuppuswamy
2021-11-18 9:13 ` Borislav Petkov
2021-11-17 19:02 ` Peter Zijlstra
2021-11-18 6:23 ` Juergen Gross
2021-11-19 10:21 ` Kirill A. Shutemov
2021-11-19 7:51 ` Lai Jiangshan
2021-11-19 10:20 ` Kirill A. Shutemov
2021-11-19 10:27 ` Juergen Gross
2021-11-20 1:23 ` Lai Jiangshan
2021-11-22 12:55 ` Juergen Gross
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=b867f002-bb62-94b0-1e13-f2b8520011e6@intel.com \
--to=dave.hansen@intel.com \
--cc=ak@linux.intel.com \
--cc=bp@alien8.de \
--cc=jgross@suse.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=kirill@shutemov.name \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=pv-drivers@vmware.com \
--cc=sathyanarayanan.kuppuswamy@linux.intel.com \
--cc=sdeep@vmware.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox