From: Vlastimil Babka <vbabka@suse.cz>
To: Shuah Khan <skhan@linuxfoundation.org>,
David Hildenbrand <david@redhat.com>,
Alex Sierra <alex.sierra@amd.com>,
Alistair Popple <apopple@nvidia.com>
Cc: Jason Gunthorpe <jgg@nvidia.com>,
Ralph Campbell <rcampbell@nvidia.com>,
Felix Kuehling <Felix.Kuehling@amd.com>,
Christoph Hellwig <hch@lst.de>,
Jerome Glisse <jglisse@redhat.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"open list:KERNEL SELFTEST FRAMEWORK"
<linux-kselftest@vger.kernel.org>, Shuah Khan <shuah@kernel.org>
Subject: Re: hmm_test issues with latest mainline
Date: Thu, 13 Oct 2022 21:43:48 +0200 [thread overview]
Message-ID: <2d4b8d64-f17f-90ad-7328-b5ca7537d08a@suse.cz> (raw)
In-Reply-To: <a7b3cf86-4578-c23d-7326-4ddf7dcda043@linuxfoundation.org>
On 10/13/2022 9:38 PM, Shuah Khan wrote:
> On 10/13/22 12:00, David Hildenbrand wrote:
>>>>>> When did that test start failing? Was it still ok for 6.0?
>>>>
>>>> Didn't test yet, will try, in case it's my system/config specific thing.
>>>
>>> So it's actually all the same with v6.0 for me. The infinite loops, the test
>>> failures, the misreported SKIPs.
>>>
>
> I am not seeing infinite loops and seeing 25 failures which could
> be skips.
>
>>
>> Is the kernel compiled with support. I have the feeling that we might simply miss kernel support and it's not handled gracefully ...
>>
>
> Here is my config
> CONFIG_HMM_MIRROR=y
> # CONFIG_TEST_HMM is not set
>
> Okay here is what is going on - hmm_tests are supposed to be run
> from test_hmm.sh script. When I run this I see a message that tells
> me what to do.
>
> sudo ./test_hmm.sh
> ./test_hmm.sh: You must have the following enabled in your kernel:
> CONFIG_TEST_HMM=m
>
> Running ./hmm_tests gives me all the failures. So it appears running
> hmm_tests executable won't work. This is expected as test_hmm.sh does
> the right setup before running the test. We have several tests that do
> that.
>
> Vlastimil, can you try this and let me know what you see. I will compile
> with CONFIG_TEST_HMM=m and let you know what I see on my system.
Right, I didn't mention it, sorry. I did have CONFIG_TEST_HMM=m and was running
"test_hmm.sh smoke"
> thanks,
> -- Shuah
>
>
>
next prev parent reply other threads:[~2022-10-13 19:43 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-13 16:54 Vlastimil Babka
2022-10-13 17:01 ` David Hildenbrand
2022-10-13 17:10 ` Shuah Khan
2022-10-13 17:12 ` Vlastimil Babka
2022-10-13 17:29 ` Shuah Khan
2022-10-13 17:45 ` Vlastimil Babka
2022-10-13 18:00 ` David Hildenbrand
2022-10-13 19:38 ` Shuah Khan
2022-10-13 19:43 ` Vlastimil Babka [this message]
2022-10-14 1:45 ` Alistair Popple
2022-10-14 3:21 ` Alistair Popple
2022-10-14 6:53 ` Vlastimil Babka
2022-10-14 6:45 ` Vlastimil Babka
2022-10-13 17:03 ` Shuah Khan
2022-10-13 17:10 ` Vlastimil Babka
2022-10-14 12:01 ` Jason Gunthorpe
2022-10-14 15:03 ` Felix Kuehling
2022-10-14 15:47 ` Jason Gunthorpe
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=2d4b8d64-f17f-90ad-7328-b5ca7537d08a@suse.cz \
--to=vbabka@suse.cz \
--cc=Felix.Kuehling@amd.com \
--cc=alex.sierra@amd.com \
--cc=apopple@nvidia.com \
--cc=david@redhat.com \
--cc=hch@lst.de \
--cc=jgg@nvidia.com \
--cc=jglisse@redhat.com \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rcampbell@nvidia.com \
--cc=shuah@kernel.org \
--cc=skhan@linuxfoundation.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