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

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



Le Mardi 17 Octobre 2006 14:30, Doi.Tsunehisa@xxxxxxxxxxxxxx a Ãcrit :
> Hi all,
>
> I (Doi.Tsunehisa) said:
[...]
>   Today, I was testing my preliminary patch on RHEL4 U2.
>
>   But, xen-platform-pci.ko could not be attached with RHEL4 U2 original
> kernel. Thus I was investigating it. So, I found a strange movement about
> PCI configuration.
>
>   I tested on two envrionments, linux-2.6.16.29  and RHEL4 U2 original.
> Outputs of lspci command are same on both environment.
>
>    The output is follow:
>
> [Both environment of VT-i domain]
> # lspci -v
> 00:00.0 Host bridge: Intel Corporation 440FX - 82441FX PMC [Natoma] (rev
> 02) Flags: fast devsel
>
> 00:01.0 ISA bridge: Intel Corporation 82371SB PIIX3 ISA [Natoma/Triton II]
>         Flags: medium devsel
>
> 00:01.1 IDE interface: Intel Corporation 82371SB PIIX3 IDE [Natoma/Triton
> II] (prog-if 80 [Master]) Flags: bus master, fast devsel, latency 0
>         I/O ports at 1100 [size=16]
>
> 00:02.0 VGA compatible controller: Cirrus Logic GD 5446 (prog-if 00 [VGA])
>         Flags: bus master, fast devsel, latency 0
>         Memory at 00000000c0000000 (32-bit, prefetchable) [size=32M]
>         Memory at 00000000c3000000 (32-bit, non-prefetchable) [size=4K]
>
> 00:03.0 Class ff80: Unknown device 5853:0001 (rev 01)
>         Flags: fast devsel
>         I/O ports at 1000 [disabled] [size=256]
>         Memory at 00000000c2000000 (32-bit, prefetchable) [disabled]
> [size=16M]
>
>   There is `Unknown device' in thie message. It's pyseudo-device for
> PV-on-HVM called `xen-platform-pci'.
>
>   Next, I showed IO-memory maps with /proc/iomem. But, IO-memory maps
> are different on both environment.
>
> [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.

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

Tristan.

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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.