qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Isaku Yamahata <yamahata@valinux.co.jp>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] MSI broken?
Date: Wed, 3 Nov 2010 22:37:18 +0900	[thread overview]
Message-ID: <20101103133718.GC26077@valinux.co.jp> (raw)
In-Reply-To: <4CD1585B.2010200@redhat.com>

On Wed, Nov 03, 2010 at 01:40:59PM +0100, Gerd Hoffmann wrote:
> On 11/03/10 13:34, Isaku Yamahata wrote:
>> On Wed, Nov 03, 2010 at 12:03:15PM +0100, Gerd Hoffmann wrote:
>>>   Hi,
>>>
>>> What is the status if the recently merged MSI support?
>>>
>>> I'm trying to use it to add msi support to the intel-hda driver (current
>>> wip patch attached).  Everything works fine up to the point where it
>>> comes to delivering the interrupt to the guest.  msi_notify pretends to
>>> signal the guest:
>>>
>>> msi_notify:243 intel-hda:30 notify vector 0x0 address: 0xfee01008 data:
>>> 0x4151
>>>
>>> The guest never ever receives this interrupt though:
>>>
>>> [root@localhost ~]# grep hda /proc/interrupts
>>>   43:          0   PCI-MSI-edge      hda_intel
>>>
>>> Ideas anyone?
>>
>> Let's track it down futher.
>> Were acpi_mem_writel() and apic_send_msi() in hw/apic.c called or not?
>
> No such function in my tree (savannah/master).
>
> Looks like some bits needed for msi are not merged yet?

Sorry typo. s/acpi/apic/.

I'm looking at 7d72e76228351d18a856f1e4f5365b59d3205dc3
of git://git.savannah.nongnu.org/qemu.git


>
> cheers,
>   Gerd
>

-- 
yamahata

  reply	other threads:[~2010-11-03 13:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-03 11:03 [Qemu-devel] MSI broken? Gerd Hoffmann
2010-11-03 12:34 ` Isaku Yamahata
2010-11-03 12:40   ` Gerd Hoffmann
2010-11-03 13:37     ` Isaku Yamahata [this message]
2010-11-03 15:15       ` Gerd Hoffmann

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=20101103133718.GC26077@valinux.co.jp \
    --to=yamahata@valinux.co.jp \
    --cc=kraxel@redhat.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).