search for: init_hw_perf_events

...e: - boot bare metal kernel (that is, no xen hypervisor) - (re)boot dom0 with xen This results in the following kernel warning: [ 0.016036] ------------[ cut here ]------------ [ 0.016070] WARNING: at /build/buildd-linux_3.2.35-2-amd64-v9djlH/linux-3.2.35/arch/x86/xen/enlighten.c:738 init_hw_perf_events+0x246/0x3e1() [ 0.016107] Hardware name: MS-7368 [ 0.016135] Modules linked in: [ 0.016189] Pid: 1, comm: swapper/0 Not tainted 3.2.0-4-amd64 #1 Debian 3.2.35-2 [ 0.016224] Call Trace: [ 0.016257] [<ffffffff81046a75>] ? warn_slowpath_common+0x78/0x8c [ 0.016289]...

Hello! I'm having problems getting PCI pass-through to work. This is on a AMD64 system, paravirtualized with xen-hypervisor-4.0-amd64 4.0.0-1~experimental.1, dom0: linux-image-2.6.32-5-xen-amd64 2.6.32-12. From IRC, earlier today: <tschwinge> waldi: Aren't the Debian xen domU-capable kernels supposed to contain the PCI frontend (needed for PCI pass-through)? I'm getting:

Hello! I'm having problems getting PCI pass-through to work. This is on a AMD64 system, paravirtualized with xen-hypervisor-4.0-amd64 4.0.0-1~experimental.1, dom0: linux-image-2.6.32-5-xen-amd64 2.6.32-12. From IRC, earlier today: <tschwinge> waldi: Aren't the Debian xen domU-capable kernels supposed to contain the PCI frontend (needed for PCI pass-through)? I'm getting:

...0d7f00000 [ 0.005827] CPU: Physical Processor ID: 0 [ 0.005831] CPU: Processor Core ID: 0 [ 0.005836] mce: CPU supports 6 MCE banks [ 0.005855] Performance Events: AMD PMU driver. [ 0.005861] ------------[ cut here ]------------ [ 0.005870] WARNING: at arch/x86/xen/enlighten.c:729 init_hw_perf_events+0x337/0x3d7() [ 0.005875] Hardware name: H8DG6/H8DGi [ 0.005879] Modules linked in: [ 0.005885] Pid: 0, comm: swapper Not tainted 2.6.32.26 #7 [ 0.005890] Call Trace: [ 0.005898] [] ? warn_slowpath_common+0x76/0x8c [ 0.005905] [] ? init_hw_perf_events+0x337/0x3d7 [ 0.005912]...

...r Not tainted 2.6.32-5-xen-686 #1 [ 0.004000] Call Trace: [ 0.004000] [<c1037799>] ? warn_slowpath_common+0x5e/0x8a [ 0.004000] [<c10377cf>] ? warn_slowpath_null+0xa/0xc [ 0.004000] [<c1011cdc>] ? perf_events_lapic_init+0x28/0x29 [ 0.004000] [<c14073d9>] ? init_hw_perf_events+0x2dd/0x376 [ 0.004000] [<c140702c>] ? check_bugs+0x8/0xd8 [ 0.004000] [<c13ff808>] ? start_kernel+0x309/0x31d [ 0.004000] [<c1401410>] ? xen_start_kernel+0x564/0x56b [ 0.004000] [<c1409046>] ? mtrr_cleanup+0x341/0x3eb [ 0.004000] ---[ end trace a7919e7f17...

Hi, another issue I''m seeing with 3.0-rc2 and Xen is that there is an unexpectedly high amount of kernel reserved memory. I suspect that Linux allocates page table entries and corresponding data structures for the whole 6GB areas of the provided ''physical RAM map'' even though it has rather big unusable holes in it. [ 0.000000] BIOS-provided physical RAM map: [

Lots of changes since v2, too much to remember or summarize. Please ignore patch 11/11, it's just for my testing. Rich.

Hello, I tried out kernel 3.1.0-rc2 on my i386 Laptop with Xen 4.1.1. Booting hangs after these messages on the VGA console: pci 0000:02:09.0: address space collision: [mem 0x000da000-0x000dafff] conflicts with reserved [mem 0x0009f800-0x000fffff] reserve RAM buffer: 00000000 0009f000 - 00000000 0009ffff reserve RAM buffer: 00000000 38400000 - 00000000 3bffffff reserve RAM buffer: 00000001

Hello, I tried out kernel 3.1.0-rc2 on my i386 Laptop with Xen 4.1.1. Booting hangs after these messages on the VGA console: pci 0000:02:09.0: address space collision: [mem 0x000da000-0x000dafff] conflicts with reserved [mem 0x0009f800-0x000fffff] reserve RAM buffer: 00000000 0009f000 - 00000000 0009ffff reserve RAM buffer: 00000000 38400000 - 00000000 3bffffff reserve RAM buffer: 00000001