Linux EDAC development
 help / color / mirror / Atom feed
From: "Farber, Eliav" <farbere@amazon.com>
To: Borislav Petkov <bp@alien8.de>
Cc: <mchehab@kernel.org>, <tony.luck@intel.com>,
	<james.morse@arm.com>, <rric@kernel.org>,
	<linux-edac@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<talel@amazon.com>, <jonnyc@amazon.com>, <hhhawa@amazon.com>,
	<hanochu@amazon.com>, <itamark@amazon.com>, <shellykz@amazon.com>,
	<amitlavi@amazon.com>, <dkl@amazon.com>
Subject: Re: [PATCH v2] edac: fix period calculation in edac_device_reset_delay_period()
Date: Thu, 29 Dec 2022 22:17:48 +0200	[thread overview]
Message-ID: <aebd2f07-674c-b848-69e7-5479d111bad1@amazon.com> (raw)
In-Reply-To: <Y62xA548/wQAggRL@zn.tnic>

On 12/29/2022 5:23 PM, Borislav Petkov wrote:
> On Thu, Oct 20, 2022 at 12:44:58PM +0000, Eliav Farber wrote:
>> Fix period calculation in case user sets a value of 1000.
>> The input of round_jiffies_relative() should be in jiffies and not in
>> milli-seconds.
>>
>> Signed-off-by: Eliav Farber <farbere@amazon.com>
>
> Fixes: c4cf3b454eca ("EDAC: Rework workqueue handling")
>
> I guess.
>
> Also, I think the one-liner below does the same, no?

The one-liner below will not work.
See the comment in edac_device_workq_setup() that explains why round
is used:
"
optimize here for the 1 second case, which will be normal value, to
fire ON the 1 second time event. This helps reduce all sorts of
timers firing on sub-second basis, while they are happy
to fire together on the 1 second exactly
"
So only the first schedule should be rounded.
But all other schedules after that should be 1000ms.
When rounding jiffs and saving it in edac_dev->delay it means that all
future schedules will not be with the correct delay.

The fix I suggested is the same logic used in:
  - edac_device_workq_setup()
  - edac_device_workq_function()

--
Regards, Eliav


> ---
>
> diff --git a/drivers/edac/edac_device.c b/drivers/edac/edac_device.c
> index 19522c568aa5..88942a6edc2c 100644
> --- a/drivers/edac/edac_device.c
> +++ b/drivers/edac/edac_device.c
> @@ -399,7 +399,7 @@ void edac_device_reset_delay_period(struct 
> edac_device_ctl_info *edac_dev,
>        unsigned long jiffs = msecs_to_jiffies(value);
>
>        if (value == 1000)
> -               jiffs = round_jiffies_relative(value);
> +               jiffs = round_jiffies_relative(jiffs);
>
>        edac_dev->poll_msec = value;
>        edac_dev->delay     = jiffs;
>
> -- 
> Regards/Gruss,
>    Boris.
>
> https://people.kernel.org/tglx/notes-about-netiquette

  reply	other threads:[~2022-12-29 20:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-20 12:44 [PATCH v2] edac: fix period calculation in edac_device_reset_delay_period() Eliav Farber
2022-12-29 15:23 ` Borislav Petkov
2022-12-29 20:17   ` Farber, Eliav [this message]
2022-12-30 14:48     ` Borislav Petkov

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=aebd2f07-674c-b848-69e7-5479d111bad1@amazon.com \
    --to=farbere@amazon.com \
    --cc=amitlavi@amazon.com \
    --cc=bp@alien8.de \
    --cc=dkl@amazon.com \
    --cc=hanochu@amazon.com \
    --cc=hhhawa@amazon.com \
    --cc=itamark@amazon.com \
    --cc=james.morse@arm.com \
    --cc=jonnyc@amazon.com \
    --cc=linux-edac@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=rric@kernel.org \
    --cc=shellykz@amazon.com \
    --cc=talel@amazon.com \
    --cc=tony.luck@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