From: Jason Andryuk <jandryuk@gmail.com>
To: Boris Ostrovsky <boris.ostrovsky@oracle.com>,
Juergen Gross <jgross@suse.com>,
Stefano Stabellini <sstabellini@kernel.org>,
xen-devel@lists.xenproject.org
Cc: Jason Andryuk <jandryuk@gmail.com>,
"H. Peter Anvin" <hpa@zytor.com>,
linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] Remove Xen PVH dependency on PCI
Date: Wed, 14 Oct 2020 13:53:39 -0400 [thread overview]
Message-ID: <20201014175342.152712-1-jandryuk@gmail.com> (raw)
A Xen PVH domain doesn't have a PCI bus or devices, so it doesn't need
PCI support built in. Currently, XEN_PVH depends on XEN_PVHVM which
depends on PCI.
The first patch introduces XEN_PVHVM_GUEST as a toplevel item and
changes XEN_PVHVM to a hidden variable. This allows XEN_PVH to depend
on XEN_PVHVM without PCI while XEN_PVHVM_GUEST depends on PCI.
The second patch moves XEN_512GB to clean up the option nesting.
Jason Andryuk (2):
xen: Remove Xen PVH/PVHVM dependency on PCI
xen: Kconfig: nest Xen guest options
arch/x86/xen/Kconfig | 38 ++++++++++++++++++++++----------------
drivers/xen/Makefile | 2 +-
2 files changed, 23 insertions(+), 17 deletions(-)
--
2.26.2
next reply other threads:[~2020-10-14 17:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-14 17:53 Jason Andryuk [this message]
2020-10-14 17:53 ` [PATCH 1/2] xen: Remove Xen PVH/PVHVM dependency on PCI Jason Andryuk
2020-10-15 8:10 ` Jan Beulich
2020-10-15 14:59 ` Jason Andryuk
2020-10-15 15:02 ` Jan Beulich
2020-10-15 15:08 ` Roger Pau Monné
2020-10-14 17:53 ` [PATCH 2/2] xen: Kconfig: nest Xen guest options Jason Andryuk
2020-10-15 9:41 ` Jürgen Groß
2020-10-15 14:52 ` Jason Andryuk
2020-10-15 12:37 ` boris.ostrovsky
2020-10-15 13:10 ` Andrew Cooper
2020-10-15 13:17 ` boris.ostrovsky
2020-10-15 14:50 ` Jason Andryuk
2020-10-14 18:04 ` [SUSPECTED SPAM][PATCH 0/2] Remove Xen PVH dependency on PCI Andrew Cooper
2020-10-14 19:31 ` Jason Andryuk
2020-12-16 7:01 ` [PATCH " Jürgen Groß
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=20201014175342.152712-1-jandryuk@gmail.com \
--to=jandryuk@gmail.com \
--cc=boris.ostrovsky@oracle.com \
--cc=hpa@zytor.com \
--cc=jgross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.