All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keir Fraser <keir@xensource.com>
To: Glauber de Oliveira Costa <gcosta@redhat.com>,
	Keir Fraser <keir@xensource.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: [PATCH] Make ballooning work with maxmem > mem (i386 version)
Date: Fri, 10 Nov 2006 15:44:07 +0000	[thread overview]
Message-ID: <C17A4EC7.4549%keir@xensource.com> (raw)
In-Reply-To: <20061110153357.GD32562@redhat.com>




On 10/11/06 15:33, "Glauber de Oliveira Costa" <gcosta@redhat.com> wrote:

>> I took both patches and then changed my mind and immediately reverted them.
>> There is a better way: we should support the XENMEM_memory_map hypercall.
>> We should provide a hypercall (domctl) to set a memory_map_limit parameter
>> and then Xen can use that to fake a memory map when XENMEM_memory_map is
>> called. The tools can set that parameter from config['maxmem'].
> 
> And what happens when the hypercall ever returns ENOSYS, like a kernel
> running in a bit old Hypervisor?

Oh, and bear in mind you can always use 'memory=' as a boot parameter to
force the p2m size and mem_map size.

 -- Keir

  parent reply	other threads:[~2006-11-10 15:44 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-10 13:24 [PATCH] Make ballooning work with maxmem > mem (i386 version) Glauber de Oliveira Costa
     [not found] ` <C17A49E3.4537%keir@xensource.com>
2006-11-10 15:33   ` Glauber de Oliveira Costa
2006-11-10 15:43     ` Keir Fraser
2006-11-10 15:54       ` Daniel P. Berrange
2006-11-10 15:57         ` Keir Fraser
2006-11-10 16:10       ` Glauber de Oliveira Costa
2006-11-10 16:16         ` Keir Fraser
2006-11-10 20:27       ` Glauber de Oliveira Costa
2006-11-11  0:08         ` Keir Fraser
2006-11-10 15:44     ` Keir Fraser [this message]
2006-11-10 15:50       ` Daniel P. Berrange

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=C17A4EC7.4549%keir@xensource.com \
    --to=keir@xensource.com \
    --cc=gcosta@redhat.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.