qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Brad Hards <bradh@frogmouth.net>
To: qemu-devel@nongnu.org
Cc: "Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] [PATCH RFC 0/5] kvm/vhost: enable durty logging during memory registration
Date: Thu, 7 Apr 2011 15:39:04 +1000	[thread overview]
Message-ID: <201104071539.04904.bradh@frogmouth.net> (raw)
In-Reply-To: <cover.1302121974.git.mst@redhat.com>

On Thu, 7 Apr 2011 06:41:35 am Michael S. Tsirkin wrote:
> As a solution, this adds an explicit flag that
> will enable dirty logging directly when registering
> the ram. kvm then needs a single system call
> to update tables for vga ram, vhost-net can simply ignore it.
I'm not very familiar with QEMU coding style and standards (so this could be 
completely bogus), but I think that the code would be easier if you used a 
integer flag / enum instead of a boolean. That would also give you options for 
additional behaviour changes later too. So instead of passing true/false, pass 
MEM_LOG_DIRTY_PAGES (or whatever you decide to call it).

I can't really comment on the rest of the patch - I'm too clueless. 

> This replaces the RFC patchset 'vga: flag vga ram for notifiers'.
> Warning: compile-tested only.
I compiled and booted my Ubuntu guest (on ubuntu host) which uses Cirrus for 
each step in this patchset. Seems OK to me - I didn't notice appreciable 
speedup, but I wasn't really expecting to.

Brad

  parent reply	other threads:[~2011-04-07  5:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-06 20:41 [Qemu-devel] [PATCH RFC 0/5] kvm/vhost: enable durty logging during memory registration Michael S. Tsirkin
2011-04-06 20:41 ` [Qemu-devel] [PATCH RFC 1/5] cpu: add set_memory flag to request dirty logging Michael S. Tsirkin
2011-04-06 20:41 ` [Qemu-devel] [PATCH RFC 2/5] kvm: halve number of set memory calls for vga Michael S. Tsirkin
2011-04-06 20:41 ` [Qemu-devel] [PATCH RFC 3/5] vhost: skip memory which needs dirty logging Michael S. Tsirkin
2011-04-06 20:41 ` [Qemu-devel] [PATCH RFC 4/5] vhost: optimize out no-change assignment Michael S. Tsirkin
2011-04-06 20:42 ` [Qemu-devel] [PATCH RFC 5/5] cirrus_vga: flag on-device ram for dirty logging Michael S. Tsirkin
2011-04-07  5:39 ` Brad Hards [this message]
2011-04-07 17:01   ` [Qemu-devel] [PATCH RFC 0/5] kvm/vhost: enable durty logging during memory registration Blue Swirl

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=201104071539.04904.bradh@frogmouth.net \
    --to=bradh@frogmouth.net \
    --cc=mst@redhat.com \
    --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).