From: Liu Sheng <liusheng@linux.vnet.ibm.com>
To: kvm@vger.kernel.org
Cc: aliguori@us.ibm.com, mtosatti@redhat.com, qemu-devel@nongnu.org,
xiaoguangrong@linux.vnet.ibm.com, avi@redhat.com,
Liu Sheng <liusheng@linux.vnet.ibm.com>
Subject: [Qemu-devel] [PATCH 0/3] support kvm readonly memory slot in qemu
Date: Fri, 7 Sep 2012 16:26:26 +0800 [thread overview]
Message-ID: <1347006389-543-1-git-send-email-liusheng@linux.vnet.ibm.com> (raw)
This patch set make the readonly memory in qemu really readonly, using
readonly memory slots feature in kvm, to make qemu-kvm safer. Memory
regions with readonly property would be plug into kvm as readonly memory
slots.
This patch set depends on the last patch "Introduce write_readonly_mem
in mmio-exit-info to indicate this exit is caused by write access on
readonly memslot" http://marc.info/?l=linux-kernel&m=134563967500539&w=2
of readonly memory slots in kvm", which has not been accepted yet.
Liu Sheng (3):
set the readonly property of rom memory region in pc
update kvm related the head file from kernel
support readonly memory feature in qemu
hw/pc.c | 1 +
hw/pci.c | 1 +
kvm-all.c | 47 ++++++++++++++++++++++++++++++++----------
linux-headers/asm-x86/kvm.h | 1 +
linux-headers/linux/kvm.h | 16 +++++++++++--
5 files changed, 52 insertions(+), 14 deletions(-)
--
1.7.7.6
next reply other threads:[~2012-09-07 8:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-07 8:26 Liu Sheng [this message]
2012-09-07 8:26 ` [Qemu-devel] [PATCH 1/3] set the readonly property of rom memory region in pc Liu Sheng
2012-09-07 8:26 ` [Qemu-devel] [PATCH 2/3] update kvm related the head file from kernel Liu Sheng
2012-09-07 8:49 ` Jan Kiszka
2012-09-07 9:39 ` Xiao Guangrong
2012-09-07 10:17 ` Jan Kiszka
2012-09-07 8:26 ` [Qemu-devel] [PATCH 3/3] support readonly memory feature in qemu Liu Sheng
2012-09-07 8:50 ` Jan Kiszka
2012-09-09 15:45 ` Avi Kivity
2012-09-10 9:25 ` Jan Kiszka
2012-09-11 3:02 ` Kevin O'Connor
2012-09-11 15:31 ` Jan Kiszka
2012-09-11 16:15 ` Anthony Liguori
2012-09-11 16:33 ` Jan Kiszka
2012-09-12 0:01 ` Kevin O'Connor
2012-09-09 15:42 ` Avi Kivity
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=1347006389-543-1-git-send-email-liusheng@linux.vnet.ibm.com \
--to=liusheng@linux.vnet.ibm.com \
--cc=aliguori@us.ibm.com \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=xiaoguangrong@linux.vnet.ibm.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).