All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bjorn Helgaas <bjorn.helgaas@hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH] (2.4.21-bjorn-bk) Minimalist PAL mapping for SN2
Date: Thu, 17 Jul 2003 17:42:23 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105846378209951@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105832171829546@msgid-missing>

On Tuesday 15 July 2003 8:14 pm, Christopher Wedgwood wrote:
> Altix/SN2 presently has the PAL located in a granule that has mixed
> cachability --- for this reason we need to map the PAL using the
> smallest mapping possible.

We had a big discussion inside HP a while back about a similar
issue (firmware reported a region that required run-time mapping
inside a granule that also contained a hole).  We pushed hard to
make everything inside a granule have the same attributes.

Given that you're stuck with this situation:

- I hate to clutter the generic efi.c with so much platform-
  specific stuff.  What are the implications of making this
  a platform vector?  I don't see any obvious dependencies that
  prevent us from doing machvec_init() earlier.

- As Tony mentioned, you might want to verify that there's nothing
  else in the granule that requires run-time mapping.

- If there are different cacheability attributes within a granule,
  efi_memmap_walk should remove the granule from efi_memmap.  Do
  you see that happening?  I guess since PAL is mapped with a TR,
  we probably can live without it being in the EFI memmap, but since
  we use the memmap to validate accesses to /dev/mem, the wrong
  thing will probably happen if you try to read the PAL space.

Bjorn


  parent reply	other threads:[~2003-07-17 17:42 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-16  2:14 [PATCH] (2.4.21-bjorn-bk) Minimalist PAL mapping for SN2 Christopher Wedgwood
2003-07-16 15:22 ` Luck, Tony
2003-07-16 18:23 ` Christopher Wedgwood
2003-07-17 17:42 ` Bjorn Helgaas [this message]
2003-07-17 17:57 ` Christopher Wedgwood
2003-07-17 22:52 ` Bjorn Helgaas
2003-07-18  2:22 ` Christopher Wedgwood
2003-07-18 16:13 ` Bjorn Helgaas
2003-07-19  1:05 ` Christopher Wedgwood
2003-07-22  1:38 ` Bjorn Helgaas
2003-07-22 21:26 ` Christopher Wedgwood

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=marc-linux-ia64-105846378209951@msgid-missing \
    --to=bjorn.helgaas@hp.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 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.