All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@web.de>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: dyngen-exec.h cleanup
Date: Sun, 08 Mar 2009 17:00:00 +0100	[thread overview]
Message-ID: <49B3EB80.6080901@web.de> (raw)
In-Reply-To: <761ea48b0903080846p6a0c0bfcoc96dd2f37490dde0@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1671 bytes --]

Laurent Desnogues wrote:
> On Sun, Mar 8, 2009 at 4:36 PM, Jan Kiszka <jan.kiszka@web.de> wrote:
>> Laurent Desnogues wrote:
>>> On Sun, Mar 8, 2009 at 3:41 PM, Jan Kiszka <jan.kiszka@web.de> wrote:
>>>> Also, some discussion on this list suggested that it's more efficient to
>>>> look into converting the remaining AREGS to TCG and finally do the
>>>> ultimative "rm dyngen-exec.h". Don't you want to spend some time on this
>>>> already?
>>> This requires modifying ARM translator which is the last one to use
>>> AREGn with n>0. And don't all targets use AREG0 as a pointer to the
>>> CPU state?
>> Yes, but wasn't it you who suggested that all those users should be
>> converted over to the tcg_global_reg API?
> 
> Yes, and I did the work for ARM.  However when considering the
> removal of AREG0, and after looking at generated code, I came
> to the perhaps premature conclusion that removing it would not
> bring me any speedup (at least for a not so register starved
> target as x86_64).

I don't think we are looking for speedup here, just for cleanup. Status
quo regarding performance after a conversion would be more than fine IMHO.

> 
>> There is surely some work to do, and that probably across all archs. But
>> the sooner we should start. dyngen-exec.h is a constant source of pain
>> when you try to introduce new headers or refactor existing ones.
> 
> Well dyngen-exec.h is long gone in my sources even though
> AREG0 is still used.  I would have to backtrack my changes to
> see how I arrived to that, but for sure the first thing to do is to
> remove cpu_T from ARM target.

Yes, please share your wisdom!

Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 257 bytes --]

  reply	other threads:[~2009-03-08 16:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-08 13:25 [Qemu-devel] dyngen-exec.h cleanup Blue Swirl
2009-03-08 14:41 ` [Qemu-devel] " Jan Kiszka
2009-03-08 15:03   ` Laurent Desnogues
2009-03-08 15:36     ` Jan Kiszka
2009-03-08 15:46       ` Laurent Desnogues
2009-03-08 16:00         ` Jan Kiszka [this message]
2009-03-08 16:12           ` Laurent Desnogues
2009-03-08 16:39             ` Jan Kiszka
2009-03-08 15:16 ` [Qemu-devel] " Hasso Tepper
2009-03-08 16:28 ` Anthony Liguori

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=49B3EB80.6080901@web.de \
    --to=jan.kiszka@web.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.