All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sai Prakash Ranjan <saiprakash.ranjan@codeaurora.org>
To: Robin Murphy <robin.murphy@arm.com>
Cc: Doug Anderson <dianders@chromium.org>,
	Will Deacon <will@kernel.org>,
	linux-arm-msm <linux-arm-msm@vger.kernel.org>,
	linux-arm-msm-owner@vger.kernel.org,
	Joerg Roedel <joro@8bytes.org>,
	LKML <linux-kernel@vger.kernel.org>,
	iommu@lists.linux-foundation.org
Subject: Re: [PATCH] iommu/arm-smmu: Demote error messages to debug in shutdown callback
Date: Thu, 23 Apr 2020 15:11:03 +0530	[thread overview]
Message-ID: <685e51afcf8f89c2d8e225716a57b67a@codeaurora.org> (raw)
In-Reply-To: <006edb3b-8834-41fe-d9d1-fe873edfca99@arm.com>

On 2020-04-23 14:58, Robin Murphy wrote:
> On 2020-04-23 9:17 am, Sai Prakash Ranjan wrote:
> [...]
>>> Any update on the status here?  If I'm reading the conversation 
>>> above,
>>> Robin said: "we'll *always* see the warning because there's no way to
>>> tear down the default DMA domains, and even if all devices *have* 
>>> been
>>> nicely quiesced there's no way to tell".  Did I understand that
>>> properly?  If so, it seems like it's fully expected to see this
>>> message on every reboot and it doesn't necessarily signify anything
>>> bad.
>>> 
>> 
>> Understanding is the same, waiting for Will and Robin to check if its 
>> OK
>> to make the message more friendly.
> 
> The way I see it, we essentially just want *something* visible that
> will correlate with any misbehaviour that *might* result from turning
> off a possibly-live context. How about simply "disabling translation",
> at dev_warn or dev_info level?
> 


Sounds good, I'll go with disabling translation with dev_info.

Thanks,
Sai
-- 
QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a 
member
of Code Aurora Forum, hosted by The Linux Foundation

WARNING: multiple messages have this Message-ID (diff)
From: Sai Prakash Ranjan <saiprakash.ranjan@codeaurora.org>
To: Robin Murphy <robin.murphy@arm.com>
Cc: linux-arm-msm <linux-arm-msm@vger.kernel.org>,
	Doug Anderson <dianders@chromium.org>,
	LKML <linux-kernel@vger.kernel.org>,
	iommu@lists.linux-foundation.org, Will Deacon <will@kernel.org>,
	linux-arm-msm-owner@vger.kernel.org
Subject: Re: [PATCH] iommu/arm-smmu: Demote error messages to debug in shutdown callback
Date: Thu, 23 Apr 2020 15:11:03 +0530	[thread overview]
Message-ID: <685e51afcf8f89c2d8e225716a57b67a@codeaurora.org> (raw)
In-Reply-To: <006edb3b-8834-41fe-d9d1-fe873edfca99@arm.com>

On 2020-04-23 14:58, Robin Murphy wrote:
> On 2020-04-23 9:17 am, Sai Prakash Ranjan wrote:
> [...]
>>> Any update on the status here?  If I'm reading the conversation 
>>> above,
>>> Robin said: "we'll *always* see the warning because there's no way to
>>> tear down the default DMA domains, and even if all devices *have* 
>>> been
>>> nicely quiesced there's no way to tell".  Did I understand that
>>> properly?  If so, it seems like it's fully expected to see this
>>> message on every reboot and it doesn't necessarily signify anything
>>> bad.
>>> 
>> 
>> Understanding is the same, waiting for Will and Robin to check if its 
>> OK
>> to make the message more friendly.
> 
> The way I see it, we essentially just want *something* visible that
> will correlate with any misbehaviour that *might* result from turning
> off a possibly-live context. How about simply "disabling translation",
> at dev_warn or dev_info level?
> 


Sounds good, I'll go with disabling translation with dev_info.

Thanks,
Sai
-- 
QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a 
member
of Code Aurora Forum, hosted by The Linux Foundation
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu

  reply	other threads:[~2020-04-23  9:41 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-27 13:28 [PATCH] iommu/arm-smmu: Demote error messages to debug in shutdown callback Sai Prakash Ranjan
2020-03-27 13:28 ` Sai Prakash Ranjan
2020-03-27 14:12 ` Robin Murphy
2020-03-27 14:12   ` Robin Murphy
2020-03-27 15:09   ` Sai Prakash Ranjan
2020-03-27 15:09     ` Sai Prakash Ranjan
2020-03-27 16:17     ` Rob Clark
2020-03-27 16:17       ` Rob Clark
2020-03-27 18:18       ` Sai Prakash Ranjan
2020-03-27 18:18         ` Sai Prakash Ranjan
2020-03-27 19:02     ` Robin Murphy
2020-03-27 19:02       ` Robin Murphy
2020-03-28  7:35       ` Sai Prakash Ranjan
2020-03-28  7:35         ` Sai Prakash Ranjan
2020-03-30 18:24         ` Doug Anderson
2020-03-30 18:24           ` Doug Anderson
2020-03-31  7:36           ` Sai Prakash Ranjan
2020-03-31  7:36             ` Sai Prakash Ranjan
2020-03-31  7:44             ` Will Deacon
2020-03-31  7:44               ` Will Deacon
2020-03-31  7:53               ` Sai Prakash Ranjan
2020-03-31  7:53                 ` Sai Prakash Ranjan
2020-04-22 19:49                 ` Doug Anderson
2020-04-22 19:49                   ` Doug Anderson
2020-04-23  8:17                   ` Sai Prakash Ranjan
2020-04-23  8:17                     ` Sai Prakash Ranjan
2020-04-23  9:28                     ` Robin Murphy
2020-04-23  9:28                       ` Robin Murphy
2020-04-23  9:41                       ` Sai Prakash Ranjan [this message]
2020-04-23  9:41                         ` Sai Prakash Ranjan

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=685e51afcf8f89c2d8e225716a57b67a@codeaurora.org \
    --to=saiprakash.ranjan@codeaurora.org \
    --cc=dianders@chromium.org \
    --cc=iommu@lists.linux-foundation.org \
    --cc=joro@8bytes.org \
    --cc=linux-arm-msm-owner@vger.kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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.