public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alexander Duyck <alexander.h.duyck@intel.com>
To: shuah.kh@samsung.com
Cc: akpm@linux-foundation.org, joro@8bytes.org,
	linux-kernel@vger.kernel.org, shuahkhan@gmail.com
Subject: Re: [PATCH] dma-debug: enhance dma_debug_device_change() to check for mapping errors
Date: Tue, 12 Nov 2013 16:22:24 -0800	[thread overview]
Message-ID: <5282C640.3030205@intel.com> (raw)
In-Reply-To: <5282A9C8.9050304@samsung.com>

On 11/12/2013 02:20 PM, Shuah Khan wrote:
> On 11/12/2013 03:12 PM, Alexander Duyck wrote:
>> I think this might be overdoing the error checking by a bit.  I would
>> much rather have the DMA leaked error be visible than have it buried
>> under messages about the failure to check for DMA errors.  In my mind
>> the DMA buffer leak is much more serious than the failure to check for
>> mapping errors.
>>
>
> I agree DMA leak message is more important. Would you like to see just
> one message if mapping errors are found? Instead of printing the
> entire stacktrace like it does now, it could just do warn.
>
> -- Shuah
>
>

I think only one message would be preferred.  If nothing else you might
update the function so that it only dumps the DMA mapping error check on
the first one found and then goes quiet after that.  There is no point
in displaying the same error message multiple times since that is likely
what we would see.

Thanks,

Alex

      reply	other threads:[~2013-11-13  0:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-12 20:51 [PATCH] dma-debug: enhance dma_debug_device_change() to check for mapping errors Shuah Khan
2013-11-12 22:12 ` Alexander Duyck
2013-11-12 22:20   ` Shuah Khan
2013-11-13  0:22     ` Alexander Duyck [this message]

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=5282C640.3030205@intel.com \
    --to=alexander.h.duyck@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=joro@8bytes.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shuah.kh@samsung.com \
    --cc=shuahkhan@gmail.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox