From: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
To: "Alex Bennée" <alex.bennee@linaro.org>, qemu-devel@nongnu.org
Cc: "Stefano Stabellini" <sstabellini@kernel.org>,
"Eduardo Habkost" <ehabkost@redhat.com>,
"Paul Durrant" <paul@xen.org>,
"Michael S. Tsirkin" <mst@redhat.com>,
"Richard Henderson" <richard.henderson@linaro.org>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
xen-devel@lists.xenproject.org,
"Anthony Perard" <anthony.perard@citrix.com>,
"Paolo Bonzini" <pbonzini@redhat.com>
Subject: [PATCH v3 0/7] hw/xen: Introduce XEN_FV/XEN_PV Kconfig
Date: Mon, 1 Feb 2021 12:28:58 +0100 [thread overview]
Message-ID: <20210201112905.545144-1-f4bug@amsat.org> (raw)
Sort the Xen buildsys glue a bit.
The first patches are probably ready now.
Since v2:
- Addressed some of Paolo's comments
- More fixes
- XEN_PV still not buildable alone -> postponed
v2: Considered Paolo's comments from v1
Philippe Mathieu-Daudé (7):
meson: Do not build Xen x86_64-softmmu on Aarch64
hw/xen: Relax dependency on FSDEV_9P
accel/xen: Incorporate xen-mapcache.c
hw/i386/xen: Introduce XEN_FV Kconfig
hw/xen: Make xen_shutdown_fatal_error() available out of X86 HVM
hw/xen: Make qmp_xen_set_global_dirty_log() available out of X86 HVM
NOTFORMERGE hw/xen/Kconfig: Introduce XEN_PV config
meson.build | 8 ++++++--
accel/xen/trace.h | 1 +
{hw/i386 => accel}/xen/xen-mapcache.c | 0
hw/i386/xen/xen-hvm.c | 24 ------------------------
hw/xen/xen-legacy-backend.c | 3 ++-
hw/xen/xen-migration.c | 22 ++++++++++++++++++++++
hw/xen/xen-utils.c | 25 +++++++++++++++++++++++++
accel/Kconfig | 2 +-
accel/xen/meson.build | 5 ++++-
accel/xen/trace-events | 10 ++++++++++
hw/Kconfig | 1 +
hw/i386/Kconfig | 2 ++
hw/i386/xen/Kconfig | 5 +++++
hw/i386/xen/meson.build | 3 +--
hw/i386/xen/trace-events | 6 ------
hw/xen/Kconfig | 7 +++++++
hw/xen/meson.build | 4 +++-
17 files changed, 90 insertions(+), 38 deletions(-)
create mode 100644 accel/xen/trace.h
rename {hw/i386 => accel}/xen/xen-mapcache.c (100%)
create mode 100644 hw/xen/xen-migration.c
create mode 100644 hw/xen/xen-utils.c
create mode 100644 accel/xen/trace-events
create mode 100644 hw/i386/xen/Kconfig
create mode 100644 hw/xen/Kconfig
--
2.26.2
next reply other threads:[~2021-02-01 11:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-01 11:28 Philippe Mathieu-Daudé [this message]
2021-02-01 11:28 ` [PATCH v3 1/7] meson: Do not build Xen x86_64-softmmu on Aarch64 Philippe Mathieu-Daudé
2021-02-01 11:29 ` [PATCH v3 2/7] hw/xen: Relax dependency on FSDEV_9P Philippe Mathieu-Daudé
2021-02-01 11:29 ` [PATCH v3 3/7] accel/xen: Incorporate xen-mapcache.c Philippe Mathieu-Daudé
2021-02-01 13:08 ` Philippe Mathieu-Daudé
2021-02-01 11:29 ` [PATCH v3 4/7] hw/i386/xen: Introduce XEN_FV Kconfig Philippe Mathieu-Daudé
2021-02-01 11:29 ` [PATCH v3 5/7] hw/xen: Make xen_shutdown_fatal_error() available out of X86 HVM Philippe Mathieu-Daudé
2021-02-01 13:09 ` Philippe Mathieu-Daudé
2021-02-01 11:29 ` [PATCH v3 6/7] hw/xen: Make qmp_xen_set_global_dirty_log() " Philippe Mathieu-Daudé
2021-02-01 11:29 ` [PATCH v3 7/7] NOTFORMERGE hw/xen/Kconfig: Introduce XEN_PV config Philippe Mathieu-Daudé
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=20210201112905.545144-1-f4bug@amsat.org \
--to=f4bug@amsat.org \
--cc=alex.bennee@linaro.org \
--cc=anthony.perard@citrix.com \
--cc=ehabkost@redhat.com \
--cc=mst@redhat.com \
--cc=paul@xen.org \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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 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).