Re: [RFC] pciehp: Add archdata setting

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Hi, Kaneshige

You are right!
Setting dma_ops in pcibios_enable_device is a nice way.
In PCI driver, pci_enable_device_xxx that calls pcibios_enable_device is called before checking archdata.dma_ops.

I added code of checking and setting dma_ops to pcibios_enable_device in
It works good.

I will send this code to arch/powerpc guys.
Thanks for your great proposal.


Hiroo Matsumoto

Hi, Bjorn and Kaneshige

Thanks for your comments and proposal.
I will rethink a way of setting archdata with pcibios_xxx() hook or bus notifier.



I'm trying to use pciehp on powerpc platform.
I set e1000e card to PCI Express bridge that has PCI Express HotPlug

There is problem when poweron PCI Express HotPlug slot with pciehp.
e1000e driver needs dma_ops in struct dev_archdata, but archdata isn't
set (dma_ops is NULL) when probe from pciehp.
Then e1000e driver returns error as below.

-sh-3.2# echo 1>  /sys/bus/pci/slots/1/power
[   65.493662] pci 0000:03:00.0: BAR 2: set to [io
0xff7ee000-0xff7ee01f] (PCI address [0x1000-0x101f])
[   65.502890] pcieport 0000:02:01.0: PCI bridge to [bus 03-03]
[   65.508555] pcieport 0000:02:01.0:   bridge window [io
[   65.515785] pcieport 0000:02:01.0:   bridge window [mem
[   65.523015] pcieport 0000:02:01.0:   bridge window [mem
0xa0200000-0xa02fffff 64bit pref]
[   65.531238] pci 0000:03:00.0: no hotplug settings from platform
[   65.538361] e1000e 0000:03:00.0: Disabling ASPM  L1
[   65.543616] e1000e 0000:03:00.0: enabling device (0000 ->  0002)
[ 65.549876] e1000e 0000:03:00.0: No usable DMA configuration, aborting
[   65.557194] e1000e: probe of 0000:03:00.0 failed with error -5
-sh-3.2# lspci
0000:03:00.0 Ethernet controller: Intel Corporation 82572EI Gigabit
Ethernet Controller (Copper) (rev 06)
-sh-3.2# ifconfig -a
<snip>    // There is no network interface for 82572EI

If archdata.dma_ops is NULL on x86 platform, e1000e will get dma_ops
without archdata.
So e1000e driver doesn't return error.

I think that archdata should be set before driver probe (e.g pciehp).
I tried to fix it (pciehp-add-archdata.patch), but I'm not good at PCI
driver..., so please give better way.

Interesting.  It would be nice if we could set archdata the same way
for both devices present at boot and those hot-added later.

Yes. But it might be not so easy...

                                                             Can you
figure out where archdata is set for devices present at boot?

I read some x86 and powerpc code to setup archdata. x86 and powerpc
have different way to setup archdata. And it seems archdata is not
set in one location, each member in the archdata is setup in the
different locations.

On x86, archdata.dma_ops is set in the pci_iommu_init() code path, which
is called through rootfs_initcall(). On powerpc, archdata.dma_ops is set
in pcibios_fixup_bus() code path.

Here are my notes.

x86 (calgary iommu)
 => pci_iommu_init()
     => x86_init.iommu.iommu_init() (== calgary_iommu_init())
         => calgary_init()

        for_each_pci_dev() {
                        dev->dev.archdata.dma_ops = &calgary_dma_ops;

x86 (amd iommu)
 => pci_iommu_init()
     => x86_init.iommu.iommu_init() (== amd_iommu_init())
         => amd_iommu_init_dma_ops()
             => device_dma_ops_init()

    for_each_pci_dev() {
        pdev->dev.archdata.dma_ops = &amd_iommu_dma_ops;

 => pcibios_fixup_bus()
     => pcibios_setup_bus_devices()
=> set_dma_ops() # for each device on the bus (default) => ppc_md.pci_dma_dev_setup() # for each device on the bus (machine depend)

static inline void set_dma_ops(struct device *dev, struct dma_map_ops *ops)
        dev->archdata.dma_ops = ops;

One possible idea is that to setup archdata in the pcibios_xxx() hook.
(for example, use existing pcibios_enable_device(), or provide new
hook like pcibios_setup_device() which is called by pci_setup_device).

Another idea is that to add support for hot-plug to each iommu (dma)
code. Maybe it can be implemented by using bus notifier.

Kenji Kaneshige

To unsubscribe from this list: send the line "unsubscribe linux-pci" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at

[Home]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Photo]     [Yosemite News]    [Yosemite Photos]    [Free Online Dating]     [Linux Kernel]     [Linux SCSI]     [XFree86]

Add to Google Powered by Linux