All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: Andrew Jones <drjones@redhat.com>
Cc: "Christian Borntraeger" <borntraeger@de.ibm.com>,
	"Janosch Frank" <frankja@linux.ibm.com>,
	kvm@vger.kernel.org, "Paolo Bonzini" <pbonzini@redhat.com>,
	"Radim Krčmář" <rkrcmar@redhat.com>,
	"Shuah Khan" <shuah@kernel.org>,
	"David Hildenbrand" <david@redhat.com>,
	"Cornelia Huck" <cohuck@redhat.com>,
	linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
	linux-s390@vger.kernel.org
Subject: Re: [RFC PATCH 4/4] KVM: selftests: Add the sync_regs test for s390x
Date: Thu, 23 May 2019 13:19:58 +0200	[thread overview]
Message-ID: <6fbe22d3-b9a9-48c5-8227-743841332ae0@redhat.com> (raw)
In-Reply-To: <20190523105623.3zlnbleniovobwzk@kamzik.brq.redhat.com>

On 23/05/2019 12.56, Andrew Jones wrote:
> On Thu, May 16, 2019 at 01:12:53PM +0200, Thomas Huth wrote:
>> The test is an adaption of the same test for x86. Note that there
>> are some differences in the way how s390x deals with the kvm_valid_regs
>> in struct kvm_run, so some of the tests had to be removed. Also this
>> test is not using the ucall() interface on s390x yet (which would need
>> some work to be usable on s390x), so it simply drops out of the VM with
>> a diag 0x501 breakpoint instead.
>>
>> Signed-off-by: Thomas Huth <thuth@redhat.com>
>> ---
>>  MAINTAINERS                                   |   1 +
>>  tools/testing/selftests/kvm/Makefile          |   2 +
>>  .../selftests/kvm/s390x/sync_regs_test.c      | 151 ++++++++++++++++++
>>  3 files changed, 154 insertions(+)
>>  create mode 100644 tools/testing/selftests/kvm/s390x/sync_regs_test.c
>>
>> diff --git a/MAINTAINERS b/MAINTAINERS
>> index 514d1f88ee26..68f76ee9e821 100644
>> --- a/MAINTAINERS
>> +++ b/MAINTAINERS
>> @@ -8645,6 +8645,7 @@ F:	arch/s390/include/asm/gmap.h
>>  F:	arch/s390/include/asm/kvm*
>>  F:	arch/s390/kvm/
>>  F:	arch/s390/mm/gmap.c
>> +F:	tools/testing/selftests/kvm/s390x/
>>  F:	tools/testing/selftests/kvm/*/s390x/
> 
> Do we need these lines added? We have tools/testing/selftests/kvm/ in the
> common KVM section already. If we do want to specify them specifically,
> then I guess we need x86 and arm MAINTAINERS updates as well.

I think they are helpful in the sense that the s390x maintainers get
CC:-ed on related patches as well, and if I've got Christian right, he's
interested in getting informed here. For Arm related patches, I guess
you should ask the Arm maintainers first. For x86, it does not really
matter, since the maintainers are the same.

 Thomas

WARNING: multiple messages have this Message-ID (diff)
From: thuth at redhat.com (Thomas Huth)
Subject: [RFC PATCH 4/4] KVM: selftests: Add the sync_regs test for s390x
Date: Thu, 23 May 2019 13:19:58 +0200	[thread overview]
Message-ID: <6fbe22d3-b9a9-48c5-8227-743841332ae0@redhat.com> (raw)
In-Reply-To: <20190523105623.3zlnbleniovobwzk@kamzik.brq.redhat.com>

On 23/05/2019 12.56, Andrew Jones wrote:
> On Thu, May 16, 2019 at 01:12:53PM +0200, Thomas Huth wrote:
>> The test is an adaption of the same test for x86. Note that there
>> are some differences in the way how s390x deals with the kvm_valid_regs
>> in struct kvm_run, so some of the tests had to be removed. Also this
>> test is not using the ucall() interface on s390x yet (which would need
>> some work to be usable on s390x), so it simply drops out of the VM with
>> a diag 0x501 breakpoint instead.
>>
>> Signed-off-by: Thomas Huth <thuth at redhat.com>
>> ---
>>  MAINTAINERS                                   |   1 +
>>  tools/testing/selftests/kvm/Makefile          |   2 +
>>  .../selftests/kvm/s390x/sync_regs_test.c      | 151 ++++++++++++++++++
>>  3 files changed, 154 insertions(+)
>>  create mode 100644 tools/testing/selftests/kvm/s390x/sync_regs_test.c
>>
>> diff --git a/MAINTAINERS b/MAINTAINERS
>> index 514d1f88ee26..68f76ee9e821 100644
>> --- a/MAINTAINERS
>> +++ b/MAINTAINERS
>> @@ -8645,6 +8645,7 @@ F:	arch/s390/include/asm/gmap.h
>>  F:	arch/s390/include/asm/kvm*
>>  F:	arch/s390/kvm/
>>  F:	arch/s390/mm/gmap.c
>> +F:	tools/testing/selftests/kvm/s390x/
>>  F:	tools/testing/selftests/kvm/*/s390x/
> 
> Do we need these lines added? We have tools/testing/selftests/kvm/ in the
> common KVM section already. If we do want to specify them specifically,
> then I guess we need x86 and arm MAINTAINERS updates as well.

