From: Joel Schopp <joel.schopp@amd.com>
To: Timur Tabi <timur@codeaurora.org>,
Jungseok Lee <jungseoklee85@gmail.com>
Cc: Kukjin Kim <kgene.kim@samsung.com>,
steve.capper@linaro.org, Arnd Bergmann <arnd@arndb.de>,
Marc Zyngier <Marc.Zyngier@arm.com>,
Catalin.Marinas@arm.com, lkml <linux-kernel@vger.kernel.org>,
ilho215.lee@samsung.com,
linux-samsung-soc <linux-samsung-soc@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
barami97@gmail.com, kvmarm@lists.cs.columbia.edu,
Christoffer Dall <christoffer.dall@linaro.org>
Subject: Re: [PATCH v6 2/7] arm64: Introduce VA_BITS and translation level options
Date: Mon, 14 Jul 2014 15:38:59 -0500 [thread overview]
Message-ID: <53C43FE3.1050008@amd.com> (raw)
In-Reply-To: <CAOZdJXWCu-zHuQoAUdiieqsKqCfG9BsZariFqQP=NCgQP-zpNA@mail.gmail.com>
I agree that these patches would be very useful. I just rebased my fix
for a VTTBR_BADDR_MASK bug on one of these patches that could be pulled
out independently. See
https://lists.cs.columbia.edu/pipermail/kvmarm/2014-July/010480.html
The original author Jungseok Lee is no longer available to work on
future versions of these patches. I was thinking that if they didn't
get picked up as they are that with the original author's blessing I
would pick them up and keep them forward ported/resubmitted. I have an
SOC to test them on.
-Joel
On 07/14/2014 02:53 PM, Timur Tabi wrote:
> On Mon, May 12, 2014 at 4:40 AM, Jungseok Lee <jays.lee@samsung.com> wrote:
>> This patch adds virtual address space size and a level of translation
>> tables to kernel configuration. It facilicates introduction of
>> different MMU options, such as 4KB + 4 levels, 16KB + 4 levels and
>> 64KB + 3 levels, easily.
> Is there a reason why this patch has not yet been picked up? It
> appears to work just fine, and the change is necessary for ARM SOCs
> that support large amounts of memory. It seems weird that after so
> many versions, reviews, and ACKs, that it still not in linux-next.
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: joel.schopp@amd.com (Joel Schopp)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v6 2/7] arm64: Introduce VA_BITS and translation level options
Date: Mon, 14 Jul 2014 15:38:59 -0500 [thread overview]
Message-ID: <53C43FE3.1050008@amd.com> (raw)
In-Reply-To: <CAOZdJXWCu-zHuQoAUdiieqsKqCfG9BsZariFqQP=NCgQP-zpNA@mail.gmail.com>
I agree that these patches would be very useful. I just rebased my fix
for a VTTBR_BADDR_MASK bug on one of these patches that could be pulled
out independently. See
https://lists.cs.columbia.edu/pipermail/kvmarm/2014-July/010480.html
The original author Jungseok Lee is no longer available to work on
future versions of these patches. I was thinking that if they didn't
get picked up as they are that with the original author's blessing I
would pick them up and keep them forward ported/resubmitted. I have an
SOC to test them on.
-Joel
On 07/14/2014 02:53 PM, Timur Tabi wrote:
> On Mon, May 12, 2014 at 4:40 AM, Jungseok Lee <jays.lee@samsung.com> wrote:
>> This patch adds virtual address space size and a level of translation
>> tables to kernel configuration. It facilicates introduction of
>> different MMU options, such as 4KB + 4 levels, 16KB + 4 levels and
>> 64KB + 3 levels, easily.
> Is there a reason why this patch has not yet been picked up? It
> appears to work just fine, and the change is necessary for ARM SOCs
> that support large amounts of memory. It seems weird that after so
> many versions, reviews, and ACKs, that it still not in linux-next.
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Joel Schopp <joel.schopp@amd.com>
To: Timur Tabi <timur@codeaurora.org>,
Jungseok Lee <jungseoklee85@gmail.com>
Cc: Kukjin Kim <kgene.kim@samsung.com>, <steve.capper@linaro.org>,
"Arnd Bergmann" <arnd@arndb.de>,
Marc Zyngier <Marc.Zyngier@arm.com>, <Catalin.Marinas@arm.com>,
lkml <linux-kernel@vger.kernel.org>, <ilho215.lee@samsung.com>,
linux-samsung-soc <linux-samsung-soc@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>, <barami97@gmail.com>,
<kvmarm@lists.cs.columbia.edu>,
Christoffer Dall <christoffer.dall@linaro.org>
Subject: Re: [PATCH v6 2/7] arm64: Introduce VA_BITS and translation level options
Date: Mon, 14 Jul 2014 15:38:59 -0500 [thread overview]
Message-ID: <53C43FE3.1050008@amd.com> (raw)
In-Reply-To: <CAOZdJXWCu-zHuQoAUdiieqsKqCfG9BsZariFqQP=NCgQP-zpNA@mail.gmail.com>
I agree that these patches would be very useful. I just rebased my fix
for a VTTBR_BADDR_MASK bug on one of these patches that could be pulled
out independently. See
https://lists.cs.columbia.edu/pipermail/kvmarm/2014-July/010480.html
The original author Jungseok Lee is no longer available to work on
future versions of these patches. I was thinking that if they didn't
get picked up as they are that with the original author's blessing I
would pick them up and keep them forward ported/resubmitted. I have an
SOC to test them on.
-Joel
On 07/14/2014 02:53 PM, Timur Tabi wrote:
> On Mon, May 12, 2014 at 4:40 AM, Jungseok Lee <jays.lee@samsung.com> wrote:
>> This patch adds virtual address space size and a level of translation
>> tables to kernel configuration. It facilicates introduction of
>> different MMU options, such as 4KB + 4 levels, 16KB + 4 levels and
>> 64KB + 3 levels, easily.
> Is there a reason why this patch has not yet been picked up? It
> appears to work just fine, and the change is necessary for ARM SOCs
> that support large amounts of memory. It seems weird that after so
> many versions, reviews, and ACKs, that it still not in linux-next.
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2014-07-14 20:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-12 9:40 [PATCH v6 2/7] arm64: Introduce VA_BITS and translation level options Jungseok Lee
2014-05-12 9:40 ` Jungseok Lee
2014-07-14 19:53 ` Timur Tabi
2014-07-14 19:53 ` Timur Tabi
2014-07-14 20:38 ` Joel Schopp [this message]
2014-07-14 20:38 ` Joel Schopp
2014-07-14 20:38 ` Joel Schopp
2014-07-14 22:41 ` Catalin Marinas
2014-07-14 22:41 ` Catalin Marinas
2014-07-15 14:53 ` Jungseok Lee
2014-07-15 14:53 ` Jungseok Lee
2014-07-15 21:44 ` Catalin Marinas
2014-07-15 21:44 ` Catalin Marinas
2014-07-15 21:44 ` Catalin Marinas
2014-07-16 14:23 ` Jungseok Lee
2014-07-16 14:23 ` Jungseok Lee
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=53C43FE3.1050008@amd.com \
--to=joel.schopp@amd.com \
--cc=Catalin.Marinas@arm.com \
--cc=Marc.Zyngier@arm.com \
--cc=arnd@arndb.de \
--cc=barami97@gmail.com \
--cc=christoffer.dall@linaro.org \
--cc=ilho215.lee@samsung.com \
--cc=jungseoklee85@gmail.com \
--cc=kgene.kim@samsung.com \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=steve.capper@linaro.org \
--cc=timur@codeaurora.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.