WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-ia64-devel

Re: [Xen-ia64-devel] [RFC] MCA handler support for Xen/ia64

To: Masaki Kanno <kanno.masaki@xxxxxxxxxxxxxx>
Subject: Re: [Xen-ia64-devel] [RFC] MCA handler support for Xen/ia64
From: Alex Williamson <alex.williamson@xxxxxx>
Date: Wed, 12 Jul 2006 22:59:30 -0600
Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 12 Jul 2006 21:59:41 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <8DC6A596BD1093kanno.masaki@xxxxxxxxxxxxxx>
List-help: <mailto:xen-ia64-devel-request@lists.xensource.com?subject=help>
List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
List-post: <mailto:xen-ia64-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=unsubscribe>
Organization: OSLO R&D
References: <8DC6A596BD1093kanno.masaki@xxxxxxxxxxxxxx>
Sender: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
Hi Masaki,

   Thanks for the write-up, generally looks like a good approach to me.
A few comments and questions:

   How do you plan to handle the mismatch between dom0's vCPUs and the
pCPUs reporting errors.  For instance, will all pCPU's CMCs be injected
into dom0 vCPU0?  Will all CPE records be returned from all pCPUs when
dom0 does a SAL_GET_STATE_INFO from vCPU0?  SAL_GET_STATE_INFO_SIZE may
need to return the platform state info size * number of pCPUs to allow
dom0 enough space to save the records.  On big SMP systems we need to
make sure that's not more than can reasonable be allocated in the kernel
by dom0.

   What about clearing error records?  We need to be careful that error
records read by Xen and cleared before being passed to dom0 are volatile
and could be lost if the system crashes or if dom0 doesn't retrieve
them.  It's best to only clear the log after the error record has been
received by dom0 and dom0 issues a SAL_CLEAR_STATE_INFO.  This will get
complicated if we need to clear error records on all pCPUs in response
to a SAL_CLEAR_STATE_INFO on dom0 vCPU0.

   Do you plan to support CMC and CPE throttling in Xen (ie. switching
between interrupt driven and polling handlers under load) and dynamic
polling intervals?

   It may be overly complicated to support CPEI on dom0 (fake MADT
entries, trapping IOSAPIC write, maybe an entirely virtual IOSAPIC in
order to describe a valid GSI for the CPEI, etc...).  Probably best to
start out with just letting dom0 poll for CPE records.  Thanks,

        Alex

-- 
Alex Williamson                             HP Open Source & Linux Org.


_______________________________________________
Xen-ia64-devel mailing list
Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ia64-devel