[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] xenbus device state transitions


  • To: <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: "James Harper" <james.harper@xxxxxxxxxxxxxxxx>
  • Date: Thu, 24 Jun 2010 10:43:09 +1000
  • Delivery-date: Wed, 23 Jun 2010 17:43:56 -0700
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcsTNjd81GU3jRVwTL6RqQBEvgbfaQ==
  • Thread-topic: xenbus device state transitions

In my GPLPV drivers, I have put the state transition (eg Initialising ->
InitWait -> Initialised -> Connected) management into the bus driver so
it handles all of that for the child drivers (vbd, vif, vscsi, vusb,
etc). None of them are quite the same though, some skip states while
others don't and so my code seems to be more exception than rule.

Is this just the way it is?

The problem I'm having now is that vscsi backend goes to Closed when my
driver unloads, and stays there until the frontend goes to Initialising,
while other driver backends will reset to InitWait once the frontend
goes to InitWait (or something like that - different to vscsi anyway).

Thanks

James

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.