From mboxrd@z Thu Jan 1 00:00:00 1970 From: wei@redhat.com (Wei Huang) Date: Thu, 17 Sep 2015 00:56:54 -0500 Subject: [PATCH v2 00/22] KVM: ARM64: Add guest PMU support In-Reply-To: <55FA1832.3040008@linaro.org> References: <1441961715-11688-1-git-send-email-zhaoshenglong@huawei.com> <55F9D9FC.6010905@redhat.com> <55FA1832.3040008@linaro.org> Message-ID: <55FA5626.7040105@redhat.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On 09/16/2015 08:32 PM, Shannon Zhao wrote: > Hi Wei, > > On 2015/9/17 5:07, Wei Huang wrote: >> I am testing this series. > Thanks for your time and help. > >> The first question is: do you plan to add ACPI >> support in QEMU? I saw "KVM_{SET/GET}_DEVICE_ATTR failed: Invalid argument" while using your QEMU tree (PMU_v2 branch). A quick debugging: (1) dmesg on host kernel didn't show any vPMU initialization errors. So I suspect the problem is related to QEMU. (2) Commit 58771bc2a78 worked fine. So probably the problem was introduced by new PMU code. Have you seen it before? Thanks, -Wei > To the completeness, this should be added. Maybe this could be added at > v3. But I have a look at the kernel PMU driver, it doesn't support > probing through ACPI, although there are some patches[1] out-of-tree. > >> My in-house kernel uses ACPI for device probing. I had >> to force "acpi=off" when I test this patch series. > Guest kernel only boots with ACPI when you add "acpi=force". No need to > add "acpi=off". > > Thanks, > > [1] http://marc.info/?l=linaro-acpi&m=137949337925645&w=2 > From mboxrd@z Thu Jan 1 00:00:00 1970 From: Wei Huang Subject: Re: [PATCH v2 00/22] KVM: ARM64: Add guest PMU support Date: Thu, 17 Sep 2015 00:56:54 -0500 Message-ID: <55FA5626.7040105@redhat.com> References: <1441961715-11688-1-git-send-email-zhaoshenglong@huawei.com> <55F9D9FC.6010905@redhat.com> <55FA1832.3040008@linaro.org> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <55FA1832.3040008@linaro.org> Sender: kvm-owner@vger.kernel.org To: Shannon Zhao , Shannon Zhao , kvmarm@lists.cs.columbia.edu Cc: linux-arm-kernel@lists.infradead.org, kvm@vger.kernel.org, marc.zyngier@arm.com, christoffer.dall@linaro.org, will.deacon@arm.com, alex.bennee@linaro.org, peter.huangpeng@huawei.com List-Id: kvmarm@lists.cs.columbia.edu On 09/16/2015 08:32 PM, Shannon Zhao wrote: > Hi Wei, > > On 2015/9/17 5:07, Wei Huang wrote: >> I am testing this series. > Thanks for your time and help. > >> The first question is: do you plan to add ACPI >> support in QEMU? I saw "KVM_{SET/GET}_DEVICE_ATTR failed: Invalid argument" while using your QEMU tree (PMU_v2 branch). A quick debugging: (1) dmesg on host kernel didn't show any vPMU initialization errors. So I suspect the problem is related to QEMU. (2) Commit 58771bc2a78 worked fine. So probably the problem was introduced by new PMU code. Have you seen it before? Thanks, -Wei > To the completeness, this should be added. Maybe this could be added at > v3. But I have a look at the kernel PMU driver, it doesn't support > probing through ACPI, although there are some patches[1] out-of-tree. > >> My in-house kernel uses ACPI for device probing. I had >> to force "acpi=off" when I test this patch series. > Guest kernel only boots with ACPI when you add "acpi=force". No need to > add "acpi=off". > > Thanks, > > [1] http://marc.info/?l=linaro-acpi&m=137949337925645&w=2 >