qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Johan Rydberg <jrydberg@night.trouble.net>
To: "David S. Miller" <davem@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Updated Sparc support
Date: Thu, 15 May 2003 22:17:24 +0200	[thread overview]
Message-ID: <20030515201724.GA19302@bushwacker> (raw)
In-Reply-To: <20030515.130541.41655467.davem@redhat.com>; from davem@redhat.com on Thu, May 15, 2003 at 22:05:41 +0200

On 2003.05.15 22:05 David S. Miller wrote:

>    The reason for me asking is that I some time soon "port" my
> simulator
>    [1] to SPARC hosts, and it needs to have a lot of global registers
>    (more than those 6-7 available).
> 
> Just only execute the generated code in a fixed context and thus
> in the same register window, then at the call site into the generated
> code clobber all of the input registers.

The global registers will initially not be used for dynamic generated
code, but in the direct threaded interpreter.  Using global registers
for commonly used variables such as the CPU structure and current 
virtual
program counter will increase the performance with a magnitude I guess.

So, if I understand you correctly, everything should work pretty good
i you use -fflat and stay away from the input registers?  (I have no
need for the -fno-delay-slot flag)

> Just look at the qemu code, it works quite well.

Will do that aswell.

brgds,
Johan.

  reply	other threads:[~2003-05-15 20:14 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-13  4:13 [Qemu-devel] [PATCH] Updated Sparc support David S. Miller
2003-05-13 12:31 ` [Qemu-devel] " Fabrice Bellard
2003-05-13 19:49   ` David S. Miller
2003-05-14  0:13   ` Rusty Russell
2003-05-14 11:48     ` Fabrice Bellard
2003-05-16 13:54       ` [Qemu-devel] Regression tests - syscall note Fabrice Bellard
2003-05-15 13:03 ` [Qemu-devel] [PATCH] Updated Sparc support Johan Rydberg
2003-05-15 20:05   ` David S. Miller
2003-05-15 20:17     ` Johan Rydberg [this message]
2003-05-15 20:24       ` David S. Miller

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=20030515201724.GA19302@bushwacker \
    --to=jrydberg@night.trouble.net \
    --cc=davem@redhat.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).