From: Pranjal Shrivastava <praan@google.com>
To: "Li,Rongqing" <lirongqing@baidu.com>
Cc: Robin Murphy <robin.murphy@arm.com>,
"joro@8bytes.org" <joro@8bytes.org>,
"will@kernel.org" <will@kernel.org>,
"iommu@lists.linux.dev" <iommu@lists.linux.dev>
Subject: Re: 答复: [外部邮件] Re: [PATCH] iommu: Downgrade print level for iommu group information
Date: Wed, 27 Nov 2024 10:16:35 +0000 [thread overview]
Message-ID: <Z0bxg0P9AtSHW82A@google.com> (raw)
In-Reply-To: <e790f039210f4bd78a015a6fa439c607@baidu.com>
On Tue, Nov 26, 2024 at 12:09:03PM +0000, Li,Rongqing wrote:
>
> > On 26/11/2024 7:23 am, Li RongQing wrote:
> > > This per device log is becoming longer with more and more PCI devices
> > > in system, which slows down the boot process due to the serializing
> > > nature of printk().
> > >
> > > Downgrade dev_info() to dev_dbg() so it is still accessible for debug
> > > purposes.
> >
> > Previously discussed 4 and a half years ago:
> >
> > https://lore.kernel.org/linux-iommu/20200302154426.GC6540@8bytes.org/
> >
Hmm.. I'm wondering if ratelimiting might help here?
We can define a rate_limit for the iommu subsystem that can be tuned
accordingly to control verbosity. We can keep the rate_limit to a min.
as we'd like and maintain it upstream and give users an option to tune
it as per their requirement.
> > Also, given that the iommu_probe_device() path is inherently serialised anyway,
> > if logging a message from there significantly slows down your boot process, how
> > slow is your console device?
> >
>
>
> There are 482 in my machine, spends nearly about 3 seconds
>
> [ 40.083614] DMAR: dmar1: Using Queued invalidation
> [ 40.089008] DMAR: dmar0: Using Queued invalidation
> [ 40.094402] DMAR: dmar19: Using Queued invalidation
> [ 40.100816] pci 0000:79:00.4: Adding to iommu group 0
> [ 40.106586] pci 0000:79:01.0: Adding to iommu group 1
> [ 40.112346] pci 0000:79:02.0: Adding to iommu group 2
> [ 40.118315] pci 0000:74:00.4: Adding to iommu group 3
> [ 40.124074] pci 0000:74:01.0: Adding to iommu group 4
> [ 40.129830] pci 0000:74:02.0: Adding to iommu group 5
------------------------------->8-----------------------------
snip
------------------------------->8-----------------------------
> [ 43.140538] pci 0000:ff:1e.6: Adding to iommu group 482
> [ 43.146522] pci 0000:ff:1e.7: Adding to iommu group 482
> [ 43.153222] DMAR: Intel(R) Virtualization Technology for Directed I/O
> [ 43.160471] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
> [ 43.167715] software IO TLB: mapped [mem 0x000000006123e000-0x000000006523e000] (64MB)
> [ 43.178633] RAPL PMU: API unit is 2^-32 Joules, 3 fixed counters, 655360 ms ovfl timer
> [ 43.187540] RAPL PMU: hw unit of domain package 2^-14 Joules
> [ 43.193906] RAPL PMU: hw unit of domain dram 2^-14 Joules
> [ 43.199984] RAPL PMU: hw unit of domain psys 2^-0 Joules
>
Thanks,
Praan
next prev parent reply other threads:[~2024-11-27 10:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-26 7:23 [PATCH] iommu: Downgrade print level for iommu group information Li RongQing
2024-11-26 10:25 ` Pranjal Shrivastava
2024-11-26 10:47 ` 答复: [????] " Li,Rongqing
2024-11-26 11:49 ` Robin Murphy
2024-11-26 12:09 ` 答复: [外部邮件] " Li,Rongqing
2024-11-27 10:16 ` Pranjal Shrivastava [this message]
2024-11-27 11:32 ` 答复: " Li,Rongqing
2024-11-29 8:21 ` Li,Rongqing
2024-11-27 12:37 ` Robin Murphy
2024-11-27 20:56 ` Pranjal Shrivastava
2024-11-27 12:12 ` Robin Murphy
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=Z0bxg0P9AtSHW82A@google.com \
--to=praan@google.com \
--cc=iommu@lists.linux.dev \
--cc=joro@8bytes.org \
--cc=lirongqing@baidu.com \
--cc=robin.murphy@arm.com \
--cc=will@kernel.org \
/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.