From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chris Lalancette Subject: [RFC][PATCH 0/3]: Fixes to IRQ routing Date: Tue, 8 Jun 2010 13:55:00 -0400 Message-ID: <1276019703-18136-1-git-send-email-clalance@redhat.com> Cc: avi@redhat.com, mtosatti@redhat.com To: kvm@vger.kernel.org Return-path: Received: from mx1.redhat.com ([209.132.183.28]:19512 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755723Ab0FHR5T (ORCPT ); Tue, 8 Jun 2010 13:57:19 -0400 Received: from int-mx01.intmail.prod.int.phx2.redhat.com (int-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.11]) by mx1.redhat.com (8.13.8/8.13.8) with ESMTP id o58HvI0e027065 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Tue, 8 Jun 2010 13:57:19 -0400 Sender: kvm-owner@vger.kernel.org List-ID: As we've discussed previously, here is a series of patches to fix some of the IRQ routing issues we have in KVM. With this series in place I was able to successfully kdump a RHEL-5 64-bit, and RHEL-6 32- and 64-bit guest on CPU's other than the BSP. RHEL-5 32-bit kdump still does not work; it gets stuck on "Checking 'hlt' instruction". However, it does that both before and after this series, so there is something else going on there that I still have to debug. I also need to change the "kvm_migrate_pit_timer" function to migrate the timer over to the last CPU that handled the timer interrupt, on the theory that that particlar CPU is likely to handle the timer interrupt again in the near future. The other outstanding question about these patches is how to setup the workqueue. As it stands I have a single workqueue for all guests. However, for efficiency reasons we may want to have one workqueue per guest. Opinions? Chris Lalancette