All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keir Fraser <keir.fraser@eu.citrix.com>
To: Kieran Mansley <kmansley@solarflare.com>,
	Brendan Cully <brendan@cs.ubc.ca>
Cc: "andy@cs.ubc.ca" <andy@cs.ubc.ca>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [PATCH] Skip vcpu_hotplug for VCPU 0 in smp_resume
Date: Wed, 01 Apr 2009 11:31:46 +0100	[thread overview]
Message-ID: <C5F90122.5516%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <1238581584.4440.18.camel@moonstone.uk.level5networks.com>

On 01/04/2009 11:26, "Kieran Mansley" <kmansley@solarflare.com> wrote:

>> Could it be as simple as this? I can't remember what happens if
>> unregister_xenbus_watch is called after the xenbus connection has been
>> reset. Should we just free the guest structures without interacting
>> with xenstore at the start of the resume method?
> 
> It may be possible to synchronise the watch handler with the
> suspend/resume/cancel cycle without removing the watch, but that starts
> to get complicated.

Could we avoid any of this logic executing if there are no net accelerators?

 -- Keir

  reply	other threads:[~2009-04-01 10:31 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
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 [this message]
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=C5F90122.5516%keir.fraser@eu.citrix.com \
    --to=keir.fraser@eu.citrix.com \
    --cc=andy@cs.ubc.ca \
    --cc=brendan@cs.ubc.ca \
    --cc=kmansley@solarflare.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.