From: Avi Kivity <avi@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: qemu-devel@nongnu.org, Anthony Liguori <anthony@codemonkey.ws>,
virtualization@lists.linux-foundation.org
Subject: Re: [Qemu-devel] Re: [PATCH] qemu/virtio: move features to an inline function
Date: Thu, 13 Aug 2009 12:28:52 +0300 [thread overview]
Message-ID: <4A83DCD4.9040705@redhat.com> (raw)
In-Reply-To: <20090813061522.GD3029@redhat.com>
On 08/13/2009 09:15 AM, Michael S. Tsirkin wrote:
>
>> I wonder though if mmu notifiers can be used to make it transparent...
>>
>
> Maybe they can, but that decision belongs to KVM.
> Avi, what do you think?
>
>
I don't see how mmu notifiers help. You can use mmu notifiers to sync
an external mmu to the linux pagetables, but that's not the case here.
I see the following options:
- mprotect() guest memory, trap faults, mprotect() back
Will work, but exceedingly slowly and wastefully
- add a generic user visible dirty bit tracking based on linux ptes
A lot of work, not sure if useful beyond kvm
- implement vhost dirty bit tracking
Not too difficult; not sure if it's worth the effort though
- reuse the kvm dirty bitmap
Not too difficult but introduces tight coupling between vhost and kvm
which might slow down development
- drop to userspace for live migration
Reuse qemu code, lose some performance
--
error compiling committee.c: too many arguments to function
WARNING: multiple messages have this Message-ID (diff)
From: Avi Kivity <avi@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: rusty@rustcorp.com.au, qemu-devel@nongnu.org,
virtualization@lists.linux-foundation.org
Subject: Re: [Qemu-devel] Re: [PATCH] qemu/virtio: move features to an inline function
Date: Thu, 13 Aug 2009 12:28:52 +0300 [thread overview]
Message-ID: <4A83DCD4.9040705@redhat.com> (raw)
In-Reply-To: <20090813061522.GD3029@redhat.com>
On 08/13/2009 09:15 AM, Michael S. Tsirkin wrote:
>
>> I wonder though if mmu notifiers can be used to make it transparent...
>>
>
> Maybe they can, but that decision belongs to KVM.
> Avi, what do you think?
>
>
I don't see how mmu notifiers help. You can use mmu notifiers to sync
an external mmu to the linux pagetables, but that's not the case here.
I see the following options:
- mprotect() guest memory, trap faults, mprotect() back
Will work, but exceedingly slowly and wastefully
- add a generic user visible dirty bit tracking based on linux ptes
A lot of work, not sure if useful beyond kvm
- implement vhost dirty bit tracking
Not too difficult; not sure if it's worth the effort though
- reuse the kvm dirty bitmap
Not too difficult but introduces tight coupling between vhost and kvm
which might slow down development
- drop to userspace for live migration
Reuse qemu code, lose some performance
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-08-13 9:28 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-10 19:28 [PATCH] qemu/virtio: move features to an inline function Michael S. Tsirkin
2009-08-10 19:28 ` [Qemu-devel] " Michael S. Tsirkin
2009-08-10 19:37 ` [Qemu-devel] " Anthony Liguori
2009-08-10 19:47 ` Michael S. Tsirkin
2009-08-10 19:47 ` Michael S. Tsirkin
2009-08-10 20:33 ` Anthony Liguori
2009-08-10 20:33 ` Anthony Liguori
2009-08-10 22:19 ` Michael S. Tsirkin
2009-08-10 22:19 ` Michael S. Tsirkin
2009-08-10 22:35 ` Anthony Liguori
2009-08-11 8:48 ` Michael S. Tsirkin
2009-08-11 8:48 ` Michael S. Tsirkin
2009-08-11 13:15 ` Anthony Liguori
2009-08-11 13:15 ` Anthony Liguori
2009-08-11 13:43 ` Michael S. Tsirkin
2009-08-11 13:43 ` Michael S. Tsirkin
2009-08-11 16:08 ` Anthony Liguori
2009-08-11 16:08 ` Anthony Liguori
2009-08-11 16:25 ` Michael S. Tsirkin
2009-08-11 16:25 ` Michael S. Tsirkin
2009-08-12 19:18 ` Anthony Liguori
2009-08-12 19:18 ` Anthony Liguori
2009-08-13 6:15 ` Michael S. Tsirkin
2009-08-13 6:15 ` Michael S. Tsirkin
2009-08-13 9:28 ` Avi Kivity [this message]
2009-08-13 9:28 ` Avi Kivity
2009-08-13 9:51 ` Michael S. Tsirkin
2009-08-13 9:51 ` Michael S. Tsirkin
2009-08-10 22:35 ` Anthony Liguori
2009-08-10 19:37 ` Anthony Liguori
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=4A83DCD4.9040705@redhat.com \
--to=avi@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=virtualization@lists.linux-foundation.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.