From: "Zhai, Edwin" <edwin.zhai@intel.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: Xen Developers <xen-devel@lists.xensource.com>,
Keir Fraser <keir.fraser@eu.citrix.com>,
"Zhai, Edwin" <edwin.zhai@intel.com>
Subject: issue in unplug qemu PCI devices
Date: Fri, 12 Feb 2010 16:48:25 +0800 [thread overview]
Message-ID: <4B7515D9.7060407@intel.com> (raw)
IOEMU change set e7911109 uses Magic ioport (0x10) protocol for
negotating with guest PV drivers during startup, and allowing PV drivers
to disable hardware emulations thus preventing guest from seeing the
same device through two paths.
But when I tried PV drivers in xen upstream, this unplug logic never
succeed. PV driver uses following io sequence to interact with
platform_pci device in qemu:
1. inw 0x10
2. inb 0x12
3. outw(0x12, 0xbeef)
4. outl(0x10,0xdead)
But I only saw 1&2 happened in xen io instruction
emulation(x86_emulate), while 3&4 seemed to lost so the unplug will
never happen.
Are you aware of this issue? Or some suggestion for debugging?
BTW, the unplug logic itself has some issues also:
1. Pass-through NICs are also unplugged, although them have different
path with vnif and emulated NIC.
2. Unplug happens as long as inserting the xen_platform_pci module
regardless of existence of PVed device in the config file. End user
likely to unplug all the PCI device by accident.
3. Inserting xen_platform_pci module would unplug all the devices, which
is not reasonable. E.g. end user only has vbd driver, but all NICs are
also unplugged.
next reply other threads:[~2010-02-12 8:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-12 8:48 Zhai, Edwin [this message]
2010-02-12 17:14 ` issue in unplug qemu PCI devices Stefano Stabellini
2010-02-12 21:57 ` Ky Srinivasan
2010-02-15 14:10 ` Ian Jackson
2010-02-15 14:14 ` Stefano Stabellini
2010-02-17 10:04 ` Edwin Zhai
2010-02-17 11:08 ` Stefano Stabellini
2010-02-21 0:09 ` Zhai, Edwin
2010-02-15 14:07 ` Ian Jackson
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=4B7515D9.7060407@intel.com \
--to=edwin.zhai@intel.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=keir.fraser@eu.citrix.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).