linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Varun Sethi <Varun.Sethi@freescale.com>
To: <agraf@suse.de>, <galak@kernel.crashing.org>,
	<benh@kernel.crashing.org>, <linuxppc-dev@lists.ozlabs.org>,
	<kvm-ppc@vger.kernel.org>
Cc: Varun Sethi <Varun.Sethi@freescale.com>
Subject: [PATCH 0/4] powerpc/booke: Modifications to fsl booke cpu setup code
Date: Mon, 9 Jul 2012 18:22:37 +0530	[thread overview]
Message-ID: <1341838357-16887-1-git-send-email-Varun.Sethi@freescale.com> (raw)

Modifications are aimed specifically at the e500mc/e5500 cpu setup code.
Following modifications are introduced by this patchset:
1. Move the E.HV check to the cpu setup code. Based on this check we manipulte the
   CPU_FTR_EMB_HV flag (added as a part of e500mc KVM support) in the cpu_spec 
   structure. We determine the presence of this feature based on the MMUCFG[LPIDSIZE]
   check and decide if we can setup the E.HV mode ivors.
2. Merge the 32 bit cpu setup code for e500mc/e5500 and define the "cpu_restore"
   routine (for e5500/e6500) only for the 64 bit case. The cpu_restore routine
   is used in the 64 bit case for setting up the secondary cores.
3. For the 64 bit case separate out e5500 cpu_setup and cpu_restore functions.
   The cpu_setup function (for the primary core) is passed the cpu_spec pointer,
   which is not there in case of the cpu_restore function. Also, in our case
   we will have to manipulate the CPU_FTR_EMB_HV flag on the the primary core.  
4. Added CPU_FTR_EMB_HV check for e5500.

Varun Sethi (4):
  Separate out E.HV check and ivor setup code.
  Merge the PPC 32 e5500 setup code with e500mc setup and don't define
  a restore routine for PPC 32.
  Separate out restore_e5500/setup_e5500 routines and check for E.HV
  mode before setting ivor setting code.
  Add CPU_FTR_EMB_HV check for e5500.

 arch/powerpc/kernel/cpu_setup_fsl_booke.S |   74 +++++++++++++++++++++++++----
 arch/powerpc/kernel/cputable.c            |    4 ++
 arch/powerpc/kernel/exceptions-64e.S      |   18 +------
 arch/powerpc/kernel/head_fsl_booke.S      |   18 ++-----
 4 files changed, 75 insertions(+), 39 deletions(-)

-- 
1.7.4.1

             reply	other threads:[~2012-07-09 12:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-09 12:52 Varun Sethi [this message]
2012-07-27 12:57 ` [PATCH 0/4] powerpc/booke: Modifications to fsl booke cpu setup code Sethi Varun-B16395

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=1341838357-16887-1-git-send-email-Varun.Sethi@freescale.com \
    --to=varun.sethi@freescale.com \
    --cc=agraf@suse.de \
    --cc=benh@kernel.crashing.org \
    --cc=galak@kernel.crashing.org \
    --cc=kvm-ppc@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.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).