From owner-freebsd-mips@FreeBSD.ORG Sun Jul 21 21:29:38 2013 Return-Path: Delivered-To: freebsd-mips@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 80725E5D for ; Sun, 21 Jul 2013 21:29:38 +0000 (UTC) (envelope-from juli@clockworksquid.com) Received: from mail-la0-f46.google.com (mail-la0-f46.google.com [209.85.215.46]) by mx1.freebsd.org (Postfix) with ESMTP id 0B0D0375 for ; Sun, 21 Jul 2013 21:29:37 +0000 (UTC) Received: by mail-la0-f46.google.com with SMTP id hi8so1964070lab.33 for ; Sun, 21 Jul 2013 14:29:31 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:x-gm-message-state; bh=2za8TwYHTDQUB7jtyfDgMeiVdUMoMH7/wXsYKuPDDaE=; b=cleKAagfqA5mmQxzWsgI3QHcDQ+Y74EwZCUp9gSbBOgQSfV/DQrj8y950VOdmwumOL MgA4Z+xtFc/dJIX3n3mqZsG1H2XPsdtynL+5BeYcnz3WHpRfKzV6EKeAcVqB41ltmXFF rty2AuVCRXXS4PltIxyZpkYmabGJS8z1KtQJMRh4LmzhC43pHrEdbEHP/klzJrRUe0hb rd0FDMzz6nlzMApqY6AkTgP2dF9KDwKfJ3b8rQDTU9YBRT1VG2jRZUwwYqHnb6Pghjpy BTYx+V/PTIcv8YA4S4RGOUk9H+gP3jQi8ZiAT8f/DYebPQsS2Q1wudnLcvTAe6L71o1O ovGA== X-Received: by 10.112.97.132 with SMTP id ea4mr10884212lbb.80.1374442170988; Sun, 21 Jul 2013 14:29:30 -0700 (PDT) MIME-Version: 1.0 Received: by 10.152.113.231 with HTTP; Sun, 21 Jul 2013 14:29:10 -0700 (PDT) In-Reply-To: References: <6401792509903023722@unknownmsgid> From: Juli Mallett Date: Sun, 21 Jul 2013 14:29:10 -0700 Message-ID: Subject: Re: Can we undo the octeon hack? To: Warner Losh Content-Type: text/plain; charset=UTF-8 X-Gm-Message-State: ALoCoQn5SnL9qcy/tv8Spdsl1354/tSKJdf85lefm+F/O94dNlBaE2fvgP4mk22hHHPsSggut0WH Cc: Warner Losh , "freebsd-mips@freebsd.org" X-BeenThere: freebsd-mips@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to MIPS List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Jul 2013 21:29:38 -0000 I would really like a std.pci or something, too, so we don't have to enumerate all the PCI devices in every config. On Sun, Jul 21, 2013 at 1:51 PM, Warner Losh wrote: > These should really be in the std.foo files for each specific subport. That way atheros could have one set, and octeon could have another. > > I do know that we don't do the std.foo thing for the atheros config files, but we really should start, and this would be a good place to start... > > Warner > > On Jul 21, 2013, at 12:54 PM, Juli Mallett wrote: > >> Making it possible to override each value would be ideal but >> cumbersome. If you want to do that, by all means do! >> >> Thanks, >> Juli. >> >> On 2013-07-21, at 11:44, Adrian Chadd wrote: >> >>> Hi Juli/Warner, >>> >>> Is it possible to undo this particular hack, and allow these values to >>> be overridden in the kernel config files? >>> >>> from kern.pre.mk >>> >>> CFLAGS= ${COPTFLAGS} ${C_DIALECT} ${DEBUG} ${CWARNFLAGS} >>> CFLAGS+= ${INCLUDES} -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include >>> opt_global.h >>> .if ${COMPILER_TYPE} != "clang" >>> CFLAGS+= -fno-common -finline-limit=${INLINE_LIMIT} >>> .if ${MACHINE_CPUARCH} != "mips" >>> CFLAGS+= --param inline-unit-growth=100 >>> CFLAGS+= --param large-function-growth=1000 >>> .else >>> # XXX Actually a gross hack just for Octeon because of the Simple Executive. >>> CFLAGS+= --param inline-unit-growth=10000 >>> CFLAGS+= --param large-function-growth=100000 >>> CFLAGS+= --param max-inline-insns-single=10000 >>> .endif >>> .endif >>> >>> I'd like to be able to experiment with different inline settings in >>> order to try and squeeze kernels down to be smaller. >>> >>> Thanks! >>> >>> >>> -adrian >