Searched full:behave (Results 1 – 25 of 87) sorted by relevance
1234
| /Documentation/virt/kvm/x86/ |
| D | errata.rst | 55 MSRs, i.e. {RD,WR}MSR in the guest will behave as expected, but KVM does not
62 emulates CR0.CD accesses so that loads and stores from/to CR0 behave as
|
| /Documentation/driver-api/nfc/ |
| D | nfc-pn544.rst | 19 write functions behave a bit differently because the message formats
|
| /Documentation/devicetree/bindings/display/bridge/ |
| D | megachips-stdpxxxx-ge-b850v3-fw.txt | 11 STDP2690 behave as the stock bridges would. The compatible strings include the
|
| /Documentation/hwmon/ |
| D | abituguru3.rst | 15 it to behave as a hwmon IC. There are many different revisions of the
|
| D | abituguru.rst | 19 it to behave as a hwmon IC. There are many different revisions of the
|
| D | max31827.rst | 73 reset may be required before it begins to behave normally. To prevent this,
|
| /Documentation/ABI/testing/ |
| D | sysfs-driver-zynqmp-fpga | 28 1: All I/Os behave as configured
|
| D | sysfs-class-typec | 45 source (The port will behave as source only DFP port)
46 sink (The port will behave as sink only UFP port)
47 dual (The port will behave as dual-role-data and
|
| /Documentation/admin-guide/ |
| D | highuid.rst | 43 - Validate that all filesystems behave properly.
|
| /Documentation/driver-api/soundwire/ |
| D | error_handling.rst | 62 that the Slave might behave in implementation-defined ways. The bus
|
| /Documentation/devicetree/bindings/iio/afe/ |
| D | temperature-transducer.yaml | 75 circuit behave like a temperature transducer.
|
| /Documentation/usb/ |
| D | ehci.rst | 85 behave quite right at the moment.
146 transaction translators are in use; some drivers have been seen to behave
|
| /Documentation/infiniband/ |
| D | ipoib.rst | 31 rtnl_link_ops, where children created using either way behave the same.
|
| /Documentation/devicetree/bindings/net/ |
| D | ti,dp83867.yaml | 95 PHY_INTERFACE_MODE_RGMII, by default, does not behave as RGMII with no
|
| D | mscc-phy-vsc8531.txt | 25 - vsc8531,led-[N]-mode : LED mode. Specify how the LED[N] should behave.
|
| /Documentation/i2c/ |
| D | fault-codes.rst | 23 the right fault code, so that it can (in turn) behave correctly.
|
| /Documentation/arch/x86/ |
| D | tdx.rst | 126 removal but depends on the BIOS to behave correctly.
140 but depends on the BIOS to behave correctly.
210 TDX guests behave differently from bare-metal and traditional VMX guests.
|
| /Documentation/admin-guide/cgroup-v1/ |
| D | hugetlb.rst | 135 reservations are uncharged. HugeTLB reservations behave in this manner to match
|
| /Documentation/fb/ |
| D | pxafb.rst | 91 behave in a similar way as a framebuffer.
|
| /Documentation/locking/ |
| D | pi-futex.rst | 79 mutexes involves no kernel work at all - they behave quite similarly to
|
| /Documentation/arch/arm64/ |
| D | pointer-authentication.rst | 32 these instructions behave as NOPs. Applications and libraries using
|
| D | asymmetric-32bit.rst | 49 32-bit tasks running on an asymmetric system behave in mostly the same
|
| /Documentation/scsi/ |
| D | ChangeLog.sym53c8xx_2 | 117 semaphore in order to behave synchronously as required by the eh
|
| /Documentation/process/ |
| D | code-of-conduct-interpretation.rst | 43 behave in the parts of the community where they are active. That
|
| /Documentation/networking/device_drivers/ethernet/intel/ |
| D | e100.rst | 161 (non-partitioned switch) behave as expected. All Ethernet interfaces
|
1234