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

Re: [Xen-devel] [PATCH 0/2] xen/mem Common cleanup

To: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
From: Tim Deegan <tim@xxxxxxx>
Date: Thu, 4 Jun 2015 15:00:11 +0100
Cc: Xen-devel <xen-devel@xxxxxxxxxxxxx>
Delivery-date: Thu, 04 Jun 2015 14:00:16 +0000
List-id: Xen developer discussion <xen-devel.lists.xen.org>

At 12:43 +0100 on 03 Jun (1433335401), Andrew Cooper wrote:
> Following c/s e758ed14 which describes the current terms used in Xens memory
> management, introduce some infrastructure so that new code can be written
> correctly.
> 
> This is the start of a long potential cleanup.

Acked-by: Tim Deegan <tim@xxxxxxx>

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

References:
- [Xen-devel] [PATCH 0/2] xen/mem Common cleanup
  - From: Andrew Cooper

Prev by Date: [Xen-devel] [Draft D] Xen on ARM vITS Handling
Next by Date: Re: [Xen-devel] [PATCH RFC 1/4] xen: evtchn: make evtchn_reset() ready for soft reset
Previous by thread: [Xen-devel] [PATCH 1/2] xen/mem: Expose typesafe mfns/gfns/pfns to common code
Next by thread: [Xen-devel] [PATCH] VPMU: add lost Intel processor
Index(es):
- Date
- Thread

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