qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: "Andreas Färber" <afaerber@suse.de>
Cc: i.mitsyanko@samsung.com, Evgeny Voevodin <e.voevodin@samsung.com>,
	qemu-devel@nongnu.org, kyungmin.park@samsung.com,
	d.solodkiy@samsung.com, m.kozlov@samsung.com
Subject: Re: [Qemu-devel] [PATCH v2] TCG: Convert global variables to be TLS.
Date: Thu, 1 Mar 2012 08:27:04 +0000	[thread overview]
Message-ID: <CAFEAcA8sm7163krL5RKB=tjsuphti=GEDaGwfh2Srpy696hAZA@mail.gmail.com> (raw)
In-Reply-To: <4F4F31D2.7010608@suse.de>

On 1 March 2012 08:22, Andreas Färber <afaerber@suse.de> wrote:
> Am 28.02.2012 04:13, schrieb Evgeny Voevodin:
>> On 27.02.2012 16:35, Peter Maydell wrote:
>>> A true multithreaded TCG is a large project, and unless we're
>>> going to commit to doing that I don't see much value in making
>>> some variables per-thread when we might instead need to do
>>> larger refactorings (properly encapsulating the codegen
>>> caches as qom objects, maybe?).
>>
>> [...] qomification of translation caches is an interesting suggestion I
>> think.
>
> While I have come to like QOM and am using it for the CPUState, I don't
> see the benefit in using it for these secondary structures. There are
> already dedicated monitor commands to inspect them, no?

Mostly I was thinking about the encapsulation of knowing which data
structures are associated with a translation cache and letting you
have more than one of them. You could do that with a plain struct
but since we have this OO infrastructure now why not use it?

-- PMM

  reply	other threads:[~2012-03-01  8:27 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-27 11:06 [Qemu-devel] [PATCH] TCG: Convert global variables to be TLS Evgeny Voevodin
2012-02-27 11:06 ` Evgeny Voevodin
2012-02-27 11:43 ` Evgeny Voevodin
2012-02-27 12:13 ` [Qemu-devel] [PATCH v2] " Evgeny Voevodin
2012-02-27 12:35   ` Peter Maydell
2012-02-28  3:13     ` Evgeny Voevodin
2012-02-28  8:10       ` Peter Maydell
2012-02-29  3:26         ` 陳韋任
2012-02-29  3:43           ` Evgeny Voevodin
2012-02-29  3:46             ` 陳韋任
2012-02-29  4:01               ` Evgeny Voevodin
2012-03-01  7:51         ` 陳韋任
2012-03-02  6:08           ` Evgeny Voevodin
2012-03-01  8:22       ` Andreas Färber
2012-03-01  8:27         ` Peter Maydell [this message]
2012-03-01 10:57           ` Evgeny Voevodin

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='CAFEAcA8sm7163krL5RKB=tjsuphti=GEDaGwfh2Srpy696hAZA@mail.gmail.com' \
    --to=peter.maydell@linaro.org \
    --cc=afaerber@suse.de \
    --cc=d.solodkiy@samsung.com \
    --cc=e.voevodin@samsung.com \
    --cc=i.mitsyanko@samsung.com \
    --cc=kyungmin.park@samsung.com \
    --cc=m.kozlov@samsung.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).