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=-2.3 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,USER_AGENT_SANE_1 autolearn=no 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 D5D6DC76188 for ; Tue, 16 Jul 2019 08:30:59 +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 A7E962173C for ; Tue, 16 Jul 2019 08:30:59 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=lists.infradead.org header.i=@lists.infradead.org header.b="TBtk2oar" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org A7E962173C Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=arm.com 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:In-Reply-To:MIME-Version:References: 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=lK5AubK7HFnlTNsZRq24weQCel4EsNYMH3B1ErLf52Y=; b=TBtk2oarWU9QaN OfT3ENoO9aG3BKMDClSzar5EHQyo9WcgMAq7tVwZVMoc0LgQ02WItt1NLMbxKsHg1TmL9ML/Kejf9 /Sq14GLUQWs6rDXYvPgp/hrGNnraFvkkZDQpMk/T0Vlm++vt/n+CsT07tLEUZod5sBzK5Ob/3r1b+ 0fFBjwD2wRssXnofSipnQO6V/Wv5V14nQNeydeelUHdiA+Xx6e6DBV4f3iz+ZS7EOkY0B6Jqq8bgN FsHaSeqrAmlwsUybXE5PAzM2C05rLnTG8ti4Rzna04m+mz4eqmpZdeUocGTNppgcv1HPt7OlY7AAx 3uePT0YZ5By8b2aQh5uA==; Received: from localhost ([127.0.0.1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.92 #3 (Red Hat Linux)) id 1hnIrS-0001Zn-FA; Tue, 16 Jul 2019 08:30:58 +0000 Received: from foss.arm.com ([217.140.110.172]) by bombadil.infradead.org with esmtp (Exim 4.92 #3 (Red Hat Linux)) id 1hnIrP-0001ZK-0N for linux-arm-kernel@lists.infradead.org; Tue, 16 Jul 2019 08:30:56 +0000 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id F095B2B; Tue, 16 Jul 2019 01:30:53 -0700 (PDT) Received: from e103592.cambridge.arm.com (usa-sjc-imap-foss1.foss.arm.com [10.121.207.14]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id EC4B03F59C; Tue, 16 Jul 2019 01:30:52 -0700 (PDT) Date: Tue, 16 Jul 2019 09:30:50 +0100 From: Dave Martin To: Mark Rutland Subject: Re: [RFC] Add virtual SDEI support in qemu Message-ID: <20190716083050.GK2790@e103592.cambridge.arm.com> References: <1b0aa6b2-80b1-a72e-6849-7323c3b9c6bc@huawei.com> <20190715134059.GJ2790@e103592.cambridge.arm.com> <20190715134848.GI56232@lakrids.cambridge.arm.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20190715134848.GI56232@lakrids.cambridge.arm.com> User-Agent: Mutt/1.5.23 (2014-03-12) X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20190716_013055_091153_0CD571B4 X-CRM114-Status: GOOD ( 10.04 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Marc Zyngier , qemu-devel@nongnu.org, qemu-arm@nongnu.org, Guoheyi , kvmarm@lists.cs.columbia.edu, linux-arm-kernel@lists.infradead.org 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 Mon, Jul 15, 2019 at 02:48:49PM +0100, Mark Rutland wrote: > On Mon, Jul 15, 2019 at 02:41:00PM +0100, Dave Martin wrote: [...] > > So long as KVM_EXIT_HYPERCALL reports sufficient information so that > > userspace can identify the cause as an SMC and retrieve the SMC > > immediate field, this seems feasible. > > > > For its own SMCCC APIs, KVM exclusively uses HVC, so rerouting SMC to > > userspace shouldn't conflict. > > Be _very_ careful here! In systems without EL3 (and without NV), SMC > UNDEFs rather than trapping to EL2. Given that, we shouldn't build a > hypervisor ABI that depends on SMC. Good point. I was hoping that was all ancient history by now, but if not... [...] Cheers ---Dave _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel