From: "Hao, Xudong" <xudong.hao@intel.com>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: "kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"gleb@redhat.com" <gleb@redhat.com>,
"pbonzini@redhat.com" <pbonzini@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: RE: [PATCH] qemu-kvm: fix unmatched RAM alloction/free
Date: Wed, 29 May 2013 02:37:06 +0000 [thread overview]
Message-ID: <403610A45A2B5242BD291EDAE8B37D3010E3C845@SHSMSX102.ccr.corp.intel.com> (raw)
In-Reply-To: <51A4F8A5.9020308@msgid.tls.msk.ru>
> -----Original Message-----
> From: Michael Tokarev [mailto:mjt@tls.msk.ru]
> Sent: Wednesday, May 29, 2013 2:34 AM
> To: Hao, Xudong
> Cc: kvm@vger.kernel.org; gleb@redhat.com; pbonzini@redhat.com;
> qemu-devel@nongnu.org
> Subject: Re: [PATCH] qemu-kvm: fix unmatched RAM alloction/free
>
> Um, something's wrong with the Date. Care to resend with that fixed?
>
Because the similar fix are already in qemu upstream, seems we need not this patch longer.
> Thanks,
>
> /mjt
>
> 18.01.2009 02:13, Xudong Hao wrote:
> > mmap is used in qemu_vmalloc function instead of qemu_memalign(commit
> > 7dda5dc8), so it should change qemu_vfree to munmap to fix a unmatched
> > issue.
> [...]
WARNING: multiple messages have this Message-ID (diff)
From: "Hao, Xudong" <xudong.hao@intel.com>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: "pbonzini@redhat.com" <pbonzini@redhat.com>,
"gleb@redhat.com" <gleb@redhat.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] qemu-kvm: fix unmatched RAM alloction/free
Date: Wed, 29 May 2013 02:37:06 +0000 [thread overview]
Message-ID: <403610A45A2B5242BD291EDAE8B37D3010E3C845@SHSMSX102.ccr.corp.intel.com> (raw)
In-Reply-To: <51A4F8A5.9020308@msgid.tls.msk.ru>
> -----Original Message-----
> From: Michael Tokarev [mailto:mjt@tls.msk.ru]
> Sent: Wednesday, May 29, 2013 2:34 AM
> To: Hao, Xudong
> Cc: kvm@vger.kernel.org; gleb@redhat.com; pbonzini@redhat.com;
> qemu-devel@nongnu.org
> Subject: Re: [PATCH] qemu-kvm: fix unmatched RAM alloction/free
>
> Um, something's wrong with the Date. Care to resend with that fixed?
>
Because the similar fix are already in qemu upstream, seems we need not this patch longer.
> Thanks,
>
> /mjt
>
> 18.01.2009 02:13, Xudong Hao wrote:
> > mmap is used in qemu_vmalloc function instead of qemu_memalign(commit
> > 7dda5dc8), so it should change qemu_vfree to munmap to fix a unmatched
> > issue.
> [...]
next prev parent reply other threads:[~2013-05-29 2:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-17 23:13 [PATCH] qemu-kvm: fix unmatched RAM alloction/free Xudong Hao
2013-05-23 1:02 ` [Qemu-devel] " Xudong Hao
2013-05-23 17:13 ` Paolo Bonzini
2013-05-23 17:13 ` [Qemu-devel] " Paolo Bonzini
2013-05-24 1:21 ` Hao, Xudong
2013-05-24 1:21 ` [Qemu-devel] " Hao, Xudong
2013-05-24 13:08 ` Eric Blake
2013-05-24 13:08 ` Eric Blake
2013-05-28 18:34 ` Michael Tokarev
2013-05-28 18:34 ` [Qemu-devel] " Michael Tokarev
2013-05-29 2:37 ` Hao, Xudong [this message]
2013-05-29 2:37 ` Hao, Xudong
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=403610A45A2B5242BD291EDAE8B37D3010E3C845@SHSMSX102.ccr.corp.intel.com \
--to=xudong.hao@intel.com \
--cc=gleb@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mjt@tls.msk.ru \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.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 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.