From: Wei Liu <liuw@liuw.name>
To: qemu-devel@nongnu.org
Cc: Anthony Perard <anthony.perard@citrix.com>,
Wei LIU <liuw@liuw.name>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: [Qemu-devel] Questions on DeviceState and Virtio infrastructure
Date: Wed, 29 Jun 2011 21:59:03 +0800 [thread overview]
Message-ID: <BANLkTikAizKrkeOpLqsMXYYXJYiuwH7PyQ@mail.gmail.com> (raw)
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).
Here is the problem, say I'm to implement virtio nic for Xen pv guest,
I use Xenbus to probe and initialize the device. When doing
initialization, I am to reuse virtio_net_init, which takes DeviceState
as the first argument -- but I just don't have one in XenDevice. All I
need is to use qemu's virtio infrastructure.
What's the purpose of this DeviceState argument?
If I just construct my own DeviceState and pass it to virtio_net_init,
what will happen? Will qemu emulates virtio nic as usual?
Thanks.
Wei.
next reply other threads:[~2011-06-29 13:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-29 13:59 Wei Liu [this message]
2011-06-30 8:31 ` [Qemu-devel] Questions on DeviceState and Virtio infrastructure 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
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=BANLkTikAizKrkeOpLqsMXYYXJYiuwH7PyQ@mail.gmail.com \
--to=liuw@liuw.name \
--cc=anthony.perard@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 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).