All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Andreas Färber" <afaerber@suse.de>
To: "Denis V. Lunev" <den@openvz.org>,
	Paolo Bonzini <pbonzini@redhat.com>,
	qemu-devel@nongnu.org
Cc: Eduardo Habkost <ehabkost@redhat.com>,
	Nadav Amit <namit@cs.technion.ac.il>,
	mst@redhat.com, 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, 07 Apr 2015 15:47:12 +0200	[thread overview]
Message-ID: <5523DFE0.4040301@suse.de> (raw)
In-Reply-To: <5523DF4A.7050905@openvz.org>

Am 07.04.2015 um 15:44 schrieb Denis V. Lunev:
> On 07/04/15 16:29, Paolo Bonzini wrote:
>>
>>
>> On 07/04/2015 15:26, Denis V. Lunev wrote:
>>> 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.
>>
>> Yes.  Would you like to send a patch?
>>
>> Paolo
>>
> 
> no prob, just give me 2 minutes. Side note, bsp will become uint32_t
> and we will loose tracepoint inside cpu_get_apic_base() on this
> path...

Yes, I intentionally left it out above as I don't think we need to trace
the local usage here. Worth mentioning in the commit message though.

Regards,
Andreas

-- 
SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu,
Graham Norton; HRB 21284 (AG Nürnberg)

      reply	other threads:[~2015-04-07 13:47 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
2015-04-07 13:29                   ` Paolo Bonzini
2015-04-07 13:44                     ` Denis V. Lunev
2015-04-07 13:47                       ` Andreas Färber [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=5523DFE0.4040301@suse.de \
    --to=afaerber@suse.de \
    --cc=den@openvz.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.