[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1284527192.2256.113.camel@yhuang-dev.sh.intel.com>
Date: Wed, 15 Sep 2010 13:06:32 +0800
From: Huang Ying <ying.huang@...el.com>
To: Ingo Molnar <mingo@...e.hu>
Cc: Andi Kleen <andi@...stfloor.org>, Don Zickus <dzickus@...hat.com>,
"H. Peter Anvin" <hpa@...or.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [RFC 5/6] x86, NMI, Add support to notify hardware error with
unknown NMI
On Wed, 2010-09-15 at 01:48 +0800, Ingo Molnar wrote:
> * Some One <some@...re> stripped out all quoted identities and wrote:
> > >
> > > The proper approach would be not to add hacks to the NMI code but to
> > > implement southbridge drivers - which would also have NMI callbacks.
> >
> > BTW southbridges do less and less regarding PCI.
>
> Except WICTCR.
>
> > > These are unchartered waters, but variance in that space is reducing
> > > systematically so it would be worth a shot.
> >
> > You don't really need special drivers for AER [...]
>
> On the contrary, we need proper driverization for _everything_ new.
> Embedded x86 is here to stay, so we are abstracting away each and every
> bit of the platform. See struct x86_ops for a highlevel platform driver
> - but a more specific, southbridge-encompassing driver framework can be
> created too.
All in all, we can have proper drivers to printk/write to NVRAM the
error information collected for unknown NMI, regardless they are AER or
Southbridge driver or both. And, the drivers will register handlers for
unknown NMI. Do you agree?
Best Regards,
Huang Ying
--
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