Hi Dave,
On Mon, Jul 16, 2018 at 10:07:44PM -0400, David H. Gutteridge wrote:
> I redid my testing on bare metal and in a VM (as with my previous
> testing
> efforts: https://lkml.org/lkml/2018/2/19/844, same setups
> and coverage,
> plus CONFIG_X86_DEBUG_ENTRY_CR3 enabled too) with the
>
Hi Dave,
On Mon, Jul 16, 2018 at 10:07:44PM -0400, David H. Gutteridge wrote:
> I redid my testing on bare metal and in a VM (as with my previous
> testing
> efforts: https://lkml.org/lkml/2018/2/19/844, same setups
> and coverage,
> plus CONFIG_X86_DEBUG_ENTRY_CR3 enabled too) with the
>
On Wed, 2018-07-11 at 13:29 +0200, Joerg Roedel wrote:
> Hi,
>
> here is version 7 of my patches to enable PTI on x86-32.
> Changes to the previous version are:
>
> * Rebased to v4.18-rc4
>
> * Introduced pti_finalize() which is called after
> mark_readonly() and used to
On Wed, 2018-07-11 at 13:29 +0200, Joerg Roedel wrote:
> Hi,
>
> here is version 7 of my patches to enable PTI on x86-32.
> Changes to the previous version are:
>
> * Rebased to v4.18-rc4
>
> * Introduced pti_finalize() which is called after
> mark_readonly() and used to
Hi!
> here is version 7 of my patches to enable PTI on x86-32.
> Changes to the previous version are:
>
> * Rebased to v4.18-rc4
>
> * Introduced pti_finalize() which is called after
> mark_readonly() and used to update the kernel
> mappings in the user page-table
Hi!
> here is version 7 of my patches to enable PTI on x86-32.
> Changes to the previous version are:
>
> * Rebased to v4.18-rc4
>
> * Introduced pti_finalize() which is called after
> mark_readonly() and used to update the kernel
> mappings in the user page-table
On 07/11/2018 03:57 PM, Thomas Backlund wrote:
> Den 2018-07-11 kl. 20:28, skrev Jiri Kosina:
>> On Wed, 11 Jul 2018, Linus Torvalds wrote:
>>
>>> It's the testing that worries me most. Pretty much no developers run
>>> 32-bit any more, and I'd be most worried about the odd interactions
>>> that
On 07/11/2018 03:57 PM, Thomas Backlund wrote:
> Den 2018-07-11 kl. 20:28, skrev Jiri Kosina:
>> On Wed, 11 Jul 2018, Linus Torvalds wrote:
>>
>>> It's the testing that worries me most. Pretty much no developers run
>>> 32-bit any more, and I'd be most worried about the odd interactions
>>> that
On Wed 2018-07-11 09:28:39, Linus Torvalds wrote:
> On Wed, Jul 11, 2018 at 4:30 AM Joerg Roedel wrote:
> >
> > I did the load-testing again with 'perf top', the ldt_gdt
> > self-test and a kernel-compile running in a loop again.
>
> So none of the patches looked scary to me, but then, neither
On Wed 2018-07-11 09:28:39, Linus Torvalds wrote:
> On Wed, Jul 11, 2018 at 4:30 AM Joerg Roedel wrote:
> >
> > I did the load-testing again with 'perf top', the ldt_gdt
> > self-test and a kernel-compile running in a loop again.
>
> So none of the patches looked scary to me, but then, neither
Den 2018-07-11 kl. 20:28, skrev Jiri Kosina:
On Wed, 11 Jul 2018, Linus Torvalds wrote:
It's the testing that worries me most. Pretty much no developers run
32-bit any more, and I'd be most worried about the odd interactions that
might be hw-specific. Some crazy EFI mapping setup or the
Den 2018-07-11 kl. 20:28, skrev Jiri Kosina:
On Wed, 11 Jul 2018, Linus Torvalds wrote:
It's the testing that worries me most. Pretty much no developers run
32-bit any more, and I'd be most worried about the odd interactions that
might be hw-specific. Some crazy EFI mapping setup or the
On Wed, 11 Jul 2018, Linus Torvalds wrote:
> It's the testing that worries me most. Pretty much no developers run
> 32-bit any more, and I'd be most worried about the odd interactions that
> might be hw-specific. Some crazy EFI mapping setup or the similar odd
> case that simply requires a
On Wed, 11 Jul 2018, Linus Torvalds wrote:
> It's the testing that worries me most. Pretty much no developers run
> 32-bit any more, and I'd be most worried about the odd interactions that
> might be hw-specific. Some crazy EFI mapping setup or the similar odd
> case that simply requires a
On Wed, Jul 11, 2018 at 4:30 AM Joerg Roedel wrote:
>
> I did the load-testing again with 'perf top', the ldt_gdt
> self-test and a kernel-compile running in a loop again.
So none of the patches looked scary to me, but then, neither did
earlier versions.
It's the testing that worries me most.
On Wed, Jul 11, 2018 at 4:30 AM Joerg Roedel wrote:
>
> I did the load-testing again with 'perf top', the ldt_gdt
> self-test and a kernel-compile running in a loop again.
So none of the patches looked scary to me, but then, neither did
earlier versions.
It's the testing that worries me most.
Hi,
here is version 7 of my patches to enable PTI on x86-32.
Changes to the previous version are:
* Rebased to v4.18-rc4
* Introduced pti_finalize() which is called after
mark_readonly() and used to update the kernel
mappings in the user page-table after
Hi,
here is version 7 of my patches to enable PTI on x86-32.
Changes to the previous version are:
* Rebased to v4.18-rc4
* Introduced pti_finalize() which is called after
mark_readonly() and used to update the kernel
mappings in the user page-table after
18 matches
Mail list logo
