From: Yan Zhao <yan.y.zhao@intel.com>
To: qemu-devel@nongnu.org
Cc: Yan Zhao <yan.y.zhao@intel.com>,
pbonzini@redhat.com, alex.williamson@redhat.com,
philmd@redhat.com, xin.zeng@intel.com
Subject: [PATCH v2 0/3] drop writes to read-only ram device & vfio regions
Date: Fri, 3 Apr 2020 17:08:23 +0000 [thread overview]
Message-ID: <20200403170823.20805-1-yan.y.zhao@intel.com> (raw)
In-Reply-To: <20200403165657.20566-1-yan.y.zhao@intel.com>
patch 1 modifies handler of ram device memory regions to drop guest writes
to read-only ram device memory regions
patch 2 modifies handler of non-mmap'd read-only vfio regions to drop guest
writes to those regions
patch 3 let mmap'd read-only vfio regions be able to generate vmexit for
guest write. so, without patch 1, host qemu would crash on guest write to
this read-only region. with patch 1, host qemu would drop the writes.
Changelog:
v2:
-split one big patches into smaller ones (Philippe)
-modify existing trace to record guest writes to read-only memory (Alex)
-modify vfio_region_write() to drop guest writes to non-mmap'd read-only
region (Alex)
Yan Zhao (3):
memory: drop guest writes to read-only ram device regions
hw/vfio: drop guest writes to ro regions
hw/vfio: let read-only flag take effect for mmap'd regions
hw/vfio/common.c | 12 +++++++++++-
hw/vfio/trace-events | 2 +-
memory.c | 6 +++++-
trace-events | 2 +-
4 files changed, 18 insertions(+), 4 deletions(-)
--
2.17.1
next prev parent reply other threads:[~2020-04-03 8:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-03 16:56 [PATCH v2 0/3] drop writes to read-only ram device & vfio regions Yan Zhao
2020-04-03 12:53 ` Peter Maydell
2020-04-07 3:15 ` Yan Zhao
2020-04-03 16:59 ` [PATCH v2 1/3] memory: drop guest writes to read-only ram device regions Yan Zhao
2020-04-03 17:00 ` [PATCH v2 2/3] hw/vfio: drop guest writes to ro regions Yan Zhao
2020-04-03 17:00 ` [PATCH v2 3/3] hw/vfio: let read-only flag take effect for mmap'd regions Yan Zhao
2020-04-03 17:08 ` Yan Zhao [this message]
2020-04-03 8:15 ` [PATCH v2 0/3] drop writes to read-only ram device & vfio regions Yan Zhao
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=20200403170823.20805-1-yan.y.zhao@intel.com \
--to=yan.y.zhao@intel.com \
--cc=alex.williamson@redhat.com \
--cc=pbonzini@redhat.com \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=xin.zeng@intel.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).