| 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
| ||
|
Message-ID: <20100930190536.GA18845@srcf.ucam.org> Date: Thu, 30 Sep 2010 20:05:36 +0100 From: Matthew Garrett <mjg59@...f.ucam.org> To: Joerg Roedel <joro@...tes.org> Cc: linux-kernel@...r.kernel.org, linux-pci@...r.kernel.org, joerg.roedel@....com, jbarnes@...tuousgeek.org Subject: Re: [PATCH] pci: Reenable the AMD IOMMU if it's mysteriously vanished over suspend On Thu, Sep 30, 2010 at 08:43:01PM +0200, Joerg Roedel wrote: > Enabling the IOMMU device is only part of what the BIOS is supposed to > do to get the IOMMU ready for the OS. A handful of registers in the > config space of the device and the IOMMU MMIO region must also be > restored. Thats the simple part. The IOMMU device also spans two > indirect register spaces to configure the IOMMU caches. I have no idea > yet how this need to be configured. The plan is definitly to > work-around a missing IOMMU device in the IOMMU driver. But I am still > talking to some people to find out what exactly must be done, especially > with the indirect register spaces. Chapter 8 of the register setup guide seems to have something on this - I'll try saving and restoring all of the setup it performs to see if it improves things. -- Matthew Garrett | mjg59@...f.ucam.org -- 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