mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Konrad Rzeszutek Wilk <konrad@darnok.org>
Cc: Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [Xen-devel] [PATCH 4/7] xen/mmu: Recycle the Xen provided L4, L3, and L2 pages
Date: Tue, 31 Jul 2012 10:39:15 -0400	[thread overview]
Message-ID: <20120731143915.GJ4789@phenom.dumpdata.com> (raw)
In-Reply-To: <20120727173824.GD17427@andromeda.dapyr.net>

> > > +	for (i = 0; i < ARRAY_SIZE(addr); i++) {
> > > +		unsigned j;
> > > +		/* No idea about the order the addr are in, so just do them twice. */
> > > +		for (j = 0; j < ARRAY_SIZE(addr); j++) {
> > 
> > I don't think I understand this double loop.
> 
> So with Xen toolstack, the order is L4, L3, L2, L1s.. and with
> the hypervisor it is L4, L1,... but in the future the order might
> be L1, L1 ..., L1, L2, L3, L4 (potentially?) so this double loop
> will loop around the addresses twice to catch this in case we get
> it like this.

Which we would get in case the toolstack ever decided to put those
pages in L4, L2, L3 order. Since the toolstack puts them in L4, L3, L2
and hypervisor puts it in L4, L1, L3, L2 we might as well just
simplify this and not do the extra loop. Posting patches shortly with
this.

  reply	other threads:[~2012-07-31 14:49 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 [this message]
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
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=20120731143915.GJ4789@phenom.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=konrad@darnok.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stefano.stabellini@eu.citrix.com \
    --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

Powered by JetHome