From owner-freebsd-arch@FreeBSD.ORG Sun Oct 21 02:47:33 2012 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6422FE13 for ; Sun, 21 Oct 2012 02:47:33 +0000 (UTC) (envelope-from jmg@h2.funkthat.com) Received: from h2.funkthat.com (gate2.funkthat.com [208.87.223.18]) by mx1.freebsd.org (Postfix) with ESMTP id 142D28FC0C for ; Sun, 21 Oct 2012 02:47:32 +0000 (UTC) Received: from h2.funkthat.com (localhost [127.0.0.1]) by h2.funkthat.com (8.14.3/8.14.3) with ESMTP id q9L2lQZP005178 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 20 Oct 2012 19:47:26 -0700 (PDT) (envelope-from jmg@h2.funkthat.com) Received: (from jmg@localhost) by h2.funkthat.com (8.14.3/8.14.3/Submit) id q9L2lQrb005177; Sat, 20 Oct 2012 19:47:26 -0700 (PDT) (envelope-from jmg) Date: Sat, 20 Oct 2012 19:47:26 -0700 From: John-Mark Gurney To: Peter Wemm Subject: Re: using SSE2 in kernel C code (improving AES-NI module) Message-ID: <20121021024726.GA1563@funkthat.com> Mail-Followup-To: Peter Wemm , Konstantin Belousov , freebsd-arch@freebsd.org References: <20121019233833.GS1967@funkthat.com> <20121020054847.GB35915@deviant.kiev.zoral.com.ua> <20121020171124.GU1967@funkthat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i X-Operating-System: FreeBSD 7.2-RELEASE i386 X-PGP-Fingerprint: 54BA 873B 6515 3F10 9E88 9322 9CB1 8F74 6D3F A396 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html X-to-the-FBI-CIA-and-NSA: HI! HOW YA DOIN? can i haz chizburger? X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.2 (h2.funkthat.com [127.0.0.1]); Sat, 20 Oct 2012 19:47:26 -0700 (PDT) Cc: Konstantin Belousov , freebsd-arch@freebsd.org X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Oct 2012 02:47:33 -0000 Peter Wemm wrote this message on Sat, Oct 20, 2012 at 11:10 -0700: > Or, another option.. do something like genassym or the many other > kernel build tools. aicasm builds and runs a userland tool to > generate something to build into the kernel. With sufficient > cross-contamination safeguards I wonder if something similar might be > able to be done here. Well, looks like I may this working... Turns out I can't name the file .s otherwise config puts it in SFILES which causes all sorts of problems.. So, I went w/ .nos, does any one else have any suggestions? how does this look to people: aesni_wrap2.nos optional aesni \ dependency "$S/crypto/aesni/aesni_wrap2.c" \ compile-with "${CC} -O3 -fPIC -S -o aesni_wrap2.nos $S/crypto/aesni/aesni_wrap2.c" \ no-obj no-implicit-rule before-depend \ clean "aesni_wrap2.nos" aesni_wrap2.o optional aesni \ dependency "aesni_wrap2.nos" \ compile-with "${NORMAL_S} aesni_wrap2.nos" \ no-implicit-rule \ clean "aesni_wrap2.o" We'll have to do something similar in the module Makefile, but that is easier... Also, I thought we had a better way to note that some devices depend upon others than just throwing a depend error... If you include aesni w/o crypto, you get error about missing cryptodev_if.h... -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not."