All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wei Liu <wei.liu2@citrix.com>
To: Razvan Cojocaru <rcojocaru@bitdefender.com>
Cc: tamas@tklengyel.com, wei.liu2@citrix.com,
	ian.campbell@citrix.com, stefano.stabellini@eu.citrix.com,
	andrew.cooper3@citrix.com, ian.jackson@eu.citrix.com,
	xen-devel@lists.xen.org, stefano.stabellini@citrix.com,
	jbeulich@suse.com, keir@xen.org
Subject: Re: [PATCH V3] vm_event: Remove xc_mem_access_enable_emulate() and friends
Date: Mon, 15 Feb 2016 11:34:25 +0000	[thread overview]
Message-ID: <20160215113425.GG8818@citrix.com> (raw)
In-Reply-To: <1455439138-19093-1-git-send-email-rcojocaru@bitdefender.com>

On Sun, Feb 14, 2016 at 10:38:58AM +0200, Razvan Cojocaru wrote:
> xc_mem_access_enable_emulate() and xc_mem_access_disable_emulate()
> are currently no-ops, that is all they do is set a flag that
> nobody else checks. The user can already set the EMULATE flags in
> the vm_event response if emulation is desired, and having an extra
> check above that is not inherently safer, but it does complicate
> (currenly unnecessarily) the API. This patch removes these
> functions and the corresponding hypervisor code.
> 
> Signed-off-by: Razvan Cojocaru <rcojocaru@bitdefender.com>
> 
> ---
> Changes since V1:
>  - Commented-out the XENMEM_access_op_enable_emulate and
>    XENMEM_access_op_disable_emulate #defines instead of simply
>    removing them to prevent their reuse, as requested by
>    Jan Beulich.
> ---
>  tools/libxc/include/xenctrl.h | 11 -----------
>  tools/libxc/xc_mem_access.c   | 24 ------------------------

Acked-by: Wei Liu <wei.liu2@citrix.com>

      parent reply	other threads:[~2016-02-15 11:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-14  8:38 [PATCH V3] vm_event: Remove xc_mem_access_enable_emulate() and friends Razvan Cojocaru
2016-02-14  8:40 ` Razvan Cojocaru
2016-02-14 18:00 ` Tamas K Lengyel
2016-02-15 11:15 ` Jan Beulich
2016-02-15 11:21   ` Stefano Stabellini
2016-02-15 11:34 ` Wei Liu [this message]

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=20160215113425.GG8818@citrix.com \
    --to=wei.liu2@citrix.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=ian.campbell@citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=jbeulich@suse.com \
    --cc=keir@xen.org \
    --cc=rcojocaru@bitdefender.com \
    --cc=stefano.stabellini@citrix.com \
    --cc=stefano.stabellini@eu.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.