From: Will Deacon <will.deacon-5wv7dgnIgG8@public.gmane.org>
To: Joerg Roedel <joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
Cc: "srv_heupstream-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org"
<srv_heupstream-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>,
"linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Tomasz Figa <tfiga-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>,
"iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org"
<iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org>,
"linux-mediatek-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org"
<linux-mediatek-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>,
"linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org"
<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>,
Sascha Hauer <kernel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>,
Matthias Brugger
<matthias.bgg-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Yong Wu <yong.wu-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>,
Lucas Stach <l.stach-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
Subject: Re: [RFC PATCH] iommu: add ARM short descriptor page table allocator.
Date: Tue, 5 May 2015 18:05:41 +0100 [thread overview]
Message-ID: <20150505170541.GN1550@arm.com> (raw)
In-Reply-To: <20150505161802.GA20611-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
On Tue, May 05, 2015 at 05:18:02PM +0100, Joerg Roedel wrote:
> On Tue, Apr 28, 2015 at 03:41:21PM +0800, Yong Wu wrote:
> > This patch is for ARM Short Descriptor Format.It has 2-levels
> > pagetable and the allocator supports 4K/64K/1M/16M.
> >
> > Signed-off-by: Yong Wu <yong.wu-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
> > ---
> > drivers/iommu/Kconfig | 7 +
> > drivers/iommu/Makefile | 1 +
> > drivers/iommu/io-pgtable-arm-short.c | 489 +++++++++++++++++++++++++++++++++++
> > drivers/iommu/io-pgtable.c | 4 +
> > drivers/iommu/io-pgtable.h | 6 +
> > 5 files changed, 507 insertions(+)
> > create mode 100644 drivers/iommu/io-pgtable-arm-short.c
>
> What is the context of this, where will it be used?
I think the MT8173 IOMMU [1] uses this format and, since it's part of
the ARM architecture, the ARM SMMU can make use of it too if the
implementation supports it.
Will
[1]
http://lists.infradead.org/pipermail/linux-mediatek/2015-March/000058.html
WARNING: multiple messages have this Message-ID (diff)
From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH] iommu: add ARM short descriptor page table allocator.
Date: Tue, 5 May 2015 18:05:41 +0100 [thread overview]
Message-ID: <20150505170541.GN1550@arm.com> (raw)
In-Reply-To: <20150505161802.GA20611@8bytes.org>
On Tue, May 05, 2015 at 05:18:02PM +0100, Joerg Roedel wrote:
> On Tue, Apr 28, 2015 at 03:41:21PM +0800, Yong Wu wrote:
> > This patch is for ARM Short Descriptor Format.It has 2-levels
> > pagetable and the allocator supports 4K/64K/1M/16M.
> >
> > Signed-off-by: Yong Wu <yong.wu@mediatek.com>
> > ---
> > drivers/iommu/Kconfig | 7 +
> > drivers/iommu/Makefile | 1 +
> > drivers/iommu/io-pgtable-arm-short.c | 489 +++++++++++++++++++++++++++++++++++
> > drivers/iommu/io-pgtable.c | 4 +
> > drivers/iommu/io-pgtable.h | 6 +
> > 5 files changed, 507 insertions(+)
> > create mode 100644 drivers/iommu/io-pgtable-arm-short.c
>
> What is the context of this, where will it be used?
I think the MT8173 IOMMU [1] uses this format and, since it's part of
the ARM architecture, the ARM SMMU can make use of it too if the
implementation supports it.
Will
[1]
http://lists.infradead.org/pipermail/linux-mediatek/2015-March/000058.html
WARNING: multiple messages have this Message-ID (diff)
From: Will Deacon <will.deacon@arm.com>
To: Joerg Roedel <joro@8bytes.org>
Cc: Yong Wu <yong.wu@mediatek.com>,
Matthias Brugger <matthias.bgg@gmail.com>,
Robin Murphy <Robin.Murphy@arm.com>,
Tomasz Figa <tfiga@google.com>,
Lucas Stach <l.stach@pengutronix.de>,
"linux-mediatek@lists.infradead.org"
<linux-mediatek@lists.infradead.org>,
Sascha Hauer <kernel@pengutronix.de>,
"srv_heupstream@mediatek.com" <srv_heupstream@mediatek.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"iommu@lists.linux-foundation.org"
<iommu@lists.linux-foundation.org>
Subject: Re: [RFC PATCH] iommu: add ARM short descriptor page table allocator.
Date: Tue, 5 May 2015 18:05:41 +0100 [thread overview]
Message-ID: <20150505170541.GN1550@arm.com> (raw)
In-Reply-To: <20150505161802.GA20611@8bytes.org>
On Tue, May 05, 2015 at 05:18:02PM +0100, Joerg Roedel wrote:
> On Tue, Apr 28, 2015 at 03:41:21PM +0800, Yong Wu wrote:
> > This patch is for ARM Short Descriptor Format.It has 2-levels
> > pagetable and the allocator supports 4K/64K/1M/16M.
> >
> > Signed-off-by: Yong Wu <yong.wu@mediatek.com>
> > ---
> > drivers/iommu/Kconfig | 7 +
> > drivers/iommu/Makefile | 1 +
> > drivers/iommu/io-pgtable-arm-short.c | 489 +++++++++++++++++++++++++++++++++++
> > drivers/iommu/io-pgtable.c | 4 +
> > drivers/iommu/io-pgtable.h | 6 +
> > 5 files changed, 507 insertions(+)
> > create mode 100644 drivers/iommu/io-pgtable-arm-short.c
>
> What is the context of this, where will it be used?
I think the MT8173 IOMMU [1] uses this format and, since it's part of
the ARM architecture, the ARM SMMU can make use of it too if the
implementation supports it.
Will
[1]
http://lists.infradead.org/pipermail/linux-mediatek/2015-March/000058.html
next prev parent reply other threads:[~2015-05-05 17:05 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-28 7:41 [RFC PATCH] iommu: add ARM short descriptor page table allocator Yong Wu
2015-04-28 7:41 ` Yong Wu
2015-04-28 7:41 ` Yong Wu
[not found] ` <1430206881-18294-1-git-send-email-yong.wu-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
2015-05-05 16:18 ` Joerg Roedel
2015-05-05 16:18 ` Joerg Roedel
2015-05-05 16:18 ` Joerg Roedel
[not found] ` <20150505161802.GA20611-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
2015-05-05 17:05 ` Will Deacon [this message]
2015-05-05 17:05 ` Will Deacon
2015-05-05 17:05 ` Will Deacon
[not found] ` <20150505170541.GN1550-5wv7dgnIgG8@public.gmane.org>
2015-05-11 10:13 ` Joerg Roedel
2015-05-11 10:13 ` Joerg Roedel
2015-05-11 10:13 ` Joerg Roedel
[not found] ` <20150511101309.GH20611-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
2015-05-11 10:40 ` Will Deacon
2015-05-11 10:40 ` Will Deacon
2015-05-11 10:40 ` Will Deacon
[not found] ` <20150511104030.GA4795-5wv7dgnIgG8@public.gmane.org>
2015-05-12 5:30 ` Yong Wu
2015-05-12 5:30 ` Yong Wu
2015-05-12 5:30 ` Yong Wu
2015-05-12 9:15 ` Matthias Brugger
2015-05-12 9:15 ` Matthias Brugger
[not found] ` <CABuKBeKupM0zmWu6T3g5omH7PRo9Oxp85bfpQVhC1ur16_dzvg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-05-13 2:52 ` Yong Wu
2015-05-13 2:52 ` Yong Wu
2015-05-13 2:52 ` Yong Wu
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=20150505170541.GN1550@arm.com \
--to=will.deacon-5wv7dgnigg8@public.gmane.org \
--cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org \
--cc=kernel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org \
--cc=l.stach-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-mediatek-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=matthias.bgg-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=srv_heupstream-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org \
--cc=tfiga-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org \
--cc=yong.wu-NuS5LvNUpcJWk0Htik3J/w@public.gmane.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.