kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Beth Kon <eak@us.ibm.com>
Cc: kvm@vger.kernel.org
Subject: Re: [PATCH 1/5] BIOS changes for irq0->inti2 override (v9)
Date: Wed, 08 Jul 2009 15:01:49 +0300	[thread overview]
Message-ID: <4A548AAD.8030209@redhat.com> (raw)
In-Reply-To: <1246981838-20465-1-git-send-email-eak@us.ibm.com>

On 07/07/2009 06:50 PM, Beth Kon wrote:
>      bios: allow qemu to configure irq0->inti2 override
>
>      Win2k8 expects the HPET interrupt on inti2, regardless of whether
>      an override exists in the BIOS. And the HPET spec states that in legacy mode,
>      timer interrupt is on inti2.
>
>      The irq0->inti2 override will always be used unless the kernel cannot do irq
>      routing (i.e., compatibility with old kernels). So if the kernel is capable,
>      userspace sets up irq0->inti2 via the irq routing interface, and adds the
>      irq0->inti2 override to the MADT interrupt source override table,
>      and the mp table (for the no-acpi case).
>
>      Changes from v8 - Incorporated Gleb's comments to patch 1/5 and 4/5.
>                        In 1/5, removed a "return" per Gleb's comment.
>                        See 4/5 for v8->v9 change description.
>
>    

This series doesn't boot for me - Linux says the 8254 is not connected 
to ioapic.  I pushed it as the 'hpet' branch again, can you take a look?

-- 
error compiling committee.c: too many arguments to function


      parent reply	other threads:[~2009-07-08 11:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-07 15:50 [PATCH 1/5] BIOS changes for irq0->inti2 override (v9) Beth Kon
2009-07-07 15:50 ` [PATCH 2/5] Userspace changes for irq0->inti2 override support (v9) Beth Kon
2009-07-07 15:50 ` [PATCH 3/5] BIOS changes for qemu-kvm hpet " Beth Kon
2009-07-07 15:50 ` [PATCH 4/5] Userspace changes for qemu-kvm HPET support(v9) Beth Kon
2009-07-07 15:50 ` [PATCH 5/5] Kernel changes for HPET legacy support(v9) Beth Kon
2009-07-08 12:01 ` Avi Kivity [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=4A548AAD.8030209@redhat.com \
    --to=avi@redhat.com \
    --cc=eak@us.ibm.com \
    --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;
as well as URLs for NNTP newsgroup(s).