Messages in this thread |  | | Date | Wed, 19 Dec 2012 13:55:59 -0800 | Subject | Re: [PATCH v6 02/27] x86, mm: make pgd next calculation consistent with pud/pmd | From | Yinghai Lu <> |
| |
On Wed, Dec 19, 2012 at 12:48 PM, Borislav Petkov <bp@alien8.de> wrote: > > "Also, do not boundary-check 'next' but pass 'end' down to > phys_pud_init() instead because the loop in there terminates at > PTRS_PER_PUD and thus can handle a possibly bigger 'end' properly."
--- Just like the way we calculate next for pud and pmd, aka round down and add size.
Also, do not do boundary-checking with 'next', and just pass 'end' down to phys_pud_init() instead. Because the loop in phys_pud_init() terminates at PTRS_PER_PUD and thus can handle a possibly bigger 'end' properly. ---
|  |