[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] Re: [RFC] RAS(Part II)--MCA enalbing in XEN



Jiang, Yunhong wrote:
> Christoph Egger wrote:
I think, we should mark the 'struct mcinfo_global' as a kind of header for each error. All following information describe the error (including the follow-up errors) and all recover actions. This gives us the flexibility
to get as many information as possible and allows to do
as many recover actions as necessary instead of just one.

I think your original proposal can also meet such purpose, i.e. include the 
mc_recover_info and we still need pass all mc_bacnk infor to dom0 for 
telemetry. If you prefer this one, can you please define the interface? 
Gavin/Frank, do you have any idea for this changes?

Sorry about the slow reply.

Our changes to the MCE code (to combine the AMD and Intel code as much as possible, and use a transactional approach to the telemetry) already pretty much uses mc_global as a header. With our code, dom0 retrieves one mcinfo structure, with one global structure (which always comes first, but that's not required).

In other words, using mc_global as kind of a header to the mcinfo data is fine, since we're already doing that.

And, since we're talking about transactions with one mcinfo structure at a time (with one mc_global structure), the recover_info structures can be separate from the bank structures.

- Frank

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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.