Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752818AbbKJMXK (ORCPT ); Tue, 10 Nov 2015 07:23:10 -0500 Received: from mail-wm0-f42.google.com ([74.125.82.42]:33438 "EHLO mail-wm0-f42.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751379AbbKJMXE (ORCPT ); Tue, 10 Nov 2015 07:23:04 -0500 From: Paolo Bonzini To: linux-kernel@vger.kernel.org, kvm@vger.kernel.org Cc: digitaleric@google.com Subject: [PATCH 0/3] Infinite loops in microcode while running guests Date: Tue, 10 Nov 2015 13:22:51 +0100 Message-Id: <1447158174-10484-1-git-send-email-pbonzini@redhat.com> X-Mailer: git-send-email 1.8.3.1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1024 Lines: 29 Yes, these can happen. The issue is that benign exceptions are delivered serially, but two of them (#DB and #AC) can also happen during exception delivery itself. The subsequent infinite stream of exceptions causes the processor to never exit guest mode. Paolo Eric Northup (1): KVM: x86: work around infinite loop in microcode when #AC is delivered Paolo Bonzini (2): KVM: svm: unconditionally intercept #DB KVM: x86: rename update_db_bp_intercept to update_bp_intercept arch/x86/include/asm/kvm_host.h | 2 +- arch/x86/include/uapi/asm/svm.h | 1 + arch/x86/kvm/svm.c | 22 +++++++++++----------- arch/x86/kvm/vmx.c | 7 +++++-- arch/x86/kvm/x86.c | 2 +- 5 files changed, 19 insertions(+), 15 deletions(-) -- 1.8.3.1 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/