From: Mick Jordan <Mick.Jordan@sun.com>
To: Keir Fraser <keir.fraser@eu.citrix.com>
Cc: xen-devel-list <xen-devel@lists.xensource.com>
Subject: Re: memory_reservation bug?
Date: Wed, 11 Mar 2009 12:34:39 -0700 [thread overview]
Message-ID: <49B8124F.8010609@Sun.COM> (raw)
In-Reply-To: <C5DDAE97.4D02%keir.fraser@eu.citrix.com>
[-- Attachment #1.1: Type: text/plain, Size: 820 bytes --]
On 03/11/09 11:08, Keir Fraser wrote:
> On 11/03/2009 17:32, "Mick Jordan" <Mick.Jordan@sun.com> wrote:
>
>
>> I've looked at the code in memory.c and page_alloc.c and Xen certainly
>> thinks tot_pages > max_pages for the domain when it reports the error.
>>
>> The extent_order on the reservations is 0.
>>
>> Any ideas?
>>
>
> Just because you called decrease_reservation() doesn't mean the pages
> necessarily really got freed. If you still have mappings to them squirrelled
> away then the free can be deferred.
>
Ah, that explains it, thank you. I was taking the fact that the return
value equaled the number I tried to decrease meant that it really did
decrease by that amount. But, owing to a bug, I do in fact have mappings
still lying around.
Xen really does need a developer manual -;)
Mick
[-- Attachment #1.2: Type: text/html, Size: 1320 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2009-03-11 19:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-11 17:32 memory_reservation bug? Mick Jordan
2009-03-11 18:08 ` Keir Fraser
2009-03-11 19:34 ` Mick Jordan [this message]
2009-03-11 19:50 ` memory_reservation bug?: memory holes Mick Jordan
2009-03-11 22:41 ` Keir Fraser
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=49B8124F.8010609@Sun.COM \
--to=mick.jordan@sun.com \
--cc=keir.fraser@eu.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 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.