search for: register_keyhandler

...gned-off-by: Jan Beulich <jbeulich@suse.com> --- a/xen/arch/x86/hvm/svm/vmcb.c +++ b/xen/arch/x86/hvm/svm/vmcb.c @@ -310,7 +310,7 @@ static struct keyhandler vmcb_dump_keyha .desc = "dump AMD-V VMCBs" }; -void setup_vmcb_dump(void) +void __init setup_vmcb_dump(void) { register_keyhandler(''v'', &vmcb_dump_keyhandler); } --- a/xen/arch/x86/hvm/vmx/vmcs.c +++ b/xen/arch/x86/hvm/vmx/vmcs.c @@ -1492,7 +1492,7 @@ static struct keyhandler vmcs_dump_keyha .desc = "dump Intel''s VMCS" }; -void setup_vmcs_dump(void) +void __init setup_vmcs_dump...

.... */ #define switch_code (opt_conswitch[0]-''a''+1) static int __read_mostly xen_rx = 1; /* FALSE => serial input passed to domain 0. */ @@ -661,6 +704,8 @@ void __init console_endboot(void) if ( opt_conswitch[1] == ''x'' ) xen_rx = !xen_rx; + register_keyhandler(''w'', &dump_console_ring_keyhandler); + /* Serial input is directed to DOM0 by default. */ switch_serial_input(); }

...truct keyhandler dump_gic_keyhandler = { + .irq_callback = 0, + .u.fn = do_dump_gic, + .desc = "dump GIC state" +}; + /* Set up the GIC */ void __init gic_init(void) { @@ -460,6 +532,9 @@ void __init gic_init(void) gic_hyp_init(); spin_unlock(&gic.lock); + + register_keyhandler(''G'', &dump_gic_keyhandler); + } void send_SGI_mask(const cpumask_t *cpumask, enum gic_sgi sgi) @@ -913,7 +988,7 @@ static void maintenance_interrupt(int irq, void *dev_id, struct cpu_user_regs *r } } -void gic_dump_info(struct vcpu *v) +void gic_dump_info_guest(str...

This series consists of improvements to Xen''s ability to print traces of its own stack, and specifically for the stack overflow case to be able to use frame pointers in a debug build. I have dev tested the series in debug and non-debug cases, with and without memory guards, and I believe that all the stack traces look correct. However, I would greatly appreciate a second opinion on the

This series consists of improvements to Xen''s ability to print traces of its own stack, and specifically for the stack overflow case to be able to use frame pointers in a debug build. I have dev tested the series in debug and non-debug cases, with and without memory guards, and I believe that all the stack traces look correct (given the available information Xen has), and that the

...ap[i][j][k]) ) + { + total = count_bucket(&heap[i][j][k], k); + printk("heap[%d][%d][%d]-> %lu pages\n", + i, j, k, total); + } +} + +static __init int register_heap_trigger(void) +{ + register_keyhandler(''H'', dump_heap, "dump heap info"); + return 0; +} +__initcall(register_heap_trigger); + static __init int page_scrub_init(void) { diff -r e87b07e5fddd xen/include/xen/mm.h --- a/xen/include/xen/mm.h Tue Aug 15 11:36:36 2006 -0500 +++ b/xen/include/xen/mm.h Tue Aug...

...0; +} + void __init init_8259A(int auto_eoi) { unsigned long flags; diff -r 3ef0510e44d0 xen/arch/x86/io_apic.c --- a/xen/arch/x86/io_apic.c Tue May 08 10:21:23 2007 +0100 +++ b/xen/arch/x86/io_apic.c Mon May 14 15:09:20 2007 -0400 @@ -1793,6 +1793,78 @@ void __init setup_IO_APIC(void) register_keyhandler(''z'', print_IO_APIC_keyhandler, "print ioapic info"); } +struct IO_APIC_route_entry *ioapic_pm_state=NULL; + +void ioapic_pm_state_alloc(void) +{ + int i, nr_entry=0; + + if (ioapic_pm_state!=NULL) + return; + + for (i=0; i<nr_ioapics; i++) +...

I''m afraid this series is rather a grab bag and it is distressingly large at this stage. With this series I can boot an Xgene board until it fails to find its SATA controller. This is a dom0 issue for which patches are pending from APM (/me nudges Anup). As well as the APM specific platform stuff there are also some generic improvements which were either necessary or useful during this