xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: David Vrabel <david.vrabel@citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [PATCH 2/3] xen: allow extra memory to be two regions
Date: Mon, 22 Aug 2011 09:55:59 -0400	[thread overview]
Message-ID: <20110822135559.GB645@dumpdata.com> (raw)
In-Reply-To: <20110816153615.GA31689@dumpdata.com>

> > Okay.  This behaviour is kept as well.
> > 
> > For example, on my test box with 8 GiB RAM with dom0 started with 752
> > MiB of initial pages and limited to 4 GiB.
> 
> So dom0_mem=max:4GB,725MB ?
> 
> > 
> > [    0.000000]  Xen: 0000000000000000 - 000000000009e000 (usable)
> > [    0.000000]  Xen: 00000000000a0000 - 0000000000100000 (reserved)
> > [    0.000000]  Xen: 0000000000100000 - 00000000bf699000 (usable)
> > [    0.000000]  Xen: 00000000bf699000 - 00000000bf6af000 (reserved)
> > [    0.000000]  Xen: 00000000bf6af000 - 00000000bf6ce000 (ACPI data)
> > [    0.000000]  Xen: 00000000bf6ce000 - 00000000c0000000 (reserved)
> > [    0.000000]  Xen: 00000000e0000000 - 00000000f0000000 (reserved)
> > [    0.000000]  Xen: 00000000fe000000 - 0000000100000000 (reserved)
> > [    0.000000]  Xen: 0000000100000000 - 0000000140967000 (usable)
> > [    0.000000]  Xen: 0000000140967000 - 0000000240000000 (unusable)
> > 
> What did it look before?
> 
> What does "Memory:" look before and after?

ping? Did I miss some patches from you? Are you waiting for Keir to merge
the Xen hypervisor patches - if so I think we can just work on this in parallel?
> 
> > David
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel

  reply	other threads:[~2011-08-22 13:55 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-16 10:00 [RFC] limit dom0 memory using Xen's dom0_mem command line option David Vrabel
2011-08-16 10:00 ` [PATCH 1/3] xen: allow balloon driver to use more than one memory region David Vrabel
2011-08-16 13:38   ` Konrad Rzeszutek Wilk
2011-08-16 14:21     ` David Vrabel
2011-08-16 14:48       ` Konrad Rzeszutek Wilk
2011-08-16 15:03         ` David Vrabel
2011-08-16 10:00 ` [PATCH 2/3] xen: allow extra memory to be two regions David Vrabel
2011-08-16 13:48   ` Konrad Rzeszutek Wilk
2011-08-16 14:33     ` David Vrabel
2011-08-16 14:48       ` Konrad Rzeszutek Wilk
2011-08-16 15:03         ` David Vrabel
2011-08-16 15:36           ` Konrad Rzeszutek Wilk
2011-08-22 13:55             ` Konrad Rzeszutek Wilk [this message]
2011-08-22 14:01               ` David Vrabel
2011-08-16 10:00 ` [PATCH 3/3] xen: use maximum reservation to limit dom0 memory David Vrabel
2011-08-16 13:53   ` Konrad Rzeszutek Wilk
2011-08-16 14:41     ` David Vrabel
2011-08-16 14:54       ` Konrad Rzeszutek Wilk
2011-08-16 14:50     ` Konrad Rzeszutek Wilk
2011-08-16 13:33 ` [RFC] limit dom0 memory using Xen's dom0_mem command line option Konrad Rzeszutek Wilk

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=20110822135559.GB645@dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=david.vrabel@citrix.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 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).