cpufreq Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Hoelbling <christian.holbling@cern.ch>
To: Dominik Brodowski <linux@dominikbrodowski.de>
Cc: cpufreq@www.linux.org.uk
Subject: Re: [PATCH 2.6.8-rc2] speedstep SMT support
Date: Thu, 29 Jul 2004 12:19:00 +0000	[thread overview]
Message-ID: <4108EB34.9060505@cern.ch> (raw)
In-Reply-To: <20040728172028.GB8678@dominikbrodowski.de>

  hi and thanks alot for your comments!

Dominik Brodowski wrote:

>
>This I'd prefer not to be merged: 
>a) CONFIG_SMP doesn't mean cpu_sibling_map exist, e.g. on non-x86 architectures
>b) it "emulates" sibling-awareness, though the governors are not.
>  
>
 agree on both of these

>Instead, I'd prefer if we keep up with the "only-register-one-CPU" in the
>speedstep-ich case until a proper SMT patchkit is applied.
>
>However, for the other changes: could you consider my opinions, maybe update it
>and resend it, please? 
>
>  
>
  i will gladly do. however, i am a bit afraid of missing some patch - 
could you send me a diff of your source tree to a recent vanilla source 
so i know where to start from? or is there some repository somewhere 
that i don't know about where the cpufreq development sources are kept?

 thanks alot,

chris

  reply	other threads:[~2004-07-29 12:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-28 14:31 [PATCH 2.6.8-rc2] speedstep SMT support Christian Hoelbling
2004-07-28 17:20 ` Dominik Brodowski
2004-07-29 12:19   ` Christian Hoelbling [this message]
2004-07-29 16:34     ` Dominik Brodowski
2004-07-30 11:36       ` Christian Hoelbling
2004-07-30 15:46         ` Dominik Brodowski

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=4108EB34.9060505@cern.ch \
    --to=christian.holbling@cern.ch \
    --cc=cpufreq@www.linux.org.uk \
    --cc=holbling@cpt.univ-mrs.fr \
    --cc=linux@dominikbrodowski.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