On Fri, 07 Nov 2008 00:23:43 -0500 Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxx> wrote:
> 32 to 64 bits clock extension. Extracts 64 bits tsc from a [1..32]
> bits counter, kept up to date by periodical timer interrupt. Lockless.
>
> ...
>
> +#include <linux/sched.h> /* FIX for m68k local_irq_enable in on_each_cpu */
What's going on here?
> +struct synthetic_tsc_struct {
> + union {
> + u64 val;
> + struct {
> +#ifdef __BIG_ENDIAN
> + u32 msb;
> + u32 lsb;
> +#else
> + u32 lsb;
> + u32 msb;
> +#endif
One would expect an identifier called "msb" to mean "most significant
bit" or possible "most significant byte".
Maybe ms32 and ls32?
> + } sel;
> + } tsc[2];
> + unsigned int index; /* Index of the current synth. tsc. */
> +};
> +
> +static DEFINE_PER_CPU(struct synthetic_tsc_struct, synthetic_tsc);
> +
> +/* Called from IPI : either in interrupt or process context */
IPI handlers should always be called with local interrupts disabled.
> +static void update_synthetic_tsc(void)
> +{
> + struct synthetic_tsc_struct *cpu_synth;
> + u32 tsc;
> +
> + preempt_disable();
which would make this unnecessary.
> + cpu_synth = &per_cpu(synthetic_tsc, smp_processor_id());
> + tsc = trace_clock_read32(); /* Hardware clocksource read */
> +
> + if (tsc < HW_LSB(cpu_synth->tsc[cpu_synth->index].sel.lsb)) {
> + unsigned int new_index = 1 - cpu_synth->index; /* 0 <-> 1 */
> + /*
> + * Overflow
> + * Non atomic update of the non current synthetic TSC, followed
> + * by an atomic index change. There is no write concurrency,
> + * so the index read/write does not need to be atomic.
> + */
> + cpu_synth->tsc[new_index].val =
> + (SW_MSB(cpu_synth->tsc[cpu_synth->index].val)
> + | (u64)tsc) + (1ULL << HW_BITS);
> + cpu_synth->index = new_index; /* atomic change of index */
> + } else {
> + /*
> + * No overflow : We know that the only bits changed are
> + * contained in the 32 LSBs, which can be written to atomically.
> + */
> + cpu_synth->tsc[cpu_synth->index].sel.lsb =
> + SW_MSB(cpu_synth->tsc[cpu_synth->index].sel.lsb) | tsc;
> + }
> + preempt_enable();
> +}
Is there something we should be fixing in m68k?
--
To unsubscribe from this list: send the line "unsubscribe linux-arch" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
