From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: ioeventfd question Date: Fri, 27 May 2011 11:30:16 +0300 Message-ID: <4DDF6118.9030103@redhat.com> References: <1306436620.3065.43.camel@lappy> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: kvm , Ingo Molnar , Pekka Enberg , Asias He , Prasad Joshi , Cyrill Gorcunov To: Sasha Levin Return-path: Received: from mx1.redhat.com ([209.132.183.28]:27582 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757391Ab1E0Iae (ORCPT ); Fri, 27 May 2011 04:30:34 -0400 In-Reply-To: <1306436620.3065.43.camel@lappy> Sender: kvm-owner@vger.kernel.org List-ID: On 05/26/2011 10:03 PM, Sasha Levin wrote: > 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. You can use KVM_IOEVENTFD_FLAG_DATAMATCH for that. -- I have a truly marvellous patch that fixes the bug which this signature is too narrow to contain.