From: Don Slutz <dslutz@verizon.com>
To: Paolo Bonzini <pbonzini@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
"Markus Armbruster" <armbru@redhat.com>,
"Luiz Capitulino" <lcapitulino@redhat.com>,
"Anthony Liguori" <aliguori@amazon.com>,
"Andreas Färber" <afaerber@suse.de>,
"Richard Henderson" <rth@twiddle.net>
Subject: Re: [Qemu-devel] [PATCH v4 6/7] vmport: Add VMware all ring hack
Date: Thu, 30 Apr 2015 11:15:06 -0400 [thread overview]
Message-ID: <554246FA.7020401@one.verizon.com> (raw)
In-Reply-To: <5542342C.7080904@redhat.com>
On 04/30/15 09:54, Paolo Bonzini wrote:
> On 30/04/2015 15:32, Don Slutz wrote:
>> This is done by adding a new machine property vmware-port-ring3 that
>> needs to be enabled to have any effect. It only effects accel=tcg
>> mode. It is needed if you want to use VMware tools in accel=tcg
>> mode.
>
> How does it work on KVM or Xen?
>
Xen change is in progress (patch posted). I have not done any work on
HVM yet.
>>
>> diff --git a/target-i386/cpu.c b/target-i386/cpu.c
>> index 3305e09..5085f29 100644
>> --- a/target-i386/cpu.c
>> +++ b/target-i386/cpu.c
>> @@ -2592,6 +2592,7 @@ static void x86_cpu_reset(CPUState *s)
>> X86CPUClass *xcc = X86_CPU_GET_CLASS(cpu);
>> CPUX86State *env = &cpu->env;
>> int i;
>> + bool save_vmware_port_ring3 = env->hflags2 & HF2_VMPORT_HACK_MASK;
>>
>> xcc->parent_reset(s);
>>
>> @@ -2607,6 +2608,9 @@ static void x86_cpu_reset(CPUState *s)
>> env->hflags |= HF_SOFTMMU_MASK;
>> #endif
>> env->hflags2 |= HF2_GIF_MASK;
>> + if (save_vmware_port_ring3) {
>> + env->hflags2 |= HF2_VMPORT_HACK_MASK;
>> + }
>>
>> cpu_x86_update_cr0(env, 0x60000010);
>> env->a20_mask = ~0x0;
>
> The save/restore suggests that you want a new bool-typed field in
> CPUX86State instead of a bit env->hflags2.
>
That is a possibility. It did not look simple to access CPUX86State
where I needed to check HF2_VMPORT_HACK_MASK. Instead of the
save/restore I could add it both places.
-Don Slutz
> Paolo
>
next prev parent reply other threads:[~2015-04-30 15:15 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-30 13:32 [Qemu-devel] [PATCH v4 0/7] Add limited support of VMware's hyper-call rpc Don Slutz
2015-04-30 13:32 ` [Qemu-devel] [PATCH v4 1/7] vmport.c: Fix vmport_cmd_ram_size Don Slutz
2015-04-30 13:32 ` [Qemu-devel] [PATCH v4 2/7] vmport_rpc: Add the object vmport_rpc Don Slutz
2015-04-30 13:32 ` [Qemu-devel] [PATCH v4 3/7] vmport_rpc: Add limited support of VMware's hyper-call rpc Don Slutz
2015-04-30 13:32 ` [Qemu-devel] [PATCH v4 4/7] vmport_rpc: Add QMP access to vmport_rpc object Don Slutz
2015-04-30 13:55 ` Paolo Bonzini
2015-04-30 15:17 ` Don Slutz
2015-04-30 13:32 ` [Qemu-devel] [PATCH v4 5/7] vmport_rpc: Add migration Don Slutz
2015-04-30 13:32 ` [Qemu-devel] [PATCH v4 6/7] vmport: Add VMware all ring hack Don Slutz
2015-04-30 13:54 ` Paolo Bonzini
2015-04-30 15:15 ` Don Slutz [this message]
2015-04-30 15:23 ` Paolo Bonzini
2015-04-30 18:11 ` Don Slutz
2015-04-30 15:25 ` Paolo Bonzini
2015-04-30 13:32 ` [Qemu-devel] [PATCH v4 7/7] MAINTAINERS: add VMware port Don Slutz
2015-04-30 13:55 ` [Qemu-devel] [PATCH v4 0/7] Add limited support of VMware's hyper-call rpc Paolo Bonzini
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=554246FA.7020401@one.verizon.com \
--to=dslutz@verizon.com \
--cc=afaerber@suse.de \
--cc=aliguori@amazon.com \
--cc=armbru@redhat.com \
--cc=lcapitulino@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/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).