qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: LIU Zhiwei <zhiwei_liu@c-sky.com>
To: pavel.dovgaluk@ispras.ru
Cc: Palmer Dabbelt <palmer@dabbelt.com>,
	Richard Henderson <richard.henderson@linaro.org>,
	Alistair Francis <Alistair.Francis@wdc.com>,
	"qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>,
	pbonzini@redhat.com
Subject: Questions about record & replay for RISC-V
Date: Tue, 12 May 2020 10:01:31 +0800	[thread overview]
Message-ID: <30f3e5ff-fd20-5005-a033-d8c93a0f3194@c-sky.com> (raw)

Hi Pavel,

I am developing a profiling tool depending on record & replay feature of 
QEMU for  RISC-V.
Here I'd like to ask you some questions.

First, is it possible to record & replay a Linux system by this feature 
in theory? I mean keep the strict instruction
sequence of each process and kernel, for a very simple image,  with only 
timer and UART.

Second, is it planed to support RISC-V?

Thanks very much.

Best regards,
Zhiwei


                 reply	other threads:[~2020-05-12  2:02 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=30f3e5ff-fd20-5005-a033-d8c93a0f3194@c-sky.com \
    --to=zhiwei_liu@c-sky.com \
    --cc=Alistair.Francis@wdc.com \
    --cc=palmer@dabbelt.com \
    --cc=pavel.dovgaluk@ispras.ru \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=richard.henderson@linaro.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).