[PATCH] MMU bug-fixes in generic code that are mostly used by Xen.

[Konrad Rzeszutek Wilk]

I was wondering if you could help. I've this bug-fix:
 [PATCH 1/3] x86/paravirt: PTE updates in k(un)map_atomic need to be

that you picked up some time ago in your tree and then dropped. I am not sure why it
was dropped but perhaps it is b/c I also had that patch in my linux-next and your tool
decided to drop it. Anyhow, was wondering if you would be OK giving it your
Ack or just pulling it in your tree for 3.2.

These two:
 [PATCH 2/3] xen: use generic functions instead of xen_{alloc,
 [PATCH 3/3] xen: map foreign pages for shared rings by updating the

remove what git commit d2fe97c3315a6a406540f74651e7430d9d51e671
	Author: David Vrabel <david.vrabel@xxxxxxxxxx>
	Date:   Thu Sep 29 16:53:32 2011 +0100

	    xen: map foreign pages for shared rings by updating the PTEs directly

added in 3.1 with a more selective way instead of using the big hammer.

I was wondering if you would be OK ACK-ing those two or sticking them
in your tree for 3.2.

All of the patches are in:

 git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git stable/for-akpm-3.2

and the last two have also been sitting for some time in linux-next (and the first
one was there but it looks like I forgot to put it back there as I had thought
that Linus had picked it up.. argh).

 arch/ia64/include/asm/xen/grant_table.h |   29 --------------
 arch/ia64/xen/grant-table.c             |   62 -------------------------------
 arch/x86/include/asm/xen/grant_table.h  |    7 ---
 arch/x86/mm/highmem_32.c                |    2 +
 arch/x86/xen/grant-table.c              |    2 +-
 drivers/xen/xenbus/xenbus_client.c      |   15 +++++--
 include/linux/vmalloc.h                 |    2 +-
 include/xen/grant_table.h               |    1 -
 mm/vmalloc.c                            |   27 ++++++-------
 9 files changed, 27 insertions(+), 120 deletions(-)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/