mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bertrand Marquis <Bertrand.Marquis@arm.com>
To: Stefano Stabellini <sstabellini@kernel.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Stefano Stabellini <stefano.stabellini@xilinx.com>,
	"boris.ostrovsky@oracle.com" <boris.ostrovsky@oracle.com>,
	Juergen Gross <jgross@suse.com>
Subject: Re: [PATCH] xen/arm: do not setup the runstate info page if kpti is enabled
Date: Fri, 25 Sep 2020 15:08:23 +0000	[thread overview]
Message-ID: <F3D30F3F-7AEF-43A0-8A2D-A55AA570C3C8@arm.com> (raw)
In-Reply-To: <20200924234955.15455-1-sstabellini@kernel.org>

Hi,

> On 25 Sep 2020, at 00:49, Stefano Stabellini <sstabellini@kernel.org> wrote:
>
> From: Stefano Stabellini <stefano.stabellini@xilinx.com>
>
> The VCPUOP_register_runstate_memory_area hypercall takes a virtual
> address of a buffer as a parameter. The semantics of the hypercall are
> such that the virtual address should always be valid.
>
> When KPTI is enabled and we are running userspace code, the virtual
> address is not valid, thus, Linux is violating the semantics of
> VCPUOP_register_runstate_memory_area.
>
> Do not call VCPUOP_register_runstate_memory_area when KPTI is enabled.
>
> Signed-off-by: Stefano Stabellini <stefano.stabellini@xilinx.com>
Reviewed-by: Bertrand Marquis <bertrand.marquis@arm.com>

I tested this on an Arm64 FVP and Errors generated by Xen are not present anymore.
Thanks a lot for the patch Stefano.

Cheers,
Bertrand

> CC: Bertrand Marquis <Bertrand.Marquis@arm.com>
> CC: boris.ostrovsky@oracle.com
> CC: jgross@suse.com
> ---
> arch/arm/include/asm/xen/page.h   | 5 +++++
> arch/arm/xen/enlighten.c          | 6 ++++--
> arch/arm64/include/asm/xen/page.h | 6 ++++++
> 3 files changed, 15 insertions(+), 2 deletions(-)
>
> diff --git a/arch/arm/include/asm/xen/page.h b/arch/arm/include/asm/xen/page.h
> index 31bbc803cecb..dc7f6e91aafa 100644
> --- a/arch/arm/include/asm/xen/page.h
> +++ b/arch/arm/include/asm/xen/page.h
> @@ -1 +1,6 @@
> #include <xen/arm/page.h>
> +
> +static inline bool xen_kernel_unmapped_at_usr(void)
> +{
> +return false;
> +}
> diff --git a/arch/arm/xen/enlighten.c b/arch/arm/xen/enlighten.c
> index e93145d72c26..ea76562af1e9 100644
> --- a/arch/arm/xen/enlighten.c
> +++ b/arch/arm/xen/enlighten.c
> @@ -158,7 +158,8 @@ static int xen_starting_cpu(unsigned int cpu)
> BUG_ON(err);
> per_cpu(xen_vcpu, cpu) = vcpup;
>
> -xen_setup_runstate_info(cpu);
> +if (!xen_kernel_unmapped_at_usr())
> +xen_setup_runstate_info(cpu);
>
> after_register_vcpu_info:
> enable_percpu_irq(xen_events_irq, 0);
> @@ -387,7 +388,8 @@ static int __init xen_guest_init(void)
> return -EINVAL;
> }
>
> -xen_time_setup_guest();
> +if (!xen_kernel_unmapped_at_usr())
> +xen_time_setup_guest();
>
> if (xen_initial_domain())
> pvclock_gtod_register_notifier(&xen_pvclock_gtod_notifier);
> diff --git a/arch/arm64/include/asm/xen/page.h b/arch/arm64/include/asm/xen/page.h
> index 31bbc803cecb..dffdc773221b 100644
> --- a/arch/arm64/include/asm/xen/page.h
> +++ b/arch/arm64/include/asm/xen/page.h
> @@ -1 +1,7 @@
> #include <xen/arm/page.h>
> +#include <asm/mmu.h>
> +
> +static inline bool xen_kernel_unmapped_at_usr(void)
> +{
> +return arm64_kernel_unmapped_at_el0();
> +}
> --
> 2.17.1
>

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.

  reply	other threads:[~2020-09-25 15:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-24 23:49 Stefano Stabellini
2020-09-25 15:08 ` Bertrand Marquis [this message]
2020-09-30 14:13 ` boris.ostrovsky

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=F3D30F3F-7AEF-43A0-8A2D-A55AA570C3C8@arm.com \
    --to=bertrand.marquis@arm.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=jgross@suse.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sstabellini@kernel.org \
    --cc=stefano.stabellini@xilinx.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®