Searched refs:must (Results 1 – 25 of 994) sorted by relevance
12345678910>>...40
| /linux-3.4.99/Documentation/virtual/kvm/ |
| D | review-checklist.txt | 4 1. The patch must follow Documentation/CodingStyle and
10 - the API must be documented in Documentation/virtual/kvm/api.txt
11 - the API must be discoverable using KVM_CHECK_EXTENSION
13 4. New state must include support for save/restore.
15 5. New features must default to off (userspace should explicitly request them).
29 10. User/kernel interfaces and guest/host interfaces must be 64-bit clean
33 11. New guest visible features must either be documented in a hardware manual
36 12. Features must be robust against reset and kexec - for example, shared
37 host/guest memory must be unshared to prevent the host from writing to
|
| D | msr.txt | 18 data: 4-byte alignment physical address of a memory area which must be
44 Availability of this MSR must be checked via bit 3 in 0x4000001 cpuid
49 data: 4-byte aligned physical address of a memory area which must be in
113 Availability of this MSR must be checked via bit 3 in 0x4000001 cpuid
124 Availability of this MSR must be checked via bit 0 in 0x4000001 cpuid
134 Availability of this MSR must be checked via bit 0 in 0x4000001 cpuid
156 64 byte memory area which must be in guest RAM and must be
167 interrupt inhibits APFs. Guest must not enable interrupt
170 fault guest must reset the reason to 0 before it does
191 data: 64-byte alignment physical address of a memory area which must be
|
| D | locking.txt | 17 Comment: 'raw' because hardware enabling/disabling must be atomic /wrt
25 Comment: 'raw' because updating the tsc offsets must not be preempted.
|
| /linux-3.4.99/Documentation/arm/ |
| D | Booting | 65 The boot loader must ultimately be able to provide a MACH_TYPE_xxx
74 The boot loader must provide either a tagged list or a dtb image for
81 The boot loader must create and initialise the kernel tagged list.
84 has the size field set to '2' (0x00000002). The ATAG_NONE must set
92 The boot loader must pass at a minimum the size and location of
106 The tagged list must be placed in a region of memory where neither
113 The boot loader must load a device tree image (dtb) into system ram
120 The boot loader must pass at a minimum the size and location of the
121 system memory, and the root filesystem location. The dtb must be
143 In either case, the following conditions must be met:
[all …]
|
| /linux-3.4.99/Documentation/infiniband/ |
| D | core_locking.txt | 25 which may not sleep and must be callable from any context.
52 driver must be fully reentrant. The low-level driver is required to
68 A low-level driver must not perform a callback directly from the
77 simultaneously. The driver must guarantee that only one CQ event
101 must be complete before this call. The device must remain usable
104 A low-level driver must call ib_register_device() and
105 ib_unregister_device() from process context. It must not hold any
111 device. A consumer must finish all cleanup and free all resources
|
| /linux-3.4.99/Documentation/networking/ |
| D | driver.txt | 5 1) The ndo_start_xmit method must not return NETDEV_TX_BUSY under
10 Instead it must maintain the queue properly. For example,
62 2) An ndo_start_xmit method must not modify the shared parts of a
76 must not keep any reference to that SKB and you must not attempt
87 1) After the ndo_stop routine has been called, the hardware must
88 not receive or transmit any data. All in flight packets must
|
| D | nfc.txt | 56 When registering on the NFC subsystem, the device driver must inform the core
58 callbacks that must be implemented are the following:
87 The user must call START_POLL to poll for NFC targets, passing the desired NFC
94 sent (including the device id). The user must call GET_TARGET to get the list of
103 The userspace must use PF_NFC sockets to perform any data communication with
113 To establish a connection with one target, the user must create an
117 must inform which protocol it wants to use.
|
| /linux-3.4.99/Documentation/ |
| D | media-framework.txt | 53 registration. The following fields must be set:
55 - dev must point to the parent device (usually a pci_dev, usb_interface or
58 - model must be filled with the device model name as a NUL-terminated UTF-8
59 string. The device/model revision must not be stored in this field.
65 doesn't provide a unique serial number this field must be left empty.
68 NUL-terminated ASCII string. For PCI/PCIe devices bus_info must be set to
70 the usb_make_path() function must be used. This field is used by
79 minor must be incremented when new features are added to the userspace API
80 without breaking binary compatibility. The version major must be
118 Drivers must set the direction of every pad in the pads array before calling
[all …]
|
| D | preempt-locking.txt | 31 the previous value of smp_processor_id may not equal the current. You must
37 RULE #2: CPU state must be protected.
40 Under preemption, the state of the CPU must be protected. This is arch-
43 section that must occur while preemption is disabled. Think what would happen
47 preemption must be disabled around such regions.
51 However, math_state_restore must be called with preemption disabled.
54 RULE #3: Lock acquire and release must be performed by same task
57 A lock acquired in one task must be released by the same task. This
104 Notice how the preemption statements must encompass every reference of the
121 local_irq_save. Note, when doing so, you must be very careful to not cause
|
| D | local_ops.txt | 8 properly. It also stresses on the precautions that must be taken when reading
26 CPU which owns the data. Therefore, care must taken to make sure that only one
36 their UP variant must be kept. It typically means removing LOCK prefix (on
50 - Variables touched by local ops must be per cpu variables.
51 - _Only_ the CPU owner of these variables must write to them.
54 - Preemption (or interrupts) must be disabled when using local ops in
58 - When using local ops in interrupt context, no special care must be
100 the data seen by local_read across CPUs must be considered to be out of order
108 between CPUs, explicit smp_wmb() and smp_rmb() memory barriers must be used
|
| D | stable_kernel_rules.txt | 6 - It must be obviously correct and tested.
8 - It must fix only one thing.
9 - It must fix a real bug that bothers people (not a, "This could be a
11 - It must fix a problem that causes a build error (but not for things
26 - It must follow the Documentation/SubmittingPatches rules.
27 - It or an equivalent fix must already exist in Linus' tree (upstream).
33 stable@vger.kernel.org. You must note the upstream commit ID in the
|
| /linux-3.4.99/Documentation/filesystems/ |
| D | files.txt | 36 1. All references to the fdtable must be done through
52 The fdtable pointer must be read within the read-side
55 2. Reading of the fdtable as described above must be protected
58 3. For any update to the fd table, files->file_lock must
62 must use either fcheck() or fcheck_files() APIs. These
100 lock-free, they must be installed using rcu_assign_pointer()
102 must be used. However it is advisable to use files_fdtable()
105 7. While updating, the fdtable pointer must be looked up while
122 the fdtable pointer (fdt) must be loaded after locate_fd().
|
| /linux-3.4.99/Documentation/isdn/ |
| D | syncPPP.FAQ | 76 To enable MPPP negotiation you must call the
78 You must also configure a slave device for
81 To use channel bundling you must first activate
108 must not use the ipppd for this.
132 A: you must bind a network interface explicitly to
153 must I configure the network device.
155 A: At least you must have a route which forwards
159 Now you must choose a dummy IP address for your
167 must call the ipppd with the 'ipcp-accept-local' option.
169 A: You must know, how the ipppd gets the addresses it wanna
[all …]
|
| D | README.syncppp | 28 Currently, all devices must have the name ipppX where
31 To set up a PPP connection you need the ipppd .. You must start
42 You must disable BSD-compression, this implementation can't
48 To use the MPPP stuff, you must configure a slave device
50 To increase the number of links, you must use the
|
| /linux-3.4.99/Documentation/devicetree/bindings/powerpc/fsl/cpm_qe/ |
| D | cpm.txt | 40 Ranges must be set up subject to the following restrictions:
42 - Children's reg nodes must be offsets from the start of all muram, even
45 address and the child address must be the same in all, so that a single
49 - A child address of zero must be translatable, even if no reg resources
52 A child "data" node must exist, compatible with "fsl,cpm-muram-data", to
|
| /linux-3.4.99/drivers/block/paride/ |
| D | Kconfig | 5 # PARIDE must also be a module.
20 must also have at least one parallel port protocol driver in your
34 must also have at least one parallel port protocol driver in your
50 You must also have at least one parallel port protocol driver in
64 You must also have at least one parallel port protocol driver in
82 You must also have at least one parallel port protocol driver in
104 loadable module. The module will be called aten. You must also
123 called bpck. You must also have a high-level driver for the type
142 called bpck6. You must also have a high-level driver for the type
153 module. The module will be called comm. You must also have
[all …]
|
| /linux-3.4.99/Documentation/arm/SA1100/ |
| D | Brutus | 6 To compile for Brutus, you must issue the following commands:
14 must be loaded at 0xc0008000 in Brutus's memory and execution started at
18 But prior to execute the kernel, a ramdisk image must also be loaded in
20 containing the (compressed) ramdisk image must not exceed 4 MB.
|
| /linux-3.4.99/Documentation/devicetree/bindings/c6x/ |
| D | soc.txt | 7 - #address-cells: must be 1
8 - #size-cells: must be 1
|
| D | emifa.txt | 9 - compatible: must be "ti,c64x+emifa", "simple-bus"
11 - #address-cells: must be 2 (chip-select + offset)
12 - #size-cells: must be 1
|
| /linux-3.4.99/Documentation/connector/ |
| D | connector.txt | 9 netlink based network. One must register a callback and an identifier.
21 driver writer must create special sockets, must know about struct sk_buff
35 idx and val are unique identifiers which must be registered in the
38 is received by the connector core. The argument for that function must
61 It must be registered in connector.h for legal in-kernel users.
134 so caller is warned that it must be prepared. That is why the struct
145 with a different group number, the userspace application must subscribe to
172 group number 12345, you must increment CN_NETLINK_USERS to that number.
|
| /linux-3.4.99/Documentation/serial/ |
| D | rocket.txt | 63 If installed as a module, the module must be loaded. This can be done
68 In order to use the ports, their device names (nodes) must be created with mknod.
87 You must assign and configure the I/O addresses used by the ISA Rocketport
95 Before installing RocketPort(R) or RocketPort RA boards, you must find
99 0x300h, 0x340h, 0x380h. This I/O address must be reflected in the DIP
107 software control. The DIP switch settings for the I/O address must be
111 must have a unique board ID set on the dip switches. The first
112 Rocketport board must be set with the DIP switches corresponding to
113 the first board, the second board must be set with the DIP switches
118 The I/O address range used by any of the RocketPort cards must not
|
| D | driver | 81 This call must not sleep
98 This call must not sleep
115 This call must not sleep
127 This call must not sleep
134 This call must not sleep
142 This call must not sleep
153 This call must not sleep
163 This call must not sleep
181 Drivers must not access port->info once this call has completed.
198 This call must not sleep
[all …]
|
| /linux-3.4.99/Documentation/devicetree/bindings/hwmon/ |
| D | ads1015.txt | 38 - compatible : must be "ti,ads1015"
40 - #address-cells : must be <1>
41 - #size-cells : must be <0>
|
| /linux-3.4.99/Documentation/RCU/ |
| D | UP.txt | 43 RCU usage, since call_rcu() must wait for a grace period to elapse.
56 callback function must acquire this same lock. In this case, if
79 Quick Quiz #2: What locking restriction must RCU callbacks respect?
86 infrastructure -must- respect grace periods, and -must- invoke callbacks
107 What locking restriction must RCU callbacks respect?
109 Any lock that is acquired within an RCU callback must be
113 lock must use something like spin_lock_irqsave() to
|
| /linux-3.4.99/arch/powerpc/boot/dts/ |
| D | p1020mbg-pc.dtsi | 8 * * Redistributions of source code must retain the above copyright
10 * * Redistributions in binary form must reproduce the above copyright
63 /* This location must not be altered */
71 /* This location must not be altered */
141 /* USB2 is shared with localbus, so it must be disabled
|
12345678910>>...40