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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Mon, 2 Aug 2021 21:08:52 +0800 From: Tianyu Lan <ltykernel@...il.com> To: Joerg Roedel <joro@...tes.org> Cc: kys@...rosoft.com, haiyangz@...rosoft.com, sthemmin@...rosoft.com, wei.liu@...nel.org, decui@...rosoft.com, tglx@...utronix.de, mingo@...hat.com, bp@...en8.de, x86@...nel.org, hpa@...or.com, dave.hansen@...ux.intel.com, luto@...nel.org, peterz@...radead.org, konrad.wilk@...cle.com, boris.ostrovsky@...cle.com, jgross@...e.com, sstabellini@...nel.org, will@...nel.org, davem@...emloft.net, kuba@...nel.org, jejb@...ux.ibm.com, martin.petersen@...cle.com, arnd@...db.de, hch@....de, m.szyprowski@...sung.com, robin.murphy@....com, thomas.lendacky@....com, brijesh.singh@....com, ardb@...nel.org, Tianyu.Lan@...rosoft.com, rientjes@...gle.com, martin.b.radev@...il.com, akpm@...ux-foundation.org, rppt@...nel.org, kirill.shutemov@...ux.intel.com, aneesh.kumar@...ux.ibm.com, krish.sadhukhan@...cle.com, saravanand@...com, xen-devel@...ts.xenproject.org, pgonda@...gle.com, david@...hat.com, keescook@...omium.org, hannes@...xchg.org, sfr@...b.auug.org.au, michael.h.kelley@...rosoft.com, iommu@...ts.linux-foundation.org, linux-arch@...r.kernel.org, linux-hyperv@...r.kernel.org, linux-kernel@...r.kernel.org, linux-scsi@...r.kernel.org, netdev@...r.kernel.org, vkuznets@...hat.com, anparri@...rosoft.com Subject: Re: [PATCH 04/13] HV: Mark vmbus ring buffer visible to host in Isolation VM On 8/2/2021 8:59 PM, Joerg Roedel wrote: > On Mon, Aug 02, 2021 at 08:56:29PM +0800, Tianyu Lan wrote: >> Both second and third are HV_GPADL_RING type. One is send ring and the >> other is receive ring. The driver keeps the order to allocate rx and >> tx buffer. You are right this is not robust and will add a mutex to keep >> the order. > > Or you introduce fixed indexes for the RX and TX buffers? > The interface just allocates a buffer and driver will continue to configure the buffer to be rx or tx after calling.
Powered by blists - more mailing lists