From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:46781) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QoEHe-0008GK-9J for qemu-devel@nongnu.org; Tue, 02 Aug 2011 08:41:19 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QoEHd-0001Pe-5z for qemu-devel@nongnu.org; Tue, 02 Aug 2011 08:41:18 -0400 Received: from mail-qw0-f45.google.com ([209.85.216.45]:65148) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QoEHc-0001PY-Vz for qemu-devel@nongnu.org; Tue, 02 Aug 2011 08:41:17 -0400 Received: by qwj8 with SMTP id 8so4316224qwj.4 for ; Tue, 02 Aug 2011 05:41:16 -0700 (PDT) Date: Tue, 2 Aug 2011 08:41:14 -0400 From: Kevin O'Connor Message-ID: <20110802124114.GA29924@morn.localdomain> References: <87ochmmhma.fsf@nemi.mork.no> <87sjqi9jsx.fsf@nemi.mork.no> <20110707235009.GB12991@morn.localdomain> <87fwmh9puv.fsf@nemi.mork.no> <20110710204100.GA25495@morn.localdomain> <0895461378D74EC49BD787BDBFF8C934@FSCPC> <8739hlb5t4.fsf@nemi.mork.no> <20110802003637.GA3046@morn.localdomain> <87y5zc9mzu.fsf@nemi.mork.no> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <87y5zc9mzu.fsf@nemi.mork.no> Subject: Re: [Qemu-devel] [SeaBIOS] SeaBIOS error with Juniper FreeBSD kernel List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: =?iso-8859-1?Q?Bj=F8rn?= Mork Cc: Brandon Bennett , seabios@seabios.org, qemu-devel@nongnu.org, Sebastian Herbszt On Tue, Aug 02, 2011 at 11:33:09AM +0200, Bjørn Mork wrote: > "Kevin O'Connor" writes: > > Also, it's possible the code could try to use the f-segment if there > > are less than say 16 cpus and use high memory when more cpus are > > present. > > How about a variant over the last suggestion: Don't actually care bout > the number of CPUs, but just fall back to malloc_high if malloc_fseg > fails? This could make testing painful - small changes in the code could cause a different table layout that is OS visible. I'd prefer a more strict cutoff. Though, I suppose the cutoff could be by the table size itself instead of by number of CPUs. -Kevin