From: Rob Herring <robh@kernel.org>
To: Sebastian Ene <sebastianene@google.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Arnd Bergmann <arnd@arndb.de>,
Dragan Cvetic <dragan.cvetic@xilinx.com>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
maz@kernel.org, will@kernel.org, vdonnefort@google.com,
Guenter Roeck <linux@roeck-us.net>
Subject: Re: [PATCH v6 1/2] dt-bindings: vcpu_stall_detector: Add qemu,vcpu-stall-detector compatible
Date: Thu, 16 Jun 2022 09:30:17 -0600 [thread overview]
Message-ID: <20220616153017.GA3503416-robh@kernel.org> (raw)
In-Reply-To: <20220616092737.1713667-2-sebastianene@google.com>
On Thu, Jun 16, 2022 at 09:27:38AM +0000, Sebastian Ene wrote:
> The VCPU stall detection mechanism allows to configure the expiration
> duration and the internal counter clock frequency measured in Hz.
> Add these properties in the schema.
>
> While this is a memory mapped virtual device, it is expected to be loaded
> when the DT contains the compatible: "qemu,vcpu-stall-detector" node.
> In a protected VM we trust the generated DT nodes and we don't rely on
> the host to present the hardware peripherals.
>
> Signed-off-by: Sebastian Ene <sebastianene@google.com>
> ---
> .../bindings/misc/vcpu_stall_detector.yaml | 49 +++++++++++++++++++
qemu,vcpu-stall-detector.yaml
> 1 file changed, 49 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/misc/vcpu_stall_detector.yaml
>
> diff --git a/Documentation/devicetree/bindings/misc/vcpu_stall_detector.yaml b/Documentation/devicetree/bindings/misc/vcpu_stall_detector.yaml
> new file mode 100644
> index 000000000000..55323676194b
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/misc/vcpu_stall_detector.yaml
> @@ -0,0 +1,49 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/misc/vcpu_stall_detector.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: VCPU stall detector
> +
> +description: |
Don't need '|' if no formatting.
> + This binding describes a CPU stall detector mechanism for virtual cpus
s/cpus/CPUs/
> + which is accessed through MMIO.
> +
> +maintainers:
> + - Sebastian Ene <sebastianene@google.com>
> +
> +properties:
> + compatible:
> + enum:
> + - qemu,vcpu-stall-detector
> +
> + clock-frequency:
> + $ref: /schemas/types.yaml#/definitions/uint32
> + description: |
> + The internal clock of the stall detector peripheral measure in Hz used
> + to decrement its internal counter register on each tick.
> + Defaults to 10 if unset.
default: 10
> +
> + timeout-sec:
> + $ref: /schemas/types.yaml#/definitions/uint32
> + description: |
> + The stall detector expiration timeout measured in seconds.
> + Defaults to 8 if unset. Please note that it also takes into account the
> + time spent while the VCPU is not running.
default: 8
> +
> +required:
> + - compatible
> +
> +additionalProperties: false
> +
> +examples:
> + - |
> + vmwdt@9030000 {
> + compatible = "qemu,vcpu-stall-detector";
> + clock-frequency = <10>;
> + timeout-sec = <8>;
> + reg = <0x0 0x9030000 0x0 0x10000>;
> + };
> +
> +...
> --
> 2.36.1.476.g0c4daa206d-goog
>
>
next prev parent reply other threads:[~2022-06-16 15:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-16 9:27 [PATCH v6 0/2] Detect stalls on guest vCPUS Sebastian Ene
2022-06-16 9:27 ` [PATCH v6 1/2] dt-bindings: vcpu_stall_detector: Add qemu,vcpu-stall-detector compatible Sebastian Ene
2022-06-16 14:05 ` Rob Herring
2022-06-16 15:30 ` Rob Herring [this message]
2022-06-16 9:27 ` [PATCH v6 2/2] misc: Add a mechanism to detect stalls on guest vCPUs Sebastian Ene
2022-06-16 10:08 ` Greg Kroah-Hartman
2022-06-16 13:08 ` Guenter Roeck
2022-06-16 16:05 ` Sebastian Ene
2022-06-16 16:01 ` Sebastian Ene
2022-06-16 16:09 ` Guenter Roeck
2022-06-16 10:10 ` Greg Kroah-Hartman
2022-06-16 16:03 ` Sebastian Ene
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=20220616153017.GA3503416-robh@kernel.org \
--to=robh@kernel.org \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=dragan.cvetic@xilinx.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=maz@kernel.org \
--cc=sebastianene@google.com \
--cc=vdonnefort@google.com \
--cc=will@kernel.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).