All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joerg Roedel <joerg.roedel@amd.com>
To: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
Cc: mingo@elte.hu, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] remove fullflush and nofullflush in IOMMU generic option
Date: Mon, 22 Sep 2008 18:23:14 +0200	[thread overview]
Message-ID: <20080922162314.GC24392@amd.com> (raw)
In-Reply-To: <20080923002516R.fujita.tomonori@lab.ntt.co.jp>

On Tue, Sep 23, 2008 at 12:25:24AM +0900, FUJITA Tomonori wrote:
> 
> I'm not sure we can because he has a quite different opinion on this,
> he thinks that the IOMMU parameters are unimportant and minor issue.
> 

Stop your personal attacks and come down. I've never said that iommu
parameters are unimportant. The _move_ of the iommu=[no]fullflush to
generic code is a minor issue in my opinion. For the user it changes
nothing. There was an iommu=fullflush parameter before and now there is
also an iommu=fullflush parameter. The only difference is that it now
affects AMD IOMMU too.

> I'm against adding new generic IOMMU parameters without serious
> consideration. Joerg thinks that we can clean up the parameters like
> adding some for 2.6.28, then add some for 2.6.X, then rename some, in
> an ad-hoc way.

Again. Stop your personal attacks.

Joerg

-- 
           |           AMD Saxony Limited Liability Company & Co. KG
 Operating |         Wilschdorfer Landstr. 101, 01109 Dresden, Germany
 System    |                  Register Court Dresden: HRA 4896
 Research  |              General Partner authorized to represent:
 Center    |             AMD Saxony LLC (Wilmington, Delaware, US)
           | General Manager of AMD Saxony LLC: Dr. Hans-R. Deppe, Thomas McCoy


  reply	other threads:[~2008-09-22 16:23 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-19 16:23 [PATCH] remove fullflush and nofullflush in IOMMU generic option FUJITA Tomonori
2008-09-19 16:45 ` Joerg Roedel
2008-09-19 17:09   ` FUJITA Tomonori
2008-09-19 17:20     ` Joerg Roedel
2008-09-19 17:34       ` FUJITA Tomonori
2008-09-19 17:46         ` Joerg Roedel
2008-09-19 18:40           ` FUJITA Tomonori
2008-09-19 19:42             ` Joerg Roedel
2008-09-19 17:30     ` Joerg Roedel
2008-09-19 17:40       ` FUJITA Tomonori
2008-09-19 18:01         ` Joerg Roedel
2008-09-19 18:48           ` FUJITA Tomonori
2008-09-19 19:52             ` Joerg Roedel
2008-09-19 20:02               ` FUJITA Tomonori
2008-09-19 20:19                 ` Joerg Roedel
2008-09-19 21:56                   ` FUJITA Tomonori
2008-09-19 22:09                     ` Joerg Roedel
2008-09-19 22:18                       ` FUJITA Tomonori
2008-09-19 22:39                         ` Joerg Roedel
2008-09-20  0:54                           ` FUJITA Tomonori
2008-09-20  6:00 ` Ingo Molnar
2008-09-20 13:57   ` FUJITA Tomonori
2008-09-22 11:17     ` Ingo Molnar
2008-09-22 12:05       ` Joerg Roedel
2008-09-22 15:25       ` FUJITA Tomonori
2008-09-22 16:23         ` Joerg Roedel [this message]
2008-09-22 16:51           ` FUJITA Tomonori
2008-09-22 18:34             ` Joerg Roedel
2008-09-22 18:48               ` Ingo Molnar
2008-09-22 19:01                 ` Joerg Roedel
2008-09-24 13:12               ` FUJITA Tomonori

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=20080922162314.GC24392@amd.com \
    --to=joerg.roedel@amd.com \
    --cc=fujita.tomonori@lab.ntt.co.jp \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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.