From: Sasha Levin <levinsasha928@gmail.com>
To: Avi Kivity <avi@redhat.com>
Cc: kvm <kvm@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>,
Pekka Enberg <penberg@kernel.org>,
Asias He <asias.hejun@gmail.com>,
Prasad Joshi <prasadjoshi124@gmail.com>,
Cyrill Gorcunov <gorcunov@gmail.com>
Subject: ioeventfd question
Date: Thu, 26 May 2011 22:03:40 +0300 [thread overview]
Message-ID: <1306436620.3065.43.camel@lappy> (raw)
Hi Avi,
I'm working on adding ioeventfd support into tools/kvm/.
Currently the implementation creates ioeventfd entries at the
'VIRTIO_PCI_QUEUE_NOTIFY' of each device and waits on all of them using
epoll().
The basics are working - when IO is triggered I receive a notification
using the event instead of an exit.
I couldn't find a way to retrieve the value written to the PIO port -
the guest memory at that location doesn't change, 'reading' the event
just returns 1 (as expected) and I couldn't find anything else which
might suggest what value was written to the PIO port.
This is an issue with devices which have multiple virtio-rings, such as
virtio-net.
--
Sasha.
next reply other threads:[~2011-05-26 19:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-26 19:03 Sasha Levin [this message]
2011-05-27 8:30 ` ioeventfd question Avi Kivity
2011-05-27 8:39 ` Sasha Levin
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=1306436620.3065.43.camel@lappy \
--to=levinsasha928@gmail.com \
--cc=asias.hejun@gmail.com \
--cc=avi@redhat.com \
--cc=gorcunov@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=penberg@kernel.org \
--cc=prasadjoshi124@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox