Linux Kernel Selftest development
 help / color / mirror / Atom feed
From: Shuah Khan <skhan@linuxfoundation.org>
To: Xinyu Zheng <zhengxinyu6@huawei.com>, Shuah Khan <shuah@kernel.org>
Cc: Moon Hee Lee <moonhee.lee.ca@gmail.com>,
	yifei.l.liu@oracle.com, zhujun2@cmss.chinamobile.com,
	linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
	zouyipeng@huawei.com, Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH] selftests: breakpoints: check RTC wakeup alarm support before test
Date: Wed, 19 Nov 2025 15:15:02 -0700	[thread overview]
Message-ID: <b0ceed9c-3ff6-4eee-80e3-f50631bb1230@linuxfoundation.org> (raw)
In-Reply-To: <20251112061532.2867859-1-zhengxinyu6@huawei.com>

On 11/11/25 23:15, Xinyu Zheng wrote:
> If RTC wakeup alarm feature is unsupported, this testcase may cause

It may cause infinite suspend? Doesn't sound definitive.> infinite suspend if there is no other wakeup source. To solve this
> problem, set wakeup alarm up before we trigger suspend. In this case,
> we can test if RTC support RTC_FEATURE_ALARM and efi_set_alarm function.
> 

For a "may cause" problem, this change> Signed-off-by: Xinyu Zheng <zhengxinyu6@huawei.com>
> --->   .../breakpoints/step_after_suspend_test.c     | 23 +++++++++++++++++++
>   1 file changed, 23 insertions(+)
> 
> diff --git a/tools/testing/selftests/breakpoints/step_after_suspend_test.c b/tools/testing/selftests/breakpoints/step_after_suspend_test.c
> index 8d233ac95696..e738af896ce1 100644
> --- a/tools/testing/selftests/breakpoints/step_after_suspend_test.c
> +++ b/tools/testing/selftests/breakpoints/step_after_suspend_test.c
> @@ -13,6 +13,8 @@
>   #include <stdio.h>
>   #include <string.h>
>   #include <unistd.h>
> +#include <linux/rtc.h>
> +#include <sys/ioctl.h>
>   #include <sys/ptrace.h>
>   #include <sys/stat.h>
>   #include <sys/timerfd.h>
> @@ -159,10 +161,30 @@ void suspend(void)
>   	int count_before;
>   	int count_after;
>   	struct itimerspec spec = {};
> +	char *rtc_file = "/dev/rtc0";
> +	int rtc_fd;
> +	struct rtc_wkalrm alarm = { 0 };
> +	time_t secs;
>   
>   	if (getuid() != 0)
>   		ksft_exit_skip("Please run the test as root - Exiting.\n");
>   
> +	rtc_fd = open(rtc_file, O_RDONLY);
> +	if (rtc_fd < 0)
> +		ksft_exit_fail_msg("open rtc0 failed\n");
> +
> +	err = ioctl(rtc_fd, RTC_RD_TIME, &alarm.time);
> +	if (err < 0)
> +		ksft_exit_fail_msg("get rtc time failed\n");
> +
> +	secs = timegm((struct tm *)&alarm.time) + 3;
> +	gmtime_r(&secs, (struct tm *)&alarm.time);
> +	alarm.enabled = 1;
> +
> +	err = ioctl(rtc_fd, RTC_WKALM_SET, &alarm);
> +	if (err < 0)
> +		ksft_exit_fail_msg("set wake alarm test failed, errno %d\n", errno);

Essentially with this change the test doesn't run unless
RTC wake is supported. That sounds restrictive - is there
another way do do this?

> +
>   	timerfd = timerfd_create(CLOCK_BOOTTIME_ALARM, 0);
>   	if (timerfd < 0)
>   		ksft_exit_fail_msg("timerfd_create() failed\n");
> @@ -180,6 +202,7 @@ void suspend(void)
>   	if (count_after <= count_before)
>   		ksft_exit_fail_msg("Failed to enter Suspend state\n");
>   
> +	close(rtc_fd);
>   	close(timerfd);
>   }
>  
thanks,
-- Shuah

  reply	other threads:[~2025-11-19 22:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-12  6:15 [PATCH] selftests: breakpoints: check RTC wakeup alarm support before test Xinyu Zheng
2025-11-19 22:15 ` Shuah Khan [this message]
2025-12-01  8:31   ` Xinyu Zheng

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=b0ceed9c-3ff6-4eee-80e3-f50631bb1230@linuxfoundation.org \
    --to=skhan@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=moonhee.lee.ca@gmail.com \
    --cc=shuah@kernel.org \
    --cc=yifei.l.liu@oracle.com \
    --cc=zhengxinyu6@huawei.com \
    --cc=zhujun2@cmss.chinamobile.com \
    --cc=zouyipeng@huawei.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