From: Conor Dooley <conor@kernel.org>
To: Sebastian Ene <sebastianene@google.com>
Cc: arnd@arndb.de, gregkh@linuxfoundation.org, will@kernel.org,
maz@kernel.org, Rob Herring <robh+dt@kernel.org>,
Dragan Cvetic <dragan.cvetic@xilinx.com>,
Guenter Roeck <linux@roeck-us.net>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
kernel-team@android.com
Subject: Re: [PATCH 2/2] misc: Register a PPI for the vcpu stall detection virtual device
Date: Fri, 24 May 2024 20:00:42 +0100 [thread overview]
Message-ID: <20240524-joyous-fantastic-2747ab94e83d@spud> (raw)
In-Reply-To: <20240523160413.868830-3-sebastianene@google.com>
[-- Attachment #1: Type: text/plain, Size: 3691 bytes --]
On Thu, May 23, 2024 at 04:04:13PM +0000, Sebastian Ene wrote:
> Request a PPI for each vCPU during probe which will be used by the host
> to communicate a stall detected event on the vCPU. When the host raises
> this interrupt from the virtual machine monitor, the guest is expected to
> handle the interrupt and panic.
>
> Signed-off-by: Sebastian Ene <sebastianene@google.com>
> ---
> drivers/misc/vcpu_stall_detector.c | 41 ++++++++++++++++++++++++++++--
> 1 file changed, 39 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/misc/vcpu_stall_detector.c b/drivers/misc/vcpu_stall_detector.c
> index e2015c87f03f..c580cd7fd225 100644
> --- a/drivers/misc/vcpu_stall_detector.c
> +++ b/drivers/misc/vcpu_stall_detector.c
> @@ -32,6 +32,7 @@
> struct vcpu_stall_detect_config {
> u32 clock_freq_hz;
> u32 stall_timeout_sec;
> + int ppi_irq;
>
> void __iomem *membase;
> struct platform_device *dev;
> @@ -77,6 +78,12 @@ vcpu_stall_detect_timer_fn(struct hrtimer *hrtimer)
> return HRTIMER_RESTART;
> }
>
> +static irqreturn_t vcpu_stall_detector_irq(int irq, void *dev)
> +{
> + panic("vCPU stall detector");
> + return IRQ_HANDLED;
> +}
> +
> static int start_stall_detector_cpu(unsigned int cpu)
> {
> u32 ticks, ping_timeout_ms;
> @@ -132,7 +139,7 @@ static int stop_stall_detector_cpu(unsigned int cpu)
>
> static int vcpu_stall_detect_probe(struct platform_device *pdev)
> {
> - int ret;
> + int ret, irq, num_irqs;
> struct resource *r;
> void __iomem *membase;
> u32 clock_freq_hz = VCPU_STALL_DEFAULT_CLOCK_HZ;
> @@ -169,9 +176,32 @@ static int vcpu_stall_detect_probe(struct platform_device *pdev)
> vcpu_stall_config = (struct vcpu_stall_detect_config) {
> .membase = membase,
> .clock_freq_hz = clock_freq_hz,
> - .stall_timeout_sec = stall_timeout_sec
> + .stall_timeout_sec = stall_timeout_sec,
> + .ppi_irq = -1,
> };
>
> + num_irqs = platform_irq_count(pdev);
> + if (num_irqs < 0) {
> + dev_err(&pdev->dev, "Failed to get irqs\n");
platform_irq_count() either returns a number or EPROBE_DEFER, I don't
think emitting an error on deferred probe is the correct thing to do
here?
> + ret = num_irqs;
> + goto err;
> + } else if (num_irqs > 1) {
> + dev_err(&pdev->dev, "Multipple irqs detected\n");
Typo. I don't really see why you're going to this level of complexity
though, why aren't you just doing a single get_irq_optional()?
> + ret = -EINVAL;
> + goto err;
> + } else if (num_irqs == 1) {
> + irq = platform_get_irq(pdev, 0);
> + if ((irq > 0) && irq_is_percpu_devid(irq)) {
> + ret = request_percpu_irq(irq,
> + vcpu_stall_detector_irq,
> + "vcpu_stall_detector",
> + vcpu_stall_detectors);
> + if (!ret)
> + vcpu_stall_config.ppi_irq = irq;
> +
> + }
> + }
> +
> ret = cpuhp_setup_state(CPUHP_AP_ONLINE_DYN,
> "virt/vcpu_stall_detector:online",
> start_stall_detector_cpu,
> @@ -184,6 +214,9 @@ static int vcpu_stall_detect_probe(struct platform_device *pdev)
> vcpu_stall_config.hp_online = ret;
> return 0;
> err:
> + if (vcpu_stall_config.ppi_irq > 0)
> + free_percpu_irq(vcpu_stall_config.ppi_irq,
> + vcpu_stall_detectors);
> return ret;
> }
>
> @@ -193,6 +226,10 @@ static void vcpu_stall_detect_remove(struct platform_device *pdev)
>
> cpuhp_remove_state(vcpu_stall_config.hp_online);
>
> + if (vcpu_stall_config.ppi_irq > 0)
> + free_percpu_irq(vcpu_stall_config.ppi_irq,
> + vcpu_stall_detectors);
> +
> for_each_possible_cpu(cpu)
> stop_stall_detector_cpu(cpu);
> }
> --
> 2.45.1.288.g0e0cd299f1-goog
>
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2024-05-24 19:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-23 16:04 [PATCH 0/2] misc: vcpu_stall_detector: Add a PPI interrupt Sebastian Ene
2024-05-23 16:04 ` [PATCH 1/2] dt-bindings: vcpu_stall_detector: Add a PPI interrupt to the virtual device Sebastian Ene
2024-05-24 19:01 ` Conor Dooley
2024-05-23 16:04 ` [PATCH 2/2] misc: Register a PPI for the vcpu stall detection " Sebastian Ene
2024-05-24 19:00 ` Conor Dooley [this message]
2024-06-11 10:49 ` 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=20240524-joyous-fantastic-2747ab94e83d@spud \
--to=conor@kernel.org \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=dragan.cvetic@xilinx.com \
--cc=gregkh@linuxfoundation.org \
--cc=kernel-team@android.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=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