From: Ingo Molnar <mingo@kernel.org>
To: Dave Hansen <dave.hansen@intel.com>
Cc: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
Jonathan Corbet <corbet@lwn.net>,
Andy Lutomirski <luto@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Ard Biesheuvel <ardb@kernel.org>,
Jan Kiszka <jan.kiszka@siemens.com>,
Kieran Bingham <kbingham@kernel.org>,
Michael Roth <michael.roth@amd.com>,
Rick Edgecombe <rick.p.edgecombe@intel.com>,
Brijesh Singh <brijesh.singh@amd.com>,
Sandipan Das <sandipan.das@amd.com>,
Juergen Gross <jgross@suse.com>,
Tom Lendacky <thomas.lendacky@amd.com>,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
linux-efi@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCHv3 2/4] x86/64/mm: Make SPARSEMEM_VMEMMAP the only memory model
Date: Fri, 16 May 2025 17:35:21 +0200 [thread overview]
Message-ID: <aCdbOeK3EkVUTGD2@gmail.com> (raw)
In-Reply-To: <a0ca765c-a506-4c1f-a38c-24a8074988df@intel.com>
* Dave Hansen <dave.hansen@intel.com> wrote:
> On 5/16/25 07:08, Ingo Molnar wrote:
> >> And is there any value to support !SPARSEMEM_VMEMMAP?
> > Not really IMHO:
> >
> > .config.opensuse.default: CONFIG_SPARSEMEM_VMEMMAP_ENABLE=y
> > .config.ubuntu.localinstall: CONFIG_SPARSEMEM_VMEMMAP_ENABLE=y
> > .config.fedora.generic: CONFIG_SPARSEMEM_VMEMMAP_ENABLE=y
> > .config.rhel.generic: CONFIG_SPARSEMEM_VMEMMAP_ENABLE=y
>
> I look at the distro configs all the time as well.
>
> But let's also not forget that none of these have lockdep turned on,
Not actually true, quite a few distro debug kernel packages have
lockdep on, and it's often enabled in internal QA rigs as well.
Not so SPARSEMEM_VMEMMAP...
> [...] and we don't want to toss out lockdep support on x86, for
> example. ;)
That's an apples to oranges comparison:
- SPARSEMEM_VMEMMAP is always enabled, in standard and debug kernels
as well.
- lockdep is disabled in standard kernels, enabled in debug kernels
and very much relied on.
Thanks,
Ingo
next prev parent reply other threads:[~2025-05-16 15:35 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-16 12:33 [PATCHv3 0/4] x86: Make 5-level paging support unconditional for x86-64 Kirill A. Shutemov
2025-05-16 12:33 ` [PATCHv3 1/4] x86/64/mm: Always use dynamic memory layout Kirill A. Shutemov
2025-05-16 13:44 ` [tip: x86/core] x86/mm/64: " tip-bot2 for Kirill A. Shutemov
2025-05-17 13:00 ` [tip: x86/merge] " tip-bot2 for Kirill A. Shutemov
2025-05-16 12:33 ` [PATCHv3 2/4] x86/64/mm: Make SPARSEMEM_VMEMMAP the only memory model Kirill A. Shutemov
2025-05-16 13:42 ` Dave Hansen
2025-05-16 13:45 ` Ingo Molnar
2025-05-16 14:59 ` Dave Hansen
2025-05-16 15:08 ` Dave Hansen
2025-05-16 14:01 ` Kirill A. Shutemov
2025-05-16 14:08 ` Ingo Molnar
2025-05-16 15:03 ` Dave Hansen
2025-05-16 15:35 ` Ingo Molnar [this message]
2025-05-16 15:46 ` Dave Hansen
2025-05-16 18:28 ` H. Peter Anvin
2025-05-16 15:01 ` Dave Hansen
2025-05-16 13:44 ` [tip: x86/core] x86/mm/64: " tip-bot2 for Kirill A. Shutemov
2025-05-17 13:00 ` [tip: x86/merge] " tip-bot2 for Kirill A. Shutemov
2025-05-16 12:33 ` [PATCHv3 3/4] x86/64/mm: Make 5-level paging support unconditional Kirill A. Shutemov
2025-05-17 13:00 ` [tip: x86/merge] x86/mm/64: " tip-bot2 for Kirill A. Shutemov
2025-05-16 12:33 ` [PATCHv3 4/4] x86/paravirt: Restrict PARAVIRT_XXL to 64-bit only Kirill A. Shutemov
2025-05-16 12:43 ` Jürgen Groß
2025-05-17 13:00 ` [tip: x86/merge] " tip-bot2 for Kirill A. Shutemov
2025-05-16 13:11 ` [PATCHv3 0/4] x86: Make 5-level paging support unconditional for x86-64 Ingo Molnar
2025-05-16 13:17 ` Kirill A. Shutemov
2025-05-17 9:59 ` Borislav Petkov
2025-06-24 8:23 ` [PATCHv2 0/3] " Khalid Ali
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=aCdbOeK3EkVUTGD2@gmail.com \
--to=mingo@kernel.org \
--cc=ardb@kernel.org \
--cc=bp@alien8.de \
--cc=brijesh.singh@amd.com \
--cc=corbet@lwn.net \
--cc=dave.hansen@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jan.kiszka@siemens.com \
--cc=jgross@suse.com \
--cc=kbingham@kernel.org \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=luto@kernel.org \
--cc=michael.roth@amd.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rick.p.edgecombe@intel.com \
--cc=sandipan.das@amd.com \
--cc=tglx@linutronix.de \
--cc=thomas.lendacky@amd.com \
--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 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.