From: Dominik Brodowski <linux@dominikbrodowski.de>
To: Dave Jones <davej@redhat.com>
Cc: cpufreq@www.linux.org.uk
Subject: Re: post-OLS pending cpufreq patches
Date: Mon, 2 Aug 2004 22:40:44 +0200 [thread overview]
Message-ID: <20040802204044.GA8795@dominikbrodowski.de> (raw)
In-Reply-To: <20040802193350.GA15740@redhat.com>
On Mon, Aug 02, 2004 at 08:33:50PM +0100, Dave Jones wrote:
> On Tue, Jul 27, 2004 at 10:51:26PM +0200, Dominik Brodowski wrote:
>
> > - [core] HT fix before CPU group support is merged
> > fixes bug #3012: blind de-referencing of CPUdata independent of
> > whether this CPU is actually registered with the CPUfreq core is
> > bad. The small fix proposed is really straightforward, the proper
> > solution will be to merge the cpufreq-SMT patchkit, but that's much
> > more invasive and not yet completely ready. A "must" for 2.6.8.
>
> couldnt find this in my inbox/cpufreq folder. can you bounce this please?
Done in separate mail.
> > - [speedstep-smi] get_frequencies SMM call causes failures
> > fixes bug reported by Pierre Maziere. Also really straightforward.
>
> ditto (unless this is the 0xffff patch I just merged ?)
No, it's this patch you merged:
http://linux-dj.bkbits.net:8080/cpufreq/gnupatch@410e9165OpfEFE684FCd4kzghQsn5g
> > - [pmac] scaling_availbale_frequencies, #define cleanup [John Clemens]
> > x [pmac] does it keep frequency across suspend? If not, remove "equal" check
> > in target and/or set_speed
> > Don't really know about pmac's side of things, just wanted to
> > mention it again.
>
> pmac bits I'd rather go via benh, as he has a far better handle
> on whats going on in that world, along with hardware with which
> to test these changes.
Agreed; as I said I don't know about pmac's side of things, just wanted to
keep benh awake :)
> > - [core] SMT patchkit
> > needs a bit of work, will re-submit for 2.6.9
>
> Hmm.
>
> Subject: Re: [PATCH 2.6.8-rc2] speedstep SMT support
> ...
> DB> Patch looks good, so: Dave, could you please merge it?
>
> Merged.
Acutally, I meant something else...
[RFC][PATCH] (1/4) cpufreq SMT awareness: keep affected_cpu_mask
[RFC][PATCH] (2/4) cpufreq SMT awareness: save CPU's sys_device
[RFC][PATCH] (3/4) cpufreq SMT awareness: only register SMT group once
[RFC][PATCH] (4/4) cpufreq SMT awareness: code reduction
... but they need some work. Will do that against cpufreq-bk in a few days.
> Thanks for the summary 8-)
You're welcome. Thanks for removing items from the summary by merging them :)
Dominik
next prev parent reply other threads:[~2004-08-02 20:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-27 20:51 post-OLS pending cpufreq patches Dominik Brodowski
2004-07-28 13:59 ` Dave Jones
2004-07-28 17:25 ` Dominik Brodowski
2004-08-02 19:33 ` Dave Jones
2004-08-02 20:40 ` Dominik Brodowski [this message]
2004-08-02 20:42 ` Dominik Brodowski
2004-08-02 20:52 ` Dave Jones
-- strict thread matches above, loose matches on Subject: below --
2004-08-02 22:45 Pallipadi, Venkatesh
2004-08-03 12:42 ` Dominik Brodowski
2004-08-03 13:17 ` Dave Jones
2004-08-03 13:30 ` Dominik Brodowski
2004-08-03 13:37 ` Dave Jones
2004-08-03 14:07 ` Dominik Brodowski
2004-08-03 14:19 ` Dave Jones
2004-08-03 15:06 Pallipadi, Venkatesh
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=20040802204044.GA8795@dominikbrodowski.de \
--to=linux@dominikbrodowski.de \
--cc=cpufreq@www.linux.org.uk \
--cc=davej@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox