Re: [PATCH] mark read_crX() asm code as volatile

On Wednesday 03 October 2007 16:18, H. Peter Anvin wrote:
> Nick Piggin wrote:
> >> This should work because the result gets used before reading again:
> >>
> >> read_cr3(a);
> >> write_cr3(a | 1);
> >> read_cr3(a);
> >>
> >> But this might be reordered so that b gets read before the write:
> >>
> >> read_cr3(a);
> >> write_cr3(a | 1);
> >> read_cr3(b);
> >>
> >> ?
> >
> > I don't see how, as write_cr3 clobbers memory.
>
> Because read_cr3() doesn't depend on memory, and b could be stored in a
> register.

How does the compiler know it doesn't depend on memory?

How do you say it depends on memory? You really need something
as heavy as volatile?
-
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/

---

• Follow-Ups:
  • Re: [PATCH] mark read_crX() asm code as volatile
    • From: Andi Kleen <[email protected]>

• References:
  • [PATCH] mark read_crX() asm code as volatile
    • From: Kirill Korotaev <[email protected]>
  • Re: [PATCH] mark read_crX() asm code as volatile
    • From: Nick Piggin <[email protected]>
  • Re: [PATCH] mark read_crX() asm code as volatile
    • From: "H. Peter Anvin" <[email protected]>

• Prev by Date: Re: [patch] sched: fix sched-domains partitioning by cpusets
• Next by Date: [PATCH] task containersv11 add tasks file interface fix for cpusets
• Previous by thread: Re: [PATCH] mark read_crX() asm code as volatile
• Next by thread: Re: [PATCH] mark read_crX() asm code as volatile
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]