All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keir Fraser <keir@xensource.com>
To: "Subrahmanian, Raj" <raj.subrahmanian@unisys.com>,
	xen-devel@lists.xensource.com
Subject: Re: RE: [PATCH] calling zap_low_mappings breaks xen boot on the es7000
Date: Fri, 25 May 2007 13:39:51 +0100	[thread overview]
Message-ID: <C27C97A7.F848%keir@xensource.com> (raw)
In-Reply-To: <94C8C9E8B25F564F95185BDA64AB05F60513F2EC@USTR-EXCH5.na.uis.unisys.com>

On 25/5/07 13:24, "Subrahmanian, Raj" <raj.subrahmanian@unisys.com> wrote:

>> So where is the late low-memory access happening? There's not
>> that much es7000-specific code. It can't be hard to fix
>> properly. If the physical pointer is known to be below 1MB you
>> can just __va() it. If not you may need to use a fixmap, or
>> acpi_map_table, or just __va() only on x86_64. I'd like to
>> keep the zap as early as possible to catch truly erroneous low
>> pointers.
> I will look into that code and fix it.
> If you don't mind me asking, what exactly does zap_low_mappings do? I am
> not able to figure it out looking at the code.

It removes the 1:1 mapping of physical memory at virtual address 0x0.

 -- Keir

  reply	other threads:[~2007-05-25 12:39 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-14 15:23 [PATCH] x86/hvm: determine shared info format earlier Jan Beulich
2007-05-15  6:59 ` Keir Fraser
2007-05-15  7:13   ` Jan Beulich
2007-05-15  7:16     ` Keir Fraser
2007-05-15  7:24       ` Jan Beulich
2007-05-18 19:20   ` [PATCH] calling zap_low_mappings breaks xen boot on the es7000 Subrahmanian, Raj
2007-05-19  8:19     ` Keir Fraser
2007-05-23 21:16       ` Subrahmanian, Raj
2007-05-24  9:04         ` Keir Fraser
2007-05-25 12:24           ` Subrahmanian, Raj
2007-05-25 12:39             ` Keir Fraser [this message]
2007-06-14 17:58           ` Subrahmanian, Raj
2007-06-14 18:12             ` Keir Fraser

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=C27C97A7.F848%keir@xensource.com \
    --to=keir@xensource.com \
    --cc=raj.subrahmanian@unisys.com \
    --cc=xen-devel@lists.xensource.com \
    /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.