qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Sean Halle <seanhalle@yahoo.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] libqemu for use in parallel-language based simulator
Date: Thu, 02 Feb 2012 18:29:58 -0800	[thread overview]
Message-ID: <477413.37640.bm@smtp101.mail.ne1.yahoo.com> (raw)


Hi,

    We’re trying to use QEMU as a library in our 
research. We have created a parallel language for 
simulating parallel activities. The language 
controls the suspension and re-animation of 
threads it creates, in such a way that physical 
memory contents remains consistent with the order of events in simulation time.

    We want to simulate processors, using QEMU as 
their behavior. This means the language has to 
control suspending QEMU and re-animating it. 
Which works fine if QEMU is called as a library, 
in one of the language’s threads.

    Libvirt won't work ­ our language doesn’t 
have control over OS threads ­ and the overhead 
of OS threads is around 50x higher than our 
language, even more on larger machines (We just 
submitted a paper measuring the difference).

    libqemu appears to be the heart of what we 
need.  Just the core functionality of a 
processor's instruction-set.  We will need a few 
thousand or so separate processor-states, similar 
to how COREMU has multiple processor states.
    Searches for other tools that use libqemu 
this way haven't yielded results..  We're just in 
the planning stages of adding QEMU..  any help on 
problems we're likely to encounter, or places 
that others may have used libqemu by itself, will be greatly appreciated,

Thanks, Sean

             reply	other threads:[~2012-02-03  2:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-03  2:29 Sean Halle [this message]
2012-02-03  6:21 ` [Qemu-devel] libqemu for use in parallel-language based simulator 陳韋任

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=477413.37640.bm@smtp101.mail.ne1.yahoo.com \
    --to=seanhalle@yahoo.com \
    --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).