From: Ingo Molnar <mingo@elte.hu>
To: Borislav Petkov <bp@amd64.org>
Cc: "Luck, Tony" <tony.luck@intel.com>,
Peter Zijlstra <peterz@infradead.org>,
Arnaldo Carvalho de Melo <acme@infradead.org>,
Steven Rostedt <rostedt@goodmis.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
Mauro Carvalho Chehab <mchehab@redhat.com>,
EDAC devel <linux-edac@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 4/4] x86, mce: Have MCE persistent event off by default for now
Date: Tue, 3 May 2011 21:56:58 +0200 [thread overview]
Message-ID: <20110503195658.GA24750@elte.hu> (raw)
In-Reply-To: <20110503195200.GA23243@aftab>
* Borislav Petkov <bp@amd64.org> wrote:
> > Probably make some sense to delay such a message (so that in the boot case
> > we give the daemon a chance to get started before complaining that it
> > hasn't shown up for work).
>
> Yep, that and also I need to address the case for catching earlybird MCEs,
> when perf hasn't been initialized yet. I'm thinking we could reuse the mcelog
> buffer and feed those into the RAS daemon after init. Something like that.
I'd suggest that to solve that problem we initialize events earlier and allow
something like a small static buffer backed event which does not need any
dynamic memory so it can be enabled early on and can receive events, at the
same time the MCE hw bits are enabled.
That event can get a larger buffer once the system is more fully up - without
losing whatever events it is already holding.
Thanks,
Ingo
next prev parent reply other threads:[~2011-05-03 19:57 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-02 17:34 [PATCH 0/4] RAS daemon: kernel part Borislav Petkov
2011-05-02 17:34 ` [PATCH 1/4] perf: Start the restructuring Borislav Petkov
2011-05-02 17:34 ` [PATCH 2/4] perf: Add persistent event facilities Borislav Petkov
2011-05-03 6:40 ` Ingo Molnar
2011-05-03 6:48 ` Ingo Molnar
2011-05-03 7:12 ` Borislav Petkov
2011-05-03 8:22 ` Ingo Molnar
2011-05-03 12:51 ` [GIT PULL] Rename perf_event.c Borislav Petkov
2011-05-03 12:59 ` [PATCH 2/4] perf: Add persistent event facilities Frederic Weisbecker
2011-05-03 13:30 ` Borislav Petkov
2011-05-03 14:26 ` Borislav Petkov
2011-05-02 17:34 ` [PATCH 3/4] x86, mce: Add persistent MCE event Borislav Petkov
2011-05-03 6:44 ` Ingo Molnar
2011-05-03 7:18 ` Borislav Petkov
2011-05-03 8:27 ` Ingo Molnar
2011-05-03 15:14 ` Joe Perches
2011-05-03 15:22 ` Borislav Petkov
2011-05-03 15:32 ` Joe Perches
2011-05-03 15:34 ` Steven Rostedt
2011-05-03 15:42 ` Borislav Petkov
2011-05-02 17:34 ` [PATCH 4/4] x86, mce: Have MCE persistent event off by default for now Borislav Petkov
2011-05-03 6:45 ` Ingo Molnar
2011-05-03 7:23 ` Borislav Petkov
2011-05-03 8:17 ` Ingo Molnar
2011-05-03 17:17 ` Luck, Tony
2011-05-03 19:52 ` Borislav Petkov
2011-05-03 19:56 ` Ingo Molnar [this message]
2011-05-04 6:58 ` Ingo Molnar
2011-05-04 21:40 ` Luck, Tony
2011-05-05 1:34 ` Arnaldo Carvalho de Melo
2011-05-05 6:39 ` Ingo Molnar
2011-05-05 7:17 ` Borislav Petkov
2011-05-05 7:33 ` Ingo Molnar
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=20110503195658.GA24750@elte.hu \
--to=mingo@elte.hu \
--cc=acme@infradead.org \
--cc=bp@amd64.org \
--cc=fweisbec@gmail.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tony.luck@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