Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1709741
| From | Pasha Tatashin <pasha.tatashin@oracle.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [v6 01/15] x86/mm: reserve only exiting low pages |
| Date | 2017-08-11 17:30 +0200 |
| Message-ID | <udk2T-5cA-37@gated-at.bofh.it> (permalink) |
| References | <ubX8m-5vB-5@gated-at.bofh.it> <ubX8m-5vB-21@gated-at.bofh.it> <uddb4-14n-23@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
>> Struct pages are initialized by going through __init_single_page(). Since >> the existing physical memory in memblock is represented in memblock.memory >> list, struct page for every page from this list goes through >> __init_single_page(). > > By a page _from_ this list you mean struct pages backing the physical > memory of the memblock lists? Correct: "for every page from this list...", for every page represented by this list the struct page is initialized through __init_single_page() >> In this patchset we will stop zeroing struct page memory during allocation. >> Therefore, this bug must be fixed in order to avoid random assert failures >> caused by CONFIG_DEBUG_VM_PGFLAGS triggers. >> >> The fix is to reserve memory from the first existing PFN. > > Hmm, I assume this is a result of some assert triggering, right? Which > one? Why don't we need the same treatment for other than x86 arch? Correct, the pgflags asserts were triggered when we were setting reserved flags to struct page for PFN 0 in which was never initialized through __init_single_page(). The reason they were triggered is because we set all uninitialized memory to ones in one of the debug patches. >> Signed-off-by: Pavel Tatashin <pasha.tatashin@oracle.com> >> Reviewed-by: Steven Sistare <steven.sistare@oracle.com> >> Reviewed-by: Daniel Jordan <daniel.m.jordan@oracle.com> >> Reviewed-by: Bob Picco <bob.picco@oracle.com> > > I guess that the review happened inhouse. I do not want to question its > value but it is rather strange to not hear the specific review comments > which might be useful in general and moreover even not include those > people on the CC list so they are aware of the follow up discussion. I will bring this up with my colleagues to how to handle this better in the future. I will also CC the reviewers when I sent out the updated patch series.
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
[v6 01/15] x86/mm: reserve only exiting low pages Pavel Tatashin <pasha.tatashin@oracle.com> - 2017-08-07 22:50 +0200
Re: [v6 01/15] x86/mm: reserve only exiting low pages Michal Hocko <mhocko@kernel.org> - 2017-08-11 10:10 +0200
Re: [v6 01/15] x86/mm: reserve only exiting low pages Pasha Tatashin <pasha.tatashin@oracle.com> - 2017-08-11 17:30 +0200
Re: [v6 01/15] x86/mm: reserve only exiting low pages Michal Hocko <mhocko@kernel.org> - 2017-08-14 13:50 +0200
Re: [v6 01/15] x86/mm: reserve only exiting low pages Pasha Tatashin <pasha.tatashin@oracle.com> - 2017-08-14 15:40 +0200
Re: [v6 01/15] x86/mm: reserve only exiting low pages Michal Hocko <mhocko@kernel.org> - 2017-08-14 16:00 +0200
Re: [v6 01/15] x86/mm: reserve only exiting low pages Pasha Tatashin <pasha.tatashin@oracle.com> - 2017-08-17 17:40 +0200
csiph-web