linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Dev Jain <dev.jain@arm.com>
To: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
Cc: akpm@linux-foundation.org, Liam.Howlett@oracle.com,
	shuah@kernel.org, pfalcato@suse.de, vbabka@suse.cz,
	jannh@google.com, pulehui@huawei.com, linux-mm@kvack.org,
	linux-kselftest@vger.kernel.org, aishwarya.tcv@arm.com,
	broonie@kernel.org, ryan.roberts@arm.com
Subject: Re: [PATCH] selftests/mm: Add CONFIG_FTRACE to config
Date: Wed, 11 Jun 2025 18:21:22 +0530	[thread overview]
Message-ID: <d38ea060-38a0-4672-a4ea-2a52e1d0fdd7@arm.com> (raw)
In-Reply-To: <452f1851-5511-4326-a206-86e119b58841@lucifer.local>


On 11/06/25 6:05 pm, Lorenzo Stoakes wrote:
> Thanks for this!
>
> On Wed, Jun 11, 2025 at 05:40:11PM +0530, Dev Jain wrote:
>> If CONFIG_UPROBES is not set, a merge subtest fails:
>>
>> Failure log:
>>
>>    7151 12:46:54.627936  # # #  RUN           merge.handle_uprobe_upon_merged_vma ...
>>    7152 12:46:54.639014  # # f /sys/bus/event_source/devices/uprobe/type
>>    7153 12:46:54.639306  # # fopen: No such file or directory
>>    7154 12:46:54.650451  # # # merge.c:473:handle_uprobe_upon_merged_vma:Expected read_sysfs("/sys/bus/event_source/devices/uprobe/type", &type) (1) == 0 (0)
>>    7155 12:46:54.650730  # # # handle_uprobe_upon_merged_vma: Test terminated by assertion
>>    7156 12:46:54.661750  # # #          FAIL  merge.handle_uprobe_upon_merged_vma
>>    7157 12:46:54.662030  # # not ok 8 merge.handle_uprobe_upon_merged_vma
>>
>> CONFIG_UPROBES is enabled by CONFIG_UPROBE_EVENTS, which gets enabled by
>> CONFIG_FTRACE. Therefore add this config to selftests/mm/config so that
>> CI systems can include this config in the kernel build.
> OK I see the dependency chain here:
>
> menuconfig FTRACE
>       bool "Tracers"
>       depends on TRACING_SUPPORT
>       default y if DEBUG_KERNEL
>       help
>         Enable the kernel tracing infrastructure.
>
> if FTRACE
>
> ...
>
> endif # FTRACE
>
> ..
>
> config UPROBE_EVENTS
>       bool "Enable uprobes-based dynamic events"
>       depends on ARCH_SUPPORTS_UPROBES
>       depends on MMU
>       depends on PERF_EVENTS
>       select UPROBES
>       select PROBE_EVENTS
>       select DYNAMIC_EVENTS
>       select TRACING
>       default y
>
> ...
>
>
> However we also need PERF_EVENTS w, which is defaulted to y if CONFIG_PROFILING
> is set:
>
> config PERF_EVENTS
>       bool "Kernel performance events and counters"
>       default y if PROFILING
>       depends on HAVE_PERF_EVENTS
>       select IRQ_WORK
>
> ...
>
>
> config PROFILING
>       bool "Profiling support"
>       help
>         Say Y here to enable the extended profiling support mechanisms used
>         by profilers.
>
> So maybe to be totally and completely pedantic we should add CONFIG_PROFILING
> here too.

I don't totally understand this config stuff but I will trust you and update
this in v2 : )

>
>> Fixes: efe99fabeb11b ("selftests/mm: add test about uprobe pte be orphan during vma merge")
>> Reported-by: Aishwarya <aishwarya.tcv@arm.com>
>> Closes: https://lore.kernel.org/all/20250610103729.72440-1-aishwarya.tcv@arm.com/
> This is already (semi-)addressed by
> https://lore.kernel.org/linux-mm/20250610122209.3177587-1-pfalcato@suse.de/,
> perhaps worth mentioning?
>
> Pedro's patch is still important, as for any system that hasn't happened to set
> this up, we get a skip + information rather than a failure.
>
>> Signed-off-by: Dev Jain <dev.jain@arm.com>
> This looks correct, see above for nits etc. but:
>
> Reviewed-by: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>

Thanks.

>
>> ---
>>   tools/testing/selftests/mm/config | 1 +
>>   1 file changed, 1 insertion(+)
>>
>> diff --git a/tools/testing/selftests/mm/config b/tools/testing/selftests/mm/config
>> index a28baa536332..e600b41030c1 100644
>> --- a/tools/testing/selftests/mm/config
>> +++ b/tools/testing/selftests/mm/config
>> @@ -8,3 +8,4 @@ CONFIG_GUP_TEST=y
>>   CONFIG_TRANSPARENT_HUGEPAGE=y
>>   CONFIG_MEM_SOFT_DIRTY=y
>>   CONFIG_ANON_VMA_NAME=y
>> +CONFIG_FTRACE=y
>> --
>> 2.30.2
>>
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.


  reply	other threads:[~2025-06-11 12:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-11 12:10 Dev Jain
2025-06-11 12:26 ` Aishwarya
2025-06-11 12:30 ` Pedro Falcato
2025-06-12  6:28   ` Dev Jain
2025-06-12 10:04     ` Pedro Falcato
2025-06-11 12:35 ` Lorenzo Stoakes
2025-06-11 12:51   ` Dev Jain [this message]
2025-06-11 12:39 ` Mark Brown
2025-06-11 12:50   ` Dev Jain
2025-06-11 14:01 ` Donet Tom

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=d38ea060-38a0-4672-a4ea-2a52e1d0fdd7@arm.com \
    --to=dev.jain@arm.com \
    --cc=Liam.Howlett@oracle.com \
    --cc=aishwarya.tcv@arm.com \
    --cc=akpm@linux-foundation.org \
    --cc=broonie@kernel.org \
    --cc=jannh@google.com \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lorenzo.stoakes@oracle.com \
    --cc=pfalcato@suse.de \
    --cc=pulehui@huawei.com \
    --cc=ryan.roberts@arm.com \
    --cc=shuah@kernel.org \
    --cc=vbabka@suse.cz \
    /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