Home
last modified time | relevance | path

Searched refs:ownership (Results 1 – 25 of 27) sorted by relevance

12

/linux-3.4.99/arch/arm/mm/
Dcache-v6.S208 ldrb r2, [r0] @ read for ownership
209 strb r2, [r0] @ write for ownership
220 ldrneb r2, [r1, #-1] @ read for ownership
221 strneb r2, [r1, #-1] @ write for ownership
238 ldrlo r2, [r0] @ read for ownership
239 strlo r2, [r0] @ write for ownership
255 ldr r2, [r0] @ read for ownership
276 ldrb r2, [r0] @ read for ownership
277 strb r2, [r0] @ write for ownership
289 ldrlob r2, [r0] @ read for ownership
[all …]
/linux-3.4.99/Documentation/
Drt-mutex.txt63 Pending-ownership handling is a performance optimization:
64 pending-ownership is assigned to the first (highest priority) waiter of
70 The pending-ownership optimization is especially important for the
Drt-mutex-design.txt548 pending ownership. This means that it's the new owner, unless a higher
595 mutex, we check to see if we can take the ownership. This is done if the
619 If there are waiters on this mutex, and we just stole the ownership, we need
623 would add itself back when it realizes that it had the ownership stolen
635 3) Failed to grab ownership
638 The most interesting case is when we fail to take ownership. This means that
647 Now we enter a loop that will continue to try to take ownership of the mutex, or
690 1) we were given pending ownership of the mutex.
695 ownership of the mutex. If we succeed, we exit the loop, otherwise we continue
743 pending ownership.
/linux-3.4.99/fs/hfsplus/
DKconfig13 style features such as file ownership and permissions.
/linux-3.4.99/tools/perf/Documentation/
Dperf-buildid-list.txt32 Don't do ownership validation.
/linux-3.4.99/arch/arm/vfp/
Dvfphw.S91 @ thread wants ownership of the VFP hardware, save the old
121 @ This thread has ownership of the current hardware context.
/linux-3.4.99/drivers/staging/iio/Documentation/
Dtrigger.txt18 ownership of core allocated resources.
Ddevice.txt30 Set to THIS_MODULE. Used to ensure correct ownership
/linux-3.4.99/scripts/rt-tester/
Dt3-l1-pi-steal.tst48 # 3 threads 1 lock PI steal pending ownership
/linux-3.4.99/Documentation/power/
Dvideo_extension.txt17 VGA/DOS : Used to get/set ownership of output switching:
/linux-3.4.99/arch/arm/kernel/
Diwmmxt.S92 teq r1, #0 @ test for last ownership
339 streq r0, [r3] @ then clear ownership
/linux-3.4.99/drivers/char/tpm/
Dtpm.h198 u8 ownership; member
/linux-3.4.99/Documentation/ABI/stable/
Dsysfs-bus-firewire38 Users: udev rules to set ownership and access permissions or ACLs of
/linux-3.4.99/Documentation/rapidio/
Drapidio.txt111 algorithm. When a new device is found, the enumerator takes ownership of that
113 the enumerator has exclusive right to enumerate the device. If device ownership
/linux-3.4.99/arch/arm/mach-ep93xx/
Dcrunch-bits.S89 teq r1, #0 @ test for last ownership
/linux-3.4.99/Documentation/networking/
Dtuntap.txt46 If you want to create persistent devices and give ownership of them to
/linux-3.4.99/Documentation/networking/caif/
DLinux-CAIF.txt98 - When receiving / transmitting CAIF Packets (cfpkt), ownership is passed
/linux-3.4.99/Documentation/isdn/
DINTERFACE.CAPI140 If the method returns 0 (CAPI_NOERROR) the driver has taken ownership
142 non-zero (error) value then ownership of the skb returns to the caller
/linux-3.4.99/Documentation/security/
Dkeys.txt170 The ownership of the thread keyring changes when the real UID and GID of
248 For changing the ownership, group ID or permissions mask, being the owner of
480 the process's ownership.
508 (*) Change the ownership of a key:
796 The calling process must have the same ownership as its parent, the
797 keyring must have the same ownership as the calling process, the calling
Dcredentials.txt51 (2) Object ownership.
54 indicates the ownership of that object. This is used for resource
/linux-3.4.99/Documentation/fb/
Dudlfb.txt51 * Fbdev does not arbitrate client ownership of the framebuffer well.
/linux-3.4.99/Documentation/development-process/
D1.Intro250 original ownership; as a result, the kernel now has thousands of owners.
252 One implication of this ownership structure is that any attempt to change
/linux-3.4.99/drivers/staging/vme/
Dvme_api.txt82 The driver can request ownership of one or more master windows, slave windows
/linux-3.4.99/Documentation/PCI/
Dpci.txt42 Once the driver knows about a PCI device and takes ownership, the
95 take "ownership" of the device or an error code
/linux-3.4.99/Documentation/scsi/
Dscsi_mid_low_api.txt307 This effectively spreads the ownership of struct Scsi_Host instances
323 This effectively spreads the ownership of struct Scsi_device instances
1078 * Command ownership. If the driver returns zero, it owns the

12