xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Wei Liu <wei.liu2@citrix.com>
To: Juergen Gross <jgross@suse.com>
Cc: Wei Liu <wei.liu2@citrix.com>,
	Ian.Campbell@citrix.com, stefano.stabellini@eu.citrix.com,
	andrew.cooper3@citrix.com, ian.jackson@eu.citrix.com,
	xen-devel@lists.xen.org
Subject: Re: [PATCH v3 2/4] libxc: support of linear p2m list for migration of pv-domains
Date: Thu, 7 Jan 2016 10:33:50 +0000	[thread overview]
Message-ID: <20160107103350.GU27789@citrix.com> (raw)
In-Reply-To: <568E3C10.5040305@suse.com>

On Thu, Jan 07, 2016 at 11:21:04AM +0100, Juergen Gross wrote:
> On 06/01/16 16:40, Wei Liu wrote:
> > On Wed, Dec 16, 2015 at 10:24:18AM +0100, Juergen Gross wrote:
> > [...]
> >> @@ -698,21 +868,19 @@ static int normalise_pagetable(struct xc_sr_context *ctx, const uint64_t *src,
> >>              /* 32bit guests can only use the first 4 entries of their L3 tables.
> >>               * All other are potentially used by Xen. */
> >>              xen_first = 4;
> >> -            xen_last = 512;
> >> +            xen_last = 511;
> > 
> > Is this a bug fix in its own right?
> 
> Hmm, bug fix is too much. It is a harmonization with the change below
> using macros to set xen_last to 511 at maximum. In fact it doesn't
> matter, because xen_last is used in:
> 
>    if ( i >= xen_first && i <= xen_last )
> 
> with i being in the range from 0 to 511.
> 

Yes, that's what I was thinking. There seemed to be an off-by-one error
in the code. But as you said, i is within [0,511] so the code is fine.

Could you add a words or two about this hunk in commit message please.

With that:

Reviewed-by: Wei Liu <wei.liu2@citrix.com>

Wei.

> 
> Juergen
> 
> > 
> > Wei.
> > 
> >>              break;
> >>  
> >>          case XEN_DOMCTL_PFINFO_L2TAB:
> >>              /* It is hard to spot Xen mappings in a 32bit guest's L2.  Most
> >>               * are normal but only a few will have Xen mappings.
> >> -             *
> >> -             * 428 = (HYPERVISOR_VIRT_START_PAE >> L2_PAGETABLE_SHIFT_PAE)&0x1ff
> >> -             *
> >> -             * ...which is conveniently unavailable to us in a 64bit build.
> >>               */
> >> -            if ( pte_to_frame(src[428]) == ctx->x86_pv.compat_m2p_mfn0 )
> >> +            i = (HYPERVISOR_VIRT_START_X86_32 >> L2_PAGETABLE_SHIFT_PAE) & 511;
> >> +            if ( pte_to_frame(src[i]) == ctx->x86_pv.compat_m2p_mfn0 )
> >>              {
> >> -                xen_first = 428;
> >> -                xen_last = 512;
> >> +                xen_first = i;
> >> +                xen_last = (HYPERVISOR_VIRT_END_X86_32 >>
> >> +                            L2_PAGETABLE_SHIFT_PAE) & 511;
> >>              }
> >>              break;
> >>          }
> >> -- 
> >> 2.6.2
> >>
> > 
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@lists.xen.org
> > http://lists.xen.org/xen-devel
> > 
> 

  reply	other threads:[~2016-01-07 10:33 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-16  9:24 [PATCH v3 0/4] support linear p2m list in migrate stream v2 Juergen Gross
2015-12-16  9:24 ` [PATCH v3 1/4] libxc: split mapping p2m leaves into a separate function Juergen Gross
2016-01-06 15:39   ` Wei Liu
2015-12-16  9:24 ` [PATCH v3 2/4] libxc: support of linear p2m list for migration of pv-domains Juergen Gross
2016-01-06 15:40   ` Wei Liu
2016-01-07 10:21     ` Juergen Gross
2016-01-07 10:33       ` Wei Liu [this message]
2016-01-07 10:37         ` Juergen Gross
2015-12-16  9:24 ` [PATCH v3 3/4] libxc: stop migration in case of p2m list structural changes Juergen Gross
2016-01-06 15:40   ` Wei Liu
2015-12-16  9:24 ` [PATCH v3 4/4] libxc: set flag for support of linear p2m list in domain builder Juergen Gross
2016-01-06 15:40   ` Wei Liu
2016-01-06 16:05   ` Ian Campbell
2016-01-07  7:02     ` Juergen Gross

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=20160107103350.GU27789@citrix.com \
    --to=wei.liu2@citrix.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=jgross@suse.com \
    --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;
as well as URLs for NNTP newsgroup(s).