From: Jan Kiszka <jan.kiszka@siemens.com>
To: Bernhard Kohl <bernhard.kohl@nsn.com>
Cc: "kvm@vger.kernel.org" <kvm@vger.kernel.org>,
Marcelo Tosatti <mtosatti@redhat.com>
Subject: Re: [PATCH] qemu-kvm-x86: consider the irq0override flag in kvm_arch_init_irq_routing
Date: Mon, 07 Feb 2011 11:29:10 +0100 [thread overview]
Message-ID: <4D4FC976.5010800@siemens.com> (raw)
In-Reply-To: <4D4FC6BE.2010203@nsn.com>
On 2011-02-07 11:17, Bernhard Kohl wrote:
> Am 07.02.2011 10:42, schrieb ext Jan Kiszka:
>> Hi Bernhard,
>>
>> On 2010-09-14 15:51, Bernhard Kohl wrote:
>>> The setting of the irq0override flag must be also passed properly
>>> to the KVM_IRQCHIP_IOAPIC.
>>>
>>> Signed-off-by: Bernhard Kohl<bernhard.kohl@nsn.com>
>>> ---
>>> qemu-kvm-x86.c | 4 ++--
>>> 1 files changed, 2 insertions(+), 2 deletions(-)
>>>
>>> diff --git a/qemu-kvm-x86.c b/qemu-kvm-x86.c
>>> index fd974b3..e35c234 100644
>>> --- a/qemu-kvm-x86.c
>>> +++ b/qemu-kvm-x86.c
>>> @@ -1388,9 +1388,9 @@ int kvm_arch_init_irq_routing(void)
>>> }
>>> }
>>> for (i = 0; i< 24; ++i) {
>>> - if (i == 0) {
>>> + if (i == 0&& irq0override) {
>>> r = kvm_add_irq_route(kvm_context, i, KVM_IRQCHIP_IOAPIC, 2);
>>> - } else if (i != 2) {
>>> + } else if (i != 2 || !irq0override) {
>>> r = kvm_add_irq_route(kvm_context, i, KVM_IRQCHIP_IOAPIC, i);
>>> }
>>> if (r< 0) {
>> While cleaning up the irq0override fragments, I stumbled over this
>> commit. It is a nop for qemu-kvm, today and also by the time it was applied:
>>
>> irq0override = !kvm_irqchip || kvm_has_gsi_routing
>>
>> But, for obvious reasons, the code above is only executed when gsi
>> routing is available.
>>
>> Can you remember what motivated this patch?
>>
>> Jan
>>
> For our legacy OS which only could handle the timer interrupt
> at irq 0, I set in qemu "irq0override=0;". In fact I added
> temporarily a command line option for that. Of course this
> setting needed to be passed to kvm.
As I already suspected: private changes... :)
>
> Today we have a correction in our OS and can use qemu-kvm's
> default setting.
So I'm going to file a revert. Or does anyone feel strong about making
this configurable?
Jan
--
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux
prev parent reply other threads:[~2011-02-07 10:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-14 13:51 [PATCH] qemu-kvm-x86: consider the irq0override flag in kvm_arch_init_irq_routing Bernhard Kohl
2010-09-29 20:36 ` Marcelo Tosatti
2011-02-07 9:42 ` Jan Kiszka
2011-02-07 10:12 ` Marcelo Tosatti
2011-02-07 10:17 ` Bernhard Kohl
2011-02-07 10:29 ` Jan Kiszka [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=4D4FC976.5010800@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=bernhard.kohl@nsn.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
/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.