All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Dave Jones <davej@redhat.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Venki Pallipadi <venkatesh.pallipadi@intel.com>,
	Len Brown <len.brown@intel.com>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Display Intel Dynamic Acceleration feature in /proc/cpuinfo
Date: Thu, 24 May 2007 23:08:38 +0200	[thread overview]
Message-ID: <200705242308.38360.ak@suse.de> (raw)
In-Reply-To: <20070524210103.GA5380@redhat.com>

On Thursday 24 May 2007 23:01:04 Dave Jones wrote:
> On Thu, May 24, 2007 at 01:55:13PM -0700, Andrew Morton wrote:
>  > On Wed, 23 May 2007 15:46:37 -0700
>  > Venki Pallipadi <venkatesh.pallipadi@intel.com> wrote:
>  > 
>  > > Display Intel Dynamic Acceleration feature in /proc/cpuinfo. This feature
>  > > will be enabled automatically by current acpi-cpufreq driver and cpufreq.
>  > 
>  > So you're saying that the cpufreq code in Linus's tree aleady supports IDA?
>  > If so, this is a 2.6.22 patch, isn't it?
> 
> From my limited understanding[*], ida is the "We're single threaded,
> disable the 2nd core, and clock the first core faster" magic.
> It doesn't need code-changes, as its all done in hardware afaik.

P0 is somewhat visible to software, but it should be pretty transparent

> 
> identifying & exporting the flags on earlier kernels should be harmless,
> but not really 'mustfix'.

I think it's generally a good idea to push cpuinfo flags in earliest
as possible; just make sure we actually use the final name (so that we don't get
into a pni->sse3 mess again) 
 
-Andi

  reply	other threads:[~2007-05-24 21:08 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-23 22:46 [PATCH] Display Intel Dynamic Acceleration feature in /proc/cpuinfo Venki Pallipadi
2007-05-24 20:55 ` Andrew Morton
2007-05-24 21:01   ` Dave Jones
2007-05-24 21:08     ` Andi Kleen [this message]
2007-05-24 21:13       ` Venki Pallipadi
2007-05-24 21:25         ` Andi Kleen
2007-05-24 21:28           ` Venki Pallipadi
2007-05-24 21:37             ` Dave Jones
2007-05-24 21:56             ` Andi Kleen
2007-05-24 23:03             ` H. Peter Anvin
2007-05-24 23:13               ` Pallipadi, Venkatesh
2007-05-24 23:23                 ` H. Peter Anvin
2007-05-25  0:00                   ` Pallipadi, Venkatesh
2007-05-25  0:04                     ` H. Peter Anvin
2007-05-30  0:52                       ` Venki Pallipadi
2007-05-24 21:10     ` Venki Pallipadi
2007-05-24 22:02 ` Andrew Morton
2007-05-24 22:08   ` Venki Pallipadi
2007-05-24 22:16     ` H. Peter Anvin
2007-05-24 22:14   ` H. Peter Anvin
2007-05-24 22:41     ` Dave Jones
2007-05-24 22:51       ` H. Peter Anvin
2007-05-24 23:06         ` Dave Jones
2007-05-24 23:11           ` H. Peter Anvin
2007-05-24 23:50       ` Alan Cox
2007-05-24 23:53         ` H. Peter Anvin
2007-05-24 22:27   ` H. Peter Anvin

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=200705242308.38360.ak@suse.de \
    --to=ak@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=davej@redhat.com \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=venkatesh.pallipadi@intel.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.