From: Takuya Yoshikawa <yoshikawa.takuya@oss.ntt.co.jp>
To: kvm-ia64@vger.kernel.org
Subject: [PATCH v2 0/4] KVM: kvm_vm_ioctl_get_dirty_log() fix and cleanup
Date: Wed, 23 Jun 2010 05:58:07 +0000 [thread overview]
Message-ID: <20100623145807.07a07c4c.yoshikawa.takuya@oss.ntt.co.jp> (raw)
This patch series is for making dirty logging development, and of course
maintenance, easier. Please see individual patches for details.
Changelog
v1 -> v2:
- rebased
- booke and s390, kvm_vm_ioctl_get_dirty_log() to kvm_arch_vm_ioctl_get_dirty_log()
Takuya
---
arch/ia64/kvm/kvm-ia64.c | 54 ++++++++++++++++++--------------------------
arch/powerpc/kvm/book3s.c | 29 ++++++++++++++----------
arch/powerpc/kvm/booke.c | 2 +-
arch/s390/kvm/kvm-s390.c | 4 +-
arch/x86/kvm/x86.c | 14 +----------
include/linux/kvm_host.h | 6 +---
virt/kvm/kvm_main.c | 24 +++++--------------
7 files changed, 53 insertions(+), 80 deletions(-)
--
1.7.0.4
next reply other threads:[~2010-06-23 5:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-23 5:58 Takuya Yoshikawa [this message]
2010-06-23 8:50 ` [PATCH v2 0/4] KVM: kvm_vm_ioctl_get_dirty_log() fix and cleanup 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=20100623145807.07a07c4c.yoshikawa.takuya@oss.ntt.co.jp \
--to=yoshikawa.takuya@oss.ntt.co.jp \
--cc=kvm-ia64@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 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 read-only IMAP folder(s) and NNTP newsgroup(s).