linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Yinghai Lu <yinghai@kernel.org>
To: Brice Goglin <brice.goglin@gmail.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
	Ulrich Drepper <drepper@gmail.com>,
	jbarnes@virtuousgeek.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	lenb@kernel.org, x86@kernel.org, linux-pci@vger.kernel.org
Subject: Re: SNB PCI root information
Date: Fri, 22 Jun 2012 13:41:35 -0700	[thread overview]
Message-ID: <CAE9FiQUOWjLz86JZQrN-v1PdKfLAV022CPrjeArmYM5bRD+drA@mail.gmail.com> (raw)
In-Reply-To: <4FE4D7B7.8000004@gmail.com>

On Fri, Jun 22, 2012 at 1:38 PM, Brice Goglin <brice.goglin@gmail.com> wrote:
> Le 22/06/2012 19:28, Yinghai Lu a écrit :
>> On Fri, Jun 22, 2012 at 12:14 AM, Brice Goglin <brice.goglin@gmail.com> wrote:
>>
>>>> BIOS _PXM return 0 for both pci root buses?
>>>>
>>> Here's dmesg.
>>> I can't say for sure whether _PXM returns 0 since I don't know how to
>>> read all this :) But Linux puts the first socket cpumap in
>>> /sys/bus/pci/devices/*/local_cpus (and that's wrong according to the
>>> motherboard manual and according to the performance we see).
>>>
>> hi, looks like you system bios does not provide _PXM for the root bus.
>>
>
> So why does Linux say that all buses are close to socket 0 instead of
> close to everything as usual?

        if (bus && node != -1) {
#ifdef CONFIG_ACPI_NUMA
                if (pxm >= 0)
                        dev_printk(KERN_DEBUG, &bus->dev,
                                   "on NUMA node %d (pxm %d)\n", node, pxm);
#else
                dev_printk(KERN_DEBUG, &bus->dev, "on NUMA node %d\n", node);
#endif
        }

so can you boot with "debug ignore_loglevel" ?

Thanks

Yinghai

  reply	other threads:[~2012-06-22 20:41 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAOPLpQfUm-2ENkbnYfXEn1nf9FHnaRk3aqQTSTBWb-CsfCUCFA@mail.gmail.com>
2012-06-16  3:03 ` SNB PCI root information Yinghai Lu
2012-06-16  8:52   ` Thomas Gleixner
2012-06-16 19:36     ` Yinghai Lu
2012-06-16 21:56   ` Bjorn Helgaas
2012-06-18 22:30     ` Ulrich Drepper
2012-06-18 23:40       ` Yinghai Lu
2012-06-19 12:36         ` Bjorn Helgaas
2012-06-19 18:20           ` Yinghai Lu
2012-06-20 17:11             ` Ulrich Drepper
2012-06-20 17:17             ` Bjorn Helgaas
2012-06-20 17:59               ` Ulrich Drepper
2012-06-20 18:37                 ` Yinghai Lu
2012-06-20 18:46                 ` Bjorn Helgaas
2012-06-20 19:28                   ` Yinghai Lu
2012-06-20 19:34                     ` Ingo Molnar
2012-06-20 20:04                       ` Ulrich Drepper
2012-06-20 20:16                         ` Bjorn Helgaas
2012-06-20 21:21                           ` Ulrich Drepper
2012-06-20 23:58                         ` Yinghai Lu
2012-06-21  2:37                       ` Yinghai Lu
2012-06-21  3:50                         ` Yinghai Lu
2012-06-21 12:17                           ` Ulrich Drepper
2012-06-21 16:22                             ` Ulrich Drepper
2012-06-21 18:11                               ` Yinghai Lu
2012-06-25 17:54                                 ` Ulrich Drepper
2012-06-20 19:57                     ` Brice Goglin
2012-06-21  2:43                       ` Yinghai Lu
2012-06-21  5:56                         ` Brice Goglin
2012-06-21 19:24                           ` Yinghai Lu
2012-06-22  7:14                             ` Brice Goglin
2012-06-22 17:28                               ` Yinghai Lu
2012-06-22 20:38                                 ` Brice Goglin
2012-06-22 20:41                                   ` Yinghai Lu [this message]
2012-06-25  9:07                                     ` Brice Goglin

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=CAE9FiQUOWjLz86JZQrN-v1PdKfLAV022CPrjeArmYM5bRD+drA@mail.gmail.com \
    --to=yinghai@kernel.org \
    --cc=bhelgaas@google.com \
    --cc=brice.goglin@gmail.com \
    --cc=drepper@gmail.com \
    --cc=jbarnes@virtuousgeek.org \
    --cc=lenb@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=x86@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;
as well as URLs for NNTP newsgroup(s).