xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Olaf Hering <olaf@aepfle.de>
To: Wei Liu <wei.liu2@citrix.com>
Cc: Ian Jackson <Ian.Jackson@eu.citrix.com>,
	Ian Campbell <ian.campbell@citrix.com>,
	xen-devel@lists.xen.org
Subject: Re: xl dev-detach hangs with missing frontends
Date: Fri, 12 Feb 2016 15:53:06 +0100	[thread overview]
Message-ID: <20160212145306.GA14753@aepfle.de> (raw)
In-Reply-To: <20160212140752.GA5427@citrix.com>

On Fri, Feb 12, Wei Liu wrote:

> CC'ing other tools maintainer.
> 
> On Thu, Feb 11, 2016 at 11:37:49AM +0100, Olaf Hering wrote:
> > How should libxl__initiate_device_generic_remove deal with devices which
> 
> I think you meant libxl__initiate_device_remove. There is no function
> called libxl__initiate_device_generic _remove.

Not yet.

> > have no frontend driver? Right now it moves "state" from either
> > XenbusStateInitialising or XenbusStateInitWait to XenbusStateClosing.
> > Then it expects the backend to move "state" to XenbusStateClosed. This
> > will never happen, at least for netback and scsiback. The result is a 10
> > second delay.
> > 
> 
> I don't think there is a way to tell whether there is no frontend driver
> or the frontend driver is just too slow.

To handle this the code should check the current value of "state". If
its XenbusStateInitialising or XenbusStateInitWait nothing should be
done.

Olaf

  reply	other threads:[~2016-02-12 14:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-11 10:37 xl dev-detach hangs with missing frontends Olaf Hering
2016-02-12 14:07 ` Wei Liu
2016-02-12 14:53   ` Olaf Hering [this message]
2016-02-12 16:56     ` Wei Liu

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=20160212145306.GA14753@aepfle.de \
    --to=olaf@aepfle.de \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=ian.campbell@citrix.com \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xen.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).