From: Ingo Molnar <mingo@elte.hu>
To: Roland McGrath <roland@redhat.com>,
"K.Prasad" <prasad@linux.vnet.ibm.com>,
Alan Stern <stern@rowland.harvard.edu>
Cc: Alexey Dobriyan <adobriyan@gmail.com>,
Oleg Nesterov <oleg@redhat.com>,
akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
containers@lists.linux-foundation.org
Subject: Re: [PATCH] x86: ptrace debugreg checks rewrite
Date: Thu, 7 May 2009 11:13:57 +0200 [thread overview]
Message-ID: <20090507091357.GA26433@elte.hu> (raw)
In-Reply-To: <20090506203852.D9AC9FC39E@magilla.sf.frob.com>
* Roland McGrath <roland@redhat.com> wrote:
> > > On Mon, May 04, 2009 at 04:16:01AM +0400, Alexey Dobriyan wrote:
> > > > +static int ptrace_check_debugreg(int _32bit,
> > > > + unsigned long dr0, unsigned long dr1,
> > > > + unsigned long dr2, unsigned long dr3,
> > > > + unsigned long dr6, unsigned long dr7)
> > > > +{
> > > > + /* Breakpoint type: 00: --x, 01: -w-, 10: undefined, 11: rw- */
> > > > + unsigned int rw[4];
> > > > + /* Breakpoint length: 00: 1 byte, 01: 2 bytes, 10: 8 bytes, 11: bytes */
> > > 4 bytes, of course
> >
> > Roland, Oleg, do you have any pending/planned changes in this area?
>
> I don't. I expect the only future work on this arch debugreg
> stuff to be via the hw_breakpoint work, extending that and/or
> building new things on it.
Yes. That work, despite being in its upteenth iteration, is taking a
frustratingly long amount of time to get even to a minimal "review
passed, lets commit and test this in a tree a bit" intermediate
stage though.
I've Cc:-ed K.Prasad and Alan Stern. Roland, Oleg, would you be
interested in having a look at that thread, to help drive it
forward?
The last iteration was posted to lkml on Apr 24:
[Patch 00/12] Hardware Breakpoint Interfaces
and it has a good deal of ptrace, signal handling and other impact
as well.
Ingo
next prev parent reply other threads:[~2009-05-07 9:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-04 0:16 [PATCH] x86: ptrace debugreg checks rewrite Alexey Dobriyan
2009-05-04 0:24 ` Alexey Dobriyan
2009-05-06 9:56 ` Ingo Molnar
2009-05-06 20:38 ` Roland McGrath
2009-05-07 9:13 ` Ingo Molnar [this message]
2009-05-07 0:24 ` Oleg Nesterov
-- strict thread matches above, loose matches on Subject: below --
2009-06-22 21:09 Alexey Dobriyan
2009-06-23 8:55 ` Ingo Molnar
2009-06-23 9:47 ` Alexey Dobriyan
2009-06-30 21:48 ` Ingo Molnar
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=20090507091357.GA26433@elte.hu \
--to=mingo@elte.hu \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=containers@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@redhat.com \
--cc=prasad@linux.vnet.ibm.com \
--cc=roland@redhat.com \
--cc=stern@rowland.harvard.edu \
/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