From: Consul <void@aleksoft.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH] SIGSEGV when USE_KQEMU is defined
Date: Fri, 20 Feb 2009 09:14:15 -0800 [thread overview]
Message-ID: <gnmod9$s4e$1@ger.gmane.org> (raw)
In-Reply-To: <gnksl3$ka2$1@ger.gmane.org>
Consul wrote:
> Signed-off-by: Alex Ivanov <void@aleksoft.net>
>
> $ svn diff
> Index: block.c
> ===================================================================
> --- block.c (revision 6628)
> +++ block.c (working copy)
> @@ -1263,7 +1263,7 @@
> if (!s->is_write) {
> qemu_iovec_from_buffer(s->iov, s->bounce, s->iov->size);
> }
> - qemu_free(s->bounce);
> + qemu_vfree(s->bounce);
> s->this_aiocb->cb(s->this_aiocb->opaque, ret);
> qemu_aio_release(s->this_aiocb);
> }
>
On Windows s->bounce = qemu_memalign(512, nb_sectors * 512);
translates to VirtualAlloc and should be freed with VirtualFree (what qemu_vfree does).
next prev parent reply other threads:[~2009-02-20 17:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-20 0:14 [Qemu-devel] [PATCH] SIGSEGV when USE_KQEMU is defined Consul
2009-02-20 17:14 ` Consul [this message]
2009-03-03 6:28 ` Aurelien Jarno
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='gnmod9$s4e$1@ger.gmane.org' \
--to=void@aleksoft.net \
--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 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).