From owner-freebsd-arch@freebsd.org Thu Jul 12 19:38:44 2018 Return-Path: Delivered-To: freebsd-arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1DA5C103BD9F for ; Thu, 12 Jul 2018 19:38:44 +0000 (UTC) (envelope-from eric@vangyzen.net) Received: from smtp.vangyzen.net (hotblack.vangyzen.net [IPv6:2607:fc50:1000:7400:216:3eff:fe72:314f]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id BC1D57BE51; Thu, 12 Jul 2018 19:38:43 +0000 (UTC) (envelope-from eric@vangyzen.net) Received: from sweettea.beer.town (unknown [76.164.8.130]) by smtp.vangyzen.net (Postfix) with ESMTPSA id 4A9185646E; Thu, 12 Jul 2018 14:38:42 -0500 (CDT) Subject: Re: early x86 microcode loading To: John Baldwin , Mark Johnston , freebsd-arch@freebsd.org References: <20180712183116.GB15892@raichu> <6a83fad1-7616-eea5-d86b-83db693a9c73@FreeBSD.org> From: Eric van Gyzen Openpgp: preference=signencrypt Message-ID: Date: Thu, 12 Jul 2018 14:38:41 -0500 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: <6a83fad1-7616-eea5-d86b-83db693a9c73@FreeBSD.org> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Jul 2018 19:38:44 -0000 On 07/12/2018 14:24, John Baldwin wrote: > On 7/12/18 11:31 AM, Mark Johnston wrote: >> I'm interested in any feedback on the above, and especially any >> suggestions on how this feature should be integrated with the >> devcpu-data port. Thanks in advance. > > In general this sounds good to me. I'm not quite sure how to manage > setting the lines in loader.conf. Using 'service foo start/stop' > seems to be a bit of an abuse of what service is used for as opposed > to just including a standalone script in the devcpu-data port with a > suitable pkg-message. sysrc seems to be a closer analog than service > in theory, but shoehorning this into sysrc would seem to be quite > ugly and doesn't seem like a good idea to me either. I hesitate to suggest this, due to the necessary change in /two/ boot loaders, but... The foo.d approach is very convenient for packages. An activation script installed by the port/package could create a new /boot/loader.conf.d/devcpu-data file containing these lines. A pkg-message would instruct the user to run it. Eric