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

Re: [Xen-devel] [PATCH 00/16] x86/vm-event: numerous adjustments & fixes



what's the difference between this series and earlier one?

[PATCH v3 0/8] x86/vm-event: Adjustments & fixes

looks you have some patches cross-posted (e.g. 1/16)...

> -----Original Message-----
> From: Corneliu ZUZU [mailto:czuzu@xxxxxxxxxxxxxxx]
> Sent: Saturday, July 09, 2016 12:12 PM
> To: xen-devel@xxxxxxxxxxxxx
> Cc: Andrew Cooper; George Dunlap; Jan Beulich; Julien Grall; Nakajima, Jun; 
> Tian, Kevin;
> Paul Durrant; Razvan Cojocaru; Stefano Stabellini; Tamas K Lengyel
> Subject: [PATCH 00/16] x86/vm-event: numerous adjustments & fixes
> 
> Adjustments & fixes to the vm-events code, mostly monitor-related.
> As I hadn't got the time/proper context to test these changes on a real 
> machine,
> for now please consider them only for review, I'll let you know when and how
> actual testing went.
> 
> Thanks,
> 
> Corneliu ZUZU (16):
>   x86/vmx_update_guest_cr: minor optimization
>   x86: fix: make atomic_read() param const
>   x86/monitor: mechanical renames
>   x86/monitor: relocate vm_event_register_write_resume() function to
>     monitor code
>   x86/monitor: relocate code more appropriately
>   x86/monitor: fix: set msr_bitmap to NULL after xfree
>   x86/vm-event: fix: call cleanup when init fails, to free partial
>     allocs
>   x86/vm-event: call monitor init & cleanup funcs from respective
>     vm_event funcs
>   arm/monitor: move d->monitor cleanup to monitor_cleanup_domain()
>   x86/vm-event: centralize vcpu-destroy cleanup in vm-events code
>   x86/monitor: fix: treat -monitor- properly, as a subsys of the
>     vm-event subsys
>   x86/vm-event: fix: move cleanup of mem_access_emulate_each_rep to
>     monitor stub
>   x86/monitor: introduce writes_pending field in monitor_write_data
>   x86/monitor: clarify separation between monitor subsys and vm-event as
>     a whole
>   x86/monitor: fix: don't compromise a monitor_write_data with pending
>     CR writes
>   x86/monitor: fix: xc_monitor _write_ctrlreg w/o previous _enable must
>     fail
> 
>  xen/arch/x86/domain.c             |   4 +-
>  xen/arch/x86/hvm/emulate.c        |  11 +-
>  xen/arch/x86/hvm/hvm.c            |  92 ++++++++--------
>  xen/arch/x86/hvm/vmx/vmx.c        |  64 +++++++++--
>  xen/arch/x86/mm/p2m.c             |   7 +-
>  xen/arch/x86/monitor.c            | 218
> +++++++++++++++++++++++++++++++++++---
>  xen/arch/x86/vm_event.c           |  82 +++++++-------
>  xen/common/monitor.c              |   4 +-
>  xen/common/vm_event.c             |  37 ++++---
>  xen/include/asm-arm/monitor.h     |  17 +--
>  xen/include/asm-arm/vm_event.h    |  21 ++--
>  xen/include/asm-x86/atomic.h      |   4 +-
>  xen/include/asm-x86/domain.h      |  31 ++++--
>  xen/include/asm-x86/hvm/vmx/vmx.h |   1 +
>  xen/include/asm-x86/monitor.h     |  32 ++++--
>  xen/include/asm-x86/vm_event.h    |  27 ++---
>  xen/include/xen/monitor.h         |  11 +-
>  xen/include/xen/sched.h           |   1 +
>  18 files changed, 473 insertions(+), 191 deletions(-)
> 
> --
> 2.5.0


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

 


Rackspace

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