All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgunthorpe@obsidianresearch.com>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: "linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>
Subject: Re: [PATCH 1/2] PCI: Prevent bus conflicts while checking for bridge apertures
Date: Mon, 9 Dec 2013 13:15:37 -0700	[thread overview]
Message-ID: <20131209201537.GJ5429@obsidianresearch.com> (raw)
In-Reply-To: <CAErSpo5ab6buYa9GvpYECeeCwhYATt6dVePD6Cov-75kQndf4g@mail.gmail.com>

On Mon, Dec 09, 2013 at 01:00:36PM -0700, Bjorn Helgaas wrote:

> I don't think it's 100% spec compliant because the spec allows
> PCI_COMMAND_IO to be set if the bridge has an enabled I/O BAR but does
> not support an I/O aperture.  I admit I have never seen such a device,
> and I doubt one exists :)

Yes, fair enough!

Jason

  reply	other threads:[~2013-12-09 20:15 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-06  0:19 [PATCH 0/2] Bridge window discovery and setup fixes Bjorn Helgaas
2013-12-06  0:19 ` [PATCH 1/2] PCI: Prevent bus conflicts while checking for bridge apertures Bjorn Helgaas
2013-12-09 19:31   ` Jason Gunthorpe
2013-12-09 20:00     ` Bjorn Helgaas
2013-12-09 20:15       ` Jason Gunthorpe [this message]
2013-12-06  0:19 ` [PATCH 2/2] PCI: Stop clearing bridge Secondary Status when setting up I/O aperture Bjorn Helgaas
2013-12-09 19:33   ` Jason Gunthorpe
2013-12-09 20:15     ` Bjorn Helgaas
2013-12-09 21:27       ` Jason Gunthorpe
2013-12-09 21:58         ` Bjorn Helgaas
2013-12-10  0:10           ` Jason Gunthorpe
2013-12-10  0:18             ` Bjorn Helgaas
2013-12-10  1:31               ` Jason Gunthorpe
2013-12-10 18:22                 ` Bjorn Helgaas

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=20131209201537.GJ5429@obsidianresearch.com \
    --to=jgunthorpe@obsidianresearch.com \
    --cc=bhelgaas@google.com \
    --cc=linux-pci@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.