From: Michal Simek <michal.simek@amd.com>
To: Radhey Shyam Pandey <radhey.shyam.pandey@amd.com>,
abhyuday.godhasara@xilinx.com
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, git@amd.com,
Tanmay Shah <tanmay.shah@xilinx.com>
Subject: Re: [PATCH] soc: xilinx: fix unhandled SGI warning message
Date: Wed, 15 Nov 2023 15:05:06 +0100 [thread overview]
Message-ID: <511b866a-b851-4019-aed4-2c11f24eece3@amd.com> (raw)
In-Reply-To: <1698431039-2734260-1-git-send-email-radhey.shyam.pandey@amd.com>
On 10/27/23 20:23, Radhey Shyam Pandey wrote:
> From: Tanmay Shah <tanmay.shah@xilinx.com>
>
> Xen broadcasts SGI to each VM when multiple VMs run on Xen hypervisor. In
> such case spurious SGI is expected if one event is registered by one VM and
> not registered by another VM. We let users know that Unhandled SGI is not
> error and expected if kernel is running on Xen hypervisor.
>
> Signed-off-by: Tanmay Shah <tanmay.shah@xilinx.com>
> Signed-off-by: Radhey Shyam Pandey <radhey.shyam.pandey@amd.com>
> ---
> drivers/soc/xilinx/xlnx_event_manager.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/soc/xilinx/xlnx_event_manager.c b/drivers/soc/xilinx/xlnx_event_manager.c
> index 86a048a10a13..6356b80ce57b 100644
> --- a/drivers/soc/xilinx/xlnx_event_manager.c
> +++ b/drivers/soc/xilinx/xlnx_event_manager.c
> @@ -477,7 +477,7 @@ static void xlnx_call_notify_cb_handler(const u32 *payload)
> }
> }
> if (!is_callback_found)
> - pr_warn("Didn't find any registered callback for 0x%x 0x%x\n",
> + pr_warn("Unhandled SGI node 0x%x event 0x%x. Expected with Xen hypervisor\n",
> payload[1], payload[2]);
> }
>
Applied.
M
prev parent reply other threads:[~2023-11-15 14:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-27 18:23 Radhey Shyam Pandey
2023-11-15 14:05 ` Michal Simek [this message]
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=511b866a-b851-4019-aed4-2c11f24eece3@amd.com \
--to=michal.simek@amd.com \
--cc=abhyuday.godhasara@xilinx.com \
--cc=git@amd.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=radhey.shyam.pandey@amd.com \
--cc=tanmay.shah@xilinx.com \
/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
all inboxes | Powered by JetHome®