From: Tim Deegan <tim@xen.org>
To: Christoph Egger <Christoph.Egger@amd.com>
Cc: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [PATCH] nestedsvm: fix memory leak on shutdown/crash
Date: Mon, 22 Oct 2012 16:24:40 +0100 [thread overview]
Message-ID: <20121022152440.GI12577@ocelot.phlegethon.org> (raw)
In-Reply-To: <507E6DF1.7080506@amd.com>
At 10:36 +0200 on 17 Oct (1350470161), Christoph Egger wrote:
>
> Fix memory leak of l1 vmcb page when destroying a vcpu while
> l2 guest is running.
>
> Signed-off-by: Christoph Egger <Christoph.Egger@amd.com>
Acked-by: Tim Deegan <tim@xen.org>
Content-Description: xen_nh_shutdown.diff
> diff -r 6b73078a4403 xen/arch/x86/hvm/svm/nestedsvm.c
> --- a/xen/arch/x86/hvm/svm/nestedsvm.c Fri Oct 12 14:38:20 2012 +0200
> +++ b/xen/arch/x86/hvm/svm/nestedsvm.c Wed Oct 17 09:08:20 2012 +0200
> @@ -122,6 +122,15 @@ void nsvm_vcpu_destroy(struct vcpu *v)
> struct nestedvcpu *nv = &vcpu_nestedhvm(v);
> struct nestedsvm *svm = &vcpu_nestedsvm(v);
>
> + /*
> + * When destroying the vcpu, it may be running on behalf of l2 guest.
> + * Therefore we need to switch the VMCB pointer back to the l1 vmcb,
> + * in order to avoid double free of l2 vmcb and the possible memory leak
> + * of l1 vmcb page.
> + */
> + if (nv->nv_n1vmcx)
> + v->arch.hvm_svm.vmcb = nv->nv_n1vmcx;
> +
> if (svm->ns_cached_msrpm) {
> free_xenheap_pages(svm->ns_cached_msrpm,
> get_order_from_bytes(MSRPM_SIZE));
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
prev parent reply other threads:[~2012-10-22 15:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-17 8:36 [PATCH] nestedsvm: fix memory leak on shutdown/crash Christoph Egger
2012-10-22 15:24 ` Tim Deegan [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=20121022152440.GI12577@ocelot.phlegethon.org \
--to=tim@xen.org \
--cc=Christoph.Egger@amd.com \
--cc=xen-devel@lists.xen.org \
/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).