Blame view
Documentation/printk-formats.txt
5.67 KB
b67ad18b0 DOC: add printk-f... |
1 2 3 4 5 6 7 8 9 10 |
If variable is of Type, use printk format specifier: --------------------------------------------------------- int %d or %x unsigned int %u or %x long %ld or %lx unsigned long %lu or %lx long long %lld or %llx unsigned long long %llu or %llx size_t %zu or %zx ssize_t %zd or %zx |
04c55715c Documentation: up... |
11 12 13 14 15 16 17 18 |
Raw pointer value SHOULD be printed with %p. The kernel supports the following extended format specifiers for pointer types: Symbols/Function Pointers: %pF versatile_init+0x0/0x110 %pf versatile_init %pS versatile_init+0x0/0x110 |
b0d33c2bd vsprintf: Add ext... |
19 20 |
%pSR versatile_init+0x9/0x110 (with __builtin_extract_return_addr() translation) |
04c55715c Documentation: up... |
21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 |
%ps versatile_init %pB prev_fn_of_versatile_init+0x88/0x88 For printing symbols and function pointers. The 'S' and 's' specifiers result in the symbol name with ('S') or without ('s') offsets. Where this is used on a kernel without KALLSYMS - the symbol address is printed instead. The 'B' specifier results in the symbol name with offsets and should be used when printing stack backtraces. The specifier takes into consideration the effect of compiler optimisations which may occur when tail-call's are used and marked with the noreturn GCC attribute. On ia64, ppc64 and parisc64 architectures function pointers are actually function descriptors which must first be resolved. The 'F' and 'f' specifiers perform this resolution and then provide the same functionality as the 'S' and 's' specifiers. Kernel Pointers: %pK 0x01234567 or 0x0123456789abcdef For printing kernel pointers which should be hidden from unprivileged users. The behaviour of %pK depends on the kptr_restrict sysctl - see Documentation/sysctl/kernel.txt for more details. Struct Resources: %pr [mem 0x60000000-0x6fffffff flags 0x2200] or [mem 0x0000000060000000-0x000000006fffffff flags 0x2200] %pR [mem 0x60000000-0x6fffffff pref] or [mem 0x0000000060000000-0x000000006fffffff pref] For printing struct resources. The 'R' and 'r' specifiers result in a printed resource with ('R') or without ('r') a decoded flags member. |
7d7992108 lib/vsprintf.c: a... |
56 57 58 59 60 61 62 |
Physical addresses: %pa 0x01234567 or 0x0123456789abcdef For printing a phys_addr_t type (and its derivatives, such as resource_size_t) which can vary based on build options, regardless of the width of the CPU data path. Passed by reference. |
31550a16a vsprintf: add sup... |
63 64 65 66 67 68 69 70 71 |
Raw buffer as a hex string: %*ph 00 01 02 ... 3f %*phC 00:01:02: ... :3f %*phD 00-01-02- ... -3f %*phN 000102 ... 3f For printing a small buffers (up to 64 bytes long) as a hex string with certain separator. For the larger buffers consider to use print_hex_dump(). |
04c55715c Documentation: up... |
72 73 74 |
MAC/FDDI addresses: %pM 00:01:02:03:04:05 |
76597ff98 vsprintf: add %pM... |
75 |
%pMR 05:04:03:02:01:00 |
04c55715c Documentation: up... |
76 77 |
%pMF 00-01-02-03-04-05 %pm 000102030405 |
7c59154e7 lib/vsprintf: upd... |
78 |
%pmR 050403020100 |
04c55715c Documentation: up... |
79 80 81 82 83 84 85 86 |
For printing 6-byte MAC/FDDI addresses in hex notation. The 'M' and 'm' specifiers result in a printed address with ('M') or without ('m') byte separators. The default byte separator is the colon (':'). Where FDDI addresses are concerned the 'F' specifier can be used after the 'M' specifier to use dash ('-') separators instead of the default separator. |
76597ff98 vsprintf: add %pM... |
87 88 89 |
For Bluetooth addresses the 'R' specifier shall be used after the 'M' specifier to use reversed byte order suitable for visual interpretation of Bluetooth addresses which are in the little endian order. |
04c55715c Documentation: up... |
90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 |
IPv4 addresses: %pI4 1.2.3.4 %pi4 001.002.003.004 %p[Ii][hnbl] For printing IPv4 dot-separated decimal addresses. The 'I4' and 'i4' specifiers result in a printed address with ('i4') or without ('I4') leading zeros. The additional 'h', 'n', 'b', and 'l' specifiers are used to specify host, network, big or little endian order addresses respectively. Where no specifier is provided the default network/big endian order is used. IPv6 addresses: %pI6 0001:0002:0003:0004:0005:0006:0007:0008 %pi6 00010002000300040005000600070008 %pI6c 1:2:3:4:5:6:7:8 For printing IPv6 network-order 16-bit hex addresses. The 'I6' and 'i6' specifiers result in a printed address with ('I6') or without ('i6') colon-separators. Leading zeros are always used. The additional 'c' specifier can be used with the 'I' specifier to print a compressed IPv6 address as described by http://tools.ietf.org/html/rfc5952 UUID/GUID addresses: %pUb 00010203-0405-0607-0809-0a0b0c0d0e0f %pUB 00010203-0405-0607-0809-0A0B0C0D0E0F %pUl 03020100-0504-0706-0809-0a0b0c0e0e0f %pUL 03020100-0504-0706-0809-0A0B0C0E0E0F For printing 16-byte UUID/GUIDs addresses. The additional 'l', 'L', 'b' and 'B' specifiers are used to specify a little endian order in lower ('l') or upper case ('L') hex characters - and big endian order in lower ('b') or upper case ('B') hex characters. Where no additional specifiers are used the default little endian order with lower case hex characters will be printed. struct va_format: %pV For printing struct va_format structures. These contain a format string and va_list as follows: struct va_format { const char *fmt; va_list *va; }; Do not use this feature without some mechanism to verify the correctness of the format string and va_list arguments. |
b67ad18b0 DOC: add printk-f... |
147 148 149 150 151 152 153 154 155 156 |
u64 SHOULD be printed with %llu/%llx, (unsigned long long): printk("%llu", (unsigned long long)u64_var); s64 SHOULD be printed with %lld/%llx, (long long): printk("%lld", (long long)s64_var); If <type> is dependent on a config option for its size (e.g., sector_t, |
7d7992108 lib/vsprintf.c: a... |
157 158 159 |
blkcnt_t) or is architecture-dependent for its size (e.g., tcflag_t), use a format specifier of its largest possible type and explicitly cast to it. Example: |
b67ad18b0 DOC: add printk-f... |
160 161 162 163 164 165 166 167 |
printk("test: sector number/total blocks: %llu/%llu ", (unsigned long long)sector, (unsigned long long)blockcount); Reminder: sizeof() result is of type size_t. Thank you for your cooperation and attention. |
755727b7f Randy has moved |
168 |
By Randy Dunlap <rdunlap@infradead.org> and |
04c55715c Documentation: up... |
169 |
Andrew Murray <amurray@mpc-data.co.uk> |