All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sander Eikelenboom <linux@eikelenboom.it>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: xen-devel <xen-devel@lists.xensource.com>,
	Ian Jackson <ian.jackson@eu.citrix.com>,
	Ian Campbell <Ian.Campbell@citrix.com>
Subject: Re: xl shutdown --wait "racy"
Date: Wed, 16 Apr 2014 17:21:57 +0200	[thread overview]
Message-ID: <1022190423.20140416172157@eikelenboom.it> (raw)
In-Reply-To: <20140416151934.GA27066@phenom.dumpdata.com>


Wednesday, April 16, 2014, 5:19:34 PM, you wrote:

> On Wed, Apr 16, 2014 at 04:08:21PM +0200, Sander Eikelenboom wrote:
>> Hi Ian (C|J) Konrad,
>> 
>> I'm currently trying to workaround the pci-(detach|assignable-remove) issues i 
>> reported earlier. 
>> 
>> The workaround i thought of was:
>> - shutting down the guest
>> - starting it without 1 of the original devices passed through
>> - use xl pci-assignable-remove and bind the device to the dom0 driver.
>> 
>> But during this i noticed that a "xl shutdown --wait" does wait .. but returns:
>> - Before the domain is removed from for instance "xl list", it still listed there in 
>> "--ps--" state.
>> - before pciback has done it's restore config space magic.

> Which reminds me - when you do this - are you (or any processes) in the /sysfs directory?
> I've been having a hard-time reproducing the issue. Sometimes I see it, but then if I try
> again the problem does not show up again.

When i do *what* ? (it's not exactly clear if you are referring to the problem 
i'm trying to workaround .. or the problems i'm finding when trying to 
workaround :-) )

>> 
>> So it seems the wait loop is exiting somewhat prematurely, is this expected ? 
>> 
>> --
>> Sander
>> 

  reply	other threads:[~2014-04-16 15:21 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-16 14:08 xl shutdown --wait "racy" Sander Eikelenboom
2014-04-16 14:13 ` Ian Campbell
2014-04-16 14:26   ` Sander Eikelenboom
2014-04-16 14:33     ` Ian Campbell
2014-04-16 14:55       ` Sander Eikelenboom
2014-04-16 15:02         ` Ian Campbell
2014-04-16 15:10           ` George Dunlap
2014-04-16 15:20           ` Sander Eikelenboom
2014-04-16 16:27             ` Ian Campbell
2014-04-16 17:04               ` Sander Eikelenboom
2014-04-17  8:07                 ` Ian Campbell
2014-04-16 14:29   ` George Dunlap
2014-04-17 18:09     ` Ian Jackson
2014-04-23 13:38       ` Sander Eikelenboom
2014-04-23 13:42         ` Ian Campbell
2014-04-23 13:49           ` Sander Eikelenboom
2014-04-23 14:12             ` Ian Campbell
2014-04-16 15:19 ` Konrad Rzeszutek Wilk
2014-04-16 15:21   ` Sander Eikelenboom [this message]
2014-04-16 17:08     ` Konrad Rzeszutek Wilk

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=1022190423.20140416172157@eikelenboom.it \
    --to=linux@eikelenboom.it \
    --cc=Ian.Campbell@citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=konrad.wilk@oracle.com \
    --cc=xen-devel@lists.xensource.com \
    /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.