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
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Tue, 10 Aug 2021 15:50:58 -0600
From:   Alex Williamson <>
To:     Christoph Hellwig <>
Cc:     Jason Gunthorpe <>,,,
Subject: Re: [PATCH 3/7] vfio/pci: Use vfio_device_unmap_mapping_range()

On Tue, 10 Aug 2021 13:55:00 +0100
Christoph Hellwig <> wrote:

> On Tue, Aug 10, 2021 at 08:57:22AM -0300, Jason Gunthorpe wrote:
> > I'm not sure there is a real performance win to chase here? Doesn't
> > this only protect mmap against reset? The mmap isn't performance
> > sensitive, right?
> > 
> > If this really needs extra optimization adding a rwsem to the devset
> > and using that across the whole set would surely be sufficient.  
> Every mmio read or write takes memory_lock.

Exactly.  Ideally we're not using that path often, but I don't think
that's a good excuse to introduce memory access serialization, or even
dependencies between devices.  Thanks,


Powered by blists - more mailing lists