qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: Alexander Graf <agraf@suse.de>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 2/6] Implement POWER7's CFAR in TCG
Date: Thu, 11 Aug 2011 10:35:25 +1000	[thread overview]
Message-ID: <20110811003525.GB6342@yookeroo.fritz.box> (raw)
In-Reply-To: <4E429F53.9030108@suse.de>

On Wed, Aug 10, 2011 at 05:10:11PM +0200, Alexander Graf wrote:
> On 08/04/2011 09:02 AM, David Gibson wrote:
[snip]
> >@@ -187,12 +195,13 @@ typedef struct DisasContext {
> >      int le_mode;
> >  #if defined(TARGET_PPC64)
> >      int sf_mode;
> >+    int has_cfar;
> >  #endif
> >      int fpu_enabled;
> >      int altivec_enabled;
> >      int spe_enabled;
> >      ppc_spr_t *spr_cb; /* Needed to check rights for mfspr/mtspr */
> >-    int singlestep_enabled;
> >+    int singlestep_enabled;
> 
> Fairly sure this isn't intended :)

Oops, fixed.  I think I'll blame Ben for that one :).  And the others.

[snip]
> >@@ -6508,6 +6519,14 @@ static void init_proc_POWER7 (CPUPPCState *env)
> >                   &spr_read_purr, SPR_NOACCESS,
> >                   &spr_read_purr, SPR_NOACCESS,
> >                   0x00000000);
> >+    spr_register(env, SPR_CFAR, "SPR_CFAR",
> >+                 SPR_NOACCESS, SPR_NOACCESS,
> >+&spr_read_cfar,&spr_write_cfar,
> >+                 0x00000000);
> >+    spr_register(env, SPR_DSCR, "SPR_DSCR",
> >+                 SPR_NOACCESS, SPR_NOACCESS,
> >+&spr_read_generic,&spr_write_generic,
> >+                 0x00000000);
> 
> Are you sure this is only present on POWER7 and no machines before
> that? Does 970 have CFAR?

Looking at the feature bits in the kernel, it appears that it's in
POWER6 and POWER7, but not in 970, POWER4 or POWER5.  Since we don't
have a model for POWER5 or POWER6, I believe the qemu logic here is
correct.

-- 
David Gibson			| I'll have my music baroque, and my code
david AT gibson.dropbear.id.au	| minimalist, thank you.  NOT _the_ _other_
				| _way_ _around_!
http://www.ozlabs.org/~dgibson

  reply	other threads:[~2011-08-11  0:44 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-04  7:02 [Qemu-devel] pseries machine updates David Gibson
2011-08-04  7:02 ` [Qemu-devel] [PATCH 1/6] pseries: Bugfixes for interrupt numbering in XICS code David Gibson
2011-08-04  7:02 ` [Qemu-devel] [PATCH 2/6] Implement POWER7's CFAR in TCG David Gibson
2011-08-10 15:10   ` Alexander Graf
2011-08-11  0:35     ` David Gibson [this message]
2011-08-04  7:02 ` [Qemu-devel] [PATCH 3/6] pseries: Add real mode debugging hcalls David Gibson
2011-08-10 15:19   ` Alexander Graf
2011-08-04  7:02 ` [Qemu-devel] [PATCH 4/6] pseries: Add a phandle to the xicp interrupt controller device tree node David Gibson
2011-08-04  7:02 ` [Qemu-devel] [PATCH 5/6] pseries: interrupt controller should not have a 'reg' property David Gibson
2011-08-04  7:02 ` [Qemu-devel] [PATCH 6/6] pseries: More complete WIMG validation in H_ENTER code David Gibson
2011-08-10 15:16 ` [Qemu-devel] pseries machine updates Alexander Graf
2011-08-10 15:24   ` Alexander Graf
2011-08-11  0:44     ` David Gibson
2011-08-31  9:18       ` Alexander Graf
2011-08-11  0:39   ` David Gibson
2011-08-31  9:17     ` Alexander Graf
2011-09-01  1:45       ` David Gibson
2011-09-02 13:20         ` Alexander Graf

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=20110811003525.GB6342@yookeroo.fritz.box \
    --to=david@gibson.dropbear.id.au \
    --cc=agraf@suse.de \
    --cc=qemu-devel@nongnu.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).