diff options
| author |   Juergen Gross <jgross@suse.com> | 2017-04-27 07:01:20 +0200 |
|---|---|---|
| committer | Juergen Gross <jgross@suse.com> | 2017-05-11 15:55:14 +0200 |
| commit | def9331a12977770cc6132d79f8e6565871e8e38 (patch) | |
| tree | e060cefab582b280d97681608d15bb959050b0d4 /arch/arm64/boot/dts/marvell/armada-8020.dtsi | |
| parent | xen/x86: Do not call xen_init_time_ops() until shared_info is initialized (diff) | |
| download | linux-dev-def9331a12977770cc6132d79f8e6565871e8e38.tar.xz linux-dev-def9331a12977770cc6132d79f8e6565871e8e38.zip | |
x86/amd: don't set X86_BUG_SYSRET_SS_ATTRS when running under Xen
When running as Xen pv guest X86_BUG_SYSRET_SS_ATTRS must not be set
on AMD cpus.
This bug/feature bit is kind of special as it will be used very early
when switching threads. Setting the bit and clearing it a little bit
later leaves a critical window where things can go wrong. This time
window has enlarged a little bit by using setup_clear_cpu_cap() instead
of the hypervisor's set_cpu_features callback. It seems this larger
window now makes it rather easy to hit the problem.
The proper solution is to never set the bit in case of Xen.
Signed-off-by: Juergen Gross <jgross@suse.com>
Reviewed-by: Boris Ostrovsky <boris.ostrovsky@oracle.com>
Acked-by: Thomas Gleixner <tglx@linutronix.de>
Signed-off-by: Juergen Gross <jgross@suse.com>
Diffstat (limited to 'arch/arm64/boot/dts/marvell/armada-8020.dtsi')
0 files changed, 0 insertions, 0 deletions