From: Andreas Schwab <schwab@linux-m68k.org>
To: prasad@linux.vnet.ibm.com
Cc: linuxppc-dev@ozlabs.org,
Dave Kleikamp <shaggy@linux.vnet.ibm.com>,
Srikar Dronamraju <srikar@linux.vnet.ibm.com>,
Paul Mackerras <paulus@samba.org>
Subject: Re: ppc_set_hwdebug vs ptrace_set_debugreg
Date: Mon, 13 Dec 2010 20:05:36 +0100 [thread overview]
Message-ID: <m2vd2x1ojj.fsf@igel.home> (raw)
In-Reply-To: <20101213082619.GA6582@in.ibm.com> (K. Prasad's message of "Mon, 13 Dec 2010 13:56:19 +0530")
"K.Prasad" <prasad@linux.vnet.ibm.com> writes:
> +#ifdef CONFIG_HAVE_HW_BREAKPOINT
> + /* Create a new breakpoint request if one doesn't exist already */
> + hw_breakpoint_init(&attr);
> + attr.bp_addr = bp_info->addr & ~HW_BREAKPOINT_ALIGN;
> + arch_bp_generic_fields(bp_info->addr &
> + (DABR_DATA_WRITE | DABR_DATA_READ),
> + &attr.bp_type);
> +
> + bp = register_user_hw_breakpoint(&attr, ptrace_triggered, task);
> + if (IS_ERR(bp))
> + return PTR_ERR(bp);
> +
> + child->thread.ptrace_bps[0] = bp;
> +#endif /* CONFIG_HAVE_HW_BREAKPOINT */
> +
> child->thread.dabr = (unsigned long)bp_info->addr;
That cannot work, see
<http://permalink.gmane.org/gmane.linux.ports.ppc64.devel/71418>.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2010-12-13 19:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-27 19:36 ppc_set_hwdebug vs ptrace_set_debugreg Andreas Schwab
2010-11-29 7:22 ` K.Prasad
2010-11-29 10:15 ` Andreas Schwab
2010-12-01 4:37 ` K.Prasad
2010-12-13 8:26 ` K.Prasad
2010-12-13 19:05 ` Andreas Schwab [this message]
2010-12-14 12:54 ` K.Prasad
2010-12-14 18:59 ` Andreas Schwab
2010-12-16 17:07 ` Andreas Schwab
2011-01-02 12:54 ` K.Prasad
2011-01-02 14:58 ` Andreas Schwab
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=m2vd2x1ojj.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.org \
--cc=prasad@linux.vnet.ibm.com \
--cc=shaggy@linux.vnet.ibm.com \
--cc=srikar@linux.vnet.ibm.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).