public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Jes Sorensen <jes@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH 11/15] ia64/pv_ops: paravirtualize NR_IRQS
Date: Tue, 22 Apr 2008 12:05:59 +0000	[thread overview]
Message-ID: <480DD4A7.9020207@sgi.com> (raw)
In-Reply-To: <1207716549755-git-send-email-yamahata@valinux.co.jp>

Isaku Yamahata wrote:
> I'm willing to introduce something like PARAVIRT_NR_IRQS,
> but I don't see how PARAVIRT_NR_IRQS solves the issues.
> What I want here is to define by cpp
> #define PARAVIRT_NR_IRQS                                                \
>         max(                                                            \
>                 IA64_NATIVE_NR_IRQS,                                    \
>                 XEN_NR_IRQS,            /* only if CONFIG_XEN */        \
>                 LGUSET_NR_IRQS,         /* only if CONFIG_LGUSET */     \
>                 KVM_GUEST_NR_IRQS,      /* only if CONFIG_KVM_GUEST */  \
>                 MORE_FUTURE_VM_NR_IRQS, /* only if ...*/                \
>                 ....    \
>         )
> 
> Probably I'm missing something.
> Could you suggest more concretly? Hopefully (pseudo) code snippet.

I'd rather have PARAVIRT_NR_IRQ set from Kconfig if possible given that
all of these are constants anyway. If we cannot do that, then it would
be better to do the #if FOO_NR_IRQ > PARAVIRT_NR_IRQ in the various
header files for Xen/KVM/lguest so we don't get the clutter in the main
makefile.

Cheers,
Jes


  parent reply	other threads:[~2008-04-22 12:05 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-09  4:49 [PATCH 11/15] ia64/pv_ops: paravirtualize NR_IRQS Isaku Yamahata
2008-04-22  9:08 ` Jes Sorensen
2008-04-22 10:11 ` Isaku Yamahata
2008-04-22 12:05 ` Jes Sorensen [this message]
2008-04-23  2:54 ` Isaku Yamahata
2008-04-23 14:03 ` Jes Sorensen
2008-04-24 11:19 ` Isaku Yamahata
2008-04-24 11:52 ` Jes Sorensen
2008-04-24 12:21 ` Isaku Yamahata
2008-04-30 12:29 ` Isaku Yamahata

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=480DD4A7.9020207@sgi.com \
    --to=jes@sgi.com \
    --cc=linux-ia64@vger.kernel.org \
    /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