From: Avi Kivity <avi@qumranet.com>
To: Fabrice Bellard <fabrice@bellard.org>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [4514] convert remaining segment handling to TCG
Date: Wed, 21 May 2008 21:19:39 +0300 [thread overview]
Message-ID: <483467BB.7000803@qumranet.com> (raw)
In-Reply-To: <48345E88.5080908@bellard.org>
Fabrice Bellard wrote:
>>
>> Does qemu generate different code when the segment bases are zero?
>> The segment base additions can be trivially avoided in this case.
>
> Yes, but only when DS, ES and SS have zero bases.
>
Sure, that's the common case.
On a slightly different subject, are you considering improving tcg
optimization? It can even be made dynamic, with aggressive optimization
only kicking in if a block has been executed a large number of times.
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
prev parent reply other threads:[~2008-05-21 18:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-21 16:34 [Qemu-devel] [4514] convert remaining segment handling to TCG Fabrice Bellard
2008-05-21 17:01 ` Avi Kivity
2008-05-21 17:40 ` Fabrice Bellard
2008-05-21 18:19 ` Avi Kivity [this message]
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=483467BB.7000803@qumranet.com \
--to=avi@qumranet.com \
--cc=fabrice@bellard.org \
--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).