From: Laurent Vivier <lvivier@redhat.com>
To: qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org,
"Stefan Berger" <stefanb@linux.vnet.ibm.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
jasowang@redhat.com, mst@redhat.com,
"David Hildenbrand" <david@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
marcandre.lureau@redhat.com, eric.auger@redhat.com,
"Peter Xu" <peterx@redhat.com>,
"Laurent Vivier" <lvivier@redhat.com>
Subject: [PATCH 0/2] vhost-vdpa: skip TPM CRB memory section
Date: Tue, 20 Jun 2023 21:50:52 +0200 [thread overview]
Message-ID: <20230620195054.23929-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 DMA-able memory.
We have a memory flag for that, RAM_PROTECTED.
This series expands the memory API to provide a way to initialize
a "protected" memory region and use it with the TPM CRB object.
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 (2):
memory: introduce memory_region_init_ram_protected()
tpm_crb: mark memory as protected
hw/tpm/tpm_crb.c | 2 +-
include/exec/memory.h | 33 +++++++++++++++++++++++++++++++++
softmmu/memory.c | 33 +++++++++++++++++++++++++++------
softmmu/physmem.c | 4 ++--
4 files changed, 63 insertions(+), 9 deletions(-)
--
2.41.0
next reply other threads:[~2023-06-20 19:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-20 19:50 Laurent Vivier [this message]
2023-06-20 19:50 ` [PATCH 1/2] memory: introduce memory_region_init_ram_protected() Laurent Vivier
2023-06-21 12:27 ` Stefan Berger
2023-06-22 13:05 ` David Hildenbrand
2023-06-22 13:16 ` Peter Maydell
2023-06-20 19:50 ` [PATCH 2/2] tpm_crb: mark memory as protected Laurent Vivier
2023-06-21 9:13 ` David Hildenbrand
2023-06-22 12:59 ` Laurent Vivier
2023-06-22 13:05 ` David Hildenbrand
2023-06-21 12:29 ` Stefan Berger
2023-06-22 13:05 ` David Hildenbrand
2023-06-22 13:12 ` Peter Maydell
2023-06-22 13:39 ` Laurent Vivier
2023-06-22 13:53 ` Peter Maydell
2023-07-04 3:07 ` Jason Wang
2023-07-04 6:45 ` Laurent Vivier
2023-06-21 15:32 ` [PATCH 0/2] vhost-vdpa: skip TPM CRB memory section Peter Xu
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=20230620195054.23929-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).