From: David Woodhouse <dwmw2@infradead.org>
To: Stefano Stabellini <sstabellini@kernel.org>,
Peter Maydell <peter.maydell@linaro.org>
Cc: qemu-devel@nongnu.org
Subject: Re: [PULL 00/10] xenpvh machine
Date: Wed, 15 Feb 2023 16:15:37 +0100 [thread overview]
Message-ID: <d5d826d85e67afa204598778022ca46ac2be3e2b.camel@infradead.org> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2302141544110.2025117@ubuntu-linux-20-04-desktop>
[-- Attachment #1: Type: text/plain, Size: 1090 bytes --]
On Tue, 2023-02-14 at 15:44 -0800, Stefano Stabellini wrote:
> > Something weird has happened here -- I'm getting merge conflicts
> > in files in migration/ and in tests/unit/test-xbzrle.c, even though
> > your pullreq diffstat says it doesn't touch those files. Can you
> > try a rebase and resend?
>
> Just sent as a full pull request patch series. Also here for
> convenience:
>
> https://gitlab.com/sstabellini/qemu xenpvh2
I've rebased my tree at
https://git.infradead.org/users/dwmw2/qemu.git/shortlog/refs/heads/xenfv
on top of this.
For the "phase 1" series I've been posting already, there's not a lot
of interaction. But when it comes to wiring up all the PV back ends
there were a few things to tweak, including frowning at the fact that
you moved xen_bus_init() and xen_be_init() to somewhere generic to
cover both "actual Xen" builds, while I wanted to move it to pc.c to
cover "actual Xen" and "emulated Xen" on i386. I think I'm happy with
what I did there in the final two commits.
Please could I ask you to give it a quick smoke test on Arm?
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5965 bytes --]
prev parent reply other threads:[~2023-02-15 15:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-10 22:27 [PULL 00/10] xenpvh machine Stefano Stabellini
2023-02-10 22:27 ` [PULL 01/10] hw/i386/xen/: move xen-mapcache.c to hw/xen/ Stefano Stabellini
2023-02-10 22:27 ` [PULL 02/10] hw/i386/xen: rearrange xen_hvm_init_pc Stefano Stabellini
2023-02-10 22:27 ` [PULL 03/10] hw/i386/xen/xen-hvm: move x86-specific fields out of XenIOState Stefano Stabellini
2023-02-10 22:27 ` [PULL 04/10] xen-hvm: reorganize xen-hvm and move common function to xen-hvm-common Stefano Stabellini
2023-02-10 22:27 ` [PULL 05/10] include/hw/xen/xen_common: return error from xen_create_ioreq_server Stefano Stabellini
2023-02-10 22:27 ` [PULL 06/10] hw/xen/xen-hvm-common: skip ioreq creation on ioreq registration failure Stefano Stabellini
2023-02-10 22:27 ` [PULL 07/10] hw/xen/xen-hvm-common: Use g_new and error_report Stefano Stabellini
2023-02-10 22:27 ` [PULL 08/10] meson.build: do not set have_xen_pci_passthrough for aarch64 targets Stefano Stabellini
2023-02-10 22:27 ` [PULL 09/10] hw/arm: introduce xenpvh machine Stefano Stabellini
2023-02-10 22:27 ` [PULL 10/10] meson.build: enable xenpv machine build for ARM Stefano Stabellini
2023-02-13 15:44 ` [PULL 00/10] xenpvh machine Peter Maydell
2023-02-13 22:34 ` Stefano Stabellini
2023-02-14 11:10 ` Peter Maydell
2023-02-14 23:44 ` Stefano Stabellini
2023-02-15 15:15 ` David Woodhouse [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=d5d826d85e67afa204598778022ca46ac2be3e2b.camel@infradead.org \
--to=dwmw2@infradead.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=sstabellini@kernel.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).