From: Stefan Roese <ml@stefan-roese.de>
To: Joakim Tjernlund <joakim.tjernlund@transmode.se>
Cc: Scott Wood <scottwood@freescale.com>, linuxppc-dev@lists.ozlabs.org
Subject: Re: FTrace on MPC8xx
Date: Thu, 14 Apr 2011 17:59:30 +0200 [thread overview]
Message-ID: <201104141759.30446.ml@stefan-roese.de> (raw)
In-Reply-To: <OF832AEAAB.68C38F85-ONC1257871.0055965D-C1257871.0055E1C2@transmode.se>
Hi Joakim,
On Wednesday 13 April 2011 17:38:03 Joakim Tjernlund wrote:
> > > How big was the size to copy_tofrom_user()? Did it mange to copy
> > > any bytes?
> >
> > The size in __copy_tofrom_user is 4. And its the first call in
> > ftrace_modify_code() that fails directly. This works just fine on a
> > PPC440EPx board.
>
> Since the size is only 4 it would not use dcbX anyway(I think).
> Then is is probably called with the wrong addresses?
No, addresses seem to be correct. I checked a bit further (I'm quite new to
the MPC8xx MMU) and it seems that trying to modify the code (that's the
destination address) via __copy_tofrom_user() fails on MPC8xx. Still not sure
why this is the case. Perhaps an 8xx guru might chime in here. ;)
BTW: I just noticed that enabling CONFIG_PIN_TLB seems to resolve this issue.
With this option enabled, the dynamic code modification works just fine.
Joakim, Scott? Any ideas on this?
Thanks,
Stefan
next prev parent reply other threads:[~2011-04-14 15:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-13 14:32 FTrace on MPC8xx Stefan Roese
2011-04-13 14:58 ` Joakim Tjernlund
2011-04-13 15:21 ` Stefan Roese
2011-04-13 15:38 ` Joakim Tjernlund
2011-04-14 15:59 ` Stefan Roese [this message]
2011-04-14 16:49 ` Joakim Tjernlund
2011-04-14 19:21 ` Joakim Tjernlund
2011-04-15 7:22 ` Stefan Roese
2011-04-15 8:46 ` Joakim Tjernlund
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=201104141759.30446.ml@stefan-roese.de \
--to=ml@stefan-roese.de \
--cc=joakim.tjernlund@transmode.se \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=scottwood@freescale.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