linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Robert Hancock <hancockr@shaw.ca>
To: tcamuso@redhat.com
Cc: Greg KH <gregkh@suse.de>,
	linux-kernel@vger.kernel.org, linux-pci@atrey.karlin.mff.cuni.cz,
	"Chumbalkar, Nagananda" <Nagananda.Chumbalkar@hp.com>,
	Prarit Bhargava <prarit@redhat.com>,
	bnagendr@redhat.com
Subject: Re: [Fwd: Re: [PATCH 0/5]PCI: x86 MMCONFIG]
Date: Thu, 20 Dec 2007 20:15:52 -0600	[thread overview]
Message-ID: <476B21D8.2030602@shaw.ca> (raw)
In-Reply-To: <476B185D.3000409@redhat.com>

Tony Camuso wrote:
> Robert Hancock wrote:
> 
>> First off, I would like to see confirmation from the horses's mouths 
>> here (namely AMD, ServerWorks/Broadcom, and whoever else) that there 
>> is no other way to get around this problem than disabling MMCONFIG for 
>> accesses behind those chips.
>>
> 
> I happen to have this one stored in my desktop.
> 
>  From AMD-8132TM HyperTransportTM
>      PCI-X®2.0 Tunnel
>       Revision Guide
> 
> http://www.amd.com/us-en/assets/content_type/white_papers_and_tech_docs/30801.pdf 
> 
> 
> 79 AMD-8132TM Tunnel Lacks Extended Configuration
>         Space Memory-Mapped I/O Base Address Register
> 
> Description
> 
> Current AMD processors do not natively support PCI-defined extended 
> configuration space. A memory
> mapped I/O base address register (MMIO BAR) is required in chipset 
> devices to support extended
> configuration space. The AMD-8132 does not have this MMIO BAR.
> Potential Effect On System
> 
> The AMD-8132 is a PCI-X® Mode 2 capable device and requires the MMIO BAR 
> to support extended
> configuration space. Using a device which does have this MMIO BAR and an 
> AMD-8132 on the same
> HyperTransportTM link of the processor may cause firmware/software 
> problems.
> 
> The base configuration space of the AMD-8132 and PCI(-X) devices 
> attached to it are accessible using only
> the mechanism defined in PCI 2.3. Registers of PCI-X Mode 2 devices 
> attached to the AMD-8132 in the
> extended configuration space are not accessible. The AMD-8132 has no 
> registers in the extended
> configuration space.
> 
> Suggested Workaround
> 
> It is strongly recommended that system designers do not connect the 
> AMD-8132 and devices that use extended
> configuration space MMIO BARs (ex: HyperTransport-to-PCI Express® 
> bridges) to the same processor
> HyperTransport link.
> 
> Fix Planned
> No

That does sound fairly definitive. I have to wonder why certain system 
designers then didn't follow their strong recommendation..

-- 
Robert Hancock      Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/


  parent reply	other threads:[~2007-12-21  2:17 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.HvUNJ45qy60H427u0v9fNt3Gc7E@ifi.uio.no>
     [not found] ` <fa.uuzqvr64HFsgxfiWwhEmE16Di6c@ifi.uio.no>
     [not found]   ` <fa.zhxdNN/1rfQhfJLVmdGBjvKYrCM@ifi.uio.no>
     [not found]     ` <fa.z1qlON6DA9ubBPFdrEcaFTMgYOY@ifi.uio.no>
     [not found]       ` <fa.U/SCC1Gvd3nSOpkMu5vcsSPYyPE@ifi.uio.no>
     [not found]         ` <fa.d8kGTkzOZH22bXRIRiakqgOPBM4@ifi.uio.no>
2007-12-21  0:44           ` [Fwd: Re: [PATCH 0/5]PCI: x86 MMCONFIG] Robert Hancock
2007-12-21  1:35             ` Tony Camuso
2007-12-21  1:42               ` Tony Camuso
2007-12-21 14:59                 ` Bhavana Nagendra
2007-12-21  2:15               ` Robert Hancock [this message]
2007-12-21  2:44                 ` Tony Camuso
2007-12-21  3:40                 ` Loic Prylli
2007-12-21  4:07                   ` Tony Camuso
2007-12-21  2:09             ` Tony Camuso
2007-12-21 14:11             ` Andi Kleen
     [not found]           ` <fa.pdOcVPk2gFn5iK76ExRH6Ow+NPw@ifi.uio.no>
2007-12-22 16:41             ` Robert Hancock
2007-12-22 16:59               ` [Fwd: Re: [PATCH 4/5]PCI: x86 MMCONFIG] introduce pcibios_fix_bus_scan_quirk() Tony Camuso
     [not found] ` <fa.AlLzUeumrcT2SswgOn6MxKfDE0U@ifi.uio.no>
     [not found]   ` <fa.wIE0QfzMAxr82X049FecszlEnQY@ifi.uio.no>
     [not found]     ` <fa.2jJbe4cdXLfOVhNWVxdIjsW8GQc@ifi.uio.no>
     [not found]       ` <fa.JiW7yU0G/EdLOCYcPOacl/XVocc@ifi.uio.no>
     [not found]         ` <fa.PI93hBriZRT9ggytQ5eY/446Tno@ifi.uio.no>
2007-12-24 17:13           ` [Fwd: Re: [PATCH 0/5]PCI: x86 MMCONFIG] Robert Hancock
2007-12-20 12:28 Tony Camuso
  -- strict thread matches above, loose matches on Subject: below --
2007-12-20 12:28 Tony Camuso
2007-12-20 17:22 ` Greg KH
2007-12-20 17:35   ` Matthew Wilcox
2007-12-20 18:04     ` Tony Camuso
2007-12-20 18:16       ` Matthew Wilcox
2007-12-20 18:30         ` Tony Camuso
2007-12-20 18:36           ` Matthew Wilcox
2007-12-20 18:49         ` Loic Prylli
2007-12-20 19:04           ` Tony Camuso
2007-12-20 19:08             ` Matthew Wilcox
2007-12-20 19:50               ` Ivan Kokshaysky
2007-12-20 20:17                 ` Tony Camuso
2007-12-20 20:27                 ` Tony Camuso
2008-01-08  3:41                 ` Tony Camuso
2007-12-20 20:05               ` Loic Prylli
2007-12-20 20:15                 ` Matthew Wilcox
2007-12-20 20:56                   ` Loic Prylli
2007-12-20 21:00                     ` Matthew Wilcox
2007-12-20 21:55                       ` Loic Prylli
2007-12-20 19:37         ` Tony Camuso
2007-12-20 20:04           ` Matthew Wilcox
2007-12-20 20:15             ` Tony Camuso
2007-12-23 20:16         ` Loic Prylli
2007-12-23 20:55           ` Matthew Wilcox
2007-12-23 22:40             ` Loic Prylli
2007-12-24  8:09           ` Grant Grundler
2007-12-20 18:25   ` Tony Camuso
2007-12-20 21:57     ` Greg KH
2007-12-20 22:36       ` Tony Camuso
2007-12-20 22:40         ` Greg KH
2007-12-20 23:21           ` Tony Camuso
2007-12-21  2:07             ` Loic Prylli
2007-12-24  8:28           ` Grant Grundler

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=476B21D8.2030602@shaw.ca \
    --to=hancockr@shaw.ca \
    --cc=Nagananda.Chumbalkar@hp.com \
    --cc=bnagendr@redhat.com \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@atrey.karlin.mff.cuni.cz \
    --cc=prarit@redhat.com \
    --cc=tcamuso@redhat.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;
as well as URLs for NNTP newsgroup(s).