All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Lieven <pl@kamp.de>
To: Paolo Bonzini <pbonzini@redhat.com>,
	Laszlo Ersek <lersek@redhat.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Qemu and PCI Interrupt Link?
Date: Thu, 7 Jul 2016 13:39:30 +0200	[thread overview]
Message-ID: <577E3F72.4000706@kamp.de> (raw)
In-Reply-To: <6fa89d4e-1a32-c28d-5133-5308ae30cdf6@redhat.com>

Am 05.07.2016 um 22:53 schrieb Paolo Bonzini:
>
> 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 startup:
>>>
>>> ACPI: No IRQ available for PCI Interrupt Link [LNKS]. Try pci=noacpi or
>>> acpi=off
>>>
>>> Cmdline:
>>> x86_64-softmmu/qemu-system-x86_64 -enable-kvm -m 2048 -cdrom
>>> ~/Downloads/ubuntu-16.04-desktop-amd64.iso
>>>
>>> Is this expected?
>> This seems to come from kernel commit 5ebc76035303. Thankfully the
>> commit message is quite detailed.
>>
>> The commit message makes me think that the kernel patch is incorrect. It
>> certainly seems to conflict with the following SeaBIOS commit:
>>
>> commit f64a472a481784231fbf8541825501df411b11d1
>> Author: Paolo Bonzini <pbonzini@redhat.com>
>> Date:   Thu Dec 13 08:42:02 2012 +0100
>>
>>      acpi: reintroduce LNKS
>>
>> 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.

Okay, so just ignore this message for good or is there anything futher
I can/should do?

Peter

      reply	other threads:[~2016-07-07 11:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-04 13:14 [Qemu-devel] Qemu and PCI Interrupt Link? Peter Lieven
2016-07-05 18:30 ` Laszlo Ersek
2016-07-05 20:53   ` Paolo Bonzini
2016-07-07 11:39     ` Peter Lieven [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=577E3F72.4000706@kamp.de \
    --to=pl@kamp.de \
    --cc=lersek@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.