qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Aurelien Jarno <aurelien@aurel32.net>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH 0/6] AREG0 patches v4
Date: Sun, 8 Jan 2012 01:52:47 +0100	[thread overview]
Message-ID: <20120108005247.GA20125@hall.aurel32.net> (raw)
In-Reply-To: <CAAu8pHvF4sCMi2prP3z+Ri+M0aC0fX1_Wu_HdP0ivAmErSRPig@mail.gmail.com>

On Sat, Jan 07, 2012 at 10:24:09PM +0000, Blue Swirl wrote:
> In this version, I made basic AREG0 free load/store implementations
> for all targets. Only x86-64 is tested, others have probably problems,
> especially 64 bit guest (Sparc64 in this case) on 32 bit hosts.
> 
> I think this should be committed as a starting point if there are no
> major objections.
> 

If it is known to be broken on 32-bit hosts, I am not sure it's really
a good idea to commit these patches. It's just going to prevent all
people developing on x86 to continue testing or developing QEMU.

Also I have to say I still don't get the goal of these patch series. I
have just tried it on an x86-64 guest with a 32-bit sparc guest. It
works well, but the generated TB are slightly bigger. I have done a
quick and dirty performance test by compiling some code inside the
guests, and I get a slow down of about 0.6%, though for this kind of
performance changes, it should probably done with other methods.

Is there another goal behind this patch series beside performance?

-- 
Aurelien Jarno	                        GPG: 1024D/F1BCDB73
aurelien@aurel32.net                 http://www.aurel32.net

  reply	other threads:[~2012-01-08  0:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-07 22:24 [Qemu-devel] [PATCH 0/6] AREG0 patches v4 Blue Swirl
2012-01-08  0:52 ` Aurelien Jarno [this message]
2012-01-08 12:27   ` Blue Swirl
2012-01-09 23:04     ` Aurelien Jarno
2012-01-21 16:55       ` Blue Swirl

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=20120108005247.GA20125@hall.aurel32.net \
    --to=aurelien@aurel32.net \
    --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).