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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Mon, 13 May 2019 18:28:05 +0200
From:   Alexandre Chartre <>
To:     Andy Lutomirski <>
Cc:     Paolo Bonzini <>,
        Radim Krcmar <>,
        Thomas Gleixner <>,
        Ingo Molnar <>, Borislav Petkov <>,
        "H. Peter Anvin" <>,
        Dave Hansen <>,
        Peter Zijlstra <>,
        kvm list <>, X86 ML <>,
        Linux-MM <>,
        LKML <>,
        Konrad Rzeszutek Wilk <>,, Liran Alon <>,
        Jonathan Adams <>
Subject: Re: [RFC KVM 06/27] KVM: x86: Exit KVM isolation on IRQ entry

On 5/13/19 5:51 PM, Andy Lutomirski wrote:
> On Mon, May 13, 2019 at 7:39 AM Alexandre Chartre
> <> wrote:
>> From: Liran Alon <>
>> Next commits will change most of KVM #VMExit handlers to run
>> in KVM isolated address space. Any interrupt handler raised
>> during execution in KVM address space needs to switch back
>> to host address space.
>> This patch makes sure that IRQ handlers will run in full
>> host address space instead of KVM isolated address space.
> IMO this needs to be somewhere a lot more central.  What about NMI and
> MCE?  Or async page faults?  Or any other entry?

Actually, I am not sure this is effectively useful because the IRQ
handler is probably faulting before it tries to exit isolation, so
the isolation exit will be done by the kvm page fault handler. I need
to check that.


Powered by blists - more mailing lists