[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150929084422.GB332@gmail.com>
Date: Tue, 29 Sep 2015 10:44:22 +0200
From: Ingo Molnar <mingo@...nel.org>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
linux-mm <linux-mm@...ck.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>, Oleg Nesterov <oleg@...hat.com>,
Waiman Long <waiman.long@...com>,
Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [PATCH 06/11] x86/virt/guest/xen: Remove use of pgd_list from
the Xen guest code
* Linus Torvalds <torvalds@...ux-foundation.org> wrote:
> On Mon, Sep 21, 2015 at 11:23 PM, Ingo Molnar <mingo@...nel.org> wrote:
> > xen_mm_pin_all()/unpin_all() are used to implement full guest instance
> > suspend/restore. It's a stop-all method that needs to iterate through
> > all allocated pgds in the system to fix them up for Xen's use.
>
> And _this_ is why I'd reall ylike that "for_each_mm()" helper.
>
> Yeah, yeah, maybe it would require syntax like
>
> for_each_mm (tsk, mm) {
> ...
> } end_for_each_mm(mm);
>
> to do variable allocation things or cleanups (ie "end_for_each_mm()" might drop
> the task lock etc), but wouldn't that still be better than this complex
> boilerplate thing?
Yeah, agreed absolutely.
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