From: Brendan Cully <brendan@cs.ubc.ca>
To: xen-devel@lists.xensource.com
Cc: andy@cs.ubc.ca
Subject: Re: [PATCH] Skip vcpu_hotplug for VCPU 0 in smp_resume
Date: Tue, 31 Mar 2009 10:24:25 -0700 [thread overview]
Message-ID: <20090331172423.GA70062@zanzibar.lan> (raw)
In-Reply-To: <ed51e0ec7b8c08b1f191.1238518391@anthrax.cs.ubc.ca>
On Tuesday, 31 March 2009 at 09:53, Brendan Cully wrote:
> Skip vcpu_hotplug for VCPU 0 in smp_resume.
> This function can occasionally take up to 2 seconds to complete,
> and smp_suspend also skips VCPU 0.
I'm doing a bit of testing ahead of releasing Remus, and I've noticed
that there are a couple of places where resuming from suspension can
get stuck for a long time, which can cause Remus to think that the
domain has died. This is one of them.
The other is in the netfront accelerator. It tears down a xenstore
watch on the accelerator path at every suspend, and adds the watch
back on resume. As with any xenstore interaction, this can
occasionally take a very long time. I'm going from faulty memory here,
but I didn't think it was necessary to tear down and restore watches
across suspend. Would it make sense to move the watch remove and add
into the resume hook (taking it completely out of suspend and
suspend_cancel)?
next prev parent reply other threads:[~2009-03-31 17:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-31 16:53 [PATCH] Skip vcpu_hotplug for VCPU 0 in smp_resume Brendan Cully
2009-03-31 17:24 ` Brendan Cully [this message]
2009-03-31 17:35 ` Keir Fraser
2009-03-31 20:04 ` Brendan Cully
2009-04-01 10:26 ` Kieran Mansley
2009-04-01 10:31 ` Keir Fraser
2009-04-01 11:00 ` Kieran Mansley
2009-04-01 18:39 ` Brendan Cully
2009-04-02 8:13 ` Kieran Mansley
2009-04-02 8:27 ` Keir Fraser
2009-04-02 9:13 ` Kieran Mansley
2009-04-07 9:26 ` Kieran Mansley
2009-04-01 20:36 ` Ian Campbell
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=20090331172423.GA70062@zanzibar.lan \
--to=brendan@cs.ubc.ca \
--cc=andy@cs.ubc.ca \
--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.