From: Ian Campbell <ian.campbell@citrix.com>
To: Samuel Thibault <samuel.thibault@ens-lyon.org>,
Juergen Gross <jgross@suse.com>
Cc: minios-devel@lists.xenproject.org, wei.liu2@citrix.com,
xen-devel@lists.xen.org, ian.jackson@eu.citrix.com,
stefano.stabellini@eu.citrix.com
Subject: Re: [PATCH v3] minios: don't rely on specific page table allocation scheme
Date: Mon, 23 Nov 2015 09:55:53 +0000 [thread overview]
Message-ID: <1448272553.4973.17.camel@citrix.com> (raw)
In-Reply-To: <20151120183929.GD3151@var.home>
On Fri, 2015-11-20 at 19:39 +0100, Samuel Thibault wrote:
> Juergen Gross, on Fri 20 Nov 2015 19:32:42 +0100, wrote:
This patch conflicted with 1855e8b2e884 "mini-os: enable compiler check for
printk format types" which was committed in June.
I have (hopefully correctly) resolved the conflict by simply removing the
entirety of need_pt_frame(), but in the future please base your patches on
something up to date.
> > Today mini-os is making assumptions how the page tables it is started
> > with are being allocated. Especially it is using the number of page
> > table frames to calculate which is the first unmapped pfn.
> >
> > Instead of relying on page table number assumptions just look into the
> > page tables to find the first pfn not already mapped.
> >
> > Signed-off-by: Juergen Gross <jgross@suse.com>
>
> Acked-by: Samuel Thibault <samuel.thibault@ens-lyon.org>
Applied, along with a corresponding update to MINIOS_UPSTREAM_REVISION in
xen.git:Config.mk.
Ian.
prev parent reply other threads:[~2015-11-23 9:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-20 18:32 [PATCH v3] minios: don't rely on specific page table allocation scheme Juergen Gross
2015-11-20 18:39 ` Samuel Thibault
2015-11-23 9:55 ` Ian Campbell [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=1448272553.4973.17.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jgross@suse.com \
--cc=minios-devel@lists.xenproject.org \
--cc=samuel.thibault@ens-lyon.org \
--cc=stefano.stabellini@eu.citrix.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xen.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.