From mboxrd@z Thu Jan  1 00:00:00 1970
From: Andi Kleen <andi@firstfloor.org>
Subject: Re: loop in copy_user_generic_string
Date: Wed, 12 Mar 2008 15:40:05 +0100
Message-ID: <20080312144004.GD2522@one.firstfloor.org>
References: <c4e36d110803040802o54afe4eavc56b772d7d82173f@mail.gmail.com>
	<47CD73DF.6070502@qumranet.com> <p73lk4y5qpc.fsf@bingen.suse.de>
	<47CE42C1.5040701@qumranet.com>
	<c4e36d110803050052v145f5df9m773541a370b68555@mail.gmail.com>
	<c4e36d110803071132h7990e5ffrb086c59427043187@mail.gmail.com>
	<c4e36d110803091513x4634ee11u41201e7e03c28e34@mail.gmail.com>
	<c4e36d110803111519u3614a5dak574552e40b29c670@mail.gmail.com>
	<c4e36d110803120550j2238eff4i76c2c3f6c3559e2d@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Cc: kvm-devel@lists.sourceforge.net,
	Andi Kleen <andi@firstfloor.org>, Avi Kivity <avi@qumranet.com>
To: Zdenek Kabelac <zdenek.kabelac@gmail.com>
Return-path: <kvm-devel-bounces@lists.sourceforge.net>
Content-Disposition: inline
In-Reply-To: <c4e36d110803120550j2238eff4i76c2c3f6c3559e2d@mail.gmail.com>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/kvm-devel>,
	<mailto:kvm-devel-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=kvm-devel>
List-Post: <mailto:kvm-devel@lists.sourceforge.net>
List-Help: <mailto:kvm-devel-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/kvm-devel>,
	<mailto:kvm-devel-request@lists.sourceforge.net?subject=subscribe>
Sender: kvm-devel-bounces@lists.sourceforge.net
Errors-To: kvm-devel-bounces@lists.sourceforge.net
List-Id: kvm.vger.kernel.org

> Argh - being stupid here - it looks like these 'working' kernels were
> not SMP actually.
> As long as the SMP is used - I still get the busy loop :(
> Now being clueless....

Sorry don't have the cycles to look into your problem, but the 
standard procedure for hard problems that can be reproduced
is to git bisect them down to the change set that introduced the
problem originally and then complain to whoever authored that.

-Andi

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/