From: Thomas Gleixner <tglx@linutronix.de>
To: Hou Wenlong <houwenlong.hwl@antgroup.com>, linux-kernel@vger.kernel.org
Cc: Lai Jiangshan <jiangshan.ljs@antgroup.com>,
Hou Wenlong <houwenlong.hwl@antgroup.com>,
Alexey Makhalov <amakhalov@vmware.com>,
Andrew Morton <akpm@linux-foundation.org>,
Andy Lutomirski <luto@kernel.org>,
Anshuman Khandual <anshuman.khandual@arm.com>,
Borislav Petkov <bp@alien8.de>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
Brian Gerst <brgerst@gmail.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
David Woodhouse <dwmw@amazon.co.uk>,
"H. Peter Anvin" <hpa@zytor.com>, Ingo Molnar <mingo@redhat.com>,
Josh Poimboeuf <jpoimboe@kernel.org>,
Juergen Gross <jgross@suse.com>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
"Mike Rapoport (IBM)" <rppt@kernel.org>,
Pasha Tatashin <pasha.tatashin@soleen.com>,
Peter Zijlstra <peterz@infradead.org>,
"Srivatsa S. Bhat (VMware)" <srivatsa@csail.mit.edu>,
Suren Baghdasaryan <surenb@google.com>,
Usama Arif <usama.arif@bytedance.com>,
virtualization@lists.linux-foundation.org,
VMware PV-Drivers Reviewers <pv-drivers@vmware.com>,
x86@kernel.org, xen-devel@lists.xenproject.org
Subject: Re: [PATCH RFC 0/4] x86/fixmap: Unify FIXADDR_TOP
Date: Wed, 07 Jun 2023 20:29:32 +0200 [thread overview]
Message-ID: <877csfjfcj.ffs@tglx> (raw)
In-Reply-To: <cover.1684137557.git.houwenlong.hwl@antgroup.com>
On Mon, May 15 2023 at 16:19, Hou Wenlong wrote:
> This patchset unifies FIXADDR_TOP as a variable for x86, allowing the
> fixmap area to be movable and relocated with the kernel image in the
> x86/PIE patchset [0]. This enables the kernel image to be relocated in
> the top 512G of the address space.
What for? What's the use case.
Please provide a proper argument why this is generally useful and
important.
Thanks,
tglx
prev parent reply other threads:[~2023-06-07 18:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-15 8:19 [PATCH RFC 0/4] x86/fixmap: Unify FIXADDR_TOP Hou Wenlong
2023-05-15 8:19 ` [PATCH RFC 1/4] x86/vsyscall: Don't use set_fixmap() to map vsyscall page Hou Wenlong
2023-05-15 8:19 ` [PATCH RFC 2/4] x86/xen: Pin up to VSYSCALL_ADDR when vsyscall page is out of fixmap area Hou Wenlong
2023-06-07 7:44 ` [PATCH RFC 0/4] x86/fixmap: Unify FIXADDR_TOP Hou Wenlong
2023-06-07 12:49 ` Dave Hansen
2023-06-08 9:33 ` Hou Wenlong
2023-06-10 18:37 ` Thomas Gleixner
2023-06-07 18:29 ` Thomas Gleixner [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=877csfjfcj.ffs@tglx \
--to=tglx@linutronix.de \
--cc=akpm@linux-foundation.org \
--cc=amakhalov@vmware.com \
--cc=anshuman.khandual@arm.com \
--cc=boris.ostrovsky@oracle.com \
--cc=bp@alien8.de \
--cc=brgerst@gmail.com \
--cc=dave.hansen@linux.intel.com \
--cc=dwmw@amazon.co.uk \
--cc=houwenlong.hwl@antgroup.com \
--cc=hpa@zytor.com \
--cc=jgross@suse.com \
--cc=jiangshan.ljs@antgroup.com \
--cc=jpoimboe@kernel.org \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=pasha.tatashin@soleen.com \
--cc=peterz@infradead.org \
--cc=pv-drivers@vmware.com \
--cc=rppt@kernel.org \
--cc=srivatsa@csail.mit.edu \
--cc=surenb@google.com \
--cc=usama.arif@bytedance.com \
--cc=virtualization@lists.linux-foundation.org \
--cc=x86@kernel.org \
--cc=xen-devel@lists.xenproject.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;
as well as URLs for NNTP newsgroup(s).