From: <vijayak@cavium.com>
To: qemu-arm@nongnu.org, peter.maydell@linaro.org, pbonzini@redhat.com
Cc: qemu-devel@nongnu.org, Prasun.Kapoor@cavium.com,
vijay.kilari@gmail.com,
Vijaya Kumar K <vijayak@caviumnetworks.com>
Subject: [Qemu-devel] [PATCH v3 0/1] ARM64: Live migration optimization
Date: Wed, 29 Jun 2016 14:17:08 +0530 [thread overview]
Message-ID: <1467190029-694-1-git-send-email-vijayak@cavium.com> (raw)
From: Vijaya Kumar K <vijayak@caviumnetworks.com>
To optimize Live migration time on ARM64 machine,
Neon instructions are used for Zero page checking.
With these changes, total migration time comes down
from 3.5 seconds to 2.9 seconds.
These patches are tested on top of (GICv3 live migration support)
https://lists.gnu.org/archive/html/qemu-devel/2015-10/msg05284.html
However there is no direct dependency on these patches.
v2 -> v3 changes:
- Dropped Thunderx specific patches(2) from this series. Will
be added on kernel exposing midr register to userspace.
- Used generic zero page checking function. Only macros
are updated.
v1 -> v2 changes:
----------------
- Dropped 'target-arm: Update page size for aarch64' patch.
- Each loop in zero buffer check function is reduced to
16 from 32.
- Replaced vorrq_u64 with '|' in Neon macros
- Renamed local variable to reflect 128 bit.
- Introduced new file cpuinfo.c to parse /proc/cpuinfo
- Added Thunderx specific patches to add prefetch in
zero buffer check function.
Vijay (1):
target-arm: Use Neon for zero checking
util/cutils.c | 7 +++++++
1 file changed, 7 insertions(+)
--
1.7.9.5
next reply other threads:[~2016-06-29 8:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-29 8:47 vijayak [this message]
2016-06-29 8:47 ` [Qemu-devel] [PATCH v3 1/1] target-arm: Use Neon for zero checking vijayak
2016-06-29 12:53 ` Paolo Bonzini
2016-06-30 13:45 ` Peter Maydell
2016-07-01 22:07 ` Richard Henderson
2016-07-02 9:42 ` Peter Maydell
2016-07-05 12:24 ` Vijay Kilari
2016-07-11 17:55 ` 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=1467190029-694-1-git-send-email-vijayak@cavium.com \
--to=vijayak@cavium.com \
--cc=Prasun.Kapoor@cavium.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=vijay.kilari@gmail.com \
--cc=vijayak@caviumnetworks.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).