From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: "James E.J. Bottomley" <jejb@linux.ibm.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
linux-scsi@vger.kernel.org
Subject: calling context of scsi_end_request() always hard IRQ or sometimes different?
Date: Fri, 6 May 2022 18:57:35 +0200 [thread overview]
Message-ID: <YnVTf+vkcLl2wZZE@zx2c4.com> (raw)
Hey James, Martin,
I'm in the process of fixing a few issues with the RNG and one thing
that surprised me is that scsi_end_request() appears to be called from
hard IRQ context rather than some worker or soft IRQ as I assumed it
would be. That's fine, and I can deal with it, but what I haven't yet
been able to figure out is whether it's _always_ called from hard IRQ,
or whether it's sometimes from hard IRQ and sometimes not, and so I
should handle both cases in the thing I'm working on?
And if the answer turns out to be, "I don't know; that's really
complicated and..." just say so, and I'll just try to work out the whole
function graph.
Jason
next reply other threads:[~2022-05-06 16:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-06 16:57 Jason A. Donenfeld [this message]
2022-05-06 18:19 ` calling context of scsi_end_request() always hard IRQ or sometimes different? James Bottomley
2022-05-06 19:22 ` Jason A. Donenfeld
2022-05-06 20:11 ` James Bottomley
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=YnVTf+vkcLl2wZZE@zx2c4.com \
--to=jason@zx2c4.com \
--cc=jejb@linux.ibm.com \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.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