From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Jason Andryuk <jason.andryuk@amd.com>
Cc: xen-devel@lists.xenproject.org, Jiqian Chen <Jiqian.Chen@amd.com>,
Huang Rui <ray.huang@amd.com>,
Anthony PERARD <anthony.perard@vates.tech>,
Juergen Gross <jgross@suse.com>
Subject: Re: [PATCH 1/2] tools/ctrl: Silence missing GSI in xc_pcidev_get_gsi()
Date: Fri, 28 Feb 2025 15:02:05 +0100 [thread overview]
Message-ID: <Z8HB3bTQAhQrFhbp@macbook.local> (raw)
In-Reply-To: <20250226201022.42447-2-jason.andryuk@amd.com>
On Wed, Feb 26, 2025 at 03:10:21PM -0500, Jason Andryuk wrote:
> It is valid for a PCI device to not have a legacy IRQ. In that case, do
> not print an error to keep the lgs clean.
>
> This relies on pciback being updated to return -ENOENT for a missing
> GSI.
>
> Fixes: b93e5981d258 ("tools: Add new function to get gsi from dev")
> Signed-off-by: Jason Andryuk <jason.andryuk@amd.com>
> ---
> tools/libs/ctrl/xc_linux.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/tools/libs/ctrl/xc_linux.c b/tools/libs/ctrl/xc_linux.c
> index 92591e49a1..c18f09392f 100644
> --- a/tools/libs/ctrl/xc_linux.c
> +++ b/tools/libs/ctrl/xc_linux.c
> @@ -78,7 +78,8 @@ int xc_pcidev_get_gsi(xc_interface *xch, uint32_t sbdf)
> IOCTL_PRIVCMD_PCIDEV_GET_GSI, &dev_gsi);
>
> if (ret < 0) {
> - PERROR("Failed to get gsi from dev");
> + if (errno != ENOENT)
> + PERROR("Failed to get gsi from dev");
While here, could you maybe print the S:B:D:F as part of the error
message? (seeing as it's a function parameter).
Thanks, Roger.
next prev parent reply other threads:[~2025-02-28 14:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-26 20:10 [PATCH 0/2] tools: Fix PVH dom0 passthrough with legacy irq Jason Andryuk
2025-02-26 20:10 ` [PATCH 1/2] tools/ctrl: Silence missing GSI in xc_pcidev_get_gsi() Jason Andryuk
2025-02-28 13:59 ` Roger Pau Monné
2025-02-28 14:02 ` Roger Pau Monné [this message]
2025-02-26 20:10 ` [PATCH 2/2] tools/libxl: Skip missing PCI GSIs Jason Andryuk
2025-02-27 8:25 ` Jan Beulich
2025-02-27 15:24 ` Jason Andryuk
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=Z8HB3bTQAhQrFhbp@macbook.local \
--to=roger.pau@citrix.com \
--cc=Jiqian.Chen@amd.com \
--cc=anthony.perard@vates.tech \
--cc=jason.andryuk@amd.com \
--cc=jgross@suse.com \
--cc=ray.huang@amd.com \
--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.