From: Christoffer Dall <christoffer.dall@linaro.org>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: KVM devel mailing list <kvm@vger.kernel.org>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
Marc Zyngier <marc.zyngier@arm.com>,
Catalin Marinas <catalin.marinas@arm.com>,
"kvmarm@lists.cs.columbia.edu" <kvmarm@lists.cs.columbia.edu>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] arm64: KVM: Turn kvm_ksym_ref into a NOP on VHE
Date: Mon, 21 Mar 2016 13:42:16 +0100 [thread overview]
Message-ID: <20160321124216.GA16859@cbox> (raw)
In-Reply-To: <56EFEABA.3010604@redhat.com>
On Mon, Mar 21, 2016 at 01:36:10PM +0100, Paolo Bonzini wrote:
>
>
> On 21/03/2016 09:47, Ard Biesheuvel wrote:
> > On 18 March 2016 at 18:25, Marc Zyngier <marc.zyngier@arm.com> wrote:
> >> When running with VHE, there is no need to translate kernel pointers
> >> to the EL2 memory space, since we're already there (and we have a much
> >> saner memory map to start with).
> >>
> >> Unfortunately, kvm_ksym_ref is getting in the way, and the first
> >> call into the "hypervisor" section is going to end up in fireworks,
> >> since we're now branching into nowhereland. Meh.
> >>
> >> A potential solution is to test if VHE is engaged or not, and only
> >> perform the translation in the negative case. With this in place,
> >> VHE is able to run again.
> >>
> >> Signed-off-by: Marc Zyngier <marc.zyngier@arm.com>
> >
> > I think you need the & when initializing val, otherwise, it will
> > silently refer to the value rather than the address of a void* symbol
> > if we ever end up using this macro on one.
> >
> > That was the whoie point of the opaque struct type in the original
> > patch that introduced this macro, to disallow references lacking the
> > &, but unfortunately, that was incompatible with the other VHE
> > changes.
> >
> > With that fixed
> >
> > Acked-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
>
> Marc, if you send a v2 I can merge it directly without a pull request.
>
Marc is on holiday this week, but I put this (with the fix) on top of
Linus' master in the kvmarm/master branch:
git://git.kernel.org/pub/scm/linux/kernel/git/kvmarm/kvmarm.git master
Do you want to just grab it from there?
Thanks,
-Christoffer
WARNING: multiple messages have this Message-ID (diff)
From: christoffer.dall@linaro.org (Christoffer Dall)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: KVM: Turn kvm_ksym_ref into a NOP on VHE
Date: Mon, 21 Mar 2016 13:42:16 +0100 [thread overview]
Message-ID: <20160321124216.GA16859@cbox> (raw)
In-Reply-To: <56EFEABA.3010604@redhat.com>
On Mon, Mar 21, 2016 at 01:36:10PM +0100, Paolo Bonzini wrote:
>
>
> On 21/03/2016 09:47, Ard Biesheuvel wrote:
> > On 18 March 2016 at 18:25, Marc Zyngier <marc.zyngier@arm.com> wrote:
> >> When running with VHE, there is no need to translate kernel pointers
> >> to the EL2 memory space, since we're already there (and we have a much
> >> saner memory map to start with).
> >>
> >> Unfortunately, kvm_ksym_ref is getting in the way, and the first
> >> call into the "hypervisor" section is going to end up in fireworks,
> >> since we're now branching into nowhereland. Meh.
> >>
> >> A potential solution is to test if VHE is engaged or not, and only
> >> perform the translation in the negative case. With this in place,
> >> VHE is able to run again.
> >>
> >> Signed-off-by: Marc Zyngier <marc.zyngier@arm.com>
> >
> > I think you need the & when initializing val, otherwise, it will
> > silently refer to the value rather than the address of a void* symbol
> > if we ever end up using this macro on one.
> >
> > That was the whoie point of the opaque struct type in the original
> > patch that introduced this macro, to disallow references lacking the
> > &, but unfortunately, that was incompatible with the other VHE
> > changes.
> >
> > With that fixed
> >
> > Acked-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
>
> Marc, if you send a v2 I can merge it directly without a pull request.
>
Marc is on holiday this week, but I put this (with the fix) on top of
Linus' master in the kvmarm/master branch:
git://git.kernel.org/pub/scm/linux/kernel/git/kvmarm/kvmarm.git master
Do you want to just grab it from there?
Thanks,
-Christoffer
next prev parent reply other threads:[~2016-03-21 12:41 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-18 17:25 [PATCH] arm64: KVM: Turn kvm_ksym_ref into a NOP on VHE Marc Zyngier
2016-03-18 17:25 ` Marc Zyngier
2016-03-18 17:41 ` Robin Murphy
2016-03-18 17:41 ` Robin Murphy
2016-03-18 18:07 ` Catalin Marinas
2016-03-18 18:07 ` Catalin Marinas
2016-03-20 21:07 ` Christoffer Dall
2016-03-20 21:07 ` Christoffer Dall
2016-03-21 11:34 ` Catalin Marinas
2016-03-21 11:34 ` Catalin Marinas
2016-03-21 8:47 ` Ard Biesheuvel
2016-03-21 8:47 ` Ard Biesheuvel
2016-03-21 12:36 ` Paolo Bonzini
2016-03-21 12:36 ` Paolo Bonzini
2016-03-21 12:42 ` Christoffer Dall [this message]
2016-03-21 12:42 ` Christoffer Dall
2016-03-21 14:02 ` Paolo Bonzini
2016-03-21 14:02 ` Paolo Bonzini
2016-03-21 18:55 ` Christoffer Dall
2016-03-21 18:55 ` Christoffer Dall
2016-03-21 20:55 ` Paolo Bonzini
2016-03-21 20:55 ` Paolo Bonzini
2016-03-22 7:33 ` Christoffer Dall
2016-03-22 7:33 ` Christoffer Dall
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=20160321124216.GA16859@cbox \
--to=christoffer.dall@linaro.org \
--cc=ard.biesheuvel@linaro.org \
--cc=catalin.marinas@arm.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=marc.zyngier@arm.com \
--cc=pbonzini@redhat.com \
/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.