All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@gmail.com>
To: Arnabjyoti Kalita <akalita@cs.stonybrook.edu>
Cc: qemu-devel@nongnu.org, Pavel Dovgalyuk <pavel.dovgaluk@ispras.ru>
Subject: Re: [Qemu-devel] Recording I/O activity after KVM does a VMEXIT
Date: Thu, 31 May 2018 09:50:57 +0100	[thread overview]
Message-ID: <20180531085057.GG26429@stefanha-x1.localdomain> (raw)
In-Reply-To: <CAJGDS+HNBG6PSvG7Cc7bN4rMadgm5W+1aQUAeizN9CGjSOCP5w@mail.gmail.com>

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

On Wed, May 30, 2018 at 11:19:13PM -0400, Arnabjyoti Kalita wrote:
> I am trying to implement a 'minimal' record-replay mechanism for KVM, which
> is similar to the one existing for TCG via -icount. I am trying to record
> I/O events only (specifically disk and network events) when KVM does a
> VMEXIT. This has led me to the function kvm_cpu_exec where I can clearly
> see the different ways of handling all of the possible VMExit cases (like
> PIO, MMIO etc.). To record network packets, I am working with the e1000
> hardware device.
> 
> Can I make sure that all of the network I/O, atleast for the e1000 device
> happens through the KVM_EXIT_MMIO case and subsequent use of the
> address_space_rw() function ? Do I also need to look at other functions as
> well ? Also for recording disk activity, can I make sure that looking out
> for the KVM_EXIT_MMIO and/or KVM_EXIT_PIO cases in the vmexit mechanism,
> will be enough ?
> 
> Let me know if there are other details that I need to take care of. I am
> using QEMU 2.11 on a x86-64 CPU and the guest runs a Linux Kernel 4.4 with
> Ubuntu 16.04.

I have CCed Pavel Dovgalyuk, the record/replay maintainer.

Stefan

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 455 bytes --]

  reply	other threads:[~2018-05-31  8:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-31  3:19 [Qemu-devel] Recording I/O activity after KVM does a VMEXIT Arnabjyoti Kalita
2018-05-31  8:50 ` Stefan Hajnoczi [this message]
2018-05-31 12:44   ` Pavel Dovgalyuk
2018-05-31 20:14     ` Arnabjyoti Kalita
2018-06-01  5:31       ` Pavel Dovgalyuk
2018-06-01  8:27         ` Arnabjyoti Kalita
2018-06-01  9:32           ` Pavel Dovgalyuk

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=20180531085057.GG26429@stefanha-x1.localdomain \
    --to=stefanha@gmail.com \
    --cc=akalita@cs.stonybrook.edu \
    --cc=pavel.dovgaluk@ispras.ru \
    --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 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.