Re: [Xen-devel] [PATCH] xen/pci: Deal with toolstack missing an 'XenbusStateClosing'.

2013-06-11 Thread konrad wilk
On 6/11/2013 5:00 AM, George Dunlap wrote: On 06/11/2013 08:29 AM, Jan Beulich wrote: On 10.06.13 at 23:06, Konrad Rzeszutek Wilk wrote: There are two tool-stack that can instruct the Xen PCI frontend and backend to change states: 'xm' (Python code with a daemon), and 'xl' (C library - does n

Re: [Xen-devel] [PATCH] xen/pci: Deal with toolstack missing an 'XenbusStateClosing'.

2013-06-11 Thread George Dunlap
On 06/11/2013 08:29 AM, Jan Beulich wrote: On 10.06.13 at 23:06, Konrad Rzeszutek Wilk wrote: There are two tool-stack that can instruct the Xen PCI frontend and backend to change states: 'xm' (Python code with a daemon), and 'xl' (C library - does not keep state changes). With the 'xm', the p

Re: [Xen-devel] [PATCH] xen/pci: Deal with toolstack missing an 'XenbusStateClosing'.

2013-06-11 Thread Jan Beulich
>>> On 10.06.13 at 23:06, Konrad Rzeszutek Wilk wrote: > There are two tool-stack that can instruct the Xen PCI frontend > and backend to change states: 'xm' (Python code with a daemon), > and 'xl' (C library - does not keep state changes). > > With the 'xm', the path to disconnect a PCI device (