qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Qin, Chao" <chao.qin@linux.intel.com>
To: Igor Mammedov <imammedo@redhat.com>
Cc: qemu-devel@nongnu.org, yu.ning@linux.intel.com,
	Qin Chao <chao.qin@intel.com>,
	Richard Henderson <rth@twiddle.net>,
	Eduardo Habkost <ehabkost@redhat.com>,
	Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] hax: Properly handle IA32_APIC_BASE MSR
Date: Tue, 20 Mar 2018 15:45:45 +0800	[thread overview]
Message-ID: <05e0dd7c-6e0a-d126-cdc5-e0989bf9bdf6@linux.intel.com> (raw)
In-Reply-To: <20180320081226.66d4b92e@redhat.com>



On 3/20/2018 3:12 PM, Igor Mammedov wrote:
> On Tue, 20 Mar 2018 13:29:24 +0800 "Qin, Chao"  > <chao.qin@linux.intel.com> wrote: > >> On 3/20/2018 12:05 AM, Igor 
Mammedov wrote: >>> On Mon, 19 Mar 2018 17:04:49 +0800 
chao.qin@linux.intel.com >>> wrote: > >> From: Qin Chao 
<chao.qin@intel.com> > / something horribly wrong with mail client used 
for reply / >
Very sorry for the wrong reply style.

>>> @@  >> -933,6 +944,9 @@ static int hax_set_msrs(CPUArchState *env) >> >> 
hax_msr_entry_set(&msrs[n++], MSR_FMASK, env->fmask); >> >> 
hax_msr_entry_set(&msrs[n++], MSR_KERNELGSBASE, >> >> 
env->kernelgsbase); #endif + hax_msr_entry_set(&msrs[n++], >> >> 
MSR_IA32_APICBASE, \ + >> >> 
cpu_get_apic_base(x86_env_get_cpu(env)->apic_state)); + md.nr_msr = >> 
 >> n; md.done = 0; > Does it work for you if you drop everything >> 
except of this chunk? Yes, it works just with this chunk. > Could you 
send v2 dropping unnecessary chunks pls? (provided that > Paolo would 
drop queued v1).
I think you may missed the clarification for the codes that syncing
IA32_APIC_BASE MSR from HAXM to QEMU due to rhe wrong reply style.
Sorry again for the inconvenience. Please refer to the following.

Yes, the BSP is hard-coded in QEMU. But other bits, not just BSP flag, are
alse needed to sync from HAXM, such as x2APIC mode flag (bit 10) and
APIC enable/disable flag (bit 11). As in the Google Zircon
(https://github.com/fuchsia-mirror/zircon/blob/master/kernel/arch/x86/lapic.cpp#L157),
it will change IA32_APIC_BASE[10] and the the bit to 1 if x2APIC enabled.
Although x2APIC mode is not supported yet for TCG mode, it's worthy to
keep the codes that syncing IA32_APIC_BASE from HAXM to QEMU and
if x2APIC mode is supported fro TCG in future, there is no any effort needed
to make HAXM to work with this mode. Alos, in KVM it synced the 
IA32_APIC_BASE
MSR to QEMU at every VM-Exit.

      reply	other threads:[~2018-03-20  7:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-19  9:04 [Qemu-devel] [PATCH] hax: Properly handle IA32_APIC_BASE MSR chao.qin
2018-03-19 15:52 ` Paolo Bonzini
2018-03-19 16:05 ` Igor Mammedov
2018-03-20  5:29   ` Qin, Chao
2018-03-20  7:12     ` Igor Mammedov
2018-03-20  7:45       ` Qin, Chao [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=05e0dd7c-6e0a-d126-cdc5-e0989bf9bdf6@linux.intel.com \
    --to=chao.qin@linux.intel.com \
    --cc=chao.qin@intel.com \
    --cc=ehabkost@redhat.com \
    --cc=imammedo@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=rth@twiddle.net \
    --cc=yu.ning@linux.intel.com \
    /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).