All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@suse.cz>
To: Muli Ben-Yehuda <mulix@mulix.org>
Cc: Andi Kleen <ak@suse.de>, Jon Mason <jdmason@us.ibm.com>,
	Muli Ben-Yehuda <MULI@il.ibm.com>,
	Linux-Kernel <linux-kernel@vger.kernel.org>,
	discuss@x86-64.org, Andrew Morton <akpm@osdl.org>
Subject: Re: [RFC PATCH 3/3] x86-64: Calgary IOMMU - hook it in
Date: Wed, 15 Mar 2006 00:03:48 +0100	[thread overview]
Message-ID: <20060314230348.GC1579@elf.ucw.cz> (raw)
In-Reply-To: <20060314082634.GG23631@granada.merseine.nu>

On Út 14-03-06 10:26:34, Muli Ben-Yehuda wrote:
> This patch hooks Calgary into the build and the x86-64 IOMMU
> initialization paths.
> 
> Signed-Off-By: Muli Ben-Yehuda <mulix@mulix.org>
> Signed-Off-By: Jon Mason <jdmason@us.ibm.com>
> 
> diff -Naurp --exclude-from /home/muli/w/dontdiff iommu_detected/arch/x86_64/Kconfig linux/arch/x86_64/Kconfig
> --- iommu_detected/arch/x86_64/Kconfig	2006-03-14 08:58:23.000000000 +0200
> +++ linux/arch/x86_64/Kconfig	2006-03-12 10:49:04.000000000 +0200
> @@ -372,6 +372,16 @@ config GART_IOMMU
>  	  and a software emulation used on other systems.
>  	  If unsure, say Y.
>  
> +config CALGARY_IOMMU
> +	bool "IBM x366 server IOMMU"
> +	default y
> +	depends on PCI && MPSC && EXPERIMENTAL
> +	help
> +	  Support for hardware IOMMUs in IBM's x366 server
> +	  systems. The IOMMU can be turned off at runtime with the
> +	  iommu=off parameter. Normally the kernel will make the right

Runtime? I think you meant boottime.

> +	  choice by itself.  If unsure, say Y.

Eh? How common are those machines?
								Pavel

-- 
32:        bw.Write( sbuffer );

  reply	other threads:[~2006-03-14 23:04 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-14  8:24 [RFC PATCH 1/3] x86-64: Calgary IOMMU - introduce iommu_detected Muli Ben-Yehuda
2006-03-14  8:25 ` [PATCH RFC 2/3] x86-64: Calgary IOMMU - Calgary specific bits Muli Ben-Yehuda
2006-03-14  8:26   ` [RFC PATCH 3/3] x86-64: Calgary IOMMU - hook it in Muli Ben-Yehuda
2006-03-14 23:03     ` Pavel Machek [this message]
2006-03-14 23:22       ` Jon Mason
2006-03-14 23:26         ` Pavel Machek
2006-03-15  0:06           ` Jon Mason
2006-03-15  1:38             ` Muli Ben-Yehuda
2006-03-14 23:03   ` [PATCH RFC 2/3] x86-64: Calgary IOMMU - Calgary specific bits Pavel Machek
2006-03-15  0:55     ` Jon Mason
2006-03-15  0:56       ` Olof Johansson
2006-03-15  1:27         ` Jon Mason
2006-03-15  3:18           ` Olof Johansson
2006-03-15  1:52         ` Muli Ben-Yehuda
2006-03-14 15:01 ` [RFC PATCH 1/3] x86-64: Calgary IOMMU - introduce iommu_detected Andi Kleen
2006-03-14 15:07   ` Muli Ben-Yehuda

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=20060314230348.GC1579@elf.ucw.cz \
    --to=pavel@suse.cz \
    --cc=MULI@il.ibm.com \
    --cc=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=discuss@x86-64.org \
    --cc=jdmason@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mulix@mulix.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.