License cleanup: add SPDX GPL-2.0 license identifier to files with no license
Many source files in the tree are missing licensing information, which
makes it harder for compliance tools to determine the correct license.
By default all files without license information are under the default
license of the kernel, which is GPL version 2.
Update the files which contain no license information with the 'GPL-2.0'
SPDX license identifier. The SPDX identifier is a legally binding
shorthand, which can be used instead of the full boiler plate text.
This patch is based on work done by Thomas Gleixner and Kate Stewart and
Philippe Ombredanne.
How this work was done:
Patches were generated and checked against linux-4.14-rc6 for a subset of
the use cases:
- file had no licensing information it it.
- file was a */uapi/* one with no licensing information in it,
- file was a */uapi/* one with existing licensing information,
Further patches will be generated in subsequent months to fix up cases
where non-standard license headers were used, and references to license
had to be inferred by heuristics based on keywords.
The analysis to determine which SPDX License Identifier to be applied to
a file was done in a spreadsheet of side by side results from of the
output of two independent scanners (ScanCode & Windriver) producing SPDX
tag:value files created by Philippe Ombredanne. Philippe prepared the
base worksheet, and did an initial spot review of a few 1000 files.
The 4.13 kernel was the starting point of the analysis with 60,537 files
assessed. Kate Stewart did a file by file comparison of the scanner
results in the spreadsheet to determine which SPDX license identifier(s)
to be applied to the file. She confirmed any determination that was not
immediately clear with lawyers working with the Linux Foundation.
Criteria used to select files for SPDX license identifier tagging was:
- Files considered eligible had to be source code files.
- Make and config files were included as candidates if they contained >5
lines of source
- File already had some variant of a license header in it (even if <5
lines).
All documentation files were explicitly excluded.
The following heuristics were used to determine which SPDX license
identifiers to apply.
- when both scanners couldn't find any license traces, file was
considered to have no license information in it, and the top level
COPYING file license applied.
For non */uapi/* files that summary was:
SPDX license identifier # files
---------------------------------------------------|-------
GPL-2.0 11139
and resulted in the first patch in this series.
If that file was a */uapi/* path one, it was "GPL-2.0 WITH
Linux-syscall-note" otherwise it was "GPL-2.0". Results of that was:
SPDX license identifier # files
---------------------------------------------------|-------
GPL-2.0 WITH Linux-syscall-note 930
and resulted in the second patch in this series.
- if a file had some form of licensing information in it, and was one
of the */uapi/* ones, it was denoted with the Linux-syscall-note if
any GPL family license was found in the file or had no licensing in
it (per prior point). Results summary:
SPDX license identifier # files
---------------------------------------------------|------
GPL-2.0 WITH Linux-syscall-note 270
GPL-2.0+ WITH Linux-syscall-note 169
((GPL-2.0 WITH Linux-syscall-note) OR BSD-2-Clause) 21
((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause) 17
LGPL-2.1+ WITH Linux-syscall-note 15
GPL-1.0+ WITH Linux-syscall-note 14
((GPL-2.0+ WITH Linux-syscall-note) OR BSD-3-Clause) 5
LGPL-2.0+ WITH Linux-syscall-note 4
LGPL-2.1 WITH Linux-syscall-note 3
((GPL-2.0 WITH Linux-syscall-note) OR MIT) 3
((GPL-2.0 WITH Linux-syscall-note) AND MIT) 1
and that resulted in the third patch in this series.
- when the two scanners agreed on the detected license(s), that became
the concluded license(s).
- when there was disagreement between the two scanners (one detected a
license but the other didn't, or they both detected different
licenses) a manual inspection of the file occurred.
- In most cases a manual inspection of the information in the file
resulted in a clear resolution of the license that should apply (and
which scanner probably needed to revisit its heuristics).
- When it was not immediately clear, the license identifier was
confirmed with lawyers working with the Linux Foundation.
- If there was any question as to the appropriate license identifier,
the file was flagged for further research and to be revisited later
in time.
In total, over 70 hours of logged manual review was done on the
spreadsheet to determine the SPDX license identifiers to apply to the
source files by Kate, Philippe, Thomas and, in some cases, confirmation
by lawyers working with the Linux Foundation.
Kate also obtained a third independent scan of the 4.13 code base from
FOSSology, and compared selected files where the other two scanners
disagreed against that SPDX file, to see if there was new insights. The
Windriver scanner is based on an older version of FOSSology in part, so
they are related.
Thomas did random spot checks in about 500 files from the spreadsheets
for the uapi headers and agreed with SPDX license identifier in the
files he inspected. For the non-uapi files Thomas did random spot checks
in about 15000 files.
In initial set of patches against 4.14-rc6, 3 files were found to have
copy/paste license identifier errors, and have been fixed to reflect the
correct identifier.
Additionally Philippe spent 10 hours this week doing a detailed manual
inspection and review of the 12,461 patched files from the initial patch
version early this week with:
- a full scancode scan run, collecting the matched texts, detected
license ids and scores
- reviewing anything where there was a license detected (about 500+
files) to ensure that the applied SPDX license was correct
- reviewing anything where there was no detection but the patch license
was not GPL-2.0 WITH Linux-syscall-note to ensure that the applied
SPDX license was correct
This produced a worksheet with 20 files needing minor correction. This
worksheet was then exported into 3 different .csv files for the
different types of files to be modified.
These .csv files were then reviewed by Greg. Thomas wrote a script to
parse the csv files and add the proper SPDX tag to the file, in the
format that the file expected. This script was further refined by Greg
based on the output to detect more types of files automatically and to
distinguish between header and source .c files (which need different
comment types.) Finally Greg ran the script using the .csv files to
generate the patches.
Reviewed-by: Kate Stewart <kstewart@linuxfoundation.org>
Reviewed-by: Philippe Ombredanne <pombredanne@nexb.com>
Reviewed-by: Thomas Gleixner <tglx@linutronix.de>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2017-11-01 15:07:57 +01:00
|
|
|
// SPDX-License-Identifier: GPL-2.0
|
2019-07-22 20:47:11 +02:00
|
|
|
|
2008-07-10 11:16:59 -07:00
|
|
|
#include <linux/cpumask.h>
|
2019-07-22 20:47:11 +02:00
|
|
|
#include <linux/acpi.h>
|
2008-07-21 22:08:21 -07:00
|
|
|
|
2019-07-22 20:47:14 +02:00
|
|
|
#include "local.h"
|
2008-07-10 11:16:59 -07:00
|
|
|
|
2009-02-21 14:23:21 -08:00
|
|
|
int x2apic_phys;
|
2008-07-21 22:08:21 -07:00
|
|
|
|
2011-05-20 17:51:20 -07:00
|
|
|
static struct apic apic_x2apic_phys;
|
2023-08-08 15:04:11 -07:00
|
|
|
u32 x2apic_max_apicid __ro_after_init = UINT_MAX;
|
2020-10-24 22:35:01 +01:00
|
|
|
|
|
|
|
void __init x2apic_set_max_apicid(u32 apicid)
|
|
|
|
{
|
|
|
|
x2apic_max_apicid = apicid;
|
2023-08-08 15:04:11 -07:00
|
|
|
if (apic->x2apic_set_max_apicid)
|
|
|
|
apic->max_apic_id = apicid;
|
2020-10-24 22:35:01 +01:00
|
|
|
}
|
2011-05-20 17:51:20 -07:00
|
|
|
|
2018-01-17 11:45:43 +08:00
|
|
|
static int __init set_x2apic_phys_mode(char *arg)
|
2008-07-21 22:08:21 -07:00
|
|
|
{
|
|
|
|
x2apic_phys = 1;
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
early_param("x2apic_phys", set_x2apic_phys_mode);
|
|
|
|
|
x86/apic: Work around boot failure on HP ProLiant DL980 G7 Server systems
When a HP ProLiant DL980 G7 Server boots a regular kernel,
there will be intermittent lost interrupts which could
result in a hang or (in extreme cases) data loss.
The reason is that this system only supports x2apic physical
mode, while the kernel boots with a logical-cluster default
setting.
This bug can be worked around by specifying the "x2apic_phys" or
"nox2apic" boot option, but we want to handle this system
without requiring manual workarounds.
The BIOS sets ACPI_FADT_APIC_PHYSICAL in FADT table.
As all apicids are smaller than 255, BIOS need to pass the
control to the OS with xapic mode, according to x2apic-spec,
chapter 2.9.
Current code handle x2apic when BIOS pass with xapic mode
enabled:
When user specifies x2apic_phys, or FADT indicates PHYSICAL:
1. During madt oem check, apic driver is set with xapic logical
or xapic phys driver at first.
2. enable_IR_x2apic() will enable x2apic_mode.
3. if user specifies x2apic_phys on the boot line, x2apic_phys_probe()
will install the correct x2apic phys driver and use x2apic phys mode.
Otherwise it will skip the driver will let x2apic_cluster_probe to
take over to install x2apic cluster driver (wrong one) even though FADT
indicates PHYSICAL, because x2apic_phys_probe does not check
FADT PHYSICAL.
Add checking x2apic_fadt_phys in x2apic_phys_probe() to fix the
problem.
Signed-off-by: Stoney Wang <song-bo.wang@hp.com>
[ updated the changelog and simplified the code ]
Signed-off-by: Yinghai Lu <yinghai@kernel.org>
Cc: stable@kernel.org
Link: http://lkml.kernel.org/r/1360263182-16226-1-git-send-email-yinghai@kernel.org
Signed-off-by: Ingo Molnar <mingo@kernel.org>
2013-02-07 10:53:02 -08:00
|
|
|
static bool x2apic_fadt_phys(void)
|
2008-07-21 22:08:21 -07:00
|
|
|
{
|
2015-05-04 17:58:00 +02:00
|
|
|
#ifdef CONFIG_ACPI
|
x86/apic: Work around boot failure on HP ProLiant DL980 G7 Server systems
When a HP ProLiant DL980 G7 Server boots a regular kernel,
there will be intermittent lost interrupts which could
result in a hang or (in extreme cases) data loss.
The reason is that this system only supports x2apic physical
mode, while the kernel boots with a logical-cluster default
setting.
This bug can be worked around by specifying the "x2apic_phys" or
"nox2apic" boot option, but we want to handle this system
without requiring manual workarounds.
The BIOS sets ACPI_FADT_APIC_PHYSICAL in FADT table.
As all apicids are smaller than 255, BIOS need to pass the
control to the OS with xapic mode, according to x2apic-spec,
chapter 2.9.
Current code handle x2apic when BIOS pass with xapic mode
enabled:
When user specifies x2apic_phys, or FADT indicates PHYSICAL:
1. During madt oem check, apic driver is set with xapic logical
or xapic phys driver at first.
2. enable_IR_x2apic() will enable x2apic_mode.
3. if user specifies x2apic_phys on the boot line, x2apic_phys_probe()
will install the correct x2apic phys driver and use x2apic phys mode.
Otherwise it will skip the driver will let x2apic_cluster_probe to
take over to install x2apic cluster driver (wrong one) even though FADT
indicates PHYSICAL, because x2apic_phys_probe does not check
FADT PHYSICAL.
Add checking x2apic_fadt_phys in x2apic_phys_probe() to fix the
problem.
Signed-off-by: Stoney Wang <song-bo.wang@hp.com>
[ updated the changelog and simplified the code ]
Signed-off-by: Yinghai Lu <yinghai@kernel.org>
Cc: stable@kernel.org
Link: http://lkml.kernel.org/r/1360263182-16226-1-git-send-email-yinghai@kernel.org
Signed-off-by: Ingo Molnar <mingo@kernel.org>
2013-02-07 10:53:02 -08:00
|
|
|
if ((acpi_gbl_FADT.header.revision >= FADT2_REVISION_ID) &&
|
|
|
|
(acpi_gbl_FADT.flags & ACPI_FADT_APIC_PHYSICAL)) {
|
2012-04-24 18:23:56 -06:00
|
|
|
printk(KERN_DEBUG "System requires x2apic physical mode\n");
|
x86/apic: Work around boot failure on HP ProLiant DL980 G7 Server systems
When a HP ProLiant DL980 G7 Server boots a regular kernel,
there will be intermittent lost interrupts which could
result in a hang or (in extreme cases) data loss.
The reason is that this system only supports x2apic physical
mode, while the kernel boots with a logical-cluster default
setting.
This bug can be worked around by specifying the "x2apic_phys" or
"nox2apic" boot option, but we want to handle this system
without requiring manual workarounds.
The BIOS sets ACPI_FADT_APIC_PHYSICAL in FADT table.
As all apicids are smaller than 255, BIOS need to pass the
control to the OS with xapic mode, according to x2apic-spec,
chapter 2.9.
Current code handle x2apic when BIOS pass with xapic mode
enabled:
When user specifies x2apic_phys, or FADT indicates PHYSICAL:
1. During madt oem check, apic driver is set with xapic logical
or xapic phys driver at first.
2. enable_IR_x2apic() will enable x2apic_mode.
3. if user specifies x2apic_phys on the boot line, x2apic_phys_probe()
will install the correct x2apic phys driver and use x2apic phys mode.
Otherwise it will skip the driver will let x2apic_cluster_probe to
take over to install x2apic cluster driver (wrong one) even though FADT
indicates PHYSICAL, because x2apic_phys_probe does not check
FADT PHYSICAL.
Add checking x2apic_fadt_phys in x2apic_phys_probe() to fix the
problem.
Signed-off-by: Stoney Wang <song-bo.wang@hp.com>
[ updated the changelog and simplified the code ]
Signed-off-by: Yinghai Lu <yinghai@kernel.org>
Cc: stable@kernel.org
Link: http://lkml.kernel.org/r/1360263182-16226-1-git-send-email-yinghai@kernel.org
Signed-off-by: Ingo Molnar <mingo@kernel.org>
2013-02-07 10:53:02 -08:00
|
|
|
return true;
|
2012-04-24 18:23:56 -06:00
|
|
|
}
|
2015-05-04 17:58:00 +02:00
|
|
|
#endif
|
x86/apic: Work around boot failure on HP ProLiant DL980 G7 Server systems
When a HP ProLiant DL980 G7 Server boots a regular kernel,
there will be intermittent lost interrupts which could
result in a hang or (in extreme cases) data loss.
The reason is that this system only supports x2apic physical
mode, while the kernel boots with a logical-cluster default
setting.
This bug can be worked around by specifying the "x2apic_phys" or
"nox2apic" boot option, but we want to handle this system
without requiring manual workarounds.
The BIOS sets ACPI_FADT_APIC_PHYSICAL in FADT table.
As all apicids are smaller than 255, BIOS need to pass the
control to the OS with xapic mode, according to x2apic-spec,
chapter 2.9.
Current code handle x2apic when BIOS pass with xapic mode
enabled:
When user specifies x2apic_phys, or FADT indicates PHYSICAL:
1. During madt oem check, apic driver is set with xapic logical
or xapic phys driver at first.
2. enable_IR_x2apic() will enable x2apic_mode.
3. if user specifies x2apic_phys on the boot line, x2apic_phys_probe()
will install the correct x2apic phys driver and use x2apic phys mode.
Otherwise it will skip the driver will let x2apic_cluster_probe to
take over to install x2apic cluster driver (wrong one) even though FADT
indicates PHYSICAL, because x2apic_phys_probe does not check
FADT PHYSICAL.
Add checking x2apic_fadt_phys in x2apic_phys_probe() to fix the
problem.
Signed-off-by: Stoney Wang <song-bo.wang@hp.com>
[ updated the changelog and simplified the code ]
Signed-off-by: Yinghai Lu <yinghai@kernel.org>
Cc: stable@kernel.org
Link: http://lkml.kernel.org/r/1360263182-16226-1-git-send-email-yinghai@kernel.org
Signed-off-by: Ingo Molnar <mingo@kernel.org>
2013-02-07 10:53:02 -08:00
|
|
|
return false;
|
|
|
|
}
|
|
|
|
|
|
|
|
static int x2apic_acpi_madt_oem_check(char *oem_id, char *oem_table_id)
|
|
|
|
{
|
|
|
|
return x2apic_enabled() && (x2apic_phys || x2apic_fadt_phys());
|
2008-07-21 22:08:21 -07:00
|
|
|
}
|
2008-07-10 11:16:59 -07:00
|
|
|
|
2015-11-04 22:57:04 +00:00
|
|
|
static void x2apic_send_IPI(int cpu, int vector)
|
|
|
|
{
|
|
|
|
u32 dest = per_cpu(x86_cpu_to_apicid, cpu);
|
|
|
|
|
x86/apic: Add extra serialization for non-serializing MSRs
Jan Kiszka reported that the x2apic_wrmsr_fence() function uses a plain
MFENCE while the Intel SDM (10.12.3 MSR Access in x2APIC Mode) calls for
MFENCE; LFENCE.
Short summary: we have special MSRs that have weaker ordering than all
the rest. Add fencing consistent with current SDM recommendations.
This is not known to cause any issues in practice, only in theory.
Longer story below:
The reason the kernel uses a different semantic is that the SDM changed
(roughly in late 2017). The SDM changed because folks at Intel were
auditing all of the recommended fences in the SDM and realized that the
x2apic fences were insufficient.
Why was the pain MFENCE judged insufficient?
WRMSR itself is normally a serializing instruction. No fences are needed
because the instruction itself serializes everything.
But, there are explicit exceptions for this serializing behavior written
into the WRMSR instruction documentation for two classes of MSRs:
IA32_TSC_DEADLINE and the X2APIC MSRs.
Back to x2apic: WRMSR is *not* serializing in this specific case.
But why is MFENCE insufficient? MFENCE makes writes visible, but
only affects load/store instructions. WRMSR is unfortunately not a
load/store instruction and is unaffected by MFENCE. This means that a
non-serializing WRMSR could be reordered by the CPU to execute before
the writes made visible by the MFENCE have even occurred in the first
place.
This means that an x2apic IPI could theoretically be triggered before
there is any (visible) data to process.
Does this affect anything in practice? I honestly don't know. It seems
quite possible that by the time an interrupt gets to consume the (not
yet) MFENCE'd data, it has become visible, mostly by accident.
To be safe, add the SDM-recommended fences for all x2apic WRMSRs.
This also leaves open the question of the _other_ weakly-ordered WRMSR:
MSR_IA32_TSC_DEADLINE. While it has the same ordering architecture as
the x2APIC MSRs, it seems substantially less likely to be a problem in
practice. While writes to the in-memory Local Vector Table (LVT) might
theoretically be reordered with respect to a weakly-ordered WRMSR like
TSC_DEADLINE, the SDM has this to say:
In x2APIC mode, the WRMSR instruction is used to write to the LVT
entry. The processor ensures the ordering of this write and any
subsequent WRMSR to the deadline; no fencing is required.
But, that might still leave xAPIC exposed. The safest thing to do for
now is to add the extra, recommended LFENCE.
[ bp: Massage commit message, fix typos, drop accidentally added
newline to tools/arch/x86/include/asm/barrier.h. ]
Reported-by: Jan Kiszka <jan.kiszka@siemens.com>
Signed-off-by: Dave Hansen <dave.hansen@linux.intel.com>
Signed-off-by: Borislav Petkov <bp@suse.de>
Acked-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Acked-by: Thomas Gleixner <tglx@linutronix.de>
Cc: <stable@vger.kernel.org>
Link: https://lkml.kernel.org/r/20200305174708.F77040DD@viggo.jf.intel.com
2020-03-05 09:47:08 -08:00
|
|
|
/* x2apic MSRs are special and need a special fence: */
|
|
|
|
weak_wrmsr_fence();
|
2015-11-04 22:57:04 +00:00
|
|
|
__x2apic_send_IPI_dest(dest, vector, APIC_DEST_PHYSICAL);
|
|
|
|
}
|
|
|
|
|
2011-05-19 16:45:47 -07:00
|
|
|
static void
|
|
|
|
__x2apic_send_IPI_mask(const struct cpumask *mask, int vector, int apic_dest)
|
2008-07-10 11:16:59 -07:00
|
|
|
{
|
|
|
|
unsigned long query_cpu;
|
2011-05-19 16:45:47 -07:00
|
|
|
unsigned long this_cpu;
|
2009-01-28 15:42:24 +01:00
|
|
|
unsigned long flags;
|
2008-07-10 11:16:59 -07:00
|
|
|
|
x86/apic: Add extra serialization for non-serializing MSRs
Jan Kiszka reported that the x2apic_wrmsr_fence() function uses a plain
MFENCE while the Intel SDM (10.12.3 MSR Access in x2APIC Mode) calls for
MFENCE; LFENCE.
Short summary: we have special MSRs that have weaker ordering than all
the rest. Add fencing consistent with current SDM recommendations.
This is not known to cause any issues in practice, only in theory.
Longer story below:
The reason the kernel uses a different semantic is that the SDM changed
(roughly in late 2017). The SDM changed because folks at Intel were
auditing all of the recommended fences in the SDM and realized that the
x2apic fences were insufficient.
Why was the pain MFENCE judged insufficient?
WRMSR itself is normally a serializing instruction. No fences are needed
because the instruction itself serializes everything.
But, there are explicit exceptions for this serializing behavior written
into the WRMSR instruction documentation for two classes of MSRs:
IA32_TSC_DEADLINE and the X2APIC MSRs.
Back to x2apic: WRMSR is *not* serializing in this specific case.
But why is MFENCE insufficient? MFENCE makes writes visible, but
only affects load/store instructions. WRMSR is unfortunately not a
load/store instruction and is unaffected by MFENCE. This means that a
non-serializing WRMSR could be reordered by the CPU to execute before
the writes made visible by the MFENCE have even occurred in the first
place.
This means that an x2apic IPI could theoretically be triggered before
there is any (visible) data to process.
Does this affect anything in practice? I honestly don't know. It seems
quite possible that by the time an interrupt gets to consume the (not
yet) MFENCE'd data, it has become visible, mostly by accident.
To be safe, add the SDM-recommended fences for all x2apic WRMSRs.
This also leaves open the question of the _other_ weakly-ordered WRMSR:
MSR_IA32_TSC_DEADLINE. While it has the same ordering architecture as
the x2APIC MSRs, it seems substantially less likely to be a problem in
practice. While writes to the in-memory Local Vector Table (LVT) might
theoretically be reordered with respect to a weakly-ordered WRMSR like
TSC_DEADLINE, the SDM has this to say:
In x2APIC mode, the WRMSR instruction is used to write to the LVT
entry. The processor ensures the ordering of this write and any
subsequent WRMSR to the deadline; no fencing is required.
But, that might still leave xAPIC exposed. The safest thing to do for
now is to add the extra, recommended LFENCE.
[ bp: Massage commit message, fix typos, drop accidentally added
newline to tools/arch/x86/include/asm/barrier.h. ]
Reported-by: Jan Kiszka <jan.kiszka@siemens.com>
Signed-off-by: Dave Hansen <dave.hansen@linux.intel.com>
Signed-off-by: Borislav Petkov <bp@suse.de>
Acked-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Acked-by: Thomas Gleixner <tglx@linutronix.de>
Cc: <stable@vger.kernel.org>
Link: https://lkml.kernel.org/r/20200305174708.F77040DD@viggo.jf.intel.com
2020-03-05 09:47:08 -08:00
|
|
|
/* x2apic MSRs are special and need a special fence: */
|
|
|
|
weak_wrmsr_fence();
|
2009-03-17 10:16:54 -08:00
|
|
|
|
2008-07-10 11:16:59 -07:00
|
|
|
local_irq_save(flags);
|
2011-05-19 16:45:47 -07:00
|
|
|
|
|
|
|
this_cpu = smp_processor_id();
|
2008-12-16 17:33:59 -08:00
|
|
|
for_each_cpu(query_cpu, mask) {
|
2011-05-19 16:45:47 -07:00
|
|
|
if (apic_dest == APIC_DEST_ALLBUT && this_cpu == query_cpu)
|
|
|
|
continue;
|
2008-07-10 11:16:59 -07:00
|
|
|
__x2apic_send_IPI_dest(per_cpu(x86_cpu_to_apicid, query_cpu),
|
|
|
|
vector, APIC_DEST_PHYSICAL);
|
|
|
|
}
|
|
|
|
local_irq_restore(flags);
|
|
|
|
}
|
|
|
|
|
2011-05-19 16:45:47 -07:00
|
|
|
static void x2apic_send_IPI_mask(const struct cpumask *mask, int vector)
|
|
|
|
{
|
|
|
|
__x2apic_send_IPI_mask(mask, vector, APIC_DEST_ALLINC);
|
|
|
|
}
|
|
|
|
|
2009-01-28 15:42:24 +01:00
|
|
|
static void
|
|
|
|
x2apic_send_IPI_mask_allbutself(const struct cpumask *mask, int vector)
|
2008-07-10 11:16:59 -07:00
|
|
|
{
|
2011-05-19 16:45:47 -07:00
|
|
|
__x2apic_send_IPI_mask(mask, vector, APIC_DEST_ALLBUT);
|
2008-12-16 17:33:52 -08:00
|
|
|
}
|
2008-07-10 11:16:59 -07:00
|
|
|
|
2023-08-08 15:04:07 -07:00
|
|
|
static void __x2apic_send_IPI_shorthand(int vector, u32 which)
|
|
|
|
{
|
|
|
|
unsigned long cfg = __prepare_ICR(which, vector, 0);
|
|
|
|
|
|
|
|
/* x2apic MSRs are special and need a special fence: */
|
|
|
|
weak_wrmsr_fence();
|
|
|
|
native_x2apic_icr_write(cfg, 0);
|
|
|
|
}
|
|
|
|
|
|
|
|
void x2apic_send_IPI_allbutself(int vector)
|
2008-12-16 17:33:52 -08:00
|
|
|
{
|
2019-07-22 20:47:30 +02:00
|
|
|
__x2apic_send_IPI_shorthand(vector, APIC_DEST_ALLBUT);
|
2008-07-10 11:16:59 -07:00
|
|
|
}
|
|
|
|
|
2023-08-08 15:04:07 -07:00
|
|
|
void x2apic_send_IPI_all(int vector)
|
2008-07-10 11:16:59 -07:00
|
|
|
{
|
2019-07-22 20:47:30 +02:00
|
|
|
__x2apic_send_IPI_shorthand(vector, APIC_DEST_ALLINC);
|
2008-07-10 11:16:59 -07:00
|
|
|
}
|
|
|
|
|
2023-08-08 15:04:07 -07:00
|
|
|
void x2apic_send_IPI_self(int vector)
|
|
|
|
{
|
|
|
|
apic_write(APIC_SELF_IPI, vector);
|
|
|
|
}
|
|
|
|
|
|
|
|
void __x2apic_send_IPI_dest(unsigned int apicid, int vector, unsigned int dest)
|
|
|
|
{
|
|
|
|
unsigned long cfg = __prepare_ICR(0, vector, dest);
|
|
|
|
native_x2apic_icr_write(cfg, apicid);
|
|
|
|
}
|
|
|
|
|
2011-05-19 16:45:46 -07:00
|
|
|
static int x2apic_phys_probe(void)
|
|
|
|
{
|
2023-06-17 02:52:36 +05:30
|
|
|
if (!x2apic_mode)
|
|
|
|
return 0;
|
|
|
|
|
|
|
|
if (x2apic_phys || x2apic_fadt_phys())
|
2011-05-19 16:45:46 -07:00
|
|
|
return 1;
|
|
|
|
|
|
|
|
return apic == &apic_x2apic_phys;
|
|
|
|
}
|
|
|
|
|
2023-08-14 10:18:44 +02:00
|
|
|
u32 x2apic_get_apic_id(u32 id)
|
2017-09-13 23:29:16 +02:00
|
|
|
{
|
|
|
|
return id;
|
|
|
|
}
|
|
|
|
|
2016-08-08 16:29:06 -07:00
|
|
|
static struct apic apic_x2apic_phys __ro_after_init = {
|
2009-01-28 02:37:01 +01:00
|
|
|
|
|
|
|
.name = "physical x2apic",
|
2011-05-19 16:45:46 -07:00
|
|
|
.probe = x2apic_phys_probe,
|
2009-01-28 02:37:01 +01:00
|
|
|
.acpi_madt_oem_check = x2apic_acpi_madt_oem_check,
|
|
|
|
|
2020-10-24 22:35:08 +01:00
|
|
|
.dest_mode_logical = false,
|
2009-01-28 02:37:01 +01:00
|
|
|
|
2009-01-28 05:08:44 +01:00
|
|
|
.disable_esr = 0,
|
2009-01-28 02:37:01 +01:00
|
|
|
|
2009-01-28 06:50:47 +01:00
|
|
|
.cpu_present_to_apicid = default_cpu_present_to_apicid,
|
2009-01-28 02:37:01 +01:00
|
|
|
|
2023-08-08 15:04:10 -07:00
|
|
|
.max_apic_id = UINT_MAX,
|
2023-08-08 15:04:11 -07:00
|
|
|
.x2apic_set_max_apicid = true,
|
2011-05-19 16:45:50 -07:00
|
|
|
.get_apic_id = x2apic_get_apic_id,
|
2009-01-28 02:37:01 +01:00
|
|
|
|
2017-09-13 23:29:37 +02:00
|
|
|
.calc_dest_apicid = apic_default_calc_apicid,
|
2009-01-28 02:37:01 +01:00
|
|
|
|
2015-11-04 22:57:04 +00:00
|
|
|
.send_IPI = x2apic_send_IPI,
|
2009-01-28 02:37:01 +01:00
|
|
|
.send_IPI_mask = x2apic_send_IPI_mask,
|
|
|
|
.send_IPI_mask_allbutself = x2apic_send_IPI_mask_allbutself,
|
|
|
|
.send_IPI_allbutself = x2apic_send_IPI_allbutself,
|
|
|
|
.send_IPI_all = x2apic_send_IPI_all,
|
|
|
|
.send_IPI_self = x2apic_send_IPI_self,
|
2023-10-02 14:00:07 +02:00
|
|
|
.nmi_to_offline_cpu = true,
|
2009-01-28 02:37:01 +01:00
|
|
|
|
2009-02-16 23:02:14 -08:00
|
|
|
.read = native_apic_msr_read,
|
|
|
|
.write = native_apic_msr_write,
|
2023-08-08 15:04:15 -07:00
|
|
|
.eoi = native_apic_msr_eoi,
|
2009-02-16 23:02:14 -08:00
|
|
|
.icr_read = native_x2apic_icr_read,
|
|
|
|
.icr_write = native_x2apic_icr_write,
|
2008-07-10 11:16:59 -07:00
|
|
|
};
|
2011-05-20 17:51:17 -07:00
|
|
|
|
|
|
|
apic_driver(apic_x2apic_phys);
|