From: "Valdis Klētnieks" <valdis.kletnieks@vt.edu>
To: William Tambe <tambewilliam@gmail.com>
Cc: Kernel Newbies <kernelnewbies@kernelnewbies.org>
Subject: Re: When returning from schedule_tail() ...
Date: Wed, 15 Jul 2020 19:31:52 -0400 [thread overview]
Message-ID: <590787.1594855912@turing-police> (raw)
In-Reply-To: <CAF8i9mPzZjApVvfPohW5hu-eM0i+ZfNZx1dwXUkhLysSkOmMJA@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 388 bytes --]
On Wed, 15 Jul 2020 10:05:25 -0400, William Tambe said:
> When returning from schedule_tail(), is it still necessary to check
> for (_TIF_SIGPENDING | _TIF_NOTIFY_RESUME) before resuming task ?
Well.. since the semantics of signals are defined as being delivered
when a process returns from the kernel, how would you avoid checking
for a pending signal and still maintain the semantics?
[-- Attachment #1.2: Type: application/pgp-signature, Size: 832 bytes --]
[-- Attachment #2: Type: text/plain, Size: 170 bytes --]
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next prev parent reply other threads:[~2020-07-15 23:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-15 14:05 When returning from schedule_tail() William Tambe
2020-07-15 23:31 ` Valdis Klētnieks [this message]
2020-07-16 0:01 ` William Tambe
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=590787.1594855912@turing-police \
--to=valdis.kletnieks@vt.edu \
--cc=kernelnewbies@kernelnewbies.org \
--cc=tambewilliam@gmail.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;
as well as URLs for NNTP newsgroup(s).