All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: "Ke, Liping" <liping.ke@intel.com>
Cc: "Li, Haicheng" <haicheng.li@intel.com>,
	"Jiang, Yunhong" <yunhong.jiang@intel.com>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [pvops-dom0]Let PV ops guest could handle Machine Check trap
Date: Tue, 22 Sep 2009 09:36:34 -0700	[thread overview]
Message-ID: <4AB8FD12.1090709@goop.org> (raw)
In-Reply-To: <E2263E4A5B2284449EEBD0AAB751098418E3F1DC3E@PDSMSX501.ccr.corp.intel.com>

On 09/21/09 23:32, Ke, Liping wrote:
> Hi, Jeremy and all
>
> This small patch lets pv ops guest handle machine check trap. When non
> fatal mce error happens, xen will inject vMCE# to the impacted pv ops guest.
> This patch allows pv ops guest could receive machine check trap and enter
> its own machine check handler.
>   

Have you tested this?  This code is specifically to deal with traps
installed using an IST stack.  If the machine_check handler just works
as-is then there's no need for that whole ifdef block.  If it doesn't
work, then we need a variant which has the right exception frame format.

Thanks,
    J

> Thanks & Regards,
> Criping
>
>
> From 5efc12fe8214d55e2becc2c4b6ec4a30531d7b60 Mon Sep 17 00:00:00 2001
> From: Liping Ke <liping.ke@intel.com>
> Date: Tue, 22 Sep 2009 10:46:05 +0800
> Subject: [PATCH] Let PV guest handle machine check trap.
>
> This patch lets pv ops guest handle machine check trap. When non
> fatal mce error happens, XEN will inject vMCE# to the pv ops guest
> This patch allows pv ops guest could receive machine check trap 
> and enter its own machine check handler.
>
> Signed-off-by: Liping Ke <liping.ke@intel.com>
> ---
>  arch/x86/xen/enlighten.c |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/arch/x86/xen/enlighten.c b/arch/x86/xen/enlighten.c
> index 1edf6a8..3399a40 100644
> --- a/arch/x86/xen/enlighten.c
> +++ b/arch/x86/xen/enlighten.c
> @@ -476,7 +476,7 @@ static int cvt_gate_to_trap(int vector, const gate_desc *val,
>  		return 0;
>  #ifdef CONFIG_X86_MCE
>  	} else if (addr == (unsigned long)machine_check) {
> -		return 0;
> +		addr = (unsigned long)machine_check;
>  #endif
>  	} else {
>  		/* Some other trap using IST? */
>   

  reply	other threads:[~2009-09-22 16:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-22  6:32 [pvops-dom0]Let PV ops guest could handle Machine Check trap Ke, Liping
2009-09-22 16:36 ` Jeremy Fitzhardinge [this message]
2009-11-03  8:16   ` Jiang, Yunhong

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=4AB8FD12.1090709@goop.org \
    --to=jeremy@goop.org \
    --cc=haicheng.li@intel.com \
    --cc=liping.ke@intel.com \
    --cc=xen-devel@lists.xensource.com \
    --cc=yunhong.jiang@intel.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.