From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261590AbULFSt1 (ORCPT ); Mon, 6 Dec 2004 13:49:27 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261611AbULFSt0 (ORCPT ); Mon, 6 Dec 2004 13:49:26 -0500 Received: from smtp.mailbox.co.uk ([195.82.125.32]:7644 "EHLO smtp.mailbox.co.uk") by vger.kernel.org with ESMTP id S261590AbULFStS (ORCPT ); Mon, 6 Dec 2004 13:49:18 -0500 Message-ID: <41B4A9A6.3050107@jonmasters.org> Date: Mon, 06 Dec 2004 18:49:10 +0000 From: Jon Masters Organization: World Organi[sz]ation Of Broken Dreams User-Agent: Mozilla Thunderbird 0.8 (Windows/20040913) X-Accept-Language: en-us, en MIME-Version: 1.0 To: krishna CC: Linux Kernel Subject: Re: How to understand flow of kernel code References: <41B46B18.5030707@globaledgesoft.com> In-Reply-To: <41B46B18.5030707@globaledgesoft.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-MailScanner: Found to be clean Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org krishna wrote: > Thank you. I am able to use UML. This needs to be advocated more profusely as a experimentation mechanism suitable for people just wanting to have an overview initially. Sure, it's not great for figuring out the lower level stuff, but it shines if you want to pick apart the overall VM or sched stuff. Cheers, Jon.