Edit File by line
/home/barbar84/public_h.../wp-conte.../plugins/sujqvwi/ExeBy/smexe_ro.../usr/include/asm
File: e820.h
/* SPDX-License-Identifier: GPL-2.0 WITH Linux-syscall-note */
[0] Fix | Delete
#ifndef _ASM_X86_E820_H
[1] Fix | Delete
#define _ASM_X86_E820_H
[2] Fix | Delete
#define E820MAP 0x2d0 /* our map */
[3] Fix | Delete
#define E820MAX 128 /* number of entries in E820MAP */
[4] Fix | Delete
[5] Fix | Delete
/*
[6] Fix | Delete
* Legacy E820 BIOS limits us to 128 (E820MAX) nodes due to the
[7] Fix | Delete
* constrained space in the zeropage. If we have more nodes than
[8] Fix | Delete
* that, and if we've booted off EFI firmware, then the EFI tables
[9] Fix | Delete
* passed us from the EFI firmware can list more nodes. Size our
[10] Fix | Delete
* internal memory map tables to have room for these additional
[11] Fix | Delete
* nodes, based on up to three entries per node for which the
[12] Fix | Delete
* kernel was built: MAX_NUMNODES == (1 << CONFIG_NODES_SHIFT),
[13] Fix | Delete
* plus E820MAX, allowing space for the possible duplicate E820
[14] Fix | Delete
* entries that might need room in the same arrays, prior to the
[15] Fix | Delete
* call to sanitize_e820_map() to remove duplicates. The allowance
[16] Fix | Delete
* of three memory map entries per node is "enough" entries for
[17] Fix | Delete
* the initial hardware platform motivating this mechanism to make
[18] Fix | Delete
* use of additional EFI map entries. Future platforms may want
[19] Fix | Delete
* to allow more than three entries per node or otherwise refine
[20] Fix | Delete
* this size.
[21] Fix | Delete
*/
[22] Fix | Delete
[23] Fix | Delete
#define E820_X_MAX E820MAX
[24] Fix | Delete
[25] Fix | Delete
#define E820NR 0x1e8 /* # entries in E820MAP */
[26] Fix | Delete
[27] Fix | Delete
#define E820_RAM 1
[28] Fix | Delete
#define E820_RESERVED 2
[29] Fix | Delete
#define E820_ACPI 3
[30] Fix | Delete
#define E820_NVS 4
[31] Fix | Delete
#define E820_UNUSABLE 5
[32] Fix | Delete
#define E820_PMEM 7
[33] Fix | Delete
[34] Fix | Delete
/*
[35] Fix | Delete
* This is a non-standardized way to represent ADR or NVDIMM regions that
[36] Fix | Delete
* persist over a reboot. The kernel will ignore their special capabilities
[37] Fix | Delete
* unless the CONFIG_X86_PMEM_LEGACY option is set.
[38] Fix | Delete
*
[39] Fix | Delete
* ( Note that older platforms also used 6 for the same type of memory,
[40] Fix | Delete
* but newer versions switched to 12 as 6 was assigned differently. Some
[41] Fix | Delete
* time they will learn... )
[42] Fix | Delete
*/
[43] Fix | Delete
#define E820_PRAM 12
[44] Fix | Delete
[45] Fix | Delete
/*
[46] Fix | Delete
* reserved RAM used by kernel itself
[47] Fix | Delete
* if CONFIG_INTEL_TXT is enabled, memory of this type will be
[48] Fix | Delete
* included in the S3 integrity calculation and so should not include
[49] Fix | Delete
* any memory that BIOS might alter over the S3 transition
[50] Fix | Delete
*/
[51] Fix | Delete
#define E820_RESERVED_KERN 128
[52] Fix | Delete
[53] Fix | Delete
#ifndef __ASSEMBLY__
[54] Fix | Delete
#include <linux/types.h>
[55] Fix | Delete
struct e820entry {
[56] Fix | Delete
__u64 addr; /* start of memory segment */
[57] Fix | Delete
__u64 size; /* size of memory segment */
[58] Fix | Delete
__u32 type; /* type of memory segment */
[59] Fix | Delete
} __attribute__((packed));
[60] Fix | Delete
[61] Fix | Delete
struct e820map {
[62] Fix | Delete
__u32 nr_map;
[63] Fix | Delete
struct e820entry map[E820_X_MAX];
[64] Fix | Delete
};
[65] Fix | Delete
[66] Fix | Delete
#define ISA_START_ADDRESS 0xa0000
[67] Fix | Delete
#define ISA_END_ADDRESS 0x100000
[68] Fix | Delete
[69] Fix | Delete
#define BIOS_BEGIN 0x000a0000
[70] Fix | Delete
#define BIOS_END 0x00100000
[71] Fix | Delete
[72] Fix | Delete
#define BIOS_ROM_BASE 0xffe00000
[73] Fix | Delete
#define BIOS_ROM_END 0xffffffff
[74] Fix | Delete
[75] Fix | Delete
#endif /* __ASSEMBLY__ */
[76] Fix | Delete
[77] Fix | Delete
[78] Fix | Delete
#endif /* _ASM_X86_E820_H */
[79] Fix | Delete
[80] Fix | Delete
It is recommended that you Edit text format, this type of Fix handles quite a lot in one request
Function