Home
last modified time | relevance | path

Searched refs:cross (Results 1 – 72 of 72) sorted by relevance

/linux-4.1.27/Documentation/filesystems/
Ddirectory-locking18 4) rename() that is _not_ cross-directory. Locking rules: caller locks
29 6) cross-directory rename. The trickiest in the whole bunch. Locking
56 (1) if object removal or non-cross-directory rename holds lock on A and
58 acquire the lock on B. (Proof: only cross-directory rename can change
61 (2) if cross-directory rename holds the lock on filesystem, order will not
62 change until rename acquires all locks. (Proof: other cross-directory
86 Any contended object is either held by cross-directory rename or
88 operation other than cross-directory rename. Then the lock this operation
91 It means that one of the operations is cross-directory rename.
94 own descendent. Moreover, there is exactly one cross-directory rename
[all …]
Dporting69 Locking change: ->s_vfs_rename_sem is taken only by cross-directory renames.
217 * filesystem has no cross-directory rename()
Df2fs.txt67 3. It checks the cross-reference between the data and its parent index structure.
286 are cross-referenced correctly or not.
Dxfs-self-describing-metadata.txt48 understanding how things like cross linked block lists (e.g. sibling
DLocking104 cross-directory ->rename() and rename2() has (per-superblock)
Dcoda.txt854 does not support cross directory hard links. Only the return value is
/linux-4.1.27/drivers/media/tuners/
Dr820t.c1535 struct r820t_sect_type cross[5]; /* (0,0)(0,Q-1)(0,I-1)(Q-1,0)(I-1,0) */ in r820t_imr_cross() local
1550 cross[i].gain_x = reg08; in r820t_imr_cross()
1551 cross[i].phase_y = reg09; in r820t_imr_cross()
1554 cross[i].gain_x = reg08; /* 0 */ in r820t_imr_cross()
1555 cross[i].phase_y = reg09 + 1; /* Q-1 */ in r820t_imr_cross()
1558 cross[i].gain_x = reg08; /* 0 */ in r820t_imr_cross()
1559 cross[i].phase_y = (reg09 | 0x20) + 1; /* I-1 */ in r820t_imr_cross()
1562 cross[i].gain_x = reg08 + 1; /* Q-1 */ in r820t_imr_cross()
1563 cross[i].phase_y = reg09; in r820t_imr_cross()
1566 cross[i].gain_x = (reg08 | 0x20) + 1; /* I-1 */ in r820t_imr_cross()
[all …]
/linux-4.1.27/tools/testing/ktest/examples/
Dcrosstests.conf33 OUTPUT_DIR = ${THIS_DIR}/cross-compile
47 LOG_FILE = ${OUTPUT_DIR}/cross.log
243 BUILD_TARGET = cross
DREADME13 cross compilers from:
/linux-4.1.27/arch/unicore32/
DMakefile15 CROSS_COMPILE := $(call cc-cross-prefix, unicore32-linux-)
/linux-4.1.27/arch/ia64/scripts/
Dtoolchain-flags22 warning: your linker cannot handle cross-segment segment-relative relocations.
/linux-4.1.27/drivers/cpuidle/
DKconfig10 idle processor power management. It includes modular cross-platform
/linux-4.1.27/arch/m68k/
DMakefile21 CROSS_COMPILE := $(call cc-cross-prefix, \
/linux-4.1.27/drivers/isdn/mISDN/
DKconfig19 cross connecting of bchannels, conferencing, dtmf decoding,
/linux-4.1.27/Documentation/
DSubmitChecklist23 3: Builds on multiple CPU architectures by using local cross-compile tools
26 4: ppc64 is a good architecture for cross-compilation checking because it
Dgdb-kernel-debugging.txt24 www.qemu.org for more details). For cross-development,
DDMA-ISA-LPC.txt37 Also the transfer block may not cross page boundaries (which are 64
Dflexible-arrays.txt10 vmalloc() allocations can require expensive cross-processor interrupts on
DDMA-API-HOWTO.txt416 buffer you receive will not cross a 64K boundary.
444 must not cross 4KByte boundaries (but at that time it may be better to
Dmemory-barriers.txt109 CPU are perceived by the rest of the system as the operations cross the
487 access queue that accesses of the appropriate type may not cross.
1824 the two accesses can themselves then cross:
1849 sections corresponding to the RELEASE and the ACQUIRE can cross, so that:
2684 accesses cross from the CPU side of things to the memory side of things, and
Dxillybus.txt347 it must not cross a 4kB boundary. Otherwise, it must be 4kB aligned. The
Dedac.txt187 is placed in each Channel, the csrows cross both DIMMs.
DDMA-API.txt104 from this pool must not cross 4KByte boundaries.
Dkernel-docs.txt637 Lots of cross references to variables and functions. You can see
Dpinctrl.txt287 situations a cross-subsystem mapping between pins and GPIOs is needed.
/linux-4.1.27/arch/parisc/
DMakefile39 CROSS_COMPILE := $(call cc-cross-prefix, \
/linux-4.1.27/Documentation/devicetree/bindings/clock/st/
Dst,flexgen.txt5 - a clock cross bar (represented by a mux element)
/linux-4.1.27/Documentation/hwmon/
Dk8temp54 70 degrees C. The rule of the thumb -> CPU temperature should not cross
/linux-4.1.27/scripts/
DKbuild.include71 # cc-cross-prefix
72 # Usage: CROSS_COMPILE := $(call cc-cross-prefix, m68k-linux-gnu- m68k-linux-)
75 cc-cross-prefix = \
/linux-4.1.27/Documentation/sound/alsa/soc/
Dpops_clicks.txt50 amplitude too quickly. It can be minimised by enabling the zero cross setting
/linux-4.1.27/tools/testing/selftests/ftrace/
DREADME39 minimal cross-build environments.
/linux-4.1.27/Documentation/sound/alsa/
DREADME.maya44128 Crossmix: cross-mixer from channels 1+2 to channels 3+4
129 Crossmix 1: cross-mixer from channels 3+4 to channels 1+2
/linux-4.1.27/tools/perf/Documentation/
Dandroid.txt13 2. Set cross-compiling environment variables for NDK toolchain and sysroot.
/linux-4.1.27/net/ipx/
DKconfig53 internal IPX network the cross-forwarding of packets targeted at
/linux-4.1.27/arch/sh/
DMakefile14 …CROSS_COMPILE := $(call cc-cross-prefix, $(UTS_MACHINE)-linux- $(UTS_MACHINE)-linux-gnu- $(UTS_M…
/linux-4.1.27/Documentation/misc-devices/
Dspear-pcie-gadget.txt60 read back bar size and address after writing to cross check.
/linux-4.1.27/drivers/usb/host/
Dfotg210.h471 u8 cross; /* buf crosses pages */ member
Dfusbh200.h461 u8 cross; /* buf crosses pages */ member
Dehci-sched.c1245 uframe->cross = 1; in itd_sched_init()
1729 if (unlikely (uf->cross)) { in itd_patch()
2044 packet->cross = 1; in sitd_sched_init()
2148 if (uf->cross) in sitd_patch()
Dehci.h450 u8 cross; /* buf crosses pages */ member
Dfusbh200-hcd.c4184 uframe->cross = 1; in itd_sched_init()
4471 if (unlikely (uf->cross)) { in itd_patch()
Dfotg210-hcd.c4250 uframe->cross = 1; in itd_sched_init()
4535 if (unlikely(uf->cross)) { in itd_patch()
/linux-4.1.27/tools/usb/usbip/
DINSTALL162 If you are _building_ compiler tools for cross-compiling, you should
166 If you want to _use_ a cross compiler, that generates code for a
/linux-4.1.27/Documentation/sysctl/
Dfs.txt167 is to cross privilege boundaries when following a given hardlink (i.e. a
187 is to cross privilege boundaries when following a given symlink (i.e. a
/linux-4.1.27/arch/mips/
DMakefile47 …CROSS_COMPILE := $(call cc-cross-prefix, $(tool-archpref)-linux- $(tool-archpref)-linux-gnu- $(t…
/linux-4.1.27/Documentation/kbuild/
Dkbuild.txt131 specify a custom installer when cross compiling a kernel.
Dmakefiles.txt564 cc-cross-prefix
565 cc-cross-prefix is used to check if there exists a $(CC) in path with
570 call of cc-cross-prefix.
574 It is recommended only to try to set CROSS_COMPILE if it is a cross
582 CROSS_COMPILE := $(call cc-cross-prefix, m68k-linux-gnu-)
1353 host system architecture. For a cross build, a user may
/linux-4.1.27/Documentation/cgroups/
Dmemcg_test.txt275 You will see message from cgroup_event_listener every time you cross
/linux-4.1.27/Documentation/arm/
DREADME20 If you wish to cross-compile, then alter the following lines in the top
/linux-4.1.27/Documentation/crypto/
Dasync-tx-api.txt46 2/ cross channel dependency chains: the API allows a chain of dependent
/linux-4.1.27/Documentation/fb/
Dmatroxfb.txt206 cross4MB - enables that pixel line can cross 4MB boundary. It is default for
208 nocross4MB - pixel line must not cross 4MB boundary. It is default for
/linux-4.1.27/Documentation/arm64/
Dbooting.txt50 cross a 2-megabyte boundary. This is to allow the kernel to map the
/linux-4.1.27/arch/powerpc/platforms/
DKconfig.cputype428 Note that if cross compiling a little endian kernel,
/linux-4.1.27/Documentation/RCU/
Drcubarrier.txt300 causing this latter to spin until the cross-CPU invocation of
/linux-4.1.27/Documentation/ide/
DChangeLog.ide-tape.1995-2002132 * Ver 1.9 Nov 5 96 Automatically cross encountered filemarks rather
/linux-4.1.27/arch/sparc/
DKconfig404 from www.gaisler.com. You can download a sparc-linux cross-compilation
/linux-4.1.27/Documentation/usb/
Dusbmon.txt354 Although the buffer is circular, the returned headers and data do not cross
/linux-4.1.27/Documentation/devicetree/bindings/thermal/
Dthermal.txt178 such that a device does not cross several trip boundaries unexpectedly
/linux-4.1.27/Documentation/scsi/
Daic79xx.txt92 - Remove S/G splitting for segments that cross a 4GB boundary.
DChangeLog.megaraid210 That, BTW, shows why cross-builds are useful-the only indication of
DChangeLog.lpfc1656 * Reintroduced usage of the cross compiler for building on
/linux-4.1.27/Documentation/gpio/
Dgpio-legacy.txt456 But how does the pin control subsystem cross-correlate the GPIO
461 cross-reference tables. These are described in
/linux-4.1.27/Documentation/development-process/
D5.Posting37 combinations of configuration options, use cross-compilers to build for
D4.Coding303 step. A large set of cross compilers for x86 systems can be found at
/linux-4.1.27/
DREADME218 The above also works when cross compiling.
/linux-4.1.27/drivers/message/fusion/lsi/
Dmpi_history.txt281 * Added defines for SES, SAF-TE, and cross channel for
/linux-4.1.27/Documentation/security/
Dkeys.txt5 This service allows cryptographic keys, authentication tokens, cross-domain
/linux-4.1.27/arch/arm/
DKconfig1165 switching code so that no page table walks can cross the ASID switch.
/linux-4.1.27/drivers/scsi/aic7xxx/
Daic79xx.seq452 * Don't cross an ADB or Cachline boundary when DMA'ing
/linux-4.1.27/init/
DKconfig54 directory to select the cross-compiler automatically.
/linux-4.1.27/Documentation/s390/
DDebugging390.txt894 you get fed up of cross referencing with System.map
/linux-4.1.27/Documentation/virtual/uml/
DUserModeLinux-HOWTO.txt1090 with two nodes on it (UML and the host) and arp requests don't cross