From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from list by lists.gnu.org with archive (Exim 4.71) id 1efisH-00028T-Ds for mharc-grub-devel@gnu.org; Sun, 28 Jan 2018 04:03:41 -0500 Received: from eggs.gnu.org ([2001:4830:134:3::10]:46730) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1efisF-00028B-8h for grub-devel@gnu.org; Sun, 28 Jan 2018 04:03:40 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1efisC-0005Ja-5P for grub-devel@gnu.org; Sun, 28 Jan 2018 04:03:39 -0500 Received: from tomli.me ([2a00:1a28:1157:199::5a76]:46560) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1efisB-0005Ip-Ps for grub-devel@gnu.org; Sun, 28 Jan 2018 04:03:36 -0500 Received: from tomli.me (localhost [127.0.0.1]) by tomli.me (OpenSMTPD) with ESMTP id 952bf47a for ; Sun, 28 Jan 2018 09:03:28 +0000 (UTC) X-HELO: x220 Authentication-Results: tomli.me; auth=pass (login) smtp.auth=tomli; iprev=permerror; iprev=fail Received: from hostby.channelnet.ie (HELO x220) (5.188.86.30) by tomli.me (qpsmtpd/0.95) with ESMTPSA (DHE-RSA-CHACHA20-POLY1305 encrypted); Sun, 28 Jan 2018 09:03:28 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=tomli.me; h=date:from:to:subject:message-id:references:mime-version:content-type:in-reply-to; s=1490979754; bh=rRK2iTwZ+7QWOR43JWPrJwTzHNU0WsbNlJHKBhhCIEY=; b=0opfvlJg3QmZKxeUn0DkL/seQPvoxtMMyHLQJUAi9tG8pKrK4lTvjBKfXQdCCGOowagW0mYkIt5Qf6xFyD8i2qLmQ+z6wW524XAPxlSVnRU4XFbPP2CzwCw6+LzWwpP0e8U4DkrAs1yXcSwGWDKxzNLRYX0xioBQwtNE3iTPf1N2SiIkC5Rokl7zNbkFLhL853rNlUg/2sLJ7RHnwZ/lzi1MKJcH01vCywenPUowLDrl6o0ofDWNEO5VeU3coH0WG/UKZcyhdHmxK9NEDT1VjKQk55xTcab0OQdvnMef3YQHUXfeFoh6yrybzL2g7TLcEbx8Z1Mt+fw9kFmiwI4jBQ== Date: Sun, 28 Jan 2018 17:03:15 +0800 From: tomli@tomli.me To: The development of GNU GRUB Subject: Re: [HELP] cryptomount is slow, what is the proper way to [PATCH] libgcrypt-grub? Message-ID: <20180128090315.GA16153@x220> References: <20180125135655.GA45678@x220> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.1 (2017-09-22) X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 2a00:1a28:1157:199::5a76 X-BeenThere: grub-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: The development of GNU GRUB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Jan 2018 09:03:40 -0000 > In GRUB SSE registers are disabled. If you want to use SSE, you need to > make sure you enable them and that they are disabled again before kernel > handoff Thanks for the tip. >> I have no idea about how to integrate my changes. For example, how to link >> .c and .S assembly together in the same GRUB module by changing import_gcry.py? >> I can't understand. From some comments, modifications of libgcrypt itself >> is not >> allowed at all, and import_gcry.py should do all the additional fixups? > Yes, just put your version of libgcrypt there and rerun ./autogen.sh I've added a .S file for the additional assembly code to be link with sha512.c, but apparently import_gcry.py doesn't know how to preprocess this file: WARNING: unknown file sha512-sse2-x86.S gcry_sha512 I've read import_gcry.py but the preprocessing is pretty complicated. What is the correct way to make my assembly code be recognized and preprocessed as a grub module by the script? Cheers, Tom Li