Date: Tue, 30 Oct 2007 15:44:51 -0700 (PDT)
Message-Id: <20071030.154451.128207404.davem@davemloft.net>
To: jbarnes@virtuousgeek.org
Cc: torvalds@linux-foundation.org, arjan@infradead.org, hancockr@shaw.ca,
       greg@kroah.com, akpm@linux-foundation.org, ak@suse.de,
       rajesh.shah@intel.com, linux-kernel@vger.kernel.org
Subject: Re: pci-disable-decode-of-io-memory-during-bar-sizing.patch
From: David Miller <davem@davemloft.net>
In-Reply-To: <200710301531.58957.jbarnes@virtuousgeek.org>
References: <200710301504.36972.jbarnes@virtuousgeek.org>
	<alpine.LFD.0.999.0710301518570.30120@woody.linux-foundation.org>
	<200710301531.58957.jbarnes@virtuousgeek.org>
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 977
Lines: 22

From: Jesse Barnes <jbarnes@virtuousgeek.org>
Date: Tue, 30 Oct 2007 15:31:57 -0700

> I don't disagree there.  I'm just saying the actual mechanism is fine 
> (as illustrated by the numerous non-PC ports of Linux), and this 
> particular problem, at least, isn't really specific to how MMCONFIG is 
> described or configured by the firmware and OS, it's simply a Linux 
> problem.

I totally disagree, it is not a Linux problem.

The non-PC ports don't have this issue because the PCI config space
MMIO area of the PCI controller does not overlap PCI MMIO space at
all.  So the problem simply cannot happen.

They choose to put this MMCONFIG in an area overlapping with PCI MMIO
space, which breaks both existing practice and code.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/