[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150613074844.GC30388@gmail.com>
Date: Sat, 13 Jun 2015 09:48:44 +0200
From: Ingo Molnar <mingo@...nel.org>
To: Oleg Nesterov <oleg@...hat.com>
Cc: linux-kernel@...r.kernel.org, linux-mml@...r.kernel.org,
Andy Lutomirski <luto@...capital.net>,
Andrew Morton <akpm@...ux-foundation.org>,
Denys Vlasenko <dvlasenk@...hat.com>,
Brian Gerst <brgerst@...il.com>,
Peter Zijlstra <peterz@...radead.org>,
Borislav Petkov <bp@...en8.de>,
"H. Peter Anvin" <hpa@...or.com>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Thomas Gleixner <tglx@...utronix.de>,
Waiman Long <Waiman.Long@...com>
Subject: Re: [PATCH 02/12] x86/mm/hotplug: Remove pgd_list use from the
memory hotplug code
* Oleg Nesterov <oleg@...hat.com> wrote:
> On 06/11, Ingo Molnar wrote:
> >
> > void sync_global_pgds(unsigned long start, unsigned long end, int removed)
> > {
> > @@ -169,29 +169,33 @@ void sync_global_pgds(unsigned long start, unsigned long end, int removed)
> >
> > for (address = start; address <= end; address += PGDIR_SIZE) {
> > const pgd_t *pgd_ref = pgd_offset_k(address);
> > - struct page *page;
> > + struct task_struct *g, *p;
> >
> > /*
> > - * When it is called after memory hot remove, pgd_none()
> > - * returns true. In this case (removed == 1), we must clear
> > - * the PGD entries in the local PGD level page.
> > + * When this function is called after memory hot remove,
> > + * pgd_none() already returns true, but only the reference
> > + * kernel PGD has been cleared, not the process PGDs.
> > + *
> > + * So clear the affected entries in every process PGD as well:
> > */
> > if (pgd_none(*pgd_ref) && !removed)
> > continue;
> >
> > spin_lock(&pgd_lock);
> > - list_for_each_entry(page, &pgd_list, lru) {
> > - pgd_t *pgd;
> > +
> > + for_each_process_thread(g, p) {
> > + pgd_t *pgd = p->mm->pgd;
>
> and we use the same pgd later: set_pgd(pgd, *pgd_ref).
> looks like this should be pgd_offset(p->mm, address) ?
>
> And obviously you need to check ->mm != NULL first?
Yes.
> And perhaps it makes sense to swap "for (address)" and for_each_process()
> loops...
Yes, but I'd flip around the logic in a later, separate patch.
Note that PGDIR_SIZE is 512 GB here, so the outer loop will most likely execute at
most twice in practice.
Thanks,
Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists