From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: Nicholas Piggin <npiggin@gmail.com>, linuxppc-dev@lists.ozlabs.org
Cc: Alexey Kardashevskiy <aik@ozlabs.ru>
Subject: Re: [PATCH 1/3] powerpc/64s/interrupt: Fix decrementer storm
Date: Mon, 21 Mar 2022 16:05:54 +1100 [thread overview]
Message-ID: <164783915433.1783931.15144105177430156080.b4-ty@ellerman.id.au> (raw)
In-Reply-To: <20220124143930.3923442-1-npiggin@gmail.com>
On Tue, 25 Jan 2022 00:39:28 +1000, Nicholas Piggin wrote:
> The decrementer exception can fail to be cleared when the interrupt
> returns in the case where the decrementer wraps with the next timer
> still beyond decrementer_max. This results in a decrementer interrupt
> storm. This is triggerable with small decrementer system with hard
> and soft watchdogs disabled.
>
> Fix this by always programming the decrementer if there was no timer.
>
> [...]
Patch 2 & 3 applied to powerpc/next.
[2/3] powerpc/time: Fix KVM host re-arming a timer beyond decrementer range
https://git.kernel.org/powerpc/c/cf74ff52e352112be78c4c4c3637a37ec36a6608
[3/3] powerpc/time: improve decrementer clockevent processing
https://git.kernel.org/powerpc/c/35de589cb8793573ed56a915af9cb4b5f15ad7d7
cheers
prev parent reply other threads:[~2022-03-21 5:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-24 14:39 [PATCH 1/3] powerpc/64s/interrupt: Fix decrementer storm Nicholas Piggin
2022-01-24 14:39 ` [PATCH 2/3] powerpc/time: Fix KVM host re-arming a timer beyond decrementer range Nicholas Piggin
2022-01-24 14:39 ` [PATCH 3/3] powerpc/time: improve decrementer clockevent processing Nicholas Piggin
2022-01-29 11:14 ` (subset) [PATCH 1/3] powerpc/64s/interrupt: Fix decrementer storm Michael Ellerman
2022-03-21 5:05 ` Michael Ellerman [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=164783915433.1783931.15144105177430156080.b4-ty@ellerman.id.au \
--to=patch-notifications@ellerman.id.au \
--cc=aik@ozlabs.ru \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=npiggin@gmail.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;
as well as URLs for NNTP newsgroup(s).