From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Gabriel L. Somlo" Subject: Re: RFC: ioapic polarity vs. qemu os-x guest Date: Fri, 14 Feb 2014 17:06:00 -0500 Message-ID: <20140214220600.GI29329@ERROL.INI.CMU.EDU> References: <20140130204423.GK29329@ERROL.INI.CMU.EDU> <20140211182330.GC29329@ERROL.INI.CMU.EDU> <20140211195444.GB10951@redhat.com> <20140214211311.GH29329@ERROL.INI.CMU.EDU> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: "Michael S. Tsirkin" , "kvm@vger.kernel.org" , "qemu-devel@nongnu.org" , "eddie.dong@intel.com" To: Alexander Graf Return-path: Received: from mail-qa0-f50.google.com ([209.85.216.50]:42536 "EHLO mail-qa0-f50.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753001AbaBNWHi (ORCPT ); Fri, 14 Feb 2014 17:07:38 -0500 Received: by mail-qa0-f50.google.com with SMTP id cm18so19352081qab.9 for ; Fri, 14 Feb 2014 14:07:37 -0800 (PST) Content-Disposition: inline In-Reply-To: Sender: kvm-owner@vger.kernel.org List-ID: On Fri, Feb 14, 2014 at 10:21:09PM +0100, Alexander Graf wrote: > > Can't you just turn the polarity around in the pci host adapter? I tried this: diff --git a/hw/pci/pci.c b/hw/pci/pci.c index 1221f32..0e86d21 100644 --- a/hw/pci/pci.c +++ b/hw/pci/pci.c @@ -118,13 +118,13 @@ static int pci_bar(PCIDevice *d, int reg) static inline int pci_irq_state(PCIDevice *d, int irq_num) { - return (d->irq_state >> irq_num) & 0x1; + return !(d->irq_state >> irq_num) & 0x1; } static inline void pci_set_irq_state(PCIDevice *d, int irq_num, int level) { d->irq_state &= ~(0x1 << irq_num); - d->irq_state |= level << irq_num; + d->irq_state &= ~(level << irq_num); } static void pci_change_irq_level(PCIDevice *pci_dev, int irq_num, int change) @@ -229,7 +229,7 @@ static void pcibus_reset(BusState *qbus) } for (i = 0; i < bus->nirq; i++) { - assert(bus->irq_count[i] == 0); + assert(bus->irq_count[i] != 0); } } --- but now OS X freezes during boot right after [ PCI configuration begin ] [ PCI configuration end, bridges 1, devices 10 ] RTC: Only single RAM bank (128 bytes) which all looks normal, except the process is supposed to continue on from there and doesn't :) On Linux, I get Fedora 20 live all the way up with no obvious/loud complaints, but mouse and keyboard don't work at all... I have to admit I'm a bit out of my depth here, though :) --Gabriel