Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Mon, 16 Apr 2001 12:04:02 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Mon, 16 Apr 2001 12:03:52 -0400 Received: from nat-hdqt.valinux.com ([198.186.202.17]:18766 "EHLO macallan.engr.valinux.com") by vger.kernel.org with ESMTP id ; Mon, 16 Apr 2001 12:03:42 -0400 From: Walt Drummond MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15067.6084.459899.879345@macallan.engr.valinux.com> Date: Mon, 16 Apr 2001 09:03:16 -0700 To: george anzinger Cc: drummond@engr.valinux.com, Hubertus Franke , mingo@elte.hu, Linux Kernel List , lse-tech@lists.sourceforge.net Subject: Re: [Lse-tech] Bug in sys_sched_yield In-Reply-To: <3AD5E676.CF1C1684@mvista.com> In-Reply-To: <3AD5D311.5BFE39A6@mvista.com> <15061.56474.247739.99673@macallan.engr.valinux.com> <3AD5E676.CF1C1684@mvista.com> X-Mailer: VM 6.90 under Emacs 20.7.1 Reply-To: drummond@engr.valinux.com Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org george anzinger writes: > All that is cool. Still, most places we don't really address the > processor, so the logical cpu number is all we need. Places like > sched_yield, for example, should be using this, not the actual number, > which IMO should only be used when, for some reason, we NEED the hard > address of the cpu. I don't think this ever has to leak out to the > common kernel code, or am i missing something here. No your not, I was. I completely misinterpreted your question. Sorry about that. Hubertus and Kanoj have provided the answer I should have given. --Walt - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/