Re: [Xen-devel] [PATCH v5 00/17] Mem_event and mem_access for ARM

["Jan Beulich" <JBeulich@xxxxxxxx>]

>>> On 10.09.14 at 15:28, <tklengyel@xxxxxxxxxxxxx> wrote:
> The ARM virtualization extension provides 2-stage paging, a similar mechanisms
> to Intel's EPT, which can be used to trace the memory accesses performed by
> the guest systems. This series moves the mem_access and mem_event codebase
> into Xen common, performs some code cleanup and architecture specific 
> division
> of components, then sets up the necessary infrastructure in the ARM code
> to deliver the event on R/W/X traps. Finally, we turn on the compilation of
> mem_access and mem_event on ARM and perform the necessary changes to the 
> tools side.
> 
> This version of the series has been fully tested and is functional on an
> Arndale board.
> 
> This PATCH series is also available at:
> https://github.com/tklengyel/xen/tree/arm_memaccess5 
> 
> Tamas K Lengyel (17):
>   xen: Relocate mem_access and mem_event into common.
>   xen: Relocate p2m_mem_access_resume to mem_access common
>   xen: Relocate struct npfec definition into common
>   xen: Relocate mem_event_op domctl and access_op memop into common.
>   xen/mem_event: Clean out superfluous white-spaces
>   xen/mem_event: Relax error condition on debug builds
>   xen/mem_event: Abstract architecture specific sanity checks
>   xen/mem_access: Abstract architecture specific sanity check

So I think up to here the series could go in afaic. Question is - does
this make sense without the ARM parts?

Thanks, Jan


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