From: Alexander Graf <agraf@suse.de>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: Anthony Perard <anthony.perard@citrix.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Jan Beulich <jbeulich@novell.com>, Wei Liu <liuw@liuw.name>
Subject: Re: [Qemu-devel] Questions on DeviceState and Virtio infrastructure
Date: Thu, 30 Jun 2011 16:28:37 +0200 [thread overview]
Message-ID: <4E0C8815.8010100@suse.de> (raw)
In-Reply-To: <alpine.DEB.2.00.1106301356130.12963@kaball-desktop>
On 06/30/2011 04:11 PM, Stefano Stabellini wrote:
> On Thu, 30 Jun 2011, Alexander Graf wrote:
>> On 06/30/2011 12:21 PM, Stefano Stabellini wrote:
>>> On Thu, 30 Jun 2011, Wei Liu wrote:
>>>> On Thu, Jun 30, 2011 at 4:31 PM, Alexander Graf<agraf@suse.de> wrote:
>>>>> On 29.06.2011, at 15:59, Wei Liu<liuw@liuw.name> wrote:
>>>>>
>>>>>> Hi, QEMU folks
>>>>>>
>>>>>> I know that I might have a bad title for this post, but I just don't
>>>>>> have better idea for the title.
>>>>>>
>>>>>> I'm developing virtio support for Xen pv guest, hoping to reuse the
>>>>>> virtio infrastructure in qemu, i.e. I'm planning to use qemu as
>>>>>> "virtio backend" for Xen pv. And qemu can be run as pv backend if
>>>>>> proper "machine" option is given.
>>>>>>
>>>>>> Maybe you've known that Xen pv guest utilizes Xenbus/Xenstore to
>>>>>> configure its paravirt devices. So I'm to configure virtio devices
>>>>>> with Xenbus/Xenstore as well. But in nowdays XenDevice in qemu does
>>>>>> not include a DeviceState. To my understanding, it is not connected to
>>>>>> qemu's internal buses or whatever (correct me if I'm wrong, I'm
>>>>>> relatively new to qemu).
>>>>> I'm not a huge fan of adding multiple different transports for virtio if we don't have to. IIRC Xen PV guests can do PCI device assignment, right? That means there is a PCI bus for them which we could reuse to run virtio-pci on.
>>>>>
>>>>> By then, you'd get all the virtio code for free and don't have to worry about maintaining yet another transport (which _is_ cumbersome)
>>>>>
>>>> Good point, I will check this.
>>>>
>>>> I thought that Xen pv pci assignment is only used for pci passthrough.
>>>> But I will check the possibility to assign pv backend to guest.
>>>>
>>>> Stefano, how would you say about this?
>>> Yes, the PCI bus is an empty PCI bus created by xen-pcifront and it is
>>> only used for PCI passthrough. It couldn't be used as is for virtio-pci.
>> What's keeping us from doing so? Doesn't MMIO emulation work with Xen PV?
> No, it does not.
> The only realistic way that I can see to make virtio work with PV guests
> is to write "virtio-xenstore".
Hrm. What's technically keeping you from doing MMIO with PV guests?
Alex
next prev parent reply other threads:[~2011-06-30 14:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-29 13:59 [Qemu-devel] Questions on DeviceState and Virtio infrastructure Wei Liu
2011-06-30 8:31 ` Alexander Graf
2011-06-30 8:44 ` Wei Liu
2011-06-30 10:21 ` Stefano Stabellini
2011-06-30 11:12 ` Alexander Graf
2011-06-30 14:11 ` Stefano Stabellini
2011-06-30 14:28 ` Alexander Graf [this message]
2011-06-30 17:43 ` 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=4E0C8815.8010100@suse.de \
--to=agraf@suse.de \
--cc=anthony.perard@citrix.com \
--cc=jbeulich@novell.com \
--cc=liuw@liuw.name \
--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 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).