xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Joao Martins <joao.m.martins@oracle.com>
To: Oleksandr Grytsov <al1img@gmail.com>
Cc: Ian Jackson <ian.jackson@eu.citrix.com>,
	Wei Liu <wei.liu2@citrix.com>,
	Xen Development List <xen-devel@lists.xen.org>
Subject: Re: [PATCH RFC 3/8] libxl: add backend_features to libxl_device_disk
Date: Tue, 7 Nov 2017 11:48:53 +0000	[thread overview]
Message-ID: <94340ebd-5c0f-a707-6e75-a388d29acc97@oracle.com> (raw)
In-Reply-To: <CACvf2oVFrKrd0FOa4UWfJCTkWRYunDFDhHAO06TNwkx1krKFxA@mail.gmail.com>



On 11/07/2017 11:28 AM, Oleksandr Grytsov wrote:
> On Thu, Nov 2, 2017 at 8:06 PM, Joao Martins <joao.m.martins@oracle.com
> <mailto:joao.m.martins@oracle.com>> wrote:
> 
>     The function libxl__device_generic_add will have an additional
>     argument whereby it adds a second set of entries visible to the
>     backend only. These entries will then be used for devices
>     thus overriding backend maximum feature set with this user-defined ones.
> 
>     libxl_device_disk.backend_features are a key value store storing:
>      <feature-name> = <feature-value>
> 
>     xl|libxl are stateless with respect to feature names therefore is up to the
>     admin to carefully select those. If backend isn't supported therefore the
>     features won't be overwritten.
> 
>     Signed-off-by: Joao Martins <joao.m.martins@oracle.com
>     <mailto:joao.m.martins@oracle.com>>
>     ---
>      tools/libxl/libxl.h          |  8 ++++++++
>      tools/libxl/libxl_console.c  |  5 +++--
>      tools/libxl/libxl_device.c   | 37 +++++++++++++++++++++++++++++++++----
>      tools/libxl/libxl_disk.c     | 17 +++++++++++++++--
>      tools/libxl/libxl_internal.h |  4 +++-
>      tools/libxl/libxl_pci.c      |  2 +-
>      tools/libxl/libxl_types.idl  |  1 +
>      tools/libxl/libxl_usb.c      |  2 +-
>      8 files changed, 65 insertions(+), 11 deletions(-)
> 
> 
> No need to extend libxl__device_generic_add with additional parameter (brents).
> You can add nested entry in libxl__set_xenstore_<device> as following:
> 
> flexarray_append(back, "require/feature-persistent", "0");

Right, although entries on "back" array will have readonly permission to the
frontend. And these newly added "require" directory in this RFC was meant to be
only visible to the backend, hence only having XS_PERM_NONE permission set.

Joao

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

  reply	other threads:[~2017-11-07 11:48 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-02 18:06 [PATCH RFC 0/8] libxl, xl, public/io: PV backends feature control Joao Martins
2017-11-02 18:06 ` [PATCH RFC 1/8] public/io/blkif: add directory for backend parameters Joao Martins
2018-02-07 11:36   ` Roger Pau Monné
2017-11-02 18:06 ` [PATCH RFC 2/8] public/io/netif: " Joao Martins
2017-11-06 10:33   ` Paul Durrant
2017-11-06 12:33     ` Joao Martins
2018-02-06 17:12       ` Wei Liu
2018-02-07 12:10         ` Joao Martins
2018-02-08 11:13           ` Wei Liu
2018-02-08 13:51             ` Joao Martins
2018-02-13 11:33               ` Wei Liu
2017-11-02 18:06 ` [PATCH RFC 3/8] libxl: add backend_features to libxl_device_disk Joao Martins
2017-11-07 11:28   ` Oleksandr Grytsov
2017-11-07 11:48     ` Joao Martins [this message]
2017-11-02 18:06 ` [PATCH RFC 4/8] libxl: add backend_features to libxl_device_nic Joao Martins
2017-11-02 18:06 ` [PATCH RFC 5/8] libxlu: parse disk backend features parameters Joao Martins
2017-11-02 18:06 ` [PATCH RFC 6/8] xl: parse vif " Joao Martins
2017-11-02 18:06 ` [PATCH RFC 7/8] xen-blkback: frontend feature control Joao Martins
2018-02-07 12:08   ` Roger Pau Monné
2018-02-07 14:16     ` Joao Martins
2018-02-07 14:24       ` Roger Pau Monné
2017-11-02 18:06 ` [PATCH RFC 8/8] xen-netback: " Joao Martins
2018-02-07 11:16 ` [PATCH RFC 0/8] libxl, xl, public/io: PV backends " Roger Pau Monné
2018-02-07 11:20   ` Juergen Gross
2018-02-07 11:30     ` Roger Pau Monné
2018-02-07 11:36       ` Joao Martins
2018-02-07 11:44       ` Joao Martins
2018-02-07 12:03   ` Joao Martins

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=94340ebd-5c0f-a707-6e75-a388d29acc97@oracle.com \
    --to=joao.m.martins@oracle.com \
    --cc=al1img@gmail.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=wei.liu2@citrix.com \
    --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;
as well as URLs for NNTP newsgroup(s).