qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Richard Henderson <rth@twiddle.net>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Blue Swirl <blauwirbel@gmail.com>, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Re: Compile files only once: some planning
Date: Wed, 24 Mar 2010 13:12:06 -0700	[thread overview]
Message-ID: <4BAA7216.3020105@twiddle.net> (raw)
In-Reply-To: <4BAA46D8.1080505@twiddle.net>

On 03/24/2010 10:07 AM, Richard Henderson wrote:
> struct CPUSmallCommonState
> {
>     // most of the stuff from CPU_COMMON.
>     // sorted for some thought of padding elimination.  ;-)
> };
> 
> struct CPULargeCommonState
> {
>     CPUTLBEntry tlb_table[NB_MMU_MODES][CPU_TLB_SIZE];
>     target_phys_addr_t iotlb[NB_MMU_MODES][CPU_TLB_SIZE];
>     struct TranslationBlock *tb_jmp_cache[TB_JMP_CACHE_SIZE];
>     jmp_buf jmp_env;
> };
...
> Now.  If you're compiling a file for which cpu-specific code is ok:
> 
> register CPUXYZLargeState *env __asm__(AREG0);
> #define ENV_SMALL_COMMON_STATE    (&env->s.common_s)
> #define ENV_LARGE_COMMON_STATE    (&env->common_l)
> 
> If you're compiling a file which is supposed to be independant of cpu:
> 
> register CPUSmallCommonState *env __asm__(AREG0);
> #define ENV_SMALL_COMMON_STATE    (env)
> #define ENV_LARGE_COMMON_STATE    ((CPULargeCommonState *)((char *)env + cpu_large_state_offset))

On 03/24/2010 11:00 AM, Blue Swirl wrote:
> One trick is to define a fixed offset (about half CPUState size) and
> make env point to CPUState + offset. Then the negative part of the
> offset space can be used efficiently. But this just doubles the space
> that can be accessed fast, so it's not a big win.

A good idea.  We can eliminate the cpu_large_state_offset from above via:

struct CPUSmallCommonState
{
    // most of the stuff from CPU_COMMON.
} __attribute__((aligned));

struct CPUXYZPrivateState
{
    // all the cpu-specific stuff
};

struct CPUXYZSmallState
{
    CPUXYZPrivateState p;
    CPUSmallCommonState s;
};

struct CPUXYZAllState
{
    CPUXYZSmallState s;
    CPULargeCommonState l;  // ARG0 register points here.
};

register void *biased_env __asm__(AREG0);

static inline CPUXYZPrivateState *get_env_cpu_private(void)
{
    return &((CPUXYZSmallState *)biased_env - 1)->p;
}

static inline CPUSmallCommonState *get_env_common_small(void)
{
    return (CPUSmallCommonState *)biased_env - 1;
}

static inline CPULargeCommonState *get_env_common_large(void)
{
    return (CPULargeCommonState *)biased_env;
}


r~

  reply	other threads:[~2010-03-24 20:13 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-23 21:43 [Qemu-devel] Compile files only once: some planning Blue Swirl
2010-03-24  9:17 ` [Qemu-devel] " Juan Quintela
2010-03-24 17:56   ` Blue Swirl
2010-03-24 19:28     ` Juan Quintela
2010-03-24 22:47       ` Paul Brook
2010-03-24 22:57         ` Anthony Liguori
2010-03-25  3:08           ` Jamie Lokier
2010-03-25  2:54   ` Jamie Lokier
2010-03-24  9:47 ` Paolo Bonzini
2010-03-24 11:19   ` Richard Henderson
2010-03-24 14:45     ` Paolo Bonzini
2010-03-24 14:56       ` Paul Brook
2010-03-24 16:18         ` Paolo Bonzini
2010-03-24 17:27           ` Paul Brook
2010-03-24 17:07       ` Richard Henderson
2010-03-24 20:12         ` Richard Henderson [this message]
2010-03-24 18:00     ` Blue Swirl
2010-03-24 19:39 ` Michael S. Tsirkin
2010-03-24 20:05   ` Blue Swirl
2010-03-24 20:08     ` Michael S. Tsirkin
2010-03-24 20:24       ` Blue Swirl
2010-03-24 20:24         ` Michael S. Tsirkin
2010-03-24 20:32           ` Blue Swirl
2010-03-24 20:28         ` Anthony Liguori
2010-03-24 21:00         ` Aurelien Jarno
2010-03-24 22:33     ` Paul Brook
2010-03-24 22:50       ` Anthony Liguori
2010-03-24 23:05         ` Paul Brook
2010-03-24 23:07           ` Anthony Liguori
2010-03-25  8:21             ` Michael S. Tsirkin
2010-03-25 12:01               ` Paul Brook

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=4BAA7216.3020105@twiddle.net \
    --to=rth@twiddle.net \
    --cc=blauwirbel@gmail.com \
    --cc=pbonzini@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).