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: Sat, 20 Sep 2008 00:09:46 +0200 [thread overview]
Message-ID: <20080919220946.GB11410@amd.com> (raw)
In-Reply-To: <20080920065630N.fujita.tomonori@lab.ntt.co.jp>
On Sat, Sep 20, 2008 at 06:56:21AM +0900, FUJITA Tomonori wrote:
>
> Because you did things int the wrong way, I said again and again.
>
> I can't see why you refuse to do the things in the proper way.
>
>
> > objections agains the generic iommu=fullflush come up. The patch does
> > not break anything and just moves the iommu=flush parameter (which is
> > already available) to pci-dma.c to make it useable by AMD IOMMU too.
>
> Breaking anything does mean that it's fine. My patch doesn't break
> anything too.
>
> I'm not against fullflush (as I said again and again). I guess that
> it's the right move though it might be not so useful if VT-d doesn't
> support it.
>
> I'm against totally pointless nofullflush and the way you changed the
> generic IOMMU code.
Then submit a patch that changes it to the version you prefer. I already
said that I am fine with the removal of nofullflush. But completly
reverting is the wrong way. For AMD IOMMU I want to use the
iommu=fullflush way because I want to reuse a parameter thats already
there. Thats why I am against your reverting patch.
So now I stop repeating my points again and again. EOD.
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
next prev parent reply other threads:[~2008-09-19 22:10 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 [this message]
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
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=20080919220946.GB11410@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox