From: "Tim Hockin" <thockin@google.com>
To: "Andi Kleen" <ak@suse.de>
Cc: "Joshua Wise" <jwise@google.com>,
akpm@google.com, linux-kernel@vger.kernel.org,
"Mike Waychison" <mikew@google.com>
Subject: Re: [x86_64 MCE] [RFC] mce.c race condition (or: when evil hacks are the only options)
Date: Thu, 12 Jul 2007 14:28:25 -0700 [thread overview]
Message-ID: <cc96a5040707121428j6c03fb6eyd27685a9f172ac23@mail.gmail.com> (raw)
In-Reply-To: <200707122320.19489.ak@suse.de>
On 7/12/07, Andi Kleen <ak@suse.de> wrote:
> > -- there may be other edge cases other than
> > this one. I'm actually surprised that this wasn't a ring buffer to start
> > with -- it certainly seems like it wanted to be one.
>
> The problem with a ring buffer is that it would lose old entries; but
> for machine checks you really want the first entries because
> the later ones might be just junk.
Couldn't the ring just have logic to detect an overrun and stop
logging until that is alleviated? Similar to what is done now. Maybe
I am underestimating it..
prev parent reply other threads:[~2007-07-12 21:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-12 20:24 Joshua Wise
2007-07-12 21:20 ` Andi Kleen
2007-07-12 21:28 ` Tim Hockin [this message]
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=cc96a5040707121428j6c03fb6eyd27685a9f172ac23@mail.gmail.com \
--to=thockin@google.com \
--cc=ak@suse.de \
--cc=akpm@google.com \
--cc=jwise@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mikew@google.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
all inboxes | Powered by JetHome®