[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <DE8DF0795D48FD4CA783C40EC82923359662@SHSMSX101.ccr.corp.intel.com>
Date: Fri, 23 Dec 2011 10:20:26 +0000
From: "Liu, Jinsong" <jinsong.liu@...el.com>
To: Konrad Rzeszutek Wilk <konrad@...nok.org>
CC: "konrad.wilk@...cle.com" <konrad.wilk@...cle.com>,
"xen-devel@...ts.xensource.com" <xen-devel@...ts.xensource.com>,
"Jiang, Yunhong" <yunhong.jiang@...el.com>,
"jeremy.fitzhardinge@...rix.com" <jeremy.fitzhardinge@...rix.com>,
"Brown, Len" <len.brown@...el.com>,
"Zhao, Yakui" <yakui.zhao@...el.com>,
Kernel development list <linux-kernel@...r.kernel.org>,
"Luck, Tony" <tony.luck@...el.com>,
"Kleen, Andi" <andi.kleen@...el.com>
Subject: RE: [Xen-devel] Linux 3.1.0 Xen RAS rebase
Liu, Jinsong wrote:
> Konrad Rzeszutek Wilk wrote:
>> On Thu, Dec 22, 2011 at 09:57:55AM +0000, Liu, Jinsong wrote:
>>> Recently we did dom0 Xen RAS rebase work.
>>
>> Hey Liu,
>>
>> Thank you for posting this. Couple of questions:
>> 1). How does one test these patches?
>
> These patches include mce, cpu online/offline, cpu hotadd, memory
> hotadd.
> Testing method of these features are
> 1. mce: a normal way is to inject error through EINJ user interface,
> and getting mcelog at dom0 side
> 2. cpu online/offline: by echoing sysfs/.../xen_pcpu user interface,
> and getting result at sysfs/.../xen_pcpu
> 3. cpu hotadd: Intel has some new server, by pressing a button can
> add cpu. We can verify cpu hotadd by sysfs/.../xen_pcpu interface
> 4. memory hotadd: also by pressing a button to add memory, and can
> verify memory hotadd by 'xl info'
>
>> 2). Please CC LKML and also the ACPI maintainer - since a majority
>> of this also touch their tree. And the memory hotadd maintainer
>> as well.
>
> OK, cc
> LKML
> ACPI maintainer: len.brown@...el.com
> memory hotadd maintianer: I'm not sure who is maintainer, but I will
> cc yakui.zhao@...el.com and len.brown@...el.com
Will also cc Tony Luck and Andi Kleen, mce maintainers.
>
> I'll re-send the patches later, cc above people.
>
>> 3). Can any of this code (like the MCE) leverage the existing
>> generic code?
>
> Basically no, for mce, xen implement mce logic at hypervisor,
> at dom0 side, it only add mcelog interface to get log from hypervisor
> and transfer to kernel mcelog format.
>
>> 4). Have you guys talked with Len Brown (the ACPI maintainer)
>> about some of this code and how to make it fit within his
>> goals?
>
> Not yet, but will.
>
> Thanks,
> Jinsong
>
>>
>> Thanks!
>>>
>>> Basically it rebased from Jeremy's pvops (2.6.32), to Konrad's pvops
>>> (3.1.0, branch "devel/acpi-cpufreq.v3") patch 1: for mcelog logic
>>> patch 2: for dom0 vmce patch 3: for cpu sysfs and cpu online/offline
>>> patch 4: for cpu hotadd
>>> patch 5: for memory hotadd prepare work
>>> patch 6: for memory hotadd
>>> patch 7: for cpu hotadd prepare work
>>> patch 8: complement cpu hotadd lacked at Konrad's tree
>>> patch 9: update PM logic
>>> patch 10: upate cpu online/offline logic
>>>
>>>
>>> Thanks,
>>> Jinsong
>>> _______________________________________________
>>> Xen-devel mailing list
>>> Xen-devel@...ts.xensource.com
>>> http://lists.xensource.com/xen-devel
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists