virtualization.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: Zachary Amsden <zach@vmware.com>
To: Andrew Morton <akpm@osdl.org>
Cc: chrisw@sous-sol.org, virtualization@lists.osdl.org,
	xen-devel@lists.xensource.com, linux-kernel@vger.kernel.org
Subject: Re: [patch 7/8] Add a bootparameter to reserve high linear address space.
Date: Sat, 05 Aug 2006 15:52:46 -0700	[thread overview]
Message-ID: <44D5213E.3000900@vmware.com> (raw)
In-Reply-To: <20060805145840.653912a2.akpm@osdl.org>

Andrew Morton wrote:
> On Thu, 03 Aug 2006 01:58:32 -0700
> Zachary Amsden <zach@vmware.com> wrote:
>
>   
>> Add a bootparameter to reserve high linear address space for hypervisors.
>> This is necessary to allow dynamically loaded hypervisor modules, which
>> might not happen until userspace is already running, and also provides a
>> useful tool to benchmark the performance impact of reduced lowmem address
>> space.
>>     
>
> Andi has gone and rotorooted the x86 boot parameter handling in there. 
> This patch now looks like this:
>   

The rototilled patch looks great.  Acked.

Zach

  reply	other threads:[~2006-08-05 22:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20060803002510.634721860@xensource.com>
     [not found] ` <20060803002518.595166293@xensource.com>
     [not found]   ` <20060802231912.ed77f930.akpm@osdl.org>
     [not found]     ` <44D1A6B6.8040003@vmware.com>
     [not found]       ` <20060803004144.554d9882.akpm@osdl.org>
     [not found]         ` <44D1BAB8.8070509@vmware.com>
2006-08-05 21:58           ` [patch 7/8] Add a bootparameter to reserve high linear address space Andrew Morton
2006-08-05 22:52             ` Zachary Amsden [this message]
2006-08-05 23:17             ` Rusty Russell
2006-08-06 22:00   ` Pavel Machek
2006-08-06 22:02   ` Pavel Machek
2006-08-07  9:12   ` Pavel Machek
     [not found]   ` <19700101001522.GA3999@ucw.cz>
2006-08-07  2:10     ` Andi Kleen
2010-05-04 23:37     ` Jeremy Fitzhardinge

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=44D5213E.3000900@vmware.com \
    --to=zach@vmware.com \
    --cc=akpm@osdl.org \
    --cc=chrisw@sous-sol.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=virtualization@lists.osdl.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).