Re: [PATCH] Document Linux's memory barriers [try #2]

Jesse Barnes writes:

> Hm, a static checker should be able to find this stuff, shouldn't it?

Good idea.  I wonder if sparse could be extended to do it.

Alternatively, it wouldn't be hard to check dynamically.  Just have a
per-cpu count of outstanding MMIO stores.  Zero it in spin_lock and
mmiowb, increment it in write*, and grizzle if spin_unlock finds it
non-zero.  Should be very little overhead.

Paul.
-
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/

---

• References:
  • Re: [PATCH] Document Linux's memory barriers [try #2]
    • From: Linus Torvalds <[email protected]>
  • Re: [PATCH] Document Linux's memory barriers [try #2]
    • From: Linus Torvalds <[email protected]>
  • Re: [PATCH] Document Linux's memory barriers [try #2]
    • From: Paul Mackerras <[email protected]>
  • Re: [PATCH] Document Linux's memory barriers [try #2]
    • From: Jesse Barnes <[email protected]>

• Prev by Date: Re: [Ocfs2-devel] Ocfs2 performance bugs of doom
• Next by Date: Re: [Ocfs2-devel] Ocfs2 performance bugs of doom
• Previous by thread: Re: [PATCH] Document Linux's memory barriers [try #2]
• Next by thread: Re: [PATCH] Document Linux's memory barriers [try #2]
• 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]