From: Avi Kivity <avi@qumranet.com>
To: kvm-ia64@vger.kernel.org
Subject: Re: [PATCH] kvm-ia64 irq assignment 1/2 kernel
Date: Thu, 12 Jun 2008 12:24:05 +0000 [thread overview]
Message-ID: <48511565.60005@qumranet.com> (raw)
In-Reply-To: <51CFAB8CB6883745AE7B93B3E084EBE201CC875F@pdsmsx412.ccr.corp.intel.com>
Alexander Graf wrote:
>>
>> Apparently this is broken on x86 too. I was just trying this patch
>> with Mac OS X as target and magically the in-kernel APIC starts
>> working, so I guess something is going wrong already here.
>> Btw, according to the ACPI tables, all PCI interrupts are currently
>> defined Active-Low.
>
So there's something else wrong.
> Sorry, ActiveHigh that is. Nevertheless I am having trouble with this
> since the very first time I used osx inside KVM. Does PCI allow Active
>
> > Interrupt (, Level, ActiveHigh, Shared)
>
> According to the PCI 3.0 Spec, "Interrupts on PCI are optional and
> defined as 'level sensitive,' asserted low (negative true)".
The pci interrupts are active low, but they are converted to active high
by the chipset qemu emulates, so active high is correct. Does OS X boot
from the qemu bios or something else? If the latter, it may need
adjustment.
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
WARNING: multiple messages have this Message-ID (diff)
From: Avi Kivity <avi@qumranet.com>
To: Alexander Graf <agraf@suse.de>
Cc: "Xu, Anthony" <anthony.xu@intel.com>, Jes Sorensen <jes@sgi.com>,
kvm@vger.kernel.org, kvm-ia64@vger.kernel.org
Subject: Re: [PATCH] kvm-ia64 irq assignment 1/2 kernel
Date: Thu, 12 Jun 2008 15:24:05 +0300 [thread overview]
Message-ID: <48511565.60005@qumranet.com> (raw)
In-Reply-To: <484CF4EA.1030406@suse.de>
Alexander Graf wrote:
>>
>> Apparently this is broken on x86 too. I was just trying this patch
>> with Mac OS X as target and magically the in-kernel APIC starts
>> working, so I guess something is going wrong already here.
>> Btw, according to the ACPI tables, all PCI interrupts are currently
>> defined Active-Low.
>
So there's something else wrong.
> Sorry, ActiveHigh that is. Nevertheless I am having trouble with this
> since the very first time I used osx inside KVM. Does PCI allow Active
>
> > Interrupt (, Level, ActiveHigh, Shared)
>
> According to the PCI 3.0 Spec, "Interrupts on PCI are optional and
> defined as 'level sensitive,' asserted low (negative true)".
The pci interrupts are active low, but they are converted to active high
by the chipset qemu emulates, so active high is correct. Does OS X boot
from the qemu bios or something else? If the latter, it may need
adjustment.
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
next prev parent reply other threads:[~2008-06-12 12:24 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-06 15:58 [PATCH] kvm-ia64 irq assignment 1/2 kernel Xu, Anthony
2008-06-06 15:58 ` Xu, Anthony
2008-06-06 19:58 ` Avi Kivity
2008-06-06 19:58 ` Avi Kivity
2008-06-09 8:58 ` Alexander Graf
2008-06-09 8:58 ` Alexander Graf
2008-06-09 9:16 ` Alexander Graf
2008-06-09 9:16 ` Alexander Graf
2008-06-10 6:33 ` Xu, Anthony
2008-06-10 6:33 ` Xu, Anthony
2008-06-10 7:25 ` Alexander Graf
2008-06-10 7:25 ` Alexander Graf
2008-06-12 12:24 ` Avi Kivity [this message]
2008-06-12 12:24 ` Avi Kivity
2008-06-12 12:30 ` Avi Kivity
2008-06-12 12:30 ` Avi Kivity
-- strict thread matches above, loose matches on Subject: below --
2008-06-10 7:57 [RFC]RE: " Xu, Anthony
2008-06-10 7:57 ` Xu, Anthony
2008-06-11 14:24 ` Alexander Graf
2008-06-11 14:24 ` Alexander Graf
2008-06-11 16:02 ` Marcelo Tosatti
2008-06-11 16:02 ` Marcelo Tosatti
2008-06-11 16:16 ` Marcelo Tosatti
2008-06-11 16:16 ` Marcelo Tosatti
2008-06-12 12:34 ` Avi Kivity
2008-06-12 12:34 ` Avi Kivity
2008-06-12 16:08 ` Xu, Anthony
2008-06-12 16:08 ` Xu, Anthony
2008-06-12 16:15 ` Xu, Anthony
2008-06-12 16:15 ` Xu, Anthony
2008-06-12 16:19 ` Xu, Anthony
2008-06-12 16:19 ` Xu, Anthony
2008-06-12 16:20 ` Xu, Anthony
2008-06-12 16:20 ` Xu, Anthony
2008-06-14 22:58 ` Marcelo Tosatti
2008-06-14 22:58 ` Marcelo Tosatti
2008-06-16 1:13 ` Xu, Anthony
2008-06-16 1:13 ` Xu, Anthony
2008-07-02 9:11 ` Jes Sorensen
2008-07-02 9:11 ` Jes Sorensen
2008-07-03 1:22 ` Xu, Anthony
2008-07-03 1:22 ` Xu, Anthony
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=48511565.60005@qumranet.com \
--to=avi@qumranet.com \
--cc=kvm-ia64@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
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.