I think they are helpful in the sense that the s390x maintainers get
CC:-ed on related patches as well, and if I've got Christian right, he's
interested in getting informed here. For Arm related patches, I guess
you should ask the Arm maintainers first. For x86, it does not really
matter, since the maintainers are the same.

 Thomas

WARNING: multiple messages have this Message-ID (diff)
From: thuth@redhat.com (Thomas Huth)
Subject: [RFC PATCH 4/4] KVM: selftests: Add the sync_regs test for s390x
Date: Thu, 23 May 2019 13:19:58 +0200	[thread overview]
Message-ID: <6fbe22d3-b9a9-48c5-8227-743841332ae0@redhat.com> (raw)
Message-ID: <20190523111958.eAbA16p8_j7JAyQ69NPcaNVyrcWfFqZMkpVPX25Bm_U@z> (raw)
In-Reply-To: <20190523105623.3zlnbleniovobwzk@kamzik.brq.redhat.com>

On 23/05/2019 12.56, Andrew Jones wrote:
> On Thu, May 16, 2019@01:12:53PM +0200, Thomas Huth wrote:
>> The test is an adaption of the same test for x86. Note that there
>> are some differences in the way how s390x deals with the kvm_valid_regs
>> in struct kvm_run, so some of the tests had to be removed. Also this
>> test is not using the ucall() interface on s390x yet (which would need
>> some work to be usable on s390x), so it simply drops out of the VM with
>> a diag 0x501 breakpoint instead.
>>
>> Signed-off-by: Thomas Huth <thuth at redhat.com>
>> ---
>>  MAINTAINERS                                   |   1 +
>>  tools/testing/selftests/kvm/Makefile          |   2 +
>>  .../selftests/kvm/s390x/sync_regs_test.c      | 151 ++++++++++++++++++
>>  3 files changed, 154 insertions(+)
>>  create mode 100644 tools/testing/selftests/kvm/s390x/sync_regs_test.c
>>
>> diff --git a/MAINTAINERS b/MAINTAINERS
>> index 514d1f88ee26..68f76ee9e821 100644
>> --- a/MAINTAINERS
>> +++ b/MAINTAINERS
>> @@ -8645,6 +8645,7 @@ F:	arch/s390/include/asm/gmap.h
>>  F:	arch/s390/include/asm/kvm*
>>  F:	arch/s390/kvm/
>>  F:	arch/s390/mm/gmap.c
>> +F:	tools/testing/selftests/kvm/s390x/
>>  F:	tools/testing/selftests/kvm/*/s390x/
> 
> Do we need these lines added? We have tools/testing/selftests/kvm/ in the
> common KVM section already. If we do want to specify them specifically,
> then I guess we need x86 and arm MAINTAINERS updates as well.

I think they are helpful in the sense that the s390x maintainers get
CC:-ed on related patches as well, and if I've got Christian right, he's
interested in getting informed here. For Arm related patches, I guess
you should ask the Arm maintainers first. For x86, it does not really
matter, since the maintainers are the same.

 Thomas

  reply	other threads:[~2019-05-23 11:20 UTC|newest]

Thread overview: 58+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-16 11:12 [RFC PATCH 0/4] KVM selftests for s390x Thomas Huth
2019-05-16 11:12 ` Thomas Huth
2019-05-16 11:12 ` thuth
2019-05-16 11:12 ` [RFC PATCH 1/4] KVM: selftests: Guard struct kvm_vcpu_events with __KVM_HAVE_VCPU_EVENTS Thomas Huth
2019-05-16 11:12   ` Thomas Huth
2019-05-16 11:12   ` thuth
2019-05-16 11:22   ` David Hildenbrand
2019-05-16 11:22     ` David Hildenbrand
2019-05-16 11:22     ` david
2019-05-20  7:12   ` Christian Borntraeger
2019-05-20  7:12     ` Christian Borntraeger
2019-05-20  7:12     ` borntraeger
2019-05-20  8:08     ` Thomas Huth
2019-05-20  8:08       ` Thomas Huth
2019-05-20  8:08       ` thuth
2019-05-20  8:13       ` Christian Borntraeger
2019-05-20  8:13         ` Christian Borntraeger
2019-05-20  8:13         ` borntraeger
2019-05-16 11:12 ` [RFC PATCH 2/4] KVM: selftests: Align memory region addresses to 1M on s390x Thomas Huth
2019-05-16 11:12   ` Thomas Huth
2019-05-16 11:12   ` thuth
2019-05-16 11:30   ` David Hildenbrand
2019-05-16 11:30     ` David Hildenbrand
2019-05-16 11:30     ` david
2019-05-16 11:59     ` Thomas Huth
2019-05-16 11:59       ` Thomas Huth
2019-05-16 11:59       ` thuth
2019-05-16 12:08       ` David Hildenbrand
2019-05-16 12:08         ` David Hildenbrand
2019-05-16 12:08         ` david
2019-05-16 11:12 ` [RFC PATCH 3/4] KVM: selftests: Add processor code for s390x Thomas Huth
2019-05-16 11:12   ` Thomas Huth
2019-05-16 11:12   ` thuth
2019-05-16 11:12 ` [RFC PATCH 4/4] KVM: selftests: Add the sync_regs test " Thomas Huth
2019-05-16 11:12   ` Thomas Huth
2019-05-16 11:12   ` thuth
2019-05-20 11:19   ` Paolo Bonzini
2019-05-20 11:19     ` Paolo Bonzini
2019-05-20 11:19     ` pbonzini
2019-05-23 10:56   ` Andrew Jones
2019-05-23 10:56     ` Andrew Jones
2019-05-23 10:56     ` drjones
2019-05-23 11:19     ` Thomas Huth [this message]
2019-05-23 11:19       ` Thomas Huth
2019-05-23 11:19       ` thuth
2019-05-20 11:20 ` [RFC PATCH 0/4] KVM selftests " Paolo Bonzini
2019-05-20 11:20   ` Paolo Bonzini
2019-05-20 11:20   ` pbonzini
2019-05-20 11:30   ` Thomas Huth
2019-05-20 11:30     ` Thomas Huth
2019-05-20 11:30     ` thuth
2019-05-20 11:43     ` Paolo Bonzini
2019-05-20 11:43       ` Paolo Bonzini
2019-05-20 11:43       ` pbonzini
2019-05-20 11:43       ` Paolo Bonzini
2019-05-22  8:44       ` Andrew Jones
2019-05-22  8:44         ` Andrew Jones
2019-05-22  8:44         ` drjones

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=6fbe22d3-b9a9-48c5-8227-743841332ae0@redhat.com \
    --to=thuth@redhat.com \
    --cc=borntraeger@de.ibm.com \
    --cc=cohuck@redhat.com \
    --cc=david@redhat.com \
    --cc=drjones@redhat.com \
    --cc=frankja@linux.ibm.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=rkrcmar@redhat.com \
    --cc=shuah@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.