From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Linux Media Mailing List <linux-media@vger.kernel.org>
Cc: Andy Shevchenko <andy.shevchenko@gmail.com>,
Patrik Gfeller <patrik.gfeller@gmail.com>
Subject: Re: atomisp kernel driver(s)
Date: Wed, 13 May 2020 11:56:05 +0200 [thread overview]
Message-ID: <20200513115605.787e9079@coco.lan> (raw)
In-Reply-To: <20200512165644.6609098b@coco.lan>
Em Tue, 12 May 2020 16:56:44 +0200
Mauro Carvalho Chehab <mchehab@kernel.org> escreveu:
> [ 79.625858] virt_to_cache: Object is not a Slab page!
Solved this issue:
https://git.linuxtv.org/mchehab/experimental.git/commit/?h=atomisp_v2.1&id=c916263a340ef1c4cc187ad6267302bdd4298514
Yet, I'm not happy with the code inside the hmm/ dir, nor the code at
isp_mmu.c. There are too many dirty memory-management magic there, including
some forks from upstream /mm code inside it.
Changing it may not be an easy task, as it currently uses three different
VMA areas (dynamic, reserved, and "normal"). Touching it without knowing more
about the atomisp or being able to test the driver seems risky.
Thanks,
Mauro
next prev parent reply other threads:[~2020-05-13 9:56 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-18 14:39 atomisp kernel driver(s) Patrik Gfeller
2020-04-18 15:25 ` Mauro Carvalho Chehab
2020-04-18 15:26 ` Mauro Carvalho Chehab
2020-04-18 15:37 ` Patrik Gfeller
2020-04-19 23:31 ` Mauro Carvalho Chehab
2020-04-20 17:48 ` Patrik Gfeller
2020-04-20 18:27 ` Patrik Gfeller
2020-04-20 20:47 ` Mauro Carvalho Chehab
2020-04-22 17:56 ` Patrik Gfeller
2020-04-22 19:13 ` Mauro Carvalho Chehab
2020-04-24 8:52 ` Patrik Gfeller
2020-04-24 9:10 ` Patrik Gfeller
2020-04-24 10:07 ` Patrik Gfeller
2020-04-24 13:58 ` Patrik Gfeller
2020-04-25 11:22 ` Mauro Carvalho Chehab
2020-04-26 11:38 ` Patrik Gfeller
2020-04-26 16:50 ` Mauro Carvalho Chehab
2020-04-27 18:31 ` Patrik Gfeller
2020-04-27 21:50 ` Mauro Carvalho Chehab
2020-04-28 17:59 ` Patrik Gfeller
2020-04-28 23:13 ` Mauro Carvalho Chehab
2020-04-29 17:56 ` Patrik Gfeller
2020-04-29 18:17 ` Mauro Carvalho Chehab
2020-04-30 7:56 ` Patrik Gfeller
2020-04-30 10:55 ` Mauro Carvalho Chehab
2020-04-30 15:09 ` Patrik Gfeller
2020-04-30 22:25 ` Mauro Carvalho Chehab
2020-05-01 8:54 ` Patrik Gfeller
2020-05-01 9:38 ` Mauro Carvalho Chehab
2020-05-01 17:31 ` Patrik Gfeller
2020-05-01 19:30 ` Mauro Carvalho Chehab
2020-05-02 8:15 ` Patrik Gfeller
2020-05-02 9:20 ` Patrik Gfeller
2020-05-02 10:00 ` Mauro Carvalho Chehab
2020-05-02 9:34 ` Mauro Carvalho Chehab
2020-05-02 14:29 ` Patrik Gfeller
2020-05-02 16:28 ` Mauro Carvalho Chehab
2020-05-02 18:23 ` Patrik Gfeller
2020-05-02 14:50 ` Patrik Gfeller
2020-05-01 20:56 ` [PATCH] media: atomisp: use add_qos_request instead of update Mauro Carvalho Chehab
2020-04-18 15:29 ` atomisp kernel driver(s) Patrik Gfeller
2020-04-25 2:39 ` Laurent Pinchart
2020-04-25 10:36 ` Patrik Gfeller
2020-04-25 12:19 ` Mauro Carvalho Chehab
2020-04-26 19:07 ` Laurent Pinchart
2020-04-26 20:51 ` Mauro Carvalho Chehab
2020-04-26 19:33 ` Laurent Pinchart
2020-04-28 18:13 ` Patrik Gfeller
2020-04-26 7:44 ` Patrik Gfeller
2020-04-26 19:17 ` Laurent Pinchart
2020-04-29 17:59 ` Patrik Gfeller
2020-04-29 18:19 ` Laurent Pinchart
2020-04-30 15:28 ` Patrik Gfeller
2020-05-02 16:08 ` Andy Shevchenko
2020-05-02 17:04 ` Mauro Carvalho Chehab
2020-05-02 17:33 ` Andy Shevchenko
2020-05-03 10:18 ` Mauro Carvalho Chehab
2020-05-12 10:20 ` Mauro Carvalho Chehab
2020-05-12 11:12 ` Andy Shevchenko
2020-05-12 11:21 ` Andy Shevchenko
2020-05-12 14:56 ` Mauro Carvalho Chehab
2020-05-12 16:01 ` Andy Shevchenko
2020-05-13 18:36 ` Patrik Gfeller
2020-05-20 8:04 ` Mauro Carvalho Chehab
2020-05-13 9:56 ` Mauro Carvalho Chehab [this message]
2020-05-03 8:46 ` Patrik Gfeller
2020-05-03 10:23 ` Mauro Carvalho Chehab
2020-05-03 12:31 ` Patrik Gfeller
2020-05-03 13:36 ` Patrik Gfeller
2020-05-03 14:43 ` Mauro Carvalho Chehab
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=20200513115605.787e9079@coco.lan \
--to=mchehab+huawei@kernel.org \
--cc=andy.shevchenko@gmail.com \
--cc=linux-media@vger.kernel.org \
--cc=patrik.gfeller@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.