From: Roman Bolshakov <r.bolshakov@yadro.com>
To: Cameron Esfahani <dirty@apple.com>
Cc: pbonzini@redhat.com, qemu-devel@nongnu.org
Subject: Re: [PATCH v2] hvf: use standard CR0 and CR4 register definitions
Date: Wed, 15 Apr 2020 16:01:19 +0300 [thread overview]
Message-ID: <20200415130119.GA7853@SPB-NB-133.local> (raw)
In-Reply-To: <a31c1c7f7a7b4f537be9d307ccddc6e17761f1b0.1586927010.git.dirty@apple.com>
On Tue, Apr 14, 2020 at 10:12:12PM -0700, Cameron Esfahani wrote:
> target/i386/cpu.h | 2 ++
> target/i386/hvf/hvf.c | 2 +-
> target/i386/hvf/vmx.h | 15 ++++++++-------
> target/i386/hvf/x86.c | 6 +++---
> target/i386/hvf/x86.h | 34 ----------------------------------
> target/i386/hvf/x86_mmu.c | 2 +-
> target/i386/hvf/x86_task.c | 3 ++-
> 7 files changed, 17 insertions(+), 47 deletions(-)
>
Hi Cameron,
Reviewed-by: Roman Bolshakov <r.bolshakov@yadro.com>
Thanks,
Roman
prev parent reply other threads:[~2020-04-15 13:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-15 5:12 [PATCH v2] hvf: use standard CR0 and CR4 register definitions Cameron Esfahani via
2020-04-15 12:06 ` Paolo Bonzini
2020-04-15 13:01 ` Roman Bolshakov [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=20200415130119.GA7853@SPB-NB-133.local \
--to=r.bolshakov@yadro.com \
--cc=dirty@apple.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.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).