From: Avi Kivity <avi@qumranet.com>
To: "Zhang, Xiantao" <xiantao.zhang@intel.com>
Cc: kvm-ia64@vger.kernel.org, kvm@vger.kernel.org
Subject: Re: [PATCH] Fix KVM/IA-64 build issue in latest kvm.git.
Date: Tue, 19 Aug 2008 13:41:23 +0300 [thread overview]
Message-ID: <48AAA353.3060204@qumranet.com> (raw)
In-Reply-To: <42DFA526FC41B1429CE7279EF83C6BDC017F9D9A@pdsmsx415.ccr.corp.intel.com>
Zhang, Xiantao wrote:
> From d53dfacedea40213382694229700d02bfa72d923 Mon Sep 17 00:00:00 2001
> From: Xiantao Zhang <xiantao.zhang@intel.com>
> Date: Tue, 19 Aug 2008 17:33:21 +0800
> Subject: [PATCH] KVM: KVM/IA-64: Fix kvm/ia64's build issue.
>
> Disable irq ack notification for ia64.
> Signed-off-by: Xiantao Zhang <xiantao.zhang@intel.com>
> ---
> virt/kvm/ioapic.c | 7 ++++++-
> 1 files changed, 6 insertions(+), 1 deletions(-)
>
> diff --git a/virt/kvm/ioapic.c b/virt/kvm/ioapic.c
> index 515cd7c..992199b 100644
> --- a/virt/kvm/ioapic.c
> +++ b/virt/kvm/ioapic.c
> @@ -39,7 +39,10 @@
>
> #include "ioapic.h"
> #include "lapic.h"
> +
> +#ifdef CONFIG_X86
> #include "irq.h"
> +#endif
>
Please keep the include; add an ia64 specific irq.h instead.
>
> #if 0
> #define ioapic_debug(fmt,arg...) printk(KERN_WARNING fmt,##arg)
> @@ -293,7 +296,9 @@ static void __kvm_ioapic_update_eoi(struct
> kvm_ioapic *ioapic, int gsi,
>
> ent = &ioapic->redirtbl[gsi];
>
> +#ifdef CONFIG_X86
> kvm_notify_acked_irq(ioapic->kvm, gsi);
> +#endif
>
>
Keep this as well. You can have a nop-op irq notification API, and
later merge with x86. I think you will need irq ack notification if you
implement device assignment, or for improved timekeeping.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2008-08-19 10:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-19 9:55 [PATCH] Fix KVM/IA-64 build issue in latest kvm.git Zhang, Xiantao
2008-08-19 10:41 ` Avi Kivity [this message]
2008-08-19 13:06 ` Zhang, Xiantao
2008-08-19 14:04 ` 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=48AAA353.3060204@qumranet.com \
--to=avi@qumranet.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