xcp-1.6-updates/xen-4.1.hg

view buildconfigs/select-linux-image @ 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 419a141ca16d
children
line source
1 #!/bin/sh
3 ME=$(basename $0)
5 if [ $# -lt 3 ] ; then
6 echo "usage: $ME <linux-build-directory> <linux-arch> <linux-targets...>" 1>&2
7 exit 1;
8 fi
10 LINUX_DIR=$1
11 LINUX_ARCH=$2
12 LINUX_TARGET=$3 # We don't care about second and subsequent targets
14 case ${XEN_TARGET_ARCH} in
15 ia64)
16 IMAGE=${LINUX_DIR}/arch/ia64/hp/sim/boot/vmlinux.gz
17 ;;
18 *)
19 if [ -f ${LINUX_DIR}/arch/${LINUX_ARCH}/boot/${LINUX_TARGET} ] ; then
20 IMAGE=${LINUX_DIR}/arch/${LINUX_ARCH}/boot/${LINUX_TARGET}
21 elif [ -f ${LINUX_DIR}/${LINUX_TARGET} ] ; then
22 IMAGE=${LINUX_DIR}/${LINUX_TARGET}
23 else
24 echo "$ME: cannot determine Linux image to use for ${LINUX_ARCH} in ${LINUX_DIR}" 1>&2
25 exit 1
26 fi
27 ;;
28 esac
30 echo "$ME: ${IMAGE}" 1>&2
31 echo ${IMAGE}
33 exit 0