qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Blue Swirl <blauwirbel@gmail.com>
To: Ben Vogler <bvogler@toyotatech.com.au>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Benchmarking activities
Date: Fri, 1 Jul 2011 22:32:45 +0300	[thread overview]
Message-ID: <BANLkTi=BjM4be3qAcdhvhkS_7YWatfZDQA@mail.gmail.com> (raw)
In-Reply-To: <CEA33001889C174B834ECD2CD8B0C12805F2995D@auc11mx.toyotatech.com.au>

2011/6/27 Ben Vogler <bvogler@toyotatech.com.au>:
> Hi QEMU devel team,
>
>
>
> I work for Toyota Technical Centre Australia in the software department. We
> are currently conducting benchmarking on a broad spectrum of virtual
> platform simulators. I was wondering if I could ask you guys a few question
> about QEMU, however I understand if it is too much to ask. Below is a list
> of questions I have:
>
>
>
> -          I have seen examples of QEMU processor cores being wrapped in
> SystemC and used in OSCI based virtual systems – is this the general
> approach, or is there other/better ways of going about using QEMU not as an
> emulator (such as VMware), but as a simulator?

Maybe this report from QEMU User Forum may help:
http://lists.nongnu.org/archive/html/qemu-devel/2011-03/msg02065.html

> -          Is there full backwards compatibility between versions of QEMU?

In some cases (maybe x86 only) there is migration compatibility
between versions. In other cases this effort has not been considered
worthwhile.

> -          I have been looking but could not find a complete list of
> processor core models supported by QEMU. I have seen there are processors
> from Sparc, ARM, MIPS, but are there any core models from NEC, or Renesas in
> particular? Would you please be able to point me in the right direction?

Those are not supported. Each emulator can list the CPU models with
flag -cpu '?'.

>
>
>
> The rest of my questions are based on the assumption that QEMU IP will be
> used in a virtual system simulation, rather than emulation.
>
>
>
> -          Is co-simulation possible? For example, connecting an engine
> model running in Dymola to the QEMU (processor model) based virtual system
> simulator.

No idea.

> -           Are there any inbuilt data tracing features? For example,
> hardware signal tracing, register monitoring etc.

Tracing is quite new addition, so far it's only used for development
or debugging QEMU point of view I think.

>
>
>
>
> Thanks for your time.
>
>
>
>
>
> Regards,
>
>
>
> TOYOTA TECHNICAL CENTER AUSTRALIA
> Ben Vogler            ベン・ヴォグラ
> Software Engineer
> Software Development Group
> 611-633 Blackburn Road
> Notting Hill, VIC 3168
> Email:    bvogler@toyotatech.com.au
>
> Phone:  +61 3 9501 5226
>
> Confidential - do not forward this email.
>
> P  Please consider the environment before printing this e-mail
>
>

  reply	other threads:[~2011-07-01 19:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-26 23:02 [Qemu-devel] Benchmarking activities Ben Vogler
2011-07-01 19:32 ` Blue Swirl [this message]
2011-07-02  8:32   ` Stefan Hajnoczi
2011-07-02 11:50     ` Edgar E. Iglesias
2011-07-02 15:46     ` Andreas Färber
2011-07-04 12:47       ` Lluís

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='BANLkTi=BjM4be3qAcdhvhkS_7YWatfZDQA@mail.gmail.com' \
    --to=blauwirbel@gmail.com \
    --cc=bvogler@toyotatech.com.au \
    --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).