From: Ingo Molnar <mingo@kernel.org>
To: Boris Ostrovsky <boris.ostrovsky@oracle.com>
Cc: Denys Vlasenko <dvlasenk@redhat.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Josh Poimboeuf <jpoimboe@redhat.com>,
matt@codeblueprint.co.uk, Brian Gerst <brgerst@gmail.com>,
x86@kernel.org, linux-kernel@vger.kernel.org, mingo@redhat.com,
Borislav Petkov <bp@alien8.de>, Andy Lutomirski <luto@kernel.org>,
hpa@zytor.com, xen-devel@lists.xenproject.org,
tglx@linutronix.de,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH] x86/head: Refactor 32-bit pgtable setup
Date: Sun, 18 Dec 2016 09:44:57 +0100 [thread overview]
Message-ID: <20161218084457.GA19538@gmail.com> (raw)
In-Reply-To: <17b4298e-f073-d323-3a3f-1974ed3ec62f@oracle.com>
* Boris Ostrovsky <boris.ostrovsky@oracle.com> wrote:
> On 12/08/2016 11:33 PM, Ingo Molnar wrote:
> > * Boris Ostrovsky <boris.ostrovsky@oracle.com> wrote:
> >
> >> The new Xen PVH entry point requires page tables to be setup by the
> >> kernel since it is entered with paging disabled.
> >>
> >> Pull the common code out of head_32.S so that mk_early_pgtbl_32 can be
> >> invoked from both the new Xen entry point and the existing startup_32
> >> code.
> >>
> >> Convert resulting common code to C.
> >>
> >> Signed-off-by: Boris Ostrovsky <boris.ostrovsky@oracle.com>
> >> ---
> >> This is replacement for https://lkml.org/lkml/2016/10/14/434, with
> >> assembly code re-written in C as requested by Ingo.
> >>
> >>
> >> arch/x86/include/asm/pgtable_32.h | 32 ++++++++++
> >> arch/x86/kernel/head32.c | 62 +++++++++++++++++++
> >> arch/x86/kernel/head_32.S | 122 +++-----------------------------------
> >> 3 files changed, 101 insertions(+), 115 deletions(-)
> > Whee, I love it! And the code is so much more readable!
> >
> > Did you have any particular robustness problems (difficult to resolve crashes)
> > while developing it, or was it reasonably straightforward to do?
>
> There was nothing particularly difficult beyond understanding current
> code. That, of course, is not to say that there were no crashes but
> developing this on a guest gives you pretty good insight into why/where
> you crashed.
>
> This was tested on bare-metal (in case you are wondering), but obviously
> more testing is always good.
Ok, cool!
Would you like to carry this with your other Xen dependencies? If yes:
Acked-by: Ingo Molnar <mingo@kernel.org>
If not then I can pick it up and get it to Linus in v4.10.
Thanks,
Ingo
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-12-18 8:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1481215471-9639-1-git-send-email-boris.ostrovsky@oracle.com>
2016-12-09 4:33 ` [PATCH] x86/head: Refactor 32-bit pgtable setup Ingo Molnar
[not found] ` <20161209043347.GB2595@gmail.com>
2016-12-09 14:33 ` Boris Ostrovsky
[not found] ` <17b4298e-f073-d323-3a3f-1974ed3ec62f@oracle.com>
2016-12-18 8:44 ` Ingo Molnar [this message]
2016-12-19 14:09 ` Boris Ostrovsky
2017-01-05 8:52 ` Ingo Molnar
2017-01-05 14:17 ` Boris Ostrovsky
2017-01-05 20:12 ` [PATCH] x86/boot/32: Convert the 32-bit pgtable setup code from assembly to C kbuild test robot
2016-12-08 16:44 [PATCH] x86/head: Refactor 32-bit pgtable setup 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=20161218084457.GA19538@gmail.com \
--to=mingo@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=boris.ostrovsky@oracle.com \
--cc=bp@alien8.de \
--cc=brgerst@gmail.com \
--cc=dvlasenk@redhat.com \
--cc=hpa@zytor.com \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=matt@codeblueprint.co.uk \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--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;
as well as URLs for NNTP newsgroup(s).