public inbox for kvm@vger.kernel.org
 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] Userspace changes for configuring irq0->inti2 override (v6)
Date: Sun, 14 Jun 2009 11:50:43 +0300	[thread overview]
Message-ID: <4A34B9E3.1020809@redhat.com> (raw)
In-Reply-To: <1244771206-19872-1-git-send-email-eak@us.ibm.com>

Beth Kon wrote:
> These patches resolve the irq0->inti2 override issue, and get the hpet working
> on kvm.
>
> Override and HPET changes are sent as a series because HPET depends on the
> 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).
>
>   

Applied the first four patches; thanks.  See separate reply about patch 5.

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


      parent reply	other threads:[~2009-06-14  8:50 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-12  1:46 [PATCH 1/5] Userspace changes for configuring irq0->inti2 override (v6) Beth Kon
2009-06-12  1:46 ` [PATCH 2/5] " Beth Kon
2009-06-12  1:46 ` [PATCH 3/5] BIOS changes for KVM HPET (v6) Beth Kon
2009-06-12  1:46 ` [PATCH 4/5] Userspace " Beth Kon
2009-06-14  8:55   ` Avi Kivity
2009-06-14  9:00     ` Avi Kivity
2009-06-12  1:46 ` [PATCH 5/5] HPET interaction with in-kernel PIT (v6) Beth Kon
2009-06-14  8:53   ` Avi Kivity
2009-06-14  9:10     ` Jan Kiszka
2009-06-14  9:18       ` Avi Kivity
2009-06-14  9:26         ` Jan Kiszka
2009-06-14  9:35           ` Avi Kivity
2009-06-14  8:50 ` 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=4A34B9E3.1020809@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