From: Michael Neuling <mikey@neuling.org>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] Fix ptrace compat wrapper for fpu register access
Date: Tue, 31 Mar 2009 09:53:59 +1100 [thread overview]
Message-ID: <12572.1238453639@neuling.org> (raw)
In-Reply-To: <m2myb32rk8.fsf@igel.home>
In message <m2myb32rk8.fsf@igel.home> you wrote:
> Michael Neuling <mikey@neuling.org> writes:
>
> >> @@ -263,7 +263,9 @@ long compat_arch_ptrace(struct task_stru
> >> ret = ptrace_put_reg(child, numReg, freg);
> >> } else {
> >> flush_fp_to_thread(child);
> >> - ((unsigned int *)child->thread.regs)[index] = data;
> >> + ((unsigned int *)child->thread.fpr)
> >> + [TS_FPRWIDTH * (numReg - PT_FPR0) * 2 +
> >> + index % 2] = data;
> >
> > I think the indexing here should be the same as PEEKUSR_3264. This
> > looks better but all this magic indexing makes me want to vomit.
>
> How about this instead:
>
> @@ -241,6 +241,7 @@ long compat_arch_ptrace(struct task_stru
> case PPC_PTRACE_POKEUSR_3264: {
> u32 index;
> u32 numReg;
> + u32 *tmp;
>
> ret = -EIO;
> /* Determine which register the user wants */
> @@ -263,7 +264,8 @@ long compat_arch_ptrace(struct task_stru
> ret = ptrace_put_reg(child, numReg, freg);
> } else {
> flush_fp_to_thread(child);
> - ((unsigned int *)child->thread.regs)[index] = data;
> + tmp = (u32 *)child->thread.fpr[numReg - PT_FPR0];
> + tmp[index % 2] = data;
I do like this approach better (two arrays) but there is no accounting
for TS_WIDTH, so I'm not sure it works.
We *really* need a test case for this stuff :-)
Mikey
> ret = 0;
> }
> break;
>
> 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:[~2009-03-30 22:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-29 17:56 [PATCH] Fix ptrace compat wrapper for fpu register access Andreas Schwab
2009-03-29 23:57 ` Michael Neuling
2009-03-30 9:17 ` Andreas Schwab
2009-03-30 9:52 ` Michael Neuling
2009-03-30 11:11 ` Andreas Schwab
2009-03-30 22:53 ` Michael Neuling [this message]
2009-04-06 6:48 ` Michael Neuling
2009-04-06 6:59 ` Michael Neuling
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=12572.1238453639@neuling.org \
--to=mikey@neuling.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=schwab@linux-m68k.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 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).