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
| ||
|
Message-ID: <c966018b-95f0-7b92-0a5a-9023236b0dfb@infradead.org> Date: Sat, 28 Jan 2023 08:41:38 -0800 From: Randy Dunlap <rdunlap@...radead.org> To: "GuoRui.Yu" <GuoRui.Yu@...ux.alibaba.com>, linux-kernel@...r.kernel.org, iommu@...ts.linux-foundation.org, konrad.wilk@...cle.com, linux-coco@...ts.linux.dev Cc: robin.murphy@....com Subject: Re: [PATCH 2/4] swiotlb: Add a new cc-swiotlb implementation for Confidential VMs Hi-- On 1/28/23 00:32, GuoRui.Yu wrote: > diff --git a/kernel/dma/Kconfig b/kernel/dma/Kconfig > index 56866aaa2ae1..7e6b20d2091f 100644 > --- a/kernel/dma/Kconfig > +++ b/kernel/dma/Kconfig > @@ -78,8 +78,18 @@ config ARCH_HAS_FORCE_DMA_UNENCRYPTED > > config SWIOTLB > bool > + depends on !CC_SWIOTLB > select NEED_DMA_MAP_STATE > > +config CC_SWIOTLB > + bool "Enable cc-swiotlb for Confidential VMs" > + default n > + select NEED_DMA_MAP_STATE > + help > + This enables a cc-swiotlb implementation for Confidential VMs, > + which allows allocating the SWIOTLB buffer allocation on runtime. Two "allocat..." words seems to be redundant. Probably the second one can be dropped. Also, instead of "on runtime", how about "at runtime"? > + If unsure, say "n". Thanks. -- ~Randy
Powered by blists - more mailing lists