[lkml]   [2013]   [Aug]   [12]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH 3/3] mce: acpi/apei: trace: Enable ghes memory error trace event
Em Mon, 12 Aug 2013 14:38:13 +0200
Borislav Petkov <> escreveu:

> On Mon, Aug 12, 2013 at 08:33:55AM -0300, Mauro Carvalho Chehab wrote:
> > APEI is just the mechanism that collects the data, not the mechanism
> > that reports to userspace.
> Both methods add a tracepoint - no difference.
> > I really don't see any sense on adding yet-another-way to report the
> > very same error.
> Well, your suggested way through the layers is this:
> Hardware->APEI->EDAC.
> His is
> Hardware->APEI.
> If I can lose the EDAC layer, then this is a clear win.

Clear win from what PoV? Userspace will need to decode a different type
of tracing, and implement a different logic for APEI. So, it will be
reinventing the wheel, with a different trace format, and will require
userspace to implement another tracing event for the same thing that
EDAC already provides.

Also, if both ghes_edac and this new tracing is enabled, userspace will
receive twice the same event, as two traces will be received for the
same thing.

Worse than that, how userspace is supposed to merge those two events
into one?



 \ /
  Last update: 2013-08-12 17:01    [W:0.129 / U:0.584 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site