mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: ALOK TIWARI <alok.a.tiwari@oracle.com>
To: Rob Clark <robdclark@gmail.com>, dri-devel@lists.freedesktop.org
Cc: freedreno@lists.freedesktop.org, linux-arm-msm@vger.kernel.org,
	Connor Abbott <cwabbott0@gmail.com>,
	Rob Clark <robdclark@chromium.org>, Will Deacon <will@kernel.org>,
	Robin Murphy <robin.murphy@arm.com>,
	Joerg Roedel <joro@8bytes.org>, Jason Gunthorpe <jgg@ziepe.ca>,
	Kevin Tian <kevin.tian@intel.com>,
	Nicolin Chen <nicolinc@nvidia.com>,
	Joao Martins <joao.m.martins@oracle.com>,
	"moderated list:ARM SMMU DRIVERS"
	<linux-arm-kernel@lists.infradead.org>,
	"open list:IOMMU SUBSYSTEM" <iommu@lists.linux.dev>,
	open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4 03/33] iommu/io-pgtable-arm: Add quirk to quiet WARN_ON()
Date: Sat, 3 May 2025 00:59:55 +0530	[thread overview]
Message-ID: <b98001c0-8374-4f00-9733-d9edf72c4989@oracle.com> (raw)
In-Reply-To: <20250502165831.44850-4-robdclark@gmail.com>



On 02-05-2025 22:26, Rob Clark wrote:
> In situations where mapping/unmapping squence can be controlled by

typo squence -> sequence

> userspace, attempting to map over a region that has not yet been
> unmapped is an error.  But not something that should spam dmesg.
> 
> Now that there is a quirk, we can also drop the selftest_running
> flag, and use the quirk instead for selftests.
> 
> Signed-off-by: Rob Clark<robdclark@chromium.org>

Thanks,
Alok

  reply	other threads:[~2025-05-02 19:30 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-02 16:56 [PATCH v4 00/33] drm/msm: sparse / "VM_BIND" support Rob Clark
2025-05-02 16:56 ` [PATCH v4 01/33] drm/gpuvm: Don't require obj lock in destructor path Rob Clark
2025-05-02 16:56 ` [PATCH v4 02/33] drm/gpuvm: Allow VAs to hold soft reference to BOs Rob Clark
2025-05-02 16:56 ` [PATCH v4 03/33] iommu/io-pgtable-arm: Add quirk to quiet WARN_ON() Rob Clark
2025-05-02 19:29   ` ALOK TIWARI [this message]
2025-05-02 16:56 ` [PATCH v4 04/33] drm/msm: Rename msm_file_private -> msm_context Rob Clark
2025-05-02 16:56 ` [PATCH v4 05/33] drm/msm: Improve msm_context comments Rob Clark
2025-05-02 16:56 ` [PATCH v4 06/33] drm/msm: Rename msm_gem_address_space -> msm_gem_vm Rob Clark
2025-05-02 16:56 ` [PATCH v4 07/33] drm/msm: Remove vram carveout support Rob Clark
2025-05-02 16:56 ` [PATCH v4 08/33] drm/msm: Collapse vma allocation and initialization Rob Clark
2025-05-02 16:56 ` [PATCH v4 09/33] drm/msm: Collapse vma close and delete Rob Clark
2025-05-02 16:56 ` [PATCH v4 10/33] drm/msm: Don't close VMAs on purge Rob Clark
2025-05-02 16:56 ` [PATCH v4 11/33] drm/msm: drm_gpuvm conversion Rob Clark
2025-05-02 16:56 ` [PATCH v4 12/33] drm/msm: Convert vm locking Rob Clark
2025-05-02 16:56 ` [PATCH v4 13/33] drm/msm: Use drm_gpuvm types more Rob Clark
2025-05-02 16:56 ` [PATCH v4 14/33] drm/msm: Split out helper to get iommu prot flags Rob Clark
2025-05-02 16:56 ` [PATCH v4 15/33] drm/msm: Add mmu support for non-zero offset Rob Clark
2025-05-02 16:56 ` [PATCH v4 16/33] drm/msm: Add PRR support Rob Clark
2025-05-02 16:56 ` [PATCH v4 17/33] drm/msm: Rename msm_gem_vma_purge() -> _unmap() Rob Clark
2025-05-02 16:56 ` [PATCH v4 18/33] drm/msm: Lazily create context VM Rob Clark
2025-05-02 16:56 ` [PATCH v4 19/33] drm/msm: Add opt-in for VM_BIND Rob Clark
2025-05-02 16:56 ` [PATCH v4 20/33] drm/msm: Mark VM as unusable on GPU hangs Rob Clark
2025-05-02 16:56 ` [PATCH v4 21/33] drm/msm: Add _NO_SHARE flag Rob Clark
2025-05-05  7:54   ` Christian König
2025-05-05 14:15     ` Rob Clark
2025-05-05 15:17       ` Christian König
2025-05-02 16:56 ` [PATCH v4 22/33] drm/msm: Crashdump prep for sparse mappings Rob Clark

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=b98001c0-8374-4f00-9733-d9edf72c4989@oracle.com \
    --to=alok.a.tiwari@oracle.com \
    --cc=cwabbott0@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=freedreno@lists.freedesktop.org \
    --cc=iommu@lists.linux.dev \
    --cc=jgg@ziepe.ca \
    --cc=joao.m.martins@oracle.com \
    --cc=joro@8bytes.org \
    --cc=kevin.tian@intel.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nicolinc@nvidia.com \
    --cc=robdclark@chromium.org \
    --cc=robdclark@gmail.com \
    --cc=robin.murphy@arm.com \
    --cc=will@kernel.org \
    /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

all inboxes | Powered by JetHome®