Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1161187AbXBILNy (ORCPT ); Fri, 9 Feb 2007 06:13:54 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1161168AbXBILNy (ORCPT ); Fri, 9 Feb 2007 06:13:54 -0500 Received: from smtp-outbound-1.vmware.com ([65.113.40.141]:37948 "EHLO smtp-outbound-1.vmware.com" rhost-flags-OK-FAIL-OK-FAIL) by vger.kernel.org with ESMTP id S1161187AbXBILNx (ORCPT ); Fri, 9 Feb 2007 06:13:53 -0500 Message-ID: <45CC5771.1070309@vmware.com> Date: Fri, 09 Feb 2007 03:13:53 -0800 From: Zachary Amsden User-Agent: Thunderbird 1.5.0.9 (X11/20061206) MIME-Version: 1.0 To: Rusty Russell CC: Andrew Morton , lkml - Kernel Mailing List , Andi Kleen , virtualization , Paul Mackerras , Stephen Rothwell Subject: Re: [PATCH 6/10] lguest code: the little linux hypervisor. References: <1171012296.2718.26.camel@localhost.localdomain> <1171012458.2718.30.camel@localhost.localdomain> <1171012693.2718.37.camel@localhost.localdomain> <1171012761.2718.40.camel@localhost.localdomain> <1171012827.2718.42.camel@localhost.localdomain> <20070209013518.e75d5036.akpm@linux-foundation.org> <1171018812.2718.66.camel@localhost.localdomain> In-Reply-To: <1171018812.2718.66.camel@localhost.localdomain> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1291 Lines: 39 Rusty Russell wrote: > On Fri, 2007-02-09 at 01:35 -0800, Andrew Morton wrote: > >> On Fri, 09 Feb 2007 20:20:27 +1100 Rusty Russell wrote: >> >> >>> +#define log(...) \ >>> + do { \ >>> + mm_segment_t oldfs = get_fs(); \ >>> + char buf[100]; \ >>> + sprintf(buf, "lguest:" __VA_ARGS__); \ >>> + set_fs(KERNEL_DS); \ >>> + sys_write(1, buf, strlen(buf)); \ >>> + set_fs(oldfs); \ >>> + } while(0) >>> >> Due to gcc shortcomings, each instance of this will chew an additional 100 >> bytes of stack. Unless they fixed it recently. Is a bit of a timebomb. I >> guess ksaprintf() could be used. >> >> It also looks a bit, umm, innovative. >> > > It's also unused 8) > > It's an extremely useful macro for doing grossly invasive logging of the > guest. I'll drop it if you prefer. > Yes, it is a bit, umm, innovative. If it is going to be kept, even if just for devel logging, you should disable interrupts around it. Changing segments is not a normal thing to do. Zach - 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/