From: cyliu@suse.com
To: xen-devel@lists.xensource.com
Cc: cyliu@suse.com
Subject: [PATCH 0 of 2] pci passthrough: support "managed" pci device in xend for libvirt usage
Date: Thu, 17 Jan 2013 13:29:50 +0800 [thread overview]
Message-ID: <patchbomb.1358400590@linux-1.site> (raw)
One of our customers requests parallel pci passthrough functionality between xen
(xend and libxl) and kvm, including support managed host pci devices. A
"managed" pci device will be made assignable before vm start and reattach to
its original dirver after vm shut off.
Currently, libvirt supports "managed=yes/no" options in pci device definition.
Qemu driver already supports managed pci devices, libxl driver will add that
support in libvirt source code. For xend driver, since it's stateful, libvirt
can't do much things because libvirt doesn't store much informtion and most
work is done by calling xend directly. Even "managed" option won't be stored if
xend doesn't support it. For that reason, this patch series tries to add code in
xend toolstack to support managed pci devices first, then libvirt can call xend
operations directly to support "managed" host pci devices.
Syntax for managed pci device could be:
pci=['0000:00:1a.0,managed=1']
Please share your comments. Thanks!
next reply other threads:[~2013-01-17 5:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-17 5:29 cyliu [this message]
2013-01-17 5:29 ` [PATCH 1 of 2] pci passtrough: add xm pci-assignable-add/remove commands cyliu
2013-01-17 5:29 ` [PATCH 2 of 2] pci passthrough: handle managed pci devices cyliu
2013-01-17 18:00 ` [PATCH 0 of 2] pci passthrough: support "managed" pci device in xend for libvirt usage George Dunlap
2013-01-17 19:12 ` Jim Fehlig
2013-01-18 13:39 ` George Dunlap
2013-01-21 4:50 ` Jim Fehlig
2013-01-21 11:40 ` George Dunlap
2013-01-18 15:48 ` Konrad Rzeszutek Wilk
2013-01-18 16:16 ` Ian Campbell
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=patchbomb.1358400590@linux-1.site \
--to=cyliu@suse.com \
--cc=xen-devel@lists.xensource.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).