linux-kernel - Re: Problem? intel_iommu=off; perf top shows acpi_os_read

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] [thread-next>] [day] [month] [year] [list]

Date:	Sat, 28 Nov 2009 08:18:08 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Michael Breuer <mbreuer@...jas.com>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Thomas Gleixner <tglx@...utronix.de>,
	Len Brown <lenb@...nel.org>,
	Arjan van de Ven <arjan@...radead.org>,
	Arnaldo Carvalho de Melo <acme@...hat.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Problem? intel_iommu=off; perf top shows acpi_os_read_port as
 extremely busy


* Michael Breuer <mbreuer@...jas.com> wrote:

> 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.

Could you post the perf top output please?

Also, could you also post the output of:

	perf stat -a --repeat 10 sleep 1

this will show us how idle the system is. (My guess is that your system 
is idle and perf top shows acpi_os_read_port because the system goes to 
idle via ACPI methods and PIO is slow. In that case all is nominal and 
your system is fine. But it's hard to tell without more details.)

Thanks,

	Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/