From: "Michael S. Tsirkin" <mst@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: Paul Durrant <paul.durrant@citrix.com>,
qemu-devel@nongnu.org, Anthony Liguori <aliguori@amazon.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: [Qemu-devel] [PATCH] xen: make xen-platform a default device
Date: Thu, 22 May 2014 17:00:51 +0300 [thread overview]
Message-ID: <20140522140051.GA1086@redhat.com> (raw)
In-Reply-To: <1400763199.25874.66.camel@nilsson.home.kraxel.org>
On Thu, May 22, 2014 at 02:53:19PM +0200, Gerd Hoffmann wrote:
> On Do, 2014-05-22 at 15:35 +0300, Michael S. Tsirkin wrote:
> > On Thu, May 22, 2014 at 01:11:28PM +0100, Stefano Stabellini wrote:
> > > On Thu, 22 May 2014, Gerd Hoffmann wrote:
> > > > Patch hooks up the xen platform device to the default device code we
> > > > have in qemu. Two effects:
> > > >
> > > > (1) The device will not be created in case -nodefaults is specified
> > > > on the command line.
> > > > (2) Autocreating the device is also turned off in case xen-platform
> > > > is added manually via -device.
> > > >
> > > > With the patch applied you can move the xen-platform device to some
> > > > other place with a simple 'qemu -device xen-platform,addr=$slot'.
> > > >
> > > > Tested-by: Tiejun Chen <tiejun.chen@intel.com>
> > > > Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
> > >
> > > Given that libxl always passes -nodefaults to QEMU, this patch is going
> > > to effectively disable xen_platform_pci for all Xen users. It is not a
> > > good idea. With the patch applied a Xen user would have no way to enable
> > > xen_platform_pci except for passing some magic command line runes via
> > > device_model_args_hvm.
> > >
> >
> > Yes, it's an unfortunate use of the interface.
> > How about a new machine type for xenfv - that's the only one
> > that's affected, right?
> > It's time xen started versioning qemu hardware anyway.
>
> That would do the trick for sure. Question is what versioning scheme.
> Might be useful for xen machine types to version after xen releases,
> i.e. xenfv-4.4 would would be supposed to be compatible with the xen-4.4
> toolstack etc.
>
> cheers,
> Gerd
>
It's much easier for us to version it with qemu machine version,
like we do for pc, if that can work at all.
next prev parent reply other threads:[~2014-05-22 14:02 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-22 7:20 [Qemu-devel] [PATCH] xen: make xen-platform a default device Gerd Hoffmann
2014-05-22 7:21 ` Michael S. Tsirkin
2014-05-22 10:57 ` Chen, Tiejun
2014-05-22 10:59 ` Michael S. Tsirkin
2014-05-22 12:11 ` Stefano Stabellini
2014-05-22 12:35 ` Michael S. Tsirkin
2014-05-22 12:53 ` Gerd Hoffmann
2014-05-22 14:00 ` Michael S. Tsirkin [this message]
2014-05-22 12:45 ` Gerd Hoffmann
2014-05-22 13:49 ` Stefano Stabellini
2014-05-22 12:50 ` Paolo Bonzini
2014-05-22 13:22 ` Gerd Hoffmann
2014-05-22 13:56 ` Stefano Stabellini
2014-05-23 10:08 ` Paul Durrant
2014-05-23 10:11 ` Stefano Stabellini
2014-05-23 10:18 ` Paul Durrant
2014-05-23 11:36 ` Stefano Stabellini
2014-05-23 11:51 ` Paul Durrant
2014-05-22 13:55 ` Stefano Stabellini
2014-05-22 14:03 ` Paolo Bonzini
-- strict thread matches above, loose matches on Subject: below --
2014-05-23 13:03 Fabio Fantoni
2014-05-23 14:30 ` Stefano Stabellini
2014-05-23 15:02 ` Fabio Fantoni
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=20140522140051.GA1086@redhat.com \
--to=mst@redhat.com \
--cc=aliguori@amazon.com \
--cc=kraxel@redhat.com \
--cc=paul.durrant@citrix.com \
--cc=qemu-devel@nongnu.org \
--cc=stefano.stabellini@eu.citrix.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.