From: Haibo Xu <haibo.xu@linaro.org>
To: dgilbert@redhat.com, quintela@redhat.com, drjones@redhat.com,
richard.henderson@linaro.org
Cc: peter.maydell@linaro.org, qemu-arm@nongnu.org, philmd@redhat.com,
qemu-devel@nongnu.org, Haibo Xu <haibo.xu@linaro.org>
Subject: [RFC PATCH v2 0/5] target/arm: Add MTE support to KVM guest
Date: Wed, 17 Mar 2021 09:28:19 +0000 [thread overview]
Message-ID: <cover.1615972140.git.haibo.xu@linaro.org> (raw)
This version is rebased against kernel patches v10, and only header
files are updated since v1[1].
This series add support for MTE(Memory Tagging Extension)[2]
in KVM guest. It's based on Steven Price's kernel KVM patches
v10[3], and has been tested to ensure that test case[4] can be
passed in a KVM guest. Basic pre-copy migration test also passed
between two MTE enabled kvm guest.
This is a RFC patch series becuase:
(1) Need to add some arm MTE specific codes to the ram migration
loop. There may be better way to do that in a more abstract way.
(2) Only pre-copy migration is supported and tested currently,
post-copy as well as compress/zero page migration are still WIP.
All kinds of feedbacks are very welcomed, especially for the migration
support.
Note:
(1) To support MTE migration, tags for one page are appended to
the page data during ram save iteration which make it easier
to sync the page data and tags.
[1] https://lore.kernel.org/qemu-devel/cover.1612747873.git.haibo.xu@linaro.org/
[2] https://community.arm.com/developer/ip-products/processors/b/
processors-ip-blog/posts/enhancing-memory-safety
[3] https://patchew.org/QEMU/20210312151902.17853-1-steven.price@arm.com/
[4] https://elixir.bootlin.com/linux/latest/source/Documentation/
arm64/memory-tagging-extension.rst
Haibo Xu (5):
Update Linux headers with new MTE support
Add basic MTE support to KVM guest
Add APIs to get/set MTE tags
Add migration support for KVM guest with MTE
Enable the MTE support for KVM guest
hw/arm/virt.c | 44 +++++++++++++-------
include/hw/arm/virt.h | 2 +
include/migration/misc.h | 1 +
linux-headers/linux/kvm.h | 16 ++++++++
migration/ram.c | 86 ++++++++++++++++++++++++++++++++++++++-
target/arm/cpu.c | 2 +-
target/arm/kvm.c | 9 ++++
target/arm/kvm64.c | 31 ++++++++++++++
target/arm/kvm_arm.h | 2 +
9 files changed, 177 insertions(+), 16 deletions(-)
--
2.17.1
next reply other threads:[~2021-03-17 9:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-17 9:28 Haibo Xu [this message]
2021-03-17 9:28 ` [RFC PATCH v2 1/5] Update Linux headers with new MTE support Haibo Xu
2021-03-17 9:28 ` [RFC PATCH v2 2/5] Add basic MTE support to KVM guest Haibo Xu
2021-03-17 9:28 ` [RFC PATCH v2 3/5] Add APIs to get/set MTE tags Haibo Xu
2021-03-25 12:18 ` Juan Quintela
2021-04-01 13:12 ` Haibo Xu
2021-03-17 9:28 ` [RFC PATCH v2 4/5] Add migration support for KVM guest with MTE Haibo Xu
2021-03-17 20:11 ` Dr. David Alan Gilbert
2021-03-18 6:38 ` Haibo Xu
2021-03-25 19:37 ` Dr. David Alan Gilbert
2021-04-01 13:33 ` Haibo Xu
2021-03-25 15:37 ` Juan Quintela
2021-04-01 13:26 ` Haibo Xu
2021-03-17 9:28 ` [RFC PATCH v2 5/5] Enable the MTE support for KVM guest Haibo Xu
2021-03-25 12:40 ` Juan Quintela
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=cover.1615972140.git.haibo.xu@linaro.org \
--to=haibo.xu@linaro.org \
--cc=dgilbert@redhat.com \
--cc=drjones@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@redhat.com \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=richard.henderson@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 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.