From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 1A7ACC43613 for ; Mon, 24 Jun 2019 13:09:01 +0000 (UTC) Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id E36102133F for ; Mon, 24 Jun 2019 13:09:00 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=lists.infradead.org header.i=@lists.infradead.org header.b="GIUIzlsp" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org E36102133F Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=arm.com Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-riscv-bounces+infradead-linux-riscv=archiver.kernel.org@lists.infradead.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20170209; h=Sender: Content-Transfer-Encoding:Content-Type:Cc:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:Date: Message-ID:From:References:To:Subject:Reply-To:Content-ID:Content-Description :Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=9gocr6lgUUDenvrJZMc0aizkoy8m+/TA0kTGtI0QIlQ=; b=GIUIzlspDQ9AOM 5cDzJCd3B80dy9oswI5IntILOP/OJNPrK2+3546XhwEJTQ9cemv/tCrsj6S2MCGtoKhmODTphRqZP kntxawkSE0llp3DeLBjsF6FyEt0Hdko8DtnGGqGwfgxQsQDeA6Hu8LqFyEnTxGPUKYfHPRfzetE2q UtBnk/cKgC3KvLeI7cXrHbWElvMBuxSuW1wiFQr63hbRNfDOYpVevSvqtXeWkPaNyWY7qOLFGOtFb 6j9ktF8N0u1G2ztfmrMNzh6FjcrQiGrPEIsrQGGuUxnzf6A+oDRK6sKxQdBc11ACpucT+RItxtVia L84MTDsQ56ODq7HgGYNA==; Received: from localhost ([127.0.0.1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.92 #3 (Red Hat Linux)) id 1hfOiN-0006FK-Q2; Mon, 24 Jun 2019 13:08:55 +0000 Received: from foss.arm.com ([217.140.110.172]) by bombadil.infradead.org with esmtp (Exim 4.92 #3 (Red Hat Linux)) id 1hfOiL-0006Ez-Mt for linux-riscv@lists.infradead.org; Mon, 24 Jun 2019 13:08:54 +0000 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 4D4FD344; Mon, 24 Jun 2019 06:08:53 -0700 (PDT) Received: from [10.1.32.158] (unknown [10.1.32.158]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id BB6A33F71E; Mon, 24 Jun 2019 06:08:51 -0700 (PDT) Subject: Re: RISC-V nommu support v2 To: Christoph Hellwig References: <20190624054311.30256-1-hch@lst.de> <28e3d823-7b78-fa2b-5ca7-79f0c62f9ecb@arm.com> <20190624115428.GA9538@lst.de> From: Vladimir Murzin Message-ID: Date: Mon, 24 Jun 2019 14:08:50 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.7.0 MIME-Version: 1.0 In-Reply-To: <20190624115428.GA9538@lst.de> Content-Language: en-US X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20190624_060853_786671_DD7CBD96 X-CRM114-Status: GOOD ( 14.35 ) X-BeenThere: linux-riscv@lists.infradead.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Damien Le Moal , Palmer Dabbelt , linux-kernel@vger.kernel.org, linux-mm@kvack.org, Paul Walmsley , linux-riscv@lists.infradead.org Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-riscv" Errors-To: linux-riscv-bounces+infradead-linux-riscv=archiver.kernel.org@lists.infradead.org Archived-At: List-Archive: On 6/24/19 12:54 PM, Christoph Hellwig wrote: > On Mon, Jun 24, 2019 at 12:47:07PM +0100, Vladimir Murzin wrote: >> Since you are using binfmt_flat which is kind of 32-bit only I was expecting to see >> CONFIG_COMPAT (or something similar to that, like ILP32) enabled, yet I could not >> find it. > > There is no such thing in RISC-V. I don't know of any 64-bit RISC-V > cpu that can actually run 32-bit RISC-V code, although in theory that > is possible. There also is nothing like the x86 x32 or mips n32 mode > available either for now. > > But it turns out that with a few fixes to binfmt_flat it can run 64-bit > binaries just fine. I sent that series out a while ago, and IIRC you > actually commented on it. > True, yet my observation was that elf2flt utility assumes that address space cannot exceed 32-bit (for header and absolute relocations). So, from my limited point of view straightforward way to guarantee that would be to build incoming elf in 32-bit mode (it is why I mentioned COMPAT/ILP32). Also one of your patches expressed somewhat related idea "binfmt_flat isn't the right binary format for huge executables to start with" Since you said there is no support for compat/ilp32, probably I'm missing some toolchain magic? Cheers Vladimir _______________________________________________ linux-riscv mailing list linux-riscv@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-riscv