[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250707220529.19eb2a74@gandalf.local.home>
Date: Mon, 7 Jul 2025 22:05:29 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: "Li,Rongqing" <lirongqing@...du.com>
Cc: Oleg Nesterov <oleg@...hat.com>, Peter Zijlstra <peterz@...radead.org>,
David Laight <david.laight.linux@...il.com>, "linux-kernel@...r.kernel.org"
<linux-kernel@...r.kernel.org>, "vschneid@...hat.com"
<vschneid@...hat.com>, "mgorman@...e.de" <mgorman@...e.de>,
"bsegall@...gle.com" <bsegall@...gle.com>, "dietmar.eggemann@....com"
<dietmar.eggemann@....com>, "vincent.guittot@...aro.org"
<vincent.guittot@...aro.org>, "juri.lelli@...hat.com"
<juri.lelli@...hat.com>, "mingo@...hat.com" <mingo@...hat.com>
Subject: Re: [????] Re: [????] Re: divide error in x86 and cputime
On Tue, 8 Jul 2025 01:58:00 +0000
"Li,Rongqing" <lirongqing@...du.com> wrote:
> But mul_u64_u64_div_u64() for x86 should not trigger a division error panic, maybe should return a ULLONG_MAX on #DE (like non-x86 mul_u64_u64_div_u64(),)
Perhaps. But it is still producing garbage.
-- Steve
Powered by blists - more mailing lists