Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753262Ab2HMDY4 (ORCPT ); Sun, 12 Aug 2012 23:24:56 -0400 Received: from terminus.zytor.com ([198.137.202.10]:43216 "EHLO mail.zytor.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753020Ab2HMDYz (ORCPT ); Sun, 12 Aug 2012 23:24:55 -0400 Message-ID: <50287378.5090801@zytor.com> Date: Sun, 12 Aug 2012 20:24:40 -0700 From: "H. Peter Anvin" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20120717 Thunderbird/14.0 MIME-Version: 1.0 To: Khalid Aziz CC: Betty Dall , Andi Kleen , x86@kernel.org, linux-kernel@vger.kernel.org, Andi Kleen Subject: Re: [PATCH] x86, pci: Fix all early PCI scans to check the vendor ID first References: <1344464246-14618-1-git-send-email-andi@firstfloor.org> <1344551691.10751.12.camel@ejdallLaptop> <50259FCE.4070205@zytor.com> <50287315.5010203@hp.com> In-Reply-To: <50287315.5010203@hp.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 785 Lines: 22 On 08/12/2012 08:23 PM, Khalid Aziz wrote: > > If that is the case, there is a problem in the original code in > arch/x86/kernel/aperture_64.c.The original code already stops scanning > functions the first time it finds an invalid PCI class: > Unless we can prove that that is invalid *for that specific case*, then it is definitely wrong, and yes, I have seen devices in the field with multiple, discontiguous functions. -hpa -- H. Peter Anvin, Intel Open Source Technology Center I work for Intel. I don't speak on their behalf. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/