From: Keir Fraser <keir.xen@gmail.com>
To: Jan Beulich <JBeulich@suse.com>, Ben Guthro <Benjamin.Guthro@citrix.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: Wed, 03 Apr 2013 15:29:56 +0100 [thread overview]
Message-ID: <CD81FB74.1FD9B%keir.xen@gmail.com> (raw)
In-Reply-To: <515AA9BE02000078000C9FEE@nat28.tlf.novell.com>
On 02/04/2013 08:49, "Jan Beulich" <JBeulich@suse.com> wrote:
>>> Thanks George.
>>>
>>> Jan,
>>>
>>> Is this a sufficient Ack, or does Kier need to weigh in as well?
>>
>> Acked-by: Keir Fraser <keir@xen.org>
>>
>> I kind of feel this sort of thing should be done in dom0 userspace but,
>> pragmatically, I know that's not really going to happen!
>
> How would that work, considering the Dom0's vCPU affinities are
> equally affected, and considering that all domains get thawed at
> once? Minimally you'd have a burst of (overcommit) load on pCPU0
> right after resume, and whether the system would survive that is
> impossible to predict.
Ha, yes, well you'd put freeze/thaw in dom0 too. Well, it wasn't really a
serious suggestion on my part, what we have works, this new patch will also
work, and I'm happy. :)
-- Keir
prev parent reply other threads:[~2013-04-03 14:29 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
2013-04-01 20:17 ` Keir Fraser
2013-04-02 7:49 ` Jan Beulich
2013-04-03 14:29 ` Keir Fraser [this message]
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=CD81FB74.1FD9B%keir.xen@gmail.com \
--to=keir.xen@gmail.com \
--cc=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.