From: Matthew Barnes <matthew.barnes@cloud.com>
To: xen-devel@lists.xenproject.org
Cc: Matthew Barnes <matthew.barnes@cloud.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
George Dunlap <george.dunlap@citrix.com>,
Jan Beulich <jbeulich@suse.com>, Julien Grall <julien@xen.org>,
Stefano Stabellini <sstabellini@kernel.org>,
Anthony PERARD <anthony.perard@citrix.com>
Subject: [XEN PATCH v2 0/2] Enumerate all allocated evtchns in lsevtchn
Date: Mon, 29 Apr 2024 14:42:40 +0100 [thread overview]
Message-ID: <cover.1714148012.git.matthew.barnes@cloud.com> (raw)
Currently, lsevtchn aborts its event channel enumeration when it hits
its first hypercall error, namely:
* When an event channel doesn't exist at the specified port
* When the event channel is owned by Xen
This results in lsevtchn missing potential relevant event channels with
higher port numbers, since lsevtchn cannot determine the cause of
hypercall errors.
This patch adds error status indicators for the evtchn_status hypercall
for when no further event channels will be yielded for higher port
numbers, allowing lsevtchn to terminate when all event channels have
been enumerated over.
Matthew Barnes (2):
evtchn: Add error status indicators for evtchn_status hypercall
tools/lsevtchn: Use new status identifiers in loop
tools/xcutils/lsevtchn.c | 11 ++++++++++-
xen/common/event_channel.c | 12 +++++++++++-
xen/include/public/event_channel.h | 2 ++
3 files changed, 23 insertions(+), 2 deletions(-)
--
2.34.1
next reply other threads:[~2024-04-29 13:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-29 13:42 Matthew Barnes [this message]
2024-04-29 13:42 ` [XEN PATCH v2 1/2] evtchn: Add error status indicators for evtchn_status hypercall Matthew Barnes
2024-04-30 12:19 ` Jan Beulich
2024-04-29 13:42 ` [XEN PATCH v2 2/2] tools/lsevtchn: Use new status identifiers in loop Matthew Barnes
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=cover.1714148012.git.matthew.barnes@cloud.com \
--to=matthew.barnes@cloud.com \
--cc=andrew.cooper3@citrix.com \
--cc=anthony.perard@citrix.com \
--cc=george.dunlap@citrix.com \
--cc=jbeulich@suse.com \
--cc=julien@xen.org \
--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.