Received: by 2002:a05:6358:3188:b0:123:57c1:9b43 with SMTP id q8csp8371873rwd; Tue, 20 Jun 2023 14:19:06 -0700 (PDT) X-Google-Smtp-Source: ACHHUZ6l8O0hS+BgIuL+aGqQDZ4/vmnziL75azOC36uDgGviXYeBqLkweI4/N6yhB8YAlCw7mtJg X-Received: by 2002:a05:6a00:1805:b0:668:98a1:5e8d with SMTP id y5-20020a056a00180500b0066898a15e8dmr3569822pfa.16.1687295945924; Tue, 20 Jun 2023 14:19:05 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1687295945; cv=none; d=google.com; s=arc-20160816; b=t6AC971Fth9WwJgDQMNszBKKpdhhiGzWJZiN7bMi9E96XLzN5nfNRGpy5cMIGQ8uXR fxqQjzyHLty//czCFVZ/0qS8aB4ErsRSRk5yQlE2CqwUiKYS1JzEYwaUD734BkEz0ec1 yS2qZRPgcUo8j/M2klcAbWeOqqmJ40f+jlBcYbPV3Gc9zj9DpnJUjeGYRKf2r6MAKKW5 AOJkMkAoxh0m61GbrsXFFEcVKLodsd5B06L/By06Lbj52Yg665mgyKXU/kPAjQImElms VWkw1VROITeu72IDlFEaEV7V61XysTnWu7tDONjNIbwobBemQSwp66Eo1B5neQQR2jBD DCjQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:dkim-signature:date; bh=AknCkCooyVujKThdxC1FM7ZvENiuN9/CmEk5IHQ7iJc=; b=jQJvrTffRoGUEKS1P+QSjv06aOQczrRqhjEIh6AINjcXB74cz2n7XnPIGe7CpwJv+h tXBXWOOeWX5FPenqirKTqto8lz9Mo/KDQNBZVfOLeQ0kMmNP9U01nXOoUqYmFsBzrD3L C+cvLgj67fxcLfqHLgLj/ZMLqn8uIt5s5BfPcNUx+glM/7PFm5dpbRmBE0mHHLki2IFp iMx72yRQxeBfSqgnuX6jQGwqarS542kuiJhHGAa6fXVzGF5rz0bMy9De+CHMxqJ3jFfr OcfblUKkjzreWJWJf98CLdewE7T+nXI8xb8Afi7UnATOCWDIw2HLEo4ghFSt8r5+Q8+A ssSQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linux.dev header.s=key1 header.b=XuzztPfV; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linux.dev Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id d199-20020a621dd0000000b006650cdc0d48si2541902pfd.102.2023.06.20.14.18.52; Tue, 20 Jun 2023 14:19:05 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@linux.dev header.s=key1 header.b=XuzztPfV; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linux.dev Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229955AbjFTUTW (ORCPT + 99 others); Tue, 20 Jun 2023 16:19:22 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:56634 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230191AbjFTUTT (ORCPT ); Tue, 20 Jun 2023 16:19:19 -0400 Received: from out-26.mta0.migadu.com (out-26.mta0.migadu.com [91.218.175.26]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 6D2E519A4 for ; Tue, 20 Jun 2023 13:18:59 -0700 (PDT) Date: Tue, 20 Jun 2023 16:18:51 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux.dev; s=key1; t=1687292337; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=AknCkCooyVujKThdxC1FM7ZvENiuN9/CmEk5IHQ7iJc=; b=XuzztPfVVe+3n5nJEOjm27aqlllgXuZQ6rVKnaNP1qE0QAgMdGx6B41jDrtlCUaSZVvcwB aFXG7iOPoRS+k3iuIDq6aCVJVdfwEIwxm8O1jeyxNx8BlQuDXJKsTMlQrOrb4Uy0Osm8So ZIKImGyM50seypVLOxcay429rYAWiDE= X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. From: Kent Overstreet To: Dave Hansen Cc: Andy Lutomirski , Mark Rutland , Linux Kernel Mailing List , linux-fsdevel@vger.kernel.org, "linux-bcachefs@vger.kernel.org" , Kent Overstreet , Andrew Morton , Uladzislau Rezki , "hch@infradead.org" , linux-mm@kvack.org, Kees Cook , the arch/x86 maintainers Subject: Re: [PATCH 07/32] mm: Bring back vmalloc_exec Message-ID: <20230620201851.qrcabl327mrofygb@moria.home.lan> References: <20230509165657.1735798-1-kent.overstreet@linux.dev> <20230509165657.1735798-8-kent.overstreet@linux.dev> <20230619104717.3jvy77y3quou46u3@moria.home.lan> <20230619191740.2qmlza3inwycljih@moria.home.lan> <5ef2246b-9fe5-4206-acf0-0ce1f4469e6c@app.fastmail.com> <20230620180839.oodfav5cz234pph7@moria.home.lan> <37d2378e-72de-e474-5e25-656b691384ba@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <37d2378e-72de-e474-5e25-656b691384ba@intel.com> X-Migadu-Flow: FLOW_OUT X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,SPF_HELO_NONE,SPF_PASS, T_SCC_BODY_TEXT_LINE,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Jun 20, 2023 at 11:48:26AM -0700, Dave Hansen wrote: > >> No, I'm saying your concerns are baseless and too vague to > >> address. > > If you don't address them, the NAK will stand forever, or at least > > until a different group of people take over x86 maintainership. > > That's fine with me. > > I've got a specific concern: I don't see vmalloc_exec() used in this > series anywhere. I also don't see any of the actual assembly that's > being generated, or the glue code that's calling into the generated > assembly. > > I grepped around a bit in your git trees, but I also couldn't find it in > there. Any chance you could help a guy out and point us to some of the > specifics of this new, tiny JIT? vmalloc_exec() has already been dropped from the patchset - I'll switch to the new jit allocator when that's available and doing sub-page allocations. I can however point you at the code that generates the unpack functions: https://evilpiepirate.org/git/bcachefs.git/tree/fs/bcachefs/bkey.c#n727 > >> Andy, I replied explaining the difference between text_poke() and > >> text_poke_sync(). It's clear you have no idea what you're talking about, > >> so I'm not going to be wasting my time on further communications with > >> you. > > One more specific concern: This comment made me very uncomfortable and > it read to me very much like a personal attack, something which is > contrary to our code of conduct. It's not; I prefer to be direct than passive aggressive, and if I have to bow out of a discussion that isn't going anywhere I feel I owe an explanation of _why_. Too much conflict avoidance means things don't get resolved. And Andy and I are talking on IRC now, so things are proceeding in a better direction.