%PDF- <> %âãÏÓ endobj 2 0 obj <> endobj 3 0 obj <>/ExtGState<>/ProcSet[/PDF/Text/ImageB/ImageC/ImageI] >>/Annots[ 28 0 R 29 0 R] /MediaBox[ 0 0 595.5 842.25] /Contents 4 0 R/Group<>/Tabs/S>> endobj ºaâÚÎΞ-ÌE1ÍØÄ÷{òò2ÿ ÛÖ^ÔÀá TÎ{¦?§®¥kuµùÕ5sLOšuY>endobj 2 0 obj<>endobj 2 0 obj<>endobj 2 0 obj<>endobj 2 0 obj<> endobj 2 0 obj<>endobj 2 0 obj<>es 3 0 R>> endobj 2 0 obj<> ox[ 0.000000 0.000000 609.600000 935.600000]/Fi endobj 3 0 obj<> endobj 7 1 obj<>/ProcSet[/PDF/Text/ImageB/ImageC/ImageI]>>/Subtype/Form>> stream
/* SPDX-License-Identifier: GPL-2.0-only */ /* * vvar.h: Shared vDSO/kernel variable declarations * Copyright (c) 2011 Andy Lutomirski * * A handful of variables are accessible (read-only) from userspace * code in the vsyscall page and the vdso. They are declared here. * Some other file must define them with DEFINE_VVAR. * * In normal kernel code, they are used like any other variable. * In user code, they are accessed through the VVAR macro. * * These variables live in a page of kernel data that has an extra RO * mapping for userspace. Each variable needs a unique offset within * that page; specify that offset with the DECLARE_VVAR macro. (If * you mess up, the linker will catch it.) */ #ifndef _ASM_X86_VVAR_H #define _ASM_X86_VVAR_H #if defined(__VVAR_KERNEL_LDS) /* The kernel linker script defines its own magic to put vvars in the * right place. */ #define DECLARE_VVAR(offset, type, name) \ EMIT_VVAR(name, offset) #else extern char __vvar_page; #define DECLARE_VVAR(offset, type, name) \ extern type vvar_ ## name[CS_BASES] \ __attribute__((visibility("hidden"))); #define VVAR(name) (vvar_ ## name) #define DEFINE_VVAR(type, name) \ type name[CS_BASES] \ __attribute__((section(".vvar_" #name), aligned(16))) __visible #endif /* DECLARE_VVAR(offset, type, name) */ DECLARE_VVAR(128, struct vdso_data, _vdso_data) #undef DECLARE_VVAR #endif