linux-kernel - Re: [tip:x86/apic] iommu/vt-d: Move iommu preparatory allocations to irq_remap

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 for Android: free password hash cracker in your pocket

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

Message-ID: <CAE9FiQWfX5xuzz=n+Pps5dH0--srQh-yFH4pg-ak5AnP-AvRPg@mail.gmail.com>
Date:	Mon, 27 Apr 2015 15:46:05 -0700
From:	Yinghai Lu <yinghai@...nel.org>
To:	Thomas Gleixner <tglx@...utronix.de>
Cc:	Jiang Liu <jiang.liu@...ux.intel.com>,
	Joerg Roedel <joro@...tes.org>, Borislav Petkov <bp@...en8.de>,
	Ingo Molnar <mingo@...nel.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	"H. Peter Anvin" <hpa@...or.com>,
	Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: [tip:x86/apic] iommu/vt-d: Move iommu preparatory allocations to irq_remap_ops.prepare

On Thu, Dec 11, 2014 at 6:04 PM, Yinghai Lu <yinghai@...nel.org> wrote:
> On Thu, Dec 11, 2014 at 12:30 PM, Thomas Gleixner <tglx@...utronix.de> wrote:
>
>> So irq_2_iommu is empty. That's a multi MSI, and that's the second
>> interrupt which gets enabled.
>>
>> The patch below should fix it.
>>
>
> Yes, that fixes the problem.
>
> Assume you will fold it into
>
> commit 289472f461d922507f75dd2451770282adb3a99b
> Author: Jiang Liu <jiang.liu@...ux.intel.com>
> Date:   Tue Nov 25 13:53:19 2014 +0800
>
>     iommu/vt-d: Enhance Intel IR driver to suppport hierarchy irqdomain
>

Looks like you did not put your fix in new tip/x86/apic with Jiang's patchset.

    Yinghai
--
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/