From: Arjan van de Ven <arjan@infradead.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Michael Breuer <mbreuer@majjas.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Thomas Gleixner <tglx@linutronix.de>, Len Brown <lenb@kernel.org>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: Problem? intel_iommu=off; perf top shows acpi_os_read_port as extremely busy
Date: Sat, 28 Nov 2009 09:45:30 -0800 [thread overview]
Message-ID: <20091128094530.0ede7b1a@infradead.org> (raw)
In-Reply-To: <20091128071808.GA32183@elte.hu>
On Sat, 28 Nov 2009 08:18:08 +0100
Ingo Molnar <mingo@elte.hu> wrote:
>
> * Michael Breuer <mbreuer@majjas.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.)
>
yeah the os_read_port is part of the idle loop, so if your system is
idle it'll show up big.... not much we can optimize there though...
next prev parent reply other threads:[~2009-11-28 17:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-28 0:20 Problem? intel_iommu=off; perf top shows acpi_os_read_port as extremely busy Michael Breuer
2009-11-28 7:18 ` Ingo Molnar
2009-11-28 15:27 ` Peter Zijlstra
2009-11-28 15:47 ` Michael Breuer
2009-11-28 17:45 ` Arjan van de Ven [this message]
2009-11-28 18:10 ` Michael Breuer
2009-11-29 20:47 ` Arjan van de Ven
2009-11-30 5:11 ` Michael Breuer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20091128094530.0ede7b1a@infradead.org \
--to=arjan@infradead.org \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@redhat.com \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mbreuer@majjas.com \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.