From: Avihai Horon <avihaih@nvidia.com>
To: Joao Martins <joao.m.martins@oracle.com>, qemu-devel@nongnu.org
Cc: Alex Williamson <alex.williamson@redhat.com>,
Cedric Le Goater <clg@redhat.com>,
Yishai Hadas <yishaih@nvidia.com>,
Jason Gunthorpe <jgg@nvidia.com>,
Maor Gottlieb <maorg@nvidia.com>,
Kirti Wankhede <kwankhede@nvidia.com>,
Tarun Gupta <targupta@nvidia.com>
Subject: Re: [PATCH v4 06/14] vfio/common: Consolidate skip/invalid section into helper
Date: Tue, 7 Mar 2023 11:13:58 +0200 [thread overview]
Message-ID: <8ef23f46-a5c7-2723-42e3-6f5efa7f993d@nvidia.com> (raw)
In-Reply-To: <20230307020258.58215-7-joao.m.martins@oracle.com>
On 07/03/2023 4:02, Joao Martins wrote:
> External email: Use caution opening links or attachments
>
>
> The checks are replicated against region_add and region_del
> and will be soon added in another memory listener dedicated
> for dirty tracking.
>
> Move these into a new helper for avoid duplication.
>
> Signed-off-by: Joao Martins <joao.m.martins@oracle.com>
> Reviewed-by: Cédric Le Goater <clg@redhat.com>
> ---
> hw/vfio/common.c | 52 +++++++++++++++++++-----------------------------
> 1 file changed, 21 insertions(+), 31 deletions(-)
>
> diff --git a/hw/vfio/common.c b/hw/vfio/common.c
> index 99acb998eb14..54b4a4fc7daf 100644
> --- a/hw/vfio/common.c
> +++ b/hw/vfio/common.c
> @@ -933,23 +933,14 @@ static bool vfio_known_safe_misalignment(MemoryRegionSection *section)
> return true;
> }
>
> -static void vfio_listener_region_add(MemoryListener *listener,
> - MemoryRegionSection *section)
> +static bool vfio_listener_valid_section(MemoryRegionSection *section)
> {
> - VFIOContainer *container = container_of(listener, VFIOContainer, listener);
> - hwaddr iova, end;
> - Int128 llend, llsize;
> - void *vaddr;
> - int ret;
> - VFIOHostDMAWindow *hostwin;
> - Error *err = NULL;
> -
> if (vfio_listener_skipped_section(section)) {
> trace_vfio_listener_region_add_skip(
> section->offset_within_address_space,
> section->offset_within_address_space +
> int128_get64(int128_sub(section->size, int128_one())));
The original code uses two different traces depending on add or del --
trace_vfio_listener_region_{add,del}_skip.
Should we combine the two traces into a single trace? If the distinction
is important then maybe pass a flag or the caller name to indicate
whether it's add, del or dirty tracking update?
But other than that:
Reviewed-by: Avihai Horon <avihaih@nvidia.com>
Thanks.
> - return;
> + return false;
> }
>
> if (unlikely((section->offset_within_address_space &
> @@ -964,6 +955,24 @@ static void vfio_listener_region_add(MemoryListener *listener,
> section->offset_within_region,
> qemu_real_host_page_size());
> }
> + return false;
> + }
> +
> + return true;
> +}
> +
> +static void vfio_listener_region_add(MemoryListener *listener,
> + MemoryRegionSection *section)
> +{
> + VFIOContainer *container = container_of(listener, VFIOContainer, listener);
> + hwaddr iova, end;
> + Int128 llend, llsize;
> + void *vaddr;
> + int ret;
> + VFIOHostDMAWindow *hostwin;
> + Error *err = NULL;
> +
> + if (!vfio_listener_valid_section(section)) {
> return;
> }
>
> @@ -1182,26 +1191,7 @@ static void vfio_listener_region_del(MemoryListener *listener,
> int ret;
> bool try_unmap = true;
>
> - if (vfio_listener_skipped_section(section)) {
> - trace_vfio_listener_region_del_skip(
> - section->offset_within_address_space,
> - section->offset_within_address_space +
> - int128_get64(int128_sub(section->size, int128_one())));
> - return;
> - }
> -
> - if (unlikely((section->offset_within_address_space &
> - ~qemu_real_host_page_mask()) !=
> - (section->offset_within_region & ~qemu_real_host_page_mask()))) {
> - if (!vfio_known_safe_misalignment(section)) {
> - error_report("%s received unaligned region %s iova=0x%"PRIx64
> - " offset_within_region=0x%"PRIx64
> - " qemu_real_host_page_size=0x%"PRIxPTR,
> - __func__, memory_region_name(section->mr),
> - section->offset_within_address_space,
> - section->offset_within_region,
> - qemu_real_host_page_size());
> - }
> + if (!vfio_listener_valid_section(section)) {
> return;
> }
>
> --
> 2.17.2
>
next prev parent reply other threads:[~2023-03-07 9:15 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-07 2:02 [PATCH v4 00/14] vfio/migration: Device dirty page tracking Joao Martins
2023-03-07 2:02 ` [PATCH v4 01/14] vfio/common: Fix error reporting in vfio_get_dirty_bitmap() Joao Martins
2023-03-07 2:02 ` [PATCH v4 02/14] vfio/common: Fix wrong %m usages Joao Martins
2023-03-07 2:02 ` [PATCH v4 03/14] vfio/common: Abort migration if dirty log start/stop/sync fails Joao Martins
2023-03-07 2:02 ` [PATCH v4 04/14] vfio/common: Add VFIOBitmap and alloc function Joao Martins
2023-03-07 8:49 ` Avihai Horon
2023-03-07 10:17 ` Joao Martins
2023-03-07 2:02 ` [PATCH v4 05/14] vfio/common: Add helper to validate iova/end against hostwin Joao Martins
2023-03-07 8:57 ` Avihai Horon
2023-03-07 10:18 ` Joao Martins
2023-03-07 2:02 ` [PATCH v4 06/14] vfio/common: Consolidate skip/invalid section into helper Joao Martins
2023-03-07 9:13 ` Avihai Horon [this message]
2023-03-07 9:47 ` Cédric Le Goater
2023-03-07 10:22 ` Joao Martins
2023-03-07 11:00 ` Joao Martins
2023-03-07 11:07 ` Cédric Le Goater
2023-03-07 10:21 ` Joao Martins
2023-03-07 2:02 ` [PATCH v4 07/14] vfio/common: Add helper to consolidate iova/end calculation Joao Martins
2023-03-07 2:40 ` Alex Williamson
2023-03-07 10:11 ` Joao Martins
2023-03-07 9:52 ` Avihai Horon
2023-03-07 10:26 ` Joao Martins
2023-03-07 2:02 ` [PATCH v4 08/14] vfio/common: Record DMA mapped IOVA ranges Joao Martins
2023-03-07 2:57 ` Alex Williamson
2023-03-07 10:08 ` Cédric Le Goater
2023-03-07 10:30 ` Joao Martins
2023-03-07 10:16 ` Joao Martins
2023-03-07 12:13 ` Joao Martins
2023-03-07 2:02 ` [PATCH v4 09/14] vfio/common: Add device dirty page tracking start/stop Joao Martins
2023-03-07 10:14 ` Avihai Horon
2023-03-07 10:31 ` Joao Martins
2023-03-07 2:02 ` [PATCH v4 10/14] vfio/common: Extract code from vfio_get_dirty_bitmap() to new function Joao Martins
2023-03-07 2:02 ` [PATCH v4 11/14] vfio/common: Add device dirty page bitmap sync Joao Martins
2023-03-07 2:02 ` [PATCH v4 12/14] vfio/migration: Block migration with vIOMMU Joao Martins
2023-03-07 10:22 ` Cédric Le Goater
2023-03-07 10:31 ` Joao Martins
2023-03-07 2:02 ` [PATCH v4 13/14] vfio/migration: Query device dirty page tracking support Joao Martins
2023-03-07 2:02 ` [PATCH v4 14/14] docs/devel: Document VFIO device dirty page tracking Joao Martins
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=8ef23f46-a5c7-2723-42e3-6f5efa7f993d@nvidia.com \
--to=avihaih@nvidia.com \
--cc=alex.williamson@redhat.com \
--cc=clg@redhat.com \
--cc=jgg@nvidia.com \
--cc=joao.m.martins@oracle.com \
--cc=kwankhede@nvidia.com \
--cc=maorg@nvidia.com \
--cc=qemu-devel@nongnu.org \
--cc=targupta@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).