linux-kernel - Re: [patch 1/5] x2apic: fix reserved APIC register accesses in print_local

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <200809050218.25504.jbarnes@virtuousgeek.org>
Date:	Fri, 5 Sep 2008 02:18:25 -0700
From:	Jesse Barnes <jbarnes@...tuousgeek.org>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	Suresh Siddha <suresh.b.siddha@...el.com>,
	"hpa@...or.com" <hpa@...or.com>,
	"tglx@...utronix.de" <tglx@...utronix.de>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Yinghai Lu <yhlu.kernel@...il.com>,
	"Maciej W. Rozycki" <macro@...ux-mips.org>
Subject: Re: [patch 1/5] x2apic: fix reserved APIC register accesses in print_local_APIC()

On Friday, September 05, 2008 1:10 am Ingo Molnar wrote:
> * Suresh Siddha <suresh.b.siddha@...el.com> wrote:
> > On Thu, Sep 04, 2008 at 04:06:31AM -0700, Ingo Molnar wrote:
> > > applied the following patches tip/irq/sparseirq:
> >
> > Ingo, Shouldn't this go to tip/x86/x2apic ? Thanks.
>
> normally yes - but this is a special case: there's existing overlap with
> other DMAR changes in irq/sparseirq (intr-remap and ioapic unification
> changes), so these followups have to go there too. Also, since they
> change the generic PCI code it's better they live in a generic topic to
> begin with. The full stack of pending changes is:
>
> 0f48966: dmar: fix dmar_parse_dev() devices_cnt error condition check
> 2283240: dmar: use list_for_each_entry_safe() in dmar_dev_scope_init()
> 3f1fdb3: dmar: initialize the return value in dmar_parse_dev()
> f12c73e: dmar: fix using early fixmap mapping for DMAR table parsing
> 1cb1158: x64, x2apic/intr-remap: disable DMA-remapping if
> Interrupt-remapping is detected (temporary quirk) 2ae2101: x64,
> x2apic/intr-remap: Interrupt remapping infrastructure fe962e9: x64,
> x2apic/intr-remap: Queued invalidation infrastructure (part of VT-d)
> ad3ad3f: x64, x2apic/intr-remap: parse ioapic scope under vt-d structures
> 2d6b5f8: x64, x2apic/intr-remap: Fix the need for RMRR in the DMA-remapping
> detection aaa9d1d: x64, x2apic/intr-remap: use CONFIG_DMAR for
> DMA-remapping specific code 1886e8a: x64, x2apic/intr-remap: code
> re-structuring, to be used by both DMA and Interrupt remapping c42d9f3:
> x64, x2apic/intr-remap: fix the need for sequential array allocation of
> iommus e61d98d: x64, x2apic/intr-remap: Intel vt-d, IOMMU code
> reorganization
>
> Jesse, do you have any objections to this approach?

Nope, no problems.  I think I have some pending patches that may have 
conflicts with the above, but I'll take care of that when I get back to the 
US (I think Sunday or Monday will be a massive patch review/merge/comment 
day).

Thanks,
Jesse
--
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/