From: Muli Ben-Yehuda <muli@il.ibm.com>
To: Olof Johansson <olof@lixom.net>
Cc: Jon Mason <jdmason@us.ibm.com>, Pavel Machek <pavel@suse.cz>,
Muli Ben-Yehuda <mulix@mulix.org>, Andi Kleen <ak@suse.de>,
Linux-Kernel <linux-kernel@vger.kernel.org>,
discuss@x86-64.org, Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH RFC 2/3] x86-64: Calgary IOMMU - Calgary specific bits
Date: Wed, 15 Mar 2006 03:52:26 +0200 [thread overview]
Message-ID: <20060315015226.GD725@rhun.zurich.ibm.com> (raw)
In-Reply-To: <20060315005632.GE5170@pb15.lixom.net>
On Tue, Mar 14, 2006 at 06:56:32PM -0600, Olof Johansson wrote:
> We're killing structures like that one by one on PPC, I just haven't
> gotten around to dealing with tce_entry yet.
>
> The way to do it is to use masking and shifting by hand.
I actually wrote it that way and compared with the bitmapped TCE at
run time to convince myself the bitmap version is doing the right
thing (it does). Then I kept the bitmap version since if that's what
PPC does, it can't be bad :-)
Will fix.
Cheers,
Muli
next prev parent reply other threads:[~2006-03-15 1:52 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
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 [this message]
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=20060315015226.GD725@rhun.zurich.ibm.com \
--to=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 \
--cc=olof@lixom.net \
--cc=pavel@suse.cz \
/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