From: Avi Kivity <avi@redhat.com>
To: Gleb Natapov <gleb@redhat.com>
Cc: Jan Kiszka <jan.kiszka@web.de>, kvm-devel <kvm@vger.kernel.org>
Subject: Re: Debugging an inconsistent shadow page table
Date: Sun, 26 Apr 2009 14:34:59 +0300 [thread overview]
Message-ID: <49F446E3.5030705@redhat.com> (raw)
In-Reply-To: <20090426112749.GT24095@redhat.com>
Gleb Natapov wrote:
> On Sun, Apr 26, 2009 at 01:11:40PM +0200, Jan Kiszka wrote:
>
>> That raise a question for a kvm-mmu newbie like me:
>>
>> If a page of the qemu process gets pushed around (here likely due to
>> fork()->exec(smbd)->COW), how will kvm's shadow table catch up? Via
>> MMU_NOTIFIER?
>>
>> I'm on a 2.6.25 kernel, and that means without CONFIG_MMU_NOTIFIER. So
>> far I assumed that kernels without this feature do not work optimally,
>> but they won't break my guests...
>>
>>
> Guest memory is not COWed on fork (madvise(MADV_DONTFORK))
>
>
Which isn't present in upstream.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-04-26 11:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-25 10:36 Debugging an inconsistent shadow page table Jan Kiszka
2009-04-26 10:32 ` Avi Kivity
2009-04-26 11:11 ` Jan Kiszka
2009-04-26 11:27 ` Gleb Natapov
2009-04-26 11:34 ` Avi Kivity [this message]
2009-04-26 11:36 ` Jan Kiszka
2009-04-26 11:39 ` Gleb Natapov
2009-04-26 11:41 ` Jan Kiszka
2009-04-26 11:42 ` Avi Kivity
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=49F446E3.5030705@redhat.com \
--to=avi@redhat.com \
--cc=gleb@redhat.com \
--cc=jan.kiszka@web.de \
--cc=kvm@vger.kernel.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.