| |
|
 |
|
 |
|
|
|
| |
|
|
xen-devel
Re: [Xen-devel] [PATCH 3/7] xen/hvm: Xen PV extension of HVM initializat
|
To: |
Ian Campbell <Ian.Campbell@xxxxxxxxxx> |
|
Subject: |
Re: [Xen-devel] [PATCH 3/7] xen/hvm: Xen PV extension of HVM initialization |
|
From: |
Jeremy Fitzhardinge <jeremy@xxxxxxxx> |
|
Date: |
Tue, 02 Mar 2010 12:17:12 -0800 |
|
Cc: |
xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, Stefano Stabellini <Stefano.Stabellini@xxxxxxxxxxxxx>, "Yaozu \(Eddie\) Dong" <eddie.dong@xxxxxxxxx>, "linux-kernel@xxxxxxxxxxxxxxx" <linux-kernel@xxxxxxxxxxxxxxx>, Ian Pratt <Ian.Pratt@xxxxxxxxxxxxx>, Jeremy Fitzhardinge <Jeremy.Fitzhardinge@xxxxxxxxxx>, Keir Fraser <Keir.Fraser@xxxxxxxxxxxxx>, Sheng Yang <sheng@xxxxxxxxxxxxxxx> |
|
Delivery-date: |
Tue, 02 Mar 2010 12:17:45 -0800 |
|
Envelope-to: |
www-data@xxxxxxxxxxxxxxxxxxx |
|
In-reply-to: |
<1267521735.11737.23107.camel@xxxxxxxxxxxxxxxxxxxxxx> |
|
List-help: |
<mailto:xen-devel-request@lists.xensource.com?subject=help> |
|
List-id: |
Xen developer discussion <xen-devel.lists.xensource.com> |
|
List-post: |
<mailto:xen-devel@lists.xensource.com> |
|
List-subscribe: |
<http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe> |
|
List-unsubscribe: |
<http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe> |
|
References: |
<1267436315-24486-1-git-send-email-sheng@xxxxxxxxxxxxxxx> <1267436315-24486-4-git-send-email-sheng@xxxxxxxxxxxxxxx> <4B8C63B0.2090507@xxxxxxxx> <201003020938.53630.sheng@xxxxxxxxxxxxxxx> <1267521735.11737.23107.camel@xxxxxxxxxxxxxxxxxxxxxx> |
|
Sender: |
xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
|
User-agent: |
Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.7) Gecko/20100120 Fedora/3.0.1-1.fc12 Lightning/1.0b2pre Thunderbird/3.0.1 |
On 03/02/2010 01:22 AM, Ian Campbell wrote:
On Tue, 2010-03-02 at 01:38 +0000, Sheng Yang wrote:
A annoy thing in pv drivers is that it would test if the domain type
is _NOT_ XEN_NATIVE. So set the domain to XEN_HVM_DOMAIN would result
in PV driver initialization then probably panic.
What _actually_ panics?
Registration of the frontend devices should be completely harmless
(apart from a little wasted RAM) unless a xenbus driver manages to come
up and enumerate the xen bus and cause the ->probe function run.
You should be gating the xenbus startup on the availability of PV
functionality not the individual driver registrations. This keeps the
test in a single easy to maintain place.
Compare with pci_register_driver and all of the callers of that function
-- not a single one of them has an "is_pci_available" test anywhere.
The problem is that it currently assumes xenbus is initialized by the
time the PV drivers init, because in a PV boot xenbus gets initted very
early. We need to change it so that it can cope with drivers being
initialized and registering with xenbus before it has been initialized.
We have the same problem with plain PV-on-HVM drivers as xenbus only
comes up as a result of probing the Xen PCI platform device, which may
be after the PV drivers' init functions have been called.
J
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
| |
|
Home