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 X-Spam-Level: X-Spam-Status: No, score=-1.0 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, T_DKIMWL_WL_HIGH,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 4B952C28CC3 for ; Tue, 4 Jun 2019 15:05:08 +0000 (UTC) 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 mail.kernel.org (Postfix) with ESMTPS id 031FC242F0 for ; Tue, 4 Jun 2019 15:05:08 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=lists.infradead.org header.i=@lists.infradead.org header.b="Qt+ZBFfz" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 031FC242F0 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=goodmis.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-arm-kernel-bounces+infradead-linux-arm-kernel=archiver.kernel.org@lists.infradead.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20170209; h=Sender: Content-Transfer-Encoding:Content-Type:Cc:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:MIME-Version:References:In-Reply-To: Message-ID:Subject: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=Xn5i2YHrxZ7MBOkPJq1bH7BLLqMm/iXEsaIaIO+0TAc=; b=Qt+ZBFfztfnSbO HqGSgrsSIjJ2fIQegKtQZy0LhvagtNn7rzarROFoG6VepEiksoBhv1P4d2Hxr1OvqrAmT2ASWhkhK 5NCgEgmA+l/Fq+dFTMDo1rD3B7ENvy+bvQGuI45bDDUjwq6+uFTrjP6BDG+SAaQ2nPfyrknn4E+5C 3A4H2cb8q3V09lbX/X69mm7gyOrOLpmtKKCZSUCSwItn/krpDhva2NVpbYMIVjNP6/OmUbHrob4HX JkNA0E22Q0kWiRxPH65+vTkPIR3TEJji0GEsh1JBKMOI8l4nxkCVrxvTziQe6aSVq6EhUq8kWjA+F 4rkC6ECm8v5KuByIaB9g==; Received: from localhost ([127.0.0.1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.90_1 #2 (Red Hat Linux)) id 1hYAzq-00059u-EP; Tue, 04 Jun 2019 15:05:06 +0000 Received: from mail.kernel.org ([198.145.29.99]) by bombadil.infradead.org with esmtps (Exim 4.90_1 #2 (Red Hat Linux)) id 1hYAzl-0004VS-Ff for linux-arm-kernel@lists.infradead.org; Tue, 04 Jun 2019 15:05:03 +0000 Received: from oasis.local.home (unknown [146.247.46.6]) (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 5147B24059; Tue, 4 Jun 2019 15:04:59 +0000 (UTC) Date: Tue, 4 Jun 2019 11:04:54 -0400 From: Steven Rostedt To: Marc Zyngier Subject: Re: KVM Arm Device passthrough and linux-rt Message-ID: <20190604110454.2b99ee6e@oasis.local.home> In-Reply-To: References: <26832850-37ee-ae07-08ca-cc3e90978867@arm.com> <20190604091607.2e87eb36@oasis.local.home> X-Mailer: Claws Mail 3.17.3 (GTK+ 2.24.32; x86_64-pc-linux-gnu) MIME-Version: 1.0 X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20190604_080501_935321_F8ADB313 X-CRM114-Status: UNSURE ( 7.73 ) X-CRM114-Notice: Please train this message. X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: linux-rt-users , julia@ni.com, Sebastian Andrzej Siewior , Julien Grall , kvmarm@lists.cs.columbia.edu, linux-arm-kernel Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+infradead-linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Tue, 4 Jun 2019 14:53:26 +0100 Marc Zyngier wrote: > That's to prevent the injection of an interrupt firing on the same CPU > while we're saving the corresponding vcpu interrupt context, among other > things (the whole guest exit path runs with interrupt disabled in order > to avoid this kind of thing). Can't we use a per_cpu local lock for this? -- Steve _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel