All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Martin <furryfuttock@gmail.com>
To: xen-users@lists.xenproject.org
Cc: Ian Campbell <ian.campbell@citrix.com>,
	George Dunlap <George.Dunlap@eu.citrix.com>,
	Ian Jackson <Ian.Jackson@eu.citrix.com>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
	David Vrabel <david.vrabel@citrix.com>,
	Boris Ostrovsky <boris.ostrovsky@oracle.com>,
	Atom2 <ariel.atom2@web2web.at>,
	Roger Pau Monne <roger.pau@citrix.com>
Subject: 10s shutdown delay for PV guests with PCI passthrough
Date: Thu, 17 Jul 2014 15:41:04 +0100	[thread overview]
Message-ID: <323082597.20140717154104@gmail.com> (raw)

Hi all,

I'm not sure whether this is related to Atom2's post "substantial
shutdown delay for PV guests with PCI -passthrough", I didn't see any
resolution to it and I am seeing something similar, but slightly
different.

I get a 10s delay shutting down my PV, I have implemented the code as
I see it in mini-os:

1.- frontend sets state XenbusStateClosing and waits for backend to go
to state >= XenbusStateClosing.

2.- frontend sets state XenbusStateClosed and waits for backend to go
to state >= XenbusStateClosed

3.- frontend set state XenbusStateInitialising and waits for frontend
to go to a state in the interval [XenbusStateInitWait,
XenbusStateClosed).

If I perform step 3 then the frontend never exits as the backend state
stays at XenbusStateClosed

If I do not perform step 3 then PV shutsdown after a 10s timeout.

Is this mini-os implementation in sync with the pciback
implementation? Is there a step I have missed?

-- 
Best regards,
 Simon                          mailto:furryfuttock@gmail.com

             reply	other threads:[~2014-07-17 14:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-17 14:41 Simon Martin [this message]
2014-07-18 18:45 ` 10s shutdown delay for PV guests with PCI passthrough Konrad Rzeszutek Wilk
2014-07-20 20:01   ` Simon Martin
2014-08-04 13:53     ` Is: Xen pci backend state transition from Closed -> Initialized broken. Was:Re: " 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=323082597.20140717154104@gmail.com \
    --to=furryfuttock@gmail.com \
    --cc=George.Dunlap@eu.citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=ariel.atom2@web2web.at \
    --cc=boris.ostrovsky@oracle.com \
    --cc=david.vrabel@citrix.com \
    --cc=ian.campbell@citrix.com \
    --cc=roger.pau@citrix.com \
    --cc=xen-devel@lists.xen.org \
    --cc=xen-users@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.