From: Jan Beulich <jbeulich@suse.com>
To: Andrii Sultanov <sultanovandriy@gmail.com>
Cc: "Andrew Cooper" <andrew.cooper3@citrix.com>,
"Roger Pau Monné" <roger.pau@citrix.com>,
xen-devel@lists.xenproject.org
Subject: Re: [PATCH v2 2/3] drivers: Change find_iommu_for_device function to take pci_sbdf_t, simplify code
Date: Mon, 17 Mar 2025 17:07:25 +0100 [thread overview]
Message-ID: <b33592fb-8532-4580-92e0-5b60fa345e2f@suse.com> (raw)
In-Reply-To: <47e9f0a75a8bce85af0e53c06c95c25b0a061e3e.1742063500.git.sultanovandriy@gmail.com>
On 16.03.2025 11:08, Andrii Sultanov wrote:
> Following a similar change to amd_iommu struct, change the
> find_iommu_for_device function to take pci_sbdf_t as a single parameter.
> This avoids splitting a single argument into two registers in the majority
> of cases.
>
> Bloat-o-meter reports (on top of the first patch in the series):
> add/remove: 0/0 grow/shrink: 11/13 up/down: 90/-154 (-64)
> Function old new delta
> amd_iommu_get_supported_ivhd_type 54 86 +32
> parse_ivrs_table 3955 3966 +11
> amd_iommu_assign_device 271 282 +11
> __mon_lengths 2928 2936 +8
> update_intremap_entry_from_msi_msg 859 864 +5
> iov_supports_xt 270 275 +5
> amd_setup_hpet_msi 232 237 +5
> amd_iommu_domain_destroy 43 48 +5
> find_iommu_for_device 242 246 +4
> amd_iommu_ioapic_update_ire 572 575 +3
> allocate_domain_resources 82 83 +1
> amd_iommu_read_ioapic_from_ire 347 344 -3
> reassign_device 843 838 -5
> amd_iommu_remove_device 352 347 -5
> amd_iommu_get_reserved_device_memory 524 519 -5
> amd_iommu_flush_iotlb 359 354 -5
> amd_iommu_add_device 844 839 -5
> amd_iommu_setup_domain_device 1478 1472 -6
> build_info 752 744 -8
> amd_iommu_detect_one_acpi 886 876 -10
> register_range_for_device 297 281 -16
> amd_iommu_msi_msg_update_ire 472 448 -24
> parse_ivmd_block 1339 1312 -27
> _hvm_dpci_msi_eoi 168 133 -35
>
> Signed-off-by: Andrii Sultanov <sultanovandriy@gmail.com>
>
> ---
>> This avoids splitting a single argument into two registers
> And adds a few conversions into a pci_sbdf_t... these are addressed further
> in the series. - not part of the commit message in case said commit isn't taken.
What is "said commit" here? Everything done in a patch should be in the
commit message. If parts are later dropped, the commit message would need
refining. With the commit message amended (assuming I guessed correctly
that this is about a few secondary changes done here):
Acked-by: Jan Beulich <jbeulich@suse.com>
Jan
next prev parent reply other threads:[~2025-03-17 16:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-16 10:08 [PATCH v2 0/3] drivers: Simplify handling of pci_sbdf_t in passthrough/amd Andrii Sultanov
2025-03-16 10:08 ` [PATCH v2 1/3] drivers: Change amd_iommu struct to contain pci_sbdf_t, simplify code Andrii Sultanov
2025-03-17 15:55 ` Jan Beulich
2025-03-16 10:08 ` [PATCH v2 2/3] drivers: Change find_iommu_for_device function to take " Andrii Sultanov
2025-03-17 16:07 ` Jan Beulich [this message]
2025-03-16 10:08 ` [PATCH v2 3/3] drivers: Make ioapic_sbdf and hpet_sbdf contain pci_sbdf_t Andrii Sultanov
2025-03-17 16:17 ` Jan Beulich
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=b33592fb-8532-4580-92e0-5b60fa345e2f@suse.com \
--to=jbeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=roger.pau@citrix.com \
--cc=sultanovandriy@gmail.com \
--cc=xen-devel@lists.xenproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.