public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Yinghai Lu <yinghai@kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	linux-kernel@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	"H. Peter Anvin" <hpa@zytor.com>,
	Jesse Barnes <jbarnes@virtuousgeek.org>
Subject: Re: [git pull, take 2] x86 updates for v2.6.28, phase #9, sparse IRQ support
Date: Fri, 10 Oct 2008 22:14:18 +0200	[thread overview]
Message-ID: <20081010201418.GA9046@elte.hu> (raw)
In-Reply-To: <48EFB704.9070308@kernel.org>


* Yinghai Lu <yinghai@kernel.org> wrote:

> Ingo Molnar wrote:
> > * Yinghai Lu <yinghai@kernel.org> wrote:
> > 
> >> Ingo Molnar wrote:
> >>> * Ingo Molnar <mingo@elte.hu> wrote:
> >>>
> >>>> Linus,
> >>>>
> >>>> Please pull the latest x86-v28-for-linus-phase9 git tree from:
> >>>>
> >>>> Sparse IRQ support - make NR_IRQS dynamic by turning it into nr_irqs, 
> >>>> an by creating irq descriptors in a sparse way.
> >>>>
> >>>> Includes a number of dependent x86 topics: timers/hpet-percpu, IO-APIC 
> >>>> and local APIC code unification, UV support updates.
> >>>>
> >>>> Has been cross-built on all architectures we could get crosscompilers 
> >>>> for:
> >>>>
> >>>>   http://www.tglx.de/autoqa/index
> >>>>
> >>>> It should be largely uneventful for sparse-irq unaware, non-x86 
> >>>> architectures.
> >>> please find updated pull request below. Relative to phase-N-1. Updates 
> >>> from today in this class of topics:
> >>>
> >>>   b570868: x86: apic - unify APIC_DIVISOR
> >>>
> >>> And i removed:
> >>>
> >>>   eada62c: acpi/x86: introduce __apci_map_table, v4
> >>>
> >>> [ Cc:-ed Yinghai for that - we can live without that patch (i.e. we at
> >>>   most get a leak warning) and can have that via acpi.git, correct? ]
> >> yes. we have several patches that even didn't pick up for a while.
> >>
> >> also please ask Linus to pull pci tree from Jesse before sparseirq.
> >>
> >> because we need
> >> 	PCI: change MSI-x vector to 32bit
> >>
> >> in pci tree.
> > 
> > is it absolutely needed?
> > 
> 
> qla2xxx with MSI-X will crash. only happend with the new card that support msi-x.
> 
> so it is not absolutely needed.

but as Jesse noted we have:

 9e40236: pci: change msi-x vector to 32bit

included in irq/sparseirq so it should be fine and there's no dependency 
on the PCI tree.

	Ingo

  reply	other threads:[~2008-10-10 20:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-10  0:17 [git pull] x86 updates for v2.6.28, phase #9, sparse IRQ support Ingo Molnar
2008-10-10 18:59 ` [git pull, take 2] " Ingo Molnar
2008-10-10 19:11   ` Yinghai Lu
2008-10-10 19:34     ` Jesse Barnes
2008-10-10 19:50       ` [git pull, take 2] x86 updates for v2.6.28, phase #9, sparse IRQ?support Ingo Molnar
2008-10-10 19:47     ` [git pull, take 2] x86 updates for v2.6.28, phase #9, sparse IRQ support Ingo Molnar
2008-10-10 20:11       ` Yinghai Lu
2008-10-10 20:14         ` Ingo Molnar [this message]
2008-10-10 20:15           ` Yinghai Lu

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=20081010201418.GA9046@elte.hu \
    --to=mingo@elte.hu \
    --cc=akpm@linux-foundation.org \
    --cc=hpa@zytor.com \
    --cc=jbarnes@virtuousgeek.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    --cc=yinghai@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