From: BVK Chaitanya <bayapuneni_chaitanya@symantec.com>
To: Keir Fraser <keir.fraser@eu.citrix.com>
Cc: Xen-devel@lists.xensource.com
Subject: Re: [PATCH] serialize suspend-resume process
Date: Thu, 31 Jul 2008 17:27:24 +0530 [thread overview]
Message-ID: <4891A8A4.7010506@symantec.com> (raw)
In-Reply-To: <C4B75DE5.24E7F%keir.fraser@eu.citrix.com>
Keir Fraser wrote:
> On 31/7/08 12:09, "BVK Chaitanya" <bayapuneni_chaitanya@symantec.com> wrote:
>>
>> Below patch makes suspend-resume process serialized.
>
> It's already supposed to be serialised, and there's a loop in xen_suspend()
> to deal with up to one queued suspend request. Your patch may deal with an
> arbitrary number of queued suspend requests, but a sane dom0 control stack
> should never issue more than one suspend request in a suspend-resume cycle.
>
Yes, but there must be a way for dom0 to know that suspend-resume cycle
is completed. Currently dom0 only gets suspend completed notification
-- as part of shutdown hypercall -- but no resume
(xenbus_suspend_cancel) completed notification.
If dom0 issues second suspend request before resume is completed a _new_
kthread is started and will proceed with xen_suspend in parallel. I saw
this hitting BUG_ON in netfront_accelerator_add_watch.
Am i missing anything?
regards,
--
bvk-chaitanya
next prev parent reply other threads:[~2008-07-31 11:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-31 11:09 [PATCH] serialize suspend-resume process BVK Chaitanya
2008-07-31 11:17 ` Keir Fraser
2008-07-31 11:57 ` BVK Chaitanya [this message]
2008-07-31 12:23 ` Keir Fraser
2008-07-31 13:04 ` BVK Chaitanya
2008-07-31 13:07 ` Keir Fraser
2008-07-31 13:34 ` BVK Chaitanya
2008-07-31 13:46 ` Keir Fraser
2008-07-31 14:10 ` BVK Chaitanya
2008-07-31 14:12 ` Neil Turton
2008-07-31 14:36 ` Keir Fraser
2008-07-31 15:27 ` BVK Chaitanya
2008-07-31 15:24 ` Keir Fraser
2008-08-01 5:31 ` BVK Chaitanya
2008-08-01 5:58 ` BVK Chaitanya
2008-08-01 8:01 ` Keir Fraser
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=4891A8A4.7010506@symantec.com \
--to=bayapuneni_chaitanya@symantec.com \
--cc=Xen-devel@lists.xensource.com \
--cc=keir.fraser@eu.citrix.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.