[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Fri, 10 Oct 2008 13:11:48 -0700
From: Yinghai Lu <yinghai@...nel.org>
To: Ingo Molnar <mingo@...e.hu>
CC: Linus Torvalds <torvalds@...ux-foundation.org>,
linux-kernel@...r.kernel.org,
Andrew Morton <akpm@...ux-foundation.org>,
Thomas Gleixner <tglx@...utronix.de>,
"H. Peter Anvin" <hpa@...or.com>,
Jesse Barnes <jbarnes@...tuousgeek.org>
Subject: Re: [git pull, take 2] x86 updates for v2.6.28, phase #9, sparse
IRQ support
Ingo Molnar wrote:
> * Yinghai Lu <yinghai@...nel.org> wrote:
>
>> Ingo Molnar wrote:
>>> * Ingo Molnar <mingo@...e.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.
YH
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists