From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: linuxppc-dev@lists.ozlabs.org, Benjamin Gray <bgray@linux.ibm.com>
Subject: Re: [PATCH 0/3] Fix preemption errors in watchpoints
Date: Thu, 21 Sep 2023 19:24:48 +1000 [thread overview]
Message-ID: <169528828844.872767.7469796002349483809.b4-ty@ellerman.id.au> (raw)
In-Reply-To: <20230829063457.54157-1-bgray@linux.ibm.com>
On Tue, 29 Aug 2023 16:34:54 +1000, Benjamin Gray wrote:
> When enabling debug config options relating to preemption, several bugs
> appear in the kernel log. With this series applied, the breakpoint code
> no longer prints bugs when running the powerpc/ptrace selftests.
>
> Benjamin Gray (3):
> powerpc/watchpoints: Disable preemption in thread_change_pc()
> powerpc/watchpoint: Disable pagefaults when getting user instruction
> powerpc/watchpoints: Annotate atomic context in more places
>
> [...]
Applied to powerpc/fixes.
[1/3] powerpc/watchpoints: Disable preemption in thread_change_pc()
https://git.kernel.org/powerpc/c/cc879ab3ce39bc39f9b1d238b283f43a5f6f957d
[2/3] powerpc/watchpoint: Disable pagefaults when getting user instruction
https://git.kernel.org/powerpc/c/3241f260eb830d27d09cc604690ec24533fdb433
[3/3] powerpc/watchpoints: Annotate atomic context in more places
https://git.kernel.org/powerpc/c/27646b2e02b096a6936b3e3b6ba334ae20763eab
cheers
prev parent reply other threads:[~2023-09-21 9:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-29 6:34 [PATCH 0/3] Fix preemption errors in watchpoints Benjamin Gray
2023-08-29 6:34 ` [PATCH 1/3] powerpc/watchpoints: Disable preemption in thread_change_pc() Benjamin Gray
2023-08-29 6:34 ` [PATCH 2/3] powerpc/watchpoint: Disable pagefaults when getting user instruction Benjamin Gray
2023-08-29 6:34 ` [PATCH 3/3] powerpc/watchpoints: Annotate atomic context in more places Benjamin Gray
2023-08-29 6:42 ` [PATCH 0/3] Fix preemption errors in watchpoints Benjamin Gray
2023-09-21 9:24 ` 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=169528828844.872767.7469796002349483809.b4-ty@ellerman.id.au \
--to=patch-notifications@ellerman.id.au \
--cc=bgray@linux.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.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.