From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Yan Zhao <yan.y.zhao@intel.com>, qemu-devel@nongnu.org
Cc: pbonzini@redhat.com, alex.williamson@redhat.com,
Xin Zeng <xin.zeng@intel.com>,
stefanha@redhat.com
Subject: Re: [PATCH v3 3/3] hw/vfio: let read-only flag take effect for mmap'd regions
Date: Tue, 14 Apr 2020 11:37:58 +0200 [thread overview]
Message-ID: <c2a0631b-4c2a-6b46-ec11-cd247b751dae@redhat.com> (raw)
In-Reply-To: <20200413063747.84753-1-yan.y.zhao@intel.com>
On 4/13/20 8:37 AM, Yan Zhao wrote:
> along side setting host page table to be read-only, the memory regions
> are also required to be read-only, so that when guest writes to the
> read-only & mmap'd regions, vmexits would happen and region write handlers
> are called.
>
> Signed-off-by: Yan Zhao <yan.y.zhao@intel.com>
> Signed-off-by: Xin Zeng <xin.zeng@intel.com>
> ---
> hw/vfio/common.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/hw/vfio/common.c b/hw/vfio/common.c
> index fd6ee1fe3e..fc7618e041 100644
> --- a/hw/vfio/common.c
> +++ b/hw/vfio/common.c
> @@ -977,6 +977,10 @@ int vfio_region_mmap(VFIORegion *region)
> name, region->mmaps[i].size,
> region->mmaps[i].mmap);
> g_free(name);
> +
> + if (!(region->flags & VFIO_REGION_INFO_FLAG_WRITE)) {
> + memory_region_set_readonly(®ion->mmaps[i].mem, true);
> + }
> memory_region_add_subregion(region->mem, region->mmaps[i].offset,
> ®ion->mmaps[i].mem);
>
>
Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
next prev parent reply other threads:[~2020-04-14 9:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-13 6:36 [PATCH v3 0/3] drop writes to read-only ram device & vfio regions Yan Zhao
2020-04-13 6:37 ` [PATCH v3 1/3] memory: drop guest writes to read-only ram device regions Yan Zhao
2020-04-14 9:35 ` Philippe Mathieu-Daudé
2020-04-15 8:19 ` Yan Zhao
2020-04-13 6:37 ` [PATCH v3 2/3] hw/vfio: drop guest writes to ro regions Yan Zhao
2020-04-14 9:34 ` Philippe Mathieu-Daudé
2020-04-15 8:19 ` Yan Zhao
2020-04-13 6:37 ` [PATCH v3 3/3] hw/vfio: let read-only flag take effect for mmap'd regions Yan Zhao
2020-04-14 9:37 ` Philippe Mathieu-Daudé [this message]
2020-04-15 8:19 ` 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=c2a0631b-4c2a-6b46-ec11-cd247b751dae@redhat.com \
--to=philmd@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=xin.zeng@intel.com \
--cc=yan.y.zhao@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).