From: Amitay Isaacs <amitay@ozlabs.org>
To: linux-kernel@vger.kernel.org, linux-fsi@lists.ozlabs.org,
jk@ozlabs.org, joel@jms.id.au, alistair@popple.id.au,
eajames@linux.ibm.com
Cc: Amitay Isaacs <amitay@ozlabs.org>
Subject: [PATCH v2 0/2] Enable read timeout specification for sbefifo read
Date: Thu, 16 Dec 2021 17:24:03 +1100 [thread overview]
Message-ID: <20211216062405.415888-1-amitay@ozlabs.org> (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 currentlly 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.
v2 changes:
- uint32 --> u32
- Avoid resetting the read timeout after single operation. Use ioctl
to set the read timeout per open fd for sbefifo device.
- Specifying 0 value to ioctl will reset the timeout to default value
- Document ioctl behaviour in uapi/linux/fsi.h
Amitay Isaacs (2):
fsi: sbefifo: Use specified value of start of response timeout
fsi: sbefifo: implement FSI_SBEFIFO_READ_TIMEOUT ioctl
drivers/fsi/fsi-sbefifo.c | 48 ++++++++++++++++++++++++++++++++++++++-
include/uapi/linux/fsi.h | 14 ++++++++++++
2 files changed, 61 insertions(+), 1 deletion(-)
--
2.33.1
next reply other threads:[~2021-12-16 6:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-16 6:24 Amitay Isaacs [this message]
2021-12-16 6:24 ` [PATCH v2 1/2] fsi: sbefifo: Use specified value of start of response timeout Amitay Isaacs
2021-12-16 6:24 ` [PATCH v2 2/2] fsi: sbefifo: implement FSI_SBEFIFO_READ_TIMEOUT ioctl Amitay Isaacs
2021-12-16 8:04 ` Greg KH
2022-01-13 6:04 ` Joel Stanley
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=20211216062405.415888-1-amitay@ozlabs.org \
--to=amitay@ozlabs.org \
--cc=alistair@popple.id.au \
--cc=eajames@linux.ibm.com \
--cc=jk@ozlabs.org \
--cc=joel@jms.id.au \
--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®