[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b2489acc-d997-43e7-aeaf-c662b6fd3253@lunn.ch>
Date: Wed, 9 Oct 2024 14:23:12 +0200
From: Andrew Lunn <andrew@...n.ch>
To: Fedor Pchelkin <pchelkin@...ras.ru>
Cc: Stephen Boyd <sboyd@...nel.org>, lvc-project@...uxtesting.org,
Michael Turquette <mturquette@...libre.com>,
linux-kernel@...r.kernel.org, linux-clk@...r.kernel.org,
Gregory Clement <gregory.clement@...tlin.com>,
linux-arm-kernel@...ts.infradead.org,
Sebastian Hesselbarth <sebastian.hesselbarth@...il.com>
Subject: Re: [lvc-project] [PATCH v3] clk: mvebu: Prevent division by zero in
clk_double_div_recalc_rate()
> > I would say, let is divide by 0, so there is an obvious kernel stack
> > trace and hopefully a report of the issue. It can then be investigated
> > in a way we can then find out what the hardware actually is doing.
>
> Is it worth adding some kind of WARN assertions? Or actually just leave it
> for now as is?
What actually happens on a / 0 on ARM? I assume it triggers an
exception, which will give a stack trace? If so a WARN adds no value.
Andrew
Powered by blists - more mailing lists