[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <c4dfa4166c219b3655248e3ae3af93675db51b49.camel@intel.com>
Date: Wed, 29 Jun 2022 21:09:06 +1200
From: Kai Huang <kai.huang@...el.com>
To: Christoph Hellwig <hch@...radead.org>
Cc: linux-kernel@...r.kernel.org, kvm@...r.kernel.org,
linux-acpi@...r.kernel.org, seanjc@...gle.com, pbonzini@...hat.com,
dave.hansen@...el.com, len.brown@...el.com, tony.luck@...el.com,
rafael.j.wysocki@...el.com, reinette.chatre@...el.com,
dan.j.williams@...el.com, peterz@...radead.org, ak@...ux.intel.com,
kirill.shutemov@...ux.intel.com,
sathyanarayanan.kuppuswamy@...ux.intel.com,
isaku.yamahata@...el.com, thomas.lendacky@....com,
Tianyu.Lan@...rosoft.com, rdunlap@...radead.org, Jason@...c4.com,
juri.lelli@...hat.com, mark.rutland@....com, frederic@...nel.org,
yuehaibing@...wei.com, dongli.zhang@...cle.com
Subject: Re: [PATCH v5 02/22] cc_platform: Add new attribute to prevent ACPI
CPU hotplug
On Tue, 2022-06-28 at 22:33 -0700, Christoph Hellwig wrote:
> On Wed, Jun 22, 2022 at 11:15:43PM +1200, Kai Huang wrote:
> > Platforms with confidential computing technology may not support ACPI
> > CPU hotplug when such technology is enabled by the BIOS. Examples
> > include Intel platforms which support Intel Trust Domain Extensions
> > (TDX).
>
> What does this have to to wit hthe cc_platform abstraction? This is
> just an intel implementation bug because they hastended so much into
> implementing this. So the quirks should not overload the cc_platform
> abstraction.
>
Thanks for feedback. I thought there might be similar technologies and it would
be better to have a common attribute. I'll give up this approach and change to
use arch-specific check.
--
Thanks,
-Kai
Powered by blists - more mailing lists