From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoph Egger Subject: Re: [RFC][PATCH 0/2] MCA support for Intel64 Date: Mon, 6 Oct 2008 12:20:01 +0200 Message-ID: <200810061220.01459.Christoph.Egger@amd.com> References: <20080926.150442.238184376.kaz@flab.fujitsu.co.jp> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: Content-Disposition: inline List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: xen-devel@lists.xensource.com Cc: "Jiang, Yunhong" , SUZUKI Kazuhiro List-Id: xen-devel@lists.xenproject.org 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 thi= nk > "current" is very helpful. 2) How to split the effort between Xen and Dom= 0? > 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 enhanci= ng > MCE handler. Of course, another option is to place all handler in Xen sid= e. > 3) We need consider what will happen if multiple MCA happen at multiple C= PU > 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 h= ow > > 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 > > > > 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 =2D-=20 AMD Saxony, Dresden, Germany Operating System Research Center Legal Information: AMD Saxony Limited Liability Company & Co. KG Sitz (Gesch=E4ftsanschrift): Wilschdorfer Landstr. 101, 01109 Dresden, Deutschland Registergericht Dresden: HRA 4896 vertretungsberechtigter Komplement=E4r: AMD Saxony LLC (Sitz Wilmington, Delaware, USA) Gesch=E4ftsf=FChrer der AMD Saxony LLC: Dr. Hans-R. Deppe, Thomas McCoy