public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: linux-pm@lists.linux-foundation.org,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
	"Neil Brown" <neilb@suse.de>,
	"Matthew Garrett" <mjg59@srcf.ucam.org>,
	"mark gross" <640e9920@gmail.com>,
	"Arve Hjønnevåg" <arve@android.com>,
	"Dmitry Torokhov" <dmitry.torokhov@gmail.com>,
	"Florian Mickler" <florian@mickler.org>,
	linux-pci@vger.kernel.org,
	"Jesse Barnes" <jbarnes@virtuousgeek.org>
Subject: Re: [update] Re: [PATCH] PM: Make it possible to avoid wakeup events from being lost
Date: Thu, 1 Jul 2010 23:05:31 +0200	[thread overview]
Message-ID: <201007012305.31380.rjw@sisk.pl> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1007011627030.1303-100000@iolanthe.rowland.org>

On Thursday, July 01, 2010, Alan Stern wrote:
> On Thu, 1 Jul 2010, Rafael J. Wysocki wrote:
> 
> > > > +	if (msec) {
> > > > +		ktime_t kt;
> > > > +		struct timespec ts;
> > > > +		unsigned long expires;
> > > > +
> > > > +		kt = ktime_get();
> > > > +		kt = ktime_add_ns(kt, msec * NSEC_PER_MSEC);
> > > > +		ts = ktime_to_timespec(kt);
> > > > +		expires = timespec_to_jiffies(&ts);
> > > 
> > > Is this somehow better than jiffies + msecs_to_jiffies(msec)?
> > 
> > I'm not sure about overflows.  That said, the "+" version is used in many
> > places, so there's no problem I think.
> 
> Hmm.  NSEC_PER_MSEC must be one million, right?  So if msec referred to
> anything above 4 seconds (which seems unlikely but not impossible), the
> multiplication would overflow on a 32-bit machine.
> 
> Apart from that, the main difference between the two patches lies in
> when the events are counted, i.e., whether event_count gets incremented
> at the start or when the timer expires.  I can't see that it matters 
> much either way.

Well, your version doesn't require the additional static variable and
generally takes fewer lines of code. :-)

> > Index: linux-2.6/drivers/base/power/wakeup.c
> > ===================================================================
> > --- linux-2.6.orig/drivers/base/power/wakeup.c
> > +++ linux-2.6/drivers/base/power/wakeup.c
> > @@ -9,6 +9,7 @@
> >  #include <linux/device.h>
> >  #include <linux/slab.h>
> >  #include <linux/sched.h>
> > +#include <linux/ktime.h>
> 
> This isn't needed any more.

Right, I've dropped this line.

Rafael

  reply	other threads:[~2010-07-01 21:07 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-26 13:14 [PATCH] PM: Make it possible to avoid wakeup events from being lost Rafael J. Wysocki
2010-06-27 15:50 ` Alan Stern
2010-06-27 23:59   ` Rafael J. Wysocki
2010-06-28 14:16     ` Alan Stern
2010-06-28 19:01       ` [update] " Rafael J. Wysocki
2010-06-28 19:11         ` Jesse Barnes
2010-06-28 19:19         ` Alan Stern
2010-06-28 21:19           ` Rafael J. Wysocki
2010-06-28 20:38         ` Greg KH
2010-06-30  7:10         ` Florian Mickler
2010-06-30 13:47           ` mark gross
2010-06-30 18:00         ` Alan Stern
2010-06-30 19:27           ` Rafael J. Wysocki
2010-06-30 19:58             ` Alan Stern
2010-06-30 23:52               ` Rafael J. Wysocki
2010-07-01 13:58                 ` Alan Stern
2010-07-01 20:08                   ` Rafael J. Wysocki
2010-07-01 20:44                     ` Alan Stern
2010-07-01 21:05                       ` Rafael J. Wysocki [this message]
2010-06-28 23:28     ` [linux-pm] " David Brownell
2010-06-29 19:57       ` Alan Stern
2010-06-27 22:28 ` mark gross
2010-06-28 12:50   ` Rafael J. Wysocki
2010-06-29  4:43     ` mark gross
2010-07-01 13:32 ` Pavel Machek
2010-07-01 15:08   ` Florian Mickler
2010-07-01 19:02   ` Rafael J. Wysocki
2010-07-02 18:14     ` Pavel Machek
2010-07-02 19:21       ` 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=201007012305.31380.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=640e9920@gmail.com \
    --cc=arve@android.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=florian@mickler.org \
    --cc=jbarnes@virtuousgeek.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=mjg59@srcf.ucam.org \
    --cc=neilb@suse.de \
    --cc=stern@rowland.harvard.edu \
    /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