From nobody Tue May 7 13:51:32 2024 Delivered-To: importer@patchew.org Authentication-Results: mx.zohomail.com; spf=none (zoho.com: 192.237.175.120 is neither permitted nor denied by domain of lists.xenproject.org) smtp.mailfrom=xen-devel-bounces@lists.xenproject.org ARC-Seal: i=1; a=rsa-sha256; t=1563823350; cv=none; d=zoho.com; s=zohoarc; b=YK/6wd4uIeT2dGAIRHbDAlfpBM1rdg/xRmMEcDI6VUMgW2pkzt5SK8lFWGUR6QfLIkIi7uHm0I2pDsS1xY6FKc2Bm5OjmV84ipNOniXh5QV5z4PMJK5vRkNTULW+hbXZFiicIK67ygOo+lqPycEiw73Jt1b1HKRzJvA9ueL7dG4= ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=zoho.com; s=zohoarc; t=1563823350; h=Content-Type:Content-Transfer-Encoding:Cc:Date:From:List-Subscribe:List-Post:List-Id:List-Help:List-Unsubscribe:MIME-Version:Message-ID:Sender:Subject:To:ARC-Authentication-Results; bh=Hcw1r6bLa2tVDgA+3yx5nCk2i+0DoJ2Nt9TAhXgXGLc=; b=CU86v+HggQGbr/HvJnY8s5LOCFMd7iADufsMGttVTMlgNAiGfupFij5fq2BzObFM5rD5BSDrsXEvNDaHY6XpGg5KldOQHmhh/NWFuNW7Vx21E9Tc6LuEz8PD2ftR95WCFBXgIKuuZiyfQDhorgKvr4BDM/Kq8y2mWE0MXPIETEM= ARC-Authentication-Results: i=1; mx.zoho.com; spf=none (zoho.com: 192.237.175.120 is neither permitted nor denied by domain of lists.xenproject.org) smtp.mailfrom=xen-devel-bounces@lists.xenproject.org Return-Path: Received: from lists.xenproject.org (lists.xenproject.org [192.237.175.120]) by mx.zohomail.com with SMTPS id 1563823349881292.58776910780125; Mon, 22 Jul 2019 12:22:29 -0700 (PDT) Received: from localhost ([127.0.0.1] helo=lists.xenproject.org) by lists.xenproject.org with esmtp (Exim 4.89) (envelope-from ) id 1hpdrs-0000m7-5R; Mon, 22 Jul 2019 19:21:04 +0000 Received: from us1-rack-dfw2.inumbo.com ([104.130.134.6]) by lists.xenproject.org with esmtp (Exim 4.89) (envelope-from ) id 1hpdrq-0000m2-R1 for xen-devel@lists.xenproject.org; Mon, 22 Jul 2019 19:21:02 +0000 Received: from esa4.hc3370-68.iphmx.com (unknown [216.71.155.144]) by us1-rack-dfw2.inumbo.com (Halon) with ESMTPS id d6b24842-acb5-11e9-8980-bc764e045a96; Mon, 22 Jul 2019 19:21:00 +0000 (UTC) X-Inumbo-ID: d6b24842-acb5-11e9-8980-bc764e045a96 Authentication-Results: esa4.hc3370-68.iphmx.com; dkim=none (message not signed) header.i=none; spf=None smtp.pra=andrew.cooper3@citrix.com; spf=Pass smtp.mailfrom=Andrew.Cooper3@citrix.com; spf=None smtp.helo=postmaster@mail.citrix.com Received-SPF: none (zoho.com: 192.237.175.120 is neither permitted nor denied by domain of lists.xenproject.org) client-ip=192.237.175.120; envelope-from=xen-devel-bounces@lists.xenproject.org; helo=lists.xenproject.org; Received-SPF: None (esa4.hc3370-68.iphmx.com: no sender authenticity information available from domain of andrew.cooper3@citrix.com) identity=pra; client-ip=162.221.158.21; receiver=esa4.hc3370-68.iphmx.com; envelope-from="Andrew.Cooper3@citrix.com"; x-sender="andrew.cooper3@citrix.com"; x-conformance=sidf_compatible Received-SPF: Pass (esa4.hc3370-68.iphmx.com: domain of Andrew.Cooper3@citrix.com designates 162.221.158.21 as permitted sender) identity=mailfrom; client-ip=162.221.158.21; receiver=esa4.hc3370-68.iphmx.com; envelope-from="Andrew.Cooper3@citrix.com"; x-sender="Andrew.Cooper3@citrix.com"; x-conformance=sidf_compatible; x-record-type="v=spf1"; x-record-text="v=spf1 ip4:209.167.231.154 ip4:178.63.86.133 ip4:195.66.111.40/30 ip4:85.115.9.32/28 ip4:199.102.83.4 ip4:192.28.146.160 ip4:192.28.146.107 ip4:216.52.6.88 ip4:216.52.6.188 ip4:162.221.158.21 ip4:162.221.156.83 ~all" Received-SPF: None (esa4.hc3370-68.iphmx.com: no sender authenticity information available from domain of postmaster@mail.citrix.com) identity=helo; client-ip=162.221.158.21; receiver=esa4.hc3370-68.iphmx.com; envelope-from="Andrew.Cooper3@citrix.com"; x-sender="postmaster@mail.citrix.com"; x-conformance=sidf_compatible IronPort-SDR: txGUa52mpJOEAIJ2UwrBzidTcL5kb5a5yO7AsdHvERDD5+M44VGmdAc6OOyFxSUbWYRyFTHTcy eOzbpbGINqgUR9TI7lCP3ZjUyMbDCU0PSQ7TR9AqTglvbUbmynIjYVGeXXh5FzwSHT8quvM8Bk QREuwPM830vi3tSVlU/UwjWM/76/NupuCSjZHDVdSE96PS8SEg2dIrM5JOnywvS2UAFXzyY8KG mmWXKnXvs2mBiKU/iyPBDxsjsaoF/K26Ix7hUtSDGiCZSIYJe01KnDefbTBsmeVKBUTnDJ6AhF kwM= X-SBRS: 2.7 X-MesageID: 3396927 X-Ironport-Server: esa4.hc3370-68.iphmx.com X-Remote-IP: 162.221.158.21 X-Policy: $RELAYED X-IronPort-AV: E=Sophos;i="5.64,296,1559534400"; d="scan'208";a="3396927" From: Andrew Cooper To: Xen-devel Date: Mon, 22 Jul 2019 20:20:56 +0100 Message-ID: <20190722192056.15816-1-andrew.cooper3@citrix.com> X-Mailer: git-send-email 2.11.0 MIME-Version: 1.0 Subject: [Xen-devel] [PATCH] docs/sphinx: todo/wishlist X-BeenThere: xen-devel@lists.xenproject.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Xen developer discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Cc: Lars Kurth , Stefano Stabellini , Wei Liu , George Dunlap , Andrew Cooper , Tim Deegan , Julien Grall , Paul Durrant , Jan Beulich , Ian Jackson , =?UTF-8?q?Roger=20Pau=20Monn=C3=A9?= Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Errors-To: xen-devel-bounces@lists.xenproject.org Sender: "Xen-devel" a.k.a. (at least in this form) Andrew's "work which might be offloadable to someone else" list. Signed-off-by: Andrew Cooper --- CC: George Dunlap CC: Ian Jackson CC: Jan Beulich CC: Stefano Stabellini CC: Tim Deegan CC: Wei Liu CC: Julien Grall CC: Lars Kurth CC: Paul Durrant CC: Roger Pau Monn=C3=A9 RFC for obvious reasons. A rendered version of this can be found at: https://andrewcoop-xen.readthedocs.io/en/docs-wishlist/misc/wishlist.html During XenSummit in Chicago, it was expressed several times that having some todo lists would be a benefit, to help coordinate work in related areas. Here is an attempt to start one. For now, it covers one single item (xenstored's use of non-stable APIs) to get some feedback about the general approach. I have plenty to get stuck into in Xen itself if this way of expressing them isn't deemed unacceptable. As for the wishlist itself, I think it is important that it be restricted to concrete actions (i.e. already partially groomed, if you speak agile), which are identified problems, and suggested fixes. In particular, I don't think it is appropriate to devolve into a bullet poi= nt list of new features, or tasks like "document $whotsit". It should be restricted to things which are real problems, on existing systems, which ha= ve some forward plan of action. That way, any developer should be able to cross-reference at least at a high level, and see if there are areas of overlapping work, or whether a slightly tweaked approach might be suitable = for multiple areas. Anyway - thoughts from the peanut gallery? --- docs/conf.py | 10 +++++++++- docs/index.rst | 9 +++++++++ docs/misc/wishlist.rst | 53 ++++++++++++++++++++++++++++++++++++++++++++++= ++++ 3 files changed, 71 insertions(+), 1 deletion(-) create mode 100644 docs/misc/wishlist.rst diff --git a/docs/conf.py b/docs/conf.py index 73b7b9bfa2..a5765bf7f4 100644 --- a/docs/conf.py +++ b/docs/conf.py @@ -52,7 +52,7 @@ # Add any Sphinx extension module names here, as strings. They can be # extensions coming with Sphinx (named 'sphinx.ext.*') or your custom # ones. -extensions =3D [] +extensions =3D ["sphinx.ext.extlinks"] =20 # Add any paths that contain templates here, relative to this directory. templates_path =3D ['_templates'] @@ -191,3 +191,11 @@ =20 # A list of files that should not be packed into the epub file. epub_exclude_files =3D ['search.html'] + + +# -- Configuration for extlinks ------------------------------------------= ---- + +extlinks =3D { + 'xen-cs': ('https://xenbits.xen.org/gitweb/?p=3Dxen.git;a=3Dcommitdiff= ;h=3D%s', + "Xen c/s "), +} diff --git a/docs/index.rst b/docs/index.rst index 31bb8927f2..9bbe6ee688 100644 --- a/docs/index.rst +++ b/docs/index.rst @@ -45,3 +45,12 @@ kind of development environment. :maxdepth: 2 =20 hypervisor-guide/index + + +Misc unsorted +------------- + +.. toctree:: + :maxdepth: 2 + + misc/wishlist diff --git a/docs/misc/wishlist.rst b/docs/misc/wishlist.rst new file mode 100644 index 0000000000..6cdb47d6e7 --- /dev/null +++ b/docs/misc/wishlist.rst @@ -0,0 +1,53 @@ +Development Wishlist +=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D + +Remove xenstored's dependencies on unstable interfaces +------------------------------------------------------ + +Various xenstored implementations use libxc for two purposes. It would be= a +substantial advantage to move xenstored onto entirely stable interfaces, w= hich +disconnects it from the internal of the libxc. + +1. Foreign mapping of the store ring +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +This is obsolete since :xen-cs:`6a2de353a9` (2012) which allocated grant +entries instead, to allow xenstored to function as a stub-domain without d= om0 +permissions. :xen-cs:`38eeb3864d` dropped foreign mapping for cxenstored. +However, there are no OCaml bindings for libxengnttab. + +Work Items: + +* Minimal ``tools/ocaml/libs/xg/`` binding for ``tools/libs/gnttab/``. +* Replicate :xen-cs:`38eeb3864d` for oxenstored as well. + + +2. Figuring out which domain(s) have gone away +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +Currently, the handling of domains is asymmetric. + +* When a domain is created, the toolstack explicitly sends an + ``XS_INTRODUCE(domid, store mfn, store evtchn)`` message to xenstored, to + cause xenstored to connect to the guest ring, and fire the + ``@introduceDomain`` watch. +* When a domain is destroyed, Xen fires ``VIRQ_DOM_EXC`` which is bound by + xenstored, rather than the toolstack. xenstored updates its idea of the + status of domains, and fires the ``@releaseDomain`` watch. + +Xenstored uses ``xc_domain_getinfo()``, to work out which domain(s) have g= one +away, and only cares about the shutdown status. + +Furthermore, ``@releaseDomain`` (like ``VIRQ_DOM_EXC``) is a single-bit +message, which requires all listeners to evaluate whether the message appl= ies +to them or not. This results in a flurry of ``xc_domain_getinfo()`` calls +from multiple entities in the system, which all serialise on the domctl lo= ck +in Xen. + +Work Items: + +* Figure out how shutdown status can be expressed in a stable way from Xen. +* Figure out if ``VIRQ_DOM_EXC`` and ``@releaseDomain`` can be extended to + carry at least a domid, to make domain shutdown scale better. +* Figure out if ``VIRQ_DOM_EXC`` would better be bound by the toolstack, + rather than xenstored. --=20 2.11.0 _______________________________________________ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel