From: David Hildenbrand <david@redhat.com>
To: Ryan Roberts <ryan.roberts@arm.com>,
Andrew Morton <akpm@linux-foundation.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
John Hubbard <jhubbard@nvidia.com>
Cc: linux-arm-kernel@lists.infradead.org, linux-mm@kvack.org
Subject: Re: [PATCH 1/2] arm64/mm: Export contpte symbols only to GPL users
Date: Mon, 26 Feb 2024 13:25:34 +0100 [thread overview]
Message-ID: <c9f00402-bb95-4fcf-a309-c36a5e68ec93@redhat.com> (raw)
In-Reply-To: <20240226120321.1055731-2-ryan.roberts@arm.com>
On 26.02.24 13:03, Ryan Roberts wrote:
> The contpte symbols must be exported since some of the public inline
> ptep_* APIs are called from modules and these inlines now call the
> contpte functions. Originally they were exported as EXPORT_SYMBOL() for
> fear of breaking out-of-tree modules. But we subsequently concluded that
> EXPORT_SYMBOL_GPL() should be safe since these functions are deeply core
> mm routines, and any module operating at this level is not going to be
> able to survive on EXPORT_SYMBOL alone.
>
I only looked at __set_ptes() to get a feeling what would currently work.
__set_ptes() might already call __sync_icache_dcache() via
__sync_cache_and_tags(), that is EXPORT_SYMBOL_GPL.
[mte_sync_tags() is not exported at all, so maybe it's safe to assume
that some out-of-tree module could not make good use of set_pte_at() in
general]
Acked-by: David Hildenbrand <david@redhat.com>
--
Cheers,
David / dhildenb
next prev parent reply other threads:[~2024-02-26 12:25 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-26 12:03 [PATCH 0/2] Address some contpte nits Ryan Roberts
2024-02-26 12:03 ` [PATCH 1/2] arm64/mm: Export contpte symbols only to GPL users Ryan Roberts
2024-02-26 12:25 ` David Hildenbrand [this message]
2024-02-26 12:40 ` Ryan Roberts
2024-02-27 2:49 ` John Hubbard
2024-03-04 17:38 ` Catalin Marinas
2024-02-26 12:03 ` [PATCH 2/2] arm64/mm: Improve comment in contpte_ptep_get_lockless() Ryan Roberts
2024-02-26 12:30 ` David Hildenbrand
2024-02-26 12:37 ` Ryan Roberts
2024-02-26 12:40 ` David Hildenbrand
2024-02-27 23:45 ` John Hubbard
2024-03-01 18:47 ` Catalin Marinas
2024-03-04 12:54 ` Ryan Roberts
2024-03-04 17:37 ` Catalin Marinas
2024-03-04 18:40 ` Ryan Roberts
2024-03-04 22:04 ` David Hildenbrand
2024-03-05 9:13 ` Ryan Roberts
2024-03-05 9:14 ` Ryan Roberts
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=c9f00402-bb95-4fcf-a309-c36a5e68ec93@redhat.com \
--to=david@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=catalin.marinas@arm.com \
--cc=jhubbard@nvidia.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mm@kvack.org \
--cc=mark.rutland@arm.com \
--cc=ryan.roberts@arm.com \
/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