xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Suravee Suthikulanit <suravee.suthikulpanit@amd.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>,
	Julien Grall <julien.grall@linaro.org>,
	Ian Campbell <ian.campbell@citrix.com>,
	Stefano Stabellini <stefano.stabellini@citrix.com>,
	xen-devel <xen-devel@lists.xen.org>,
	Jan Beulich <jbeulich@suse.com>
Subject: Re: [PATCH for-4.6 0/5] xen: arm: Parse PCI DT nodes' ranges and interrupt-map
Date: Tue, 17 Feb 2015 18:31:45 -0600	[thread overview]
Message-ID: <54E3DD71.6070001@amd.com> (raw)
In-Reply-To: <54E3C21A.6080909@amd.com>

On 2/17/2015 4:35 PM, Suravee Suthikulanit wrote:
> On 2/17/2015 7:50 AM, Andrew Cooper wrote:
>> On 17/02/15 13:43, Julien Grall wrote:
>>> (CC Jan and Andrew)
>>>
>>> Hi Suravee,
>>>
>>> On 17/02/15 03:04, Suravee Suthikulanit wrote:
>>>> By the way, looking at the output of "xl dmesg", I saw the following
>>>> message:
>>>>
>>>> (XEN) DOM0: PCI host bridge /smb/pcie@f0000000 ranges:
>>>> (XEN) DOM0:    IO 0xefff0000..0xefffffff -> 0x00000000
>>>> (XEN) DOM0:   MEM 0x40000000..0xbfffffff -> 0x40000000
>>>> (XEN) DOM0:   MEM 0x100000000..0x7fffffffff -> 0x100000000
>>>> (XEN) DOM0: pci-host-generic f0000000.pcie: PCI host bridge to bus
>>>> 0000:00
>>>> (XEN) DOM0: pci_bus 0000:00: root bus resource [bus 00-7f]
>>>> (XEN) DOM0: pci_bus 0000:00: root bus resource [io  0x0000-0xffff]
>>>> (XEN) DOM0: pci_bus 0000:00: root bus resource [mem
>>>> 0x40000000-0xbfffffff]
>>>> (XEN) DOM0: pci_bus 0000:00: root bus resource [mem
>>>> 0x100000000-0x7fffffffff]
>>>> (XEN) DOM0: pci 0000:00:00.0: of_irq_parse_pci() failed with rc=-19
>>>> (XEN) do_physdev_op 16 cmd=25: not implemented yet
>>>> (XEN) do_physdev_op 16 cmd=15: not implemented yet
>>>> (XEN) DOM0: pci 0000:00:00.0: Failed to add - passthrough or MSI/MSI-X
>>>> might fail!
>>>> (XEN) DOM0: pci 0000:00:02.0: of_irq_parse_pci() failed with rc=-19
>>>> (XEN) do_physdev_op 16 cmd=15: not implemented yet
>>>> (XEN) DOM0: pci 0000:00:02.0: Failed to add - passthrough or MSI/MSI-X
>>>> might fail!
>>>> (XEN) do_physdev_op 16 cmd=15: not implemented yet
>>>> (XEN) DOM0: pci 0000:00:02.1: Failed to add - passthrough or MSI/MSI-X
>>>> might fail!
>>>> (XEN) do_physdev_op 16 cmd=15: not implemented yet
>>>> (XEN) DOM0: pci 0000:01:00.0: Failed to add - passthrough or MSI/MSI-X
>>>> might fail!
>>>> (XEN) DOM0: pci 0000:01:00.1: of_irq_parse_pci() failed with rc=-22
>>>> (XEN) do_physdev_op 16 cmd=15: not implemented yet
>>>> (XEN) DOM0: pci 0000:01:00.1: Failed to add - passthrough or MSI/MSI-X
>>>> might fail!
>>>>
>>>> IIUC, This is because xen_add_device() failed, and it seems to be
>>>> related to some hyper call not implemented. Not sure what is "cmd=15".
>>>> Any ideas?
>>> There is 2 commands not implemented in the log:
>>>     * cmd 15: PHYSDEVOP_manage_pci_add
>>>     * cmd 25: PHYSDEVOP_pci_device_add
>>>
>>> Linux fallbacks on the former because the later is not implemented.
>>>
>>> AFAICT, PHYSDEVOP_manage_pci_add should not be implemented for ARM
>>> because it doesn't support segment. I suspect that it's kept for legacy
>>> on older Xen x86. Maybe Jan or Andrew have more input on this?
>>
>> It needs to be kept for backwards compatibility in x86.
>>
>> All new code should use PHYSDEVOP_pci_device_add.
>>
>> ~Andrew
>>
>
> Ok, now that I look at the arch/arm/physdev.c, I don't think the code
> for supporting any of the PHYSDEVOP_xxx is there.  That's probably why
> Xen complains. In contrast, arch/x86/physdev.c has most PHYSDEVOP_xxx
> already supported.
>
> My question is, are we supposed to be adding code to put the support in
> here?
>
> Thanks,
>
> Suravee.

