mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Yinghai Lu <yinghai@kernel.org>
Cc: "Zhang, Lin-Bao (Linux Kernel R&D)" <linbao.zhang@hp.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"alan@lxorguk.ukuu.org.uk" <alan@lxorguk.ukuu.org.uk>,
	"mingo@redhat.com" <mingo@redhat.com>,
	"tglx@linutronix.de" <tglx@linutronix.de>,
	"x86@kernel.org" <x86@kernel.org>,
	"a.p.zijlstra@chello.nl" <a.p.zijlstra@chello.nl>,
	"jarkko.sakkinen@intel.com" <jarkko.sakkinen@intel.com>,
	"joerg.roedel@amd.com" <joerg.roedel@amd.com>,
	"agordeev@redhat.com" <agordeev@redhat.com>
Subject: Re: Why Linux kernel forced to enter X2APIC mode( just because of booting cpu has supported x2apic) without depending on BIOS' setting in MSR->x2apic enablement bit ?
Date: Thu, 20 Dec 2012 08:48:31 -0800	[thread overview]
Message-ID: <50D3415F.8010205@zytor.com> (raw)
In-Reply-To: <CAE9FiQVRcGvaTJ6NrxnQuFbPT9OwB7j8xxhDe5kcYUpgAMkz1A@mail.gmail.com>

On 12/20/2012 08:46 AM, Yinghai Lu wrote:
> On Thu, Dec 20, 2012 at 2:38 AM, Zhang, Lin-Bao (Linux Kernel R&D)
> <linbao.zhang@hp.com> wrote:
>> I think current core argument is our BIOS did following judgement ,
>> but Linux kernel did not(Linux seems just judge BSP supports x2apic mode or not by CPUID method)
> 
> kernel checks that, if the BSP in x2apic mode, kernel will check if
> intr-remapping can be enabled, otherwise
> it will switch back to xapic mode.
> 
>> Our BSP really supports x2apic mode, however,as this spec, our BIOS think some of configuration of server
>> could not meet x2apic conditions ,So didn't place local xAPICs into x2apic mode.
>> But linux kernel indeed enable x2apic mode(just believe BSP, didn't do above judgement) . so this is the conflict.
> 
> so your BIOS is wrong,  it does not enable intr-remapping.
> 

FWIW, I bought a *server* today and it didn't have interrupt remapping
and x2APIC, I would consider it defective and return it.

	-hpa



  reply	other threads:[~2012-12-20 16:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-18  9:50 Zhang, Lin-Bao (Linux Kernel R&D)
2012-12-18 17:49 ` Yinghai Lu
2012-12-19 10:13   ` Zhang, Lin-Bao (Linux Kernel R&D)
2012-12-19 16:03     ` Yinghai Lu
2012-12-19 10:36   ` Zhang, Lin-Bao (Linux Kernel R&D)
2012-12-19 16:05     ` Yinghai Lu
2012-12-20 10:38       ` Zhang, Lin-Bao (Linux Kernel R&D)
2012-12-20 16:46         ` Yinghai Lu
2012-12-20 16:48           ` H. Peter Anvin [this message]
2012-12-19 16:10   ` H. Peter Anvin

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=50D3415F.8010205@zytor.com \
    --to=hpa@zytor.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=agordeev@redhat.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=jarkko.sakkinen@intel.com \
    --cc=joerg.roedel@amd.com \
    --cc=linbao.zhang@hp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.org \
    --cc=yinghai@kernel.org \
    /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

Powered by JetHome