<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/drivers/acpi, branch mybooklive</title>
<subtitle>Linux kernel source tree</subtitle>
<id>https://git.amat.us/linux/atom/drivers/acpi?h=mybooklive</id>
<link rel='self' href='https://git.amat.us/linux/atom/drivers/acpi?h=mybooklive'/>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/'/>
<updated>2010-03-15T15:49:36Z</updated>
<entry>
<title>ACPI: Be in TS_POLLING state during mwait based C-state entry</title>
<updated>2010-03-15T15:49:36Z</updated>
<author>
<name>Pallipadi, Venkatesh</name>
<email>venkatesh.pallipadi@intel.com</email>
</author>
<published>2010-02-10T18:35:31Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=cc03dfc07cc4acf73b721ca9a57c6d4d2101ae49'/>
<id>urn:sha1:cc03dfc07cc4acf73b721ca9a57c6d4d2101ae49</id>
<content type='text'>
commit d306ebc28649b89877a22158fe0076f06cc46f60 upstream.

ACPI deep C-state entry had a long standing bug/missing feature, wherein we were sending
resched IPIs when an idle CPU is in mwait based deep C-state. Only mwait based C1 was using
the write to the monitored address to wake up mwait'ing CPU.

This patch changes the code to retain TS_POLLING bit if we are entering an mwait based
deep C-state.

The patch has been verified to reduce the number of resched IPIs in general and also
improves the performance/power on workloads with low system utilization (i.e., when mwait based
deep C-states are being used).

Fixes "netperf ~50% regression with 2.6.33-rc1, bisect to 1b9508f"
http://marc.info/?l=linux-kernel&amp;m=126441481427331&amp;w=4

Reported-by: Lin Ming &lt;ming.m.lin@intel.com&gt;
Tested-by: Alex Shi &lt;alex.shi@intel.com&gt;
Signed-off-by: Venkatesh Pallipadi &lt;venkatesh.pallipadi@intel.com&gt;
Signed-off-by: Len Brown &lt;len.brown@intel.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>ACPI: fix "acpi=ht" boot option</title>
<updated>2010-03-15T15:49:36Z</updated>
<author>
<name>Len Brown</name>
<email>len.brown@intel.com</email>
</author>
<published>2010-02-16T08:45:45Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=b8f3bf57d555898a0c4710d72f1426b8e60db1ae'/>
<id>urn:sha1:b8f3bf57d555898a0c4710d72f1426b8e60db1ae</id>
<content type='text'>
commit 49bf83a45fc677db1ed44d0e072e6aaeabe4e124 upstream.

We broke "acpi=ht" in 2.6.32 by disabling MADT parsing
for acpi=disabled.  e5b8fc6ac158f65598f58dba2c0d52ba3b412f52
This also broke systems which invoked acpi=ht via DMI blacklist.

acpi=ht is a really ugly hack,
but restore it for those that still use it.

http://bugzilla.kernel.org/show_bug.cgi?id=14886

Signed-off-by: Len Brown &lt;len.brown@intel.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>ACPI: fix High cpu temperature with 2.6.32</title>
<updated>2010-02-23T15:37:57Z</updated>
<author>
<name>Arjan van de Ven</name>
<email>arjan@linux.intel.com</email>
</author>
<published>2010-01-27T23:25:39Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=498a84db834a62eef2e5cb2fb85d051c39f89fff'/>
<id>urn:sha1:498a84db834a62eef2e5cb2fb85d051c39f89fff</id>
<content type='text'>
commit 370d5cd88509b93b76eb2f5f97efbd71c25061cb upstream.

Since the rewrite of the CPU idle governor in 2.6.32, two laptops have
surfaced where the BIOS advertises a C2 power state, but for some reason
this state is not functioning (as verified in both cases by powertop
before the patch in .32).

The old governor had the accidental behavior that if a non-working state
was chosen too many times, it would end up falling back to C1.  The new
governor works differently and this accidental behavior is no longer
there; the result is a high temperature on these two machines.

This patch adds these 2 machines to the DMI table for C state anomalies;
by just not using C2 both these machines are better off (the TSC can be
used instead of the pm timer, giving a performance boost for example).

