view buildconfigs/src.tarball @ 23319:ff523faf2be1

x86/mm: fix mod_l1_entry() return value when encountering r/o MMIO page

While putting together the workaround announced in
http://lists.xen.org/archives/html/xen-devel/2012-06/msg00709.html, I
found that mod_l1_entry(), upon encountering a set bit in
mmio_ro_ranges, would return 1 instead of 0 (the removal of the write
permission is supposed to be entirely transparent to the caller, even
more so to the calling guest).

Signed-off-by: Jan Beulich <jbeulich@suse.com>
Acked-by: Keir Fraser <keir@xen.org>
xen-unstable changeset: 25487:baa85434d0ec
xen-unstable date: Thu Jun 21 11:30:59 2012 +0200
author Jan Beulich <jbeulich@novell.com>
date Mon Jul 09 10:30:16 2012 +0100 (2012-07-09)
parents d6889b3b6423
line source
1 XEN_LINUX_MIRROR ?= http://www.kernel.org/pub/linux/kernel/v2.6/
2 XEN_LINUX_TARBALL ?= linux-$(LINUX_VER)-xen.tar.bz2
6 KETCHUP ?= python buildconfigs/ketchup
8 vpath linux-%.tar.bz2 $(LINUX_SRC_PATH)
10 # download a pristine Linux kernel tarball if there isn't one in LINUX_SRC_PATH
11 linux-%.tar.bz2:
12 @echo "Cannot find $@ in path $(LINUX_SRC_PATH)"
13 false wget $(XEN_LINUX_MIRROR)/$@ -O./$@
15 # XXX create a pristine tree for diff -Nurp convenience
17 %/.valid-src: $(__XEN_LINUX_UPDATE)
18 $(KETCHUP) -d $(@D) $(LINUX_VER)
19 touch $@ # update timestamp to avoid rebuild