kernel-ark/drivers/lguest
Rusty Russell 2d37f94a28 generalize lgread_u32/lgwrite_u32.
Jes complains that page table code still uses lgread_u32 even though
it now uses general kernel pte types.  The best thing to do is to
generalize lgread_u32 and lgwrite_u32.

This means we lose the efficiency of getuser().  We could potentially
regain it if we used __copy_from_user instead of copy_from_user, but
I'm not certain that our range check is equivalent to access_ok() on
all platforms.

Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
Acked-by: Jes Sorensen <jes@sgi.com>
2007-10-23 15:49:56 +10:00
..
x86 generalize lgread_u32/lgwrite_u32. 2007-10-23 15:49:56 +10:00
core.c generalize lgread_u32/lgwrite_u32. 2007-10-23 15:49:56 +10:00
hypercalls.c generalize lgread_u32/lgwrite_u32. 2007-10-23 15:49:56 +10:00
interrupts_and_traps.c generalize lgread_u32/lgwrite_u32. 2007-10-23 15:49:56 +10:00
Kconfig Remove old lguest bus and drivers. 2007-10-23 15:49:55 +10:00
lg.h generalize lgread_u32/lgwrite_u32. 2007-10-23 15:49:56 +10:00
lguest_device.c Lguest support for Virtio 2007-10-23 15:49:56 +10:00
lguest_user.c Remove old lguest I/O infrrasructure. 2007-10-23 15:49:55 +10:00
Makefile Lguest support for Virtio 2007-10-23 15:49:56 +10:00
page_tables.c generalize lgread_u32/lgwrite_u32. 2007-10-23 15:49:56 +10:00
README
segments.c generalize lgread_u32/lgwrite_u32. 2007-10-23 15:49:56 +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.