linux-kernel - Re: [PATCH v6 2/7] arm64: Introduce VA

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 15 Jul 2014 22:44:56 +0100
From:	Catalin Marinas <Catalin.Marinas@....com>
To:	Jungseok Lee <jungseoklee85@...il.com>
CC:	Joel Schopp <joel.schopp@....com>,
	Timur Tabi <timur@...eaurora.org>,
	"steve.capper@...aro.org" <steve.capper@...aro.org>,
	Arnd Bergmann <arnd@...db.de>,
	Marc Zyngier <Marc.Zyngier@....com>,
	lkml <linux-kernel@...r.kernel.org>,
	linux-samsung-soc <linux-samsung-soc@...r.kernel.org>,
	"linux-arm-kernel@...ts.infradead.org" 
	<linux-arm-kernel@...ts.infradead.org>,
	"barami97@...il.com" <barami97@...il.com>,
	"kvmarm@...ts.cs.columbia.edu" <kvmarm@...ts.cs.columbia.edu>,
	Christoffer Dall <christoffer.dall@...aro.org>
Subject: Re: [PATCH v6 2/7] arm64: Introduce VA_BITS and translation level
 options

On 15 Jul 2014, at 15:53, Jungseok Lee <jungseoklee85@...il.com> 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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/