From: Alex Williamson <alex.williamson@redhat.com>
To: Thanos Makatos <thanos.makatos@nutanix.com>
Cc: "vfio-users@redhat.com" <vfio-users@redhat.com>,
John Levon <john.levon@nutanix.com>,
Swapnil Ingle <swapnil.ingle@nutanix.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: semantics of VFIO_IOMMU_DIRTY_PAGES_FLAG_GET_BITMAP
Date: Tue, 1 Jun 2021 08:14:23 -0600 [thread overview]
Message-ID: <20210601081423.47689d7a.alex.williamson@redhat.com> (raw)
In-Reply-To: <CH0PR02MB7898402DC183E37BF74FF8868B3E9@CH0PR02MB7898.namprd02.prod.outlook.com>
On Tue, 1 Jun 2021 13:48:22 +0000
Thanos Makatos <thanos.makatos@nutanix.com> wrote:
> (sending here as I can't find a relevant list in
> http://vger.kernel.org/vger-lists.html)
$ ./scripts/get_maintainer.pl include/uapi/linux/vfio.h
Alex Williamson <alex.williamson@redhat.com> (maintainer:VFIO DRIVER)
Cornelia Huck <cohuck@redhat.com> (reviewer:VFIO DRIVER)
kvm@vger.kernel.org (open list:VFIO DRIVER)
linux-kernel@vger.kernel.org (open list)
> I'm trying to understand the semantics of
> VFIO_IOMMU_DIRTY_PAGES_FLAG_GET_BITMAP. My (very rough) understanding
> so far is that once a page gets pinned then it's considered dirty and
> if the page is still pinned then it remains dirty even after we're
> done serving VFIO_IOMMU_DIRTY_PAGES_FLAG_GET_BITMAP. Is my
> understanding correct?
This is the current type1 implementation, but the semantics only
require that a page is reported dirty if it's actually been written.
Without support for tracking DMA writes, we assume that any page
accessible to the device is constantly dirty. This will be refined
over time as software and hardware support improves, but we currently
error on the side of assuming all pinned pages are always dirty.
Thanks,
Alex
next parent reply other threads:[~2021-06-01 14:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CH0PR02MB7898402DC183E37BF74FF8868B3E9@CH0PR02MB7898.namprd02.prod.outlook.com>
2021-06-01 14:14 ` Alex Williamson [this message]
2021-06-01 15:07 ` Thanos Makatos
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=20210601081423.47689d7a.alex.williamson@redhat.com \
--to=alex.williamson@redhat.com \
--cc=john.levon@nutanix.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=swapnil.ingle@nutanix.com \
--cc=thanos.makatos@nutanix.com \
--cc=vfio-users@redhat.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 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®