public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Max Ramanouski <max8rr8@gmail.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: tip-bot2 for Max Ramanouski <tip-bot2@linutronix.de>,
	linux-tip-commits@vger.kernel.org, Christoph Hellwig <hch@lst.de>,
	Alistair Popple <apopple@nvidia.com>,
	x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [tip: x86/urgent] x86/ioremap: Use is_ioremap_addr() in iounmap()
Date: Thu, 22 Aug 2024 00:21:49 +0300	[thread overview]
Message-ID: <6013396.DvuYhMxLoT@max8rr8pad> (raw)
In-Reply-To: <875xrujkeu.ffs@tglx>

> Please do not top-post and trim your replies.

Sorry, got a bit distracted and forgot to remove the default gmail
reply text. Will try to be more careful in future with better email
client.

> Careful, this might end up with other issues vs. the kernel header
> inclusion hell.
> If i386 is the only one which does not have VMALLOC start in
> asm/pgtable.h, then curing this might be the easier fix, no?

I thought about that initially, but then found out that apparently
it is like that for a reason. In commit:

186525bd6b8 ("mm, x86/mm: Untangle address space layout definitions from basic pgtable type definitions")

VMALLOC_START definition was specifically moved out of pgtable
related headers. But for some reason only for 32 bit arch. Plus
I think asm/vmalloc.h is more semantically correct to get
VMALLOC_START. Although on most arches (everywhere except x86,
arm64, powerpc and riscv) asm/vmalloc.h is an empty header. And
on riscv it doesn't actually provide VMALLOC_START... Probably
that is worth a separate fix later.

Best regards,
Max




      reply	other threads:[~2024-08-21 21:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-15 20:56 [PATCH v3] x86/ioremap: Use is_ioremap_addr() in iounmap() Max Ramanouski
2024-08-15 22:55 ` Alistair Popple
2024-08-16  9:43 ` [tip: x86/urgent] " tip-bot2 for Max Ramanouski
2024-08-20 20:35   ` Thomas Gleixner
2024-08-21  8:35     ` Max R
2024-08-21  9:27       ` Thomas Gleixner
2024-08-21 21:21         ` Max Ramanouski [this message]

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=6013396.DvuYhMxLoT@max8rr8pad \
    --to=max8rr8@gmail.com \
    --cc=apopple@nvidia.com \
    --cc=hch@lst.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tip-commits@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=tip-bot2@linutronix.de \
    --cc=x86@kernel.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