From: george anzinger <george@mvista.com>
To: Andi Kleen <ak@suse.de>
Cc: Jim Houston <jim.houston@attbi.com>, linux-kernel@vger.kernel.org
Subject: Re: POSIX clocks & timers - more choices
Date: Fri, 18 Oct 2002 23:59:08 -0700 [thread overview]
Message-ID: <3DB102BC.F181BC1F@mvista.com> (raw)
In-Reply-To: p73r8ennltj.fsf@oldwotan.suse.de
Andi Kleen wrote:
~snip~
Since he picked this up from my code...
>
> > +/*
> > + * For some reason mips/mips64 define the SIGEV constants plus 128.
> > + * Here we define a mask to get rid of the common bits. The
> > + * optimizer should make this costless to all but mips.
> > + */
> > +#if (ARCH == mips) || (ARCH == mips64)
> > +#define MIPS_SIGEV ~(SIGEV_NONE & \
> > + SIGEV_SIGNAL & \
> > + SIGEV_THREAD & \
> > + SIGEV_THREAD_ID)
> > +#else
> > +#define MIPS_SIGEV (int)-1
> > +#endif
>
> This definitely needs to be cleaned up.
>
What do you suggest? Changing mips? I would like this
number to go away also, but with the mips assignments it is
a bit of a bother.
--
George Anzinger george@mvista.com
High-res-timers:
http://sourceforge.net/projects/high-res-timers/
Preemption patch:
http://www.kernel.org/pub/linux/kernel/people/rml
next prev parent reply other threads:[~2002-10-19 6:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200210190252.g9J2quf16153@linux.local.suse.lists.linux.kernel>
2002-10-19 3:34 ` POSIX clocks & timers - more choices Andi Kleen
2002-10-19 6:40 ` Jim Houston
2002-10-20 3:49 ` Andi Kleen
2002-10-19 6:59 ` george anzinger [this message]
2002-10-20 3:50 ` Andi Kleen
2002-10-20 5:40 Jim Houston
-- strict thread matches above, loose matches on Subject: below --
2002-10-19 2:52 Jim Houston
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=3DB102BC.F181BC1F@mvista.com \
--to=george@mvista.com \
--cc=ak@suse.de \
--cc=jim.houston@attbi.com \
--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 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.