forked from rpms/kernel
		
	Re-enable CONFIG_CRYPTO_DEV_SP_PSP so I can work on SEV stuff.
Waaay back in October, we saw some issues with various system firmware talking to the AMD SP PSP devices (the secure processor feature), and so CONFIG_CRYPTO_DEV_SP_PSP got disabled in all of our kernel trees, as Laura noted here: https://bugzilla.redhat.com/show_bug.cgi?id=1608242#c44 . I'm trying to use it, and this obviously makes that impossible to do, so I'm going to re-enable it in rawhide, because the timeout that's being discussed in that bugzilla thread is already there, and so this firmware bugs people saw before shouldn't make things completely unusable. If you *do* see debilitating stalls on AMD EPYC hardware starting after the next rawhide build, make some noise so we can disable it again. (I've also posted this to kernel@l.fp.o: https://lists.fedoraproject.org/archives/list/kernel@lists.fedoraproject.org/thread/22XCMRU4R75M4D5OSXE7YMWYVOBQIU2M/ ) Signed-off-by: Peter Jones <pjones@redhat.com>
This commit is contained in:
		
							parent
							
								
									f8216ee47a
								
							
						
					
					
						commit
						fe9e33a887
					
				| @ -1 +1 @@ | ||||
| # CONFIG_CRYPTO_DEV_SP_PSP is not set | ||||
| CONFIG_CRYPTO_DEV_SP_PSP=y | ||||
|  | ||||
| @ -976,7 +976,7 @@ CONFIG_CRYPTO_DEV_QAT_C62XVF=m | ||||
| CONFIG_CRYPTO_DEV_QAT_DH895xCC=m | ||||
| CONFIG_CRYPTO_DEV_QAT_DH895xCCVF=m | ||||
| # CONFIG_CRYPTO_DEV_SP_CCP is not set | ||||
| # CONFIG_CRYPTO_DEV_SP_PSP is not set | ||||
| CONFIG_CRYPTO_DEV_SP_PSP=y | ||||
| CONFIG_CRYPTO_DEV_VIRTIO=m | ||||
| CONFIG_CRYPTO_DH=y | ||||
| CONFIG_CRYPTO_DRBG_CTR=y | ||||
|  | ||||
| @ -975,7 +975,7 @@ CONFIG_CRYPTO_DEV_QAT_C62XVF=m | ||||
| CONFIG_CRYPTO_DEV_QAT_DH895xCC=m | ||||
| CONFIG_CRYPTO_DEV_QAT_DH895xCCVF=m | ||||
| # CONFIG_CRYPTO_DEV_SP_CCP is not set | ||||
| # CONFIG_CRYPTO_DEV_SP_PSP is not set | ||||
| CONFIG_CRYPTO_DEV_SP_PSP=y | ||||
| CONFIG_CRYPTO_DEV_VIRTIO=m | ||||
| CONFIG_CRYPTO_DH=y | ||||
| CONFIG_CRYPTO_DRBG_CTR=y | ||||
|  | ||||
		Loading…
	
		Reference in New Issue
	
	Block a user