From: Thomas Huth <thuth@redhat.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>,
kvm@vger.kernel.org, Janosch Frank <frankja@linux.ibm.com>
Cc: linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
"David Hildenbrand" <david@redhat.com>,
"Cornelia Huck" <cohuck@redhat.com>,
"Radim Krčmář" <rkrcmar@redhat.com>
Subject: Re: [PATCH v3] KVM: selftests: Add a test for the KVM_S390_MEM_OP ioctl
Date: Thu, 29 Aug 2019 15:34:54 +0200 [thread overview]
Message-ID: <9457a569-c829-74c9-9836-e9bc76a3ca46@redhat.com> (raw)
In-Reply-To: <c15f4505-95aa-34eb-d618-927af550d00b@de.ibm.com>
On 29/08/2019 15.26, Christian Borntraeger wrote:
>
>
> On 29.08.19 15:07, Thomas Huth wrote:
>> Check that we can write and read the guest memory with this s390x
>> ioctl, and that some error cases are handled correctly.
>>
>> Signed-off-by: Thomas Huth <thuth@redhat.com>
>> ---
>> v3:
>> - Replaced wrong copy-n-pasted report string with a proper one
>> - Check for errno after calling the ioctl with size = 0
>
> the test succeeds (as the vmalloc fails) but dmesg then has the warning.
> Do we have a chance to parse dmesg somehow?
I'm not aware of an easy way to do this from within the KVM selftests.
> I will apply this nevertheless for the time being together with the fix.
Thanks!
Thomas
next prev parent reply other threads:[~2019-08-29 13:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-29 13:07 [PATCH v3] KVM: selftests: Add a test for the KVM_S390_MEM_OP ioctl Thomas Huth
2019-08-29 13:26 ` Christian Borntraeger
2019-08-29 13:34 ` Thomas Huth [this message]
2019-08-29 13:44 ` Christian Borntraeger
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=9457a569-c829-74c9-9836-e9bc76a3ca46@redhat.com \
--to=thuth@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=david@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=rkrcmar@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;
as well as URLs for NNTP newsgroup(s).