All of lore.kernel.org
 help / color / mirror / Atom feed
From: Frederic Konrad <fred.konrad@greensocs.com>
To: Sean Xie <sean.xie@red-chips.com>
Cc: Mark Burton <mark.burton@greensocs.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] QEMU+SystemC
Date: Thu, 12 Dec 2013 21:39:18 +0800	[thread overview]
Message-ID: <52A9BC86.2030000@greensocs.com> (raw)
In-Reply-To: <CAHgaQ+PVivm-UQgy-By+Xhn8+_z=La6PefN3ej+fAxXV_6DLMQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 973 bytes --]

On 12/12/2013 01:09, Sean Xie wrote:
> Hi all,
>
> Recently I am struggling in examing the effect of host kernel I/O 
> stacks on high-speed SSD, especially the new PCIe SSD, without 
> the availability of the necessary hardware. After several reading 
> online I found out QEMU+SystemC model environment might be able to to 
> solve my problem.
>
> Sorry I am new to QEMU. My main objective is to collect guest OS 
> statistics based on the attached external SSD model. So simple SystemC 
> stub will be the best for my case. Can anybody give me any suggestion 
> on which QEMU variant with SystemC fit me the best? I will sincerely 
> appreciate that if you could forward me the correct URL for download also.
>
> Thank you for your attention,
>
> Sean Xie

Hi,

We made a SystemC wrapper for QEMU with some limitations and a QEMU
version which is a little old now.

Maybe that can suit your need, what kind of statistics do you want to get
from the guest?

Thanks,
Fred

[-- Attachment #2: Type: text/html, Size: 1918 bytes --]

  reply	other threads:[~2013-12-12 13:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-11 17:09 [Qemu-devel] QEMU+SystemC Sean Xie
2013-12-12 13:39 ` Frederic Konrad [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-08-04 22:08 [Qemu-devel] qemu+systemc Damien Bardon

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=52A9BC86.2030000@greensocs.com \
    --to=fred.konrad@greensocs.com \
    --cc=mark.burton@greensocs.com \
    --cc=qemu-devel@nongnu.org \
    --cc=sean.xie@red-chips.com \
    /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.