public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@qumranet.com>
To: "Xu, Anthony" <anthony.xu@intel.com>
Cc: Jes Sorensen <jes@sgi.com>,
	kvm-ia64@vger.kernel.org, "Zhang,
	Xiantao" <xiantao.zhang@intel.com>,
	kvm@vger.kernel.org
Subject: Re: [kvm-ia64-devel] IRQ assignment
Date: Wed, 21 May 2008 19:16:13 +0300	[thread overview]
Message-ID: <48344ACD.6030702@qumranet.com> (raw)
In-Reply-To: <51CFAB8CB6883745AE7B93B3E084EBE201BCC43E@pdsmsx412.ccr.corp.intel.com>

Xu, Anthony wrote:
>> Allowing qemu to use all ioapic interrupt pins will reduce interrupt
>> sharing on x86, which is a good thing, so I prefer the first option
>> too. 
>>     
>
>
> Thanks for your support, I preper option #1,
> Any suggestion for the mapping from BDF to irq.
>
> In XEN both in IA64/IA32,
>
> BIOS provides a 48 pin IOAPIC ( usually it is 24) to reduce irq sharing.
> 0~15 are reserved for legacy devices.
> Pci devices use 16~47,
> The mapping is like
>   ((bdf >> 3) *4) %(48-16) + 16
> Means every pci interrup pin( irqA, irqB, irqC, irqD) of every pci
> device use different irq pin of IOAPIC if number of pci devices is less
> than 8.
> I think it can avoid interrupt sharing in most case.
>
>   

With 24 free pins, that's fine.  With 8 free pins, less so.  We'll need 
to mix in more high bits.

I guess we need to increase the number of pins on x86 too.

> If use this method, we can share same IA64 guest BIOS between XEN/IA64
> and KVM/IA64.
>   

You can use this method for ia64, and we'll have a different function 
for x86 (perhaps two functions, if we later increase the number of pins 
to 48 (or even more); the DSDT will need to select the appropriate 
routing table according to what's present on the hardware).

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


       reply	other threads:[~2008-05-21 16:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <yq0zlrkkbdn.fsf@jaguar.mkp.net>
     [not found] ` <yq0ve28ka20.fsf@jaguar.mkp.net>
     [not found]   ` <yq0bq3yjnp6.fsf@jaguar.mkp.net>
     [not found]     ` <yq0k5hniuld.fsf@jaguar.mkp.net>
     [not found]       ` <51CFAB8CB6883745AE7B93B3E084EBE201BCC43D@pdsmsx412.ccr.corp.intel.com>
     [not found]         ` <4834459B.1090900@qumranet.com>
     [not found]           ` <51CFAB8CB6883745AE7B93B3E084EBE201BCC43E@pdsmsx412.ccr.corp.intel.com>
2008-05-21 16:16             ` Avi Kivity [this message]
2008-05-21 16:47               ` [kvm-ia64-devel] IRQ assignment Xu, Anthony
2008-05-21 16:50                 ` Avi Kivity
2008-05-21 16:54                   ` Xu, Anthony
     [not found]             ` <1284E411-576E-498A-A1D2-4B9F37E72533@suse.de>
2008-05-21 16:34               ` 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=48344ACD.6030702@qumranet.com \
    --to=avi@qumranet.com \
    --cc=anthony.xu@intel.com \
    --cc=jes@sgi.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