From: Wei Liu <wei.liu2@citrix.com>
To: Juergen Gross <jgross@suse.com>
Cc: xen-devel@lists.xensource.com, Wei Liu <wei.liu2@citrix.com>,
Ian Campbell <ian.campbell@citrix.com>,
osstest service owner <osstest-admin@xenproject.org>
Subject: Re: [xen-unstable test] 64494: regressions - FAIL
Date: Thu, 19 Nov 2015 12:38:48 +0000 [thread overview]
Message-ID: <20151119123848.GT1495@citrix.com> (raw)
In-Reply-To: <564DC08D.7070602@suse.com>
On Thu, Nov 19, 2015 at 01:29:01PM +0100, Juergen Gross wrote:
[...]
> > To be precise, the problem is in mini-os, which is used by rump kernel
> > as well. :-(
> >
> >> pvgrub is making assumptions about the page table allocation scheme
> >> of the toolset starting pvgrub. It is calculating the first not yet
> >> mapped pfn by:
> >>
> >> pfn_to_map =
> >> (start_info.nr_pt_frames - NOT_L1_FRAMES) * L1_PAGETABLE_ENTRIES;
> >>
> >> NOT_L1_FRAMES is 3 for 64 bit and 32 bit:
> >>
> >> 64 bit: 1 level 4 + 1 level 4 + 1 level 2
> >> 32 bit: 1 level 3 + 2 level 2 (assuming level 2 pt are allocated
> >> for the first and the last GB)
> >>
> >> This is wrong now, as for 32 bit I'm allocating all level 2 page
> >> tables from the lowest needed address up to 0xffffffff, resulting
> >> in 4 level 2 page tables in pvgrub case.
> >>
> >> Setting NOT_L1_FRAMES to 5 for 32 bit pvgrub makes the system boot
> >> again.
> >>
> >> I think it is wrong for pvgrub to assume a fixed allocation scheme
> >> of the page tables. The question is how to fix it: either via
> >> changing NOT_L1_FRAMES or by doing it in a clean but more complicated
> >> way.
> >>
> >
> > In the mean time, shall we revert the series and think about this a bit
> > more?
> >
> > How complicated will be clean fix be?
>
> I think I can fix it today. I can just count the not_l1_frames
> dynamically by walking through the higher level page tables. This
This seems sensible.
> will work for 32 and 64 bit and with and without my patch series
> and even for 32 bit mini-os started via grub-xen.
>
> > Does changing NOT_L1_FRAMES break mini-os boot with toolstack prior to
> > your series?
>
> Yes.
>
In that case I think a clean fix is required.
Wei.
> Juergen
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2015-11-19 12:38 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-18 14:31 [xen-unstable test] 64494: regressions - FAIL osstest service owner
2015-11-18 14:49 ` Wei Liu
2015-11-18 15:54 ` Juergen Gross
2015-11-18 15:59 ` Wei Liu
2015-11-18 16:03 ` Juergen Gross
2015-11-19 10:24 ` Juergen Gross
2015-11-19 10:30 ` Ian Campbell
2015-11-19 10:50 ` Wei Liu
2015-11-19 10:55 ` Ian Campbell
2015-11-19 10:56 ` Wei Liu
2015-11-19 10:57 ` Juergen Gross
2015-11-19 11:47 ` Juergen Gross
2015-11-19 12:19 ` Wei Liu
2015-11-19 12:29 ` Juergen Gross
2015-11-19 12:38 ` Wei Liu [this message]
2015-11-20 15:14 ` Jan Beulich
2015-11-20 15:23 ` Wei Liu
[not found] ` <564F46C802000078000B73E9@suse.com>
2015-11-20 15:29 ` Juergen Gross
2015-11-20 15:34 ` Wei Liu
2015-11-20 15:41 ` Andrew Cooper
2015-11-20 15:42 ` Andrew Cooper
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=20151119123848.GT1495@citrix.com \
--to=wei.liu2@citrix.com \
--cc=ian.campbell@citrix.com \
--cc=jgross@suse.com \
--cc=osstest-admin@xenproject.org \
--cc=xen-devel@lists.xensource.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;
as well as URLs for NNTP newsgroup(s).