From: Stefan Hajnoczi <stefanha@gmail.com>
To: Andrei Bacs <andrei.bacs@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] kvm guest-host separation
Date: Tue, 21 Apr 2015 14:59:40 +0100 [thread overview]
Message-ID: <20150421135940.GH16345@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <CAKDzk=85sH3MPGdOMDKNo57e_Z2ASj-CMHxGWukdDoC+c4u+gw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 422 bytes --]
On Fri, Apr 17, 2015 at 08:31:47PM +0200, Andrei Bacs wrote:
> I would like to implement some security checks in the qemu user process
> that would monitor the disk I/O of a KVM guest.
You probably need to avoid QEMU's zero-copy disk I/O, depending on the
security checks you are performing. Otherwise the guest can modify the
contents of I/O buffers while the host is checking them.
What are you trying to do?
Stefan
[-- Attachment #2: Type: application/pgp-signature, Size: 473 bytes --]
prev parent reply other threads:[~2015-04-21 13:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-17 18:31 [Qemu-devel] kvm guest-host separation Andrei Bacs
2015-04-21 13:59 ` Stefan Hajnoczi [this message]
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=20150421135940.GH16345@stefanha-thinkpad.redhat.com \
--to=stefanha@gmail.com \
--cc=andrei.bacs@gmail.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).