From: Janosch Frank <frankja@linux.vnet.ibm.com>
To: David Hildenbrand <david@redhat.com>, kvm@vger.kernel.org
Cc: schwidefsky@de.ibm.com, borntraeger@de.ibm.com,
dominik.dingel@gmail.com, linux-s390@vger.kernel.org
Subject: Re: [PATCH 1/3] KVM: s390: Refactor host cmma and pfmfi interpretation controls
Date: Thu, 15 Feb 2018 17:42:40 +0100 [thread overview]
Message-ID: <208a30df-f8af-9f73-bffd-71c6f94cf0a0@linux.vnet.ibm.com> (raw)
In-Reply-To: <4b1638fd-c5d9-b265-861b-5065a83c0342@redhat.com>
[-- Attachment #1.1: Type: text/plain, Size: 7654 bytes --]
On 15.02.2018 17:08, David Hildenbrand wrote:
> On 15.02.2018 16:43, Janosch Frank wrote:
>> use_cmma in kvm_arch means that the vm is allowed to use cmma, whereas
>> use_cmma in the mm context means it has been used before. Let's rename
>> the kvm_arch one to has_cmma
>
> Unfortunately all naming related to CMM(A) is already screwed up.
>
> If the guest can issue the ESSA instruction, it has the CMM facility. We
> used to provide it to him by enabling the CMMA control - the
> "interpretation facility". We could right now fully emulate it (which is
> what we do when we dirty track changes).
>
> At least in the CPU model we did it right. (the feature is called "cmm")
>
> But anyhow, we only provide the CMM facility to the guest right now if
> we have CMMA, so keeping the name "cmma" here is not completely wrong.
>
>>
>> Also let's introduce has_pfmfi, so we can remove the pfmfi disablement
>
> Mixed feelings. has_pfmfi sounds more like "this guest has the PFMFI
> feature", which is something related to vSIE. It is really more
> "use_pfmfi". Because we provide the PFMF instruction either way (by
> emulating it - it belongs to edat1).
>
> Can we name this "use_cmma" and "use_pfmfi" and "use_skf", because that
> is actually what we do?
As long as we have a difference between the arch and the context one and
the implementation of the patches are not a problem, sure.
We could also invert them and use emulate_pfmf or intercept_* which is
more specific about what we actually (don't) do.
>
> The thing in the mm context should rather be renamed to "uses_cmm(a)" or
> "used_cmm(a)".
Yes, I like uses more, the rest of the gang likes used, now feel free to
propose something entirely different :)
If there's not much that speaks against the first two patches, I'd spin
them off to merge them earlier, the use_cmma cleanup has been on my list
for a long time. Thoughts?
>
>> when we activate cmma and rather not activate it in the first place.
>>
>> Signed-off-by: Janosch Frank <frankja@linux.vnet.ibm.com>
>> ---
>> arch/s390/include/asm/kvm_host.h | 3 ++-
>> arch/s390/kvm/kvm-s390.c | 25 +++++++++++++------------
>> arch/s390/kvm/priv.c | 2 +-
>> 3 files changed, 16 insertions(+), 14 deletions(-)
>>
>> diff --git a/arch/s390/include/asm/kvm_host.h b/arch/s390/include/asm/kvm_host.h
>> index afb0f08..b768754 100644
>> --- a/arch/s390/include/asm/kvm_host.h
>> +++ b/arch/s390/include/asm/kvm_host.h
>> @@ -791,7 +791,8 @@ struct kvm_arch{
>> unsigned long mem_limit;
>> int css_support;
>> int use_irqchip;
>> - int use_cmma;
>> + int has_cmma;
>> + int has_pfmfi;
>> int user_cpu_state_ctrl;
>> int user_sigp;
>> int user_stsi;
>> diff --git a/arch/s390/kvm/kvm-s390.c b/arch/s390/kvm/kvm-s390.c
>> index 4a2d68c..781aaf0 100644
>> --- a/arch/s390/kvm/kvm-s390.c
>> +++ b/arch/s390/kvm/kvm-s390.c
>> @@ -655,7 +655,9 @@ static int kvm_s390_set_mem_control(struct kvm *kvm, struct kvm_device_attr *att
>> VM_EVENT(kvm, 3, "%s", "ENABLE: CMMA support");
>> mutex_lock(&kvm->lock);
>> if (!kvm->created_vcpus) {
>> - kvm->arch.use_cmma = 1;
>> + kvm->arch.has_cmma = 1;
>> + /* Not compatible with cmma. */
>> + kvm->arch.has_pfmfi = 0;
>> ret = 0;
>> }
>> mutex_unlock(&kvm->lock);
>> @@ -665,7 +667,7 @@ static int kvm_s390_set_mem_control(struct kvm *kvm, struct kvm_device_attr *att
>> if (!sclp.has_cmma)
>> break;
>> ret = -EINVAL;
>> - if (!kvm->arch.use_cmma)
>> + if (!kvm->arch.has_cmma)
>> break;
>>
>> VM_EVENT(kvm, 3, "%s", "RESET: CMMA states");
>> @@ -810,7 +812,7 @@ static int kvm_s390_vm_start_migration(struct kvm *kvm)
>> return -ENOMEM;
>> kvm->arch.migration_state = mgs;
>>
>> - if (kvm->arch.use_cmma) {
>> + if (kvm->arch.has_cmma) {
>> /*
>> * Get the first slot. They are reverse sorted by base_gfn, so
>> * the first slot is also the one at the end of the address
>> @@ -855,7 +857,7 @@ static int kvm_s390_vm_stop_migration(struct kvm *kvm)
>> mgs = kvm->arch.migration_state;
>> kvm->arch.migration_state = NULL;
>>
>> - if (kvm->arch.use_cmma) {
>> + if (kvm->arch.has_cmma) {
>> kvm_s390_sync_request_broadcast(kvm, KVM_REQ_STOP_MIGRATION);
>> /* We have to wait for the essa emulation to finish */
>> synchronize_srcu(&kvm->srcu);
>> @@ -1551,7 +1553,7 @@ static int kvm_s390_get_cmma_bits(struct kvm *kvm,
>> cur = args->start_gfn;
>> i = next = pgstev = 0;
>>
>> - if (unlikely(!kvm->arch.use_cmma))
>> + if (unlikely(!kvm->arch.has_cmma))
>> return -ENXIO;
>> /* Invalid/unsupported flags were specified */
>> if (args->flags & ~KVM_S390_CMMA_PEEK)
>> @@ -1650,7 +1652,7 @@ static int kvm_s390_set_cmma_bits(struct kvm *kvm,
>>
>> mask = args->mask;
>>
>> - if (!kvm->arch.use_cmma)
>> + if (!kvm->arch.has_cmma)
>> return -ENXIO;
>> /* invalid/unsupported flags */
>> if (args->flags != 0)
>> @@ -2007,6 +2009,7 @@ int kvm_arch_init_vm(struct kvm *kvm, unsigned long type)
>>
>> kvm->arch.css_support = 0;
>> kvm->arch.use_irqchip = 0;
>> + kvm->arch.has_pfmfi = sclp.has_pfmfi;
>> kvm->arch.epoch = 0;
>>
>> spin_lock_init(&kvm->arch.start_stop_lock);
>> @@ -2045,7 +2048,7 @@ void kvm_arch_vcpu_destroy(struct kvm_vcpu *vcpu)
>> if (kvm_is_ucontrol(vcpu->kvm))
>> gmap_remove(vcpu->arch.gmap);
>>
>> - if (vcpu->kvm->arch.use_cmma)
>> + if (vcpu->kvm->arch.has_cmma)
>> kvm_s390_vcpu_unsetup_cmma(vcpu);
>> free_page((unsigned long)(vcpu->arch.sie_block));
>>
>> @@ -2431,8 +2434,6 @@ int kvm_s390_vcpu_setup_cmma(struct kvm_vcpu *vcpu)
>> vcpu->arch.sie_block->cbrlo = get_zeroed_page(GFP_KERNEL);
>> if (!vcpu->arch.sie_block->cbrlo)
>> return -ENOMEM;
>> -
>> - vcpu->arch.sie_block->ecb2 &= ~ECB2_PFMFI;
>> return 0;
>> }
>>
>> @@ -2468,7 +2469,7 @@ int kvm_arch_vcpu_setup(struct kvm_vcpu *vcpu)
>> if (test_kvm_facility(vcpu->kvm, 73))
>> vcpu->arch.sie_block->ecb |= ECB_TE;
>>
>> - if (test_kvm_facility(vcpu->kvm, 8) && sclp.has_pfmfi)
>> + if (test_kvm_facility(vcpu->kvm, 8) && vcpu->kvm->arch.has_pfmfi)
>> vcpu->arch.sie_block->ecb2 |= ECB2_PFMFI;
>> if (test_kvm_facility(vcpu->kvm, 130))
>> vcpu->arch.sie_block->ecb2 |= ECB2_IEP;
>> @@ -2502,7 +2503,7 @@ int kvm_arch_vcpu_setup(struct kvm_vcpu *vcpu)
>> else
>> vcpu->arch.sie_block->ictl |= ICTL_ISKE | ICTL_SSKE | ICTL_RRBE;
>>
>> - if (vcpu->kvm->arch.use_cmma) {
>> + if (vcpu->kvm->arch.has_cmma) {
>> rc = kvm_s390_vcpu_setup_cmma(vcpu);
>> if (rc)
>> return rc;
>> @@ -3013,7 +3014,7 @@ static int kvm_s390_handle_requests(struct kvm_vcpu *vcpu)
>> * Re-enable CMMA virtualization if CMMA is available and
>> * was used.
>> */
>> - if ((vcpu->kvm->arch.use_cmma) &&
>> + if ((vcpu->kvm->arch.has_cmma) &&
>> (vcpu->kvm->mm->context.use_cmma))
>> vcpu->arch.sie_block->ecb2 |= ECB2_CMMA;
>> goto retry;
>> diff --git a/arch/s390/kvm/priv.c b/arch/s390/kvm/priv.c
>> index c4c4e15..908b579 100644
>> --- a/arch/s390/kvm/priv.c
>> +++ b/arch/s390/kvm/priv.c
>> @@ -1050,7 +1050,7 @@ static int handle_essa(struct kvm_vcpu *vcpu)
>> VCPU_EVENT(vcpu, 4, "ESSA: release %d pages", entries);
>> gmap = vcpu->arch.gmap;
>> vcpu->stat.instruction_essa++;
>> - if (!vcpu->kvm->arch.use_cmma)
>> + if (!vcpu->kvm->arch.has_cmma)
>> return kvm_s390_inject_program_int(vcpu, PGM_OPERATION);
>>
>> if (vcpu->arch.sie_block->gpsw.mask & PSW_MASK_PSTATE)
>>
>
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2018-02-15 16:42 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-09 9:34 [RFC/PATCH v3 00/16] KVM/s390: Hugetlbfs enablement Janosch Frank
2018-02-09 9:34 ` [RFC/PATCH v3 01/16] s390/mm: make gmap_protect_range more modular Janosch Frank
2018-02-13 14:07 ` David Hildenbrand
2018-02-09 9:34 ` [RFC/PATCH v3 02/16] s390/mm: Abstract gmap notify bit setting Janosch Frank
2018-02-13 14:10 ` David Hildenbrand
2018-02-13 14:31 ` Janosch Frank
2018-02-09 9:34 ` [RFC/PATCH v3 03/16] s390/mm: Introduce gmap_pmdp_xchg Janosch Frank
2018-02-13 14:16 ` David Hildenbrand
2018-02-13 14:39 ` Janosch Frank
2018-02-09 9:34 ` [RFC/PATCH v3 04/16] s390/mm: add gmap PMD invalidation notification Janosch Frank
2018-02-13 14:36 ` David Hildenbrand
2018-02-13 14:54 ` Janosch Frank
2018-02-13 14:59 ` David Hildenbrand
2018-02-13 15:33 ` Janosch Frank
2018-02-14 10:42 ` David Hildenbrand
2018-02-14 11:19 ` Janosch Frank
2018-02-14 14:18 ` David Hildenbrand
2018-02-14 14:55 ` Janosch Frank
2018-02-14 15:15 ` David Hildenbrand
2018-02-14 15:24 ` Janosch Frank
2018-02-09 9:34 ` [RFC/PATCH v3 05/16] s390/mm: Add gmap pmd invalidation and clearing Janosch Frank
2018-02-09 9:34 ` [RFC/PATCH v3 06/16] s390/mm: Add huge page dirty sync support Janosch Frank
2018-02-09 9:34 ` [RFC/PATCH v3 07/16] s390/mm: Make gmap_read_table EDAT1 compatible Janosch Frank
2018-02-09 9:34 ` [RFC/PATCH v3 08/16] s390/mm: Make protect_rmap " Janosch Frank
2018-02-09 9:34 ` [RFC/PATCH v3 09/16] s390/mm: Add shadow segment code Janosch Frank
2018-02-09 9:34 ` [RFC/PATCH v3 10/16] s390/mm: Add VSIE reverse fake case Janosch Frank
2018-02-09 9:34 ` [RFC/PATCH v3 11/16] s390/mm: Enable gmap huge pmd support Janosch Frank
2018-02-09 9:34 ` [RFC/PATCH v3 12/16] s390/mm: clear huge page storage keys on enable_skey Janosch Frank
2018-02-09 9:34 ` [RFC/PATCH v3 13/16] s390/mm: Add huge pmd storage key handling Janosch Frank
2018-02-09 9:34 ` [RFC/PATCH v3 14/16] s390/mm: hugetlb pages within a gmap can not be freed Janosch Frank
2018-02-09 9:34 ` [RFC/PATCH v3 15/16] KVM: s390: Add KVM HPAGE capability Janosch Frank
2018-02-09 9:34 ` [RFC/PATCH v3 16/16] s390/mm: Add gmap lock classes Janosch Frank
2018-02-14 14:30 ` [RFC/PATCH v3 00/16] KVM/s390: Hugetlbfs enablement David Hildenbrand
2018-02-14 15:01 ` Janosch Frank
2018-02-14 15:07 ` David Hildenbrand
2018-02-14 15:33 ` Janosch Frank
2018-02-14 15:48 ` Christian Borntraeger
2018-02-14 15:57 ` David Hildenbrand
2018-02-14 15:56 ` David Hildenbrand
2018-02-15 15:43 ` [PATCH 0/3] Hpage capability rework Janosch Frank
2018-02-15 15:43 ` [PATCH 1/3] KVM: s390: Refactor host cmma and pfmfi interpretation controls Janosch Frank
2018-02-15 16:08 ` David Hildenbrand
2018-02-15 16:42 ` Janosch Frank [this message]
2018-02-16 9:46 ` David Hildenbrand
2018-02-15 15:43 ` [PATCH 2/3] KVM: s390: Add storage key facility interpretation control Janosch Frank
2018-02-15 16:09 ` David Hildenbrand
2018-02-15 20:27 ` Farhan Ali
2018-02-15 15:43 ` [PATCH 3/3] s390/mm: Enable gmap huge pmd support Janosch Frank
2018-02-15 16:10 ` David Hildenbrand
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=208a30df-f8af-9f73-bffd-71c6f94cf0a0@linux.vnet.ibm.com \
--to=frankja@linux.vnet.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=david@redhat.com \
--cc=dominik.dingel@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@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).