Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S269484AbUJLGPa (ORCPT ); Tue, 12 Oct 2004 02:15:30 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S269477AbUJLGP3 (ORCPT ); Tue, 12 Oct 2004 02:15:29 -0400 Received: from rproxy.gmail.com ([64.233.170.195]:32013 "EHLO mproxy.gmail.com") by vger.kernel.org with ESMTP id S269473AbUJLGPQ (ORCPT ); Tue, 12 Oct 2004 02:15:16 -0400 Message-ID: <46561a79041011231549ea310a@mail.gmail.com> Date: Tue, 12 Oct 2004 11:45:16 +0530 From: suthambhara nagaraj Reply-To: suthambhara nagaraj To: main kernel Subject: kernel stack Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 667 Lines: 18 Hi all, I have not understood how the common kernel stack in the init_thread_union(2.6 ,init_task_union in case of 2.4) works for all the processes which run on the same processor. The scheduling is round robin and yet the things on the stack (saved during SAVE_ALL) have to be maintained after a switch without them getting erased. I am familiar with only the i386 arch implementation. Please help regards, Suthambhara - 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/