[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1267697925.11737.32107.camel@zakaz.uk.xensource.com>
Date: Thu, 4 Mar 2010 10:18:45 +0000
From: Ian Campbell <Ian.Campbell@...rix.com>
To: Stefano Stabellini <Stefano.Stabellini@...citrix.com>
CC: Jeremy Fitzhardinge <jeremy@...p.org>,
Sheng Yang <sheng@...ux.intel.com>,
Keir Fraser <Keir.Fraser@...citrix.com>,
Jeremy Fitzhardinge <Jeremy.Fitzhardinge@...rix.com>,
Ian Pratt <Ian.Pratt@...citrix.com>,
xen-devel <xen-devel@...ts.xensource.com>,
"Yaozu (Eddie) Dong" <eddie.dong@...el.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [Xen-devel] [PATCH 3/7] xen/hvm: Xen PV extension of HVM
initialization
On Wed, 2010-03-03 at 17:41 +0000, Stefano Stabellini wrote:
> On Wed, 3 Mar 2010, Jeremy Fitzhardinge wrote:
> > On 03/03/2010 03:35 AM, Stefano Stabellini wrote:
> > > Give a look at the fourth patch of the series I just posted: it
> > > introduces a simple driver for the Xen PCI platform device to initialize
> > > xenbus and gran table later on when running in a HVM domain, at the same
> > > time leaving the PV case as it is.
> > >
> >
> > Yes, I noticed that. Do the PV drivers cope with having the PCI
> > probe/xenbus setup after their init functions have been called, or do
> > you make sure the PCI probe happens early?
> >
>
> Nope, they seem to cope fine so far.
xenbus_frontend_register is basically just driver_register so it should
be safe to call even before the register_bus(xenbusfoo) call. Things
shouldn't kick off until xen_probe() is called which either happens
explicitly in xenbus_probe_init() or via probe_work which contains a
xenstored_ready check.
Ian.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists