All of lore.kernel.org
 help / color / mirror / Atom feed
From: george anzinger <george@mvista.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: torvalds@transmeta.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH ] POSIX clocks & timers take 3 (NOT HIGH RES)
Date: Sun, 20 Oct 2002 13:14:40 -0700	[thread overview]
Message-ID: <3DB30EB0.EB5C91B1@mvista.com> (raw)
In-Reply-To: 20021021015050.21dbd4d9.sfr@canb.auug.org.au

Stephen Rothwell wrote:
> 
> Hi George,
> 
> On Thu, 17 Oct 2002 16:10:26 -0700 george anzinger <george@mvista.com> wrote:
> >
> > +++ linux/include/asm-generic/siginfo.h       Thu Oct 17 15:33:39 2002
> > @@ -43,8 +43,9 @@
> >
> >               /* POSIX.1b timers */
> >               struct {
> > -                     unsigned int _timer1;
> > -                     unsigned int _timer2;
> > +                     timer_t _tid;           /* timer id */
> > +                     int _overrun;           /* overrun count */
> > +                     sigval_t _sigval;       /* same as below */
> >               } _timer;
> 
> This, of course, will only work on architectures where (sizeof(timer_t) +
> sizeof(int) + alignment padding for sigval_t) is the same as
> (sizeof(pid_t) + sizeof(uid_t) + alignment padding for sigval_t). Which is
> true as far as I can see, but is fragile.  It might be worth a comment.

Hm..., yes, but I would rather express such things as
something that will cause the compiler to complain (i.e.
stop, not just warn).  Possibly something like:

static int
dummy[sizeof(timer_t)+sizeof(int)-sizeof(pid_t)-sizeof(uid_t)];
static int
dummy2[sizeof(pid_t)+sizeof(uid_t)-sizeof(timer_t)-sizeof(int)-];

It is UGLY, but it does cause the right thing (i.e. a
failure) to happen when things are wrong.

Or we could do the same sort of thing on the offset of
_sigval in the several unions, which is what we really care
about.

Thanks for the comments.

> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

-- 
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

      reply	other threads:[~2002-10-20 20:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-17 23:10 [PATCH ] POSIX clocks & timers take 3 (NOT HIGH RES) george anzinger
2002-10-20 15:50 ` Stephen Rothwell
2002-10-20 20:14   ` george anzinger [this message]

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=3DB30EB0.EB5C91B1@mvista.com \
    --to=george@mvista.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=torvalds@transmeta.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 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.