All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Corneliu ZUZU <czuzu@bitdefender.com>
Cc: Tamas K Lengyel <tamas@tklengyel.com>, Keir Fraser <keir@xen.org>,
	Ian Campbell <ian.campbell@citrix.com>,
	Razvan Cojocaru <rcojocaru@bitdefender.com>,
	Andrew Cooper <andrew.cooper3@citrix.com>,
	xen-devel@lists.xen.org,
	Stefano Stabellini <stefano.stabellini@citrix.com>,
	Jan Beulich <jbeulich@suse.com>
Subject: Re: [PATCH v5 0/2] Vm-events: move monitor vm-events code	to common-side.
Date: Wed, 17 Feb 2016 10:09:14 -0500	[thread overview]
Message-ID: <20160217150914.GA21956@char.us.oracle.com> (raw)
In-Reply-To: <1455694438-18466-1-git-send-email-czuzu@bitdefender.com>

On Wed, Feb 17, 2016 at 09:33:58AM +0200, Corneliu ZUZU wrote:
> This patch series is an attempt to move some of the monitor vm-events code to
> the common-side. Done to make it easier to move additional parts that can be
> moved to common when ARM-side implementations are to be added.

Both applied.
> 
> Patches summary:
> 1. Fix file comment
>     Acked-by: Stefano Stabellini <stefano.stabell...@eu.citrix.com>
> 2. Move monitor_domctl to common-side.
>     Acked-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
>     Acked-by: Razvan Cojocaru <rcojocaru@bitdefender.com>
> 
> Note: ARM support for guest-request, control-register write monitor vm-events
> will follow after review of this patch-series.
> 
> ---
> Changed since v4:
>   1/2: nothing changed
>   2/2: arch_monitor_domctl_event:
>         replaced !old_status w/ requested_status (equivalent but more readable)
> 
> Corneliu ZUZU (2):
>   xen/arm: fix file comments
>   xen/vm-events: Move parts of monitor_domctl code to common-side.
> 
>  MAINTAINERS                   |   1 +
>  xen/arch/arm/hvm.c            |  29 +++++++-
>  xen/arch/x86/monitor.c        | 153 +++++++++++-------------------------------
>  xen/common/Makefile           |   1 +
>  xen/common/domctl.c           |   2 +-
>  xen/common/monitor.c          |  69 +++++++++++++++++++
>  xen/include/asm-arm/monitor.h |  30 +++++++--
>  xen/include/asm-x86/monitor.h |  53 +++++++++++++--
>  xen/include/xen/monitor.h     |  30 +++++++++
>  9 files changed, 245 insertions(+), 123 deletions(-)
>  create mode 100644 xen/common/monitor.c
>  create mode 100644 xen/include/xen/monitor.h
> 
> -- 
> 2.5.0
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel

  parent reply	other threads:[~2016-02-17 15:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-17  7:33 [PATCH v5 0/2] Vm-events: move monitor vm-events code to common-side Corneliu ZUZU
2016-02-17  7:36 ` [PATCH v5 1/2] xen/arm: fix file comments Corneliu ZUZU
2016-02-17  7:38 ` [PATCH v5 2/2] xen/vm-events: Move parts of monitor_domctl code to common-side Corneliu ZUZU
2016-02-17 15:56   ` Tamas K Lengyel
2016-02-17 15:09 ` Konrad Rzeszutek Wilk [this message]
2016-02-17 17:58   ` [PATCH v5 0/2] Vm-events: move monitor vm-events " Corneliu ZUZU

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160217150914.GA21956@char.us.oracle.com \
    --to=konrad.wilk@oracle.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=czuzu@bitdefender.com \
    --cc=ian.campbell@citrix.com \
    --cc=jbeulich@suse.com \
    --cc=keir@xen.org \
    --cc=rcojocaru@bitdefender.com \
    --cc=stefano.stabellini@citrix.com \
    --cc=tamas@tklengyel.com \
    --cc=xen-devel@lists.xen.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.