From: Janosch Frank <frankja@linux.ibm.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>, kvm@vger.kernel.org
Cc: thuth@redhat.com, cohuck@redhat.com, linux-s390@vger.kernel.org
Subject: Re: [PATCH v3] KVM: s390: Add new reset vcpu API
Date: Wed, 8 Jan 2020 15:42:29 +0100 [thread overview]
Message-ID: <12d48cb4-40be-3044-d417-debceddcf011@linux.ibm.com> (raw)
In-Reply-To: <3b37f523-d67f-ba6c-8e14-77183f73a58a@de.ibm.com>
[-- Attachment #1.1: Type: text/plain, Size: 2877 bytes --]
On 1/8/20 3:35 PM, Christian Borntraeger wrote:
>
>
> On 08.01.20 15:28, Christian Borntraeger wrote:
>>
>>
>> On 05.12.19 13:09, Janosch Frank wrote:
>> [...]
>>> +4.123 KVM_S390_CLEAR_RESET
>>> +
>>> +Capability: KVM_CAP_S390_VCPU_RESETS
>>> +Architectures: s390
>>> +Type: vcpu ioctl
>>> +Parameters: none
>>> +Returns: 0
>>> +
>>> +This ioctl resets VCPU registers and control structures that QEMU
>>> +can't access via the kvm_run structure. The clear reset is a superset
>>> +of the initial reset and additionally clears general, access, floating
>>> +and vector registers.
>>
>> As Thomas outlined, make it more obvious that userspace does the remaining
>> parts. I do not think that we want the kernel to do the things (unless it
>> helps you in some way for the ultravisor guests)
>
> On the other hand. todays initial cpu reset DOES everything. So I guess
> the other ones should do the same. That actually makes the semantics clearer -
> when you call it it will have done whatever reset you have asked for.
Ok, will do, thanks for the clearup
>
>
>>
>> [...]
>>>
>>> +static int kvm_arch_vcpu_ioctl_normal_reset(struct kvm_vcpu *vcpu)
>>> +{
>>> + kvm_clear_async_pf_completion_queue(vcpu);
>>> + kvm_s390_clear_local_irqs(vcpu);
>>> + return 0;
>>
>> Shouldnt we also do
>> if (!kvm_s390_user_cpu_state_ctrl(vcpu->kvm))
>> kvm_s390_vcpu_stop(vcpu);
>>
>> here?
>>
>>
>>> +}
>>> +
>>> static int kvm_arch_vcpu_ioctl_initial_reset(struct kvm_vcpu *vcpu)
>>> {
>>> kvm_s390_vcpu_initial_reset(vcpu);
>>> @@ -4363,9 +4371,15 @@ long kvm_arch_vcpu_ioctl(struct file *filp,
>>> r = kvm_arch_vcpu_ioctl_set_initial_psw(vcpu, psw);
>>> break;
>>> }
>>> +
>>> + case KVM_S390_CLEAR_RESET:
>>> + /* fallthrough */
>>> case KVM_S390_INITIAL_RESET:
>>> r = kvm_arch_vcpu_ioctl_initial_reset(vcpu);
>>> break;
>>
>> Then we could also do a fallthrough here and do:
>>
>> diff --git a/arch/s390/kvm/kvm-s390.c b/arch/s390/kvm/kvm-s390.c
>> index d9e6bf3..c715ae3 100644
>> --- a/arch/s390/kvm/kvm-s390.c
>> +++ b/arch/s390/kvm/kvm-s390.c
>> @@ -2867,10 +2867,6 @@ static void kvm_s390_vcpu_initial_reset(struct kvm_vcpu *vcpu)
>> vcpu->arch.sie_block->pp = 0;
>> vcpu->arch.sie_block->fpf &= ~FPF_BPBC;
>> vcpu->arch.pfault_token = KVM_S390_PFAULT_TOKEN_INVALID;
>> - kvm_clear_async_pf_completion_queue(vcpu);
>> - if (!kvm_s390_user_cpu_state_ctrl(vcpu->kvm))
>> - kvm_s390_vcpu_stop(vcpu);
>> - kvm_s390_clear_local_irqs(vcpu);
>> }
>>
>> void kvm_arch_vcpu_postcreate(struct kvm_vcpu *vcpu)
>>
>>
>>
>>
>>> + case KVM_S390_NORMAL_RESET:
>>> + r = kvm_arch_vcpu_ioctl_normal_reset(vcpu);
>>> + break;
>>> case KVM_SET_ONE_REG:
>>> case KVM_GET_ONE_REG: {
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2020-01-08 14:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-05 12:09 [PATCH v3] KVM: s390: Add new reset vcpu API Janosch Frank
2019-12-05 12:19 ` Cornelia Huck
2019-12-05 12:28 ` [PATCH v4] " Janosch Frank
2019-12-05 12:35 ` Cornelia Huck
2019-12-05 12:50 ` Thomas Huth
2020-01-08 14:28 ` [PATCH v3] " Christian Borntraeger
2020-01-08 14:35 ` Janosch Frank
2020-01-08 14:38 ` Christian Borntraeger
2020-01-08 14:44 ` Thomas Huth
2020-01-08 15:36 ` Cornelia Huck
2020-01-08 14:35 ` Christian Borntraeger
2020-01-08 14:42 ` Janosch Frank [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=12d48cb4-40be-3044-d417-debceddcf011@linux.ibm.com \
--to=frankja@linux.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=thuth@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