public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Beth Kon <eak@us.ibm.com>
To: Sebastian Herbszt <herbszt@gmx.de>
Cc: avi@redhat.com, kvm@vger.kernel.org
Subject: Re: [PATCH 1/5] BIOS changes for configuring irq0->inti2 override (v4)
Date: Thu, 11 Jun 2009 17:23:17 -0400	[thread overview]
Message-ID: <4A3175C5.6070205@us.ibm.com> (raw)
In-Reply-To: <96E2F18C325F48788FEB591C6547B4B5@FSCPC>

Sebastian Herbszt wrote:
> 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).
>>
>> Changes from v3:
>>
>> - changes based on comments from Avi and Gleb.
>> - corrected legacy enable/disable for in-kernel PIT. The code now best
>>  approximates a multiplexer that disables PIT interrupts when HPET is 
>>  in legacy mode (as described by HPET spec). Any changes to the PIT 
>> that  may occur while HPET is operating in legacy mode are saved, so 
>> if  HPET leaves legacy mode, the PIT is just reenabled, with mode 
>> set      to whatever the last setting from guest was. Legacy mode is 
>> disabled
>>  at least during crash and shutdown (in Linux), so this needs to be 
>>  handled properly.
>>
>>
>> ---
>> kvm/bios/rombios32.c |   60 
>> ++++++++++++++++++++++++++++++++++++-------------
>> 1 files changed, 44 insertions(+), 16 deletions(-)
>
> What about the mptable entry count?
> Think it would need something like
>
> #ifdef BX_QEMU
>  if (irq0_override)
>    putle16(&q, smp_cpus + 17); /* entry count */
>  else
>    putle16(&q, smp_cpus + 18); /* entry count */
> #else
>  putle16(&q, smp_cpus + 18); /* entry count */
> #endif
>
> Your patch "Fix non-ACPI Timer Interrupt Routing - v3" [1] included 
> such a change.
>
> [1] http://lists.gnu.org/archive/html/qemu-devel/2009-04/msg01396.html
Yes, I lost that somehow! Thanks (again!).

>
> - Sebastian
>


  reply	other threads:[~2009-06-11 21:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-11 14:42 [PATCH 1/5] BIOS changes for configuring irq0->inti2 override (v4) Beth Kon
2009-06-11 14:42 ` [PATCH 2/5] Userspace " Beth Kon
2009-06-11 14:42 ` [PATCH 3/5] BIOS changes for KVM HPET (v5) Beth Kon
2009-06-11 14:42 ` [PATCH 4/5] Userspace changes for KVM HPET (v4) Beth Kon
2009-06-11 14:42 ` [PATCH 5/5] HPET interaction with in-kernel PIT Beth Kon
2009-06-11 20:50 ` [PATCH 1/5] BIOS changes for configuring irq0->inti2 override (v4) Sebastian Herbszt
2009-06-11 21:23   ` Beth Kon [this message]
2009-06-11 21:46     ` Beth Kon

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=4A3175C5.6070205@us.ibm.com \
    --to=eak@us.ibm.com \
    --cc=avi@redhat.com \
    --cc=herbszt@gmx.de \
    --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