Addresses http://bugzilla.kernel.org/show_bug.cgi?id=14742

Signed-off-by: Arjan van de Ven &lt;arjan@linux.intel.com&gt;
Reported-by: &lt;akwatts@ymail.com&gt;
Signed-off-by: Andrew Morton &lt;akpm@linux-foundation.org&gt;
Signed-off-by: Len Brown &lt;len.brown@intel.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>ACPI: Add NULL pointer check in acpi_bus_start</title>
<updated>2010-02-23T15:37:57Z</updated>
<author>
<name>Thomas Renninger</name>
<email>trenn@suse.de</email>
</author>
<published>2010-01-29T16:48:51Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=c51bfb22f31d384833e82a66872cccbab7c593df'/>
<id>urn:sha1:c51bfb22f31d384833e82a66872cccbab7c593df</id>
<content type='text'>
commit d2f6650a950dadd20667a04a9dc785f240d43695 upstream.

If acpi_bus_add does not return a device and it's passed
to acpi_bus_start, bad things will happen:

BUG: unable to handle kernel NULL pointer dereference at 0000000000000008
IP: [&lt;ffffffff8128402d&gt;] acpi_bus_start+0x14/0x24
...
[&lt;ffffffffa008977a&gt;] acpiphp_bus_add+0xba/0x130 [acpiphp]
[&lt;ffffffffa008aa72&gt;] enable_device+0x132/0x2ff [acpiphp]
[&lt;ffffffffa0089b68&gt;] acpiphp_enable_slot+0xb8/0x130 [acpiphp]
[&lt;ffffffffa0089df7&gt;] handle_hotplug_event_func+0x87/0x190 [acpiphp]

Next patch would make this NULL pointer check obsolete, but
better having one more than one missing...

Signed-off-by: Thomas Renninger &lt;trenn@suse.de&gt;
Acked-by: Bjorn Helgaas &lt;bjorn.helgaas@hp.com&gt;
Signed-off-by: Len Brown &lt;len.brown@intel.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>ACPI: Advertise to BIOS in _OSC: _OST on _PPC changes</title>
<updated>2010-02-09T12:50:44Z</updated>
<author>
<name>Zhao Yakui</name>
<email>yakui.zhao@intel.com</email>
</author>
<published>2010-01-08T13:29:58Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=3b4f785d6fd9df90b783e9a6ce9414884877593e'/>
<id>urn:sha1:3b4f785d6fd9df90b783e9a6ce9414884877593e</id>
<content type='text'>
commit 6a4e2b7503d1f630bface040cf0f5a7aac1fabdb upstream.

If the BIOS pokes the system-wide OSC bits to see if Linux
supports evaluating _OST after a _PPC change notification,
answer yes.

Also, fix an oversight where we neglected to set the OSC
bit advertising processor aggregator device support
when acpi-pad is compiled as a module.

Signed-off-by: Zhao Yakui &lt;yakui.zhao@intel.com&gt;
Signed-off-by: Len Brown &lt;len.brown@intel.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>ACPI: fix OSC regression that caused aer and pciehp not to load</title>
<updated>2010-02-09T12:50:44Z</updated>
<author>
<name>Shaohua Li</name>
<email>shaohua.li@intel.com</email>
</author>
<published>2009-12-23T09:04:11Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=0d48a1a716844bc72f0e105418261024c75ce494'/>
<id>urn:sha1:0d48a1a716844bc72f0e105418261024c75ce494</id>
<content type='text'>
commit 9dc130fccb874f2959ef313d7922d306dc6d4f75 upstream.

Executing _OSC returns a buffer, which has an acpi object in it.
Don't directly returns the buffer, instead, we return the acpi object's
buffer. This fixes a regression since caller of acpi_run_osc expects
an acpi object's buffer returned.

