From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id C5C87224EA for ; Mon, 13 Nov 2023 17:50:01 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=none Received: by smtp.kernel.org (Postfix) with ESMTPSA id 94859C433C7; Mon, 13 Nov 2023 17:49:58 +0000 (UTC) Date: Mon, 13 Nov 2023 17:49:56 +0000 From: Catalin Marinas To: Ryan Roberts Cc: Ard Biesheuvel , Ard Biesheuvel , Will Deacon , Marc Zyngier , Oliver Upton , Mark Rutland , Anshuman Khandual , Kees Cook , Joey Gouly , Suzuki K Poulose , James Morse , Zenghui Yu , linux-arm-kernel@lists.infradead.org, kvmarm@lists.linux.dev Subject: Re: [RFC PATCH v1 0/3] Update tlb invalidation routines for FEAT_LPA2 Message-ID: References: <20231027115634.1432154-1-ryan.roberts@arm.com> <3800df70-73f2-44b7-a6ed-15ec0bd63f5f@arm.com> <1bdcdd85-9470-408c-aaac-fa4548bb2385@arm.com> Precedence: bulk X-Mailing-List: kvmarm@lists.linux.dev List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1bdcdd85-9470-408c-aaac-fa4548bb2385@arm.com> On Mon, Nov 13, 2023 at 04:44:58PM +0000, Ryan Roberts wrote: > On 13/11/2023 13:27, Catalin Marinas wrote: > > If these patches are needed for Ard's series (I think they do), they > > could be posted together. But first we need to split Ard's series into > > at least two: reworking the memory map together with moving (some of) > > the init code to C and the actual LPA2 stage 1 support. We might even > > through LPA2 stage 2 on top if we feel brave ;). We can queue them all > > together but having separate series gives us an option to drop bits if > > needed. > > Sorry I'm not completely sure what you are suggesting I do here. In the context > of the lpa2/kvm series, Marc previously said he would merge it for v6.8 if I > posted against v6.7-rc1 (which is what I'm gearing up for now). If we merge your series independently of Ard's, that's fine, these three patches can go together as a prefix. > My series and Ard's are independent except that they both depend on the 3 > patches in this RFC. Ard has just suggested he would prefix his series with > these 3 patches and I would continue to do the same, then they can be handled as > 2 independent series (or more if Ard is splitting his) - the first 3 patches > will just desolve to nothing for the series that goes in second. > > Does that work for you, are are you suggesting I should re-post this as an > independent series? No need to. Just post your LPA2 patches with these three as a prefix. Ard can include them as well and if it gets to merging both, we'll sort out a small stable branch for these three patches. -- Catalin 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 9D89BC4332F for ; Mon, 13 Nov 2023 17:50:36 +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:In-Reply-To:MIME-Version:References: Message-ID:Subject:Cc:To:From:Date:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=Bc7cZLw+Q6E3RaJIUBsUkcNppLwS9odcmtFzi3+y0vc=; b=ZMJq6Ckt2a9dYy E5zRKVcpCyn8+M79JkjAqyrlRX7X83xu45noYnNhZdyqTL4/JeJ9uZFPlj/pfNGpP7fg3omWDn+ey jSa6UdLjl4P4PsBs0HrSpiG6XV7iGXqenjlVvaAaE6c7VhRwD3xILPMuXRUf5X4WrisMzdr3ISFJm 6jjPzuj3RoVFR5j9DIm0C0PXUzrtPK6r3VLVMARNgYuHxZML4AS3lTAM3InykOfZSgf+FFwrL7pVU /CbGBFYO/ctoB59YoqxMfmtjtvJzHav+QpBTzcw37fsFT9CF5fS1ddx4yuKFaN5jf6v2Xbmnhc+aC FhQz9d3GqWGEcvXuWcsQ==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.96 #2 (Red Hat Linux)) id 1r2b4Z-00ER97-29; Mon, 13 Nov 2023 17:50:07 +0000 Received: from ams.source.kernel.org ([145.40.68.75]) by bombadil.infradead.org with esmtps (Exim 4.96 #2 (Red Hat Linux)) id 1r2b4W-00ER88-21 for linux-arm-kernel@lists.infradead.org; Mon, 13 Nov 2023 17:50:06 +0000 Received: from smtp.kernel.org (transwarp.subspace.kernel.org [100.75.92.58]) by ams.source.kernel.org (Postfix) with ESMTP id CD6A4B80EF8; Mon, 13 Nov 2023 17:50:02 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 94859C433C7; Mon, 13 Nov 2023 17:49:58 +0000 (UTC) Date: Mon, 13 Nov 2023 17:49:56 +0000 From: Catalin Marinas To: Ryan Roberts Cc: Ard Biesheuvel , Ard Biesheuvel , Will Deacon , Marc Zyngier , Oliver Upton , Mark Rutland , Anshuman Khandual , Kees Cook , Joey Gouly , Suzuki K Poulose , James Morse , Zenghui Yu , linux-arm-kernel@lists.infradead.org, kvmarm@lists.linux.dev Subject: Re: [RFC PATCH v1 0/3] Update tlb invalidation routines for FEAT_LPA2 Message-ID: References: <20231027115634.1432154-1-ryan.roberts@arm.com> <3800df70-73f2-44b7-a6ed-15ec0bd63f5f@arm.com> <1bdcdd85-9470-408c-aaac-fa4548bb2385@arm.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <1bdcdd85-9470-408c-aaac-fa4548bb2385@arm.com> X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20231113_095004_813074_80B2FBDB X-CRM114-Status: GOOD ( 21.10 ) 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 Mon, Nov 13, 2023 at 04:44:58PM +0000, Ryan Roberts wrote: > On 13/11/2023 13:27, Catalin Marinas wrote: > > If these patches are needed for Ard's series (I think they do), they > > could be posted together. But first we need to split Ard's series into > > at least two: reworking the memory map together with moving (some of) > > the init code to C and the actual LPA2 stage 1 support. We might even > > through LPA2 stage 2 on top if we feel brave ;). We can queue them all > > together but having separate series gives us an option to drop bits if > > needed. > > Sorry I'm not completely sure what you are suggesting I do here. In the context > of the lpa2/kvm series, Marc previously said he would merge it for v6.8 if I > posted against v6.7-rc1 (which is what I'm gearing up for now). If we merge your series independently of Ard's, that's fine, these three patches can go together as a prefix. > My series and Ard's are independent except that they both depend on the 3 > patches in this RFC. Ard has just suggested he would prefix his series with > these 3 patches and I would continue to do the same, then they can be handled as > 2 independent series (or more if Ard is splitting his) - the first 3 patches > will just desolve to nothing for the series that goes in second. > > Does that work for you, are are you suggesting I should re-post this as an > independent series? No need to. Just post your LPA2 patches with these three as a prefix. Ard can include them as well and if it gets to merging both, we'll sort out a small stable branch for these three patches. -- Catalin _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel