From: Juan Quintela <quintela@redhat.com>
To: ling xu <ling1.xu@intel.com>
Cc: qemu-devel@nongnu.org, dgilbert@redhat.com
Subject: Re: [PATCH v3 0/2] This patch updates runtime check of AVX512
Date: Mon, 08 Aug 2022 13:54:25 +0200 [thread overview]
Message-ID: <87wnbjlzm6.fsf@secure.mitica> (raw)
In-Reply-To: <20220808074837.1484760-1-ling1.xu@intel.com> (ling xu's message of "Mon, 8 Aug 2022 15:48:35 +0800")
ling xu <ling1.xu@intel.com> wrote:
> This patch updates runtime check of AVX512 and update avx512 support for
> xbzrle_encode_buffer function to accelerate xbzrle encoding speed.
>
> The runtime check is updated in meson.build and meson_options.txt.
>
> The updated AVX512 algorithm is provided in ram.c, xbzrle.c and
> xbzrle.h.
>
> The test code is provided in test-xbzrle.c.
>
> Previous discussion is refered below:
> https://www.mail-archive.com/qemu-devel@nongnu.org/msg903520.html
>
> ling xu (2):
> Update AVX512 support for xbzrle_encode_buffer function
> Test code for AVX512 support for xbzrle_encode_buffer
I think this v3 and previous v3 are identical except for mthe link to
the previous discussion.
Later, Juan.
next prev parent reply other threads:[~2022-08-08 11:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-08 7:48 [PATCH v3 0/2] This patch updates runtime check of AVX512 ling xu
2022-08-08 7:48 ` [PATCH v3 1/2] Update AVX512 support for xbzrle_encode_buffer function ling xu
2022-08-08 13:12 ` Juan Quintela
2022-08-09 7:51 ` Xu, Ling1
2022-08-09 18:25 ` Richard Henderson
2022-08-11 7:23 ` Xu, Ling1
2022-08-09 18:41 ` Richard Henderson
2022-08-08 7:48 ` [PATCH v3 2/2] Test code for AVX512 support for xbzrle_encode_buffer ling xu
2022-08-08 8:08 ` Thomas Huth
2022-08-08 8:30 ` Xu, Ling1
2022-08-09 18:30 ` Richard Henderson
2022-08-08 11:54 ` Juan Quintela [this message]
2022-08-09 1:19 ` [PATCH v3 0/2] This patch updates runtime check of AVX512 Xu, Ling1
-- strict thread matches above, loose matches on Subject: below --
2022-08-08 7:34 ling xu
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=87wnbjlzm6.fsf@secure.mitica \
--to=quintela@redhat.com \
--cc=dgilbert@redhat.com \
--cc=ling1.xu@intel.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 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.