From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: FW: Notification from Qemu to Guest Date: Tue, 28 Apr 2009 15:01:05 +0300 Message-ID: <49F6F001.80300@redhat.com> References: <3D9CB4061D1EB3408D4A0B910433453C030BABA761@inbmail01.lsi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: "kvm@vger.kernel.org" , Anthony Liguori To: "Kumar, Venkat" Return-path: Received: from mx2.redhat.com ([66.187.237.31]:51270 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753714AbZD1MAb (ORCPT ); Tue, 28 Apr 2009 08:00:31 -0400 In-Reply-To: <3D9CB4061D1EB3408D4A0B910433453C030BABA761@inbmail01.lsi.com> Sender: kvm-owner@vger.kernel.org List-ID: Kumar, Venkat wrote: > Hi Avi - Probably you can answer this question? > > I'm no virtio expert; copying someone who is. > > I have emulated a PCI device on Qemu and hooked my sample/simple driver to that virtio device on the guest. > > I am testing the notification from Guest-Qemu and vice-versa. > > I am able to notify from Guest to Qemu but Qemu-Guest notification is not happening. > > As a part of "Kick" routine in my guest driver I could see the notification happening from Guest-Qemu and In the Qemu process as a part of handle output for the emulated device I am simply doing "virtio_notify(vdev, vq)" but I don't see my callback getting called which is already registered as a part of "find_vq" in guest driver's probe. > You need to enable notifications, not sure how exactly. > BTW, the emulated device is allocated with "GSI 11" where as for other emulated devices like "virtio-blk" is associated with GSI 10 which I found in "dmesg's". Is this a reason why interrupt is not delivered from Qemu-Guest? > Interrupts for PCI devices are assigned based on the slots where they sit. Both GSI 10 and GSI 11 are PCI link interrupts. -- I have a truly marvellous patch that fixes the bug which this signature is too narrow to contain.