Commit 5780888b authored Jun 18, 2009 by Matias Zabaljauregui Committed by Rusty Russell Jul 17, 2009

lguest: fix journey



fix: "make Guest" was complaining about duplicated G:032

Signed-off-by: Matias Zabaljauregui <zabaljauregui@gmail.com>
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>

parent 4b0a8404

arch/x86/include/asm/lguest_hcall.h

+1 −1

Original line number	Diff line number	Diff line
		@@ -30,7 +30,7 @@
		#include <asm/hw_irq.h>
		#include <asm/kvm_para.h>

		/*G:031 But first, how does our Guest contact the Host to ask for privileged
		/*G:030 But first, how does our Guest contact the Host to ask for privileged
		* operations? There are two ways: the direct way is to make a "hypercall",
		* to make requests of the Host Itself.
		*

arch/x86/lguest/boot.c

+1 −1

Original line number	Diff line number	Diff line
		@@ -1079,7 +1079,7 @@ static unsigned lguest_patch(u8 type, u16 clobber, void *ibuf,
		return insn_len;
		}

		/*G:030 Once we get to lguest_init(), we know we're a Guest. The various
		/*G:029 Once we get to lguest_init(), we know we're a Guest. The various
		* pv_ops structures in the kernel provide points for (almost) every routine we
		* have to override to avoid privileged instructions. */
		__init void lguest_init(void)

include/linux/lguest.h

+1 −1

Original line number	Diff line number	Diff line
		@@ -11,7 +11,7 @@
		#define LG_CLOCK_MIN_DELTA 100UL
		#define LG_CLOCK_MAX_DELTA ULONG_MAX

		/*G:032 The second method of communicating with the Host is to via "struct
		/*G:031 The second method of communicating with the Host is to via "struct
		* lguest_data". Once the Guest's initialization hypercall tells the Host where
		* this is, the Guest and Host both publish information in it. :*/
		struct lguest_data