All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Roger Pau Monné" <roger.pau@citrix.com>
To: "Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>
Cc: Anthony Perard <anthony.perard@citrix.com>,
	Ian Jackson <ian.jackson@citrix.com>, Wei Liu <wl@xen.org>,
	"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Subject: Re: [Xen-devel] [PATCH] libxl: create backend/ xenstore dir for driver domains
Date: Wed, 25 Mar 2020 11:36:34 +0100	[thread overview]
Message-ID: <20200325103634.GB28601@Air-de-Roger> (raw)
In-Reply-To: <20200324024530.GJ2995@mail-itl>

On Tue, Mar 24, 2020 at 03:45:30AM +0100, Marek Marczykowski-Górecki wrote:
> On Mon, Mar 23, 2020 at 04:35:12PM +0100, Roger Pau Monné wrote:
> > On Mon, Jan 06, 2020 at 05:03:40PM +0100, Marek Marczykowski-Górecki wrote:
> > > >  * There needs to be a way to deal with a broken/unresponsive driver
> > > >    domain.  That will involve not waiting for the backend so must
> > > >    involve simply deleting the backend from xenstore.
> > > 
> > > It's already there: if driver domain fails to set .../state = 6 within
> > > a timeout, toolstack will forcibly remove the entry.
> > 
> > Would it work to change this and instead of monitor .../state = 6
> > monitor that the parent directory still exist?
> 
> That could be a good idea, to avoid introducing yet another (set of)
> callback. I'll look into it, it may require different handling of
> dom0/non-dom0 backend.

Yes, the domain handling the backend needs to watch .../state, while
the control domain (where the toolstack actually runs) would need to
watch .../ AFAICT.

As you say, I think you could maybe reuse some of the code and add a
special case for the toolstack domain when the backend runs in a
driver domain.

Thanks, Roger.


      reply	other threads:[~2020-03-25 10:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-05  8:41 [Xen-devel] [PATCH] libxl: create backend/ xenstore dir for driver domains Marek Marczykowski-Górecki
2020-01-06 14:20 ` Ian Jackson
2020-01-06 14:38   ` Marek Marczykowski-Górecki
2020-01-06 15:40     ` Ian Jackson
2020-01-06 16:03       ` Marek Marczykowski-Górecki
2020-03-15 22:20         ` Marek Marczykowski-Górecki
2020-03-23 15:35         ` Roger Pau Monné
2020-03-24  2:45           ` [Xen-devel] " Marek Marczykowski-Górecki
2020-03-25 10:36             ` Roger Pau Monné [this message]

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=20200325103634.GB28601@Air-de-Roger \
    --to=roger.pau@citrix.com \
    --cc=anthony.perard@citrix.com \
    --cc=ian.jackson@citrix.com \
    --cc=marmarek@invisiblethingslab.com \
    --cc=wl@xen.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.