From: "Zhai, Edwin" <edwin.zhai@intel.com>
To: xen-devel <xen-devel@lists.xensource.com>
Cc: "Zhai, Edwin" <edwin.zhai@intel.com>
Subject: pci dev config issue
Date: Wed, 26 Dec 2007 08:42:44 +0800 [thread overview]
Message-ID: <20071226004244.GS11693@edwin-srv.sh.intel.com> (raw)
I saw the pci dev's config is different from vbd/vnif with following comments:
# Parsing the device SXP's. In most cases, the SXP looks
# like this:
#
# [device, [vif, [mac, xx:xx:xx:xx:xx:xx], [ip 1.3.4.5]]]
#
# However, for PCI devices it looks like this:
#
# [device, [pci, [dev, [domain, 0], [bus, 0], [slot, 1]]]]
#
# It seems the reasoning for this difference is because
# pciif.py needs all the PCI device configurations at
# the same time when creating the devices.
So multiple pci devices sit in one single config entry with single uuid(see
following configs), which make device handling difficult(consider if support
hotplug).
Can anybody explain why pciif.py needs all pci devs configured at one time?
Is it still valid now? If not, can I remove this limitation?
=============== multiple vbd config ===================
vbd = ""
769 = ""
virtual-device = "769"
device-type = "disk"
protocol = "x86_32-abi"
backend-id = "0"
state = "4"
backend = "/local/domain/0/backend/vbd/6/769"
ring-ref = "9"
event-channel = "7"
833 = ""
virtual-device = "833"
device-type = "disk"
protocol = "x86_32-abi"
backend-id = "0"
state = "3"
backend = "/local/domain/0/backend/vbd/6/833"
ring-ref = "790"
event-channel = "9"
================ multiple pci config ===================
pci = ""
8 = ""
0 = ""
domain = "ExampleDomain"
frontend = "/local/domain/8/device/pci/0"
uuid = "7f2dc1a1-d0de-ebf0-37fd-67ff0103c3c9"
dev-1 = "0000:03:00.00"
dev-0 = "0000:02:00.00"
state = "4"
online = "1"
frontend-id = "8"
num_devs = "2"
root-0 = "0000:00"
root_num = "1"
--
best rgds,
edwin
next reply other threads:[~2007-12-26 0:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-26 0:42 Zhai, Edwin [this message]
2008-01-07 1:47 ` pci dev config issue Mark Williamson
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=20071226004244.GS11693@edwin-srv.sh.intel.com \
--to=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.