linux-kernel - [PATCH 0/4] AER-KVM: Error containment of PCI pass-thru devices assigned to KVM guests

lists.openwall.net		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 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <F9E001219150CB45BEDC82A650F360C90146F4DA@G4W3208.americas.hpqcorp.net>
Date:	Tue, 20 Nov 2012 06:31:48 +0000
From:	"Pandarathil, Vijaymohan R" <vijaymohan.pandarathil@...com>
To:	"kvm@...r.kernel.org" <kvm@...r.kernel.org>,
	"linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>,
	"qemu-devel@...gnu.org" <qemu-devel@...gnu.org>
CC:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: [PATCH 0/4] AER-KVM: Error containment of PCI pass-thru devices
 assigned to KVM guests

Add support for error containment when a PCI pass-thru device assigned to a KVM
guest encounters an error. This is for PCIe devices/drivers that support AER
functionality. When the OS is notified of an error in a device either
through the firmware first approach or through an interrupt handled by the AER
root port driver, concerned subsystems are notified by invoking callbacks
registered by these subsystems. The device is also marked as tainted till the
corresponding driver recovery routines are successful. 

KVM module registers for a notification of such errors. In the KVM callback
routine, a global counter is incremented to keep track of the error
notification. Before each CPU enters guest mode to execute guest code,
appropriate checks are done to see if the impacted device belongs to the guest
or not. If the device belongs to the guest, qemu hypervisor for the guest is
informed and the guest is immediately brought down, thus preventing or
minimizing chances of any bad data being written out by the guest driver
after the device has encountered an error.

Note that the changes here are specific to  PCI pass-thru devices and is
confined to error containment. Error recovery is not included in these set
of changes. A future set of patches is planned to address SR-IOV devices and
VFIO devices assigned to guests as well as recovery without bringing down
the guest.

---
Vijay Mohan Pandarathil(4):

 AER-PCI: Add infrastructure for notification of errors to other subsystems
 AER-GHES: Add support for error notification in firmware first approach of AER
 AER-KVM: Integration of KVM with AER for PCI pass-thru devices
 AER-QEMU: Bring down the guest when KVM detects a PCI device error

 arch/x86/include/asm/kvm_host.h    |  1 +
 arch/x86/kvm/x86.c                 | 44 ++++++++++++++++++++++++++++++++++++++
 drivers/acpi/apei/ghes.c           | 41 +++++++++++++++++++++++++++++++++++
 drivers/pci/pcie/aer/aerdrv.c      | 20 +++++++++++++++++
 drivers/pci/pcie/aer/aerdrv_core.c |  9 +++++++-
 include/linux/aer.h                |  4 ++++
 include/linux/kvm_host.h           |  4 ++++
 include/linux/pci.h                |  2 ++
 include/uapi/linux/kvm.h           |  1 +
 virt/kvm/assigned-dev.c            | 34 +++++++++++++++++++++++++++++
 virt/kvm/kvm_main.c                | 34 +++++++++++++++++++++++++++++
 11 files changed, 193 insertions(+), 1 deletion(-)

Qemu files changed

 kvm-all.c                 |    6 ++++++
 linux-headers/linux/kvm.h |    1 +
 2 files changed, 7 insertions(+)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/