From: Jan Beulich <jbeulich@suse.com>
To: Juergen Gross <jgross@suse.com>
Cc: boris.ostrovsky@oracle.com, julien@xen.org,
sstabellini@kernel.org,
Oleksandr Andrushchenko <oleksandr_andrushchenko@epam.com>,
xen-devel@lists.xenproject.org, linux-kernel@vger.kernel.org,
Oleksandr Andrushchenko <andr2000@gmail.com>
Subject: Re: [PATCH v3 1/2] xen-pciback: prepare for the split for stub and PV
Date: Thu, 23 Sep 2021 13:17:59 +0200 [thread overview]
Message-ID: <87bb76ba-c8b4-5ab0-a8c3-13e8ab4af3b9@suse.com> (raw)
In-Reply-To: <478b9175-f21f-b77a-2bc1-ad230bbdf548@suse.com>
On 23.09.2021 13:12, Juergen Gross wrote:
> On 23.09.21 13: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.
>
> XEN_PCI_STUB != XEN_PCIDEV_STUB
Oh, sorry.
Jan
next prev parent reply other threads:[~2021-09-23 11:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-23 9:53 [PATCH v3 1/2] xen-pciback: prepare for the split for stub and PV Oleksandr Andrushchenko
2021-09-23 9:53 ` [PATCH v3 2/2] xen-pciback: allow compiling on other archs than x86 Oleksandr Andrushchenko
2021-09-23 20:00 ` Stefano Stabellini
2021-09-24 5:46 ` Oleksandr Andrushchenko
2021-09-24 11:38 ` Oleksandr Andrushchenko
2021-09-24 20:04 ` Stefano Stabellini
2021-09-27 5:13 ` Oleksandr Andrushchenko
2021-09-23 11:10 ` [PATCH v3 1/2] xen-pciback: prepare for the split for stub and PV Jan Beulich
2021-09-23 11:12 ` Juergen Gross
2021-09-23 11:17 ` Jan Beulich [this message]
2021-09-23 11:13 ` Oleksandr Andrushchenko
2021-09-23 19:47 ` Stefano Stabellini
2021-09-24 5:37 ` Oleksandr Andrushchenko
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=87bb76ba-c8b4-5ab0-a8c3-13e8ab4af3b9@suse.com \
--to=jbeulich@suse.com \
--cc=andr2000@gmail.com \
--cc=boris.ostrovsky@oracle.com \
--cc=jgross@suse.com \
--cc=julien@xen.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oleksandr_andrushchenko@epam.com \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.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;
as well as URLs for NNTP newsgroup(s).