On Mon, Nov 27, 2006 at 10:49:55AM -0800, David Miller ([email protected]) wrote:
> From: Ulrich Drepper <[email protected]>
> Date: Mon, 27 Nov 2006 10:36:06 -0800
> > David Miller wrote:
> > > Now we'll have to have a compat layer for 32-bit/64-bit environments
> > > thanks to POSIX timers, which is rediculious.
> > We already have compat_sys_timer_create. It should be sufficient just
> > to add the conversion (if anything new is needed) there. The pointer
> > value can be passed to userland in one or two int fields, I don't really
> > care. When reporting the event to the user code we cannot just point
> > into the ring buffer anyway. So while copying the data we can rewrite
> > it if necessary. I see no need to complicate the code more than it
> > already is.
> Ok, as long as that thing doesn't end up in the ring buffer entry
> data structure, that's where the real troubles would be.
Although ukevent has pointer embedded, it is unioned with u64, so there
should be no problems until 128 bit arch appeared, which likely will not
happen soon. There is also unused in kevent posix timers patch
'u32 ret_val' field, which can store segval's value too.
But the fact that ukevent does not and will not in any way have variable
size is absolutely.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Video 4 Linux]
[Linux for the blind]