From: Borislav Petkov <bp@alien8.de>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: Borislav Petkov <bp@suse.de>, Jiri Kosina <jkosina@suse.cz>,
linux-edac <linux-edac@vger.kernel.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Len Brown <lenb@kernel.org>,
Tomasz Nowicki <tomasz.nowicki@linaro.org>,
"Chen, Gong" <gong.chen@linux.intel.com>,
Wolfram Sang <wsa@the-dreams.de>,
"Zheng, Lv" <lv.zheng@intel.com>,
Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Huang, Ying" <ying.huang@intel.com>
Subject: Re: [RFC PATCH 5/5] GHES: Make NMI handler have a single reader
Date: Mon, 27 Apr 2015 22:23:50 +0200 [thread overview]
Message-ID: <20150427202349.GM28871@pd.tnic> (raw)
In-Reply-To: <3908561D78D1C84285E8C5FCA982C28F32A6446B@ORSMSX114.amr.corp.intel.com>
On Thu, Apr 23, 2015 at 06:00:15PM +0000, Luck, Tony wrote:
> > I think we should apply this.
> >
> > Here's why: nothing in the ghes_notify_nmi() handler does CPU-specific
> > accesses
>
> This looks to be true.
>
> > Tony, objections?
>
> No objections.
Thanks, queued for 4.2, pending one last test I'm doing on a machine
which says
[ 24.332560] INFO: NMI handler (ghes_notify_nmi) took too long to run: 3.265 msecs
[ 24.332567] INFO: NMI handler (ghes_notify_nmi) took too long to run: 5.946 msecs
[ 24.332568] INFO: NMI handler (ghes_notify_nmi) took too long to run: 5.948 msecs
during boot.
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
--
next prev parent reply other threads:[~2015-04-27 20:23 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-27 9:22 [RFC PATCH 0/5] GHES NMI handler cleanup Borislav Petkov
2015-03-27 9:22 ` [RFC PATCH 1/5] GHES: Carve out error queueing in a separate function Borislav Petkov
2015-03-27 9:22 ` [RFC PATCH 2/5] GHES: Carve out the panic functionality Borislav Petkov
2015-03-27 9:22 ` [RFC PATCH 3/5] GHES: Panic right after detection Borislav Petkov
2015-03-27 9:22 ` [RFC PATCH 4/5] GHES: Elliminate double-loop in the NMI handler Borislav Petkov
2015-03-27 9:22 ` [RFC PATCH 5/5] GHES: Make NMI handler have a single reader Borislav Petkov
2015-04-01 7:45 ` Jiri Kosina
2015-04-01 13:49 ` Borislav Petkov
2015-04-23 8:39 ` Jiri Kosina
2015-04-23 8:59 ` Borislav Petkov
2015-04-23 18:00 ` Luck, Tony
2015-04-23 18:00 ` Luck, Tony
2015-04-27 20:23 ` Borislav Petkov [this message]
2015-04-28 14:30 ` Don Zickus
2015-04-28 14:42 ` Don Zickus
2015-04-28 14:55 ` Borislav Petkov
2015-04-28 15:35 ` Don Zickus
2015-04-28 16:22 ` Borislav Petkov
2015-04-28 18:44 ` Don Zickus
2015-05-04 15:40 ` Borislav Petkov
2015-04-27 3:16 ` Zheng, Lv
2015-04-27 8:46 ` Borislav Petkov
2015-04-28 0:44 ` Zheng, Lv
2015-04-28 0:44 ` Zheng, Lv
2015-04-28 2:24 ` Zheng, Lv
2015-04-28 2:24 ` Zheng, Lv
2015-04-28 7:38 ` Borislav Petkov
2015-04-28 13:38 ` Zheng, Lv
2015-04-28 13:59 ` Borislav Petkov
2015-04-29 0:24 ` Zheng, Lv
2015-04-29 0:24 ` Zheng, Lv
2015-04-29 0:49 ` Zheng, Lv
2015-04-29 0:49 ` Zheng, Lv
2015-04-29 8:13 ` Borislav Petkov
2015-04-30 8:05 ` Zheng, Lv
2015-04-30 8:05 ` Zheng, Lv
2015-04-30 8:48 ` Borislav Petkov
2015-05-02 0:34 ` Zheng, Lv
2015-05-02 0:34 ` Zheng, Lv
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=20150427202349.GM28871@pd.tnic \
--to=bp@alien8.de \
--cc=bp@suse.de \
--cc=gong.chen@linux.intel.com \
--cc=jkosina@suse.cz \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lv.zheng@intel.com \
--cc=n-horiguchi@ah.jp.nec.com \
--cc=rjw@rjwysocki.net \
--cc=tomasz.nowicki@linaro.org \
--cc=tony.luck@intel.com \
--cc=wsa@the-dreams.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.