From: Simon Horman <horms@verge.net.au>
To: "Zhai, Edwin" <edwin.zhai@intel.com>
Cc: Christian Tramnitz <chris.ace@gmx.net>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
"Han, Weidong" <weidong.han@intel.com>,
Keir Fraser <keir.fraser@eu.citrix.com>,
"Cui, Dexuan" <dexuan.cui@intel.com>
Subject: Re: Bug in pci-detach (Was: Re: Re: VT-d HowTo Update)
Date: Thu, 23 Apr 2009 10:36:36 +1000 [thread overview]
Message-ID: <20090423003636.GD4473@verge.net.au> (raw)
In-Reply-To: <49EED51A.30508@intel.com>
On Wed, Apr 22, 2009 at 04:28:10PM +0800, Zhai, Edwin wrote:
> Simon,
>
> In previous solution, the "vslots" entry in xenstore is only used for
> qemu => xend communication, and not present until qemu create it.
> But with support of vslot in config file, this xenstore entry are
> created by xend at the beginning... Now xend will get value from itself
> (AUTO_PHP_SLOT when not specified) without waiting for qemu:(
>
> Temp solution is let xend to check if the return value is AUTO_PHP_SLOT,
> but xend still can't know qemu's response. We need make sure, if can
> not support specified vslots in config, qemu should notify xend. Then
> xend should know if this is qemu's response or the specified vslots
> requirement.
After some investigation it turns out that the problem was not with
the use of vslots - which is still only used for qemu=>xend communication.
The problem was with renaming vslt to vslots because in the dictionary
that describes a PCI device, these entries were different.
I have posted a patch to resolve this problem to xen-devel as
"xm: Fix hot-unplug of statically-assigned devices".
http://lists.xensource.com/archives/html/xen-devel/2009-04/msg00897.html
--
Simon Horman
VA Linux Systems Japan K.K. Satellite Lab in Sydney, Australia
H: www.vergenet.net/~horms/ W: www.valinux.co.jp/en
next prev parent reply other threads:[~2009-04-23 0:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-22 1:44 Bug in pci-detach (Was: Re: Re: VT-d HowTo Update) Simon Horman
2009-04-22 2:18 ` Akio Takebe
2009-04-22 4:12 ` Simon Horman
2009-04-22 2:50 ` Simon Horman
2009-04-22 3:37 ` Zhai, Edwin
2009-04-22 4:13 ` Simon Horman
2009-04-22 8:28 ` Zhai, Edwin
2009-04-23 0:36 ` Simon Horman [this message]
2009-04-23 0:46 ` Simon Horman
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=20090423003636.GD4473@verge.net.au \
--to=horms@verge.net.au \
--cc=chris.ace@gmx.net \
--cc=dexuan.cui@intel.com \
--cc=edwin.zhai@intel.com \
--cc=keir.fraser@eu.citrix.com \
--cc=weidong.han@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.