From: Peter Zijlstra <peterz@infradead.org>
To: "Williams, Dan J" <dan.j.williams@intel.com>
Cc: "tglx@linutronix.de" <tglx@linutronix.de>,
"Hansen, Dave" <dave.hansen@intel.com>,
"bigeasy@linutronix.de" <bigeasy@linutronix.de>,
"kirill.shutemov@linux.intel.com"
<kirill.shutemov@linux.intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"dave.hansen@linux.intel.com" <dave.hansen@linux.intel.com>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
"x86@kernel.org" <x86@kernel.org>,
"mingo@redhat.com" <mingo@redhat.com>,
"luto@kernel.org" <luto@kernel.org>,
"bp@alien8.de" <bp@alien8.de>
Subject: Re: [PATCH] x86/mm: Drop usage of __flush_tlb_all() in kernel_physical_mapping_init()
Date: Tue, 20 Nov 2018 10:03:36 +0100 [thread overview]
Message-ID: <20181120090336.GF2131@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <7b1bbfd295c4709e85ca26457b460fb4d36aa276.camel@intel.com>
On Tue, Nov 20, 2018 at 02:59:32AM +0000, Williams, Dan J wrote:
> On Mon, 2018-11-19 at 15:43 -0800, Dave Hansen wrote:
> > On 11/19/18 3:19 PM, Dan Williams wrote:
> > > Andy wondered why a path that can sleep was using __flush_tlb_all()
> > > [1]
> > > and Dave confirmed the expectation for TLB flush is for modifying /
> > > invalidating existing pte entries, but not initial population [2].
> >
> > I _think_ this is OK.
> >
> > But, could we sprinkle a few WARN_ON_ONCE(p*_present()) calls in
> > there
> > to help us sleep at night?
>
> Well, I'm having nightmares now because my naive patch to sprinkle some
> WARN_ON_ONCE() calls is leading to my VM live locking at boot... no
> backtrace. If I revert the patch below and just go with the
> __flush_tlb_all() removal it seems fine.
>
> I'm going to set this aside for a bit, but if anyone has any thoughts
> in the meantime I'd appreciate it.
Have you tried using early_printk ?
So kernel_physical_mapping_init() has a comment that states the virtual
and physical addresses we create mappings for should be PMD aligned,
which implies pud/p4d could have overlap between the mappings.
But in that case, I would expect the new and old values to match.
So maybe you should be checking something like:
WARN_ON_ONCE(pud_present(*pud) && !pud_same(pud, new));
> @@ -573,6 +578,7 @@ phys_pud_init(pud_t *pud_page, unsigned long paddr, unsigned long paddr_end,
> E820_TYPE_RAM) &&
> !e820__mapped_any(paddr & PUD_MASK, paddr_next,
> E820_TYPE_RESERVED_KERN))
> + WARN_ON_ONCE(pud_present(*pud));
> set_pud(pud, __pud(0));
> continue;
> }
> @@ -610,6 +616,7 @@ phys_pud_init(pud_t *pud_page, unsigned long paddr, unsigned long paddr_end,
> if (page_size_mask & (1<<PG_LEVEL_1G)) {
> pages++;
> spin_lock(&init_mm.page_table_lock);
> + WARN_ON_ONCE(pud_present(*pud));
> set_pte((pte_t *)pud,
> pfn_pte((paddr & PUD_MASK) >> PAGE_SHIFT,
> PAGE_KERNEL_LARGE));
> @@ -623,6 +630,7 @@ phys_pud_init(pud_t *pud_page, unsigned long paddr, unsigned long paddr_end,
> page_size_mask, prot);
>
> spin_lock(&init_mm.page_table_lock);
> + WARN_ON_ONCE(pud_present(*pud));
> pud_populate(&init_mm, pud, pmd);
> spin_unlock(&init_mm.page_table_lock);
> }
> @@ -657,6 +665,7 @@ phys_p4d_init(p4d_t *p4d_page, unsigned long paddr, unsigned long paddr_end,
> E820_TYPE_RAM) &&
> !e820__mapped_any(paddr & P4D_MASK, paddr_next,
> E820_TYPE_RESERVED_KERN))
> + WARN_ON_ONCE(p4d_present(*p4d));
> set_p4d(p4d, __p4d(0));
> continue;
> }
> @@ -674,6 +683,7 @@ phys_p4d_init(p4d_t *p4d_page, unsigned long paddr, unsigned long paddr_end,
> page_size_mask);
>
> spin_lock(&init_mm.page_table_lock);
> + WARN_ON_ONCE(p4d_present(*p4d));
> p4d_populate(&init_mm, p4d, pud);
> spin_unlock(&init_mm.page_table_lock);
> }
next prev parent reply other threads:[~2018-11-20 9:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-19 23:19 Dan Williams
2018-11-19 23:43 ` Dave Hansen
2018-11-19 23:48 ` Dan Williams
2018-11-20 2:59 ` Williams, Dan J
2018-11-20 9:03 ` Peter Zijlstra [this message]
2018-11-21 22:36 ` Dan Williams
2018-12-05 18:06 ` [tip:x86/mm] generic/pgtable: Introduce set_pte_safe() tip-bot for Dan Williams
2018-11-20 8:52 ` [PATCH] x86/mm: Drop usage of __flush_tlb_all() in kernel_physical_mapping_init() Peter Zijlstra
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=20181120090336.GF2131@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=bigeasy@linutronix.de \
--cc=bp@alien8.de \
--cc=dan.j.williams@intel.com \
--cc=dave.hansen@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=stable@vger.kernel.org \
--cc=tglx@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
all inboxes | Powered by JetHome®