From: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
To: Keith Coleman <list.keith@scaltro.com>
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: [PATCH] fs-backend: fix gnttab unmap
Date: Mon, 23 Mar 2009 10:48:38 +0000 [thread overview]
Message-ID: <49C76906.5080704@eu.citrix.com> (raw)
In-Reply-To: <5411dbdc0903201500ja2d67eak2d309361eda994c2@mail.gmail.com>
Keith Coleman wrote:
> On Thu, Mar 19, 2009 at 12:58 PM, Stefano Stabellini
> <stefano.stabellini@eu.citrix.com> wrote:
>> Hi all,
>> when a stubdom is destroyed, fs-backend does not correctly unmap all the
>> pages mapped for the shared ring.
>> This causes some pages not to be properly freed by xen, hence after a
>> cycle of 50 save\restore we don't have enough spare memory to start 2
>> VMs any more.
>> This patch fixes the issue properly unmapping all the pages needed by
>> the shared ring.
>>
>
> I can confirm that fs-backend is more stable. I have performed
> hundreds of save/restore cycles without issue.
>
good, thanks again for testing.
prev parent reply other threads:[~2009-03-23 10:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-19 16:58 [PATCH] fs-backend: fix gnttab unmap Stefano Stabellini
2009-03-20 22:00 ` Keith Coleman
2009-03-23 10:48 ` Stefano Stabellini [this message]
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=49C76906.5080704@eu.citrix.com \
--to=stefano.stabellini@eu.citrix.com \
--cc=list.keith@scaltro.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.