From: Paolo Bonzini <pbonzini@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>, qemu-devel@nongnu.org
Cc: Stefano Stabellini <sstabellini@kernel.org>,
Eduardo Habkost <ehabkost@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
Paul Durrant <paul@xen.org>,
Anthony Perard <anthony.perard@citrix.com>,
xen-devel@lists.xenproject.org,
Richard Henderson <rth@twiddle.net>
Subject: Re: [PATCH v2 0/6] hw/xen: Housekeeping
Date: Tue, 22 Sep 2020 11:40:42 +0200 [thread overview]
Message-ID: <8b4dc535-166d-9377-27ff-5d75f8978191@redhat.com> (raw)
In-Reply-To: <20200908155530.249806-1-philmd@redhat.com>
On 08/09/20 17:55, Philippe Mathieu-Daudé wrote:
> Hard to make an exciting cover of this series.
>
> Basically:
> - Make better separation between Xen accel and Xen hardware,
> - Move stuff around to restrict PCMachineState to hw/i386/.
>
> Since v1:
> - added missing include in stubs/xen-hw-stub.c
> - added missing 'exec/cpu-common.h' for ram_addr_t
>
> (Due to a bug in 'make', while rebasing the archives
> might not be updated... so I missed this missing
> hunk as hw/core/libhwcore.fa didn't rebuilt stubs/)
>
> Philippe Mathieu-Daudé (6):
> hw/i386/q35: Remove unreachable Xen code on Q35 machine
> hw/i386/xen: Rename X86/PC specific function as xen_hvm_init_pc()
> sysemu/xen: Add missing 'exec/cpu-common.h' header for ram_addr_t type
> stubs: Split accelerator / hardware related stubs
> hw/xen: Split x86-specific declaration from generic hardware ones
> typedefs: Restrict PCMachineState to 'hw/i386/pc.h'
>
> include/hw/i386/pc.h | 4 ++--
> include/hw/xen/xen-x86.h | 15 ++++++++++++
> include/hw/xen/xen.h | 2 --
> include/qemu/typedefs.h | 1 -
> include/sysemu/xen.h | 2 ++
> accel/stubs/xen-stub.c | 41 +-------------------------------
> hw/i386/pc_piix.c | 8 +++----
> hw/i386/pc_q35.c | 13 ++---------
> hw/i386/xen/xen-hvm.c | 3 ++-
> stubs/xen-hw-stub.c | 50 ++++++++++++++++++++++++++++++++++++++++
> MAINTAINERS | 1 +
> stubs/meson.build | 1 +
> 12 files changed, 80 insertions(+), 61 deletions(-)
> create mode 100644 include/hw/xen/xen-x86.h
> create mode 100644 stubs/xen-hw-stub.c
>
Queued, thanks.
Paolo
prev parent reply other threads:[~2020-09-22 9:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-08 15:55 [PATCH v2 0/6] hw/xen: Housekeeping Philippe Mathieu-Daudé
2020-09-08 15:55 ` [PATCH v2 1/6] hw/i386/q35: Remove unreachable Xen code on Q35 machine Philippe Mathieu-Daudé
2020-09-08 15:55 ` [PATCH v2 2/6] hw/i386/xen: Rename X86/PC specific function as xen_hvm_init_pc() Philippe Mathieu-Daudé
2020-09-08 15:55 ` [PATCH v2 3/6] sysemu/xen: Add missing 'exec/cpu-common.h' header for ram_addr_t type Philippe Mathieu-Daudé
2020-09-08 15:55 ` [PATCH v2 4/6] stubs: Split accelerator / hardware related stubs Philippe Mathieu-Daudé
2020-09-08 15:59 ` Philippe Mathieu-Daudé
2020-09-08 15:55 ` [PATCH v2 5/6] hw/xen: Split x86-specific declaration from generic hardware ones Philippe Mathieu-Daudé
2020-09-08 15:55 ` [PATCH v2 6/6] typedefs: Restrict PCMachineState to 'hw/i386/pc.h' Philippe Mathieu-Daudé
2020-09-22 9:40 ` Paolo Bonzini [this message]
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=8b4dc535-166d-9377-27ff-5d75f8978191@redhat.com \
--to=pbonzini@redhat.com \
--cc=anthony.perard@citrix.com \
--cc=ehabkost@redhat.com \
--cc=mst@redhat.com \
--cc=paul@xen.org \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
--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).