From: Harry Yoo <harry.yoo@oracle.com>
To: "Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>
Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Hans de Goede <hansg@kernel.org>,
linux-media@vger.kernel.org, linux-mm@kvack.org
Subject: Re: Linux 7.0-rc4: v4l2src0:src: page allocation failure - increased memory usage in 7.0?
Date: Fri, 20 Mar 2026 10:01:33 +0900 [thread overview]
Message-ID: <abycbXzYupZpGkvR@hyeyoo> (raw)
In-Reply-To: <abtAylIlW3I8s1T-@mail-itl>
On Thu, Mar 19, 2026 at 01:18:18AM +0100, Marek Marczykowski-Górecki wrote:
> Hello,
>
> When testing 7.0-rc4 (and also got it with 7.0-rc1), I got page
> allocation failure in uvcvideo when using v4l2 camera in a VM. The setup
> is rather memory constrained - it's a HVM with just 300MB of memory
> running on Xen, with PCI passthrough of USB controllers (to which an USB
> camera is connected). But the very same setup works just fine with older
> kernel (last known good is 6.19.5, built with the same config).
Could you please share what /proc/meminfo looks like on v6.19, and
also enable memory allocation profiling feature [1] and see
what has changed between v6.19 and v7.0?
On v6.19, you should be able to see how much memory is allocated by
reading /proc/allocinfo.
On v7.0-rc4, warn_alloc() should let memory allocation profiling
print top users.
[1] https://docs.kernel.org/mm/allocation-profiling.html
--
Cheers,
Harry / Hyeonggon
next prev parent reply other threads:[~2026-03-20 1:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-19 0:18 Linux 7.0-rc4: v4l2src0:src: page allocation failure - increased memory usage in 7.0? Marek Marczykowski-Górecki
2026-03-19 10:19 ` Ricardo Ribalda
2026-03-20 0:35 ` Marek Marczykowski-Górecki
2026-03-20 1:07 ` Laurent Pinchart
2026-03-20 7:48 ` Ricardo Ribalda
2026-03-19 15:16 ` Nicolas Dufresne
2026-03-20 1:01 ` Harry Yoo [this message]
2026-03-20 14:07 ` Marek Marczykowski-Górecki
2026-03-23 4:45 ` Harry Yoo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=abycbXzYupZpGkvR@hyeyoo \
--to=harry.yoo@oracle.com \
--cc=hansg@kernel.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=marmarek@invisiblethingslab.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox