WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-ia64-devel

Re: [Xen-ia64-devel] Please try PV-on-HVM on IPF

  Hi Tristan,

  Thank you for your comment.

You (Tristan.Gingold) said:
>> [linux-2.6.16.29 on VT-i domain]
>> # cat /proc/iomem
>> 00000000-0009ffff : System RAM
>> 000a0000-000bffff : reserved
>> 000c0000-000fffff : reserved
>> 00100000-03ffffff : System RAM
>> 04000000-04bf3fff : System RAM
>>   04000000-046d34bf : Kernel code
>>   046d34c0-04bf373f : Kernel data
>> 04bf4000-3c458fff : System RAM
>>    **** deleted *****
>> 3ff70000-3fffdfff : System RAM
>> 3fffe000-3fffffff : reserved
>> c0000000-c1ffffff : 0000:00:02.0
>> c2000000-c2ffffff : 0000:00:03.0
>> c3000000-c3000fff : 0000:00:02.0
>> e0000000-e033dcf7 : PCI Bus 0000:00 I/O Ports 00000000-00000cf7
>> e0340d00-e3ffffff : PCI Bus 0000:00 I/O Ports 00000d00-0000ffff
>>
>> [RHEL4 U2 on VT-i domain]
>> # cat /proc/iomem
>> c0000000-c1ffffff : PCI Bus 0000:00
>>   c0000000-c1ffffff : 0000:00:02.0
>> c2000000-c2ffffff : 0000:00:03.0
>>   c2000000-c2000fff : PCI Bus 0000:00
>> c3000000-c3000fff : 0000:00:02.0
>>
>>   On RHEL4 U2 environment, I could show only this message. It's
>> strange, and it's the reason that xen-platform-pci.ko module can't
>> be attached, I think.
>>
>>   I don't understand what is happend. Does anyone know the reason ?
> I do not really understand what is strange for you.
> The output is not the same but:
> * it may be due to kernel version
> * the xen pseudo device appears in both version.

  I think that the diffence are noticed..

>> [linux-2.6.16.29 on VT-i domain]
>> c2000000-c2ffffff : 0000:00:03.0

>> [RHEL4 U2 on VT-i domain]
>> c2000000-c2ffffff : 0000:00:03.0
>>   c2000000-c2000fff : PCI Bus 0000:00

  On RHEL4 U2 kernel (Linux version 2.6.9-22.EL), xen-platform-pci
includes `PCI Bus 0000:00', but it should be the leaf node, I think.
To insmod xen-platform-pci, this iomem space was conflicted with
the inner device, thus it can't be attached.

> What is the error message when you try to insmod xen-platform-pci ?
> Have you ever succeed to insmod it in RHEL 4 ?

  I've never succeeded to insmod it in RHEL 4 original kernel.

  The error message is follows:

# insmod xen-platform-pci.ko
PCI: Enabling device 0000:00:03.0 (0010 -> 0013)
:MEM I/O resource 0xc2000000 @ 0x1000000 busy
xen-platform-pci: probe of 0000:00:03.0 failed with error -16

   This message is outputted from follow codes:

[unmodified_drivers/linux-2.6/platform-pci/platform-pci.c]   202
   181  static int __devinit platform_pci_init(struct pci_dev *pdev,
   182                                         const struct pci_device_id *ent)
   183  {
   184          int i, ret;
   185          long ioaddr, iolen;
   186          long mmio_addr, mmio_len;
   187
           .......
   202
   203          if (request_mem_region(mmio_addr, mmio_len, DRV_NAME) == NULL)
   204          {
   205                  printk(KERN_ERR ":MEM I/O resource 0x%lx @ 0x%lx 
busy\n",
   206                         mmio_addr, mmio_len);
   207                  return -EBUSY;
   208          }

  I've tried to insert checking code before request_mem_region()
to show the resource tree. So, I found the reason that it can't be
attaced.

- Tsunehisa Doi

_______________________________________________
Xen-ia64-devel mailing list
Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ia64-devel