android_kernel_xiaomi_sdm845/drivers/lguest
Rusty Russell 47436aa4ad Boot with virtual == physical to get closer to native Linux.
1) This allows us to get alot closer to booting bzImages.

2) It means we don't have to know page_offset.

3) The Guest needs to modify the boot pagetables to create the
   PAGE_OFFSET mapping before jumping to C code.

4) guest_pa() walks the page tables rather than using page_offset.

5) We don't use page_offset to figure out whether to emulate: it was
   always kinda quesationable, and won't work for instructions done
   before remapping (bzImage unpacking in particular).

6) We still want the kernel address for tlb flushing: have the initial
   hypercall give us that, too.

Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2007-10-23 15:49:54 +10:00
..
x86 Boot with virtual == physical to get closer to native Linux. 2007-10-23 15:49:54 +10:00
core.c Allow guest to specify syscall vector to use. 2007-10-23 15:49:53 +10:00
hypercalls.c Boot with virtual == physical to get closer to native Linux. 2007-10-23 15:49:54 +10:00
interrupts_and_traps.c Boot with virtual == physical to get closer to native Linux. 2007-10-23 15:49:54 +10:00
io.c Remove fixed limit on number of guests, and lguests array. 2007-10-23 15:49:51 +10:00
Kconfig Lguest currently depends on 32-bit x86, not just x86. 2007-10-23 15:49:48 +10:00
lg.h Boot with virtual == physical to get closer to native Linux. 2007-10-23 15:49:54 +10:00
lguest_bus.c lguest_devices belongs in lguest_bus.c: it's not i386-specific. 2007-10-23 15:49:49 +10:00
lguest_user.c Boot with virtual == physical to get closer to native Linux. 2007-10-23 15:49:54 +10:00
Makefile Move i386 part of core.c to x86/core.c. 2007-10-23 15:49:51 +10:00
page_tables.c Boot with virtual == physical to get closer to native Linux. 2007-10-23 15:49:54 +10:00
README lguest: documentation I: Preparation 2007-07-26 11:35:16 -07:00
segments.c Move i386 part of core.c to x86/core.c. 2007-10-23 15:49:51 +10:00

Welcome, friend reader, to lguest.

Lguest is an adventure, with you, the reader, as Hero.  I can't think of many
5000-line projects which offer both such capability and glimpses of future
potential; it is an exciting time to be delving into the source!

But be warned; this is an arduous journey of several hours or more!  And as we
know, all true Heroes are driven by a Noble Goal.  Thus I offer a Beer (or
equivalent) to anyone I meet who has completed this documentation.

So get comfortable and keep your wits about you (both quick and humorous).
Along your way to the Noble Goal, you will also gain masterly insight into
lguest, and hypervisors and x86 virtualization in general.

Our Quest is in seven parts: (best read with C highlighting turned on)

I) Preparation
	- In which our potential hero is flown quickly over the landscape for a
	  taste of its scope.  Suitable for the armchair coders and other such
	  persons of faint constitution.

II) Guest
	- Where we encounter the first tantalising wisps of code, and come to
	  understand the details of the life of a Guest kernel.

III) Drivers
	- Whereby the Guest finds its voice and become useful, and our
	  understanding of the Guest is completed.

IV) Launcher
	- Where we trace back to the creation of the Guest, and thus begin our
	  understanding of the Host.

V) Host
	- Where we master the Host code, through a long and tortuous journey.
	  Indeed, it is here that our hero is tested in the Bit of Despair.

VI) Switcher
	- Where our understanding of the intertwined nature of Guests and Hosts
	  is completed.

VII) Mastery
	- Where our fully fledged hero grapples with the Great Question:
	  "What next?"

make Preparation!
Rusty Russell.