From: Oliver Neukum <oneukum@suse.com>
To: bingbu.cao@intel.com
Cc: linux-media@vger.kernel.org, Takashi Iwai <tiwai@suse.de>
Subject: question on 1faf84ff1c0 ("media: ipu6: optimize the IPU6 MMU unmapping flow") handling mmu_info->dummy_l2_pteval
Date: Tue, 17 Nov 2026 13:26:07 +0100 [thread overview]
Message-ID: <b3dfdcf3-2212-4151-98cf-a3d96f494f50@suse.com> (raw)
Hi,
before that commit the whole function was aborted, if dummy_l2_pteval
was encountered. The updated version skips a step in the loop,
that is it increments l1_idx but not iova. Why is this safe?
The old behavior was more drastic, but it looks saner.
Regards
Oliver
reply other threads:[~2026-11-17 12:26 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=b3dfdcf3-2212-4151-98cf-a3d96f494f50@suse.com \
--to=oneukum@suse.com \
--cc=bingbu.cao@intel.com \
--cc=linux-media@vger.kernel.org \
--cc=tiwai@suse.de \
/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