[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <DE8DF0795D48FD4CA783C40EC82923351FEEAF@SHSMSX101.ccr.corp.intel.com>
Date: Thu, 31 May 2012 13:00:58 +0000
From: "Liu, Jinsong" <jinsong.liu@...el.com>
To: Borislav Petkov <bp@...64.org>
CC: Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>,
"'linux-kernel@...r.kernel.org'" <linux-kernel@...r.kernel.org>,
"Luck, Tony" <tony.luck@...el.com>,
"'xen-devel@...ts.xensource.com'" <xen-devel@...ts.xensource.com>
Subject: RE: [PATCH 1/3] xen/mce: Add mcelog support for Xen platform (RFC)
Borislav Petkov wrote:
> On Wed, May 30, 2012 at 03:20:03PM +0000, Liu, Jinsong wrote:
>>>> IMO currently there are 2 options:
>>>> 1). use the original approach (implicitly redirect /dev/mcelog to
>>>> xen_mce_chrdev_device) --> what point of this approach do you think
>>>> unreasonable? It just remove a 'static' from native mce code! 2).
>>>> use another /dev/xen-mcelog interface, with another misc minor
>>>> '226'
>>>
>>> The 2) is no good.
>>>
>>> 3) What about moving the corresponding other users (so
>>> threshold_init_device), to be at late_initcall and the mce to be at
>>> late_initcall_sync
>>
>> I can try, but only if Boris would not jump out.
>> and it can only be tested by Boris at AMD platform :(
>
> Sure, I'll test it.
>
Boris,
I have update patches, and they have been tested under baremetal (Intel platform) and xen platform.
So you can test it at AMD platform, and thanks ahead!
Regards,
Jinsong--
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