cpufreq Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>
To: Dave Jones <davej@redhat.com>
Cc: cpufreq@lists.linux.org.uk, Mike Galbraith <efault@gmx.de>
Subject: Re: p4_clockmod broken in 2.6.16-rc? kernels
Date: Tue, 14 Mar 2006 09:55:51 -0800	[thread overview]
Message-ID: <20060314095551.A4913@unix-os.sc.intel.com> (raw)
In-Reply-To: <20060310054723.GC5600@redhat.com>; from davej@redhat.com on Fri, Mar 10, 2006 at 12:47:23AM -0500

On Fri, Mar 10, 2006 at 12:47:23AM -0500, Dave Jones wrote:
> On Thu, Mar 09, 2006 at 08:07:44PM -0800, Pallipadi, Venkatesh wrote:
>  > 
>  > Great to hear that the patch helped. I had a typo in the patch header
>  > and attaching an updated patch. 
>  > 
>  > Dave: Please push this patch towards base. This was a bug in one of the
>  > recent changes in p4-clockmod.c
> 
> Applied, thanks.  I fixed this one up by hand, but next time can you
> inline the patch instead of attaching it ?

Sorry for all the hassle. I wanted to send that patch out quick, before 2.6.16. 
And hence ended up sending it as an attachment using the dump mail client.

> btw, should acpi-cpufreq/speedstep-ich also have those errata workarounds?

No. These two errats seem specific to clock modulation and not speedstep. So,
no changes required for speedstep.

Looking at the workarounds in p4-clockmod.c again...
Seems like some more work is needed on this. The current workaround doesn't 
seem to cover all the affected steppings and also it is using int [NR_CPUS] 
array to store a single bit (whether error is present or not). I will send a 
follow-on cleanup patch, which I think can wait until 2.6.16.

Thanks,
Venki
> 
> Thanks.
> 
> 		Dave
> 
> [1] Actually this was even longer. Due to me missing chopping a MIME
> mailheader, it still confused git-apply, and I scratched my head
> for some time until Linus clued me in.  MIME- just say no!
> 
> -- 
> http://www.codemonkey.org.uk

  reply	other threads:[~2006-03-14 17:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-10  4:07 p4_clockmod broken in 2.6.16-rc? kernels Pallipadi, Venkatesh
2006-03-10  5:47 ` Dave Jones
2006-03-14 17:55   ` Venkatesh Pallipadi [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-03-09 13:53 Pallipadi, Venkatesh
2006-03-10  3:25 ` Mike Galbraith
2006-03-09  6:11 Mike Galbraith

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=20060314095551.A4913@unix-os.sc.intel.com \
    --to=venkatesh.pallipadi@intel.com \
    --cc=cpufreq@lists.linux.org.uk \
    --cc=davej@redhat.com \
    --cc=efault@gmx.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