public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Andi Kleen <ak@suse.de>
Cc: Muli Ben-Yehuda <muli@il.ibm.com>,
	Sebastian Biallas <sb@biallas.net>,
	linux-kernel@vger.kernel.org
Subject: Re: PCI-DMA: Disabling IOMMU
Date: Thu, 19 Oct 2006 13:08:08 +0100	[thread overview]
Message-ID: <1161259688.17335.32.camel@localhost.localdomain> (raw)
In-Reply-To: <200610182348.44968.ak@suse.de>

Ar Mer, 2006-10-18 am 23:48 +0200, ysgrifennodd Andi Kleen:
> On Wednesday 18 October 2006 23:15, Muli Ben-Yehuda wrote:
> > On Wed, Oct 18, 2006 at 05:03:36PM +0200, Sebastian Biallas wrote:
> > 
> > > Should I worry about this IOMMU-disabling? All other Linux/IOMMU stuff I
> > > found had AGP or BIOS messages nearby, but I only get this single
> > > "PCI-DMA: Disabling IOMMU" line, without any hint.
> > 
> > No, it's fine. Just a badly worded information message. Andi, how
> > about something like this?
> 
> I think the original message is fine. I'm sure someone will be alarmed
> about any possible message, but we can't help them.

Actually if you flip it around and print
"PCI-DMA: Enabling IOMMU"

and keep quiet if you disable it then users should be happy because its
turned something on and that is clearly always good 8)



  parent reply	other threads:[~2006-10-19 12:06 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-18 15:03 PCI-DMA: Disabling IOMMU Sebastian Biallas
2006-10-18 15:41 ` Prakash Punnoor
2006-10-18 15:51   ` Sebastian Biallas
2006-10-18 21:16     ` Muli Ben-Yehuda
2006-10-18 21:15   ` Muli Ben-Yehuda
2006-10-18 21:15 ` Muli Ben-Yehuda
2006-10-18 21:48   ` Andi Kleen
2006-10-19  5:15     ` Muli Ben-Yehuda
2006-10-19 11:52       ` Andi Kleen
2006-10-19 12:08     ` Alan Cox [this message]
2006-10-19 13:04       ` Andi Kleen

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=1161259688.17335.32.camel@localhost.localdomain \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=ak@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=muli@il.ibm.com \
    --cc=sb@biallas.net \
    /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