From: Clemens Kolbitsch <ck@iseclab.org>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] dyngen_code in 16 bit
Date: Mon, 14 Apr 2008 12:16:08 +0200 [thread overview]
Message-ID: <200804141216.08755.ck@iseclab.org> (raw)
Hi!
For a research project I extended Qemu to include some extra code inside the
op_XXX instructions that increased the generated TB-code's size to quite some
extend...
Now I have a problem when having block chaining enabled (that I don't want to
disable for performance reasons :-/): The code_gen_buffer sometimes contains
code areas that span more than 0xffff bytes, however, dyngen and all
functions related to it use 16 bit pointers, etc. Therefore, e.g. the
dyngen_code function uses the 16 bit pointers to overwrite certain params and
of course destroys the TB-code.
When working with x86 hosts and guests (both 32 bit), is there a specific
reason for all these pointers to be 16 bits or has it just been a safe
assumption up to now?? I have tried rewriting the code to use 32 bit, but
keep getting segfaults... however, of course, I might have missed some code
still.
Any help is - as always - greatly appreciated!!
Cheers,
Clemens
next reply other threads:[~2008-04-14 10:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-14 10:16 Clemens Kolbitsch [this message]
2008-04-14 11:32 ` [Qemu-devel] Re: dyngen_code in 16 bit Clemens Kolbitsch
2008-04-14 16:08 ` Clemens Kolbitsch
-- strict thread matches above, loose matches on Subject: below --
2008-04-14 16:08 [Qemu-devel] " Clemens Kolbitsch
2008-04-14 16:19 ` 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=200804141216.08755.ck@iseclab.org \
--to=ck@iseclab.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 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.