From: Avi Kivity <avi@redhat.com>
To: Jan Kiszka <jan.kiszka@web.de>
Cc: qemu-devel <qemu-devel@nongnu.org>, Gleb Natapov <gleb@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2] kvm: Avoid COW if KVM MMU is asynchronous
Date: Sun, 26 Apr 2009 19:21:21 +0300 [thread overview]
Message-ID: <49F48A01.4090308@redhat.com> (raw)
In-Reply-To: <49F485DC.2080702@web.de>
Jan Kiszka wrote:
> If the KVM MMU is asynchronous (kernel does not support MMU_NOTIFIER),
> we have to avoid COW for the guest memory. Otherwise we risk serious
> breakage when guest pages change there physical locations due to COW
> after fork. Seen when forking smbd during runtime via -smb.
>
>
> last_ram_offset += size;
>
> + if (kvm_enabled())
> + kvm_setup_guest_memory(new_block->host, size);
> +
> return new_block->offset;
> }
>
I feel a little bad about picking such small nits, but the if statement
requires braces.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-04-26 16:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-26 12:21 [Qemu-devel] [PATCH] kvm: Avoid COW if KVM MMU is asynchronous Jan Kiszka
2009-04-26 13:08 ` Avi Kivity
2009-04-26 16:03 ` [Qemu-devel] [PATCH v2] " Jan Kiszka
2009-04-26 16:21 ` Avi Kivity [this message]
2009-04-26 16:44 ` [Qemu-devel] [PATCH v3] " Jan Kiszka
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=49F48A01.4090308@redhat.com \
--to=avi@redhat.com \
--cc=gleb@redhat.com \
--cc=jan.kiszka@web.de \
--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).