Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753768AbZK1AUf (ORCPT ); Fri, 27 Nov 2009 19:20:35 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753641AbZK1AUe (ORCPT ); Fri, 27 Nov 2009 19:20:34 -0500 Received: from mta5.srv.hcvlny.cv.net ([167.206.4.200]:62668 "EHLO mta5.srv.hcvlny.cv.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753583AbZK1AUc (ORCPT ); Fri, 27 Nov 2009 19:20:32 -0500 Date: Fri, 27 Nov 2009 19:20:16 -0500 From: Michael Breuer Subject: Problem? intel_iommu=off; perf top shows acpi_os_read_port as extremely busy To: linux-kernel@vger.kernel.org Message-id: <4B106CC0.4050406@majjas.com> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7BIT User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.4pre) Gecko/20091109 Fedora/3.0-3.10.b4.fc12 Thunderbird/3.0b4 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 717 Lines: 15 Having given up for now on VT-D, I rebooted 2.6.38 rc8 with intel_iommu=off. Whilst my myriad of broken bios issues cleared, I now see in perf top acpi_os_read_port as continually the busiest function. With intel_iommu enabled, _spin_lock was always on top, and nothing else was notable. This seems odd to me, perhaps this will make sense to someone else. FWIW, I'm running on an Asus p6t deluxe v2; ht enabled; no errors or oddities in dmesg or /var/log/messages. -- 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/