From: Yosuke Iwamatsu <y-iwamatsu@ab.jp.nec.com>
To: xen-devel@lists.xensource.com, xen-api@lists.xensource.com
Subject: [PATCH][0/3] XenAPI: Add PCI Assignment Support
Date: Wed, 02 Jul 2008 20:36:07 +0900 [thread overview]
Message-ID: <486B6827.3090700@ab.jp.nec.com> (raw)
Hi all,
This series of patches is an attempt to support pci pass-through device
assignment via xen-api.
There already is 'PCI_bus' parameter in VM class to specify pci device
to be assigned, but it doesn't work now. Another problem is that pci
device hotplug/coldplug cannot be supported with the current model.
So I decided to implement fully-functional pci assignment support to
xen-api. Below is the basic design of new class models.
PPCI: Represents physical pci devices belonging to the host.
ppci instances are automatically generated by xend and contain
domain:bus:slot:func number, vendor name, device name and
other information.
DPCI: Represents direct pci devices. dpci instances work as connectors
between a vm and a physical pci device. Creation of a dpci device
will result in attachment of the pci device and deletion will
result in detachment.
+------------+ * 1 +----------+
| VM |----------| host |
+------------+ +----------+
1 | | 1
| |
* | | *
+-------------+ 0,1 1 +----------+
| DPCI |---------| PPCI |
+-------------+ +----------+
BTW I'm aware that there is xen-api community project going on.
If there's any decision made about discussing/merging procedure of
xen-api related patches, please let me know.
Technical suggestions and comments are welcome, of course.
Regards,
-----------------------
Yosuke Iwamatsu
NEC Corporation
next reply other threads:[~2008-07-02 11:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-02 11:36 Yosuke Iwamatsu [this message]
2008-07-10 8:55 ` [PATCH][0/3] XenAPI: Add PCI Assignment Support Yosuke Iwamatsu
2008-07-28 9:04 ` [PATCH] Update Document ([PATCH][0/3] XenAPI: Add PCI Assignment Support) Yosuke Iwamatsu
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=486B6827.3090700@ab.jp.nec.com \
--to=y-iwamatsu@ab.jp.nec.com \
--cc=xen-api@lists.xensource.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 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.