linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Jon Loeliger <jdl@freescale.com>
To: Michael Ellerman <michael@ellerman.id.au>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 02/14] powerpc: Allow create_branch() to return errors
Date: Tue, 24 Jun 2008 08:26:00 -0500	[thread overview]
Message-ID: <4860F5E8.1060609@freescale.com> (raw)
In-Reply-To: <bda40d2750deae8e742dc9d115a6aab4843701ee.1214271072.git.michael@ellerman.id.au>

Michael Ellerman wrote:
> Currently create_branch() creates a branch instruction for you, and patches
> it into the call site. In some circumstances it would be nice to be able to
> create the instruction and patch it later, and also some code might want
> to check for errors in the branch creation before doing the patching. A
> future patch will change create_branch() to check for errors.
> 
> For callers that don't care, replace create_branch() with patch_branch(),
> which just creates the branch and patches it directly.
> 
> While we're touching all the callers, change to using unsigned int *, as
> this seems to match usage better. That allows (and requires) us to remove
> the volatile in the definition of vector in powermac/smp.c and mpc86xx_smp.c,
> that's correct because now that we're passing vector as an unsigned int *
> the compiler knows that it's value might change across the patch_branch()
> call.
> 
> Signed-off-by: Michael Ellerman <michael@ellerman.id.au>
> ---

86xx bits...

Acked-by: Jon Loeliger <jdl@freescale.com>

  parent reply	other threads:[~2008-06-24 13:26 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-24  1:32 [PATCH 01/14] powerpc: Move code patching code into arch/powerpc/lib/code-patching.c Michael Ellerman
2008-06-24  1:32 ` [PATCH 02/14] powerpc: Allow create_branch() to return errors Michael Ellerman
2008-06-24 13:20   ` Kumar Gala
2008-06-24 13:26   ` Jon Loeliger [this message]
2008-06-24  1:32 ` [PATCH 03/14] powerpc: Make create_branch() return errors if the branch target is too large Michael Ellerman
2008-06-24 13:21   ` Kumar Gala
2008-06-24  1:32 ` [PATCH 04/14] powerpc: Add ppc_function_entry() which gets the entry point for a function Michael Ellerman
2008-06-24 13:39   ` Kumar Gala
2008-06-24  1:32 ` [PATCH 05/14] powerpc: Add new code patching routines Michael Ellerman
2008-06-24 13:48   ` Kumar Gala
2008-06-26  3:54     ` Michael Ellerman
2008-06-24  1:32 ` [PATCH 06/14] powerpc: Add tests of the " Michael Ellerman
2008-06-24 13:48   ` Kumar Gala
2008-06-24  1:32 ` [PATCH 07/14] powerpc: Add PPC_NOP_INSTR, a hash define for the preferred nop instruction Michael Ellerman
2008-06-24 13:48   ` Kumar Gala
2008-06-24  1:32 ` [PATCH 08/14] powerpc: Split out do_feature_fixups() from cputable.c Michael Ellerman
2008-06-24 13:48   ` Kumar Gala
2008-06-24  1:32 ` [PATCH 09/14] powerpc: Consolidate CPU and firmware feature fixup macros Michael Ellerman
2008-06-24 13:48   ` Kumar Gala
2008-06-24  1:32 ` [PATCH 10/14] powerpc: Consolidate feature fixup macros for 64/32 bit Michael Ellerman
2008-06-24 13:48   ` Kumar Gala
2008-06-26  3:47     ` Michael Ellerman
2008-06-24  1:32 ` [PATCH 11/14] powerpc: Introduce infrastructure for feature sections with alternatives Michael Ellerman
2008-06-24  1:33 ` [PATCH 12/14] powerpc: Add logic to patch alternative feature sections Michael Ellerman
2008-06-24 13:47   ` Kumar Gala
2008-06-26  3:45     ` Michael Ellerman
2008-06-24  1:33 ` [PATCH 13/14] powerpc: Add self-tests of the feature fixup code Michael Ellerman
2008-06-24  1:33 ` [PATCH 14/14] powerpc: Use an alternative feature section in entry_64.S Michael Ellerman
2008-06-24 13:23 ` [PATCH 01/14] powerpc: Move code patching code into arch/powerpc/lib/code-patching.c Kumar Gala

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=4860F5E8.1060609@freescale.com \
    --to=jdl@freescale.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=michael@ellerman.id.au \
    /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).