qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Cc: Blue Swirl <blauwirbel@gmail.com>, Alexander Graf <agraf@suse.de>
Subject: Re: [Qemu-devel] Re: [PATCH 2/3] PPC64: Implement slbmte
Date: Mon, 2 Mar 2009 19:07:42 +0000	[thread overview]
Message-ID: <200903021907.43121.paul@codesourcery.com> (raw)
In-Reply-To: <E5D5B27F-D0E1-4B14-94F9-854445DC55BB@suse.de>

> >>  target_ulong helper_load_sr (target_ulong sr_num)
> >>  {
> >> +    if (env->mmu_model & POWERPC_MMU_64)
> >> +        return ppc_load_sr(env, sr_num);
> >>     return env->sr[sr_num];
> >>  }
> >
> > It would be faster to move the MMU model checks to translation time.
>
> The problem is that we don't know which -cpu the user will give us
> when we run qemu-system-ppc64.

You're confusing translation time with compile time.

Paul

  reply	other threads:[~2009-03-02 19:07 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-02 17:07 [Qemu-devel] [PATCH 0/3] PPC64 Linux bringup patches Alexander Graf
2009-03-02 17:07 ` [Qemu-devel] [PATCH 1/3] PPC: Circumvent overflow in mtcrf Alexander Graf
2009-03-02 17:07   ` [Qemu-devel] [PATCH 2/3] PPC64: Implement slbmte Alexander Graf
2009-03-02 17:07     ` [Qemu-devel] [PATCH 3/3] PPC64: Implement large pages Alexander Graf
2009-03-02 18:58     ` [Qemu-devel] Re: [PATCH 2/3] PPC64: Implement slbmte Blue Swirl
2009-03-02 19:00       ` Alexander Graf
2009-03-02 19:07         ` Paul Brook [this message]
2009-03-02 19:28         ` Blue Swirl
2009-03-02 19:47           ` Alexander Graf
2009-03-02 18:53   ` [Qemu-devel] Re: [PATCH 1/3] PPC: Circumvent overflow in mtcrf Blue Swirl
2009-03-02 22:45   ` [Qemu-devel] " Laurent Desnogues
2009-03-03 10:26     ` Alexander Graf
2009-03-03 10:30       ` Laurent Desnogues

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=200903021907.43121.paul@codesourcery.com \
    --to=paul@codesourcery.com \
    --cc=agraf@suse.de \
    --cc=blauwirbel@gmail.com \
    --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).