From: "H. Peter Anvin" <hpa@zytor.com>
To: Cyrill Gorcunov <gorcunov@openvz.org>
Cc: Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
"Maciej W. Rozycki" <macro@linux-mips.org>,
Vegard Nossum <vegard.nossum@gmail.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH -tip] x86,apic -- don't forget to disconnect BSP discrete apic
Date: Wed, 08 Jul 2009 20:45:45 -0700 [thread overview]
Message-ID: <4A5567E9.5080403@zytor.com> (raw)
In-Reply-To: <aa79d98a0907082004i616ff057ic8eea014f712064d@mail.gmail.com>
Cyrill Gorcunov wrote:
> On 7/9/09, H. Peter Anvin <hpa@zytor.com> wrote:
>> Cyrill Gorcunov wrote:
>>> In case of discrete APIC cpu_has_apic could be not set.
>>> This leads to disconnect_bsp_APIC is not called where
>>> it should.
>> I thought we were going to turn on cpu_has_apic in this case?
>>
>> -hpa
>>
>>
> Yes, this is just a temporary fix. I'll remove this snippet as only
> cpu-has-apic patch will be ready (i need to re-check all ways and and
> i need some time for this. Hope will finish it at weekend). Dunno
> Peter. If there is no urgency -- lets mark that we have this temporary
> workaround in lklm and if we get kind of bugreport we could apply the
> patch shortly :)
Since discrete-APIC systems are so old and rare I think it can wait for
the proper fix, however, as you said, if there are unexpected problems
we can reconsider.
-hpa
--
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel. I don't speak on their behalf.
prev parent reply other threads:[~2009-07-09 3:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-08 20:07 [PATCH -tip] x86,apic -- don't forget to disconnect BSP discrete apic Cyrill Gorcunov
2009-07-08 21:33 ` H. Peter Anvin
2009-07-09 3:04 ` Cyrill Gorcunov
2009-07-09 3:45 ` H. Peter Anvin [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=4A5567E9.5080403@zytor.com \
--to=hpa@zytor.com \
--cc=gorcunov@openvz.org \
--cc=linux-kernel@vger.kernel.org \
--cc=macro@linux-mips.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=vegard.nossum@gmail.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