Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1513139
| From | Daniel Micay <danielmicay@gmail.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [kernel-hardening] rowhammer protection [was Re: Getting interrupt every million cache misses] |
| Date | 2016-11-01 08:30 +0100 |
| Message-ID | <syBGa-5AA-9@gated-at.bofh.it> (permalink) |
| References | (6 earlier) <sxc78-6yE-29@gated-at.bofh.it> <sxdwe-7Es-7@gated-at.bofh.it> <sxg13-Tz-11@gated-at.bofh.it> <syg8G-8jp-31@gated-at.bofh.it> <syATL-542-3@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
[Multipart message — attachments visible in raw view] - view raw
On Tue, 2016-11-01 at 07:33 +0100, Ingo Molnar wrote: > * Pavel Machek <pavel@ucw.cz> wrote: > > > I'm not going to buy broken hardware just for a test. > > Can you suggest a method to find heavily rowhammer affected hardware? > Only by > testing it, or are there some chipset IDs ranges or dmidecode info > that will > pinpoint potentially affected machines? > > Thanks, > > Ingo You can read the memory timing values, but you can't know if they're reasonable for that hardware. Higher quality memory can have better timings without being broken. The only relevant information would be the memory model, combined with an expensive / time consuming effort to build a blacklist based on testing. It doesn't seem realistic, unless it's done in a coarse way based on brand and the date information. I don't know how to get this data on Linux. The CPU-Z tool for Windows knows how to obtain it but it's based on a proprietary library. You definitely don't need to buy broken hardware to test a broken hardware setup though. You just need a custom computer build where motherboards expose the memory timing configuration. You can make it more vulnerable by raising the refresh period (tREF). I wanted to play around with that but haven't gotten around to it.
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Re: Getting interrupt every million cache misses Pavel Machek <pavel@ucw.cz> - 2016-10-27 16:40 +0200
Re: Getting interrupt every million cache misses Peter Zijlstra <peterz@infradead.org> - 2016-10-27 16:40 +0200
Re: Getting interrupt every million cache misses Kees Cook <keescook@chromium.org> - 2016-10-27 22:50 +0200
rowhammer protection [was Re: Getting interrupt every million cache misses] Pavel Machek <pavel@ucw.cz> - 2016-10-27 23:30 +0200
Re: rowhammer protection [was Re: Getting interrupt every million cache misses] Ingo Molnar <mingo@kernel.org> - 2016-10-28 09:10 +0200
Re: rowhammer protection [was Re: Getting interrupt every million cache misses] Pavel Machek <pavel@ucw.cz> - 2016-10-28 11:00 +0200
Re: rowhammer protection [was Re: Getting interrupt every million cache misses] Ingo Molnar <mingo@kernel.org> - 2016-10-28 11:00 +0200
Re: rowhammer protection [was Re: Getting interrupt every million cache misses] Pavel Machek <pavel@ucw.cz> - 2016-10-28 14:00 +0200
Re: rowhammer protection [was Re: Getting interrupt every million cache misses] Peter Zijlstra <peterz@infradead.org> - 2016-10-28 11:10 +0200
Re: rowhammer protection [was Re: Getting interrupt every million cache misses] Vegard Nossum <vegard.nossum@gmail.com> - 2016-10-28 11:30 +0200
Re: rowhammer protection [was Re: Getting interrupt every million cache misses] Ingo Molnar <mingo@kernel.org> - 2016-10-28 11:40 +0200
Re: rowhammer protection [was Re: Getting interrupt every million cache misses] Vegard Nossum <vegard.nossum@gmail.com> - 2016-10-28 11:50 +0200
Re: [kernel-hardening] Re: rowhammer protection [was Re: Getting interrupt every million cache misses] Mark Rutland <mark.rutland@arm.com> - 2016-10-28 12:00 +0200
Re: rowhammer protection [was Re: Getting interrupt every million cache misses] Pavel Machek <pavel@ucw.cz> - 2016-10-28 13:30 +0200
Re: [kernel-hardening] rowhammer protection [was Re: Getting interrupt every million cache misses] Mark Rutland <mark.rutland@arm.com> - 2016-10-28 12:00 +0200
Re: [kernel-hardening] rowhammer protection [was Re: Getting interrupt every million cache misses] Pavel Machek <pavel@ucw.cz> - 2016-10-28 13:30 +0200
Re: [kernel-hardening] rowhammer protection [was Re: Getting interrupt every million cache misses] Mark Rutland <mark.rutland@arm.com> - 2016-10-28 16:10 +0200
Re: [kernel-hardening] rowhammer protection [was Re: Getting interrupt every million cache misses] Peter Zijlstra <peterz@infradead.org> - 2016-10-28 16:20 +0200
Re: [kernel-hardening] rowhammer protection [was Re: Getting interrupt every million cache misses] Pavel Machek <pavel@ucw.cz> - 2016-10-28 20:40 +0200
Re: [kernel-hardening] rowhammer protection [was Re: Getting interrupt every million cache misses] Peter Zijlstra <peterz@infradead.org> - 2016-10-28 20:50 +0200
Re: [kernel-hardening] rowhammer protection [was Re: Getting interrupt every million cache misses] Pavel Machek <pavel@ucw.cz> - 2016-11-02 19:20 +0100
Re: [kernel-hardening] rowhammer protection [was Re: Getting interrupt every million cache misses] Pavel Machek <pavel@ucw.cz> - 2016-10-28 19:30 +0200
Re: Re: [kernel-hardening] rowhammer protection [was Re: Getting interrupt every million cache misses] Daniel Gruss <daniel@gruss.cc> - 2016-10-29 15:20 +0200
Re: Re: [kernel-hardening] rowhammer protection [was Re: Getting interrupt every million cache misses] Pavel Machek <pavel@ucw.cz> - 2016-10-29 21:50 +0200
Re: [kernel-hardening] rowhammer protection [was Re: Getting interrupt every million cache misses] Daniel Gruss <daniel@gruss.cc> - 2016-10-29 22:10 +0200
Re: [kernel-hardening] rowhammer protection [was Re: Getting interrupt every million cache misses] Pavel Machek <pavel@ucw.cz> - 2016-10-29 23:10 +0200
Re: [kernel-hardening] rowhammer protection [was Re: Getting interrupt every million cache misses] Daniel Gruss <daniel@gruss.cc> - 2016-10-29 23:10 +0200
Re: [kernel-hardening] rowhammer protection [was Re: Getting interrupt every million cache misses] Pavel Machek <pavel@ucw.cz> - 2016-10-29 23:50 +0200
Re: [kernel-hardening] rowhammer protection [was Re: Getting interrupt every million cache misses] Daniel Gruss <daniel@gruss.cc> - 2016-10-30 00:00 +0200
Re: [kernel-hardening] rowhammer protection [was Re: Getting interrupt every million cache misses] Pavel Machek <pavel@ucw.cz> - 2016-10-30 00:10 +0200
Re: [kernel-hardening] rowhammer protection [was Re: Getting interrupt every million cache misses] Daniel Gruss <daniel@gruss.cc> - 2016-10-30 00:10 +0200
Re: [kernel-hardening] rowhammer protection [was Re: Getting interrupt every million cache misses] Pavel Machek <pavel@ucw.cz> - 2016-10-31 09:30 +0100
Re: [kernel-hardening] rowhammer protection [was Re: Getting interrupt every million cache misses] Mark Rutland <mark.rutland@arm.com> - 2016-10-31 15:50 +0100
Re: [kernel-hardening] rowhammer protection [was Re: Getting interrupt every million cache misses] Pavel Machek <pavel@ucw.cz> - 2016-10-31 22:20 +0100
Re: [kernel-hardening] rowhammer protection [was Re: Getting interrupt every million cache misses] Mark Rutland <mark.rutland@arm.com> - 2016-10-31 23:10 +0100
Re: [kernel-hardening] rowhammer protection [was Re: Getting interrupt every million cache misses] Ingo Molnar <mingo@kernel.org> - 2016-11-01 07:40 +0100
Re: [kernel-hardening] rowhammer protection [was Re: Getting interrupt every million cache misses] Daniel Micay <danielmicay@gmail.com> - 2016-11-01 08:30 +0100
Re: [kernel-hardening] rowhammer protection [was Re: Getting interrupt every million cache misses] Daniel Gruss <daniel@gruss.cc> - 2016-11-01 09:00 +0100
Re: [kernel-hardening] rowhammer protection [was Re: Getting interrupt every million cache misses] Daniel Gruss <daniel@gruss.cc> - 2016-11-01 09:20 +0100
Re: [kernel-hardening] rowhammer protection [was Re: Getting interrupt every million cache misses] Pavel Machek <pavel@ucw.cz> - 2016-11-01 09:20 +0100
csiph-web