From: Bjorn Helgaas <bjorn.helgaas@hp.com>
To: Yinghai Lu <yhlu.kernel@gmail.com>
Cc: Larry Finger <Larry.Finger@lwfinger.net>,
Gary Hade <garyhade@us.ibm.com>,
Jesse Barnes <jbarnes@virtuousgeek.org>,
Jaswinder Singh Rajput <jaswinder@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
Len Brown <lenb@kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: fixing "pci=use_crs"
Date: Wed, 23 Sep 2009 21:21:42 -0600 [thread overview]
Message-ID: <1253762502.12653.4.camel@dc7800.home> (raw)
In-Reply-To: <86802c440909231628t6b35aae4u706c0c35590bc0d3@mail.gmail.com>
On Wed, 2009-09-23 at 16:28 -0700, Yinghai Lu wrote:
> On Wed, Sep 23, 2009 at 4:23 PM, Bjorn Helgaas <bjorn.helgaas@hp.com> wrote:
> > P.S. Yinghai, you posted some patches earlier dealing with "only one
> > HT chain." You apparently have some insight into what's going on here,
> > but unfortunately, the changelogs mean absolutely nothing to me. Can
> > you give me any clues?
>
> which commit?
>
> normally we only need to have split root resource into several pieces
> when we have two HT chains or other io chains...
I meant the patches here:
http://lkml.org/lkml/2009/6/24/557
My opinion is that ACPI is there to give us an abstract description of
the machine, and we shouldn't have to introduce knowledge like "this
machine has two HT chains" or add checks in amd_bus.c about
"pci_root_num <= 1".
But maybe if I knew what an HT chain was and why you think it affects
the description returned by _CRS, it would give me a clue about how to
deal with this in a generic way.
Bjorn
next prev parent reply other threads:[~2009-09-24 3:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-16 23:15 Bjorn Helgaas
2009-09-17 16:16 ` Bjorn Helgaas
2009-09-17 16:45 ` Jesse Barnes
2009-09-17 18:57 ` Bjorn Helgaas
2009-09-19 17:08 ` Larry Finger
2009-09-21 21:20 ` Bjorn Helgaas
2009-09-22 23:35 ` Larry Finger
2009-09-23 23:23 ` Bjorn Helgaas
2009-09-23 23:28 ` Yinghai Lu
2009-09-24 3:21 ` Bjorn Helgaas [this message]
2009-09-24 4:42 ` Yinghai Lu
2009-09-24 13:24 ` Bjorn Helgaas
2009-09-24 22:03 ` Gary Hade
2009-09-24 15:26 ` Bjorn Helgaas
2009-09-25 21:00 ` Larry Finger
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=1253762502.12653.4.camel@dc7800.home \
--to=bjorn.helgaas@hp.com \
--cc=Larry.Finger@lwfinger.net \
--cc=garyhade@us.ibm.com \
--cc=jaswinder@kernel.org \
--cc=jbarnes@virtuousgeek.org \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=x86@kernel.org \
--cc=yhlu.kernel@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
all inboxes | Powered by JetHome®