From: Eric Auger <eric.auger@redhat.com>
To: eric.auger.pro@gmail.com, eric.auger@redhat.com,
stefanb@linux.vnet.ibm.com, qemu-devel@nongnu.org,
alex.williamson@redhat.com
Cc: cohuck@redhat.com, david@gibson.dropbear.id.au
Subject: [PATCH 0/2] TPM-CRB: Remove spurious error report when used with VFIO
Date: Thu, 13 Jan 2022 11:37:55 +0100 [thread overview]
Message-ID: <20220113103757.2801389-1-eric.auger@redhat.com> (raw)
launching a guest with a TPM-CRB device and VFIO-PCI devices.
The CRB command buffer currently is a RAM MemoryRegion and given
its base address alignment, it causes an error report on
vfio_listener_region_add(). This series proposes to use a ram-device
region instead which helps in better assessing the dma map error
failure severity on VFIO side.
Best Regards
Eric
This series can be found at:
https://github.com/eauger/qemu/tree/tpm-crb-ram-device-v1
Eric Auger (2):
tpm: CRB: Use ram_device for "tpm-crb-cmd" region
hw/vfio/common: Silence ram device offset alignment error traces
hw/tpm/meson.build | 2 +-
hw/tpm/tpm_crb.c | 10 ++++++++--
hw/vfio/common.c | 15 ++++++++++++++-
hw/vfio/trace-events | 1 +
4 files changed, 24 insertions(+), 4 deletions(-)
--
2.26.3
next reply other threads:[~2022-01-13 10:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-13 10:37 Eric Auger [this message]
2022-01-13 10:37 ` [PATCH 1/2] tpm: CRB: Use ram_device for "tpm-crb-cmd" region Eric Auger
2022-01-13 14:06 ` Stefan Berger
2022-01-13 14:40 ` Eric Auger
2022-01-13 15:38 ` Stefan Berger
2022-01-14 8:33 ` Eric Auger
2022-01-13 16:20 ` Stefan Berger
2022-01-13 10:37 ` [PATCH 2/2] hw/vfio/common: Silence ram device offset alignment error traces Eric Auger
2022-01-13 16:21 ` 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=20220113103757.2801389-1-eric.auger@redhat.com \
--to=eric.auger@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=cohuck@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=eric.auger.pro@gmail.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).