public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Adrian Bunk <bunk@kernel.org>
Cc: Andrew Morton <akpm@osdl.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	"H. Peter Anvin" <hpa@zytor.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	linux-kernel@vger.kernel.org
Subject: Re: x86: Why have __copy_from_user_ll_nocache* been exported?
Date: Thu, 31 Jan 2008 21:31:22 +0100	[thread overview]
Message-ID: <20080131203122.GA6457@elte.hu> (raw)
In-Reply-To: <20080131201430.GA9375@cs181133002.pp.htv.fi>


* Adrian Bunk <bunk@kernel.org> wrote:

> A commit that does nothing except for adding two unused 
> EXPORT_SYMBOL's.
> 
> Without any rationale why they should be exported.

the rationale is obvious: it's part of the standard uaccess 
functionality and while it's rarely used (in fact it's not used by any 
modular code right now) there's no reason not to export it alongside the 
other uaccess vectors. We can unexport it once we unexport all uses of 
the uaccess APIs. We could make it a _GPL export perhaps.

It's very annoying to driver writers when a small portion of a sensible 
API vector is not available symmetrically.

> And that from a person who on the other hand wants to introduce (and 
> tries to force on other people) deprecation periods for unused 
> EXPORT_SYMBOL's.

why does this bother you? The API makes total sense. This is a 
completely sensible API (with a full implementation) to use non-temporal 
copies. I mean, if this was some legacy API that nobody uses anymore i'd 
agree, but this is about the ability to access user-space memory via 
SSE2+ non-temporal stores.

	Ingo

  reply	other threads:[~2008-01-31 20:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-31 20:14 x86: Why have __copy_from_user_ll_nocache* been exported? Adrian Bunk
2008-01-31 20:31 ` Ingo Molnar [this message]
2008-02-01  9:50   ` Ingo Molnar
2008-01-31 21:05 ` Andrew Morton
2008-01-31 21:18   ` Ingo Molnar
2008-02-02 21:36   ` Adrian Bunk
2008-02-02 22:06     ` Andrew Morton
2008-02-04 19:58     ` Ingo Molnar
2008-02-10 22:16       ` Adrian Bunk

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=20080131203122.GA6457@elte.hu \
    --to=mingo@elte.hu \
    --cc=akpm@osdl.org \
    --cc=bunk@kernel.org \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.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