From: Avi Kivity <avi@redhat.com>
To: "Zhang, Xiantao" <xiantao.zhang@intel.com>
Cc: kvm-ia64@vger.kernel.org, kvm@vger.kernel.org
Subject: Re: [PATCH 04/08]kvm: Split arch/x86/kvm/irq.c to two parts.
Date: Wed, 08 Oct 2008 13:02:06 +0200 [thread overview]
Message-ID: <48EC932E.1030000@redhat.com> (raw)
In-Reply-To: <42DFA526FC41B1429CE7279EF83C6BDC01ABCA37@pdsmsx415.ccr.corp.intel.com>
Zhang, Xiantao wrote:
> From 720dab659e581adba3a7846db6d2f612ffcd83a0 Mon Sep 17 00:00:00 2001
> From: Xiantao Zhang <xiantao.zhang@intel.com>
> Date: Mon, 6 Oct 2008 13:48:45 +0800
> Subject: [PATCH] kvm: Split arch/x86/kvm/irq.c to two parts.
>
> Moving irq ack notification logic as common, and make
> it shared with ia64 side.
>
> +/* This should be called with the kvm->lock mutex held */
> +void kvm_set_irq(struct kvm *kvm, int irq, int level)
> +{
> + /* Not possible to detect if the guest uses the PIC or the
> + * IOAPIC. So set the bit in both. The guest will ignore
> + * writes to the unused one.
> + */
> + kvm_ioapic_set_irq(kvm->arch.vioapic, irq, level);
> +#ifdef X86
> + kvm_pic_set_irq(pic_irqchip(kvm), irq, level);
> +#endif
> +}
> +
>
This needs to be CONFIG_X86, not X86. As is, Windows doesn't even
boot. Fixing it causes compile errors for missing declarations and
pic_irqchip().
Please fix ASAP and test much more carefully. Meanwhile I am reverting
the patchset.
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
next prev parent reply other threads:[~2008-10-08 11:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-08 1:51 [PATCH 04/08]kvm: Split arch/x86/kvm/irq.c to two parts Zhang, Xiantao
2008-10-08 11:02 ` Avi Kivity [this message]
2008-10-08 11:08 ` Zhang, Xiantao
2008-10-08 11:13 ` Avi Kivity
2008-10-08 11:52 ` Zhang, Xiantao
2008-10-08 13:39 ` Avi Kivity
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=48EC932E.1030000@redhat.com \
--to=avi@redhat.com \
--cc=kvm-ia64@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=xiantao.zhang@intel.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 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).