From: Andi Kleen <ak@linux.intel.com>
To: Tim Hockin <thockin@gmail.com>
Cc: Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
ying.huang@intel.com, Aaron Durbin <adurbin@gmail.com>,
priyankag@google.com
Subject: Re: x86/mce merge, integration hickup + crash, design thoughts
Date: Wed, 14 Jan 2009 19:05:47 +0100 [thread overview]
Message-ID: <496E297B.6010100@linux.intel.com> (raw)
In-Reply-To: <b3ece790901140818i183bc30n2de01b5edaa6a2c7@mail.gmail.com>
>
> From my point of view: a single, consistent, easy logging interface
> for the kernel to send *structured data* about hardware/system events
> and errors up to userspace.
Which kinds of events were you thinking of?
So far we managed by cramming some other CPU events like thermal
trip into "pseudo banks" in struct mce. Admittedly it's not the
most pretty solution in the world, but it worked.
-Andi
next prev parent reply other threads:[~2009-01-14 18:05 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-27 15:50 x86/mce merge, integration hickup + crash, design thoughts Ingo Molnar
2008-12-27 22:51 ` Ingo Molnar
2008-12-29 21:41 ` Andi Kleen
2009-01-13 17:45 ` Ingo Molnar
2009-01-13 18:57 ` Tim Hockin
2009-01-14 9:29 ` Andi Kleen
2009-01-14 16:18 ` Tim Hockin
2009-01-14 18:05 ` Andi Kleen [this message]
2009-01-14 19:32 ` Tim Hockin
2009-01-15 22:56 ` Andi Kleen
2009-01-15 23:39 ` Tim Hockin
2009-01-14 2:02 ` Huang Ying
2008-12-30 21:13 ` Russ Anderson
2008-12-31 13:32 ` Andi Kleen
2008-12-31 18:09 ` Russ Anderson
2008-12-29 21:51 ` Andi Kleen
2008-12-30 6:50 ` Ingo Molnar
2008-12-30 9:13 ` Andi Kleen
2008-12-30 21:29 ` Russ Anderson
2009-01-12 22:02 ` Tim Hockin
2009-01-13 5:02 ` Andi Kleen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=496E297B.6010100@linux.intel.com \
--to=ak@linux.intel.com \
--cc=adurbin@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=priyankag@google.com \
--cc=tglx@linutronix.de \
--cc=thockin@gmail.com \
--cc=ying.huang@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox