From: Michael Gagnon <mgagnon1@gmu.edu>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Time complexity for self-modifying code
Date: Thu, 08 Feb 2007 15:01:57 -0500 [thread overview]
Message-ID: <45CB81B5.9080405@gmu.edu> (raw)
Hello. I'm a student at George Mason University and I had a question
regarding the time complexity of QEMU's algorithm for dealing with
self-modifying code.
From looking at the QEMU Internals documentation
(http://fabrice.bellard.free.fr/qemu/qemu-tech.html), it seems that
QEMU's method for handling self-modifying code might have different
algorithmic efficiency classes for it's average case and worst case. As
in, on average I assume that QEMU emulates instructions at O(n)
efficiency. In the worst-case, might self-modifying code change the
efficiency of QEMU to another order of efficiency, such as O(n^2)? Any
thoughts would be greatly appreciated. Thanks!
Mike Gagnon
http://www.mikegagnon.com
next reply other threads:[~2007-02-08 20:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-08 20:01 Michael Gagnon [this message]
2007-02-08 20:37 ` [Qemu-devel] Time complexity for self-modifying code 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=45CB81B5.9080405@gmu.edu \
--to=mgagnon1@gmu.edu \
--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).