Displaying 8 results from an estimated 8 matches for "config_inline_spin_unlock".
Did you mean:
config_uninline_spin_unlock
2015 Apr 30
0
[PATCH 5/6] x86: switch config from UNINLINE_SPIN_UNLOCK to INLINE_SPIN_UNLOCK
...39a804 100644
--- a/include/linux/spinlock_api_smp.h
+++ b/include/linux/spinlock_api_smp.h
@@ -69,7 +69,7 @@ _raw_spin_unlock_irqrestore(raw_spinlock_t *lock, unsigned long flags)
#define _raw_spin_trylock_bh(lock) __raw_spin_trylock_bh(lock)
#endif
-#ifndef CONFIG_UNINLINE_SPIN_UNLOCK
+#ifdef CONFIG_INLINE_SPIN_UNLOCK
#define _raw_spin_unlock(lock) __raw_spin_unlock(lock)
#endif
diff --git a/kernel/Kconfig.locks b/kernel/Kconfig.locks
index 08561f1..9cc5f72 100644
--- a/kernel/Kconfig.locks
+++ b/kernel/Kconfig.locks
@@ -87,9 +87,6 @@ config ARCH_INLINE_WRITE_UNLOCK_IRQ
config ARCH_INLINE_WRITE_UNLOCK_IRQRE...
2015 Apr 30
12
[PATCH 0/6] x86: reduce paravirtualized spinlock overhead
Paravirtualized spinlocks produce some overhead even if the kernel is
running on bare metal. The main reason are the more complex locking
and unlocking functions. Especially unlocking is no longer just one
instruction but so complex that it is no longer inlined.
This patch series addresses this issue by adding two more pvops
functions to reduce the size of the inlined spinlock functions. When
2015 Apr 30
12
[PATCH 0/6] x86: reduce paravirtualized spinlock overhead
Paravirtualized spinlocks produce some overhead even if the kernel is
running on bare metal. The main reason are the more complex locking
and unlocking functions. Especially unlocking is no longer just one
instruction but so complex that it is no longer inlined.
This patch series addresses this issue by adding two more pvops
functions to reduce the size of the inlined spinlock functions. When
2011 Dec 21
1
Re: linux-next: Tree for Dec 21 (xen)
On 12/20/2011 10:47 PM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20111220:
drivers/xen/xenbus/xenbus_dev_backend.c:74:2: error: implicit declaration of function ''xen_initial_domain''
Full randconfig file is attached.
--
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
2010 Jun 25
1
[SPAM] The Infamous "Device 0 (vif) could not be connected. Hotplug scripts not working."
...OOP is not set
CONFIG_DEFAULT_IOSCHED="cfq"
# CONFIG_INLINE_SPIN_TRYLOCK is not set
# CONFIG_INLINE_SPIN_TRYLOCK_BH is not set
# CONFIG_INLINE_SPIN_LOCK is not set
# CONFIG_INLINE_SPIN_LOCK_BH is not set
# CONFIG_INLINE_SPIN_LOCK_IRQ is not set
# CONFIG_INLINE_SPIN_LOCK_IRQSAVE is not set
CONFIG_INLINE_SPIN_UNLOCK=y
# CONFIG_INLINE_SPIN_UNLOCK_BH is not set
CONFIG_INLINE_SPIN_UNLOCK_IRQ=y
# CONFIG_INLINE_SPIN_UNLOCK_IRQRESTORE is not set
# CONFIG_INLINE_READ_TRYLOCK is not set
# CONFIG_INLINE_READ_LOCK is not set
# CONFIG_INLINE_READ_LOCK_BH is not set
# CONFIG_INLINE_READ_LOCK_IRQ is not set
# CONFIG_INLINE...
2011 Aug 15
4
Kernel 3.1.0-rc2 hangs on boot, Xen 4.1.1
Hello,
I tried out kernel 3.1.0-rc2 on my i386 Laptop with Xen 4.1.1. Booting
hangs after these messages on the VGA console:
pci 0000:02:09.0: address space collision: [mem 0x000da000-0x000dafff] conflicts with reserved [mem 0x0009f800-0x000fffff]
reserve RAM buffer: 00000000 0009f000 - 00000000 0009ffff
reserve RAM buffer: 00000000 38400000 - 00000000 3bffffff
reserve RAM buffer: 00000001
2011 Aug 15
4
Kernel 3.1.0-rc2 hangs on boot, Xen 4.1.1
Hello,
I tried out kernel 3.1.0-rc2 on my i386 Laptop with Xen 4.1.1. Booting
hangs after these messages on the VGA console:
pci 0000:02:09.0: address space collision: [mem 0x000da000-0x000dafff] conflicts with reserved [mem 0x0009f800-0x000fffff]
reserve RAM buffer: 00000000 0009f000 - 00000000 0009ffff
reserve RAM buffer: 00000000 38400000 - 00000000 3bffffff
reserve RAM buffer: 00000001
2010 Nov 08
89
Re: DM-CRYPT: Scale to multiple CPUs v3 on 2.6.37-rc* ?
On Sun, Nov 07 2010 at 6:05pm -0500,
Andi Kleen <andi@firstfloor.org> wrote:
> On Sun, Nov 07, 2010 at 10:39:23PM +0100, Milan Broz wrote:
> > On 11/07/2010 08:45 PM, Andi Kleen wrote:
> > >> I read about barrier-problems and data getting to the partition when
> > >> using dm-crypt and several layers so I don''t know if that could be
> >