From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Julien Grall <julien.grall@citrix.com>,
David Vrabel <david.vrabel@citrix.com>,
konrad.wilk@oracle.com
Cc: kevin.tian@intel.com, jbeulich@suse.com,
linux-kernel@vger.kernel.org, dietmar.hahn@ts.fujitsu.com,
xen-devel@lists.xen.org,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: [Xen-devel] [PATCH v5 0/6] xen/PMU: PMU support for Xen PV(H) guests
Date: Fri, 07 Aug 2015 12:06:18 -0400 [thread overview]
Message-ID: <55C4D77A.7010507@oracle.com> (raw)
In-Reply-To: <55C4D3AC.1060603@citrix.com>
On 08/07/2015 11:50 AM, Julien Grall wrote:
> Hi,
>
> On 07/08/15 16:35, David Vrabel wrote:
>> On 02/07/15 15:53, Boris Ostrovsky wrote:
>>> I haven't posted Linux part of PV(H) VPMU support in a while but now
>>> that (hopefully) the hypervisor part is getting close to be done I
>>> think it's time to post it again.
>>>
>>> There are very few differences compared to the last version, mostly due
>>> to updates in shared structures layouts. Patches 1 and 4 have no changes
>>> at all and patch 5 has minor changes due to rebasing so I kept David's
>>> Reviewed-by tag.
>> This breaks the arm and arm64 builds.
>>
>> In file included from
>> /local/davidvr/work/k.org/tip/drivers/xen/sys-hypervisor.c:23:0:
>> /local/davidvr/work/k.org/tip/include/xen/interface/xenpmu.h:91:22:
>> error: field ‘pmu’ has incomplete type
>> struct xen_pmu_arch pmu;
>> ^
>> /local/davidvr/work/k.org/tip/drivers/xen/sys-hypervisor.c: In function
>> ‘pmu_mode_store’:
>> /local/davidvr/work/k.org/tip/drivers/xen/sys-hypervisor.c:403:2: error:
>> implicit declaration of function ‘HYPERVISOR_xenpmu_op’
>> [-Werror=implicit-function-declaration]
>> ret = HYPERVISOR_xenpmu_op(XENPMU_mode_set, &xp);
>> ^
> There is no PMU support for the moment on ARM and this hypercall is only
> used for x86. I would introduce a new CONFIG (CONFIG_XEN_PMMU) which is
> enabled for x86 and disabled for ARM.
CONFIG_XEN_VPMU, but yes.
>
>> cc1: some warnings being treated as errors
>> /local/davidvr/work/k.org/tip/scripts/Makefile.build:258: recipe for
>> target 'drivers/xen/sys-hypervisor.o' failed
>> make[3]: *** [drivers/xen/sys-hypervisor.o] Error 1
>> make[3]: *** Waiting for unfinished jobs....
>> /local/davidvr/work/k.org/tip/drivers/xen/xenfs/xensyms.c: In function
>> ‘xensyms_next_sym’:
>> /local/davidvr/work/k.org/tip/drivers/xen/xenfs/xensyms.c:34:2: error:
>> implicit declaration of function ‘HYPERVISOR_dom0_op’
>> [-Werror=implicit-function-declaration]
>> ret = HYPERVISOR_dom0_op(&xs->op);
>> ^
> DOM0 op doesn't exists for ARM and xensyms is not even plumbed. I would
> make sure that XEN_SYMS is not enabled for ARM maybe adding the line
> below in the kconfig?
>
> depends on X86 && XEN_DOM0 && XENFS
Yes. Sorry for breakage. I usually build the hypervisor for ARM but
clearly didn't do this for Linux.
-boris
prev parent reply other threads:[~2015-08-07 16:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-02 14:53 [PATCH v5 0/6] xen/PMU: PMU support for Xen PV(H) guests Boris Ostrovsky
2015-07-02 14:53 ` [PATCH v5 1/6] xen: xensyms support Boris Ostrovsky
2015-07-02 14:53 ` [PATCH v5 2/6] xen/PMU: Sysfs interface for setting Xen PMU mode Boris Ostrovsky
2015-07-02 16:16 ` [Xen-devel] " David Vrabel
2015-07-02 14:53 ` [PATCH v5 3/6] xen/PMU: Initialization code for Xen PMU Boris Ostrovsky
2015-07-02 16:21 ` [Xen-devel] " David Vrabel
2015-07-02 17:14 ` Boris Ostrovsky
2015-07-02 14:53 ` [PATCH v5 4/6] xen/PMU: Describe vendor-specific PMU registers Boris Ostrovsky
2015-07-02 14:53 ` [PATCH v5 5/6] xen/PMU: Intercept PMU-related MSR and APIC accesses Boris Ostrovsky
2015-07-02 14:53 ` [PATCH v5 6/6] xen/PMU: PMU emulation code Boris Ostrovsky
2015-07-02 16:22 ` [Xen-devel] " David Vrabel
2015-07-02 16:25 ` [Xen-devel] [PATCH v5 0/6] xen/PMU: PMU support for Xen PV(H) guests David Vrabel
2015-07-02 17:18 ` Boris Ostrovsky
2015-08-07 15:35 ` David Vrabel
2015-08-07 15:50 ` Julien Grall
2015-08-07 16:06 ` Boris Ostrovsky [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=55C4D77A.7010507@oracle.com \
--to=boris.ostrovsky@oracle.com \
--cc=david.vrabel@citrix.com \
--cc=dietmar.hahn@ts.fujitsu.com \
--cc=jbeulich@suse.com \
--cc=julien.grall@citrix.com \
--cc=kevin.tian@intel.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.xen.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).