From: Jason Wessel <jason.wessel@windriver.com>
To: Tim Bird <tim.bird@am.sony.com>
Cc: "kgdb-bugreport@lists.sourceforge.net"
<kgdb-bugreport@lists.sourceforge.net>,
linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] kdb: Add message about CONFIG_DEBUG_RODATA on failure to install breakpoint
Date: Wed, 21 Mar 2012 13:03:28 -0500 [thread overview]
Message-ID: <4F6A17F0.8060204@windriver.com> (raw)
In-Reply-To: <4F68FCE3.5090403@windriver.com>
On 03/20/2012 04:55 PM, Jason Wessel wrote:
>
> Obviously we are not going to go down the horrible hack route, so I
> thought I might look at how the kprobe implementation works, because
> they do deal with read-only pages. They created a function called
> text_poke() that is called from arch_arm_probe().
>
> It might be possible to take a short cut and use the
> arch_arm_probe() directly. Ultimately I would like to consider just
> using kprobes instead for things like single stepping etc..., but it
> still has a few problems with atomic reservations. This work had
> been shelved in back 2010, in favor of merging kdb. I am not sure
> if anyone wants to take a look at it, but I do think it might
> warrant some experimentation.
To follow up on this and move to closure, I did some investigation and
concluded it is possible to use the kprobes API to make use of the
text_poke() function.
I sent a patch series out for review with the implementation.
https://lkml.org/lkml/2012/3/21/375
Cheers,
Jason.
prev parent reply other threads:[~2012-03-21 18:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-21 20:07 [PATCH] kdb: Add message about CONFIG_DEBUG_RODATA on failure to install breakpoint Tim Bird
2012-03-20 18:32 ` Jason Wessel
2012-03-20 21:31 ` Tim Bird
2012-03-20 21:55 ` Jason Wessel
2012-03-21 18:03 ` Jason Wessel [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=4F6A17F0.8060204@windriver.com \
--to=jason.wessel@windriver.com \
--cc=kgdb-bugreport@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=tim.bird@am.sony.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).