qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Denis V. Lunev" <den@openvz.org>
To: "Paolo Bonzini" <pbonzini@redhat.com>,
	"Andreas Färber" <afaerber@suse.de>,
	qemu-devel@nongnu.org
Cc: Eduardo Habkost <ehabkost@redhat.com>,
	mst@redhat.com, Nadav Amit <namit@cs.technion.ac.il>,
	Igor Mammedov <imammedo@redhat.com>,
	nadav.amit@gmail.com, rth@twiddle.net
Subject: Re: [Qemu-devel] target-i386: clear bsp bit when designating bsp
Date: Tue, 7 Apr 2015 16:26:04 +0300	[thread overview]
Message-ID: <5523DAEC.6070605@openvz.org> (raw)
In-Reply-To: <5523D90A.1040604@redhat.com>

On 07/04/15 16:18, Paolo Bonzini wrote:
>
>
> On 07/04/2015 13:57, Andreas Färber wrote:
>>>> If this is some issue with sync'ing state back and forth before QEMU and
>>>> KVM then the real issue has not been explained.
>> Hm, hw/intc/apic_common.c:apic_reset_common() has:
>>
>>      bsp = cpu_is_bsp(s->cpu);
>>      s->apicbase = APIC_DEFAULT_ADDRESS |
>>          (bsp ? MSR_IA32_APICBASE_BSP : 0) | MSR_IA32_APICBASE_ENABLE;
>>
>> What this is doing is really:
>>
>>      bsp = cpu_get_apic_base(s->cpu->apic_state) & MSR_IA32_APICBASE_BSP;
>>      s->apicbase = APIC_DEFAULT_ADDRESS |
>>          (bsp ? MSR_IA32_APICBASE_BSP : 0) | MSR_IA32_APICBASE_ENABLE;
>>
>> Unless I'm missing something, since we are in the APIC device's reset
>> function, this is effectively a twisted way of writing:
>>
>>      bsp = s->apicbase & MSR_IA32_APICBASE_BSP;
>>      s->apicbase = APIC_DEFAULT_ADDRESS |
>>          (bsp ? MSR_IA32_APICBASE_BSP : 0) | MSR_IA32_APICBASE_ENABLE;
>
> Yes, this is more readable.

just $0.02 :)

why don't
         bsp = s->apicbase & MSR_IA32_APICBASE_BSP;
         s->apicbase =
		APIC_DEFAULT_ADDRESS | bsp | MSR_IA32_APICBASE_ENABLE;
in this case. This looks the same from the textual point of view.

Den

  reply	other threads:[~2015-04-07 13:26 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-01 23:58 [Qemu-devel] target-i386: clear bsp bit when designating bsp Nadav Amit
2015-04-02 12:34 ` Paolo Bonzini
2015-04-07 10:15   ` Andreas Färber
2015-04-07 10:34     ` Paolo Bonzini
2015-04-07 10:44       ` Andreas Färber
2015-04-07 10:54         ` Paolo Bonzini
2015-04-07 11:09           ` Andreas Färber
2015-04-07 11:57             ` Andreas Färber
2015-04-07 13:14               ` Igor Mammedov
2015-04-07 13:24                 ` Andreas Färber
2015-04-07 13:29                   ` Paolo Bonzini
2015-04-07 13:40                     ` Andreas Färber
2015-04-07 13:54                       ` Paolo Bonzini
2015-04-07 13:18               ` Paolo Bonzini
2015-04-07 13:26                 ` Denis V. Lunev [this message]
2015-04-07 13:29                   ` Paolo Bonzini
2015-04-07 13:44                     ` Denis V. Lunev
2015-04-07 13:47                       ` Andreas Färber

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=5523DAEC.6070605@openvz.org \
    --to=den@openvz.org \
    --cc=afaerber@suse.de \
    --cc=ehabkost@redhat.com \
    --cc=imammedo@redhat.com \
    --cc=mst@redhat.com \
    --cc=nadav.amit@gmail.com \
    --cc=namit@cs.technion.ac.il \
    --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).