public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel-+ZI9xUNit7I@public.gmane.org>
To: "Yu, Luming" <luming.yu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: Aaron Lehmann <aaronl-nCTQwlqzmeJBDgjK7y7TUQ@public.gmane.org>,
	ACPI mailing list
	<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>,
	kernel list
	<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: Tell user when ACPI is killing machine
Date: Tue, 9 Dec 2003 12:25:09 +0100	[thread overview]
Message-ID: <20031209112509.GF297@elf.ucw.cz> (raw)
In-Reply-To: <3ACA40606221794F80A5670F0AF15F8401720C05-SRlDPOYGfgogGBtAFL8yw7fspsVTdybXVpNB7YpNyf8@public.gmane.org>

Hi!

> >> >cpufreq is not connected to acpi thermal subsystem. Dominik has some
> >> >patches to change that, IIRC.
> >> Is it merged into ACPI ?
> 
> >Not yet, IIRC. It is pretty big patch.
> 
> Would you please point out where they are? --Luming

In http://sourceforge.net/mailarchive/message.php?msg_id=6219572,
Dominik wrote: [This is what I was talking about; oops, google groups
does not seem to index acpi-devel :-(].
								Pavel

From: Dominik Brodowski <linux-2f6i7I/xbB0@public.gmane.org>
[PATCHES 2.6] ACPI processor driver updates [idle,throttling,cpufreq,thermal]  
2003-10-06 13:00

 The following patches which
 - a) replace the broken ACPI CPUfreq driver with a better, flexible variant,
 - b) modularize the processor.c code: instead of one large file there are
      many small files.
 - c) improve passive cooling support
 - d) allow for easy adding of proper locking and ref-counting in processor.c
 have been re-diffed against linux-2.6.0-test6-bk-current and are available
 on my website. 
 Len, I'll send them to you in private e-mail for easier merging later.
 
 Please apply.
 
 	Dominik
 

http://www.brodo.de/patches/2003-10-06/acpi-2.6.0-test6-2-remove_previous_pstates_implementation
 	The previous arch/i386/kernel/cpu/cpufreq/acpi.c CPUfreq
 	driver was broken, of bad design, and needs to replaced 
 	by something better. But, as a first step, remove all 
 	parts related to P-States from ACPI code.
 
 http://www.brodo.de/patches/2003-10-06/acpi-2.6.0-test6-2-processor_submodules
 	Add a "submodule interface" to drivers/acpi/processor.c
 
 	It allows to create other "modules" which access the acpi_handle 
 	for the processor, and which get notified if the event value 
 	maches the value passed in acpi_processor_register_notify.
 
 http://www.brodo.de/patches/2003-10-06/acpi-2.6.0-test6-2-processor_perflib
 	This patch adds a new "P-States library" to drivers/acpi/
 
 	CPUfreq drivers can now easly access the contents of the 
 	_PCT and the _PSS. For example, the speedstep-centrino 
 	driver could be appended so that it passes the appropriate 
 	value to the P-States library which then evaluates _PDC, 
 	and then returns the updated _PCT and _PSS.
 
 	Also, the platform limit is now handled as a cpufreq notifier and
 	as a call to cpufreq_policy_update.
 
 http://www.brodo.de/patches/2003-10-06/acpi-2.6.0-test6-2-new_acpi_io_driver
 	This re-adds the acpi P-States I/O driver. It is much smaller,
 	leaner and cleaner.
 
 http://www.brodo.de/patches/2003-10-06/acpi-2.6.0-test6-2-idle_submodule
 	This moves the idle handler out of drivers/acpi/processor and into
 	an own module.
 
 	Even if only C1 is available, it is now used. If the user prefers the 
 	default pm_idle, he can unload processor_idle, and still have the other
 	functionality available.
 
 http://www.brodo.de/patches/2003-10-06/acpi-2.6.0-test6-2-thermal_submodule
 	This adds a new mechanism to manage passive cooling. Instead of
 	hardcoded -and partly wrong- access to CPUfreq and ACPI 
 	throttling-, add a generic mechanism which other modules can 
 	register with.
 
 http://www.brodo.de/patches/2003-10-06/acpi-2.6.0-test6-2-thermal_cpufreq
 	Use _any_ CPUfreq driver for passive cooling. Implemented by an
 	cpufreq policy notifier and cpufreq_update_policy.
  
 http://www.brodo.de/patches/2003-10-06/acpi-2.6.0-test6-2-thermal_throttling
 	Move throttling into its own submodule, and register it with the new
 	passive cooling module. Also, the now-useless "limit" interface is
 	removed.
 


 



-- 
When do you have a heart between your knees?
[Johanka's followup: and *two* hearts?]


-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?  SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/

  parent reply	other threads:[~2003-12-09 11:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-08  3:26 Tell user when ACPI is killing machine Yu, Luming
     [not found] ` <3ACA40606221794F80A5670F0AF15F8401720C05-SRlDPOYGfgogGBtAFL8yw7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2003-12-09 11:25   ` Pavel Machek [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-12-04  5:27 Yu, Luming
     [not found] ` <3ACA40606221794F80A5670F0AF15F8401720BFD-4yWAQGcml64gGBtAFL8yw7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2003-12-04  9:54   ` Pavel Machek
2003-12-04 10:01     ` Damien Sandras
2003-12-04 10:56       ` Pavel Machek
2003-12-04 11:24         ` Måns Rullgård
2003-11-28 14:55 Pavel Machek
     [not found] ` <20031128145558.GA576-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>
2003-11-28 16:52   ` Pavel Machek
2003-11-28 22:01 ` Aaron Lehmann
2003-11-28 23:43   ` Pavel Machek

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=20031209112509.GF297@elf.ucw.cz \
    --to=pavel-+zi9xunit7i@public.gmane.org \
    --cc=aaronl-nCTQwlqzmeJBDgjK7y7TUQ@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=luming.yu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    /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