[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: dmesg differences GENERIC/XEN3_DOM0
On Feb 27, 14:59, Greg%s1.lexort.com@localhost, "Troxel <gdt"@lexort.com wrote:
} Of course some differences are expected. But some seem surprising:
} -agp0 at pchb0: G4X-family chipset
} -agp0: detected 32252k stolen memory
} -agp0: aperture at 0xd0000000, size 0x10000000
} -i915drmkms0 at pci0 dev 2 function 0: Intel 82G45 Integrated Graphics Device (rev. 0x03)
} -Intel product 2e23 (miscellaneous display, revision 0x03) at pci0 dev 2 function 1 not configured
} +agp at pchb0 not configured
} +vga0 at pci0 dev 2 function 0: vendor 8086 product 2e22 (rev. 0x03)
} +wsdisplay0 at vga0 kbdmux 1: console (80x25, vt100 emulation)
} +wsmux1: connecting to wsdisplay0
} +drm at vga0 not configured
} +vendor 8086 product 2e23 (miscellaneous display, revision 0x03) at pci0 dev 2 function 1 not configured
} Also, even when things are found they print differently:
} -ahcisata0 at pci0 dev 31 function 2: Intel 82801JI SATA Controller (AHCI mode) (rev. 0x00)
} +ahcisata0 at pci0 dev 31 function 2: vendor 8086 product 3a22 (rev. 0x00)
} So, is it a goal that XEN3_DOM0 should in general aupport all drivers in
} GENERIC, in the sense that absent a good reason for DOM0 to differ, the
} same hardware is found? Or is there an articulated plan for
I suspect that in many cases, XEN3_DOM0 simply gets over looked.
} Perhaps put another way, if I were to fix this by making XEN3_DOM0 more
} like GENERIC, would that upset anyone?
The difference in the way things are printed is due to a
missing PCI_VERBOSE. In general, GENERIC and XEN3_DOM0 should be
as close as possible to being the same unless there is a specific
reason. Based on another comment in this thread, there was a reason
for leaving out agp0.
I suspect most Xen boxes are servers (possibly even headless)
so I'm not overly concerned about missing grahpics support (I know
there are some that will be). I'm more concerned about things like
missing SCSI HAs and missing NICs, which has happened. Fixing this
kind of problem (and maybe adding a comment to the top of GENERIC
to remind people) would be appreciated. I'm waffling on the idea
of resorting XEN3_DOM0 to make it easier to compare to GENERIC.
On one hand, it will make it easier to spot missing things (if
deliberate, there should be a comment). But, on the other hand,
it will be annoying for people with custom configs based on XEN3_DOM0.
Although, this would be a one time issue.
}-- End of excerpt from Greg%s1.lexort.com@localhost, "Troxel <gdt"@lexort.com
Main Index |
Thread Index |