public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Jes Sorensen <jes@wildopensource.com>
To: linux-ia64@vger.kernel.org
Subject: Re: pgprot_writecombine & shub 1.x
Date: Thu, 20 Jan 2005 09:03:19 +0000	[thread overview]
Message-ID: <yq0fz0wbhgo.fsf@jaguar.mkp.net> (raw)
In-Reply-To: <200501111200.02504.jbarnes@sgi.com>

>>>>> "David" = David Mosberger <davidm@napali.hpl.hp.com> writes:

>>>>> On Wed, 19 Jan 2005 09:28:27 -0800, Jesse Barnes <jbarnes@sgi.com> said:
Jesse> So I guess we need to add ia64_set_page_wc() and
Jesse> ia64_set_page_uc() functions that set the appropriate page bits
Jesse> or return errors if the EFI memory map says a particular mode
Jesse> isn't allowed?  How does that sound to you, Tony & David?
Jesse> Fortunately there aren't that many users of pgprot_writecombine
Jesse> so fixing them up should be easy.

David> I'm still not clear which case you're concerned about: mapping
David> I/O memory with WC or mapping real memory with WC.  For the
David> latter, I think we may need an API to allocate memory that can
David> be mapped WC (if possible at all).

Hmmm,

What about real memory and mapping it uncached? Do we need to play the
same trick before allowing it to be mapped uncached? and for IO memory
mapped uncached?

Trying to map real memory uncached was what made me stumble upon the
PREFETCH_VISIBILITY limitation in the PAL code.

Cheers,
Jes

  parent reply	other threads:[~2005-01-20  9:03 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-11 20:00 pgprot_writecombine & shub 1.x Jesse Barnes
2005-01-11 22:12 ` David Mosberger
2005-01-11 22:35 ` Jesse Barnes
2005-01-12 18:51 ` Jim Hull
2005-01-12 19:31 ` Hugo Kohmann
2005-01-12 19:32 ` Jesse Barnes
2005-01-12 21:54 ` David Mosberger
2005-01-19 17:28 ` Jesse Barnes
2005-01-19 17:53 ` David Mosberger
2005-01-19 17:56 ` Jesse Barnes
2005-01-19 18:04 ` David Mosberger
2005-01-19 18:16 ` Luck, Tony
2005-01-19 18:21 ` Jesse Barnes
2005-01-19 18:38 ` Luck, Tony
2005-01-19 19:33 ` Bjorn Helgaas
2005-01-19 21:51 ` Jesse Barnes
2005-01-19 22:00 ` Luck, Tony
2005-01-19 22:03 ` Jesse Barnes
2005-01-19 22:07 ` David Mosberger
2005-01-19 22:16 ` Jesse Barnes
2005-01-19 22:20 ` David Mosberger
2005-01-19 22:22 ` Jesse Barnes
2005-01-19 22:25 ` David Mosberger
2005-01-19 22:36 ` Jesse Barnes
2005-01-19 22:39 ` David Mosberger
2005-01-19 22:53 ` Jesse Barnes
2005-01-20  9:03 ` Jes Sorensen [this message]
2005-01-20 13:43 ` Hugo Kohmann
2005-01-20 16:42 ` Jesse Barnes
2005-01-20 16:45 ` Jesse Barnes
2005-01-20 17:17 ` David Mosberger
2005-01-21  9:00 ` Jes Sorensen
2005-01-21  9:01 ` 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=yq0fz0wbhgo.fsf@jaguar.mkp.net \
    --to=jes@wildopensource.com \
    --cc=linux-ia64@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