linux-kernel - Re: The current status of PKS virtualization

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] [day] [month] [year] [list]

Message-ID: <f0be7fe5-bdb8-44bc-aa57-7728a72b0b08@intel.com>
Date: Wed, 12 Nov 2025 09:06:05 +0800
From: Chenyi Qiang <chenyi.qiang@...el.com>
To: Ruihan Li <lrh2000@....edu.cn>
CC: Paolo Bonzini <pbonzini@...hat.com>, <lei4.wang@...el.com>, "Sean
 Christopherson" <seanjc@...gle.com>, Jim Mattson <jmattson@...gle.com>,
	"Joerg Roedel" <joro@...tes.org>, kvm <kvm@...r.kernel.org>, "Kernel Mailing
 List, Linux" <linux-kernel@...r.kernel.org>, Vitaly Kuznetsov
	<vkuznets@...hat.com>, Wanpeng Li <wanpengli@...cent.com>
Subject: Re: The current status of PKS virtualization



On 11/11/2025 10:24 PM, Ruihan Li wrote:
> On Tue, Nov 11, 2025 at 01:40:08PM +0800, Chenyi Qiang wrote:
>> Lei has left Intel so the mail address in unreachable.
>>
>> And as you found, we dropped the PKS KVM upstream along with the base PKS support
>> due to no valid use case in Linux. You can feel free to continue the upstream work.
> 
> Thanks for the reply and for the information!
> 
> By the way, I'm just curious (feel free to ignore this question): Is
> there an on-list discussion that rejects the originally proposed PKS use
> cases?
> 
> I found that pmem stray write protection was rejected [1], but there is
> no reason given nor any reference provided. After searching the list, I
> found the latest patch series that attempts to add pmem stray protection
> [2]. However, I didn't find any discussion rejecting the use case. Maybe
> the discussion happened off the list? Or did I miss something?

The discussion happened off the list. The customer demand for this feature
declined to such an extent that it was not worth working on any longer.