From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [PATCH 1/5] Userspace changes for configuring irq0->inti2 override (v6) Date: Sun, 14 Jun 2009 11:50:43 +0300 Message-ID: <4A34B9E3.1020809@redhat.com> References: <1244771206-19872-1-git-send-email-eak@us.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: kvm@vger.kernel.org To: Beth Kon Return-path: Received: from mx2.redhat.com ([66.187.237.31]:50323 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750770AbZFNIup (ORCPT ); Sun, 14 Jun 2009 04:50:45 -0400 In-Reply-To: <1244771206-19872-1-git-send-email-eak@us.ibm.com> Sender: kvm-owner@vger.kernel.org List-ID: Beth Kon wrote: > These patches resolve the irq0->inti2 override issue, and get the hpet working > on kvm. > > Override and HPET changes are sent as a series because HPET depends on the > override. Win2k8 expects the HPET interrupt on inti2, regardless of whether > an override exists in the BIOS. And the HPET spec states that in legacy mode, > timer interrupt is on inti2. > > The irq0->inti2 override will always be used unless the kernel cannot do irq > routing (i.e., compatibility with old kernels). So if the kernel is capable, > userspace sets up irq0->inti2 via the irq routing interface, and adds the > irq0->inti2 override to the MADT interrupt source override table, > and the mp table (for the no-acpi case). > > Applied the first four patches; thanks. See separate reply about patch 5. -- error compiling committee.c: too many arguments to function