All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julien Grall <julien@xen.org>
To: John Ernberg <john.ernberg@actia.se>, Peng Fan <peng.fan@nxp.com>,
	Stefano Stabellini <sstabellini@kernel.org>,
	Bertrand Marquis <bertrand.marquis@arm.com>,
	Michal Orzel <michal.orzel@amd.com>,
	Volodymyr Babchuk <Volodymyr_Babchuk@epam.com>
Cc: Jonas Blixt <jonas.blixt@actia.se>,
	"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH 1/2] xen/arm: Add imx8q{m,x} platform glue
Date: Wed, 6 Mar 2024 23:07:40 +0000	[thread overview]
Message-ID: <ab61278a-f3f1-41de-a0b2-eca6f19be103@xen.org> (raw)
In-Reply-To: <911ec1bb-3733-4f37-839e-673a88e408ff@actia.se>

Hi John,

 > Ping on the watchdog discussion bits.

Sorry for the late reply.

On 06/03/2024 13:13, John Ernberg wrote:
> On 2/9/24 14:14, John Ernberg wrote:
>>
>>>     * IMX_SIP_TIMER_*:  This seems to be related to the watchdog.
>>> Shouldn't dom0 rely on the watchdog provided by Xen instead? So those
>>> call will be used by Xen.
>>
>> That is indeed a watchdog SIP, and also for setting the SoC internal RTC
>> if it is being used.
>>
>> I looked around if there was previous discussion and only really found [3].
>> Is the xen/xen/include/watchdog.h header meant to be for this kind of
>> watchdog support or is that more for the VM watchdog? Looking at the x86
>> ACPI NMI watchdog it seems like the former, but I have never worked with
>> x86 nor ACPI.

include/watchdog.h contains helper to configure the watchdog for Xen. We 
also have per-VM watchdog and this is configured by the hypercall 
SCHEDOP_watchdog.

>>
>> Currently forwarding it to Dom0 has not caused any watchdog resets with
>> our watchdog timeout settings, our specific Dom0 setup and VM count.

IIUC, the SMC API for the watchdog would be similar to the ACPI NMI 
watchdog. So I think it would make more sense if this is not exposed to 
dom0 (even if Xen is doing nothing with it).

Can you try to hide the SMCs and check if dom0 still behave properly?

Cheers,

-- 
Julien Grall


  reply	other threads:[~2024-03-06 23:08 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-31 11:50 [PATCH 0/2] Xen: ARM: Improved NXP iMX8 platform support John Ernberg
2024-01-31 11:50 ` [PATCH 2/2] xen/drivers: imx-lpuart: Add iMX8QXP compatible John Ernberg
2024-01-31 12:29   ` Julien Grall
2024-01-31 15:31     ` John Ernberg
2024-01-31 11:50 ` [PATCH 1/2] xen/arm: Add imx8q{m,x} platform glue John Ernberg
2024-01-31 12:22   ` Julien Grall
2024-01-31 15:32     ` John Ernberg
2024-02-01  4:10       ` Peng Fan
2024-02-01 16:15         ` John Ernberg
2024-02-01 12:20       ` Julien Grall
2024-02-01 16:17         ` John Ernberg
2024-02-02  9:19           ` Julien Grall
2024-02-02 22:09             ` Stefano Stabellini
2024-02-04  9:40             ` Peng Fan
2024-02-05 10:13               ` Julien Grall
2024-02-09 13:14                 ` John Ernberg
2024-03-06 13:13                   ` John Ernberg
2024-03-06 23:07                     ` Julien Grall [this message]
2024-03-08 13:40                       ` John Ernberg
2024-03-08 14:04                         ` Julien Grall
2024-03-11  8:39                           ` John Ernberg
2024-03-13 10:07                           ` Bertrand Marquis
2024-03-20 16:24                             ` John Ernberg
2024-03-20 17:40                               ` Julien Grall
2024-03-20 23:53                                 ` Stefano Stabellini
2024-03-21  1:09                                   ` Peng Fan
2024-03-21  7:41                                 ` Bertrand Marquis
2024-03-21 16:05                                   ` John Ernberg
2024-03-21 16:15                                     ` Bertrand Marquis
2024-03-25 12:18                                       ` John Ernberg
2024-03-26  8:07                                         ` Bertrand Marquis

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=ab61278a-f3f1-41de-a0b2-eca6f19be103@xen.org \
    --to=julien@xen.org \
    --cc=Volodymyr_Babchuk@epam.com \
    --cc=bertrand.marquis@arm.com \
    --cc=john.ernberg@actia.se \
    --cc=jonas.blixt@actia.se \
    --cc=michal.orzel@amd.com \
    --cc=peng.fan@nxp.com \
    --cc=sstabellini@kernel.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.