From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mukesh Rathor Subject: Re: [PATCH v1 2/8]: PVH mmu changes Date: Tue, 25 Sep 2012 17:33:18 -0700 Message-ID: <20120925173318.6c829910@mantra.us.oracle.com> References: <20120921121556.1a0ea8af@mantra.us.oracle.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Stefano Stabellini Cc: "Xen-devel@lists.xensource.com" , Ian Campbell , Konrad Rzeszutek Wilk List-Id: xen-devel@lists.xenproject.org On Mon, 24 Sep 2012 15:04:22 +0100 Stefano Stabellini wrote: > On Fri, 21 Sep 2012, Mukesh Rathor wrote: > > +struct pvh_remap_data { > > struct remap_data { > > @@ -2329,7 +2468,9 @@ static int remap_area_mfn_pte_fn(pte_t *ptep, > > pgtable_t token, int xen_remap_domain_mfn_range(struct > > vm_area_struct *vma, unsigned long addr, > > unsigned long mfn, int nr, > > - pgprot_t prot, unsigned domid) > > + pgprot_t prot, unsigned domid, > > + struct xen_pvh_pfn_info *pvhp) > > + > > xen_remap_domain_mfn_range is a cross-architecture call (it is > available on ARM as well). We cannot leak architecture specific > informations like xen_pvh_pfn_info in the parameter list. > It seems to be that xen_pvh_pfn_info contains arch-agnostic > information: in that case you just need to rename the struct to > something more generic. Otherwise if it really contains x86 specific > info, you can change it into an opaque pointer. Ok, how about I just change it to: - struct xen_pvh_pfn_info *pvhp) + void *arch_spec_info) thanks, Mukesh