From: "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>
To: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>,
Heinrich Schuchardt <xypron.glpk@gmx.de>,
Dave Martin <Dave.Martin@arm.com>
Cc: linux-man@vger.kernel.org, gcc@gcc.gnu.org, cfe-users@lists.llvm.org
Subject: Re: RFC v2: Re: cacheflush.2
Date: Fri, 11 Dec 2020 19:02:19 +0100 [thread overview]
Message-ID: <de79c8a0-2839-da8e-a4cf-380fff30852d@gmail.com> (raw)
In-Reply-To: <e9d397d4-9eb4-bd49-0001-36fb45d0778a@gmail.com>
Hi Michael,
On 12/11/20 9:15 AM, Michael Kerrisk (man-pages) wrote:
> i Alex,
>
> On 12/10/20 9:56 PM, Alejandro Colomar (man-pages) wrote:
>> Hi all,
>>
>> v2:
>>
>> [
>> NOTES
>> Unless you need the finer grained control that this system
>> call provides, you probably want to use the GCC built-in
>> function __builtin___clear_cache(), which provides a more
>> portable interface:
>>
>> void __builtin___clear_cache(void *begin, void *end);
>> ]
>
> This seems a reasonable text to me, but I think it would be helpful
> to say a little more precisely what kind of portability we are
> talking about here.
Sure.
>
> Greater ortability across Linux architectures? Greater portability
> across platforms supported by GCC (including non-Linux) platforms?
> Something else?
'... which provides a portable interface across platforms supported by
GCC:' sounds good.
Maybe GCC devs have something more to add.
Thanks,
Alex
>
> Thanks,
>
> Michael
>
>
--
Alejandro Colomar
Linux man-pages comaintainer; https://www.kernel.org/doc/man-pages/
http://www.alejandro-colomar.es
next prev parent reply other threads:[~2020-12-11 19:39 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 ` cacheflush.2 Dave Martin
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) [this message]
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=de79c8a0-2839-da8e-a4cf-380fff30852d@gmail.com \
--to=alx.manpages@gmail.com \
--cc=Dave.Martin@arm.com \
--cc=cfe-users@lists.llvm.org \
--cc=gcc@gcc.gnu.org \
--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.