Re: [PATCH 1 of 3] Introduce __raw_memcpy_toio32

"Bryan O'Sullivan" <[email protected]> wrote:
>
> This arch-independent routine copies data to a memory-mapped I/O region,
>  using 32-bit accesses.  It does not guarantee access ordering, nor does
>  it perform a memory barrier afterwards.  This style of access is required
>  by some devices.

Not providing orderingor barriers makes this a rather risky thing to export
- people might use it, find their driver "works" on one architecture, but
fails on another.

I guess the "__" is a decent warning of this, and the patch anticipates a
higher-level raw_memcpy_toio32() which implements those things, yes?

How come __raw_memcpy_toio32() is inlined?
-
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 1 of 3] Introduce __raw_memcpy_toio32
    • From: "Bryan O'Sullivan" <[email protected]>
  • Re: [PATCH 1 of 3] Introduce __raw_memcpy_toio32
    • From: Roland Dreier <[email protected]>

• References:
  • [PATCH 0 of 3] 32-bit MMIO copy routine
    • From: "Bryan O'Sullivan" <[email protected]>
  • [PATCH 1 of 3] Introduce __raw_memcpy_toio32
    • From: "Bryan O'Sullivan" <[email protected]>

• Prev by Date: Re: Why the DOS has many ntfs read and write driver,but the linux can't for a long time
• Next by Date: Re: [OT] ALSA userspace API complexity
• Previous by thread: [PATCH 1 of 3] Introduce __raw_memcpy_toio32
• Next by thread: Re: [PATCH 1 of 3] Introduce __raw_memcpy_toio32
• 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]