Tested-by: Yinghai Lu &lt;yinghai@kernel.org&gt;
Signed-off-by: Shaohua Li &lt;shaohua.li@intel.com&gt;
Signed-off-by: Len Brown &lt;len.brown@intel.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>ACPI: Add platform-wide _OSC support.</title>
<updated>2010-02-09T12:50:44Z</updated>
<author>
<name>Shaohua Li</name>
<email>shaohua.li@intel.com</email>
</author>
<published>2009-10-29T03:05:05Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=1a52addab3426e94879ce3638cb9daf9058d48fd'/>
<id>urn:sha1:1a52addab3426e94879ce3638cb9daf9058d48fd</id>
<content type='text'>
commit 3563ff964fdc36358cef0330936fdac28e65142a upstream.

Signed-off-by: Shaohua Li &lt;shaohua.li@intel.com&gt;
Signed-off-by: Len Brown &lt;len.brown@intel.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>ACPI: Add a generic API for _OSC -v2</title>
<updated>2010-02-09T12:50:44Z</updated>
<author>
<name>Shaohua Li</name>
<email>shaohua.li@intel.com</email>
</author>
<published>2009-10-29T03:04:28Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=e62a96c8317c306d81ba5c690bf8f1be10e6cad9'/>
<id>urn:sha1:e62a96c8317c306d81ba5c690bf8f1be10e6cad9</id>
<content type='text'>
commit 70023de88c58a81a730ab4d13c51a30e537ec76e upstream.

v2-&gt;v1:
.improve debug info as suggedted by Bjorn,Kenji
.API is using uuid string as suggested by Alexey

Add an API to execute _OSC. A lot of devices can have this method, so add a
generic API.

Signed-off-by: Shaohua Li &lt;shaohua.li@intel.com&gt;
Signed-off-by: Len Brown &lt;len.brown@intel.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>ACPI: enable C2 and Turbo-mode on Nehalem notebooks on A/C</title>
<updated>2010-01-28T23:02:54Z</updated>
<author>
<name>Len Brown</name>
<email>len.brown@intel.com</email>
</author>
<published>2010-01-26T21:15:28Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=d274df694b319a87405e35553bd2c45ab75f4554'/>
<id>urn:sha1:d274df694b319a87405e35553bd2c45ab75f4554</id>
<content type='text'>
upstream in 2.6.33-rc:  5d76b6f6c17572e662f5c99c2023adae92100855

Refreshed here for 2.6.32.y, applies w/ offset back to 2.6.29.y.

Linux has always ignored ACPI BIOS C2 with exit latency &gt; 100 usec,
and the ACPI spec is clear that is correct FADT-supplied C2.

However, the ACPI spec explicitly states that _CST-supplied C-states
have no latency limits.

So move the 100usec C2 test out of the code shared
by FADT and _CST code-paths, and into the FADT-specific path.

This bug has not been visible until Nehalem, which advertises
a CPU-C2 worst case exit latency on servers of 205usec.
That (incorrect) figure is being used by BIOS writers
on mobile Nehalem systems for the AC configuration.
Thus, Linux ignores C2 leaving just C1, which is
saves less power, and also impacts performance
by preventing the use of turbo mode.

http://bugzilla.kernel.org/show_bug.cgi?id=15064

Tested-by: Alex Chiang &lt;achiang@hp.com&gt;
Signed-off-by: Len Brown &lt;len.brown@intel.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>ACPI: EC: Add wait for irq storm</title>
<updated>2010-01-25T18:49:36Z</updated>
<author>
<name>Alexey Starikovskiy</name>
<email>astarikovskiy@suse.de</email>
</author>
<published>2009-12-30T12:53:10Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=5f0ab2dfbf84454894568377e4dd6578ef3938f3'/>
<id>urn:sha1:5f0ab2dfbf84454894568377e4dd6578ef3938f3</id>
<content type='text'>
commit 54070101f86ca9a6e9ba243c999d144721ec3db7 upstream.

Merge of poll and irq modes accelerated EC transaction, so
that keyboard starts to suffer again. Add msleep(1) into
transaction path for the storm to allow keyboard controller
to do its job.

Reference: http://bugzilla.kernel.org/show_bug.cgi?id=14747

Signed-off-by: Alexey Starikovskiy &lt;astarikovskiy@suse.de&gt;
Signed-off-by: Len Brown &lt;len.brown@intel.com&gt;
Cc: François Valenduc &lt;francois.valenduc@tvcablenet.be&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
</feed>
