Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1664313 > unrolled thread
| Started by | Andi Kleen <ak@linux.intel.com> |
|---|---|
| First post | 2017-06-13 02:30 +0200 |
| Last post | 2017-06-13 02:30 +0200 |
| Articles | 1 — 1 participant |
Back to article view | Back to linux.kernel
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: [patch 0/7] x86/pci: Switch to lockless ECAM configuration mode Andi Kleen <ak@linux.intel.com> - 2017-06-13 02:30 +0200
| From | Andi Kleen <ak@linux.intel.com> |
|---|---|
| Date | 2017-06-13 02:30 +0200 |
| Subject | Re: [patch 0/7] x86/pci: Switch to lockless ECAM configuration mode |
| Message-ID | <tRHSx-P4-11@gated-at.bofh.it> |
On Thu, Mar 16, 2017 at 10:50:02PM +0100, Thomas Gleixner wrote: > Andi reported that the Intel Uncore performance monitoring suffers from the > global pci_lock which protects the generic PCI config space accessors. > > This lock can be removed on X86 because all architecture specific config > space accessors are either serialized by a seperate lock or can be > converted to have their own locking. The mmconfig based access (ECAM) does > not require serialization at the config read/write level because the access > is a simple byte/word/dword read from or write to the memory mapped > configuration space. In that case the lock does not provide any more > protection than the hardware provides already. > > The series converts the CE4100 PCI low level accessors to use the x86 > specific pci_config_lock and implements the switch over to lockless ECAM > configureation space accesors when the system is capable. What's the status of this patch series? The lock contention problem is still there. Thanks, -Andi
Back to top | Article view | linux.kernel
csiph-web