mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "David Hildenbrand (Arm)" <david@kernel.org>
To: "Thomas Weißschuh" <thomas.weissschuh@linutronix.de>
Cc: Lorenzo Stoakes <ljs@kernel.org>,
	David Laight <david.laight.linux@gmail.com>,
	Yury Norov <ynorov@nvidia.com>,
	Thorsten Blum <thorsten.blum@linux.dev>,
	Andrew Morton <akpm@linux-foundation.org>,
	"Liam R. Howlett" <liam@infradead.org>,
	Vlastimil Babka <vbabka@kernel.org>,
	Mike Rapoport <rppt@kernel.org>,
	Suren Baghdasaryan <surenb@google.com>,
	Michal Hocko <mhocko@suse.com>, Yury Norov <yury.norov@gmail.com>,
	Rasmus Villemoes <linux@rasmusvillemoes.dk>,
	Andy Shevchenko <andriy.shevchenko@intel.com>,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH 2/3] mm: add bytes_to_page_end() helper
Date: Mon, 18 May 2026 17:32:06 +0200	[thread overview]
Message-ID: <5e168a17-b395-4586-8b81-0a405560f8e5@kernel.org> (raw)
In-Reply-To: <20260518164802-2b27ec0f-2ee5-43d9-881a-cd41251c7371@linutronix.de>

On 5/18/26 16:52, Thomas Weißschuh wrote:
> On Mon, May 18, 2026 at 04:41:38PM +0200, David Hildenbrand (Arm) wrote:
>> On 5/18/26 16:29, Thomas Weißschuh wrote:
>>>
>>> The idea behind the vdso/ header namespace is that it can be used from
>>> vDSO userspace code. A weird middleground between linux/*.h and uapi/linux/*.h.
>>> Also in a compat vDSO anything depending on BITS_PER_LONG is wrong, and instead
>>> __BITS_PER_LONG needs to be used. A bunch of kconfig settings, like
>>> CONFIG_64BIT can also be off. Additionally internal kernel symbols are
>>> obviously not reachable from vDSO code.
>>>
>>> Regular kernel code should not use the vdso/ namespace but instead use the
>>> regular linux/ headers, which in turn include the corresponding vdso/ one.
>>
>> offset_in_page() is that trivial that I don't see how it shouldn't just go next
>> to PAGE_SIZE / PAGE_MASK, though?
> 
> Yes, IMO it could go into vdso/page.h. The related offset_in_folio() which is
> defined right next to offset_in_page() however can not go there, as folios do
> not exist in the vDSO userspace context.

yes, folio stuff should not go in there indeed.

> 
> Personally I don't care about where this goes and just wanted to clarify the
> background of the vDSO headers.

Yes, thanks!

-- 
Cheers,

David

  reply	other threads:[~2026-05-18 15:32 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-17 12:34 [PATCH 1/3] mm: move offset_in_page() to page_helpers.h Thorsten Blum
2026-05-17 12:34 ` [PATCH 2/3] mm: add bytes_to_page_end() helper Thorsten Blum
2026-05-17 15:28   ` Yury Norov
2026-05-18  6:48     ` Andy Shevchenko
2026-05-18 10:23       ` Lorenzo Stoakes
2026-05-18 11:53         ` William Kucharski
2026-05-18  9:09     ` David Laight
2026-05-18 10:24       ` Lorenzo Stoakes
2026-05-18 13:06         ` David Hildenbrand (Arm)
2026-05-18 13:15           ` Lorenzo Stoakes
2026-05-18 13:24             ` David Hildenbrand (Arm)
2026-05-18 13:38               ` Lorenzo Stoakes
2026-05-18 14:29             ` Thomas Weißschuh
2026-05-18 14:41               ` David Hildenbrand (Arm)
2026-05-18 14:52                 ` Thomas Weißschuh
2026-05-18 15:32                   ` David Hildenbrand (Arm) [this message]
2026-05-18  6:49   ` Andy Shevchenko
2026-05-18 10:24   ` Lorenzo Stoakes
2026-05-17 12:34 ` [PATCH 3/3] lib/bitmap: use " Thorsten Blum
2026-05-18 10:33   ` Lorenzo Stoakes
2026-05-18 15:29   ` Yury Norov
2026-05-18  6:51 ` [PATCH 1/3] mm: move offset_in_page() to page_helpers.h Andy Shevchenko
2026-05-18 10:02 ` Lorenzo Stoakes
2026-05-18 12:13   ` Thorsten Blum
2026-05-18 12:33     ` Lorenzo Stoakes
2026-05-18 13:36       ` Thorsten Blum
2026-05-18 14:03         ` Lorenzo Stoakes
2026-05-18 12:58     ` David Hildenbrand (Arm)

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=5e168a17-b395-4586-8b81-0a405560f8e5@kernel.org \
    --to=david@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=andriy.shevchenko@intel.com \
    --cc=david.laight.linux@gmail.com \
    --cc=liam@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux@rasmusvillemoes.dk \
    --cc=ljs@kernel.org \
    --cc=mhocko@suse.com \
    --cc=rppt@kernel.org \
    --cc=surenb@google.com \
    --cc=thomas.weissschuh@linutronix.de \
    --cc=thorsten.blum@linux.dev \
    --cc=vbabka@kernel.org \
    --cc=ynorov@nvidia.com \
    --cc=yury.norov@gmail.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

all inboxes | Powered by JetHome®