|
|
|
|
|
|
|
|
|
|
xen-devel
[Xen-devel] 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
|
<Prev in Thread] |
Current Thread |
[Next in Thread> |
- [Xen-devel] xenbus device state transitions,
James Harper <=
|
|
|
|
|