From: Keir Fraser <keir@xensource.com>
To: "Subrahmanian, Raj" <raj.subrahmanian@unisys.com>,
xen-devel@lists.xensource.com
Subject: Re: [PATCH] calling zap_low_mappings breaks xen boot on the es7000
Date: Thu, 24 May 2007 10:04:53 +0100 [thread overview]
Message-ID: <C27B13C5.F6DB%keir@xensource.com> (raw)
In-Reply-To: <94C8C9E8B25F564F95185BDA64AB05F60513EAC9@USTR-EXCH5.na.uis.unisys.com>
On 23/5/07 22:16, "Subrahmanian, Raj" <raj.subrahmanian@unisys.com> wrote:
>> Either we should just delay the zap_low_mappings() call, or
>> fix your code to map_domain_page()/unmap_domain_page(). How
>> late in boot do you need the low mappings?
>
> This patch delays the zap_low_mappings() call until after the
> smp_prepare_cpus call. With this patch, I am able to run Xen on the
> ES7000 and a Dell SC 1430.
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.
-- Keir
next prev parent reply other threads:[~2007-05-24 9:04 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 [this message]
2007-05-25 12:24 ` Subrahmanian, Raj
2007-05-25 12:39 ` Keir Fraser
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=C27B13C5.F6DB%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.