From: Anthony PERARD via <qemu-devel@nongnu.org>
To: <qemu-devel@nongnu.org>
Cc: Peter Maydell <peter.maydell@linaro.org>,
Anthony PERARD <anthony.perard@citrix.com>
Subject: [PULL 0/2] xen queue
Date: Fri, 24 Mar 2023 14:56:11 +0000 [thread overview]
Message-ID: <20230324145613.41502-1-anthony.perard@citrix.com> (raw)
The following changes since commit 60ca584b8af0de525656f959991a440f8c191f12:
Merge tag 'pull-for-8.0-220323-1' of https://gitlab.com/stsquad/qemu into staging (2023-03-22 17:58:12 +0000)
are available in the Git repository at:
https://xenbits.xen.org/git-http/people/aperard/qemu-dm.git tags/pull-xen-20230324
for you to fetch changes up to 670d8c6ebf7a2c425575bbd6fbaeb27d21edd6c6:
hw/xenpv: Initialize Xen backend operations (2023-03-24 14:52:14 +0000)
----------------------------------------------------------------
Xen queue
- fix guest creation when -xen-domid-restrict is used.
- fix Xen PV guest creation.
----------------------------------------------------------------
David Woodhouse (2):
accel/xen: Fix DM state change notification in dm_restrict mode
hw/xenpv: Initialize Xen backend operations
accel/xen/xen-all.c | 27 ++++++++++-----------------
hw/xenpv/xen_machine_pv.c | 2 ++
2 files changed, 12 insertions(+), 17 deletions(-)
next reply other threads:[~2023-03-24 15:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-24 14:56 Anthony PERARD via [this message]
2023-03-24 14:56 ` [PULL 1/2] accel/xen: Fix DM state change notification in dm_restrict mode Anthony PERARD via
2023-03-24 14:56 ` [PULL 2/2] hw/xenpv: Initialize Xen backend operations Anthony PERARD via
2023-03-25 16:28 ` [PULL 0/2] xen queue Peter Maydell
-- strict thread matches above, loose matches on Subject: below --
2023-03-06 14:00 Anthony PERARD via
2023-03-07 12:41 ` Peter Maydell
2022-07-05 13:45 Anthony PERARD via
2022-07-06 1:48 ` Richard Henderson
2022-01-27 15:42 [PULL 0/2] Xen queue Anthony PERARD via
2022-01-28 14:03 ` Peter Maydell
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=20230324145613.41502-1-anthony.perard@citrix.com \
--to=qemu-devel@nongnu.org \
--cc=anthony.perard@citrix.com \
--cc=peter.maydell@linaro.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).