mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jan Beulich" <JBeulich@suse.com>
To: "Stefano Stabellini" <stefano.stabellini@eu.citrix.com>
Cc: "xen-devel" <xen-devel@lists.xen.org>,
	"Konrad Rzeszutek Wilk" <konrad.wilk@oracle.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [Xen-devel] [PATCH 5/7] xen/p2m: Add logic to revector a P2M tree to use __va leafs.
Date: Fri, 27 Jul 2012 12:47:47 +0100	[thread overview]
Message-ID: <50129C030200007800090F9B@nat28.tlf.novell.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1207271215540.26163@kaball.uk.xensource.com>

>>> On 27.07.12 at 13:18, Stefano Stabellini <stefano.stabellini@eu.citrix.com> wrote:
> On Thu, 26 Jul 2012, Konrad Rzeszutek Wilk wrote:
>>  1) All P2M lookups instead of using the __ka address would
>>     use the __va address. This means we can safely erase from
>>     __ka space the PMD pointers that point to the PFNs for
>>     P2M array and be OK.
>>  2). Allocate a new array, copy the existing P2M into it,
>>     revector the P2M tree to use that, and return the old
>>     P2M to the memory allocate. This has the advantage that
>>     it sets the stage for using XEN_ELF_NOTE_INIT_P2M
>>     feature. That feature allows us to set the exact virtual
>>     address space we want for the P2M - and allows us to
>>     boot as initial domain on large machines.
>> 
>> So we pick option 2).
> 
> 1) looks like a decent option that requires less code.
> Is the problem with 1) that we might want to access the P2M before we
> have __va addresses ready?

AIUI 1) has no easy way of subsequently accommodating support
for XEN_ELF_NOTE_INIT_P2M (where you almost definitely will
want/need to reclaim the originally used VA space - if nothing else,
then for forward compatibility with the rest of the kernel).

Jan


  reply	other threads:[~2012-07-27 11:47 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-26 20:47 [RFC PATCH] Boot PV guests with more than 128GB (v1) for 3.7 Konrad Rzeszutek Wilk
2012-07-26 20:47 ` [PATCH 1/7] xen/mmu: use copy_page instead of memcpy Konrad Rzeszutek Wilk
2012-07-27  7:35   ` [Xen-devel] " Jan Beulich
2012-07-26 20:47 ` [PATCH 2/7] xen/mmu: For 64-bit do not call xen_map_identity_early Konrad Rzeszutek Wilk
2012-07-26 20:47 ` [PATCH 3/7] xen/mmu: Release the Xen provided L4 (PGD) back Konrad Rzeszutek Wilk
2012-07-27 11:37   ` [Xen-devel] " Stefano Stabellini
2012-07-27 17:35     ` Konrad Rzeszutek Wilk
2012-07-26 20:47 ` [PATCH 4/7] xen/mmu: Recycle the Xen provided L4, L3, and L2 pages Konrad Rzeszutek Wilk
2012-07-27 11:45   ` [Xen-devel] " Stefano Stabellini
2012-07-27 17:38     ` Konrad Rzeszutek Wilk
2012-07-31 14:39       ` Konrad Rzeszutek Wilk
2012-07-26 20:47 ` [PATCH 5/7] xen/p2m: Add logic to revector a P2M tree to use __va leafs Konrad Rzeszutek Wilk
2012-07-27 11:18   ` [Xen-devel] " Stefano Stabellini
2012-07-27 11:47     ` Jan Beulich [this message]
2012-07-27 17:34       ` Konrad Rzeszutek Wilk
2012-07-30  7:10         ` Jan Beulich
2012-07-26 20:47 ` [PATCH 6/7] xen/mmu: Copy and revector the P2M tree Konrad Rzeszutek Wilk
2012-07-26 20:47 ` [PATCH 7/7] xen/mmu: Remove from __ka space PMD entries for pagetables Konrad Rzeszutek Wilk
2012-07-27 11:31   ` [Xen-devel] " Stefano Stabellini
2012-07-27 17:42     ` Konrad Rzeszutek Wilk
2012-07-31 14:37       ` Konrad Rzeszutek Wilk
2012-07-27  7:34 ` [Xen-devel] [RFC PATCH] Boot PV guests with more than 128GB (v1) for 3.7 Jan Beulich
2012-07-27 10:00   ` Ian Campbell
2012-07-27 10:17     ` Jan Beulich
2012-07-27 10:21       ` Ian Campbell
2012-07-27 10:33         ` Jan Beulich

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=50129C030200007800090F9B@nat28.tlf.novell.com \
    --to=jbeulich@suse.com \
    --cc=konrad.wilk@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stefano.stabellini@eu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®