linux-kernel - Re: [patch 0/2] Intel IOMMU Suspend/Resume Support

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] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 25 Mar 2009 16:53:22 -0400
From:	Andrew Lutomirski <amluto@...il.com>
To:	fenghua.yu@...el.com
Cc:	mingo@...e.hu, dwmw2@...radead.org, kyle@...hat.com,
	mgross@...ux.intel.com, linux-kernel@...r.kernel.org,
	iommu@...ts.linux-foundation.org
Subject: Re: [patch 0/2] Intel IOMMU Suspend/Resume Support

It looks like patch 1 calls dmar_reenable_qi but patch 2 defines it.

In 2.6.29, there's no dmar_disable_qi that I can see.  Can you respin
these against something a little less scary than -tip during a merge
window?  (Especially since -stable will need this soon.)

Thanks,
Andy

On Wed, Mar 25, 2009 at 2:45 PM,  <fenghua.yu@...el.com> wrote:
> Current Intel IOMMU does not support suspend and resume. In S3 event, kernel
> crashes when IOMMU is enabled. The attached patch set implements the suspend and
> resume feature for Intel IOMMU. It hooks to kernel suspend and resume interface.
> When suspend happens, it saves necessary hardware registers. When resume happens
> it restores the registers and restarts IOMMU.
>
> This patch set is applied to the tip tree.
>
> --
>
>
--
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/