From: Michael Ellerman <patch-notifications@ellerman•id.au>
To: Michal Suchanek <msuchanek@suse•de>,
Benjamin Herrenschmidt <benh@kernel•crashing.org>,
Paul Mackerras <paulus@samba•org>,
Balbir Singh <bsingharora@gmail•com>,
Nicholas Piggin <npiggin@gmail•com>,
Breno Leitao <leitao@debian•org>,
Vaibhav Jain <vaibhav@linux•vnet.ibm.com>,
"Guilherme G. Piccoli" <gpiccoli@linux•vnet.ibm.com>,
Michal Suchanek <msuchanek@suse•de>,
linuxppc-dev@lists•ozlabs.org, linux-kernel@vger•kernel.org
Subject: Re: [v2] powerpc/xmon: Also setup debugger hooks when single-stepping
Date: Fri, 25 May 2018 21:41:54 +1000 (AEST) [thread overview]
Message-ID: <40skql47Ddz9s28@ozlabs.org> (raw)
In-Reply-To: <20180523180054.9937-1-msuchanek@suse.de>
On Wed, 2018-05-23 at 18:00:54 UTC, Michal Suchanek wrote:
> When single-stepping kernel code from xmon without a debug hook enabled
> the kernel crashes. This can happen when kernel starts with xmon on
> crash disabled but xmon is entered using sysrq.
>
> Call force_enable_xmon when single-stepping in xmon to install the xmon
> debug hooks.
>
> Fixes: e1368d0c9edb ("powerpc/xmon: Setup debugger hooks when first
> break-point is set")
>
> Signed-off-by: Michal Suchanek <msuchanek@suse•de>
> Reviewed-by: Vaibhav Jain <vaibhav@linux•ibm.com>
Applied to powerpc next, thanks.
https://git.kernel.org/powerpc/c/7daf59300999693b85233762b847f1
cheers
prev parent reply other threads:[~2018-05-25 11:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-23 18:00 [PATCH v2] powerpc/xmon: Also setup debugger hooks when single-stepping Michal Suchanek
2018-05-23 18:21 ` Vaibhav Jain
2018-05-25 11:41 ` 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=40skql47Ddz9s28@ozlabs.org \
--to=patch-notifications@ellerman$(echo .)id.au \
--cc=benh@kernel$(echo .)crashing.org \
--cc=bsingharora@gmail$(echo .)com \
--cc=gpiccoli@linux$(echo .)vnet.ibm.com \
--cc=leitao@debian$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=msuchanek@suse$(echo .)de \
--cc=npiggin@gmail$(echo .)com \
--cc=paulus@samba$(echo .)org \
--cc=vaibhav@linux$(echo .)vnet.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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