search for: kill_guest_dump

Displaying 4 results from an estimated 4 matches for "kill_guest_dump".

2007 Apr 18
1
[RFC/PATCH LGUEST X86_64 03/13] lguest64 core
...+int lguest_address_ok(const struct lguest_guest_info *linfo, u64 addr) +{ + return addr / PAGE_SIZE < linfo->pfn_limit; +} + +u8 lhread_u8(struct lguest_vcpu *vcpu, u64 addr) +{ + u8 val = 0; + + if (!lguest_address_ok(vcpu->guest, addr) + || get_user(val, (u8 __user *)addr) != 0) + kill_guest_dump(vcpu, "bad read address %llx", addr); + return val; +} + +u16 lhread_u16(struct lguest_vcpu *vcpu, u64 addr) +{ + u16 val = 0; + + if (!lguest_address_ok(vcpu->guest, addr) + || get_user(val, (u16 __user *)addr) != 0) + kill_guest_dump(vcpu, "bad read address %llx", add...
2007 Apr 18
1
[RFC/PATCH LGUEST X86_64 03/13] lguest64 core
...+int lguest_address_ok(const struct lguest_guest_info *linfo, u64 addr) +{ + return addr / PAGE_SIZE < linfo->pfn_limit; +} + +u8 lhread_u8(struct lguest_vcpu *vcpu, u64 addr) +{ + u8 val = 0; + + if (!lguest_address_ok(vcpu->guest, addr) + || get_user(val, (u8 __user *)addr) != 0) + kill_guest_dump(vcpu, "bad read address %llx", addr); + return val; +} + +u16 lhread_u16(struct lguest_vcpu *vcpu, u64 addr) +{ + u16 val = 0; + + if (!lguest_address_ok(vcpu->guest, addr) + || get_user(val, (u16 __user *)addr) != 0) + kill_guest_dump(vcpu, "bad read address %llx", add...
2007 Apr 18
1
[RFC/PATCH LGUEST X86_64 00/13] Lguest for the x86_64
...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 the guest as well as a guest back trace. Which can be really usefull. Well that's it! We currently get to just before console_init in init/main.c of the guest before we take an timer interrupt...
2007 Apr 18
1
[RFC/PATCH LGUEST X86_64 00/13] Lguest for the x86_64
...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 the guest as well as a guest back trace. Which can be really usefull. Well that's it! We currently get to just before console_init in init/main.c of the guest before we take an timer interrupt...