From mboxrd@z Thu Jan  1 00:00:00 1970
From: Razvan Cojocaru <rcojocaru@bitdefender.com>
Subject: Re: [PATCH] xen: Disable RAM-to-RAM copy in
 hvmemul_rep_movs() when mem_access_emulate_enabled
Date: Tue, 05 May 2015 13:08:11 +0300
Message-ID: <5548968B.8070403@bitdefender.com>
References: <1430820082-15790-1-git-send-email-rcojocaru@bitdefender.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
In-Reply-To: <1430820082-15790-1-git-send-email-rcojocaru@bitdefender.com>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: xen-devel@lists.xen.org
Cc: andrew.cooper3@citrix.com, keir@xen.org, jbeulich@suse.com
List-Id: xen-devel@lists.xenproject.org

On 05/05/2015 01:01 PM, Razvan Cojocaru wrote:
> The mem_access client might want to use hvm_emulate_one_no_write(),
> in which case the RAM-to-RAM copy code in hvmemul_rep_movs() would
> lead to an unwanted (and unexpected) write operation.

This patch requires Tamas' last series, which is now in staging.


Thanks,
Razvan Cojocaru