From: Juergen Gross <jgross@suse.com>
To: linux-kernel@vger.kernel.org, xen-devel@lists.xenproject.org,
x86@kernel.org
Cc: boris.ostrovsky@oracle.com, hpa@zytor.com, tglx@linutronix.de,
mingo@redhat.com, Juergen Gross <jgross@suse.com>
Subject: [PATCH v2 0/3] fix xen hvm guest with kaslr enabled
Date: Fri, 28 Jul 2017 12:23:11 +0200 [thread overview]
Message-ID: <20170728102314.29100-1-jgross@suse.com> (raw)
This patch series fixes a regression introduced in 4.13-rc1: A Xen
HVM guest with KASLR enabled wouldn't boot any longer due to the usage
of __va() before kernel_randomize_memory() was called.
Changes in V2:
- patch 1: test for x86_hyper being not NULL
Juergen Gross (3):
x86: provide an init_mem_mapping hypervisor hook
xen: split up xen_hvm_init_shared_info()
xen: fix hvm guest with kaslr enabled
arch/x86/include/asm/hypervisor.h | 10 +++++++
arch/x86/mm/init.c | 3 ++
arch/x86/xen/enlighten_hvm.c | 59 ++++++++++++++++++++++++---------------
3 files changed, 50 insertions(+), 22 deletions(-)
--
2.12.3
next reply other threads:[~2017-07-28 10:23 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-28 10:23 Juergen Gross [this message]
2017-07-28 10:23 ` [PATCH v2 1/3] x86: provide an init_mem_mapping hypervisor hook Juergen Gross
2017-07-28 10:23 ` Juergen Gross
2017-07-28 10:23 ` [PATCH v2 2/3] xen: split up xen_hvm_init_shared_info() Juergen Gross
2017-07-28 10:23 ` Juergen Gross
2017-07-28 10:23 ` [PATCH v2 3/3] xen: fix hvm guest with kaslr enabled Juergen Gross
2017-07-28 10:23 ` Juergen Gross
2017-08-08 10:03 ` Andrew Cooper
2017-08-08 10:03 ` [Xen-devel] " Andrew Cooper
2017-08-08 6:46 ` [PATCH v2 0/3] fix xen " Juergen Gross
2017-08-08 14:00 ` Boris Ostrovsky
2017-08-08 14:00 ` Boris Ostrovsky
2017-08-11 10:00 ` Juergen Gross
2017-08-11 10:00 ` Juergen Gross
2017-08-11 12:51 ` Ingo Molnar
2017-08-11 12:51 ` Ingo Molnar
2017-08-08 6:46 ` Juergen Gross
-- strict thread matches above, loose matches on Subject: below --
2017-07-28 10:23 Juergen Gross
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=20170728102314.29100-1-jgross@suse.com \
--to=jgross@suse.com \
--cc=boris.ostrovsky@oracle.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=xen-devel@lists.xenproject.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 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.