From: "Daniel P. Berrange" <berrange@redhat.com>
To: "Zhai, Edwin" <edwin.zhai@intel.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: [PATCH][HVM] pass-through PCI device hotplug support
Date: Thu, 24 Jan 2008 18:06:56 +0000 [thread overview]
Message-ID: <20080124180656.GC2400@redhat.com> (raw)
In-Reply-To: <20080123155208.GA21201@edwin-srv.sh.intel.com>
On Wed, Jan 23, 2008 at 11:52:09PM +0800, Zhai, Edwin wrote:
> All,
>
> This patch enables HVM guest VT-d device hotplug via a simple ACPI hotplug
> device model. Pls. have a look.
>
> On VT-d side, it's very useful as you can dynamically assign VT-d device to a
> guest as long as it support ACPI hotplug(Linux 2.6, 2000, 2003, XP... pass the
> test).
>
> * Usage is very simple.
> Three new commands are added:
> "xm dpci-list domid" show the current assigned vtd device, like:
> ID domain bus slot func
> 0 0x0 0x02 0x00 0x0
>
> "xm dpci-remove" hot remove the specified vtd device by the ID, like:
> xm dpci-remove EdwinHVMDomainVtd 0
>
> "xm dpci-insert" hot add a new vtd device, like '03:00.0':
> xm dpci-insert EdwinHVMDomainVtd 3 0 0
IMHO we shouldn't have a 'd' on the front of the command names. VT-d is a
vendor specific implementation whose nomenculture doesn't need to be exposed
to users. In addition the existing block & network hotplug commands use
'attach' and 'detach' for their command names. So for sake of consistency
I'd recommend command names of:
pci-list
pci-attach
pci-detach
I think it is useful to use the same unique naming & data for both attach and
detach operations. So if we use a (bus,slot,func) triple for attachment, I
think we should use the same (bus,slot,func) triple for detachment too,
rather than having to make apps / users lookup the dynamically-allocated
'ID' value for the device.
Regards,
Dan.
--
|=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=|
|=- Perl modules: http://search.cpan.org/~danberr/ -=|
|=- Projects: http://freshmeat.net/~danielpb/ -=|
|=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=|
next prev parent reply other threads:[~2008-01-24 18:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-23 15:52 [PATCH][HVM] pass-through PCI device hotplug support Zhai, Edwin
2008-01-24 17:57 ` Keir Fraser
2008-01-24 18:06 ` Daniel P. Berrange [this message]
2008-01-24 18:08 ` Keir Fraser
2008-01-25 1:31 ` Zhai, Edwin
2008-01-25 1:40 ` Daniel P. Berrange
2008-01-25 3:06 ` Zhai, Edwin
2008-01-25 7:41 ` Keir Fraser
-- strict thread matches above, loose matches on Subject: below --
2008-02-15 13:32 Zhai, Edwin
2008-02-15 14:36 ` Keir Fraser
2008-02-17 15:34 ` Zhai, Edwin
2008-02-17 16:43 ` Keir Fraser
2008-02-18 12:53 ` Yosuke Iwamatsu
2008-02-20 3:56 ` Zhai, Edwin
2008-02-20 4:45 ` 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=20080124180656.GC2400@redhat.com \
--to=berrange@redhat.com \
--cc=edwin.zhai@intel.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.