From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from out-188.mta1.migadu.com (out-188.mta1.migadu.com [95.215.58.188]) (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 E9BE72080E8 for ; Fri, 20 Jun 2025 19:28:52 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=95.215.58.188 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1750447735; cv=none; b=nj1U9+Qe7Nb1KD8UoerGguKr910/ZHknSozcYnd1ppLwEQeDN5tmMgBJC4KPx4IntKII1p6SOVPXQR02osPUpRz0eRftEMA9KUjIjBsZ/xhHodTDNAhYW/lJfklI3tZ+a9UFVa54Pfbr+jHBlTqWo9hDR0+gqiJgTEIarVmnmH4= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1750447735; c=relaxed/simple; bh=DrZw3DT7Kllwn6vq1+VE3kts+TAHt/nlr3suzeS8pgk=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=Yd3hSIVtuelc6zfFvZgg+VAaV4yIjdDD5tF266IRglcBuCQ6rPnNWKwQEDt78N2Eph32sSENfmFq9YYKA1Rdemelkk3ukZPV/xCocROJQbZh8YyWeTT8c47hiNYr2+OfKeLPLDhbuM4zIOKatVj1xvUnFNqezDgM3KVoJMlkp6o= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.dev; spf=pass smtp.mailfrom=linux.dev; dkim=pass (1024-bit key) header.d=linux.dev header.i=@linux.dev header.b=W42T7MNl; arc=none smtp.client-ip=95.215.58.188 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.dev Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=linux.dev Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linux.dev header.i=@linux.dev header.b="W42T7MNl" Date: Fri, 20 Jun 2025 12:27:48 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux.dev; s=key1; t=1750447730; 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=NgldqAkN4EcKf+iDJigOAF1MecbzOvfvyTrQTD43eRc=; b=W42T7MNlvzs/y0GgOq0jyWHLLYVFWnXTLt8ehslxEORhH363LQ3I2EKnyY/lcXJ7TuYCCP /ddoesoS1z3+FzcQtRf+UEyi/ryVP6PVmtH1LVq3QA7cCZuxX6dbA5NubQaX4Y9lVNRphf Jqn5Jzz8vxkhz8VXmNt/f9dhM/LssW8= X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. From: Oliver Upton To: Sean Christopherson Cc: Marc Zyngier , Paolo Bonzini , Joerg Roedel , David Woodhouse , Lu Baolu , linux-arm-kernel@lists.infradead.org, kvmarm@lists.linux.dev, kvm@vger.kernel.org, iommu@lists.linux.dev, linux-kernel@vger.kernel.org, Sairaj Kodilkar , Vasant Hegde , Maxim Levitsky , Joao Martins , Francesco Lavra , David Matlack Subject: Re: [PATCH v3 02/62] KVM: arm64: WARN if unmapping vLPI fails Message-ID: References: <20250611224604.313496-2-seanjc@google.com> <20250611224604.313496-4-seanjc@google.com> <86tt4lcgs3.wl-maz@kernel.org> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Migadu-Flow: FLOW_OUT On Fri, Jun 20, 2025 at 12:04:19PM -0700, Sean Christopherson wrote: > On Fri, Jun 20, 2025, Oliver Upton wrote: > > Can you just send it out as a standalone patch? It's only tangientally > > related to the truckload of x86 stuff > > The issue is that "KVM: Don't WARN if updating IRQ bypass route fails" directly > depends on both this patch Eh? At worst we break bisection for the warn, which I'm sure we manage to commit similar high crimes on the regular. > If I post it as a standalone patch, could you/Marc put it into a stable topic > branch based on kvm/master? (kvm/master now has patch 1, yay!) Then I can create > a topic branch for this mountain of stuff based on the arm64 topic branch. Ok, how about making the arm64 piece patch 1 in your series and you take the whole pile. If we need it, I'll bug you for a ref that only has the first change. That ok? Thanks, Oliver