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: Thu, 02 Apr 2009 09:27:58 +0100	[thread overview]
Message-ID: <C5FA359E.64C3%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <1238659983.4271.6.camel@moonstone.uk.level5networks.com>

On 02/04/2009 09:13, "Kieran Mansley" <kmansley@solarflare.com> wrote:

> On Wed, 2009-04-01 at 11:39 -0700, Brendan Cully wrote:
>> I'm afraid my memory of the kernel suspend mechanics has gotten a bit
>> rusty over the last few months, so I may be off-base here. But I
>> thought that xs_suspend masked watches until xs_reusume or
>> xs_suspend_cancel? If that is the case, isn't that on its own enough
>> to protect netfront?
> 
> If that's the case, it should be enough, yes.
> 
> Do watches that would have fired during that time fire at the end of
> masked period?  If not, we'd still have to access xenstore on suspend
> cancel to check if we've missed a change.

I don't think watches get lost across suspend-cancel, just delayed.

 -- Keir

  reply	other threads:[~2009-04-02  8:27 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
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 [this message]
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=C5FA359E.64C3%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.