linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chen Gang <gang.chen.5i5j@gmail.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
	Guan Xuetao <gxt@mprc.pku.edu.cn>,
	len.brown@intel.com,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>
Subject: Re: [PATCH v2] kernel/power/hibernate.c: use 'u64' instead of 's64' to avoid warning
Date: Tue, 22 Apr 2014 15:56:55 +0800	[thread overview]
Message-ID: <535620C7.2080700@gmail.com> (raw)
In-Reply-To: <20140422072112.GB14108@amd.pavel.ucw.cz>

On 04/22/2014 03:21 PM, Pavel Machek wrote:
> On Tue 2014-04-22 09:29:20, Chen Gang wrote:
>> For do_div(), it need 'u64' type, which means the outside must be sure
>> of 'start' is not bigger than 'stop', or it will report warning.
>>
>> Even if 'start' was really bigger than 'stop', it would print incorrect
>> information, but for kernel, it still can continue, so use WARN_ON() is
>> enough.
>>
>> The related warning (with allmodconfig for unicore32):
>>
>>     CC      kernel/power/hibernate.o
>>   kernel/power/hibernate.c: In function ‘swsusp_show_speed’:
>>   kernel/power/hibernate.c:237: warning: comparison of distinct pointer types lacks a cast
>>
>>
> 
> Certainly better, but
> 
>> -	s64 elapsed_centisecs64;
>> +	u64 elapsed_centisecs64;
>>  	int centisecs;
>>  	int k;
>>  	int kps;
>>  
>>  	elapsed_centisecs64 = timeval_to_ns(stop) - timeval_to_ns(start);
>> +	WARN_ON((s64)elapsed_centisecs64 < 0);
>>  	do_div(elapsed_centisecs64, NSEC_PER_SEC / 100);
>>  	centisecs = elapsed_centisecs64;
> 
> ...do we need to do the WARN_ON()? Only result of underflow will be
> very long elapsed time reported... that does not sound too
> bad. ... and it will be quite obvious what went wrong.
> 									Pavel
> 

Hmm... that sounds reasonable to me.  If no any other reply within 2
days, I shall send patch v3 for it.

BTW: sorry, I guess I can not finish allmodconfig for unicore32 within
this month (2014-04-30) -- at present I only finish 40-50%, I
will/should try to finish it within next month.


Thanks.
-- 
Chen Gang

Open, share, and attitude like air, water, and life which God blessed

  reply	other threads:[~2014-04-22  7:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-22  1:29 [PATCH v2] kernel/power/hibernate.c: use 'u64' instead of 's64' to avoid warning Chen Gang
2014-04-22  7:21 ` Pavel Machek
2014-04-22  7:56   ` Chen Gang [this message]
2014-04-22  9:52     ` Chen Gang
2014-04-22 11:29       ` Rafael J. Wysocki
2014-04-22 12:10         ` Chen Gang

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=535620C7.2080700@gmail.com \
    --to=gang.chen.5i5j@gmail.com \
    --cc=gxt@mprc.pku.edu.cn \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --cc=rjw@rjwysocki.net \
    /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;
as well as URLs for NNTP newsgroup(s).