From: Cornelia Huck <cohuck@redhat.com>
To: Eric Auger <eric.auger@redhat.com>,
eric.auger.pro@gmail.com, eric.auger@redhat.com,
qemu-devel@nongnu.org, alex.williamson@redhat.com
Cc: f4bug@amsat.org, stefanb@linux.vnet.ibm.com
Subject: Re: [PATCH v4] vfio/common: remove spurious tpm-crb-cmd misalignment warning
Date: Thu, 28 Apr 2022 15:58:47 +0200 [thread overview]
Message-ID: <87o80ll36w.fsf@redhat.com> (raw)
In-Reply-To: <20220428134945.511829-1-eric.auger@redhat.com>
On Thu, Apr 28 2022, Eric Auger <eric.auger@redhat.com> wrote:
> 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 region could have been a RAM device
> region, easing the detection of such safe situation but this option
> was not well received. So let's add a helper function that uses the
> memory region owner type to detect the situation is safe wrt
> the assignment. Other device types can be checked here if such kind
> of problem occurs again.
>
> Signed-off-by: Eric Auger <eric.auger@redhat.com>
> Reviewed-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
> Acked-by: Stefan Berger <stefanb@linux.ibm.com>
> Reviewed-by: Cornelia Huck <cohuck@redhat.com>
>
> ---
>
> v3 -> v4:
> - rebase on top of qemu_real_host_page_size() and
> qemu_real_host_page_size(). Print the size and make the message
> consistent
> - Added Stefan's A-b and Connie R-b (despite the changes)
Still fine with me.
> ---
> hw/vfio/common.c | 27 ++++++++++++++++++++++++++-
> hw/vfio/trace-events | 1 +
> 2 files changed, 27 insertions(+), 1 deletion(-)
next prev parent reply other threads:[~2022-04-28 14:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-28 13:49 [PATCH v4] vfio/common: remove spurious tpm-crb-cmd misalignment warning Eric Auger
2022-04-28 13:58 ` Cornelia Huck [this message]
2022-04-28 20:14 ` Alex Williamson
2022-05-06 7:05 ` Eric Auger
2022-05-06 7:34 ` Cornelia Huck
2022-05-06 7:49 ` Eric Auger
2022-05-06 7:56 ` Cornelia Huck
2022-05-06 12:40 ` 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=87o80ll36w.fsf@redhat.com \
--to=cohuck@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=eric.auger.pro@gmail.com \
--cc=eric.auger@redhat.com \
--cc=f4bug@amsat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.