From: Ahmed Abd El Mawgood <ahmedsoliman0x666@gmail.com>
To: kvm@vger.kernel.org,
Kernel Hardening <kernel-hardening@lists.openwall.com>,
virtualization@lists.linux-foundation.org,
linux-doc@vger.kernel.org, x86@kernel.org,
xen-devel@lists.xensource.com
Cc: Paolo Bonzini <pbonzini@redhat.com>,
rkrcmar@redhat.com, nathan Corbet <corbet@lwn.net>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
hpa@zytor.com, Kees Cook <keescook@chromium.org>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
David Hildenbrand <david@redhat.com>,
Boris Lukashev <blukashev@sempervictus.com>,
David Vrabel <david.vrabel@nutanix.com>,
nigel.edwards@hpe.com, Rik van Riel <riel@surriel.com>
Subject: Memory Read Only Enforcement: VMM assisted kernel rootkit mitigation for KVM V4
Date: Sat, 21 Jul 2018 01:31:27 +0200 [thread overview]
Message-ID: <20180720233130.14129-1-ahmedsoliman0x666@gmail.com> (raw)
Here is change log from V3 To V4:
- Fixing spelling/grammar mistakes suggested by Randy Dunlap
- Changing the hypercall interface to be able to process multiple pages
per one hypercall also suggested by Randy Dunlap. It turns out that
this will save lots of vmexist/memory slot flushes when protecting many
pages.
[PATCH RFC V4 1/3] KVM: X86: Memory ROE documentation
[PATCH RFC V4 2/3] KVM: X86: Adding arbitrary data pointer in kvm memslot iterator functions
[PATCH RFC V4 3/3] KVM: X86: Adding skeleton for Memory ROE
Summary:
Documentation/virtual/kvm/hypercalls.txt | 14 ++++
arch/x86/include/asm/kvm_host.h | 11 ++-
arch/x86/kvm/Kconfig | 7 ++
arch/x86/kvm/mmu.c | 127 ++++++++++++++++++++++---------
arch/x86/kvm/x86.c | 104 ++++++++++++++++++++++++-
include/linux/kvm_host.h | 3 +
include/uapi/linux/kvm_para.h | 1 +
virt/kvm/kvm_main.c | 29 ++++++-
8 files changed, 254 insertions(+), 42 deletions(-)
--
To unsubscribe from this list: send the line "unsubscribe linux-doc" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2018-07-20 23:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-20 23:31 Ahmed Abd El Mawgood [this message]
2018-07-20 23:31 ` [PATCH RFC V4 1/3] KVM: X86: Memory ROE documentation Ahmed Abd El Mawgood
2018-07-20 23:31 ` [PATCH RFC V4 2/3] KVM: X86: Adding arbitrary data pointer in kvm memslot iterator functions Ahmed Abd El Mawgood
2018-07-20 23:31 ` [PATCH RFC V4 3/3] KVM: X86: Adding skeleton for Memory ROE Ahmed Abd El Mawgood
2018-07-25 9:36 ` David Hildenbrand
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=20180720233130.14129-1-ahmedsoliman0x666@gmail.com \
--to=ahmedsoliman0x666@gmail.com \
--cc=ard.biesheuvel@linaro.org \
--cc=blukashev@sempervictus.com \
--cc=corbet@lwn.net \
--cc=david.vrabel@nutanix.com \
--cc=david@redhat.com \
--cc=hpa@zytor.com \
--cc=keescook@chromium.org \
--cc=kernel-hardening@lists.openwall.com \
--cc=kvm@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=nigel.edwards@hpe.com \
--cc=pbonzini@redhat.com \
--cc=riel@surriel.com \
--cc=rkrcmar@redhat.com \
--cc=tglx@linutronix.de \
--cc=virtualization@lists.linux-foundation.org \
--cc=x86@kernel.org \
--cc=xen-devel@lists.xensource.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).