From: Matthew Wilcox <matthew@wil.cx>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: linux-pci@vger.kernel.org, Prarit Bhargava <prarit@redhat.com>,
Jesse Barnes <jbarnes@virtuousgeek.org>,
Matthew Wilcox <matthew.wilcox@linux.intel.com>,
Don Dutile <ddutile@redhat.com>, Myron Stowe <mstowe@redhat.com>,
James Paradis <jim.paradis@stratus.com>
Subject: Re: [PATCH v1] PCI: work around Stratus ftServer broken PCIe hierarchy
Date: Sat, 28 Apr 2012 13:26:00 -0600 [thread overview]
Message-ID: <20120428192559.GB28349@parisc-linux.org> (raw)
In-Reply-To: <20120425233632.12292.32916.stgit@bhelgaas.mtv.corp.google.com>
On Wed, Apr 25, 2012 at 05:36:32PM -0600, Bjorn Helgaas wrote:
> @@ -2161,6 +2161,9 @@ bytes respectively. Such letter suffixes can also be entirely omitted.
> on: Turn realloc on
> realloc same as realloc=on
> noari do not use PCIe ARI.
> + pcie_scan_all Scan all possible PCIE devices. Otherwise we
> + only look for one device below a PCIE downstream
> + port.
We should probably s/device/slot/ throughout. I've recently become
aware of a hype-rvisor that doesn't include PCI device number remapping,
so if you assign, say, function 03.6 to a guest, the PCI scanning code
doesn't find it.
--
Matthew Wilcox Intel Open Source Technology Centre
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours. We can't possibly take such
a retrograde step."
next prev parent reply other threads:[~2012-04-28 19:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-25 23:36 [PATCH v1] PCI: work around Stratus ftServer broken PCIe hierarchy Bjorn Helgaas
2012-04-26 0:30 ` Yinghai Lu
2012-04-26 12:29 ` Prarit Bhargava
2012-04-26 14:41 ` Bjorn Helgaas
2012-04-26 12:24 ` Prarit Bhargava
2012-04-27 3:35 ` Wei Yang
2012-04-27 14:21 ` Bjorn Helgaas
2012-04-28 19:26 ` Matthew Wilcox [this message]
2012-04-30 21:38 ` 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=20120428192559.GB28349@parisc-linux.org \
--to=matthew@wil.cx \
--cc=bhelgaas@google.com \
--cc=ddutile@redhat.com \
--cc=jbarnes@virtuousgeek.org \
--cc=jim.paradis@stratus.com \
--cc=linux-pci@vger.kernel.org \
--cc=matthew.wilcox@linux.intel.com \
--cc=mstowe@redhat.com \
--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 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.