Re: [PATCH] x86/vdso: Remove direct HPET access through the vDSO

2016-04-09 Thread Thomas Gleixner
On Thu, 7 Apr 2016, Andy Lutomirski wrote: > Allowing user code to map the HPET is problematic. HPET > implementations are notoriously buggy, and there are probably many > machines on which even MMIO reads from bogus HPET addresses are > problematic. > > We have a report that the Dell Precision

Re: [PATCH] x86/vdso: Remove direct HPET access through the vDSO

2016-04-09 Thread Thomas Gleixner
On Thu, 7 Apr 2016, Andy Lutomirski wrote: > Allowing user code to map the HPET is problematic. HPET > implementations are notoriously buggy, and there are probably many > machines on which even MMIO reads from bogus HPET addresses are > problematic. > > We have a report that the Dell Precision

Re: [PATCH] x86/vdso: Remove direct HPET access through the vDSO

2016-04-08 Thread Andy Lutomirski
On Apr 8, 2016 3:36 AM, "Borislav Petkov" wrote: > > On Thu, Apr 07, 2016 at 05:16:59PM -0700, Andy Lutomirski wrote: > > Allowing user code to map the HPET is problematic. HPET > > implementations are notoriously buggy, and there are probably many > > machines on which even MMIO

Re: [PATCH] x86/vdso: Remove direct HPET access through the vDSO

2016-04-08 Thread Andy Lutomirski
On Apr 8, 2016 3:36 AM, "Borislav Petkov" wrote: > > On Thu, Apr 07, 2016 at 05:16:59PM -0700, Andy Lutomirski wrote: > > Allowing user code to map the HPET is problematic. HPET > > implementations are notoriously buggy, and there are probably many > > machines on which even MMIO reads from

Re: [PATCH] x86/vdso: Remove direct HPET access through the vDSO

2016-04-08 Thread Borislav Petkov
On Thu, Apr 07, 2016 at 05:16:59PM -0700, Andy Lutomirski wrote: > Allowing user code to map the HPET is problematic. HPET > implementations are notoriously buggy, and there are probably many > machines on which even MMIO reads from bogus HPET addresses are > problematic. > > We have a report

Re: [PATCH] x86/vdso: Remove direct HPET access through the vDSO

2016-04-08 Thread Borislav Petkov
On Thu, Apr 07, 2016 at 05:16:59PM -0700, Andy Lutomirski wrote: > Allowing user code to map the HPET is problematic. HPET > implementations are notoriously buggy, and there are probably many > machines on which even MMIO reads from bogus HPET addresses are > problematic. > > We have a report

[PATCH] x86/vdso: Remove direct HPET access through the vDSO

2016-04-07 Thread Andy Lutomirski
Allowing user code to map the HPET is problematic. HPET implementations are notoriously buggy, and there are probably many machines on which even MMIO reads from bogus HPET addresses are problematic. We have a report that the Dell Precision M2800 with: ACPI: HPET 0xC8FE6238 38 (v01

[PATCH] x86/vdso: Remove direct HPET access through the vDSO

2016-04-07 Thread Andy Lutomirski
Allowing user code to map the HPET is problematic. HPET implementations are notoriously buggy, and there are probably many machines on which even MMIO reads from bogus HPET addresses are problematic. We have a report that the Dell Precision M2800 with: ACPI: HPET 0xC8FE6238 38 (v01