From: Richard Henderson <rth@twiddle.net>
To: qemu-devel@nongnu.org
Cc: "Andreas Färber" <afaerber@suse.de>
Subject: Re: [Qemu-devel] [PATCH] cpu: Move tcg_exit_req to the end of CPUState
Date: Wed, 19 Mar 2014 14:04:16 -0700 [thread overview]
Message-ID: <532A0650.3040109@twiddle.net> (raw)
In-Reply-To: <1394836210-15934-1-git-send-email-rth@twiddle.net>
Ping? This is a significant TCG code size regression
for ARM, AArch64, and Sparc hosts. It helps x86 too,
though that's not as severe.
r~
On 03/14/2014 03:30 PM, Richard Henderson wrote:
> Reverse an increase in the size of generated code.
>
> Cc: Andreas Färber <afaerber@suse.de>
> Signed-off-by: Richard Henderson <rth@twiddle.net>
> ---
> include/qom/cpu.h | 7 ++++++-
> 1 file changed, 6 insertions(+), 1 deletion(-)
>
> diff --git a/include/qom/cpu.h b/include/qom/cpu.h
> index 06ee263..f99885a 100644
> --- a/include/qom/cpu.h
> +++ b/include/qom/cpu.h
> @@ -227,7 +227,6 @@ struct CPUState {
> bool stop;
> bool stopped;
> volatile sig_atomic_t exit_request;
> - volatile sig_atomic_t tcg_exit_req;
> uint32_t interrupt_request;
> int singlestep_enabled;
> int64_t icount_extra;
> @@ -272,6 +271,12 @@ struct CPUState {
> } icount_decr;
> uint32_t can_do_io;
> int32_t exception_index; /* used by m68k TCG */
> +
> + /* Note that this is accessed at the start of every TB via a negative
> + offset from AREG0. Leave this field at the end so as to make the
> + (absolute value) offset as small as possible. This reduces code
> + size, especially for hosts without large memory offsets. */
> + volatile sig_atomic_t tcg_exit_req;
> };
>
> QTAILQ_HEAD(CPUTailQ, CPUState);
>
next prev parent reply other threads:[~2014-03-19 21:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-14 22:30 [Qemu-devel] [PATCH] cpu: Move tcg_exit_req to the end of CPUState Richard Henderson
2014-03-19 21:04 ` Richard Henderson [this message]
2014-03-19 21:13 ` Andreas Färber
2014-03-19 22:13 ` Richard Henderson
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=532A0650.3040109@twiddle.net \
--to=rth@twiddle.net \
--cc=afaerber@suse.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 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).