All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@web.de>
To: Le Tan <tamlokveer@gmail.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Why devfn will be -1
Date: Tue, 01 Jul 2014 14:56:49 +0200	[thread overview]
Message-ID: <53B2B011.2020604@web.de> (raw)
In-Reply-To: <CACrq+iJb_B+L52YHXz3qpu9_d0giLQAHwWtbvdy8Eo0zrgdG7Q@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1341 bytes --]

On 2014-07-01 14:55, Le Tan wrote:
> 2014-07-01 20:52 GMT+08:00 Le Tan <tamlokveer@gmail.com>:
>> Hi Jan,
>>
>> 2014-07-01 15:34 GMT+08:00 Jan Kiszka <jan.kiszka@web.de>:
>>> Hi Le,
>>>
>>> On 2014-07-01 04:34, Le Tan wrote:
>>>> Hi Jan,
>>>> I use pci_setup_iommu() to setup a PCIIOMMUFunc for the q35 pci bus.
>>>> In the iommu_fn, I print out the devfn parameter and find out that it
>>>> sometimes will be -1. So what does it mean?
>>>> The detail code is here:
>>>>
>>>> In mch_init() function, I write like this:
>>>> PCIBus *pci_bus = PCI_BUS(qdev_get_parent_bus(DEVICE(mch)));
>>>> pci_setup_iommu(pci_bus, q35_host_dma_iommu, mch->iommu);
>>>>
>>>> And in q35_host_dma_iommu(PCIBus *bus, void *opaque, int devfn), I
>>>> print out the devfn parameter, sometimes it will be -1.
>>>
>>> Hmm, I have no idea about the reason and would suggest to set a
>>> conditional breakpoint on this function, then print the backtrace to see
>>> where this comes from and analyze the device structure from where that
>>> -1 was most probably taken.
> 
> I think maybe this is a bug? In the function do_pci_register_device(),
> maybe these two sentence should be reorder?
> dma_as = pci_device_iommu_address_space(pci_dev);
> pci_dev->devfn = devfn;

Looks like. Give it a try, then possibly send a patch :)

Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 263 bytes --]

  reply	other threads:[~2014-07-01 12:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-01  2:34 [Qemu-devel] Why devfn will be -1 Le Tan
2014-07-01  7:34 ` Jan Kiszka
2014-07-01 12:52   ` Le Tan
2014-07-01 12:55     ` Le Tan
2014-07-01 12:56       ` Jan Kiszka [this message]
2014-07-01 13:02         ` Le Tan
2014-07-01 13:08           ` Jan Kiszka

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=53B2B011.2020604@web.de \
    --to=jan.kiszka@web.de \
    --cc=qemu-devel@nongnu.org \
    --cc=tamlokveer@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.