linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Paul Mackerras <paulus@ozlabs.org>
To: linuxppc-dev@ozlabs.org
Subject: [PATCH 0/3] powerpc: Free up CPU feature bits
Date: Tue, 20 Mar 2018 08:46:10 +1100	[thread overview]
Message-ID: <1521495973-3237-1-git-send-email-paulus@ozlabs.org> (raw)

This patch series is against the powerpc next branch.  It takes
advantage of the fact that there are only a few CPU feature bits that
are meaningful on both 32-bit and 64-bit platforms.  At the moment,
many of the 64 bits of the CPU feature mask on 64-bit platforms are
taken up with bits which are only relevant to 32-bit platforms.  This
series rearranges things so that we can use those bits for new
features that are relevant only to 64-bit platforms.  With this, there
are now 20 bits available for new 64-bit features.

To make things simpler, we use the bottom 12 bits of the CPU feature
word for features that are relevant to both 32-bit and 64-bit
platforms.  The remaining 20 or 52 bits are then available for
features specific to 32-bit or 64-bit platforms.

Paul.

 arch/powerpc/include/asm/cputable.h       | 223 +++++++++++++++---------------
 arch/powerpc/include/asm/time.h           |   2 +-
 arch/powerpc/kernel/cpu_setup_6xx.S       |   2 +-
 arch/powerpc/kernel/cpu_setup_fsl_booke.S |   2 +-
 arch/powerpc/kernel/dt_cpu_ftrs.c         |   3 +-
 arch/powerpc/kernel/vdso.c                |  12 +-
 6 files changed, 122 insertions(+), 122 deletions(-)

             reply	other threads:[~2018-03-19 21:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-19 21:46 Paul Mackerras [this message]
2018-03-19 21:46 ` [PATCH 1/3] powerpc: Use feature bit for RTC presence rather than timebase presence Paul Mackerras
2018-03-26  8:56   ` [1/3] " Michael Ellerman
2018-03-19 21:46 ` [PATCH 2/3] powerpc: Book E: Remove unused CPU_FTR_L2CSR bit Paul Mackerras
2018-03-19 21:46 ` [PATCH 3/3] powerpc: Free up CPU feature bits on 64-bit machines Paul Mackerras

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=1521495973-3237-1-git-send-email-paulus@ozlabs.org \
    --to=paulus@ozlabs.org \
    --cc=linuxppc-dev@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).