The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Paul Durrant <paul.durrant@citrix.com>,
	xen-devel@lists.xenproject.org, linux-kernel@vger.kernel.org
Cc: Juergen Gross <jgross@suse.com>
Subject: Re: [PATCH v3 2/3] xen/privcmd: Add IOCTL_PRIVCMD_DM_OP
Date: Mon, 13 Feb 2017 14:11:02 -0500	[thread overview]
Message-ID: <0ae0162c-4317-7dbf-fdce-354f71583d0a@oracle.com> (raw)
In-Reply-To: <1487005404-3183-3-git-send-email-paul.durrant@citrix.com>



> diff --git a/drivers/xen/privcmd.c b/drivers/xen/privcmd.c
> index 5e5c7ae..a33f17e 100644
> --- a/drivers/xen/privcmd.c
> +++ b/drivers/xen/privcmd.c
> @@ -22,6 +22,7 @@
>  #include <linux/pagemap.h>
>  #include <linux/seq_file.h>
>  #include <linux/miscdevice.h>
> +#include <linux/moduleparam.h>
>
>  #include <asm/pgalloc.h>
>  #include <asm/pgtable.h>
> @@ -32,6 +33,7 @@
>  #include <xen/xen.h>
>  #include <xen/privcmd.h>
>  #include <xen/interface/xen.h>
> +#include <xen/interface/hvm/dm_op.h>
>  #include <xen/features.h>
>  #include <xen/page.h>
>  #include <xen/xen-ops.h>
> @@ -43,6 +45,17 @@ MODULE_LICENSE("GPL");
>
>  #define PRIV_VMA_LOCKED ((void *)1)
>
> +unsigned int privcmd_dm_op_max_num = 16;
> +module_param_named(dm_op_max_nr_bufs, privcmd_dm_op_max_num, uint, 0644);
> +MODULE_PARM_DESC(dm_op_max_nr_bufs,
> +		 "Maximum number of buffers per dm_op hypercall");
> +
> +unsigned int privcmd_dm_op_buf_max_size = XEN_PAGE_SIZE;

These need to be static. (I can fix it when committing.)

And I am still not sure about using XEN_PAGE_SIZE. There is no 
dependency in the hypervisor on buffers being page-sized, is there? If 
not, XEN_PAGE_SIZE is here just because it happens to be 4K, which is a 
reasonable value.

How about just setting it to 4096?


-boris

  reply	other threads:[~2017-02-13 19:11 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-13 17:03 [PATCH v3 0/3] xen/privcmd: support for dm_op and restriction Paul Durrant
2017-02-13 17:03 ` [PATCH v3 1/3] xen/privcmd: return -ENOTTY for unimplemented IOCTLs Paul Durrant
2017-02-13 18:52   ` Boris Ostrovsky
2017-02-13 17:03 ` [PATCH v3 2/3] xen/privcmd: Add IOCTL_PRIVCMD_DM_OP Paul Durrant
2017-02-13 19:11   ` Boris Ostrovsky [this message]
2017-02-14  9:20     ` Paul Durrant
2017-02-14 14:11       ` Boris Ostrovsky
2017-02-14 17:25   ` Boris Ostrovsky
2017-02-14 18:38     ` Stefano Stabellini
2017-02-15  9:14       ` Paul Durrant
2017-02-15 14:47   ` Boris Ostrovsky
2017-02-13 17:03 ` [PATCH v3 3/3] xen/privcmd: add IOCTL_PRIVCMD_RESTRICT Paul Durrant
2017-02-13 19:20   ` Boris Ostrovsky
2017-02-15 14:49   ` Boris Ostrovsky

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=0ae0162c-4317-7dbf-fdce-354f71583d0a@oracle.com \
    --to=boris.ostrovsky@oracle.com \
    --cc=jgross@suse.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paul.durrant@citrix.com \
    --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: 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