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

[Wei Liu <wei.liu2@xxxxxxxxxx>]

On Tue, Feb 13, 2018 at 03:32:04PM +0200, Oleksandr Grytsov wrote:
> On Tue, Feb 13, 2018 at 2:06 PM, Wei Liu <wei.liu2@xxxxxxxxxx> 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 <wei.liu2@xxxxxxxxxx> wrote:
> > >
> > > > On Thu, Dec 14, 2017 at 04:14:12PM +0200, Oleksandr Grytsov wrote:
> > > > > From: Oleksandr Grytsov <oleksandr_grytsov@xxxxxxxx>
> > > > >
> > > > > 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 in this
> > > > case?
> > > >
> > > > I seem to have seen people use this term in different contexts to mean
> > > > slightly different things. I need to figure out what you actually mean
> > > > first.
> > > >
> > > >
> > > I see in the libxl/xl sources that closing PV devices is done differently
> > > in case backends are in Dom0 and are in other domain. It is called as
> > > driver domain in the sources. So, I don't have clear understanding
> > > what does it mean. In our setup backends are in Dom1 and xl is in Dom0.
> > > And I see that xl dosn't close PV device on domain reboot or shutdown.
> >
> > Do you run xl devd in your backend domain?
> >
> > Wei.
> >
> 
> No I don't

Can you try that? I think xl devd should clean up the stale entries --
that's how we envisage driver domains to be used.

Wei.

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/xen-devel