From: Joel Stanley <joel@jms.id.au>
To: Jeremy Kerr <jk@ozlabs.org>,
Alistar Popple <alistair@popple.id.au>,
Eddie James <eajames@linux.ibm.com>,
Amitay Isaacs <amitay@ozlabs.org>
Cc: linux-fsi@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: [PATCH v3 0/2] fsi: sbefifo: Add userspace timeout control
Date: Fri, 21 Jan 2022 16:08:14 +1030 [thread overview]
Message-ID: <20220121053816.82253-1-joel@jms.id.au> (raw)
Certain SBE operations (e.g. collecting trace information from processors)
can take long time (> 10 seconds) to finish before SBE can respond.
Such operations will currently timeout due to the default response
timeout of 10 seconds. This patchset allows users to set a longer timeout
using ioctl on the sbefifo device fd, before issuing SBE operations that
are likely to take longer.
The userspace that interacts with the sbefifo character device is
libpdbg. An example use of the ioctl is in this branch:
https://github.com/amitay/pdbg/commits/ioctl
v3:
Take over from Amitay
Clarify use case in commit message
Link to userspace implementation in cover letter
Amitay Isaacs (2):
fsi: sbefifo: Use specified value of start of response timeout
fsi: sbefifo: Implement FSI_SBEFIFO_READ_TIMEOUT_SECONDS ioctl
drivers/fsi/fsi-sbefifo.c | 53 ++++++++++++++++++++++++++++++++++++++-
include/uapi/linux/fsi.h | 14 +++++++++++
2 files changed, 66 insertions(+), 1 deletion(-)
--
2.34.1
next reply other threads:[~2022-01-21 5:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-21 5:38 Joel Stanley [this message]
2022-01-21 5:38 ` [PATCH v3 1/2] fsi: sbefifo: Use specified value of start of response timeout Joel Stanley
2022-01-24 14:17 ` Eddie James
2022-01-21 5:38 ` [PATCH v3 2/2] fsi: sbefifo: Implement FSI_SBEFIFO_READ_TIMEOUT_SECONDS ioctl Joel Stanley
2022-01-24 14:17 ` Eddie James
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=20220121053816.82253-1-joel@jms.id.au \
--to=joel@jms.id.au \
--cc=alistair@popple.id.au \
--cc=amitay@ozlabs.org \
--cc=eajames@linux.ibm.com \
--cc=jk@ozlabs.org \
--cc=linux-fsi@lists.ozlabs.org \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®