All of lore.kernel.org
 help / color / mirror / Atom feed
From: George Dunlap <george.dunlap@eu.citrix.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: Konrad Rzeszutek Wilk <konrad@kernel.org>,
	xen-devel@lists.xensource.com, david.vrabel@citrix.com,
	christian@holpert.de,
	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: [PATCH] xl, e820_host, PV passthrough: Fix guests crashing when memory == maxmem
Date: Fri, 24 May 2013 15:57:41 +0100	[thread overview]
Message-ID: <519F7FE5.6060809@eu.citrix.com> (raw)
In-Reply-To: <1369407312.17830.202.camel@zakaz.uk.xensource.com>

On 24/05/13 15:55, Ian Campbell wrote:
> On Fri, 2013-05-24 at 10:51 -0400, Konrad Rzeszutek Wilk wrote:
>> On Fri, May 24, 2013 at 02:58:24PM +0100, Ian Campbell wrote:
>>> On Fri, 2013-05-24 at 09:36 -0400, Konrad Rzeszutek Wilk wrote:
>>>> The code had an obvious bug where it would assume that the balloon
>>>> amount would always be _something_ and add an E820_RAM entry at the
>>>> end of the E820 array. The added E820_RAM would contain the balloon amount
>>>> plus the delta of memory that had to be subtracted b/c of the various
>>>> E820 entries. That assumption is certainly true when maxmem != mem,
>>>> but if guest config has maxmem = memory that is incorrect (as balloon
>>>> value is zero). The end result is that the E820 that is constructed
>>>> is missing a swath of "delta" memory and in most cases ends up with
>>>> only one E820_RAM entry that is of 512MB size on many Intel systems.
>>>>
>>>> Reported-by: Christian Holpert <christian@holpert.de>
>>>> Signed-off-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
>>> Acked-by: Ian Campbell <ian.campbell@citrix.com>
>> George,
>> Would you be OK putting this in Xen 4.3? It is only exposed if a user
>>   1) launches a PV guest
>>   2). Has in the guest config: pci=['blabla']\ne820_host=1
>>   3). Is not that freq used as only a couple of people seem to use it
> TBH I was just going to commit it as an obvious bug fix in my next sweep
> of my queue (probably on Tuesday at this rate...)
>
> I guess George has until then to object ;-)

Sounds like a bug fix -- no objections. :-)

  -George

  reply	other threads:[~2013-05-24 14:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-24 13:36 [PATCH] xl, e820_host, PV passthrough: Fix guests crashing when memory == maxmem Konrad Rzeszutek Wilk
2013-05-24 13:58 ` Ian Campbell
2013-05-24 14:51   ` Konrad Rzeszutek Wilk
2013-05-24 14:55     ` Ian Campbell
2013-05-24 14:57       ` George Dunlap [this message]
2013-05-30  9:01   ` Ian Campbell

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=519F7FE5.6060809@eu.citrix.com \
    --to=george.dunlap@eu.citrix.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=christian@holpert.de \
    --cc=david.vrabel@citrix.com \
    --cc=konrad.wilk@oracle.com \
    --cc=konrad@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.