From: Ingo Molnar <mingo@kernel.org>
To: Juergen Gross <jgross@suse.com>
Cc: linux-kernel@vger.kernel.org, xen-devel@lists.xenproject.org,
x86@kernel.org, hpa@zytor.com, tglx@linutronix.de,
mingo@redhat.com, Boris Ostrovsky <boris.ostrovsky@oracle.com>
Subject: Re: [PATCH v2 0/3] fix xen hvm guest with kaslr enabled
Date: Fri, 11 Aug 2017 14:51:07 +0200 [thread overview]
Message-ID: <20170811125107.f5nflg2bffalg6hf@gmail.com> (raw)
In-Reply-To: <99bef8e4-34f3-54dc-5790-7fa2db4e3787@suse.com>
* Juergen Gross <jgross@suse.com> wrote:
> On 08/08/17 16:00, Boris Ostrovsky wrote:
> > On 08/08/2017 02:46 AM, Juergen Gross wrote:
> >> On 28/07/17 12:23, Juergen Gross wrote:
> >>> 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(-)
> >>>
> >> Could I have some feedback, please?
> >>
> >> I'd like to get this regression fixed in 4.13.
> >>
> >> In case nobody objects this week I'll just add the patches to the Xen
> >> tree for rc5.
> >
> >
> > As I said before I think .init_mem_mapping() could live in
> > x86_platform_ops() but this works too, so
> >
> > Reviewed-by: Boris Ostrovsky <boris.ostrovsky@oracle.com>
> >
> > But this still wants x86 maintainers' ACK.
>
> x86 maintainers, could you please comment on at least patch 1?
LGTM:
Acked-by: Ingo Molnar <mingo@kernel.org>
Thanks,
Ingo
prev parent reply other threads:[~2017-08-11 12:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-28 10:23 Juergen Gross
2017-07-28 10:23 ` [PATCH v2 1/3] x86: provide an init_mem_mapping hypervisor hook 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 ` [PATCH v2 3/3] xen: fix hvm guest with kaslr enabled Juergen Gross
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-11 10:00 ` Juergen Gross
2017-08-11 12:51 ` Ingo Molnar [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=20170811125107.f5nflg2bffalg6hf@gmail.com \
--to=mingo@kernel.org \
--cc=boris.ostrovsky@oracle.com \
--cc=hpa@zytor.com \
--cc=jgross@suse.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome