From: Thomas Huth <thuth@redhat.com>
To: Juan Quintela <quintela@redhat.com>,
qemu-devel@nongnu.org, ling xu <ling1.xu@intel.com>
Cc: kvm@vger.kernel.org, "Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
"Daniel P. Berrangé" <berrange@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Cornelia Huck" <cohuck@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Zhou Zhao" <zhou.zhao@intel.com>,
"Jun Jin" <jun.i.jin@intel.com>
Subject: Re: [PULL 12/17] AVX512 support for xbzrle_encode_buffer
Date: Fri, 10 Feb 2023 08:43:15 +0100 [thread overview]
Message-ID: <31bc059c-dc8c-36ee-8288-209811d9ba98@redhat.com> (raw)
In-Reply-To: <20230209233426.37811-13-quintela@redhat.com>
On 10/02/2023 00.34, Juan Quintela wrote:
> From: ling xu <ling1.xu@intel.com>
>
> This commit is the same with [PATCH v6 1/2], and provides avx512 support for xbzrle_encode_buffer
> function to accelerate xbzrle encoding speed.
Hi!
Just a hint for future patches: Please don't put version information into
the patch description itself, this "PATCH v6 1/2" will now end up in the git
history without its context.
Information like that should go into cover letters or below the "---" marker
only.
Thanks,
Thomas
next prev parent reply other threads:[~2023-02-10 7:43 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-09 23:34 [PULL 00/17] Migration 20230209 patches Juan Quintela
2023-02-09 23:34 ` [PULL 01/17] migration: Remove spurious files Juan Quintela
2023-02-09 23:34 ` [PULL 02/17] multifd: cleanup the function multifd_channel_connect Juan Quintela
2023-02-09 23:34 ` [PULL 03/17] multifd: Remove some redundant code Juan Quintela
2023-02-09 23:34 ` [PULL 04/17] linux-headers: Update to v6.1 Juan Quintela
2023-02-09 23:34 ` [PULL 05/17] util/userfaultfd: Support /dev/userfaultfd Juan Quintela
2023-02-09 23:34 ` [PULL 06/17] migration: Simplify ram_find_and_save_block() Juan Quintela
2023-02-09 23:34 ` [PULL 07/17] migration: Make find_dirty_block() return a single parameter Juan Quintela
2023-02-09 23:34 ` [PULL 08/17] migration: Split ram_bytes_total_common() in two functions Juan Quintela
2023-02-09 23:34 ` [PULL 09/17] migration: Calculate ram size once Juan Quintela
2023-02-09 23:34 ` [PULL 10/17] migration: Make ram_save_target_page() a pointer Juan Quintela
2023-02-09 23:34 ` [PULL 11/17] migration: I messed state_pending_exact/estimate Juan Quintela
2023-02-09 23:34 ` [PULL 12/17] AVX512 support for xbzrle_encode_buffer Juan Quintela
2023-02-10 7:43 ` Thomas Huth [this message]
2023-02-09 23:34 ` [PULL 13/17] Update bench-code for addressing CI problem Juan Quintela
2023-02-09 23:34 ` [PULL 14/17] migration: Rework multi-channel checks on URI Juan Quintela
2023-02-09 23:34 ` [PULL 15/17] migration: Cleanup postcopy_preempt_setup() Juan Quintela
2023-02-09 23:34 ` [PULL 16/17] migration: Add a semaphore to count PONGs Juan Quintela
2023-02-09 23:34 ` [PULL 17/17] migration: Postpone postcopy preempt channel to be after main Juan Quintela
2023-02-10 13:36 ` [PULL 00/17] Migration 20230209 patches Peter Maydell
2023-02-10 14:21 ` Juan Quintela
2023-02-10 14:33 ` Peter Maydell
2023-02-10 16:13 ` Juan Quintela
2023-02-10 16:17 ` Peter Maydell
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=31bc059c-dc8c-36ee-8288-209811d9ba98@redhat.com \
--to=thuth@redhat.com \
--cc=berrange@redhat.com \
--cc=cohuck@redhat.com \
--cc=dgilbert@redhat.com \
--cc=jun.i.jin@intel.com \
--cc=kvm@vger.kernel.org \
--cc=ling1.xu@intel.com \
--cc=marcandre.lureau@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=zhou.zhao@intel.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).