All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Martin <Dave.Martin@arm.com>
To: "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>
Cc: Heinrich Schuchardt <xypron.glpk@gmx.de>,
	"Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>,
	linux-man@vger.kernel.org
Subject: Re: cacheflush.2
Date: Thu, 10 Dec 2020 18:17:28 +0000	[thread overview]
Message-ID: <20201210181726.GT6882@arm.com> (raw)
In-Reply-To: <ca265930-00d7-44f5-b2dd-535a5cf0310a@gmail.com>

On Wed, Dec 09, 2020 at 07:34:09PM +0100, Alejandro Colomar (man-pages) wrote:
> Hi Heinrich & Michael,
> 
> What about the following?:
> 
> [
> NOTES
>        GCC provides a similar function, which may be useful on  archi‐
>        tectures that lack this system call:
> 
>            void __builtin___clear_cache(void *begin, void *end);
> ]
> 
> Cheers,
> 
> Alex

Maybe we should discourage people from calling the cacheflush syscall?

I think that people shouldn't be using the syscall unless they really
need the finer grained control it provides, and are prepared to take a
hit to portability.

(On arches where userspace is allowed to do cache flushing directly,
__builtin___clear_cache() should transparently do the right thing, with
no syscall overhead -- if not, that's probably a bug in the toolchain or
compiler support library.)

[...]

Cheers
---Dave

  parent reply	other threads:[~2020-12-10 18:18 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-09 18:04 cacheflush.2 Heinrich Schuchardt
2020-12-09 18:34 ` cacheflush.2 Alejandro Colomar (man-pages)
2020-12-09 18:48   ` cacheflush.2 Heinrich Schuchardt
2020-12-09 19:15     ` cacheflush.2 Alejandro Colomar (man-pages)
2020-12-11 18:14       ` cacheflush.2 Alejandro Colomar (man-pages)
2020-12-14 21:13         ` cacheflush.2 Martin Sebor
2020-12-14 22:34           ` cacheflush.2 Alejandro Colomar (man-pages)
2020-12-18 10:42             ` Ping: cacheflush.2 Alejandro Colomar (man-pages)
2020-12-18 16:51               ` Martin Sebor
2020-12-19 14:04                 ` Alejandro Colomar (man-pages)
2020-12-10 18:17   ` Dave Martin [this message]
2020-12-10 19:20     ` cacheflush.2 Heinrich Schuchardt
2020-12-10 20:56       ` RFC v2: cacheflush.2 Alejandro Colomar (man-pages)
2020-12-11  8:15         ` Michael Kerrisk (man-pages)
2020-12-11 18:02           ` Alejandro Colomar (man-pages)
2020-12-11 18:22             ` RFC v3: " Alejandro Colomar (man-pages)
2020-12-11 18:26               ` RFC v4: " Alejandro Colomar (man-pages)
2020-12-14 11:43                 ` [PATCH v5] cacheflush.2: Document __builtin___clear_cache() as a more portable alternative Alejandro Colomar
2020-12-14 11:43                   ` Alejandro Colomar
2020-12-14 12:00                   ` Heinrich Schuchardt
2020-12-14 12:00                     ` Heinrich Schuchardt
2020-12-15 13:30                 ` [PATCH v6] " Alejandro Colomar
2020-12-15 13:30                   ` Alejandro Colomar
2020-12-20 15:35                   ` Ping: " Alejandro Colomar (man-pages)
2020-12-20 15:35                     ` Alejandro Colomar (man-pages)
2020-12-20 20:48                   ` Michael Kerrisk (man-pages)
2020-12-20 20:48                     ` Michael Kerrisk (man-pages)

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=20201210181726.GT6882@arm.com \
    --to=dave.martin@arm.com \
    --cc=alx.manpages@gmail.com \
    --cc=linux-man@vger.kernel.org \
    --cc=mtk.manpages@gmail.com \
    --cc=xypron.glpk@gmx.de \
    /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.