lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Fri, 12 Jan 2018 22:20:51 -0800
From:   Andy Lutomirski <>
To:     Dave Hansen <>
Cc:     "Raj, Ashok" <>,
        Andy Lutomirski <>,
        LKML <>,
        Thomas Gleixner <>,
        Tim Chen <>,
        Linus Torvalds <>,
        Greg KH <>,
        Andrea Arcangeli <>,
        Andi Kleen <>,
        Arjan Van De Ven <>,
        David Woodhouse <>,
        Peter Zijlstra <>,
        Dan Williams <>,
        Paolo Bonzini <>,
        Jun Nakajima <>,
        Asit Mallick <>
Subject: Re: [PATCH 1/5] x86/ibrs: Introduce native_rdmsrl, and native_wrmsrl

On Thu, Jan 11, 2018 at 9:03 PM, Dave Hansen <> wrote:
> On 01/11/2018 07:01 PM, Raj, Ashok wrote:
>> On Thu, Jan 11, 2018 at 06:20:13PM -0800, Andy Lutomirski wrote:
>>> On Thu, Jan 11, 2018 at 5:52 PM, Raj, Ashok <> wrote:
>>>>> What's wrong with native_read_msr()?
>>>> Yes, i think i should have added to msr.h. The names didn't read as a
>>>> pair, one was native_read_msr, wrmsrl could be taken over when paravirt is
>>>> defined?
>>> Why do you need to override paravirt?
>> The idea was since these MSR's are passed through we shouldn't need to
>> handle them any differently. Also its best to do this as soon as possible
>> and avoid longer paths to get this barrier to hardware.
> We were also worried about the indirect calls that are part of the
> paravirt interfaces when retpolines are not in place.

How could those possibly be any worse than any other indirect call in
the kernel?

Powered by blists - more mailing lists