On Fri, Oct 27, 2023 at 09:12:40AM +0200, Jan Beulich wrote:
> On 26.10.2023 22:55, Andrew Cooper wrote:
> > We eventually want to be able to build a stripped down Xen for a single
> > platform. Make a start with CONFIG_{AMD,INTEL} (hidden behind EXPERT, but
> > available to randconfig), and adjust the microcode logic.
> >
> > No practical change.
> >
> > Signed-off-by: Andrew Cooper <andrew.coop...@citrix.com>
> > ---
> > CC: Jan Beulich <jbeul...@suse.com>
> > CC: Roger Pau Monné <roger....@citrix.com>
> > CC: Wei Liu <w...@xen.org>
> > CC: Alejandro Vallejo <alejandro.vall...@cloud.com>
> > CC: Stefano Stabellini <stefano.stabell...@amd.com>
> > CC: Xenia Ragiadakou <xenia.ragiada...@amd.com>
> >
> > I've intentionally ignored the other vendors for now. They can be put into
> > Kconfig by whomever figures out the actual dependencies between their init
> > routines.
> >
> > v2:
> > * Tweak text
>
> What about the indentation issues mentioned in reply to v1?
>
> As to using un-amended AMD and INTEL - Roger, what's your view here?
I think it would be good to add a suffix, like we do for
{AMD,INTEL}_IOMMU options, and reserve the plain AMD and INTEL options
as platform/system level options that enable both VENDOR_{CPU,IOMMU}
sub options.
So yes, {INTEL,AMD}_CPU seems a good option.
Regards, Roger.
