public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
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] KVM: Qemu: Enable kvm/ia64's network.
Date: Mon, 25 Aug 2008 14:35:54 +0300	[thread overview]
Message-ID: <48B2991A.90903@qumranet.com> (raw)
In-Reply-To: <42DFA526FC41B1429CE7279EF83C6BDC01845C49@pdsmsx415.ccr.corp.intel.com>

Zhang, Xiantao wrote:
>  Hi, Avi 
>      Since x86 and IA-64's ioapic don't have same number of PINs. They
> have to use different map functions.  Besides,  we also need to modify
> x86's dsdt to meet the map,  so in this patch, I just changed it for
> ia64 side, and didn't touch x86.  Maybe x86 needs another patch. Please
> help to apply. 
> Thanks
> Xiantao
>
> From d2bc9284cb659d120beb7dd224567f7a859d80ce Mon Sep 17 00:00:00 2001
> From: Xiantao Zhang <xiantao.zhang@intel.com>
> Date: Mon, 25 Aug 2008 09:28:29 +0800
> Subject: [PATCH] KVM: Qemu: Enable kvm/ia64's network.
>
> kvm/ia64's IRQ may >16, but current Qemu can't support it.
> Here we implment a IRQ map function to solve this issue to
> enable its networking.
>
> diff --git a/qemu/hw/ipf.c b/qemu/hw/ipf.c
> index b11e328..134076a 100644
> --- a/qemu/hw/ipf.c
> +++ b/qemu/hw/ipf.c
> @@ -672,3 +672,32 @@ QEMUMachine ipf_machine = {
>      ipf_init_pci,
>      VGA_RAM_SIZE + VGA_RAM_SIZE,
>  };
> +
> +#define IOAPIC_NUM_PINS 48
> +
> +static int ioapic_irq_count[IOAPIC_NUM_PINS];
> +
> +static int ioapic_map_irq(int devfn, int irq_num)
> +{
> +    int irq, dev;
> +    dev = devfn >> 3;
> +    irq = ((((dev << 2) + (dev >> 3) + irq_num) & 31) + 16);
> +    return irq;
> +}
> +
> +void ioapic_set_irq(void *opaque, int irq_num, int level)
> +{
> +    int vector;
> +
> +    PCIDevice *pci_dev = (PCIDevice *)opaque;
> +    vector = ioapic_map_irq(pci_dev->devfn, irq_num);
> +
> +    if (level)
> +        ioapic_irq_count[vector] += 1;
> +    else
> +        ioapic_irq_count[vector] -= 1;
> +
> +    if (kvm_enabled())
> +	if (kvm_set_irq(vector, ioapic_irq_count[vector] == 0))
> +	    return;
> +}
>   

I could move this myself to pci.c, but then I might break it since I 
still don't have an ia64 host.  It's therefore best to put this in pci.c.

The formula can be made generic by replacing '& 31' by '% 
(IOAPIC_NUM_PINS - 16)', and having defining IOAPIC_NUM_PINS according 
to architecture.

> index 92683d1..07d37a8 100644
> --- a/qemu/hw/pci.c
> +++ b/qemu/hw/pci.c
> @@ -544,6 +544,11 @@ static void pci_set_irq(void *opaque, int irq_num,
> int level)
>          return;
>  
>      pci_dev->irq_state[irq_num] = level;
> +
> +#if defined(TARGET_IA64)
> +    ioapic_set_irq(pci_dev, irq_num, level);
> +#endif
> +
>      for (;;) {
>          bus = pci_dev->bus;
>          irq_num = bus->map_irq(pci_dev, irq_num);
>   

This generates a compile warning now.

Please move it to pci.c.  You only need to make sure it works on ia64; I 
will take care of x86.

-- 
error compiling committee.c: too many arguments to function


      reply	other threads:[~2008-08-25 11:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-22  9:36 [PATCH] KVM: Qemu: Enable kvm/ia64's network Zhang, Xiantao
2008-08-24  9:22 ` Avi Kivity
2008-08-24  9:35   ` Zhang, Xiantao
2008-08-24  9:50     ` Avi Kivity
2008-08-25  1:53       ` Zhang, Xiantao
2008-08-25 11:35         ` Avi Kivity [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=48B2991A.90903@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