<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Microsoft produces crap, AMD eats it</title>
	<atom:link href="http://handyfloss.net/2009.06/microsoft-produces-crap-amd-eats-it/feed/" rel="self" type="application/rss+xml" />
	<link>http://handyfloss.net/2009.06/microsoft-produces-crap-amd-eats-it/</link>
	<description>Because FLOSS is handy, isn&#039;t it?</description>
	<lastBuildDate>Mon, 21 May 2012 06:39:20 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: isilanes</title>
		<link>http://handyfloss.net/2009.06/microsoft-produces-crap-amd-eats-it/comment-page-1/#comment-39186</link>
		<dc:creator>isilanes</dc:creator>
		<pubDate>Mon, 24 Aug 2009 10:27:25 +0000</pubDate>
		<guid isPermaLink="false">http://handyfloss.net/?p=778#comment-39186</guid>
		<description>Mmm, thanks Marcos for clearing that up! I am still not convinced, though. If the problem is on AMD, then any other OS (Linux, MacOS) should suffer the same flaw. Do they? I don&#039;t have experience on the issue (never owned a Phenom).</description>
		<content:encoded><![CDATA[<p>Mmm, thanks Marcos for clearing that up! I am still not convinced, though. If the problem is on AMD, then any other OS (Linux, MacOS) should suffer the same flaw. Do they? I don&#8217;t have experience on the issue (never owned a Phenom).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marcos Sartori</title>
		<link>http://handyfloss.net/2009.06/microsoft-produces-crap-amd-eats-it/comment-page-1/#comment-38930</link>
		<dc:creator>Marcos Sartori</dc:creator>
		<pubDate>Thu, 13 Aug 2009 16:09:58 +0000</pubDate>
		<guid isPermaLink="false">http://handyfloss.net/?p=778#comment-38930</guid>
		<description>It is not Vista processor scheduler!

threads are placed on a queue, like in any other system, and they are run by the idle processor based on their state and prioraty.

If it actualy happens that the processor will trigs a fault (as you say, I have not read CnQ whitepapers) everytime it needs more power. That fault will be managed in a ring0 (kernel mode) trap handler. Which by nature will put the thread it was running back in the queue, like any other system supporting SMP with premptive scheduler. And if the other processor is idle, or running a thread with less prioraty, or even running something else, but for enough cycles that the system thinks it is better to switch to another task. It will take that paused task and run it.

It is not actually vistas fault. But AMD faults not considering how proc schedullers works. If they managed to make it and opt-in feature, that OSes will turn on if they manage processor prioraties based on their clocks or handle clock scalling in a better way (in a non interrup call, or with a low prioraty process on the second proc). it would be a welcomed feature for sure</description>
		<content:encoded><![CDATA[<p>It is not Vista processor scheduler!</p>
<p>threads are placed on a queue, like in any other system, and they are run by the idle processor based on their state and prioraty.</p>
<p>If it actualy happens that the processor will trigs a fault (as you say, I have not read CnQ whitepapers) everytime it needs more power. That fault will be managed in a ring0 (kernel mode) trap handler. Which by nature will put the thread it was running back in the queue, like any other system supporting SMP with premptive scheduler. And if the other processor is idle, or running a thread with less prioraty, or even running something else, but for enough cycles that the system thinks it is better to switch to another task. It will take that paused task and run it.</p>
<p>It is not actually vistas fault. But AMD faults not considering how proc schedullers works. If they managed to make it and opt-in feature, that OSes will turn on if they manage processor prioraties based on their clocks or handle clock scalling in a better way (in a non interrup call, or with a low prioraty process on the second proc). it would be a welcomed feature for sure</p>
]]></content:encoded>
	</item>
</channel>
</rss>

