public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: "Robert Richter" <robert.richter@amd.com>
Cc: "Andreas Herrmann" <andreas.herrmann3@amd.com>,
	patches@x86-64.org, linux-kernel@vger.kernel.org
Subject: Re: [patches] [patch 3/5] x86: Add PCI extended config space access for AMD Barcelona
Date: Mon, 3 Sep 2007 14:48:41 +0200	[thread overview]
Message-ID: <200709031448.42285.ak@suse.de> (raw)
In-Reply-To: <20070903112746.GH7916@erda.amd.com>

On Monday 03 September 2007 13:27, Robert Richter wrote:

> On 03.09.07 12:15:03, Andi Kleen wrote:
> > > But it is needed for some devices for full functionality.
> >
> > Examples? I can only think of PCI express error reporting, which
> > few drivers implement anyways and isn't really a show stopper
> > if it doesn't work. Besides I would be surprised if it even works
> > on the cheap desktop boards which have MCFG less BIOS.
>
> As you say, there are BIOSs that do not support MMCONFIG. Thus, CF8
> access is not only a workaround to boot a system. 

We're talking about accessing the extended part of config spaces. I'm not 
aware of any case where that is required to boot a system.

> Recent (10h) and upcomming CPU families make heavy use of PCI ext cfg
> space for certain CPU features. Setup of the extended interupt local
> vector table for IBS (used with Perfmon2) is one example. CPU
> designers do not take care anymore if a feature is in the base or
> extended config space. So access to PCI ECS is essential.

I don't think it's a big issue if IBS doesn't work on a few buggy BIOS
(which should hopefully become fewer anyways because Vista is out
which actually uses MCFG) 


> > > IMHO it is best to try to use MMCONFIG if it's working and to use
> > > a fallback (e.g. CF8 ECS access for family 0x10) if available.
> >
> > We only put in workarounds if there is a serious problem otherwise (e.g.
> > not booting etc.). I just don't see this here.
>
> As said above, I do not see CF8 access as a workaround. I expect my
> system to work in the same way also if MMCONFIG is not available.

It should boot sure, but exotic stuff not working is not a major issue

-Andi

  reply	other threads:[~2007-09-03 12:54 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20070830174311.221133000@amd.com>
     [not found] ` <20070830174311.536394000@amd.com>
2007-09-01 10:11   ` [patch 3/5] x86: Add PCI extended config space access for AMD Barcelona Andi Kleen
2007-09-03  8:32     ` [patches] " Andreas Herrmann
2007-09-03 10:15       ` Andi Kleen
2007-09-03 11:27         ` Robert Richter
2007-09-03 12:48           ` Andi Kleen [this message]
2007-09-03 14:48             ` Robert Richter
2007-09-03 15:24               ` Andi Kleen
2007-09-04  6:54             ` Yinghai Lu
2007-09-04  7:20               ` Andi Kleen
2007-09-03 11:31         ` Andreas Herrmann
2007-09-03 12:52           ` Andi Kleen
     [not found] ` <20070830174311.344418000@amd.com>
2007-09-01 10:14   ` [patch 1/5] x86: Add AMD64 Barcelona PMU MSR definitions Andi Kleen
2007-09-03  8:17 [patch 0/5] (resent) x86: PCI extended config space access on AMD Barcelona CPUs Robert Richter
2007-09-03  8:17 ` [patch 3/5] x86: Add PCI extended config space access for AMD Barcelona Robert Richter
2007-09-03  8:31   ` Arjan van de Ven
2007-09-03  9:17     ` [patches] " Andreas Herrmann
2007-09-03 11:33       ` Arjan van de Ven
2007-09-03 15:47         ` Andreas Herrmann
2007-09-05  5:58           ` H. Peter Anvin
2007-09-05  8:44             ` Robert Richter
2007-09-05 10:12               ` H. Peter Anvin
2007-09-05 10:35                 ` Robert Richter
2007-09-05 11:05                 ` Arne Georg Gleditsch
2007-09-05 16:13                   ` Andreas Herrmann
2007-09-05 22:42                     ` Yinghai Lu
2007-09-06  8:31                       ` Arne Georg Gleditsch
2007-09-06  9:48                         ` H. Peter Anvin
2007-09-06 17:41                           ` Jesse Barnes
2007-09-06 17:50                             ` Yinghai Lu
2007-09-06 17:48                               ` Jesse Barnes
2007-09-06 17:48                           ` Yinghai Lu
2007-09-05 15:00             ` Andreas Herrmann
2007-09-06 10:14               ` Arjan van de Ven

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=200709031448.42285.ak@suse.de \
    --to=ak@suse.de \
    --cc=andreas.herrmann3@amd.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=patches@x86-64.org \
    --cc=robert.richter@amd.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