From: Leon Romanovsky <leon@kernel.org>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: Yishai Hadas <yishaih@nvidia.com>,
jgg@nvidia.com, saeedm@nvidia.com, kvm@vger.kernel.org,
netdev@vger.kernel.org, kuba@kernel.org, kevin.tian@intel.com,
joao.m.martins@oracle.com, maorg@nvidia.com, cohuck@redhat.com
Subject: Re: [PATCH V6 vfio 05/10] vfio: Introduce the DMA logging feature support
Date: Wed, 7 Sep 2022 12:45:13 +0300 [thread overview]
Message-ID: <YxhoKWfnwiLqxyQX@unreal> (raw)
In-Reply-To: <20220906164154.756e26aa.alex.williamson@redhat.com>
On Tue, Sep 06, 2022 at 04:41:54PM -0600, Alex Williamson wrote:
> On Mon, 5 Sep 2022 13:58:47 +0300
> Yishai Hadas <yishaih@nvidia.com> wrote:
> > diff --git a/include/linux/vfio.h b/include/linux/vfio.h
> > index e05ddc6fe6a5..b17f2f454389 100644
> > --- a/include/linux/vfio.h
> > +++ b/include/linux/vfio.h
> > @@ -108,6 +110,21 @@ struct vfio_migration_ops {
> > enum vfio_device_mig_state *curr_state);
> > };
> >
> > +/**
> > + * @log_start: Optional callback to ask the device start DMA logging.
> > + * @log_stop: Optional callback to ask the device stop DMA logging.
> > + * @log_read_and_clear: Optional callback to ask the device read
> > + * and clear the dirty DMAs in some given range.
>
> I don't see anywhere in the core that we track the device state
> relative to the DEVICE_FEATURE_DMA_LOGGING features, nor do we
> explicitly put the responsibility on the driver implementation to
> handle invalid user requests. The mlx5 driver implementation appears
> to do this, but maybe we should at least include a requirement here, ex.
>
> The vfio core implementation of the DEVICE_FEATURE_DMA_LOGGING_ set
> of features does not track logging state relative to the device,
> therefore the device implementation of vfio_log_ops must handle
> arbitrary user requests. This includes rejecting subsequent calls
> to log_start without an intervening log_stop, as well as graceful
> handling of log_stop and log_read_and_clear from invalid states.
>
> With something like that.
>
> Acked-by: Alex Williamson <alex.williamson@redhat.com>
>
> You can also add my Ack on 3, 4, and (fwiw) 6-10 as I assume this would
> be a PR from Leon. Thanks,
Yes, it is.
I sent PR based on clean 6.0-rc4.
Thanks
>
> Alex
>
> > + */
> > +struct vfio_log_ops {
> > + int (*log_start)(struct vfio_device *device,
> > + struct rb_root_cached *ranges, u32 nnodes, u64 *page_size);
> > + int (*log_stop)(struct vfio_device *device);
> > + int (*log_read_and_clear)(struct vfio_device *device,
> > + unsigned long iova, unsigned long length,
> > + struct iova_bitmap *dirty);
> > +};
> > +
> > /**
> > * vfio_check_feature - Validate user input for the VFIO_DEVICE_FEATURE ioctl
> > * @flags: Arg from the device_feature op
>
next prev parent reply other threads:[~2022-09-07 9:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-05 10:58 [PATCH V6 vfio 00/10] Add device DMA logging support for mlx5 driver Yishai Hadas
2022-09-05 10:58 ` [PATCH V6 vfio 01/10] net/mlx5: Introduce ifc bits for page tracker Yishai Hadas
2022-09-05 10:58 ` [PATCH V6 vfio 02/10] net/mlx5: Query ADV_VIRTUALIZATION capabilities Yishai Hadas
2022-09-05 10:58 ` [PATCH V6 vfio 03/10] vfio: Introduce DMA logging uAPIs Yishai Hadas
2022-09-05 10:58 ` [PATCH V6 vfio 04/10] vfio: Add an IOVA bitmap support Yishai Hadas
2022-09-05 10:58 ` [PATCH V6 vfio 05/10] vfio: Introduce the DMA logging feature support Yishai Hadas
2022-09-06 22:41 ` Alex Williamson
2022-09-07 9:45 ` Leon Romanovsky [this message]
2022-09-05 10:58 ` [PATCH V6 vfio 06/10] vfio/mlx5: Init QP based resources for dirty tracking Yishai Hadas
2022-09-05 10:58 ` [PATCH V6 vfio 07/10] vfio/mlx5: Create and destroy page tracker object Yishai Hadas
2022-09-05 10:58 ` [PATCH V6 vfio 08/10] vfio/mlx5: Report dirty pages from tracker Yishai Hadas
2022-09-05 10:58 ` [PATCH V6 vfio 09/10] vfio/mlx5: Manage error scenarios on tracker Yishai Hadas
2022-09-05 10:58 ` [PATCH V6 vfio 10/10] vfio/mlx5: Set the driver DMA logging callbacks Yishai Hadas
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=YxhoKWfnwiLqxyQX@unreal \
--to=leon@kernel.org \
--cc=alex.williamson@redhat.com \
--cc=cohuck@redhat.com \
--cc=jgg@nvidia.com \
--cc=joao.m.martins@oracle.com \
--cc=kevin.tian@intel.com \
--cc=kuba@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=maorg@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=saeedm@nvidia.com \
--cc=yishaih@nvidia.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;
as well as URLs for NNTP newsgroup(s).