All of lore.kernel.org
 help / color / mirror / Atom feed
From: Razvan Cojocaru <rcojocaru@bitdefender.com>
To: xen-devel@lists.xen.org
Cc: andrew.cooper3@citrix.com, keir@xen.org, jbeulich@suse.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	[thread overview]
Message-ID: <5548968B.8070403@bitdefender.com> (raw)
In-Reply-To: <1430820082-15790-1-git-send-email-rcojocaru@bitdefender.com>

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

  reply	other threads:[~2015-05-05 10:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-05 10:01 [PATCH] xen: Disable RAM-to-RAM copy in hvmemul_rep_movs() when mem_access_emulate_enabled Razvan Cojocaru
2015-05-05 10:08 ` Razvan Cojocaru [this message]
2015-05-05 10:23 ` Jan Beulich
2015-05-05 11:27   ` Razvan Cojocaru

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=5548968B.8070403@bitdefender.com \
    --to=rcojocaru@bitdefender.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=jbeulich@suse.com \
    --cc=keir@xen.org \
    --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.