linux-kernel - Re: [PATCH v3 0/6] Expose GPU memory as coherently CPU accessible

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <BY5PR12MB3763086D7CD36B7B158FC426B09B9@BY5PR12MB3763.namprd12.prod.outlook.com>
Date:   Wed, 12 Apr 2023 08:43:56 +0000
From:   Ankit Agrawal <ankita@...dia.com>
To:     David Hildenbrand <david@...hat.com>,
        Jason Gunthorpe <jgg@...dia.com>,
        "alex.williamson@...hat.com" <alex.williamson@...hat.com>,
        "naoya.horiguchi@....com" <naoya.horiguchi@....com>,
        "maz@...nel.org" <maz@...nel.org>,
        "oliver.upton@...ux.dev" <oliver.upton@...ux.dev>
CC:     Aniket Agashe <aniketa@...dia.com>, Neo Jia <cjia@...dia.com>,
        Kirti Wankhede <kwankhede@...dia.com>,
        "Tarun Gupta (SW-GPU)" <targupta@...dia.com>,
        Vikram Sethi <vsethi@...dia.com>,
        Andy Currid <acurrid@...dia.com>,
        Alistair Popple <apopple@...dia.com>,
        John Hubbard <jhubbard@...dia.com>,
        Dan Williams <danw@...dia.com>,
        "kvm@...r.kernel.org" <kvm@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "linux-arm-kernel@...ts.infradead.org" 
        <linux-arm-kernel@...ts.infradead.org>,
        "linux-mm@...ck.org" <linux-mm@...ck.org>
Subject: Re: [PATCH v3 0/6] Expose GPU memory as coherently CPU accessible

Thanks David, response inline.

[...]

> I briefly skimmed over the series, the patch subject prefixes are a bit
> misleading IMHO and could be improved:

Understood. Will fix that in the next iteration.


>> Ankit Agrawal (6):
>>    kvm: determine memory type from VMA

> this is arch64 specific kvm (kvm/aarch64: ?)
Right. I'll change the prefix to kvm/aarch64


>>>    vfio/nvgpu: expose GPU device memory as BAR1
>>    mm: handle poisoning of pfn without struct pages
>mm/memory-failure:
Will change the prefix.

>>    mm: Add poison error check in fixup_user_fault() for mapped PFN
> That's both MM and core-KVM, maybe worth splitting up.
Ack, will do.

>>    mm: Change ghes code to allow poison of non-struct PFN
> That's  drivers/acpi/apei code, not core-mm code.
Ack.

>>    vfio/nvgpu: register device memory for poison handling

Thanks,
Ankit Agrawal