From: Ben Guthro <Benjamin.Guthro@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: George Dunlap <George.Dunlap@eu.citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [PATCH] x86/S3: Restore broken vcpu affinity on resume (v4)
Date: Mon, 1 Apr 2013 15:47:51 -0400 [thread overview]
Message-ID: <5159E467.9040603@citrix.com> (raw)
In-Reply-To: <CAFLBxZYxMyKmcoB+ScJ_SusKSHOnyN_iuSbjfaKw+3jwv0KmQA@mail.gmail.com>
On 03/28/2013 08:18 AM, George Dunlap wrote:
> On Wed, Mar 27, 2013 at 1:13 PM, Ben Guthro <benjamin.guthro@citrix.com> wrote:
>> When in SYS_STATE_suspend, and going through the cpu_disable_scheduler
>> path, save a copy of the current cpu affinity, and mark a flag to
>> restore it later.
>>
>> Later, in the resume process, when enabling nonboot cpus restore these
>> affinities.
>>
>> v2:
>> Formatting: Fix hard tabs.
>> remove early return in cpu_disable_scheduler() path.
>>
>> v3:
>> Formatting: Fix remaining errant tab.
>> Move restore_vcpu_affinity() to thaw_domains(), eliminating the need to
>> promote for_each_cpupool()
>>
>> v4:
>> Formatting: Fix if statement spacing.
>> Eliminate unnecessary if statement in thaw_domains()
>> Suppress affinity related logging to XENLOG_DEBUG to reduce noise.
>>
>> Signed-off-by: Ben Guthro <benjamin.guthro@citrix.com>
>
> I'm not super-familiar with the save/restore paths; but it looks like
> a reasonable change to me:
>
> Acked-by: George Dunlap <george.dunlap@eu.citrix.com>
>
Thanks George.
Jan,
Is this a sufficient Ack, or does Kier need to weigh in as well?
Thanks,
Ben
next prev parent reply other threads:[~2013-04-01 19:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-27 13:13 [PATCH] x86/S3: Restore broken vcpu affinity on resume (v4) Ben Guthro
2013-03-28 8:19 ` Jan Beulich
2013-03-28 12:18 ` George Dunlap
2013-04-01 19:47 ` Ben Guthro [this message]
2013-04-01 20:17 ` Keir Fraser
2013-04-02 7:49 ` Jan Beulich
2013-04-03 14:29 ` 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=5159E467.9040603@citrix.com \
--to=benjamin.guthro@citrix.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=xen-devel@lists.xen.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.