public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: "Bryan O'Sullivan" <bos@pathscale.com>
Cc: Christoph Hellwig <hch@infradead.org>,
	Roland Dreier <rdreier@cisco.com>,
	sam@ravnborg.org, Andrew Morton <akpm@osdl.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1 of 3] Introduce __raw_memcpy_toio32
Date: Tue, 10 Jan 2006 17:51:31 +0000	[thread overview]
Message-ID: <20060110175131.GA5235@infradead.org> (raw)
In-Reply-To: <1136915386.6294.8.camel@serpentine.pathscale.com>

On Tue, Jan 10, 2006 at 09:49:46AM -0800, Bryan O'Sullivan wrote:
> On Tue, 2006-01-10 at 17:07 +0000, Christoph Hellwig wrote:
> 
> > Or add a CONFIG_GENERIC_MEMCPY_IO that's non-uservisible and just set
> > by all the architectures that don't provide their own version.
> 
> Here's another i386-only review patch that does essentially that.  It
> looks cleaner to me than my previous patch from this morning.
> (Copyrights and other arches omitted, for clarity.)
> 
> What do you think?
> 
> 	<b
> 
> diff -r 48616306e7bd lib/Makefile
> --- a/lib/Makefile	Tue Jan 10 10:41:42 2006 +0800
> +++ b/lib/Makefile	Tue Jan 10 09:32:53 2006 -0800
> @@ -21,6 +21,7 @@
>  lib-$(CONFIG_RWSEM_XCHGADD_ALGORITHM) += rwsem.o
>  lib-$(CONFIG_SEMAPHORE_SLEEPERS) += semaphore-sleepers.o
>  lib-$(CONFIG_GENERIC_FIND_NEXT_BIT) += find_next_bit.o
> +lib-$(CONFIG_GENERIC_RAW_MEMCPY_IO) += raw_memcpy_io.o
>  obj-$(CONFIG_LOCK_KERNEL) += kernel_lock.o
>  obj-$(CONFIG_DEBUG_PREEMPT) += smp_processor_id.o
>  
> --- /dev/null	Thu Jan  1 00:00:00 1970 +0000
> +++ b/include/asm-generic/raw_memcpy_io.h	Tue Jan 10 09:32:53 2006 -0800
> @@ -0,0 +1,16 @@
> +#ifndef _ASM_GENERIC_RAW_MEMCPY_IO_H
> +#define _ASM_GENERIC_RAW_MEMCPY_IO_H
> +
> +/*
> + * __raw_memcpy_toio32 - copy data to MMIO space, in 32-bit units
> + *
> + * Order of access is not guaranteed, nor is a memory barrier performed
> + * afterwards.  This is an arch-independent generic implementation.
> + *
> + * @to: destination, in MMIO space (must be 32-bit aligned)
> + * @from: source (must be 32-bit aligned)
> + * @count: number of 32-bit quantities to copy
> + */

This should be in the implementation file, not near the prototype.
And needs to start with /** to be valid kernel doc.

> +void __raw_memcpy_toio32(void __iomem *to, const void *from, size_t count);

and without that comment I'd suggest just adding this to every asm/io.h
instead of an asm-generic header for just one prototype.


  reply	other threads:[~2006-01-10 17:51 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-06 20:26 [PATCH 0 of 3] 32-bit MMIO copy routine Bryan O'Sullivan
2006-01-06 20:26 ` [PATCH 1 of 3] Introduce __raw_memcpy_toio32 Bryan O'Sullivan
2006-01-10  9:18   ` Andrew Morton
2006-01-10 14:55     ` Roland Dreier
2006-01-10 16:07       ` Bryan O'Sullivan
2006-01-10 16:56         ` [PATCH] [RFC] Generic 32-bit MMIO copy, out of line Bryan O'Sullivan
2006-01-10 17:07         ` [PATCH 1 of 3] Introduce __raw_memcpy_toio32 Christoph Hellwig
2006-01-10 17:13           ` Bryan O'Sullivan
2006-01-10 17:49           ` Bryan O'Sullivan
2006-01-10 17:51             ` Christoph Hellwig [this message]
2006-01-10 17:55               ` Bryan O'Sullivan
2006-01-10 22:05                 ` Andrew Morton
2006-01-10 22:29                   ` Bryan O'Sullivan
2006-01-10 23:32                     ` Andrew Morton
2006-01-11 17:20                       ` Bryan O'Sullivan
2006-01-11 17:22                         ` Sam Ravnborg
2006-01-11 17:30                           ` Andrew Morton
2006-01-11 17:43                             ` Bryan O'Sullivan
2006-01-11 18:49                               ` Roland Dreier
2006-01-11 18:57                                 ` Bryan O'Sullivan
2006-01-11 19:01                                   ` Roland Dreier
2006-01-11 19:08                                     ` Bryan O'Sullivan
2006-01-13 15:19                       ` Adrian Bunk
2006-01-10 18:02               ` Randy.Dunlap
2006-01-10 20:04         ` Sam Ravnborg
2006-01-10 15:59     ` Bryan O'Sullivan
2006-01-06 20:26 ` [PATCH 2 of 3] memcpy32 for x86_64 Bryan O'Sullivan
2006-01-06 20:26 ` [PATCH 3 of 3] Add __raw_memcpy_toio32 to each arch Bryan O'Sullivan
  -- strict thread matches above, loose matches on Subject: below --
2006-01-10 19:53 [PATCH 0 of 3] 32-bit MMIO copy routines, reworked Bryan O'Sullivan
2006-01-10 19:53 ` [PATCH 1 of 3] Introduce __raw_memcpy_toio32 Bryan O'Sullivan
2006-01-11 22:39 [PATCH 0 of 3] MMIO 32-bit copy routine, the final frontier Bryan O'Sullivan
2006-01-11 22:39 ` [PATCH 1 of 3] Introduce __raw_memcpy_toio32 Bryan O'Sullivan
2006-01-11 23:43   ` Andrew Morton
     [not found] <5s6p8-1O3-29@gated-at.bofh.it>
     [not found] ` <5s6p8-1O3-27@gated-at.bofh.it>
     [not found]   ` <5tnZx-1lb-17@gated-at.bofh.it>
     [not found]     ` <5tt8U-xV-5@gated-at.bofh.it>
     [not found]       ` <5tueu-2mb-9@gated-at.bofh.it>
     [not found]         ` <5tvaH-3MA-55@gated-at.bofh.it>
     [not found]           ` <5tvX6-4MO-13@gated-at.bofh.it>
     [not found]             ` <5tvX6-4MO-11@gated-at.bofh.it>
     [not found]               ` <5tvXa-4MO-23@gated-at.bofh.it>
     [not found]                 ` <5tzQR-2zH-11@gated-at.bofh.it>
2006-01-15 15:33                   ` Bodo Eggert

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20060110175131.GA5235@infradead.org \
    --to=hch@infradead.org \
    --cc=akpm@osdl.org \
    --cc=bos@pathscale.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdreier@cisco.com \
    --cc=sam@ravnborg.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox