On Mon, May 12, 2014 at 4:40 AM, Jungseok Lee <[email protected]> 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.
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 <[email protected]> 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
> [email protected]
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
On Mon, Jul 14, 2014 at 09:38:59PM +0100, Joel Schopp wrote:
> 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.
The patches are pretty good. I'll give them a try tomorrow and if there
isn't something fundamental missing I'll consider taking them for 3.17.
--
Catalin
On Jul 15, 2014, at 7:41 AM, Catalin Marinas wrote:
> On Mon, Jul 14, 2014 at 09:38:59PM +0100, Joel Schopp wrote:
>> 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.
>
> The patches are pretty good. I'll give them a try tomorrow and if there
> isn't something fundamental missing I'll consider taking them for 3.17.
Hi All,
If only stage1 side is taken and merged, KVM should be disabled under 4 level
lookups with the following configuration adjustment. I've tested it on top of
arm64/for-next/core branch and it works fine.
--- a/arch/arm64/kvm/Kconfig
+++ b/arch/arm64/kvm/Kconfig
@@ -18,6 +18,7 @@ if VIRTUALIZATION
config KVM
bool "Kernel-based Virtual Machine (KVM) support"
+ depends on !ARM64_4_LEVELS
select MMU_NOTIFIER
select PREEMPT_NOTIFIERS
select ANON_INODES
However, I don't know whether it does make sense or not.
In other words, stage2 side should be prepared to fully support 4 level lookups.
In order to cover all combinations of host and guest, VTTBR_X should be determined
dynamically as referring to hardware capability. At this point, the patches have
been revised many times, but they don't have got ACKs from Christoffer and Marc yet.
That is why the patches are pending now in the author's point of view.
- Jungseok Lee-
On 15 Jul 2014, at 15:53, Jungseok Lee <[email protected]> wrote:
> On Jul 15, 2014, at 7:41 AM, Catalin Marinas wrote:
>> On Mon, Jul 14, 2014 at 09:38:59PM +0100, Joel Schopp wrote:
>>> 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.
>>
>> The patches are pretty good. I'll give them a try tomorrow and if there
>> isn't something fundamental missing I'll consider taking them for 3.17.
>
> Hi All,
>
> If only stage1 side is taken and merged, KVM should be disabled under 4 level
> lookups with the following configuration adjustment. I've tested it on top of
> arm64/for-next/core branch and it works fine.
>
> --- a/arch/arm64/kvm/Kconfig
> +++ b/arch/arm64/kvm/Kconfig
> @@ -18,6 +18,7 @@ if VIRTUALIZATION
>
> config KVM
> bool "Kernel-based Virtual Machine (KVM) support"
> + depends on !ARM64_4_LEVELS
> select MMU_NOTIFIER
> select PREEMPT_NOTIFIERS
> select ANON_INODES
>
> However, I don't know whether it does make sense or not.
I added some patches on top of your series, I hope to be able to post
them tomorrow. My interim approach was to disable 4-levels if KVM is
enabled.
> In other words, stage2 side should be prepared to fully support 4 level lookups.
>
> In order to cover all combinations of host and guest, VTTBR_X should be determined
> dynamically as referring to hardware capability. At this point, the patches have
> been revised many times, but they don't have got ACKs from Christoffer and Marc yet.
>
> That is why the patches are pending now in the author's point of view.
I have some clean-up for stage 1 on top but nothing major.
Catalin
-- IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
ARM Limited, Registered office 110 Fulbourn Road, Cambridge CB1 9NJ, Registered in England & Wales, Company No: 2557590
ARM Holdings plc, Registered office 110 Fulbourn Road, Cambridge CB1 9NJ, Registered in England & Wales, Company No: 2548782
On Jul 16, 2014, at 6:44 AM, Catalin Marinas wrote:
> On 15 Jul 2014, at 15:53, Jungseok Lee <[email protected]> wrote:
>> On Jul 15, 2014, at 7:41 AM, Catalin Marinas wrote:
>>> On Mon, Jul 14, 2014 at 09:38:59PM +0100, Joel Schopp wrote:
>>>> 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.
>>>
>>> The patches are pretty good. I'll give them a try tomorrow and if there
>>> isn't something fundamental missing I'll consider taking them for 3.17.
>>
>> Hi All,
>>
>> If only stage1 side is taken and merged, KVM should be disabled under 4 level
>> lookups with the following configuration adjustment. I've tested it on top of
>> arm64/for-next/core branch and it works fine.
>>
>> --- a/arch/arm64/kvm/Kconfig
>> +++ b/arch/arm64/kvm/Kconfig
>> @@ -18,6 +18,7 @@ if VIRTUALIZATION
>>
>> config KVM
>> bool "Kernel-based Virtual Machine (KVM) support"
>> + depends on !ARM64_4_LEVELS
>> select MMU_NOTIFIER
>> select PREEMPT_NOTIFIERS
>> select ANON_INODES
>>
>> However, I don't know whether it does make sense or not.
>
> I added some patches on top of your series, I hope to be able to post
> them tomorrow. My interim approach was to disable 4-levels if KVM is
> enabled.
Hi Catalin,
Thanks for the work!
I will take a close look at them.
- Jungseok Lee-