mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Yinghai Lu" <yhlu.kernel@gmail.com>
To: "Jeremy Fitzhardinge" <jeremy@goop.org>
Cc: "Ingo Molnar" <mingo@elte.hu>,
	"Thomas Gleixner" <tglx@linutronix.de>,
	"H. Peter Anvin" <hpa@zytor.com>,
	"Andrew Morton" <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org,
	"Alex Nixon" <alex.nixon@citrix.com>
Subject: Re: [PATCH] x86: fix probe_nr_irqs for xen
Date: Thu, 21 Aug 2008 16:56:36 -0700	[thread overview]
Message-ID: <86802c440808211656o20f9a22dv34e3ac8e8e84b4e1@mail.gmail.com> (raw)
In-Reply-To: <48ADFFD2.7030309@goop.org>

On Thu, Aug 21, 2008 at 4:52 PM, Jeremy Fitzhardinge <jeremy@goop.org> wrote:
> Yinghai Lu wrote:
>> On Thu, Aug 21, 2008 at 4:33 PM, Jeremy Fitzhardinge <jeremy@goop.org> wrote:
>>
>>> Yinghai Lu wrote:
>>>
>>>> otherwise Xen is _completely_ unusable with 5 or more VCPUs.
>>>> ( when !CONFIG_HAVE_SPARSE_IRQ)
>>>>
>>>> based on Alex's patch
>>>>
>>>> also add +1 offset after redir_entries
>>>>
>>>> Signed-off-by: Yinghai Lu <yhlu.kernel@gmail.com>
>>>> Cc: Alex Nixon <alex.nixon@citrix.com>
>>>>
>>>>
>>> Looks good to me.  We can fix this in a better way later.
>>>
>>
>> later could set CONFIG_HAVE_SPARSE_IRQ to true by default.
>>
>
> Well, perhaps.  But we can use vectors rather than IRQs for Xen event
> channel mappings, which will save us from having to allocate lots of
> per-cpu irqs.

like system vectors with smp-ipi etc?

>
> Also, implementing probe_nr_irqs() in a more generic (rather than
> io_apic-specific) way.  Using some interface that queries each irq chip
> for how many irqs it supports, or something.

hope we can kill nr_irqs/NR_IRQS

YH

  reply	other threads:[~2008-08-21 23:56 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-21 20:10 Yinghai Lu
2008-08-21 23:33 ` Jeremy Fitzhardinge
2008-08-21 23:49   ` Yinghai Lu
2008-08-21 23:52     ` Jeremy Fitzhardinge
2008-08-21 23:56       ` Yinghai Lu [this message]
2008-08-22  0:02         ` Jeremy Fitzhardinge
2008-08-22  0:27           ` Yinghai Lu
2008-08-22  4:26           ` Ingo Molnar
2008-08-22  5:06             ` Yinghai Lu
2008-08-22  5:16               ` Ingo Molnar
2008-08-22 13:44                 ` Cyrill Gorcunov
2008-08-22  4:28   ` Ingo Molnar
2008-08-22  9:07     ` Alex Nixon

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=86802c440808211656o20f9a22dv34e3ac8e8e84b4e1@mail.gmail.com \
    --to=yhlu.kernel@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=alex.nixon@citrix.com \
    --cc=hpa@zytor.com \
    --cc=jeremy@goop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tglx@linutronix.de \
    /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

all inboxes | Powered by JetHome®