All of lore.kernel.org
 help / color / mirror / Atom feed
From: Juergen Gross <juergen.gross@ts.fujitsu.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: xen-devel <xen-devel@lists.xen.org>,
	keir@xen.org, Ben Guthro <ben@guthro.net>,
	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: dump with xen-unstable & linux 3.2.17
Date: Wed, 23 May 2012 13:00:54 +0200	[thread overview]
Message-ID: <4FBCC366.1060908@ts.fujitsu.com> (raw)
In-Reply-To: <4FBCCC650200007800085694@nat28.tlf.novell.com>

On 05/23/2012 11:39 AM, Jan Beulich wrote:
>>>> On 22.05.12 at 23:00, Ben Guthro<ben@guthro.net>  wrote:
>> I've bisected this to the following commit in the xen-unstable git tree.
>>
>> I'll be able to dive in a little deeper tomorrow.
>> If you see anything here that looks suspicious to the crash
>> referenced... let me know.
> As the change was really a re-write of a submission by Jürgen,
> I'm adding him to Cc.
>
> Unless he has an immediate idea, we definitely want to
> understand why "cpus" is empty - hence we'd want to see
> *online, *vc->cpu_affinity, vc->cpu_id, and maybe
> vc->processor. (Printing them is probably not a good idea
> here, so I'd instead suggest just copying them to [additional]
> on-stack variables, making sure the compiler doesn't optimize
> them away.)
>
> Probably it would be good to also know what each active
> vCPU's ->cpu_affinity was right before suspend and/or right
> after resume (perhaps in freeze_domains() and/or
> thaw_domains(). That way we'd at least know whether the
> affinity - despite the offending changeset's inverse intention -
> did get changed during the resume process.

No idea, sorry.
I tested the patch only against a problem with power_off, so I never hit the
resume path.


Juergen

-- 
Juergen Gross                 Principal Developer Operating Systems
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


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

  reply	other threads:[~2012-05-23 11:00 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-17 21:20 dump with xen-unstable & linux 3.2.17 Ben Guthro
2012-05-21 14:55 ` Jan Beulich
2012-05-21 19:12   ` Ben Guthro
2012-05-21 19:49     ` Ben Guthro
2012-05-22 15:38       ` Ben Guthro
2012-05-22 16:08         ` Jan Beulich
2012-05-22 16:21           ` Ben Guthro
2012-05-22 17:34             ` Konrad Rzeszutek Wilk
2012-05-22 17:55               ` Ben Guthro
2012-05-22 18:00                 ` Konrad Rzeszutek Wilk
2012-05-22 18:26                   ` Ben Guthro
2012-05-22 21:00                     ` Ben Guthro
2012-05-23  9:39                       ` Jan Beulich
2012-05-23 11:00                         ` Juergen Gross [this message]
2012-05-25 13:20                           ` Ben Guthro
2012-05-31 15:52                             ` Ben Guthro
2012-05-31 16:06                               ` Jan Beulich
2012-05-31 16:18                                 ` Ben Guthro
2012-06-01  6:54                                 ` Dietmar Hahn

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=4FBCC366.1060908@ts.fujitsu.com \
    --to=juergen.gross@ts.fujitsu.com \
    --cc=JBeulich@suse.com \
    --cc=ben@guthro.net \
    --cc=keir@xen.org \
    --cc=konrad.wilk@oracle.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.