[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.02.1507161815350.17378@kaball.uk.xensource.com>
Date: Thu, 16 Jul 2015 18:16:32 +0100
From: Stefano Stabellini <stefano.stabellini@...citrix.com>
To: Stefano Stabellini <stefano.stabellini@...citrix.com>
CC: Julien Grall <julien.grall@...rix.com>,
<xen-devel@...ts.xenproject.org>,
<linux-arm-kernel@...ts.infradead.org>, <ian.campbell@...rix.com>,
<linux-kernel@...r.kernel.org>,
Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>,
Boris Ostrovsky <boris.ostrovsky@...cle.com>,
"David Vrabel" <david.vrabel@...rix.com>
Subject: Re: [PATCH v2 19/20] xen/privcmd: Add support for Linux 64KB page
granularity
On Thu, 16 Jul 2015, Stefano Stabellini wrote:
> > + /* setup_hparams guarantees ret == 0 */
> > + BUG_ON(xen_apply_to_page(page, setup_hparams, info));
> > +
> > + set_xen_guest_handle(xatp.idxs, info->h_idxs);
> > + set_xen_guest_handle(xatp.gpfns, info->h_gpfns);
> > + set_xen_guest_handle(xatp.errs, info->h_errs);
> > + xatp.size = info->h_iter;
> > +
> > + rc = HYPERVISOR_memory_op(XENMEM_add_to_physmap_range, &xatp);
>
> I would have thought that XENMEM_add_to_physmap_range operates at 4K
> granularity, regardless of how the guest decides to layout its
> pagetables. If so, the call to XENMEM_add_to_physmap_range needs to be
> moved within the function passed to xen_apply_to_page.
Sorry, this comment is wrong, please ignore it. The others are OK.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists