From: Avi Kivity <avi@redhat.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>
Cc: Marcelo Tossati <mtosatti@redhat.com>,
Carsten Otte <cotte@de.ibm.com>, Alexander Graf <agraf@suse.de>,
Jens Freimann <jfrei@linux.vnet.ibm.com>,
Cornelia Huck <cornelia.huck@de.ibm.com>,
Heiko Carstens <heiko.carstens@de.ibm.com>,
Martin Schwidefsky <schwidefsky@de.ibm.com>,
Heinz Graalfs <graalfs@linux.vnet.ibm.com>,
KVM <kvm@vger.kernel.org>
Subject: Re: [PATCH 1/4] kvm-s390: add capability indicating COW support
Date: Tue, 15 May 2012 15:24:49 +0300 [thread overview]
Message-ID: <4FB24B11.1050607@redhat.com> (raw)
In-Reply-To: <1337084128-38219-2-git-send-email-borntraeger@de.ibm.com>
On 05/15/2012 03:15 PM, Christian Borntraeger wrote:
> Currently qemu/kvm on s390 uses a guest mapping that does not
> allow the guest backing page table to be write-protected to
> support older systems. On those older systems a host write
> protection fault will be delivered to the guest.
>
> Newer systems allow to write-protect the guest backing memory
> and let the fault be delivered to the host, thus allowing COW.
>
> Use a capability bit to tell qemu if that is possible.
>
Asking out of ignorance: who is doing the write protection here? The
guest? If so, why is qemu involved?
Or is qemu just passing the capability on to the guest?
btw, we usually use 'userspace' in kernel patches instead of qemu to
create the illusion that it's not the only consumer of kvm interfaces.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2012-05-15 12:25 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-15 12:15 [PATCH 0/4] kvm-s390: feature patches Christian Borntraeger
2012-05-15 12:15 ` [PATCH 1/4] kvm-s390: add capability indicating COW support Christian Borntraeger
2012-05-15 12:24 ` Avi Kivity [this message]
2012-05-15 12:31 ` Christian Borntraeger
2012-05-15 12:33 ` Avi Kivity
2012-05-15 12:38 ` Christian Borntraeger
2012-05-15 12:40 ` Avi Kivity
2012-06-05 12:36 ` Alexander Graf
2012-05-15 12:49 ` [Qemu-devel] [PATCH 0/1] memory detection hack for s390 Christian Borntraeger
2012-05-15 12:49 ` [Qemu-devel] [PATCH 1/1] s390: autodetect map private Christian Borntraeger
2012-06-05 12:50 ` Alexander Graf
2012-06-05 12:44 ` [Qemu-devel] [PATCH 0/1] memory detection hack for s390 Alexander Graf
2012-05-15 12:15 ` [PATCH 2/4] kvm-s390: KVM_GET/SET_ONEREG " Christian Borntraeger
2012-06-05 12:37 ` Alexander Graf
2012-05-15 12:15 ` [PATCH 3/4] kvm-s390: epoch difference and TOD programmable field Christian Borntraeger
2012-06-05 12:40 ` Alexander Graf
2012-05-15 12:15 ` [PATCH 4/4] kvm-s390: onereg for timer related registers Christian Borntraeger
2012-06-05 12:42 ` Alexander Graf
2012-06-05 12:57 ` Christian Borntraeger
2012-06-05 13:03 ` Alexander Graf
2012-05-15 12:26 ` [PATCH 0/4] kvm-s390: feature patches Avi Kivity
2012-05-15 12:34 ` Christian Borntraeger
2012-05-18 0:06 ` Marcelo Tosatti
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=4FB24B11.1050607@redhat.com \
--to=avi@redhat.com \
--cc=agraf@suse.de \
--cc=borntraeger@de.ibm.com \
--cc=cornelia.huck@de.ibm.com \
--cc=cotte@de.ibm.com \
--cc=graalfs@linux.vnet.ibm.com \
--cc=heiko.carstens@de.ibm.com \
--cc=jfrei@linux.vnet.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=schwidefsky@de.ibm.com \
/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.