All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: akpm@linux-foundation.org
Cc: mm-commits@vger.kernel.org, randy.dunlap@oracle.com,
	cooloney@kernel.org, davem@davemloft.net, dhowells@redhat.com,
	geert@linux-m68k.org, hpa@zytor.com, ink@jurassic.park.msu.ru,
	kyle@mcmartin.ca, lethal@linux-sh.org,
	linux-arch@vger.kernel.org, mingo@elte.hu, ralf@linux-mips.org,
	rth@twiddle.net, schwidefsky@de.ibm.com, starvik@axis.com,
	takata@linux-m32r.org, tglx@linutronix.de, tony.luck@intel.com,
	vapier@gentoo.org
Subject: Re: + kmap_types-make-most-arches-use-generic-header-file.patch added to -mm tree
Date: Thu, 28 May 2009 22:11:56 +0000	[thread overview]
Message-ID: <200905282211.58997.arnd@arndb.de> (raw)
In-Reply-To: <200905282131.n4SLV7rj025720@imap1.linux-foundation.org>

On Thursday 28 May 2009 21:31:06 akpm@linux-foundation.org wrote:
> 
> The patch titled
>      kmap_types: make most arches use generic header file
> has been added to the -mm tree.  Its filename is
>      kmap_types-make-most-arches-use-generic-header-file.patch

Thanks for adding it back.

> Move the KM_FENCE_ macro additions into asm-generic/kmap_types.h,
> controlled by __WITH_KM_FENCE from each arch's kmap_types.h file.

I completely missed this part of the patch before. Is this actually useful?
All architectures that define it (x86 with a twist, the check for X86_32 is
an artifact from the x86 arch merge) do

#ifdef CONFIG_DEBUG_HIGHMEM
#define  __WITH_KM_FENCE
#endif

However: alpha, ia64, m32r, parisc and sh don't even support CONFIG_HIGHMEM
and therefore also can't set CONFIG_DEBUG_HIGHMEM. Conversely, mn10300 and
sparc can set CONFIG_DEBUG_HIGHMEM but don't get the extra checking
from KM_FENCE without this.

It seems to me that it would be at least as correct but simpler to just
leave the check for CONFIG_DEBUG_HIGHMEM.
 
> Would be nice to be able to add custom KM_types per arch, but I don't yet
> see a nice, clean way to do that.

FWIW, the only types that are not in the generic file right now are

arm: KM_L2_CACHE
powerpc: KM_PPC_SYNC_ICACHE, KM_PPC_SYNC_PAGE
um: KM_UML_USERCOPY

We could easily add these as KM_SYNC_ICACHE, KM_SYNC_DCACHE and
KM_UML_USERCOPY in the generic file and get rid of all architecture
specific types here.

	Arnd <><

  reply	other threads:[~2009-05-28 22:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-28 21:31 + kmap_types-make-most-arches-use-generic-header-file.patch added to -mm tree akpm
2009-05-28 22:11 ` Arnd Bergmann [this message]
2009-05-28 22:54   ` Randy Dunlap
  -- strict thread matches above, loose matches on Subject: below --
2009-04-20 22:08 akpm
2009-04-20 22:08 akpm

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=200905282211.58997.arnd@arndb.de \
    --to=arnd@arndb.de \
    --cc=akpm@linux-foundation.org \
    --cc=cooloney@kernel.org \
    --cc=davem@davemloft.net \
    --cc=dhowells@redhat.com \
    --cc=geert@linux-m68k.org \
    --cc=hpa@zytor.com \
    --cc=ink@jurassic.park.msu.ru \
    --cc=kyle@mcmartin.ca \
    --cc=lethal@linux-sh.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=mm-commits@vger.kernel.org \
    --cc=ralf@linux-mips.org \
    --cc=randy.dunlap@oracle.com \
    --cc=rth@twiddle.net \
    --cc=schwidefsky@de.ibm.com \
    --cc=starvik@axis.com \
    --cc=takata@linux-m32r.org \
    --cc=tglx@linutronix.de \
    --cc=tony.luck@intel.com \
    --cc=vapier@gentoo.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.