From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ingo Molnar Subject: Re: [PATCH 2/2] iommu: dmar -- reserve mmio space used by IOMMU Date: Wed, 6 Jun 2012 10:29:00 +0200 Message-ID: <20120606082900.GF5991@gmail.com> References: <1338845342-12464-1-git-send-email-ddutile@redhat.com> <1338845342-12464-3-git-send-email-ddutile@redhat.com> <1338849430.10884.288.camel@shinybook.infradead.org> <4FCD401D.9000304@redhat.com> <1338852196.26785.10.camel@shinybook.infradead.org> <20120606081600.GB5991@gmail.com> <1338971183.26785.33.camel@shinybook.infradead.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <1338971183.26785.33.camel-Fexsq3y4057IgHVZqg5X0TlWvGAXklZc@public.gmane.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: iommu-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org Errors-To: iommu-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org To: David Woodhouse Cc: chrisw-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org, suresh.b.siddha-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org, linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org, mingo-X9Un+BFzKDI@public.gmane.org List-Id: iommu@lists.linux-foundation.org * David Woodhouse wrote: > On Wed, 2012-06-06 at 10:16 +0200, Ingo Molnar wrote: > > > So basically the patch-set is fine as-is, we just want a > > sufficiently nasty sounding warning message about the BIOS > > bug, > > No. The other change that's required is that the warning and > the workaround need to trigger even when IOMMU support isn't > built into the kernel. This BIOS bug can bite you even when > you aren't *using* the IOMMU. Right, but that's the status quo and most of the time (distro kernels) the driver is available, right? So for all practical purposes we get 99% of the warning power without going into chicken-and-egg problems like how do we determine that there's an IOMMU area there if there's no IOMMU aware code in the kernel, right? Thanks, Ingo