From: "H. Peter Anvin" <hpa@zytor.com>
To: Konrad Rzeszutek Wilk <konrad@kernel.org>
Cc: Jacob Shin <jacob.shin@amd.com>, X86-ML <x86@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Yinghai Lu <yinghai@kernel.org>,
Andreas Herrmann <andreas.herrmann3@amd.com>,
Tejun Heo <tj@kernel.org>,
Borislav Petkov <borislav.petkov@amd.com>,
Dave Young <dyoung@redhat.com>, Chao Wang <chaowang@redhat.com>,
Vivek Goyal <vgoyal@redhat.com>
Subject: Re: [PATCH 3/4] x86: Only direct map addresses that are marked as E820_RAM
Date: Thu, 23 Aug 2012 14:23:51 -0700 [thread overview]
Message-ID: <50369F67.8040101@zytor.com> (raw)
In-Reply-To: <20120823201224.GA24203@phenom.dumpdata.com>
On 08/23/2012 01:12 PM, Konrad Rzeszutek Wilk wrote:
>>
>> Okay... I think I need to grok that a bit better. For memory
>> allocations, we probably should just use brk allocations, for
>> virtual space allocations it is called the fixmap for a reason (even
>> though the Xen people managed to break that on 32 bits, sigh!)
>
> Can you rope me in on that? Was that added ooh years ago ?
Yeah, it dates back to the original paravirt work.
The issue is that Xen likes to live at the top of the virtual address
space, which is where the fixmap lives. Suddenly the fixmap is no
longer at a fixed address, which was sort of the whole idea.
The problem is that on i386 there are very few unmovable boundaries left
in the virtual address space. The only other one left, really, is at
the very beginning of kernel space.
At this point people's appetite for large changes on 32 bits is limited,
of course.
-hpa
next prev parent reply other threads:[~2012-08-23 21:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-14 22:39 [PATCH V3 0/4] x86: Create direct mappings for E820_RAM only Jacob Shin
2012-08-14 22:39 ` [PATCH 1/4] x86: Move enabling of PSE and PGE out of init_memory_mapping Jacob Shin
2012-08-14 22:39 ` [PATCH 2/4] x86: find_early_table_space based on memory ranges that are being mapped Jacob Shin
2012-08-14 22:39 ` [PATCH 3/4] x86: Only direct map addresses that are marked as E820_RAM Jacob Shin
2012-08-22 23:30 ` H. Peter Anvin
2012-08-23 14:50 ` Jacob Shin
2012-08-23 15:39 ` H. Peter Anvin
2012-08-23 20:12 ` Konrad Rzeszutek Wilk
2012-08-23 21:23 ` H. Peter Anvin [this message]
2012-08-23 22:35 ` Jacob Shin
2012-08-23 23:46 ` Yinghai Lu
2012-08-23 23:53 ` H. Peter Anvin
2012-08-14 22:39 ` [PATCH 4/4] x86: Fixup code testing if a pfn is direct mapped Jacob Shin
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=50369F67.8040101@zytor.com \
--to=hpa@zytor.com \
--cc=andreas.herrmann3@amd.com \
--cc=borislav.petkov@amd.com \
--cc=chaowang@redhat.com \
--cc=dyoung@redhat.com \
--cc=jacob.shin@amd.com \
--cc=konrad@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@kernel.org \
--cc=vgoyal@redhat.com \
--cc=x86@kernel.org \
--cc=yinghai@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