All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joel Granados <j.granados@samsung.com>
To: Yi Liu <yi.l.liu@intel.com>, Zhenzhong Duan <zhenzhong.duan@intel.com>
Cc: Alex Williamson <alex.williamson@redhat.com>,
	Eric Auger <eric.auger@redhat.com>,
	Nicolin Chen <nicolinc@nvidia.com>,
	Kevin Tian <kevin.tian@intel.com>, Jason Gunthorpe <jgg@ziepe.ca>,
	qemu-devel <qemu-devel@nongnu.org>
Subject: Questions regarding the still unpublished qemu series https://github.com/yiliu1765/qemu/tree/zhenzhong/wip/iommufd_nesting_rfcv1
Date: Wed, 20 Dec 2023 13:11:16 +0100	[thread overview]
Message-ID: <20231220121116.hjfl7zkcm2q74aco@localhost> (raw)
In-Reply-To: CGME20231220121121eucas1p23ee600a82137ce935bf182e0e8ce76fe@eucas1p2.samsung.com

[-- Attachment #1: Type: text/plain, Size: 823 bytes --]

Hello Everyone

While running https://github.com/yiliu1765/qemu/tree/zhenzhong/wip/iommufd_nesting_rfcv1
I have come across particular code path that seems odd:

I'm hitting an assert in softmmu/memory.c:1994 after calling a
notification from vtd_flt_page_walk_level. The code in memory.c:1994
makes sure that when type==IOMMU_NOTIFIER_UNMAP, the permissions are
IOMMU_NONE. But the code in vtd_flt_page_walk_level sets the
permissions to read|write. This is part of the "intel_iommu: piotlb
invalidation should notify unmap" commit in the iommufd_nesting_rfcv1
series.

Question is: Why assert on the permissions being NONE if they might be
read|write?

Hope this makes sense. Don't hesitate to get back to me if you see that
there is something missing in my explanation.

Best

-- 

Joel Granados

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]

       reply	other threads:[~2023-12-20 12:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20231220121121eucas1p23ee600a82137ce935bf182e0e8ce76fe@eucas1p2.samsung.com>
2023-12-20 12:11 ` Joel Granados [this message]
2023-12-21  3:33   ` Questions regarding the still unpublished qemu series https://github.com/yiliu1765/qemu/tree/zhenzhong/wip/iommufd_nesting_rfcv1 Duan, Zhenzhong
2023-12-23 12:40     ` Joel Granados

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=20231220121116.hjfl7zkcm2q74aco@localhost \
    --to=j.granados@samsung.com \
    --cc=alex.williamson@redhat.com \
    --cc=eric.auger@redhat.com \
    --cc=jgg@ziepe.ca \
    --cc=kevin.tian@intel.com \
    --cc=nicolinc@nvidia.com \
    --cc=qemu-devel@nongnu.org \
    --cc=yi.l.liu@intel.com \
    --cc=zhenzhong.duan@intel.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.