public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Mika Penttilä" <mika.penttila@kolumbus.fi>
To: "Nguyen, Tom L" <tom.l.nguyen@intel.com>
Cc: Andreas Schwab <schwab@suse.de>,
	greg@kroah.com, linux-kernel@vger.kernel.org, "Nakajima,
	Jun" <jun.nakajima@intel.com>, "Luck, Tony" <tony.luck@intel.com>
Subject: Re: [PATCH]2.6.3-rc2 MSI Support for IA64
Date: Fri, 20 Feb 2004 21:43:11 +0200	[thread overview]
Message-ID: <4036634F.2020406@kolumbus.fi> (raw)
In-Reply-To: <C7AB9DA4D0B1F344BF2489FA165E5024040580FE@orsmsx404.jf.intel.com>



Nguyen, Tom L wrote:

>Friday, Feb. 20, 2004 10:58 AM, Mika Penttilä wrote:
>
>  
>
>>ia64 already has a function ia64_alloc_vector(void) in 
>>arch/ia64/kernel/irq_ia64, why the doubling?
>>    
>>
>
>+#ifndef CONFIG_PCI_USE_VECTOR
> int
> ia64_alloc_vector (void)
> {
>@@ -67,6 +68,7 @@
> 		panic("ia64_alloc_vector: out of interrupt vectors!");
> 	return next_vector++;
> }
>+#endif
>
>#ifndef CONFIG_PCI_USE_VECTOR is added in arch/ia64/kernel/irq_ia64.c
>as above to avoid the double definement of ia64_alloc_vector(void).
>Setting CONFIG_PCI_USE_VECTOR to 'Y' by enabling MSI support will
>use function ia64_alloc_vector(void) defined in drivers/pci/msi.c.
>The main reason behind it is to keep track of the number of vectors
>already assigned during the runtime. Keeping track of already assigned
>vectors is required in MSI implementation.
>
>Thanks,
>Long 
>
>  
>
I see, thanks

--Mika



  reply	other threads:[~2004-02-20 19:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-20 19:31 [PATCH]2.6.3-rc2 MSI Support for IA64 Nguyen, Tom L
2004-02-20 19:43 ` Mika Penttilä [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-02-23 16:44 Nguyen, Tom L
2004-02-20 19:38 Nguyen, Tom L
2004-02-20 18:36 Nguyen, Tom L
2004-02-20 18:58 ` Mika Penttilä
2004-02-20 19:05 ` David Mosberger
2004-02-21  1:55 ` Zwane Mwaikambo
2004-02-20 17:47 long
2004-02-20 16:54 ` Andreas Schwab

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=4036634F.2020406@kolumbus.fi \
    --to=mika.penttila@kolumbus.fi \
    --cc=greg@kroah.com \
    --cc=jun.nakajima@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=schwab@suse.de \
    --cc=tom.l.nguyen@intel.com \
    --cc=tony.luck@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