From: Alex Williamson <alex.williamson@redhat.com>
To: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
qemu-devel@nongnu.org, Eric Auger <eric.auger@redhat.com>,
Stefan Berger <stefanb@linux.vnet.ibm.com>
Subject: Re: [PATCH v3 0/2] tpm: CRB: Use ram_device for "tpm-crb-cmd" region
Date: Thu, 27 Jan 2022 07:40:47 -0700 [thread overview]
Message-ID: <20220127074047.6d3ecd16.alex.williamson@redhat.com> (raw)
In-Reply-To: <ccd1ccae-d9eb-8873-ded4-8caca5985b80@amsat.org>
On Thu, 27 Jan 2022 08:51:15 +0100
Philippe Mathieu-Daudé <f4bug@amsat.org> wrote:
> Hi Alex,
>
> On 27/1/22 00:51, Alex Williamson wrote:
> > On Thu, 20 Jan 2022 01:12:40 +0100
> > Philippe Mathieu-Daudé <f4bug@amsat.org> wrote:
> >
> >> This is a respin of Eric's work, but not making tpm_crb.c target
> >> specific.
> >>
> >> Based-on: <20220120000836.229419-1-f4bug@amsat.org>
> >> "exec/cpu: Make host pages variables / macros 'target agnostic'"
> >> https://lore.kernel.org/qemu-devel/20220120000836.229419-1-f4bug@amsat.org/
>
> [*]
>
> >> --
> >>
> >> Eric's v2 cover:
> >>
> >> 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.
> >>
> >> 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/tpm_crb.c | 22 ++++++++++++++++++++--
> >> hw/vfio/common.c | 15 ++++++++++++++-
> >> hw/vfio/trace-events | 1 +
> >> 3 files changed, 35 insertions(+), 3 deletions(-)
> >>
> >
> > Unfortunately, FTB:
> >
> > ../hw/tpm/tpm_crb.c: In function ‘tpm_crb_realize’:
> > ../hw/tpm/tpm_crb.c:297:33: warning: implicit declaration of function ‘HOST_PAGE_ALIGN’ [-Wimplicit-function-declaration]
> > 297 | HOST_PAGE_ALIGN(CRB_CTRL_CMD_SIZE));
> > | ^~~~~~~~~~~~~~~
> > ../hw/tpm/tpm_crb.c:297:33: warning: nested extern declaration of ‘HOST_PAGE_ALIGN’ [-Wnested-externs]
> >
> > This is a regression since Eric's v2. Thanks,
>
> This series is based on another patch that Paolo already queued
> (see [*] earlier).
>
> Next time I'll try to make it more explicit.
Sorry I missed that. Since Paolo now has that pending in a pull
request I'll try again next week. Thanks,
Alex
prev parent reply other threads:[~2022-01-27 14:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-20 0:12 [PATCH v3 0/2] tpm: CRB: Use ram_device for "tpm-crb-cmd" region Philippe Mathieu-Daudé via
2022-01-20 0:12 ` [PATCH v3 1/2] " Philippe Mathieu-Daudé via
2022-01-20 8:01 ` Eric Auger
2022-01-20 0:12 ` [PATCH v3 2/2] hw/vfio/common: Silence ram device offset alignment error traces Philippe Mathieu-Daudé via
2022-01-26 23:51 ` [PATCH v3 0/2] tpm: CRB: Use ram_device for "tpm-crb-cmd" region Alex Williamson
2022-01-27 7:51 ` Philippe Mathieu-Daudé via
2022-01-27 14:40 ` Alex Williamson [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=20220127074047.6d3ecd16.alex.williamson@redhat.com \
--to=alex.williamson@redhat.com \
--cc=eric.auger@redhat.com \
--cc=f4bug@amsat.org \
--cc=pbonzini@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).