From: Bjorn Helgaas <bjorn.helgaas@hp.com>
To: Jes Sorensen <jes@sgi.com>
Cc: Robin Holt <holt@sgi.com>, Andi Kleen <ak@suse.de>,
linux-kernel@vger.kernel.org,
Nick Piggin <nickpiggin@yahoo.com.au>,
Hugh Dickins <hugh@veritas.com>, Carsten Otte <cotte@de.ibm.com>,
bjorn_helgaas@hp.com
Subject: Re: [patch] do_no_pfn
Date: Tue, 20 Jun 2006 10:03:52 -0600 [thread overview]
Message-ID: <200606201003.52307.bjorn.helgaas@hp.com> (raw)
In-Reply-To: <4497AB46.4000402@sgi.com>
On Tuesday 20 June 2006 02:01, Jes Sorensen wrote:
> Robin Holt wrote:
> > On Mon, Jun 19, 2006 at 03:06:05PM +0200, Andi Kleen wrote:
> >> The big question is - why do you have pages without struct page?
> >> It seems ... wrong.
> ...
> Note that Bjorn Helgas has a case where he needs this as well.
I do have a case where I used pages without struct pages, but
I don't really like the implementation, and I'd love to have
someone who knows about VM tell me "no, dummy, you should do it
this way instead."
Here's the scenario: I'm trying to implement
/sys/class/pci_bus/DDDD:BB/legacy_mem so we can run X servers
on multiple VGA cards. The chipset (used in HP parisc and ia64
boxes) supports multiple PCI root bridges, and it routes the
VGA legacy MMIO space at 0xA0000-0xBFFFF to one of them.
This region is MMIO, so there are no struct pages for it. I can
easily mmap the space for the first VGA device. But to support
a second device, I have to be able to invalidate the mappings
for the first device, twiddle stuff in the chipset, and make new
mappings for the second device. And of course I have to do the
reverse (invalidate mappings of second device, twiddle chipset,
map first device) when the first X server faults on the frame
buffer.
Basically, only one of the /sys/class/pci_bus/DDDD:BB/legacy_mem
files can have an active mmap at a time, and I haven't figured
out a good way to do the mutual exclusion.
Bjorn
next prev parent reply other threads:[~2006-06-20 16:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-19 9:19 Jes Sorensen
2006-06-19 13:06 ` Andi Kleen
2006-06-19 22:49 ` Robin Holt
2006-06-20 8:01 ` Jes Sorensen
2006-06-20 8:13 ` Andi Kleen
2006-06-20 8:40 ` Jes Sorensen
2006-06-20 8:48 ` Andi Kleen
2006-06-20 9:12 ` Jes Sorensen
2006-06-20 9:35 ` Andi Kleen
2006-06-20 11:02 ` Robin Holt
2006-06-21 9:50 ` Jes Sorensen
2006-06-20 16:03 ` Bjorn Helgaas [this message]
2006-06-21 7:38 ` Carsten Otte
2006-06-20 8:58 ` Carsten Otte
2006-06-27 12:46 ` [patch] do_no_pfn - against latest git Jes Sorensen
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=200606201003.52307.bjorn.helgaas@hp.com \
--to=bjorn.helgaas@hp.com \
--cc=ak@suse.de \
--cc=bjorn_helgaas@hp.com \
--cc=cotte@de.ibm.com \
--cc=holt@sgi.com \
--cc=hugh@veritas.com \
--cc=jes@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nickpiggin@yahoo.com.au \
/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
all inboxes | Powered by JetHome®