All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy@debian.org>
To: Grant Grundler <grundler@parisc-linux.org>
Cc: Joel Soete <joel.soete@tiscali.be>,
	"Conan C. Albrecht" <conan_albrecht@byu.edu>,
	parisc-linux@lists.parisc-linux.org,
	debian-hppa@lists.debian.org
Subject: Re: [parisc-linux] Re: Debian on rp 7400
Date: Fri, 8 Aug 2003 18:56:13 +0100	[thread overview]
Message-ID: <20030808175613.GP22222@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <20030808163744.GA29158@dsl2.external.hp.com>

On Fri, Aug 08, 2003 at 10:37:44AM -0600, Grant Grundler wrote:
> On Fri, Aug 08, 2003 at 09:10:44AM +0000, Joel Soete wrote:
> > >IIRC, "non-equivalently mapped aliases" 
> 
> > Is there much more detailed public doc some where about this stuff?
> 
> sorry - I don't understand the problems well enough.
> The PA 2.0 arch book might describe the cache behaviors sufficiently
> to determine this will be a problem.

You're looking for the section "Address Aliasing" starting on page F-5.
For the dead-tree-non-enabled, it's covered at
http://h21007.www2.hp.com/dspp/tech/tech_TechDocumentDetailPage_IDX/1,1701,959!218!244,00.html

Note that the book has some small errata in this section; the copy on
the web has these errata corrected.

Also note that the use of space bits in generating the cache index
is disabled.

Also note that the 16MB boundary discussed is relaxed to 4MB.

> I only partially understand what Jerry talking about and have no idea
> how linux VM implementation collides with the aliasing rules.

User mappings of shared pages are equivalently aliased.  The kernel's
view of user pages is a non-equivalent alias.  We could (ab)use kmap()
to ensure the kernel only accesses user pages through equivalent aliases,
but that requires quite some work.

-- 
"It's not Hollywood.  War is real, war is primarily not about defeat or
victory, it is about death.  I've seen thousands and thousands of dead bodies.
Do you think I want to have an academic debate on this subject?" -- Robert Fisk

  parent reply	other threads:[~2003-08-08 17:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <25EEF58E-C82D-11D7-8F19-00039398B282@byu.edu>
     [not found] ` <20030806205220.GA6353@dsl2.external.hp.com>
     [not found]   ` <3F336914.5020305@tiscali.be>
2003-08-08 16:37     ` [parisc-linux] Re: Debian on rp 7400 Grant Grundler
2003-08-08 17:56       ` Matthew Wilcox
2003-08-08 17:56       ` Matthew Wilcox [this message]
2003-08-08 20:46       ` Joel Soete
2003-08-08 20:46       ` Joel Soete
2003-08-08 22:40       ` Bjorn Helgaas
2003-08-11 15:11         ` Joel Soete
2003-08-11 15:11         ` Joel Soete
2003-08-08 22:40       ` Bjorn Helgaas
2003-08-08 16:37     ` Grant Grundler

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=20030808175613.GP22222@parcelfarce.linux.theplanet.co.uk \
    --to=willy@debian.org \
    --cc=conan_albrecht@byu.edu \
    --cc=debian-hppa@lists.debian.org \
    --cc=grundler@parisc-linux.org \
    --cc=joel.soete@tiscali.be \
    --cc=parisc-linux@lists.parisc-linux.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.