linux-kernel - Re: possible dmar_init_reserved

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: <20170104143909.GD10632@8bytes.org>
Date:   Wed, 4 Jan 2017 15:39:09 +0100
From:   Joerg Roedel <joro@...tes.org>
To:     "Raj, Ashok" <ashok.raj@...el.com>
Cc:     Bjorn Helgaas <helgaas@...nel.org>,
        David Woodhouse <dwmw2@...radead.org>,
        g@...lgaas-glaptop.roam.corp.google.com, linux-pci@...r.kernel.org,
        iommu@...ts.linux-foundation.org, linux-kernel@...r.kernel.org,
        rwright@....com
Subject: Re: possible dmar_init_reserved_ranges() error

On Tue, Dec 27, 2016 at 07:21:39PM -0800, Raj, Ashok wrote:
> This sounds reasonable, if we can reserve from the host bridge apertures 
> it should take care of hot-plug cases as well, and should simply how the
> reservation is made.

Agreed, I have this on my todo list already since I converted the AMD
IOMMU driver to the iova allocator. Just reserving the pci windows is
much better than what we are currently doing.


	Joerg