All of lore.kernel.org
 help / color / mirror / Atom feed
From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Julien Grall <julien.grall@arm.com>, xen-devel@lists.xen.org
Cc: jgross@suse.com, Feng Kan <fkan@apm.com>,
	sstabellini@kernel.org, linux-kernel@vger.kernel.org,
	stable@vger.kernel.org
Subject: Re: [PATCH] xen/privcmd: Support correctly 64KB page granularity when mapping memory
Date: Wed, 31 May 2017 09:54:43 -0400	[thread overview]
Message-ID: <7199e366-f56a-acc8-ffa5-0c85d6975049__40014.8824010559$1496238962$gmane$org@oracle.com> (raw)
In-Reply-To: <20170531130357.14492-1-julien.grall@arm.com>

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()?

-boris

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

  parent reply	other threads:[~2017-05-31 13:54 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-31 13:03 [PATCH] xen/privcmd: Support correctly 64KB page granularity when mapping memory Julien Grall
2017-05-31 13:54 ` Boris Ostrovsky
2017-06-01 12:50   ` Julien Grall
2017-06-01 13:33     ` Boris Ostrovsky
2017-06-01 13:33     ` Boris Ostrovsky
2017-06-01 14:01       ` Julien Grall
2017-06-01 15:16         ` Boris Ostrovsky
2017-06-01 15:38           ` Julien Grall
2017-06-01 15:38           ` Julien Grall
2017-06-01 20:41             ` Boris Ostrovsky
2017-06-01 21:04               ` Julien Grall
2017-06-01 21:04               ` Julien Grall
2017-06-06 16:17               ` Julien Grall
2017-06-06 16:17               ` Julien Grall
2017-06-01 20:41             ` Boris Ostrovsky
2017-06-01 15:16         ` Boris Ostrovsky
2017-06-01 14:01       ` Julien Grall
2017-06-01 12:50   ` Julien Grall
2017-05-31 13:54 ` Boris Ostrovsky [this message]
2017-06-07  9:25 ` Juergen Gross
2017-06-07  9:25 ` Juergen Gross
2017-05-31 13:03 Julien Grall

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='7199e366-f56a-acc8-ffa5-0c85d6975049__40014.8824010559$1496238962$gmane$org@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.