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 EF3FBC3DA6E for ; Sun, 17 Dec 2023 17:35:14 +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=8d9tqOHjFpXH0c+NHdt/6hbY1IN/IIJyXrzv4ntSHFc=; b=1bGt9xnhQYsNCw q59lpOvBb+LlEBsv06XfzT+PKPQxnbNe89cR+uLCaYRD6RUcR1GrDY+NBJam1QZ7xxtDE87xl8Vc3 HpopyPwa23fyz/NotElNr+CZHN95dC1oEe8UAm/GWz7qkQJ1nZmlBoYtQWr0XBeVH9DsFRTcSwNK5 FW5wpCZmrv7hVIruW4Z3ZybYTVhJfZiYOb8GSOwka64tfDqqVz0VZz/NNcjzpzp5pGRLGyf7v5m8o iU87dLb1pPl7NHWNGr1tB9tymNgNUSi2jro7cUf4a0z0xIstqcZuE6U6mArWrNhUVpkZp/8QfEmYI +37C6IhLRRD8XqbR3h3g==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.96 #2 (Red Hat Linux)) id 1rEv2R-008ENv-2x; Sun, 17 Dec 2023 17:34:51 +0000 Received: from out-173.mta1.migadu.com ([95.215.58.173]) by bombadil.infradead.org with esmtps (Exim 4.96 #2 (Red Hat Linux)) id 1rEv2P-008ENF-1m for linux-arm-kernel@lists.infradead.org; Sun, 17 Dec 2023 17:34:51 +0000 Date: Sun, 17 Dec 2023 17:34:38 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux.dev; s=key1; t=1702834483; 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=tMaWKK6aNhEcNfGg2LkGPbfORjqRLPRkKIISdX758Xs=; b=DwF57sKLMND/XMkN6KaeRPN8526vV2qSNpsGgPACgycdjmXJwmSQ41nD7AXG5J900WS2dQ ALV9Zcgid8ICXaFBUgWjFDD2HYgIjQv0mp7J9YXhF1LgCI4z4odlb2nulN0SYA3D5mKM26 45jlUdzYlJb2uwbzE4u2EBVCulRwlZw= X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. From: Oliver Upton To: Marc Zyngier Cc: Kunkun Jiang , James Morse , Suzuki K Poulose , Zenghui Yu , Catalin Marinas , Will Deacon , Jean-Philippe Brucker , "moderated list:ARM SMMU DRIVERS" , kvmarm@lists.linux.dev, open list , "wanghaibin.wang@huawei.com" Subject: Re: [bug report] GICv4.1: vSGI remains pending across the guest reset Message-ID: References: <7e7f2c0c-448b-10a9-8929-4b8f4f6e2a32@huawei.com> <87a5q983zc.wl-maz@kernel.org> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: X-Migadu-Flow: FLOW_OUT X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20231217_093449_733266_CAFAB923 X-CRM114-Status: GOOD ( 19.12 ) 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 Sun, Dec 17, 2023 at 05:33:16PM +0000, Oliver Upton wrote: > On Sun, Dec 17, 2023 at 11:26:15AM +0000, Marc Zyngier wrote: > > [...] > > > But this has *nothing* to do with the guest. This is the *host* > > userspace performing a write to the redistributor view, which has > > different semantics. Which is why your earlier description made no > > sense to me. > > > > I think the problem is slightly larger than what you describe. A write > > to ISPENDR0 should be propagated to the ITS for any values of the > > latch, just like this happens on enabling HW-backed SGIs. > > > > Can you please give this a go? > > What do you think about using this as an opportunity for a bit of > cleanup? It'd be nice unify the various MMIO and uaccess handlers for > SPENDING + CPENDING while being careful about the arch_timer interrupt. Cut myself off... Meant to say that user writes to SPENDING for GICv3 can then be treated as: > clear = ~val; > vgic_uaccess_write_spending(val); > vgic_uaccess_write_cpending(clear); -- Thanks, Oliver _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel