From: Yang Weijiang <weijiang.yang@intel.com>
To: pbonzini@redhat.com
Cc: kvm@vger.kernel.org
Subject: Migration for SPP(Sub-Page Protection) bitmaps
Date: Wed, 17 Apr 2019 17:59:18 +0800 [thread overview]
Message-ID: <20190417095918.GA15982@local-michael-cet-test.sh.intel.com> (raw)
Hi, Paolo,
I'm working on migration support for SPP(Sub-Page Protection) feature,
the previous patch set is here:
https://lkml.org/lkml/2018/11/30/574, basically it's used to protect
128-byte subpages within a normal 4KB page.
but I'm not sure whether we need to add migration support for such kind of feature.
Currently, my solution is to store the SPP bitmaps to destination KVM, when
there's EPT violation, search the bitmap mapping table to check if the
guest page needs to be protected.
Another solution is to setup EPT table directly at the end of migration.
Do you have perferred approach?
Thanks for your comments!
next reply other threads:[~2019-04-18 3:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-17 9:59 Yang Weijiang [this message]
2019-04-26 8:06 ` Migration for SPP(Sub-Page Protection) bitmaps Paolo Bonzini
2019-04-26 8:57 ` Yang Weijiang
2019-04-27 7:37 ` Paolo Bonzini
2019-04-28 2:31 ` Yang Weijiang
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=20190417095918.GA15982@local-michael-cet-test.sh.intel.com \
--to=weijiang.yang@intel.com \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.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