From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:60239) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eRwgz-00053i-4x for guix-patches@gnu.org; Thu, 21 Dec 2017 03:59:06 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eRwgw-0001Gb-48 for guix-patches@gnu.org; Thu, 21 Dec 2017 03:59:05 -0500 Received: from debbugs.gnu.org ([208.118.235.43]:36487) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1eRwgv-0001GO-WB for guix-patches@gnu.org; Thu, 21 Dec 2017 03:59:02 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1eRwgv-0005CL-Ip for guix-patches@gnu.org; Thu, 21 Dec 2017 03:59:01 -0500 Subject: [bug#29409] Remove hugetlb control group on ARM32. Resent-Message-ID: Date: Thu, 21 Dec 2017 09:57:52 +0100 From: Danny Milosavljevic Message-ID: <20171221095752.1a018320@scratchpost.org> In-Reply-To: <87ind19pok.fsf@gmail.com> References: <877euhtjkj.fsf@gmail.com> <87ind19pok.fsf@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-patches-bounces+kyle=kyleam.com@gnu.org Sender: "Guix-patches" To: Mathieu Othacehe Cc: 29409@debbugs.gnu.org Hi Mathieu, On Wed, 20 Dec 2017 20:15:07 +0100 Mathieu Othacehe wrote: > I'm not sure what do about, a workaround could be the ugly hack > attached, WDYT ? I researched cgroups a bit and it seems that /sys/fs/cgroup/hugetlb is for configuration of hugetlb and that cgroups themselves don't require hugetlb - and neither does elogind. There could be any number of reasons hugetlb doesn't work (custom kernel config etc). We could use (file-exists? "/proc/sys/vm/nr_hugepages") in order to test for hugetlb support. The proc filesystem is already mounted at this point. Alternatively, it would be possible to use (needed-for-boot? #f) for the hugetlb cgroup file-system. In that case, maybe failure isn't so bad. I didn't test that, however. If we want to make this ARM-specific we can do that too, but I think it's more general than that.