From: Alex Williamson <alex.williamson@redhat.com>
To: Eric Auger <eric.auger@redhat.com>
Cc: cohuck@redhat.com, stefanb@linux.vnet.ibm.com,
qemu-devel@nongnu.org, david@gibson.dropbear.id.au,
eric.auger.pro@gmail.com
Subject: Re: [PATCH v2 2/2] hw/vfio/common: Silence ram device offset alignment error traces
Date: Wed, 19 Jan 2022 13:13:55 -0700 [thread overview]
Message-ID: <20220119131355.47bafabd.alex.williamson@redhat.com> (raw)
In-Reply-To: <20220118153306.282681-3-eric.auger@redhat.com>
On Tue, 18 Jan 2022 16:33:06 +0100
Eric Auger <eric.auger@redhat.com> wrote:
> Failing to DMA MAP a ram_device should not cause an error message.
> This is currently happening with the TPM CRB command region and
> this is causing confusion.
>
> We may want to keep the trace for debug purpose though.
>
> Signed-off-by: Eric Auger <eric.auger@redhat.com>
> Tested-by: Stefan Berger <stefanb@linux.ibm.com>
> ---
> hw/vfio/common.c | 15 ++++++++++++++-
> hw/vfio/trace-events | 1 +
> 2 files changed, 15 insertions(+), 1 deletion(-)
Thanks! Looks good to me.
Stefan, I can provide an ack here if you want to send a pull request
for both or likewise I can send a pull request with your ack on the
previous patch. I suppose the patches themselves are technically
independent if you want to split them. Whichever you prefer.
Acked-by: Alex Williamson <alex.williamson@redhat.com>
>
> diff --git a/hw/vfio/common.c b/hw/vfio/common.c
> index 080046e3f5..9caa560b07 100644
> --- a/hw/vfio/common.c
> +++ b/hw/vfio/common.c
> @@ -884,7 +884,20 @@ static void vfio_listener_region_add(MemoryListener *listener,
> if (unlikely((section->offset_within_address_space &
> ~qemu_real_host_page_mask) !=
> (section->offset_within_region & ~qemu_real_host_page_mask))) {
> - error_report("%s received unaligned region", __func__);
> + if (memory_region_is_ram_device(section->mr)) { /* just debug purpose */
> + trace_vfio_listener_region_add_bad_offset_alignment(
> + memory_region_name(section->mr),
> + section->offset_within_address_space,
> + section->offset_within_region, qemu_real_host_page_size);
> + } else { /* error case we don't want to be fatal */
> + error_report("%s received unaligned region %s iova=0x%"PRIx64
> + " offset_within_region=0x%"PRIx64
> + " qemu_real_host_page_mask=0x%"PRIx64,
> + __func__, memory_region_name(section->mr),
> + section->offset_within_address_space,
> + section->offset_within_region,
> + qemu_real_host_page_mask);
> + }
> return;
> }
>
> diff --git a/hw/vfio/trace-events b/hw/vfio/trace-events
> index 0ef1b5f4a6..ccd9d7610d 100644
> --- a/hw/vfio/trace-events
> +++ b/hw/vfio/trace-events
> @@ -100,6 +100,7 @@ vfio_listener_region_add_skip(uint64_t start, uint64_t end) "SKIPPING region_add
> vfio_spapr_group_attach(int groupfd, int tablefd) "Attached groupfd %d to liobn fd %d"
> vfio_listener_region_add_iommu(uint64_t start, uint64_t end) "region_add [iommu] 0x%"PRIx64" - 0x%"PRIx64
> vfio_listener_region_add_ram(uint64_t iova_start, uint64_t iova_end, void *vaddr) "region_add [ram] 0x%"PRIx64" - 0x%"PRIx64" [%p]"
> +vfio_listener_region_add_bad_offset_alignment(const char *name, uint64_t iova, uint64_t offset_within_region, uint64_t page_size) "Region \"%s\" @0x%"PRIx64", offset_within_region=0x%"PRIx64", qemu_real_host_page_mask=0x%"PRIx64 " cannot be mapped for DMA"
> vfio_listener_region_add_no_dma_map(const char *name, uint64_t iova, uint64_t size, uint64_t page_size) "Region \"%s\" 0x%"PRIx64" size=0x%"PRIx64" is not aligned to 0x%"PRIx64" and cannot be mapped for DMA"
> vfio_listener_region_del_skip(uint64_t start, uint64_t end) "SKIPPING region_del 0x%"PRIx64" - 0x%"PRIx64
> vfio_listener_region_del(uint64_t start, uint64_t end) "region_del 0x%"PRIx64" - 0x%"PRIx64
next prev parent reply other threads:[~2022-01-19 20:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-18 15:33 [PATCH v2 0/2] TPM-CRB: Remove spurious error report when used with VFIO Eric Auger
2022-01-18 15:33 ` [PATCH v2 1/2] tpm: CRB: Use ram_device for "tpm-crb-cmd" region Eric Auger
2022-01-19 22:46 ` Philippe Mathieu-Daudé via
2022-01-19 23:13 ` Alex Williamson
2022-01-18 15:33 ` [PATCH v2 2/2] hw/vfio/common: Silence ram device offset alignment error traces Eric Auger
2022-01-19 20:13 ` Alex Williamson [this message]
2022-01-19 20:40 ` Stefan Berger
2022-01-19 20:40 ` [PATCH v2 0/2] TPM-CRB: Remove spurious error report when used with VFIO Stefan Berger
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=20220119131355.47bafabd.alex.williamson@redhat.com \
--to=alex.williamson@redhat.com \
--cc=cohuck@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=eric.auger.pro@gmail.com \
--cc=eric.auger@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanb@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).