public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Grant Grundler <grundler@parisc-linux.org>
To: Michael Chan <mchan@broadcom.com>
Cc: Andi Kleen <ak@suse.de>,
	Grant Grundler <grundler@parisc-linux.org>,
	linux-kernel@vger.kernel.org, linux-pci@atrey.karlin.mff.cuni.cz,
	akpm@osdl.org, greg@kroah.com, "Durairaj,
	Sundarapandian" <sundarapandian.durairaj@intel.com>
Subject: Re: [PATCH] pci-mmconfig fix for 2.6.9
Date: Sat, 13 Nov 2004 12:46:34 -0700	[thread overview]
Message-ID: <20041113194634.GC3023@colo.lackof.org> (raw)
In-Reply-To: <B1508D50A0692F42B217C22C02D849720312DED3@NT-IRVA-0741.brcm.ad.broadcom.com>

On Sat, Nov 13, 2004 at 08:22:50AM -0800, Michael Chan wrote:
> > If I got the discussion so far correctly then the PCI-SGI spec does not
> > guarantee that there is no posting, but you know that the chipset
> > you are using right now doesn't do it.
> 
> Yes, that's my understanding of the spec. Grant Grundler does not agree
>  and thinks that non-posting is the only compliant implementation.

That's not what I said. I think we do agree. I'll rephrase.
The code currently in arch/i386 and arch/x86_64 support a chipset that
is compliant with the part of the spec that requires non-postable
config writes.

Other chipsets can implement postable config space. To be compliant
with the ECN, the architecture must define a method to guarantee
the posted writes have reached the target device. I think the
ECN we've been talking about assumes that method will be implemented
in firmware somehow and NOT as a direct access method in the OS.

> I wish he was right as it would be the easiest to deal with.
> We contacted Intel about the out-of-spec readl when writing to
> the PMCSR to change power state as they were the original author
> of the mmconfig code. Their solution was to remove the readl after
> confirming that mmconfig was non-posted on their chipsets.

That means someone has to introduce a new method to access
mmconfig if they implement postable writes.

hth,
grant

  reply	other threads:[~2004-11-13 19:46 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-13 16:22 [PATCH] pci-mmconfig fix for 2.6.9 Michael Chan
2004-11-13 19:46 ` Grant Grundler [this message]
2004-11-14  8:58   ` Andi Kleen
2004-11-15  6:00     ` Grant Grundler
2004-11-15  8:33       ` Andi Kleen
  -- strict thread matches above, loose matches on Subject: below --
2004-11-15  7:07 Michael Chan
2004-11-15  8:01 ` Grant Grundler
2004-11-12 23:56 Michael Chan
2004-11-13  9:22 ` Andi Kleen
2004-11-12 21:49 Michael Chan
2004-11-12 22:31 ` Grant Grundler
2004-11-12 19:23 Michael Chan
2004-11-12 20:55 ` Grant Grundler
2004-11-12 17:52 Michael Chan
2004-11-12 18:35 ` Grant Grundler
2004-11-11 16:33 Nguyen, Tom L
2004-11-10 22:20 long
2004-11-11  1:30 ` Greg KH
2004-11-11  7:57 ` Andi Kleen
2004-11-10 19:38 long
2004-11-10 19:35 ` Greg KH
2004-11-10 17:26 Durairaj, Sundarapandian
2004-11-10 17:35 ` Greg KH

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=20041113194634.GC3023@colo.lackof.org \
    --to=grundler@parisc-linux.org \
    --cc=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@atrey.karlin.mff.cuni.cz \
    --cc=mchan@broadcom.com \
    --cc=sundarapandian.durairaj@intel.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