mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Srivatsa Vaddagiri <vatsa@in.ibm.com>
To: Thomas Schlichter <thomas.schlichter@web.de>
Cc: john stultz <johnstul@us.ibm.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] Updated dynamic tick patches - Fix lost tick
Date: Thu, 1 Sep 2005 17:03:30 +0530	[thread overview]
Message-ID: <20050901113330.GB11145@in.ibm.com> (raw)
In-Reply-To: <200509011305.24038.thomas.schlichter@web.de>

On Thu, Sep 01, 2005 at 01:05:23PM +0200, Thomas Schlichter wrote:
> Yes, the only real differences are the two points mentioned in my first 
> mail... I only wanted to help you fixing these.

Thanks for pointing them out. I have fixed it in the experimental version
that I have now.

> Well, that seems to be fine. If you want somebody to have a look over your 
> final patch, feel free to mail me...

sure!

> I should have defined PMTMR_TICKS_PER_JIFFY like you assigned 
> pm_ticks_per_jiffy (why did you use a static and constant variable and not a 
> macro?):

I actually started with using the calibrated value of PMTMR_TICKS_PER_JIFFY 
rather than compile time constant (as found in verify_pmtmr), but later dropped
the idea since I didnt get good results with it. After that didnt revert
back pm_ticks_per_jiffy to be a macro. But good point, will include
this in the next patch that I am trying out. Will post it if I happen
to have success :)



-- 


Thanks and Regards,
Srivatsa Vaddagiri,
Linux Technology Center,
IBM Software Labs,
Bangalore, INDIA - 560017

      reply	other threads:[~2005-09-01 11:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-01  6:29 Thomas Schlichter
2005-09-01  7:23 ` Srivatsa Vaddagiri
2005-09-01  7:42   ` Thomas Schlichter
2005-09-01 10:28     ` Srivatsa Vaddagiri
2005-09-01 11:05       ` Thomas Schlichter
2005-09-01 11:33         ` Srivatsa Vaddagiri [this message]

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=20050901113330.GB11145@in.ibm.com \
    --to=vatsa@in.ibm.com \
    --cc=johnstul@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=thomas.schlichter@web.de \
    /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

all inboxes | Powered by JetHome®