Thread (55 messages) 55 messages, 7 authors, 2021-09-27

Re: [PATCH v4 11/15] pci: Add pci_iomap_shared{,_range}

From: Bjorn Helgaas <helgaas@kernel.org>
Date: 2021-08-25 14:52:40
Also in: linux-alpha, linux-doc, linux-mips, linux-pci, lkml, sparclinux, virtualization

On Tue, Aug 24, 2021 at 01:50:00PM -0700, Andi Kleen wrote:
On 8/24/2021 1:31 PM, Bjorn Helgaas wrote:
quoted
On Tue, Aug 24, 2021 at 01:14:02PM -0700, Andi Kleen wrote:
quoted
On 8/24/2021 11:55 AM, Bjorn Helgaas wrote:
quoted
[+cc Rajat; I still don't know what "shared memory with a hypervisor
in a confidential guest" means,
A confidential guest is a guest which uses memory encryption to isolate
itself from the host. It doesn't trust the host. But it still needs to
communicate with the host for IO, so it has some special memory areas that
are explicitly marked shared. These are used to do IO with the host. All
their usage needs to be carefully hardened to avoid any security attacks on
the guest, that's why we want to limit this interaction only to a small set
of hardened drivers. For MMIO, the set is currently only virtio and MSI-X.
Good material for the commit log next time around.  Thanks!
This is all in the patch intro too, which should make it into the merge
commits.
It's good if the cover letter makes into the merge commit log.

It's probably just because my git foo is lacking, but merge commit
logs don't seem as discoverable as the actual patch commit logs.  Five
years from now, if I want to learn about pci_iomap_shared() history, I
would "git log -p lib/pci_iomap.c" and search for it.  But I don't
think I would see the merge commit then.

Bjorn
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help