linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Ananth N Mavinakayanahalli <ananth@in.ibm.com>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org, Paul Mackerras <paulus@samba.org>
Subject: Re: [PATCH] Emulate more instructions in software
Date: Wed, 18 Apr 2007 12:43:49 +0530	[thread overview]
Message-ID: <20070418071349.GA11729@in.ibm.com> (raw)
In-Reply-To: <4F8C7783-242E-4254-A8AD-A8452C7B248C@kernel.crashing.org>

On Wed, Apr 18, 2007 at 01:11:00AM -0500, Kumar Gala wrote:
> 
> On Apr 18, 2007, at 12:56 AM, Ananth N Mavinakayanahalli wrote:
> 
> > Emulate a few more instructions in software - especially useful during
> > singlestepping (xmon/kprobes).
> >
> > Instructions emulated with this patch are mfcr/mtcr rX, mfxer/mtxer  
> > rX,
> > mflr/mtlr rX, mfctr/mtctr rX and mr rA,rB.
> >
> >
> > Signed-off-by: Ananth N Mavinakayanahalli <ananth@in.ibm.com>
> 
> When do we actually need to emulate any of these instructions?  I  
> don't see why single stepping would effect the ability to execute  
> these instructions.

In cases when these instructions are kprobed, it'd be possible to
eliminate the single step exception as we can emulate them.

Most usecases of kprobes are at function entry and in most cases, the
instruction at function entry is mflr r0, which can be emulated. So you
can get rid of one exception and get a nice speedup too. My other patch
did just this.

Ananth

  reply	other threads:[~2007-04-18  7:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-18  5:56 [PATCH] Emulate more instructions in software Ananth N Mavinakayanahalli
2007-04-18  6:11 ` Kumar Gala
2007-04-18  7:13   ` Ananth N Mavinakayanahalli [this message]
2007-04-18 16:23     ` Kumar Gala
2007-04-18 16:25       ` Kumar Gala
2007-04-19  4:17         ` Ananth N Mavinakayanahalli

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=20070418071349.GA11729@in.ibm.com \
    --to=ananth@in.ibm.com \
    --cc=galak@kernel.crashing.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=paulus@samba.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).