Searched hist:d4647f0a2ad711101067cba69c34716758aa1e48 (Results 1 – 5 of 5) sorted by relevance
| /linux/arch/arm64/include/asm/ |
| H A D | spectre.h | d4647f0a2ad711101067cba69c34716758aa1e48 Wed Sep 16 00:30:17 CEST 2020 Will Deacon <will@kernel.org> arm64: Rewrite Spectre-v2 mitigation code
The Spectre-v2 mitigation code is pretty unwieldy and hard to maintain.
This is largely due to it being written hastily, without much clue as to
how things would pan out, and also because it ends up mixing policy and
state in such a way that it is very difficult to figure out what's going
on.
Rewrite the Spectre-v2 mitigation so that it clearly separates state from
policy and follows a more structured approach to handling the mitigation.
Signed-off-by: Will Deacon <will@kernel.org>
|
| H A D | processor.h | diff d4647f0a2ad711101067cba69c34716758aa1e48 Wed Sep 16 00:30:17 CEST 2020 Will Deacon <will@kernel.org> arm64: Rewrite Spectre-v2 mitigation code
The Spectre-v2 mitigation code is pretty unwieldy and hard to maintain.
This is largely due to it being written hastily, without much clue as to
how things would pan out, and also because it ends up mixing policy and
state in such a way that it is very difficult to figure out what's going
on.
Rewrite the Spectre-v2 mitigation so that it clearly separates state from
policy and follows a more structured approach to handling the mitigation.
Signed-off-by: Will Deacon <will@kernel.org>
|
| H A D | cpufeature.h | diff d4647f0a2ad711101067cba69c34716758aa1e48 Wed Sep 16 00:30:17 CEST 2020 Will Deacon <will@kernel.org> arm64: Rewrite Spectre-v2 mitigation code
The Spectre-v2 mitigation code is pretty unwieldy and hard to maintain.
This is largely due to it being written hastily, without much clue as to
how things would pan out, and also because it ends up mixing policy and
state in such a way that it is very difficult to figure out what's going
on.
Rewrite the Spectre-v2 mitigation so that it clearly separates state from
policy and follows a more structured approach to handling the mitigation.
Signed-off-by: Will Deacon <will@kernel.org>
|
| /linux/arch/arm64/kvm/ |
| H A D | psci.c | diff d4647f0a2ad711101067cba69c34716758aa1e48 Wed Sep 16 00:30:17 CEST 2020 Will Deacon <will@kernel.org> arm64: Rewrite Spectre-v2 mitigation code
The Spectre-v2 mitigation code is pretty unwieldy and hard to maintain.
This is largely due to it being written hastily, without much clue as to
how things would pan out, and also because it ends up mixing policy and
state in such a way that it is very difficult to figure out what's going
on.
Rewrite the Spectre-v2 mitigation so that it clearly separates state from
policy and follows a more structured approach to handling the mitigation.
Signed-off-by: Will Deacon <will@kernel.org>
|
| /linux/arch/arm64/kernel/ |
| H A D | proton-pack.c | diff d4647f0a2ad711101067cba69c34716758aa1e48 Wed Sep 16 00:30:17 CEST 2020 Will Deacon <will@kernel.org> arm64: Rewrite Spectre-v2 mitigation code
The Spectre-v2 mitigation code is pretty unwieldy and hard to maintain.
This is largely due to it being written hastily, without much clue as to
how things would pan out, and also because it ends up mixing policy and
state in such a way that it is very difficult to figure out what's going
on.
Rewrite the Spectre-v2 mitigation so that it clearly separates state from
policy and follows a more structured approach to handling the mitigation.
Signed-off-by: Will Deacon <will@kernel.org>
|