From: "Christoph Schlameuss" <schlameuss@linux.ibm.com>
To: "Claudio Imbrenda" <imbrenda@linux.ibm.com>,
"David Hildenbrand" <david@redhat.com>
Cc: <kvm@vger.kernel.org>, <linux-s390@vger.kernel.org>,
<frankja@linux.ibm.com>, <borntraeger@de.ibm.com>,
<willy@infradead.org>, <hca@linux.ibm.com>, <svens@linux.ibm.com>,
<agordeev@linux.ibm.com>, <gor@linux.ibm.com>,
<nrb@linux.ibm.com>, <nsg@linux.ibm.com>, <seanjc@google.com>,
<seiden@linux.ibm.com>
Subject: Re: [PATCH v3 04/15] KVM: s390: selftests: fix ucontrol memory region test
Date: Mon, 20 Jan 2025 16:40:30 +0100 [thread overview]
Message-ID: <D770IISGV0WG.2QZ4BTF9VJHND@linux.ibm.com> (raw)
In-Reply-To: <20250120132531.625e2ab2@p-imbrenda>
On Mon Jan 20, 2025 at 1:25 PM CET, Claudio Imbrenda wrote:
> On Mon, 20 Jan 2025 13:12:31 +0100
> David Hildenbrand <david@redhat.com> wrote:
>
> > On 17.01.25 20:09, Claudio Imbrenda wrote:
> > > With the latest patch, attempting to create a memslot from userspace
> > > will result in an EEXIST error for UCONTROL VMs, instead of EINVAL,
> > > since the new memslot will collide with the internal memslot. There is
> > > no simple way to bring back the previous behaviour.
> > >
> > > This is not a problem, but the test needs to be fixed accordingly.
> > >
> > > Signed-off-by: Claudio Imbrenda <imbrenda@linux.ibm.com>
> > > ---
> > > tools/testing/selftests/kvm/s390x/ucontrol_test.c | 6 ++++--
> > > 1 file changed, 4 insertions(+), 2 deletions(-)
> > >
> > > diff --git a/tools/testing/selftests/kvm/s390x/ucontrol_test.c b/tools/testing/selftests/kvm/s390x/ucontrol_test.c
> > > index 135ee22856cf..ca18736257f8 100644
> > > --- a/tools/testing/selftests/kvm/s390x/ucontrol_test.c
> > > +++ b/tools/testing/selftests/kvm/s390x/ucontrol_test.c
> > > @@ -459,10 +459,12 @@ TEST_F(uc_kvm, uc_no_user_region)
> > > };
> > >
> > > ASSERT_EQ(-1, ioctl(self->vm_fd, KVM_SET_USER_MEMORY_REGION, ®ion));
> > > - ASSERT_EQ(EINVAL, errno);
> > > + if (errno != EEXIST)
> > > + ASSERT_EQ(EINVAL, errno);
> >
> > ASSERT_TRUE(errno == EEXIST || errno == EINVAL)'
> >
> > ?
> >
How about this?
ASSERT_TRUE(errno == EEXIST || errno == EINVAL)
TH_LOG("errno %s (%i) not expected for ioctl KVM_SET_USER_MEMORY_REGION",
strerror(errno), errno);
>
> I had thought about that, but in case of failure it won't print the
> failing value.
>
> It's probably more readable with the ASSERT_EQ, I will change it.
next prev parent reply other threads:[~2025-01-20 15:40 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-17 19:09 [PATCH v3 00/15] KVM: s390: Stop using page->index and other things Claudio Imbrenda
2025-01-17 19:09 ` [PATCH v3 01/15] KVM: Do not restrict the size of KVM-internal memory regions Claudio Imbrenda
2025-01-20 12:06 ` David Hildenbrand
2025-01-17 19:09 ` [PATCH v3 02/15] KVM: s390: wrapper for KVM_BUG Claudio Imbrenda
2025-01-20 12:07 ` David Hildenbrand
2025-01-17 19:09 ` [PATCH v3 03/15] KVM: s390: fake memslot for ucontrol VMs Claudio Imbrenda
2025-01-20 12:09 ` David Hildenbrand
2025-01-20 15:27 ` Christoph Schlameuss
2025-01-21 16:33 ` Claudio Imbrenda
2025-01-21 12:23 ` Janosch Frank
2025-01-17 19:09 ` [PATCH v3 04/15] KVM: s390: selftests: fix ucontrol memory region test Claudio Imbrenda
2025-01-20 12:12 ` David Hildenbrand
2025-01-20 12:25 ` Claudio Imbrenda
2025-01-20 15:40 ` Christoph Schlameuss [this message]
2025-01-17 19:09 ` [PATCH v3 05/15] KVM: s390: move pv gmap functions into kvm Claudio Imbrenda
2025-01-21 10:55 ` Christoph Schlameuss
2025-01-21 12:54 ` Janosch Frank
2025-01-17 19:09 ` [PATCH v3 06/15] KVM: s390: use __kvm_faultin_pfn() Claudio Imbrenda
2025-01-21 15:11 ` Christoph Schlameuss
2025-01-17 19:09 ` [PATCH v3 07/15] KVM: s390: get rid of gmap_fault() Claudio Imbrenda
2025-01-22 9:44 ` Christoph Schlameuss
2025-01-17 19:09 ` [PATCH v3 08/15] KVM: s390: get rid of gmap_translate() Claudio Imbrenda
2025-01-22 9:59 ` Christoph Schlameuss
2025-01-17 19:09 ` [PATCH v3 09/15] KVM: s390: move some gmap shadowing functions away from mm/gmap.c Claudio Imbrenda
2025-01-21 13:30 ` Janosch Frank
2025-01-22 12:50 ` Christoph Schlameuss
2025-01-22 15:05 ` Janosch Frank
2025-01-17 19:09 ` [PATCH v3 10/15] KVM: s390: stop using page->index for non-shadow gmaps Claudio Imbrenda
2025-01-21 13:41 ` Janosch Frank
2025-01-17 19:09 ` [PATCH v3 11/15] KVM: s390: stop using lists to keep track of used dat tables Claudio Imbrenda
2025-01-20 15:10 ` Steffen Eiden
2025-01-20 15:29 ` Claudio Imbrenda
2025-01-21 14:09 ` Janosch Frank
2025-01-22 16:13 ` Christoph Schlameuss
2025-01-22 16:19 ` Claudio Imbrenda
2025-01-17 19:09 ` [PATCH v3 12/15] KVM: s390: move gmap_shadow_pgt_lookup() into kvm Claudio Imbrenda
2025-01-21 14:23 ` Janosch Frank
2025-01-17 19:09 ` [PATCH v3 13/15] KVM: s390: remove useless page->index usage Claudio Imbrenda
2025-01-17 19:09 ` [PATCH v3 14/15] KVM: s390: move PGSTE softbits Claudio Imbrenda
2025-01-17 19:09 ` [PATCH v3 15/15] KVM: s390: remove the last user of page->index Claudio Imbrenda
2025-01-21 14:44 ` Janosch Frank
2025-01-21 14:48 ` Claudio Imbrenda
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=D770IISGV0WG.2QZ4BTF9VJHND@linux.ibm.com \
--to=schlameuss@linux.ibm.com \
--cc=agordeev@linux.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=david@redhat.com \
--cc=frankja@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=imbrenda@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=nrb@linux.ibm.com \
--cc=nsg@linux.ibm.com \
--cc=seanjc@google.com \
--cc=seiden@linux.ibm.com \
--cc=svens@linux.ibm.com \
--cc=willy@infradead.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