All of lore.kernel.org
 help / color / mirror / Atom feed
From: srinivas pandruvada <srinivas.pandruvada@linux.intel.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: daniel.lezcano@linaro.org, rui.zhang@intel.com,
	linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/7] thermal: processor_thermal: Suport workload hint
Date: Tue, 12 Sep 2023 12:44:10 -0700	[thread overview]
Message-ID: <275e34c2e67a85c087ff983354bf74b5257b2fc4.camel@linux.intel.com> (raw)
In-Reply-To: <CAJZ5v0jrKSUOGG72w-EdzhQqC==CA7zYUofNSEW1wV-58TOnLw@mail.gmail.com>

Hi Rafael,

On Tue, 2023-09-12 at 16:09 +0200, Rafael J. Wysocki wrote:
> On Tue, Aug 29, 2023 at 2:23 AM Srinivas Pandruvada
> <srinivas.pandruvada@linux.intel.com> wrote:
> > 
> > 

[...]

> > --
> 
> There is a slight issue with the patch ordering in this series,
> because the interface to enable the interrupt should only be provided
> after implementing the interrupt handlers.  I don't think that anyone
> will apply the series partially and try to enable the feature,
> though.
Thanks!

> 
> Also, I'm not actually sure if proc_thermal_wt_intr_callback() can
> run
> safely against the work item scheduled in proc_thermal_irq_handler()
> in case the workload hint one triggers along with a thermal threshold
> one.  I think that the access to MMIO is cached, so what if they both
> try to update the same cache line at the same time?  Or are they
> guaranteed to be different cache lines?
These two registers are 90 cache lines apart. Looking at all the
registers on this bar for status offsets, they are several cache lines
apart. Also this bar is non prefetchable, so continuous data can't be
fetched ahead.


> 
> Anyway, tentatively applied as 6.7 material, but I've changed the
> second patch somewhat, because I couldn't convince myself that the
> implicit type conversions in
> processor_thermal_mbox_interrupt_config()
> would always do the right thing regardless of the numbers involved,
> so
> please check the result in my bleeding-edge branch.
> 
If I diff, there is only one change in processor_thermal_mbox.c. Tested
that change and works fine.

Thanks,
Srinivas


> Thanks!


  reply	other threads:[~2023-09-12 19:44 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-29  0:23 [PATCH v3 0/7] thermal: processor_thermal: Suport workload hint Srinivas Pandruvada
2023-08-29  0:23 ` [PATCH v3 1/7] thermal: int340x: processor_thermal: Move mailbox code to common module Srinivas Pandruvada
2023-08-29  0:23 ` [PATCH v3 2/7] thermal: int340x: processor_thermal: Add interrupt configuration Srinivas Pandruvada
2023-08-29  0:23 ` [PATCH v3 3/7] thermal: int340x: processor_thermal: Use non MSI interrupts by default Srinivas Pandruvada
2023-08-29  0:23 ` [PATCH v3 4/7] thermal/drivers/int340x: Remove PROC_THERMAL_FEATURE_WLT_REQ for Meteor Lake Srinivas Pandruvada
2023-08-29  0:23 ` [PATCH v3 5/7] thermal: int340x: processor_thermal: Add workload type hint interface Srinivas Pandruvada
2023-08-29  0:23 ` [PATCH v3 6/7] thermal/drivers/int340x: Support workload hint interrupts Srinivas Pandruvada
2023-08-29  0:23 ` [PATCH v3 7/7] selftests/thermel/intel: Add test to read workload hint Srinivas Pandruvada
2023-09-12 14:09 ` [PATCH v3 0/7] thermal: processor_thermal: Suport " Rafael J. Wysocki
2023-09-12 19:44   ` srinivas pandruvada [this message]
2023-09-13  8:15     ` Rafael J. Wysocki

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=275e34c2e67a85c087ff983354bf74b5257b2fc4.camel@linux.intel.com \
    --to=srinivas.pandruvada@linux.intel.com \
    --cc=daniel.lezcano@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=rafael@kernel.org \
    --cc=rui.zhang@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 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.