Received: by 2002:a25:8b91:0:0:0:0:0 with SMTP id j17csp4939374ybl; Wed, 22 Jan 2020 07:25:24 -0800 (PST) X-Google-Smtp-Source: APXvYqwhGigmDZUrrru3Je1foG9tOQzSLDVXNniLHCrudJrgwwgR/Ly+gtfAjuY91QnbymLxaWln X-Received: by 2002:aca:ec4d:: with SMTP id k74mr6880375oih.64.1579706724075; Wed, 22 Jan 2020 07:25:24 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1579706724; cv=none; d=google.com; s=arc-20160816; b=zpji5tvqnY0D+q1hENBDQO1NHRrrfam/4ps3hv3asVS12czY5sbDqKmzI4USVz48Q2 q3tciXsAkrsnajF960AnMWy4mdoYnwW5jlB3LeNxipB/Y9QSlBIlS/qF6e4kFRS2EW5y 4405/5qMIEJVKjigLHogLJjb3d0Kg+Si5hnK5ttMczqR0pUoe5pN1Ds0xvtPs53XGLDn uztgd8ybRzWAxOm+x66iDDzykpRkQsHC8KiCGGqxpMnx3nWHlECn5IIDeTG6dLhkcHbe 2EE/gVMyObF0Uc7HW9Tm5L0eMmJ+NK3XaTo3SmzglxW3rnQcGMEZXnRL6HQa5+Tx6XOe OgvQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:message-id:references :in-reply-to:subject:cc:to:from:date:content-transfer-encoding :mime-version:dkim-signature; bh=E8oxKSUhokEZlbcHsyilpMd1d0CdDcKLUO0ULzU4rqI=; b=wwgZTrVQB3JlavfhrcbVJt9vouB5xgldC1ayqcox+BJS4rpoHEPadalYwau5xUbiCH 2ARRo9cK0sOFiFE0bS/YilZoLyahxOoY13r5hdv/92F7VrkSioFM2VrRdsjOAzz08mgO 31+McJNWxSVM9OmMkb9IpHoNGjOesUoxGEkt22NFbQuqPsH51u044XDojLjPYrW2rFl0 sScVT5Qq3H7dqOIE+w+Bz8j9jst8VRnwVGN7SKU2/lhEo0lDBiObbt09sN7VIqjx06iH XK4BRlIUXFzCKMp8jmZVL15nselbnmY59rZErEAL+auCyQW3n2ghzcY1f4UrdEJvxs5H uV0g== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=JwTI5lg6; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id f23si23177120oto.205.2020.01.22.07.25.11; Wed, 22 Jan 2020 07:25:24 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=JwTI5lg6; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726061AbgAVPXB (ORCPT + 99 others); Wed, 22 Jan 2020 10:23:01 -0500 Received: from mail.kernel.org ([198.145.29.99]:57884 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725802AbgAVPXA (ORCPT ); Wed, 22 Jan 2020 10:23:00 -0500 Received: from disco-boy.misterjones.org (disco-boy.misterjones.org [51.254.78.96]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id D22252071E; Wed, 22 Jan 2020 15:22:59 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1579706580; bh=I6Fm8pRywuvXE5eAUkUFAQZAHyzekaXyAPBr1svSKo8=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=JwTI5lg67kVcQZIQcX7ngbpqPVDrnWFO32tRtNk66TifmLRWur2b1K1wjX+ROG3X0 XB30G7TCO7UebtCILqcyhNb14J2XasD7fQ/G27ccRi73U6HXREZSbiH9YsNPJiQ8dU m4lf4upiI6ZYcecFKp26B20XROJqHXZFQN7U8/6U= Received: from disco-boy.misterjones.org ([51.254.78.96] helo=www.loen.fr) by disco-boy.misterjones.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1iuHqM-000m1N-1z; Wed, 22 Jan 2020 15:22:58 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Date: Wed, 22 Jan 2020 15:22:58 +0000 From: Marc Zyngier To: Zenghui Yu Cc: kvmarm@lists.cs.columbia.edu, linux-kernel@vger.kernel.org, tglx@linutronix.de, jason@lakedaemon.net, wanghaibin.wang@huawei.com Subject: Re: [PATCH] irqchip/gic-v3-its: Don't confuse get_vlpi_map() by writing DB config In-Reply-To: <06a484bd-4f46-6884-1bee-9b7b65fd0856@huawei.com> References: <20200122085609.658-1-yuzenghui@huawei.com> <4aaaad3ae7367c5c932c430e18550d9e@kernel.org> <06a484bd-4f46-6884-1bee-9b7b65fd0856@huawei.com> Message-ID: X-Sender: maz@kernel.org User-Agent: Roundcube Webmail/1.3.8 X-SA-Exim-Connect-IP: 51.254.78.96 X-SA-Exim-Rcpt-To: yuzenghui@huawei.com, kvmarm@lists.cs.columbia.edu, linux-kernel@vger.kernel.org, tglx@linutronix.de, jason@lakedaemon.net, wanghaibin.wang@huawei.com X-SA-Exim-Mail-From: maz@kernel.org X-SA-Exim-Scanned: No (on disco-boy.misterjones.org); SAEximRunCond expanded to false Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2020-01-22 11:29, Zenghui Yu wrote: > Hi Marc, > > On 2020/1/22 18:44, Marc Zyngier wrote: >> Hi Zenghui, >> >> Thanks for this. >> >> On 2020-01-22 08:56, Zenghui Yu wrote: >>> When we're writing config for the doorbell interrupt, get_vlpi_map() >>> will >>> get confused by doorbell's d->parent_data hack and find the wrong >>> its_dev >>> as chip data and the wrong event. >>> >>> Fix this issue by making sure no doorbells will be involved before >>> invoking >>> get_vlpi_map(), which restore some of the logic in >>> lpi_write_config(). >>> >>> Fixes: c1d4d5cd203c ("irqchip/gic-v3-its: Add its_vlpi_map helpers") >>> Signed-off-by: Zenghui Yu >>> --- >>> >>> This is based on mainline and can't be directly applied to the >>> current >>> irqchip-next. >>> >>>  drivers/irqchip/irq-gic-v3-its.c | 5 +++-- >>>  1 file changed, 3 insertions(+), 2 deletions(-) >>> >>> diff --git a/drivers/irqchip/irq-gic-v3-its.c >>> b/drivers/irqchip/irq-gic-v3-its.c >>> index e05673bcd52b..cc8a4fcbd6d6 100644 >>> --- a/drivers/irqchip/irq-gic-v3-its.c >>> +++ b/drivers/irqchip/irq-gic-v3-its.c >>> @@ -1181,12 +1181,13 @@ static struct its_vlpi_map >>> *get_vlpi_map(struct irq_data *d) >>> >>>  static void lpi_write_config(struct irq_data *d, u8 clr, u8 set) >>>  { >>> -    struct its_vlpi_map *map = get_vlpi_map(d); >>>      irq_hw_number_t hwirq; >>>      void *va; >>>      u8 *cfg; >>> >>> -    if (map) { >>> +    if (irqd_is_forwarded_to_vcpu(d)) { >>> +        struct its_vlpi_map *map = get_vlpi_map(d); >>> + >>>          va = page_address(map->vm->vprop_page); >>>          hwirq = map->vintid; >> >> Shouldn't we fix get_vlpi_map() instead? Something like (untested): >> >> diff --git a/drivers/irqchip/irq-gic-v3-its.c >> b/drivers/irqchip/irq-gic-v3-its.c >> index e05673bcd52b..b704214390c0 100644 >> --- a/drivers/irqchip/irq-gic-v3-its.c >> +++ b/drivers/irqchip/irq-gic-v3-its.c >> @@ -1170,13 +1170,14 @@ static void its_send_vclear(struct its_device >> *dev, u32 event_id) >>   */ >>  static struct its_vlpi_map *get_vlpi_map(struct irq_data *d) >>  { >> -    struct its_device *its_dev = irq_data_get_irq_chip_data(d); >> -    u32 event = its_get_event_id(d); >> +    if (irqd_is_forwarded_to_vcpu(d)) { >> +        struct its_device *its_dev = irq_data_get_irq_chip_data(d); >> +        u32 event = its_get_event_id(d); >> >> -    if (!irqd_is_forwarded_to_vcpu(d)) >> -        return NULL; >> +        return dev_event_to_vlpi_map(its_dev, event); >> +    } >> >> -    return dev_event_to_vlpi_map(its_dev, event); >> +    return NULL; >>  } >> >>  static void lpi_write_config(struct irq_data *d, u8 clr, u8 set) >> >> >> Or am I missing the actual problem? > > No. I also thought about fixing the issue by this way and I'm OK with > both approaches. OK, thanks. I've added this to irqchip-next[1], and rebased the v4.1 series on top of it. That way, the fix will trickle down to stable without conflicts. I've also given it a go on D05 with GICv4 enabled, and nothing caught fire. M. [1] https://git.kernel.org/pub/scm/linux/kernel/git/maz/arm-platforms.git/commit/?h=irq/irqchip-next&id=093bf439fee0d40ade7e309c1288b409cdc3b38f -- Jazz is not dead. It just smells funny...