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 mm01.cs.columbia.edu (mm01.cs.columbia.edu [128.59.11.253]) by smtp.lore.kernel.org (Postfix) with ESMTP id 94C1DC6FA8B for ; Wed, 21 Sep 2022 03:53:32 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by mm01.cs.columbia.edu (Postfix) with ESMTP id 4F0064B79B; Tue, 20 Sep 2022 23:53:32 -0400 (EDT) X-Virus-Scanned: at lists.cs.columbia.edu Authentication-Results: mm01.cs.columbia.edu (amavisd-new); dkim=softfail (fail, message has been altered) header.i=@google.com Received: from mm01.cs.columbia.edu ([127.0.0.1]) by localhost (mm01.cs.columbia.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Z61bVWPZQvEC; Tue, 20 Sep 2022 23:53:31 -0400 (EDT) Received: from mm01.cs.columbia.edu (localhost [127.0.0.1]) by mm01.cs.columbia.edu (Postfix) with ESMTP id 2F82A40FAA; Tue, 20 Sep 2022 23:53:31 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by mm01.cs.columbia.edu (Postfix) with ESMTP id 1E0004B269 for ; Tue, 20 Sep 2022 23:53:29 -0400 (EDT) X-Virus-Scanned: at lists.cs.columbia.edu Received: from mm01.cs.columbia.edu ([127.0.0.1]) by localhost (mm01.cs.columbia.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JfE6VRnDZQb2 for ; Tue, 20 Sep 2022 23:53:28 -0400 (EDT) Received: from mail-wm1-f45.google.com (mail-wm1-f45.google.com [209.85.128.45]) by mm01.cs.columbia.edu (Postfix) with ESMTPS id E90894B630 for ; Tue, 20 Sep 2022 23:53:27 -0400 (EDT) Received: by mail-wm1-f45.google.com with SMTP id n35-20020a05600c502300b003b4924c6868so1677267wmr.1 for ; Tue, 20 Sep 2022 20:53:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date; bh=YjNJwrSGGsmqwkos7/v8yu+we95EXK5+N0CYYMWfM9Q=; b=VN/89PxJc45yG4lc8yqdX46Pa4D79Mh+lXq0MdwtCoqk6H+vPb0LYEGHxXxS0OAM1+ 7RmnF/LUaYOBG1W3DFvw8Lkn5MpRYPZwJLvhEs7ruA2GSOv3b2YvH7hUZOHrdR2zbEiA yTfU1+O3beASWzV4c0GeNLj05YiKbgIKYNkV+PJcuPE4wxVo2TXv9YZLiaatDHLgtpmQ GON/Vu3+5/D77WWTrzPWPFcpgy4Ornyxr7/HX/qmrufG41d4inNUeDdtVhrlLoQr110w hcvpstlAuApR4OeGLmxuVIaGhkDR6bTDnFFtUPIHaLmqLZtxkutVbKpmn2u0NjMB7wPB vOug== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date; bh=YjNJwrSGGsmqwkos7/v8yu+we95EXK5+N0CYYMWfM9Q=; b=UyaPVn06G3/DAssFqp6tteGsgg6HPiSXx9Hx2tKW8jDXYVsSEoAO2yS1wBtRgBBS+B BJX+5pA0iheKKjmKkcXrujAzPDNWnwgomZkIpUtNf27wSgoC2fX/oRIs2r/NG9L69lp9 GycJlyMi6Py/CIIvo1W7NkLXRcoehwhzknnMljtOHV0HRK5ZBf1wdv3D0aLAzwI6coFY 3pN+OhmCxMgbvCxikTQQwfikFlsFoMWE+r++WI0qm6MwDvGddsfiU+9vOm6cASZQ+/4e RzWH+XhRjUgJjDxPUWk74gWtQmvO6+bPi/wGMK0HkGiPMC3G6iiUBN6ICf8vy/JEJNrK LkzQ== X-Gm-Message-State: ACrzQf0TNVtMlfq8vhTodNjnkD58e89UN9gIaveQ9jmlqUwAmMz0EGY/ 4pJoH4dJHvC4YrWOgu/Tand1ian3RmxoXVSmlwQDYQ== X-Google-Smtp-Source: AMsMyM4SOMzNPoEP4Br6h1r2CJRQYNKipv9r9MWilIR/DuJ8W+mBmmO97KOemPkCF+KRZPoaDKwtz/8KvAWwatKO7qo= X-Received: by 2002:a05:600c:2202:b0:3b4:6189:fc6a with SMTP id z2-20020a05600c220200b003b46189fc6amr4451007wml.171.1663732406891; Tue, 20 Sep 2022 20:53:26 -0700 (PDT) MIME-Version: 1.0 References: <20220810193033.1090251-4-pcc@google.com> <202208111500.62e0Bl2l-lkp@intel.com> <878rmfkzbu.wl-maz@kernel.org> <871qs6kntl.wl-maz@kernel.org> In-Reply-To: From: Peter Collingbourne Date: Tue, 20 Sep 2022 20:53:15 -0700 Message-ID: Subject: Re: [PATCH v3 3/7] mm: Add PG_arch_3 page flag To: Catalin Marinas Cc: kbuild-all@lists.01.org, kernel test robot , kvm@vger.kernel.org, Marc Zyngier , Cornelia Huck , Steven Price , Evgenii Stepanov , Vincenzo Frascino , Will Deacon , kvmarm@lists.cs.columbia.edu, Linux ARM X-BeenThere: kvmarm@lists.cs.columbia.edu X-Mailman-Version: 2.1.14 Precedence: list List-Id: Where KVM/ARM decisions are made List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: kvmarm-bounces@lists.cs.columbia.edu Sender: kvmarm-bounces@lists.cs.columbia.edu On Tue, Sep 20, 2022 at 9:58 AM Catalin Marinas wrote: > > On Tue, Sep 20, 2022 at 05:33:42PM +0100, Marc Zyngier wrote: > > On Tue, 20 Sep 2022 16:39:47 +0100, > > Catalin Marinas wrote: > > > On Mon, Sep 19, 2022 at 07:12:53PM +0100, Marc Zyngier wrote: > > > > On Mon, 05 Sep 2022 18:01:55 +0100, > > > > Catalin Marinas wrote: > > > > > Peter, please let me know if you want to pick this series up together > > > > > with your other KVM patches. Otherwise I can post it separately, it's > > > > > worth merging it on its own as it clarifies the page flag vs tag setting > > > > > ordering. > > > > > > > > I'm looking at queuing this, but I'm confused by this comment. Do I > > > > need to pick this as part of the series? Or is this an independent > > > > thing (my hunch is that it is actually required not to break other > > > > architectures...). > > > > > > This series series (at least the first patches) won't apply cleanly on > > > top of 6.0-rc1 and, of course, we shouldn't break other architectures. I > > > can repost the whole series but I don't have the setup to test the > > > MAP_SHARED KVM option (unless Peter plans to post it soon). > > > > I don't feel brave enough to take a series affecting all architectures > > It shouldn't affect the others, the only change is that PG_arch_2 is now > only defined for arm64 but no other architecture is using it. The > problem with loongarch is that it doesn't have enough spare bits in > page->flags and even without any patches I think it's broken with the > right value for NR_CPUS. > > > so late in the game, and the whole thing had very little arm64 > > exposure. The latest QEMU doesn't seem to work anymore, so I don't > > have any MTE-capable emulation (and using the FVP remotely is a pain > > in the proverbial neck). > > > > I'll come back to this after the merge window, should Peter decide to > > respin the series. > > It makes sense. Apologies for the delay, I've now sent out v4 of this series which includes the patches on your branch. Peter _______________________________________________ kvmarm mailing list kvmarm@lists.cs.columbia.edu https://lists.cs.columbia.edu/mailman/listinfo/kvmarm 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 vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 9F81CC6FA82 for ; Wed, 21 Sep 2022 03:53:51 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231182AbiIUDxu (ORCPT ); Tue, 20 Sep 2022 23:53:50 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:37248 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231158AbiIUDxf (ORCPT ); Tue, 20 Sep 2022 23:53:35 -0400 Received: from mail-wm1-x32a.google.com (mail-wm1-x32a.google.com [IPv6:2a00:1450:4864:20::32a]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id F1C847E811 for ; Tue, 20 Sep 2022 20:53:28 -0700 (PDT) Received: by mail-wm1-x32a.google.com with SMTP id r3-20020a05600c35c300b003b4b5f6c6bdso2982880wmq.2 for ; Tue, 20 Sep 2022 20:53:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date; bh=YjNJwrSGGsmqwkos7/v8yu+we95EXK5+N0CYYMWfM9Q=; b=VN/89PxJc45yG4lc8yqdX46Pa4D79Mh+lXq0MdwtCoqk6H+vPb0LYEGHxXxS0OAM1+ 7RmnF/LUaYOBG1W3DFvw8Lkn5MpRYPZwJLvhEs7ruA2GSOv3b2YvH7hUZOHrdR2zbEiA yTfU1+O3beASWzV4c0GeNLj05YiKbgIKYNkV+PJcuPE4wxVo2TXv9YZLiaatDHLgtpmQ GON/Vu3+5/D77WWTrzPWPFcpgy4Ornyxr7/HX/qmrufG41d4inNUeDdtVhrlLoQr110w hcvpstlAuApR4OeGLmxuVIaGhkDR6bTDnFFtUPIHaLmqLZtxkutVbKpmn2u0NjMB7wPB vOug== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date; bh=YjNJwrSGGsmqwkos7/v8yu+we95EXK5+N0CYYMWfM9Q=; b=pOzacA6OOA5NG8UOVTZf+vC36mZcu+WHwuL6rOxat+fwTFEbJw+6TyV9p9ipvN3IjR tEByjIKMrQl9JDqLTw0c1wFEkn7pDubUhkJ9g8Ed0ujSl75FnQoRU2q0tqfyZhj9L4yk aCx99Y/2Zc08FkLj9ESRbisdUfV2Wl/JyMb1/44VH0k5iemKGJhdJZ0bmueR2NSxbIE2 DyB29P7ELzZatvQclpx2BYUdF8X+7AD8ZSU6HGX36NooyJIZLCKFin+Bj0WtmqX302p7 pcgospWnIRqII5G+SnhkRAYV/MDZ08RFSRy7kpDMOW3RHLDK3HNiuYTekgWEZpd63Yok ZycQ== X-Gm-Message-State: ACrzQf1Y+/tEX07FnCLkJPWvhtqd7qil9d3b3ZJUOk9mZSoCyWjm/n3z QzAnZPIrC6/lRMHPlJKyC/Gy0dLipcWGYFtCbg9byA== X-Google-Smtp-Source: AMsMyM4SOMzNPoEP4Br6h1r2CJRQYNKipv9r9MWilIR/DuJ8W+mBmmO97KOemPkCF+KRZPoaDKwtz/8KvAWwatKO7qo= X-Received: by 2002:a05:600c:2202:b0:3b4:6189:fc6a with SMTP id z2-20020a05600c220200b003b46189fc6amr4451007wml.171.1663732406891; Tue, 20 Sep 2022 20:53:26 -0700 (PDT) MIME-Version: 1.0 References: <20220810193033.1090251-4-pcc@google.com> <202208111500.62e0Bl2l-lkp@intel.com> <878rmfkzbu.wl-maz@kernel.org> <871qs6kntl.wl-maz@kernel.org> In-Reply-To: From: Peter Collingbourne Date: Tue, 20 Sep 2022 20:53:15 -0700 Message-ID: Subject: Re: [PATCH v3 3/7] mm: Add PG_arch_3 page flag To: Catalin Marinas Cc: Marc Zyngier , kernel test robot , Linux ARM , kvmarm@lists.cs.columbia.edu, kbuild-all@lists.01.org, Cornelia Huck , Will Deacon , Evgenii Stepanov , kvm@vger.kernel.org, Steven Price , Vincenzo Frascino Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: kvm@vger.kernel.org On Tue, Sep 20, 2022 at 9:58 AM Catalin Marinas wrote: > > On Tue, Sep 20, 2022 at 05:33:42PM +0100, Marc Zyngier wrote: > > On Tue, 20 Sep 2022 16:39:47 +0100, > > Catalin Marinas wrote: > > > On Mon, Sep 19, 2022 at 07:12:53PM +0100, Marc Zyngier wrote: > > > > On Mon, 05 Sep 2022 18:01:55 +0100, > > > > Catalin Marinas wrote: > > > > > Peter, please let me know if you want to pick this series up together > > > > > with your other KVM patches. Otherwise I can post it separately, it's > > > > > worth merging it on its own as it clarifies the page flag vs tag setting > > > > > ordering. > > > > > > > > I'm looking at queuing this, but I'm confused by this comment. Do I > > > > need to pick this as part of the series? Or is this an independent > > > > thing (my hunch is that it is actually required not to break other > > > > architectures...). > > > > > > This series series (at least the first patches) won't apply cleanly on > > > top of 6.0-rc1 and, of course, we shouldn't break other architectures. I > > > can repost the whole series but I don't have the setup to test the > > > MAP_SHARED KVM option (unless Peter plans to post it soon). > > > > I don't feel brave enough to take a series affecting all architectures > > It shouldn't affect the others, the only change is that PG_arch_2 is now > only defined for arm64 but no other architecture is using it. The > problem with loongarch is that it doesn't have enough spare bits in > page->flags and even without any patches I think it's broken with the > right value for NR_CPUS. > > > so late in the game, and the whole thing had very little arm64 > > exposure. The latest QEMU doesn't seem to work anymore, so I don't > > have any MTE-capable emulation (and using the FVP remotely is a pain > > in the proverbial neck). > > > > I'll come back to this after the merge window, should Peter decide to > > respin the series. > > It makes sense. Apologies for the delay, I've now sent out v4 of this series which includes the patches on your branch. Peter 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 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 smtp.lore.kernel.org (Postfix) with ESMTPS id 413DBC6FA82 for ; Wed, 21 Sep 2022 03:57:05 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:Cc:To:Subject:Message-ID:Date:From: In-Reply-To:References:MIME-Version:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=ISLUpx4SinlK9jbQlgJUWY3rtK7JBeULDR5rHfzRuUE=; b=S/dvELea9hb6El NHMhupxyBQ9so+q7US/FAxZxgUoxPip60nwGbhBeJQlU6Wte3ZaG4q13ABvqelvy5/NxIK10bdSmv I8i4+LBGb/MnO6XapI0H4cmA7VkNwanmUj1SSb15L/Y+uWYVwwC1wVaUdW69c4PsL2Z7GQ0oaFWVV PKUeaGWP2rVrD/u+/MhsDI4GCEClMEZMeK15GVRynyahHF1o9EIuo2QZzvcM50zPns7pNpFutK5Xy dd/zSeb85IfYtawoqDBW7fe6lQUfrnQduYc/RlYYDH8zZqm9FZnBhTXw8WfboKC1v++ZpXsfNWqWo ePASpUwm0LEavBGXg2yA==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1oaqpw-008h5F-0d; Wed, 21 Sep 2022 03:55:48 +0000 Received: from mail-wm1-x32b.google.com ([2a00:1450:4864:20::32b]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1oaqnk-008g09-VO for linux-arm-kernel@lists.infradead.org; Wed, 21 Sep 2022 03:53:34 +0000 Received: by mail-wm1-x32b.google.com with SMTP id o20-20020a05600c4fd400b003b4a516c479so2993455wmq.1 for ; Tue, 20 Sep 2022 20:53:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date; bh=YjNJwrSGGsmqwkos7/v8yu+we95EXK5+N0CYYMWfM9Q=; b=VN/89PxJc45yG4lc8yqdX46Pa4D79Mh+lXq0MdwtCoqk6H+vPb0LYEGHxXxS0OAM1+ 7RmnF/LUaYOBG1W3DFvw8Lkn5MpRYPZwJLvhEs7ruA2GSOv3b2YvH7hUZOHrdR2zbEiA yTfU1+O3beASWzV4c0GeNLj05YiKbgIKYNkV+PJcuPE4wxVo2TXv9YZLiaatDHLgtpmQ GON/Vu3+5/D77WWTrzPWPFcpgy4Ornyxr7/HX/qmrufG41d4inNUeDdtVhrlLoQr110w hcvpstlAuApR4OeGLmxuVIaGhkDR6bTDnFFtUPIHaLmqLZtxkutVbKpmn2u0NjMB7wPB vOug== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date; bh=YjNJwrSGGsmqwkos7/v8yu+we95EXK5+N0CYYMWfM9Q=; b=mu+MqcLQoz+8qdRiQIvX5J7NQWX0pDPCJraFowlVrAfBve8xRyG1rfcplRHT7fNm0B 39fRHDrmgD21Y8OeReAJmWg/nvQcxPuCIx6OrlIxaEjjugE5h1N0yaMAQE9L2xUHrVxq miZ2ahWkPCTsiZ8XSYAbB1RApspr07RMCSUS8QRa9oOWJzrZL46S+cX6DQ7P4p0/ikuz IbCiwjz7kVeTh1UxMlSMuopu99qzkG/N1lyRND8FD1H6TjqayNfVy1DpR50iX8AEtQn5 ZWvhdXtRrj/cFTG5YwYR5PHiJ6aY/e4vhIMi6lUTHavZh2q4FsHNfdcp/5BfK24HEZc/ LPqg== X-Gm-Message-State: ACrzQf1voensx7JRJLq9+i8ava6LysfSLglAFdxmdMI7EgjIdz4MCZXQ gKMlGwBgNoxIU5ZAMQy2okpAtYAwflud4jrfZBgnRQ== X-Google-Smtp-Source: AMsMyM4SOMzNPoEP4Br6h1r2CJRQYNKipv9r9MWilIR/DuJ8W+mBmmO97KOemPkCF+KRZPoaDKwtz/8KvAWwatKO7qo= X-Received: by 2002:a05:600c:2202:b0:3b4:6189:fc6a with SMTP id z2-20020a05600c220200b003b46189fc6amr4451007wml.171.1663732406891; Tue, 20 Sep 2022 20:53:26 -0700 (PDT) MIME-Version: 1.0 References: <20220810193033.1090251-4-pcc@google.com> <202208111500.62e0Bl2l-lkp@intel.com> <878rmfkzbu.wl-maz@kernel.org> <871qs6kntl.wl-maz@kernel.org> In-Reply-To: From: Peter Collingbourne Date: Tue, 20 Sep 2022 20:53:15 -0700 Message-ID: Subject: Re: [PATCH v3 3/7] mm: Add PG_arch_3 page flag To: Catalin Marinas Cc: Marc Zyngier , kernel test robot , Linux ARM , kvmarm@lists.cs.columbia.edu, kbuild-all@lists.01.org, Cornelia Huck , Will Deacon , Evgenii Stepanov , kvm@vger.kernel.org, Steven Price , Vincenzo Frascino X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20220920_205333_043645_33573FEC X-CRM114-Status: GOOD ( 32.06 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Tue, Sep 20, 2022 at 9:58 AM Catalin Marinas wrote: > > On Tue, Sep 20, 2022 at 05:33:42PM +0100, Marc Zyngier wrote: > > On Tue, 20 Sep 2022 16:39:47 +0100, > > Catalin Marinas wrote: > > > On Mon, Sep 19, 2022 at 07:12:53PM +0100, Marc Zyngier wrote: > > > > On Mon, 05 Sep 2022 18:01:55 +0100, > > > > Catalin Marinas wrote: > > > > > Peter, please let me know if you want to pick this series up together > > > > > with your other KVM patches. Otherwise I can post it separately, it's > > > > > worth merging it on its own as it clarifies the page flag vs tag setting > > > > > ordering. > > > > > > > > I'm looking at queuing this, but I'm confused by this comment. Do I > > > > need to pick this as part of the series? Or is this an independent > > > > thing (my hunch is that it is actually required not to break other > > > > architectures...). > > > > > > This series series (at least the first patches) won't apply cleanly on > > > top of 6.0-rc1 and, of course, we shouldn't break other architectures. I > > > can repost the whole series but I don't have the setup to test the > > > MAP_SHARED KVM option (unless Peter plans to post it soon). > > > > I don't feel brave enough to take a series affecting all architectures > > It shouldn't affect the others, the only change is that PG_arch_2 is now > only defined for arm64 but no other architecture is using it. The > problem with loongarch is that it doesn't have enough spare bits in > page->flags and even without any patches I think it's broken with the > right value for NR_CPUS. > > > so late in the game, and the whole thing had very little arm64 > > exposure. The latest QEMU doesn't seem to work anymore, so I don't > > have any MTE-capable emulation (and using the FVP remotely is a pain > > in the proverbial neck). > > > > I'll come back to this after the merge window, should Peter decide to > > respin the series. > > It makes sense. Apologies for the delay, I've now sent out v4 of this series which includes the patches on your branch. Peter _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel From mboxrd@z Thu Jan 1 00:00:00 1970 Content-Type: multipart/mixed; boundary="===============9046186096512964119==" MIME-Version: 1.0 From: Peter Collingbourne To: kbuild-all@lists.01.org Subject: Re: [PATCH v3 3/7] mm: Add PG_arch_3 page flag Date: Tue, 20 Sep 2022 20:53:15 -0700 Message-ID: In-Reply-To: List-Id: --===============9046186096512964119== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable On Tue, Sep 20, 2022 at 9:58 AM Catalin Marinas = wrote: > > On Tue, Sep 20, 2022 at 05:33:42PM +0100, Marc Zyngier wrote: > > On Tue, 20 Sep 2022 16:39:47 +0100, > > Catalin Marinas wrote: > > > On Mon, Sep 19, 2022 at 07:12:53PM +0100, Marc Zyngier wrote: > > > > On Mon, 05 Sep 2022 18:01:55 +0100, > > > > Catalin Marinas wrote: > > > > > Peter, please let me know if you want to pick this series up toge= ther > > > > > with your other KVM patches. Otherwise I can post it separately, = it's > > > > > worth merging it on its own as it clarifies the page flag vs tag = setting > > > > > ordering. > > > > > > > > I'm looking at queuing this, but I'm confused by this comment. Do I > > > > need to pick this as part of the series? Or is this an independent > > > > thing (my hunch is that it is actually required not to break other > > > > architectures...). > > > > > > This series series (at least the first patches) won't apply cleanly on > > > top of 6.0-rc1 and, of course, we shouldn't break other architectures= . I > > > can repost the whole series but I don't have the setup to test the > > > MAP_SHARED KVM option (unless Peter plans to post it soon). > > > > I don't feel brave enough to take a series affecting all architectures > > It shouldn't affect the others, the only change is that PG_arch_2 is now > only defined for arm64 but no other architecture is using it. The > problem with loongarch is that it doesn't have enough spare bits in > page->flags and even without any patches I think it's broken with the > right value for NR_CPUS. > > > so late in the game, and the whole thing had very little arm64 > > exposure. The latest QEMU doesn't seem to work anymore, so I don't > > have any MTE-capable emulation (and using the FVP remotely is a pain > > in the proverbial neck). > > > > I'll come back to this after the merge window, should Peter decide to > > respin the series. > > It makes sense. Apologies for the delay, I've now sent out v4 of this series which includes the patches on your branch. Peter --===============9046186096512964119==--