linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Roland McGrath <roland@redhat.com>
To: linuxppc-dev@ozlabs.org
Subject: how to check for "optional" ppc chip features (MSR_BE)
Date: Thu,  1 May 2008 18:21:18 -0700 (PDT)	[thread overview]
Message-ID: <20080502012118.96ED926FA07@magilla.localdomain> (raw)

I've been looking at PowerISA_Public.pdf that I downloaded from some ppc
site.  It describes various things as "need not be supported on all
implementations", for example the MSR_BE bit.  Is there a generic way to
detect if such a feature is supported, or a known table of models that
support features, or what?

Right now I'm considering MSR_BE (branch tracing).  I have a patch to use
this (arch_has_block_step, enabling a PTRACE_SINGLEBLOCK).  The only
machine handy to test is a Mac G5 (PPC970FX, 3.0 (pvr 003c 0300)).  I know
this chip supports MSR_BE.  But that's only because I wrote an affirmative
test case and tried it and saw it work right.  

Before submitting the kernel changes, I want to get the CPU model
conditionalization correct (a runtime check on some feature bit mask is
fine here, if CONFIG_* alone does not indicate for sure).


Thanks,
Roland

             reply	other threads:[~2008-05-02  1:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-02  1:21 Roland McGrath [this message]
2008-05-02  3:48 ` how to check for "optional" ppc chip features (MSR_BE) Kumar Gala
2008-05-04 21:45   ` Benjamin Herrenschmidt
2008-05-04 23:12     ` Roland McGrath
2008-05-05  0:49       ` Benjamin Herrenschmidt
2008-05-13 11:55       ` Paul Mackerras
2008-05-13 13:47         ` Kumar Gala
2008-05-13 19:33         ` Roland McGrath
2008-06-11 16:05           ` 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=20080502012118.96ED926FA07@magilla.localdomain \
    --to=roland@redhat.com \
    --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).