All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Egger <Christoph.Egger@amd.com>
To: xen-devel@lists.xensource.com
Cc: "Jiang, Yunhong" <yunhong.jiang@intel.com>,
	SUZUKI Kazuhiro <kaz@jp.fujitsu.com>
Subject: Re: [RFC][PATCH 0/2] MCA support for Intel64
Date: Mon, 6 Oct 2008 12:20:01 +0200	[thread overview]
Message-ID: <200810061220.01459.Christoph.Egger@amd.com> (raw)
In-Reply-To: <E2263E4A5B2284449EEBD0AAB751098401ABDE6969@PDSMSX501.ccr.corp.intel.com>


When I submitted the MCA support patches, I also sent
a design document as a pdf file to this list.
This should answer below questions.

Christoph



On Friday 26 September 2008 16:35:55 Jiang, Yunhong wrote:
> Glad to know you are working on MCA too.
> There are some discussion already on it, I google and get the link
> http://article.gmane.org/gmane.comp.emulators.xen.devel/56284 for some
> discussion. You can check that thread.
>
> Some point need discussion including:
> 1) How to detect the impacted components in Xen side? As the above mail
> thread discussed, maybe some improvement can be added to check the context
> more precisely. For example, if the stack tell the MCE happens when Xen is
> running, even if current is idle, we still think Xen is impacted. Also we
> can check the page owner to decide impacted guest. Personally I don't think
> "current" is very helpful. 2) How to split the effort between Xen and Dom0?
> Maybe we can re-use dom0's MCE handler as much as possible, Xen will only
> do some initial containment, especially considering Linux is also enhancing
> MCE handler. Of course, another option is to place all handler in Xen side.
> 3) We need consider what will happen if multiple MCA happen at multiple CPU
> simuatanously, maybe some monarch algrithom is needed.
>
> Hope your input on it.
>
> BTW, I checked you patch to kernel of mce-xen.c, seems not much change to
> it. You will add more changes on it, right?
>
> Thanks
> Yunhong Jiang
>
> xen-devel-bounces@lists.xensource.com <> wrote:
> > Hi,
> >
> > I am interested in MCA/MCE on x86 system. But I don't have AMD
> > machine, so I tried to port MCA handler on AMD k8 to Intel p4, I
> > attach it. Additionally, I attach a patch that supports MCA handler for
> > linux-2.6.18-xen/x86_64.
> >
> > Unfortunately, I don't know how to test MCA/MCE on Intel p4 CPU and
> > chipset, so I could not test with real MCA only in testing with fake
> > mode(just function calling). Is there anyone who knows and teaches me how
> > to test the real MCA?
> >
> > [1/2] xen part: mca-support-for-intel-xen.patch
> > [2/2] linux/x86_64 part: mca-support-for-intel-linux.patch
> >
> > Signed-off-by: Kazuhiro Suzuki <kaz@jp.fujitsu.com>
> >
> > Thanks,
> > KAZ
> >
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@lists.xensource.com
> > http://lists.xensource.com/xen-devel
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel



-- 
AMD Saxony, Dresden, Germany
Operating System Research Center

Legal Information:
AMD Saxony Limited Liability Company & Co. KG
Sitz (Geschäftsanschrift):
   Wilschdorfer Landstr. 101, 01109 Dresden, Deutschland
Registergericht Dresden: HRA 4896
vertretungsberechtigter Komplementär:
   AMD Saxony LLC (Sitz Wilmington, Delaware, USA)
Geschäftsführer der AMD Saxony LLC:
   Dr. Hans-R. Deppe, Thomas McCoy

      parent reply	other threads:[~2008-10-06 10:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-26  6:04 [RFC][PATCH 0/2] MCA support for Intel64 SUZUKI Kazuhiro
2008-09-26 14:35 ` Jiang, Yunhong
2008-10-02  7:27   ` SUZUKI Kazuhiro
2008-10-06  3:19     ` Jiang, Yunhong
2008-10-06 10:20   ` Christoph Egger [this message]

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=200810061220.01459.Christoph.Egger@amd.com \
    --to=christoph.egger@amd.com \
    --cc=kaz@jp.fujitsu.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.