[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] [PATCH] documentation, refactor, and cleanups (v2) for 3.7

To: linux-kernel@xxxxxxxxxxxxxxx
From: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Date: Thu, 26 Jul 2012 16:34:01 -0400
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 26 Jul 2012 20:43:39 +0000
List-id: Xen developer discussion <xen-devel.lists.xen.org>

Attached are four patches that documented a bit more the P2M and MMU
code. And as well make some of the code cleaner and easier to read.



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel

Follow-Ups:
- [Xen-devel] [PATCH 1/4] xen/p2m: Fix the comment describing the P2M tree.
  - From: Konrad Rzeszutek Wilk
- [Xen-devel] [PATCH 2/4] xen/x86: Use memblock_reserve for sensitive areas.
  - From: Konrad Rzeszutek Wilk
- [Xen-devel] [PATCH 4/4] xen/mmu: Provide comments describing the _ka and _va aliasing issue
  - From: Konrad Rzeszutek Wilk
- [Xen-devel] [PATCH 3/4] xen/mmu: The xen_setup_kernel_pagetable doesn't need to return anything.
  - From: Konrad Rzeszutek Wilk

Prev by Date: [Xen-devel] [PATCH 2/4] xen/x86: Use memblock_reserve for sensitive areas.
Next by Date: [Xen-devel] [PATCH 1/4] xen/p2m: Fix the comment describing the P2M tree.
Previous by thread: [Xen-devel] About revoke write access of all the shadows
Next by thread: [Xen-devel] [PATCH 3/4] xen/mmu: The xen_setup_kernel_pagetable doesn't need to return anything.
Index(es):
- Date
- Thread

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.