[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] RE: [Xen-devel] RE: [PATCH] x86: add CMCI software injection interface
Ok, we will do it this way. --jyh >-----Original Message----- >From: Keir Fraser [mailto:keir.fraser@xxxxxxxxxxxxx] >Sent: Wednesday, May 05, 2010 5:21 PM >To: Jiang, Yunhong; Frank Van Der Linden; Ke, Liping >Cc: Christoph@xxxxxxxxxxxxxxxxxxxx; Egger; xen-devel@xxxxxxxxxxxxxxxxxxx; >gavin.maltby@xxxxxxxxxx >Subject: Re: [Xen-devel] RE: [PATCH] x86: add CMCI software injection interface > >On 05/05/2010 10:07, "Jiang, Yunhong" <yunhong.jiang@xxxxxxxxx> wrote: > >>> If going with the former option it would be good to think ahead in your >>> designs and make sure you end up adding the smallest possible number of new >>> XEN_MC_* commands. It could easily become a real mess I'm sure. >> >> "either of these"? Maybe I didn't express my idea clearly. I didn't propose >> two options. I just suggest to use a new command for this purpose. And we can >> update the version number if needed. >> >> BTW, as currently Xen already will return -EINVAL for not-support command >> (i.e. <= 5), maybe the version number update is not needed. ( the -EINVAL may >> be not good as -ENOSYS). > >Oh, sorry, I thought you were expressing either-or. If you add a new command >then you do not update the version number: that would pointlessly disable >MCE on older guests. > > -- Keir > _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel
|
![]() |
Lists.xenproject.org is hosted with RackSpace, monitoring our |