From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Jan Beulich <JBeulich@suse.com>,
xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH v2 2/2] hvmloader: clone REP INSW test from REP INSB one
Date: Thu, 7 Sep 2017 12:50:03 +0100 [thread overview]
Message-ID: <fa7af5fd-bfaa-3fea-53cb-f01455b2f5b0@citrix.com> (raw)
In-Reply-To: <59B1357302000078001782DC@prv-mh.provo.novell.com>
On 07/09/17 11:02, Jan Beulich wrote:
> This also covers an individual string insn access crossing a page
> boundary.
>
> Signed-off-by: Jan Beulich <jbeulich@suse.com>
Reviewed-by: Andrew Cooper <andrew.cooper3@citrix.com>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
prev parent reply other threads:[~2017-09-07 11:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-07 8:53 [PATCH v2 0/2] hvmloader: improve (debug) tests Jan Beulich
2017-09-07 10:02 ` [PATCH v2 1/2] hvmloader: dynamically determine scratch memory range for tests Jan Beulich
2017-09-07 10:22 ` Andrew Cooper
2017-09-07 10:02 ` [PATCH v2 2/2] hvmloader: clone REP INSW test from REP INSB one Jan Beulich
2017-09-07 11:50 ` Andrew Cooper [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=fa7af5fd-bfaa-3fea-53cb-f01455b2f5b0@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=JBeulich@suse.com \
--cc=xen-devel@lists.xenproject.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).