From: Michal Orzel <michal.orzel@arm.com>
To: xen-devel@lists.xenproject.org
Cc: "George Dunlap" <george.dunlap@citrix.com>,
"Nick Rosbrook" <rosbrookn@ainfosec.com>,
"Ian Jackson" <iwj@xenproject.org>, "Wei Liu" <wl@xen.org>,
"Andrew Cooper" <andrew.cooper3@citrix.com>,
"Jan Beulich" <jbeulich@suse.com>,
"Julien Grall" <julien@xen.org>,
"Stefano Stabellini" <sstabellini@kernel.org>,
"Anthony PERARD" <anthony.perard@citrix.com>,
"Juergen Gross" <jgross@suse.com>,
"Christian Lindig" <christian.lindig@citrix.com>,
"David Scott" <dave@recoil.org>,
"Volodymyr Babchuk" <Volodymyr_Babchuk@epam.com>,
"Roger Pau Monné" <roger.pau@citrix.com>,
bertrand.marquis@arm.com
Subject: [PATCH v2 0/3] Expose PMU to the guests
Date: Wed, 6 Oct 2021 12:58:24 +0200 [thread overview]
Message-ID: <20211006105827.15217-1-michal.orzel@arm.com> (raw)
This patch series is a rework of an already pushed patch
exposing PMU to the guests. In the second version the vpmu
parameter is common and prework in the form of reporting
availability of vPMU on the hardware is added.
The current status is that the PMU registers are not virtualized
and the physical registers are directly accessible when "vpmu"
parameter is enabled in the guest config file. There is no interrupt
support and Xen will not save/restore the register values on context
switches. This is to be done in the future.
Michal Orzel (3):
xen+tools: Introduce XEN_SYSCTL_PHYSCAP_vpmu
xen/arm: Check for PMU platform support
xen: Expose the PMU to the guests
docs/man/xl.cfg.5.pod.in | 17 ++++++++++
tools/golang/xenlight/helpers.gen.go | 8 +++++
tools/golang/xenlight/types.gen.go | 2 ++
tools/include/libxl.h | 12 +++++++
tools/libs/light/libxl.c | 1 +
tools/libs/light/libxl_create.c | 4 +++
tools/libs/light/libxl_types.idl | 3 ++
tools/ocaml/libs/xc/xenctrl.ml | 2 ++
tools/ocaml/libs/xc/xenctrl.mli | 2 ++
tools/xl/xl_info.c | 5 +--
tools/xl/xl_parse.c | 2 ++
xen/arch/arm/domain.c | 10 ++++--
xen/arch/arm/setup.c | 1 +
xen/arch/x86/domain.c | 6 ++++
xen/common/domain.c | 11 ++++++-
xen/common/sysctl.c | 3 ++
xen/include/asm-arm/cpufeature.h | 49 ++++++++++++++++++++++++++--
xen/include/asm-arm/domain.h | 1 +
xen/include/public/domctl.h | 5 ++-
xen/include/public/sysctl.h | 8 +++--
xen/include/xen/domain.h | 2 ++
21 files changed, 144 insertions(+), 10 deletions(-)
--
2.29.0
next reply other threads:[~2021-10-06 10:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-06 10:58 Michal Orzel [this message]
2021-10-06 10:58 ` [PATCH v2 1/3] xen+tools: Introduce XEN_SYSCTL_PHYSCAP_vpmu Michal Orzel
2021-10-07 4:45 ` Stefano Stabellini
2021-10-07 7:59 ` Jan Beulich
2021-10-07 8:02 ` Michal Orzel
2021-10-07 8:05 ` Jan Beulich
2021-10-06 10:58 ` [PATCH v2 2/3] xen/arm: Check for PMU platform support Michal Orzel
2021-10-07 4:42 ` Stefano Stabellini
2021-10-06 10:58 ` [PATCH v2 3/3] xen: Expose the PMU to the guests Michal Orzel
2021-10-06 12:31 ` Christian Lindig
2021-10-07 8:03 ` Jan Beulich
2021-10-07 8:21 ` Michal Orzel
2021-10-07 8:34 ` Jan Beulich
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=20211006105827.15217-1-michal.orzel@arm.com \
--to=michal.orzel@arm.com \
--cc=Volodymyr_Babchuk@epam.com \
--cc=andrew.cooper3@citrix.com \
--cc=anthony.perard@citrix.com \
--cc=bertrand.marquis@arm.com \
--cc=christian.lindig@citrix.com \
--cc=dave@recoil.org \
--cc=george.dunlap@citrix.com \
--cc=iwj@xenproject.org \
--cc=jbeulich@suse.com \
--cc=jgross@suse.com \
--cc=julien@xen.org \
--cc=roger.pau@citrix.com \
--cc=rosbrookn@ainfosec.com \
--cc=sstabellini@kernel.org \
--cc=wl@xen.org \
--cc=xen-devel@lists.xenproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.