qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@linux.vnet.ibm.com>
To: qemu-devel@nongnu.org
Cc: Thomas Huth <thuth@linux.vnet.ibm.com>,
	kvm@vger.kernel.org, agraf@suse.de, borntraeger@de.ibm.com,
	cornelia.huck@de.ibm.com, pbonzini@redhat.com
Subject: [Qemu-devel] [PATCH 0/2] s390x/kvm: ioctl for reading and writing from/to guest memory
Date: Mon, 16 Feb 2015 13:22:16 +0100	[thread overview]
Message-ID: <1424089338-14562-1-git-send-email-thuth@linux.vnet.ibm.com> (raw)

These two patches enable QEMU to make use of the new KVM_GUEST_MEM_OP
ioctl on s390x (see my kernel patch with the title "KVM: s390: Add MEMOP
ioctls for reading/writing guest memory" that I've posted on the KVM
mailing list).
The first patch in this series updates the Linux headers with the new
ioctl definitions. This should be replaced with a proper synchronized
header update against kvm/next as soon as the kernel part has been
accepted.
The second patch then uses the ioctl when QEMU has to access the logical
memory of a guest. This patch goes on top of my "s390x: rework guest
memory access" patch series that has been sent out to the qemu-devel list
by Jens Freimann on last thursday.

Thomas Huth (2):
  Update Linux headers with KVM_GUEST_MEM_OP ioctl
  s390x/mmu: Use ioctl for reading and writing from/to guest memory

 linux-headers/linux/kvm.h |   21 +++++++++++++++++++++
 target-s390x/cpu.h        |    7 +++++++
 target-s390x/kvm.c        |   35 +++++++++++++++++++++++++++++++++++
 target-s390x/mmu_helper.c |    9 +++++++++
 4 files changed, 72 insertions(+), 0 deletions(-)

             reply	other threads:[~2015-02-16 12:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-16 12:22 Thomas Huth [this message]
2015-02-16 12:22 ` [Qemu-devel] [PATCH 1/2] Update Linux headers with KVM_GUEST_MEM_OP ioctl Thomas Huth
2015-02-16 12:22 ` [Qemu-devel] [PATCH 2/2] s390x/mmu: Use ioctl for reading and writing from/to guest memory Thomas Huth

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=1424089338-14562-1-git-send-email-thuth@linux.vnet.ibm.com \
    --to=thuth@linux.vnet.ibm.com \
    --cc=agraf@suse.de \
    --cc=borntraeger@de.ibm.com \
    --cc=cornelia.huck@de.ibm.com \
    --cc=kvm@vger.kernel.org \
    --cc=pbonzini@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).