On 20 November 2017 at 14:43, Mark Rutland wrote:
> On Mon, Nov 20, 2017 at 02:41:47PM +, Mark Rutland wrote:
>> On Wed, Nov 15, 2017 at 01:34:16PM -0800, Sami Tolvanen wrote:
>> > Use -fno-jump-tables to make sure clang doesn't generate branches
>> > to EL1 virtual
On 20 November 2017 at 14:43, Mark Rutland wrote:
> On Mon, Nov 20, 2017 at 02:41:47PM +, Mark Rutland wrote:
>> On Wed, Nov 15, 2017 at 01:34:16PM -0800, Sami Tolvanen wrote:
>> > Use -fno-jump-tables to make sure clang doesn't generate branches
>> > to EL1 virtual addresses.
>>
>> Are there
On Mon, Nov 20, 2017 at 02:41:47PM +, Mark Rutland wrote:
> On Wed, Nov 15, 2017 at 01:34:16PM -0800, Sami Tolvanen wrote:
> > Use -fno-jump-tables to make sure clang doesn't generate branches
> > to EL1 virtual addresses.
>
> Are there any other reasons that clang might generate absolute
>
On Mon, Nov 20, 2017 at 02:41:47PM +, Mark Rutland wrote:
> On Wed, Nov 15, 2017 at 01:34:16PM -0800, Sami Tolvanen wrote:
> > Use -fno-jump-tables to make sure clang doesn't generate branches
> > to EL1 virtual addresses.
>
> Are there any other reasons that clang might generate absolute
>
On Wed, Nov 15, 2017 at 01:34:16PM -0800, Sami Tolvanen wrote:
> Use -fno-jump-tables to make sure clang doesn't generate branches
> to EL1 virtual addresses.
Are there any other reasons that clang might generate absolute
references/relocations?
It would be nice if there was the option to
On Wed, Nov 15, 2017 at 01:34:16PM -0800, Sami Tolvanen wrote:
> Use -fno-jump-tables to make sure clang doesn't generate branches
> to EL1 virtual addresses.
Are there any other reasons that clang might generate absolute
references/relocations?
It would be nice if there was the option to
On Thu, Nov 16, 2017 at 11:46:17AM +, Will Deacon wrote:
> Can you elaborate a bit more on exactly what you saw failing here,
> please?
Mark noticed that clang built kernels fail to boot when the kernel
starts at EL2:
http://lkml.iu.edu/hypermail/linux/kernel/1711.0/02817.html
Turns out
On Thu, Nov 16, 2017 at 11:46:17AM +, Will Deacon wrote:
> Can you elaborate a bit more on exactly what you saw failing here,
> please?
Mark noticed that clang built kernels fail to boot when the kernel
starts at EL2:
http://lkml.iu.edu/hypermail/linux/kernel/1711.0/02817.html
Turns out
On Wed, Nov 15, 2017 at 01:34:16PM -0800, Sami Tolvanen wrote:
> Use -fno-jump-tables to make sure clang doesn't generate branches
> to EL1 virtual addresses.
Can you elaborate a bit more on exactly what you saw failing here, please?
Whilst it's obviously broken to jump to EL1 from EL2 w/o VHE,
On Wed, Nov 15, 2017 at 01:34:16PM -0800, Sami Tolvanen wrote:
> Use -fno-jump-tables to make sure clang doesn't generate branches
> to EL1 virtual addresses.
Can you elaborate a bit more on exactly what you saw failing here, please?
Whilst it's obviously broken to jump to EL1 from EL2 w/o VHE,
Use -fno-jump-tables to make sure clang doesn't generate branches
to EL1 virtual addresses.
Suggested-by: AKASHI Takahiro
Signed-off-by: Sami Tolvanen
---
arch/arm64/kvm/hyp/Makefile | 4
1 file changed, 4 insertions(+)
diff --git
Use -fno-jump-tables to make sure clang doesn't generate branches
to EL1 virtual addresses.
Suggested-by: AKASHI Takahiro
Signed-off-by: Sami Tolvanen
---
arch/arm64/kvm/hyp/Makefile | 4
1 file changed, 4 insertions(+)
diff --git a/arch/arm64/kvm/hyp/Makefile
12 matches
Mail list logo