Received: by 2002:a25:d7c1:0:0:0:0:0 with SMTP id o184csp2785452ybg; Thu, 24 Oct 2019 15:20:25 -0700 (PDT) X-Google-Smtp-Source: APXvYqzfM6phwNc7DN7ewSNocvvjWMzYrsNepJYWlgA77mgkwO1VJcmu4+OlKcoNAlRJBUqIztA2 X-Received: by 2002:a05:6402:1452:: with SMTP id d18mr546064edx.158.1571955625642; Thu, 24 Oct 2019 15:20:25 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1571955625; cv=none; d=google.com; s=arc-20160816; b=YJGwlh6vkQC2g4sWnlc+YtJRUxgktuIZQptdqLV9V4n+gTkr9HrRS7xsozEqh5f3RB 1/tAwYYZ8OdCYUr/8osjNNsTSMDckrOIYphplwXbF6qoczjb/YOCYPZaqFCr3RzC5pvY uMxX4CJXNXAzXTQeF6GVjmrGxuwyscElL01Q202dEBx/UeaCHZCIQiLn6NBhsWenC/6h Sg7Vu6hOFCv3FE0zngMooa+xBko6s5rsxBh39QnDjk2/8D97t2+Zy8udWakOvJOsACRx tohuluLg379VqzAKQEW3R8LCFhfbKon5UsIUKm5ubqiw95MvQBJdbuN0PE3VflcpuP2M /i6A== 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:cc:from:date:content-transfer-encoding:mime-version :subject:to; bh=IEJs5+1JfXR1VaU2c3uvz75TGBROujo1NYQqCBU92OI=; b=S9TERPmOeWR7yxm/pak9uHiUsjoaXxrgPmB3Kmnks+srAods6v3cEHT5M8+JK01e2g LX8Ymkv9F/YvLd8Rg6NeEn6bhBwAy66Mnm5dVlp3CpYEKUgAzAE+K1YSXTKQXI4gNZXU lUfOfJd7kdi/3UQBF9eO+0JYetfHi2T5/xxHmJxLA7UAVTiF8mLoXSA6vGrkWD6esHXS YksVW93Zdxesgygfb20MJTPV4NwRqPrU9tT7/gcDkJP3f8s7hNJR4uZxjy0VTvwAgvSl FEbHMnD2XoIVEQihWVfXJcsIkIHL6VTcVlLQNwZ9Tx0okYHLQdcTR1CUDA76rdU7HgD7 +5Eg== ARC-Authentication-Results: i=1; mx.google.com; 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=fail (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 m9si52085ejk.322.2019.10.24.15.20.01; Thu, 24 Oct 2019 15:20:25 -0700 (PDT) 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; 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=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2408595AbfJXH1z (ORCPT + 99 others); Thu, 24 Oct 2019 03:27:55 -0400 Received: from inca-roads.misterjones.org ([213.251.177.50]:33725 "EHLO inca-roads.misterjones.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2408571AbfJXH1z (ORCPT ); Thu, 24 Oct 2019 03:27:55 -0400 Received: from www-data by cheepnis.misterjones.org with local (Exim 4.80) (envelope-from ) id 1iNXXE-0002IH-M6; Thu, 24 Oct 2019 09:27:52 +0200 To: Christoph Hellwig Subject: Re: [PATCH] irqchip: Skip contexts other supervisor in =?UTF-8?Q?plic=5Finit=28=29?= X-PHP-Originating-Script: 0:main.inc MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Date: Thu, 24 Oct 2019 08:27:52 +0100 From: Marc Zyngier Cc: Palmer Dabbelt , Paul Walmsley , , , , , In-Reply-To: <20191024070311.GA16652@infradead.org> References: <20191024013019.GA675@infradead.org> <20191024075116.48055961@why> <20191024070311.GA16652@infradead.org> Message-ID: <67fff4d811c27017e7b34267365c8c0f@www.loen.fr> X-Sender: maz@kernel.org User-Agent: Roundcube Webmail/0.7.2 X-SA-Exim-Connect-IP: X-SA-Exim-Rcpt-To: hch@infradead.org, palmer@sifive.com, paul.walmsley@sifive.com, alan.mikhak@sifive.com, linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org, tglx@linutronix.de, jason@lakedaemon.net X-SA-Exim-Mail-From: maz@kernel.org X-SA-Exim-Scanned: No (on cheepnis.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 2019-10-24 08:03, Christoph Hellwig wrote: > On Thu, Oct 24, 2019 at 07:51:16AM +0100, Marc Zyngier wrote: >> > > > Will this need to change for RISC-V M-mode Linux support? >> > > > >> > > > >> https://lore.kernel.org/linux-riscv/20191017173743.5430-1-hch@lst.de/ >> > > >> > > Yes. >> > >> > For M-mode we'll want to check IRQ_M_EXT above. So we should just >> > merge this patch ASAP and then for my rebased M-mode series I'll >> > fix the check to do that for the M-Mode case, which is much >> cleaner >> > than my hack. >> >> Does this need to be taken as a fix, potentially Cc to stable? Or is >> that 5.5 material? > > So I though that the S-mode context were kinda aways to be sorted > before > M-mode, but I can't find anything guranteeing it. So I think this > actually is a fix, and getting this queued up in the next -rc would > really help me with the nommu stuff - otherwise we'd need to take it > through the riscv tree for 5.5 to avoid conflicts. > > Btw, here is my: > > Reviewed-by: Christoph Hellwig > > for the patch. Thanks for that. Alan, if you can respin this patch with an updated commit message, I'll queue it with a couple of other nits I have lying around, and send it to Thomas by the end of the week. M. -- Jazz is not dead. It just smells funny...