My guess is yes, and that would mean we need to enable building 
drivers/pci.c when building arm code, which then open up a can of worms 
with re-factoring MSI support code from x86 and etc.

Suravee

  reply	other threads:[~2015-02-18  0:31 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-24  9:58 [PATCH for-4.6 0/5] xen: arm: Parse PCI DT nodes' ranges and interrupt-map Ian Campbell
2014-10-24  9:58 ` [PATCH 1/5] xen: arm: propagate gic's #address-cells property to dom0 Ian Campbell
2014-10-29 19:03   ` Julien Grall
2014-10-30 10:06     ` Ian Campbell
2014-10-30 10:31       ` Julien Grall
2014-11-04 10:23     ` Ian Campbell
2014-11-04 17:11       ` Konrad Rzeszutek Wilk
2014-11-05 10:47         ` Ian Campbell
2014-10-24  9:58 ` [PATCH 2/5] xen: device-tree: add accessors for the addr/size-cells of a node's children Ian Campbell
2014-10-24  9:58 ` [PATCH 3/5] xen: arm: Add DT_NR_GIC_INTERRUPT_CELLS rather than hardcoding 3 Ian Campbell
2014-10-24  9:58 ` [PATCH 4/5] xen: refactor irq_set_type out of platform_get_irq Ian Campbell
2014-10-24  9:58 ` [PATCH 5/5] xen: arm: handle PCI DT node ranges and interrupt-map properties Ian Campbell
2015-02-17 17:33   ` Julien Grall
2015-02-18 13:50     ` Ian Campbell
2015-02-18 14:19       ` Julien Grall
2015-02-18 14:37         ` Ian Campbell
2015-02-18 15:05           ` Julien Grall
2015-02-18 15:16             ` Julien Grall
2015-03-05 12:43               ` Ian Campbell
2015-03-05 15:59                 ` Julien Grall
2015-02-18 15:18             ` Ian Campbell
2015-02-18 15:31               ` Julien Grall
2015-02-18 15:44                 ` Ian Campbell
2015-02-18 15:13           ` Julien Grall
2015-02-18 15:21             ` Ian Campbell
2015-02-16  3:49 ` [PATCH for-4.6 0/5] xen: arm: Parse PCI DT nodes' ranges and interrupt-map Suravee Suthikulpanit
2015-02-16 10:12   ` Julien Grall
     [not found]     ` <54E2AFCC.3090302@amd.com>
2015-02-17 13:43       ` Julien Grall
2015-02-17 13:50         ` Andrew Cooper
2015-02-17 22:35           ` Suravee Suthikulanit
2015-02-18  0:31             ` Suravee Suthikulanit [this message]
2015-02-18  5:28               ` Suravee Suthikulanit
2015-02-18 12:48                 ` Julien Grall
2015-02-18 20:13                   ` Suravee Suthikulanit
2015-02-19  5:16                     ` Manish
2015-02-19  8:14                     ` Jan Beulich
2015-02-19  8:47                       ` Manish
2015-02-19 13:46                     ` Julien Grall
2015-02-18  7:58               ` Jan Beulich
2015-02-18 13:52   ` Ian Campbell

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=54E3DD71.6070001@amd.com \
    --to=suravee.suthikulpanit@amd.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=ian.campbell@citrix.com \
    --cc=jbeulich@suse.com \
    --cc=julien.grall@linaro.org \
    --cc=stefano.stabellini@citrix.com \
    --cc=xen-devel@lists.xen.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).