From: Thomas Huth <thuth@redhat.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>,
Janosch Frank <frankja@linux.ibm.com>,
kvm@vger.kernel.org
Cc: 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:44:57 +0100 [thread overview]
Message-ID: <d3370e31-ca33-567d-ce0e-1168f603a686@redhat.com> (raw)
In-Reply-To: <3ddb7aa6-96d4-246f-a8ba-fdf2408a4ff0@de.ibm.com>
On 08/01/2020 15.38, Christian Borntraeger wrote:
>
>
> On 08.01.20 15:35, Janosch Frank wrote:
>> On 1/8/20 3:28 PM, 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)
>>
>> Ok, will do
>
> I changed my mind (see my other mail) but I would like Thomas, Conny or David
> to ack/nack.
I don't mind too much as long as it is properly documented, but I also
slightly prefer to be consistent here, i.e. let the kernel clear the
rest here, too, just like we do it already with the initial reset.
Thomas
next prev parent reply other threads:[~2020-01-08 14:45 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 [this message]
2020-01-08 15:36 ` Cornelia Huck
2020-01-08 14:35 ` Christian Borntraeger
2020-01-08 14:42 ` Janosch Frank
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=d3370e31-ca33-567d-ce0e-1168f603a686@redhat.com \
--to=thuth@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=frankja@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
/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