xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Tim Deegan <tim@xen.org>
To: "Ding, ShengGe" <ShengGe.Ding@amd.com>
Cc: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: dom0 crashes while domain_pause in NPF handler
Date: Thu, 27 Sep 2012 15:45:19 +0100	[thread overview]
Message-ID: <20120927144519.GF8831@ocelot.phlegethon.org> (raw)
In-Reply-To: <4DEE49724F3FA0438F8949D4497F451A05620D7B@SCYBEXDAG03.amd.com>

Hi,

At 05:25 +0000 on 18 Sep (1347945907), Ding, ShengGe wrote:
> Hi all,
> 
> I checked the domain_id again and I'm sure the paused domain is domU.
> But the crashing seems like dom0 is paused, then whole system is killed and reboots.
> 
> In Nested page fault handler, hypervisor get the VCPU via current macro and this VCPU is bound to domU(the domain_id is so).
> I'm really confused, how does dom0 crash if I pause domU here? Maybe this is a logic issue of hypervisor, the same codes could run well in old version.
> 

You haven't given enough information to understand what's gone wrong. 

What do you mean my 'dom0 crashes'?  Can you post a log of the serial
console of the machine showing the actual crash?

What changes have you made to Xen?  If your patches are very small,
maybe you could post them; if not, at least a description of what you've
done would be a good idea.

Calling domain_pause() on domU from inside a domU fault handler is
probably unsafe -- if two vcpus take the fault at the same time they
might deadlock. 

Tim.

  reply	other threads:[~2012-09-27 14:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-18  5:25 dom0 crashes while domain_pause in NPF handler Ding, ShengGe
2012-09-27 14:45 ` Tim Deegan [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-09-17  3:20 Ding, ShengGe

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=20120927144519.GF8831@ocelot.phlegethon.org \
    --to=tim@xen.org \
    --cc=ShengGe.Ding@amd.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).