From: Dave Hansen <dave.hansen@intel.com>
To: Gwan-gyeong Mun <gwan-gyeong.mun@intel.com>,
linux-kernel@vger.kernel.org
Cc: osalvador@suse.de, 42.hyeyoo@gmail.com, byungchul@sk.com,
dave.hansen@linux.intel.com, luto@kernel.org,
peterz@infradead.org, akpm@linux-foundation.org,
max.byungchul.park@sk.com, max.byungchul.park@gmail.com
Subject: Re: [RFC 1/1] x86/vmemmap: Add missing update of PML4 table / PML5 table entry
Date: Fri, 14 Feb 2025 11:57:50 -0800 [thread overview]
Message-ID: <25b9d3f5-bfe8-48a9-b11b-819d19cfae1e@intel.com> (raw)
In-Reply-To: <20250214195151.168306-2-gwan-gyeong.mun@intel.com>
On 2/14/25 11:51, Gwan-gyeong Mun wrote:
> when performing vmemmap populate, if the entry of the PML4 table/PML5 table
> pointing to the target virtual address has never been updated, a page fault
> occurs when the memset(start) called from the vmemmap_use_new_sub_pmd()
> execution flow.
"Page fault" meaning oops? Or something that we manage to handle and
return from without oopsing?
> This fixes the problem of using the virtual address without updating the
> entry in the PML4 table or PML5 table. But this is a temporary solution to
> prevent page fault problems, and it requires improvement of the routine
> that updates the missing entry in the PML4 table or PML5 table.
Can we please skip past the band-aid and go to the real fix?
next prev parent reply other threads:[~2025-02-14 19:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-14 19:51 [RFC 0/1] " Gwan-gyeong Mun
2025-02-14 19:51 ` [RFC 1/1] " Gwan-gyeong Mun
2025-02-14 19:57 ` Dave Hansen [this message]
2025-02-15 0:20 ` Harry (Hyeonggon) Yoo
2025-02-15 0:29 ` Dave Hansen
2025-02-17 11:40 ` Gwan-gyeong Mun
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=25b9d3f5-bfe8-48a9-b11b-819d19cfae1e@intel.com \
--to=dave.hansen@intel.com \
--cc=42.hyeyoo@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=byungchul@sk.com \
--cc=dave.hansen@linux.intel.com \
--cc=gwan-gyeong.mun@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=max.byungchul.park@gmail.com \
--cc=max.byungchul.park@sk.com \
--cc=osalvador@suse.de \
--cc=peterz@infradead.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
all inboxes | Powered by JetHome®