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>,
	Alex Williamson <alex.williamson@redhat.com>,
	Kirti Wankhede <kwankhede@nvidia.com>
Cc: qemu-devel@nongnu.org, Tony Krowiak <akrowiak@linux.ibm.com>,
	Eric Farman <farman@linux.ibm.com>,
	Eric Auger <eric.auger@redhat.com>,
	tomitamoeko@gmail.com, corvin.koehne@gmail.com
Subject: Re: [PATCH v2] vfio: Add property documentation
Date: Wed, 5 Mar 2025 14:13:38 +0100	[thread overview]
Message-ID: <8ac4f034-3e68-4c8a-9a63-9eeacc0de113@redhat.com> (raw)
In-Reply-To: <6985a62f-a091-4087-887c-361570170ef6@oracle.com>

Joao,

On 3/5/25 12:16, Joao Martins wrote:
> On 14/02/2025 13:05, Cédric Le Goater wrote:
>> +Kirti
>> +Joao
>>
>> On 2/13/25 22:45, Alex Williamson wrote:
>>>> +
>>>> +    /*
>>>> +     * Migration support
>>>> +     */
>>>> +    object_class_property_set_description(klass, /* 5.2 */
>>>> +                                          "x-pre-copy-dirty-page-tracking",
>>>> +                                          "Disable dirty pages tracking
>>>> during iterative phase");
>>>> +    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");
>>> These are really debug as well, right?  They just happen to be
>>> migration related debug.
>>
>> I suppose so. I would rather keep them under the migration topic
>> and add 'debug' in the comment.
>>
>> Changes :
>>
>>    commit bb0990d1740f ("vfio: Change default dirty pages tracking behavior
>> during migration")
>>    commit 30b916778517 ("vfio/common: Allow disabling device dirty page tracking")
>>
>> do not explicitly explain why these properties are useful in any way.
>>
>> Kirti, Joao, could you ?
> 
> Sorry for the extreme delay but I was out travelling for the past 3 weeks for
> vacation and work.
> 
> The property is marked as x- but my intent was both debug/testing and to have
> something that allows me to select the dirty tracker between device vs platform
> dirty tracker if something is wrong with say VF dirty tracker or if there's some
> limitations around it. These days we actually use it a lot as my default to have
> IOMMU dirty tracker in use. I wouldn't label it exclusively as '(debug)' just yet.
> 
> The precopy option might be to avoid dirty tracking at all and it's generally
> useful when you don't have dirty tracking at all or say snapshots or 'offline
> migration'. But I have never seen real use of it, or need for that matter,
> except the early days of VFIO migration during testing.

Could you please send a patch on top of :

   https://lore.kernel.org/qemu-devel/20250217173455.449983-1-clg@redhat.com/

This would be great to keep the information in the git history.

Thanks,

C.




  reply	other threads:[~2025-03-05 13:14 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-13 13:50 [PATCH v2] vfio: Add property documentation Cédric Le Goater
2025-02-13 14:17 ` BALATON Zoltan
2025-02-13 14:48   ` Cédric Le Goater
2025-02-13 14:45 ` Eric Auger
2025-02-13 14:49   ` Cédric Le Goater
2025-02-13 21:45 ` Alex Williamson
2025-02-14  9:31   ` Corvin Köhne
2025-02-14 11:03     ` Tomita Moeko
2025-02-14 13:05   ` Cédric Le Goater
2025-03-05 11:16     ` Joao Martins
2025-03-05 13:13       ` Cédric Le Goater [this message]
2025-03-11 16:44         ` Joao Martins
2025-03-11 17:43           ` Cédric Le Goater
2025-03-11 17:49             ` Joao Martins
2025-02-14 13:54   ` Cédric Le Goater

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=8ac4f034-3e68-4c8a-9a63-9eeacc0de113@redhat.com \
    --to=clg@redhat.com \
    --cc=akrowiak@linux.ibm.com \
    --cc=alex.williamson@redhat.com \
    --cc=corvin.koehne@gmail.com \
    --cc=eric.auger@redhat.com \
    --cc=farman@linux.ibm.com \
    --cc=joao.m.martins@oracle.com \
    --cc=kwankhede@nvidia.com \
    --cc=qemu-devel@nongnu.org \
    --cc=tomitamoeko@gmail.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).