From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Yan Zhao <yan.y.zhao@intel.com>,
pbonzini@redhat.com, alex.williamson@redhat.com
Cc: xin.zeng@intel.com, qemu-devel@nongnu.org
Subject: Re: [PATCH v4 2/3] hw/vfio: drop guest writes to ro regions
Date: Fri, 17 Apr 2020 10:49:38 +0200 [thread overview]
Message-ID: <e37889d5-fdf1-c0a0-b651-aeaff8eaafd1@redhat.com> (raw)
In-Reply-To: <20200417074446.28573-1-yan.y.zhao@intel.com>
On 4/17/20 9:44 AM, Yan Zhao wrote:
> for vfio regions that are without write permission,
> drop guest writes to those regions.
>
> Cc: Philippe Mathieu-Daudé <philmd@redhat.com>
> Signed-off-by: Yan Zhao <yan.y.zhao@intel.com>
> Signed-off-by: Xin Zeng <xin.zeng@intel.com>
> ---
> hw/vfio/common.c | 12 ++++++++++--
> 1 file changed, 10 insertions(+), 2 deletions(-)
>
> diff --git a/hw/vfio/common.c b/hw/vfio/common.c
> index 0b3593b3c0..b6956a8098 100644
> --- a/hw/vfio/common.c
> +++ b/hw/vfio/common.c
> @@ -38,6 +38,7 @@
> #include "sysemu/reset.h"
> #include "trace.h"
> #include "qapi/error.h"
> +#include "qemu/log.h"
>
> VFIOGroupList vfio_group_list =
> QLIST_HEAD_INITIALIZER(vfio_group_list);
> @@ -190,6 +191,15 @@ void vfio_region_write(void *opaque, hwaddr addr,
> uint64_t qword;
> } buf;
>
> + trace_vfio_region_write(vbasedev->name, region->nr, addr, data, size);
> + if (!(region->flags & VFIO_REGION_INFO_FLAG_WRITE)) {
> + qemu_log_mask(LOG_GUEST_ERROR,
> + "Invalid write to read only vfio region 0x%"
> + HWADDR_PRIx" size %u\n", addr, size);
> +
> + return;
> + }
> +
> switch (size) {
> case 1:
> buf.byte = data;
> @@ -215,8 +225,6 @@ void vfio_region_write(void *opaque, hwaddr addr,
> addr, data, size);
> }
>
> - trace_vfio_region_write(vbasedev->name, region->nr, addr, data, size);
> -
> /*
> * A read or write to a BAR always signals an INTx EOI. This will
> * do nothing if not pending (including not in INTx mode). We assume
>
Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
prev parent reply other threads:[~2020-04-17 8:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-17 7:44 [PATCH v4 2/3] hw/vfio: drop guest writes to ro regions Yan Zhao
2020-04-17 8:49 ` Philippe Mathieu-Daudé [this message]
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=e37889d5-fdf1-c0a0-b651-aeaff8eaafd1@redhat.com \
--to=philmd@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--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).