qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Cédric Le Goater" <clg@redhat.com>
To: Joao Martins <joao.m.martins@oracle.com>, qemu-devel@nongnu.org
Cc: Alex Williamson <alex.williamson@redhat.com>
Subject: Re: [PATCH] vfio/pci: Drop debug comentary from x-device-dirty-page-tracking
Date: Tue, 11 Mar 2025 19:00:51 +0100	[thread overview]
Message-ID: <54e1e265-6c18-4ad5-a2e0-384e35965b49@redhat.com> (raw)
In-Reply-To: <20250311174807.79825-1-joao.m.martins@oracle.com>

On 3/11/25 18:48, Joao Martins wrote:
> The intent behind the x-device-dirty-page-tracking option is twofold:
> 
> 1) development/testing in the presence of VFs with VF dirty page tracking
> 
> 2) deliberately choosing platform dirty tracker over the VF one.
> 
> Item 2) scenario is useful when VF dirty tracker is not as fast as
> IOMMU, or there's some limitations around it (e.g. number of them is
> limited; aggregated address space under tracking is limited),
> efficiency/scalability (e.g. 1 pagetable in IOMMU dirty tracker to scan
> vs N VFs) or just troubleshooting. Given item 2 it is not restricted to
> debugging, hence drop the debug parenthesis from the option description.
> 
> Signed-off-by: Joao Martins <joao.m.martins@oracle.com



Reviewed-by: Cédric Le Goater <clg@redhat.com>

Thanks,

C.


> ---
>   hw/vfio/pci.c | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/hw/vfio/pci.c b/hw/vfio/pci.c
> index 64629c13b6fb..3496a0b6b099 100644
> --- a/hw/vfio/pci.c
> +++ b/hw/vfio/pci.c
> @@ -3531,7 +3531,7 @@ static void vfio_pci_dev_class_init(ObjectClass *klass, void *data)
>       object_class_property_set_description(klass, /* 9.1 */
>                                             "x-device-dirty-page-tracking",
>                                             "Disable device dirty page tracking and use "
> -                                          "container-based dirty page tracking (DEBUG)");
> +                                          "container-based dirty page tracking");
>       object_class_property_set_description(klass, /* 9.1 */
>                                             "migration-events",
>                                             "Emit VFIO migration QAPI event when a VFIO device "



      reply	other threads:[~2025-03-11 18:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-11 17:48 [PATCH] vfio/pci: Drop debug comentary from x-device-dirty-page-tracking Joao Martins
2025-03-11 18:00 ` Cédric Le Goater [this message]

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=54e1e265-6c18-4ad5-a2e0-384e35965b49@redhat.com \
    --to=clg@redhat.com \
    --cc=alex.williamson@redhat.com \
    --cc=joao.m.martins@oracle.com \
    --cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).