public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Petr Vorel <pvorel@suse.cz>
To: "Kubaj, Piotr" <piotr.kubaj@intel.com>
Cc: "Dubel, Helena Anna" <helena.anna.dubel@intel.com>,
	"Ossowski, Tomasz" <tomasz.ossowski@intel.com>,
	"Wysocki, Rafael J" <rafael.j.wysocki@intel.com>,
	"ltp@lists.linux.it" <ltp@lists.linux.it>,
	"Niestepski, Daniel" <daniel.niestepski@intel.com>
Subject: Re: [LTP] [PATCH] high_freq_hwp_cap_cppc.c: new test
Date: Wed, 18 Mar 2026 14:34:42 +0100	[thread overview]
Message-ID: <20260318133442.GA18914@pevik> (raw)
In-Reply-To: <f30646a1e3d1b7bf781385a8d58bc47c52b463fd.camel@intel.com>

> > Hi Piotr,

> > > Verify for all online logical CPUs that their highest performance
> > > value are
> > > the same for HWP Capability MSR 0x771 and CPPC sysfs file.

> > You were supposed to add your RBT:
> > Signed-off-by: Piotr Kubaj <piotr.kubaj@intel.com>

> > > ---
> > >  testcases/kernel/power_management/.gitignore  |  1 +
> > >  .../power_management/high_freq_hwp_cap_cppc.c | 57
> > > +++++++++++++++++++

> > You did not add test into runtest/thermal. OTOH test will apply also
> > after we
> > finally merge thermal_interrupt_events.c.

> It's actually not thermal-related, but there are going to be more
> thermal tests anyway.

I'm sorry, I overlooked power_management directory. Anyway, even in new v2
you haven't added a new test into any runtest file.

Kind regards,
Petr

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

  reply	other threads:[~2026-03-18 13:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-13 12:54 [LTP] [PATCH] high_freq_hwp_cap_cppc.c: new test Piotr Kubaj
2026-03-16 12:33 ` Petr Vorel
2026-03-18 13:05   ` Kubaj, Piotr
2026-03-18 13:34     ` Petr Vorel [this message]
2026-03-16 12:55 ` Andrea Cervesato via ltp
2026-03-18 13:08   ` Kubaj, Piotr

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=20260318133442.GA18914@pevik \
    --to=pvorel@suse.cz \
    --cc=daniel.niestepski@intel.com \
    --cc=helena.anna.dubel@intel.com \
    --cc=ltp@lists.linux.it \
    --cc=piotr.kubaj@intel.com \
    --cc=rafael.j.wysocki@intel.com \
    --cc=tomasz.ossowski@intel.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