From: Avi Kivity <avi@qumranet.com>
To: "Xu, Anthony" <anthony.xu@intel.com>
Cc: Alexander Graf <agraf@suse.de>, Jes Sorensen <jes@sgi.com>,
kvm@vger.kernel.org, kvm-ia64@vger.kernel.org
Subject: Re: [RFC]RE: [PATCH] kvm-ia64 irq assignment 1/2 kernel
Date: Thu, 12 Jun 2008 15:34:10 +0300 [thread overview]
Message-ID: <485117C2.3050009@qumranet.com> (raw)
In-Reply-To: <51CFAB8CB6883745AE7B93B3E084EBE201CC8A61@pdsmsx412.ccr.corp.intel.com>
Xu, Anthony wrote:
> Thanks for comments
>
> Basically we are on the same page, while I didn't find your patch about
> irq assignment, can you post it in this thread again, thx?
> Below patch makes all PCI devices use level-trigger , active low
> interrupt, it worked well when running linux guest, I didn't try windows
> guest yet.
> (didn't have windows image in hand)
>
> Please comment!
>
> If this is acceptabled, we can figure out how to use IOAPIC in kvm/ia32
> based on this. Which will reduce irq sharing dramatically.
>
>
> Thanks,
> Anthony
>
>
>
> diff --git a/bios/acpi-dsdt.dsl b/bios/acpi-dsdt.dsl
> index 21fc76a..4b5e824 100755
> --- a/bios/acpi-dsdt.dsl
> +++ b/bios/acpi-dsdt.dsl
> @@ -974,7 +974,7 @@ DefinitionBlock (
> Name(_HID, EISAID("PNP0C0F")) // PCI interrupt link
> Name(_UID, 1)
> Name(_PRS, ResourceTemplate(){
> - Interrupt (, Level, ActiveHigh, Shared)
> + Interrupt (, Level, ActiveLow, Shared)
> { 5, 10, 11 }
>
I think this will fail for guests which use the PIC, since the PIC is
always active high.
For x86 the interrupts will have to be active high since that's how piix
works.
--
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:36 UTC|newest]
Thread overview: 21+ 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 19:58 ` Avi Kivity
2008-06-09 8:58 ` Alexander Graf
2008-06-09 9:16 ` Alexander Graf
2008-06-12 12:24 ` Avi Kivity
2008-06-10 6:33 ` Xu, Anthony
2008-06-10 7:25 ` Alexander Graf
2008-06-10 7:57 ` [RFC]RE: " Xu, Anthony
2008-06-11 14:24 ` Alexander Graf
2008-06-11 16:02 ` Marcelo Tosatti
2008-06-12 16:15 ` Xu, Anthony
2008-06-14 22:58 ` Marcelo Tosatti
2008-06-16 1:13 ` Xu, Anthony
2008-07-02 9:11 ` Jes Sorensen
2008-07-03 1:22 ` Xu, Anthony
2008-06-12 16:08 ` Xu, Anthony
2008-06-11 16:16 ` Marcelo Tosatti
2008-06-12 16:19 ` Xu, Anthony
2008-06-12 12:34 ` Avi Kivity [this message]
2008-06-12 16:20 ` Xu, Anthony
2008-06-12 12:30 ` Avi Kivity
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=485117C2.3050009@qumranet.com \
--to=avi@qumranet.com \
--cc=agraf@suse.de \
--cc=anthony.xu@intel.com \
--cc=jes@sgi.com \
--cc=kvm-ia64@vger.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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox