From: Stefan Hajnoczi <stefanha@gmail.com>
To: "Dong, Eddie" <eddie.dong@intel.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Asynchronous / synchronous IO emulation
Date: Thu, 24 Nov 2016 11:16:55 +0000 [thread overview]
Message-ID: <20161124111655.GD9117@stefanha-x1.localdomain> (raw)
In-Reply-To: <A12AC9D104E08D47BAF23C492F83C53B54624913@SHSMSX104.ccr.corp.intel.com>
[-- Attachment #1: Type: text/plain, Size: 409 bytes --]
On Thu, Nov 24, 2016 at 08:44:06AM +0000, Dong, Eddie wrote:
> Under certain situation, we have a requirement to apply the virtual DMA event in a deterministic way. Current Qemu uses asynchronous approach to emulate the virtual IO events since quite long time ago. I am wondering if we still have an option to choose the synchronous emulation solution.
Please explain exactly what you mean.
Stefan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 455 bytes --]
next prev parent reply other threads:[~2016-11-24 11:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-24 8:44 [Qemu-devel] Asynchronous / synchronous IO emulation Dong, Eddie
2016-11-24 11:16 ` Stefan Hajnoczi [this message]
2016-11-25 9:17 ` Dong, Eddie
2016-11-25 12:01 ` Stefan Hajnoczi
2016-11-26 7:27 ` Dong, Eddie
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=20161124111655.GD9117@stefanha-x1.localdomain \
--to=stefanha@gmail.com \
--cc=eddie.dong@intel.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).