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
| ||
|
Date: Tue, 14 Mar 2017 19:24:14 -0700 From: Andi Kleen <andi@...stfloor.org> To: Bjorn Helgaas <helgaas@...nel.org> Cc: Thomas Gleixner <tglx@...utronix.de>, Andi Kleen <ak@...ux.intel.com>, Andi Kleen <andi@...stfloor.org>, bhelgaas@...gle.com, x86@...nel.org, linux-pci@...r.kernel.org, eranian@...gle.com, Peter Zijlstra <peterz@...radead.org>, LKML <linux-kernel@...r.kernel.org> Subject: Re: [PATCH 3/4] x86, pci: Add interface to force mmconfig > I agree that it should be fairly safe to do ECAM/MMCONFIG without > locking. Can we handle the decision part by adding a "lockless" bit > to struct pci_ops? Old ops don't mention that bit, so it will be > initialized to zero and we'll do locking as today. ECAM/MMCONFIG ops > can set it and we can skip the locking. That's what my other patch already did. -Andi
Powered by blists - more mailing lists