xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Oleksandr Grytsov <al1img@gmail.com>
To: Wei Liu <wei.liu2@citrix.com>
Cc: Xen-devel <xen-devel@lists.xenproject.org>,
	Ian Jackson <ian.jackson@eu.citrix.com>,
	Oleksandr Grytsov <oleksandr_grytsov@epam.com>
Subject: Re: [PATCH] libxl: add libxl__is_driver_domain function
Date: Mon, 26 Feb 2018 12:14:55 +0200	[thread overview]
Message-ID: <CACvf2oXkN6xfNmveFT2hQCPdicrdTe1pedLmCXsOVsx8OLBW-A@mail.gmail.com> (raw)
In-Reply-To: <20180223174448.3vmc7a74vr6b42lx@citrix.com>


[-- Attachment #1.1: Type: text/plain, Size: 1730 bytes --]

On Fri, Feb 23, 2018 at 7:44 PM, Wei Liu <wei.liu2@citrix.com> 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 <wei.liu2@citrix.com> 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@citrix.com> wrote:
> > > >
> > > > > On Thu, Dec 14, 2017 at 04:14:12PM +0200, Oleksandr Grytsov wrote:
> > > > > > From: Oleksandr Grytsov <oleksandr_grytsov@epam.com>
> > > > > >
> > > > > > 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.
>

We will check this. Thanks.

-- 
Best Regards,
Oleksandr Grytsov.

[-- Attachment #1.2: Type: text/html, Size: 2855 bytes --]

[-- Attachment #2: Type: text/plain, Size: 157 bytes --]

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

  reply	other threads:[~2018-02-26 10:14 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-14 14:14 [PATCH] libxl: add libxl__is_driver_domain function Oleksandr Grytsov
2017-12-14 14:14 ` Oleksandr Grytsov
2018-01-09 11:34 ` Oleksandr Grytsov
2018-02-05 11:02   ` Oleksandr Grytsov
2018-02-06 12:36 ` Wei Liu
2018-02-06 13:08   ` Oleksandr Grytsov
2018-02-13 12:06     ` Wei Liu
2018-02-13 13:32       ` Oleksandr Grytsov
2018-02-23 17:44         ` Wei Liu
2018-02-26 10:14           ` Oleksandr Grytsov [this message]
2019-10-02 16:30             ` [Xen-devel] " Oleksandr Grytsov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CACvf2oXkN6xfNmveFT2hQCPdicrdTe1pedLmCXsOVsx8OLBW-A@mail.gmail.com \
    --to=al1img@gmail.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=oleksandr_grytsov@epam.com \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xenproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).