public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Andi Kleen <ak@suse.de>
Cc: "Brown, Len" <len.brown@intel.com>,
	torvalds@osdl.org, akpm@osdl.org, linux-kernel@vger.kernel.org,
	gregkh@suse.de
Subject: Re: [PATCH for 2.6.17] [3/5] i386/x86_64: Force pci=noacpi on HP XW9300
Date: Mon, 15 May 2006 13:17:20 -0400	[thread overview]
Message-ID: <4468B7A0.2040309@pobox.com> (raw)
In-Reply-To: <200605151905.42105.ak@suse.de>

Andi Kleen wrote:
> On Monday 15 May 2006 18:47, Brown, Len wrote:
>>> The system has multiple PCI segments and we don't handle that properly
>>> yet in PCI and ACPI. Short term before this is fixed blacklist it to
>>> pci=noacpi.
>> I'm okay with the patch, but it makes me wonder...
>>
>> Is this the 1st/only system 
> 
> x86-
> 
> IA64/PA-RISC support subdomains successfully
> 
>> Linux has run on with multiple PCI segments? 
> 
> I think IBM summit somehow uses it too.
> 
> And there is a patch from Jeff Garzik I think to make the xw9300 subdomains 
> work (or rather implement subdomain support in arch/i386/pci/*), but it 
> breaks the Summit and possibly other non x86 systems. Greg 
> should know details about that.
> 
> As usual the systems usually boot even without this patch, but you can't 
> reach all PCI devices.
> 
>> What are your expectations for where "short-term" ends and "long-term"
>> begins?
> 
> I think Greg has Jeff's patch still queued somewhere, but it needs
> to be debugged to work everywhere. After that is done we can drop the blacklist 
> entry. Hopefully for 2.6.19?
> 
> For 2.6.17 I don't see any alternative to blacklisting.
> 
> -Andi
> 
> 


FWIW I also maintain this "PCI domain support for x86" stuff in a 
separate branch, which I keep up to date:

'pciseg' branch of
  git://git.kernel.org/pub/scm/linux/kernel/git/jgarzik/misc-2.6.git

Haven't done anything substantive since the original implementation, 
just kept up with recent kernels.

The xw9300 continues to be my primary workstation (2x2 Opteron), but 
haven't found time to mess with PCI domains in a while.  The BIOS gives 
me the option to disable PCI domains, so I took the slack way out :)

	Jeff



  reply	other threads:[~2006-05-15 17:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-15 16:47 [PATCH for 2.6.17] [3/5] i386/x86_64: Force pci=noacpi on HP XW9300 Brown, Len
2006-05-15 17:05 ` Andi Kleen
2006-05-15 17:17   ` Jeff Garzik [this message]
2006-05-18 15:56 ` Greg KH
  -- strict thread matches above, loose matches on Subject: below --
2006-05-15 16:19 Andi Kleen

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=4468B7A0.2040309@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=gregkh@suse.de \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.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