From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933107AbdCUWRy (ORCPT ); Tue, 21 Mar 2017 18:17:54 -0400 Received: from mail-wr0-f172.google.com ([209.85.128.172]:34616 "EHLO mail-wr0-f172.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933034AbdCUWRw (ORCPT ); Tue, 21 Mar 2017 18:17:52 -0400 MIME-Version: 1.0 In-Reply-To: <20170321193933.GB31111@cbox> References: <1489996534-8270-1-git-send-email-gengdongjiu@huawei.com> <7055772d-2a20-6e0c-2bf8-204bc9ef52a5@arm.com> <22fb583f-a33e-15f8-a059-fb112b27dd4f@arm.com> <58CFF058.8020205@arm.com> <76795e20-2f20-1e54-cfa5-7444f28b18ee@huawei.com> <20170321113428.GC15920@cbox> <58D17AF0.2010802@arm.com> <20170321193933.GB31111@cbox> From: Peter Maydell Date: Tue, 21 Mar 2017 22:10:41 +0000 Message-ID: Subject: Re: [PATCH] kvm: pass the virtual SEI syndrome to guest OS To: Christoffer Dall Cc: James Morse , kvm-devel , Marc Zyngier , Catalin Marinas , Will Deacon , lkml - Kernel Mailing List , gengdongjiu , wangxiongfeng2@huawei.com, wuquanming@huawei.com, huangshaoyu@huawei.com, arm-mail-list , Andre Przywara , "kvmarm@lists.cs.columbia.edu" Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 21 March 2017 at 19:39, Christoffer Dall wrote: > My confusion here comes from not thinking about QEMU or KVM as firmware, > but as the machine, so it would be sort of like the functionality is > baked into hardware rather than firmware. There is precedent for that kind of thing -- we implement PSCI in KVM/QEMU for the guest, though in real hardware it would be provided by firmware at EL3. thanks -- PMM From mboxrd@z Thu Jan 1 00:00:00 1970 From: Peter Maydell Subject: Re: [PATCH] kvm: pass the virtual SEI syndrome to guest OS Date: Tue, 21 Mar 2017 22:10:41 +0000 Message-ID: References: <1489996534-8270-1-git-send-email-gengdongjiu@huawei.com> <7055772d-2a20-6e0c-2bf8-204bc9ef52a5@arm.com> <22fb583f-a33e-15f8-a059-fb112b27dd4f@arm.com> <58CFF058.8020205@arm.com> <76795e20-2f20-1e54-cfa5-7444f28b18ee@huawei.com> <20170321113428.GC15920@cbox> <58D17AF0.2010802@arm.com> <20170321193933.GB31111@cbox> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: "kvmarm@lists.cs.columbia.edu" , wuquanming@huawei.com, kvm-devel , Marc Zyngier , Catalin Marinas , Will Deacon , lkml - Kernel Mailing List , gengdongjiu , Andre Przywara , huangshaoyu@huawei.com, wangxiongfeng2@huawei.com, arm-mail-list To: Christoffer Dall Return-path: In-Reply-To: <20170321193933.GB31111@cbox> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: kvmarm-bounces@lists.cs.columbia.edu Sender: kvmarm-bounces@lists.cs.columbia.edu List-Id: kvm.vger.kernel.org On 21 March 2017 at 19:39, Christoffer Dall wrote: > My confusion here comes from not thinking about QEMU or KVM as firmware, > but as the machine, so it would be sort of like the functionality is > baked into hardware rather than firmware. There is precedent for that kind of thing -- we implement PSCI in KVM/QEMU for the guest, though in real hardware it would be provided by firmware at EL3. thanks -- PMM From mboxrd@z Thu Jan 1 00:00:00 1970 From: peter.maydell@linaro.org (Peter Maydell) Date: Tue, 21 Mar 2017 22:10:41 +0000 Subject: [PATCH] kvm: pass the virtual SEI syndrome to guest OS In-Reply-To: <20170321193933.GB31111@cbox> References: <1489996534-8270-1-git-send-email-gengdongjiu@huawei.com> <7055772d-2a20-6e0c-2bf8-204bc9ef52a5@arm.com> <22fb583f-a33e-15f8-a059-fb112b27dd4f@arm.com> <58CFF058.8020205@arm.com> <76795e20-2f20-1e54-cfa5-7444f28b18ee@huawei.com> <20170321113428.GC15920@cbox> <58D17AF0.2010802@arm.com> <20170321193933.GB31111@cbox> Message-ID: To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On 21 March 2017 at 19:39, Christoffer Dall wrote: > My confusion here comes from not thinking about QEMU or KVM as firmware, > but as the machine, so it would be sort of like the functionality is > baked into hardware rather than firmware. There is precedent for that kind of thing -- we implement PSCI in KVM/QEMU for the guest, though in real hardware it would be provided by firmware at EL3. thanks -- PMM