From: Hollis Blanchard <hollisb@us.ibm.com>
To: kvm-ppc@vger.kernel.org
Subject: Re: [kvm-ppc-devel] [PATCH 1/5] Remove KVM_HANDLER macro.
Date: Tue, 29 Jan 2008 16:41:38 +0000 [thread overview]
Message-ID: <1201624898.22639.20.camel@basalt> (raw)
In-Reply-To: <12012451794158-git-send-email-wei.zhang@freescale.com>
On Tue, 2008-01-29 at 14:02 +0800, Zhang Wei wrote:
>
> > However, now that we've gotten away from binary patching the branch
> > instruction, I'm not eager to go back to that with the "li"
> > instruction.
> > Each handler is only 24 bytes, so I'm not that worried about
> > duplicating
> > them, and the readability and simplicity are better with the
> > duplication.
> >
>
> Another reason is e500 have additional exceptions for SPE exceptions
> (IVOR32 - IVOR35).
> And there are hole from IVOR16 to IVOR 31. If we use fixed macro
> functions definition,
> we will leave blank functions there. How about it?
True, in that case I think your approach will be best. Could you rebase
the patch?
--
Hollis Blanchard
IBM Linux Technology Center
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
kvm-ppc-devel mailing list
kvm-ppc-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-ppc-devel
next prev parent reply other threads:[~2008-01-29 16:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-25 7:12 [kvm-ppc-devel] [PATCH 1/5] Remove KVM_HANDLER macro Zhang Wei
2008-01-28 20:41 ` Hollis Blanchard
2008-01-29 4:16 ` Hollis Blanchard
2008-01-29 6:02 ` Zhang Wei
2008-01-29 16:41 ` Hollis Blanchard [this message]
2008-01-30 5:46 ` Zhang Wei
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=1201624898.22639.20.camel@basalt \
--to=hollisb@us.ibm.com \
--cc=kvm-ppc@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox