All of lore.kernel.org
 help / color / mirror / Atom feed
From: Beth Kon <eak@us.ibm.com>
To: Avi Kivity <avi@redhat.com>, kvm <kvm@vger.kernel.org>
Subject: Re: [PATCH 1/4] BIOS changes for configuring irq0->inti2 override(v2)
Date: Thu, 07 May 2009 12:30:11 -0400	[thread overview]
Message-ID: <4A030C93.50907@us.ibm.com> (raw)
In-Reply-To: <4A0304C3.4050103@redhat.com>

Avi Kivity wrote:
> Beth Kon wrote:
>> These patches resolve the irq0->inti2 override issue, and get the 
>> hpet working
>> on kvm.
>> They are dependent on Jes Sorensen's recent 
>> 0006-qemu-kvm-irq-routing.patch.
>>
>> 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).
>>
>> A couple of months ago, Marcelo was seeing RHEL5 guests complain of 
>> invalid
>> checksum with these patches, but later he couldn't reproduce it, and 
>> I'm not seeing it now. While all guests still need to be fully 
>> tested, everything appears to be in order.  I've tested on win2k864, 
>> win2k832, RHEL5.3 32 bit, and ubuntu 8.10 64 bit.
>>   
>
> What are the changes relative to v1?
Just merge issues with the changes you put in when moving to the newer 
bios. I submitted prematurely, incorrectly thinking I was done testing. 
When I finished, some problems surfaced.
>
>> @@ -477,6 +480,7 @@ void wrmsr_smp(uint32_t index, uint64_t val)
>>  #define QEMU_CFG_SIGNATURE  0x00
>>  #define QEMU_CFG_ID         0x01
>>  #define QEMU_CFG_UUID       0x02
>> +#define QEMU_CFG_IRQ0_OVERRIDE 0x0e
>>   
>
> As noted, this should be in the arch local space.
>
The base changes were not in the code yet. As we discussed on IRC, I'll 
resubmit once they're there.


      reply	other threads:[~2009-05-07 16:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-07 14:56 [PATCH 1/4] BIOS changes for configuring irq0->inti2 override (v2) Beth Kon
2009-05-07 14:57 ` [PATCH 2/4] Userspace " Beth Kon
2009-05-07 14:57 ` [PATCH 3/4] BIOS changes for KVM HPET (v2) Beth Kon
2009-05-07 14:57 ` [PATCH 4/4] Userspace " Beth Kon
2009-05-07 15:56 ` [PATCH 1/4] BIOS changes for configuring irq0->inti2 override (v2) Avi Kivity
2009-05-07 16:30   ` Beth Kon [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=4A030C93.50907@us.ibm.com \
    --to=eak@us.ibm.com \
    --cc=avi@redhat.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 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.