All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jan Beulich" <jbeulich@novell.com>
To: Guanqun Lu <guanqun.lu@intel.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	Keir Fraser <keir.fraser@eu.citrix.com>
Subject: RE: [PATCH] small adjustment to asm constraints for c/s19400
Date: Mon, 30 Mar 2009 10:13:06 +0100	[thread overview]
Message-ID: <49D0A942.76E4.0078.0@novell.com> (raw)
In-Reply-To: <8FED46E8A9CA574792FC7AACAC38FE7701D4B7A7D8@PDSMSX501.ccr.corp.intel.com>

>>> "Lu, Guanqun" <guanqun.lu@intel.com> 30.03.09 10:56 >>>
>On Monday, March 30, 2009 4:45 PM Keir Fraser wrote:
>
>> On 30/03/2009 05:45, "Lu, Guanqun" <guanqun.lu@intel.com> wrote:
>> 
>>> With this adjustment or previous patch 19400, S3 still fails on 64
>>> xen / 32 dom0. Do you have any idea what will cause this problem?
>> 
>> Does it still fail at the LTR? Does the alternative fix of settign
>> the type to 9 rather than 11 work?
>> 
>>  -- Keir
>
>It doesn't fail at the LTR.
>Xen resumes back, but dom0 hangs there(technically speaking, it doen't hang, eip changes, but can't come back to shell console),
>I used xen serial line to dump the dom0 registers,
>the eip it runs to from time to time is 'general_protection' in dom0.

Since under normal circumstances GP faults are rare, why don't you just
print out the faulting vCPU's state from Xen at the point where the fault
gets forwarded to the guest? That'll tell you exactly what the guest is
dying on.

Jan

  reply	other threads:[~2009-03-30  9:13 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-27 16:35 [PATCH] small adjustment to asm constraints for c/s 19400 Jan Beulich
2009-03-30  4:45 ` Lu, Guanqun
2009-03-30  6:42   ` [PATCH] small adjustment to asm constraints for c/s19400 Jan Beulich
2009-03-30  8:58     ` Lu, Guanqun
2009-03-30  8:45   ` [PATCH] small adjustment to asm constraints for c/s 19400 Keir Fraser
2009-03-30  8:56     ` Lu, Guanqun
2009-03-30  9:13       ` Jan Beulich [this message]
2009-03-31  8:54         ` [PATCH] small adjustment to asm constraints for c/s19400 Lu, Guanqun
2009-03-31  9:05           ` Tian, Kevin
2009-03-31  9:24           ` [PATCH] small adjustment to asm constraints forc/s19400 Jan Beulich
2009-03-31  9:26             ` Tian, Kevin
2009-03-31  9:40               ` Jan Beulich
2009-03-31  9:47             ` Tian, Kevin
2009-03-31 10:15               ` Jan Beulich
2009-03-31 10:21                 ` Tian, Kevin
2009-03-31 10:54                   ` [PATCH] small adjustment to asm constraintsforc/s19400 Jan Beulich
2009-03-31 11:09                     ` Tian, Kevin
2009-03-31 11:30                       ` Jan Beulich
2009-03-31 11:35                         ` Tian, Kevin

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=49D0A942.76E4.0078.0@novell.com \
    --to=jbeulich@novell.com \
    --cc=guanqun.lu@intel.com \
    --cc=keir.fraser@eu.citrix.com \
    --cc=xen-devel@lists.xensource.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.