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 Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by smtp.lore.kernel.org (Postfix) with ESMTP id 538DAD75E30 for ; Fri, 22 Nov 2024 12:18:34 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id AB5DB6B00B8; Fri, 22 Nov 2024 07:18:33 -0500 (EST) Received: by kanga.kvack.org (Postfix, from userid 40) id A3D006B00B9; Fri, 22 Nov 2024 07:18:33 -0500 (EST) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 8B9186B00BA; Fri, 22 Nov 2024 07:18:33 -0500 (EST) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0014.hostedemail.com [216.40.44.14]) by kanga.kvack.org (Postfix) with ESMTP id 687EE6B00B8 for ; Fri, 22 Nov 2024 07:18:33 -0500 (EST) Received: from smtpin24.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay03.hostedemail.com (Postfix) with ESMTP id E5DA4A123A for ; Fri, 22 Nov 2024 12:18:32 +0000 (UTC) X-FDA: 82813632510.24.F640D75 Received: from verein.lst.de (verein.lst.de [213.95.11.211]) by imf17.hostedemail.com (Postfix) with ESMTP id B95834000A for ; Fri, 22 Nov 2024 12:17:49 +0000 (UTC) Authentication-Results: imf17.hostedemail.com; dkim=none; spf=pass (imf17.hostedemail.com: domain of hch@lst.de designates 213.95.11.211 as permitted sender) smtp.mailfrom=hch@lst.de; dmarc=none ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=hostedemail.com; s=arc-20220608; t=1732277848; h=from:from:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=tfIeBq+tuOflX4ksZA/x+0iCc/nSAYnurOOzuWjvZwM=; b=0cERQyWVaXzYzc2ZgYo8HlSS8hLFkNju0uzMySwyoEk/BwKvqPF66VqBrWUnufyO7sWJ/N RCspr5GRkpK1oAPRXJQhxBJ7mKVZIwhTbbLEkxDWezG3yrS1FEnyQ4mX+n02cP2nQOr9/l 5yYKlHTBNuiOf/qZvA1tZOxutMwrBzw= ARC-Seal: i=1; s=arc-20220608; d=hostedemail.com; t=1732277848; a=rsa-sha256; cv=none; b=Ry+4W7Kfs79gJp8s8D1JYUGxjmuSfvuEyZcgoKGpQ5pN3mnpeyPwhcOEYccfQNC8lOMCnW g8OhsNJwA9bSJ9pAWAwApWCteTpFsZ9zd6s6ZBYeS2BvyeBTa5LTGnCJLpxfxe1imQI1db nvLkg3X6c9dSh6vBQlHKjhrprTXrhRA= ARC-Authentication-Results: i=1; imf17.hostedemail.com; dkim=none; spf=pass (imf17.hostedemail.com: domain of hch@lst.de designates 213.95.11.211 as permitted sender) smtp.mailfrom=hch@lst.de; dmarc=none Received: by verein.lst.de (Postfix, from userid 2407) id 92EBF68D16; Fri, 22 Nov 2024 13:18:26 +0100 (CET) Date: Fri, 22 Nov 2024 13:18:26 +0100 From: Christoph Hellwig To: Johannes Berg Cc: Lorenzo Stoakes , Hajime Tazaki , linux-um@lists.infradead.org, ricarkol@google.com, Liam.Howlett@oracle.com, vbabka@suse.cz, linux-mm@kvack.org, Jann Horn , Christoph Hellwig , Damien Le Moal Subject: Re: [RFC PATCH v2 00/13] nommu UML Message-ID: <20241122121826.GA26024@lst.de> References: <77ab71c7-3608-4636-a618-3044c2316a92@lucifer.local> <0930a0fa8e28ecaf92727229e6633278399409e7.camel@sipsolutions.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <0930a0fa8e28ecaf92727229e6633278399409e7.camel@sipsolutions.net> User-Agent: Mutt/1.5.17 (2007-11-01) X-Stat-Signature: ap1nsj3aig9xfx3hmqfayftmjs8b91g1 X-Rspam-User: X-Rspamd-Queue-Id: B95834000A X-Rspamd-Server: rspam02 X-HE-Tag: 1732277869-122666 X-HE-Meta: U2FsdGVkX18oPwHEy7QRZTccX3rG6VS2btSru44skvS62fp9YMKOKb87QhVyMYQ4pLAYVkIlbjvRHpSYeJQKK/GsH8yHN6w8Ntl8XcE6D7EyqKE8ujmzhZLpAEog2t9dbW3Z0AG3fhM9+zPCyctcI5dcq8QYGYZJlfxYJPx78hqCWf1r7uZ3hQ9yOAndpjMG9F2G4BHFPm96QILenHEXSbB/hXMV0s7tUQqka8FVHbXYQXv3mpT+Ol91y2mdAaTyWUACq+Ph6qBdWLRQzI5pqFGk49Sf1GTVYCvMEITQ5tQ36pQzMH6opJiJ/F0y91KZDOHJRfEtABxIxF3qT+IJAYsz6o3D2jEwlOxZP7liRaBw16KCIgkbKEqu1j0m4T295HRqF3957V2g0gVjS3SEo8qkAvqDgatSuZwT0jxfTqzTiSOt4NqKCEdzl7e4/HTSF2HpUqwg+s3OEerqfIQMK8OdWHNPzd5u7Pnzr/kyUDPFuS+wYfKRKk1/veQDS8eHYF5SVK6BzDLmVPNEydMeyn+PIsTUttlWLMPrWrLqns5M5x3Iq710TlLJltvlSy3zcUV3Gncdn6tQH24jUfzidDwRxSG9OoAgwjixUMdhcLM1Z9eXD4n5hqG/tQA1DXcgISAP2v0sa7w3HThoPfzWcgoHDFR6dBrYK5oKrKka5MswSG7u2YvW7jkaTFqsK0Vjpi1CSCysCXe2g2QJVVqzPOH5X3oj3EJAmEJv91Zya+SagqAt9O489Q+rRIVji6cJf+p8eW9gBanddmE767dmlbG3o74JUd8jNyduMR4lueaR6KQTxUiUzDJvOGbxJGy9zNFp41qshHIX8HHHc9EEd5rKgKUuN7LNUwZFhflmLv2Tbph10uYphgOMJlLTyMS0UgtEnop/c+2Sgclw+aYFAtYyoKYzqmMFrAL9xaMZwd987W9hDOMWR0huUc6ZNXFSevYGYhYWfWwbYV768Qc lykj/Ysy xImH/eZ2fLwQxnfF30coI1uz3wpRyUEvFB7TzhgEPdNoYJdHcsGUHuOQiiVGizrQsNWcS6x6GrJxfdVJ+Ep6owiQHWftIvhQwQljG X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: List-Subscribe: List-Unsubscribe: Maybe I'm missing something, but where does this discussion about killing nommu even come from? Nommu is a long standing and reasonable well maintained part of the kernel, why would anyone want to kill it for no good reason? I know quite a lot of products shipping it. Btw, nommu UML certainly sounds interesting to me, at least indirectly. I have a project for next year or so for which the linux kernel library or something like it would be useful to run an in-kernel workload as a user space process if needed. nommu uml sounds like a really good base for that as there basically won't be any userspace that needs memory protection to start with.