Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit 507a03c1 authored by Linus Torvalds's avatar Linus Torvalds
Browse files

Merge branch 'release' of git://git.kernel.org/pub/scm/linux/kernel/git/lenb/linux 

This includes initial support for the recently published ACPI 5.0 spec.
In particular, support for the "hardware-reduced" bit that eliminates
the dependency on legacy hardware.

APEI has patches resulting from testing on real hardware.

Plus other random fixes.

* 'release' of git://git.kernel.org/pub/scm/linux/kernel/git/lenb/linux: (52 commits)
  acpi/apei/einj: Add extensions to EINJ from rev 5.0 of acpi spec
  intel_idle: Split up and provide per CPU initialization func
  ACPI processor: Remove unneeded variable passed by acpi_processor_hotadd_init V2
  ACPI processor: Remove unneeded cpuidle_unregister_driver call
  intel idle: Make idle driver more robust
  intel_idle: Fix a cast to pointer from integer of different size warning in intel_idle
  ACPI: kernel-parameters.txt : Add intel_idle.max_cstate
  intel_idle: remove redundant local_irq_disable() call
  ACPI processor: Fix error path, also remove sysdev link
  ACPI: processor: fix acpi_get_cpuid for UP processor
  intel_idle: fix API misuse
  ACPI APEI: Convert atomicio routines
  ACPI: Export interfaces for ioremapping/iounmapping ACPI registers
  ACPI: Fix possible alignment issues with GAS 'address' references
  ACPI, ia64: Use SRAT table rev to use 8bit or 16/32bit PXM fields (ia64)
  ACPI, x86: Use SRAT table rev to use 8bit or 32bit PXM fields (x86/x86-64)
  ACPI: Store SRAT table revision
  ACPI, APEI, Resolve false conflict between ACPI NVS and APEI
  ACPI, Record ACPI NVS regions
  ACPI, APEI, EINJ, Refine the fix of resource conflict
  ...
parents be405411 79ba0db6

Documentation/acpi/apei/einj.txt

+44 −11
Original line number Diff line number Diff line
@@ -47,20 +47,53 @@ directory apei/einj. The following files are provided. 


- param1

  This file is used to set the first error parameter value. Effect of

  parameter depends on error_type specified. For memory error, this is

  physical memory address.  Only available if param_extension module

  parameter is specified.

  parameter depends on error_type specified.



- param2

  This file is used to set the second error parameter value. Effect of

  parameter depends on error_type specified. For memory error, this is

  physical memory address mask.  Only available if param_extension

  module parameter is specified.

  parameter depends on error_type specified.



BIOS versions based in the ACPI 4.0 specification have limited options

to control where the errors are injected.  Your BIOS may support an

extension (enabled with the param_extension=1 module parameter, or

boot command line einj.param_extension=1). This allows the address

and mask for memory injections to be specified by the param1 and

param2 files in apei/einj.



BIOS versions using the ACPI 5.0 specification have more control over

the target of the injection. For processor related errors (type 0x1,

0x2 and 0x4) the APICID of the target should be provided using the

param1 file in apei/einj. For memory errors (type 0x8, 0x10 and 0x20)

the address is set using param1 with a mask in param2 (0x0 is equivalent

to all ones). For PCI express errors (type 0x40, 0x80 and 0x100) the

segment, bus, device and function are specified using param1:



         31     24 23    16 15    11 10      8  7        0

	+-------------------------------------------------+

	| segment |   bus  | device | function | reserved |

	+-------------------------------------------------+



An ACPI 5.0 BIOS may also allow vendor specific errors to be injected.

In this case a file named vendor will contain identifying information

from the BIOS that hopefully will allow an application wishing to use

the vendor specific extension to tell that they are running on a BIOS

that supports it. All vendor extensions have the 0x80000000 bit set in

error_type. A file vendor_flags controls the interpretation of param1

and param2 (1 = PROCESSOR, 2 = MEMORY, 4 = PCI). See your BIOS vendor

documentation for details (and expect changes to this API if vendors

creativity in using this feature expands beyond our expectations).



Example:

# cd /sys/kernel/debug/apei/einj

# cat available_error_type		# See which errors can be injected

0x00000002	Processor Uncorrectable non-fatal

0x00000008	Memory Correctable

0x00000010	Memory Uncorrectable non-fatal

