From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Julien Grall <julien.grall@arm.com>, xen-devel@lists.xen.org
Cc: sstabellini@kernel.org, jgross@suse.com,
linux-kernel@vger.kernel.org, stable@vger.kernel.org,
Feng Kan <fkan@apm.com>
Subject: Re: [PATCH] xen/privcmd: Support correctly 64KB page granularity when mapping memory
Date: Thu, 1 Jun 2017 09:33:52 -0400 [thread overview]
Message-ID: <c93f773f-dcfe-17ac-b6fc-1fc701d5abbe@oracle.com> (raw)
In-Reply-To: <592886a8-1443-6475-e318-85cb9acecead@arm.com>
On 06/01/2017 08:50 AM, Julien Grall wrote:
> Hi Boris,
>
> On 31/05/17 14:54, Boris Ostrovsky wrote:
>> On 05/31/2017 09:03 AM, Julien Grall wrote:
>>> Commit 5995a68 "xen/privcmd: Add support for Linux 64KB page
>>> granularity" did
>>> not go far enough to support 64KB in mmap_batch_fn.
>>>
>>> The variable 'nr' is the number of 4KB chunk to map. However, when
>>> Linux
>>> is using 64KB page granularity the array of pages
>>> (vma->vm_private_data)
>>> contain one page per 64KB. Fix it by incrementing st->index correctly.
>>>
>>> Furthermore, st->va is not correctly incremented as PAGE_SIZE !=
>>> XEN_PAGE_SIZE.
>>>
>>> Fixes: 5995a68 ("xen/privcmd: Add support for Linux 64KB page
>>> granularity")
>>> CC: stable@vger.kernel.org
>>> Reported-by: Feng Kan <fkan@apm.com>
>>> Signed-off-by: Julien Grall <julien.grall@arm.com>
>>> ---
>>> drivers/xen/privcmd.c | 4 ++--
>>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>>
>>> diff --git a/drivers/xen/privcmd.c b/drivers/xen/privcmd.c
>>> index 7a92a5e1d40c..feca75b07fdd 100644
>>> --- a/drivers/xen/privcmd.c
>>> +++ b/drivers/xen/privcmd.c
>>> @@ -362,8 +362,8 @@ static int mmap_batch_fn(void *data, int nr,
>>> void *state)
>>> st->global_error = 1;
>>> }
>>> }
>>> - st->va += PAGE_SIZE * nr;
>>> - st->index += nr;
>>> + st->va += XEN_PAGE_SIZE * nr;
>>> + st->index += nr / XEN_PFN_PER_PAGE;
>>>
>>> return 0;
>>> }
>>
>>
>> Are we still using PAGE_MASK for xen_remap_domain_gfn_array()?
>
> Do you mean in the xen_xlate_remap_gfn_array implementation? If so
> there are no use of PAGE_MASK as the code has been converted to
> support 64K page granularity.
>
> If you mean the x86 version of xen_remap_domain_gfn_array, then we
> don't really care as x86 only use 4KB page granularity.
I meant right above the change that you made. Should it also be replaced
with XEN_PAGE_MASK? (Sorry for being unclear.)
==> ret = xen_remap_domain_gfn_array(st->vma, st->va & PAGE_MASK,
gfnp, nr,
(int *)gfnp, st->vma->vm_page_prot,
st->domain, cur_pages);
/* Adjust the global_error? */
if (ret != nr) {
if (ret == -ENOENT)
st->global_error = -ENOENT;
else {
/* Record that at least one error has happened. */
if (st->global_error == 0)
st->global_error = 1;
}
}
st->va += PAGE_SIZE * nr;
st->index += nr;
next prev parent reply other threads:[~2017-06-01 13:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-31 13:03 Julien Grall
2017-05-31 13:54 ` Boris Ostrovsky
2017-06-01 12:50 ` Julien Grall
2017-06-01 13:33 ` Boris Ostrovsky [this message]
2017-06-01 14:01 ` Julien Grall
2017-06-01 15:16 ` Boris Ostrovsky
2017-06-01 15:38 ` Julien Grall
2017-06-01 20:41 ` Boris Ostrovsky
2017-06-01 21:04 ` Julien Grall
2017-06-06 16:17 ` Julien Grall
2017-06-07 9:25 ` 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=c93f773f-dcfe-17ac-b6fc-1fc701d5abbe@oracle.com \
--to=boris.ostrovsky@oracle.com \
--cc=fkan@apm.com \
--cc=jgross@suse.com \
--cc=julien.grall@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sstabellini@kernel.org \
--cc=stable@vger.kernel.org \
--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
all inboxes | Powered by JetHome®