From: Laurent Vivier <lvivier@redhat.com>
To: qemu-devel@nongnu.org
Cc: jasowang@redhat.com, eric.auger@redhat.com,
"Peter Xu" <peterx@redhat.com>,
"Stefan Berger" <stefanb@linux.vnet.ibm.com>,
mst@redhat.com, "Philippe Mathieu-Daudé" <philmd@linaro.org>,
"David Hildenbrand" <david@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
marcandre.lureau@redhat.com, peter.maydell@linaro.org,
"Laurent Vivier" <lvivier@redhat.com>
Subject: [PATCH v2 0/1] vhost-vdpa: skip TPM CRB memory section
Date: Tue, 4 Jul 2023 09:19:30 +0200 [thread overview]
Message-ID: <20230704071931.575888-1-lvivier@redhat.com> (raw)
An error is reported for vhost-vdpa case:
qemu-kvm: vhost_vdpa_listener_region_add received unaligned region
Marc-André has proposed a fix to this problem by skipping
the memory region owned by the TPM CRB but it seems more generic
to skip not aligned memory.
v1 of this series proposed to set the RAM_PROTECTED flag for the
TPM CRB memory region.
v2:
- do not introduce special case for TPM CRB
- do not set RAM_PROTECTED flag for TPM CRB
- remove error_report() and replace it with a trace
For the previous discussions, see
https://lists.nongnu.org/archive/html/qemu-devel/2022-11/msg03670.html
and from Eric for VFIO:
https://lore.kernel.org/all/20220506132510.1847942-1-eric.auger@redhat.com/
https://lore.kernel.org/all/20220524091405.416256-1-eric.auger@redhat.com/
Bug: https://bugzilla.redhat.com/show_bug.cgi?id=2141965
Thanks,
Laurent
Laurent Vivier (1):
vhost-vdpa: mute unaligned memory error report
hw/virtio/trace-events | 2 ++
hw/virtio/vhost-vdpa.c | 8 ++++++--
2 files changed, 8 insertions(+), 2 deletions(-)
--
2.41.0
next reply other threads:[~2023-07-04 7:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-04 7:19 Laurent Vivier [this message]
2023-07-04 7:19 ` [PATCH v2 1/1] vhost-vdpa: mute unaligned memory error report Laurent Vivier
2023-07-04 7:25 ` David Hildenbrand
2023-07-04 7:52 ` Laurent Vivier
2023-07-05 7:56 ` Jason Wang
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=20230704071931.575888-1-lvivier@redhat.com \
--to=lvivier@redhat.com \
--cc=david@redhat.com \
--cc=eric.auger@redhat.com \
--cc=jasowang@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=peterx@redhat.com \
--cc=philmd@linaro.org \
--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).