From: Kyle McMartin <kyle@hera.kernel.org>
To: linux-parisc@vger.kernel.org
Subject: [git] parisc: Changes to ref refs/heads/tracehook
Date: Sun, 5 Jul 2009 19:12:44 GMT [thread overview]
Message-ID: <200907051912.n65JCiPx011838@hera.kernel.org> (raw)
New commits:
commit cc29c79e2c02e3857c4856d58efc703e8f404d4a
Author: Kyle McMartin <kyle@phobos.i.jkkm.org>
Date: Sun Jul 5 15:08:57 2009 -0400
parisc: stop using task->ptrace for {single,block}step flags
task->ptrace flags belong to generic code, so instead thief some
TIF_ bits to use. Somewhat risky conversion of code to test TASK_FLAGS
instead of TASK_PTRACE in assembly, but it looks alright in the end.
Not-yet-signed-off-by: Kyle McMartin <kyle@mcmartin.ca>
commit 78db65f7fffd1fc875d76e531b3a047ea61cf480
Author: Kyle McMartin <kyle@phobos.i.jkkm.org>
Date: Sun Jul 5 14:36:16 2009 -0400
parisc: split syscall_trace into two halves
Instead of fiddling with gr[20], restructure code to return whether
or not to -ENOSYS. (Also do a bit of fiddling to let them take
pt_regs directly instead of re-computing it.)
Not-yet-signed-off-by: Kyle McMartin <kyle@mcmartin.ca>
commit 089a930b17e497d35d84b0ee388112e24a5ffb34
Author: Kyle McMartin <kyle@phobos.i.jkkm.org>
Date: Sun Jul 5 14:39:58 2009 -0400
parisc: add missing TI_TASK macro in syscall.S
LDREG 0(%r1),%r1 really wants to be accessing thread_info.task,
instead of hardcoding the 0.
Signed-off-by: Kyle McMartin <kyle@mcmartin.ca>
next reply other threads:[~2009-07-05 19:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-05 19:12 Kyle McMartin [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-09-28 3:44 [git] parisc: Changes to ref refs/heads/tracehook Kyle McMartin
2009-07-07 19:07 Kyle McMartin
2009-07-07 18:46 Kyle McMartin
2009-07-07 17:29 Kyle McMartin
2009-07-07 6:45 Kyle McMartin
2009-07-07 7:16 ` Kyle McMartin
2009-07-07 1:40 Kyle McMartin
2009-07-06 21:30 Kyle McMartin
2009-07-05 20:02 Kyle McMartin
2009-07-05 20:01 Kyle McMartin
2009-07-03 4:51 Kyle McMartin
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=200907051912.n65JCiPx011838@hera.kernel.org \
--to=kyle@hera.kernel.org \
--cc=linux-parisc@vger.kernel.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.