public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tony Camuso <tcamuso@redhat.com>
To: gregkh@suse.de, linux-kernel@vger.kernel.org,
	linux-pci@atrey.karlin.mff.cuni.cz, prarit@redhat.com,
	tcamuso@redhat.com
Subject: Re: [PATCH 0/5]PCI: x86 MMCONFIG - a couple of corrections to the preamble
Date: Sat, 22 Dec 2007 00:29:51 -0500	[thread overview]
Message-ID: <476CA0CF.3090607@redhat.com> (raw)
In-Reply-To: <20071222024044.26026.1461.sendpatchset@dhcp83-188.boston.redhat.com>

Some corrections to the preamble.

> The large amount of text is due to the nature of the
> problem and the discussion it engendered on the lkml.

Should say:

The large amount of text in the explanation below is due to
the nature of the problem and the discussion engendered on
lkml by my first submission.


> This patch-set detects the problem by comparing an MMCONFIG
> read to a Legacy PCI config read of the vendor/device dword
> of every device discovered during the PCI probing sequence.

Actually, the patch doesn't do a pci config read of EVERY device
discovered on every bus. Only on buses above a number defined
by PCI_MMCFG_MAX_CHECK_BUS and whose parent bus's pci_bus.ops
field points to pci_root_ops, which are mmconfig access routines
in systems in which mmconfig is the default mechanism.

In such cases where the parent bus pci_bus.ops field points
to pci_legacy_ops, the current bus does not need to be probed,
since its own pci_bus.ops field will inherit the pointer to
pci_legacy_ops from its parent.


           reply	other threads:[~2007-12-22  5:30 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20071222024044.26026.1461.sendpatchset@dhcp83-188.boston.redhat.com>]

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=476CA0CF.3090607@redhat.com \
    --to=tcamuso@redhat.com \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@atrey.karlin.mff.cuni.cz \
    --cc=prarit@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