qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Nathan Froyd <froydnj@codesourcery.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH 0/4] target-ppc: create TCG slots for registers based on CPU
Date: Sat, 28 Mar 2009 14:30:13 -0700	[thread overview]
Message-ID: <1238275817-9758-1-git-send-email-froydnj@codesourcery.com> (raw)

For PPC guests, I noticed that we create TCG slots for all the potential
kinds of registers (float, Altivec, SPE), even if the chip doesn't have
instructions to access those registers.

This patch series tweaks the initialization routine to create the TCG
values for registers necessary for particular classes of instructions
only if the emulated chip supports those instructions.  The first couple
of patches are simply busywork of moving things around; the last patch
is where all the action is at.

I am not a TCG expert, but there are several loops in TCG over all
globals and it seems like those loops would go faster if they didn't
have to consider registers that would never be touched.  If this patch
series makes no difference in TCG's performance, then I'd be glad to
have an explanation of why that's the case.

-Nathan

             reply	other threads:[~2009-03-28 21:30 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-28 21:30 Nathan Froyd [this message]
2009-03-28 21:30 ` [Qemu-devel] [PATCH 1/4] move PPC insn flags to cpu.h Nathan Froyd
2009-03-28 22:58   ` Aurelien Jarno
2009-03-28 23:07     ` Nathan Froyd
2009-03-28 23:14       ` Aurelien Jarno
2009-03-28 21:30 ` [Qemu-devel] [PATCH 2/4] move ppc_def_t definition " Nathan Froyd
2009-03-28 21:30 ` [Qemu-devel] [PATCH 3/4] pass the cpu definition to ppc_translate_init Nathan Froyd
2009-03-28 21:30 ` [Qemu-devel] [PATCH 4/4] create TCG slots for registers based on CPU Nathan Froyd
2009-03-28 22:54 ` [Qemu-devel] [PATCH 0/4] target-ppc: " Aurelien Jarno
2009-03-29  0:18   ` Nathan Froyd
2009-03-29 13:34     ` Aurelien Jarno
2009-03-29 14:42       ` Aurelien Jarno
2009-03-29 14:57         ` Aurelien Jarno

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=1238275817-9758-1-git-send-email-froydnj@codesourcery.com \
    --to=froydnj@codesourcery.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).