From: Greg KH <gregkh@linuxfoundation.org>
To: Andrew Banman <abanman@hpe.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org, Mike Travis <mike.travis@hpe.com>,
linux-kernel@vger.kernel.org, stable@vger.kernel.org,
Russ Anderson <rja@hpe.com>, Dimitri Sivanich <sivanich@hpe.com>
Subject: Re: [PATCH] x86/platform/uv/BAU: gracefully disable BAU during panic
Date: Sun, 3 Jun 2018 21:55:35 +0200 [thread overview]
Message-ID: <20180603195535.GB7941@kroah.com> (raw)
In-Reply-To: <1528044152-148686-1-git-send-email-abanman@hpe.com>
On Sun, Jun 03, 2018 at 11:42:32AM -0500, Andrew Banman wrote:
> When panic happens while BAU is active there is a chance that
> outstanding broadcasts tie up BAU resources enough to cause timeouts in
> the UV ASIC. These timeouts are hardware errors that immediately bring
> down the system, preventing kdump from completing.
>
> Add uv_bau_crash_shutdown() to bring BAU to quiescence during panic before
> continuing with the native crash shutdown. Assign uv_bau_crash_shutdown
> to machine_ops during init.
>
> Signed-off-by: Andrew Banman <abanman@hpe.com>
> ---
> arch/x86/platform/uv/tlb_uv.c | 31 +++++++++++++++++++++++++++++++
> 1 file changed, 31 insertions(+)
<formletter>
This is not the correct way to submit patches for inclusion in the
stable kernel tree. Please read:
https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
for how to do this properly.
</formletter>
next prev parent reply other threads:[~2018-06-03 19:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-03 16:42 [PATCH] x86/platform/uv/BAU: gracefully disable BAU during panic Andrew Banman
2018-06-03 19:55 ` Greg KH [this message]
2018-06-04 2:26 ` kbuild test robot
-- strict thread matches above, loose matches on Subject: below --
2018-08-13 13:54 Andrew Banman
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=20180603195535.GB7941@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=abanman@hpe.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mike.travis@hpe.com \
--cc=mingo@redhat.com \
--cc=rja@hpe.com \
--cc=sivanich@hpe.com \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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.