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

On Fri, Mar 10, 2006 at 10:34:53AM +1100, Paul Mackerras wrote:
> MMIO accesses are done under a spinlock, and that if your driver is
> missing them then that is a bug.  I don't think it makes sense to say
> that mmiowb is required "on some systems".

Agreed. But if it is missing it may not be a bug. It depends what the lock
actually protects.

-
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] Document Linux's memory barriers [try #4]
  - From: Paul Mackerras <[email protected]>

References:
- [PATCH] Document Linux's memory barriers [try #4]
  - From: David Howells <[email protected]>
- Re: [PATCH] Document Linux's memory barriers [try #4]
  - From: Paul Mackerras <[email protected]>

Prev by Date: Re: [PATCH 9 of 20] ipath - char devices for diagnostics and lightweight subnet management
Next by Date: Re: [PATCH] Document Linux's memory barriers
Previous by thread: Re: [PATCH] Document Linux's memory barriers [try #4]
Next by thread: Re: [PATCH] Document Linux's memory barriers [try #4]
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]