Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-6.3 required=3.0 tests=DKIM_ADSP_CUSTOM_MED, DKIM_INVALID,DKIM_SIGNED,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_PATCH,MAILING_LIST_MULTI,SIGNED_OFF_BY, SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id B041DC433E0 for ; Wed, 20 May 2020 10:51:14 +0000 (UTC) Received: from lists.xenproject.org (lists.xenproject.org [192.237.175.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 71F7F207D3 for ; Wed, 20 May 2020 10:51:14 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="signature verification failed" (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="diYlybjP" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 71F7F207D3 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=gmail.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=xen-devel-bounces@lists.xenproject.org Received: from localhost ([127.0.0.1] helo=lists.xenproject.org) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1jbMIw-0005Lj-UT; Wed, 20 May 2020 10:50:30 +0000 Received: from us1-rack-iad1.inumbo.com ([172.99.69.81]) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1jbMIv-0005Le-Hu for xen-devel@lists.xenproject.org; Wed, 20 May 2020 10:50:29 +0000 X-Inumbo-ID: b7b326f6-9a87-11ea-ae69-bc764e2007e4 Received: from mail-ej1-x62b.google.com (unknown [2a00:1450:4864:20::62b]) by us1-rack-iad1.inumbo.com (Halon) with ESMTPS id b7b326f6-9a87-11ea-ae69-bc764e2007e4; Wed, 20 May 2020 10:50:28 +0000 (UTC) Received: by mail-ej1-x62b.google.com with SMTP id d7so3196868eja.7 for ; Wed, 20 May 2020 03:50:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:reply-to:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-transfer-encoding:content-language :thread-index; bh=kXc3YsXD6WdzJLKK/MADRHqsmnNYXZb1UrKhbte5gqU=; b=diYlybjPAwMFN/TSud4BonXo4C/RCNMpGBar/EgLWY9VzP3qUu3qPtGo7DdldZ5U/I CJPFwu5pNuzzUNEhUmiS3gXBQJ47b6Fz05CCtEdQkYBWmaSusB11x4beyc47Pe7fCgPL zQC3vD7fy3XJ0WckAsEzLcKjcC1r/Ia+/wDWIK7OlLPw1h17RU2BbjPGhkU5savowTQ6 A2+NWoxKwpJQSPFO1i0ueJHRaI4EE4XGLXeYy93bYmGr6uX86vVf+2Dy3eF1NkAznHXU NvANnPtOcad9mfzJgxSvZppGGDGJZyxOkQIrfldNNC+TtGd9CBUYUtAaQxeZeEnuBUZv qFtQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:reply-to:to:cc:references:in-reply-to :subject:date:message-id:mime-version:content-transfer-encoding :content-language:thread-index; bh=kXc3YsXD6WdzJLKK/MADRHqsmnNYXZb1UrKhbte5gqU=; b=pQ6Y1Y2+3F9m7cVCpjHvpPimwVyUG8D4jiXybgzWplqr8+KL9e7ltM/9WYy5G37BG6 RM/79EdgbLaPPSrbpyjjEvLVzmcmYSBe7kESU9kA2g62IKSeARBarhpjd/u85bv/My0W q99X+1HSwL4QpAZqqsQJnSznTHmJtFkbVN85G6MJcHUOUxaWoPiVTxh3aFWdsLeTvbGW eJDUI5S9xRnfEZ5izXnEgAsjsrdWDmlBsI6R8U9nflHPZQlV2CXTiYlwyb9Go30xSJJA OLHYqvql6NmPRhBukvWAAaYYCAOFj4Snd3E3ckLyj82ZCdZfSAm/q+StBy18leFSt9Go Fi7w== X-Gm-Message-State: AOAM532euLZ0ol9BwXQSBN3EX6Y42cKjdLRAKFfj/iOvJDmT9APrcms+ 3eGjkBLtUAokPI0b85zAAT8= X-Google-Smtp-Source: ABdhPJzwoKWYQshUjlG53R7HghVrVszBOYZcRQ6iXW1dZpJqVY12+qoQYbfCLiAyYk57d5t46mxxfA== X-Received: by 2002:a17:906:4815:: with SMTP id w21mr3340872ejq.533.1589971827772; Wed, 20 May 2020 03:50:27 -0700 (PDT) Received: from CBGR90WXYV0 ([54.239.6.187]) by smtp.gmail.com with ESMTPSA id oq4sm1606166ejb.0.2020.05.20.03.50.26 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 20 May 2020 03:50:27 -0700 (PDT) From: Paul Durrant X-Google-Original-From: "Paul Durrant" To: "'Juergen Gross'" , References: <20200520101605.4263-1-jgross@suse.com> In-Reply-To: <20200520101605.4263-1-jgross@suse.com> Subject: RE: [PATCH] docs: update xenstore-migration.md Date: Wed, 20 May 2020 11:50:25 +0100 Message-ID: <002a01d62e94$78de4b40$6a9ae1c0$@xen.org> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Outlook 16.0 Content-Language: en-gb Thread-Index: AQJtc1rpVxCWDPAud8mNEtXyIsLDq6eCQa8g X-BeenThere: xen-devel@lists.xenproject.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Xen developer discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Reply-To: paul@xen.org Cc: 'Stefano Stabellini' , 'Julien Grall' , 'Wei Liu' , 'Andrew Cooper' , 'Ian Jackson' , 'George Dunlap' , 'Jan Beulich' Errors-To: xen-devel-bounces@lists.xenproject.org Sender: "Xen-devel" > -----Original Message----- > From: Xen-devel On Behalf Of Juergen Gross > Sent: 20 May 2020 11:16 > To: xen-devel@lists.xenproject.org > Cc: Juergen Gross ; Stefano Stabellini ; Julien Grall > ; Wei Liu ; Andrew Cooper ; Ian Jackson > ; George Dunlap ; Jan Beulich > Subject: [PATCH] docs: update xenstore-migration.md > > Update connection record details: make flags common for sockets and > domains, and add pending incoming data. > > Signed-off-by: Juergen Gross LGTM Reviewed-by: Paul Durrant > --- > docs/designs/xenstore-migration.md | 63 ++++++++++++++++-------------- > 1 file changed, 34 insertions(+), 29 deletions(-) > > diff --git a/docs/designs/xenstore-migration.md b/docs/designs/xenstore-migration.md > index 34a2afd17e..e361d6b5e7 100644 > --- a/docs/designs/xenstore-migration.md > +++ b/docs/designs/xenstore-migration.md > @@ -147,31 +147,45 @@ the domain being migrated. > ``` > 0 1 2 3 4 5 6 7 octet > +-------+-------+-------+-------+-------+-------+-------+-------+ > -| conn-id | conn-type | conn-spec > +| conn-id | conn-type | flags | > ++-------------------------------+---------------+---------------+ > +| conn-spec > ... > +-------------------------------+-------------------------------+ > -| data-len | data > -+-------------------------------+ > +| in-data-len | out-data-len | > ++-------------------------------+-------------------------------+ > +| data > ... > ``` > > > -| Field | Description | > -|-------------|-------------------------------------------------| > -| `conn-id` | A non-zero number used to identify this | > -| | connection in subsequent connection-specific | > -| | records | > -| | | > -| `conn-type` | 0x0000: shared ring | > -| | 0x0001: socket | > -| | 0x0002 - 0xFFFF: reserved for future use | > -| | | > -| `conn-spec` | See below | > -| | | > -| `data-len` | The length (in octets) of any pending data not | > -| | yet written to the connection | > -| | | > -| `data` | Pending data (may be empty) | > +| Field | Description | > +|----------------|----------------------------------------------| > +| `conn-id` | A non-zero number used to identify this | > +| | connection in subsequent connection-specific | > +| | records | > +| | | > +| `flags` | A bit-wise OR of: | > +| | 0001: read-only | > +| | | > +| `conn-type` | 0x0000: shared ring | > +| | 0x0001: socket | > +| | 0x0002 - 0xFFFF: reserved for future use | > +| | | > +| `conn-spec` | See below | > +| | | > +| `in-data-len` | The length (in octets) of any data read | > +| | from the connection not yet processed | > +| | | > +| `out-data-len` | The length (in octets) of any pending data | > +| | not yet written to the connection | > +| | | > +| `data` | Pending data, first read data, then written | > +| | data (any of both may be empty) | > + > +In case of live update the connection record for the connection via which > +the live update command was issued will contain the response for the live > +update command in the pending write data. > > The format of `conn-spec` is dependent upon `conn-type`. > > @@ -182,8 +196,6 @@ For `shared ring` connections it is as follows: > > ``` > 0 1 2 3 4 5 6 7 octet > - +-------+-------+ > - | flags | > +---------------+---------------+---------------+---------------+ > | domid | tdomid | evtchn | > +-------------------------------+-------------------------------+ > @@ -198,8 +210,6 @@ For `shared ring` connections it is as follows: > | | it has been subject to an SET_TARGET | > | | operation [2] or DOMID_INVALID [3] otherwise | > | | | > -| `flags` | Must be zero | > -| | | > | `evtchn` | The port number of the interdomain channel used | > | | by `domid` to communicate with xenstored | > | | | > @@ -211,8 +221,6 @@ For `socket` connections it is as follows: > > > ``` > - +-------+-------+ > - | flags | > +---------------+---------------+---------------+---------------+ > | socket-fd | pad | > +-------------------------------+-------------------------------+ > @@ -221,9 +229,6 @@ For `socket` connections it is as follows: > > | Field | Description | > |-------------|-------------------------------------------------| > -| `flags` | A bit-wise OR of: | > -| | 0001: read-only | > -| | | > | `socket-fd` | The file descriptor of the connected socket | > > This type of connection is only relevant for live update, where the xenstored > @@ -398,4 +403,4 @@ explanation of node permissions. > > [3] See https://xenbits.xen.org/gitweb/?p=xen.git;a=blob;f=xen/include/public/xen.h;hb=HEAD#l612 > > -[4] https://wiki.xen.org/wiki/XenBus > \ No newline at end of file > +[4] https://wiki.xen.org/wiki/XenBus > -- > 2.26.1 >