Re: [Xen-devel] [PATCH] libxl: add libxl__is_driver_domain function

2019-10-02 Thread Oleksandr Grytsov
On Mon, Feb 26, 2018 at 12:14 PM Oleksandr Grytsov wrote: > > On Fri, Feb 23, 2018 at 7:44 PM, Wei Liu wrote: >> >> On Tue, Feb 13, 2018 at 03:32:04PM +0200, Oleksandr Grytsov wrote: >> > On Tue, Feb 13, 2018 at 2:06 PM, Wei Liu wrote: >> > >> > > On Tue, Feb 06, 2018 at 03:08:45PM +0200, Oleksa

Re: [Xen-devel] [PATCH] libxl: add libxl__is_driver_domain function

2018-02-26 Thread Oleksandr Grytsov
On Fri, Feb 23, 2018 at 7:44 PM, Wei Liu wrote: > On Tue, Feb 13, 2018 at 03:32:04PM +0200, Oleksandr Grytsov wrote: > > On Tue, Feb 13, 2018 at 2:06 PM, Wei Liu wrote: > > > > > On Tue, Feb 06, 2018 at 03:08:45PM +0200, Oleksandr Grytsov wrote: > > > > On Tue, Feb 6, 2018 at 2:36 PM, Wei Liu w

Re: [Xen-devel] [PATCH] libxl: add libxl__is_driver_domain function

2018-02-23 Thread Wei Liu
On Tue, Feb 13, 2018 at 03:32:04PM +0200, Oleksandr Grytsov wrote: > On Tue, Feb 13, 2018 at 2:06 PM, Wei Liu wrote: > > > On Tue, Feb 06, 2018 at 03:08:45PM +0200, Oleksandr Grytsov wrote: > > > On Tue, Feb 6, 2018 at 2:36 PM, Wei Liu wrote: > > > > > > > On Thu, Dec 14, 2017 at 04:14:12PM +020

Re: [Xen-devel] [PATCH] libxl: add libxl__is_driver_domain function

2018-02-13 Thread Oleksandr Grytsov
On Tue, Feb 13, 2018 at 2:06 PM, Wei Liu wrote: > On Tue, Feb 06, 2018 at 03:08:45PM +0200, Oleksandr Grytsov wrote: > > On Tue, Feb 6, 2018 at 2:36 PM, Wei Liu wrote: > > > > > On Thu, Dec 14, 2017 at 04:14:12PM +0200, Oleksandr Grytsov wrote: > > > > From: Oleksandr Grytsov > > > > > > > > We

Re: [Xen-devel] [PATCH] libxl: add libxl__is_driver_domain function

2018-02-13 Thread Wei Liu
On Tue, Feb 06, 2018 at 03:08:45PM +0200, Oleksandr Grytsov wrote: > On Tue, Feb 6, 2018 at 2:36 PM, Wei Liu wrote: > > > On Thu, Dec 14, 2017 at 04:14:12PM +0200, Oleksandr Grytsov wrote: > > > From: Oleksandr Grytsov > > > > > > We have following arm-based setup: > > > > > > - Dom0 with xen an

Re: [Xen-devel] [PATCH] libxl: add libxl__is_driver_domain function

2018-02-06 Thread Oleksandr Grytsov
On Tue, Feb 6, 2018 at 2:36 PM, Wei Liu wrote: > On Thu, Dec 14, 2017 at 04:14:12PM +0200, Oleksandr Grytsov wrote: > > From: Oleksandr Grytsov > > > > We have following arm-based setup: > > > > - Dom0 with xen and xen tools; > > - Dom1 with device backends (but it is not the driver domain); > >

Re: [Xen-devel] [PATCH] libxl: add libxl__is_driver_domain function

2018-02-06 Thread Wei Liu
On Thu, Dec 14, 2017 at 04:14:12PM +0200, Oleksandr Grytsov wrote: > From: Oleksandr Grytsov > > We have following arm-based setup: > > - Dom0 with xen and xen tools; > - Dom1 with device backends (but it is not the driver domain); What is your definition of a "driver domain"? What does it do i

Re: [Xen-devel] [PATCH] libxl: add libxl__is_driver_domain function

2018-02-05 Thread Oleksandr Grytsov
On Tue, Jan 9, 2018 at 1:34 PM, Oleksandr Grytsov wrote: > On Thu, Dec 14, 2017 at 4:14 PM, Oleksandr Grytsov > wrote: > >> From: Oleksandr Grytsov >> >> We have following arm-based setup: >> >> - Dom0 with xen and xen tools; >> - Dom1 with device backends (but it is not the driver domain); >>

Re: [Xen-devel] [PATCH] libxl: add libxl__is_driver_domain function

2018-01-09 Thread Oleksandr Grytsov
On Thu, Dec 14, 2017 at 4:14 PM, Oleksandr Grytsov wrote: > From: Oleksandr Grytsov > > We have following arm-based setup: > > - Dom0 with xen and xen tools; > - Dom1 with device backends (but it is not the driver domain); > - Dom2 with device frontend; > > On Dom2 destroying we have timeout err

[Xen-devel] [PATCH] libxl: add libxl__is_driver_domain function

2017-12-14 Thread Oleksandr Grytsov
From: Oleksandr Grytsov libxl__is_driver_domain determines the driver domain by presence of libxl entry in the domain xen store. Use this function on device destroy to properly manage cleanup in case backends are located on domain with non zero id. Signed-off-by: Oleksandr Grytsov --- tools/li

[Xen-devel] [PATCH] libxl: add libxl__is_driver_domain function

2017-12-14 Thread Oleksandr Grytsov
From: Oleksandr Grytsov We have following arm-based setup: - Dom0 with xen and xen tools; - Dom1 with device backends (but it is not the driver domain); - Dom2 with device frontend; On Dom2 destroying we have timeout error. Because xl treats our Dom1 as driver domain and waits for backend path