From: David Vrabel <david.vrabel@citrix.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: <linux-kernel@vger.kernel.org>, <david.vrabel@citrix.com>,
<xen-devel@lists.xensource.com>
Subject: Re: [Xen-devel] [PATCH] fixes to stable/for-linus-3.5
Date: Wed, 23 May 2012 17:02:33 +0100 [thread overview]
Message-ID: <4FBD0A19.30701@citrix.com> (raw)
In-Reply-To: <1337636562-9579-1-git-send-email-konrad.wilk@oracle.com>
On 21/05/12 22:42, Konrad Rzeszutek Wilk wrote:
>
> The autoballoon one would try to balloon up to E820_MAX when
> there were no dom0_mem=.. argument.
I don't see this behaviour and looking at the code I don't see how it
could. The autoballoon code only populates pages that were released so
it won't go above xen_start_info->nr_pages.
Do you have any logs showing the problem behaviour?
> The patch fixes it, and
> is also makes the dom0_mem=1G case work better (I think?). The
> other solution would be to use the current_reservation patch
> I posted a while back to work-around when no dom0_mem= argument
> is used.
David
WARNING: multiple messages have this Message-ID (diff)
From: David Vrabel <david.vrabel@citrix.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: linux-kernel@vger.kernel.org, david.vrabel@citrix.com,
xen-devel@lists.xensource.com
Subject: Re: [Xen-devel] [PATCH] fixes to stable/for-linus-3.5
Date: Wed, 23 May 2012 17:02:33 +0100 [thread overview]
Message-ID: <4FBD0A19.30701@citrix.com> (raw)
In-Reply-To: <1337636562-9579-1-git-send-email-konrad.wilk@oracle.com>
On 21/05/12 22:42, Konrad Rzeszutek Wilk wrote:
>
> The autoballoon one would try to balloon up to E820_MAX when
> there were no dom0_mem=.. argument.
I don't see this behaviour and looking at the code I don't see how it
could. The autoballoon code only populates pages that were released so
it won't go above xen_start_info->nr_pages.
Do you have any logs showing the problem behaviour?
> The patch fixes it, and
> is also makes the dom0_mem=1G case work better (I think?). The
> other solution would be to use the current_reservation patch
> I posted a while back to work-around when no dom0_mem= argument
> is used.
David
next prev parent reply other threads:[~2012-05-23 16:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-21 21:42 [PATCH] fixes to stable/for-linus-3.5 Konrad Rzeszutek Wilk
2012-05-21 21:42 ` [PATCH 1/2] xen/smp: unbind irqworkX when unplugging vCPUs Konrad Rzeszutek Wilk
2012-05-21 21:42 ` [PATCH 2/2] xen/setup: Work properly with 'dom0_mem=X' or with not dom0_mem Konrad Rzeszutek Wilk
2012-05-23 16:02 ` David Vrabel [this message]
2012-05-23 16:02 ` [Xen-devel] [PATCH] fixes to stable/for-linus-3.5 David Vrabel
2012-05-23 17:32 ` 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=4FBD0A19.30701@citrix.com \
--to=david.vrabel@citrix.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.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 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.