Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1175562
| From | "Kirill A. Shutemov" <kirill@shutemov.name> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH 05/11] mm: debug: dump page into a string rather than directly on screen |
| Date | 2015-07-01 23:40 +0200 |
| Message-ID | <pHxTA-28A-11@gated-at.bofh.it> (permalink) |
| References | <pq4XD-6ml-3@gated-at.bofh.it> <pq4XE-6ml-15@gated-at.bofh.it> <pHdia-59-5@gated-at.bofh.it> <pHvRL-Md-13@gated-at.bofh.it> <pHxJV-23b-61@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Wed, Jul 01, 2015 at 02:25:56PM -0700, David Rientjes wrote:
> On Wed, 1 Jul 2015, Sasha Levin wrote:
>
> > On 06/30/2015 07:35 PM, David Rientjes wrote:
> > > I don't know how others feel, but this looks strange to me and seems like
> > > it's only a result of how we must now dump page information
> > > (dump_page(page) is no longer available, we must do pr_alert("%pZp",
> > > page)).
> > >
> > > Since we're relying on print formats, this would arguably be better as
> > >
> > > pr_alert("Not movable balloon page:\n");
> > > pr_alert("%pZp", page);
> > >
> > > to avoid introducing newlines into potentially lengthy messages that need
> > > a specified loglevel like you've done above.
> > >
> > > But that's not much different than the existing dump_page()
> > > implementation.
> > >
> > > So for this to be worth it, it seems like we'd need a compelling usecase
> > > for something like pr_alert("%pZp %pZv", page, vma) and I'm not sure we're
> > > ever actually going to see that. I would argue that
> > >
> > > dump_page(page);
> > > dump_vma(vma);
> > >
> > > would be simpler in such circumstances.
> >
> > I think we can find usecases where we want to dump more information than what's
> > contained in just one page/vma/mm struct. Things like the following from mm/gup.c:
> >
> > VM_BUG_ON_PAGE(compound_head(page) != head, page);
> >
> > Where seeing 'head' would be interesting as well.
> >
>
> I think it's a debate about whether this would be better off handled as
>
> if (VM_BUG_ON(compound_head(page) != head)) {
> dump_page(page);
> dump_page(head);
Huh? How would we reach this, if VM_BUG_ON() will trigger BUG()?
> }
>
> and avoid VM_BUG_ON_PAGE() and the new print formats entirely. We can
> improve upon existing VM_BUG_ON(), and BUG_ON() itself since the VM isn't
> anything special in this regard, to print diagnostic information that may
> be helpful, but I don't feel like adding special VM_BUG_ON_*() macros or
> printing formats makes any of this simpler.
--
Kirill A. Shutemov
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Re: [PATCH 05/11] mm: debug: dump page into a string rather than directly on screen David Rientjes <rientjes@google.com> - 2015-07-01 23:30 +0200 Re: [PATCH 05/11] mm: debug: dump page into a string rather than directly on screen "Kirill A. Shutemov" <kirill@shutemov.name> - 2015-07-01 23:40 +0200 Re: [PATCH 05/11] mm: debug: dump page into a string rather than directly on screen Vlastimil Babka <vbabka@suse.cz> - 2015-07-02 00:40 +0200 Re: [PATCH 05/11] mm: debug: dump page into a string rather than directly on screen Sasha Levin <sasha.levin@oracle.com> - 2015-07-02 01:00 +0200
csiph-web