public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: Grant Grundler <grundler@parisc-linux.org>
Cc: Matthew Wilcox <matthew@wil.cx>, Yinghai Lu <yinghai@kernel.org>,
	Jesse Barnes <jbarnes@virtuousgeek.org>,
	Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
	"H. Peter Anvin" <hpa@zytor.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org
Subject: Re: [PATCH] pci: show dma_mask bits in /sys
Date: Fri, 24 Oct 2008 12:50:12 +0200	[thread overview]
Message-ID: <87zlku8dy3.fsf@basil.nowhere.org> (raw)
In-Reply-To: <20081023064412.GD31186@colo.lackof.org> (Grant Grundler's message of "Thu, 23 Oct 2008 00:44:12 -0600")

Grant Grundler <grundler@parisc-linux.org> writes:

> On Wed, Oct 22, 2008 at 09:28:33PM -0600, Matthew Wilcox wrote:
>> On Wed, Oct 22, 2008 at 06:45:10PM -0700, Yinghai Lu wrote:
>> > Grant prefer to add it /sys instead of showing in bootlog
>> > 
>> > so could catch if the driver set the correct dma_mask.
>> 
>> I still don't think this is useful information to be exposing.
>
> It's useful for anyone involved with device drivers - we agree that's
> a very limited subset of users.  I certainly get fed up with trying
> to figure out which dma_mask each driver is using since in some

One simple way that doesn't need any kernel changes is to use
crash on the running kernel. I personally just stuck in printks
when I needed that, but it doesn't strike me as something that 
is generally useful in standard kernels (agreeing with Willy)

-Andi
-- 
ak@linux.intel.com

  parent reply	other threads:[~2008-10-24 10:50 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-08 23:02 [PATCH] pci: print out DMA mask info Yinghai Lu
2008-10-09 21:18 ` Grant Grundler
2008-10-09 21:27   ` Yinghai Lu
2008-10-09 21:35     ` Matthew Wilcox
2008-10-09 21:51       ` Yinghai Lu
2008-10-09 22:55         ` Grant Grundler
2008-10-09 23:05           ` Yinghai Lu
2008-10-10  2:40             ` FUJITA Tomonori
2008-10-10  4:56               ` Yinghai Lu
2008-10-10  6:08                 ` FUJITA Tomonori
2008-10-10  6:32                   ` Yinghai Lu
2008-10-10  7:32                     ` FUJITA Tomonori
2008-10-12  7:16                       ` Grant Grundler
2008-10-10 22:45               ` Grant Grundler
2008-10-14  6:50                 ` FUJITA Tomonori
2008-10-12  7:11             ` Grant Grundler
2008-10-23  1:45               ` [PATCH] pci: show dma_mask bits in /sys Yinghai Lu
2008-10-23  3:28                 ` Matthew Wilcox
2008-10-23  4:19                   ` Yinghai Lu
2008-10-23  6:44                   ` Grant Grundler
2008-10-23  8:38                     ` Rolf Eike Beer
2008-10-23 15:39                     ` Greg KH
2008-10-23 18:37                       ` H. Peter Anvin
2008-10-23 19:36                       ` Grant Grundler
2008-10-23 19:49                         ` Greg KH
2008-10-24 10:50                     ` Andi Kleen [this message]
2008-11-01 17:10                       ` Grant Grundler
2008-10-23  6:48                 ` Grant Grundler
2008-10-23  6:51                   ` Yinghai Lu
2008-10-23 19:28                     ` Grant Grundler
2008-10-10  2:40     ` [PATCH] pci: print out DMA mask info FUJITA Tomonori
2008-10-10  2:59       ` FUJITA Tomonori
2008-10-10  2:40   ` FUJITA Tomonori
2008-10-10 15:48     ` Jesse Barnes
2008-10-10 16:19       ` Yinghai Lu
2008-10-10 16:28         ` Jesse Barnes
2008-10-10 16:33         ` Matthew Wilcox
2008-10-10 16:46           ` Yinghai Lu
2008-10-10 17:12             ` Matthew Wilcox
2008-10-10 17:18               ` Roland Dreier
2008-10-12  7:38                 ` Grant Grundler
2008-10-12  7:20       ` Grant Grundler

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=87zlku8dy3.fsf@basil.nowhere.org \
    --to=andi@firstfloor.org \
    --cc=akpm@linux-foundation.org \
    --cc=grundler@parisc-linux.org \
    --cc=hpa@zytor.com \
    --cc=jbarnes@virtuousgeek.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=matthew@wil.cx \
    --cc=mingo@elte.hu \
    --cc=tglx@linutronix.de \
    --cc=yinghai@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox