qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
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: Wed, 12 Aug 2009 14:18:20 -0500	[thread overview]
Message-ID: <4A83157C.9040009@codemonkey.ws> (raw)
In-Reply-To: <20090811162537.GA25705@redhat.com>

Michael S. Tsirkin wrote:
> On
>   
>> Why bother switching to userspace for migration?  Can't you just have  
>> get/set ioctls for the state?
>>     
>
> I have these. But live migration requires dirty page logging.
> I do not want to implement it in kernel.
>   

Is it really that difficult?  I think it would be better to just do that.

I wonder though if mmu notifiers can be used to make it transparent...

Regards,

Anthony Liguori

>> Regards,
>>
>> Anthony Liguori
>>
>>     

  reply	other threads:[~2009-08-12 19:18 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-10 19:28 [Qemu-devel] [PATCH] qemu/virtio: move features to an inline function Michael S. Tsirkin
2009-08-10 19:37 ` [Qemu-devel] " Anthony Liguori
2009-08-10 19:47   ` Michael S. Tsirkin
2009-08-10 20:33     ` Anthony Liguori
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 13:15             ` Anthony Liguori
2009-08-11 13:43               ` Michael S. Tsirkin
2009-08-11 16:08                 ` Anthony Liguori
2009-08-11 16:25                   ` Michael S. Tsirkin
2009-08-12 19:18                     ` Anthony Liguori [this message]
2009-08-13  6:15                       ` Michael S. Tsirkin
2009-08-13  9:28                         ` Avi Kivity
2009-08-13  9:51                           ` Michael S. Tsirkin

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=4A83157C.9040009@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=rusty@rustcorp.com.au \
    --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 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).