KVM Archive on lore.kernel.org
 help / color / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 208767] kernel stack overflow due to Lazy update IOAPIC on an x86_64 *host*, when gpu is passthrough to macos guest vm
Date: Thu, 06 Aug 2020 09:09:28 +0000
Message-ID: <bug-208767-28872-a9ZOJEmpTj@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-208767-28872@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=208767

--- Comment #6 from Yani Stoyanov (yaweb@mail.bg) ---
I am not sure if this is relevant but there was old bug which explains how osx
configure IOAPIC with the wrong polarity bit values. I may be interesting to
take a look (I know it is from 6 years ago).

https://www.contrib.andrew.cmu.edu/~somlo/OSXKVM/index_old.html

the part: 

ACPI-compliant operating systems are expected to query the firmware for an
indication of which polarity type (ActiveLow or ActiveHigh) to use for any
devices with level-triggered interrupts, and to configure the IOAPIC registers
accordingly. Both QEMU and KVM have accumulated a significant number of
optimizations based on the assumption that guest operating systems use
ActiveHigh polarity, and are coded to assume that "physical" and "logical" IRQ
line states are in sync. Even when a misbehaving guest OS (you guessed it, OS X
does this) ignores the ACPI polarity hint (which in QEMU/KVM is ActiveLow, i.e.
"physical"=="logical") and configures the virtual IOAPIC with the wrong
polarity bit values, both QEMU and KVM will mostly use "logical" IRQ line
levels.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

      parent reply index

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-02  9:01 [Bug 208767] New: " bugzilla-daemon
2020-08-02  9:03 ` [Bug 208767] " bugzilla-daemon
2020-08-02  9:19 ` bugzilla-daemon
2020-08-02 10:36 ` bugzilla-daemon
2020-08-02 17:45 ` bugzilla-daemon
2020-08-03  9:43 ` bugzilla-daemon
2020-08-03 20:39 ` [Bug 208767] New: " Jim Mattson
2020-08-03 20:39 ` [Bug 208767] " bugzilla-daemon
2020-08-04  0:25 ` bugzilla-daemon
2020-08-06  9:02 ` bugzilla-daemon
2020-08-06  9:09 ` bugzilla-daemon [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=bug-208767-28872-a9ZOJEmpTj@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=kvm@vger.kernel.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

KVM Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/kvm/0 kvm/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 kvm kvm/ https://lore.kernel.org/kvm \
		kvm@vger.kernel.org
	public-inbox-index kvm

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.kvm


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git