From: Rob Herring <robh@kernel.org>
To: Sebastian Ene <sebastianene@google.com>
Cc: Guenter Roeck <linux@roeck-us.net>,
Rob Herring <robh+dt@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
devicetree@vger.kernel.org, maz@kernel.org,
vdonnefort@google.com,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
will@kernel.org, Dragan Cvetic <dragan.cvetic@xilinx.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v9 1/2] dt-bindings: vcpu_stall_detector: Add qemu,vcpu-stall-detector compatible
Date: Fri, 1 Jul 2022 15:01:18 -0600 [thread overview]
Message-ID: <20220701210118.GA1523163-robh@kernel.org> (raw)
In-Reply-To: <20220701144013.1085272-2-sebastianene@google.com>
On Fri, 01 Jul 2022 14:40:13 +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>
> ---
> .../misc/qemu,vcpu-stall-detector.yaml | 51 +++++++++++++++++++
> 1 file changed, 51 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/misc/qemu,vcpu-stall-detector.yaml
>
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2022-07-01 21:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-01 14:40 [PATCH v9 0/2] Detect stalls on guest vCPUS Sebastian Ene
2022-07-01 14:40 ` [PATCH v9 1/2] dt-bindings: vcpu_stall_detector: Add qemu,vcpu-stall-detector compatible Sebastian Ene
2022-07-01 21:01 ` Rob Herring [this message]
2022-07-01 14:40 ` [PATCH v9 2/2] misc: Add a mechanism to detect stalls on guest vCPUs Sebastian Ene
2022-07-01 14:52 ` Guenter Roeck
2022-07-06 15:21 ` Will Deacon
2022-07-06 15:50 ` Greg Kroah-Hartman
2022-07-06 16:10 ` Will Deacon
2022-07-06 17:35 ` Greg Kroah-Hartman
2022-07-07 13:17 ` 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=20220701210118.GA1523163-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=robh+dt@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 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.