lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Thu, 23 Sep 2021 11:13:31 +0000 From: Oleksandr Andrushchenko <Oleksandr_Andrushchenko@...m.com> To: Jan Beulich <jbeulich@...e.com>, Oleksandr Andrushchenko <andr2000@...il.com> CC: "boris.ostrovsky@...cle.com" <boris.ostrovsky@...cle.com>, "jgross@...e.com" <jgross@...e.com>, "julien@....org" <julien@....org>, "sstabellini@...nel.org" <sstabellini@...nel.org>, "xen-devel@...ts.xenproject.org" <xen-devel@...ts.xenproject.org>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org> Subject: Re: [PATCH v3 1/2] xen-pciback: prepare for the split for stub and PV On 23.09.21 14:10, Jan Beulich wrote: > On 23.09.2021 11:53, Oleksandr Andrushchenko wrote: >> --- a/drivers/xen/Kconfig >> +++ b/drivers/xen/Kconfig >> @@ -180,10 +180,34 @@ config SWIOTLB_XEN >> select DMA_OPS >> select SWIOTLB >> >> +config XEN_PCI_STUB >> + bool >> + >> +config XEN_PCIDEV_STUB >> + tristate "Xen PCI-device stub driver" >> + depends on PCI && !X86 && XEN >> + depends on XEN_BACKEND >> + select XEN_PCI_STUB >> + default m >> + help >> + The PCI device stub driver provides limited version of the PCI >> + device backend driver without para-virtualized support for guests. >> + If you select this to be a module, you will need to make sure no >> + other driver has bound to the device(s) you want to make visible to >> + other guests. >> + >> + The "hide" parameter (only applicable if backend driver is compiled >> + into the kernel) allows you to bind the PCI devices to this module >> + from the default device drivers. The argument is the list of PCI BDFs: >> + xen-pciback.hide=(03:00.0)(04:00.0) >> + >> + If in doubt, say m. >> + >> config XEN_PCIDEV_BACKEND >> tristate "Xen PCI-device backend driver" >> depends on PCI && X86 && XEN >> depends on XEN_BACKEND >> + select XEN_PCI_STUB > Does kconfig not at least warn about this? The selected item has a > "depends on !X88" conflicting with the "depends on X86" here. Why? XEN_PCIDEV_STUB depends on PCI && !X86 && XEN XEN_PCI_STUB has nothing, just bool XEN_PCIDEV_BACKEND selects XEN_PCI_STUB > > Jan >
Powered by blists - more mailing lists