All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: RE: [Linux-ia64] [PATCH]ACPI fACS global lock & virtual memmap
Date: Thu, 07 Nov 2002 03:13:16 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590709805347@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590709805326@msgid-missing>

>>>>> On Wed, 6 Nov 2002 20:52:40 -0600 , "Sluder, Charles" <Charles.Sluder@UNISYS.com> said:

  Chuck> I tried the patch and it gets rid of the panic.  Before and
  Chuck> after dumps of the memory map are below. The SAL and ACPI
  Chuck> tables are being trimmed from the memory map. That is why the
  Chuck> FACS global lock is mapped uncached. Debug from
  Chuck> acpi_map_os_memory is also include below.

  Chuck> Shouldn't the trim code ignore runtime memory?

No, it can't ignore it.  There is a real problem here: the ACPI table
lies in a 64MB granule which has a hole (because of the missing 4KB
page at 0x000000007ffff000).  Because of that, the kernel simply
cannot safely access that memory via a write-back mapping (the reason
is that the processor prefetch or a speculative load might otherwise
access the hole and MCA while doing that).

So as it stands, Linux simply won't be able to work correctly on a
machine with this kind of memory map.  Can you move the firmware
tables to a granule which is fully populated?

	--david


  parent reply	other threads:[~2002-11-07  3:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-01 22:14 [Linux-ia64] [PATCH]ACPI fACS global lock & virtual memmap Sluder, Charles
2002-11-04 15:45 ` Van Maren, Kevin
2002-11-06 17:32 ` David Mosberger
2002-11-06 23:31 ` David Mosberger
2002-11-06 23:35 ` David Mosberger
2002-11-07  2:52 ` Sluder, Charles
2002-11-07  3:13 ` David Mosberger [this message]
2002-11-07 18:02 ` Sluder, Charles

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-105590709805347@msgid-missing \
    --to=davidm@napali.hpl.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.