[PATCH igt 7/9] msm/mapping: Handle larger gmem file size

Rob Clark rob.clark at oss.qualcomm.com
Tue Jul 1 18:01:06 UTC 2025


On Tue, Jul 1, 2025 at 9:21 AM Kamil Konieczny
<kamil.konieczny at linux.intel.com> wrote:
>
> Hi Rob,
> On 2025-06-30 at 11:09:01 -0700, Rob Clark wrote:
> > From: Rob Clark <rob.clark at oss.qualcomm.com>
> >
> > If running on a system with full desktop environment, the file will be
> > much larger than 0x4000 bytes.
> >
> > Signed-off-by: Rob Clark <rob.clark at oss.qualcomm.com>
> > ---
> >  tests/msm/msm_mapping.c | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/tests/msm/msm_mapping.c b/tests/msm/msm_mapping.c
> > index 03a9e814c931..978ea18375dd 100644
> > --- a/tests/msm/msm_mapping.c
> > +++ b/tests/msm/msm_mapping.c
> > @@ -122,7 +122,7 @@ endswith(const char *str, const char *end)
> >  static uint64_t
> >  get_bo_addr(int drm_fd, const char *name)
> >  {
> > -     char buf[0x4000];
> > +     char buf[0x80000];
>
> If it is that big why not malloc() it?

in kernel, for sure.  But userspace stack size is multiple MB at least

BR,
-R

> Regards,
> Kamil
>
> >       char *p = buf;
> >
> >       igt_debugfs_read(drm_fd, "gem", buf);
> > --
> > 2.50.0
> >


More information about the igt-dev mailing list