public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Marc Zyngier <maz@kernel.org>
Cc: Sebastian Ene <sebastianene@google.com>,
	Rob Herring <robh+dt@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
	Dragan Cvetic <dragan.cvetic@xilinx.com>,
	linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
	will@kernel.org, vdonnefort@google.com,
	Guenter Roeck <linux@roeck-us.net>
Subject: Re: [PATCH v7 2/2] misc: Add a mechanism to detect stalls on guest vCPUs
Date: Tue, 21 Jun 2022 10:54:35 +0200	[thread overview]
Message-ID: <YrGHS48LR759stoL@kroah.com> (raw)
In-Reply-To: <6b5bb5e69888f69fcfdcb8c9c2fd2660@kernel.org>

On Tue, Jun 21, 2022 at 09:44:35AM +0100, Marc Zyngier wrote:
> On 2022-06-21 09:27, Greg Kroah-Hartman wrote:
> > On Tue, Jun 21, 2022 at 08:03:09AM +0000, Sebastian Ene wrote:
> > > This driver creates per-cpu hrtimers which are required to do the
> > > periodic 'pet' operation. On a conventional watchdog-core driver, the
> > > userspace is responsible for delivering the 'pet' events by writing to
> > > the particular /dev/watchdogN node. In this case we require a strong
> > > thread affinity to be able to account for lost time on a per vCPU.
> > > 
> > > This part of the driver is the 'frontend' which is reponsible for
> > > delivering the periodic 'pet' events, configuring the virtual
> > > peripheral
> > > and listening for cpu hotplug events. The other part of the driver
> > > handles the peripheral emulation and this part accounts for lost
> > > time by
> > > looking at the /proc/{}/task/{}/stat entries and is located here:
> > > https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/3548817
> > > 
> > > Signed-off-by: Sebastian Ene <sebastianene@google.com>
> > > ---
> > >  drivers/misc/Kconfig               |  12 ++
> > >  drivers/misc/Makefile              |   1 +
> > >  drivers/misc/vcpu_stall_detector.c | 222
> > > +++++++++++++++++++++++++++++
> > >  3 files changed, 235 insertions(+)
> > >  create mode 100644 drivers/misc/vcpu_stall_detector.c
> > > 
> > > diff --git a/drivers/misc/Kconfig b/drivers/misc/Kconfig
> > > index 41d2bb0ae23a..e15c85d74c4b 100644
> > > --- a/drivers/misc/Kconfig
> > > +++ b/drivers/misc/Kconfig
> > > @@ -483,6 +483,18 @@ config OPEN_DICE
> > > 
> > >  	  If unsure, say N.
> > > 
> > > +config VCPU_STALL_DETECTOR
> > > +	tristate "VCPU stall detector"
> > > +	select LOCKUP_DETECTOR
> > > +	help
> > > +	  Detect CPU locks on a kvm virtual machine. This driver relies on
> > > +	  the hrtimers which are CPU-binded to do the 'pet' operation.
> > > When a
> > > +	  vCPU has to do a 'pet', it exits the guest through MMIO write and
> > > +	  the backend driver takes into account the lost ticks for this
> > > +	  particular CPU.
> > > +	  To compile this driver as a module, choose M here: the
> > > +	  module will be called vcpu_stall_detector.
> > 
> > Should this depend on KVM_GUEST?
> 
> Not all architectures have KVM_GUEST, and arm64 has no use for it.

Ah, I thought this was a requirement (or created a better guest image)
for use under KVM.  Nevermind then...

thanks,

greg k-h

  reply	other threads:[~2022-06-21  8:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-21  8:03 [PATCH v7 0/2] Detect stalls on guest vCPUS Sebastian Ene
2022-06-21  8:03 ` [PATCH v7 1/2] dt-bindings: vcpu_stall_detector: Add qemu,vcpu-stall-detector compatible Sebastian Ene
2022-06-24 17:26   ` Rob Herring
2022-06-21  8:03 ` [PATCH v7 2/2] misc: Add a mechanism to detect stalls on guest vCPUs Sebastian Ene
2022-06-21  8:27   ` Greg Kroah-Hartman
2022-06-21  8:44     ` Marc Zyngier
2022-06-21  8:54       ` Greg Kroah-Hartman [this message]
2022-06-21  9:24         ` Marc Zyngier

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=YrGHS48LR759stoL@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=arnd@arndb.de \
    --cc=devicetree@vger.kernel.org \
    --cc=dragan.cvetic@xilinx.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox