From mboxrd@z Thu Jan 1 00:00:00 1970 From: Joerg Roedel Subject: Re: [PATCH 0/9] AMD IOMMU cleanups, fixes and IVRS bug workarounds Date: Sat, 13 Apr 2013 17:26:03 +0200 Message-ID: <20130413152602.GO6858@8bytes.org> References: <1365538384-12426-1-git-send-email-joro@8bytes.org> <20130412080637.GN6858@8bytes.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: 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: Andrew Cooks Cc: "open list:INTEL IOMMU (VT-d)" , Shuah Khan , open list List-Id: iommu@lists.linux-foundation.org On Sat, Apr 13, 2013 at 11:06:22PM +0800, Andrew Cooks wrote: > On Fri, Apr 12, 2013 at 4:06 PM, Joerg Roedel wrote: > > Oh, that's sad. You were the only one having a machine wich actually has > > unity-mapped ranges defined in the BIOS table. The code for those > > mappings was basically untested before you ran it on that machine. > > > What is the machine in question? Maybe someone else has access to one, > if it's not too exotic. Shuah had access to a HP server machine (don't know which one) that defined unity-map ranges in the BIOS table. Shuah certainly knows the details about that machine. Joerg