From: Alexandru Elisei <alexandru.elisei@arm.com>
To: Andrew Jones <andrew.jones@linux.dev>
Cc: kvm@vger.kernel.org, kvmarm@lists.linux.dev
Subject: Re: [kvm-unit-tests PATCH v4 2/2] arm/psci: Add PSCI CPU_OFF test case
Date: Thu, 19 Jan 2023 10:35:35 +0000 [thread overview]
Message-ID: <Y8kc92nC4tiVXNfs@arm.com> (raw)
In-Reply-To: <20230118184821.frpeemjwt4ey6m7v@orel>
Hi Drew,
On Wed, Jan 18, 2023 at 07:48:21PM +0100, Andrew Jones wrote:
> On Wed, Jan 18, 2023 at 02:49:12PM +0000, Alexandru Elisei wrote:
> > From: Nikita Venkatesh <Nikita.Venkatesh@arm.com>
> >
> > The test uses the following method.
> >
> > The primary CPU brings up all the secondary CPUs, which are held in a wait
> > loop. Once the primary releases the CPUs, each of the secondary CPUs
> > proceed to issue PSCI_CPU_OFF. This is indicated by a cpumask and also the
> > status of the call is updated by the secondary CPU in cpu_off_done[].
> >
> > The primary CPU waits for all the secondary CPUs to update the cpumask and
> > then proceeds to check for the status of the individual CPU CPU_OFF
> > request. There is a chance that some CPUs might fail at the CPU_OFF request
> > and come back and update the status once the primary CPU has finished the
> > scan. There is no fool proof method to handle this. As of now, we add a
> > 1sec delay between the cpumask check and the scan for the status.
> >
> > Signed-off-by: Nikita Venkatesh <Nikita.Venkatesh@arm.com>
> > [ Alex E: Skip CPU_OFF test if CPU_ON failed ]
> > Signed-off-by: Alexandru Elisei <alexandru.elisei@arm.com>
> > ---
> > arm/psci.c | 71 ++++++++++++++++++++++++++++++++++++++++++++++++++----
> > 1 file changed, 66 insertions(+), 5 deletions(-)
> >
> > diff --git a/arm/psci.c b/arm/psci.c
> > index e96be941953b..d045616bfcd4 100644
> > --- a/arm/psci.c
> > +++ b/arm/psci.c
> > @@ -15,6 +15,8 @@
> > #include <asm/psci.h>
> > #include <asm/smp.h>
> >
> > +#define CPU_OFF_TEST_WAIT_TIME 1000
> > +
> > static bool invalid_function_exception;
> >
> > #ifdef __arm__
> > @@ -71,8 +73,10 @@ static bool psci_affinity_info_off(void)
> > }
> >
> > static int cpu_on_ret[NR_CPUS];
> > -static cpumask_t cpu_on_ready, cpu_on_done;
> > +static bool cpu_off_success[NR_CPUS];
> > +static cpumask_t cpu_on_ready, cpu_on_done, cpu_off_done;
> > static volatile int cpu_on_start;
> > +static volatile int cpu_off_start;
> >
> > extern void secondary_entry(void);
> > static void cpu_on_do_wake_target(void)
> > @@ -94,6 +98,20 @@ static void cpu_on_target(void)
> > cpumask_set_cpu(cpu, &cpu_on_done);
> > }
> >
> > +static void cpu_off_secondary_entry(void *data)
> > +{
> > + int cpu = smp_processor_id();
> > +
> > + while (!cpu_off_start)
> > + cpu_relax();
> > + /* On to the CPU off test */
> > + cpu_off_success[cpu] = true;
> > + cpumask_set_cpu(cpu, &cpu_off_done);
> > + cpu_psci_cpu_die();
> > + /* The CPU shouldn't execute the next steps. */
> > + cpu_off_success[cpu] = false;
> > +}
> > +
> > static bool psci_cpu_on_test(void)
> > {
> > bool failed = false;
> > @@ -162,9 +180,45 @@ out:
> > return !failed;
> > }
> >
> > -int main(void)
> > +static bool psci_cpu_off_test(void)
> > +{
> > + bool failed = false;
> > + int cpu;
> > +
> > + for_each_present_cpu(cpu) {
> > + if (cpu == 0)
> > + continue;
> > + on_cpu_async(cpu, cpu_off_secondary_entry, NULL);
> > + }
> > +
> > + cpumask_set_cpu(0, &cpu_off_done);
>
> Since we're setting cpu_off_done for cpu0, then we could also set
> cpu_off_success[0] = true and not have to skip it in the check loop
> below.
I would prefer not to, since CPU 0 never invokes CPU_OFF for itself and setting
cpu_off_success to true for CPU 0 might get confusing. Unless you insist :)
>
> > +
> > + report_info("starting CPU_OFF test...");
> > +
> > + cpu_off_start = 1;
> > + while (!cpumask_full(&cpu_off_done))
> > + cpu_relax();
> > +
> > + /* Allow all the other CPUs to complete the operation */
> > + mdelay(CPU_OFF_TEST_WAIT_TIME);
>
> Don't really need the define, just the numbers work for stuff
> like this, but OK.
I'll get rid of the define.
You ok with waiting for 1 second for each test run? I remember you had
objections when I added a similar delay to the timer tests.
>
> > +
> > + for_each_present_cpu(cpu) {
> > + if (cpu == 0)
> > + continue;
> > +
> > + if (!cpu_off_success[cpu]) {
> > + report_info("CPU%d could not be turned off", cpu);
> > + failed = true;
> > + }
> > + }
> > +
> > + return !failed;
> > +}
> > +
> > +int main(int argc, char **argv)
> > {
> > int ver = psci_invoke(PSCI_0_2_FN_PSCI_VERSION, 0, 0, 0);
> > + bool cpu_on_success = true;
> >
> > report_prefix_push("psci");
> >
> > @@ -179,10 +233,17 @@ int main(void)
> > report(psci_affinity_info_on(), "affinity-info-on");
> > report(psci_affinity_info_off(), "affinity-info-off");
> >
> > - if (ERRATA(6c7a5dce22b3))
> > - report(psci_cpu_on_test(), "cpu-on");
> > - else
> > + if (ERRATA(6c7a5dce22b3)) {
> > + cpu_on_success = psci_cpu_on_test();
> > + report(cpu_on_success, "cpu-on");
> > + } else {
> > report_skip("Skipping unsafe cpu-on test. Set ERRATA_6c7a5dce22b3=y to enable.");
> > + }
> > +
> > + if (!cpu_on_success)
> > + report_skip("Skipping cpu-off test because the cpu-on test failed");
> > + else
> > + report(psci_cpu_off_test(), "cpu-off");
> >
> > done:
> > #if 0
> > --
> > 2.25.1
> >
>
> Besides the nits,
>
> Reviewed-by: Andrew Jones <andrew.jones@linux.dev>
Thanks!
Alex
>
> Thanks,
> drew
next prev parent reply other threads:[~2023-01-19 10:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-18 14:49 [kvm-unit-tests PATCH v4 0/2] arm: Add PSCI CPU_OFF test Alexandru Elisei
2023-01-18 14:49 ` [kvm-unit-tests PATCH v4 1/2] arm/psci: Test that CPU 1 has been successfully brought online Alexandru Elisei
2023-01-18 18:35 ` Andrew Jones
2023-01-19 10:32 ` Alexandru Elisei
2023-01-19 11:01 ` Andrew Jones
2023-01-19 11:46 ` Andrew Jones
2023-01-18 14:49 ` [kvm-unit-tests PATCH v4 2/2] arm/psci: Add PSCI CPU_OFF test case Alexandru Elisei
2023-01-18 18:48 ` Andrew Jones
2023-01-19 10:35 ` Alexandru Elisei [this message]
2023-01-19 11:36 ` Andrew Jones
2023-01-19 11:45 ` Andrew Jones
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=Y8kc92nC4tiVXNfs@arm.com \
--to=alexandru.elisei@arm.com \
--cc=andrew.jones@linux.dev \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.linux.dev \
/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