Ok, fair enough. I was using the xtime lock to protect monotonic_base in
(updated in mark_offset()), but since that isn't obvious I should be
more explicit and use a different lock.
> Also doing seqlocks around hardware register reads is quite nasty,
> because a hardware register read can be hundreds of cycles and you're
> very likely to get retries. If you really need a seqlock I would
> move it into the low level function and do it after the hardware access.
> But as far as I can see it can be just removed.
I should be able to use a regular rwlock w/o troubles. I change that and
thanks for the feedback!
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/