# echo 0x12345000 > param1		# Set memory address for injection

# echo 0xfffffffffffff000 > param2	# Mask - anywhere in this page

# echo 0x8 > error_type			# Choose correctable memory error

# echo 1 > error_inject			# Inject now



Injecting parameter support is a BIOS version specific extension, that

is, it only works on some BIOS version.  If you want to use it, please

make sure your BIOS version has the proper support and specify

"param_extension=y" in module parameter.



For more information about EINJ, please refer to ACPI specification

version 4.0, section 17.5.
 
version 4.0, section 17.5 and ACPI 5.0, section 18.6.

Documentation/kernel-parameters.txt

+5 −0
Original line number Diff line number Diff line
@@ -1059,6 +1059,11 @@ bytes respectively. Such letter suffixes can also be entirely omitted. 
			By default, super page will be supported if Intel IOMMU

			has the capability. With this option, super page will

			not be supported.



	intel_idle.max_cstate=	[KNL,HW,ACPI,X86]

			0	disables intel_idle and fall back on acpi_idle.

			1 to 6	specify maximum depth of C-state.



	intremap=	[X86-64, Intel-IOMMU]

			on	enable Interrupt Remapping (default)

			off	disable Interrupt Remapping

arch/ia64/kernel/acpi.c

+6 −4
Original line number Diff line number Diff line
@@ -429,22 +429,24 @@ static u32 __devinitdata pxm_flag[PXM_FLAG_LEN]; 
static struct acpi_table_slit __initdata *slit_table;

cpumask_t early_cpu_possible_map = CPU_MASK_NONE;



static int get_processor_proximity_domain(struct acpi_srat_cpu_affinity *pa)

static int __init

get_processor_proximity_domain(struct acpi_srat_cpu_affinity *pa)

{

	int pxm;



	pxm = pa->proximity_domain_lo;

	if (ia64_platform_is("sn2"))

	if (ia64_platform_is("sn2") || acpi_srat_revision >= 2)

		pxm += pa->proximity_domain_hi[0] << 8;

	return pxm;

}



static int get_memory_proximity_domain(struct acpi_srat_mem_affinity *ma)

static int __init

get_memory_proximity_domain(struct acpi_srat_mem_affinity *ma)

{

	int pxm;



	pxm = ma->proximity_domain;

	if (!ia64_platform_is("sn2"))

	if (!ia64_platform_is("sn2") && acpi_srat_revision <= 1)

		pxm &= 0xff;



	return pxm;

arch/x86/kernel/e820.c

+2 −2
Original line number Diff line number Diff line
@@ -703,7 +703,7 @@ void __init e820_mark_nosave_regions(unsigned long limit_pfn) 
}

#endif



#ifdef CONFIG_HIBERNATION

#ifdef CONFIG_ACPI

/**

 * Mark ACPI NVS memory region, so that we can save/restore it during

 * hibernation and the subsequent resume.
@@ -716,7 +716,7 @@ static int __init e820_mark_nvs_memory(void) 
		struct e820entry *ei = &e820.map[i];



		if (ei->type == E820_NVS)

			suspend_nvs_register(ei->addr, ei->size);

			acpi_nvs_register(ei->addr, ei->size);

	}



	return 0;

arch/x86/mm/srat.c

+4 −0
Original line number Diff line number Diff line
@@ -109,6 +109,8 @@ acpi_numa_processor_affinity_init(struct acpi_srat_cpu_affinity *pa) 
	if ((pa->flags & ACPI_SRAT_CPU_ENABLED) == 0)

		return;

	pxm = pa->proximity_domain_lo;

	if (acpi_srat_revision >= 2)

		pxm |= *((unsigned int*)pa->proximity_domain_hi) << 8;

	node = setup_node(pxm);

	if (node < 0) {

		printk(KERN_ERR "SRAT: Too many proximity domains %x\n", pxm);
@@ -160,6 +162,8 @@ acpi_numa_memory_affinity_init(struct acpi_srat_mem_affinity *ma) 
	start = ma->base_address;

	end = start + ma->length;

	pxm = ma->proximity_domain;

	if (acpi_srat_revision <= 1)

		pxm &= 0xff;

	node = setup_node(pxm);

	if (node < 0) {

		printk(KERN_ERR "SRAT: Too many proximity domains.\n");