From: Matthew Wilcox <matthew@wil.cx>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Notes from LPC PCI/MSI BoF session
Date: Wed, 1 Oct 2008 09:00:50 -0600 [thread overview]
Message-ID: <20081001150050.GH13822@parisc-linux.org> (raw)
In-Reply-To: <200809221229.18501.jbarnes@virtuousgeek.org>
On Mon, Sep 22, 2008 at 12:29:18PM -0700, Jesse Barnes wrote:
> PCI address space management
> ----------------------------
> TJ has a bunch of code to improve address space management in Linux. We
> talked for a few minutes about this at the BoF; at this point I'm just
> waiting for TJ to post his stuff so we can start integrating it. Hopefully
> we can start merging small pieces of it (like the multiple PCI gap stuff) for
> 2.6.28, and get some more eyes on the more aggressive PCI-DMAR stuff he's
> been talking about soon.
>
> Well that's all I have in the way of notes. Feel free to add your own if I
> missed anything or correct me if I mischaracterized things.
One thing that wasn't resolved at the meeting was the question of 64-bit
addressing and PCI-PCI bridges (primarily because nobody had their
PCI-SIG login with them). I've now downloaded the latest PCI-PCI Bridge
spec and there are still no facilities to forward addresses >4GB (other
than the prefetchable region that was already in PPB 1.1).
--
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."
prev parent reply other threads:[~2008-10-01 15:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-22 19:29 Notes from LPC PCI/MSI BoF session Jesse Barnes
2008-09-24 5:51 ` Grant Grundler
2008-09-24 6:47 ` David Miller
2008-09-25 15:53 ` Grant Grundler
2008-09-24 15:44 ` Matthew Wilcox
2008-09-25 16:15 ` Grant Grundler
2008-10-01 15:00 ` Matthew Wilcox [this message]
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=20081001150050.GH13822@parisc-linux.org \
--to=matthew@wil.cx \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox