All of lore.kernel.org
 help / color / mirror / Atom feed
From: srinivas pandruvada <srinivas.pandruvada@linux.intel.com>
To: Borislav Petkov <bp@alien8.de>
Cc: rafael@kernel.org, viresh.kumar@linaro.org, tglx@linutronix.de,
	 mingo@redhat.com, dave.hansen@linux.intel.com, hpa@zytor.com,
	 linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
	x86@kernel.org
Subject: Re: [PATCH 2/2] cpufreq: intel_pstate: Support highest performance change interrupt
Date: Tue, 18 Jun 2024 03:11:18 -0700	[thread overview]
Message-ID: <12e498226b33c6cb30e40dac6a11652f29ef48ea.camel@linux.intel.com> (raw)
In-Reply-To: <20240618090836.GBZnFOlFurqQiLeI7a@fat_crate.local>

Hi Borislav,

On Tue, 2024-06-18 at 11:08 +0200, Borislav Petkov wrote:
> On Mon, Jun 17, 2024 at 08:51:21PM -0700, Srinivas Pandruvada wrote:
> > +       status_mask = HWP_GUARANTEED_PERF_CHANGE_STATUS;
> > +       if (boot_cpu_has(X86_FEATURE_HWP_HIGHEST_PERF_CHANGE))
> 
> s/boot_cpu_has/cpu_feature_enabled/g

I will change in V2

> > +               status_mask |= HWP_HIGHEST_PERF_CHANGE_STATUS;
> > +
> >         rdmsrl_safe(MSR_HWP_STATUS, &value);
> > -       if (!(value & 0x01))
> > +       if (!(value & status_mask))
> >                 return;
> >  
> >         spin_lock_irqsave(&hwp_notify_lock, flags);
> > @@ -1668,17 +1675,25 @@ static void
> > intel_pstate_disable_hwp_interrupt(struct cpudata *cpudata)
> >                 cancel_delayed_work_sync(&cpudata-
> > >hwp_notify_work);
> >  }
> >  
> > +#define HWP_GUARANTEED_PERF_CHANGE_REQ BIT(0)
> > +#define HWP_HIGHEST_PERF_CHANGE_REQ    BIT(2)
> > +
> >  static void intel_pstate_enable_hwp_interrupt(struct cpudata
> > *cpudata)
> >  {
> > -       /* Enable HWP notification interrupt for guaranteed
> > performance change */
> > +       /* Enable HWP notification interrupt for performance change
> > */
> >         if (boot_cpu_has(X86_FEATURE_HWP_NOTIFY)) {
> > +               u64 interrupt_mask =
> > HWP_GUARANTEED_PERF_CHANGE_REQ;
> > +
> >                 spin_lock_irq(&hwp_notify_lock);
> >                 INIT_DELAYED_WORK(&cpudata->hwp_notify_work,
> > intel_pstate_notify_work);
> >                 cpumask_set_cpu(cpudata->cpu,
> > &hwp_intr_enable_mask);
> >                 spin_unlock_irq(&hwp_notify_lock);
> >  
> > +               if
> > (boot_cpu_has(X86_FEATURE_HWP_HIGHEST_PERF_CHANGE))a
> 
> Ditto.

Will change in v2.


Thanks,
Srinivas


      reply	other threads:[~2024-06-18 10:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-18  3:51 [PATCH 0/2] Update highest frequency of a CPU after boot Srinivas Pandruvada
2024-06-18  3:51 ` [PATCH 1/2] x86/cpufeatures: Add HWP highest perf change feature flag Srinivas Pandruvada
2024-06-18  9:07   ` Borislav Petkov
2024-06-18 10:25     ` srinivas pandruvada
2024-06-18  3:51 ` [PATCH 2/2] cpufreq: intel_pstate: Support highest performance change interrupt Srinivas Pandruvada
2024-06-18  9:08   ` Borislav Petkov
2024-06-18 10:11     ` srinivas pandruvada [this message]

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=12e498226b33c6cb30e40dac6a11652f29ef48ea.camel@linux.intel.com \
    --to=srinivas.pandruvada@linux.intel.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=rafael@kernel.org \
    --cc=tglx@linutronix.de \
    --cc=viresh.kumar@linaro.org \
    --cc=x86@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.