From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/1] iommu/arm-smmu: modify the calculation of PASize and SEP fields
Date: Fri, 12 Dec 2014 10:57:49 +0000 [thread overview]
Message-ID: <20141212105749.GC25781@arm.com> (raw)
In-Reply-To: <1418373663-9124-1-git-send-email-thunder.leizhen@huawei.com>
On Fri, Dec 12, 2014 at 08:41:03AM +0000, Zhen Lei wrote:
> 1. the calculation appear 3 times, it's good to define a function.
> 2. VA_BITS is dynamic determined by CONFIG_ARM64_VA_BITS yet, but current
> switch..case can not cover all possible values.
> 3. change TTBCR2_ADDR_xx to ADDR_SIZE_xx, because it's not only TTBCR2 use it.
Please take a look at the pgtable rework I posted recently -- it moves a
bunch of this into a generic framework.
http://lists.infradead.org/pipermail/linux-arm-kernel/2014-November/306786.html
(I plan to post v2 soon).
Will
next prev parent reply other threads:[~2014-12-12 10:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-12 8:41 [PATCH 1/1] iommu/arm-smmu: modify the calculation of PASize and SEP fields Zhen Lei
2014-12-12 10:57 ` Will Deacon [this message]
2014-12-15 11:16 ` leizhen
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=20141212105749.GC25781@arm.com \
--to=will.deacon@arm.com \
--cc=linux-arm-kernel@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).