LKML Archive on lore.kernel.org help / color / mirror / Atom feed
From: Paul Durrant <Paul.Durrant@citrix.com> To: "'Julien Grall'" <julien.grall@arm.com>, "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>, "linux-arm-kernel@lists.infradead.org" <linux-arm-kernel@lists.infradead.org>, "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org> Cc: Juergen Gross <jgross@suse.com>, Thomas Gleixner <tglx@linutronix.de>, Stefano Stabellini <sstabellini@kernel.org>, Ingo Molnar <mingo@redhat.com> Subject: RE: [PATCH v4] xen/privcmd: add IOCTL_PRIVCMD_MMAP_RESOURCE Date: Wed, 11 Apr 2018 09:50:25 +0000 [thread overview] Message-ID: <68f3d9b993d644e8ab137ccecceb575c@AMSPEX02CL03.citrite.net> (raw) In-Reply-To: <8fff31d5-7eb4-33e8-0fc8-c5bb1ab47eba@arm.com> > -----Original Message----- > From: Julien Grall [mailto:julien.grall@arm.com] > Sent: 11 April 2018 10:46 > To: Paul Durrant <Paul.Durrant@citrix.com>; xen-devel@lists.xenproject.org; > linux-arm-kernel@lists.infradead.org; linux-kernel@vger.kernel.org > Cc: Juergen Gross <jgross@suse.com>; Thomas Gleixner > <tglx@linutronix.de>; Stefano Stabellini <sstabellini@kernel.org>; Ingo > Molnar <mingo@redhat.com> > Subject: Re: [PATCH v4] xen/privcmd: add > IOCTL_PRIVCMD_MMAP_RESOURCE > > Hi, > > On 10/04/18 08:58, Paul Durrant wrote: > > +static long privcmd_ioctl_mmap_resource(struct file *file, void __user > *udata) > > +{ > > + struct privcmd_data *data = file->private_data; > > + struct mm_struct *mm = current->mm; > > + struct vm_area_struct *vma; > > + struct privcmd_mmap_resource kdata; > > + xen_pfn_t *pfns = NULL; > > + struct xen_mem_acquire_resource xdata; > > + int rc; > > + > > + if (copy_from_user(&kdata, udata, sizeof(kdata))) > > + return -EFAULT; > > + > > + /* If restriction is in place, check the domid matches */ > > + if (data->domid != DOMID_INVALID && data->domid != kdata.dom) > > + return -EPERM; > > + > > + down_write(&mm->mmap_sem); > > + > > + vma = find_vma(mm, kdata.addr); > > + if (!vma || vma->vm_ops != &privcmd_vm_ops) { > > + rc = -EINVAL; > > + goto out; > > + } > > + > > + pfns = kcalloc(kdata.num, sizeof(*pfns), GFP_KERNEL); > > + if (!pfns) { > > + rc = -ENOMEM; > > + goto out; > > + } > > + > > + if (xen_feature(XENFEAT_auto_translated_physmap)) { > > + struct page **pages; > > + unsigned int i; > > + > > + rc = alloc_empty_pages(vma, kdata.num); > > + if (rc < 0) > > + goto out; > > + > > + pages = vma->vm_private_data; > > + for (i = 0; i < kdata.num; i++) > > + pfns[i] = page_to_pfn(pages[i]); > > I don't think this is going to work well if the hypervisor is using a > different granularity for the page. > > Imagine Xen is using 4K but the kernel 64K. You would end up to have the > resource not mapped contiguously in the memory. Good point. I do need to take account of the kernel page size in this case. Paul > > Cheers, > > -- > Julien Grall
prev parent reply other threads:[~2018-04-11 9:50 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-04-10 7:58 [PATCH v4] xen/privcmd: add IOCTL_PRIVCMD_MMAP_RESOURCE Paul Durrant 2018-04-11 9:45 ` Julien Grall 2018-04-11 9:50 ` Paul Durrant [this message]
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=68f3d9b993d644e8ab137ccecceb575c@AMSPEX02CL03.citrite.net \ --to=paul.durrant@citrix.com \ --cc=jgross@suse.com \ --cc=julien.grall@arm.com \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=mingo@redhat.com \ --cc=sstabellini@kernel.org \ --cc=tglx@linutronix.de \ --cc=xen-devel@lists.xenproject.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: linkBe 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).