public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: "Kumar, Venkat" <Venkat.Kumar@lsi.com>
Cc: "kvm@vger.kernel.org" <kvm@vger.kernel.org>,
	Anthony Liguori <anthony@codemonkey.ws>
Subject: Re: FW: Notification from Qemu to Guest
Date: Tue, 28 Apr 2009 15:01:05 +0300	[thread overview]
Message-ID: <49F6F001.80300@redhat.com> (raw)
In-Reply-To: <3D9CB4061D1EB3408D4A0B910433453C030BABA761@inbmail01.lsi.com>

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.


  reply	other threads:[~2009-04-28 12:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-28 11:54 FW: Notification from Qemu to Guest Kumar, Venkat
2009-04-28 12:01 ` Avi Kivity [this message]
2009-04-28 15:11   ` Anthony Liguori
2009-04-28 17:00     ` Kumar, Venkat
2009-05-01 17:35       ` Pantelis Koukousoulas

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=49F6F001.80300@redhat.com \
    --to=avi@redhat.com \
    --cc=Venkat.Kumar@lsi.com \
    --cc=anthony@codemonkey.ws \
    --cc=kvm@vger.kernel.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