All of lore.kernel.org
 help / color / mirror / Atom feed
From: John David Anglin <dave.anglin@bell.net>
To: Jeroen Roovers <jer@gentoo.org>
Cc: linux-parisc@vger.kernel.org, Helge Deller <deller@gmx.de>
Subject: Re: systemd real-time signals choices clash with Linux/PARISC available SIGRT range, WAS: fanotify_mark()
Date: Tue, 27 Aug 2013 11:26:41 -0400	[thread overview]
Message-ID: <521CC531.6020106@bell.net> (raw)
In-Reply-To: <20130827164601.4accbbfb@marga.jer-c2.orkz.net>

On 8/27/2013 10:46 AM, Jeroen Roovers wrote:
> On Mon, 26 Aug 2013 18:37:54 -0400
> John David Anglin <dave.anglin@bell.net> wrote:
>
>> On 26-Aug-13, at 5:27 PM, Helge Deller wrote:
>>>> [1] Sneak preview: https://bugs.gentoo.org/show_bug.cgi?id=482214
>>> Did you already filed this signal-problem upstream as suggested in
>>> comment #3 (https://bugs.gentoo.org/show_bug.cgi?id=482214#c3)?
> Well, there are two ways to resolve this problem, and seeing who is
> developing systemd and seeing the generous way the "available" signal
> range is used, I'm pretty doubtful about changes there.
>
> As I said in comment #2, that range could be compacted (a lot) and then
> fit easily on any future platform. Since it was a design choice even
> reflected in man pages[1] ("[...], SIGRTMIN+29   Sets the log level to
> [...]"), I'm very afraid they will not change it easily.
>
>> I believe two of the signal numbers come from HP-UX.
> #define SIGXCPU         33
> #define SIGXFSZ         34
The signal numbers for these two signals come from HP-UX but the signals 
are used
by Linux, so I can't see how they can change.
> #define SIGSTKFLT       36
>
> According to [2], SIGSTKFLT isn't used.
This signal isn't used by HP-UX but it is used by Linux, so again this 
can't change.

Can we change _NSIG to 69 so there are 32 RT signals as on other arches?

>
> Do we still support HP-UX? I have never seen a binary for it I could
> try with, but then maybe I never went looking for one, either. :)
Doesn't really matter...
>
>
>       jer
>
>
> [1] http://www.freedesktop.org/software/systemd/man/systemd.html
> [2]
> http://h21007.www2.hp.com/portal/download/files/unprot/STK/Linux_STK/impacts/i60.html
> --
> To unsubscribe from this list: send the line "unsubscribe linux-parisc" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>
>


-- 
John David Anglin    dave.anglin@bell.net


  reply	other threads:[~2013-08-27 15:26 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-13 13:49 fanotify_mark() Jeroen Roovers
2013-08-13 21:29 ` fanotify_mark() Helge Deller
2013-08-13 22:54   ` fanotify_mark() Jeroen Roovers
2013-08-25 23:46     ` fanotify_mark() Jeroen Roovers
2013-08-26 21:27       ` fanotify_mark() Helge Deller
2013-08-26 22:37         ` fanotify_mark() John David Anglin
2013-08-27 14:46           ` systemd real-time signals choices clash with Linux/PARISC available SIGRT range, WAS: fanotify_mark() Jeroen Roovers
2013-08-27 15:26             ` John David Anglin [this message]
2013-08-27 15:52               ` John David Anglin
2013-09-18 18:40               ` Helge Deller
2013-09-18 18:58                 ` John David Anglin
2013-08-27 14:31         ` fanotify_mark() Jeroen Roovers

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=521CC531.6020106@bell.net \
    --to=dave.anglin@bell.net \
    --cc=deller@gmx.de \
    --cc=jer@gentoo.org \
    --cc=linux-parisc@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 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.