Hi, At 01:11 +0100 on 18 Feb (1424218290), Tamas K Lengyel wrote: > This patch series aims to clean up the mem_event subsystem within Xen. The > original use-case for this system was to allow external helper applications > running in privileged domains to control various memory operations performed > by Xen. Amongs these were paging, sharing and access control. The subsystem > has since been extended to also deliver non-memory related events, namely > various HVM debugging events (INT3, MTF, MOV-TO-CR, MOV-TO-MSR). The > structures > and naming of related functions however has not caught up to these new > use-cases, thus leaving many ambiguities in the code. Furthermore, future > use-cases envisioned for this subsystem include PV domains and ARM domains, > thus there is a need to establish a common base to build on. > > In this series we convert the mem_event system to vm_event in which we clearly > define the scope of information that is transmitted via the event > delivery mechanism. Afterwards, we clean up the naming of the structures and > related functions to more clearly be in line with their actual operations. > Finally, the control of monitor events is moved to a new domctl, monitor_op.
I've read through these and except for the comments I made on patch #11, it looks good to me. You can add my ack to patches 9, 10 and 12 as well as the ones I replied to separately. Cheers, Tim. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
