From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>, xen-devel@lists.xen.org
Subject: Re: Xen 4.2 and PCI hotplug.
Date: Fri, 21 Dec 2012 16:13:34 -0500 [thread overview]
Message-ID: <20121221211334.GB32523@phenom.dumpdata.com> (raw)
In-Reply-To: <50D1E67F02000078000B1791@nat28.tlf.novell.com>
On Wed, Dec 19, 2012 at 03:08:31PM +0000, Jan Beulich wrote:
> >>> On 19.12.12 at 15:36, Andrew Cooper <andrew.cooper3@citrix.com> wrote:
> > On 19/12/2012 09:14, Zhang, Xiantao wrote:
> >>> -----Original Message-----
> >>> From: Jan Beulich [mailto:JBeulich@suse.com]
> >>> Sent: Wednesday, December 19, 2012 4:48 PM
> >>> To: Zhang, Xiantao
> >>> Cc: Konrad Rzeszutek Wilk; xen-devel
> >>> Subject: Re: [Xen-devel] Xen 4.2 and PCI hotplug.
> >>>
> >>>>>> On 19.12.12 at 09:13, "Zhang, Xiantao" <xiantao.zhang@intel.com>
> >>> wrote:
> >>>> Are you playing with Xen ? so far, Xen doesn't support PCIe device
> >>>> hot-plug feature yet.
> >>> When saying Xen, I assume you mean the pv-ops kernel instead? So far I was
> >>> under the impression that this worked even with the very old 2.6.18 tree (as
> >>> much or as little as hotplug there worked in the native case). And given
> > that
> >>> there are no special requirements on the hypervisor to make this work, it's
> >>> not even obvious to me what would be missing in the pv-ops kernel to make
> >>> it work.
> >> Oh, my fault! Perhaps we don't need to do anything for pv-ops kernel to
> > support device hot-plug if native system has it supported. Actually, we
> > didn't do such testings before, since it is a native feature, not a
> > Xen-specific one.
> >> Xiantao
> >
> > My current understanding is that on boot, Xen scans the PCI bus, then
> > dom0 rescans it later. If a hotplug event gets serviced by dom0, does
> > there not need to be some hypercall informing Xen that a new device has
> > appeared? I expect PCIPassthrough would not work correctly on a
> > hotplugged device which Xen is unaware of.
>
> Sure - such a hypercall exists and is - from all I can tell - being made
> not only during the boot time bus scan, but also during hotplug
> processing. See drivers/xen/pci.c.
Right. What I am not sure about - and this is why I am asking Intel - whether
that notifier gets called _after_ dom0 has interogated the new PCI device.
And if so, would Xen (which gets trapped on the 0xcf8) would not let dom0
actually interogate the new BDF b/c it hasn't been told about this BDF
existence.
This is all speculation - and I might be very well completly wrong about
all of this - hence this email-thread.
Testing would of course tell for sure, but I am not sure if I even have
such hardware.
>
> Jan
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
>
next prev parent reply other threads:[~2012-12-21 21:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-18 22:46 Xen 4.2 and PCI hotplug Konrad Rzeszutek Wilk
2012-12-19 8:13 ` Zhang, Xiantao
2012-12-19 8:47 ` Jan Beulich
2012-12-19 9:14 ` Zhang, Xiantao
2012-12-19 14:36 ` Andrew Cooper
2012-12-19 15:08 ` Jan Beulich
2012-12-21 21:13 ` Konrad Rzeszutek Wilk [this message]
2012-12-21 21:09 ` Konrad Rzeszutek Wilk
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=20121221211334.GB32523@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=xen-devel@lists.xen.org \
/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).