qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Berger <stefanb@linux.ibm.com>
To: Eric Auger <eric.auger@redhat.com>,
	eric.auger.pro@gmail.com, stefanb@linux.vnet.ibm.com,
	qemu-devel@nongnu.org, alex.williamson@redhat.com
Cc: cohuck@redhat.com, david@gibson.dropbear.id.au
Subject: Re: [PATCH v2 0/2] TPM-CRB: Remove spurious error report when used with VFIO
Date: Wed, 19 Jan 2022 15:40:56 -0500	[thread overview]
Message-ID: <1ae39366-74af-c1f3-ae0d-4cb48ab9a7ea@linux.ibm.com> (raw)
In-Reply-To: <20220118153306.282681-1-eric.auger@redhat.com>


On 1/18/22 10:33, Eric Auger wrote:
> This series aims at removing a spurious error message we get when
> 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 on VFIO side.
>
> Best Regards
>
> Eric
>
> This series can be found at:
> https://github.com/eauger/qemu/tree/tpm-crb-ram-device-v2
>
> History:
> v1 -> v2:
> - added tpm_crb_unrealize (dared to keep Stefan's T-b though)
>
> 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     | 22 ++++++++++++++++++++--
>   hw/vfio/common.c     | 15 ++++++++++++++-
>   hw/vfio/trace-events |  1 +
>   4 files changed, 36 insertions(+), 4 deletions(-)
>
Acked-by: Stefan Berger <stefanb@linux.ibm.com>


      parent reply	other threads:[~2022-01-19 20:43 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
2022-01-19 20:40     ` Stefan Berger
2022-01-19 20:40 ` Stefan Berger [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=1ae39366-74af-c1f3-ae0d-4cb48ab9a7ea@linux.ibm.com \
    --to=stefanb@linux.ibm.com \
    --cc=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).