From: Marcelo Tosatti <mtosatti@redhat.com>
To: Carsten Otte <cotte@de.ibm.com>
Cc: Avi Kivity <avi@redhat.com>,
Christian Borntraeger <borntraeger@de.ibm.com>,
Heiko Carstens <heiko.carstens@de.ibm.com>,
Martin Schwidefsky <schwidefsky@de.ibm.com>,
Cornelia Huck <cornelia.huck@de.ibm.com>,
KVM <kvm@vger.kernel.org>,
Joachim von Buttlar <joachim_von_buttlar@de.ibm.com>,
Jens Freimann <jfrei@de.ibm.com>,
agraf@suse.de
Subject: Re: [patch 00/11] Ucontrol patchset respin without storage keys
Date: Mon, 9 Jan 2012 10:19:34 -0200 [thread overview]
Message-ID: <20120109121934.GA6563@amt.cnet> (raw)
In-Reply-To: <20120104092519.060746143@de.ibm.com>
On Wed, Jan 04, 2012 at 10:25:19AM +0100, Carsten Otte wrote:
> Hi Avi,
>
> after some more discussion about how to do storage keys proper, I could
> not come up with a sane and safe way of doing SSKE without either
> over or underindicating the change bit in corner cases (leads to
> corrupted guest memory or host kernel panic).
> The storage key operations are completely seperate from the rest of
> the ucontrol series:
> - ucontrol VMs can operate without them (handled by hardware)
> - regular VMs can make use of them too (needed for live migration)
>
> This respin only contains the non-controversial patches. I would
> kindly like to ask for inclusion, I will retry on storage keys as
> soon as I've got a solution.
>
> so long,
> Carsten
Applied, thanks.
prev parent reply other threads:[~2012-01-09 12:30 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-04 9:25 [patch 00/11] Ucontrol patchset respin without storage keys Carsten Otte
2012-01-04 9:25 ` [patch 01/11] [PATCH] kvm-s390: add parameter for KVM_CREATE_VM Carsten Otte
2012-01-04 9:25 ` [patch 02/11] [PATCH] kvm-s390-ucontrol: per vcpu address spaces Carsten Otte
2012-01-04 9:25 ` [patch 03/11] [PATCH] kvm-s390-ucontrol: export page faults to user Carsten Otte
2012-01-04 9:25 ` [patch 04/11] [PATCH] kvm-s390-ucontrol: export SIE control block " Carsten Otte
2012-01-04 9:25 ` [patch 05/11] [PATCH] kvm-s390-ucontrol: disable in-kernel handling of SIE intercepts Carsten Otte
2012-01-04 9:25 ` [patch 06/11] [PATCH] kvm-s390-ucontrol: disable in-kernel irq stack Carsten Otte
2012-01-04 9:25 ` [patch 07/11] [PATCH] kvm-s390-ucontrol: interface to inject faults on a vcpu page table Carsten Otte
2012-01-04 14:52 ` Avi Kivity
2012-01-04 16:09 ` Carsten Otte
2012-01-04 16:34 ` Carsten Otte
2012-01-04 17:25 ` Avi Kivity
2012-01-04 9:25 ` [patch 08/11] [PATCH] kvm-s390-ucontrol: disable sca Carsten Otte
2012-01-04 9:25 ` [patch 09/11] [PATCH] kvm-s390: fix assumption for KVM_MAX_VCPUS Carsten Otte
2012-01-04 9:25 ` [patch 10/11] [PATCH] kvm-s390-ucontrol: announce capability for user controlled vms Carsten Otte
2012-01-04 9:25 ` [patch 11/11] [PATCH] kvm-s390: Fix return code for unknown ioctl numbers Carsten Otte
2012-01-04 14:54 ` [patch 00/11] Ucontrol patchset respin without storage keys Avi Kivity
2012-01-04 14:56 ` Avi Kivity
2012-01-05 13:41 ` Marcelo Tosatti
2012-01-05 13:47 ` Marcelo Tosatti
2012-01-05 15:24 ` Carsten Otte
2012-01-09 12:19 ` Marcelo Tosatti [this message]
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=20120109121934.GA6563@amt.cnet \
--to=mtosatti@redhat.com \
--cc=agraf@suse.de \
--cc=avi@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=cornelia.huck@de.ibm.com \
--cc=cotte@de.ibm.com \
--cc=heiko.carstens@de.ibm.com \
--cc=jfrei@de.ibm.com \
--cc=joachim_von_buttlar@de.ibm.com \
--cc=kvm@vger.kernel.org \
--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 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).