From: Paolo Bonzini <pbonzini@redhat.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: Sander Eikelenboom <linux@eikelenboom.it>,
qemu-devel@nongnu.org, Anthony Liguori <aliguori@amazon.com>,
"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] pc_piix: enable legacy hotplug for Xen
Date: Wed, 05 Feb 2014 18:04:08 +0100 [thread overview]
Message-ID: <52F26F08.2000300@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1402051651160.4373@kaball.uk.xensource.com>
Il 05/02/2014 17:54, Stefano Stabellini ha scritto:
>> > I'm not sure how this is related to fw_cfg? fw_cfg is just a simple key-value
>> > store. If hvmloader doesn't use it, it should be a burden.
> I was referring to the fact that QEMU might not have all the info that
> need to be written to fw_cfg when running on Xen: some of the info might
> be in the hypervisor and some other in another QEMU instance.
> Or do you think that fw_cfg could be written by multiple entities
> simultaneously?
Wouldn't it be possible to fetch the necessary information via
hypercalls or in xenstore?
It's possible that some particular fw_cfg entries will be skipped for
Xen, but most of them should apply. fw_cfg support would also make it
possible to use -kernel/-initrd in Xen HVM machines, for example.
Paolo
next prev parent reply other threads:[~2014-02-05 17:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-04 21:32 [Qemu-devel] [PATCH] pc_piix: enable legacy hotplug for Xen Michael S. Tsirkin
2014-02-04 21:55 ` Paolo Bonzini
2014-02-04 22:28 ` Sander Eikelenboom
2014-02-05 16:35 ` Stefano Stabellini
2014-02-05 16:45 ` Sander Eikelenboom
2014-02-05 16:50 ` Stefano Stabellini
2014-02-05 16:41 ` Stefano Stabellini
2014-02-05 16:47 ` Paolo Bonzini
2014-02-05 16:54 ` Stefano Stabellini
2014-02-05 17:04 ` Paolo Bonzini [this message]
2014-02-05 17:53 ` Stefano Stabellini
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=52F26F08.2000300@redhat.com \
--to=pbonzini@redhat.com \
--cc=aliguori@amazon.com \
--cc=linux@eikelenboom.it \
--cc=mst@redhat.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.