From: Andi Kleen <andi@firstfloor.org>
To: Or Sagi <ors@tutis.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>, Nir Peleg <nir@tutis.com>
Subject: Re: [PATCH] Reserve low memory
Date: Mon, 22 Oct 2007 15:53:39 +0200 [thread overview]
Message-ID: <p73oder9rx8.fsf@bingen.suse.de> (raw)
In-Reply-To: <20071021165401.GA8626@cleopatra.qumranet.com> (Or Sagi's message of "Sun\, 21 Oct 2007 18\:54\:01 +0200")
Or Sagi <ors@tutis.com> writes:
> Adds a CONFIG_RESERVE_LOWMEM option which reserves all memory below
> CONFIG_PHYSICAL_START address.
>
> Cleans up some of the static early-boot memory allocations (nodemap, trampoline)
> Useful in particular for running virtual machines which require a 1:1 mapping
> of the physical memory. This lets a virtual machine control a dma-capable device
> directly without hypervisor involvement.
With the infrastructure in
ftp://firstfloor.org/pub/ak/x86_64/quilt/patches/early-reserve
you can do this much cleaner (and likely safer)
And using CONFIG_* options for such things is wrong anyways. If anything
it should be run time options.
-Andi
>
prev parent reply other threads:[~2007-10-22 13:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-21 16:54 [PATCH] Reserve low memory Or Sagi
2007-10-22 13:53 ` Andi Kleen [this message]
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=p73oder9rx8.fsf@bingen.suse.de \
--to=andi@firstfloor.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nir@tutis.com \
--cc=ors@tutis.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox