search for: lguest_debug

...,4 +4,4 @@ obj-$(CONFIG_LGUEST_GUEST) += lguest.o l # Host requires the other files, which can be a module. obj-$(CONFIG_LGUEST) += lg.o lg-objs := core.o hypercalls.o page_tables.o interrupts_and_traps.o \ - segments.o io.o lguest_user.o hypervisor.o + segments.o io.o lguest_user.o hypervisor.o lguest_debug.o Index: linux-2.6.21-rc5-mm2/drivers/lguest/core.c =================================================================== --- linux-2.6.21-rc5-mm2.orig/drivers/lguest/core.c +++ linux-2.6.21-rc5-mm2/drivers/lguest/core.c @@ -210,6 +210,28 @@ int lguest_address_ok(const struct lgues } /* Just like...

...,4 +4,4 @@ obj-$(CONFIG_LGUEST_GUEST) += lguest.o l # Host requires the other files, which can be a module. obj-$(CONFIG_LGUEST) += lg.o lg-objs := core.o hypercalls.o page_tables.o interrupts_and_traps.o \ - segments.o io.o lguest_user.o hypervisor.o + segments.o io.o lguest_user.o hypervisor.o lguest_debug.o Index: linux-2.6.21-rc5-mm2/drivers/lguest/core.c =================================================================== --- linux-2.6.21-rc5-mm2.orig/drivers/lguest/core.c +++ linux-2.6.21-rc5-mm2/drivers/lguest/core.c @@ -210,6 +210,28 @@ int lguest_address_ok(const struct lgues } /* Just like...

...her the host or the guest. It incorporates kallsyms, and can do a nice back trace of a guest when it crashes. The guest needs kallsyms obviously compiled in. Note: This code needs to be fixed to be more secure! Implements a lgdebug_print that can be used within the host that will only print when lguest_debug is true. There's a hypercall that the guest can call to turn this on. There's also a function called lguest_set_debug(n) the makes it easy for the guest to turn it on. Where n=1 will turn on debugging prints, and n=0 will turn it off. (well n!=0 will turn it on). Signed-off-by: Steven Ro...

...her the host or the guest. It incorporates kallsyms, and can do a nice back trace of a guest when it crashes. The guest needs kallsyms obviously compiled in. Note: This code needs to be fixed to be more secure! Implements a lgdebug_print that can be used within the host that will only print when lguest_debug is true. There's a hypercall that the guest can call to turn this on. There's also a function called lguest_set_debug(n) the makes it easy for the guest to turn it on. Where n=1 will turn on debugging prints, and n=0 will turn it off. (well n!=0 will turn it on). Signed-off-by: Steven Ro...

...paravirt_ops replacement and the bus driver. +obj-$(CONFIG_LGUEST_GUEST) += lguest.o lguest_bus.o + +# Host requires the other files, which can be a module. +obj-$(CONFIG_LGUEST) += lg.o +lg-objs := core.o hypervisor.o lguest_user.o hv_vm.o page_tables.o \ +hypercalls.o io.o interrupts_and_traps.o lguest_debug.o + +# hypercalls.o page_tables.o interrupts_and_traps.o \ +# segments.o io.o lguest_user.o + +# We use top 4MB for guest traps page, then hypervisor. */ +HYPE_ADDR := (0xFFC00000+4096) +# The data is only 1k (256 interrupt handler pointers) +HYPE_DATA_SIZE := 1024 +CFLAGS += -DHYPE_ADDR="$(HY...

...paravirt_ops replacement and the bus driver. +obj-$(CONFIG_LGUEST_GUEST) += lguest.o lguest_bus.o + +# Host requires the other files, which can be a module. +obj-$(CONFIG_LGUEST) += lg.o +lg-objs := core.o hypervisor.o lguest_user.o hv_vm.o page_tables.o \ +hypercalls.o io.o interrupts_and_traps.o lguest_debug.o + +# hypercalls.o page_tables.o interrupts_and_traps.o \ +# segments.o io.o lguest_user.o + +# We use top 4MB for guest traps page, then hypervisor. */ +HYPE_ADDR := (0xFFC00000+4096) +# The data is only 1k (256 interrupt handler pointers) +HYPE_DATA_SIZE := 1024 +CFLAGS += -DHYPE_ADDR="$(HY...

...2345, you will get 54321 out of the serial. It's just easier that way (code wise). The macros with a 'S_' prefix will store the regs used on the stack, but that's not always good, since most of the hypervisor code, does not have a usable stack. Page tables. There's functions in lguest_debug.c that allows for dumping out either the guest page tables, or host page tables. kill_guest(linfo) - is just like i386 kill_guest and takes the lguest_guest_info pointer as input. kill_guest_dump(vcpu) - when possible, use the vcpu version, since this will also dump to host printk, the regs of th...

...2345, you will get 54321 out of the serial. It's just easier that way (code wise). The macros with a 'S_' prefix will store the regs used on the stack, but that's not always good, since most of the hypervisor code, does not have a usable stack. Page tables. There's functions in lguest_debug.c that allows for dumping out either the guest page tables, or host page tables. kill_guest(linfo) - is just like i386 kill_guest and takes the lguest_guest_info pointer as input. kill_guest_dump(vcpu) - when possible, use the vcpu version, since this will also dump to host printk, the regs of th...