From: Fabiano Rosas <farosas@suse.de>
To: Michael Tokarev <mjt@tls.msk.ru>,
Shameer Kolothum <shameerali.kolothum.thodi@huawei.com>,
qemu-devel@nongnu.org, peterx@redhat.com
Cc: linuxarm@huawei.com, zhangfei.gao@linaro.org,
qemu-stable <qemu-stable@nongnu.org>
Subject: Re: [PATCH] migration/multifd: Fix compile error caused by page_size usage
Date: Mon, 13 Jan 2025 09:55:44 -0300 [thread overview]
Message-ID: <87h662hnzj.fsf@suse.de> (raw)
In-Reply-To: <0198d019-1d50-4b94-ab15-9d2bdef183db@tls.msk.ru>
Michael Tokarev <mjt@tls.msk.ru> writes:
> 03.12.2024 15:49, Shameer Kolothum via wrote:
>> From Commit 90fa121c6c07 ("migration/multifd: Inline page_size and
>> page_count") onwards page_size is not part of MutiFD*Params but uses
>> an inline constant instead.
>>
>> However, it missed updating an old usage, causing a compile error.
>>
>> Fixes: 90fa121c6c07 ("migration/multifd: Inline page_size and page_count")
>> Signed-off-by: Shameer Kolothum <shameerali.kolothum.thodi@huawei.com>
>
> This looks like a qemu-stable material, is it not?
>
Yes.
> I wonder how come thie code hasn't been compiled since 90fa121c6c07.
The various pieces of code that support hardware accelerators in
migration all depend on specific hardware and libraries, so it's all
gated behind CONFIGs that are not enabled by default. We don't have
resources to test this, it's up to the people interested in that code to
check that it still works.
I have suggested we move more code out of the CONFIGs to minimize the
amount of untested code, but we've ended up deciding that since we need
help from people to maintain it anyway, it's not worth the extra work to
isolate the hw-specific code even more.
>
> /mjt
>
>> migration/multifd-uadk.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/migration/multifd-uadk.c b/migration/multifd-uadk.c
>> index 6e6a290ae9..6895c1f65a 100644
>> --- a/migration/multifd-uadk.c
>> +++ b/migration/multifd-uadk.c
>> @@ -169,7 +169,7 @@ static int multifd_uadk_send_prepare(MultiFDSendParams *p, Error **errp)
>> .src_len = page_size,
>> .dst = buf,
>> /* Set dst_len to double the src in case compressed out >= page_size */
>> - .dst_len = p->page_size * 2,
>> + .dst_len = page_size * 2,
>> };
>>
>> if (uadk_data->handle) {
prev parent reply other threads:[~2025-01-13 12:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-03 12:49 [PATCH] migration/multifd: Fix compile error caused by page_size usage Shameer Kolothum via
2024-12-03 13:17 ` Fabiano Rosas
2024-12-03 17:31 ` Peter Xu
2024-12-03 17:59 ` Fabiano Rosas
2025-01-12 13:04 ` Michael Tokarev
2025-01-13 12:55 ` Fabiano Rosas [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=87h662hnzj.fsf@suse.de \
--to=farosas@suse.de \
--cc=linuxarm@huawei.com \
--cc=mjt@tls.msk.ru \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@nongnu.org \
--cc=shameerali.kolothum.thodi@huawei.com \
--cc=zhangfei.gao@linaro.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).