From: Jungseok Lee <jungseoklee85@gmail.com>
To: Catalin Marinas <Catalin.Marinas@arm.com>
Cc: Joel Schopp <joel.schopp@amd.com>,
Timur Tabi <timur@codeaurora.org>,
"steve.capper@linaro.org" <steve.capper@linaro.org>,
Arnd Bergmann <arnd@arndb.de>,
Marc Zyngier <Marc.Zyngier@arm.com>,
lkml <linux-kernel@vger.kernel.org>,
linux-samsung-soc <linux-samsung-soc@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"barami97@gmail.com" <barami97@gmail.com>,
"kvmarm@lists.cs.columbia.edu" <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: Wed, 16 Jul 2014 23:23:42 +0900 [thread overview]
Message-ID: <6986494B-04F6-45F0-9C39-303D1F5992D3@gmail.com> (raw)
In-Reply-To: <95F7642B-124A-4E03-ACDE-5BF9D70E8E15@arm.com>
On Jul 16, 2014, at 6:44 AM, Catalin Marinas wrote:
> On 15 Jul 2014, at 15:53, Jungseok Lee <jungseoklee85@gmail.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.
Hi Catalin,
Thanks for the work!
I will take a close look at them.
- Jungseok Lee
prev parent reply other threads:[~2014-07-16 14:23 UTC|newest]
Thread overview: 7+ 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-07-14 19:53 ` Timur Tabi
2014-07-14 20:38 ` Joel Schopp
2014-07-14 22:41 ` Catalin Marinas
2014-07-15 14:53 ` Jungseok Lee
2014-07-15 21:44 ` Catalin Marinas
2014-07-16 14:23 ` Jungseok Lee [this message]
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=6986494B-04F6-45F0-9C39-303D1F5992D3@gmail.com \
--to=jungseoklee85@gmail.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=joel.schopp@amd.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 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).