From: David Hildenbrand <david@redhat.com>
To: "Christian Borntraeger" <borntraeger@de.ibm.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Radim Krčmář" <rkrcmar@redhat.com>
Cc: KVM <kvm@vger.kernel.org>,
Cornelia Huck <cornelia.huck@de.ibm.com>,
linux-s390 <linux-s390@vger.kernel.org>,
Farhan Ali <alifm@linux.vnet.ibm.com>,
"Corey S . McQuay" <csmcquay@linux.vnet.ibm.com>
Subject: Re: [GIT PULL 4/4] KVM: s390: Support keyless subset guest mode
Date: Fri, 21 Apr 2017 14:15:22 +0200 [thread overview]
Message-ID: <00eaf534-b042-a09e-933f-cb051816fea2@redhat.com> (raw)
In-Reply-To: <1492769385-237420-5-git-send-email-borntraeger@de.ibm.com>
> diff --git a/arch/s390/kvm/vsie.c b/arch/s390/kvm/vsie.c
> index 025b1f2..4719ecb 100644
> --- a/arch/s390/kvm/vsie.c
> +++ b/arch/s390/kvm/vsie.c
> @@ -117,6 +117,8 @@ static int prepare_cpuflags(struct kvm_vcpu *vcpu, struct vsie_page *vsie_page)
> newflags |= cpuflags & CPUSTAT_SM;
> if (test_kvm_cpu_feat(vcpu->kvm, KVM_S390_VM_CPU_FEAT_IBS))
> newflags |= cpuflags & CPUSTAT_IBS;
> + if (test_kvm_cpu_feat(vcpu->kvm, KVM_S390_VM_CPU_FEAT_KSS))
> + newflags |= cpuflags & CPUSTAT_KSS;
>
> atomic_set(&scb_s->cpuflags, newflags);
> return 0;
> @@ -289,7 +291,9 @@ static int shadow_scb(struct kvm_vcpu *vcpu, struct vsie_page *vsie_page)
> * bits. Therefore we cannot provide interpretation and would later
> * have to provide own emulation handlers.
> */
> - scb_s->ictl |= ICTL_ISKE | ICTL_SSKE | ICTL_RRBE;
> + if (!(atomic_read(&scb_s->cpuflags) & CPUSTAT_KSS))
> + scb_s->ictl |= ICTL_ISKE | ICTL_SSKE | ICTL_RRBE;
> +
What would actually happen, if ICTL_ISKE | ICTL_SSKE | ICTL_RRBE remain
set? I assume KSS will dominate? Or are there any validity interceptions
defined for this?
--
Thanks,
David
next prev parent reply other threads:[~2017-04-21 12:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-21 10:09 [GIT PULL 0/4] KVM: s390: Guarded storage fixup and keyless subset mode (kvm/next) Christian Borntraeger
2017-04-21 10:09 ` [GIT PULL 1/4] KVM: s390: Fix sdnxo setting for nested guests Christian Borntraeger
2017-04-21 10:09 ` [GIT PULL 2/4] KVM: s390: fix stale machine check data for guarded storage Christian Borntraeger
2017-04-21 10:09 ` [GIT PULL 3/4] s390/sclp: Detect KSS facility Christian Borntraeger
2017-04-21 10:09 ` [GIT PULL 4/4] KVM: s390: Support keyless subset guest mode Christian Borntraeger
2017-04-21 12:15 ` David Hildenbrand [this message]
2017-04-21 12:23 ` Christian Borntraeger
2017-04-21 12:29 ` David Hildenbrand
2017-04-21 10:28 ` [GIT PULL 0/4] KVM: s390: Guarded storage fixup and keyless subset mode (kvm/next) Paolo Bonzini
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=00eaf534-b042-a09e-933f-cb051816fea2@redhat.com \
--to=david@redhat.com \
--cc=alifm@linux.vnet.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=cornelia.huck@de.ibm.com \
--cc=csmcquay@linux.vnet.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=rkrcmar@redhat.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