On Wed, 2018-01-10 at 07:15 +, David Woodhouse wrote:
> I'd really like to know what went wrong though. Did we merge Borislav's
> attempt to peek at jumps inside alternatives, perchance? Will take a
> look...
Ah, it only happens if I run in KVM, not with Qemu's CPU; that's why it
didn't show
On Wed, 2018-01-10 at 07:15 +, David Woodhouse wrote:
> I'd really like to know what went wrong though. Did we merge Borislav's
> attempt to peek at jumps inside alternatives, perchance? Will take a
> look...
Ah, it only happens if I run in KVM, not with Qemu's CPU; that's why it
didn't show
On Tue, 2018-01-09 at 17:30 -0800, Andi Kleen wrote:
> I assume you don't need FILL_RETURN_BUFFER on AMD. If not let me know
> and we can add a X86_FEATURE_RETPOLINE_COMMON
FWIW the AMD doc I have here (Tom, is that public now?) does say we
should fill the RSB. That's a minor tweak
On Tue, 2018-01-09 at 17:30 -0800, Andi Kleen wrote:
> I assume you don't need FILL_RETURN_BUFFER on AMD. If not let me know
> and we can add a X86_FEATURE_RETPOLINE_COMMON
FWIW the AMD doc I have here (Tom, is that public now?) does say we
should fill the RSB. That's a minor tweak
On Tue, 2018-01-09 at 16:39 -0800, Linus Torvalds wrote:
> On Tue, Jan 9, 2018 at 4:31 PM, Andi Kleen
> wrote:
> >
> >
> > The following patch fixes it for me. Something doesn't
> > seem to work with ALTERNATIVE_2. It adds only a few bytes
> > more code, so seems
On Tue, 2018-01-09 at 16:39 -0800, Linus Torvalds wrote:
> On Tue, Jan 9, 2018 at 4:31 PM, Andi Kleen
> wrote:
> >
> >
> > The following patch fixes it for me. Something doesn't
> > seem to work with ALTERNATIVE_2. It adds only a few bytes
> > more code, so seems acceptable.
> Ugh. It's kind of
On Wed, Jan 10, 2018 at 02:50:12AM +0100, Thomas Gleixner wrote:
> On Tue, 9 Jan 2018, Andi Kleen wrote:
>
> > > > I think there are areas that rely on X86_FEATURE_RETPOLINE being set
> > > > even if X86_FEATURE_RETPOLINE_AMD is set. For example, line 261 in
> > > > arch/x86/entry/entry_32.S is
On Wed, Jan 10, 2018 at 02:50:12AM +0100, Thomas Gleixner wrote:
> On Tue, 9 Jan 2018, Andi Kleen wrote:
>
> > > > I think there are areas that rely on X86_FEATURE_RETPOLINE being set
> > > > even if X86_FEATURE_RETPOLINE_AMD is set. For example, line 261 in
> > > > arch/x86/entry/entry_32.S is
On Tue, 9 Jan 2018, Andi Kleen wrote:
> > > I think there are areas that rely on X86_FEATURE_RETPOLINE being set
> > > even if X86_FEATURE_RETPOLINE_AMD is set. For example, line 261 in
> > > arch/x86/entry/entry_32.S is only checking for X86_FEATURE_RETPOLINE.
> >
> > I audited the difference
On Tue, 9 Jan 2018, Andi Kleen wrote:
> > > I think there are areas that rely on X86_FEATURE_RETPOLINE being set
> > > even if X86_FEATURE_RETPOLINE_AMD is set. For example, line 261 in
> > > arch/x86/entry/entry_32.S is only checking for X86_FEATURE_RETPOLINE.
> >
> > I audited the difference
> > I think there are areas that rely on X86_FEATURE_RETPOLINE being set
> > even if X86_FEATURE_RETPOLINE_AMD is set. For example, line 261 in
> > arch/x86/entry/entry_32.S is only checking for X86_FEATURE_RETPOLINE.
>
> I audited the difference places. They all seem ok.
Actually 32bit is not
> > I think there are areas that rely on X86_FEATURE_RETPOLINE being set
> > even if X86_FEATURE_RETPOLINE_AMD is set. For example, line 261 in
> > arch/x86/entry/entry_32.S is only checking for X86_FEATURE_RETPOLINE.
>
> I audited the difference places. They all seem ok.
Actually 32bit is not
On Tue, Jan 09, 2018 at 06:45:34PM -0600, Tom Lendacky wrote:
> On 1/9/2018 6:40 PM, Thomas Gleixner wrote:
> > On Tue, 9 Jan 2018, Linus Torvalds wrote:
> >
> >> On Tue, Jan 9, 2018 at 4:31 PM, Andi Kleen wrote:
> >>>
> >>> The following patch fixes it for me. Something
On Tue, Jan 09, 2018 at 06:45:34PM -0600, Tom Lendacky wrote:
> On 1/9/2018 6:40 PM, Thomas Gleixner wrote:
> > On Tue, 9 Jan 2018, Linus Torvalds wrote:
> >
> >> On Tue, Jan 9, 2018 at 4:31 PM, Andi Kleen wrote:
> >>>
> >>> The following patch fixes it for me. Something doesn't
> >>> seem to
On Tue, 9 Jan 2018, Andi Kleen wrote:
> > Then just make sure X86_FEATURE_RETPOLINE_AMD disables
> > X86_FEATURE_RETPOLINE.
> >
> > That is both simpler an dsmaller, no?
>
> Yes that works, and is clearly better/simpler.
>
> Tested-by: Andi Kleen
>
> Thomas, I assume
On Tue, 9 Jan 2018, Andi Kleen wrote:
> > Then just make sure X86_FEATURE_RETPOLINE_AMD disables
> > X86_FEATURE_RETPOLINE.
> >
> > That is both simpler an dsmaller, no?
>
> Yes that works, and is clearly better/simpler.
>
> Tested-by: Andi Kleen
>
> Thomas, I assume you will fix it up, or
> Then just make sure X86_FEATURE_RETPOLINE_AMD disables X86_FEATURE_RETPOLINE.
>
> That is both simpler an dsmaller, no?
Yes that works, and is clearly better/simpler.
Tested-by: Andi Kleen
Thomas, I assume you will fix it up, or let me know if I should
send another
> Then just make sure X86_FEATURE_RETPOLINE_AMD disables X86_FEATURE_RETPOLINE.
>
> That is both simpler an dsmaller, no?
Yes that works, and is clearly better/simpler.
Tested-by: Andi Kleen
Thomas, I assume you will fix it up, or let me know if I should
send another patch.
-Andi
On Tue, 9 Jan 2018, Tom Lendacky wrote:
> On 1/9/2018 6:40 PM, Thomas Gleixner wrote:
> > On Tue, 9 Jan 2018, Linus Torvalds wrote:
> >
> >> On Tue, Jan 9, 2018 at 4:31 PM, Andi Kleen wrote:
> >>>
> >>> The following patch fixes it for me. Something doesn't
> >>> seem to
On Tue, 9 Jan 2018, Tom Lendacky wrote:
> On 1/9/2018 6:40 PM, Thomas Gleixner wrote:
> > On Tue, 9 Jan 2018, Linus Torvalds wrote:
> >
> >> On Tue, Jan 9, 2018 at 4:31 PM, Andi Kleen wrote:
> >>>
> >>> The following patch fixes it for me. Something doesn't
> >>> seem to work with ALTERNATIVE_2.
On 1/9/2018 6:40 PM, Thomas Gleixner wrote:
> On Tue, 9 Jan 2018, Linus Torvalds wrote:
>
>> On Tue, Jan 9, 2018 at 4:31 PM, Andi Kleen wrote:
>>>
>>> The following patch fixes it for me. Something doesn't
>>> seem to work with ALTERNATIVE_2. It adds only a few bytes
>>>
On 1/9/2018 6:40 PM, Thomas Gleixner wrote:
> On Tue, 9 Jan 2018, Linus Torvalds wrote:
>
>> On Tue, Jan 9, 2018 at 4:31 PM, Andi Kleen wrote:
>>>
>>> The following patch fixes it for me. Something doesn't
>>> seem to work with ALTERNATIVE_2. It adds only a few bytes
>>> more code, so seems
On Tue, 9 Jan 2018, Linus Torvalds wrote:
> On Tue, Jan 9, 2018 at 4:31 PM, Andi Kleen wrote:
> >
> > The following patch fixes it for me. Something doesn't
> > seem to work with ALTERNATIVE_2. It adds only a few bytes
> > more code, so seems acceptable.
>
> Ugh. It's kind
On Tue, 9 Jan 2018, Linus Torvalds wrote:
> On Tue, Jan 9, 2018 at 4:31 PM, Andi Kleen wrote:
> >
> > The following patch fixes it for me. Something doesn't
> > seem to work with ALTERNATIVE_2. It adds only a few bytes
> > more code, so seems acceptable.
>
> Ugh. It's kind of stupid, though.
>
On Tue, Jan 9, 2018 at 4:31 PM, Andi Kleen wrote:
>
> The following patch fixes it for me. Something doesn't
> seem to work with ALTERNATIVE_2. It adds only a few bytes
> more code, so seems acceptable.
Ugh. It's kind of stupid, though.
Why is the code sequence not simply:
On Tue, Jan 9, 2018 at 4:31 PM, Andi Kleen wrote:
>
> The following patch fixes it for me. Something doesn't
> seem to work with ALTERNATIVE_2. It adds only a few bytes
> more code, so seems acceptable.
Ugh. It's kind of stupid, though.
Why is the code sequence not simply:
ALTERNATIVE "",
On Tue, 9 Jan 2018, Andi Kleen wrote:
> From: Andi Kleen
>
> With the latest tip x86/pti I get oopses when booting
> a 64bit VM in qemu with RETPOLINE/gcc7 and PTI enabled.
>
> The following patch fixes it for me. Something doesn't
> seem to work with ALTERNATIVE_2. It
On Tue, 9 Jan 2018, Andi Kleen wrote:
> From: Andi Kleen
>
> With the latest tip x86/pti I get oopses when booting
> a 64bit VM in qemu with RETPOLINE/gcc7 and PTI enabled.
>
> The following patch fixes it for me. Something doesn't
> seem to work with ALTERNATIVE_2. It adds only a few bytes
>
From: Andi Kleen
With the latest tip x86/pti I get oopses when booting
a 64bit VM in qemu with RETPOLINE/gcc7 and PTI enabled.
The following patch fixes it for me. Something doesn't
seem to work with ALTERNATIVE_2. It adds only a few bytes
more code, so seems acceptable.
From: Andi Kleen
With the latest tip x86/pti I get oopses when booting
a 64bit VM in qemu with RETPOLINE/gcc7 and PTI enabled.
The following patch fixes it for me. Something doesn't
seem to work with ALTERNATIVE_2. It adds only a few bytes
more code, so seems acceptable.
Signed-off-by: Andi
30 matches
Mail list logo