From: Pavel Machek <pavel@ucw.cz>
To: Len Brown <len.brown@intel.com>
Cc: Linus Torvalds <torvalds@osdl.org>,
Kernel Mailing List <linux-kernel@vger.kernel.org>,
ACPI Developers <acpi-devel@lists.sourceforge.net>
Subject: Re: [BKPATCH] ACPI for 2.6
Date: Fri, 12 Nov 2004 18:42:48 +0100 [thread overview]
Message-ID: <20041112174248.GA4267@openzaurus.ucw.cz> (raw)
In-Reply-To: <1099986428.6090.53.camel@d845pe>
Hi!
> <len.brown@intel.com> (04/11/05 1.1803.163.1)
> [ACPI] Allow limiting idle C-States.
>
> Useful to workaround C3 ipw2100 packet loss,
> reducing noise or boot issues on some models.
> http://bugme.osdl.org/show_bug.cgi?id=3549
>
> For static processor driver, boot cmdline:
> processor.acpi_cstate_limit=2
You certainly win "ugliest parameter of the month" contest :-).
What about processor.max_cstate= or something?
> <len.brown@intel.com> (04/10/18 1.1803.119.24)
> [ACPI] add module parameters: processor.c2=[0,1] processor.c3=[0,1]
> to disable/enable C2 or C3
> blacklist entries for R40e and Medion 41700
So we have two independend ways to disable C states?
Pavel
--
64 bytes from 195.113.31.123: icmp_seq=28 ttl=51 time=448769.1 ms
next prev parent reply other threads:[~2004-11-12 17:42 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-09 7:47 [BKPATCH] ACPI for 2.6 Len Brown
2004-11-12 17:42 ` Pavel Machek [this message]
2004-11-12 18:18 ` Hiroshi Itoh
[not found] ` <20041112174248.GA4267-u08AdweFZfgxtPtxi4kahqVXKuFTiq87@public.gmane.org>
2004-12-01 23:13 ` Len Brown
-- strict thread matches above, loose matches on Subject: below --
2004-10-09 5:54 Len Brown
2004-08-14 6:55 Len Brown
2004-08-14 20:56 ` Jesse Barnes
2004-06-21 19:41 Len Brown
[not found] <E1BbPIM-00044a-0A@sc8-sf-list2.sourceforge.net>
[not found] ` <E1BbPIM-00044a-0A-ek0oC1U1TqqnvZpeIfgr/KQD96bmaF075NbjCUgZEJk@public.gmane.org>
2004-06-19 21:22 ` Carsten Rietzschel
2004-06-18 6:42 Len Brown
[not found] ` <1087540933.4487.212.camel-D2Zvc0uNKG8@public.gmane.org>
2004-06-23 13:47 ` Stefan Seyfried
2004-05-20 19:12 Len Brown
2004-05-11 16:48 Len Brown
2004-05-03 16:52 Len Brown
2004-04-01 10:40 Len Brown
2004-03-30 1:26 Manpreet Singh
2004-03-30 0:28 Manpreet Singh
2004-03-29 17:32 Moore, Robert
2004-03-27 9:18 Manpreet Singh
2004-03-27 0:59 Len Brown
[not found] ` <1080349151.16211.33.camel-D2Zvc0uNKG8@public.gmane.org>
2004-03-27 11:11 ` Marcel Holtmann
2004-03-23 10:02 Len Brown
2004-03-14 6:08 Len Brown
2004-03-06 6:37 Len Brown
2004-02-25 9:18 Len Brown
2004-02-14 4:46 Len Brown
2004-02-07 9:10 Len Brown
[not found] ` <1076145027.8682.34.camel-D2Zvc0uNKG8@public.gmane.org>
2004-02-09 9:09 ` Olaf Hering
2004-02-09 9:11 ` Olaf Hering
2004-01-27 6:03 Len Brown
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=20041112174248.GA4267@openzaurus.ucw.cz \
--to=pavel@ucw.cz \
--cc=acpi-devel@lists.sourceforge.net \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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