[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <46f68930-fdfc-db3d-5f28-521ff76e170a@redhat.com>
Date: Thu, 6 Apr 2023 14:07:58 +0200
From: David Hildenbrand <david@...hat.com>
To: ankita@...dia.com, jgg@...dia.com, alex.williamson@...hat.com,
naoya.horiguchi@....com, maz@...nel.org, oliver.upton@...ux.dev
Cc: aniketa@...dia.com, cjia@...dia.com, kwankhede@...dia.com,
targupta@...dia.com, vsethi@...dia.com, acurrid@...dia.com,
apopple@...dia.com, jhubbard@...dia.com, danw@...dia.com,
kvm@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-mm@...ck.org
Subject: Re: [PATCH v3 0/6] Expose GPU memory as coherently CPU accessible
[...]
> This goes along with a qemu series to provides the necessary
> implementation of the Grace Hopper Superchip firmware specification so
> that the guest operating system can see the correct ACPI modeling for
> the coherent GPU device.
> https://github.com/qemu/qemu/compare/master...ankita-nv:qemu:dev-ankit/cohmem-0330
>
> Applied and tested over v6.3-rc4.
>
I briefly skimmed over the series, the patch subject prefixes are a bit
misleading IMHO and could be improved:
> Ankit Agrawal (6):
> kvm: determine memory type from VMA
this is arch64 specific kvm (kvm/aarch64: ?)
> vfio/nvgpu: expose GPU device memory as BAR1
> mm: handle poisoning of pfn without struct pages
mm/memory-failure:
> mm: Add poison error check in fixup_user_fault() for mapped PFN
That's both MM and core-KVM, maybe worth splitting up.
> mm: Change ghes code to allow poison of non-struct PFN
That's drivers/acpi/apei code, not core-mm code.
> vfio/nvgpu: register device memory for poison handling
--
Thanks,
David / dhildenb
Powered by blists - more mailing lists