qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Cc: Clemens Kolbitsch <clemens.kol@gmx.at>
Subject: Re: [Qemu-devel] dyngen_code in 16 bit
Date: Mon, 14 Apr 2008 17:19:19 +0100	[thread overview]
Message-ID: <200804141719.19754.paul@codesourcery.com> (raw)
In-Reply-To: <200804141808.34958.clemens.kol@gmx.at>

On Monday 14 April 2008, Clemens Kolbitsch wrote:
> 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...

Don't do that. Put it in a helper function. The performance overhead will be 
minimal.

Most likely the segfaults are because you're overrunning a buffer. qemu has 
static limits on the maximum size of an guest instruction.

Paul

  reply	other threads:[~2008-04-14 16:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-14 16:08 [Qemu-devel] dyngen_code in 16 bit Clemens Kolbitsch
2008-04-14 16:19 ` Paul Brook [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-04-14 10:16 Clemens Kolbitsch

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=200804141719.19754.paul@codesourcery.com \
    --to=paul@codesourcery.com \
    --cc=clemens.kol@gmx.at \
    --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).