search for: lgue

...isn't there (thanks to Tony Breeds <tony@bakeyournoodle.com>). 3) Point out that guest and host kernel are usually the same. 4) Set the "no checksum" option on the tun device as a minor optimization. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> --- Documentation/lguest/Makefile | 9 ++++++++- Documentation/lguest/lguest.c | 6 ++++-- Documentation/lguest/lguest.txt | 8 ++++++-- 3 files changed, 18 insertions(+), 5 deletions(-) =================================================================== --- a/Documentation/lguest/Makefile +++ b/Documentati...

...isn't there (thanks to Tony Breeds <tony@bakeyournoodle.com>). 3) Point out that guest and host kernel are usually the same. 4) Set the "no checksum" option on the tun device as a minor optimization. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> --- Documentation/lguest/Makefile | 9 ++++++++- Documentation/lguest/lguest.c | 6 ++++-- Documentation/lguest/lguest.txt | 8 ++++++-- 3 files changed, 18 insertions(+), 5 deletions(-) =================================================================== --- a/Documentation/lguest/Makefile +++ b/Documentati...

We don't actually need the Guest handlers mapped to avoid double fault, just the stack pages. Thanks to Zach for confirming. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> --- drivers/lguest/interrupts_and_traps.c | 26 +------------------------- drivers/lguest/lg.h | 2 +- drivers/lguest/page_tables.c | 6 +++--- 3 files changed, 5 insertions(+), 29 deletions(-) =================================================================== --- a/drivers/lgue...

We don't actually need the Guest handlers mapped to avoid double fault, just the stack pages. Thanks to Zach for confirming. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> --- drivers/lguest/interrupts_and_traps.c | 26 +------------------------- drivers/lguest/lg.h | 2 +- drivers/lguest/page_tables.c | 6 +++--- 3 files changed, 5 insertions(+), 29 deletions(-) =================================================================== --- a/drivers/lgue...

Hi all, Lguest is a simple hypervisor which runs Linux under Linux, without needing VT hardware. Two people asked if I had a version of lguest which worked on other-than-bleeding-edge-mm kernels, so I did a backport of the latest version to 2.6.21. http://lguest.ozlabs.org/lguest-2.6.21-254.patch.gz See Do...

Hi all, Lguest is a simple hypervisor which runs Linux under Linux, without needing VT hardware. Two people asked if I had a version of lguest which worked on other-than-bleeding-edge-mm kernels, so I did a backport of the latest version to 2.6.21. http://lguest.ozlabs.org/lguest-2.6.21-254.patch.gz See Do...

[ Ingo, Thomas cc'd in case this issue effects normal jiffies clock too? ] When the Host TSC is unreliable or can change, lguest guests use the jiffies clock. However, the clock value seems to creep upwards in sub-jiffies increments, and then tick_handle_periodic() goes into an infinite loop. Instead, the host writes the current time into the lguest page on every interrupt. This doesn't cost much but is more precise...

[ Ingo, Thomas cc'd in case this issue effects normal jiffies clock too? ] When the Host TSC is unreliable or can change, lguest guests use the jiffies clock. However, the clock value seems to creep upwards in sub-jiffies increments, and then tick_handle_periodic() goes into an infinite loop. Instead, the host writes the current time into the lguest page on every interrupt. This doesn't cost much but is more precise...

Lguest currently requires a TSC, which breaks older machines and Matt Mackall who boots the host with "notsc". In addition, there is no good solution to changing TSC speeds (informing all the guests about the TSC impending change before it happens would be a great deal of code and have issues...

Lguest currently requires a TSC, which breaks older machines and Matt Mackall who boots the host with "notsc". In addition, there is no good solution to changing TSC speeds (informing all the guests about the TSC impending change before it happens would be a great deal of code and have issues...

...her slightly more robust in the case of any other bugs which cause it to fault. We kill the Guest if it causes a fault in the Switcher, so it has to make sure it's not using segments when it changes them. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> diff -r 55fdd7fa62b7 drivers/lguest/core.c --- a/drivers/lguest/core.c Mon Aug 06 16:38:47 2007 +1000 +++ b/drivers/lguest/core.c Wed Aug 08 13:24:59 2007 +1000 @@ -452,6 +452,11 @@ static void run_guest_once(struct lguest /* Copy the guest-specific information into this CPU's "struct * lguest_pages". */ copy_i...

...her slightly more robust in the case of any other bugs which cause it to fault. We kill the Guest if it causes a fault in the Switcher, so it has to make sure it's not using segments when it changes them. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> diff -r 55fdd7fa62b7 drivers/lguest/core.c --- a/drivers/lguest/core.c Mon Aug 06 16:38:47 2007 +1000 +++ b/drivers/lguest/core.c Wed Aug 08 13:24:59 2007 +1000 @@ -452,6 +452,11 @@ static void run_guest_once(struct lguest /* Copy the guest-specific information into this CPU's "struct * lguest_pages". */ copy_i...

Christoph Hellwig said runs sparse: 1) page_tables.c unnecessary initialization 2) Change prototype of run_lguest and do cast in caller instead (when we add __user to cast, it runs over another line). Al Viro pointed out the ugly cast in push_lguest_stack(): 3) Stick with unsigned long for arg, removes 4 casts in total. Most importantly, I now realize that Christoph's incorrect ranting about lgread_u...

Christoph Hellwig said runs sparse: 1) page_tables.c unnecessary initialization 2) Change prototype of run_lguest and do cast in caller instead (when we add __user to cast, it runs over another line). Al Viro pointed out the ugly cast in push_lguest_stack(): 3) Stick with unsigned long for arg, removes 4 casts in total. Most importantly, I now realize that Christoph's incorrect ranting about lgread_u...

This is taken from the work I did on lguest64. When killing a guest, we read the guest stack to do a nice back trace of the guest and send it via printk to the host. So instead of just getting an error message from the lguest launcher of: lguest: bad read address 537012178 len 1 I also get in my dmesg: called from [<c0405f30>]...

This is taken from the work I did on lguest64. When killing a guest, we read the guest stack to do a nice back trace of the guest and send it via printk to the host. So instead of just getting an error message from the lguest launcher of: lguest: bad read address 537012178 len 1 I also get in my dmesg: called from [<c0405f30>]...

...ches I'm planning to submit for 2.6.24. Comments gratefully accepted. Along with the usual cleanups and improvements are Jes' de-i386-ification patches, and a new "virtio" mechanism designed to be shared with KVM (and hopefully other hypervisors). Cheers, Rusty. Documentation/lguest/Makefile | 30 Documentation/lguest/lguest.c | 1745 ++++++++++++----------- Documentation/lguest/lguest.txt | 67 a/drivers/block/lguest_blk.c | 423 ----- a/drivers/char/hvc_lguest.c | 177 --...

...ches I'm planning to submit for 2.6.24. Comments gratefully accepted. Along with the usual cleanups and improvements are Jes' de-i386-ification patches, and a new "virtio" mechanism designed to be shared with KVM (and hopefully other hypervisors). Cheers, Rusty. Documentation/lguest/Makefile | 30 Documentation/lguest/lguest.c | 1745 ++++++++++++----------- Documentation/lguest/lguest.txt | 67 a/drivers/block/lguest_blk.c | 423 ----- a/drivers/char/hvc_lguest.c | 177 --...