From: Paul Durrant <paul.durrant@citrix.com>
To: qemu-devel@nongnu.org, xen-devel@lists.xen.org
Subject: [Qemu-devel] [PATCH 0/2] Remove hardcoded xen-platform device initialization (v4)
Date: Tue, 18 Jun 2013 12:16:59 +0100 [thread overview]
Message-ID: <1371554221-5762-1-git-send-email-paul.durrant@citrix.com> (raw)
Because of concerns over backwards compatibility and a suggestion that
xenfv should be retired in favour of using the pc machine type I have re-
worked my original patch into 2 patches:
[PATCH 1/2] Allow use of pc machine type (accel=xen) for Xen HVM
[PATCH 2/2] Move hardcoded initialization of xen-platform device.
Application of both these patches allows alternative pc machine types to be
used with the accel=xen option, but preserves the hardcoded creation of
the xen-platform device only for machine type xenfv.
v3:
- Add test for xen_enabled() that went missing in v2
v4:
- Remove erroneous whitespace hunk
- Replace hw_error() with fprintf()+exit(1)
- Add braces to single-line if
next reply other threads:[~2013-06-18 11:17 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-18 11:16 Paul Durrant [this message]
2013-06-18 11:17 ` [Qemu-devel] [PATCH 1/2] Allow use of pc machine type (accel=xen) for Xen HVM domains Paul Durrant
2013-06-20 14:44 ` [Qemu-devel] [Xen-devel] " Stefano Stabellini
2013-06-25 12:01 ` Stefano Stabellini
2013-06-25 12:58 ` Paul Durrant
2013-06-18 11:17 ` [Qemu-devel] [PATCH 2/2] Move hardcoded initialization of xen-platform device Paul Durrant
2013-06-20 14:44 ` [Qemu-devel] [Xen-devel] " Stefano Stabellini
2013-06-18 12:23 ` [Qemu-devel] [PATCH 0/2] Remove hardcoded xen-platform device initialization (v4) Paolo Bonzini
2013-06-18 12:37 ` Laszlo Ersek
2013-06-18 12:51 ` Michael S. Tsirkin
2013-06-18 12:57 ` Paul Durrant
2013-06-18 13:01 ` Michael S. Tsirkin
2013-06-18 13:06 ` Paul Durrant
2013-06-18 13:14 ` Laszlo Ersek
2013-06-18 13:15 ` Paul Durrant
2013-06-18 14:22 ` Michael S. Tsirkin
2013-06-20 15:02 ` Paolo Bonzini
2013-06-20 15:12 ` Michael S. Tsirkin
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=1371554221-5762-1-git-send-email-paul.durrant@citrix.com \
--to=paul.durrant@citrix.com \
--cc=qemu-devel@nongnu.org \
--cc=xen-devel@lists.xen.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).