All of lore.kernel.org
 help / color / mirror / Atom feed
From: Juergen Gross <juergen.gross@ts.fujitsu.com>
To: Ben Guthro <benjamin.guthro@citrix.com>
Cc: "Fraser, Keir" <keir.xen@gmail.com>, xen-devel@lists.xen.org
Subject: Re: [PATCH] x86/S3: Fix cpu pool scheduling after suspend/resume
Date: Tue, 09 Apr 2013 15:12:36 +0200	[thread overview]
Message-ID: <516413C4.2080103@ts.fujitsu.com> (raw)
In-Reply-To: <CAOvdn6UqthJD1u_tCyOkhZTTqL7wfiyrX0EgC3JzsR10_AJ9Ag@mail.gmail.com>

On 09.04.2013 15:04, Ben Guthro wrote:
> How would you suggest this be solved then - because we are seeing that
> all non-boot cpus are not being put in a pool at all - which is
> clearly worse than being put into pool0

I proposed a patch before, which should have worked:

http://lists.xen.org/archives/html/xen-devel/2012-03/msg01843.html

Keir didn't like it and came up with the state variable...


Juergen

-- 
Juergen Gross                 Principal Developer Operating Systems
PBG PDG ES&S SWE OS6                   Telephone: +49 (0) 89 3222 2967
Fujitsu Technology Solutions              e-mail: juergen.gross@ts.fujitsu.com
Domagkstr. 28                           Internet: ts.fujitsu.com
D-80807 Muenchen                 Company details: ts.fujitsu.com/imprint.html

  reply	other threads:[~2013-04-09 13:12 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-09 12:46 [PATCH] x86/S3: Fix cpu pool scheduling after suspend/resume Ben Guthro
2013-04-09 12:57 ` Juergen Gross
2013-04-09 13:04   ` Ben Guthro
2013-04-09 13:12     ` Juergen Gross [this message]
2013-04-09 13:17     ` Jan Beulich
2013-04-09 15:30     ` George Dunlap
2013-04-10  8:56       ` Jan Beulich
2013-04-09 13:03 ` Jan Beulich
2013-04-09 13:17   ` Ben Guthro
2013-04-09 14:00     ` Jan Beulich
2013-04-09 14:52     ` Keir Fraser
2013-04-15 12:33       ` Ben Guthro

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=516413C4.2080103@ts.fujitsu.com \
    --to=juergen.gross@ts.fujitsu.com \
    --cc=benjamin.guthro@citrix.com \
    --cc=keir.xen@gmail.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.