From mboxrd@z Thu Jan  1 00:00:00 1970
From: Avi Kivity <avi@redhat.com>
Subject: Re: system_powerdown not working for qemu-kvm 0.12.4?
Date: Tue, 12 Oct 2010 09:39:50 +0200
Message-ID: <4CB410C6.5040407@redhat.com>
References: <4BEFDC8D.70007@redhat.com> <AANLkTikyOEf0ZA9WoejLZt2xAOug4YGUmtbXK40ITv9p@mail.gmail.com> <4BF41051.2010608@redhat.com> <AANLkTik2TjWx8YbseR+gnSyU6JkBm7X5uabiymBaXUyh@mail.gmail.com> <4C67C8D2.5000400@redhat.com> <AANLkTi=MKG5hnfW1KfWhPMnfdoMKcnTi_B9UeWPJ37L6@mail.gmail.com> <4CB341E4.3060400@redhat.com> <AANLkTinFe2XaBdnDN8HqMJOPX6OU+rq_skOr_S2domh6@mail.gmail.com> <4CB40515.2030809@redhat.com> <20101012071124.GA10190@morn.localdomain> <20101012071404.GA18974@redhat.com> <4CB40D87.6000405@redhat.com> <4CB40F56.20402@redhat.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=windows-1252;
	format=flowed
Content-Transfer-Encoding: QUOTED-PRINTABLE
Cc: "Kevin O'Connor" <kevin@koconnor.net>,
	Ruben Kerkhof <ruben@rubenkerkhof.com>,
	Teck Choon Giam <giamteckchoon@gmail.com>,
	kvm@vger.kernel.org, seabios@seabios.org
To: Gleb Natapov <gleb@redhat.com>
Return-path: <kvm-owner@vger.kernel.org>
Received: from mx1.redhat.com ([209.132.183.28]:57279 "EHLO mx1.redhat.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1754915Ab0JLHkR (ORCPT <rfc822;kvm@vger.kernel.org>);
	Tue, 12 Oct 2010 03:40:17 -0400
In-Reply-To: <4CB40F56.20402@redhat.com>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

  On 10/12/2010 09:33 AM, Avi Kivity wrote:
>
> Aha! The piix4 specification updates says:
>
>>
>> =95 IRQ9OUT#/GPO29 should be labeled as IRQ9OUT/GPO29
>

Even more explicitly:

> 14. IRQ9OUT# Is Active HI
> Problem: The signal identified as IRQ9OUT#/GPO29, pin F3, is not=20
> active level LO, it is active level HI, when APIC Chip Select=20
> (XBCS[8]) is set.
> Implication: This signal is typically used in Dual Processor capable=20
> systems and is connected to an IOAPIC. If the IOAPIC input is=20
> programmed for level LO, and SCIs or SM Bus events in the=20
> PIIX4/PIIX4E/PIIX4M are programmed to be reported on IRQ9OUT, devices=
=20
> using these will not be recognized by the IOAPIC and will not work=20
> correctly.
> Workaround: Program the appropriate input of the IOAPIC to active=20
> level HI.
> Status: This will not be fixed in the PIIX4/PIIX4E/PIIX4M. This is=20
> planned to be incorporated into the PIIX4 datasheet as a specificatio=
n=20
> change.



--=20
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.