From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner+willy=40w.ods.org-S1751139AbVLCBjO@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1751139AbVLCBjO (ORCPT <rfc822;willy@w.ods.org>);
	Fri, 2 Dec 2005 20:39:14 -0500
Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1750775AbVLCBjO
	(ORCPT <rfc822;linux-kernel-outgoing>);
	Fri, 2 Dec 2005 20:39:14 -0500
Received: from havoc.gtf.org ([69.61.125.42]:44192 "EHLO havoc.gtf.org")
	by vger.kernel.org with ESMTP id S1751139AbVLCBjN (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Fri, 2 Dec 2005 20:39:13 -0500
Date: Fri, 2 Dec 2005 20:39:04 -0500
From: Jeff Garzik <jgarzik@pobox.com>
To: linux-kernel@vger.kernel.org
Cc: gregkh@suse.de, ak@suse.de
Subject: [PATCH 0/3] x86 PCI domain support
Message-ID: <20051203013904.GA2560@havoc.gtf.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4.1i
Sender: linux-kernel-owner@vger.kernel.org
X-Mailing-List: linux-kernel@vger.kernel.org


ACPI PCI support stopped short of supporting multiple PCI domains,
which is something I need in order to support a current machine
configuration, and something many will soon need, to support upcoming
systems.

This is a minimal, untested implementation.  But it should work,
provided your PCI op hooks (direct, BIOS, mmconfig) support PCI domains
(mmconfig).

Patches:

1) Fix: don't hardcode PCI domain to zero
2) Introduce struct pci_sysdata
3) Add PCI domain to struct pci_sysdata