From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:57381)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <pbonzini@redhat.com>) id 1bKXLN-0002Bj-RE
	for qemu-devel@nongnu.org; Tue, 05 Jul 2016 16:53:22 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <pbonzini@redhat.com>) id 1bKXLH-0002H6-Rw
	for qemu-devel@nongnu.org; Tue, 05 Jul 2016 16:53:20 -0400
Received: from mx1.redhat.com ([209.132.183.28]:40727)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <pbonzini@redhat.com>) id 1bKXLH-0002Gu-MK
	for qemu-devel@nongnu.org; Tue, 05 Jul 2016 16:53:15 -0400
References: <577A611E.3010204@kamp.de>
	<f20f1c6f-4942-a9fe-0138-70bcca6ceddc@redhat.com>
From: Paolo Bonzini <pbonzini@redhat.com>
Message-ID: <6fa89d4e-1a32-c28d-5133-5308ae30cdf6@redhat.com>
Date: Tue, 5 Jul 2016 22:53:10 +0200
MIME-Version: 1.0
In-Reply-To: <f20f1c6f-4942-a9fe-0138-70bcca6ceddc@redhat.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [Qemu-devel] Qemu and PCI Interrupt Link?
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel/>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Laszlo Ersek <lersek@redhat.com>, Peter Lieven <pl@kamp.de>, "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>



On 05/07/2016 20:30, Laszlo Ersek wrote:
> On 07/04/16 15:14, Peter Lieven wrote:
>> Hi,
>>
>> i noticed that newer guest kernels emit the following message at start=
up:
>>
>> ACPI: No IRQ available for PCI Interrupt Link [LNKS]. Try pci=3Dnoacpi=
 or
>> acpi=3Doff
>>
>> Cmdline:
>> x86_64-softmmu/qemu-system-x86_64 -enable-kvm -m 2048 -cdrom
>> ~/Downloads/ubuntu-16.04-desktop-amd64.iso
>>
>> Is this expected?
>=20
> This seems to come from kernel commit 5ebc76035303. Thankfully the
> commit message is quite detailed.
>=20
> The commit message makes me think that the kernel patch is incorrect. I=
t
> certainly seems to conflict with the following SeaBIOS commit:
>=20
> commit f64a472a481784231fbf8541825501df411b11d1
> Author: Paolo Bonzini <pbonzini@redhat.com>
> Date:   Thu Dec 13 08:42:02 2012 +0100
>=20
>     acpi: reintroduce LNKS
>=20
> That SeaBIOS patch is where we have the identical functionality in QEMU
> from (see QEMU commits 74523b850189a and c35b6e8032105).

The error is harmless.  LNKS has been there forever and I suspect no one
really knows why it was introduced in the first place.  The link for the
device that uses LNKS probably can be changed back to LNKA since the SCI
is specified in the FADT, but again---who knows why it was changed.

Paolo