BMC/Intel-BMC/linux.git/drivers/lguest/core.c, branch dev-4.3

lguest: fix out-by-one error in address checking.

2015-05-27T16:57:21+00:00

This bug has been there since day 1; addresses in the top guest physical page weren't considered valid. You could map that page (the check in check_gpte() is correct), but if a guest tried to put a pagetable there we'd check that address manually when walking it, and kill the guest. Signed-off-by: Rusty Russell Cc: stable@kernel.org Signed-off-by: Linus Torvalds

lguest: remove NOTIFY call and eventfd facility.

2015-02-11T06:17:46+00:00

Disappointing, as this was kind of neat (especially getting to use RCU to manage the address -> eventfd mapping). But now the devices are PCI handled in userspace, we get rid of both the NOTIFY hypercall and the interface to connect an eventfd. Signed-off-by: Rusty Russell

lguest: write more information to userspace about pending traps.

2015-02-11T06:17:30+00:00

This is preparation for userspace handling MMIO and ioport accesses. Signed-off-by: Rusty Russell

lguest: add operations to get/set a register from the Launcher.

2015-02-11T06:17:29+00:00

We use the ptrace API struct, and we currently don't let them set anything but the normal registers (we'd have to filter the others). Signed-off-by: Rusty Russell

mm/vmalloc.c: clean up map_vm_area third argument

2014-08-07T01:01:19+00:00

Currently map_vm_area() takes (struct page *** pages) as third argument, and after mapping, it moves (*pages) to point to (*pages + nr_mappped_pages). It looks like this kind of increment is useless to its caller these days. The callers don't care about the increments and actually they're trying to avoid this by passing another copy to map_vm_area(). The caller can always guarantee all the pages can be mapped into vm_area as specified in first argument and the caller only cares about whether map_vm_area() fails or not. This patch cleans up the pointer movement in map_vm_area() and updates its callers accordingly. Signed-off-by: WANG Chao Cc: Zhang Yanfei Acked-by: Greg Kroah-Hartman Cc: Minchan Kim Cc: Nitin Gupta Cc: Rusty Russell Signed-off-by: Andrew Morton Signed-off-by: Linus Torvalds

lguest: map Switcher below fixmap.

2013-04-22T06:15:03+00:00

Now we've adjusted all the code, we can simply set switcher_addr to wherever it needs to go below the fixmaps, rather than asserting that it should be so. With large NR_CPUS and PAE, people were hitting the "mapping switcher would thwack fixmap" message. Reported-by: Paul Bolle Signed-off-by: Rusty Russell

lguest: don't share Switcher PTE pages between guests.

2013-04-22T06:15:01+00:00

We currently use the whole top PGD entry for the switcher, so we simply share a fixed page of PTEs between all guests (actually, it's one per Host CPU, to ensure isolation between guests). Changes to a scheme where every guest has its own mappings. Signed-off-by: Rusty Russell

lguest: expost switcher_pages array (as lg_switcher_pages).

2013-04-22T06:15:00+00:00

We will need this in page_table.c soon. Signed-off-by: Rusty Russell

lguest: assume Switcher text is a single page.

2013-04-22T06:01:36+00:00

ie. SHARED_SWITCHER_PAGES == 1. It is well under a page, and it's a minor simplification: it's nice to have *one* simplification in a patch series! Signed-off-by: Rusty Russell

lguest: rename switcher_page to switcher_pages.

2013-04-22T06:01:35+00:00

There is a single page with the Switcher in it, but it's followed by 2 pages per Host CPU. Signed-off-by: Rusty Russell