From mirageos-devel-bounces@lists.xenproject.org Sun Feb 01 21:12:43 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 01 Feb 2015 21:12:43 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YI1op-00063N-Cq; Sun, 01 Feb 2015 21:12:35 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YI1oo-000637-D1 for mirageos-devel@lists.xenproject.org; Sun, 01 Feb 2015 21:12:34 +0000 Received: from [85.158.143.35] by server-2.bemta-4.messagelabs.com id BC/CE-02749-1C69EC45; Sun, 01 Feb 2015 21:12:33 +0000 X-Env-Sender: Dave.Scott@citrix.com X-Msg-Ref: server-6.tower-21.messagelabs.com!1422825152!13793440!1 X-Originating-IP: [185.25.65.24] X-SpamReason: No, hits=0.0 required=7.0 tests=received_headers: No Received headers X-StarScan-Received: X-StarScan-Version: 6.12.5; banners=-,-,- X-VirusChecked: Checked Received: (qmail 9857 invoked from network); 1 Feb 2015 21:12:32 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (185.25.65.24) by server-6.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 1 Feb 2015 21:12:32 -0000 X-IronPort-AV: E=Sophos;i="5.09,503,1418083200"; d="scan'208";a="30715821" From: Dave Scott To: Xen-devel Thread-Topic: entropy for VMs Thread-Index: AQHQPmPK0gebIcSiW0KibH3nefMq7Q== Date: Sun, 1 Feb 2015 21:12:31 +0000 Message-ID: <0EEB9201-A222-4EF2-96A2-790FFDB78970@citrix.com> Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: Content-ID: <3ECD6D22B847FA4B9DE2C8F67680BD49@citrix.com> MIME-Version: 1.0 X-DLP: AMS1 Cc: mirageos-devel Subject: [MirageOS-devel] entropy for VMs X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org SGksDQoNCk1pcmFnZSBub3cgaGFzIG5pY2UgZmVhdHVyZXMgbGlrZSBUTFNbMV0gYW5kIHRoZXJl Zm9yZSBuZWVkcyBhIGdvb2Qgc291cmNlIG9mIHJhbmRvbW5lc3MgdG8gZ2VuZXJhdGUgc2Vzc2lv biBrZXlzLiBNaXJhZ2UgVk1zIGFyZSBQViwgc28gd2UgY2Fu4oCZdCB1c2UgdmlydGlvLXJuZy4g V2UndmUgY3JlYXRlZCBhIHByb3RvdHlwZSBlbnRyb3B5IHNlcnZlciB3aGljaCBtYXkgYmUgb2Yg aW50ZXJlc3QgdG8gb3RoZXIgcGVvcGxlIHRvbzoNCg0KaHR0cHM6Ly9naXRodWIuY29tL21pcmFn ZS94ZW50cm9weWQNCg0KVGhpcyBiZWhhdmVzIGEgYml0IGxpa2UgeGVuY29uc29sZWQ6IGl0IHdh dGNoZXMgZm9yIGRvbWFpbnMgYmVpbmcgY3JlYXRlZCBhbmQgdGhlbiBjb25uZWN0cyB0byB0aGVt IHZpYSB0aGUgY29uc29sZSBwcm90b2NvbC4gVGhlcmUgaXMgYSBsaXR0bGUgaGFuZHNoYWtlWzJd ICh0byBjYXRjaCBhY2NpZGVudGFsIHNjcmV3dXBzIHdpdGggdGhlIHdyb25nIGNvbnNvbGUpIGFu ZCB0aGVuIHRoZSBkYWVtb24gZmVlZHMgcmFuZG9tIGRhdGEgaW50byB0aGUgY29uc29sZSB0aHJv dWdoIGEgcmF0ZS1saW1pdGVyLiBNaXJhZ2XigJlzIGVudHJvcHkgZHJpdmVyIGNhbiByZWFkIHRo ZSBkYXRhIGZyb20gdGhlIGNvbnNvbGUgZmFpcmx5IGVhc2lseVszXS4gSSBhc3N1bWUgd2UgY291 bGQgd3JpdGUgYSBzaW1pbGFyIHRoaW5nIGZvciBsaW51eCB0b28uDQoNCldoYXQgZG8geW91IHRo aW5rPyAoQW5kIGRvZXMgYW55b25lIGtub3cgYSBiZXR0ZXIgd2F5IChUTSk/KQ0KDQpUaGUgY29k ZSBpcyBzdGlsbCBhIGJpdCBvZiBhIHByb3RvdHlwZSwgYW5kIGNvbnRhaW5zIHNsaWdodGx5IGZv cmtlZCB2ZXJzaW9ucyBvZiBjb3JlIE1pcmFnZSBsaWJyYXJpZXMtLSBJIG5lZWQgdG8gc29ydCB0 aGF0IG91dCBiZWZvcmUgYSAxLjAuDQoNCkNoZWVycywNCkRhdmUNCg0KWzFdIGh0dHA6Ly9vcGVu bWlyYWdlLm9yZy9ibG9nL2ludHJvZHVjaW5nLW9jYW1sLXRscw0KWzJdIGh0dHBzOi8vZ2l0aHVi LmNvbS9taXJhZ2UveGVudHJvcHlkL2Jsb2IvbWFzdGVyL2RvYy9wcm90b2NvbC5tZA0KWzNdIGh0 dHBzOi8vZ2l0aHViLmNvbS9kanM1NS9taXJhZ2UtZW50cm9weS9ibG9iLzk4MWIwNzBkNzhhZTQw NzAxNWIxZThkZWRiMzE0MWIwNTQ1NDM2NmYveGVuL2VudHJvcHlfeGVuLm1sI0wxMzAKX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KTWlyYWdlT1MtZGV2ZWwg bWFpbGluZyBsaXN0Ck1pcmFnZU9TLWRldmVsQGxpc3RzLnhlbnByb2plY3Qub3JnCmh0dHA6Ly9s aXN0cy54ZW5wcm9qZWN0Lm9yZy9jZ2ktYmluL21haWxtYW4vbGlzdGluZm8vbWlyYWdlb3MtZGV2 ZWwK From mirageos-devel-bounces@lists.xenproject.org Sun Feb 01 21:12:43 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 01 Feb 2015 21:12:43 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YI1op-00063N-Cq; Sun, 01 Feb 2015 21:12:35 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YI1oo-000637-D1 for mirageos-devel@lists.xenproject.org; Sun, 01 Feb 2015 21:12:34 +0000 Received: from [85.158.143.35] by server-2.bemta-4.messagelabs.com id BC/CE-02749-1C69EC45; Sun, 01 Feb 2015 21:12:33 +0000 X-Env-Sender: Dave.Scott@citrix.com X-Msg-Ref: server-6.tower-21.messagelabs.com!1422825152!13793440!1 X-Originating-IP: [185.25.65.24] X-SpamReason: No, hits=0.0 required=7.0 tests=received_headers: No Received headers X-StarScan-Received: X-StarScan-Version: 6.12.5; banners=-,-,- X-VirusChecked: Checked Received: (qmail 9857 invoked from network); 1 Feb 2015 21:12:32 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (185.25.65.24) by server-6.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 1 Feb 2015 21:12:32 -0000 X-IronPort-AV: E=Sophos;i="5.09,503,1418083200"; d="scan'208";a="30715821" From: Dave Scott To: Xen-devel Thread-Topic: entropy for VMs Thread-Index: AQHQPmPK0gebIcSiW0KibH3nefMq7Q== Date: Sun, 1 Feb 2015 21:12:31 +0000 Message-ID: <0EEB9201-A222-4EF2-96A2-790FFDB78970@citrix.com> Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: Content-ID: <3ECD6D22B847FA4B9DE2C8F67680BD49@citrix.com> MIME-Version: 1.0 X-DLP: AMS1 Cc: mirageos-devel Subject: [MirageOS-devel] entropy for VMs X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org SGksDQoNCk1pcmFnZSBub3cgaGFzIG5pY2UgZmVhdHVyZXMgbGlrZSBUTFNbMV0gYW5kIHRoZXJl Zm9yZSBuZWVkcyBhIGdvb2Qgc291cmNlIG9mIHJhbmRvbW5lc3MgdG8gZ2VuZXJhdGUgc2Vzc2lv biBrZXlzLiBNaXJhZ2UgVk1zIGFyZSBQViwgc28gd2UgY2Fu4oCZdCB1c2UgdmlydGlvLXJuZy4g V2UndmUgY3JlYXRlZCBhIHByb3RvdHlwZSBlbnRyb3B5IHNlcnZlciB3aGljaCBtYXkgYmUgb2Yg aW50ZXJlc3QgdG8gb3RoZXIgcGVvcGxlIHRvbzoNCg0KaHR0cHM6Ly9naXRodWIuY29tL21pcmFn ZS94ZW50cm9weWQNCg0KVGhpcyBiZWhhdmVzIGEgYml0IGxpa2UgeGVuY29uc29sZWQ6IGl0IHdh dGNoZXMgZm9yIGRvbWFpbnMgYmVpbmcgY3JlYXRlZCBhbmQgdGhlbiBjb25uZWN0cyB0byB0aGVt IHZpYSB0aGUgY29uc29sZSBwcm90b2NvbC4gVGhlcmUgaXMgYSBsaXR0bGUgaGFuZHNoYWtlWzJd ICh0byBjYXRjaCBhY2NpZGVudGFsIHNjcmV3dXBzIHdpdGggdGhlIHdyb25nIGNvbnNvbGUpIGFu ZCB0aGVuIHRoZSBkYWVtb24gZmVlZHMgcmFuZG9tIGRhdGEgaW50byB0aGUgY29uc29sZSB0aHJv dWdoIGEgcmF0ZS1saW1pdGVyLiBNaXJhZ2XigJlzIGVudHJvcHkgZHJpdmVyIGNhbiByZWFkIHRo ZSBkYXRhIGZyb20gdGhlIGNvbnNvbGUgZmFpcmx5IGVhc2lseVszXS4gSSBhc3N1bWUgd2UgY291 bGQgd3JpdGUgYSBzaW1pbGFyIHRoaW5nIGZvciBsaW51eCB0b28uDQoNCldoYXQgZG8geW91IHRo aW5rPyAoQW5kIGRvZXMgYW55b25lIGtub3cgYSBiZXR0ZXIgd2F5IChUTSk/KQ0KDQpUaGUgY29k ZSBpcyBzdGlsbCBhIGJpdCBvZiBhIHByb3RvdHlwZSwgYW5kIGNvbnRhaW5zIHNsaWdodGx5IGZv cmtlZCB2ZXJzaW9ucyBvZiBjb3JlIE1pcmFnZSBsaWJyYXJpZXMtLSBJIG5lZWQgdG8gc29ydCB0 aGF0IG91dCBiZWZvcmUgYSAxLjAuDQoNCkNoZWVycywNCkRhdmUNCg0KWzFdIGh0dHA6Ly9vcGVu bWlyYWdlLm9yZy9ibG9nL2ludHJvZHVjaW5nLW9jYW1sLXRscw0KWzJdIGh0dHBzOi8vZ2l0aHVi LmNvbS9taXJhZ2UveGVudHJvcHlkL2Jsb2IvbWFzdGVyL2RvYy9wcm90b2NvbC5tZA0KWzNdIGh0 dHBzOi8vZ2l0aHViLmNvbS9kanM1NS9taXJhZ2UtZW50cm9weS9ibG9iLzk4MWIwNzBkNzhhZTQw NzAxNWIxZThkZWRiMzE0MWIwNTQ1NDM2NmYveGVuL2VudHJvcHlfeGVuLm1sI0wxMzAKX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KTWlyYWdlT1MtZGV2ZWwg bWFpbGluZyBsaXN0Ck1pcmFnZU9TLWRldmVsQGxpc3RzLnhlbnByb2plY3Qub3JnCmh0dHA6Ly9s aXN0cy54ZW5wcm9qZWN0Lm9yZy9jZ2ktYmluL21haWxtYW4vbGlzdGluZm8vbWlyYWdlb3MtZGV2 ZWwK From mirageos-devel-bounces@lists.xenproject.org Mon Feb 02 00:46:26 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 02 Feb 2015 00:46:26 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YI59j-0000nK-KZ; Mon, 02 Feb 2015 00:46:23 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YI59i-0000nF-5x for mirageos-devel@lists.xenproject.org; Mon, 02 Feb 2015 00:46:22 +0000 Received: from [85.158.137.68] by server-17.bemta-3.messagelabs.com id 80/60-02896-DD8CEC45; Mon, 02 Feb 2015 00:46:21 +0000 X-Env-Sender: Christophe.TROESTLER@umons.ac.be X-Msg-Ref: server-11.tower-31.messagelabs.com!1422837980!11241074!1 X-Originating-IP: [157.56.112.58] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.12.5; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15115 invoked from network); 2 Feb 2015 00:46:20 -0000 Received: from mail-am1on0058.outbound.protection.outlook.com (HELO emea01-am1-obe.outbound.protection.outlook.com) (157.56.112.58) by server-11.tower-31.messagelabs.com with AES256-SHA encrypted SMTP; 2 Feb 2015 00:46:20 -0000 Received: from DB3PR05CA0046.eurprd05.prod.outlook.com (25.160.41.174) by AMSPR05MB518.eurprd05.prod.outlook.com (10.242.224.156) with Microsoft SMTP Server (TLS) id 15.1.75.20; Mon, 2 Feb 2015 00:45:58 +0000 Received: from AM1FFO11FD036.protection.gbl (2a01:111:f400:7e00::166) by DB3PR05CA0046.outlook.office365.com (2a01:111:e400:9428::46) with Microsoft SMTP Server (TLS) id 15.1.75.20 via Frontend Transport; Mon, 2 Feb 2015 00:45:58 +0000 Received: from smtp.umons.ac.be (193.190.208.132) by AM1FFO11FD036.mail.protection.outlook.com (10.174.64.225) with Microsoft SMTP Server (TLS) id 15.1.75.11 via Frontend Transport; Mon, 2 Feb 2015 00:45:57 +0000 Received: from poincare (10.104.2.68) by smtp.umons.ac.be (10.104.2.84) with Microsoft SMTP Server (TLS) id 14.3.224.2; Mon, 2 Feb 2015 01:45:51 +0100 Received: from localhost ([::1]) by poincare with esmtp (Exim 4.84) (envelope-from ) id 1YI59C-0003vl-5d; Mon, 02 Feb 2015 01:45:50 +0100 Date: Mon, 2 Feb 2015 01:45:49 +0100 Message-ID: <20150202.014549.1883720051237442569.Christophe.Troestler@umons.ac.be> To: Thomas Leonard , From: Christophe Troestler In-Reply-To: References: X-Face: #2fb%mPx>rRL@4ff~TVgZ"<[:,oL"`TUEGK/[8/qb58~C>jR(x4A+v/n)7BgpEtIph_neoLKJBq0JBY9:}8v|j Organization: Universite de Mons (http://math.umons.ac.be/anum/) X-Mailer: Mew version 6.6 on Emacs 24.4 / Mule 6.0 (HANACHIRUSATO) MIME-Version: 1.0 Content-Length: 5204 X-Originating-IP: [10.104.2.68] X-EOPAttributedMessage: 0 X-Matching-Connectors: 130673115579947630; (9b551343-d075-4328-d154-08d0574c44b8,aa519c6d-c5b7-417d-4ec3-08d1170c20a9); (9b551343-d075-4328-d154-08d0574c44b8,aa519c6d-c5b7-417d-4ec3-08d1170c20a9) Received-SPF: Pass (protection.outlook.com: domain of umons.ac.be designates 193.190.208.132 as permitted sender) receiver=protection.outlook.com; client-ip=193.190.208.132; helo=smtp.umons.ac.be; X-Forefront-Antispam-Report: CIP:193.190.208.132; CTRY:BE; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(10009020)(6009001)(438002)(51704005)(24454002)(6806004)(16796002)(36756003)(87936001)(57986006)(74482002)(46102003)(107886001)(76506005)(2950100001)(50226001)(23676002)(50466002)(226693001)(92566002)(76176999)(62966003)(77156002)(50986999)(106466001)(86362001)(103116003); DIR:OUT; SFP:1101; SCL:1; SRVR:AMSPR05MB518; H:smtp.umons.ac.be; FPR:; SPF:Pass; MLV:sfv; LANG:en; X-Microsoft-Antispam: UriScan:; X-Microsoft-Antispam: BCL:0;PCL:0;RULEID:;SRVR:AMSPR05MB518; X-Exchange-Antispam-Report-Test: UriScan:; X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(601004); SRVR:AMSPR05MB518; X-Forefront-PRVS: 0475418F50 X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(401004)(400005); SRVR:AMSPR05MB518; X-MS-Exchange-CrossTenant-OriginalArrivalTime: 02 Feb 2015 00:45:57.7295 (UTC) X-MS-Exchange-CrossTenant-Id: 5afe0b00-7697-4969-b663-5eab37d5f47e X-MS-Exchange-CrossTenant-OriginalAttributedTenantConnectingIp: TenantId=5afe0b00-7697-4969-b663-5eab37d5f47e; Ip=[193.190.208.132] X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem X-MS-Exchange-Transport-CrossTenantHeadersStamped: AMSPR05MB518 Subject: Re: [MirageOS-devel] Error handling in Mirage - request for comments! X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org T24gU2F0LCAzMSBKYW4gMjAxNSAyMTowNzoyMiArMDAwMCwgVGhvbWFzIExlb25hcmQgd3JvdGU6 Cj4gCj4gW+KApl0gQnV0IHRoZSByZWFsIHByb2JsZW0gaGVyZSBpcyB0aGF0IGJ5IG1ha2luZyBl eGNlcHRpb25zIGZhdGFsIHdlCj4gdHVybiBldmVyeSBleGNlcHRpb24gdXNlZCBpbiBleGlzdGlu ZyBPQ2FtbCBjb2RlIGludG8gYSBzZWN1cml0eQo+IHZ1bG5lcmFiaWxpdHkuIFvigKZdCgpTaW5j ZSBPQ2FtbCBzdXBwb3J0cyBleGNlcHRpb25zLCBJIHRoaW5rIHRoZXJlIGlzIG5vIGRvdWJ0IHRo YXQgd2UKbXVzdCBoYW5kbGUgdGhlbSBlZmZlY3RpdmVseSDigJQgbm90IGp1c3Qgd2lwZSB0aGVt IHVuZGVyIHRoZSBjYXJwZXQgYW5kCmxldCB0aGVtIGFib3J0IHRoZSBwcm9ncmFtL3VuaWtlcm5l bC4gIElkZWFsbHkgTHd0IHNob3VsZCBkZWFsCnNlbnNpYmx5IHdpdGggZXhjZXB0aW9ucyAoYW5k IHRoZSBkaXNjdXNzaW9uIHNlZW1zIHRvIGltcGx5IHRoZXJlIGFyZQphcmVhcyBvZiBpbXByb3Zl bWVudCDigJQgYnV0IGl0IGlzIHVuY2xlYXIgdG8gbWUgaG93IHlvdSBjYW4gZG8gdGhhdAplZmZp Y2llbnRseSB3aXRob3V0IHVzaW5nIGEgdHJ5IGJsb2NrIGluIGFsbCBiaW5kcykuICBTbyBpdCBz ZWVtcyB0bwptZSB0aGF0IHRoZXJlIGlzIGxpdHRsZSBjaG9pY2UgYnV0IHRoYXQgZXhjZXB0aW9u cyBiZSB0dXJuZWQgaW50bwpmYWlsZWQgdGhyZWFkcyBhdCB0aGUgcHJvZ3JhbW1lcidzIGRpc2Ny ZXRpb24uICBNYXliZSDigJxydW7igJ0gc2hvdWxkIGJlCnJlbmFtZWQg4oCccnVuX2V4buKAnSB0 byBpbmRpY2F0ZSB0aGF0IGV4Y2VwdGlvbnMgcGFzcyB0aHJvdWdoIGFuZCB0aGUKInNhZmUiIHJ1 biBzaG91bGQgYmUKCiAgICBydW4gOiAodW5pdCAtPiAnYSB0KSAtPiBbYE9rIG9mICdhIHwgYEV4 biBvZiBleG5dCgpBcyBpdCB3YXMgcHJldmlvdXNseSBtZW50aW9uZWQsIEkgYWxzbyB0aGluayB0 aGF0IHVzaW5nICJlcnJvci1hd2FyZQpyZXR1cm4gdHlwZXMiIHNob3VsZCBiZSBsaW1pdGVkIG1v c3RseSB0byBjYXNlcyB3aGVyZSB0aGUgZmFpbHVyZSBpcwpub3QgcmVhbGx5IGFuIGVycm9yIGFu ZCBzaG91bGQgYmUgZGVhbHQgd2l0aCBpbW1lZGlhdGVseSBieSB0aGUKY2FsbGVyLiAgQW5kIEkg YWdyZWUgd2l0aCBUaG9tYXMgd2hlbiBoZSBzYXlzIHRoYXQgb3ZlcnVzaW5nIHRoaXMKc2NoZW1l IHdpbGwgcmVzdWx0IGluIGVycm9ycyBiZWluZyBpZ25vcmVkIGluc3RlYWQgb2YgYmVpbmcgZGVh bHQgd2l0aApwcm9wZXJseS4KClRoZXJlIGFyZSBob3dldmVyIGVycm9ycyB0aGF0IHlvdSB3YW50 IHRvIG1hbmRhdGUgdGhhdCB0aGV5IGFyZSBkZWFsdAp3aXRoIGJ1dCBub3QgbmVjZXNzYXJpbHkg YXQgdGhlIGNhbGxpbmcgcG9pbnQuICBBIHR5cGljYWwgZXhhbXBsZSB0bwptZSBpcyDigJxyZWFk 4oCdIGJlY2F1c2UgaXQgaXMgb2Z0ZW4gbXVjaCAiaGlnaGVyIiBpbiB0aGUgcHJvZ3JhbSB0aGF0 IGFuCmFwcHJvcHJpYXRlIHJlc3BvbnNlIHRvIGEgZmFpbGluZyByZWFkIGNhbiBiZSBtYWRlIOKA lCB0aGlzIGlzIGltcG9ydGFudApmb3IgbGlicmFyaWVzIHRoYXQgd2lsbCBwb3N0LXByb2Nlc3Mg 4oCccmVhZOKAnXMgYW5kIHdpbGwgaGF2ZSBubyBpZGVhCndoYXQgdG8gZG8gaWYg4oCccmVhZOKA nSBmYWlscy4KClRvIG1ha2UgdGhlIGRpc2N1c3Npb24gYSBiaXQgbW9yZSBjb25jcmV0ZSwgaGVy ZSBpcyBhIHNpZ25hdHVyZQppbGx1c3RyYXRpbmcgaG93IHRoZXNlIGxhdHRlciBlcnJvcnMgbWF5 IGJlIGhhbmRsZWQ6CgogICAgdHlwZSAoJ2EsICdiKSB0CiAgICB2YWwgcmV0dXJuIDogJ2EgLT4g KCdhLCAnYikgdAogICAgdmFsICggPj49ICkgOiAoJ2EsICdiKSB0IC0+ICgnYSAtPiAoJ2MsICdi KSB0KSAtPiAoJ2MsICdiKSB0CiAgICB2YWwgZmFpbCA6IChbPiBdIGFzICdiKSAtPiAoXywgJ2Ip IHQKICAgIHZhbCBmYWlsX2V4biA6IGV4biAtPiAoJ2EsICdiKSB0CiAgICB2YWwgY2F0Y2ggOiAo J2EsICdiKSB0IC0+ICgnYiAtPiAoJ2EsICdjKSB0KSAtPiAoJ2EsICdjKSB0CiAgICB2YWwgY2F0 Y2hfZXhuIDogP2V4bjooZXhuIC0+ICgnYSwgJ2IpIHQpIC0+ICh1bml0IC0+ICgnYSwgJ2IpIHQp IC0+ICgnYSwgJ2IpIHQKICAgIHZhbCBydW4gOiAodW5pdCAtPiAoJ2EsIHVuaXQpIHQpIC0+IFtg T2sgb2YgJ2EgfCBgRXhuIG9mIGV4bl0KICAgIHZhbCBydW5fZXhuIDogKCdhLCB1bml0KSB0IC0+ ICdhCgpTb21lIHJlbWFya3MuICBUaGUg4oCcZmFpbOKAnSBmdW5jdGlvbiBpbXBvc2VzIHRoYXQg dGhlIGVycm9ycyBhcmUgbGFiZWxlZAp3aXRoIHBvbHltb3JwaGljIHZhcmlhbnRzLiAgU2luY2Ug dGhlc2UgYXJlIG5vdCBxdWFsaWZpZWQgYnkgdGhlCm1vZHVsZSBhbmQgdG8gYWxsb3cgZ2VuZXJp YyB0cmVhdG1lbnQsIGEgZ29vZCBpZGlvbSB3b3VsZCBwcm9iYWJseSBiZQp0byB1c2Ugc29tZXRo aW5nIGxpa2Ug4oCcYFggb2YgWC5lcnLigJ0gd2hlcmUg4oCcYFjigJ0gaXMgc3VmZmljaWVudGx5 CmV4cGxpY2l0IGFuZCDigJxYLmVycuKAnSBlbnVtZXJhdGVzIHRoZSBwb3NzaWJsZSBmYWlsdXJl cyBmb3IgdGhlIG1vZHVsZQrigJxY4oCdLiAgVGhlIGZ1bmN0aW9uIOKAnGNhdGNoX2V4biBm4oCd IHdpbGwgY2F0Y2ggZXhjZXB0aW9ucyByYWlzZWQgYnkg4oCcZuKAnQphcyB3ZWxsIGFzIGZhaWxl ZC10aHJlYWRzIG9uZXMgKGJ5IGRlZmF1bHQsIG9ubHkgdHVybmluZyBhbGwgZXhjZXB0aW9ucwpp bnRvIGZhaWxpbmcgdGhyZWFkIG9uZXMpLiAgVGhlIHVzZSBvZiDigJx1bml04oCdIGluIOKAnCgn YSwgdW5pdCkgdOKAnSBlbnN1cmVzCnRoYXQgdGhlIHRocmVhZCBpcyBvZiB0eXBlIOKAnChfLCAn YikgdOKAnSDigJQgaS5lLiB0aGF0IGFsbCBlcnJvcnMgaGF2ZQpiZWVuIGRlYWx0IHdpdGgg4oCU IHNvIGl0IGNhbiBiZSB1bmlmaWVkIHdpdGggYSBub24tcG9seW1vcnBoaWMgdmFyaWFudAp0eXBl LgoKVGhpcyBpcyBzaW1pbGFyIHRvIGRlY2xhcmluZwoKICAgIHR5cGUgKCdhLCAnYikgdCA9ICgn YSwgJ2IpIFJlc3VsdC50IEx3dC50CgpleGNlcHQgdGhhdCBvbmUgY2Fubm90IGRpdGNoIHRoZSDi gJxSZXN1bHQudOKAnSAoYW5kIG9uZSBhdm9pZHMgMQppbmRpcmVjdGlvbiBwZXIgYmluZCkuCgpV bmZvcnR1bmF0ZWx5LCBpdCBpcyBzb21lIHdvcmsgdG8gZW5zdXJlIHRoYXQgdGhlIGNvbXBpbGVy IHVuZGVyc3RhbmRzCnRoYXQgYWxsIGVycm9ycyB3ZXJlIGRlYWx0IHdpdGguICBDb25zaWRlcgoK ICAgIGxldCBtMSA9IGZhaWwoYFggMSkgPj49IGZ1biB4IC0+IGZhaWwgYFkKClRoZW4KCiAgICBs ZXQgbTIgPSBjYXRjaCBtMSAoZnVuY3Rpb24gYFggeCAtPiByZXR1cm4geAogICAgICAgICAgICAg ICAgICAgICAgICAgICAgICB8IGUgLT4gZmFpbCBlKQoKd2lsbCBub3QgZG8sIHlvdSBoYXZlIHRv IHdyaXRlCgogICAgbGV0IG0yID0gY2F0Y2ggbTEgKGZ1bmN0aW9uIGBYIHggLT4gcmV0dXJuIHgK ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgfCBgWSBhcyBlIC0+IGZhaWwgZSkKCnRvIG1h a2Ugc3VyZSDigJxtMuKAnSBzaG93cyB0aGF0IOKAnGBY4oCdIGlzIG5vIGxvbmdlciBhbiBpc3N1 ZS4gIFRodXMKZGVmaW5pbmcgZ29vZCB0eXBlcyB0byB1c2Ug4oCcI3R5cGXigJ0gaXMgaW1wb3J0 YW50LgoKTXkgMC4wMuKCrCwKQy4KCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fCk1pcmFnZU9TLWRldmVsIG1haWxpbmcgbGlzdApNaXJhZ2VPUy1kZXZlbEBs aXN0cy54ZW5wcm9qZWN0Lm9yZwpodHRwOi8vbGlzdHMueGVucHJvamVjdC5vcmcvY2dpLWJpbi9t YWlsbWFuL2xpc3RpbmZvL21pcmFnZW9zLWRldmVsCg== From mirageos-devel-bounces@lists.xenproject.org Mon Feb 02 00:46:26 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 02 Feb 2015 00:46:26 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YI59j-0000nK-KZ; Mon, 02 Feb 2015 00:46:23 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YI59i-0000nF-5x for mirageos-devel@lists.xenproject.org; Mon, 02 Feb 2015 00:46:22 +0000 Received: from [85.158.137.68] by server-17.bemta-3.messagelabs.com id 80/60-02896-DD8CEC45; Mon, 02 Feb 2015 00:46:21 +0000 X-Env-Sender: Christophe.TROESTLER@umons.ac.be X-Msg-Ref: server-11.tower-31.messagelabs.com!1422837980!11241074!1 X-Originating-IP: [157.56.112.58] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.12.5; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15115 invoked from network); 2 Feb 2015 00:46:20 -0000 Received: from mail-am1on0058.outbound.protection.outlook.com (HELO emea01-am1-obe.outbound.protection.outlook.com) (157.56.112.58) by server-11.tower-31.messagelabs.com with AES256-SHA encrypted SMTP; 2 Feb 2015 00:46:20 -0000 Received: from DB3PR05CA0046.eurprd05.prod.outlook.com (25.160.41.174) by AMSPR05MB518.eurprd05.prod.outlook.com (10.242.224.156) with Microsoft SMTP Server (TLS) id 15.1.75.20; Mon, 2 Feb 2015 00:45:58 +0000 Received: from AM1FFO11FD036.protection.gbl (2a01:111:f400:7e00::166) by DB3PR05CA0046.outlook.office365.com (2a01:111:e400:9428::46) with Microsoft SMTP Server (TLS) id 15.1.75.20 via Frontend Transport; Mon, 2 Feb 2015 00:45:58 +0000 Received: from smtp.umons.ac.be (193.190.208.132) by AM1FFO11FD036.mail.protection.outlook.com (10.174.64.225) with Microsoft SMTP Server (TLS) id 15.1.75.11 via Frontend Transport; Mon, 2 Feb 2015 00:45:57 +0000 Received: from poincare (10.104.2.68) by smtp.umons.ac.be (10.104.2.84) with Microsoft SMTP Server (TLS) id 14.3.224.2; Mon, 2 Feb 2015 01:45:51 +0100 Received: from localhost ([::1]) by poincare with esmtp (Exim 4.84) (envelope-from ) id 1YI59C-0003vl-5d; Mon, 02 Feb 2015 01:45:50 +0100 Date: Mon, 2 Feb 2015 01:45:49 +0100 Message-ID: <20150202.014549.1883720051237442569.Christophe.Troestler@umons.ac.be> To: Thomas Leonard , From: Christophe Troestler In-Reply-To: References: X-Face: #2fb%mPx>rRL@4ff~TVgZ"<[:,oL"`TUEGK/[8/qb58~C>jR(x4A+v/n)7BgpEtIph_neoLKJBq0JBY9:}8v|j Organization: Universite de Mons (http://math.umons.ac.be/anum/) X-Mailer: Mew version 6.6 on Emacs 24.4 / Mule 6.0 (HANACHIRUSATO) MIME-Version: 1.0 Content-Length: 5204 X-Originating-IP: [10.104.2.68] X-EOPAttributedMessage: 0 X-Matching-Connectors: 130673115579947630; (9b551343-d075-4328-d154-08d0574c44b8,aa519c6d-c5b7-417d-4ec3-08d1170c20a9); (9b551343-d075-4328-d154-08d0574c44b8,aa519c6d-c5b7-417d-4ec3-08d1170c20a9) Received-SPF: Pass (protection.outlook.com: domain of umons.ac.be designates 193.190.208.132 as permitted sender) receiver=protection.outlook.com; client-ip=193.190.208.132; helo=smtp.umons.ac.be; X-Forefront-Antispam-Report: CIP:193.190.208.132; CTRY:BE; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(10009020)(6009001)(438002)(51704005)(24454002)(6806004)(16796002)(36756003)(87936001)(57986006)(74482002)(46102003)(107886001)(76506005)(2950100001)(50226001)(23676002)(50466002)(226693001)(92566002)(76176999)(62966003)(77156002)(50986999)(106466001)(86362001)(103116003); DIR:OUT; SFP:1101; SCL:1; SRVR:AMSPR05MB518; H:smtp.umons.ac.be; FPR:; SPF:Pass; MLV:sfv; LANG:en; X-Microsoft-Antispam: UriScan:; X-Microsoft-Antispam: BCL:0;PCL:0;RULEID:;SRVR:AMSPR05MB518; X-Exchange-Antispam-Report-Test: UriScan:; X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(601004); SRVR:AMSPR05MB518; X-Forefront-PRVS: 0475418F50 X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(401004)(400005); SRVR:AMSPR05MB518; X-MS-Exchange-CrossTenant-OriginalArrivalTime: 02 Feb 2015 00:45:57.7295 (UTC) X-MS-Exchange-CrossTenant-Id: 5afe0b00-7697-4969-b663-5eab37d5f47e X-MS-Exchange-CrossTenant-OriginalAttributedTenantConnectingIp: TenantId=5afe0b00-7697-4969-b663-5eab37d5f47e; Ip=[193.190.208.132] X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem X-MS-Exchange-Transport-CrossTenantHeadersStamped: AMSPR05MB518 Subject: Re: [MirageOS-devel] Error handling in Mirage - request for comments! X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org T24gU2F0LCAzMSBKYW4gMjAxNSAyMTowNzoyMiArMDAwMCwgVGhvbWFzIExlb25hcmQgd3JvdGU6 Cj4gCj4gW+KApl0gQnV0IHRoZSByZWFsIHByb2JsZW0gaGVyZSBpcyB0aGF0IGJ5IG1ha2luZyBl eGNlcHRpb25zIGZhdGFsIHdlCj4gdHVybiBldmVyeSBleGNlcHRpb24gdXNlZCBpbiBleGlzdGlu ZyBPQ2FtbCBjb2RlIGludG8gYSBzZWN1cml0eQo+IHZ1bG5lcmFiaWxpdHkuIFvigKZdCgpTaW5j ZSBPQ2FtbCBzdXBwb3J0cyBleGNlcHRpb25zLCBJIHRoaW5rIHRoZXJlIGlzIG5vIGRvdWJ0IHRo YXQgd2UKbXVzdCBoYW5kbGUgdGhlbSBlZmZlY3RpdmVseSDigJQgbm90IGp1c3Qgd2lwZSB0aGVt IHVuZGVyIHRoZSBjYXJwZXQgYW5kCmxldCB0aGVtIGFib3J0IHRoZSBwcm9ncmFtL3VuaWtlcm5l bC4gIElkZWFsbHkgTHd0IHNob3VsZCBkZWFsCnNlbnNpYmx5IHdpdGggZXhjZXB0aW9ucyAoYW5k IHRoZSBkaXNjdXNzaW9uIHNlZW1zIHRvIGltcGx5IHRoZXJlIGFyZQphcmVhcyBvZiBpbXByb3Zl bWVudCDigJQgYnV0IGl0IGlzIHVuY2xlYXIgdG8gbWUgaG93IHlvdSBjYW4gZG8gdGhhdAplZmZp Y2llbnRseSB3aXRob3V0IHVzaW5nIGEgdHJ5IGJsb2NrIGluIGFsbCBiaW5kcykuICBTbyBpdCBz ZWVtcyB0bwptZSB0aGF0IHRoZXJlIGlzIGxpdHRsZSBjaG9pY2UgYnV0IHRoYXQgZXhjZXB0aW9u cyBiZSB0dXJuZWQgaW50bwpmYWlsZWQgdGhyZWFkcyBhdCB0aGUgcHJvZ3JhbW1lcidzIGRpc2Ny ZXRpb24uICBNYXliZSDigJxydW7igJ0gc2hvdWxkIGJlCnJlbmFtZWQg4oCccnVuX2V4buKAnSB0 byBpbmRpY2F0ZSB0aGF0IGV4Y2VwdGlvbnMgcGFzcyB0aHJvdWdoIGFuZCB0aGUKInNhZmUiIHJ1 biBzaG91bGQgYmUKCiAgICBydW4gOiAodW5pdCAtPiAnYSB0KSAtPiBbYE9rIG9mICdhIHwgYEV4 biBvZiBleG5dCgpBcyBpdCB3YXMgcHJldmlvdXNseSBtZW50aW9uZWQsIEkgYWxzbyB0aGluayB0 aGF0IHVzaW5nICJlcnJvci1hd2FyZQpyZXR1cm4gdHlwZXMiIHNob3VsZCBiZSBsaW1pdGVkIG1v c3RseSB0byBjYXNlcyB3aGVyZSB0aGUgZmFpbHVyZSBpcwpub3QgcmVhbGx5IGFuIGVycm9yIGFu ZCBzaG91bGQgYmUgZGVhbHQgd2l0aCBpbW1lZGlhdGVseSBieSB0aGUKY2FsbGVyLiAgQW5kIEkg YWdyZWUgd2l0aCBUaG9tYXMgd2hlbiBoZSBzYXlzIHRoYXQgb3ZlcnVzaW5nIHRoaXMKc2NoZW1l IHdpbGwgcmVzdWx0IGluIGVycm9ycyBiZWluZyBpZ25vcmVkIGluc3RlYWQgb2YgYmVpbmcgZGVh bHQgd2l0aApwcm9wZXJseS4KClRoZXJlIGFyZSBob3dldmVyIGVycm9ycyB0aGF0IHlvdSB3YW50 IHRvIG1hbmRhdGUgdGhhdCB0aGV5IGFyZSBkZWFsdAp3aXRoIGJ1dCBub3QgbmVjZXNzYXJpbHkg YXQgdGhlIGNhbGxpbmcgcG9pbnQuICBBIHR5cGljYWwgZXhhbXBsZSB0bwptZSBpcyDigJxyZWFk 4oCdIGJlY2F1c2UgaXQgaXMgb2Z0ZW4gbXVjaCAiaGlnaGVyIiBpbiB0aGUgcHJvZ3JhbSB0aGF0 IGFuCmFwcHJvcHJpYXRlIHJlc3BvbnNlIHRvIGEgZmFpbGluZyByZWFkIGNhbiBiZSBtYWRlIOKA lCB0aGlzIGlzIGltcG9ydGFudApmb3IgbGlicmFyaWVzIHRoYXQgd2lsbCBwb3N0LXByb2Nlc3Mg 4oCccmVhZOKAnXMgYW5kIHdpbGwgaGF2ZSBubyBpZGVhCndoYXQgdG8gZG8gaWYg4oCccmVhZOKA nSBmYWlscy4KClRvIG1ha2UgdGhlIGRpc2N1c3Npb24gYSBiaXQgbW9yZSBjb25jcmV0ZSwgaGVy ZSBpcyBhIHNpZ25hdHVyZQppbGx1c3RyYXRpbmcgaG93IHRoZXNlIGxhdHRlciBlcnJvcnMgbWF5 IGJlIGhhbmRsZWQ6CgogICAgdHlwZSAoJ2EsICdiKSB0CiAgICB2YWwgcmV0dXJuIDogJ2EgLT4g KCdhLCAnYikgdAogICAgdmFsICggPj49ICkgOiAoJ2EsICdiKSB0IC0+ICgnYSAtPiAoJ2MsICdi KSB0KSAtPiAoJ2MsICdiKSB0CiAgICB2YWwgZmFpbCA6IChbPiBdIGFzICdiKSAtPiAoXywgJ2Ip IHQKICAgIHZhbCBmYWlsX2V4biA6IGV4biAtPiAoJ2EsICdiKSB0CiAgICB2YWwgY2F0Y2ggOiAo J2EsICdiKSB0IC0+ICgnYiAtPiAoJ2EsICdjKSB0KSAtPiAoJ2EsICdjKSB0CiAgICB2YWwgY2F0 Y2hfZXhuIDogP2V4bjooZXhuIC0+ICgnYSwgJ2IpIHQpIC0+ICh1bml0IC0+ICgnYSwgJ2IpIHQp IC0+ICgnYSwgJ2IpIHQKICAgIHZhbCBydW4gOiAodW5pdCAtPiAoJ2EsIHVuaXQpIHQpIC0+IFtg T2sgb2YgJ2EgfCBgRXhuIG9mIGV4bl0KICAgIHZhbCBydW5fZXhuIDogKCdhLCB1bml0KSB0IC0+ ICdhCgpTb21lIHJlbWFya3MuICBUaGUg4oCcZmFpbOKAnSBmdW5jdGlvbiBpbXBvc2VzIHRoYXQg dGhlIGVycm9ycyBhcmUgbGFiZWxlZAp3aXRoIHBvbHltb3JwaGljIHZhcmlhbnRzLiAgU2luY2Ug dGhlc2UgYXJlIG5vdCBxdWFsaWZpZWQgYnkgdGhlCm1vZHVsZSBhbmQgdG8gYWxsb3cgZ2VuZXJp YyB0cmVhdG1lbnQsIGEgZ29vZCBpZGlvbSB3b3VsZCBwcm9iYWJseSBiZQp0byB1c2Ugc29tZXRo aW5nIGxpa2Ug4oCcYFggb2YgWC5lcnLigJ0gd2hlcmUg4oCcYFjigJ0gaXMgc3VmZmljaWVudGx5 CmV4cGxpY2l0IGFuZCDigJxYLmVycuKAnSBlbnVtZXJhdGVzIHRoZSBwb3NzaWJsZSBmYWlsdXJl cyBmb3IgdGhlIG1vZHVsZQrigJxY4oCdLiAgVGhlIGZ1bmN0aW9uIOKAnGNhdGNoX2V4biBm4oCd IHdpbGwgY2F0Y2ggZXhjZXB0aW9ucyByYWlzZWQgYnkg4oCcZuKAnQphcyB3ZWxsIGFzIGZhaWxl ZC10aHJlYWRzIG9uZXMgKGJ5IGRlZmF1bHQsIG9ubHkgdHVybmluZyBhbGwgZXhjZXB0aW9ucwpp bnRvIGZhaWxpbmcgdGhyZWFkIG9uZXMpLiAgVGhlIHVzZSBvZiDigJx1bml04oCdIGluIOKAnCgn YSwgdW5pdCkgdOKAnSBlbnN1cmVzCnRoYXQgdGhlIHRocmVhZCBpcyBvZiB0eXBlIOKAnChfLCAn YikgdOKAnSDigJQgaS5lLiB0aGF0IGFsbCBlcnJvcnMgaGF2ZQpiZWVuIGRlYWx0IHdpdGgg4oCU IHNvIGl0IGNhbiBiZSB1bmlmaWVkIHdpdGggYSBub24tcG9seW1vcnBoaWMgdmFyaWFudAp0eXBl LgoKVGhpcyBpcyBzaW1pbGFyIHRvIGRlY2xhcmluZwoKICAgIHR5cGUgKCdhLCAnYikgdCA9ICgn YSwgJ2IpIFJlc3VsdC50IEx3dC50CgpleGNlcHQgdGhhdCBvbmUgY2Fubm90IGRpdGNoIHRoZSDi gJxSZXN1bHQudOKAnSAoYW5kIG9uZSBhdm9pZHMgMQppbmRpcmVjdGlvbiBwZXIgYmluZCkuCgpV bmZvcnR1bmF0ZWx5LCBpdCBpcyBzb21lIHdvcmsgdG8gZW5zdXJlIHRoYXQgdGhlIGNvbXBpbGVy IHVuZGVyc3RhbmRzCnRoYXQgYWxsIGVycm9ycyB3ZXJlIGRlYWx0IHdpdGguICBDb25zaWRlcgoK ICAgIGxldCBtMSA9IGZhaWwoYFggMSkgPj49IGZ1biB4IC0+IGZhaWwgYFkKClRoZW4KCiAgICBs ZXQgbTIgPSBjYXRjaCBtMSAoZnVuY3Rpb24gYFggeCAtPiByZXR1cm4geAogICAgICAgICAgICAg ICAgICAgICAgICAgICAgICB8IGUgLT4gZmFpbCBlKQoKd2lsbCBub3QgZG8sIHlvdSBoYXZlIHRv IHdyaXRlCgogICAgbGV0IG0yID0gY2F0Y2ggbTEgKGZ1bmN0aW9uIGBYIHggLT4gcmV0dXJuIHgK ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgfCBgWSBhcyBlIC0+IGZhaWwgZSkKCnRvIG1h a2Ugc3VyZSDigJxtMuKAnSBzaG93cyB0aGF0IOKAnGBY4oCdIGlzIG5vIGxvbmdlciBhbiBpc3N1 ZS4gIFRodXMKZGVmaW5pbmcgZ29vZCB0eXBlcyB0byB1c2Ug4oCcI3R5cGXigJ0gaXMgaW1wb3J0 YW50LgoKTXkgMC4wMuKCrCwKQy4KCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fCk1pcmFnZU9TLWRldmVsIG1haWxpbmcgbGlzdApNaXJhZ2VPUy1kZXZlbEBs aXN0cy54ZW5wcm9qZWN0Lm9yZwpodHRwOi8vbGlzdHMueGVucHJvamVjdC5vcmcvY2dpLWJpbi9t YWlsbWFuL2xpc3RpbmZvL21pcmFnZW9zLWRldmVsCg== From mirageos-devel-bounces@lists.xenproject.org Mon Feb 02 09:44:20 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 02 Feb 2015 09:44:20 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YIDYE-0004nG-SS; Mon, 02 Feb 2015 09:44:14 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YIDYD-0004nB-2o for mirageos-devel@lists.xenproject.org; Mon, 02 Feb 2015 09:44:13 +0000 Received: from [85.158.143.35] by server-2.bemta-4.messagelabs.com id DF/28-02749-CE64FC45; Mon, 02 Feb 2015 09:44:12 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-14.tower-21.messagelabs.com!1422870251!11883175!1 X-Originating-IP: [74.125.82.51] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 32188 invoked from network); 2 Feb 2015 09:44:11 -0000 Received: from mail-wg0-f51.google.com (HELO mail-wg0-f51.google.com) (74.125.82.51) by server-14.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 2 Feb 2015 09:44:11 -0000 Received: by mail-wg0-f51.google.com with SMTP id k14so37517045wgh.10 for ; Mon, 02 Feb 2015 01:44:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=aI4A/JibfXdtS7VrVPDc3CpC5DC2DyhG3koet/QNo/Y=; b=xbZAiHSPHY3nwg+caKwzyph5B6MDPlvrUkiyOsqLcpFXNSlvJf0H/5jE+KFOGQ/5zM 0N3qiuWDhbOh6P25g7GsViLqgh8w/OQRC/dHNMH+I3kl4b94KCWce9XnHjtZxdT4CE53 jvPCoUgBa55QPrOMMBbUovKGuhJEj8fKbeA/tf+P5SitLmQgB7iiL5vx4YEpBQZEC8WQ aVshVRGCStymLdrQDdOTqqRbpTqBzll6NrXaU95jUJKT9+bGY8HAMBIxTjNo5iCBXPLu /aovgVkQBhx4lFltNf2rm3caJa9b0+mLVmem6/zECeBiD6d4AM7kVok1f3mflpP0OLIR hxoA== X-Received: by 10.194.189.77 with SMTP id gg13mr41500746wjc.81.1422870251032; Mon, 02 Feb 2015 01:44:11 -0800 (PST) Received: from dhcp-172-17-162-242.eduroam.wireless.private.cam.ac.uk (global-1-27.nat.csx.cam.ac.uk. [131.111.184.27]) by mx.google.com with ESMTPSA id hl1sm27035159wjc.18.2015.02.02.01.44.08 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 02 Feb 2015 01:44:09 -0800 (PST) Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\)) From: Thomas Gazagnaire In-Reply-To: <874mr6ag4c.fsf@gmail.com> Date: Mon, 2 Feb 2015 09:44:09 +0000 Message-Id: <07E83A7F-D277-40BE-B466-9C0CE1493621@gazagnaire.org> References: <2126FC5196B044EC8BDA0E07CB51089F@erratique.ch> <874mr6ag4c.fsf@gmail.com> To: Thomas Leonard X-Mailer: Apple Mail (2.1993) Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Error handling in Mirage - request for comments! X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org SGksCgpUaGFua3MgVGhvbWFzIGZvciB5b3VyIHByb3Bvc2FsIQoKPiBJdCBkb2VzIHRha2UgZGlz Y2lwbGluZSwgYXMgVGhvbWFzIHBvaW50ZWQgb3V0LCBidXQgdGhhdCBpcyBhdCBsZWFzdCBvbgo+ IHRoZSBkZXZlbG9wZXIgdG8gZ2V0IHJpZ2h0LiAgVW5sZXNzIGV4Y2VwdGlvbnMgY2FuIGJlIG1h ZGUgdG8gbWFrZSBzZW5zZQo+IGluc2lkZSB0aGUgY29uY3VycmVuY3kgZnJhbWV3b3JrLCBJIHRo aW5rIGl0IGlzIGltcG9ydGFudCB0byBhdm9pZCB0aGVtLgoKSSB0aGluayB0aGF0J3Mgb25lIG9m IHRoZSBtYWluIGFyZ3VtZW50IGhlcmUuIFJlYXNvbmluZyBhYm91dCBjb25jdXJyZW5jeSB3aXRo IGV4Y2VwdGlvbnMgaXMgaGFyZCwgc28gaXQncyBiZXR0ZXIgdG8gYmUgdmVyeSBleHBsaWNpdCBh Ym91dCB0aGVtIChhbmQgaXQgZG9lc24ndCBoZWxwIHRoYXQgbmF0aXZlIGJhY2t0cmFjZXMgZG9u J3Qgd29yayBhdCBhbGwgd2l0aCBsd3QpLiBUaGF0J3Mgd2h5IEkgdGVuZCB0byBsaWtlIHRoZSBl eHBsaWNpdCBFcnJvciBtb25hZCBtb3JlIGFuZCBtb3JlLCBzbyBJIHdvdWxkIGJlIG1vcmUgaW4g ZmF2b3VyIG9mIGltcHJvdmluZyAob3IgY3JlYXRpbmcpIHRoZSBtaXJhZ2UgbGlicmFyeSBmb3Ig aGFuZGxpbmcgZXJyb3JzIHVzaW5nIHBvbHltb3JwaGljIHZhcmlhbnRzIGluc3RlYWQgb2YgY2hh bmdpbmcgZXZlcnl0aGluZyBpbnRvIGltcGxpY2l0IGV4Y2VwdGlvbnMgKGJ1dCBhcyB1c3VhbCwg ZXhjZXB0aW9uYWwgZXZlbnRzIHNob3VsZCByZW1haW5zIGV4Y2VwdGlvbnM6IGZvciBpbnN0YW5j ZSByZXF1aXJpbmcgYSBgc3RyaW5nX29mX2Vycm9yYCB3YXMgYSBnb29kIG1vdmUgaW4gdGhhdCBk aXJlY3Rpb24gKHNvIHRoYXQgdGhlIG1pcmFnZSB0b29sIGp1c3Qgd29uJ3QgdGhyb3cgZXJyb3Jz IGF3YXkgYW5kIGRpc3BsYXkgZ2VuZXJpYyBtZXNzYWdlcykuCgpBcyBhIHNpZGUtbm90ZTogd2Ug YXJlIG1vdmluZyB0b3dhcmRzIGEgd29ybGQgd2l0aG91dCBjYW1scDQsIHNvIHdlIHNob3VsZCBu b3QgcmVseSBvbiB0cnlfbHd0OiB0aGlzIG1lYW5zIHRoYXQgdGhlIHVzZXIgc2hvdWxkIGNhbGwg THd0LmNhdGNoIGluc3RlYWQsIHdoaWNoIGlzIGEgYml0IG1vcmUgaGVhdnktd2VpZ2h0IHRvIHVz ZSBhbmQgaGF2ZSBhbiBpbXBhY3Qgb24gYmFja3RyYWNlcyAoYW5kIEknbSBub3Qgc3VyZSB0aGF0 IHVzaW5nIHBweCB3aWxsIGhlbHAgYSBsb3QsIEkgcmF0aGVyIG1vdmUgYXdheSBmcm9tIGFueSBw cmUtcHJvY2Vzc2luZyB0b29scyBmb3Igbm93IG9uIGlmIHBvc3NpYmxlKS4KCkkgbmVlZCBhIGJp dCBtb3JlIHRpbWUgdG8gZGlnZXN0IHlvdXIgcHJvcG9zYWwgYW5kIHRoZSBpbXBhY3QgaXQgd2ls bCBoYXZlIG9uIGZ1dHVyZSBtaXJhZ2UgdXNlcnMsIHRoYW5rcyBhbnl3YXkgZm9yIHN0YXJ0aW5n IHRoZSBkaXNjdXNzaW9uIHdpdGggYSBjb25jcmV0ZSBwbGFuIQoKVGhvbWFzCgo+PiBMZSB2ZW5k cmVkaSwgMzAgamFudmllciAyMDE1IMOgIDE2OjUzLCBUaG9tYXMgTGVvbmFyZCBhIMOpY3JpdCA6 Cj4+IAo+Pj4gV2hhdCBwcm9ibGVtcyBkbyB5b3Ugc2VlIGluIEx3dCdzIGVycm9yIGhhbmRsaW5n Pwo+Pj4gCj4+IAo+PiBbLi4uXSAgCj4+IAo+Pj4gSXNuJ3QgTHd0IGFscmVhZHkgYW4gZXJyb3Ig bW9uYWQ/IENhbiB5b3UgZGVmaW5lICJ3ZWxsIHByaW5jaXBsZWQiIGhlcmU/Cj4+IAo+PiAKPj4g SSBtZWFudCB0aGUgd2F5IHRoZXkgZGVhbCB3aXRoIGV4Y2VwdGlvbnMgKGFuZCBjYW5jZWxhdGlv bikuIEkgdGhpbmsgdGhleSBzaG91bGQgaGF2ZSBsaWZ0ZWQgdGhlIGVycm9yIGhhbmRsaW5nIHRv IHZhbHVlIGxhbmQgYW5kIHRvbGQgdXNlcnMKPj4gbm90IHRvIHVzZSBleGNlcHRpb25zIChjYXRj aCB0aGVtIGJldHdlZW4geWllbGRzIGlmIHlvdSBuZWVkIHRvIHVzZSB0aGVtIG9yIHVzZSBjb2Rl IHRoYXQgdXNlcyB0aGVtKSByYXRoZXIgdGhhbiB0cnkgdG8gY29wZSB3aXRoCj4+IHRoZW0uIEJl c2lkZXMsIHRoZSBmYWN0IHRoYXQgdGhleSB1c2UgZXhjZXB0aW9ucyB0byBwZXJmb3JtIGNhbmNl bGxhdGlvbiBpdHNlbGYgbGVhZHMgdG8gZnVydGhlciBhYnN1cmRpdGllcyAod2hpY2ggc2VlbXMg dG8gaW5kaWNhdGUgdGhhdAo+PiBjYW5jZWxhdGlvbiB3YXMgYWZ0ZXJ0aG91Z2h0LCBidXQgdGhh dCdzIHRoZSBraW5kIG9mIGNvbmNlcHQgeW91IG5lZWQgdGhpbmsgYWJvdXQgZnJvbSBkYXkgMCBp biBhIHN5c3RlbSB0byBnZXQgdG8gc29tZXRoaW5nKSwgYXMgSSB3cm90ZQo+PiBlbHNld2hlcmU6 Cj4+IAo+PiAiTHd0IGhhcyBib3RoIGNhbmNlbGFibGUgYW5kIG5vbi1jYW5jZWxhYmxlIHRocmVh ZHMgYW5kIHVzZXMgYW4gZXhjZXB0aW9uIGZvciB0aHJlYWQgY2FuY2VsbGF0aW9uLiBTb21ldGlt ZXMgdGhpcyBtYXkgbGVhZCB0byBzdXJwcmlzaW5nCj4+IHJlc3VsdHMgZS5nLiBMd3QucGljayBb dCwgdCddIG1heSByZXR1cm4gYSBjYW5jZWxsZWQgdGhyZWFkIGlmIHQgdGVybWluYXRlZCBhbmQg dCcgd2FzIGNhbmNlbGxlZC4iCj4+IAo+PiBMd3QncyBjb21iaW5hdG9yIGFsZ2VicmEgaXMgYnJv a2VuOiBhIGNhbmNlbGxlZCB0aHJlYWQgc2hvdWxkIGJlIGEgbmV1dHJhbCBlbGVtZW50IGZvciBM d3QucGljay4gIAo+PiAKPj4gTXkgcG9pbnQgaGVyZSBpcyB0aGF0IEkgdGhpbmsgbWlyYWdlIHNo b3VsZCBkZWZpbmUgaXQncyBvd24gZXJyb3IgbW9uYWQgYW5kIHNvbHZlIGVycm9yIGhhbmRsaW5n IGluIHZhbHVlIGxhbmQgKHcuci50LiB0aGUgY29uY3VycmVuY3kKPj4gbW9uYWRzKSwgaW5kZXBl bmRlbnRseSBmcm9tIHRoZSBoaWdoZXItbGV2ZWwgY29uY3VycmVuY3kgcHJpbWl0aXZlcyB1c2Vk LiBCeSBwcm92aWRpbmcgYXBwcm9wcmlhdGUgY29tYmluYXRvcnMgYW5kIG90aGVyIHJlc291cmNl IGhvbGRpbmcKPj4gY29tYmluYXRvcnMgdGhhdCBlbnN1cmUgYSByZXNvdXJjZSBpcyBvbmx5IGhl bGQgaW4gYSBnaXZlbiBzY29wZSBhbmQgdGhhdCBpbnRlcmFjdCB3aXRoIHRoYXQgZXJyb3IgbW9u YWQgc28gdGhhdCB3ZSBzaG91bGQgbm90IGV2ZXIgc2VlIHRoYXQKPj4ga2luZCBvZiBob3JyaWJs ZSBjb2RlOgo+PiAKPj4gaHR0cHM6Ly9naXRodWIuY29tL21pcmFnZS9taXJhZ2Utd3d3L3B1bGwv Mjc0L2ZpbGVzI2RpZmYtYWJiOGMwYzYwYzc1MDY1Zjg2ZmYyOTk0MmE0ODNlYzRSODgKPj4gCj4+ IGFuZCBhdXRvbWF0aWNhbGx5IGd1aWRlIHRoZSBwcm9ncmFtbWVyIGluIGRvaW5nIHRoZSByaWdo dCB0aGluZy4KPj4gCj4+PiBJJ2QgYWdyZWUgaWYgdGhhdCB3YXMgImFib3J0IHRoZSBjdXJyZW50 IHRyYW5zYWN0aW9uICh3aGljaCBtYXkgY292ZXIKPj4+IHRoZSB3aG9sZSB1bmlrZXJuZWwpIi4g UmVhbGlzdGljYWxseSwgdGhlcmUgYXJlIGFsd2F5cyBnb2luZyB0byBiZQo+Pj4gZXJyb3IgY29u ZGl0aW9ucyB0aGF0IHJlc3VsdCBpbiBleGNlcHRpb25zIHRoYXQgc2hvdWxkIG5vdCB0ZXJtaW5h dGUKPj4+IGl0IChlLmcuIHJ1bm5pbmcgb3V0IG9mIG1lbW9yeSBzZXJ2aW5nIHJlcXVlc3RzIHNo b3VsZCBvbmx5IGFib3J0IHNvbWUKPj4+IHJlcXVlc3RzLCBldGMpLgo+PiAKPj4gCj4+IFRoZW4g dGhlc2UgdGhpbmdzIHNob3VsZCBub3QgYmUgZXhjZXB0aW9ucyBidXQgYmUgdGhyZWFkZWQgdGhy b3VnaCBhbiBhcHByb3ByaWF0ZSBlcnJvciBtb25hZCBpbiBjb21iaW5hdGlvbiB3aXRoIHJlc291 cmNlIGhvbGRpbmcgY29tYmluYXRvcnMgdG8gY29ycmVjdGx5IHJlbGlucXVpc2ggaGVsZCByZXNv dXJjZXMuICAKPj4gCj4+IAo+Pj4gSWYgSSB1bmRlcnN0YW5kIHlvdXIgcG9zaXRpb246Cj4+PiAK Pj4+IC0gRXZlcnkgZXhjZXB0aW9uIHJhaXNlZCBNVVNUIHRlcm1pbmF0ZSB0aGUgdW5pa2VybmVs LiBUaGlzIGluY2x1ZGVzCj4+PiBvdXQtb2YtbWVtb3J5LCBkaXZpc2lvbi1ieS16ZXJvLCBpbnRf b2Zfc3RyaW5nIG9uIGFuIG91dC1vZi1yYW5nZSBpbnQsCj4+PiBldGMsIGluIGFueSBjb2RlIHBh dGguIEFib3J0aW5nIHRoZSBvcGVyYXRpb24gKGUuZy4gSFRUUCByZXF1ZXN0KSB0aGF0Cj4+PiBj YXVzZWQgdGhlIHByb2JsZW0sIGxvZ2dpbmcgdGhlIGV4Y2VwdGlvbiBhbmQgY29udGludWluZyBp cyBub3QgYW4KPj4+IG9wdGlvbi4KPj4gCj4+IFllcy4gVGhhdCBpcywgYW55dGhpbmcgbm9uIHJl Y292ZXJhYmxlLiBpbnRfb2Zfc3RyaW5nIHNob3VsZCBpbiBmYWN0IG5ldmVyIGhhdmUgcmFpc2Vk IGluIHRoZSBmaXJzdCBwbGFjZSBidXQgaGF2ZSByZXR1cm5lZCBhbiBvcHRpb24gdHlwZS4KPj4g Cj4+PiAtIEl0IGlzIHRoZXJlZm9yZSBhY2NlcHRhYmxlIGZvciBhIG1vZHVsZSB0byBsZWFrIHJl c291cmNlcyBhbmQvb3IKPj4+IGxlYXZlIHRoZSBzeXN0ZW0gaW4gYW4gaW52YWxpZCBzdGF0ZSBp ZiBpdCBpdCByZWNlaXZlcyBhbiBleGNlcHRpb24KPj4+IGZyb20gYW55IGNvZGUgaXQgY2FsbHMu Cj4+IAo+PiBOby4gSWYgeW91IG5lZWQgdG8gcmVjb3ZlciB0aGVuIGRvbid0IHVzZSBleGNlcHRp b25zLiBVc2UgYW4gZXJyb3IgbW9uYWQgYW5kIHJlc291cmNlIGhvbGRpbmcgY29tYmluYXRvcnMu Cj4+IAo+Pj4gSSBkb24ndCB0aGluayBleGNlcHRpb24gc2FmZXR5IGlzIG11Y2ggd29yayBpbiBt b3N0Cj4+PiBjYXNlcyAoSSBhbHdheXMgdHJ5IHRvIGRvIHRoaXMgaW4gbXkgb3duIGNvZGUsIGFu eXdheSkuCj4+IAo+PiAKPj4gSWYgYnkgZXhjZXB0aW9uIHNhZmV0eSB5b3UgbWVhbiwgaGFuZGxp bmcgZXhjZXB0aW9ucyBjb3JyZWN0bHkuIFRoZW4gbm8uIFRoZXJlJ3MgYWx3YXlzIHRoZSBleGNl cHRpb24geW91IGZvcmdldCB0byBoYW5kbGUsIHlvdSBoYXZlIHRvIHB1dAo+PiB0aGUgaGFuZGxl cnMgYXQgdGhlIHJpZ2h0IHBsYWNlLCBhbmQgdGhlcmUncyBhIGxhY2sgb2YgbG9jYWxpdHkgaW4g cHJvZ3JhbSB1bmRlcnN0YW5kaW5nIChiZWNhdXNlIGV4Y2VwdGlvbnMgbWF5IGZsb3cgYmV5b25k IGEgaGFuZGxlciBpZgo+PiBpdCdzIG5vdCBoYW5kbGVkIGJ5IGl0KSB0aGF0J3MgdG9vIG11Y2gg dGhpbmtpbmcgYW5kIHN1YnRlbHRpZXMuIEJlc2lkZXMgdGhlcmUncyBubyBleGhhdXN0aXZlbmVz cyBjaGVjayBmb3IgZXhjZXB0aW9ucy4gVGhhdCdzIHRoZSByZWFzb24KPj4gd2h5IEkgcHJlZmVy IHRvIGhhdmUgYSBtb25hZCB0aGF0IGZvcmNlcyB5b3UgaW50byBkb2luZyB0aGUgcmlnaHQgdGhp bmdzIGJ5IHR5cGUgZGlyZWN0aW9uLgo+PiAKPj4+IEkgd291bGQgaG93ZXZlciByZXBsYWNlIGFs bCB0aGUgbmV0d29yayBjb2RlcyB3aXRoIGEgZ2VuZXJpYwo+Pj4gKGBOZXR3b3JrX2Vycm9yIG9m IGV4biksIHdoZXJlIHRoZSBleG4gbWlnaHQgYmUgZS5nLiBhIFJlZnVzZWQKPj4+IGV4Y2VwdGlv biB3aXRoIG1vcmUgaW5mb3JtYXRpb24gYWJvdXQgd2h5IGl0IHdhcyByZWZ1c2VkLiBUaGlzIG1h a2VzCj4+PiBpdCBlYXN5IGZvciBjYWxsZXJzIHdobyBkb24ndCBjYXJlIHRvIGhhbmRsZSB0aGVt IGFsbCBhdCBvbmNlICh3aXRoCj4+PiBMd3QuZmFpbCksIGFsbG93cyBleHRyYSBuZXR3b3JrIGVy cm9ycyB0byBiZSBhZGRlZCBieSBpbXBsZW1lbnRhdGlvbnMsCj4+PiBhbmQgYWxsb3dzIGF0dGFj aGluZyBtb3JlIGRldGFpbHMgYWJvdXQgdGhlIGNhdXNlcy4KPj4gCj4+IEknbSByZWFsbHkgbm90 IGZvbmQgb2YgdGhpcy4gWW91IGNhbiB1c2Ugb3BlbiBwb2x5bW9ycGhpYyB2YXJpYW50cyBmb3Ig dGhpcyBvciBhIGNsb3NlZCBvbmUgd2l0aCBhIGZldyBrbm93biBjb21tb24gY2FzZXMgYW5kIGEg Y3VzdG9tIG9uZQo+PiB3aXRoIGEgcHJpbnRhYmxlIHVuaXZlcnNhbCB0eXBlLiBCdXQgdGhlbiBp dCBzZWVtcyB5b3UgYXJlIGRlc2lnbmluZyB3aXRoIHRoZSBpZGVhIG9mIHVzaW5nIEx3dCdzIGZh aWxlZCBzdGF0ZSBhcyBhbiBlcnJvciBtZWNoYW5pc20gd2hpY2ggSQo+PiBkaXNhZ3JlZSB3aXRo Lgo+PiAKPj4gQmVzdCwKPj4gCj4+IERhbmllbAo+PiAKPj4gCj4+IAo+PiBfX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwo+PiBNaXJhZ2VPUy1kZXZlbCBtYWls aW5nIGxpc3QKPj4gTWlyYWdlT1MtZGV2ZWxAbGlzdHMueGVucHJvamVjdC5vcmcKPj4gaHR0cDov L2xpc3RzLnhlbnByb2plY3Qub3JnL2NnaS1iaW4vbWFpbG1hbi9saXN0aW5mby9taXJhZ2Vvcy1k ZXZlbAo+IAo+IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f Cj4gTWlyYWdlT1MtZGV2ZWwgbWFpbGluZyBsaXN0Cj4gTWlyYWdlT1MtZGV2ZWxAbGlzdHMueGVu cHJvamVjdC5vcmcKPiBodHRwOi8vbGlzdHMueGVucHJvamVjdC5vcmcvY2dpLWJpbi9tYWlsbWFu L2xpc3RpbmZvL21pcmFnZW9zLWRldmVsCgoKX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX18KTWlyYWdlT1MtZGV2ZWwgbWFpbGluZyBsaXN0Ck1pcmFnZU9TLWRl dmVsQGxpc3RzLnhlbnByb2plY3Qub3JnCmh0dHA6Ly9saXN0cy54ZW5wcm9qZWN0Lm9yZy9jZ2kt YmluL21haWxtYW4vbGlzdGluZm8vbWlyYWdlb3MtZGV2ZWwK From mirageos-devel-bounces@lists.xenproject.org Mon Feb 02 09:44:20 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 02 Feb 2015 09:44:20 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YIDYE-0004nG-SS; Mon, 02 Feb 2015 09:44:14 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YIDYD-0004nB-2o for mirageos-devel@lists.xenproject.org; Mon, 02 Feb 2015 09:44:13 +0000 Received: from [85.158.143.35] by server-2.bemta-4.messagelabs.com id DF/28-02749-CE64FC45; Mon, 02 Feb 2015 09:44:12 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-14.tower-21.messagelabs.com!1422870251!11883175!1 X-Originating-IP: [74.125.82.51] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 32188 invoked from network); 2 Feb 2015 09:44:11 -0000 Received: from mail-wg0-f51.google.com (HELO mail-wg0-f51.google.com) (74.125.82.51) by server-14.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 2 Feb 2015 09:44:11 -0000 Received: by mail-wg0-f51.google.com with SMTP id k14so37517045wgh.10 for ; Mon, 02 Feb 2015 01:44:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=aI4A/JibfXdtS7VrVPDc3CpC5DC2DyhG3koet/QNo/Y=; b=xbZAiHSPHY3nwg+caKwzyph5B6MDPlvrUkiyOsqLcpFXNSlvJf0H/5jE+KFOGQ/5zM 0N3qiuWDhbOh6P25g7GsViLqgh8w/OQRC/dHNMH+I3kl4b94KCWce9XnHjtZxdT4CE53 jvPCoUgBa55QPrOMMBbUovKGuhJEj8fKbeA/tf+P5SitLmQgB7iiL5vx4YEpBQZEC8WQ aVshVRGCStymLdrQDdOTqqRbpTqBzll6NrXaU95jUJKT9+bGY8HAMBIxTjNo5iCBXPLu /aovgVkQBhx4lFltNf2rm3caJa9b0+mLVmem6/zECeBiD6d4AM7kVok1f3mflpP0OLIR hxoA== X-Received: by 10.194.189.77 with SMTP id gg13mr41500746wjc.81.1422870251032; Mon, 02 Feb 2015 01:44:11 -0800 (PST) Received: from dhcp-172-17-162-242.eduroam.wireless.private.cam.ac.uk (global-1-27.nat.csx.cam.ac.uk. [131.111.184.27]) by mx.google.com with ESMTPSA id hl1sm27035159wjc.18.2015.02.02.01.44.08 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 02 Feb 2015 01:44:09 -0800 (PST) Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\)) From: Thomas Gazagnaire In-Reply-To: <874mr6ag4c.fsf@gmail.com> Date: Mon, 2 Feb 2015 09:44:09 +0000 Message-Id: <07E83A7F-D277-40BE-B466-9C0CE1493621@gazagnaire.org> References: <2126FC5196B044EC8BDA0E07CB51089F@erratique.ch> <874mr6ag4c.fsf@gmail.com> To: Thomas Leonard X-Mailer: Apple Mail (2.1993) Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Error handling in Mirage - request for comments! X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org SGksCgpUaGFua3MgVGhvbWFzIGZvciB5b3VyIHByb3Bvc2FsIQoKPiBJdCBkb2VzIHRha2UgZGlz Y2lwbGluZSwgYXMgVGhvbWFzIHBvaW50ZWQgb3V0LCBidXQgdGhhdCBpcyBhdCBsZWFzdCBvbgo+ IHRoZSBkZXZlbG9wZXIgdG8gZ2V0IHJpZ2h0LiAgVW5sZXNzIGV4Y2VwdGlvbnMgY2FuIGJlIG1h ZGUgdG8gbWFrZSBzZW5zZQo+IGluc2lkZSB0aGUgY29uY3VycmVuY3kgZnJhbWV3b3JrLCBJIHRo aW5rIGl0IGlzIGltcG9ydGFudCB0byBhdm9pZCB0aGVtLgoKSSB0aGluayB0aGF0J3Mgb25lIG9m IHRoZSBtYWluIGFyZ3VtZW50IGhlcmUuIFJlYXNvbmluZyBhYm91dCBjb25jdXJyZW5jeSB3aXRo IGV4Y2VwdGlvbnMgaXMgaGFyZCwgc28gaXQncyBiZXR0ZXIgdG8gYmUgdmVyeSBleHBsaWNpdCBh Ym91dCB0aGVtIChhbmQgaXQgZG9lc24ndCBoZWxwIHRoYXQgbmF0aXZlIGJhY2t0cmFjZXMgZG9u J3Qgd29yayBhdCBhbGwgd2l0aCBsd3QpLiBUaGF0J3Mgd2h5IEkgdGVuZCB0byBsaWtlIHRoZSBl eHBsaWNpdCBFcnJvciBtb25hZCBtb3JlIGFuZCBtb3JlLCBzbyBJIHdvdWxkIGJlIG1vcmUgaW4g ZmF2b3VyIG9mIGltcHJvdmluZyAob3IgY3JlYXRpbmcpIHRoZSBtaXJhZ2UgbGlicmFyeSBmb3Ig aGFuZGxpbmcgZXJyb3JzIHVzaW5nIHBvbHltb3JwaGljIHZhcmlhbnRzIGluc3RlYWQgb2YgY2hh bmdpbmcgZXZlcnl0aGluZyBpbnRvIGltcGxpY2l0IGV4Y2VwdGlvbnMgKGJ1dCBhcyB1c3VhbCwg ZXhjZXB0aW9uYWwgZXZlbnRzIHNob3VsZCByZW1haW5zIGV4Y2VwdGlvbnM6IGZvciBpbnN0YW5j ZSByZXF1aXJpbmcgYSBgc3RyaW5nX29mX2Vycm9yYCB3YXMgYSBnb29kIG1vdmUgaW4gdGhhdCBk aXJlY3Rpb24gKHNvIHRoYXQgdGhlIG1pcmFnZSB0b29sIGp1c3Qgd29uJ3QgdGhyb3cgZXJyb3Jz IGF3YXkgYW5kIGRpc3BsYXkgZ2VuZXJpYyBtZXNzYWdlcykuCgpBcyBhIHNpZGUtbm90ZTogd2Ug YXJlIG1vdmluZyB0b3dhcmRzIGEgd29ybGQgd2l0aG91dCBjYW1scDQsIHNvIHdlIHNob3VsZCBu b3QgcmVseSBvbiB0cnlfbHd0OiB0aGlzIG1lYW5zIHRoYXQgdGhlIHVzZXIgc2hvdWxkIGNhbGwg THd0LmNhdGNoIGluc3RlYWQsIHdoaWNoIGlzIGEgYml0IG1vcmUgaGVhdnktd2VpZ2h0IHRvIHVz ZSBhbmQgaGF2ZSBhbiBpbXBhY3Qgb24gYmFja3RyYWNlcyAoYW5kIEknbSBub3Qgc3VyZSB0aGF0 IHVzaW5nIHBweCB3aWxsIGhlbHAgYSBsb3QsIEkgcmF0aGVyIG1vdmUgYXdheSBmcm9tIGFueSBw cmUtcHJvY2Vzc2luZyB0b29scyBmb3Igbm93IG9uIGlmIHBvc3NpYmxlKS4KCkkgbmVlZCBhIGJp dCBtb3JlIHRpbWUgdG8gZGlnZXN0IHlvdXIgcHJvcG9zYWwgYW5kIHRoZSBpbXBhY3QgaXQgd2ls bCBoYXZlIG9uIGZ1dHVyZSBtaXJhZ2UgdXNlcnMsIHRoYW5rcyBhbnl3YXkgZm9yIHN0YXJ0aW5n IHRoZSBkaXNjdXNzaW9uIHdpdGggYSBjb25jcmV0ZSBwbGFuIQoKVGhvbWFzCgo+PiBMZSB2ZW5k cmVkaSwgMzAgamFudmllciAyMDE1IMOgIDE2OjUzLCBUaG9tYXMgTGVvbmFyZCBhIMOpY3JpdCA6 Cj4+IAo+Pj4gV2hhdCBwcm9ibGVtcyBkbyB5b3Ugc2VlIGluIEx3dCdzIGVycm9yIGhhbmRsaW5n Pwo+Pj4gCj4+IAo+PiBbLi4uXSAgCj4+IAo+Pj4gSXNuJ3QgTHd0IGFscmVhZHkgYW4gZXJyb3Ig bW9uYWQ/IENhbiB5b3UgZGVmaW5lICJ3ZWxsIHByaW5jaXBsZWQiIGhlcmU/Cj4+IAo+PiAKPj4g SSBtZWFudCB0aGUgd2F5IHRoZXkgZGVhbCB3aXRoIGV4Y2VwdGlvbnMgKGFuZCBjYW5jZWxhdGlv bikuIEkgdGhpbmsgdGhleSBzaG91bGQgaGF2ZSBsaWZ0ZWQgdGhlIGVycm9yIGhhbmRsaW5nIHRv IHZhbHVlIGxhbmQgYW5kIHRvbGQgdXNlcnMKPj4gbm90IHRvIHVzZSBleGNlcHRpb25zIChjYXRj aCB0aGVtIGJldHdlZW4geWllbGRzIGlmIHlvdSBuZWVkIHRvIHVzZSB0aGVtIG9yIHVzZSBjb2Rl IHRoYXQgdXNlcyB0aGVtKSByYXRoZXIgdGhhbiB0cnkgdG8gY29wZSB3aXRoCj4+IHRoZW0uIEJl c2lkZXMsIHRoZSBmYWN0IHRoYXQgdGhleSB1c2UgZXhjZXB0aW9ucyB0byBwZXJmb3JtIGNhbmNl bGxhdGlvbiBpdHNlbGYgbGVhZHMgdG8gZnVydGhlciBhYnN1cmRpdGllcyAod2hpY2ggc2VlbXMg dG8gaW5kaWNhdGUgdGhhdAo+PiBjYW5jZWxhdGlvbiB3YXMgYWZ0ZXJ0aG91Z2h0LCBidXQgdGhh dCdzIHRoZSBraW5kIG9mIGNvbmNlcHQgeW91IG5lZWQgdGhpbmsgYWJvdXQgZnJvbSBkYXkgMCBp biBhIHN5c3RlbSB0byBnZXQgdG8gc29tZXRoaW5nKSwgYXMgSSB3cm90ZQo+PiBlbHNld2hlcmU6 Cj4+IAo+PiAiTHd0IGhhcyBib3RoIGNhbmNlbGFibGUgYW5kIG5vbi1jYW5jZWxhYmxlIHRocmVh ZHMgYW5kIHVzZXMgYW4gZXhjZXB0aW9uIGZvciB0aHJlYWQgY2FuY2VsbGF0aW9uLiBTb21ldGlt ZXMgdGhpcyBtYXkgbGVhZCB0byBzdXJwcmlzaW5nCj4+IHJlc3VsdHMgZS5nLiBMd3QucGljayBb dCwgdCddIG1heSByZXR1cm4gYSBjYW5jZWxsZWQgdGhyZWFkIGlmIHQgdGVybWluYXRlZCBhbmQg dCcgd2FzIGNhbmNlbGxlZC4iCj4+IAo+PiBMd3QncyBjb21iaW5hdG9yIGFsZ2VicmEgaXMgYnJv a2VuOiBhIGNhbmNlbGxlZCB0aHJlYWQgc2hvdWxkIGJlIGEgbmV1dHJhbCBlbGVtZW50IGZvciBM d3QucGljay4gIAo+PiAKPj4gTXkgcG9pbnQgaGVyZSBpcyB0aGF0IEkgdGhpbmsgbWlyYWdlIHNo b3VsZCBkZWZpbmUgaXQncyBvd24gZXJyb3IgbW9uYWQgYW5kIHNvbHZlIGVycm9yIGhhbmRsaW5n IGluIHZhbHVlIGxhbmQgKHcuci50LiB0aGUgY29uY3VycmVuY3kKPj4gbW9uYWRzKSwgaW5kZXBl bmRlbnRseSBmcm9tIHRoZSBoaWdoZXItbGV2ZWwgY29uY3VycmVuY3kgcHJpbWl0aXZlcyB1c2Vk LiBCeSBwcm92aWRpbmcgYXBwcm9wcmlhdGUgY29tYmluYXRvcnMgYW5kIG90aGVyIHJlc291cmNl IGhvbGRpbmcKPj4gY29tYmluYXRvcnMgdGhhdCBlbnN1cmUgYSByZXNvdXJjZSBpcyBvbmx5IGhl bGQgaW4gYSBnaXZlbiBzY29wZSBhbmQgdGhhdCBpbnRlcmFjdCB3aXRoIHRoYXQgZXJyb3IgbW9u YWQgc28gdGhhdCB3ZSBzaG91bGQgbm90IGV2ZXIgc2VlIHRoYXQKPj4ga2luZCBvZiBob3JyaWJs ZSBjb2RlOgo+PiAKPj4gaHR0cHM6Ly9naXRodWIuY29tL21pcmFnZS9taXJhZ2Utd3d3L3B1bGwv Mjc0L2ZpbGVzI2RpZmYtYWJiOGMwYzYwYzc1MDY1Zjg2ZmYyOTk0MmE0ODNlYzRSODgKPj4gCj4+ IGFuZCBhdXRvbWF0aWNhbGx5IGd1aWRlIHRoZSBwcm9ncmFtbWVyIGluIGRvaW5nIHRoZSByaWdo dCB0aGluZy4KPj4gCj4+PiBJJ2QgYWdyZWUgaWYgdGhhdCB3YXMgImFib3J0IHRoZSBjdXJyZW50 IHRyYW5zYWN0aW9uICh3aGljaCBtYXkgY292ZXIKPj4+IHRoZSB3aG9sZSB1bmlrZXJuZWwpIi4g UmVhbGlzdGljYWxseSwgdGhlcmUgYXJlIGFsd2F5cyBnb2luZyB0byBiZQo+Pj4gZXJyb3IgY29u ZGl0aW9ucyB0aGF0IHJlc3VsdCBpbiBleGNlcHRpb25zIHRoYXQgc2hvdWxkIG5vdCB0ZXJtaW5h dGUKPj4+IGl0IChlLmcuIHJ1bm5pbmcgb3V0IG9mIG1lbW9yeSBzZXJ2aW5nIHJlcXVlc3RzIHNo b3VsZCBvbmx5IGFib3J0IHNvbWUKPj4+IHJlcXVlc3RzLCBldGMpLgo+PiAKPj4gCj4+IFRoZW4g dGhlc2UgdGhpbmdzIHNob3VsZCBub3QgYmUgZXhjZXB0aW9ucyBidXQgYmUgdGhyZWFkZWQgdGhy b3VnaCBhbiBhcHByb3ByaWF0ZSBlcnJvciBtb25hZCBpbiBjb21iaW5hdGlvbiB3aXRoIHJlc291 cmNlIGhvbGRpbmcgY29tYmluYXRvcnMgdG8gY29ycmVjdGx5IHJlbGlucXVpc2ggaGVsZCByZXNv dXJjZXMuICAKPj4gCj4+IAo+Pj4gSWYgSSB1bmRlcnN0YW5kIHlvdXIgcG9zaXRpb246Cj4+PiAK Pj4+IC0gRXZlcnkgZXhjZXB0aW9uIHJhaXNlZCBNVVNUIHRlcm1pbmF0ZSB0aGUgdW5pa2VybmVs LiBUaGlzIGluY2x1ZGVzCj4+PiBvdXQtb2YtbWVtb3J5LCBkaXZpc2lvbi1ieS16ZXJvLCBpbnRf b2Zfc3RyaW5nIG9uIGFuIG91dC1vZi1yYW5nZSBpbnQsCj4+PiBldGMsIGluIGFueSBjb2RlIHBh dGguIEFib3J0aW5nIHRoZSBvcGVyYXRpb24gKGUuZy4gSFRUUCByZXF1ZXN0KSB0aGF0Cj4+PiBj YXVzZWQgdGhlIHByb2JsZW0sIGxvZ2dpbmcgdGhlIGV4Y2VwdGlvbiBhbmQgY29udGludWluZyBp cyBub3QgYW4KPj4+IG9wdGlvbi4KPj4gCj4+IFllcy4gVGhhdCBpcywgYW55dGhpbmcgbm9uIHJl Y292ZXJhYmxlLiBpbnRfb2Zfc3RyaW5nIHNob3VsZCBpbiBmYWN0IG5ldmVyIGhhdmUgcmFpc2Vk IGluIHRoZSBmaXJzdCBwbGFjZSBidXQgaGF2ZSByZXR1cm5lZCBhbiBvcHRpb24gdHlwZS4KPj4g Cj4+PiAtIEl0IGlzIHRoZXJlZm9yZSBhY2NlcHRhYmxlIGZvciBhIG1vZHVsZSB0byBsZWFrIHJl c291cmNlcyBhbmQvb3IKPj4+IGxlYXZlIHRoZSBzeXN0ZW0gaW4gYW4gaW52YWxpZCBzdGF0ZSBp ZiBpdCBpdCByZWNlaXZlcyBhbiBleGNlcHRpb24KPj4+IGZyb20gYW55IGNvZGUgaXQgY2FsbHMu Cj4+IAo+PiBOby4gSWYgeW91IG5lZWQgdG8gcmVjb3ZlciB0aGVuIGRvbid0IHVzZSBleGNlcHRp b25zLiBVc2UgYW4gZXJyb3IgbW9uYWQgYW5kIHJlc291cmNlIGhvbGRpbmcgY29tYmluYXRvcnMu Cj4+IAo+Pj4gSSBkb24ndCB0aGluayBleGNlcHRpb24gc2FmZXR5IGlzIG11Y2ggd29yayBpbiBt b3N0Cj4+PiBjYXNlcyAoSSBhbHdheXMgdHJ5IHRvIGRvIHRoaXMgaW4gbXkgb3duIGNvZGUsIGFu eXdheSkuCj4+IAo+PiAKPj4gSWYgYnkgZXhjZXB0aW9uIHNhZmV0eSB5b3UgbWVhbiwgaGFuZGxp bmcgZXhjZXB0aW9ucyBjb3JyZWN0bHkuIFRoZW4gbm8uIFRoZXJlJ3MgYWx3YXlzIHRoZSBleGNl cHRpb24geW91IGZvcmdldCB0byBoYW5kbGUsIHlvdSBoYXZlIHRvIHB1dAo+PiB0aGUgaGFuZGxl cnMgYXQgdGhlIHJpZ2h0IHBsYWNlLCBhbmQgdGhlcmUncyBhIGxhY2sgb2YgbG9jYWxpdHkgaW4g cHJvZ3JhbSB1bmRlcnN0YW5kaW5nIChiZWNhdXNlIGV4Y2VwdGlvbnMgbWF5IGZsb3cgYmV5b25k IGEgaGFuZGxlciBpZgo+PiBpdCdzIG5vdCBoYW5kbGVkIGJ5IGl0KSB0aGF0J3MgdG9vIG11Y2gg dGhpbmtpbmcgYW5kIHN1YnRlbHRpZXMuIEJlc2lkZXMgdGhlcmUncyBubyBleGhhdXN0aXZlbmVz cyBjaGVjayBmb3IgZXhjZXB0aW9ucy4gVGhhdCdzIHRoZSByZWFzb24KPj4gd2h5IEkgcHJlZmVy IHRvIGhhdmUgYSBtb25hZCB0aGF0IGZvcmNlcyB5b3UgaW50byBkb2luZyB0aGUgcmlnaHQgdGhp bmdzIGJ5IHR5cGUgZGlyZWN0aW9uLgo+PiAKPj4+IEkgd291bGQgaG93ZXZlciByZXBsYWNlIGFs bCB0aGUgbmV0d29yayBjb2RlcyB3aXRoIGEgZ2VuZXJpYwo+Pj4gKGBOZXR3b3JrX2Vycm9yIG9m IGV4biksIHdoZXJlIHRoZSBleG4gbWlnaHQgYmUgZS5nLiBhIFJlZnVzZWQKPj4+IGV4Y2VwdGlv biB3aXRoIG1vcmUgaW5mb3JtYXRpb24gYWJvdXQgd2h5IGl0IHdhcyByZWZ1c2VkLiBUaGlzIG1h a2VzCj4+PiBpdCBlYXN5IGZvciBjYWxsZXJzIHdobyBkb24ndCBjYXJlIHRvIGhhbmRsZSB0aGVt IGFsbCBhdCBvbmNlICh3aXRoCj4+PiBMd3QuZmFpbCksIGFsbG93cyBleHRyYSBuZXR3b3JrIGVy cm9ycyB0byBiZSBhZGRlZCBieSBpbXBsZW1lbnRhdGlvbnMsCj4+PiBhbmQgYWxsb3dzIGF0dGFj aGluZyBtb3JlIGRldGFpbHMgYWJvdXQgdGhlIGNhdXNlcy4KPj4gCj4+IEknbSByZWFsbHkgbm90 IGZvbmQgb2YgdGhpcy4gWW91IGNhbiB1c2Ugb3BlbiBwb2x5bW9ycGhpYyB2YXJpYW50cyBmb3Ig dGhpcyBvciBhIGNsb3NlZCBvbmUgd2l0aCBhIGZldyBrbm93biBjb21tb24gY2FzZXMgYW5kIGEg Y3VzdG9tIG9uZQo+PiB3aXRoIGEgcHJpbnRhYmxlIHVuaXZlcnNhbCB0eXBlLiBCdXQgdGhlbiBp dCBzZWVtcyB5b3UgYXJlIGRlc2lnbmluZyB3aXRoIHRoZSBpZGVhIG9mIHVzaW5nIEx3dCdzIGZh aWxlZCBzdGF0ZSBhcyBhbiBlcnJvciBtZWNoYW5pc20gd2hpY2ggSQo+PiBkaXNhZ3JlZSB3aXRo Lgo+PiAKPj4gQmVzdCwKPj4gCj4+IERhbmllbAo+PiAKPj4gCj4+IAo+PiBfX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwo+PiBNaXJhZ2VPUy1kZXZlbCBtYWls aW5nIGxpc3QKPj4gTWlyYWdlT1MtZGV2ZWxAbGlzdHMueGVucHJvamVjdC5vcmcKPj4gaHR0cDov L2xpc3RzLnhlbnByb2plY3Qub3JnL2NnaS1iaW4vbWFpbG1hbi9saXN0aW5mby9taXJhZ2Vvcy1k ZXZlbAo+IAo+IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f Cj4gTWlyYWdlT1MtZGV2ZWwgbWFpbGluZyBsaXN0Cj4gTWlyYWdlT1MtZGV2ZWxAbGlzdHMueGVu cHJvamVjdC5vcmcKPiBodHRwOi8vbGlzdHMueGVucHJvamVjdC5vcmcvY2dpLWJpbi9tYWlsbWFu L2xpc3RpbmZvL21pcmFnZW9zLWRldmVsCgoKX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX18KTWlyYWdlT1MtZGV2ZWwgbWFpbGluZyBsaXN0Ck1pcmFnZU9TLWRl dmVsQGxpc3RzLnhlbnByb2plY3Qub3JnCmh0dHA6Ly9saXN0cy54ZW5wcm9qZWN0Lm9yZy9jZ2kt YmluL21haWxtYW4vbGlzdGluZm8vbWlyYWdlb3MtZGV2ZWwK From mirageos-devel-bounces@lists.xenproject.org Mon Feb 02 12:30:51 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 02 Feb 2015 12:30:51 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YIG9L-0001pj-5N; Mon, 02 Feb 2015 12:30:43 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YIG9J-0001pe-IP for mirageos-devel@lists.xenproject.org; Mon, 02 Feb 2015 12:30:41 +0000 Received: from [85.158.143.35] by server-2.bemta-4.messagelabs.com id 0E/47-02749-0FD6FC45; Mon, 02 Feb 2015 12:30:40 +0000 X-Env-Sender: talex5@gmail.com X-Msg-Ref: server-7.tower-21.messagelabs.com!1422880239!11916703!1 X-Originating-IP: [209.85.215.54] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23968 invoked from network); 2 Feb 2015 12:30:39 -0000 Received: from mail-la0-f54.google.com (HELO mail-la0-f54.google.com) (209.85.215.54) by server-7.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 2 Feb 2015 12:30:39 -0000 Received: by mail-la0-f54.google.com with SMTP id hv19so40008900lab.13 for ; Mon, 02 Feb 2015 04:30:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=AyjmWIBcnGG0Opo1SpRayyidM66rB3FGu5vPgZa7jkU=; b=GBY+khINrCvETMpKhwrDFzyaA6CTmd3r1DeT+v3V2Ffy6YmCaMUB9uG2iSQxe9x0HH kC3OiPt9KrM9TBG+QGSAyLhXFJO65fGU+EBGzXym7dEJMwdk50MB++oCCRSk999pUdGV +gzN9gDxvIXVmPZCjcuV0XTYVhawVZq78gRCAMOnk3OvVmLG6iQrK2rBN00smfbQDmyM kfCbkDWwxZcHJOEbygXnBUVDH86Bye1IZog6Nq0HgERzZ6zUYx27q2nl5iDyLIdRx3i8 3MMcTiH/a83+Wmm2PPxPAfog9bEbcSi7XguJwT+0mBWZGd4pSYgdcNHnYhlVE+hghX3I kiZg== MIME-Version: 1.0 X-Received: by 10.152.243.44 with SMTP id wv12mr18566492lac.78.1422880239119; Mon, 02 Feb 2015 04:30:39 -0800 (PST) Received: by 10.25.207.206 with HTTP; Mon, 2 Feb 2015 04:30:39 -0800 (PST) In-Reply-To: <20150202.014549.1883720051237442569.Christophe.Troestler@umons.ac.be> References: <20150202.014549.1883720051237442569.Christophe.Troestler@umons.ac.be> Date: Mon, 2 Feb 2015 12:30:39 +0000 Message-ID: From: Thomas Leonard To: Christophe Troestler Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Error handling in Mirage - request for comments! X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org T24gMiBGZWJydWFyeSAyMDE1IGF0IDAwOjQ1LCBDaHJpc3RvcGhlIFRyb2VzdGxlcgo8Q2hyaXN0 b3BoZS5Ucm9lc3RsZXJAdW1vbnMuYWMuYmU+IHdyb3RlOgo+IE9uIFNhdCwgMzEgSmFuIDIwMTUg MjE6MDc6MjIgKzAwMDAsIFRob21hcyBMZW9uYXJkIHdyb3RlOgo+Pgo+PiBb4oCmXSBCdXQgdGhl IHJlYWwgcHJvYmxlbSBoZXJlIGlzIHRoYXQgYnkgbWFraW5nIGV4Y2VwdGlvbnMgZmF0YWwgd2UK Pj4gdHVybiBldmVyeSBleGNlcHRpb24gdXNlZCBpbiBleGlzdGluZyBPQ2FtbCBjb2RlIGludG8g YSBzZWN1cml0eQo+PiB2dWxuZXJhYmlsaXR5LiBb4oCmXQo+Cj4gU2luY2UgT0NhbWwgc3VwcG9y dHMgZXhjZXB0aW9ucywgSSB0aGluayB0aGVyZSBpcyBubyBkb3VidCB0aGF0IHdlCj4gbXVzdCBo YW5kbGUgdGhlbSBlZmZlY3RpdmVseSDigJQgbm90IGp1c3Qgd2lwZSB0aGVtIHVuZGVyIHRoZSBj YXJwZXQgYW5kCj4gbGV0IHRoZW0gYWJvcnQgdGhlIHByb2dyYW0vdW5pa2VybmVsLiAgSWRlYWxs eSBMd3Qgc2hvdWxkIGRlYWwKPiBzZW5zaWJseSB3aXRoIGV4Y2VwdGlvbnMgKGFuZCB0aGUgZGlz Y3Vzc2lvbiBzZWVtcyB0byBpbXBseSB0aGVyZSBhcmUKPiBhcmVhcyBvZiBpbXByb3ZlbWVudCDi gJQgYnV0IGl0IGlzIHVuY2xlYXIgdG8gbWUgaG93IHlvdSBjYW4gZG8gdGhhdAo+IGVmZmljaWVu dGx5IHdpdGhvdXQgdXNpbmcgYSB0cnkgYmxvY2sgaW4gYWxsIGJpbmRzKS4KCkx3dCBhbHJlYWR5 IHB1dHMgYSB0cnkgYmxvY2sgaW4gYWxsIChzbGVlcGluZykgYmluZHMsIHNvIHRoaXMgaXMKaGFu ZGxlZCBmb3IgeW91OgoKbGV0IGJpbmQgdCBmID0KICBsZXQgdCA9IHJlcHIgdCBpbgogIG1hdGNo IHQuc3RhdGUgd2l0aAogICAgfCBSZXR1cm4gdiAtPgogICAgICAgIGYgdgogICAgfCBGYWlsIF8g YXMgc3RhdGUgLT4KICAgICAgICB0aHJlYWQgeyBzdGF0ZSB9CiAgICB8IFNsZWVwIHNsZWVwZXIg LT4KICAgICAgICBsZXQgcmVzID0gdGVtcCB0IGluCiAgICAgICAgbGV0IGRhdGEgPSAhY3VycmVu dF9kYXRhIGluCiAgICAgICAgYWRkX2ltbXV0YWJsZV93YWl0ZXIgc2xlZXBlcgogICAgICAgICAg KGZ1bmN0aW9uCiAgICAgICAgICAgICB8IFJldHVybiB2IC0+IGN1cnJlbnRfZGF0YSA6PSBkYXRh OyBjb25uZWN0IHJlcyAodHJ5IGYgdgp3aXRoIGV4biAtPiBmYWlsIGV4bikKICAgICAgICAgICAg IHwgRmFpbCBfIGFzIHN0YXRlIC0+IGZhc3RfY29ubmVjdCByZXMgc3RhdGUKICAgICAgICAgICAg IHwgXyAtPiBhc3NlcnQgZmFsc2UpOwogICAgICAgIHJlcwoKPiBTbyBpdCBzZWVtcyB0bwo+IG1l IHRoYXQgdGhlcmUgaXMgbGl0dGxlIGNob2ljZSBidXQgdGhhdCBleGNlcHRpb25zIGJlIHR1cm5l ZCBpbnRvCj4gZmFpbGVkIHRocmVhZHMgYXQgdGhlIHByb2dyYW1tZXIncyBkaXNjcmV0aW9uLiAg TWF5YmUg4oCccnVu4oCdIHNob3VsZCBiZQo+IHJlbmFtZWQg4oCccnVuX2V4buKAnSB0byBpbmRp Y2F0ZSB0aGF0IGV4Y2VwdGlvbnMgcGFzcyB0aHJvdWdoIGFuZCB0aGUKPiAic2FmZSIgcnVuIHNo b3VsZCBiZQo+Cj4gICAgIHJ1biA6ICh1bml0IC0+ICdhIHQpIC0+IFtgT2sgb2YgJ2EgfCBgRXhu IG9mIGV4bl0KPgo+IEFzIGl0IHdhcyBwcmV2aW91c2x5IG1lbnRpb25lZCwgSSBhbHNvIHRoaW5r IHRoYXQgdXNpbmcgImVycm9yLWF3YXJlCj4gcmV0dXJuIHR5cGVzIiBzaG91bGQgYmUgbGltaXRl ZCBtb3N0bHkgdG8gY2FzZXMgd2hlcmUgdGhlIGZhaWx1cmUgaXMKPiBub3QgcmVhbGx5IGFuIGVy cm9yIGFuZCBzaG91bGQgYmUgZGVhbHQgd2l0aCBpbW1lZGlhdGVseSBieSB0aGUKPiBjYWxsZXIu ICBBbmQgSSBhZ3JlZSB3aXRoIFRob21hcyB3aGVuIGhlIHNheXMgdGhhdCBvdmVydXNpbmcgdGhp cwo+IHNjaGVtZSB3aWxsIHJlc3VsdCBpbiBlcnJvcnMgYmVpbmcgaWdub3JlZCBpbnN0ZWFkIG9m IGJlaW5nIGRlYWx0IHdpdGgKPiBwcm9wZXJseS4KPgo+IFRoZXJlIGFyZSBob3dldmVyIGVycm9y cyB0aGF0IHlvdSB3YW50IHRvIG1hbmRhdGUgdGhhdCB0aGV5IGFyZSBkZWFsdAo+IHdpdGggYnV0 IG5vdCBuZWNlc3NhcmlseSBhdCB0aGUgY2FsbGluZyBwb2ludC4gIEEgdHlwaWNhbCBleGFtcGxl IHRvCj4gbWUgaXMg4oCccmVhZOKAnSBiZWNhdXNlIGl0IGlzIG9mdGVuIG11Y2ggImhpZ2hlciIg aW4gdGhlIHByb2dyYW0gdGhhdCBhbgo+IGFwcHJvcHJpYXRlIHJlc3BvbnNlIHRvIGEgZmFpbGlu ZyByZWFkIGNhbiBiZSBtYWRlIOKAlCB0aGlzIGlzIGltcG9ydGFudAo+IGZvciBsaWJyYXJpZXMg dGhhdCB3aWxsIHBvc3QtcHJvY2VzcyDigJxyZWFk4oCdcyBhbmQgd2lsbCBoYXZlIG5vIGlkZWEK PiB3aGF0IHRvIGRvIGlmIOKAnHJlYWTigJ0gZmFpbHMuCgpZZXMsIHRoaXMgaXMgYSBjYXNlIHdo ZXJlIHlvdSBtaWdodCB3YW50IGFuIE9yX2Vycm9yLnQgdGhyZWFkZWQKdGhyb3VnaCBldmVyeXRo aW5nLiBPciwgaXQgbWlnaHQgYmUgZWFzaWVyIHRvIHdyYXAgdGhlIHdob2xlIHRoaW5nIHNvCnRo YXQgYW55IGVycm9yIGNvZGUgcmV0dXJuZWQgYnkgdGhlIHJlYWQgaXMgdGhyb3duIGFuZCB0aGVu IGNhdWdodAphZ2Fpbi4KCj4gVG8gbWFrZSB0aGUgZGlzY3Vzc2lvbiBhIGJpdCBtb3JlIGNvbmNy ZXRlLCBoZXJlIGlzIGEgc2lnbmF0dXJlCj4gaWxsdXN0cmF0aW5nIGhvdyB0aGVzZSBsYXR0ZXIg ZXJyb3JzIG1heSBiZSBoYW5kbGVkOgo+Cj4gICAgIHR5cGUgKCdhLCAnYikgdAo+ICAgICB2YWwg cmV0dXJuIDogJ2EgLT4gKCdhLCAnYikgdAo+ICAgICB2YWwgKCA+Pj0gKSA6ICgnYSwgJ2IpIHQg LT4gKCdhIC0+ICgnYywgJ2IpIHQpIC0+ICgnYywgJ2IpIHQKPiAgICAgdmFsIGZhaWwgOiAoWz4g XSBhcyAnYikgLT4gKF8sICdiKSB0Cj4gICAgIHZhbCBmYWlsX2V4biA6IGV4biAtPiAoJ2EsICdi KSB0Cj4gICAgIHZhbCBjYXRjaCA6ICgnYSwgJ2IpIHQgLT4gKCdiIC0+ICgnYSwgJ2MpIHQpIC0+ ICgnYSwgJ2MpIHQKPiAgICAgdmFsIGNhdGNoX2V4biA6ID9leG46KGV4biAtPiAoJ2EsICdiKSB0 KSAtPiAodW5pdCAtPiAoJ2EsICdiKSB0KSAtPiAoJ2EsICdiKSB0Cj4gICAgIHZhbCBydW4gOiAo dW5pdCAtPiAoJ2EsIHVuaXQpIHQpIC0+IFtgT2sgb2YgJ2EgfCBgRXhuIG9mIGV4bl0KPiAgICAg dmFsIHJ1bl9leG4gOiAoJ2EsIHVuaXQpIHQgLT4gJ2EKPgo+IFNvbWUgcmVtYXJrcy4gIFRoZSDi gJxmYWls4oCdIGZ1bmN0aW9uIGltcG9zZXMgdGhhdCB0aGUgZXJyb3JzIGFyZSBsYWJlbGVkCj4g d2l0aCBwb2x5bW9ycGhpYyB2YXJpYW50cy4gIFNpbmNlIHRoZXNlIGFyZSBub3QgcXVhbGlmaWVk IGJ5IHRoZQo+IG1vZHVsZSBhbmQgdG8gYWxsb3cgZ2VuZXJpYyB0cmVhdG1lbnQsIGEgZ29vZCBp ZGlvbSB3b3VsZCBwcm9iYWJseSBiZQo+IHRvIHVzZSBzb21ldGhpbmcgbGlrZSDigJxgWCBvZiBY LmVycuKAnSB3aGVyZSDigJxgWOKAnSBpcyBzdWZmaWNpZW50bHkKPiBleHBsaWNpdCBhbmQg4oCc WC5lcnLigJ0gZW51bWVyYXRlcyB0aGUgcG9zc2libGUgZmFpbHVyZXMgZm9yIHRoZSBtb2R1bGUK PiDigJxY4oCdLiAgVGhlIGZ1bmN0aW9uIOKAnGNhdGNoX2V4biBm4oCdIHdpbGwgY2F0Y2ggZXhj ZXB0aW9ucyByYWlzZWQgYnkg4oCcZuKAnQo+IGFzIHdlbGwgYXMgZmFpbGVkLXRocmVhZHMgb25l cyAoYnkgZGVmYXVsdCwgb25seSB0dXJuaW5nIGFsbCBleGNlcHRpb25zCj4gaW50byBmYWlsaW5n IHRocmVhZCBvbmVzKS4gIFRoZSB1c2Ugb2Yg4oCcdW5pdOKAnSBpbiDigJwoJ2EsIHVuaXQpIHTi gJ0gZW5zdXJlcwo+IHRoYXQgdGhlIHRocmVhZCBpcyBvZiB0eXBlIOKAnChfLCAnYikgdOKAnSDi gJQgaS5lLiB0aGF0IGFsbCBlcnJvcnMgaGF2ZQo+IGJlZW4gZGVhbHQgd2l0aCDigJQgc28gaXQg Y2FuIGJlIHVuaWZpZWQgd2l0aCBhIG5vbi1wb2x5bW9ycGhpYyB2YXJpYW50Cj4gdHlwZS4KClRo ZSBwcm9ibGVtIHdlIGhhdmUgaW4gTWlyYWdlIGlzIHRoYXQgb3VyIHR5cGVzIGFyZSBhYnN0cmFj dC4gRm9yCmV4YW1wbGUsIGlmIHlvdSBoYXZlIGEgZnVuY3RvcgoKICBtb2R1bGUgRlMgKEIgOiBC TE9DSykgID0gLi4uCgp0aGVuIHRoZSBhdXRob3Igb2YgdGhlIEZTIGZ1bmN0b3IgZG9lc24ndCBr bm93IGV4YWN0bHkgd2hhdCBlcnJvcnMgdGhlCmNvbmNyZXRlIEIgbWlnaHQgdGhyb3cuIEZvciBl eGFtcGxlLCBpZiBCIGlzIGEgcmVtb3RlIGRpc2sgdGhlbiBpdAptaWdodCB0aHJvdyBuZXR3b3Jr IGVycm9ycy4gU28gZW5zdXJpbmcgdGhhdCBjYWxsZXJzIGVudW1lcmF0ZSBhbGwKZXJyb3JzIGlz bid0IHZlcnkgaGVscGZ1bCBpbiB0aGlzIGNhc2UuCgpZb3UgY2FuIGdpdmUgRlMgYW4gZXJyb3Ig Y29kZSBvZiBbYEJsb2NrX2Vycm9yIG9mIEIuZXJyb3JdIGFuZCBqdXN0CnByb3BhZ2F0ZSBpdCB0 byB0aGUgY2FsbGVyLCB3aGljaCBpcyB3aGF0IHdlIGRvIG5vdy4gVGhhdCBzZWVtcyBxdWl0ZQpj bGV2ZXIsIGJ1dCBJJ20gc3RydWdnbGluZyB0byBpbWFnaW5lIGEgY2FzZSB3aGVyZSBpdCdzIGFj dHVhbGx5CnVzZWZ1bC4KCkl0J3MgcHJvYmFibHkgd29ydGggY29tcGlsaW5nIGEgbGlzdCBvZiBl eGFtcGxlcyB3aGVyZSBNaXJhZ2UgY29kZQpjdXJyZW50bHkgbWF0Y2hlcyBvbiBzcGVjaWZpYyBy ZXR1cm5lZCBFcnJvciBjb2RlcyBhbmQgdGFrZXMgc3BlY2lmaWMKYWN0aW9ucy4gTXkgZ3Vlc3Mg aXMgdGhlcmUgYXJlbid0IGVub3VnaCB0byBqdXN0aWZ5IHRoZSBjb21wbGV4aXR5CnRob3VnaC4K CkkgdHJpZWQgZ3JlcHBpbmcgbXkgc291cmNlIGRpcmVjdG9yeSAoY29udGFpbmluZyBnaXQgY2xv bmVzIG9mIHZhcmlvdXMKTWlyYWdlIGNvbXBvbmVudHMpIHdpdGggenNoOgoKZm9yIHggaW4gKigv KTsgKGVjaG8gJz09PT09PT09PScgJHg7IGNkICR4ICYmIGdpdCBncmVwICd8IGBFcnJvciAoJykK CmJ1dCBpbiBldmVyeSBvbmUgb2YgdGhlc2UgY2FzZXMgd2hlcmUgd2UgbWF0Y2ggb24gYW4gYEVy cm9yLCB3ZSBqdXN0CnByb3BhZ2F0ZSBpdCAoaS5lLiB0aGUgZGVmYXVsdCBiZWhhdmlvdXIgb2Yg YW4gZXhjZXB0aW9uIHdvdWxkIGhhdmUKYmVlbiBjb3JyZWN0KS4KCkhlcmUgYXJlIHNvbWUgZXhh bXBsZXM6Cgp8IGBFcnJvciAoYEludmFsaWRfY29uc29sZSB4KSAtPiBmYWlsIChGYWlsdXJlIChQ cmludGYuc3ByaW50ZgoiSW52YWxpZF9jb25zb2xlICVzIiB4KSkKfCBgRXJyb3IgKGBCbG9ja19k ZXZpY2UgZSkgLT4gZmFpbCAoRmFpbHVyZSAoRnMuc3RyaW5nX29mX2Jsb2NrX2Vycm9yIGUpKQp8 IGBFcnJvciAoS1YuVW5rbm93bl9rZXkga2V5KSAtPiBmYWlsIChJbnZhbGlkX2FyZ3VtZW50IGtl eSkKfCBgRXJyb3IgKGBVbmtub3duIG1zZykgLT4gTHd0LmZhaWwgKEZhaWx1cmUgbXNnKQoKVGhl IG9ubHkgY2FzZSB3aGVyZSB3ZSBkbyBzb21ldGhpbmcgaW50ZXJlc3RpbmcgaXMgYEVycm9yIChV bmtub3duX2tleQpfKSwgd2hlcmUgd2Ugbm90ZSB0aGF0IGl0IHdhcyBhIHJlYWQ6Cgp8IGBFcnJv ciAoVE1QTC5Vbmtub3duX2tleSBfKSAtPiBmYWlsIChGYWlsdXJlICgicmVhZCAiIF4gbmFtZSkp CgpIb3dldmVyLCBVbmtub3duX2tleSB3b3VsZG4ndCBiZSBhbiBleGNlcHRpb24gdW5kZXIgYW55 IHByb3Bvc2VkIHNjaGVtZSBhbnl3YXkuCgo+IFRoaXMgaXMgc2ltaWxhciB0byBkZWNsYXJpbmcK Pgo+ICAgICB0eXBlICgnYSwgJ2IpIHQgPSAoJ2EsICdiKSBSZXN1bHQudCBMd3QudAo+Cj4gZXhj ZXB0IHRoYXQgb25lIGNhbm5vdCBkaXRjaCB0aGUg4oCcUmVzdWx0LnTigJ0gKGFuZCBvbmUgYXZv aWRzIDEKPiBpbmRpcmVjdGlvbiBwZXIgYmluZCkuCj4KPiBVbmZvcnR1bmF0ZWx5LCBpdCBpcyBz b21lIHdvcmsgdG8gZW5zdXJlIHRoYXQgdGhlIGNvbXBpbGVyIHVuZGVyc3RhbmRzCj4gdGhhdCBh bGwgZXJyb3JzIHdlcmUgZGVhbHQgd2l0aC4gIENvbnNpZGVyCj4KPiAgICAgbGV0IG0xID0gZmFp bChgWCAxKSA+Pj0gZnVuIHggLT4gZmFpbCBgWQo+Cj4gVGhlbgo+Cj4gICAgIGxldCBtMiA9IGNh dGNoIG0xIChmdW5jdGlvbiBgWCB4IC0+IHJldHVybiB4Cj4gICAgICAgICAgICAgICAgICAgICAg ICAgICAgICAgfCBlIC0+IGZhaWwgZSkKPgo+IHdpbGwgbm90IGRvLCB5b3UgaGF2ZSB0byB3cml0 ZQo+Cj4gICAgIGxldCBtMiA9IGNhdGNoIG0xIChmdW5jdGlvbiBgWCB4IC0+IHJldHVybiB4Cj4g ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgfCBgWSBhcyBlIC0+IGZhaWwgZSkKPgo+IHRv IG1ha2Ugc3VyZSDigJxtMuKAnSBzaG93cyB0aGF0IOKAnGBY4oCdIGlzIG5vIGxvbmdlciBhbiBp c3N1ZS4gIFRodXMKPiBkZWZpbmluZyBnb29kIHR5cGVzIHRvIHVzZSDigJwjdHlwZeKAnSBpcyBp bXBvcnRhbnQuCj4KPiBNeSAwLjAy4oKsLAo+IEMuCgoKCi0tIApEciBUaG9tYXMgTGVvbmFyZCAg ICAgICAgaHR0cDovLzBpbnN0YWxsLm5ldC8KR1BHOiA5MjQyIDk4MDcgQzk4NSAzQzA3IDQ0QTYg IDhCOUEgQUUwNyA4MjgwIDU5QTUgM0NDMQpHUEc6IERBOTggMjVBRSBDQUQwIDg5NzUgN0NEQSAg QkQ4RSAwNzEzIDNGOTYgQ0E3NCBEOEJBCgpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fXwpNaXJhZ2VPUy1kZXZlbCBtYWlsaW5nIGxpc3QKTWlyYWdlT1MtZGV2 ZWxAbGlzdHMueGVucHJvamVjdC5vcmcKaHR0cDovL2xpc3RzLnhlbnByb2plY3Qub3JnL2NnaS1i aW4vbWFpbG1hbi9saXN0aW5mby9taXJhZ2Vvcy1kZXZlbAo= From mirageos-devel-bounces@lists.xenproject.org Mon Feb 02 12:30:51 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 02 Feb 2015 12:30:51 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YIG9L-0001pj-5N; Mon, 02 Feb 2015 12:30:43 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YIG9J-0001pe-IP for mirageos-devel@lists.xenproject.org; Mon, 02 Feb 2015 12:30:41 +0000 Received: from [85.158.143.35] by server-2.bemta-4.messagelabs.com id 0E/47-02749-0FD6FC45; Mon, 02 Feb 2015 12:30:40 +0000 X-Env-Sender: talex5@gmail.com X-Msg-Ref: server-7.tower-21.messagelabs.com!1422880239!11916703!1 X-Originating-IP: [209.85.215.54] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23968 invoked from network); 2 Feb 2015 12:30:39 -0000 Received: from mail-la0-f54.google.com (HELO mail-la0-f54.google.com) (209.85.215.54) by server-7.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 2 Feb 2015 12:30:39 -0000 Received: by mail-la0-f54.google.com with SMTP id hv19so40008900lab.13 for ; Mon, 02 Feb 2015 04:30:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=AyjmWIBcnGG0Opo1SpRayyidM66rB3FGu5vPgZa7jkU=; b=GBY+khINrCvETMpKhwrDFzyaA6CTmd3r1DeT+v3V2Ffy6YmCaMUB9uG2iSQxe9x0HH kC3OiPt9KrM9TBG+QGSAyLhXFJO65fGU+EBGzXym7dEJMwdk50MB++oCCRSk999pUdGV +gzN9gDxvIXVmPZCjcuV0XTYVhawVZq78gRCAMOnk3OvVmLG6iQrK2rBN00smfbQDmyM kfCbkDWwxZcHJOEbygXnBUVDH86Bye1IZog6Nq0HgERzZ6zUYx27q2nl5iDyLIdRx3i8 3MMcTiH/a83+Wmm2PPxPAfog9bEbcSi7XguJwT+0mBWZGd4pSYgdcNHnYhlVE+hghX3I kiZg== MIME-Version: 1.0 X-Received: by 10.152.243.44 with SMTP id wv12mr18566492lac.78.1422880239119; Mon, 02 Feb 2015 04:30:39 -0800 (PST) Received: by 10.25.207.206 with HTTP; Mon, 2 Feb 2015 04:30:39 -0800 (PST) In-Reply-To: <20150202.014549.1883720051237442569.Christophe.Troestler@umons.ac.be> References: <20150202.014549.1883720051237442569.Christophe.Troestler@umons.ac.be> Date: Mon, 2 Feb 2015 12:30:39 +0000 Message-ID: From: Thomas Leonard To: Christophe Troestler Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Error handling in Mirage - request for comments! X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org T24gMiBGZWJydWFyeSAyMDE1IGF0IDAwOjQ1LCBDaHJpc3RvcGhlIFRyb2VzdGxlcgo8Q2hyaXN0 b3BoZS5Ucm9lc3RsZXJAdW1vbnMuYWMuYmU+IHdyb3RlOgo+IE9uIFNhdCwgMzEgSmFuIDIwMTUg MjE6MDc6MjIgKzAwMDAsIFRob21hcyBMZW9uYXJkIHdyb3RlOgo+Pgo+PiBb4oCmXSBCdXQgdGhl IHJlYWwgcHJvYmxlbSBoZXJlIGlzIHRoYXQgYnkgbWFraW5nIGV4Y2VwdGlvbnMgZmF0YWwgd2UK Pj4gdHVybiBldmVyeSBleGNlcHRpb24gdXNlZCBpbiBleGlzdGluZyBPQ2FtbCBjb2RlIGludG8g YSBzZWN1cml0eQo+PiB2dWxuZXJhYmlsaXR5LiBb4oCmXQo+Cj4gU2luY2UgT0NhbWwgc3VwcG9y dHMgZXhjZXB0aW9ucywgSSB0aGluayB0aGVyZSBpcyBubyBkb3VidCB0aGF0IHdlCj4gbXVzdCBo YW5kbGUgdGhlbSBlZmZlY3RpdmVseSDigJQgbm90IGp1c3Qgd2lwZSB0aGVtIHVuZGVyIHRoZSBj YXJwZXQgYW5kCj4gbGV0IHRoZW0gYWJvcnQgdGhlIHByb2dyYW0vdW5pa2VybmVsLiAgSWRlYWxs eSBMd3Qgc2hvdWxkIGRlYWwKPiBzZW5zaWJseSB3aXRoIGV4Y2VwdGlvbnMgKGFuZCB0aGUgZGlz Y3Vzc2lvbiBzZWVtcyB0byBpbXBseSB0aGVyZSBhcmUKPiBhcmVhcyBvZiBpbXByb3ZlbWVudCDi gJQgYnV0IGl0IGlzIHVuY2xlYXIgdG8gbWUgaG93IHlvdSBjYW4gZG8gdGhhdAo+IGVmZmljaWVu dGx5IHdpdGhvdXQgdXNpbmcgYSB0cnkgYmxvY2sgaW4gYWxsIGJpbmRzKS4KCkx3dCBhbHJlYWR5 IHB1dHMgYSB0cnkgYmxvY2sgaW4gYWxsIChzbGVlcGluZykgYmluZHMsIHNvIHRoaXMgaXMKaGFu ZGxlZCBmb3IgeW91OgoKbGV0IGJpbmQgdCBmID0KICBsZXQgdCA9IHJlcHIgdCBpbgogIG1hdGNo IHQuc3RhdGUgd2l0aAogICAgfCBSZXR1cm4gdiAtPgogICAgICAgIGYgdgogICAgfCBGYWlsIF8g YXMgc3RhdGUgLT4KICAgICAgICB0aHJlYWQgeyBzdGF0ZSB9CiAgICB8IFNsZWVwIHNsZWVwZXIg LT4KICAgICAgICBsZXQgcmVzID0gdGVtcCB0IGluCiAgICAgICAgbGV0IGRhdGEgPSAhY3VycmVu dF9kYXRhIGluCiAgICAgICAgYWRkX2ltbXV0YWJsZV93YWl0ZXIgc2xlZXBlcgogICAgICAgICAg KGZ1bmN0aW9uCiAgICAgICAgICAgICB8IFJldHVybiB2IC0+IGN1cnJlbnRfZGF0YSA6PSBkYXRh OyBjb25uZWN0IHJlcyAodHJ5IGYgdgp3aXRoIGV4biAtPiBmYWlsIGV4bikKICAgICAgICAgICAg IHwgRmFpbCBfIGFzIHN0YXRlIC0+IGZhc3RfY29ubmVjdCByZXMgc3RhdGUKICAgICAgICAgICAg IHwgXyAtPiBhc3NlcnQgZmFsc2UpOwogICAgICAgIHJlcwoKPiBTbyBpdCBzZWVtcyB0bwo+IG1l IHRoYXQgdGhlcmUgaXMgbGl0dGxlIGNob2ljZSBidXQgdGhhdCBleGNlcHRpb25zIGJlIHR1cm5l ZCBpbnRvCj4gZmFpbGVkIHRocmVhZHMgYXQgdGhlIHByb2dyYW1tZXIncyBkaXNjcmV0aW9uLiAg TWF5YmUg4oCccnVu4oCdIHNob3VsZCBiZQo+IHJlbmFtZWQg4oCccnVuX2V4buKAnSB0byBpbmRp Y2F0ZSB0aGF0IGV4Y2VwdGlvbnMgcGFzcyB0aHJvdWdoIGFuZCB0aGUKPiAic2FmZSIgcnVuIHNo b3VsZCBiZQo+Cj4gICAgIHJ1biA6ICh1bml0IC0+ICdhIHQpIC0+IFtgT2sgb2YgJ2EgfCBgRXhu IG9mIGV4bl0KPgo+IEFzIGl0IHdhcyBwcmV2aW91c2x5IG1lbnRpb25lZCwgSSBhbHNvIHRoaW5r IHRoYXQgdXNpbmcgImVycm9yLWF3YXJlCj4gcmV0dXJuIHR5cGVzIiBzaG91bGQgYmUgbGltaXRl ZCBtb3N0bHkgdG8gY2FzZXMgd2hlcmUgdGhlIGZhaWx1cmUgaXMKPiBub3QgcmVhbGx5IGFuIGVy cm9yIGFuZCBzaG91bGQgYmUgZGVhbHQgd2l0aCBpbW1lZGlhdGVseSBieSB0aGUKPiBjYWxsZXIu ICBBbmQgSSBhZ3JlZSB3aXRoIFRob21hcyB3aGVuIGhlIHNheXMgdGhhdCBvdmVydXNpbmcgdGhp cwo+IHNjaGVtZSB3aWxsIHJlc3VsdCBpbiBlcnJvcnMgYmVpbmcgaWdub3JlZCBpbnN0ZWFkIG9m IGJlaW5nIGRlYWx0IHdpdGgKPiBwcm9wZXJseS4KPgo+IFRoZXJlIGFyZSBob3dldmVyIGVycm9y cyB0aGF0IHlvdSB3YW50IHRvIG1hbmRhdGUgdGhhdCB0aGV5IGFyZSBkZWFsdAo+IHdpdGggYnV0 IG5vdCBuZWNlc3NhcmlseSBhdCB0aGUgY2FsbGluZyBwb2ludC4gIEEgdHlwaWNhbCBleGFtcGxl IHRvCj4gbWUgaXMg4oCccmVhZOKAnSBiZWNhdXNlIGl0IGlzIG9mdGVuIG11Y2ggImhpZ2hlciIg aW4gdGhlIHByb2dyYW0gdGhhdCBhbgo+IGFwcHJvcHJpYXRlIHJlc3BvbnNlIHRvIGEgZmFpbGlu ZyByZWFkIGNhbiBiZSBtYWRlIOKAlCB0aGlzIGlzIGltcG9ydGFudAo+IGZvciBsaWJyYXJpZXMg dGhhdCB3aWxsIHBvc3QtcHJvY2VzcyDigJxyZWFk4oCdcyBhbmQgd2lsbCBoYXZlIG5vIGlkZWEK PiB3aGF0IHRvIGRvIGlmIOKAnHJlYWTigJ0gZmFpbHMuCgpZZXMsIHRoaXMgaXMgYSBjYXNlIHdo ZXJlIHlvdSBtaWdodCB3YW50IGFuIE9yX2Vycm9yLnQgdGhyZWFkZWQKdGhyb3VnaCBldmVyeXRo aW5nLiBPciwgaXQgbWlnaHQgYmUgZWFzaWVyIHRvIHdyYXAgdGhlIHdob2xlIHRoaW5nIHNvCnRo YXQgYW55IGVycm9yIGNvZGUgcmV0dXJuZWQgYnkgdGhlIHJlYWQgaXMgdGhyb3duIGFuZCB0aGVu IGNhdWdodAphZ2Fpbi4KCj4gVG8gbWFrZSB0aGUgZGlzY3Vzc2lvbiBhIGJpdCBtb3JlIGNvbmNy ZXRlLCBoZXJlIGlzIGEgc2lnbmF0dXJlCj4gaWxsdXN0cmF0aW5nIGhvdyB0aGVzZSBsYXR0ZXIg ZXJyb3JzIG1heSBiZSBoYW5kbGVkOgo+Cj4gICAgIHR5cGUgKCdhLCAnYikgdAo+ICAgICB2YWwg cmV0dXJuIDogJ2EgLT4gKCdhLCAnYikgdAo+ICAgICB2YWwgKCA+Pj0gKSA6ICgnYSwgJ2IpIHQg LT4gKCdhIC0+ICgnYywgJ2IpIHQpIC0+ICgnYywgJ2IpIHQKPiAgICAgdmFsIGZhaWwgOiAoWz4g XSBhcyAnYikgLT4gKF8sICdiKSB0Cj4gICAgIHZhbCBmYWlsX2V4biA6IGV4biAtPiAoJ2EsICdi KSB0Cj4gICAgIHZhbCBjYXRjaCA6ICgnYSwgJ2IpIHQgLT4gKCdiIC0+ICgnYSwgJ2MpIHQpIC0+ ICgnYSwgJ2MpIHQKPiAgICAgdmFsIGNhdGNoX2V4biA6ID9leG46KGV4biAtPiAoJ2EsICdiKSB0 KSAtPiAodW5pdCAtPiAoJ2EsICdiKSB0KSAtPiAoJ2EsICdiKSB0Cj4gICAgIHZhbCBydW4gOiAo dW5pdCAtPiAoJ2EsIHVuaXQpIHQpIC0+IFtgT2sgb2YgJ2EgfCBgRXhuIG9mIGV4bl0KPiAgICAg dmFsIHJ1bl9leG4gOiAoJ2EsIHVuaXQpIHQgLT4gJ2EKPgo+IFNvbWUgcmVtYXJrcy4gIFRoZSDi gJxmYWls4oCdIGZ1bmN0aW9uIGltcG9zZXMgdGhhdCB0aGUgZXJyb3JzIGFyZSBsYWJlbGVkCj4g d2l0aCBwb2x5bW9ycGhpYyB2YXJpYW50cy4gIFNpbmNlIHRoZXNlIGFyZSBub3QgcXVhbGlmaWVk IGJ5IHRoZQo+IG1vZHVsZSBhbmQgdG8gYWxsb3cgZ2VuZXJpYyB0cmVhdG1lbnQsIGEgZ29vZCBp ZGlvbSB3b3VsZCBwcm9iYWJseSBiZQo+IHRvIHVzZSBzb21ldGhpbmcgbGlrZSDigJxgWCBvZiBY LmVycuKAnSB3aGVyZSDigJxgWOKAnSBpcyBzdWZmaWNpZW50bHkKPiBleHBsaWNpdCBhbmQg4oCc WC5lcnLigJ0gZW51bWVyYXRlcyB0aGUgcG9zc2libGUgZmFpbHVyZXMgZm9yIHRoZSBtb2R1bGUK PiDigJxY4oCdLiAgVGhlIGZ1bmN0aW9uIOKAnGNhdGNoX2V4biBm4oCdIHdpbGwgY2F0Y2ggZXhj ZXB0aW9ucyByYWlzZWQgYnkg4oCcZuKAnQo+IGFzIHdlbGwgYXMgZmFpbGVkLXRocmVhZHMgb25l cyAoYnkgZGVmYXVsdCwgb25seSB0dXJuaW5nIGFsbCBleGNlcHRpb25zCj4gaW50byBmYWlsaW5n IHRocmVhZCBvbmVzKS4gIFRoZSB1c2Ugb2Yg4oCcdW5pdOKAnSBpbiDigJwoJ2EsIHVuaXQpIHTi gJ0gZW5zdXJlcwo+IHRoYXQgdGhlIHRocmVhZCBpcyBvZiB0eXBlIOKAnChfLCAnYikgdOKAnSDi gJQgaS5lLiB0aGF0IGFsbCBlcnJvcnMgaGF2ZQo+IGJlZW4gZGVhbHQgd2l0aCDigJQgc28gaXQg Y2FuIGJlIHVuaWZpZWQgd2l0aCBhIG5vbi1wb2x5bW9ycGhpYyB2YXJpYW50Cj4gdHlwZS4KClRo ZSBwcm9ibGVtIHdlIGhhdmUgaW4gTWlyYWdlIGlzIHRoYXQgb3VyIHR5cGVzIGFyZSBhYnN0cmFj dC4gRm9yCmV4YW1wbGUsIGlmIHlvdSBoYXZlIGEgZnVuY3RvcgoKICBtb2R1bGUgRlMgKEIgOiBC TE9DSykgID0gLi4uCgp0aGVuIHRoZSBhdXRob3Igb2YgdGhlIEZTIGZ1bmN0b3IgZG9lc24ndCBr bm93IGV4YWN0bHkgd2hhdCBlcnJvcnMgdGhlCmNvbmNyZXRlIEIgbWlnaHQgdGhyb3cuIEZvciBl eGFtcGxlLCBpZiBCIGlzIGEgcmVtb3RlIGRpc2sgdGhlbiBpdAptaWdodCB0aHJvdyBuZXR3b3Jr IGVycm9ycy4gU28gZW5zdXJpbmcgdGhhdCBjYWxsZXJzIGVudW1lcmF0ZSBhbGwKZXJyb3JzIGlz bid0IHZlcnkgaGVscGZ1bCBpbiB0aGlzIGNhc2UuCgpZb3UgY2FuIGdpdmUgRlMgYW4gZXJyb3Ig Y29kZSBvZiBbYEJsb2NrX2Vycm9yIG9mIEIuZXJyb3JdIGFuZCBqdXN0CnByb3BhZ2F0ZSBpdCB0 byB0aGUgY2FsbGVyLCB3aGljaCBpcyB3aGF0IHdlIGRvIG5vdy4gVGhhdCBzZWVtcyBxdWl0ZQpj bGV2ZXIsIGJ1dCBJJ20gc3RydWdnbGluZyB0byBpbWFnaW5lIGEgY2FzZSB3aGVyZSBpdCdzIGFj dHVhbGx5CnVzZWZ1bC4KCkl0J3MgcHJvYmFibHkgd29ydGggY29tcGlsaW5nIGEgbGlzdCBvZiBl eGFtcGxlcyB3aGVyZSBNaXJhZ2UgY29kZQpjdXJyZW50bHkgbWF0Y2hlcyBvbiBzcGVjaWZpYyBy ZXR1cm5lZCBFcnJvciBjb2RlcyBhbmQgdGFrZXMgc3BlY2lmaWMKYWN0aW9ucy4gTXkgZ3Vlc3Mg aXMgdGhlcmUgYXJlbid0IGVub3VnaCB0byBqdXN0aWZ5IHRoZSBjb21wbGV4aXR5CnRob3VnaC4K CkkgdHJpZWQgZ3JlcHBpbmcgbXkgc291cmNlIGRpcmVjdG9yeSAoY29udGFpbmluZyBnaXQgY2xv bmVzIG9mIHZhcmlvdXMKTWlyYWdlIGNvbXBvbmVudHMpIHdpdGggenNoOgoKZm9yIHggaW4gKigv KTsgKGVjaG8gJz09PT09PT09PScgJHg7IGNkICR4ICYmIGdpdCBncmVwICd8IGBFcnJvciAoJykK CmJ1dCBpbiBldmVyeSBvbmUgb2YgdGhlc2UgY2FzZXMgd2hlcmUgd2UgbWF0Y2ggb24gYW4gYEVy cm9yLCB3ZSBqdXN0CnByb3BhZ2F0ZSBpdCAoaS5lLiB0aGUgZGVmYXVsdCBiZWhhdmlvdXIgb2Yg YW4gZXhjZXB0aW9uIHdvdWxkIGhhdmUKYmVlbiBjb3JyZWN0KS4KCkhlcmUgYXJlIHNvbWUgZXhh bXBsZXM6Cgp8IGBFcnJvciAoYEludmFsaWRfY29uc29sZSB4KSAtPiBmYWlsIChGYWlsdXJlIChQ cmludGYuc3ByaW50ZgoiSW52YWxpZF9jb25zb2xlICVzIiB4KSkKfCBgRXJyb3IgKGBCbG9ja19k ZXZpY2UgZSkgLT4gZmFpbCAoRmFpbHVyZSAoRnMuc3RyaW5nX29mX2Jsb2NrX2Vycm9yIGUpKQp8 IGBFcnJvciAoS1YuVW5rbm93bl9rZXkga2V5KSAtPiBmYWlsIChJbnZhbGlkX2FyZ3VtZW50IGtl eSkKfCBgRXJyb3IgKGBVbmtub3duIG1zZykgLT4gTHd0LmZhaWwgKEZhaWx1cmUgbXNnKQoKVGhl IG9ubHkgY2FzZSB3aGVyZSB3ZSBkbyBzb21ldGhpbmcgaW50ZXJlc3RpbmcgaXMgYEVycm9yIChV bmtub3duX2tleQpfKSwgd2hlcmUgd2Ugbm90ZSB0aGF0IGl0IHdhcyBhIHJlYWQ6Cgp8IGBFcnJv ciAoVE1QTC5Vbmtub3duX2tleSBfKSAtPiBmYWlsIChGYWlsdXJlICgicmVhZCAiIF4gbmFtZSkp CgpIb3dldmVyLCBVbmtub3duX2tleSB3b3VsZG4ndCBiZSBhbiBleGNlcHRpb24gdW5kZXIgYW55 IHByb3Bvc2VkIHNjaGVtZSBhbnl3YXkuCgo+IFRoaXMgaXMgc2ltaWxhciB0byBkZWNsYXJpbmcK Pgo+ICAgICB0eXBlICgnYSwgJ2IpIHQgPSAoJ2EsICdiKSBSZXN1bHQudCBMd3QudAo+Cj4gZXhj ZXB0IHRoYXQgb25lIGNhbm5vdCBkaXRjaCB0aGUg4oCcUmVzdWx0LnTigJ0gKGFuZCBvbmUgYXZv aWRzIDEKPiBpbmRpcmVjdGlvbiBwZXIgYmluZCkuCj4KPiBVbmZvcnR1bmF0ZWx5LCBpdCBpcyBz b21lIHdvcmsgdG8gZW5zdXJlIHRoYXQgdGhlIGNvbXBpbGVyIHVuZGVyc3RhbmRzCj4gdGhhdCBh bGwgZXJyb3JzIHdlcmUgZGVhbHQgd2l0aC4gIENvbnNpZGVyCj4KPiAgICAgbGV0IG0xID0gZmFp bChgWCAxKSA+Pj0gZnVuIHggLT4gZmFpbCBgWQo+Cj4gVGhlbgo+Cj4gICAgIGxldCBtMiA9IGNh dGNoIG0xIChmdW5jdGlvbiBgWCB4IC0+IHJldHVybiB4Cj4gICAgICAgICAgICAgICAgICAgICAg ICAgICAgICAgfCBlIC0+IGZhaWwgZSkKPgo+IHdpbGwgbm90IGRvLCB5b3UgaGF2ZSB0byB3cml0 ZQo+Cj4gICAgIGxldCBtMiA9IGNhdGNoIG0xIChmdW5jdGlvbiBgWCB4IC0+IHJldHVybiB4Cj4g ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgfCBgWSBhcyBlIC0+IGZhaWwgZSkKPgo+IHRv IG1ha2Ugc3VyZSDigJxtMuKAnSBzaG93cyB0aGF0IOKAnGBY4oCdIGlzIG5vIGxvbmdlciBhbiBp c3N1ZS4gIFRodXMKPiBkZWZpbmluZyBnb29kIHR5cGVzIHRvIHVzZSDigJwjdHlwZeKAnSBpcyBp bXBvcnRhbnQuCj4KPiBNeSAwLjAy4oKsLAo+IEMuCgoKCi0tIApEciBUaG9tYXMgTGVvbmFyZCAg ICAgICAgaHR0cDovLzBpbnN0YWxsLm5ldC8KR1BHOiA5MjQyIDk4MDcgQzk4NSAzQzA3IDQ0QTYg IDhCOUEgQUUwNyA4MjgwIDU5QTUgM0NDMQpHUEc6IERBOTggMjVBRSBDQUQwIDg5NzUgN0NEQSAg QkQ4RSAwNzEzIDNGOTYgQ0E3NCBEOEJBCgpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fXwpNaXJhZ2VPUy1kZXZlbCBtYWlsaW5nIGxpc3QKTWlyYWdlT1MtZGV2 ZWxAbGlzdHMueGVucHJvamVjdC5vcmcKaHR0cDovL2xpc3RzLnhlbnByb2plY3Qub3JnL2NnaS1i aW4vbWFpbG1hbi9saXN0aW5mby9taXJhZ2Vvcy1kZXZlbAo= From mirageos-devel-bounces@lists.xenproject.org Mon Feb 02 13:18:39 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 02 Feb 2015 13:18:39 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YIGth-0007SY-MY; Mon, 02 Feb 2015 13:18:37 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YIGtg-0007SO-2A for mirageos-devel@lists.xenproject.org; Mon, 02 Feb 2015 13:18:36 +0000 Received: from [193.109.254.147] by server-8.bemta-14.messagelabs.com id D4/71-03168-B297FC45; Mon, 02 Feb 2015 13:18:35 +0000 X-Env-Sender: talex5@gmail.com X-Msg-Ref: server-2.tower-27.messagelabs.com!1422883114!12205383!1 X-Originating-IP: [209.85.215.51] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 32118 invoked from network); 2 Feb 2015 13:18:34 -0000 Received: from mail-la0-f51.google.com (HELO mail-la0-f51.google.com) (209.85.215.51) by server-2.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 2 Feb 2015 13:18:34 -0000 Received: by mail-la0-f51.google.com with SMTP id ge10so40725853lab.10 for ; Mon, 02 Feb 2015 05:18:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=2xOWzrUUpRsTWJxSh5Jd64JalCq4XmxFClj2fgQtKIU=; b=BpfRB3MqFdT138pAAVKeQqv75H8Ezm1be8a9EfygQrFpUERLJPKK7GyQEbkRAyqw0D dBRoo/YP+jwmTEMm/QfG264jGnUb3msL1pt0/MeCDgmaxYHF4fiGjTmO6hrAv829itzf E1sBQxcoyfHKz7J9ZU1loL+TZ9E3kKQExfOUbJzHWlY6MgRlcav/YFUsGmYWn+yiGjIz tlUp8BrHsH9T0Xl262tCtY0BKt/T6kH2Avjl6r9XNXOjBon72kWWsET+Ny4JtN3h3qfd NvQpgynmhWnf5UY6X3WXG3xNS9qA9EuifECzmVg0jYD2SbF2VOZE4JPrc2EsmCTMx892 JU2A== MIME-Version: 1.0 X-Received: by 10.112.130.34 with SMTP id ob2mr19662207lbb.78.1422883113853; Mon, 02 Feb 2015 05:18:33 -0800 (PST) Received: by 10.25.207.206 with HTTP; Mon, 2 Feb 2015 05:18:33 -0800 (PST) In-Reply-To: References: <8ADB7411-F46F-4CF1-B2DF-42A00F825C6F@recoil.org> Date: Mon, 2 Feb 2015 13:18:33 +0000 Message-ID: From: Thomas Leonard To: Anil Madhavapeddy Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Error handling in Mirage - request for comments! X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 30 January 2015 at 10:24, Anil Madhavapeddy wrote: > On 30 Jan 2015, at 10:06, Thomas Leonard wrote: >> >> On 30 January 2015 at 09:30, Anil Madhavapeddy wrote: >>> On 29 Jan 2015, at 15:24, Thomas Leonard wrote: >>>> >>>> As part of my continuing mission to break all Mirage APIs, I've >>>> written up some thoughts on how to improve error handling: >>> >>> s/break/fix :-) >>> >>>> >>>> https://github.com/mirage/mirage-www/pull/274 >>>> >>>> Although written as if it's a final design, it's intended only as a >>>> starting point for discussion, to find out what we do and don't agree >>>> on. Please add comments, information about successful approaches >>>> you've seen, etc. >>> >>> This is an excellent writeup. My top-level view is that moving to >>> an exception-heavier model is fine, but that we really do need to adopt >>> some sort of Async-style monitor model to make this feasible, so that >>> exceptions can be contained within a logical section of the code. >> >> Doesn't try_lwt (or similar) do this anyway? What particular problem >> are you worried about? >> > > It does, if used carefully everywhere -- and is quite slow. The > problem is along the lines of: > > Thread 1: try > Thread 1: > Thread 1: Lwt.wakeup thread2 > Thread 2: > Thread 2: raise Failure > Thread 1: catch > > The fast switch has caused thread 1 to catch the Failure. Actually, I'm having trouble seeing how this could happen. Lwt should catch the exception and turn it into a failed thread automatically: open Lwt let waiter, waker = Lwt.wait () let thread2 = waiter >>= fun () -> print_endline "raising Failure"; raise (Failure "Failed") let () = print_endline "main start"; begin try Lwt.wakeup waker (); with Failure _ -> print_endline "caught failure" end; print_endline "main end" let () = Lwt_unix.run thread2 This prints: main start raising Failure main end Fatal error: exception Failure("Failed") i.e. the fact that thread2 raised an exception didn't interfere with the main thread (no "caught failure"), since the main thread didn't care about the outcome of thead2. -- Dr Thomas Leonard http://0install.net/ GPG: 9242 9807 C985 3C07 44A6 8B9A AE07 8280 59A5 3CC1 GPG: DA98 25AE CAD0 8975 7CDA BD8E 0713 3F96 CA74 D8BA _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Mon Feb 02 13:18:39 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 02 Feb 2015 13:18:39 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YIGth-0007SY-MY; Mon, 02 Feb 2015 13:18:37 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YIGtg-0007SO-2A for mirageos-devel@lists.xenproject.org; Mon, 02 Feb 2015 13:18:36 +0000 Received: from [193.109.254.147] by server-8.bemta-14.messagelabs.com id D4/71-03168-B297FC45; Mon, 02 Feb 2015 13:18:35 +0000 X-Env-Sender: talex5@gmail.com X-Msg-Ref: server-2.tower-27.messagelabs.com!1422883114!12205383!1 X-Originating-IP: [209.85.215.51] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 32118 invoked from network); 2 Feb 2015 13:18:34 -0000 Received: from mail-la0-f51.google.com (HELO mail-la0-f51.google.com) (209.85.215.51) by server-2.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 2 Feb 2015 13:18:34 -0000 Received: by mail-la0-f51.google.com with SMTP id ge10so40725853lab.10 for ; Mon, 02 Feb 2015 05:18:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=2xOWzrUUpRsTWJxSh5Jd64JalCq4XmxFClj2fgQtKIU=; b=BpfRB3MqFdT138pAAVKeQqv75H8Ezm1be8a9EfygQrFpUERLJPKK7GyQEbkRAyqw0D dBRoo/YP+jwmTEMm/QfG264jGnUb3msL1pt0/MeCDgmaxYHF4fiGjTmO6hrAv829itzf E1sBQxcoyfHKz7J9ZU1loL+TZ9E3kKQExfOUbJzHWlY6MgRlcav/YFUsGmYWn+yiGjIz tlUp8BrHsH9T0Xl262tCtY0BKt/T6kH2Avjl6r9XNXOjBon72kWWsET+Ny4JtN3h3qfd NvQpgynmhWnf5UY6X3WXG3xNS9qA9EuifECzmVg0jYD2SbF2VOZE4JPrc2EsmCTMx892 JU2A== MIME-Version: 1.0 X-Received: by 10.112.130.34 with SMTP id ob2mr19662207lbb.78.1422883113853; Mon, 02 Feb 2015 05:18:33 -0800 (PST) Received: by 10.25.207.206 with HTTP; Mon, 2 Feb 2015 05:18:33 -0800 (PST) In-Reply-To: References: <8ADB7411-F46F-4CF1-B2DF-42A00F825C6F@recoil.org> Date: Mon, 2 Feb 2015 13:18:33 +0000 Message-ID: From: Thomas Leonard To: Anil Madhavapeddy Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Error handling in Mirage - request for comments! X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 30 January 2015 at 10:24, Anil Madhavapeddy wrote: > On 30 Jan 2015, at 10:06, Thomas Leonard wrote: >> >> On 30 January 2015 at 09:30, Anil Madhavapeddy wrote: >>> On 29 Jan 2015, at 15:24, Thomas Leonard wrote: >>>> >>>> As part of my continuing mission to break all Mirage APIs, I've >>>> written up some thoughts on how to improve error handling: >>> >>> s/break/fix :-) >>> >>>> >>>> https://github.com/mirage/mirage-www/pull/274 >>>> >>>> Although written as if it's a final design, it's intended only as a >>>> starting point for discussion, to find out what we do and don't agree >>>> on. Please add comments, information about successful approaches >>>> you've seen, etc. >>> >>> This is an excellent writeup. My top-level view is that moving to >>> an exception-heavier model is fine, but that we really do need to adopt >>> some sort of Async-style monitor model to make this feasible, so that >>> exceptions can be contained within a logical section of the code. >> >> Doesn't try_lwt (or similar) do this anyway? What particular problem >> are you worried about? >> > > It does, if used carefully everywhere -- and is quite slow. The > problem is along the lines of: > > Thread 1: try > Thread 1: > Thread 1: Lwt.wakeup thread2 > Thread 2: > Thread 2: raise Failure > Thread 1: catch > > The fast switch has caused thread 1 to catch the Failure. Actually, I'm having trouble seeing how this could happen. Lwt should catch the exception and turn it into a failed thread automatically: open Lwt let waiter, waker = Lwt.wait () let thread2 = waiter >>= fun () -> print_endline "raising Failure"; raise (Failure "Failed") let () = print_endline "main start"; begin try Lwt.wakeup waker (); with Failure _ -> print_endline "caught failure" end; print_endline "main end" let () = Lwt_unix.run thread2 This prints: main start raising Failure main end Fatal error: exception Failure("Failed") i.e. the fact that thread2 raised an exception didn't interfere with the main thread (no "caught failure"), since the main thread didn't care about the outcome of thead2. -- Dr Thomas Leonard http://0install.net/ GPG: 9242 9807 C985 3C07 44A6 8B9A AE07 8280 59A5 3CC1 GPG: DA98 25AE CAD0 8975 7CDA BD8E 0713 3F96 CA74 D8BA _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Mon Feb 02 16:35:21 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 02 Feb 2015 16:35:21 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YIJy1-0007HM-Te; Mon, 02 Feb 2015 16:35:17 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YIJy1-0007H0-Dl for mirageos-devel@lists.xenproject.org; Mon, 02 Feb 2015 16:35:17 +0000 Received: from [85.158.139.211] by server-2.bemta-5.messagelabs.com id 25/90-03511-447AFC45; Mon, 02 Feb 2015 16:35:16 +0000 X-Env-Sender: talex5@gmail.com X-Msg-Ref: server-5.tower-206.messagelabs.com!1422894915!11742991!1 X-Originating-IP: [209.85.215.42] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.12.5; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6132 invoked from network); 2 Feb 2015 16:35:16 -0000 Received: from mail-la0-f42.google.com (HELO mail-la0-f42.google.com) (209.85.215.42) by server-5.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 2 Feb 2015 16:35:16 -0000 Received: by mail-la0-f42.google.com with SMTP id ms9so42697491lab.1 for ; Mon, 02 Feb 2015 08:35:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=ZTeOw12oEAYwP3OdA+80pcyMVJjJI7L4jtsCVgfCAb8=; b=NJ3dfLriGoyNpg70CxxxVyg6OjgIXh7XJYwuagtOAXvxD/kEA4oUoB4aCiNnF6tUNJ KGJnZUWMD5wJQiEklG5BMxUnh9SZVo1aAlRp3PMSw0KGY51+ElNN/ejhYYGz4hR0kJQd XbjJkkJCGw3QjOpsabA5/7PytmwyFRUIIEEjxD0rGObIJzHHh3cc22RUSRyirUB0wVXi kMLhzxRlIaHWMzclll+0K7wadn5h17FdLjFqbP/XMnHFgX1WRfjK1bzgu3/bVeRRc8f1 ohCWFyzA8sobRlojpEYA8/vvdbKgfn18qJ0DLPzEwTCbDtUdtTKvzRwlbJtCU+l1zvTS dCLw== MIME-Version: 1.0 X-Received: by 10.152.243.44 with SMTP id wv12mr19792236lac.78.1422894915160; Mon, 02 Feb 2015 08:35:15 -0800 (PST) Received: by 10.25.207.206 with HTTP; Mon, 2 Feb 2015 08:35:15 -0800 (PST) Date: Mon, 2 Feb 2015 16:35:15 +0000 Message-ID: From: Thomas Leonard To: "mirageos-devel@lists.xenproject.org" Subject: [MirageOS-devel] Minor patches (connect / error_message) X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org I'd like to get some minor patches applied so I can remove some of my branches. Unless someone objects today, I plan to apply these myself: mirage/mirage-block-unix Add explicit 'connect' to interface https://github.com/mirage/mirage-block-unix/pull/20 mirage/mirage-net-xen Add explicit 'connect' function to interface https://github.com/mirage/mirage-net-xen/pull/19 mirage/mirage-net-unix Add explicit 'connect' function to interface https://github.com/mirage/mirage-net-unix/pull/10 mirage/mirage-tcpip Added 'error_message' functions https://github.com/mirage/mirage-tcpip/pull/98 I'd also like to apply this one, but it is a slight API change: mirage/mirage-block-xen Added explicit 'connect' to interface https://github.com/mirage/mirage-block-xen/pull/35 -- Dr Thomas Leonard http://0install.net/ GPG: 9242 9807 C985 3C07 44A6 8B9A AE07 8280 59A5 3CC1 GPG: DA98 25AE CAD0 8975 7CDA BD8E 0713 3F96 CA74 D8BA _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Mon Feb 02 16:35:21 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 02 Feb 2015 16:35:21 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YIJy1-0007HM-Te; Mon, 02 Feb 2015 16:35:17 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YIJy1-0007H0-Dl for mirageos-devel@lists.xenproject.org; Mon, 02 Feb 2015 16:35:17 +0000 Received: from [85.158.139.211] by server-2.bemta-5.messagelabs.com id 25/90-03511-447AFC45; Mon, 02 Feb 2015 16:35:16 +0000 X-Env-Sender: talex5@gmail.com X-Msg-Ref: server-5.tower-206.messagelabs.com!1422894915!11742991!1 X-Originating-IP: [209.85.215.42] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.12.5; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6132 invoked from network); 2 Feb 2015 16:35:16 -0000 Received: from mail-la0-f42.google.com (HELO mail-la0-f42.google.com) (209.85.215.42) by server-5.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 2 Feb 2015 16:35:16 -0000 Received: by mail-la0-f42.google.com with SMTP id ms9so42697491lab.1 for ; Mon, 02 Feb 2015 08:35:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=ZTeOw12oEAYwP3OdA+80pcyMVJjJI7L4jtsCVgfCAb8=; b=NJ3dfLriGoyNpg70CxxxVyg6OjgIXh7XJYwuagtOAXvxD/kEA4oUoB4aCiNnF6tUNJ KGJnZUWMD5wJQiEklG5BMxUnh9SZVo1aAlRp3PMSw0KGY51+ElNN/ejhYYGz4hR0kJQd XbjJkkJCGw3QjOpsabA5/7PytmwyFRUIIEEjxD0rGObIJzHHh3cc22RUSRyirUB0wVXi kMLhzxRlIaHWMzclll+0K7wadn5h17FdLjFqbP/XMnHFgX1WRfjK1bzgu3/bVeRRc8f1 ohCWFyzA8sobRlojpEYA8/vvdbKgfn18qJ0DLPzEwTCbDtUdtTKvzRwlbJtCU+l1zvTS dCLw== MIME-Version: 1.0 X-Received: by 10.152.243.44 with SMTP id wv12mr19792236lac.78.1422894915160; Mon, 02 Feb 2015 08:35:15 -0800 (PST) Received: by 10.25.207.206 with HTTP; Mon, 2 Feb 2015 08:35:15 -0800 (PST) Date: Mon, 2 Feb 2015 16:35:15 +0000 Message-ID: From: Thomas Leonard To: "mirageos-devel@lists.xenproject.org" Subject: [MirageOS-devel] Minor patches (connect / error_message) X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org I'd like to get some minor patches applied so I can remove some of my branches. Unless someone objects today, I plan to apply these myself: mirage/mirage-block-unix Add explicit 'connect' to interface https://github.com/mirage/mirage-block-unix/pull/20 mirage/mirage-net-xen Add explicit 'connect' function to interface https://github.com/mirage/mirage-net-xen/pull/19 mirage/mirage-net-unix Add explicit 'connect' function to interface https://github.com/mirage/mirage-net-unix/pull/10 mirage/mirage-tcpip Added 'error_message' functions https://github.com/mirage/mirage-tcpip/pull/98 I'd also like to apply this one, but it is a slight API change: mirage/mirage-block-xen Added explicit 'connect' to interface https://github.com/mirage/mirage-block-xen/pull/35 -- Dr Thomas Leonard http://0install.net/ GPG: 9242 9807 C985 3C07 44A6 8B9A AE07 8280 59A5 3CC1 GPG: DA98 25AE CAD0 8975 7CDA BD8E 0713 3F96 CA74 D8BA _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Mon Feb 02 16:38:44 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 02 Feb 2015 16:38:44 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YIK1M-0007wN-MF; Mon, 02 Feb 2015 16:38:44 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YIK1L-0007vt-8e for mirageos-devel@lists.xenproject.org; Mon, 02 Feb 2015 16:38:43 +0000 Received: from [85.158.143.35] by server-1.bemta-4.messagelabs.com id 2E/ED-03000-218AFC45; Mon, 02 Feb 2015 16:38:42 +0000 X-Env-Sender: daniel.buenzli@erratique.ch X-Msg-Ref: server-8.tower-21.messagelabs.com!1422895121!11984605!1 X-Originating-IP: [74.55.86.74] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNzQuNTUuODYuNzQgPT4gMzA4NTYz\n X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23905 invoked from network); 2 Feb 2015 16:38:42 -0000 Received: from mail6.webfaction.com (HELO smtp.webfaction.com) (74.55.86.74) by server-8.tower-21.messagelabs.com with SMTP; 2 Feb 2015 16:38:42 -0000 Received: from [172.20.10.2] (56-227.197-178.cust.bluewin.ch [178.197.227.56]) by smtp.webfaction.com (Postfix) with ESMTP id BD8DE20B60FE; Mon, 2 Feb 2015 16:38:40 +0000 (UTC) Date: Mon, 2 Feb 2015 17:38:35 +0100 From: =?utf-8?Q?Daniel_B=C3=BCnzli?= To: Christophe Troestler Message-ID: In-Reply-To: <20150202.014549.1883720051237442569.Christophe.Troestler@umons.ac.be> References: <20150202.014549.1883720051237442569.Christophe.Troestler@umons.ac.be> X-Mailer: sparrow 1.6.4 (build 1178) MIME-Version: 1.0 Content-Disposition: inline Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Error handling in Mirage - request for comments! X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org CgpMZSBsdW5kaSwgMiBmw6l2cmllciAyMDE1IMOgIDAxOjQ1LCBDaHJpc3RvcGhlIFRyb2VzdGxl ciBhIMOpY3JpdCA6Cgo+IFNpbmNlIE9DYW1sIHN1cHBvcnRzIGV4Y2VwdGlvbnMsIEkgdGhpbmsg dGhlcmUgaXMgbm8gZG91YnQgdGhhdCB3ZQo+IG11c3QgaGFuZGxlIHRoZW0gZWZmZWN0aXZlbHkg 4oCUIG5vdCBqdXN0IHdpcGUgdGhlbSB1bmRlciB0aGUgY2FycGV0IGFuZAo+IGxldCB0aGVtIGFi b3J0IHRoZSBwcm9ncmFtL3VuaWtlcm5lbC4gIAoKVGhhdCdzIGEgbGl0dGxlIGJpdCBsaWtlIHNh eWluZyBPQ2FtbCBzdXBwb3J0cyBvYmplY3RzIHRoZXJlZm9yZSB3ZSBzaG91bGQgcHJvZ3JhbSB3 aXRoIG9iamVjdHMuIFRoZSBmYWN0IGlzIHRoYXQgZXhjZXB0aW9ucyBhcmUgYWxtb3N0IGFsd2F5 cyBtaXN1c2VkIGluIE9DYW1sIEFQSSBkZXNpZ24sIG1vc3QgQVBJcyBzaG91bGQgb25seSBldmVy IHJhaXNlIEludmFsaWRfYXJndW1lbnQgYW5kIHRoYXQncyBhbGw7IGhvd2V2ZXIgdGhhdCdzIHJl YWxseSBub3Qgd2hhdCB5b3Ugc2VlIGluIHByYWN0aWNlIChJIGV2ZW4gcmVtZW1iZXIgaGF2aW5n IHNlZW4gbmV3IEFQSXMgdXNpbmcgdGhhdCBpbnNhbmUgTm90X2ZvdW5kIGV4Y2VwdGlvbi4uLiku ICAKCkJlc2lkZXMgeW91IGRvbid0IGhhdmUgdG8gYWJvcnQgdGhlIHVuaWtlcm5lbCB5b3UgY2Fu IGFsc28gaW5zdGFsbCBzb21lIGtpbmQgb2YgZ2xvYmFsIHRyYXAgdG8gaGFuZGxlIHVuY2F1Z2h0 IGV4Y2VwdGlvbnMgKHRoYXQncyBlLmcuIHRoZSB3YXkgZnV0IHdvcmtzIFsxXSkuIEkgdGhpbmsg aXQncyBtaXNndWlkZWQgdG8gdXNlIHRoZW0gYXMgYW4gZXJyb3IgcmVwb3J0aW5nIG1lY2hhbmlz bSB3ZSBoYXZlIG11Y2ggYmV0dGVyIHdheXMgYW5kIEkgaGlnaGx5IGRpc2FncmVlIHRoZXNlIGJl dHRlciB3YXlzIHdpbGwgYmUgaWdub3JlZCBpZiB5b3UgcHJvdmlkZSBnb29kIGNvbWJpbmF0b3Jz IHRvIGhhbmRsZSB0aGVtIOKAlCBtYXliZSBzbG9wcHkgcHJvZ3JhbW1lcnMgd2lsbCBpZ25vcmUg dGhlbSwgYnV0IHRoZW4gdGhlcmUncyBzbyBtdWNoIHlvdSBjYW4gZG8uIFRoZSBpbXBsaWNpdG5l c3Mgb2YgZXhjZXB0aW9ucyB3aWxsIDEpIGFsc28gbWFrZSBzbG9wcHkgcHJvZ3JhbW1lcnMgaWdu b3JlIHRoZW0gYnV0IDIpIG1ha2UgaXQgaGFyZGVyIHRvIGhhbmRsZSBlcnJvcnMgY29ycmVjdGx5 IGJ5IG5vbi1zbG9wcHkgcHJvZ3JhbW1lcnMuCgpCZXN0LAoKRGFuaWVsCgpbMV0gaHR0cDovL2Vy cmF0aXF1ZS5jaC9zb2Z0d2FyZS9mdXQvZG9jL0Z1dC5odG1sI2V4Y2VwdGlvbnMKCl9fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fCk1pcmFnZU9TLWRldmVsIG1h aWxpbmcgbGlzdApNaXJhZ2VPUy1kZXZlbEBsaXN0cy54ZW5wcm9qZWN0Lm9yZwpodHRwOi8vbGlz dHMueGVucHJvamVjdC5vcmcvY2dpLWJpbi9tYWlsbWFuL2xpc3RpbmZvL21pcmFnZW9zLWRldmVs Cg== From mirageos-devel-bounces@lists.xenproject.org Mon Feb 02 16:38:44 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 02 Feb 2015 16:38:44 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YIK1M-0007wN-MF; Mon, 02 Feb 2015 16:38:44 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YIK1L-0007vt-8e for mirageos-devel@lists.xenproject.org; Mon, 02 Feb 2015 16:38:43 +0000 Received: from [85.158.143.35] by server-1.bemta-4.messagelabs.com id 2E/ED-03000-218AFC45; Mon, 02 Feb 2015 16:38:42 +0000 X-Env-Sender: daniel.buenzli@erratique.ch X-Msg-Ref: server-8.tower-21.messagelabs.com!1422895121!11984605!1 X-Originating-IP: [74.55.86.74] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNzQuNTUuODYuNzQgPT4gMzA4NTYz\n X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23905 invoked from network); 2 Feb 2015 16:38:42 -0000 Received: from mail6.webfaction.com (HELO smtp.webfaction.com) (74.55.86.74) by server-8.tower-21.messagelabs.com with SMTP; 2 Feb 2015 16:38:42 -0000 Received: from [172.20.10.2] (56-227.197-178.cust.bluewin.ch [178.197.227.56]) by smtp.webfaction.com (Postfix) with ESMTP id BD8DE20B60FE; Mon, 2 Feb 2015 16:38:40 +0000 (UTC) Date: Mon, 2 Feb 2015 17:38:35 +0100 From: =?utf-8?Q?Daniel_B=C3=BCnzli?= To: Christophe Troestler Message-ID: In-Reply-To: <20150202.014549.1883720051237442569.Christophe.Troestler@umons.ac.be> References: <20150202.014549.1883720051237442569.Christophe.Troestler@umons.ac.be> X-Mailer: sparrow 1.6.4 (build 1178) MIME-Version: 1.0 Content-Disposition: inline Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Error handling in Mirage - request for comments! X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org CgpMZSBsdW5kaSwgMiBmw6l2cmllciAyMDE1IMOgIDAxOjQ1LCBDaHJpc3RvcGhlIFRyb2VzdGxl ciBhIMOpY3JpdCA6Cgo+IFNpbmNlIE9DYW1sIHN1cHBvcnRzIGV4Y2VwdGlvbnMsIEkgdGhpbmsg dGhlcmUgaXMgbm8gZG91YnQgdGhhdCB3ZQo+IG11c3QgaGFuZGxlIHRoZW0gZWZmZWN0aXZlbHkg 4oCUIG5vdCBqdXN0IHdpcGUgdGhlbSB1bmRlciB0aGUgY2FycGV0IGFuZAo+IGxldCB0aGVtIGFi b3J0IHRoZSBwcm9ncmFtL3VuaWtlcm5lbC4gIAoKVGhhdCdzIGEgbGl0dGxlIGJpdCBsaWtlIHNh eWluZyBPQ2FtbCBzdXBwb3J0cyBvYmplY3RzIHRoZXJlZm9yZSB3ZSBzaG91bGQgcHJvZ3JhbSB3 aXRoIG9iamVjdHMuIFRoZSBmYWN0IGlzIHRoYXQgZXhjZXB0aW9ucyBhcmUgYWxtb3N0IGFsd2F5 cyBtaXN1c2VkIGluIE9DYW1sIEFQSSBkZXNpZ24sIG1vc3QgQVBJcyBzaG91bGQgb25seSBldmVy IHJhaXNlIEludmFsaWRfYXJndW1lbnQgYW5kIHRoYXQncyBhbGw7IGhvd2V2ZXIgdGhhdCdzIHJl YWxseSBub3Qgd2hhdCB5b3Ugc2VlIGluIHByYWN0aWNlIChJIGV2ZW4gcmVtZW1iZXIgaGF2aW5n IHNlZW4gbmV3IEFQSXMgdXNpbmcgdGhhdCBpbnNhbmUgTm90X2ZvdW5kIGV4Y2VwdGlvbi4uLiku ICAKCkJlc2lkZXMgeW91IGRvbid0IGhhdmUgdG8gYWJvcnQgdGhlIHVuaWtlcm5lbCB5b3UgY2Fu IGFsc28gaW5zdGFsbCBzb21lIGtpbmQgb2YgZ2xvYmFsIHRyYXAgdG8gaGFuZGxlIHVuY2F1Z2h0 IGV4Y2VwdGlvbnMgKHRoYXQncyBlLmcuIHRoZSB3YXkgZnV0IHdvcmtzIFsxXSkuIEkgdGhpbmsg aXQncyBtaXNndWlkZWQgdG8gdXNlIHRoZW0gYXMgYW4gZXJyb3IgcmVwb3J0aW5nIG1lY2hhbmlz bSB3ZSBoYXZlIG11Y2ggYmV0dGVyIHdheXMgYW5kIEkgaGlnaGx5IGRpc2FncmVlIHRoZXNlIGJl dHRlciB3YXlzIHdpbGwgYmUgaWdub3JlZCBpZiB5b3UgcHJvdmlkZSBnb29kIGNvbWJpbmF0b3Jz IHRvIGhhbmRsZSB0aGVtIOKAlCBtYXliZSBzbG9wcHkgcHJvZ3JhbW1lcnMgd2lsbCBpZ25vcmUg dGhlbSwgYnV0IHRoZW4gdGhlcmUncyBzbyBtdWNoIHlvdSBjYW4gZG8uIFRoZSBpbXBsaWNpdG5l c3Mgb2YgZXhjZXB0aW9ucyB3aWxsIDEpIGFsc28gbWFrZSBzbG9wcHkgcHJvZ3JhbW1lcnMgaWdu b3JlIHRoZW0gYnV0IDIpIG1ha2UgaXQgaGFyZGVyIHRvIGhhbmRsZSBlcnJvcnMgY29ycmVjdGx5 IGJ5IG5vbi1zbG9wcHkgcHJvZ3JhbW1lcnMuCgpCZXN0LAoKRGFuaWVsCgpbMV0gaHR0cDovL2Vy cmF0aXF1ZS5jaC9zb2Z0d2FyZS9mdXQvZG9jL0Z1dC5odG1sI2V4Y2VwdGlvbnMKCl9fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fCk1pcmFnZU9TLWRldmVsIG1h aWxpbmcgbGlzdApNaXJhZ2VPUy1kZXZlbEBsaXN0cy54ZW5wcm9qZWN0Lm9yZwpodHRwOi8vbGlz dHMueGVucHJvamVjdC5vcmcvY2dpLWJpbi9tYWlsbWFuL2xpc3RpbmZvL21pcmFnZW9zLWRldmVs Cg== From mirageos-devel-bounces@lists.xenproject.org Mon Feb 02 17:49:28 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 02 Feb 2015 17:49:28 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YIL7k-0000zo-Ii; Mon, 02 Feb 2015 17:49:24 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YIL7i-0000zN-If for mirageos-devel@lists.xenproject.org; Mon, 02 Feb 2015 17:49:22 +0000 Received: from [85.158.143.35] by server-3.bemta-4.messagelabs.com id 6D/30-02754-1A8BFC45; Mon, 02 Feb 2015 17:49:21 +0000 X-Env-Sender: Dave.Scott@citrix.com X-Msg-Ref: server-9.tower-21.messagelabs.com!1422899360!12018309!1 X-Originating-IP: [185.25.65.24] X-SpamReason: No, hits=0.0 required=7.0 tests=received_headers: No Received headers X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7054 invoked from network); 2 Feb 2015 17:49:20 -0000 Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (185.25.65.24) by server-9.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 2 Feb 2015 17:49:20 -0000 X-IronPort-AV: E=Sophos;i="5.09,507,1418083200"; d="scan'208";a="30848028" From: Dave Scott To: Thomas Leonard Thread-Topic: [MirageOS-devel] Minor patches (connect / error_message) Thread-Index: AQHQPwY/S4McR9A+dES52eoAdqD925zdklIA Date: Mon, 2 Feb 2015 17:49:19 +0000 Message-ID: References: In-Reply-To: Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: Content-ID: <4A36576E2444204084ABF5A6560948B8@citrix.com> MIME-Version: 1.0 X-DLP: AMS1 Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Minor patches (connect / error_message) X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org > On 2 Feb 2015, at 16:35, Thomas Leonard wrote: > > I'd like to get some minor patches applied so I can remove some of my > branches. Unless someone objects today, I plan to apply these myself: They all look reasonable to me. Cheers, Dave > > mirage/mirage-block-unix Add explicit 'connect' to interface > https://github.com/mirage/mirage-block-unix/pull/20 > > mirage/mirage-net-xen Add explicit 'connect' function to interface > https://github.com/mirage/mirage-net-xen/pull/19 > > mirage/mirage-net-unix Add explicit 'connect' function to interface > https://github.com/mirage/mirage-net-unix/pull/10 > > mirage/mirage-tcpip Added 'error_message' functions > https://github.com/mirage/mirage-tcpip/pull/98 > > > I'd also like to apply this one, but it is a slight API change: > > mirage/mirage-block-xen Added explicit 'connect' to interface > https://github.com/mirage/mirage-block-xen/pull/35 > > > -- > Dr Thomas Leonard http://0install.net/ > GPG: 9242 9807 C985 3C07 44A6 8B9A AE07 8280 59A5 3CC1 > GPG: DA98 25AE CAD0 8975 7CDA BD8E 0713 3F96 CA74 D8BA > > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Mon Feb 02 17:49:28 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 02 Feb 2015 17:49:28 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YIL7k-0000zo-Ii; Mon, 02 Feb 2015 17:49:24 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YIL7i-0000zN-If for mirageos-devel@lists.xenproject.org; Mon, 02 Feb 2015 17:49:22 +0000 Received: from [85.158.143.35] by server-3.bemta-4.messagelabs.com id 6D/30-02754-1A8BFC45; Mon, 02 Feb 2015 17:49:21 +0000 X-Env-Sender: Dave.Scott@citrix.com X-Msg-Ref: server-9.tower-21.messagelabs.com!1422899360!12018309!1 X-Originating-IP: [185.25.65.24] X-SpamReason: No, hits=0.0 required=7.0 tests=received_headers: No Received headers X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7054 invoked from network); 2 Feb 2015 17:49:20 -0000 Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (185.25.65.24) by server-9.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 2 Feb 2015 17:49:20 -0000 X-IronPort-AV: E=Sophos;i="5.09,507,1418083200"; d="scan'208";a="30848028" From: Dave Scott To: Thomas Leonard Thread-Topic: [MirageOS-devel] Minor patches (connect / error_message) Thread-Index: AQHQPwY/S4McR9A+dES52eoAdqD925zdklIA Date: Mon, 2 Feb 2015 17:49:19 +0000 Message-ID: References: In-Reply-To: Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: Content-ID: <4A36576E2444204084ABF5A6560948B8@citrix.com> MIME-Version: 1.0 X-DLP: AMS1 Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Minor patches (connect / error_message) X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org > On 2 Feb 2015, at 16:35, Thomas Leonard wrote: > > I'd like to get some minor patches applied so I can remove some of my > branches. Unless someone objects today, I plan to apply these myself: They all look reasonable to me. Cheers, Dave > > mirage/mirage-block-unix Add explicit 'connect' to interface > https://github.com/mirage/mirage-block-unix/pull/20 > > mirage/mirage-net-xen Add explicit 'connect' function to interface > https://github.com/mirage/mirage-net-xen/pull/19 > > mirage/mirage-net-unix Add explicit 'connect' function to interface > https://github.com/mirage/mirage-net-unix/pull/10 > > mirage/mirage-tcpip Added 'error_message' functions > https://github.com/mirage/mirage-tcpip/pull/98 > > > I'd also like to apply this one, but it is a slight API change: > > mirage/mirage-block-xen Added explicit 'connect' to interface > https://github.com/mirage/mirage-block-xen/pull/35 > > > -- > Dr Thomas Leonard http://0install.net/ > GPG: 9242 9807 C985 3C07 44A6 8B9A AE07 8280 59A5 3CC1 > GPG: DA98 25AE CAD0 8975 7CDA BD8E 0713 3F96 CA74 D8BA > > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Mon Feb 02 20:37:30 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 02 Feb 2015 20:37:30 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YINkL-0006vY-3F; Mon, 02 Feb 2015 20:37:25 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YIL0R-0008Dg-49 for mirageos-devel@lists.xenproject.org; Mon, 02 Feb 2015 17:41:51 +0000 Received: from [85.158.143.35] by server-3.bemta-4.messagelabs.com id 02/19-02754-ED6BFC45; Mon, 02 Feb 2015 17:41:50 +0000 X-Env-Sender: Stefano.Stabellini@citrix.com X-Msg-Ref: server-16.tower-21.messagelabs.com!1422898908!8547464!1 X-Originating-IP: [66.165.176.89] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni44OSA9PiAyMDMwMDc=\n X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 14516 invoked from network); 2 Feb 2015 17:41:49 -0000 Received: from smtp.citrix.com (HELO SMTP.CITRIX.COM) (66.165.176.89) by server-16.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 2 Feb 2015 17:41:49 -0000 X-IronPort-AV: E=Sophos;i="5.09,507,1418083200"; d="scan'208";a="222508145" Received: from ukmail1.uk.xensource.com (10.80.16.128) by smtprelay.citrix.com (10.13.107.80) with Microsoft SMTP Server id 14.3.210.2; Mon, 2 Feb 2015 12:41:17 -0500 Received: from kaball.uk.xensource.com ([10.80.2.59]) by ukmail1.uk.xensource.com with esmtp (Exim 4.69) (envelope-from ) id 1YIKzs-0006vI-MZ; Mon, 02 Feb 2015 17:41:16 +0000 Date: Mon, 2 Feb 2015 17:40:52 +0000 From: Stefano Stabellini X-X-Sender: sstabellini@kaball.uk.xensource.com To: Dave Scott In-Reply-To: <0EEB9201-A222-4EF2-96A2-790FFDB78970@citrix.com> Message-ID: References: <0EEB9201-A222-4EF2-96A2-790FFDB78970@citrix.com> User-Agent: Alpine 2.02 (DEB 1266 2009-07-14) MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="1342847746-531783240-1422898852=:5246" X-DLP: MIA2 X-Mailman-Approved-At: Mon, 02 Feb 2015 20:37:23 +0000 Cc: mirageos-devel , Xen-devel Subject: Re: [MirageOS-devel] [Xen-devel] entropy for VMs X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --1342847746-531783240-1422898852=:5246 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: QUOTED-PRINTABLE On Sun, 1 Feb 2015, Dave Scott wrote: > Hi, >=20 > Mirage now has nice features like TLS[1] and therefore needs a good sourc= e of randomness to generate session keys. Mirage VMs are PV, so we can=E2= =80=99t use virtio-rng. We've created a prototype entropy server which may = be of interest to other people too: >=20 > https://github.com/mirage/xentropyd >=20 > This behaves a bit like xenconsoled: it watches for domains being created= and then connects to them via the console protocol. There is a little hand= shake[2] (to catch accidental screwups with the wrong console) and then the= daemon feeds random data into the console through a rate-limiter. Mirage= =E2=80=99s entropy driver can read the data from the console fairly easily[= 3]. I assume we could write a similar thing for linux too. >=20 > What do you think? (And does anyone know a better way (TM)?) I think it would be very useful in Linux too. > The code is still a bit of a prototype, and contains slightly forked vers= ions of core Mirage libraries-- I need to sort that out before a 1.0. >=20 > Cheers, > Dave >=20 > [1] http://openmirage.org/blog/introducing-ocaml-tls > [2] https://github.com/mirage/xentropyd/blob/master/doc/protocol.md > [3] https://github.com/djs55/mirage-entropy/blob/981b070d78ae407015b1e8de= db3141b05454366f/xen/entropy_xen.ml#L130 > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xen.org > http://lists.xen.org/xen-devel >=20 --1342847746-531783240-1422898852=:5246 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --1342847746-531783240-1422898852=:5246-- From mirageos-devel-bounces@lists.xenproject.org Mon Feb 02 20:37:30 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 02 Feb 2015 20:37:30 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YINkL-0006vY-3F; Mon, 02 Feb 2015 20:37:25 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YIL0R-0008Dg-49 for mirageos-devel@lists.xenproject.org; Mon, 02 Feb 2015 17:41:51 +0000 Received: from [85.158.143.35] by server-3.bemta-4.messagelabs.com id 02/19-02754-ED6BFC45; Mon, 02 Feb 2015 17:41:50 +0000 X-Env-Sender: Stefano.Stabellini@citrix.com X-Msg-Ref: server-16.tower-21.messagelabs.com!1422898908!8547464!1 X-Originating-IP: [66.165.176.89] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni44OSA9PiAyMDMwMDc=\n X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 14516 invoked from network); 2 Feb 2015 17:41:49 -0000 Received: from smtp.citrix.com (HELO SMTP.CITRIX.COM) (66.165.176.89) by server-16.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 2 Feb 2015 17:41:49 -0000 X-IronPort-AV: E=Sophos;i="5.09,507,1418083200"; d="scan'208";a="222508145" Received: from ukmail1.uk.xensource.com (10.80.16.128) by smtprelay.citrix.com (10.13.107.80) with Microsoft SMTP Server id 14.3.210.2; Mon, 2 Feb 2015 12:41:17 -0500 Received: from kaball.uk.xensource.com ([10.80.2.59]) by ukmail1.uk.xensource.com with esmtp (Exim 4.69) (envelope-from ) id 1YIKzs-0006vI-MZ; Mon, 02 Feb 2015 17:41:16 +0000 Date: Mon, 2 Feb 2015 17:40:52 +0000 From: Stefano Stabellini X-X-Sender: sstabellini@kaball.uk.xensource.com To: Dave Scott In-Reply-To: <0EEB9201-A222-4EF2-96A2-790FFDB78970@citrix.com> Message-ID: References: <0EEB9201-A222-4EF2-96A2-790FFDB78970@citrix.com> User-Agent: Alpine 2.02 (DEB 1266 2009-07-14) MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="1342847746-531783240-1422898852=:5246" X-DLP: MIA2 X-Mailman-Approved-At: Mon, 02 Feb 2015 20:37:23 +0000 Cc: mirageos-devel , Xen-devel Subject: Re: [MirageOS-devel] [Xen-devel] entropy for VMs X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --1342847746-531783240-1422898852=:5246 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: QUOTED-PRINTABLE On Sun, 1 Feb 2015, Dave Scott wrote: > Hi, >=20 > Mirage now has nice features like TLS[1] and therefore needs a good sourc= e of randomness to generate session keys. Mirage VMs are PV, so we can=E2= =80=99t use virtio-rng. We've created a prototype entropy server which may = be of interest to other people too: >=20 > https://github.com/mirage/xentropyd >=20 > This behaves a bit like xenconsoled: it watches for domains being created= and then connects to them via the console protocol. There is a little hand= shake[2] (to catch accidental screwups with the wrong console) and then the= daemon feeds random data into the console through a rate-limiter. Mirage= =E2=80=99s entropy driver can read the data from the console fairly easily[= 3]. I assume we could write a similar thing for linux too. >=20 > What do you think? (And does anyone know a better way (TM)?) I think it would be very useful in Linux too. > The code is still a bit of a prototype, and contains slightly forked vers= ions of core Mirage libraries-- I need to sort that out before a 1.0. >=20 > Cheers, > Dave >=20 > [1] http://openmirage.org/blog/introducing-ocaml-tls > [2] https://github.com/mirage/xentropyd/blob/master/doc/protocol.md > [3] https://github.com/djs55/mirage-entropy/blob/981b070d78ae407015b1e8de= db3141b05454366f/xen/entropy_xen.ml#L130 > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xen.org > http://lists.xen.org/xen-devel >=20 --1342847746-531783240-1422898852=:5246 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --1342847746-531783240-1422898852=:5246-- From mirageos-devel-bounces@lists.xenproject.org Tue Feb 03 15:59:56 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 03 Feb 2015 15:59:56 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YIftF-0000QV-Lp; Tue, 03 Feb 2015 15:59:49 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YIftD-0000QQ-Mb for mirageos-devel@lists.xenproject.org; Tue, 03 Feb 2015 15:59:47 +0000 Received: from [85.158.139.211] by server-6.bemta-5.messagelabs.com id 6C/8D-03165-370F0D45; Tue, 03 Feb 2015 15:59:47 +0000 X-Env-Sender: Christophe.TROESTLER@umons.ac.be X-Msg-Ref: server-4.tower-206.messagelabs.com!1422979186!10944397!1 X-Originating-IP: [157.56.112.61] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22837 invoked from network); 3 Feb 2015 15:59:46 -0000 Received: from mail-am1on0061.outbound.protection.outlook.com (HELO emea01-am1-obe.outbound.protection.outlook.com) (157.56.112.61) by server-4.tower-206.messagelabs.com with AES256-SHA encrypted SMTP; 3 Feb 2015 15:59:46 -0000 Received: from DB4PR05CA0016.eurprd05.prod.outlook.com (25.160.40.26) by DB4PR05MB526.eurprd05.prod.outlook.com (10.242.154.28) with Microsoft SMTP Server (TLS) id 15.1.75.20; Tue, 3 Feb 2015 15:55:58 +0000 Received: from AM1FFO11FD021.protection.gbl (2a01:111:f400:7e00::101) by DB4PR05CA0016.outlook.office365.com (2a01:111:e400:9850::26) with Microsoft SMTP Server (TLS) id 15.1.75.20 via Frontend Transport; Tue, 3 Feb 2015 15:55:59 +0000 Received: from smtp.umons.ac.be (193.190.208.132) by AM1FFO11FD021.mail.protection.outlook.com (10.174.64.210) with Microsoft SMTP Server (TLS) id 15.1.87.10 via Frontend Transport; Tue, 3 Feb 2015 15:55:57 +0000 Received: from poincare (10.104.2.63) by smtp.umons.ac.be (10.104.2.84) with Microsoft SMTP Server (TLS) id 14.3.224.2; Tue, 3 Feb 2015 16:55:49 +0100 Received: from localhost ([::1]) by poincare with esmtp (Exim 4.84) (envelope-from ) id 1YIfpM-0000jB-LP; Tue, 03 Feb 2015 16:55:48 +0100 Date: Tue, 3 Feb 2015 16:55:48 +0100 Message-ID: <20150203.165548.1818962153128895170.Christophe.Troestler@umons.ac.be> To: From: Christophe Troestler In-Reply-To: References: <20150202.014549.1883720051237442569.Christophe.Troestler@umons.ac.be> X-Face: #2fb%mPx>rRL@4ff~TVgZ"<[:,oL"`TUEGK/[8/qb58~C>jR(x4A+v/n)7BgpEtIph_neoLKJBq0JBY9:}8v|j Organization: Universite de Mons (http://math.umons.ac.be/anum/) X-Mailer: Mew version 6.6 on Emacs 24.4 / Mule 6.0 (HANACHIRUSATO) MIME-Version: 1.0 Content-Length: 3255 X-Originating-IP: [10.104.2.63] X-EOPAttributedMessage: 0 X-Matching-Connectors: 130674525584457031; (9b551343-d075-4328-d154-08d0574c44b8,aa519c6d-c5b7-417d-4ec3-08d1170c20a9); (9b551343-d075-4328-d154-08d0574c44b8,aa519c6d-c5b7-417d-4ec3-08d1170c20a9) Received-SPF: Pass (protection.outlook.com: domain of umons.ac.be designates 193.190.208.132 as permitted sender) receiver=protection.outlook.com; client-ip=193.190.208.132; helo=smtp.umons.ac.be; X-Forefront-Antispam-Report: CIP:193.190.208.132; CTRY:BE; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(10009020)(6009001)(51704005)(24454002)(50466002)(50226001)(16796002)(50986999)(226693001)(76506005)(76176999)(57986006)(87936001)(86362001)(103116003)(23676002)(36756003)(74482002)(2950100001)(46102003)(6806004)(77156002)(47776003)(92566002)(62966003)(2351001)(106466001)(110136001); DIR:OUT; SFP:1101; SCL:1; SRVR:DB4PR05MB526; H:smtp.umons.ac.be; FPR:; SPF:None; MLV:sfv; LANG:en; X-Microsoft-Antispam: UriScan:; X-Microsoft-Antispam: BCL:0;PCL:0;RULEID:;SRVR:DB4PR05MB526; X-Exchange-Antispam-Report-Test: UriScan:; X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(601004); SRVR:DB4PR05MB526; X-Forefront-PRVS: 0476D4AB88 X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(400005)(401004); SRVR:DB4PR05MB526; X-MS-Exchange-CrossTenant-OriginalArrivalTime: 03 Feb 2015 15:55:57.3224 (UTC) X-MS-Exchange-CrossTenant-Id: 5afe0b00-7697-4969-b663-5eab37d5f47e X-MS-Exchange-CrossTenant-OriginalAttributedTenantConnectingIp: TenantId=5afe0b00-7697-4969-b663-5eab37d5f47e; Ip=[193.190.208.132] X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB4PR05MB526 Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Error handling in Mirage - request for comments! X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org T24gTW9uLCAyIEZlYiAyMDE1IDE3OjM4OjM1ICswMTAwLCBEYW5pZWwgQsO8bnpsaSB3cm90ZToK PiAKPiBMZSBsdW5kaSwgMiBmw6l2cmllciAyMDE1IMOgIDAxOjQ1LCBDaHJpc3RvcGhlIFRyb2Vz dGxlciBhIMOpY3JpdCA6Cj4gCj4gPiBTaW5jZSBPQ2FtbCBzdXBwb3J0cyBleGNlcHRpb25zLCBJ IHRoaW5rIHRoZXJlIGlzIG5vIGRvdWJ0IHRoYXQgd2UKPiA+IG11c3QgaGFuZGxlIHRoZW0gZWZm ZWN0aXZlbHkg4oCUIG5vdCBqdXN0IHdpcGUgdGhlbSB1bmRlciB0aGUgY2FycGV0IGFuZAo+ID4g bGV0IHRoZW0gYWJvcnQgdGhlIHByb2dyYW0vdW5pa2VybmVsLiAgCj4gCj4gVGhhdCdzIGEgbGl0 dGxlIGJpdCBsaWtlIHNheWluZyBPQ2FtbCBzdXBwb3J0cyBvYmplY3RzIHRoZXJlZm9yZSB3ZQo+ IHNob3VsZCBwcm9ncmFtIHdpdGggb2JqZWN0cy4gVGhlIGZhY3QgaXMgdGhhdCBleGNlcHRpb25z IGFyZSBhbG1vc3QKPiBhbHdheXMgbWlzdXNlZCBpbiBPQ2FtbCBBUEkgZGVzaWduLCBtb3N0IEFQ SXMgc2hvdWxkIG9ubHkgZXZlciByYWlzZQo+IEludmFsaWRfYXJndW1lbnQgYW5kIHRoYXQncyBh bGw7IGhvd2V2ZXIgdGhhdCdzIHJlYWxseSBub3Qgd2hhdCB5b3UKPiBzZWUgaW4gcHJhY3RpY2Ug KEkgZXZlbiByZW1lbWJlciBoYXZpbmcgc2VlbiBuZXcgQVBJcyB1c2luZyB0aGF0Cj4gaW5zYW5l IE5vdF9mb3VuZCBleGNlcHRpb24uLi4pLgoKWW91IGFyZSBpbiBmYWN0IGNvbmN1cnJpbmcgd2l0 aCBtZSEgOy0pIEkgZGlkIG5vdCBzYXkgd2UgbXVzdCAqdXNlKgpleGNlcHRpb25zLCBJIHNhaWQg d2UgbXVzdCAqaGFuZGxlKiB0aGVtIGJlY2F1c2UsIHByZWNpc2VseSwgdGhlcmUKd2lsbCBiZSBs aWJyYXJpZXMgdGhhdCBvbmUgd2FudHMvbmVlZHMgdG8gdXNlIGFuZCBvbmUgZG9lcyBub3Qgd2Fu dAp0aGF0IHRoZWlyIChtaXMpdXNlIG9mIGV4Y2VwdGlvbnMgY2F1c2VzIGhhdm9jLiAgTm8gbmVl ZCB0byB0ZWxsIHlvdQp0aGF0IHRoZSBkaWZmZXJlbmNlIGJldHdlZW4gb2JqZWN0cyBhbmQgZXhj ZXB0aW9ucyBpcyB0aGF0IHRoZSBmb3JtZXIKY2Fubm90IHBvcCB1cCBhcyB1bmludml0ZWQgZ3Vl c3RzIHdoaWxlIHRoZSBsYXR0ZXIgY2FuIGNvbWUg4oCUIGFzIHlvdQptZW50aW9uIOKAlCBmcm9t IGFueSBleHRlcm5hbCBsaWJyYXJ5IGFuZCBkaXNydXB0IHRoZSBpbnRlbmRlZCBmbG93IG9mCnRo ZSBwcm9ncmFtLiAgSGVuY2UgdGhlIG5lZWQgdG8gdGFrZSB0aGVtIGludG8gYWNjb3VudCBpbiB0 aGUgZGVzaWduLgoKPiBCZXNpZGVzIHlvdSBkb24ndCBoYXZlIHRvIGFib3J0IHRoZSB1bmlrZXJu ZWwgeW91IGNhbiBhbHNvIGluc3RhbGwKPiBzb21lIGtpbmQgb2YgZ2xvYmFsIHRyYXAgdG8gaGFu ZGxlIHVuY2F1Z2h0IGV4Y2VwdGlvbnMgKHRoYXQncwo+IGUuZy4gdGhlIHdheSBmdXQgd29ya3Mg WzFdKS4KCkkgdGhpbmsgd2UgYXJlIGluIGFncmVlbWVudCBoZXJlIOKAlCB0aGUg4oCccnVu4oCd IEkgcHJvcG9zZWQgZG9lcyBwcmVjaXNlbHkKdGhhdCDigJQgYnV0IHNvbWV0aW1lcyB0aGlzIGlz IHRvbyBsYXRlLCBzbyDigJxjYXRjaF9leG7igJ0gaXMgYWxzbyB1c2VmdWwuCgo+IEkgdGhpbmsg aXQncyBtaXNndWlkZWQgdG8gdXNlIHRoZW0gYXMgYW4gZXJyb3IgcmVwb3J0aW5nIG1lY2hhbmlz bQo+IHdlIGhhdmUgbXVjaCBiZXR0ZXIgd2F5cyBhbmQgSSBoaWdobHkgZGlzYWdyZWUgdGhlc2Ug YmV0dGVyIHdheXMKPiB3aWxsIGJlIGlnbm9yZWQgaWYgeW91IHByb3ZpZGUgZ29vZCBjb21iaW5h dG9ycyB0byBoYW5kbGUgdGhlbSDigJQKPiBtYXliZSBzbG9wcHkgcHJvZ3JhbW1lcnMgd2lsbCBp Z25vcmUgdGhlbSwgYnV0IHRoZW4gdGhlcmUncyBzbyBtdWNoCj4geW91IGNhbiBkby4gVGhlIGlt cGxpY2l0bmVzcyBvZiBleGNlcHRpb25zIHdpbGwgMSkgYWxzbyBtYWtlIHNsb3BweQo+IHByb2dy YW1tZXJzIGlnbm9yZSB0aGVtIGJ1dCAyKSBtYWtlIGl0IGhhcmRlciB0byBoYW5kbGUgZXJyb3Jz Cj4gY29ycmVjdGx5IGJ5IG5vbi1zbG9wcHkgcHJvZ3JhbW1lcnMuCgpQbGVhc2UgbGF5IGRvd24g YSBjb25jcmV0ZSBpbnRlcmZhY2Ugc2hvd2luZyBvZiB3aGF0IHlvdSBtZWFuLiAgSQp0aGluayB3 ZSBhbGwgYWdyZWUgb24gdGhlIGdvYWwgb2Ygd3JpdGluZyByb2J1c3Qgc29mdHdhcmUsIHdlIG5l ZWQgdG8KbW92ZSB0aGUgZGlzY3Vzc2lvbiB0byBjb25jcmV0ZSBwcm9wb3NhbHMuCgpDaGVlcnMs CkMuCgpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwpNaXJh Z2VPUy1kZXZlbCBtYWlsaW5nIGxpc3QKTWlyYWdlT1MtZGV2ZWxAbGlzdHMueGVucHJvamVjdC5v cmcKaHR0cDovL2xpc3RzLnhlbnByb2plY3Qub3JnL2NnaS1iaW4vbWFpbG1hbi9saXN0aW5mby9t aXJhZ2Vvcy1kZXZlbAo= From mirageos-devel-bounces@lists.xenproject.org Tue Feb 03 15:59:56 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 03 Feb 2015 15:59:56 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YIftF-0000QV-Lp; Tue, 03 Feb 2015 15:59:49 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YIftD-0000QQ-Mb for mirageos-devel@lists.xenproject.org; Tue, 03 Feb 2015 15:59:47 +0000 Received: from [85.158.139.211] by server-6.bemta-5.messagelabs.com id 6C/8D-03165-370F0D45; Tue, 03 Feb 2015 15:59:47 +0000 X-Env-Sender: Christophe.TROESTLER@umons.ac.be X-Msg-Ref: server-4.tower-206.messagelabs.com!1422979186!10944397!1 X-Originating-IP: [157.56.112.61] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22837 invoked from network); 3 Feb 2015 15:59:46 -0000 Received: from mail-am1on0061.outbound.protection.outlook.com (HELO emea01-am1-obe.outbound.protection.outlook.com) (157.56.112.61) by server-4.tower-206.messagelabs.com with AES256-SHA encrypted SMTP; 3 Feb 2015 15:59:46 -0000 Received: from DB4PR05CA0016.eurprd05.prod.outlook.com (25.160.40.26) by DB4PR05MB526.eurprd05.prod.outlook.com (10.242.154.28) with Microsoft SMTP Server (TLS) id 15.1.75.20; Tue, 3 Feb 2015 15:55:58 +0000 Received: from AM1FFO11FD021.protection.gbl (2a01:111:f400:7e00::101) by DB4PR05CA0016.outlook.office365.com (2a01:111:e400:9850::26) with Microsoft SMTP Server (TLS) id 15.1.75.20 via Frontend Transport; Tue, 3 Feb 2015 15:55:59 +0000 Received: from smtp.umons.ac.be (193.190.208.132) by AM1FFO11FD021.mail.protection.outlook.com (10.174.64.210) with Microsoft SMTP Server (TLS) id 15.1.87.10 via Frontend Transport; Tue, 3 Feb 2015 15:55:57 +0000 Received: from poincare (10.104.2.63) by smtp.umons.ac.be (10.104.2.84) with Microsoft SMTP Server (TLS) id 14.3.224.2; Tue, 3 Feb 2015 16:55:49 +0100 Received: from localhost ([::1]) by poincare with esmtp (Exim 4.84) (envelope-from ) id 1YIfpM-0000jB-LP; Tue, 03 Feb 2015 16:55:48 +0100 Date: Tue, 3 Feb 2015 16:55:48 +0100 Message-ID: <20150203.165548.1818962153128895170.Christophe.Troestler@umons.ac.be> To: From: Christophe Troestler In-Reply-To: References: <20150202.014549.1883720051237442569.Christophe.Troestler@umons.ac.be> X-Face: #2fb%mPx>rRL@4ff~TVgZ"<[:,oL"`TUEGK/[8/qb58~C>jR(x4A+v/n)7BgpEtIph_neoLKJBq0JBY9:}8v|j Organization: Universite de Mons (http://math.umons.ac.be/anum/) X-Mailer: Mew version 6.6 on Emacs 24.4 / Mule 6.0 (HANACHIRUSATO) MIME-Version: 1.0 Content-Length: 3255 X-Originating-IP: [10.104.2.63] X-EOPAttributedMessage: 0 X-Matching-Connectors: 130674525584457031; (9b551343-d075-4328-d154-08d0574c44b8,aa519c6d-c5b7-417d-4ec3-08d1170c20a9); (9b551343-d075-4328-d154-08d0574c44b8,aa519c6d-c5b7-417d-4ec3-08d1170c20a9) Received-SPF: Pass (protection.outlook.com: domain of umons.ac.be designates 193.190.208.132 as permitted sender) receiver=protection.outlook.com; client-ip=193.190.208.132; helo=smtp.umons.ac.be; X-Forefront-Antispam-Report: CIP:193.190.208.132; CTRY:BE; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(10009020)(6009001)(51704005)(24454002)(50466002)(50226001)(16796002)(50986999)(226693001)(76506005)(76176999)(57986006)(87936001)(86362001)(103116003)(23676002)(36756003)(74482002)(2950100001)(46102003)(6806004)(77156002)(47776003)(92566002)(62966003)(2351001)(106466001)(110136001); DIR:OUT; SFP:1101; SCL:1; SRVR:DB4PR05MB526; H:smtp.umons.ac.be; FPR:; SPF:None; MLV:sfv; LANG:en; X-Microsoft-Antispam: UriScan:; X-Microsoft-Antispam: BCL:0;PCL:0;RULEID:;SRVR:DB4PR05MB526; X-Exchange-Antispam-Report-Test: UriScan:; X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(601004); SRVR:DB4PR05MB526; X-Forefront-PRVS: 0476D4AB88 X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(400005)(401004); SRVR:DB4PR05MB526; X-MS-Exchange-CrossTenant-OriginalArrivalTime: 03 Feb 2015 15:55:57.3224 (UTC) X-MS-Exchange-CrossTenant-Id: 5afe0b00-7697-4969-b663-5eab37d5f47e X-MS-Exchange-CrossTenant-OriginalAttributedTenantConnectingIp: TenantId=5afe0b00-7697-4969-b663-5eab37d5f47e; Ip=[193.190.208.132] X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB4PR05MB526 Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Error handling in Mirage - request for comments! X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org T24gTW9uLCAyIEZlYiAyMDE1IDE3OjM4OjM1ICswMTAwLCBEYW5pZWwgQsO8bnpsaSB3cm90ZToK PiAKPiBMZSBsdW5kaSwgMiBmw6l2cmllciAyMDE1IMOgIDAxOjQ1LCBDaHJpc3RvcGhlIFRyb2Vz dGxlciBhIMOpY3JpdCA6Cj4gCj4gPiBTaW5jZSBPQ2FtbCBzdXBwb3J0cyBleGNlcHRpb25zLCBJ IHRoaW5rIHRoZXJlIGlzIG5vIGRvdWJ0IHRoYXQgd2UKPiA+IG11c3QgaGFuZGxlIHRoZW0gZWZm ZWN0aXZlbHkg4oCUIG5vdCBqdXN0IHdpcGUgdGhlbSB1bmRlciB0aGUgY2FycGV0IGFuZAo+ID4g bGV0IHRoZW0gYWJvcnQgdGhlIHByb2dyYW0vdW5pa2VybmVsLiAgCj4gCj4gVGhhdCdzIGEgbGl0 dGxlIGJpdCBsaWtlIHNheWluZyBPQ2FtbCBzdXBwb3J0cyBvYmplY3RzIHRoZXJlZm9yZSB3ZQo+ IHNob3VsZCBwcm9ncmFtIHdpdGggb2JqZWN0cy4gVGhlIGZhY3QgaXMgdGhhdCBleGNlcHRpb25z IGFyZSBhbG1vc3QKPiBhbHdheXMgbWlzdXNlZCBpbiBPQ2FtbCBBUEkgZGVzaWduLCBtb3N0IEFQ SXMgc2hvdWxkIG9ubHkgZXZlciByYWlzZQo+IEludmFsaWRfYXJndW1lbnQgYW5kIHRoYXQncyBh bGw7IGhvd2V2ZXIgdGhhdCdzIHJlYWxseSBub3Qgd2hhdCB5b3UKPiBzZWUgaW4gcHJhY3RpY2Ug KEkgZXZlbiByZW1lbWJlciBoYXZpbmcgc2VlbiBuZXcgQVBJcyB1c2luZyB0aGF0Cj4gaW5zYW5l IE5vdF9mb3VuZCBleGNlcHRpb24uLi4pLgoKWW91IGFyZSBpbiBmYWN0IGNvbmN1cnJpbmcgd2l0 aCBtZSEgOy0pIEkgZGlkIG5vdCBzYXkgd2UgbXVzdCAqdXNlKgpleGNlcHRpb25zLCBJIHNhaWQg d2UgbXVzdCAqaGFuZGxlKiB0aGVtIGJlY2F1c2UsIHByZWNpc2VseSwgdGhlcmUKd2lsbCBiZSBs aWJyYXJpZXMgdGhhdCBvbmUgd2FudHMvbmVlZHMgdG8gdXNlIGFuZCBvbmUgZG9lcyBub3Qgd2Fu dAp0aGF0IHRoZWlyIChtaXMpdXNlIG9mIGV4Y2VwdGlvbnMgY2F1c2VzIGhhdm9jLiAgTm8gbmVl ZCB0byB0ZWxsIHlvdQp0aGF0IHRoZSBkaWZmZXJlbmNlIGJldHdlZW4gb2JqZWN0cyBhbmQgZXhj ZXB0aW9ucyBpcyB0aGF0IHRoZSBmb3JtZXIKY2Fubm90IHBvcCB1cCBhcyB1bmludml0ZWQgZ3Vl c3RzIHdoaWxlIHRoZSBsYXR0ZXIgY2FuIGNvbWUg4oCUIGFzIHlvdQptZW50aW9uIOKAlCBmcm9t IGFueSBleHRlcm5hbCBsaWJyYXJ5IGFuZCBkaXNydXB0IHRoZSBpbnRlbmRlZCBmbG93IG9mCnRo ZSBwcm9ncmFtLiAgSGVuY2UgdGhlIG5lZWQgdG8gdGFrZSB0aGVtIGludG8gYWNjb3VudCBpbiB0 aGUgZGVzaWduLgoKPiBCZXNpZGVzIHlvdSBkb24ndCBoYXZlIHRvIGFib3J0IHRoZSB1bmlrZXJu ZWwgeW91IGNhbiBhbHNvIGluc3RhbGwKPiBzb21lIGtpbmQgb2YgZ2xvYmFsIHRyYXAgdG8gaGFu ZGxlIHVuY2F1Z2h0IGV4Y2VwdGlvbnMgKHRoYXQncwo+IGUuZy4gdGhlIHdheSBmdXQgd29ya3Mg WzFdKS4KCkkgdGhpbmsgd2UgYXJlIGluIGFncmVlbWVudCBoZXJlIOKAlCB0aGUg4oCccnVu4oCd IEkgcHJvcG9zZWQgZG9lcyBwcmVjaXNlbHkKdGhhdCDigJQgYnV0IHNvbWV0aW1lcyB0aGlzIGlz IHRvbyBsYXRlLCBzbyDigJxjYXRjaF9leG7igJ0gaXMgYWxzbyB1c2VmdWwuCgo+IEkgdGhpbmsg aXQncyBtaXNndWlkZWQgdG8gdXNlIHRoZW0gYXMgYW4gZXJyb3IgcmVwb3J0aW5nIG1lY2hhbmlz bQo+IHdlIGhhdmUgbXVjaCBiZXR0ZXIgd2F5cyBhbmQgSSBoaWdobHkgZGlzYWdyZWUgdGhlc2Ug YmV0dGVyIHdheXMKPiB3aWxsIGJlIGlnbm9yZWQgaWYgeW91IHByb3ZpZGUgZ29vZCBjb21iaW5h dG9ycyB0byBoYW5kbGUgdGhlbSDigJQKPiBtYXliZSBzbG9wcHkgcHJvZ3JhbW1lcnMgd2lsbCBp Z25vcmUgdGhlbSwgYnV0IHRoZW4gdGhlcmUncyBzbyBtdWNoCj4geW91IGNhbiBkby4gVGhlIGlt cGxpY2l0bmVzcyBvZiBleGNlcHRpb25zIHdpbGwgMSkgYWxzbyBtYWtlIHNsb3BweQo+IHByb2dy YW1tZXJzIGlnbm9yZSB0aGVtIGJ1dCAyKSBtYWtlIGl0IGhhcmRlciB0byBoYW5kbGUgZXJyb3Jz Cj4gY29ycmVjdGx5IGJ5IG5vbi1zbG9wcHkgcHJvZ3JhbW1lcnMuCgpQbGVhc2UgbGF5IGRvd24g YSBjb25jcmV0ZSBpbnRlcmZhY2Ugc2hvd2luZyBvZiB3aGF0IHlvdSBtZWFuLiAgSQp0aGluayB3 ZSBhbGwgYWdyZWUgb24gdGhlIGdvYWwgb2Ygd3JpdGluZyByb2J1c3Qgc29mdHdhcmUsIHdlIG5l ZWQgdG8KbW92ZSB0aGUgZGlzY3Vzc2lvbiB0byBjb25jcmV0ZSBwcm9wb3NhbHMuCgpDaGVlcnMs CkMuCgpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwpNaXJh Z2VPUy1kZXZlbCBtYWlsaW5nIGxpc3QKTWlyYWdlT1MtZGV2ZWxAbGlzdHMueGVucHJvamVjdC5v cmcKaHR0cDovL2xpc3RzLnhlbnByb2plY3Qub3JnL2NnaS1iaW4vbWFpbG1hbi9saXN0aW5mby9t aXJhZ2Vvcy1kZXZlbAo= From mirageos-devel-bounces@lists.xenproject.org Tue Feb 03 17:11:11 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 03 Feb 2015 17:11:11 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YIh0C-0001Ir-WD; Tue, 03 Feb 2015 17:11:04 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YIh0B-0001Il-Ne for mirageos-devel@lists.xenproject.org; Tue, 03 Feb 2015 17:11:03 +0000 Received: from [193.109.254.147] by server-16.bemta-14.messagelabs.com id D3/24-02639-72101D45; Tue, 03 Feb 2015 17:11:03 +0000 X-Env-Sender: daniel.buenzli@erratique.ch X-Msg-Ref: server-12.tower-27.messagelabs.com!1422983461!12590749!1 X-Originating-IP: [74.55.86.74] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNzQuNTUuODYuNzQgPT4gMzA4NTYz\n X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27061 invoked from network); 3 Feb 2015 17:11:01 -0000 Received: from mail6.webfaction.com (HELO smtp.webfaction.com) (74.55.86.74) by server-12.tower-27.messagelabs.com with SMTP; 3 Feb 2015 17:11:01 -0000 Received: from [172.20.10.2] (227-224.197-178.cust.bluewin.ch [178.197.224.227]) by smtp.webfaction.com (Postfix) with ESMTP id 9127E26EA8DF; Tue, 3 Feb 2015 17:11:00 +0000 (UTC) Date: Tue, 3 Feb 2015 18:10:57 +0100 From: =?utf-8?Q?Daniel_B=C3=BCnzli?= To: Christophe Troestler Message-ID: <0235E905E5DE4F3B9422F8A37DC74FEB@erratique.ch> In-Reply-To: <20150203.165548.1818962153128895170.Christophe.Troestler@umons.ac.be> References: <20150202.014549.1883720051237442569.Christophe.Troestler@umons.ac.be> <20150203.165548.1818962153128895170.Christophe.Troestler@umons.ac.be> X-Mailer: sparrow 1.6.4 (build 1178) MIME-Version: 1.0 Content-Disposition: inline Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Error handling in Mirage - request for comments! X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org TGUgbWFyZGksIDMgZsOpdnJpZXIgMjAxNSDDoCAxNjo1NSwgQ2hyaXN0b3BoZSBUcm9lc3RsZXIg YSDDqWNyaXQgOgo+IFBsZWFzZSBsYXkgZG93biBhIGNvbmNyZXRlIGludGVyZmFjZSBzaG93aW5n IG9mIHdoYXQgeW91IG1lYW4uIEkKPiB0aGluayB3ZSBhbGwgYWdyZWUgb24gdGhlIGdvYWwgb2Yg d3JpdGluZyByb2J1c3Qgc29mdHdhcmUsIHdlIG5lZWQgdG8KPiBtb3ZlIHRoZSBkaXNjdXNzaW9u IHRvIGNvbmNyZXRlIHByb3Bvc2Fscy4KClNvcnJ5IGRvbid0IGhhdmUgdGhlIHRpbWUgdG8gd29y ayBvbiB0aGlzOyB0aGVzZSB0aGluZ3MgY29tZSBvdXQgb2Ygd3JpdGluZyBjb2RlLiBCdXQgYXMg YSBzdGFydCBJIGRvbid0IHNlZSB3aGF0J3MgdGhlIHByb2JsZW0gd2l0aCB0aGUgYmFzaWMgcmVz dWx0IG1vbmFkIGV2ZXJ5Ym9keSBrbm93cyAoZS5nLiBzZWUgaGVyZSBbMSwyXSkgYWxvbmcgd2l0 aCBhIGZldyB3aXRoX3Jlc291cmNlIGNvbWJpbmF0b3JzIGJhc2VkIG9uIHNvbWUga2luZCBvZiBg ZmluYWxseWAgWzNdIGFuZCBzdGljayB0byBwb2x5bW9ycGhpYyB2YXJpYW50IGVycm9ycyDigJQg YWxvbmcsIG9mIGNvdXJzZSwgd2l0aCBGb3JtYXQgcHJldHR5IHByaW50ZXJzIGZvciB0aGVzZSBz b21ldGhpbmcgdGhhdCBpcyBvZnRlbiBhbm5veWluZ2x5IGFic2VudCBpbiBBUElzLiBBbmQgSSB3 b3VsZCBjb21wbGV0ZWx5IGZvcmdldCBhYm91dCB1c2luZyBsd3QncyBmYWlsZWQgc3RhdGUgKGku ZS4gb25seSB0byB0cmFwIHVuZXhwZWN0ZWQgZXhjZXB0aW9ucyBhdCB0aGUgaGlnaGVzdCBsZXZl bCkuCgpCZXN0LAogIApEYW5pZWwKClsxXSAgClRoaXMgZGVhbHMgb25seSB3aXRoIHN0cmluZyBl cnJvcnMgc28gaXQgc2hvdWxkIGJlIGdlbmVyYWxpemVkIHRvIFsyXSwgYnV0IGEgZmV3IG9mIHRo ZSBlcnJvciBoYW5kbGluZwpjb21iaW5hdG9ycyBtYXkgYmUgaW50ZXJlc3RpbmcuICAKCmh0dHBz Oi8vZ2l0aHViLmNvbS9zYW1vaHQvYXNzZW1ibGFnZS9ibG9iL21hc3Rlci9saWIvYXNzZW1ibGFn ZS5tbGkjTDcwOC1MNzQ0CgpGb3IgZXhhbXBsZSBgcmV3b3JkX2Vycm9yYCBhIHF1aWNrIGNvbWJp bmF0b3IgdGhhdCBhbGxvd3MgdG8gdHJhbnNmb3JtIGEgbG93ZXItbGV2ZWwgZXJyb3IgdG8gYSBo aWdoZXIgbGV2ZWwgb25lLCBpLmUuIGdpdmUgbW9yZSBjb250ZXh0IGhpZ2hlciB1cCB3aGVuIHlv dSBoYXZlIHRoZSBpbmZvIGFib3V0IHdoYXQgeW91IGFyZSBkb2luZy4gU2luY2Ugd2UgYXJlIHVz aW5nIHN0cmluZ3MgaGVyZSBpdCdzIGFsc28gZWFzeSB0byBzdGFjayB0aGUgZXJyb3JzIGlmIHlv dSB3aXNoIHNvICh+cmVwbGFjZTpmYWxzZSBhcmd1bWVudCkgZnJvbSB0aGUgbG93ZXN0LWxldmVs IG9mIHdoYXQgd2VudCB3cm9uZyAoZS5nLiB0aGUgYWN0dWFsIHV0aWxpdHkgaW52b2NhdGlvbiBl cnJvcikgdG8gd2hhdCB5b3Ugd2VyZSB0cnlpbmcgdG8gZG8gKGUuZy4gZGV0ZXJtaW5lIHRoZSBu dW1iZXIgb2YgcHJvY2Vzc29ycyBpbiB0aGUgc3lzdGVtKSB3aGljaCBtYWtlcyBlcnJvciBkaWFn bm9zaXMgbXVjaCBlYXNpZXIgKGNvbnRleHQgKyBubyBlcnJvciBpbmZvIGlzIGxvc3QpLiBOb3Qg dGhhdCBpdCB3b3VsZG4ndCBiZSBpbXBvc3NpYmxlIHdpdGggbGlzdHMgb2YgcG9seXZhcnMsIGJ1 dCBvbmUgaGFzIHRvIHNlZSBob3cgaXQgY29tZXMgb3V0IGluIHByYWN0aWNlLiBBIGZldyBleGFt cGxlczoKCmh0dHBzOi8vZ2l0aHViLmNvbS9zYW1vaHQvYXNzZW1ibGFnZS9ibG9iL21hc3Rlci9s aWIvYXNfY29uZi5tbCNMNDIwLUw0MjgKaHR0cHM6Ly9naXRodWIuY29tL3NhbW9odC9hc3NlbWJs YWdlL2Jsb2IvbWFzdGVyL2xpYi9hc19jb25mLm1sI0w1NDMtTDU0OAoKWzJdClRoaXMgaXMgdGhl IGNsYXNzaWNhbCBnZW5lcmFsaXplZCByZXN1bHQgdHlwZSBmb3IgZGVhbGluZyB3aXRoIGVycm9y cy4gIApodHRwOi8vZXJyYXRpcXVlLmNoL3NvZnR3YXJlL2Z1dC9kb2MvRnV0Lmh0bWwjVFlQRXJl c3VsdApodHRwOi8vZXJyYXRpcXVlLmNoL3NvZnR3YXJlL2Z1dC9kb2MvRnV0Lmh0bWwjVkFMKCY+ Pj0pIChodHRwOi8vZXJyYXRpcXVlLmNoL3NvZnR3YXJlL2Z1dC9kb2MvRnV0Lmh0bWwjVkFMKCYl M0UlM0U9KSkKaHR0cDovL2VycmF0aXF1ZS5jaC9zb2Z0d2FyZS9mdXQvZG9jL0Z1dHUuaHRtbCNW QUxyZWFkCgpbM10KaHR0cDovL2VycmF0aXF1ZS5jaC9zb2Z0d2FyZS9mdXQvZG9jL0Z1dC5odG1s I1ZBTGZpbmFsbHkKVGhpcyBjb3VsZCBhbHNvIGJlIG1vZGlmaWVkIG9yIGFub3RoZXIgdmVyc2lv biBwcm92aWRlZCB0byBwcm9wYWdhdGUgcG9zc2libGUgZXJyb3JzIGluIHRoZSBmaW5hbGx5IGhh bmRsZXIgaW4gdGhlIGNvbmN1cnJlbmN5IG1vbmFkIGl0c2VsZi4KCgpfX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwpNaXJhZ2VPUy1kZXZlbCBtYWlsaW5nIGxp c3QKTWlyYWdlT1MtZGV2ZWxAbGlzdHMueGVucHJvamVjdC5vcmcKaHR0cDovL2xpc3RzLnhlbnBy b2plY3Qub3JnL2NnaS1iaW4vbWFpbG1hbi9saXN0aW5mby9taXJhZ2Vvcy1kZXZlbAo= From mirageos-devel-bounces@lists.xenproject.org Tue Feb 03 17:11:11 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 03 Feb 2015 17:11:11 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YIh0C-0001Ir-WD; Tue, 03 Feb 2015 17:11:04 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YIh0B-0001Il-Ne for mirageos-devel@lists.xenproject.org; Tue, 03 Feb 2015 17:11:03 +0000 Received: from [193.109.254.147] by server-16.bemta-14.messagelabs.com id D3/24-02639-72101D45; Tue, 03 Feb 2015 17:11:03 +0000 X-Env-Sender: daniel.buenzli@erratique.ch X-Msg-Ref: server-12.tower-27.messagelabs.com!1422983461!12590749!1 X-Originating-IP: [74.55.86.74] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNzQuNTUuODYuNzQgPT4gMzA4NTYz\n X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27061 invoked from network); 3 Feb 2015 17:11:01 -0000 Received: from mail6.webfaction.com (HELO smtp.webfaction.com) (74.55.86.74) by server-12.tower-27.messagelabs.com with SMTP; 3 Feb 2015 17:11:01 -0000 Received: from [172.20.10.2] (227-224.197-178.cust.bluewin.ch [178.197.224.227]) by smtp.webfaction.com (Postfix) with ESMTP id 9127E26EA8DF; Tue, 3 Feb 2015 17:11:00 +0000 (UTC) Date: Tue, 3 Feb 2015 18:10:57 +0100 From: =?utf-8?Q?Daniel_B=C3=BCnzli?= To: Christophe Troestler Message-ID: <0235E905E5DE4F3B9422F8A37DC74FEB@erratique.ch> In-Reply-To: <20150203.165548.1818962153128895170.Christophe.Troestler@umons.ac.be> References: <20150202.014549.1883720051237442569.Christophe.Troestler@umons.ac.be> <20150203.165548.1818962153128895170.Christophe.Troestler@umons.ac.be> X-Mailer: sparrow 1.6.4 (build 1178) MIME-Version: 1.0 Content-Disposition: inline Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Error handling in Mirage - request for comments! X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org TGUgbWFyZGksIDMgZsOpdnJpZXIgMjAxNSDDoCAxNjo1NSwgQ2hyaXN0b3BoZSBUcm9lc3RsZXIg YSDDqWNyaXQgOgo+IFBsZWFzZSBsYXkgZG93biBhIGNvbmNyZXRlIGludGVyZmFjZSBzaG93aW5n IG9mIHdoYXQgeW91IG1lYW4uIEkKPiB0aGluayB3ZSBhbGwgYWdyZWUgb24gdGhlIGdvYWwgb2Yg d3JpdGluZyByb2J1c3Qgc29mdHdhcmUsIHdlIG5lZWQgdG8KPiBtb3ZlIHRoZSBkaXNjdXNzaW9u IHRvIGNvbmNyZXRlIHByb3Bvc2Fscy4KClNvcnJ5IGRvbid0IGhhdmUgdGhlIHRpbWUgdG8gd29y ayBvbiB0aGlzOyB0aGVzZSB0aGluZ3MgY29tZSBvdXQgb2Ygd3JpdGluZyBjb2RlLiBCdXQgYXMg YSBzdGFydCBJIGRvbid0IHNlZSB3aGF0J3MgdGhlIHByb2JsZW0gd2l0aCB0aGUgYmFzaWMgcmVz dWx0IG1vbmFkIGV2ZXJ5Ym9keSBrbm93cyAoZS5nLiBzZWUgaGVyZSBbMSwyXSkgYWxvbmcgd2l0 aCBhIGZldyB3aXRoX3Jlc291cmNlIGNvbWJpbmF0b3JzIGJhc2VkIG9uIHNvbWUga2luZCBvZiBg ZmluYWxseWAgWzNdIGFuZCBzdGljayB0byBwb2x5bW9ycGhpYyB2YXJpYW50IGVycm9ycyDigJQg YWxvbmcsIG9mIGNvdXJzZSwgd2l0aCBGb3JtYXQgcHJldHR5IHByaW50ZXJzIGZvciB0aGVzZSBz b21ldGhpbmcgdGhhdCBpcyBvZnRlbiBhbm5veWluZ2x5IGFic2VudCBpbiBBUElzLiBBbmQgSSB3 b3VsZCBjb21wbGV0ZWx5IGZvcmdldCBhYm91dCB1c2luZyBsd3QncyBmYWlsZWQgc3RhdGUgKGku ZS4gb25seSB0byB0cmFwIHVuZXhwZWN0ZWQgZXhjZXB0aW9ucyBhdCB0aGUgaGlnaGVzdCBsZXZl bCkuCgpCZXN0LAogIApEYW5pZWwKClsxXSAgClRoaXMgZGVhbHMgb25seSB3aXRoIHN0cmluZyBl cnJvcnMgc28gaXQgc2hvdWxkIGJlIGdlbmVyYWxpemVkIHRvIFsyXSwgYnV0IGEgZmV3IG9mIHRo ZSBlcnJvciBoYW5kbGluZwpjb21iaW5hdG9ycyBtYXkgYmUgaW50ZXJlc3RpbmcuICAKCmh0dHBz Oi8vZ2l0aHViLmNvbS9zYW1vaHQvYXNzZW1ibGFnZS9ibG9iL21hc3Rlci9saWIvYXNzZW1ibGFn ZS5tbGkjTDcwOC1MNzQ0CgpGb3IgZXhhbXBsZSBgcmV3b3JkX2Vycm9yYCBhIHF1aWNrIGNvbWJp bmF0b3IgdGhhdCBhbGxvd3MgdG8gdHJhbnNmb3JtIGEgbG93ZXItbGV2ZWwgZXJyb3IgdG8gYSBo aWdoZXIgbGV2ZWwgb25lLCBpLmUuIGdpdmUgbW9yZSBjb250ZXh0IGhpZ2hlciB1cCB3aGVuIHlv dSBoYXZlIHRoZSBpbmZvIGFib3V0IHdoYXQgeW91IGFyZSBkb2luZy4gU2luY2Ugd2UgYXJlIHVz aW5nIHN0cmluZ3MgaGVyZSBpdCdzIGFsc28gZWFzeSB0byBzdGFjayB0aGUgZXJyb3JzIGlmIHlv dSB3aXNoIHNvICh+cmVwbGFjZTpmYWxzZSBhcmd1bWVudCkgZnJvbSB0aGUgbG93ZXN0LWxldmVs IG9mIHdoYXQgd2VudCB3cm9uZyAoZS5nLiB0aGUgYWN0dWFsIHV0aWxpdHkgaW52b2NhdGlvbiBl cnJvcikgdG8gd2hhdCB5b3Ugd2VyZSB0cnlpbmcgdG8gZG8gKGUuZy4gZGV0ZXJtaW5lIHRoZSBu dW1iZXIgb2YgcHJvY2Vzc29ycyBpbiB0aGUgc3lzdGVtKSB3aGljaCBtYWtlcyBlcnJvciBkaWFn bm9zaXMgbXVjaCBlYXNpZXIgKGNvbnRleHQgKyBubyBlcnJvciBpbmZvIGlzIGxvc3QpLiBOb3Qg dGhhdCBpdCB3b3VsZG4ndCBiZSBpbXBvc3NpYmxlIHdpdGggbGlzdHMgb2YgcG9seXZhcnMsIGJ1 dCBvbmUgaGFzIHRvIHNlZSBob3cgaXQgY29tZXMgb3V0IGluIHByYWN0aWNlLiBBIGZldyBleGFt cGxlczoKCmh0dHBzOi8vZ2l0aHViLmNvbS9zYW1vaHQvYXNzZW1ibGFnZS9ibG9iL21hc3Rlci9s aWIvYXNfY29uZi5tbCNMNDIwLUw0MjgKaHR0cHM6Ly9naXRodWIuY29tL3NhbW9odC9hc3NlbWJs YWdlL2Jsb2IvbWFzdGVyL2xpYi9hc19jb25mLm1sI0w1NDMtTDU0OAoKWzJdClRoaXMgaXMgdGhl IGNsYXNzaWNhbCBnZW5lcmFsaXplZCByZXN1bHQgdHlwZSBmb3IgZGVhbGluZyB3aXRoIGVycm9y cy4gIApodHRwOi8vZXJyYXRpcXVlLmNoL3NvZnR3YXJlL2Z1dC9kb2MvRnV0Lmh0bWwjVFlQRXJl c3VsdApodHRwOi8vZXJyYXRpcXVlLmNoL3NvZnR3YXJlL2Z1dC9kb2MvRnV0Lmh0bWwjVkFMKCY+ Pj0pIChodHRwOi8vZXJyYXRpcXVlLmNoL3NvZnR3YXJlL2Z1dC9kb2MvRnV0Lmh0bWwjVkFMKCYl M0UlM0U9KSkKaHR0cDovL2VycmF0aXF1ZS5jaC9zb2Z0d2FyZS9mdXQvZG9jL0Z1dHUuaHRtbCNW QUxyZWFkCgpbM10KaHR0cDovL2VycmF0aXF1ZS5jaC9zb2Z0d2FyZS9mdXQvZG9jL0Z1dC5odG1s I1ZBTGZpbmFsbHkKVGhpcyBjb3VsZCBhbHNvIGJlIG1vZGlmaWVkIG9yIGFub3RoZXIgdmVyc2lv biBwcm92aWRlZCB0byBwcm9wYWdhdGUgcG9zc2libGUgZXJyb3JzIGluIHRoZSBmaW5hbGx5IGhh bmRsZXIgaW4gdGhlIGNvbmN1cnJlbmN5IG1vbmFkIGl0c2VsZi4KCgpfX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwpNaXJhZ2VPUy1kZXZlbCBtYWlsaW5nIGxp c3QKTWlyYWdlT1MtZGV2ZWxAbGlzdHMueGVucHJvamVjdC5vcmcKaHR0cDovL2xpc3RzLnhlbnBy b2plY3Qub3JnL2NnaS1iaW4vbWFpbG1hbi9saXN0aW5mby9taXJhZ2Vvcy1kZXZlbAo= From mirageos-devel-bounces@lists.xenproject.org Tue Feb 03 17:26:47 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 03 Feb 2015 17:26:47 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YIhFL-0002yu-MK; Tue, 03 Feb 2015 17:26:43 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YIhFJ-0002yc-UR for mirageos-devel@lists.xenproject.org; Tue, 03 Feb 2015 17:26:42 +0000 Received: from [85.158.139.211] by server-11.bemta-5.messagelabs.com id D5/1B-02757-1D401D45; Tue, 03 Feb 2015 17:26:41 +0000 X-Env-Sender: sebastien.mondet@gmail.com X-Msg-Ref: server-16.tower-206.messagelabs.com!1422984399!8063431!1 X-Originating-IP: [74.125.82.170] X-SpamReason: No, hits=0.9 required=7.0 tests=BODY_RANDOM_LONG, HTML_30_40,HTML_MESSAGE,RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23779 invoked from network); 3 Feb 2015 17:26:39 -0000 Received: from mail-we0-f170.google.com (HELO mail-we0-f170.google.com) (74.125.82.170) by server-16.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 3 Feb 2015 17:26:39 -0000 Received: by mail-we0-f170.google.com with SMTP id w55so40860911wes.1 for ; Tue, 03 Feb 2015 09:26:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=9R9GhyCpGp6168Ow9lFDiK6z4FkCZVyHtvQSi+wS824=; b=Ky2ZHRzPHgqO8QZYGrMSXFfZjPE2GXsH/yf+W2U5bWzYa45lyHnYEBmgyahvligLnh NuFPsuGSJPvHzxJCgOWf6yx6dEjfxHyp4SVN61tTwmbwuHFr0SJtdAjHGqRO/OiEXaVl cxE0PsIAMVeGqrEnIHwSr5J1+7UajzCPdSXPOiy3Py7dbnhqPtxmFk8mO5+pnK9PkXWc 7xLZlpslaIlCNoFcI/gghajjP5Wr3SCBckI2hjs5Xtkfr4rjtMTufMNOYqtz1ek+4aex 6mgBxvlko1ajIXMOiYl0Z3N2YYnT3lNUZ9TLD1+BWZZ/dwaWlfe86B0ZMjtq760Ys3EF GcIw== X-Received: by 10.194.48.74 with SMTP id j10mr57223367wjn.38.1422984398938; Tue, 03 Feb 2015 09:26:38 -0800 (PST) MIME-Version: 1.0 Received: by 10.216.55.198 with HTTP; Tue, 3 Feb 2015 09:26:18 -0800 (PST) In-Reply-To: <0235E905E5DE4F3B9422F8A37DC74FEB@erratique.ch> References: <20150202.014549.1883720051237442569.Christophe.Troestler@umons.ac.be> <20150203.165548.1818962153128895170.Christophe.Troestler@umons.ac.be> <0235E905E5DE4F3B9422F8A37DC74FEB@erratique.ch> From: Sebastien Mondet Date: Tue, 3 Feb 2015 12:26:18 -0500 Message-ID: To: =?UTF-8?Q?Daniel_B=C3=BCnzli?= Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Error handling in Mirage - request for comments! X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============4263018076699919635==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============4263018076699919635== Content-Type: multipart/alternative; boundary=047d7ba975c89ea824050e325f81 --047d7ba975c89ea824050e325f81 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Yes if we just all agree on this type: http://erratique.ch/software/fut/doc/Fut.html#TYPEresult then we are all compatible without actual library dependencies, thanks to structural typing I've been abusing this for the past few years, it's great: http://seb.mondet.org/software/pvem/index.html http://seb.mondet.org/software/pvem_lwt_unix/index.html http://seb.mondet.org/talks/compose2015/#/25 http://seb.mondet.org/talks/compose2015/#/26 On Tue, Feb 3, 2015 at 12:10 PM, Daniel B=C3=BCnzli wrote: > Le mardi, 3 f=C3=A9vrier 2015 =C3=A0 16:55, Christophe Troestler a =C3=A9= crit : > > Please lay down a concrete interface showing of what you mean. I > > think we all agree on the goal of writing robust software, we need to > > move the discussion to concrete proposals. > > Sorry don't have the time to work on this; these things come out of > writing code. But as a start I don't see what's the problem with the basi= c > result monad everybody knows (e.g. see here [1,2]) along with a few > with_resource combinators based on some kind of `finally` [3] and stick t= o > polymorphic variant errors =E2=80=94 along, of course, with Format pretty= printers > for these something that is often annoyingly absent in APIs. And I would > completely forget about using lwt's failed state (i.e. only to trap > unexpected exceptions at the highest level). > > Best, > > Daniel > > [1] > This deals only with string errors so it should be generalized to [2], bu= t > a few of the error handling > combinators may be interesting. > > > https://github.com/samoht/assemblage/blob/master/lib/assemblage.mli#L708-= L744 > > For example `reword_error` a quick combinator that allows to transform a > lower-level error to a higher level one, i.e. give more context higher up > when you have the info about what you are doing. Since we are using strin= gs > here it's also easy to stack the errors if you wish so (~replace:false > argument) from the lowest-level of what went wrong (e.g. the actual utili= ty > invocation error) to what you were trying to do (e.g. determine the numbe= r > of processors in the system) which makes error diagnosis much easier > (context + no error info is lost). Not that it wouldn't be impossible wit= h > lists of polyvars, but one has to see how it comes out in practice. A few > examples: > > https://github.com/samoht/assemblage/blob/master/lib/as_conf.ml#L420-L428 > https://github.com/samoht/assemblage/blob/master/lib/as_conf.ml#L543-L548 > > [2] > This is the classical generalized result type for dealing with errors. > http://erratique.ch/software/fut/doc/Fut.html#TYPEresult > http://erratique.ch/software/fut/doc/Fut.html#VAL(&>>=3D) ( > http://erratique.ch/software/fut/doc/Fut.html#VAL(&%3E%3E=3D)) > http://erratique.ch/software/fut/doc/Futu.html#VALread > > [3] > http://erratique.ch/software/fut/doc/Fut.html#VALfinally > This could also be modified or another version provided to propagate > possible errors in the finally handler in the concurrency monad itself. > > > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > --047d7ba975c89ea824050e325f81 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
I've been abusing this for t= he past few years, it's great:
http://seb.mondet.org/software/pvem= /index.html
http://seb.mondet.org/software/pvem_lwt_unix/= index.html
http://seb.mondet.org/talks/compose2015/#/25
http:= //seb.mondet.org/talks/compose2015/#/26






On Tue, Feb 3, 2015 at 12= :10 PM, Daniel B=C3=BCnzli <daniel.buenzli@erratique.ch><= /span> wrote:
Le mardi, 3 f=C3=A9vrier 20= 15 =C3=A0 16:55, Christophe Troestler a =C3=A9crit :
> Please lay down a concrete interface showing of what you mean. I=
> think we all agree on the goal of writing robust software, we need to<= br> > move the discussion to concrete proposals.

Sorry don't have the time to work on this; these things come out= of writing code. But as a start I don't see what's the problem wit= h the basic result monad everybody knows (e.g. see here [1,2]) along with a= few with_resource combinators based on some kind of `finally` [3] and stic= k to polymorphic variant errors =E2=80=94 along, of course, with Format pre= tty printers for these something that is often annoyingly absent in APIs. A= nd I would completely forget about using lwt's failed state (i.e. only = to trap unexpected exceptions at the highest level).

Best,

Daniel

[1]
This deals only with string errors so it should be generalized to [2], but = a few of the error handling
combinators may be interesting.

https://github.com/samoht/assemblage/blob/= master/lib/assemblage.mli#L708-L744

For example `reword_error` a quick combinator that allows to transform a lo= wer-level error to a higher level one, i.e. give more context higher up whe= n you have the info about what you are doing. Since we are using strings he= re it's also easy to stack the errors if you wish so (~replace:false ar= gument) from the lowest-level of what went wrong (e.g. the actual utility i= nvocation error) to what you were trying to do (e.g. determine the number o= f processors in the system) which makes error diagnosis much easier (contex= t + no error info is lost). Not that it wouldn't be impossible with lis= ts of polyvars, but one has to see how it comes out in practice. A few exam= ples:

https://github.com/samoht/assemblage/blob/mast= er/lib/as_conf.ml#L420-L428
https://github.com/samoht/assemblage/blob/mast= er/lib/as_conf.ml#L543-L548

[2]
This is the classical generalized result type for dealing with errors.
http://erratique.ch/software/fut/doc/Fut.html#TYPEresult http://erratique.ch/software/fut/doc/Fut.html#VAL(&>= >=3D) (http://erratique.ch/software/fut/doc/Fut.htm= l#VAL(&%3E%3E=3D))
http://erratique.ch/software/fut/doc/Futu.html#VALread

[3]
http://erratique.ch/software/fut/doc/Fut.html#VALfinally This could also be modified or another version provided to propagate possib= le errors in the finally handler in the concurrency monad itself.


_______________________________________________
MirageOS-devel mailing list
Mi= rageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo= /mirageos-devel

--047d7ba975c89ea824050e325f81-- --===============4263018076699919635== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --===============4263018076699919635==-- From mirageos-devel-bounces@lists.xenproject.org Tue Feb 03 17:26:47 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 03 Feb 2015 17:26:47 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YIhFL-0002yu-MK; Tue, 03 Feb 2015 17:26:43 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YIhFJ-0002yc-UR for mirageos-devel@lists.xenproject.org; Tue, 03 Feb 2015 17:26:42 +0000 Received: from [85.158.139.211] by server-11.bemta-5.messagelabs.com id D5/1B-02757-1D401D45; Tue, 03 Feb 2015 17:26:41 +0000 X-Env-Sender: sebastien.mondet@gmail.com X-Msg-Ref: server-16.tower-206.messagelabs.com!1422984399!8063431!1 X-Originating-IP: [74.125.82.170] X-SpamReason: No, hits=0.9 required=7.0 tests=BODY_RANDOM_LONG, HTML_30_40,HTML_MESSAGE,RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23779 invoked from network); 3 Feb 2015 17:26:39 -0000 Received: from mail-we0-f170.google.com (HELO mail-we0-f170.google.com) (74.125.82.170) by server-16.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 3 Feb 2015 17:26:39 -0000 Received: by mail-we0-f170.google.com with SMTP id w55so40860911wes.1 for ; Tue, 03 Feb 2015 09:26:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=9R9GhyCpGp6168Ow9lFDiK6z4FkCZVyHtvQSi+wS824=; b=Ky2ZHRzPHgqO8QZYGrMSXFfZjPE2GXsH/yf+W2U5bWzYa45lyHnYEBmgyahvligLnh NuFPsuGSJPvHzxJCgOWf6yx6dEjfxHyp4SVN61tTwmbwuHFr0SJtdAjHGqRO/OiEXaVl cxE0PsIAMVeGqrEnIHwSr5J1+7UajzCPdSXPOiy3Py7dbnhqPtxmFk8mO5+pnK9PkXWc 7xLZlpslaIlCNoFcI/gghajjP5Wr3SCBckI2hjs5Xtkfr4rjtMTufMNOYqtz1ek+4aex 6mgBxvlko1ajIXMOiYl0Z3N2YYnT3lNUZ9TLD1+BWZZ/dwaWlfe86B0ZMjtq760Ys3EF GcIw== X-Received: by 10.194.48.74 with SMTP id j10mr57223367wjn.38.1422984398938; Tue, 03 Feb 2015 09:26:38 -0800 (PST) MIME-Version: 1.0 Received: by 10.216.55.198 with HTTP; Tue, 3 Feb 2015 09:26:18 -0800 (PST) In-Reply-To: <0235E905E5DE4F3B9422F8A37DC74FEB@erratique.ch> References: <20150202.014549.1883720051237442569.Christophe.Troestler@umons.ac.be> <20150203.165548.1818962153128895170.Christophe.Troestler@umons.ac.be> <0235E905E5DE4F3B9422F8A37DC74FEB@erratique.ch> From: Sebastien Mondet Date: Tue, 3 Feb 2015 12:26:18 -0500 Message-ID: To: =?UTF-8?Q?Daniel_B=C3=BCnzli?= Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Error handling in Mirage - request for comments! X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============4263018076699919635==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============4263018076699919635== Content-Type: multipart/alternative; boundary=047d7ba975c89ea824050e325f81 --047d7ba975c89ea824050e325f81 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Yes if we just all agree on this type: http://erratique.ch/software/fut/doc/Fut.html#TYPEresult then we are all compatible without actual library dependencies, thanks to structural typing I've been abusing this for the past few years, it's great: http://seb.mondet.org/software/pvem/index.html http://seb.mondet.org/software/pvem_lwt_unix/index.html http://seb.mondet.org/talks/compose2015/#/25 http://seb.mondet.org/talks/compose2015/#/26 On Tue, Feb 3, 2015 at 12:10 PM, Daniel B=C3=BCnzli wrote: > Le mardi, 3 f=C3=A9vrier 2015 =C3=A0 16:55, Christophe Troestler a =C3=A9= crit : > > Please lay down a concrete interface showing of what you mean. I > > think we all agree on the goal of writing robust software, we need to > > move the discussion to concrete proposals. > > Sorry don't have the time to work on this; these things come out of > writing code. But as a start I don't see what's the problem with the basi= c > result monad everybody knows (e.g. see here [1,2]) along with a few > with_resource combinators based on some kind of `finally` [3] and stick t= o > polymorphic variant errors =E2=80=94 along, of course, with Format pretty= printers > for these something that is often annoyingly absent in APIs. And I would > completely forget about using lwt's failed state (i.e. only to trap > unexpected exceptions at the highest level). > > Best, > > Daniel > > [1] > This deals only with string errors so it should be generalized to [2], bu= t > a few of the error handling > combinators may be interesting. > > > https://github.com/samoht/assemblage/blob/master/lib/assemblage.mli#L708-= L744 > > For example `reword_error` a quick combinator that allows to transform a > lower-level error to a higher level one, i.e. give more context higher up > when you have the info about what you are doing. Since we are using strin= gs > here it's also easy to stack the errors if you wish so (~replace:false > argument) from the lowest-level of what went wrong (e.g. the actual utili= ty > invocation error) to what you were trying to do (e.g. determine the numbe= r > of processors in the system) which makes error diagnosis much easier > (context + no error info is lost). Not that it wouldn't be impossible wit= h > lists of polyvars, but one has to see how it comes out in practice. A few > examples: > > https://github.com/samoht/assemblage/blob/master/lib/as_conf.ml#L420-L428 > https://github.com/samoht/assemblage/blob/master/lib/as_conf.ml#L543-L548 > > [2] > This is the classical generalized result type for dealing with errors. > http://erratique.ch/software/fut/doc/Fut.html#TYPEresult > http://erratique.ch/software/fut/doc/Fut.html#VAL(&>>=3D) ( > http://erratique.ch/software/fut/doc/Fut.html#VAL(&%3E%3E=3D)) > http://erratique.ch/software/fut/doc/Futu.html#VALread > > [3] > http://erratique.ch/software/fut/doc/Fut.html#VALfinally > This could also be modified or another version provided to propagate > possible errors in the finally handler in the concurrency monad itself. > > > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > --047d7ba975c89ea824050e325f81 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
I've been abusing this for t= he past few years, it's great:
http://seb.mondet.org/software/pvem= /index.html
http://seb.mondet.org/software/pvem_lwt_unix/= index.html
http://seb.mondet.org/talks/compose2015/#/25
http:= //seb.mondet.org/talks/compose2015/#/26






On Tue, Feb 3, 2015 at 12= :10 PM, Daniel B=C3=BCnzli <daniel.buenzli@erratique.ch><= /span> wrote:
Le mardi, 3 f=C3=A9vrier 20= 15 =C3=A0 16:55, Christophe Troestler a =C3=A9crit :
> Please lay down a concrete interface showing of what you mean. I=
> think we all agree on the goal of writing robust software, we need to<= br> > move the discussion to concrete proposals.

Sorry don't have the time to work on this; these things come out= of writing code. But as a start I don't see what's the problem wit= h the basic result monad everybody knows (e.g. see here [1,2]) along with a= few with_resource combinators based on some kind of `finally` [3] and stic= k to polymorphic variant errors =E2=80=94 along, of course, with Format pre= tty printers for these something that is often annoyingly absent in APIs. A= nd I would completely forget about using lwt's failed state (i.e. only = to trap unexpected exceptions at the highest level).

Best,

Daniel

[1]
This deals only with string errors so it should be generalized to [2], but = a few of the error handling
combinators may be interesting.

https://github.com/samoht/assemblage/blob/= master/lib/assemblage.mli#L708-L744

For example `reword_error` a quick combinator that allows to transform a lo= wer-level error to a higher level one, i.e. give more context higher up whe= n you have the info about what you are doing. Since we are using strings he= re it's also easy to stack the errors if you wish so (~replace:false ar= gument) from the lowest-level of what went wrong (e.g. the actual utility i= nvocation error) to what you were trying to do (e.g. determine the number o= f processors in the system) which makes error diagnosis much easier (contex= t + no error info is lost). Not that it wouldn't be impossible with lis= ts of polyvars, but one has to see how it comes out in practice. A few exam= ples:

https://github.com/samoht/assemblage/blob/mast= er/lib/as_conf.ml#L420-L428
https://github.com/samoht/assemblage/blob/mast= er/lib/as_conf.ml#L543-L548

[2]
This is the classical generalized result type for dealing with errors.
http://erratique.ch/software/fut/doc/Fut.html#TYPEresult http://erratique.ch/software/fut/doc/Fut.html#VAL(&>= >=3D) (http://erratique.ch/software/fut/doc/Fut.htm= l#VAL(&%3E%3E=3D))
http://erratique.ch/software/fut/doc/Futu.html#VALread

[3]
http://erratique.ch/software/fut/doc/Fut.html#VALfinally This could also be modified or another version provided to propagate possib= le errors in the finally handler in the concurrency monad itself.


_______________________________________________
MirageOS-devel mailing list
Mi= rageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo= /mirageos-devel

--047d7ba975c89ea824050e325f81-- --===============4263018076699919635== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --===============4263018076699919635==-- From mirageos-devel-bounces@lists.xenproject.org Tue Feb 03 18:31:30 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 03 Feb 2015 18:31:30 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YIiFw-0008Nz-7P; Tue, 03 Feb 2015 18:31:24 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YIiFt-0008Nb-UX for mirageos-devel@lists.xenproject.org; Tue, 03 Feb 2015 18:31:22 +0000 Received: from [85.158.137.68] by server-15.bemta-3.messagelabs.com id 79/04-02884-9F311D45; Tue, 03 Feb 2015 18:31:21 +0000 X-Env-Sender: agarwal1975@gmail.com X-Msg-Ref: server-3.tower-31.messagelabs.com!1422988278!11813899!1 X-Originating-IP: [74.125.82.52] X-SpamReason: No, hits=0.9 required=7.0 tests=BODY_RANDOM_LONG, HTML_30_40,HTML_MESSAGE,RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.12.5; banners=-,-,- X-VirusChecked: Checked Received: (qmail 13562 invoked from network); 3 Feb 2015 18:31:18 -0000 Received: from mail-wg0-f52.google.com (HELO mail-wg0-f52.google.com) (74.125.82.52) by server-3.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 3 Feb 2015 18:31:18 -0000 Received: by mail-wg0-f52.google.com with SMTP id y19so46157275wgg.11 for ; Tue, 03 Feb 2015 10:31:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=1mFW71VrvcIYKU7Y7F+5/hzi4C4Bi7Q+xWwJSD9FPIc=; b=h4M/2UktkXShnvl0wfwr4b0HvVOrGWt8NmG+C3bI3/ai9GJ9VFSst5lRofaotxrbrm G1xrUYC59ELta8jyUa5CfnhxqitfmWezoAv0LPKNDZnaPrIfmvdjHeDlbTipHvO/bH+p 0de9f6y2BRbxRldCK/vSSBvIdgJoE4TdwDT7rwYuZbO3RRBrZRoKgw+JCblxVTS+ha5e PKaurA6BfoT7UbMvo5sR48obvqiZoeZcFMpUwqvMSXpkpbhQPVAlsgsfcMQZEiDYcyjO fJq6uD7qD1GY/zxyDWXMfGilSrc9dMadstBeNkMWCdz3sYotlOSWoNkhL2IW0FEdOEJS SffQ== X-Received: by 10.194.172.35 with SMTP id az3mr58146813wjc.43.1422988278119; Tue, 03 Feb 2015 10:31:18 -0800 (PST) MIME-Version: 1.0 Received: by 10.27.15.4 with HTTP; Tue, 3 Feb 2015 10:30:57 -0800 (PST) In-Reply-To: References: <20150202.014549.1883720051237442569.Christophe.Troestler@umons.ac.be> <20150203.165548.1818962153128895170.Christophe.Troestler@umons.ac.be> <0235E905E5DE4F3B9422F8A37DC74FEB@erratique.ch> From: Ashish Agarwal Date: Tue, 3 Feb 2015 13:30:57 -0500 Message-ID: To: Sebastien Mondet Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Error handling in Mirage - request for comments! X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1110728963459783293==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============1110728963459783293== Content-Type: multipart/alternative; boundary=089e0122e8b6d642c8050e334640 --089e0122e8b6d642c8050e334640 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable > System 3 provides (I think) no easy way to match on the type of error. You can. An Error.t is constructed by using Sexplib. Thus, you can deserialize them to whatever specific error you want to consider. Here's an example: open Core.Std;; type myerr =3D [`Zero | `Neg of int] with sexp;; (* Get back to myerr if possible. *) let myerr_of_error (e:Error.t) : myerr option =3D match Error.sexp_of_t e with | Sexp.List (_::x::[]) -> Some (myerr_of_sexp x) | _ -> None ;; let f x : int Or_error.t =3D if x =3D 0 then error "zero not allowed" `Zero sexp_of_error else if x < 0 then error "negative not allowed" (`Neg x) sexp_of_error else Ok x ;; let g x =3D match f x with | Ok x -> x*x | Error e -> match myerr_of_error e with | Some `Zero -> 0 | Some (`Neg x) -> x*x | None -> 0 (* or parse e as another error type *) ;; In the last None clause above, you could try to parse e as another error type, continuing to consider as many error types as you want. The nice thing about this is you only have one error type, Error.t, so your APIs remain uncluttered. But you can deserialize to more strongly typed error types when you want to. The bad thing is the compiler can't tell you what are all the errors you have to consider, but this isn't achieved my most error handling strategies. Furthermore, this is all about errors, so I'm not sure exhaustiveness is so important. > Sometimes it's useful to organise errors into a hierarchy ... I don't see any way to do this in OCaml. You can get this with polymorphic variants, e.g type tcp_connection_refused =3D [`TCP_connection_refused] type tcp_error =3D [tcp_connection_refused | `Another_err] On Tue, Feb 3, 2015 at 12:26 PM, Sebastien Mondet < sebastien.mondet@gmail.com> wrote: > > Yes if we just all agree on this type: > http://erratique.ch/software/fut/doc/Fut.html#TYPEresult > then we are all compatible without actual library dependencies, thanks to > structural typing > > I've been abusing this for the past few years, it's great: > http://seb.mondet.org/software/pvem/index.html > http://seb.mondet.org/software/pvem_lwt_unix/index.html > http://seb.mondet.org/talks/compose2015/#/25 > http://seb.mondet.org/talks/compose2015/#/26 > > > > > > > > On Tue, Feb 3, 2015 at 12:10 PM, Daniel B=C3=BCnzli < > daniel.buenzli@erratique.ch> wrote: > >> Le mardi, 3 f=C3=A9vrier 2015 =C3=A0 16:55, Christophe Troestler a =C3= =A9crit : >> > Please lay down a concrete interface showing of what you mean. I >> > think we all agree on the goal of writing robust software, we need to >> > move the discussion to concrete proposals. >> >> Sorry don't have the time to work on this; these things come out of >> writing code. But as a start I don't see what's the problem with the bas= ic >> result monad everybody knows (e.g. see here [1,2]) along with a few >> with_resource combinators based on some kind of `finally` [3] and stick = to >> polymorphic variant errors =E2=80=94 along, of course, with Format prett= y printers >> for these something that is often annoyingly absent in APIs. And I would >> completely forget about using lwt's failed state (i.e. only to trap >> unexpected exceptions at the highest level). >> >> Best, >> >> Daniel >> >> [1] >> This deals only with string errors so it should be generalized to [2], >> but a few of the error handling >> combinators may be interesting. >> >> >> https://github.com/samoht/assemblage/blob/master/lib/assemblage.mli#L708= -L744 >> >> For example `reword_error` a quick combinator that allows to transform a >> lower-level error to a higher level one, i.e. give more context higher u= p >> when you have the info about what you are doing. Since we are using stri= ngs >> here it's also easy to stack the errors if you wish so (~replace:false >> argument) from the lowest-level of what went wrong (e.g. the actual util= ity >> invocation error) to what you were trying to do (e.g. determine the numb= er >> of processors in the system) which makes error diagnosis much easier >> (context + no error info is lost). Not that it wouldn't be impossible wi= th >> lists of polyvars, but one has to see how it comes out in practice. A fe= w >> examples: >> >> https://github.com/samoht/assemblage/blob/master/lib/as_conf.ml#L420-L42= 8 >> https://github.com/samoht/assemblage/blob/master/lib/as_conf.ml#L543-L54= 8 >> >> [2] >> This is the classical generalized result type for dealing with errors. >> http://erratique.ch/software/fut/doc/Fut.html#TYPEresult >> http://erratique.ch/software/fut/doc/Fut.html#VAL(&>>=3D) ( >> http://erratique.ch/software/fut/doc/Fut.html#VAL(&%3E%3E=3D)) >> http://erratique.ch/software/fut/doc/Futu.html#VALread >> >> [3] >> http://erratique.ch/software/fut/doc/Fut.html#VALfinally >> This could also be modified or another version provided to propagate >> possible errors in the finally handler in the concurrency monad itself. >> >> >> _______________________________________________ >> MirageOS-devel mailing list >> MirageOS-devel@lists.xenproject.org >> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel >> > > > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > > --089e0122e8b6d642c8050e334640 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
> System 3 provides (I think) no easy way to match on t= he type of error.

You can. An Error.t is constructed by = using Sexplib. Thus, you can deserialize them to whatever specific error yo= u want to consider. Here's an example:

op= en Core.Std;;

type myerr =3D [`Zero | `Neg of int]= with sexp;;

(* Get back to myerr if possible. *)<= /div>
let myerr_of_error (e:Error.t) : myerr option =3D
=C2= =A0 match Error.sexp_of_t e with
=C2=A0 | Sexp.List (_::x::[]) -&= gt; Some (myerr_of_sexp x)
=C2=A0 | _ -> None
;;

let f x : int Or_error.t =3D
=C2=A0 if = x =3D 0 then error "zero not allowed" `Zero sexp_of_error=C2=A0
=C2=A0 else if x < 0 then error "negative not allowed"= ; (`Neg x) sexp_of_error
=C2=A0 else Ok x
;;
=
let g x =3D match f x with
| Ok x -> x*x
<= div>| Error e -> match myerr_of_error e with
=C2=A0 | Some `Ze= ro -> 0
=C2=A0 | Some (`Neg x) -> x*x
=C2=A0 | No= ne -> 0 (* or parse e as another error type *)
;;
<= div>
In the last None clause above, you could try to parse e = as another error type, continuing to consider as many error types as you wa= nt. The nice thing about this is you only have one error type, Error.t, so = your APIs remain uncluttered. But you can deserialize to more strongly type= d error types when you want to.

The bad thing is t= he compiler can't tell you what are all the errors you have to consider= , but this isn't achieved my most error handling strategies. Furthermor= e, this is all about errors, so I'm not sure exhaustiveness is so impor= tant.


> Sometimes it's useful to organise er= rors into a hierarchy ... I don't see any way to do this in OCaml.
=
You can get this with polymorphic variants, e.g
type tcp_connection_refused =3D [`TCP_connection_refused]
type tcp_error =3D [tcp_connection_refused | `Another_err]
=


On Tue, Feb 3, 2015 at 12:26 P= M, Sebastien Mondet <sebastien.mondet@gmail.com> wr= ote:

=
Yes if we just all agree on this type: http://erratique.c= h/software/fut/doc/Fut.html#TYPEresult
then we are all compati= ble without actual library dependencies, thanks to structural typing
I've been abusing this for the past few years, it's great:http://seb.mondet.org/software/pvem/index.html
http:/= /seb.mondet.org/software/pvem_lwt_unix/index.html
http://seb.mondet.= org/talks/compose2015/#/25
http://seb.mondet.org/talks/compose2015/#= /26







On Tue, Feb 3, 2015 at 12:10 PM, Danie= l B=C3=BCnzli <daniel.buenzli@erratique.ch> wrote:=
Le mardi, 3 f=C3=A9vrier 2015 =C3=A0 16:= 55, Christophe Troestler a =C3=A9crit :
> Please lay down a concrete interface showing of what you mean. I=
> think we all agree on the goal of writing robust software, we need to<= br> > move the discussion to concrete proposals.

Sorry don't have the time to work on this; these things come out= of writing code. But as a start I don't see what's the problem wit= h the basic result monad everybody knows (e.g. see here [1,2]) along with a= few with_resource combinators based on some kind of `finally` [3] and stic= k to polymorphic variant errors =E2=80=94 along, of course, with Format pre= tty printers for these something that is often annoyingly absent in APIs. A= nd I would completely forget about using lwt's failed state (i.e. only = to trap unexpected exceptions at the highest level).

Best,

Daniel

[1]
This deals only with string errors so it should be generalized to [2], but = a few of the error handling
combinators may be interesting.

https://github.com/samoht/assemblage/blob/= master/lib/assemblage.mli#L708-L744

For example `reword_error` a quick combinator that allows to transform a lo= wer-level error to a higher level one, i.e. give more context higher up whe= n you have the info about what you are doing. Since we are using strings he= re it's also easy to stack the errors if you wish so (~replace:false ar= gument) from the lowest-level of what went wrong (e.g. the actual utility i= nvocation error) to what you were trying to do (e.g. determine the number o= f processors in the system) which makes error diagnosis much easier (contex= t + no error info is lost). Not that it wouldn't be impossible with lis= ts of polyvars, but one has to see how it comes out in practice. A few exam= ples:

https://github.com/samoht/assemblage/blob/mast= er/lib/as_conf.ml#L420-L428
https://github.com/samoht/assemblage/blob/mast= er/lib/as_conf.ml#L543-L548

[2]
This is the classical generalized result type for dealing with errors.
http://erratique.ch/software/fut/doc/Fut.html#TYPEresult http://erratique.ch/software/fut/doc/Fut.html#VAL(&>= >=3D) (http://erratique.ch/software/fut/doc/Fut.htm= l#VAL(&%3E%3E=3D))
http://erratique.ch/software/fut/doc/Futu.html#VALread

[3]
http://erratique.ch/software/fut/doc/Fut.html#VALfinally This could also be modified or another version provided to propagate possib= le errors in the finally handler in the concurrency monad itself.


_______________________________________________
MirageOS-devel mailing list
Mi= rageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo= /mirageos-devel


_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists= .xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo= /mirageos-devel


--089e0122e8b6d642c8050e334640-- --===============1110728963459783293== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --===============1110728963459783293==-- From mirageos-devel-bounces@lists.xenproject.org Tue Feb 03 18:31:30 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 03 Feb 2015 18:31:30 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YIiFw-0008Nz-7P; Tue, 03 Feb 2015 18:31:24 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YIiFt-0008Nb-UX for mirageos-devel@lists.xenproject.org; Tue, 03 Feb 2015 18:31:22 +0000 Received: from [85.158.137.68] by server-15.bemta-3.messagelabs.com id 79/04-02884-9F311D45; Tue, 03 Feb 2015 18:31:21 +0000 X-Env-Sender: agarwal1975@gmail.com X-Msg-Ref: server-3.tower-31.messagelabs.com!1422988278!11813899!1 X-Originating-IP: [74.125.82.52] X-SpamReason: No, hits=0.9 required=7.0 tests=BODY_RANDOM_LONG, HTML_30_40,HTML_MESSAGE,RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.12.5; banners=-,-,- X-VirusChecked: Checked Received: (qmail 13562 invoked from network); 3 Feb 2015 18:31:18 -0000 Received: from mail-wg0-f52.google.com (HELO mail-wg0-f52.google.com) (74.125.82.52) by server-3.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 3 Feb 2015 18:31:18 -0000 Received: by mail-wg0-f52.google.com with SMTP id y19so46157275wgg.11 for ; Tue, 03 Feb 2015 10:31:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=1mFW71VrvcIYKU7Y7F+5/hzi4C4Bi7Q+xWwJSD9FPIc=; b=h4M/2UktkXShnvl0wfwr4b0HvVOrGWt8NmG+C3bI3/ai9GJ9VFSst5lRofaotxrbrm G1xrUYC59ELta8jyUa5CfnhxqitfmWezoAv0LPKNDZnaPrIfmvdjHeDlbTipHvO/bH+p 0de9f6y2BRbxRldCK/vSSBvIdgJoE4TdwDT7rwYuZbO3RRBrZRoKgw+JCblxVTS+ha5e PKaurA6BfoT7UbMvo5sR48obvqiZoeZcFMpUwqvMSXpkpbhQPVAlsgsfcMQZEiDYcyjO fJq6uD7qD1GY/zxyDWXMfGilSrc9dMadstBeNkMWCdz3sYotlOSWoNkhL2IW0FEdOEJS SffQ== X-Received: by 10.194.172.35 with SMTP id az3mr58146813wjc.43.1422988278119; Tue, 03 Feb 2015 10:31:18 -0800 (PST) MIME-Version: 1.0 Received: by 10.27.15.4 with HTTP; Tue, 3 Feb 2015 10:30:57 -0800 (PST) In-Reply-To: References: <20150202.014549.1883720051237442569.Christophe.Troestler@umons.ac.be> <20150203.165548.1818962153128895170.Christophe.Troestler@umons.ac.be> <0235E905E5DE4F3B9422F8A37DC74FEB@erratique.ch> From: Ashish Agarwal Date: Tue, 3 Feb 2015 13:30:57 -0500 Message-ID: To: Sebastien Mondet Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Error handling in Mirage - request for comments! X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1110728963459783293==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============1110728963459783293== Content-Type: multipart/alternative; boundary=089e0122e8b6d642c8050e334640 --089e0122e8b6d642c8050e334640 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable > System 3 provides (I think) no easy way to match on the type of error. You can. An Error.t is constructed by using Sexplib. Thus, you can deserialize them to whatever specific error you want to consider. Here's an example: open Core.Std;; type myerr =3D [`Zero | `Neg of int] with sexp;; (* Get back to myerr if possible. *) let myerr_of_error (e:Error.t) : myerr option =3D match Error.sexp_of_t e with | Sexp.List (_::x::[]) -> Some (myerr_of_sexp x) | _ -> None ;; let f x : int Or_error.t =3D if x =3D 0 then error "zero not allowed" `Zero sexp_of_error else if x < 0 then error "negative not allowed" (`Neg x) sexp_of_error else Ok x ;; let g x =3D match f x with | Ok x -> x*x | Error e -> match myerr_of_error e with | Some `Zero -> 0 | Some (`Neg x) -> x*x | None -> 0 (* or parse e as another error type *) ;; In the last None clause above, you could try to parse e as another error type, continuing to consider as many error types as you want. The nice thing about this is you only have one error type, Error.t, so your APIs remain uncluttered. But you can deserialize to more strongly typed error types when you want to. The bad thing is the compiler can't tell you what are all the errors you have to consider, but this isn't achieved my most error handling strategies. Furthermore, this is all about errors, so I'm not sure exhaustiveness is so important. > Sometimes it's useful to organise errors into a hierarchy ... I don't see any way to do this in OCaml. You can get this with polymorphic variants, e.g type tcp_connection_refused =3D [`TCP_connection_refused] type tcp_error =3D [tcp_connection_refused | `Another_err] On Tue, Feb 3, 2015 at 12:26 PM, Sebastien Mondet < sebastien.mondet@gmail.com> wrote: > > Yes if we just all agree on this type: > http://erratique.ch/software/fut/doc/Fut.html#TYPEresult > then we are all compatible without actual library dependencies, thanks to > structural typing > > I've been abusing this for the past few years, it's great: > http://seb.mondet.org/software/pvem/index.html > http://seb.mondet.org/software/pvem_lwt_unix/index.html > http://seb.mondet.org/talks/compose2015/#/25 > http://seb.mondet.org/talks/compose2015/#/26 > > > > > > > > On Tue, Feb 3, 2015 at 12:10 PM, Daniel B=C3=BCnzli < > daniel.buenzli@erratique.ch> wrote: > >> Le mardi, 3 f=C3=A9vrier 2015 =C3=A0 16:55, Christophe Troestler a =C3= =A9crit : >> > Please lay down a concrete interface showing of what you mean. I >> > think we all agree on the goal of writing robust software, we need to >> > move the discussion to concrete proposals. >> >> Sorry don't have the time to work on this; these things come out of >> writing code. But as a start I don't see what's the problem with the bas= ic >> result monad everybody knows (e.g. see here [1,2]) along with a few >> with_resource combinators based on some kind of `finally` [3] and stick = to >> polymorphic variant errors =E2=80=94 along, of course, with Format prett= y printers >> for these something that is often annoyingly absent in APIs. And I would >> completely forget about using lwt's failed state (i.e. only to trap >> unexpected exceptions at the highest level). >> >> Best, >> >> Daniel >> >> [1] >> This deals only with string errors so it should be generalized to [2], >> but a few of the error handling >> combinators may be interesting. >> >> >> https://github.com/samoht/assemblage/blob/master/lib/assemblage.mli#L708= -L744 >> >> For example `reword_error` a quick combinator that allows to transform a >> lower-level error to a higher level one, i.e. give more context higher u= p >> when you have the info about what you are doing. Since we are using stri= ngs >> here it's also easy to stack the errors if you wish so (~replace:false >> argument) from the lowest-level of what went wrong (e.g. the actual util= ity >> invocation error) to what you were trying to do (e.g. determine the numb= er >> of processors in the system) which makes error diagnosis much easier >> (context + no error info is lost). Not that it wouldn't be impossible wi= th >> lists of polyvars, but one has to see how it comes out in practice. A fe= w >> examples: >> >> https://github.com/samoht/assemblage/blob/master/lib/as_conf.ml#L420-L42= 8 >> https://github.com/samoht/assemblage/blob/master/lib/as_conf.ml#L543-L54= 8 >> >> [2] >> This is the classical generalized result type for dealing with errors. >> http://erratique.ch/software/fut/doc/Fut.html#TYPEresult >> http://erratique.ch/software/fut/doc/Fut.html#VAL(&>>=3D) ( >> http://erratique.ch/software/fut/doc/Fut.html#VAL(&%3E%3E=3D)) >> http://erratique.ch/software/fut/doc/Futu.html#VALread >> >> [3] >> http://erratique.ch/software/fut/doc/Fut.html#VALfinally >> This could also be modified or another version provided to propagate >> possible errors in the finally handler in the concurrency monad itself. >> >> >> _______________________________________________ >> MirageOS-devel mailing list >> MirageOS-devel@lists.xenproject.org >> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel >> > > > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > > --089e0122e8b6d642c8050e334640 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
> System 3 provides (I think) no easy way to match on t= he type of error.

You can. An Error.t is constructed by = using Sexplib. Thus, you can deserialize them to whatever specific error yo= u want to consider. Here's an example:

op= en Core.Std;;

type myerr =3D [`Zero | `Neg of int]= with sexp;;

(* Get back to myerr if possible. *)<= /div>
let myerr_of_error (e:Error.t) : myerr option =3D
=C2= =A0 match Error.sexp_of_t e with
=C2=A0 | Sexp.List (_::x::[]) -&= gt; Some (myerr_of_sexp x)
=C2=A0 | _ -> None
;;

let f x : int Or_error.t =3D
=C2=A0 if = x =3D 0 then error "zero not allowed" `Zero sexp_of_error=C2=A0
=C2=A0 else if x < 0 then error "negative not allowed"= ; (`Neg x) sexp_of_error
=C2=A0 else Ok x
;;
=
let g x =3D match f x with
| Ok x -> x*x
<= div>| Error e -> match myerr_of_error e with
=C2=A0 | Some `Ze= ro -> 0
=C2=A0 | Some (`Neg x) -> x*x
=C2=A0 | No= ne -> 0 (* or parse e as another error type *)
;;
<= div>
In the last None clause above, you could try to parse e = as another error type, continuing to consider as many error types as you wa= nt. The nice thing about this is you only have one error type, Error.t, so = your APIs remain uncluttered. But you can deserialize to more strongly type= d error types when you want to.

The bad thing is t= he compiler can't tell you what are all the errors you have to consider= , but this isn't achieved my most error handling strategies. Furthermor= e, this is all about errors, so I'm not sure exhaustiveness is so impor= tant.


> Sometimes it's useful to organise er= rors into a hierarchy ... I don't see any way to do this in OCaml.
=
You can get this with polymorphic variants, e.g
type tcp_connection_refused =3D [`TCP_connection_refused]
type tcp_error =3D [tcp_connection_refused | `Another_err]
=


On Tue, Feb 3, 2015 at 12:26 P= M, Sebastien Mondet <sebastien.mondet@gmail.com> wr= ote:

=
Yes if we just all agree on this type: http://erratique.c= h/software/fut/doc/Fut.html#TYPEresult
then we are all compati= ble without actual library dependencies, thanks to structural typing
I've been abusing this for the past few years, it's great:http://seb.mondet.org/software/pvem/index.html
http:/= /seb.mondet.org/software/pvem_lwt_unix/index.html
http://seb.mondet.= org/talks/compose2015/#/25
http://seb.mondet.org/talks/compose2015/#= /26







On Tue, Feb 3, 2015 at 12:10 PM, Danie= l B=C3=BCnzli <daniel.buenzli@erratique.ch> wrote:=
Le mardi, 3 f=C3=A9vrier 2015 =C3=A0 16:= 55, Christophe Troestler a =C3=A9crit :
> Please lay down a concrete interface showing of what you mean. I=
> think we all agree on the goal of writing robust software, we need to<= br> > move the discussion to concrete proposals.

Sorry don't have the time to work on this; these things come out= of writing code. But as a start I don't see what's the problem wit= h the basic result monad everybody knows (e.g. see here [1,2]) along with a= few with_resource combinators based on some kind of `finally` [3] and stic= k to polymorphic variant errors =E2=80=94 along, of course, with Format pre= tty printers for these something that is often annoyingly absent in APIs. A= nd I would completely forget about using lwt's failed state (i.e. only = to trap unexpected exceptions at the highest level).

Best,

Daniel

[1]
This deals only with string errors so it should be generalized to [2], but = a few of the error handling
combinators may be interesting.

https://github.com/samoht/assemblage/blob/= master/lib/assemblage.mli#L708-L744

For example `reword_error` a quick combinator that allows to transform a lo= wer-level error to a higher level one, i.e. give more context higher up whe= n you have the info about what you are doing. Since we are using strings he= re it's also easy to stack the errors if you wish so (~replace:false ar= gument) from the lowest-level of what went wrong (e.g. the actual utility i= nvocation error) to what you were trying to do (e.g. determine the number o= f processors in the system) which makes error diagnosis much easier (contex= t + no error info is lost). Not that it wouldn't be impossible with lis= ts of polyvars, but one has to see how it comes out in practice. A few exam= ples:

https://github.com/samoht/assemblage/blob/mast= er/lib/as_conf.ml#L420-L428
https://github.com/samoht/assemblage/blob/mast= er/lib/as_conf.ml#L543-L548

[2]
This is the classical generalized result type for dealing with errors.
http://erratique.ch/software/fut/doc/Fut.html#TYPEresult http://erratique.ch/software/fut/doc/Fut.html#VAL(&>= >=3D) (http://erratique.ch/software/fut/doc/Fut.htm= l#VAL(&%3E%3E=3D))
http://erratique.ch/software/fut/doc/Futu.html#VALread

[3]
http://erratique.ch/software/fut/doc/Fut.html#VALfinally This could also be modified or another version provided to propagate possib= le errors in the finally handler in the concurrency monad itself.


_______________________________________________
MirageOS-devel mailing list
Mi= rageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo= /mirageos-devel


_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists= .xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo= /mirageos-devel


--089e0122e8b6d642c8050e334640-- --===============1110728963459783293== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --===============1110728963459783293==-- From mirageos-devel-bounces@lists.xenproject.org Tue Feb 03 18:59:24 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 03 Feb 2015 18:59:24 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YIih0-0002a9-CW; Tue, 03 Feb 2015 18:59:22 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YIigy-0002a4-Ba for mirageos-devel@lists.xenproject.org; Tue, 03 Feb 2015 18:59:20 +0000 Received: from [85.158.143.35] by server-1.bemta-4.messagelabs.com id A8/0C-03000-78A11D45; Tue, 03 Feb 2015 18:59:19 +0000 X-Env-Sender: daniel.buenzli@erratique.ch X-Msg-Ref: server-11.tower-21.messagelabs.com!1422989959!12253219!1 X-Originating-IP: [74.55.86.74] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNzQuNTUuODYuNzQgPT4gMzA4NTYz\n X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7142 invoked from network); 3 Feb 2015 18:59:19 -0000 Received: from mail6.webfaction.com (HELO smtp.webfaction.com) (74.55.86.74) by server-11.tower-21.messagelabs.com with SMTP; 3 Feb 2015 18:59:19 -0000 Received: from [172.20.10.2] (227-224.197-178.cust.bluewin.ch [178.197.224.227]) by smtp.webfaction.com (Postfix) with ESMTP id C8EB720D2BE4; Tue, 3 Feb 2015 18:59:15 +0000 (UTC) Date: Tue, 3 Feb 2015 19:59:09 +0100 From: =?utf-8?Q?Daniel_B=C3=BCnzli?= To: Ashish Agarwal Message-ID: In-Reply-To: References: <20150202.014549.1883720051237442569.Christophe.Troestler@umons.ac.be> <20150203.165548.1818962153128895170.Christophe.Troestler@umons.ac.be> <0235E905E5DE4F3B9422F8A37DC74FEB@erratique.ch> X-Mailer: sparrow 1.6.4 (build 1178) MIME-Version: 1.0 Content-Disposition: inline Cc: "=?utf-8?Q?mirageos-devel=40lists.xenproject.org?=" Subject: Re: [MirageOS-devel] Error handling in Mirage - request for comments! X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org TGUgbWFyZGksIDMgZsOpdnJpZXIgMjAxNSDDoCAxOTozMCwgQXNoaXNoIEFnYXJ3YWwgYSDDqWNy aXQgOgo+IHR5cGUgdGNwX2Nvbm5lY3Rpb25fcmVmdXNlZCA9IFtgVENQX2Nvbm5lY3Rpb25fcmVm dXNlZF0KPiB0eXBlIHRjcF9lcnJvciA9IFt0Y3BfY29ubmVjdGlvbl9yZWZ1c2VkIHwgYEFub3Ro ZXJfZXJyXQoKQW5kIGl0IHNob3VsZCBiZSBhZGRlZCwgYXMgTGVvIGFscmVhZHkgbWVudGlvbmVk LCB0aGF0IGlmIHlvdSBnYXRoZXJlZCB0b2dldGhlciBlcnJvcnMgZnJvbSBtdWx0aXBsZSBzb3Vy Y2VzIHlvdSBjYW4gZWFzaWx5IHNlbGVjdCBvbmx5IGB0Y3BfZXJyb3JgcyBieSBkb2luZyAgCgpt YXRjaCBlIHdpdGgKfCAjdGNwX2Vycm9yIGFzIGUgLT4g4oCmCnwgI290aGVyX25hbWVkX2NsYXNz X29mX2Vycm9yIGFzIGUgLT4gIAp8IOKApgoKRGFuaWVsCgoKCl9fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fCk1pcmFnZU9TLWRldmVsIG1haWxpbmcgbGlzdApN aXJhZ2VPUy1kZXZlbEBsaXN0cy54ZW5wcm9qZWN0Lm9yZwpodHRwOi8vbGlzdHMueGVucHJvamVj dC5vcmcvY2dpLWJpbi9tYWlsbWFuL2xpc3RpbmZvL21pcmFnZW9zLWRldmVsCg== From mirageos-devel-bounces@lists.xenproject.org Tue Feb 03 18:59:24 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 03 Feb 2015 18:59:24 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YIih0-0002a9-CW; Tue, 03 Feb 2015 18:59:22 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YIigy-0002a4-Ba for mirageos-devel@lists.xenproject.org; Tue, 03 Feb 2015 18:59:20 +0000 Received: from [85.158.143.35] by server-1.bemta-4.messagelabs.com id A8/0C-03000-78A11D45; Tue, 03 Feb 2015 18:59:19 +0000 X-Env-Sender: daniel.buenzli@erratique.ch X-Msg-Ref: server-11.tower-21.messagelabs.com!1422989959!12253219!1 X-Originating-IP: [74.55.86.74] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNzQuNTUuODYuNzQgPT4gMzA4NTYz\n X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7142 invoked from network); 3 Feb 2015 18:59:19 -0000 Received: from mail6.webfaction.com (HELO smtp.webfaction.com) (74.55.86.74) by server-11.tower-21.messagelabs.com with SMTP; 3 Feb 2015 18:59:19 -0000 Received: from [172.20.10.2] (227-224.197-178.cust.bluewin.ch [178.197.224.227]) by smtp.webfaction.com (Postfix) with ESMTP id C8EB720D2BE4; Tue, 3 Feb 2015 18:59:15 +0000 (UTC) Date: Tue, 3 Feb 2015 19:59:09 +0100 From: =?utf-8?Q?Daniel_B=C3=BCnzli?= To: Ashish Agarwal Message-ID: In-Reply-To: References: <20150202.014549.1883720051237442569.Christophe.Troestler@umons.ac.be> <20150203.165548.1818962153128895170.Christophe.Troestler@umons.ac.be> <0235E905E5DE4F3B9422F8A37DC74FEB@erratique.ch> X-Mailer: sparrow 1.6.4 (build 1178) MIME-Version: 1.0 Content-Disposition: inline Cc: "=?utf-8?Q?mirageos-devel=40lists.xenproject.org?=" Subject: Re: [MirageOS-devel] Error handling in Mirage - request for comments! X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org TGUgbWFyZGksIDMgZsOpdnJpZXIgMjAxNSDDoCAxOTozMCwgQXNoaXNoIEFnYXJ3YWwgYSDDqWNy aXQgOgo+IHR5cGUgdGNwX2Nvbm5lY3Rpb25fcmVmdXNlZCA9IFtgVENQX2Nvbm5lY3Rpb25fcmVm dXNlZF0KPiB0eXBlIHRjcF9lcnJvciA9IFt0Y3BfY29ubmVjdGlvbl9yZWZ1c2VkIHwgYEFub3Ro ZXJfZXJyXQoKQW5kIGl0IHNob3VsZCBiZSBhZGRlZCwgYXMgTGVvIGFscmVhZHkgbWVudGlvbmVk LCB0aGF0IGlmIHlvdSBnYXRoZXJlZCB0b2dldGhlciBlcnJvcnMgZnJvbSBtdWx0aXBsZSBzb3Vy Y2VzIHlvdSBjYW4gZWFzaWx5IHNlbGVjdCBvbmx5IGB0Y3BfZXJyb3JgcyBieSBkb2luZyAgCgpt YXRjaCBlIHdpdGgKfCAjdGNwX2Vycm9yIGFzIGUgLT4g4oCmCnwgI290aGVyX25hbWVkX2NsYXNz X29mX2Vycm9yIGFzIGUgLT4gIAp8IOKApgoKRGFuaWVsCgoKCl9fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fCk1pcmFnZU9TLWRldmVsIG1haWxpbmcgbGlzdApN aXJhZ2VPUy1kZXZlbEBsaXN0cy54ZW5wcm9qZWN0Lm9yZwpodHRwOi8vbGlzdHMueGVucHJvamVj dC5vcmcvY2dpLWJpbi9tYWlsbWFuL2xpc3RpbmZvL21pcmFnZW9zLWRldmVsCg== From mirageos-devel-bounces@lists.xenproject.org Tue Feb 03 19:17:10 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 03 Feb 2015 19:17:10 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YIiyB-0003v0-Om; Tue, 03 Feb 2015 19:17:07 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YIiy9-0003ua-R6 for mirageos-devel@lists.xenproject.org; Tue, 03 Feb 2015 19:17:06 +0000 Received: from [85.158.139.211] by server-1.bemta-5.messagelabs.com id 2C/C5-25903-1BE11D45; Tue, 03 Feb 2015 19:17:05 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-4.tower-206.messagelabs.com!1422991022!10978996!1 X-Originating-IP: [74.125.82.43] X-SpamReason: No, hits=0.6 required=7.0 tests=BODY_RANDOM_LONG, HTML_50_60,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30211 invoked from network); 3 Feb 2015 19:17:02 -0000 Received: from mail-wg0-f43.google.com (HELO mail-wg0-f43.google.com) (74.125.82.43) by server-4.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 3 Feb 2015 19:17:02 -0000 Received: by mail-wg0-f43.google.com with SMTP id y19so46454685wgg.2 for ; Tue, 03 Feb 2015 11:17:02 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:content-type:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; bh=RhDXi0tDDNO5nAn6/njukR4M9Suo2ZCaNNgYpbwXHQw=; b=X/T9wNJLw44mCD+jM8uCdlQeJ39q6iBS1aZ1wbRouuZgE2kIVKulE9epL0sB3+4Bxd Wr3Af4qwnUCiLYnY/6VVim7TGc0RbeZS8t8Lv7IKN9OvydmtaQ0o9xi78jgRCnS4sM0K WqxWCGojngk6WuLfw/qsstoPXgYdTZoxtf6cul4Ui2ZvQFpYczvRZc0IOhb+iGK1khkx M1761NYdmjTN6SFqHVCEWm5otK0bH2//A6bSuMc+ZZxhH496CTaTctiJikFipcJoV4IB skEg4V3hEJh0Lq2vA1m2AYNP7Azf26/SoDHEZgDnV/o1KK+DlwKdkvAqBix97j79wmJR kOeQ== X-Received: by 10.180.84.98 with SMTP id x2mr36913076wiy.14.1422991021889; Tue, 03 Feb 2015 11:17:01 -0800 (PST) Received: from [192.168.0.2] (cpc25-cmbg14-2-0-cust121.5-4.cable.virginm.net. [213.106.112.122]) by mx.google.com with ESMTPSA id hd5sm5392616wib.21.2015.02.03.11.17.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 03 Feb 2015 11:17:01 -0800 (PST) Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\)) From: Thomas Gazagnaire In-Reply-To: Date: Tue, 3 Feb 2015 19:16:59 +0000 Message-Id: References: <20150202.014549.1883720051237442569.Christophe.Troestler@umons.ac.be> <20150203.165548.1818962153128895170.Christophe.Troestler@umons.ac.be> <0235E905E5DE4F3B9422F8A37DC74FEB@erratique.ch> To: Ashish Agarwal X-Mailer: Apple Mail (2.1993) Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Error handling in Mirage - request for comments! X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1431713925035698413==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============1431713925035698413== Content-Type: multipart/alternative; boundary="Apple-Mail=_E834A94E-09B5-4609-8040-B11EDF3D054E" --Apple-Mail=_E834A94E-09B5-4609-8040-B11EDF3D054E Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 > > Sometimes it's useful to organise errors into a hierarchy ... I = don't see any way to do this in OCaml. >=20 > You can get this with polymorphic variants, e.g >=20 > type tcp_connection_refused =3D [`TCP_connection_refused] > type tcp_error =3D [tcp_connection_refused | `Another_err] An good example of this is the (autogen) HTTP error code hierarchy in = cohttp: = https://github.com/mirage/ocaml-cohttp/blob/master/lib/code.mli#L107 = Thomas >=20 >=20 >=20 > On Tue, Feb 3, 2015 at 12:26 PM, Sebastien Mondet = > wrote: >=20 > Yes if we just all agree on this type: = http://erratique.ch/software/fut/doc/Fut.html#TYPEresult = > then we are all compatible without actual library dependencies, thanks = to structural typing >=20 > I've been abusing this for the past few years, it's great: > http://seb.mondet.org/software/pvem/index.html = > http://seb.mondet.org/software/pvem_lwt_unix/index.html = > http://seb.mondet.org/talks/compose2015/#/25 = > http://seb.mondet.org/talks/compose2015/#/26 = >=20 >=20 >=20 >=20 >=20 >=20 >=20 > On Tue, Feb 3, 2015 at 12:10 PM, Daniel B=C3=BCnzli = > = wrote: > Le mardi, 3 f=C3=A9vrier 2015 =C3=A0 16:55, Christophe Troestler a = =C3=A9crit : > > Please lay down a concrete interface showing of what you mean. I > > think we all agree on the goal of writing robust software, we need = to > > move the discussion to concrete proposals. >=20 > Sorry don't have the time to work on this; these things come out of = writing code. But as a start I don't see what's the problem with the = basic result monad everybody knows (e.g. see here [1,2]) along with a = few with_resource combinators based on some kind of `finally` [3] and = stick to polymorphic variant errors =E2=80=94 along, of course, with = Format pretty printers for these something that is often annoyingly = absent in APIs. And I would completely forget about using lwt's failed = state (i.e. only to trap unexpected exceptions at the highest level). >=20 > Best, >=20 > Daniel >=20 > [1] > This deals only with string errors so it should be generalized to [2], = but a few of the error handling > combinators may be interesting. >=20 > = https://github.com/samoht/assemblage/blob/master/lib/assemblage.mli#L708-L= 744 = >=20 > For example `reword_error` a quick combinator that allows to transform = a lower-level error to a higher level one, i.e. give more context higher = up when you have the info about what you are doing. Since we are using = strings here it's also easy to stack the errors if you wish so = (~replace:false argument) from the lowest-level of what went wrong (e.g. = the actual utility invocation error) to what you were trying to do (e.g. = determine the number of processors in the system) which makes error = diagnosis much easier (context + no error info is lost). Not that it = wouldn't be impossible with lists of polyvars, but one has to see how it = comes out in practice. A few examples: >=20 > = https://github.com/samoht/assemblage/blob/master/lib/as_conf.ml#L420-L428 = > = https://github.com/samoht/assemblage/blob/master/lib/as_conf.ml#L543-L548 = >=20 > [2] > This is the classical generalized result type for dealing with errors. > http://erratique.ch/software/fut/doc/Fut.html#TYPEresult = > http://erratique.ch/software/fut/doc/Fut.html#VAL(& = >>=3D) = (http://erratique.ch/software/fut/doc/Fut.html#VAL(&%3E%3E=3D) = ) > http://erratique.ch/software/fut/doc/Futu.html#VALread = >=20 > [3] > http://erratique.ch/software/fut/doc/Fut.html#VALfinally = > This could also be modified or another version provided to propagate = possible errors in the finally handler in the concurrency monad itself. >=20 >=20 > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org = > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel = >=20 >=20 > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org = > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel = >=20 >=20 > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --Apple-Mail=_E834A94E-09B5-4609-8040-B11EDF3D054E Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8
> Sometimes it's useful to organise errors = into a hierarchy ... I don't see any way to do this in OCaml.

You can get this with = polymorphic variants, e.g

type tcp_connection_refused =3D = [`TCP_connection_refused]
type tcp_error =3D = [tcp_connection_refused | = `Another_err]

An good example of this is the (autogen) HTTP = error code hierarchy in cohttp: https://github.com/mirage/ocaml-cohttp/blob/master/lib/code.mli= #L107

Thomas





On Tue, = Feb 3, 2015 at 12:26 PM, Sebastien Mondet <sebastien.mondet@gmail.com> = wrote:

Yes if we just all agree on this type: http://erratique.ch/software/fut/doc/Fut.html#TYPEresult
then we are all compatible without actual library = dependencies, thanks to structural typing

I've been abusing this for the past few years, it's = great:
http://seb.mondet.org/software/pvem/index.html
http://seb.mondet.org/software/pvem_lwt_unix/index.html
http://seb.mondet.org/talks/compose2015/#/25
http://seb.mondet.org/talks/compose2015/#/26







On Tue, = Feb 3, 2015 at 12:10 PM, Daniel B=C3=BCnzli <daniel.buenzli@erratique.ch> = wrote:
Le mardi, 3 = f=C3=A9vrier 2015 =C3=A0 16:55, Christophe Troestler a =C3=A9crit :
> Please lay down a concrete interface showing of = what you mean. I
> think we all agree on the goal of writing robust software, we need = to
> move the discussion to concrete proposals.

Sorry don't have the time to work on this; these things come out = of writing code. But as a start I don't see what's the problem with the = basic result monad everybody knows (e.g. see here [1,2]) along with a = few with_resource combinators based on some kind of `finally` [3] and = stick to polymorphic variant errors =E2=80=94 along, of course, with = Format pretty printers for these something that is often annoyingly = absent in APIs. And I would completely forget about using lwt's failed = state (i.e. only to trap unexpected exceptions at the highest level).

Best,

Daniel

[1]
This deals only with string errors so it should be generalized to [2], = but a few of the error handling
combinators may be interesting.

https://github.com/samoht/assemblage/blob/master/lib/assemblage= .mli#L708-L744

For example `reword_error` a quick combinator that allows to transform a = lower-level error to a higher level one, i.e. give more context higher = up when you have the info about what you are doing. Since we are using = strings here it's also easy to stack the errors if you wish so = (~replace:false argument) from the lowest-level of what went wrong (e.g. = the actual utility invocation error) to what you were trying to do (e.g. = determine the number of processors in the system) which makes error = diagnosis much easier (context + no error info is lost). Not that it = wouldn't be impossible with lists of polyvars, but one has to see how it = comes out in practice. A few examples:

https://github.com/samoht/assemblage/blob/master/lib/as_conf.ml= #L420-L428
https://github.com/samoht/assemblage/blob/master/lib/as_conf.ml= #L543-L548

[2]
This is the classical generalized result type for dealing with = errors.
http://erratique.ch/software/fut/doc/Fut.html#TYPEresult http://erratique.ch/software/fut/doc/Fut.html#VAL(&>= >=3D) (http://erratique.ch/software/fut/doc/Fut.html#VAL(&%3E%3E=3D= ))
http://erratique.ch/software/fut/doc/Futu.html#VALread

[3]
http://erratique.ch/software/fut/doc/Fut.html#VALfinally This could also be modified or another version provided to propagate = possible errors in the finally handler in the concurrency monad = itself.


_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-d= evel


_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-d= evel


_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-d= evel

= --Apple-Mail=_E834A94E-09B5-4609-8040-B11EDF3D054E-- --===============1431713925035698413== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --===============1431713925035698413==-- From mirageos-devel-bounces@lists.xenproject.org Tue Feb 03 19:17:10 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 03 Feb 2015 19:17:10 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YIiyB-0003v0-Om; Tue, 03 Feb 2015 19:17:07 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YIiy9-0003ua-R6 for mirageos-devel@lists.xenproject.org; Tue, 03 Feb 2015 19:17:06 +0000 Received: from [85.158.139.211] by server-1.bemta-5.messagelabs.com id 2C/C5-25903-1BE11D45; Tue, 03 Feb 2015 19:17:05 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-4.tower-206.messagelabs.com!1422991022!10978996!1 X-Originating-IP: [74.125.82.43] X-SpamReason: No, hits=0.6 required=7.0 tests=BODY_RANDOM_LONG, HTML_50_60,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30211 invoked from network); 3 Feb 2015 19:17:02 -0000 Received: from mail-wg0-f43.google.com (HELO mail-wg0-f43.google.com) (74.125.82.43) by server-4.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 3 Feb 2015 19:17:02 -0000 Received: by mail-wg0-f43.google.com with SMTP id y19so46454685wgg.2 for ; Tue, 03 Feb 2015 11:17:02 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:content-type:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; bh=RhDXi0tDDNO5nAn6/njukR4M9Suo2ZCaNNgYpbwXHQw=; b=X/T9wNJLw44mCD+jM8uCdlQeJ39q6iBS1aZ1wbRouuZgE2kIVKulE9epL0sB3+4Bxd Wr3Af4qwnUCiLYnY/6VVim7TGc0RbeZS8t8Lv7IKN9OvydmtaQ0o9xi78jgRCnS4sM0K WqxWCGojngk6WuLfw/qsstoPXgYdTZoxtf6cul4Ui2ZvQFpYczvRZc0IOhb+iGK1khkx M1761NYdmjTN6SFqHVCEWm5otK0bH2//A6bSuMc+ZZxhH496CTaTctiJikFipcJoV4IB skEg4V3hEJh0Lq2vA1m2AYNP7Azf26/SoDHEZgDnV/o1KK+DlwKdkvAqBix97j79wmJR kOeQ== X-Received: by 10.180.84.98 with SMTP id x2mr36913076wiy.14.1422991021889; Tue, 03 Feb 2015 11:17:01 -0800 (PST) Received: from [192.168.0.2] (cpc25-cmbg14-2-0-cust121.5-4.cable.virginm.net. [213.106.112.122]) by mx.google.com with ESMTPSA id hd5sm5392616wib.21.2015.02.03.11.17.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 03 Feb 2015 11:17:01 -0800 (PST) Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\)) From: Thomas Gazagnaire In-Reply-To: Date: Tue, 3 Feb 2015 19:16:59 +0000 Message-Id: References: <20150202.014549.1883720051237442569.Christophe.Troestler@umons.ac.be> <20150203.165548.1818962153128895170.Christophe.Troestler@umons.ac.be> <0235E905E5DE4F3B9422F8A37DC74FEB@erratique.ch> To: Ashish Agarwal X-Mailer: Apple Mail (2.1993) Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Error handling in Mirage - request for comments! X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1431713925035698413==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============1431713925035698413== Content-Type: multipart/alternative; boundary="Apple-Mail=_E834A94E-09B5-4609-8040-B11EDF3D054E" --Apple-Mail=_E834A94E-09B5-4609-8040-B11EDF3D054E Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 > > Sometimes it's useful to organise errors into a hierarchy ... I = don't see any way to do this in OCaml. >=20 > You can get this with polymorphic variants, e.g >=20 > type tcp_connection_refused =3D [`TCP_connection_refused] > type tcp_error =3D [tcp_connection_refused | `Another_err] An good example of this is the (autogen) HTTP error code hierarchy in = cohttp: = https://github.com/mirage/ocaml-cohttp/blob/master/lib/code.mli#L107 = Thomas >=20 >=20 >=20 > On Tue, Feb 3, 2015 at 12:26 PM, Sebastien Mondet = > wrote: >=20 > Yes if we just all agree on this type: = http://erratique.ch/software/fut/doc/Fut.html#TYPEresult = > then we are all compatible without actual library dependencies, thanks = to structural typing >=20 > I've been abusing this for the past few years, it's great: > http://seb.mondet.org/software/pvem/index.html = > http://seb.mondet.org/software/pvem_lwt_unix/index.html = > http://seb.mondet.org/talks/compose2015/#/25 = > http://seb.mondet.org/talks/compose2015/#/26 = >=20 >=20 >=20 >=20 >=20 >=20 >=20 > On Tue, Feb 3, 2015 at 12:10 PM, Daniel B=C3=BCnzli = > = wrote: > Le mardi, 3 f=C3=A9vrier 2015 =C3=A0 16:55, Christophe Troestler a = =C3=A9crit : > > Please lay down a concrete interface showing of what you mean. I > > think we all agree on the goal of writing robust software, we need = to > > move the discussion to concrete proposals. >=20 > Sorry don't have the time to work on this; these things come out of = writing code. But as a start I don't see what's the problem with the = basic result monad everybody knows (e.g. see here [1,2]) along with a = few with_resource combinators based on some kind of `finally` [3] and = stick to polymorphic variant errors =E2=80=94 along, of course, with = Format pretty printers for these something that is often annoyingly = absent in APIs. And I would completely forget about using lwt's failed = state (i.e. only to trap unexpected exceptions at the highest level). >=20 > Best, >=20 > Daniel >=20 > [1] > This deals only with string errors so it should be generalized to [2], = but a few of the error handling > combinators may be interesting. >=20 > = https://github.com/samoht/assemblage/blob/master/lib/assemblage.mli#L708-L= 744 = >=20 > For example `reword_error` a quick combinator that allows to transform = a lower-level error to a higher level one, i.e. give more context higher = up when you have the info about what you are doing. Since we are using = strings here it's also easy to stack the errors if you wish so = (~replace:false argument) from the lowest-level of what went wrong (e.g. = the actual utility invocation error) to what you were trying to do (e.g. = determine the number of processors in the system) which makes error = diagnosis much easier (context + no error info is lost). Not that it = wouldn't be impossible with lists of polyvars, but one has to see how it = comes out in practice. A few examples: >=20 > = https://github.com/samoht/assemblage/blob/master/lib/as_conf.ml#L420-L428 = > = https://github.com/samoht/assemblage/blob/master/lib/as_conf.ml#L543-L548 = >=20 > [2] > This is the classical generalized result type for dealing with errors. > http://erratique.ch/software/fut/doc/Fut.html#TYPEresult = > http://erratique.ch/software/fut/doc/Fut.html#VAL(& = >>=3D) = (http://erratique.ch/software/fut/doc/Fut.html#VAL(&%3E%3E=3D) = ) > http://erratique.ch/software/fut/doc/Futu.html#VALread = >=20 > [3] > http://erratique.ch/software/fut/doc/Fut.html#VALfinally = > This could also be modified or another version provided to propagate = possible errors in the finally handler in the concurrency monad itself. >=20 >=20 > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org = > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel = >=20 >=20 > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org = > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel = >=20 >=20 > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --Apple-Mail=_E834A94E-09B5-4609-8040-B11EDF3D054E Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8
> Sometimes it's useful to organise errors = into a hierarchy ... I don't see any way to do this in OCaml.

You can get this with = polymorphic variants, e.g

type tcp_connection_refused =3D = [`TCP_connection_refused]
type tcp_error =3D = [tcp_connection_refused | = `Another_err]

An good example of this is the (autogen) HTTP = error code hierarchy in cohttp: https://github.com/mirage/ocaml-cohttp/blob/master/lib/code.mli= #L107

Thomas





On Tue, = Feb 3, 2015 at 12:26 PM, Sebastien Mondet <sebastien.mondet@gmail.com> = wrote:

Yes if we just all agree on this type: http://erratique.ch/software/fut/doc/Fut.html#TYPEresult
then we are all compatible without actual library = dependencies, thanks to structural typing

I've been abusing this for the past few years, it's = great:
http://seb.mondet.org/software/pvem/index.html
http://seb.mondet.org/software/pvem_lwt_unix/index.html
http://seb.mondet.org/talks/compose2015/#/25
http://seb.mondet.org/talks/compose2015/#/26







On Tue, = Feb 3, 2015 at 12:10 PM, Daniel B=C3=BCnzli <daniel.buenzli@erratique.ch> = wrote:
Le mardi, 3 = f=C3=A9vrier 2015 =C3=A0 16:55, Christophe Troestler a =C3=A9crit :
> Please lay down a concrete interface showing of = what you mean. I
> think we all agree on the goal of writing robust software, we need = to
> move the discussion to concrete proposals.

Sorry don't have the time to work on this; these things come out = of writing code. But as a start I don't see what's the problem with the = basic result monad everybody knows (e.g. see here [1,2]) along with a = few with_resource combinators based on some kind of `finally` [3] and = stick to polymorphic variant errors =E2=80=94 along, of course, with = Format pretty printers for these something that is often annoyingly = absent in APIs. And I would completely forget about using lwt's failed = state (i.e. only to trap unexpected exceptions at the highest level).

Best,

Daniel

[1]
This deals only with string errors so it should be generalized to [2], = but a few of the error handling
combinators may be interesting.

https://github.com/samoht/assemblage/blob/master/lib/assemblage= .mli#L708-L744

For example `reword_error` a quick combinator that allows to transform a = lower-level error to a higher level one, i.e. give more context higher = up when you have the info about what you are doing. Since we are using = strings here it's also easy to stack the errors if you wish so = (~replace:false argument) from the lowest-level of what went wrong (e.g. = the actual utility invocation error) to what you were trying to do (e.g. = determine the number of processors in the system) which makes error = diagnosis much easier (context + no error info is lost). Not that it = wouldn't be impossible with lists of polyvars, but one has to see how it = comes out in practice. A few examples:

https://github.com/samoht/assemblage/blob/master/lib/as_conf.ml= #L420-L428
https://github.com/samoht/assemblage/blob/master/lib/as_conf.ml= #L543-L548

[2]
This is the classical generalized result type for dealing with = errors.
http://erratique.ch/software/fut/doc/Fut.html#TYPEresult http://erratique.ch/software/fut/doc/Fut.html#VAL(&>= >=3D) (http://erratique.ch/software/fut/doc/Fut.html#VAL(&%3E%3E=3D= ))
http://erratique.ch/software/fut/doc/Futu.html#VALread

[3]
http://erratique.ch/software/fut/doc/Fut.html#VALfinally This could also be modified or another version provided to propagate = possible errors in the finally handler in the concurrency monad = itself.


_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-d= evel


_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-d= evel


_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-d= evel

= --Apple-Mail=_E834A94E-09B5-4609-8040-B11EDF3D054E-- --===============1431713925035698413== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --===============1431713925035698413==-- From mirageos-devel-bounces@lists.xenproject.org Tue Feb 03 19:25:59 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 03 Feb 2015 19:25:59 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YIj6l-00005E-Pe; Tue, 03 Feb 2015 19:25:59 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YIj6k-00004t-PZ for mirageos-devel@lists.xenproject.org; Tue, 03 Feb 2015 19:25:59 +0000 Received: from [85.158.137.68] by server-13.bemta-3.messagelabs.com id EE/CF-02898-6C021D45; Tue, 03 Feb 2015 19:25:58 +0000 X-Env-Sender: talex5@gmail.com X-Msg-Ref: server-14.tower-31.messagelabs.com!1422991554!9332503!1 X-Originating-IP: [209.85.217.176] X-SpamReason: No, hits=0.6 required=7.0 tests=MAILTO_TO_SPAM_ADDR, RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.12.5; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3033 invoked from network); 3 Feb 2015 19:25:54 -0000 Received: from mail-lb0-f176.google.com (HELO mail-lb0-f176.google.com) (209.85.217.176) by server-14.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 3 Feb 2015 19:25:54 -0000 Received: by mail-lb0-f176.google.com with SMTP id z12so40447930lbi.7 for ; Tue, 03 Feb 2015 11:25:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=/v6y8l3bJL3pxqYAnflQWCnT3ZAhiuW0SzdeihDcCOw=; b=LO94sOzBzPBfhBJOGn/dYt6XSH71mLYbJe/6gQnDZUrV2M/D0B9o3MqkVNyNqmI6m8 7zA8HNWERBEISpps3tH9Ofuknr1Pd6+gx1Hw65VBKqgBsvdN+vmQahfC41+pKLXTxwi+ UXQyqBWylkFOh3vjbFAgH+Hg7TLRy2cOkQfroKSfevopHx8HhG1Gqqp/+qF2S7Ra1Fcm NdVJ3HE4WZGJn1oVUa5jxfDLra1xMc/yHkVMvypOd6kOtaxkjETOxxNh5qDGwM9eAtrB TMAJAXoTE/a5r/4BagWB86GD3bd/Gfge40GcGKchUp4qTbJ/znt2krQto+ceNY09/oaQ b8KQ== MIME-Version: 1.0 X-Received: by 10.152.183.196 with SMTP id eo4mr26956699lac.0.1422991553802; Tue, 03 Feb 2015 11:25:53 -0800 (PST) Received: by 10.25.207.206 with HTTP; Tue, 3 Feb 2015 11:25:53 -0800 (PST) In-Reply-To: References: <20150202.014549.1883720051237442569.Christophe.Troestler@umons.ac.be> <20150203.165548.1818962153128895170.Christophe.Troestler@umons.ac.be> <0235E905E5DE4F3B9422F8A37DC74FEB@erratique.ch> Date: Tue, 3 Feb 2015 19:25:53 +0000 Message-ID: From: Thomas Leonard To: Ashish Agarwal Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Error handling in Mirage - request for comments! X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org T24gMyBGZWJydWFyeSAyMDE1IGF0IDE4OjMwLCBBc2hpc2ggQWdhcndhbCA8YWdhcndhbDE5NzVA Z21haWwuY29tPiB3cm90ZToKPj4gU3lzdGVtIDMgcHJvdmlkZXMgKEkgdGhpbmspIG5vIGVhc3kg d2F5IHRvIG1hdGNoIG9uIHRoZSB0eXBlIG9mIGVycm9yLgo+Cj4gWW91IGNhbi4gQW4gRXJyb3Iu dCBpcyBjb25zdHJ1Y3RlZCBieSB1c2luZyBTZXhwbGliLiBUaHVzLCB5b3UgY2FuCj4gZGVzZXJp YWxpemUgdGhlbSB0byB3aGF0ZXZlciBzcGVjaWZpYyBlcnJvciB5b3Ugd2FudCB0byBjb25zaWRl ci4gSGVyZSdzIGFuCj4gZXhhbXBsZToKPgo+IG9wZW4gQ29yZS5TdGQ7Owo+Cj4gdHlwZSBteWVy ciA9IFtgWmVybyB8IGBOZWcgb2YgaW50XSB3aXRoIHNleHA7Owo+Cj4gKCogR2V0IGJhY2sgdG8g bXllcnIgaWYgcG9zc2libGUuICopCj4gbGV0IG15ZXJyX29mX2Vycm9yIChlOkVycm9yLnQpIDog bXllcnIgb3B0aW9uID0KPiAgIG1hdGNoIEVycm9yLnNleHBfb2ZfdCBlIHdpdGgKPiAgIHwgU2V4 cC5MaXN0IChfOjp4OjpbXSkgLT4gU29tZSAobXllcnJfb2Zfc2V4cCB4KQo+ICAgfCBfIC0+IE5v bmUKCkkgZG9uJ3QgdW5kZXJzdGFuZCBob3cgdGhpcyB3b3Jrcy4gSG93IGRvZXMgbXllcnJfb2Zf ZXJyb3Iga25vdyB0aGF0CnRoaXMgaXMgYSBteWVycj8gSXQgc2VlbXMgdG8gYmUganVzdCB0ZXN0 aW5nIHRoYXQgdGhlIHNleHAgaXMgYSAyLWl0ZW0KbGlzdC4gRG9lcyBpdCB0aHJvdyBhbiBleGNl cHRpb24gaWYgZ2l2ZW4gc29tZSBkaWZmZXJlbnQgdHlwZSBvZgplcnJvcj8KCj4gbGV0IGYgeCA6 IGludCBPcl9lcnJvci50ID0KPiAgIGlmIHggPSAwIHRoZW4gZXJyb3IgInplcm8gbm90IGFsbG93 ZWQiIGBaZXJvIHNleHBfb2ZfZXJyb3IKPiAgIGVsc2UgaWYgeCA8IDAgdGhlbiBlcnJvciAibmVn YXRpdmUgbm90IGFsbG93ZWQiIChgTmVnIHgpIHNleHBfb2ZfZXJyb3IKPiAgIGVsc2UgT2sgeAo+ IDs7Cj4KPiBsZXQgZyB4ID0gbWF0Y2ggZiB4IHdpdGgKPiB8IE9rIHggLT4geCp4Cj4gfCBFcnJv ciBlIC0+IG1hdGNoIG15ZXJyX29mX2Vycm9yIGUgd2l0aAo+ICAgfCBTb21lIGBaZXJvIC0+IDAK PiAgIHwgU29tZSAoYE5lZyB4KSAtPiB4KngKPiAgIHwgTm9uZSAtPiAwICgqIG9yIHBhcnNlIGUg YXMgYW5vdGhlciBlcnJvciB0eXBlICopCj4gOzsKPgo+IEluIHRoZSBsYXN0IE5vbmUgY2xhdXNl IGFib3ZlLCB5b3UgY291bGQgdHJ5IHRvIHBhcnNlIGUgYXMgYW5vdGhlciBlcnJvcgo+IHR5cGUs IGNvbnRpbnVpbmcgdG8gY29uc2lkZXIgYXMgbWFueSBlcnJvciB0eXBlcyBhcyB5b3Ugd2FudC4g VGhlIG5pY2UgdGhpbmcKPiBhYm91dCB0aGlzIGlzIHlvdSBvbmx5IGhhdmUgb25lIGVycm9yIHR5 cGUsIEVycm9yLnQsIHNvIHlvdXIgQVBJcyByZW1haW4KPiB1bmNsdXR0ZXJlZC4gQnV0IHlvdSBj YW4gZGVzZXJpYWxpemUgdG8gbW9yZSBzdHJvbmdseSB0eXBlZCBlcnJvciB0eXBlcyB3aGVuCj4g eW91IHdhbnQgdG8uCj4KPiBUaGUgYmFkIHRoaW5nIGlzIHRoZSBjb21waWxlciBjYW4ndCB0ZWxs IHlvdSB3aGF0IGFyZSBhbGwgdGhlIGVycm9ycyB5b3UKPiBoYXZlIHRvIGNvbnNpZGVyLCBidXQg dGhpcyBpc24ndCBhY2hpZXZlZCBteSBtb3N0IGVycm9yIGhhbmRsaW5nIHN0cmF0ZWdpZXMuCj4g RnVydGhlcm1vcmUsIHRoaXMgaXMgYWxsIGFib3V0IGVycm9ycywgc28gSSdtIG5vdCBzdXJlIGV4 aGF1c3RpdmVuZXNzIGlzIHNvCj4gaW1wb3J0YW50LgoKUmlnaHQuCgo+PiBTb21ldGltZXMgaXQn cyB1c2VmdWwgdG8gb3JnYW5pc2UgZXJyb3JzIGludG8gYSBoaWVyYXJjaHkgLi4uIEkgZG9uJ3Qg c2VlCj4+IGFueSB3YXkgdG8gZG8gdGhpcyBpbiBPQ2FtbC4KPgo+IFlvdSBjYW4gZ2V0IHRoaXMg d2l0aCBwb2x5bW9ycGhpYyB2YXJpYW50cywgZS5nCj4KPiB0eXBlIHRjcF9jb25uZWN0aW9uX3Jl ZnVzZWQgPSBbYFRDUF9jb25uZWN0aW9uX3JlZnVzZWRdCj4gdHlwZSB0Y3BfZXJyb3IgPSBbdGNw X2Nvbm5lY3Rpb25fcmVmdXNlZCB8IGBBbm90aGVyX2Vycl0KClRoZSBwcm9ibGVtIGlzIHRoYXQg dGhlIHN1YmNsYXNzZXMgZ2V0IGFkZGVkIGVsc2V3aGVyZS4gZS5nLgoKbWlyYWdlLXR5cGVzJ3Mg RlMgbWF5IGRlZmluZSBSZWFkX29ubHksIGJ1dCBhbiBleHQ0IGZpbGVzeXN0ZW0gbWlnaHQKZGVm aW5lIGUuZy4gUmVhZF9vbmx5X2ZpbGUsIEltbXV0YWJsZV9maWxlIGFuZCBGU19tb3VudGVkX3Jl YWRfb25seS4KSWRlYWxseSwgZ2VuZXJpYyBjb2RlIGNhdGNoaW5nIElzX3JlYWRfb25seSBzaG91 bGQgYWxzbyBjYXRjaCB0aGUKc3BlY2lmaWMgY2FzZXMuCgpJbiBKYXZhLCB5b3UnZCBkbyBzb21l dGhpbmcgbGlrZToKCiAgY2xhc3MgUmVhZF9vbmx5IGV4dGVuZHMgRXhjZXB0aW9uCgpHZW5lcmlj IGNvZGUgd291bGQgdXNlICJjYXRjaCAoUmVhZF9vbmx5IGV4KSIsIGJ1dCBpbXBsZW1lbnRhdGlv bnMKY291bGQgYWxzbyBhZGQgc3ViZXhjZXB0aW9ucyB3aXRoOgoKICBjbGFzcyBGU19tb3VudGVk X3JlYWRfb25seSBleHRlbmRzIFJlYWRfb25seV9maWxlCgpDb2RlIGNvdWxkIHRoZW4gYWxzbyBj YXRjaCB0aGlzIHNwZWNpZmljIGNhc2UgaWYgZGVzaXJlZC4gTW9yZQppbXBvcnRhbnRseSwgdGhv dWdoLCB0aGUgc3ViZXhjZXB0aW9uIGNhbiBhZGQgZXh0cmEgZGV0YWlscyB0byB0aGUKZXJyb3Ig bWVzc2FnZS4KCgo+IE9uIFR1ZSwgRmViIDMsIDIwMTUgYXQgMTI6MjYgUE0sIFNlYmFzdGllbiBN b25kZXQKPiA8c2ViYXN0aWVuLm1vbmRldEBnbWFpbC5jb20+IHdyb3RlOgo+Pgo+Pgo+PiBZZXMg aWYgd2UganVzdCBhbGwgYWdyZWUgb24gdGhpcyB0eXBlOgo+PiBodHRwOi8vZXJyYXRpcXVlLmNo L3NvZnR3YXJlL2Z1dC9kb2MvRnV0Lmh0bWwjVFlQRXJlc3VsdAo+PiB0aGVuIHdlIGFyZSBhbGwg Y29tcGF0aWJsZSB3aXRob3V0IGFjdHVhbCBsaWJyYXJ5IGRlcGVuZGVuY2llcywgdGhhbmtzIHRv Cj4+IHN0cnVjdHVyYWwgdHlwaW5nCj4+Cj4+IEkndmUgYmVlbiBhYnVzaW5nIHRoaXMgZm9yIHRo ZSBwYXN0IGZldyB5ZWFycywgaXQncyBncmVhdDoKPj4gaHR0cDovL3NlYi5tb25kZXQub3JnL3Nv ZnR3YXJlL3B2ZW0vaW5kZXguaHRtbAo+PiBodHRwOi8vc2ViLm1vbmRldC5vcmcvc29mdHdhcmUv cHZlbV9sd3RfdW5peC9pbmRleC5odG1sCj4+IGh0dHA6Ly9zZWIubW9uZGV0Lm9yZy90YWxrcy9j b21wb3NlMjAxNS8jLzI1Cj4+IGh0dHA6Ly9zZWIubW9uZGV0Lm9yZy90YWxrcy9jb21wb3NlMjAx NS8jLzI2Cj4+Cj4+Cj4+Cj4+Cj4+Cj4+Cj4+Cj4+IE9uIFR1ZSwgRmViIDMsIDIwMTUgYXQgMTI6 MTAgUE0sIERhbmllbCBCw7xuemxpCj4+IDxkYW5pZWwuYnVlbnpsaUBlcnJhdGlxdWUuY2g+IHdy b3RlOgo+Pj4KPj4+IExlIG1hcmRpLCAzIGbDqXZyaWVyIDIwMTUgw6AgMTY6NTUsIENocmlzdG9w aGUgVHJvZXN0bGVyIGEgw6ljcml0IDoKPj4+ID4gUGxlYXNlIGxheSBkb3duIGEgY29uY3JldGUg aW50ZXJmYWNlIHNob3dpbmcgb2Ygd2hhdCB5b3UgbWVhbi4gSQo+Pj4gPiB0aGluayB3ZSBhbGwg YWdyZWUgb24gdGhlIGdvYWwgb2Ygd3JpdGluZyByb2J1c3Qgc29mdHdhcmUsIHdlIG5lZWQgdG8K Pj4+ID4gbW92ZSB0aGUgZGlzY3Vzc2lvbiB0byBjb25jcmV0ZSBwcm9wb3NhbHMuCj4+Pgo+Pj4g U29ycnkgZG9uJ3QgaGF2ZSB0aGUgdGltZSB0byB3b3JrIG9uIHRoaXM7IHRoZXNlIHRoaW5ncyBj b21lIG91dCBvZgo+Pj4gd3JpdGluZyBjb2RlLiBCdXQgYXMgYSBzdGFydCBJIGRvbid0IHNlZSB3 aGF0J3MgdGhlIHByb2JsZW0gd2l0aCB0aGUgYmFzaWMKPj4+IHJlc3VsdCBtb25hZCBldmVyeWJv ZHkga25vd3MgKGUuZy4gc2VlIGhlcmUgWzEsMl0pIGFsb25nIHdpdGggYSBmZXcKPj4+IHdpdGhf cmVzb3VyY2UgY29tYmluYXRvcnMgYmFzZWQgb24gc29tZSBraW5kIG9mIGBmaW5hbGx5YCBbM10g YW5kIHN0aWNrIHRvCj4+PiBwb2x5bW9ycGhpYyB2YXJpYW50IGVycm9ycyDigJQgYWxvbmcsIG9m IGNvdXJzZSwgd2l0aCBGb3JtYXQgcHJldHR5IHByaW50ZXJzCj4+PiBmb3IgdGhlc2Ugc29tZXRo aW5nIHRoYXQgaXMgb2Z0ZW4gYW5ub3lpbmdseSBhYnNlbnQgaW4gQVBJcy4gQW5kIEkgd291bGQK Pj4+IGNvbXBsZXRlbHkgZm9yZ2V0IGFib3V0IHVzaW5nIGx3dCdzIGZhaWxlZCBzdGF0ZSAoaS5l LiBvbmx5IHRvIHRyYXAKPj4+IHVuZXhwZWN0ZWQgZXhjZXB0aW9ucyBhdCB0aGUgaGlnaGVzdCBs ZXZlbCkuCj4+Pgo+Pj4gQmVzdCwKPj4+Cj4+PiBEYW5pZWwKPj4+Cj4+PiBbMV0KPj4+IFRoaXMg ZGVhbHMgb25seSB3aXRoIHN0cmluZyBlcnJvcnMgc28gaXQgc2hvdWxkIGJlIGdlbmVyYWxpemVk IHRvIFsyXSwKPj4+IGJ1dCBhIGZldyBvZiB0aGUgZXJyb3IgaGFuZGxpbmcKPj4+IGNvbWJpbmF0 b3JzIG1heSBiZSBpbnRlcmVzdGluZy4KPj4+Cj4+Pgo+Pj4gaHR0cHM6Ly9naXRodWIuY29tL3Nh bW9odC9hc3NlbWJsYWdlL2Jsb2IvbWFzdGVyL2xpYi9hc3NlbWJsYWdlLm1saSNMNzA4LUw3NDQK Pj4+Cj4+PiBGb3IgZXhhbXBsZSBgcmV3b3JkX2Vycm9yYCBhIHF1aWNrIGNvbWJpbmF0b3IgdGhh dCBhbGxvd3MgdG8gdHJhbnNmb3JtIGEKPj4+IGxvd2VyLWxldmVsIGVycm9yIHRvIGEgaGlnaGVy IGxldmVsIG9uZSwgaS5lLiBnaXZlIG1vcmUgY29udGV4dCBoaWdoZXIgdXAKPj4+IHdoZW4geW91 IGhhdmUgdGhlIGluZm8gYWJvdXQgd2hhdCB5b3UgYXJlIGRvaW5nLiBTaW5jZSB3ZSBhcmUgdXNp bmcgc3RyaW5ncwo+Pj4gaGVyZSBpdCdzIGFsc28gZWFzeSB0byBzdGFjayB0aGUgZXJyb3JzIGlm IHlvdSB3aXNoIHNvICh+cmVwbGFjZTpmYWxzZQo+Pj4gYXJndW1lbnQpIGZyb20gdGhlIGxvd2Vz dC1sZXZlbCBvZiB3aGF0IHdlbnQgd3JvbmcgKGUuZy4gdGhlIGFjdHVhbCB1dGlsaXR5Cj4+PiBp bnZvY2F0aW9uIGVycm9yKSB0byB3aGF0IHlvdSB3ZXJlIHRyeWluZyB0byBkbyAoZS5nLiBkZXRl cm1pbmUgdGhlIG51bWJlcgo+Pj4gb2YgcHJvY2Vzc29ycyBpbiB0aGUgc3lzdGVtKSB3aGljaCBt YWtlcyBlcnJvciBkaWFnbm9zaXMgbXVjaCBlYXNpZXIKPj4+IChjb250ZXh0ICsgbm8gZXJyb3Ig aW5mbyBpcyBsb3N0KS4gTm90IHRoYXQgaXQgd291bGRuJ3QgYmUgaW1wb3NzaWJsZSB3aXRoCj4+ PiBsaXN0cyBvZiBwb2x5dmFycywgYnV0IG9uZSBoYXMgdG8gc2VlIGhvdyBpdCBjb21lcyBvdXQg aW4gcHJhY3RpY2UuIEEgZmV3Cj4+PiBleGFtcGxlczoKPj4+Cj4+PiBodHRwczovL2dpdGh1Yi5j b20vc2Ftb2h0L2Fzc2VtYmxhZ2UvYmxvYi9tYXN0ZXIvbGliL2FzX2NvbmYubWwjTDQyMC1MNDI4 Cj4+PiBodHRwczovL2dpdGh1Yi5jb20vc2Ftb2h0L2Fzc2VtYmxhZ2UvYmxvYi9tYXN0ZXIvbGli L2FzX2NvbmYubWwjTDU0My1MNTQ4Cj4+Pgo+Pj4gWzJdCj4+PiBUaGlzIGlzIHRoZSBjbGFzc2lj YWwgZ2VuZXJhbGl6ZWQgcmVzdWx0IHR5cGUgZm9yIGRlYWxpbmcgd2l0aCBlcnJvcnMuCj4+PiBo dHRwOi8vZXJyYXRpcXVlLmNoL3NvZnR3YXJlL2Z1dC9kb2MvRnV0Lmh0bWwjVFlQRXJlc3VsdAo+ Pj4gaHR0cDovL2VycmF0aXF1ZS5jaC9zb2Z0d2FyZS9mdXQvZG9jL0Z1dC5odG1sI1ZBTCgmPj49 KQo+Pj4gKGh0dHA6Ly9lcnJhdGlxdWUuY2gvc29mdHdhcmUvZnV0L2RvYy9GdXQuaHRtbCNWQUwo JiUzRSUzRT0pKQo+Pj4gaHR0cDovL2VycmF0aXF1ZS5jaC9zb2Z0d2FyZS9mdXQvZG9jL0Z1dHUu aHRtbCNWQUxyZWFkCj4+Pgo+Pj4gWzNdCj4+PiBodHRwOi8vZXJyYXRpcXVlLmNoL3NvZnR3YXJl L2Z1dC9kb2MvRnV0Lmh0bWwjVkFMZmluYWxseQo+Pj4gVGhpcyBjb3VsZCBhbHNvIGJlIG1vZGlm aWVkIG9yIGFub3RoZXIgdmVyc2lvbiBwcm92aWRlZCB0byBwcm9wYWdhdGUKPj4+IHBvc3NpYmxl IGVycm9ycyBpbiB0aGUgZmluYWxseSBoYW5kbGVyIGluIHRoZSBjb25jdXJyZW5jeSBtb25hZCBp dHNlbGYuCgoKCi0tIApEciBUaG9tYXMgTGVvbmFyZCAgICAgICAgaHR0cDovLzBpbnN0YWxsLm5l dC8KR1BHOiA5MjQyIDk4MDcgQzk4NSAzQzA3IDQ0QTYgIDhCOUEgQUUwNyA4MjgwIDU5QTUgM0ND MQpHUEc6IERBOTggMjVBRSBDQUQwIDg5NzUgN0NEQSAgQkQ4RSAwNzEzIDNGOTYgQ0E3NCBEOEJB CgpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwpNaXJhZ2VP Uy1kZXZlbCBtYWlsaW5nIGxpc3QKTWlyYWdlT1MtZGV2ZWxAbGlzdHMueGVucHJvamVjdC5vcmcK aHR0cDovL2xpc3RzLnhlbnByb2plY3Qub3JnL2NnaS1iaW4vbWFpbG1hbi9saXN0aW5mby9taXJh Z2Vvcy1kZXZlbAo= From mirageos-devel-bounces@lists.xenproject.org Tue Feb 03 19:25:59 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 03 Feb 2015 19:25:59 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YIj6l-00005E-Pe; Tue, 03 Feb 2015 19:25:59 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YIj6k-00004t-PZ for mirageos-devel@lists.xenproject.org; Tue, 03 Feb 2015 19:25:59 +0000 Received: from [85.158.137.68] by server-13.bemta-3.messagelabs.com id EE/CF-02898-6C021D45; Tue, 03 Feb 2015 19:25:58 +0000 X-Env-Sender: talex5@gmail.com X-Msg-Ref: server-14.tower-31.messagelabs.com!1422991554!9332503!1 X-Originating-IP: [209.85.217.176] X-SpamReason: No, hits=0.6 required=7.0 tests=MAILTO_TO_SPAM_ADDR, RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.12.5; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3033 invoked from network); 3 Feb 2015 19:25:54 -0000 Received: from mail-lb0-f176.google.com (HELO mail-lb0-f176.google.com) (209.85.217.176) by server-14.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 3 Feb 2015 19:25:54 -0000 Received: by mail-lb0-f176.google.com with SMTP id z12so40447930lbi.7 for ; Tue, 03 Feb 2015 11:25:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=/v6y8l3bJL3pxqYAnflQWCnT3ZAhiuW0SzdeihDcCOw=; b=LO94sOzBzPBfhBJOGn/dYt6XSH71mLYbJe/6gQnDZUrV2M/D0B9o3MqkVNyNqmI6m8 7zA8HNWERBEISpps3tH9Ofuknr1Pd6+gx1Hw65VBKqgBsvdN+vmQahfC41+pKLXTxwi+ UXQyqBWylkFOh3vjbFAgH+Hg7TLRy2cOkQfroKSfevopHx8HhG1Gqqp/+qF2S7Ra1Fcm NdVJ3HE4WZGJn1oVUa5jxfDLra1xMc/yHkVMvypOd6kOtaxkjETOxxNh5qDGwM9eAtrB TMAJAXoTE/a5r/4BagWB86GD3bd/Gfge40GcGKchUp4qTbJ/znt2krQto+ceNY09/oaQ b8KQ== MIME-Version: 1.0 X-Received: by 10.152.183.196 with SMTP id eo4mr26956699lac.0.1422991553802; Tue, 03 Feb 2015 11:25:53 -0800 (PST) Received: by 10.25.207.206 with HTTP; Tue, 3 Feb 2015 11:25:53 -0800 (PST) In-Reply-To: References: <20150202.014549.1883720051237442569.Christophe.Troestler@umons.ac.be> <20150203.165548.1818962153128895170.Christophe.Troestler@umons.ac.be> <0235E905E5DE4F3B9422F8A37DC74FEB@erratique.ch> Date: Tue, 3 Feb 2015 19:25:53 +0000 Message-ID: From: Thomas Leonard To: Ashish Agarwal Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Error handling in Mirage - request for comments! X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org T24gMyBGZWJydWFyeSAyMDE1IGF0IDE4OjMwLCBBc2hpc2ggQWdhcndhbCA8YWdhcndhbDE5NzVA Z21haWwuY29tPiB3cm90ZToKPj4gU3lzdGVtIDMgcHJvdmlkZXMgKEkgdGhpbmspIG5vIGVhc3kg d2F5IHRvIG1hdGNoIG9uIHRoZSB0eXBlIG9mIGVycm9yLgo+Cj4gWW91IGNhbi4gQW4gRXJyb3Iu dCBpcyBjb25zdHJ1Y3RlZCBieSB1c2luZyBTZXhwbGliLiBUaHVzLCB5b3UgY2FuCj4gZGVzZXJp YWxpemUgdGhlbSB0byB3aGF0ZXZlciBzcGVjaWZpYyBlcnJvciB5b3Ugd2FudCB0byBjb25zaWRl ci4gSGVyZSdzIGFuCj4gZXhhbXBsZToKPgo+IG9wZW4gQ29yZS5TdGQ7Owo+Cj4gdHlwZSBteWVy ciA9IFtgWmVybyB8IGBOZWcgb2YgaW50XSB3aXRoIHNleHA7Owo+Cj4gKCogR2V0IGJhY2sgdG8g bXllcnIgaWYgcG9zc2libGUuICopCj4gbGV0IG15ZXJyX29mX2Vycm9yIChlOkVycm9yLnQpIDog bXllcnIgb3B0aW9uID0KPiAgIG1hdGNoIEVycm9yLnNleHBfb2ZfdCBlIHdpdGgKPiAgIHwgU2V4 cC5MaXN0IChfOjp4OjpbXSkgLT4gU29tZSAobXllcnJfb2Zfc2V4cCB4KQo+ICAgfCBfIC0+IE5v bmUKCkkgZG9uJ3QgdW5kZXJzdGFuZCBob3cgdGhpcyB3b3Jrcy4gSG93IGRvZXMgbXllcnJfb2Zf ZXJyb3Iga25vdyB0aGF0CnRoaXMgaXMgYSBteWVycj8gSXQgc2VlbXMgdG8gYmUganVzdCB0ZXN0 aW5nIHRoYXQgdGhlIHNleHAgaXMgYSAyLWl0ZW0KbGlzdC4gRG9lcyBpdCB0aHJvdyBhbiBleGNl cHRpb24gaWYgZ2l2ZW4gc29tZSBkaWZmZXJlbnQgdHlwZSBvZgplcnJvcj8KCj4gbGV0IGYgeCA6 IGludCBPcl9lcnJvci50ID0KPiAgIGlmIHggPSAwIHRoZW4gZXJyb3IgInplcm8gbm90IGFsbG93 ZWQiIGBaZXJvIHNleHBfb2ZfZXJyb3IKPiAgIGVsc2UgaWYgeCA8IDAgdGhlbiBlcnJvciAibmVn YXRpdmUgbm90IGFsbG93ZWQiIChgTmVnIHgpIHNleHBfb2ZfZXJyb3IKPiAgIGVsc2UgT2sgeAo+ IDs7Cj4KPiBsZXQgZyB4ID0gbWF0Y2ggZiB4IHdpdGgKPiB8IE9rIHggLT4geCp4Cj4gfCBFcnJv ciBlIC0+IG1hdGNoIG15ZXJyX29mX2Vycm9yIGUgd2l0aAo+ICAgfCBTb21lIGBaZXJvIC0+IDAK PiAgIHwgU29tZSAoYE5lZyB4KSAtPiB4KngKPiAgIHwgTm9uZSAtPiAwICgqIG9yIHBhcnNlIGUg YXMgYW5vdGhlciBlcnJvciB0eXBlICopCj4gOzsKPgo+IEluIHRoZSBsYXN0IE5vbmUgY2xhdXNl IGFib3ZlLCB5b3UgY291bGQgdHJ5IHRvIHBhcnNlIGUgYXMgYW5vdGhlciBlcnJvcgo+IHR5cGUs IGNvbnRpbnVpbmcgdG8gY29uc2lkZXIgYXMgbWFueSBlcnJvciB0eXBlcyBhcyB5b3Ugd2FudC4g VGhlIG5pY2UgdGhpbmcKPiBhYm91dCB0aGlzIGlzIHlvdSBvbmx5IGhhdmUgb25lIGVycm9yIHR5 cGUsIEVycm9yLnQsIHNvIHlvdXIgQVBJcyByZW1haW4KPiB1bmNsdXR0ZXJlZC4gQnV0IHlvdSBj YW4gZGVzZXJpYWxpemUgdG8gbW9yZSBzdHJvbmdseSB0eXBlZCBlcnJvciB0eXBlcyB3aGVuCj4g eW91IHdhbnQgdG8uCj4KPiBUaGUgYmFkIHRoaW5nIGlzIHRoZSBjb21waWxlciBjYW4ndCB0ZWxs IHlvdSB3aGF0IGFyZSBhbGwgdGhlIGVycm9ycyB5b3UKPiBoYXZlIHRvIGNvbnNpZGVyLCBidXQg dGhpcyBpc24ndCBhY2hpZXZlZCBteSBtb3N0IGVycm9yIGhhbmRsaW5nIHN0cmF0ZWdpZXMuCj4g RnVydGhlcm1vcmUsIHRoaXMgaXMgYWxsIGFib3V0IGVycm9ycywgc28gSSdtIG5vdCBzdXJlIGV4 aGF1c3RpdmVuZXNzIGlzIHNvCj4gaW1wb3J0YW50LgoKUmlnaHQuCgo+PiBTb21ldGltZXMgaXQn cyB1c2VmdWwgdG8gb3JnYW5pc2UgZXJyb3JzIGludG8gYSBoaWVyYXJjaHkgLi4uIEkgZG9uJ3Qg c2VlCj4+IGFueSB3YXkgdG8gZG8gdGhpcyBpbiBPQ2FtbC4KPgo+IFlvdSBjYW4gZ2V0IHRoaXMg d2l0aCBwb2x5bW9ycGhpYyB2YXJpYW50cywgZS5nCj4KPiB0eXBlIHRjcF9jb25uZWN0aW9uX3Jl ZnVzZWQgPSBbYFRDUF9jb25uZWN0aW9uX3JlZnVzZWRdCj4gdHlwZSB0Y3BfZXJyb3IgPSBbdGNw X2Nvbm5lY3Rpb25fcmVmdXNlZCB8IGBBbm90aGVyX2Vycl0KClRoZSBwcm9ibGVtIGlzIHRoYXQg dGhlIHN1YmNsYXNzZXMgZ2V0IGFkZGVkIGVsc2V3aGVyZS4gZS5nLgoKbWlyYWdlLXR5cGVzJ3Mg RlMgbWF5IGRlZmluZSBSZWFkX29ubHksIGJ1dCBhbiBleHQ0IGZpbGVzeXN0ZW0gbWlnaHQKZGVm aW5lIGUuZy4gUmVhZF9vbmx5X2ZpbGUsIEltbXV0YWJsZV9maWxlIGFuZCBGU19tb3VudGVkX3Jl YWRfb25seS4KSWRlYWxseSwgZ2VuZXJpYyBjb2RlIGNhdGNoaW5nIElzX3JlYWRfb25seSBzaG91 bGQgYWxzbyBjYXRjaCB0aGUKc3BlY2lmaWMgY2FzZXMuCgpJbiBKYXZhLCB5b3UnZCBkbyBzb21l dGhpbmcgbGlrZToKCiAgY2xhc3MgUmVhZF9vbmx5IGV4dGVuZHMgRXhjZXB0aW9uCgpHZW5lcmlj IGNvZGUgd291bGQgdXNlICJjYXRjaCAoUmVhZF9vbmx5IGV4KSIsIGJ1dCBpbXBsZW1lbnRhdGlv bnMKY291bGQgYWxzbyBhZGQgc3ViZXhjZXB0aW9ucyB3aXRoOgoKICBjbGFzcyBGU19tb3VudGVk X3JlYWRfb25seSBleHRlbmRzIFJlYWRfb25seV9maWxlCgpDb2RlIGNvdWxkIHRoZW4gYWxzbyBj YXRjaCB0aGlzIHNwZWNpZmljIGNhc2UgaWYgZGVzaXJlZC4gTW9yZQppbXBvcnRhbnRseSwgdGhv dWdoLCB0aGUgc3ViZXhjZXB0aW9uIGNhbiBhZGQgZXh0cmEgZGV0YWlscyB0byB0aGUKZXJyb3Ig bWVzc2FnZS4KCgo+IE9uIFR1ZSwgRmViIDMsIDIwMTUgYXQgMTI6MjYgUE0sIFNlYmFzdGllbiBN b25kZXQKPiA8c2ViYXN0aWVuLm1vbmRldEBnbWFpbC5jb20+IHdyb3RlOgo+Pgo+Pgo+PiBZZXMg aWYgd2UganVzdCBhbGwgYWdyZWUgb24gdGhpcyB0eXBlOgo+PiBodHRwOi8vZXJyYXRpcXVlLmNo L3NvZnR3YXJlL2Z1dC9kb2MvRnV0Lmh0bWwjVFlQRXJlc3VsdAo+PiB0aGVuIHdlIGFyZSBhbGwg Y29tcGF0aWJsZSB3aXRob3V0IGFjdHVhbCBsaWJyYXJ5IGRlcGVuZGVuY2llcywgdGhhbmtzIHRv Cj4+IHN0cnVjdHVyYWwgdHlwaW5nCj4+Cj4+IEkndmUgYmVlbiBhYnVzaW5nIHRoaXMgZm9yIHRo ZSBwYXN0IGZldyB5ZWFycywgaXQncyBncmVhdDoKPj4gaHR0cDovL3NlYi5tb25kZXQub3JnL3Nv ZnR3YXJlL3B2ZW0vaW5kZXguaHRtbAo+PiBodHRwOi8vc2ViLm1vbmRldC5vcmcvc29mdHdhcmUv cHZlbV9sd3RfdW5peC9pbmRleC5odG1sCj4+IGh0dHA6Ly9zZWIubW9uZGV0Lm9yZy90YWxrcy9j b21wb3NlMjAxNS8jLzI1Cj4+IGh0dHA6Ly9zZWIubW9uZGV0Lm9yZy90YWxrcy9jb21wb3NlMjAx NS8jLzI2Cj4+Cj4+Cj4+Cj4+Cj4+Cj4+Cj4+Cj4+IE9uIFR1ZSwgRmViIDMsIDIwMTUgYXQgMTI6 MTAgUE0sIERhbmllbCBCw7xuemxpCj4+IDxkYW5pZWwuYnVlbnpsaUBlcnJhdGlxdWUuY2g+IHdy b3RlOgo+Pj4KPj4+IExlIG1hcmRpLCAzIGbDqXZyaWVyIDIwMTUgw6AgMTY6NTUsIENocmlzdG9w aGUgVHJvZXN0bGVyIGEgw6ljcml0IDoKPj4+ID4gUGxlYXNlIGxheSBkb3duIGEgY29uY3JldGUg aW50ZXJmYWNlIHNob3dpbmcgb2Ygd2hhdCB5b3UgbWVhbi4gSQo+Pj4gPiB0aGluayB3ZSBhbGwg YWdyZWUgb24gdGhlIGdvYWwgb2Ygd3JpdGluZyByb2J1c3Qgc29mdHdhcmUsIHdlIG5lZWQgdG8K Pj4+ID4gbW92ZSB0aGUgZGlzY3Vzc2lvbiB0byBjb25jcmV0ZSBwcm9wb3NhbHMuCj4+Pgo+Pj4g U29ycnkgZG9uJ3QgaGF2ZSB0aGUgdGltZSB0byB3b3JrIG9uIHRoaXM7IHRoZXNlIHRoaW5ncyBj b21lIG91dCBvZgo+Pj4gd3JpdGluZyBjb2RlLiBCdXQgYXMgYSBzdGFydCBJIGRvbid0IHNlZSB3 aGF0J3MgdGhlIHByb2JsZW0gd2l0aCB0aGUgYmFzaWMKPj4+IHJlc3VsdCBtb25hZCBldmVyeWJv ZHkga25vd3MgKGUuZy4gc2VlIGhlcmUgWzEsMl0pIGFsb25nIHdpdGggYSBmZXcKPj4+IHdpdGhf cmVzb3VyY2UgY29tYmluYXRvcnMgYmFzZWQgb24gc29tZSBraW5kIG9mIGBmaW5hbGx5YCBbM10g YW5kIHN0aWNrIHRvCj4+PiBwb2x5bW9ycGhpYyB2YXJpYW50IGVycm9ycyDigJQgYWxvbmcsIG9m IGNvdXJzZSwgd2l0aCBGb3JtYXQgcHJldHR5IHByaW50ZXJzCj4+PiBmb3IgdGhlc2Ugc29tZXRo aW5nIHRoYXQgaXMgb2Z0ZW4gYW5ub3lpbmdseSBhYnNlbnQgaW4gQVBJcy4gQW5kIEkgd291bGQK Pj4+IGNvbXBsZXRlbHkgZm9yZ2V0IGFib3V0IHVzaW5nIGx3dCdzIGZhaWxlZCBzdGF0ZSAoaS5l LiBvbmx5IHRvIHRyYXAKPj4+IHVuZXhwZWN0ZWQgZXhjZXB0aW9ucyBhdCB0aGUgaGlnaGVzdCBs ZXZlbCkuCj4+Pgo+Pj4gQmVzdCwKPj4+Cj4+PiBEYW5pZWwKPj4+Cj4+PiBbMV0KPj4+IFRoaXMg ZGVhbHMgb25seSB3aXRoIHN0cmluZyBlcnJvcnMgc28gaXQgc2hvdWxkIGJlIGdlbmVyYWxpemVk IHRvIFsyXSwKPj4+IGJ1dCBhIGZldyBvZiB0aGUgZXJyb3IgaGFuZGxpbmcKPj4+IGNvbWJpbmF0 b3JzIG1heSBiZSBpbnRlcmVzdGluZy4KPj4+Cj4+Pgo+Pj4gaHR0cHM6Ly9naXRodWIuY29tL3Nh bW9odC9hc3NlbWJsYWdlL2Jsb2IvbWFzdGVyL2xpYi9hc3NlbWJsYWdlLm1saSNMNzA4LUw3NDQK Pj4+Cj4+PiBGb3IgZXhhbXBsZSBgcmV3b3JkX2Vycm9yYCBhIHF1aWNrIGNvbWJpbmF0b3IgdGhh dCBhbGxvd3MgdG8gdHJhbnNmb3JtIGEKPj4+IGxvd2VyLWxldmVsIGVycm9yIHRvIGEgaGlnaGVy IGxldmVsIG9uZSwgaS5lLiBnaXZlIG1vcmUgY29udGV4dCBoaWdoZXIgdXAKPj4+IHdoZW4geW91 IGhhdmUgdGhlIGluZm8gYWJvdXQgd2hhdCB5b3UgYXJlIGRvaW5nLiBTaW5jZSB3ZSBhcmUgdXNp bmcgc3RyaW5ncwo+Pj4gaGVyZSBpdCdzIGFsc28gZWFzeSB0byBzdGFjayB0aGUgZXJyb3JzIGlm IHlvdSB3aXNoIHNvICh+cmVwbGFjZTpmYWxzZQo+Pj4gYXJndW1lbnQpIGZyb20gdGhlIGxvd2Vz dC1sZXZlbCBvZiB3aGF0IHdlbnQgd3JvbmcgKGUuZy4gdGhlIGFjdHVhbCB1dGlsaXR5Cj4+PiBp bnZvY2F0aW9uIGVycm9yKSB0byB3aGF0IHlvdSB3ZXJlIHRyeWluZyB0byBkbyAoZS5nLiBkZXRl cm1pbmUgdGhlIG51bWJlcgo+Pj4gb2YgcHJvY2Vzc29ycyBpbiB0aGUgc3lzdGVtKSB3aGljaCBt YWtlcyBlcnJvciBkaWFnbm9zaXMgbXVjaCBlYXNpZXIKPj4+IChjb250ZXh0ICsgbm8gZXJyb3Ig aW5mbyBpcyBsb3N0KS4gTm90IHRoYXQgaXQgd291bGRuJ3QgYmUgaW1wb3NzaWJsZSB3aXRoCj4+ PiBsaXN0cyBvZiBwb2x5dmFycywgYnV0IG9uZSBoYXMgdG8gc2VlIGhvdyBpdCBjb21lcyBvdXQg aW4gcHJhY3RpY2UuIEEgZmV3Cj4+PiBleGFtcGxlczoKPj4+Cj4+PiBodHRwczovL2dpdGh1Yi5j b20vc2Ftb2h0L2Fzc2VtYmxhZ2UvYmxvYi9tYXN0ZXIvbGliL2FzX2NvbmYubWwjTDQyMC1MNDI4 Cj4+PiBodHRwczovL2dpdGh1Yi5jb20vc2Ftb2h0L2Fzc2VtYmxhZ2UvYmxvYi9tYXN0ZXIvbGli L2FzX2NvbmYubWwjTDU0My1MNTQ4Cj4+Pgo+Pj4gWzJdCj4+PiBUaGlzIGlzIHRoZSBjbGFzc2lj YWwgZ2VuZXJhbGl6ZWQgcmVzdWx0IHR5cGUgZm9yIGRlYWxpbmcgd2l0aCBlcnJvcnMuCj4+PiBo dHRwOi8vZXJyYXRpcXVlLmNoL3NvZnR3YXJlL2Z1dC9kb2MvRnV0Lmh0bWwjVFlQRXJlc3VsdAo+ Pj4gaHR0cDovL2VycmF0aXF1ZS5jaC9zb2Z0d2FyZS9mdXQvZG9jL0Z1dC5odG1sI1ZBTCgmPj49 KQo+Pj4gKGh0dHA6Ly9lcnJhdGlxdWUuY2gvc29mdHdhcmUvZnV0L2RvYy9GdXQuaHRtbCNWQUwo JiUzRSUzRT0pKQo+Pj4gaHR0cDovL2VycmF0aXF1ZS5jaC9zb2Z0d2FyZS9mdXQvZG9jL0Z1dHUu aHRtbCNWQUxyZWFkCj4+Pgo+Pj4gWzNdCj4+PiBodHRwOi8vZXJyYXRpcXVlLmNoL3NvZnR3YXJl L2Z1dC9kb2MvRnV0Lmh0bWwjVkFMZmluYWxseQo+Pj4gVGhpcyBjb3VsZCBhbHNvIGJlIG1vZGlm aWVkIG9yIGFub3RoZXIgdmVyc2lvbiBwcm92aWRlZCB0byBwcm9wYWdhdGUKPj4+IHBvc3NpYmxl IGVycm9ycyBpbiB0aGUgZmluYWxseSBoYW5kbGVyIGluIHRoZSBjb25jdXJyZW5jeSBtb25hZCBp dHNlbGYuCgoKCi0tIApEciBUaG9tYXMgTGVvbmFyZCAgICAgICAgaHR0cDovLzBpbnN0YWxsLm5l dC8KR1BHOiA5MjQyIDk4MDcgQzk4NSAzQzA3IDQ0QTYgIDhCOUEgQUUwNyA4MjgwIDU5QTUgM0ND MQpHUEc6IERBOTggMjVBRSBDQUQwIDg5NzUgN0NEQSAgQkQ4RSAwNzEzIDNGOTYgQ0E3NCBEOEJB CgpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwpNaXJhZ2VP Uy1kZXZlbCBtYWlsaW5nIGxpc3QKTWlyYWdlT1MtZGV2ZWxAbGlzdHMueGVucHJvamVjdC5vcmcK aHR0cDovL2xpc3RzLnhlbnByb2plY3Qub3JnL2NnaS1iaW4vbWFpbG1hbi9saXN0aW5mby9taXJh Z2Vvcy1kZXZlbAo= From mirageos-devel-bounces@lists.xenproject.org Tue Feb 03 19:48:03 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 03 Feb 2015 19:48:03 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YIjS2-0001cu-Mw; Tue, 03 Feb 2015 19:47:58 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YIjS1-0001cp-J4 for mirageos-devel@lists.xenproject.org; Tue, 03 Feb 2015 19:47:57 +0000 Received: from [85.158.143.35] by server-2.bemta-4.messagelabs.com id 75/8D-02749-CE521D45; Tue, 03 Feb 2015 19:47:56 +0000 X-Env-Sender: agarwal1975@gmail.com X-Msg-Ref: server-10.tower-21.messagelabs.com!1422992875!12299235!1 X-Originating-IP: [74.125.82.43] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE, RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21571 invoked from network); 3 Feb 2015 19:47:56 -0000 Received: from mail-wg0-f43.google.com (HELO mail-wg0-f43.google.com) (74.125.82.43) by server-10.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 3 Feb 2015 19:47:56 -0000 Received: by mail-wg0-f43.google.com with SMTP id y19so46595750wgg.2 for ; Tue, 03 Feb 2015 11:47:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=v18YNBUSiwi6VNEMRZYwq88ZVm91FIxGpU70sj4AVC4=; b=W1QsaKIt2LdWeQjji1WWbNS4llxMGvj8+6dwdNGDabK7/gJ8iww7ENoc1KePBUMhFS WYlwgVae3VU1QsLHEsDWl0TQocaG+TEI8y0j5txueNQDvEiFRuidhEMbTtFog7rPIG27 dslnMYMRqXIsbWeBiyGoL8psUoQRjTHc/+63xwWZhS5OYp9yRNbgalmTVG6gAnDzuD1S GRCz8uK3KV3kXaE3vIJm7Q7vbeHKZYwXcdzRU1oDXg+jnAg3HViY1sw1Ru56uXywmwvD x+oS3PA7c/Rg8DMbidue60evgpVzrTjSnll7xb8vR1zdGby439yEDkKMNjg1dRW2rv8X oA8g== X-Received: by 10.194.172.227 with SMTP id bf3mr7703694wjc.124.1422992875523; Tue, 03 Feb 2015 11:47:55 -0800 (PST) MIME-Version: 1.0 Received: by 10.27.15.4 with HTTP; Tue, 3 Feb 2015 11:47:35 -0800 (PST) In-Reply-To: References: <20150202.014549.1883720051237442569.Christophe.Troestler@umons.ac.be> <20150203.165548.1818962153128895170.Christophe.Troestler@umons.ac.be> <0235E905E5DE4F3B9422F8A37DC74FEB@erratique.ch> From: Ashish Agarwal Date: Tue, 3 Feb 2015 14:47:35 -0500 Message-ID: To: Thomas Leonard Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Error handling in Mirage - request for comments! X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============3491423317923893107==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============3491423317923893107== Content-Type: multipart/alternative; boundary=089e0122f36add15f3050e3458f7 --089e0122f36add15f3050e3458f7 Content-Type: text/plain; charset=UTF-8 On Tue, Feb 3, 2015 at 2:25 PM, Thomas Leonard wrote: > > open Core.Std;; > > > > type myerr = [`Zero | `Neg of int] with sexp;; > > > > (* Get back to myerr if possible. *) > > let myerr_of_error (e:Error.t) : myerr option = > > match Error.sexp_of_t e with > > | Sexp.List (_::x::[]) -> Some (myerr_of_sexp x) > > | _ -> None > > I don't understand how this works. How does myerr_of_error know that > this is a myerr? It seems to be just testing that the sexp is a 2-item > list. It's a best effort implementation. Error.create puts a string as the first item of the list and your specific error value as the second item. I haven't checked what happens when you apply Error.tag. I'd have to investigate more to see if there's a reasonably predictable sexp structure, so you can know which part is the myerr. Does it throw an exception if given some different type of > error? > I decided to return None, but maybe we could again return an Error.t. --089e0122f36add15f3050e3458f7 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On T= ue, Feb 3, 2015 at 2:25 PM, Thomas Leonard <talex5@gmail.com>= wrote:
=C2=A0
> open Core.Std;;
>
> type myerr =3D [`Zero | `Neg of int] with sexp;;
>
> (* Get back to myerr if possible. *)
> let myerr_of_error (e:Error.t) : myerr option =3D
>=C2=A0 =C2=A0match Error.sexp_of_t e with
>=C2=A0 =C2=A0| Sexp.List (_::x::[]) -> Some (myerr_of_sexp x)
>=C2=A0 =C2=A0| _ -> None

I don't understand how this works. How does myerr_of_error know = that
this is a myerr? It seems to be just testing that the sexp is a 2-item
list.

It's a best effort implementation= . Error.create puts a string as the first item of the list and your specifi= c error value as the second item. I haven't checked what happens when y= ou apply Error.tag. I'd have to investigate more to see if there's = a reasonably predictable sexp structure, so you can know which part is the = myerr.


D= oes it throw an exception if given some different type of
error?

I decided to return None, but ma= ybe we could again return an Error.t.

--089e0122f36add15f3050e3458f7-- --===============3491423317923893107== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --===============3491423317923893107==-- From mirageos-devel-bounces@lists.xenproject.org Tue Feb 03 19:48:03 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 03 Feb 2015 19:48:03 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YIjS2-0001cu-Mw; Tue, 03 Feb 2015 19:47:58 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YIjS1-0001cp-J4 for mirageos-devel@lists.xenproject.org; Tue, 03 Feb 2015 19:47:57 +0000 Received: from [85.158.143.35] by server-2.bemta-4.messagelabs.com id 75/8D-02749-CE521D45; Tue, 03 Feb 2015 19:47:56 +0000 X-Env-Sender: agarwal1975@gmail.com X-Msg-Ref: server-10.tower-21.messagelabs.com!1422992875!12299235!1 X-Originating-IP: [74.125.82.43] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE, RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21571 invoked from network); 3 Feb 2015 19:47:56 -0000 Received: from mail-wg0-f43.google.com (HELO mail-wg0-f43.google.com) (74.125.82.43) by server-10.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 3 Feb 2015 19:47:56 -0000 Received: by mail-wg0-f43.google.com with SMTP id y19so46595750wgg.2 for ; Tue, 03 Feb 2015 11:47:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=v18YNBUSiwi6VNEMRZYwq88ZVm91FIxGpU70sj4AVC4=; b=W1QsaKIt2LdWeQjji1WWbNS4llxMGvj8+6dwdNGDabK7/gJ8iww7ENoc1KePBUMhFS WYlwgVae3VU1QsLHEsDWl0TQocaG+TEI8y0j5txueNQDvEiFRuidhEMbTtFog7rPIG27 dslnMYMRqXIsbWeBiyGoL8psUoQRjTHc/+63xwWZhS5OYp9yRNbgalmTVG6gAnDzuD1S GRCz8uK3KV3kXaE3vIJm7Q7vbeHKZYwXcdzRU1oDXg+jnAg3HViY1sw1Ru56uXywmwvD x+oS3PA7c/Rg8DMbidue60evgpVzrTjSnll7xb8vR1zdGby439yEDkKMNjg1dRW2rv8X oA8g== X-Received: by 10.194.172.227 with SMTP id bf3mr7703694wjc.124.1422992875523; Tue, 03 Feb 2015 11:47:55 -0800 (PST) MIME-Version: 1.0 Received: by 10.27.15.4 with HTTP; Tue, 3 Feb 2015 11:47:35 -0800 (PST) In-Reply-To: References: <20150202.014549.1883720051237442569.Christophe.Troestler@umons.ac.be> <20150203.165548.1818962153128895170.Christophe.Troestler@umons.ac.be> <0235E905E5DE4F3B9422F8A37DC74FEB@erratique.ch> From: Ashish Agarwal Date: Tue, 3 Feb 2015 14:47:35 -0500 Message-ID: To: Thomas Leonard Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Error handling in Mirage - request for comments! X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============3491423317923893107==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============3491423317923893107== Content-Type: multipart/alternative; boundary=089e0122f36add15f3050e3458f7 --089e0122f36add15f3050e3458f7 Content-Type: text/plain; charset=UTF-8 On Tue, Feb 3, 2015 at 2:25 PM, Thomas Leonard wrote: > > open Core.Std;; > > > > type myerr = [`Zero | `Neg of int] with sexp;; > > > > (* Get back to myerr if possible. *) > > let myerr_of_error (e:Error.t) : myerr option = > > match Error.sexp_of_t e with > > | Sexp.List (_::x::[]) -> Some (myerr_of_sexp x) > > | _ -> None > > I don't understand how this works. How does myerr_of_error know that > this is a myerr? It seems to be just testing that the sexp is a 2-item > list. It's a best effort implementation. Error.create puts a string as the first item of the list and your specific error value as the second item. I haven't checked what happens when you apply Error.tag. I'd have to investigate more to see if there's a reasonably predictable sexp structure, so you can know which part is the myerr. Does it throw an exception if given some different type of > error? > I decided to return None, but maybe we could again return an Error.t. --089e0122f36add15f3050e3458f7 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On T= ue, Feb 3, 2015 at 2:25 PM, Thomas Leonard <talex5@gmail.com>= wrote:
=C2=A0
> open Core.Std;;
>
> type myerr =3D [`Zero | `Neg of int] with sexp;;
>
> (* Get back to myerr if possible. *)
> let myerr_of_error (e:Error.t) : myerr option =3D
>=C2=A0 =C2=A0match Error.sexp_of_t e with
>=C2=A0 =C2=A0| Sexp.List (_::x::[]) -> Some (myerr_of_sexp x)
>=C2=A0 =C2=A0| _ -> None

I don't understand how this works. How does myerr_of_error know = that
this is a myerr? It seems to be just testing that the sexp is a 2-item
list.

It's a best effort implementation= . Error.create puts a string as the first item of the list and your specifi= c error value as the second item. I haven't checked what happens when y= ou apply Error.tag. I'd have to investigate more to see if there's = a reasonably predictable sexp structure, so you can know which part is the = myerr.


D= oes it throw an exception if given some different type of
error?

I decided to return None, but ma= ybe we could again return an Error.t.

--089e0122f36add15f3050e3458f7-- --===============3491423317923893107== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --===============3491423317923893107==-- From mirageos-devel-bounces@lists.xenproject.org Tue Feb 03 19:49:04 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 03 Feb 2015 19:49:04 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YIjT6-0001g7-S7; Tue, 03 Feb 2015 19:49:04 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YIjT6-0001g2-0a for mirageos-devel@lists.xenproject.org; Tue, 03 Feb 2015 19:49:04 +0000 Received: from [85.158.137.68] by server-12.bemta-3.messagelabs.com id 35/FA-02881-E2621D45; Tue, 03 Feb 2015 19:49:02 +0000 X-Env-Sender: daniel.buenzli@erratique.ch X-Msg-Ref: server-7.tower-31.messagelabs.com!1422992941!11781462!1 X-Originating-IP: [74.55.86.74] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNzQuNTUuODYuNzQgPT4gMzA4NTYz\n X-StarScan-Received: X-StarScan-Version: 6.12.5; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7883 invoked from network); 3 Feb 2015 19:49:02 -0000 Received: from mail6.webfaction.com (HELO smtp.webfaction.com) (74.55.86.74) by server-7.tower-31.messagelabs.com with SMTP; 3 Feb 2015 19:49:02 -0000 Received: from [172.20.10.3] (227-224.197-178.cust.bluewin.ch [178.197.224.227]) by smtp.webfaction.com (Postfix) with ESMTP id 39F2C20D3BD1; Tue, 3 Feb 2015 19:48:58 +0000 (UTC) Date: Tue, 3 Feb 2015 20:48:54 +0100 From: =?utf-8?Q?Daniel_B=C3=BCnzli?= To: Thomas Leonard Message-ID: In-Reply-To: References: <20150202.014549.1883720051237442569.Christophe.Troestler@umons.ac.be> <20150203.165548.1818962153128895170.Christophe.Troestler@umons.ac.be> <0235E905E5DE4F3B9422F8A37DC74FEB@erratique.ch> X-Mailer: sparrow 1.6.4 (build 1178) MIME-Version: 1.0 Content-Disposition: inline Cc: "=?utf-8?Q?mirageos-devel=40lists.xenproject.org?=" Subject: Re: [MirageOS-devel] Error handling in Mirage - request for comments! X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org CgpMZSBtYXJkaSwgMyBmw6l2cmllciAyMDE1IMOgIDIwOjI1LCBUaG9tYXMgTGVvbmFyZCBhIMOp Y3JpdCA6Cgo+IFRoZSBwcm9ibGVtIGlzIHRoYXQgdGhlIHN1YmNsYXNzZXMgZ2V0IGFkZGVkIGVs c2V3aGVyZS4gZS5nLgo+ICAKPiBtaXJhZ2UtdHlwZXMncyBGUyBtYXkgZGVmaW5lIFJlYWRfb25s eSwgYnV0IGFuIGV4dDQgZmlsZXN5c3RlbSBtaWdodAo+IGRlZmluZSBlLmcuIFJlYWRfb25seV9m aWxlLCBJbW11dGFibGVfZmlsZSBhbmQgRlNfbW91bnRlZF9yZWFkX29ubHkuCj4gSWRlYWxseSwg Z2VuZXJpYyBjb2RlIGNhdGNoaW5nIElzX3JlYWRfb25seSBzaG91bGQgYWxzbyBjYXRjaCB0aGUK PiBzcGVjaWZpYyBjYXNlcy4KClRoZW4gcmF0aGVyIHRoYW4gW2BSZWFkX29ubHldIHlvdSBjb3Vs ZCBkZWZpbmUgWyBgUmVhZF9vbmx5IG9mIGVycm9yX2RldGFpbHMgXSB3aGVyZSBlcnJvcl9kZXRh aWxzIGlzIGEgdW5pdmVyc2FsIHR5cGUgWzFdLiBUaGUgRXh0NCBtb2R1bGUgd291bGQgdGhlbiBk ZWZpbmU6Cgp0eXBlIHJvX2Vycm9yID0gWyBgUmVhZF9vbmx5X2ZpbGUgfCDigKYgXQoKYW5kIGEg cHJvamVjdGlvbiBmdW5jdGlvbiBmcm9tIHRoZSB1bml2ZXJzYWwgdHlwZTogIAoKdmFsIHJvX2Vy cm9yIDogRlMuZXJyb3JfZGV0YWlsIC0+IEV4dDQucm9fZXJyb3Igb3B0aW9uCgpJbiBhbnkgY2Fz ZSBJIGRvbnQgdGhpbmsgaW5oZXJpdGVuY2UvaGlyZXJhY2h5IGlzIGdvaW5nIHNjYWxlIGFuZCBz b2x2ZSB0aGF0IHByb2JsZW0gd2VsbCBpbiBnZW5lcmFsLiBBcyB3aXRoIGFueSBraW5kIG9mIChu b24gbXVsdGlwbGUpIGhpZXJhcmNoaWNhbCBzeXN0ZW0geW91IHF1aWNrbHkgZW5kIHVwIHdhbnRp bmcgdG8gcHV0IHNvbWV0aGluZyBpbiB0d28gZGlmZmVyZW50IGJyYW5jaGVzLgoKQmVzdCwKCkRh bmllbAoKU2VlIGUuZy4gaHR0cHM6Ly9naXRodWIuY29tL3NhbW9odC9hc3NlbWJsYWdlL2Jsb2Iv bWFzdGVyL2xpYi9hc191bml2Lm1saQoKX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX18KTWlyYWdlT1MtZGV2ZWwgbWFpbGluZyBsaXN0Ck1pcmFnZU9TLWRldmVs QGxpc3RzLnhlbnByb2plY3Qub3JnCmh0dHA6Ly9saXN0cy54ZW5wcm9qZWN0Lm9yZy9jZ2ktYmlu L21haWxtYW4vbGlzdGluZm8vbWlyYWdlb3MtZGV2ZWwK From mirageos-devel-bounces@lists.xenproject.org Tue Feb 03 19:49:04 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 03 Feb 2015 19:49:04 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YIjT6-0001g7-S7; Tue, 03 Feb 2015 19:49:04 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YIjT6-0001g2-0a for mirageos-devel@lists.xenproject.org; Tue, 03 Feb 2015 19:49:04 +0000 Received: from [85.158.137.68] by server-12.bemta-3.messagelabs.com id 35/FA-02881-E2621D45; Tue, 03 Feb 2015 19:49:02 +0000 X-Env-Sender: daniel.buenzli@erratique.ch X-Msg-Ref: server-7.tower-31.messagelabs.com!1422992941!11781462!1 X-Originating-IP: [74.55.86.74] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNzQuNTUuODYuNzQgPT4gMzA4NTYz\n X-StarScan-Received: X-StarScan-Version: 6.12.5; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7883 invoked from network); 3 Feb 2015 19:49:02 -0000 Received: from mail6.webfaction.com (HELO smtp.webfaction.com) (74.55.86.74) by server-7.tower-31.messagelabs.com with SMTP; 3 Feb 2015 19:49:02 -0000 Received: from [172.20.10.3] (227-224.197-178.cust.bluewin.ch [178.197.224.227]) by smtp.webfaction.com (Postfix) with ESMTP id 39F2C20D3BD1; Tue, 3 Feb 2015 19:48:58 +0000 (UTC) Date: Tue, 3 Feb 2015 20:48:54 +0100 From: =?utf-8?Q?Daniel_B=C3=BCnzli?= To: Thomas Leonard Message-ID: In-Reply-To: References: <20150202.014549.1883720051237442569.Christophe.Troestler@umons.ac.be> <20150203.165548.1818962153128895170.Christophe.Troestler@umons.ac.be> <0235E905E5DE4F3B9422F8A37DC74FEB@erratique.ch> X-Mailer: sparrow 1.6.4 (build 1178) MIME-Version: 1.0 Content-Disposition: inline Cc: "=?utf-8?Q?mirageos-devel=40lists.xenproject.org?=" Subject: Re: [MirageOS-devel] Error handling in Mirage - request for comments! X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org CgpMZSBtYXJkaSwgMyBmw6l2cmllciAyMDE1IMOgIDIwOjI1LCBUaG9tYXMgTGVvbmFyZCBhIMOp Y3JpdCA6Cgo+IFRoZSBwcm9ibGVtIGlzIHRoYXQgdGhlIHN1YmNsYXNzZXMgZ2V0IGFkZGVkIGVs c2V3aGVyZS4gZS5nLgo+ICAKPiBtaXJhZ2UtdHlwZXMncyBGUyBtYXkgZGVmaW5lIFJlYWRfb25s eSwgYnV0IGFuIGV4dDQgZmlsZXN5c3RlbSBtaWdodAo+IGRlZmluZSBlLmcuIFJlYWRfb25seV9m aWxlLCBJbW11dGFibGVfZmlsZSBhbmQgRlNfbW91bnRlZF9yZWFkX29ubHkuCj4gSWRlYWxseSwg Z2VuZXJpYyBjb2RlIGNhdGNoaW5nIElzX3JlYWRfb25seSBzaG91bGQgYWxzbyBjYXRjaCB0aGUK PiBzcGVjaWZpYyBjYXNlcy4KClRoZW4gcmF0aGVyIHRoYW4gW2BSZWFkX29ubHldIHlvdSBjb3Vs ZCBkZWZpbmUgWyBgUmVhZF9vbmx5IG9mIGVycm9yX2RldGFpbHMgXSB3aGVyZSBlcnJvcl9kZXRh aWxzIGlzIGEgdW5pdmVyc2FsIHR5cGUgWzFdLiBUaGUgRXh0NCBtb2R1bGUgd291bGQgdGhlbiBk ZWZpbmU6Cgp0eXBlIHJvX2Vycm9yID0gWyBgUmVhZF9vbmx5X2ZpbGUgfCDigKYgXQoKYW5kIGEg cHJvamVjdGlvbiBmdW5jdGlvbiBmcm9tIHRoZSB1bml2ZXJzYWwgdHlwZTogIAoKdmFsIHJvX2Vy cm9yIDogRlMuZXJyb3JfZGV0YWlsIC0+IEV4dDQucm9fZXJyb3Igb3B0aW9uCgpJbiBhbnkgY2Fz ZSBJIGRvbnQgdGhpbmsgaW5oZXJpdGVuY2UvaGlyZXJhY2h5IGlzIGdvaW5nIHNjYWxlIGFuZCBz b2x2ZSB0aGF0IHByb2JsZW0gd2VsbCBpbiBnZW5lcmFsLiBBcyB3aXRoIGFueSBraW5kIG9mIChu b24gbXVsdGlwbGUpIGhpZXJhcmNoaWNhbCBzeXN0ZW0geW91IHF1aWNrbHkgZW5kIHVwIHdhbnRp bmcgdG8gcHV0IHNvbWV0aGluZyBpbiB0d28gZGlmZmVyZW50IGJyYW5jaGVzLgoKQmVzdCwKCkRh bmllbAoKU2VlIGUuZy4gaHR0cHM6Ly9naXRodWIuY29tL3NhbW9odC9hc3NlbWJsYWdlL2Jsb2Iv bWFzdGVyL2xpYi9hc191bml2Lm1saQoKX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX18KTWlyYWdlT1MtZGV2ZWwgbWFpbGluZyBsaXN0Ck1pcmFnZU9TLWRldmVs QGxpc3RzLnhlbnByb2plY3Qub3JnCmh0dHA6Ly9saXN0cy54ZW5wcm9qZWN0Lm9yZy9jZ2ktYmlu L21haWxtYW4vbGlzdGluZm8vbWlyYWdlb3MtZGV2ZWwK From mirageos-devel-bounces@lists.xenproject.org Tue Feb 03 21:41:53 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 03 Feb 2015 21:41:53 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YIlEB-0003VT-8R; Tue, 03 Feb 2015 21:41:47 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YIlEA-0003VO-C5 for mirageos-devel@lists.xenproject.org; Tue, 03 Feb 2015 21:41:46 +0000 Received: from [193.109.254.147] by server-15.bemta-14.messagelabs.com id F5/50-02770-99041D45; Tue, 03 Feb 2015 21:41:45 +0000 X-Env-Sender: daniel.buenzli@erratique.ch X-Msg-Ref: server-5.tower-27.messagelabs.com!1422999704!7978167!1 X-Originating-IP: [74.55.86.74] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNzQuNTUuODYuNzQgPT4gMzA4NTYz\n X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12254 invoked from network); 3 Feb 2015 21:41:44 -0000 Received: from mail6.webfaction.com (HELO smtp.webfaction.com) (74.55.86.74) by server-5.tower-27.messagelabs.com with SMTP; 3 Feb 2015 21:41:44 -0000 Received: from [172.20.10.2] (227-224.197-178.cust.bluewin.ch [178.197.224.227]) by smtp.webfaction.com (Postfix) with ESMTP id CBC3F20D493B; Tue, 3 Feb 2015 21:41:42 +0000 (UTC) Date: Tue, 3 Feb 2015 22:41:38 +0100 From: =?utf-8?Q?Daniel_B=C3=BCnzli?= To: Thomas Leonard Message-ID: In-Reply-To: References: <2126FC5196B044EC8BDA0E07CB51089F@erratique.ch> X-Mailer: sparrow 1.6.4 (build 1178) MIME-Version: 1.0 Content-Disposition: inline Cc: "=?utf-8?Q?mirageos-devel=40lists.xenproject.org?=" Subject: Re: [MirageOS-devel] Error handling in Mirage - request for comments! X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org Sorry, somehow I missed that message. > Sure, but I don't see what difference any of this cancellation stuff > makes. Layering a second error monad on top of Lwt won't un-break > cancellation. Right. There may be ways of trying to reimplement a sane cancellation API on top of the existing one though. > So, whether we continue to use Lwt.cancel or not, I don't see it as an > argument for separating error handling out of Lwt. The argument here is to explicitly know what can happen when you invoke things and hence facilitate 1) the knowledge of their existence without resorting to documentation (which is sadly never written) 2) their *correct* handling if needed. > But the real problem here is that by making exceptions fatal we turn > every exception used in existing OCaml code into a security > vulnerability. To kill my service, an attacker only needs to find some > way of triggering some code path to throw an exception. Right we can't do that. I'd suggest the strategy should be for programmers to: 1) Always handle exceptions without restoring to lwt's failed state (i.e. everything except Invalid_argument, Out_of_memory and Division_by_zero). 2) Provide an exception trap abstraction to be used at appropriate points to prevent Unikernel termination on uncaught exceptions. Here I would suggest to try to make the use of the trap *show up in the types* so that mirage signatures could enforce trap usage on implementations and thus provide clear safety checkpoints. > - If I accepted XML, they could send invalid XML (even xmlm throws). Yes. Side note, the fact that xmlm throws is a design error, I'm very ashamed of that library. See Jsonm for a better-behaved design (basically `('a, 'b) result`). > OK, but how? Do you have a concrete proposal? What would your error > monad do differently to Lwt that would make it work where Lwt doesn't? Lwt's failed state is, like exceptions, completly implicit, it doesn't show in the types what failures can happen. For hints of proposals see previous messages. I think that a lot of people standardized on the `('a, 'b) result` type for a good reason. > The Lwt error monad uses exceptions as values. It seems like you need some open type > at any rate, and in 4.01 exceptions are the only option. (a universal > type works if you give up matching) Wouldn't `('a, 'b) result` with variant composition and a one sub-level universal type (as suggested in my last message) solve the problem ? > > I'm really not fond of this. You can use open polymorphic variants for this or a closed one with a few known common cases and a custom one with a printable universal type. But then it seems you are designing with the idea of using Lwt's failed state as an error mechanism which I disagree with. > > This is possible, but there are trade-offs: > > 1. It's hard to propagate the error when you don't care (99% of the > cases I suspect). How would you rewrite the bad code you linked above > in mirage-www with this scheme? Well using `('a, 'b) result`'s monadic bind. > 2. How do you attach extra detail to the cases (a universal 'cause' > nested in each one)? Yes. Like suggested in the last message. > 3. You can't match on a printable universal type even if you know the > concrete implementation. Implementation should expose the projection function of the universal type. If it wishes your program can then precisely handle the errors of the implementations it knows by testing the universal type with the different projection functions provided by the implementations and return only return generic errors on the ones it doesn't know. Best, Daniel _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Tue Feb 03 21:41:53 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 03 Feb 2015 21:41:53 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YIlEB-0003VT-8R; Tue, 03 Feb 2015 21:41:47 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YIlEA-0003VO-C5 for mirageos-devel@lists.xenproject.org; Tue, 03 Feb 2015 21:41:46 +0000 Received: from [193.109.254.147] by server-15.bemta-14.messagelabs.com id F5/50-02770-99041D45; Tue, 03 Feb 2015 21:41:45 +0000 X-Env-Sender: daniel.buenzli@erratique.ch X-Msg-Ref: server-5.tower-27.messagelabs.com!1422999704!7978167!1 X-Originating-IP: [74.55.86.74] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNzQuNTUuODYuNzQgPT4gMzA4NTYz\n X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12254 invoked from network); 3 Feb 2015 21:41:44 -0000 Received: from mail6.webfaction.com (HELO smtp.webfaction.com) (74.55.86.74) by server-5.tower-27.messagelabs.com with SMTP; 3 Feb 2015 21:41:44 -0000 Received: from [172.20.10.2] (227-224.197-178.cust.bluewin.ch [178.197.224.227]) by smtp.webfaction.com (Postfix) with ESMTP id CBC3F20D493B; Tue, 3 Feb 2015 21:41:42 +0000 (UTC) Date: Tue, 3 Feb 2015 22:41:38 +0100 From: =?utf-8?Q?Daniel_B=C3=BCnzli?= To: Thomas Leonard Message-ID: In-Reply-To: References: <2126FC5196B044EC8BDA0E07CB51089F@erratique.ch> X-Mailer: sparrow 1.6.4 (build 1178) MIME-Version: 1.0 Content-Disposition: inline Cc: "=?utf-8?Q?mirageos-devel=40lists.xenproject.org?=" Subject: Re: [MirageOS-devel] Error handling in Mirage - request for comments! X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org Sorry, somehow I missed that message. > Sure, but I don't see what difference any of this cancellation stuff > makes. Layering a second error monad on top of Lwt won't un-break > cancellation. Right. There may be ways of trying to reimplement a sane cancellation API on top of the existing one though. > So, whether we continue to use Lwt.cancel or not, I don't see it as an > argument for separating error handling out of Lwt. The argument here is to explicitly know what can happen when you invoke things and hence facilitate 1) the knowledge of their existence without resorting to documentation (which is sadly never written) 2) their *correct* handling if needed. > But the real problem here is that by making exceptions fatal we turn > every exception used in existing OCaml code into a security > vulnerability. To kill my service, an attacker only needs to find some > way of triggering some code path to throw an exception. Right we can't do that. I'd suggest the strategy should be for programmers to: 1) Always handle exceptions without restoring to lwt's failed state (i.e. everything except Invalid_argument, Out_of_memory and Division_by_zero). 2) Provide an exception trap abstraction to be used at appropriate points to prevent Unikernel termination on uncaught exceptions. Here I would suggest to try to make the use of the trap *show up in the types* so that mirage signatures could enforce trap usage on implementations and thus provide clear safety checkpoints. > - If I accepted XML, they could send invalid XML (even xmlm throws). Yes. Side note, the fact that xmlm throws is a design error, I'm very ashamed of that library. See Jsonm for a better-behaved design (basically `('a, 'b) result`). > OK, but how? Do you have a concrete proposal? What would your error > monad do differently to Lwt that would make it work where Lwt doesn't? Lwt's failed state is, like exceptions, completly implicit, it doesn't show in the types what failures can happen. For hints of proposals see previous messages. I think that a lot of people standardized on the `('a, 'b) result` type for a good reason. > The Lwt error monad uses exceptions as values. It seems like you need some open type > at any rate, and in 4.01 exceptions are the only option. (a universal > type works if you give up matching) Wouldn't `('a, 'b) result` with variant composition and a one sub-level universal type (as suggested in my last message) solve the problem ? > > I'm really not fond of this. You can use open polymorphic variants for this or a closed one with a few known common cases and a custom one with a printable universal type. But then it seems you are designing with the idea of using Lwt's failed state as an error mechanism which I disagree with. > > This is possible, but there are trade-offs: > > 1. It's hard to propagate the error when you don't care (99% of the > cases I suspect). How would you rewrite the bad code you linked above > in mirage-www with this scheme? Well using `('a, 'b) result`'s monadic bind. > 2. How do you attach extra detail to the cases (a universal 'cause' > nested in each one)? Yes. Like suggested in the last message. > 3. You can't match on a printable universal type even if you know the > concrete implementation. Implementation should expose the projection function of the universal type. If it wishes your program can then precisely handle the errors of the implementations it knows by testing the universal type with the different projection functions provided by the implementations and return only return generic errors on the ones it doesn't know. Best, Daniel _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Tue Feb 03 21:50:19 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 03 Feb 2015 21:50:19 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YIlMQ-0003Xy-Vx; Tue, 03 Feb 2015 21:50:18 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YIlMP-0003Xt-Uj for mirageos-devel@lists.xenproject.org; Tue, 03 Feb 2015 21:50:18 +0000 Received: from [85.158.143.35] by server-2.bemta-4.messagelabs.com id A4/16-02749-99241D45; Tue, 03 Feb 2015 21:50:17 +0000 X-Env-Sender: agarwal1975@gmail.com X-Msg-Ref: server-9.tower-21.messagelabs.com!1423000215!12329257!1 X-Originating-IP: [74.125.82.46] X-SpamReason: No, hits=1.7 required=7.0 tests=BODY_RANDOM_LONG, HTML_20_30,HTML_MESSAGE,RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29511 invoked from network); 3 Feb 2015 21:50:15 -0000 Received: from mail-wg0-f46.google.com (HELO mail-wg0-f46.google.com) (74.125.82.46) by server-9.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 3 Feb 2015 21:50:15 -0000 Received: by mail-wg0-f46.google.com with SMTP id l2so47101633wgh.5 for ; Tue, 03 Feb 2015 13:50:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=xdnvySkrHckdxupoV+mSBFHzH7wRy6T3biRpnIsEU90=; b=NYw4yt3MMtbXBI7FFHa5CNyZx+gXZ9J2dK/UI2oi0ixxHl8TdrP6ERTHu2TrX05YfR hGT2mbi+VSP49WADGEKgXOq3VUONvMDWtDSCpHCCFGiZLhEdliChcyWyEiB7eG60u0ac V7Wbic1agXTR31Zc1fZLJyCtdfA1bD/xI6zMA7mN/UwHtwKr8pioesoP0Ia/RRQN+62U k0Hc84zS1qKBvfAKS23FiVeRC9M7sQFJh2giK0T7uy+1vGx+SIWgdmmXd63du2ckZSK4 8pzk1LLWzcbCrWy7KSoejUy2eL3hMlzDqkLEZwqLTX5B8tInbev4sfW8xOiVGGLqkOan Vi7A== X-Received: by 10.194.172.227 with SMTP id bf3mr8735302wjc.124.1423000215511; Tue, 03 Feb 2015 13:50:15 -0800 (PST) MIME-Version: 1.0 Received: by 10.27.15.4 with HTTP; Tue, 3 Feb 2015 13:49:55 -0800 (PST) In-Reply-To: References: <2126FC5196B044EC8BDA0E07CB51089F@erratique.ch> From: Ashish Agarwal Date: Tue, 3 Feb 2015 16:49:55 -0500 Message-ID: To: =?UTF-8?Q?Daniel_B=C3=BCnzli?= Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Error handling in Mirage - request for comments! X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0560363808637400005==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============0560363808637400005== Content-Type: multipart/alternative; boundary=089e0122f36a5c69fc050e360e65 --089e0122f36a5c69fc050e360e65 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Just in case it's not already known, please note these two operators make things very nice when you have a concurrency and error monad together. (>>=3D?) :: ('a, 'b) Result.t Lwt.t -> ('a -> ('c, 'b) Result.t Lwt.t) -> ('c, 'b) Result.t Lwt.t (>>|?) :: ('a, 'b) Result.t Lwt.t -> ('a -> 'c) -> ('c, 'b) Result.t Lwt.t Async provides both. On Tue, Feb 3, 2015 at 4:41 PM, Daniel B=C3=BCnzli wrote: > > Sorry, somehow I missed that message. > > > Sure, but I don't see what difference any of this cancellation stuff > > makes. Layering a second error monad on top of Lwt won't un-break > > cancellation. > > Right. There may be ways of trying to reimplement a sane cancellation API > on top of the existing one though. > > > So, whether we continue to use Lwt.cancel or not, I don't see it as an > > argument for separating error handling out of Lwt. > > The argument here is to explicitly know what can happen when you invoke > things and hence facilitate 1) the knowledge of their existence without > resorting to documentation (which is sadly never written) 2) their > *correct* handling if needed. > > > But the real problem here is that by making exceptions fatal we turn > > every exception used in existing OCaml code into a security > > vulnerability. To kill my service, an attacker only needs to find some > > way of triggering some code path to throw an exception. > > Right we can't do that. I'd suggest the strategy should be for programmer= s > to: > > 1) Always handle exceptions without restoring to lwt's failed state (i.e. > everything except Invalid_argument, Out_of_memory and Division_by_zero). > > 2) Provide an exception trap abstraction to be used at appropriate points > to prevent Unikernel termination on uncaught exceptions. Here I would > suggest to try to make the use of the trap *show up in the types* so that > mirage signatures could enforce trap usage on implementations and thus > provide clear safety checkpoints. > > > - If I accepted XML, they could send invalid XML (even xmlm throws). > Yes. Side note, the fact that xmlm throws is a design error, I'm very > ashamed of that library. See Jsonm for a better-behaved design (basically > `('a, 'b) result`). > > > OK, but how? Do you have a concrete proposal? What would your error > > monad do differently to Lwt that would make it work where Lwt doesn't? > > Lwt's failed state is, like exceptions, completly implicit, it doesn't > show in the types what failures can happen. For hints of proposals see > previous messages. I think that a lot of people standardized on the `('a, > 'b) result` type for a good reason. > > > The Lwt error monad uses exceptions as values. It seems like you need > some open type > > at any rate, and in 4.01 exceptions are the only option. (a universal > > type works if you give up matching) > > Wouldn't `('a, 'b) result` with variant composition and a one sub-level > universal type (as suggested in my last message) solve the problem ? > > > > > I'm really not fond of this. You can use open polymorphic variants fo= r > this or a closed one with a few known common cases and a custom one with = a > printable universal type. But then it seems you are designing with the id= ea > of using Lwt's failed state as an error mechanism which I disagree with. > > > > This is possible, but there are trade-offs: > > > > 1. It's hard to propagate the error when you don't care (99% of the > > cases I suspect). How would you rewrite the bad code you linked above > > in mirage-www with this scheme? > > Well using `('a, 'b) result`'s monadic bind. > > > 2. How do you attach extra detail to the cases (a universal 'cause' > > nested in each one)? > > Yes. Like suggested in the last message. > > > 3. You can't match on a printable universal type even if you know the > > concrete implementation. > > Implementation should expose the projection function of the universal > type. If it wishes your program can then precisely handle the errors of t= he > implementations it knows by testing the universal type with the different > projection functions provided by the implementations and return only retu= rn > generic errors on the ones it doesn't know. > > Best, > > Daniel > > > > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > --089e0122f36a5c69fc050e360e65 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Just in case it's not already known, please note these= two operators make things very nice when you have a concurrency and error = monad together.

(>>=3D?) :: ('a, 'b) Result.t Lwt.t -&= gt; ('a -> ('c, 'b) Result.t Lwt.t) -> ('c, 'b) R= esult.t Lwt.t
(>>|?) :: ('a, 'b) Result.t Lwt.t -> (= 9;a -> 'c) -> ('c, 'b) Result.t Lwt.t

Async p= rovides both.


On Tue, Feb 3, 2015 at 4:41 PM, Daniel B=C3=BCnzli <= span dir=3D"ltr"><daniel.buenzli@erratique.ch> wrote:

Sorry, somehow I missed that message.

> Sure, but I don't see what difference any of this cancellation stu= ff
> makes. Layering a second error monad on top of Lwt won't un-break<= br> > cancellation.

Right. There may be ways of trying to reimplement a sane cancellatio= n API on top of the existing one though.

> So, whether we continue to use Lwt.cancel or not, I don't see it a= s an
> argument for separating error handling out of Lwt.

The argument here is to explicitly know what can happen when you inv= oke things and hence facilitate 1) the knowledge of their existence without= resorting to documentation (which is sadly never written) 2) their *correc= t* handling if needed.

> But the real problem here is that by making exceptions fatal we turn > every exception used in existing OCaml code into a security
> vulnerability. To kill my service, an attacker only needs to find some=
> way of triggering some code path to throw an exception.

Right we can't do that. I'd suggest the strategy should be f= or programmers to:

1) Always handle exceptions without restoring to lwt's failed state (i.= e. everything except Invalid_argument, Out_of_memory and Division_by_zero).=

2) Provide an exception trap abstraction to be used at appropriate points t= o prevent Unikernel termination on uncaught exceptions. Here I would sugges= t to try to make the use of the trap *show up in the types* so that mirage = signatures could enforce trap usage on implementations and thus provide cle= ar safety checkpoints.

> - If I accepted XML, they could send invalid XML (even xmlm throws). Yes. Side note, the fact that xmlm throws is a design error, I'm= very ashamed of that library. See Jsonm for a better-behaved design (basic= ally `('a, 'b) result`).

> OK, but how? Do you have a concrete proposal? What would your error > monad do differently to Lwt that would make it work where Lwt doesn= 9;t?

Lwt's failed state is, like exceptions, completly implicit, it d= oesn't show in the types what failures can happen. For hints of proposa= ls see previous messages. I think that a lot of people standardized on the = `('a, 'b) result` type for a good reason.

> The Lwt error monad uses exceptions as values. It seems like you need = some open type
> at any rate, and in 4.01 exceptions are the only option. (a universal<= br> > type works if you give up matching)

Wouldn't `('a, 'b) result` with variant composition and = a one sub-level universal type (as suggested in my last message) solve the = problem ?


> > I'm really not fond of this. You can use open polymorphic var= iants for this or a closed one with a few known common cases and a custom o= ne with a printable universal type. But then it seems you are designing wit= h the idea of using Lwt's failed state as an error mechanism which I di= sagree with.
>
> This is possible, but there are trade-offs:
>
> 1. It's hard to propagate the error when you don't care (99% o= f the
> cases I suspect). How would you rewrite the bad code you linked above<= br> > in mirage-www with this scheme?

Well using `('a, 'b) result`'s monadic bind.

> 2. How do you attach extra detail to the cases (a universal 'cause= '
> nested in each one)?

Yes. Like suggested in the last message.

> 3. You can't match on a printable universal type even if you know = the
> concrete implementation.

Implementation should expose the projection function of the universa= l type. If it wishes your program can then precisely handle the errors of t= he implementations it knows by testing the universal type with the differen= t projection functions provided by the implementations and return only retu= rn generic errors on the ones it doesn't know.

Best,

Daniel



_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists= .xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo= /mirageos-devel

--089e0122f36a5c69fc050e360e65-- --===============0560363808637400005== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --===============0560363808637400005==-- From mirageos-devel-bounces@lists.xenproject.org Tue Feb 03 21:50:19 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 03 Feb 2015 21:50:19 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YIlMQ-0003Xy-Vx; Tue, 03 Feb 2015 21:50:18 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YIlMP-0003Xt-Uj for mirageos-devel@lists.xenproject.org; Tue, 03 Feb 2015 21:50:18 +0000 Received: from [85.158.143.35] by server-2.bemta-4.messagelabs.com id A4/16-02749-99241D45; Tue, 03 Feb 2015 21:50:17 +0000 X-Env-Sender: agarwal1975@gmail.com X-Msg-Ref: server-9.tower-21.messagelabs.com!1423000215!12329257!1 X-Originating-IP: [74.125.82.46] X-SpamReason: No, hits=1.7 required=7.0 tests=BODY_RANDOM_LONG, HTML_20_30,HTML_MESSAGE,RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29511 invoked from network); 3 Feb 2015 21:50:15 -0000 Received: from mail-wg0-f46.google.com (HELO mail-wg0-f46.google.com) (74.125.82.46) by server-9.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 3 Feb 2015 21:50:15 -0000 Received: by mail-wg0-f46.google.com with SMTP id l2so47101633wgh.5 for ; Tue, 03 Feb 2015 13:50:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=xdnvySkrHckdxupoV+mSBFHzH7wRy6T3biRpnIsEU90=; b=NYw4yt3MMtbXBI7FFHa5CNyZx+gXZ9J2dK/UI2oi0ixxHl8TdrP6ERTHu2TrX05YfR hGT2mbi+VSP49WADGEKgXOq3VUONvMDWtDSCpHCCFGiZLhEdliChcyWyEiB7eG60u0ac V7Wbic1agXTR31Zc1fZLJyCtdfA1bD/xI6zMA7mN/UwHtwKr8pioesoP0Ia/RRQN+62U k0Hc84zS1qKBvfAKS23FiVeRC9M7sQFJh2giK0T7uy+1vGx+SIWgdmmXd63du2ckZSK4 8pzk1LLWzcbCrWy7KSoejUy2eL3hMlzDqkLEZwqLTX5B8tInbev4sfW8xOiVGGLqkOan Vi7A== X-Received: by 10.194.172.227 with SMTP id bf3mr8735302wjc.124.1423000215511; Tue, 03 Feb 2015 13:50:15 -0800 (PST) MIME-Version: 1.0 Received: by 10.27.15.4 with HTTP; Tue, 3 Feb 2015 13:49:55 -0800 (PST) In-Reply-To: References: <2126FC5196B044EC8BDA0E07CB51089F@erratique.ch> From: Ashish Agarwal Date: Tue, 3 Feb 2015 16:49:55 -0500 Message-ID: To: =?UTF-8?Q?Daniel_B=C3=BCnzli?= Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Error handling in Mirage - request for comments! X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0560363808637400005==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============0560363808637400005== Content-Type: multipart/alternative; boundary=089e0122f36a5c69fc050e360e65 --089e0122f36a5c69fc050e360e65 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Just in case it's not already known, please note these two operators make things very nice when you have a concurrency and error monad together. (>>=3D?) :: ('a, 'b) Result.t Lwt.t -> ('a -> ('c, 'b) Result.t Lwt.t) -> ('c, 'b) Result.t Lwt.t (>>|?) :: ('a, 'b) Result.t Lwt.t -> ('a -> 'c) -> ('c, 'b) Result.t Lwt.t Async provides both. On Tue, Feb 3, 2015 at 4:41 PM, Daniel B=C3=BCnzli wrote: > > Sorry, somehow I missed that message. > > > Sure, but I don't see what difference any of this cancellation stuff > > makes. Layering a second error monad on top of Lwt won't un-break > > cancellation. > > Right. There may be ways of trying to reimplement a sane cancellation API > on top of the existing one though. > > > So, whether we continue to use Lwt.cancel or not, I don't see it as an > > argument for separating error handling out of Lwt. > > The argument here is to explicitly know what can happen when you invoke > things and hence facilitate 1) the knowledge of their existence without > resorting to documentation (which is sadly never written) 2) their > *correct* handling if needed. > > > But the real problem here is that by making exceptions fatal we turn > > every exception used in existing OCaml code into a security > > vulnerability. To kill my service, an attacker only needs to find some > > way of triggering some code path to throw an exception. > > Right we can't do that. I'd suggest the strategy should be for programmer= s > to: > > 1) Always handle exceptions without restoring to lwt's failed state (i.e. > everything except Invalid_argument, Out_of_memory and Division_by_zero). > > 2) Provide an exception trap abstraction to be used at appropriate points > to prevent Unikernel termination on uncaught exceptions. Here I would > suggest to try to make the use of the trap *show up in the types* so that > mirage signatures could enforce trap usage on implementations and thus > provide clear safety checkpoints. > > > - If I accepted XML, they could send invalid XML (even xmlm throws). > Yes. Side note, the fact that xmlm throws is a design error, I'm very > ashamed of that library. See Jsonm for a better-behaved design (basically > `('a, 'b) result`). > > > OK, but how? Do you have a concrete proposal? What would your error > > monad do differently to Lwt that would make it work where Lwt doesn't? > > Lwt's failed state is, like exceptions, completly implicit, it doesn't > show in the types what failures can happen. For hints of proposals see > previous messages. I think that a lot of people standardized on the `('a, > 'b) result` type for a good reason. > > > The Lwt error monad uses exceptions as values. It seems like you need > some open type > > at any rate, and in 4.01 exceptions are the only option. (a universal > > type works if you give up matching) > > Wouldn't `('a, 'b) result` with variant composition and a one sub-level > universal type (as suggested in my last message) solve the problem ? > > > > > I'm really not fond of this. You can use open polymorphic variants fo= r > this or a closed one with a few known common cases and a custom one with = a > printable universal type. But then it seems you are designing with the id= ea > of using Lwt's failed state as an error mechanism which I disagree with. > > > > This is possible, but there are trade-offs: > > > > 1. It's hard to propagate the error when you don't care (99% of the > > cases I suspect). How would you rewrite the bad code you linked above > > in mirage-www with this scheme? > > Well using `('a, 'b) result`'s monadic bind. > > > 2. How do you attach extra detail to the cases (a universal 'cause' > > nested in each one)? > > Yes. Like suggested in the last message. > > > 3. You can't match on a printable universal type even if you know the > > concrete implementation. > > Implementation should expose the projection function of the universal > type. If it wishes your program can then precisely handle the errors of t= he > implementations it knows by testing the universal type with the different > projection functions provided by the implementations and return only retu= rn > generic errors on the ones it doesn't know. > > Best, > > Daniel > > > > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > --089e0122f36a5c69fc050e360e65 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Just in case it's not already known, please note these= two operators make things very nice when you have a concurrency and error = monad together.

(>>=3D?) :: ('a, 'b) Result.t Lwt.t -&= gt; ('a -> ('c, 'b) Result.t Lwt.t) -> ('c, 'b) R= esult.t Lwt.t
(>>|?) :: ('a, 'b) Result.t Lwt.t -> (= 9;a -> 'c) -> ('c, 'b) Result.t Lwt.t

Async p= rovides both.


On Tue, Feb 3, 2015 at 4:41 PM, Daniel B=C3=BCnzli <= span dir=3D"ltr"><daniel.buenzli@erratique.ch> wrote:

Sorry, somehow I missed that message.

> Sure, but I don't see what difference any of this cancellation stu= ff
> makes. Layering a second error monad on top of Lwt won't un-break<= br> > cancellation.

Right. There may be ways of trying to reimplement a sane cancellatio= n API on top of the existing one though.

> So, whether we continue to use Lwt.cancel or not, I don't see it a= s an
> argument for separating error handling out of Lwt.

The argument here is to explicitly know what can happen when you inv= oke things and hence facilitate 1) the knowledge of their existence without= resorting to documentation (which is sadly never written) 2) their *correc= t* handling if needed.

> But the real problem here is that by making exceptions fatal we turn > every exception used in existing OCaml code into a security
> vulnerability. To kill my service, an attacker only needs to find some=
> way of triggering some code path to throw an exception.

Right we can't do that. I'd suggest the strategy should be f= or programmers to:

1) Always handle exceptions without restoring to lwt's failed state (i.= e. everything except Invalid_argument, Out_of_memory and Division_by_zero).=

2) Provide an exception trap abstraction to be used at appropriate points t= o prevent Unikernel termination on uncaught exceptions. Here I would sugges= t to try to make the use of the trap *show up in the types* so that mirage = signatures could enforce trap usage on implementations and thus provide cle= ar safety checkpoints.

> - If I accepted XML, they could send invalid XML (even xmlm throws). Yes. Side note, the fact that xmlm throws is a design error, I'm= very ashamed of that library. See Jsonm for a better-behaved design (basic= ally `('a, 'b) result`).

> OK, but how? Do you have a concrete proposal? What would your error > monad do differently to Lwt that would make it work where Lwt doesn= 9;t?

Lwt's failed state is, like exceptions, completly implicit, it d= oesn't show in the types what failures can happen. For hints of proposa= ls see previous messages. I think that a lot of people standardized on the = `('a, 'b) result` type for a good reason.

> The Lwt error monad uses exceptions as values. It seems like you need = some open type
> at any rate, and in 4.01 exceptions are the only option. (a universal<= br> > type works if you give up matching)

Wouldn't `('a, 'b) result` with variant composition and = a one sub-level universal type (as suggested in my last message) solve the = problem ?


> > I'm really not fond of this. You can use open polymorphic var= iants for this or a closed one with a few known common cases and a custom o= ne with a printable universal type. But then it seems you are designing wit= h the idea of using Lwt's failed state as an error mechanism which I di= sagree with.
>
> This is possible, but there are trade-offs:
>
> 1. It's hard to propagate the error when you don't care (99% o= f the
> cases I suspect). How would you rewrite the bad code you linked above<= br> > in mirage-www with this scheme?

Well using `('a, 'b) result`'s monadic bind.

> 2. How do you attach extra detail to the cases (a universal 'cause= '
> nested in each one)?

Yes. Like suggested in the last message.

> 3. You can't match on a printable universal type even if you know = the
> concrete implementation.

Implementation should expose the projection function of the universa= l type. If it wishes your program can then precisely handle the errors of t= he implementations it knows by testing the universal type with the differen= t projection functions provided by the implementations and return only retu= rn generic errors on the ones it doesn't know.

Best,

Daniel



_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists= .xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo= /mirageos-devel

--089e0122f36a5c69fc050e360e65-- --===============0560363808637400005== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --===============0560363808637400005==-- From mirageos-devel-bounces@lists.xenproject.org Tue Feb 03 23:16:31 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 03 Feb 2015 23:16:31 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YImhm-00031S-Tz; Tue, 03 Feb 2015 23:16:26 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YImhl-00031N-Rg for mirageos-devel@lists.xenproject.org; Tue, 03 Feb 2015 23:16:26 +0000 Received: from [193.109.254.147] by server-9.bemta-14.messagelabs.com id E6/2F-02777-8C651D45; Tue, 03 Feb 2015 23:16:24 +0000 X-Env-Sender: Christophe.TROESTLER@umons.ac.be X-Msg-Ref: server-7.tower-27.messagelabs.com!1423005383!12598049!1 X-Originating-IP: [157.55.234.55] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15334 invoked from network); 3 Feb 2015 23:16:23 -0000 Received: from mail-db3on0055.outbound.protection.outlook.com (HELO emea01-db3-obe.outbound.protection.outlook.com) (157.55.234.55) by server-7.tower-27.messagelabs.com with AES256-SHA encrypted SMTP; 3 Feb 2015 23:16:23 -0000 Received: from AMSPR05CA0021.eurprd05.prod.outlook.com (10.242.77.149) by AMSPR05MB518.eurprd05.prod.outlook.com (10.242.224.156) with Microsoft SMTP Server (TLS) id 15.1.75.20; Tue, 3 Feb 2015 23:16:23 +0000 Received: from AM1FFO11FD053.protection.gbl (2a01:111:f400:7e00::188) by AMSPR05CA0021.outlook.office365.com (2a01:111:e400:8000::21) with Microsoft SMTP Server (TLS) id 15.1.75.20 via Frontend Transport; Tue, 3 Feb 2015 23:16:22 +0000 Received: from smtp.umons.ac.be (193.190.208.132) by AM1FFO11FD053.mail.protection.outlook.com (10.174.65.72) with Microsoft SMTP Server (TLS) id 15.1.75.11 via Frontend Transport; Tue, 3 Feb 2015 23:16:22 +0000 Received: from poincare (10.104.2.63) by smtp.umons.ac.be (10.104.2.84) with Microsoft SMTP Server (TLS) id 14.3.224.2; Wed, 4 Feb 2015 00:16:15 +0100 Received: from localhost ([::1]) by poincare with esmtp (Exim 4.84) (envelope-from ) id 1YImha-0000Gc-Dc; Wed, 04 Feb 2015 00:16:14 +0100 Date: Wed, 4 Feb 2015 00:16:14 +0100 Message-ID: <20150204.001614.26478837567139584.Christophe.Troestler@umons.ac.be> To: From: Christophe Troestler In-Reply-To: References: <20150202.014549.1883720051237442569.Christophe.Troestler@umons.ac.be> X-Face: #2fb%mPx>rRL@4ff~TVgZ"<[:,oL"`TUEGK/[8/qb58~C>jR(x4A+v/n)7BgpEtIph_neoLKJBq0JBY9:}8v|j Organization: Universite de Mons (http://math.umons.ac.be/anum/) X-Mailer: Mew version 6.6 on Emacs 24.4 / Mule 6.0 (HANACHIRUSATO) MIME-Version: 1.0 Content-Length: 7490 X-Originating-IP: [10.104.2.63] X-EOPAttributedMessage: 0 X-Matching-Connectors: 130674789827964580; (9b551343-d075-4328-d154-08d0574c44b8,aa519c6d-c5b7-417d-4ec3-08d1170c20a9); (9b551343-d075-4328-d154-08d0574c44b8,aa519c6d-c5b7-417d-4ec3-08d1170c20a9) Received-SPF: Pass (protection.outlook.com: domain of umons.ac.be designates 193.190.208.132 as permitted sender) receiver=protection.outlook.com; client-ip=193.190.208.132; helo=smtp.umons.ac.be; X-Forefront-Antispam-Report: CIP:193.190.208.132; CTRY:BE; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(10009020)(6009001)(438002)(24454002)(51704005)(52604005)(103116003)(86362001)(57986006)(87936001)(76506005)(6806004)(46102003)(62966003)(77156002)(2950100001)(36756003)(74482002)(110136001)(19580395003)(19580405001)(106466001)(50226001)(2351001)(50466002)(76176999)(226693001)(47776003)(16796002)(92566002)(23676002)(50986999); DIR:OUT; SFP:1101; SCL:1; SRVR:AMSPR05MB518; H:smtp.umons.ac.be; FPR:; SPF:Pass; MLV:sfv; LANG:en; X-Microsoft-Antispam: UriScan:; X-Microsoft-Antispam: BCL:0;PCL:0;RULEID:;SRVR:AMSPR05MB518; X-Exchange-Antispam-Report-Test: UriScan:; X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(601004); SRVR:AMSPR05MB518; X-Forefront-PRVS: 0476D4AB88 X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(401004)(400005); SRVR:AMSPR05MB518; X-MS-Exchange-CrossTenant-OriginalArrivalTime: 03 Feb 2015 23:16:22.5156 (UTC) X-MS-Exchange-CrossTenant-Id: 5afe0b00-7697-4969-b663-5eab37d5f47e X-MS-Exchange-CrossTenant-OriginalAttributedTenantConnectingIp: TenantId=5afe0b00-7697-4969-b663-5eab37d5f47e; Ip=[193.190.208.132] X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem X-MS-Exchange-Transport-CrossTenantHeadersStamped: AMSPR05MB518 Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Error handling in Mirage - request for comments! X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org T24gTW9uLCAyIEZlYiAyMDE1IDEyOjMwOjM5ICswMDAwLCBUaG9tYXMgTGVvbmFyZCB3cm90ZToK PiAKPiBPbiAyIEZlYnJ1YXJ5IDIwMTUgYXQgMDA6NDUsIENocmlzdG9waGUgVHJvZXN0bGVyCj4g PENocmlzdG9waGUuVHJvZXN0bGVyQHVtb25zLmFjLmJlPiB3cm90ZToKPiA+IE9uIFNhdCwgMzEg SmFuIDIwMTUgMjE6MDc6MjIgKzAwMDAsIFRob21hcyBMZW9uYXJkIHdyb3RlOgo+ID4+Cj4gPj4g W+KApl0gQnV0IHRoZSByZWFsIHByb2JsZW0gaGVyZSBpcyB0aGF0IGJ5IG1ha2luZyBleGNlcHRp b25zIGZhdGFsIHdlCj4gPj4gdHVybiBldmVyeSBleGNlcHRpb24gdXNlZCBpbiBleGlzdGluZyBP Q2FtbCBjb2RlIGludG8gYSBzZWN1cml0eQo+ID4+IHZ1bG5lcmFiaWxpdHkuIFvigKZdCj4gPgo+ ID4gU2luY2UgT0NhbWwgc3VwcG9ydHMgZXhjZXB0aW9ucywgSSB0aGluayB0aGVyZSBpcyBubyBk b3VidCB0aGF0IHdlCj4gPiBtdXN0IGhhbmRsZSB0aGVtIGVmZmVjdGl2ZWx5IOKAlCBub3QganVz dCB3aXBlIHRoZW0gdW5kZXIgdGhlIGNhcnBldCBhbmQKPiA+IGxldCB0aGVtIGFib3J0IHRoZSBw cm9ncmFtL3VuaWtlcm5lbC4gIElkZWFsbHkgTHd0IHNob3VsZCBkZWFsCj4gPiBzZW5zaWJseSB3 aXRoIGV4Y2VwdGlvbnMgKGFuZCB0aGUgZGlzY3Vzc2lvbiBzZWVtcyB0byBpbXBseSB0aGVyZSBh cmUKPiA+IGFyZWFzIG9mIGltcHJvdmVtZW50IOKAlCBidXQgaXQgaXMgdW5jbGVhciB0byBtZSBo b3cgeW91IGNhbiBkbyB0aGF0Cj4gPiBlZmZpY2llbnRseSB3aXRob3V0IHVzaW5nIGEgdHJ5IGJs b2NrIGluIGFsbCBiaW5kcykuCj4gCj4gTHd0IGFscmVhZHkgcHV0cyBhIHRyeSBibG9jayBpbiBh bGwgKHNsZWVwaW5nKSBiaW5kcywgc28gdGhpcyBpcwo+IGhhbmRsZWQgZm9yIHlvdToKPiAKPiBs ZXQgYmluZCB0IGYgPQo+ICAgbGV0IHQgPSByZXByIHQgaW4KPiAgIG1hdGNoIHQuc3RhdGUgd2l0 aAo+ICAgICB8IFJldHVybiB2IC0+Cj4gICAgICAgICBmIHYKPiAgICAgfCBGYWlsIF8gYXMgc3Rh dGUgLT4KPiAgICAgICAgIHRocmVhZCB7IHN0YXRlIH0KPiAgICAgfCBTbGVlcCBzbGVlcGVyIC0+ Cj4gICAgICAgICBsZXQgcmVzID0gdGVtcCB0IGluCj4gICAgICAgICBsZXQgZGF0YSA9ICFjdXJy ZW50X2RhdGEgaW4KPiAgICAgICAgIGFkZF9pbW11dGFibGVfd2FpdGVyIHNsZWVwZXIKPiAgICAg ICAgICAgKGZ1bmN0aW9uCj4gICAgICAgICAgICAgIHwgUmV0dXJuIHYgLT4gY3VycmVudF9kYXRh IDo9IGRhdGE7IGNvbm5lY3QgcmVzICh0cnkgZiB2Cj4gd2l0aCBleG4gLT4gZmFpbCBleG4pCj4g ICAgICAgICAgICAgIHwgRmFpbCBfIGFzIHN0YXRlIC0+IGZhc3RfY29ubmVjdCByZXMgc3RhdGUK PiAgICAgICAgICAgICAgfCBfIC0+IGFzc2VydCBmYWxzZSk7Cj4gICAgICAgICByZXMKClRoYW5r cyBmb3IgY2hlY2tpbmcuICBBdCBmaXJzdCwgdGhlIGRpZmZlcmVuY2Ugb2YgdHJlYXRtZW50IGJl dHdlZW4KdGhlIHR3byDigJxmIHbigJ0gaXMgYSBsaXR0bGUgb2RkLiAgRG8geW91IGhhcHBlbiB0 byBrbm93IHRoZSByZWFzb24gZm9yCml0PwoKPiA+IFRoZXJlIGFyZSBob3dldmVyIGVycm9ycyB0 aGF0IHlvdSB3YW50IHRvIG1hbmRhdGUgdGhhdCB0aGV5IGFyZSBkZWFsdAo+ID4gd2l0aCBidXQg bm90IG5lY2Vzc2FyaWx5IGF0IHRoZSBjYWxsaW5nIHBvaW50LiAgQSB0eXBpY2FsIGV4YW1wbGUg dG8KPiA+IG1lIGlzIOKAnHJlYWTigJ0gYmVjYXVzZSBpdCBpcyBvZnRlbiBtdWNoICJoaWdoZXIi IGluIHRoZSBwcm9ncmFtIHRoYXQgYW4KPiA+IGFwcHJvcHJpYXRlIHJlc3BvbnNlIHRvIGEgZmFp bGluZyByZWFkIGNhbiBiZSBtYWRlIOKAlCB0aGlzIGlzIGltcG9ydGFudAo+ID4gZm9yIGxpYnJh cmllcyB0aGF0IHdpbGwgcG9zdC1wcm9jZXNzIOKAnHJlYWTigJ1zIGFuZCB3aWxsIGhhdmUgbm8g aWRlYQo+ID4gd2hhdCB0byBkbyBpZiDigJxyZWFk4oCdIGZhaWxzLgo+IAo+IFllcywgdGhpcyBp cyBhIGNhc2Ugd2hlcmUgeW91IG1pZ2h0IHdhbnQgYW4gT3JfZXJyb3IudCB0aHJlYWRlZAo+IHRo cm91Z2ggZXZlcnl0aGluZy4gT3IsIGl0IG1pZ2h0IGJlIGVhc2llciB0byB3cmFwIHRoZSB3aG9s ZSB0aGluZwo+IHNvIHRoYXQgYW55IGVycm9yIGNvZGUgcmV0dXJuZWQgYnkgdGhlIHJlYWQgaXMg dGhyb3duIGFuZCB0aGVuCj4gY2F1Z2h0IGFnYWluLgoKVGhlIHByb2JsZW0gd2l0aCBPcl9lcnJv ci50IGlzIHRoYXQgeW91IGhhdmUgdG8gd3JpdGUgdGVkaW91cyBjb2RlIHRvCnByb3BhZ2F0ZSBp dCBhdCBldmVyeSBiaW5kLiAgSWYgd2UgYWRvcHQgdGhpcywgYW4gYmluZCBpbmZpeCBvcGVyYXRv cgp0aGF0IHByb3BhZ2F0ZXMgdGhlIGVycm9yIGF1dG9tYXRpY2FsbHkgaXMgcmVhbGx5IG5lZWRl ZCAodHJ5aW5nIHRvCmNhdGNoIHdpdGggdG9kYXkncyBtZXNzYWdlcywgSSBzZWUgdGhhdCA+Pj0/ IGlzIGFscmVhZHkgdXNlZCBmb3IgdGhhdApwdXJwb3NlKS4gIEFsc28sIHdpdGggT3JfZXJyb3Iu dCAob3IgZXhjZXB0aW9ucyksIHRoZXJlIGlzIG5vIHdheSB0bwplbnN1cmUgdGhhdCB0aGUgZXJy b3IgaXMgZXZlbnR1YWxseSBhY3RlZCB1cG9uIHNvIHdoeSBub3QgdG8gc2ltcGx5CnVzZSDigJxm YWls4oCdPwoKPiBUaGUgcHJvYmxlbSB3ZSBoYXZlIGluIE1pcmFnZSBpcyB0aGF0IG91ciB0eXBl cyBhcmUgYWJzdHJhY3QuIEZvcgo+IGV4YW1wbGUsIGlmIHlvdSBoYXZlIGEgZnVuY3Rvcgo+IAo+ ICAgbW9kdWxlIEZTIChCIDogQkxPQ0spICA9IC4uLgo+IAo+IHRoZW4gdGhlIGF1dGhvciBvZiB0 aGUgRlMgZnVuY3RvciBkb2Vzbid0IGtub3cgZXhhY3RseSB3aGF0IGVycm9ycyB0aGUKPiBjb25j cmV0ZSBCIG1pZ2h0IHRocm93LiBGb3IgZXhhbXBsZSwgaWYgQiBpcyBhIHJlbW90ZSBkaXNrIHRo ZW4gaXQKPiBtaWdodCB0aHJvdyBuZXR3b3JrIGVycm9ycy4gU28gZW5zdXJpbmcgdGhhdCBjYWxs ZXJzIGVudW1lcmF0ZSBhbGwKPiBlcnJvcnMgaXNuJ3QgdmVyeSBoZWxwZnVsIGluIHRoaXMgY2Fz ZS4KPiAKPiBZb3UgY2FuIGdpdmUgRlMgYW4gZXJyb3IgY29kZSBvZiBbYEJsb2NrX2Vycm9yIG9m IEIuZXJyb3JdIGFuZCBqdXN0Cj4gcHJvcGFnYXRlIGl0IHRvIHRoZSBjYWxsZXIsIHdoaWNoIGlz IHdoYXQgd2UgZG8gbm93LiBUaGF0IHNlZW1zIHF1aXRlCj4gY2xldmVyLCBidXQgSSdtIHN0cnVn Z2xpbmcgdG8gaW1hZ2luZSBhIGNhc2Ugd2hlcmUgaXQncyBhY3R1YWxseQo+IHVzZWZ1bC4KClRo YXQncyB3aGF0IEkgd2FzIGdvaW5nIHRvIHN1Z2dlc3QuLi4gIERlY2xhcmluZyBzZXZlcmFsIGBC bG9ja19lcnJvcgppZiBuZWNlc3NhcnkgYWxsb3dzIHRvIGFjdCBvbiAiY2xhc3NlcyIgb2YgZXJy b3JzIOKAlCB3aGljaCBpcyBhbGwgb25lCmNhbiBob3BlIGZvciBnaXZlbiB0aGUgYWJzdHJhY3Rp b24uCgo+IEl0J3MgcHJvYmFibHkgd29ydGggY29tcGlsaW5nIGEgbGlzdCBvZiBleGFtcGxlcyB3 aGVyZSBNaXJhZ2UgY29kZQo+IGN1cnJlbnRseSBtYXRjaGVzIG9uIHNwZWNpZmljIHJldHVybmVk IEVycm9yIGNvZGVzIGFuZCB0YWtlcyBzcGVjaWZpYwo+IGFjdGlvbnMuIE15IGd1ZXNzIGlzIHRo ZXJlIGFyZW4ndCBlbm91Z2ggdG8ganVzdGlmeSB0aGUgY29tcGxleGl0eQo+IHRob3VnaC4KClRo YXQgd291bGQgYmUgbmljZS4gIEkgZG9uJ3QgaGF2ZSBtdWNoIGZhbWlsaWFyaXR5IHdpdGggYSBs b3Qgb2YgcGFydHMKb2YgTWlyYWdlIHNvIEkgbWF5IGJlIG1pc3NpbmcgdXNlIGNhc2VzLiAgQXMg SSB1bmRlcnN0YW5kIHRoZQpkaXNjdXNzaW9uLCBNaXJhZ2UgY29kZSBzaG91bGQgYmUgcmV2aXNp dGVkLCBub3Qgb25seSB0byBzZWUgaG93CnRoaW5ncyBhcmUgZG9uZSBub3cgYnV0IGFsc28gd2hh dCB0aGUgcHJvYmxlbXMgYXJlICh3aXRoIHRoZSBjdXJyZW50CnNjaGVtZSkgYW5kIHdoYXQgcHJv cGVydGllcyBvZiB0aGUgZXJyb3IgaGFuZGxpbmcgd2Ugd291bGQgbGlrZSBpbgp0aGVzZSBjYXNl cy4KCj4gWy4uLl0gaW4gZXZlcnkgb25lIG9mIHRoZXNlIGNhc2VzIHdoZXJlIHdlIG1hdGNoIG9u IGFuIGBFcnJvciwgd2UganVzdAo+IHByb3BhZ2F0ZSBpdCAoaS5lLiB0aGUgZGVmYXVsdCBiZWhh dmlvdXIgb2YgYW4gZXhjZXB0aW9uIHdvdWxkIGhhdmUKPiBiZWVuIGNvcnJlY3QpLgo+IAo+IEhl cmUgYXJlIHNvbWUgZXhhbXBsZXM6Cj4gCj4gfCBgRXJyb3IgKGBJbnZhbGlkX2NvbnNvbGUgeCkg LT4gZmFpbCAoRmFpbHVyZSAoUHJpbnRmLnNwcmludGYgIkludmFsaWRfY29uc29sZSAlcyIgeCkp Cj4gfCBgRXJyb3IgKGBCbG9ja19kZXZpY2UgZSkgLT4gZmFpbCAoRmFpbHVyZSAoRnMuc3RyaW5n X29mX2Jsb2NrX2Vycm9yIGUpKQo+IHwgYEVycm9yIChLVi5Vbmtub3duX2tleSBrZXkpIC0+IGZh aWwgKEludmFsaWRfYXJndW1lbnQga2V5KQo+IHwgYEVycm9yIChgVW5rbm93biBtc2cpIC0+IEx3 dC5mYWlsIChGYWlsdXJlIG1zZykKCkkgZG9uJ3QgdW5kZXJzdGFuZCB0aGUgcG9pbnQgb2YgdGhp cyB0eXBlIG9mIGNvZGUuICBXaHkgd2Fzbid0IOKAnEVycm9y4oCdCmRlY2xhcmVkIGFzIGFuIGV4 Y2VwdGlvbiAocG9zc2libHkgd2l0aCBhbiBleGNlcHRpb24gcHJpbnRlcikgYW5kCuKAnGZhaWzi gJ0gZGlyZWN0bHkgaW52b2tlZCBvbiBpdD8gIFRoaXMgYWxzbyBoaWdobGlnaHRzIHRoYXQgcGVv cGxlIHNoeQphd2F5IGZyb20gaGF2aW5nIHRvIGhhbmRsZSBldmVuIGEgc2ltcGxlIGBFcnJvciB0 byB0aGUgcG9pbnQgdGhhdCBpdApzZWVtcyBwcmVmZXJhYmxlIHRvIGRlZ2VuZXJhdGUgaXQgYXMg YSBzdHJpbmchCgo+IFRoZSBvbmx5IGNhc2Ugd2hlcmUgd2UgZG8gc29tZXRoaW5nIGludGVyZXN0 aW5nIGlzIGBFcnJvciAoVW5rbm93bl9rZXkKPiBfKSwgd2hlcmUgd2Ugbm90ZSB0aGF0IGl0IHdh cyBhIHJlYWQ6Cj4gCj4gfCBgRXJyb3IgKFRNUEwuVW5rbm93bl9rZXkgXykgLT4gZmFpbCAoRmFp bHVyZSAoInJlYWQgIiBeIG5hbWUpKQo+IAo+IEhvd2V2ZXIsIFVua25vd25fa2V5IHdvdWxkbid0 IGJlIGFuIGV4Y2VwdGlvbiB1bmRlciBhbnkgcHJvcG9zZWQgc2NoZW1lIGFueXdheQoKSW4gdGhl IHByZXZpb3VzIGRpc2N1c3Npb24sIEkgaGFkIHRoZSBpbXByZXNzaW9uIHRoYXQgaGF2aW5nIGEg c2NoZW1lCnRvIHByb3BhZ2F0ZSBlcnJvcnMgc2VhbWxlc3NseSB3aGlsZSBmb3JjaW5nIGNlcnRh aW4gKGNsYXNzZXMgb2YpCmVycm9ycyB0byBiZSBoYW5kbGVkIGJlZm9yZSB0aGV5IHJlYWNoIHRo ZSBtYWluIGxvb3Agd2FzIGltcG9ydGFudC4KSWYgd2UgZG8gbm90IGNhcmUgYWJvdXQgdGhpcywg d2hhdCBpcyB3cm9uZyB3aXRoIHRoZSDigJxmYWls4oCdIG1lY2hhbmlzbQpvZiBMd3Q/CgpCZXN0 LApDLgoKX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KTWly YWdlT1MtZGV2ZWwgbWFpbGluZyBsaXN0Ck1pcmFnZU9TLWRldmVsQGxpc3RzLnhlbnByb2plY3Qu b3JnCmh0dHA6Ly9saXN0cy54ZW5wcm9qZWN0Lm9yZy9jZ2ktYmluL21haWxtYW4vbGlzdGluZm8v bWlyYWdlb3MtZGV2ZWwK From mirageos-devel-bounces@lists.xenproject.org Tue Feb 03 23:16:31 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 03 Feb 2015 23:16:31 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YImhm-00031S-Tz; Tue, 03 Feb 2015 23:16:26 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YImhl-00031N-Rg for mirageos-devel@lists.xenproject.org; Tue, 03 Feb 2015 23:16:26 +0000 Received: from [193.109.254.147] by server-9.bemta-14.messagelabs.com id E6/2F-02777-8C651D45; Tue, 03 Feb 2015 23:16:24 +0000 X-Env-Sender: Christophe.TROESTLER@umons.ac.be X-Msg-Ref: server-7.tower-27.messagelabs.com!1423005383!12598049!1 X-Originating-IP: [157.55.234.55] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15334 invoked from network); 3 Feb 2015 23:16:23 -0000 Received: from mail-db3on0055.outbound.protection.outlook.com (HELO emea01-db3-obe.outbound.protection.outlook.com) (157.55.234.55) by server-7.tower-27.messagelabs.com with AES256-SHA encrypted SMTP; 3 Feb 2015 23:16:23 -0000 Received: from AMSPR05CA0021.eurprd05.prod.outlook.com (10.242.77.149) by AMSPR05MB518.eurprd05.prod.outlook.com (10.242.224.156) with Microsoft SMTP Server (TLS) id 15.1.75.20; Tue, 3 Feb 2015 23:16:23 +0000 Received: from AM1FFO11FD053.protection.gbl (2a01:111:f400:7e00::188) by AMSPR05CA0021.outlook.office365.com (2a01:111:e400:8000::21) with Microsoft SMTP Server (TLS) id 15.1.75.20 via Frontend Transport; Tue, 3 Feb 2015 23:16:22 +0000 Received: from smtp.umons.ac.be (193.190.208.132) by AM1FFO11FD053.mail.protection.outlook.com (10.174.65.72) with Microsoft SMTP Server (TLS) id 15.1.75.11 via Frontend Transport; Tue, 3 Feb 2015 23:16:22 +0000 Received: from poincare (10.104.2.63) by smtp.umons.ac.be (10.104.2.84) with Microsoft SMTP Server (TLS) id 14.3.224.2; Wed, 4 Feb 2015 00:16:15 +0100 Received: from localhost ([::1]) by poincare with esmtp (Exim 4.84) (envelope-from ) id 1YImha-0000Gc-Dc; Wed, 04 Feb 2015 00:16:14 +0100 Date: Wed, 4 Feb 2015 00:16:14 +0100 Message-ID: <20150204.001614.26478837567139584.Christophe.Troestler@umons.ac.be> To: From: Christophe Troestler In-Reply-To: References: <20150202.014549.1883720051237442569.Christophe.Troestler@umons.ac.be> X-Face: #2fb%mPx>rRL@4ff~TVgZ"<[:,oL"`TUEGK/[8/qb58~C>jR(x4A+v/n)7BgpEtIph_neoLKJBq0JBY9:}8v|j Organization: Universite de Mons (http://math.umons.ac.be/anum/) X-Mailer: Mew version 6.6 on Emacs 24.4 / Mule 6.0 (HANACHIRUSATO) MIME-Version: 1.0 Content-Length: 7490 X-Originating-IP: [10.104.2.63] X-EOPAttributedMessage: 0 X-Matching-Connectors: 130674789827964580; (9b551343-d075-4328-d154-08d0574c44b8,aa519c6d-c5b7-417d-4ec3-08d1170c20a9); (9b551343-d075-4328-d154-08d0574c44b8,aa519c6d-c5b7-417d-4ec3-08d1170c20a9) Received-SPF: Pass (protection.outlook.com: domain of umons.ac.be designates 193.190.208.132 as permitted sender) receiver=protection.outlook.com; client-ip=193.190.208.132; helo=smtp.umons.ac.be; X-Forefront-Antispam-Report: CIP:193.190.208.132; CTRY:BE; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(10009020)(6009001)(438002)(24454002)(51704005)(52604005)(103116003)(86362001)(57986006)(87936001)(76506005)(6806004)(46102003)(62966003)(77156002)(2950100001)(36756003)(74482002)(110136001)(19580395003)(19580405001)(106466001)(50226001)(2351001)(50466002)(76176999)(226693001)(47776003)(16796002)(92566002)(23676002)(50986999); DIR:OUT; SFP:1101; SCL:1; SRVR:AMSPR05MB518; H:smtp.umons.ac.be; FPR:; SPF:Pass; MLV:sfv; LANG:en; X-Microsoft-Antispam: UriScan:; X-Microsoft-Antispam: BCL:0;PCL:0;RULEID:;SRVR:AMSPR05MB518; X-Exchange-Antispam-Report-Test: UriScan:; X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(601004); SRVR:AMSPR05MB518; X-Forefront-PRVS: 0476D4AB88 X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(401004)(400005); SRVR:AMSPR05MB518; X-MS-Exchange-CrossTenant-OriginalArrivalTime: 03 Feb 2015 23:16:22.5156 (UTC) X-MS-Exchange-CrossTenant-Id: 5afe0b00-7697-4969-b663-5eab37d5f47e X-MS-Exchange-CrossTenant-OriginalAttributedTenantConnectingIp: TenantId=5afe0b00-7697-4969-b663-5eab37d5f47e; Ip=[193.190.208.132] X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem X-MS-Exchange-Transport-CrossTenantHeadersStamped: AMSPR05MB518 Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Error handling in Mirage - request for comments! X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org T24gTW9uLCAyIEZlYiAyMDE1IDEyOjMwOjM5ICswMDAwLCBUaG9tYXMgTGVvbmFyZCB3cm90ZToK PiAKPiBPbiAyIEZlYnJ1YXJ5IDIwMTUgYXQgMDA6NDUsIENocmlzdG9waGUgVHJvZXN0bGVyCj4g PENocmlzdG9waGUuVHJvZXN0bGVyQHVtb25zLmFjLmJlPiB3cm90ZToKPiA+IE9uIFNhdCwgMzEg SmFuIDIwMTUgMjE6MDc6MjIgKzAwMDAsIFRob21hcyBMZW9uYXJkIHdyb3RlOgo+ID4+Cj4gPj4g W+KApl0gQnV0IHRoZSByZWFsIHByb2JsZW0gaGVyZSBpcyB0aGF0IGJ5IG1ha2luZyBleGNlcHRp b25zIGZhdGFsIHdlCj4gPj4gdHVybiBldmVyeSBleGNlcHRpb24gdXNlZCBpbiBleGlzdGluZyBP Q2FtbCBjb2RlIGludG8gYSBzZWN1cml0eQo+ID4+IHZ1bG5lcmFiaWxpdHkuIFvigKZdCj4gPgo+ ID4gU2luY2UgT0NhbWwgc3VwcG9ydHMgZXhjZXB0aW9ucywgSSB0aGluayB0aGVyZSBpcyBubyBk b3VidCB0aGF0IHdlCj4gPiBtdXN0IGhhbmRsZSB0aGVtIGVmZmVjdGl2ZWx5IOKAlCBub3QganVz dCB3aXBlIHRoZW0gdW5kZXIgdGhlIGNhcnBldCBhbmQKPiA+IGxldCB0aGVtIGFib3J0IHRoZSBw cm9ncmFtL3VuaWtlcm5lbC4gIElkZWFsbHkgTHd0IHNob3VsZCBkZWFsCj4gPiBzZW5zaWJseSB3 aXRoIGV4Y2VwdGlvbnMgKGFuZCB0aGUgZGlzY3Vzc2lvbiBzZWVtcyB0byBpbXBseSB0aGVyZSBh cmUKPiA+IGFyZWFzIG9mIGltcHJvdmVtZW50IOKAlCBidXQgaXQgaXMgdW5jbGVhciB0byBtZSBo b3cgeW91IGNhbiBkbyB0aGF0Cj4gPiBlZmZpY2llbnRseSB3aXRob3V0IHVzaW5nIGEgdHJ5IGJs b2NrIGluIGFsbCBiaW5kcykuCj4gCj4gTHd0IGFscmVhZHkgcHV0cyBhIHRyeSBibG9jayBpbiBh bGwgKHNsZWVwaW5nKSBiaW5kcywgc28gdGhpcyBpcwo+IGhhbmRsZWQgZm9yIHlvdToKPiAKPiBs ZXQgYmluZCB0IGYgPQo+ICAgbGV0IHQgPSByZXByIHQgaW4KPiAgIG1hdGNoIHQuc3RhdGUgd2l0 aAo+ICAgICB8IFJldHVybiB2IC0+Cj4gICAgICAgICBmIHYKPiAgICAgfCBGYWlsIF8gYXMgc3Rh dGUgLT4KPiAgICAgICAgIHRocmVhZCB7IHN0YXRlIH0KPiAgICAgfCBTbGVlcCBzbGVlcGVyIC0+ Cj4gICAgICAgICBsZXQgcmVzID0gdGVtcCB0IGluCj4gICAgICAgICBsZXQgZGF0YSA9ICFjdXJy ZW50X2RhdGEgaW4KPiAgICAgICAgIGFkZF9pbW11dGFibGVfd2FpdGVyIHNsZWVwZXIKPiAgICAg ICAgICAgKGZ1bmN0aW9uCj4gICAgICAgICAgICAgIHwgUmV0dXJuIHYgLT4gY3VycmVudF9kYXRh IDo9IGRhdGE7IGNvbm5lY3QgcmVzICh0cnkgZiB2Cj4gd2l0aCBleG4gLT4gZmFpbCBleG4pCj4g ICAgICAgICAgICAgIHwgRmFpbCBfIGFzIHN0YXRlIC0+IGZhc3RfY29ubmVjdCByZXMgc3RhdGUK PiAgICAgICAgICAgICAgfCBfIC0+IGFzc2VydCBmYWxzZSk7Cj4gICAgICAgICByZXMKClRoYW5r cyBmb3IgY2hlY2tpbmcuICBBdCBmaXJzdCwgdGhlIGRpZmZlcmVuY2Ugb2YgdHJlYXRtZW50IGJl dHdlZW4KdGhlIHR3byDigJxmIHbigJ0gaXMgYSBsaXR0bGUgb2RkLiAgRG8geW91IGhhcHBlbiB0 byBrbm93IHRoZSByZWFzb24gZm9yCml0PwoKPiA+IFRoZXJlIGFyZSBob3dldmVyIGVycm9ycyB0 aGF0IHlvdSB3YW50IHRvIG1hbmRhdGUgdGhhdCB0aGV5IGFyZSBkZWFsdAo+ID4gd2l0aCBidXQg bm90IG5lY2Vzc2FyaWx5IGF0IHRoZSBjYWxsaW5nIHBvaW50LiAgQSB0eXBpY2FsIGV4YW1wbGUg dG8KPiA+IG1lIGlzIOKAnHJlYWTigJ0gYmVjYXVzZSBpdCBpcyBvZnRlbiBtdWNoICJoaWdoZXIi IGluIHRoZSBwcm9ncmFtIHRoYXQgYW4KPiA+IGFwcHJvcHJpYXRlIHJlc3BvbnNlIHRvIGEgZmFp bGluZyByZWFkIGNhbiBiZSBtYWRlIOKAlCB0aGlzIGlzIGltcG9ydGFudAo+ID4gZm9yIGxpYnJh cmllcyB0aGF0IHdpbGwgcG9zdC1wcm9jZXNzIOKAnHJlYWTigJ1zIGFuZCB3aWxsIGhhdmUgbm8g aWRlYQo+ID4gd2hhdCB0byBkbyBpZiDigJxyZWFk4oCdIGZhaWxzLgo+IAo+IFllcywgdGhpcyBp cyBhIGNhc2Ugd2hlcmUgeW91IG1pZ2h0IHdhbnQgYW4gT3JfZXJyb3IudCB0aHJlYWRlZAo+IHRo cm91Z2ggZXZlcnl0aGluZy4gT3IsIGl0IG1pZ2h0IGJlIGVhc2llciB0byB3cmFwIHRoZSB3aG9s ZSB0aGluZwo+IHNvIHRoYXQgYW55IGVycm9yIGNvZGUgcmV0dXJuZWQgYnkgdGhlIHJlYWQgaXMg dGhyb3duIGFuZCB0aGVuCj4gY2F1Z2h0IGFnYWluLgoKVGhlIHByb2JsZW0gd2l0aCBPcl9lcnJv ci50IGlzIHRoYXQgeW91IGhhdmUgdG8gd3JpdGUgdGVkaW91cyBjb2RlIHRvCnByb3BhZ2F0ZSBp dCBhdCBldmVyeSBiaW5kLiAgSWYgd2UgYWRvcHQgdGhpcywgYW4gYmluZCBpbmZpeCBvcGVyYXRv cgp0aGF0IHByb3BhZ2F0ZXMgdGhlIGVycm9yIGF1dG9tYXRpY2FsbHkgaXMgcmVhbGx5IG5lZWRl ZCAodHJ5aW5nIHRvCmNhdGNoIHdpdGggdG9kYXkncyBtZXNzYWdlcywgSSBzZWUgdGhhdCA+Pj0/ IGlzIGFscmVhZHkgdXNlZCBmb3IgdGhhdApwdXJwb3NlKS4gIEFsc28sIHdpdGggT3JfZXJyb3Iu dCAob3IgZXhjZXB0aW9ucyksIHRoZXJlIGlzIG5vIHdheSB0bwplbnN1cmUgdGhhdCB0aGUgZXJy b3IgaXMgZXZlbnR1YWxseSBhY3RlZCB1cG9uIHNvIHdoeSBub3QgdG8gc2ltcGx5CnVzZSDigJxm YWls4oCdPwoKPiBUaGUgcHJvYmxlbSB3ZSBoYXZlIGluIE1pcmFnZSBpcyB0aGF0IG91ciB0eXBl cyBhcmUgYWJzdHJhY3QuIEZvcgo+IGV4YW1wbGUsIGlmIHlvdSBoYXZlIGEgZnVuY3Rvcgo+IAo+ ICAgbW9kdWxlIEZTIChCIDogQkxPQ0spICA9IC4uLgo+IAo+IHRoZW4gdGhlIGF1dGhvciBvZiB0 aGUgRlMgZnVuY3RvciBkb2Vzbid0IGtub3cgZXhhY3RseSB3aGF0IGVycm9ycyB0aGUKPiBjb25j cmV0ZSBCIG1pZ2h0IHRocm93LiBGb3IgZXhhbXBsZSwgaWYgQiBpcyBhIHJlbW90ZSBkaXNrIHRo ZW4gaXQKPiBtaWdodCB0aHJvdyBuZXR3b3JrIGVycm9ycy4gU28gZW5zdXJpbmcgdGhhdCBjYWxs ZXJzIGVudW1lcmF0ZSBhbGwKPiBlcnJvcnMgaXNuJ3QgdmVyeSBoZWxwZnVsIGluIHRoaXMgY2Fz ZS4KPiAKPiBZb3UgY2FuIGdpdmUgRlMgYW4gZXJyb3IgY29kZSBvZiBbYEJsb2NrX2Vycm9yIG9m IEIuZXJyb3JdIGFuZCBqdXN0Cj4gcHJvcGFnYXRlIGl0IHRvIHRoZSBjYWxsZXIsIHdoaWNoIGlz IHdoYXQgd2UgZG8gbm93LiBUaGF0IHNlZW1zIHF1aXRlCj4gY2xldmVyLCBidXQgSSdtIHN0cnVn Z2xpbmcgdG8gaW1hZ2luZSBhIGNhc2Ugd2hlcmUgaXQncyBhY3R1YWxseQo+IHVzZWZ1bC4KClRo YXQncyB3aGF0IEkgd2FzIGdvaW5nIHRvIHN1Z2dlc3QuLi4gIERlY2xhcmluZyBzZXZlcmFsIGBC bG9ja19lcnJvcgppZiBuZWNlc3NhcnkgYWxsb3dzIHRvIGFjdCBvbiAiY2xhc3NlcyIgb2YgZXJy b3JzIOKAlCB3aGljaCBpcyBhbGwgb25lCmNhbiBob3BlIGZvciBnaXZlbiB0aGUgYWJzdHJhY3Rp b24uCgo+IEl0J3MgcHJvYmFibHkgd29ydGggY29tcGlsaW5nIGEgbGlzdCBvZiBleGFtcGxlcyB3 aGVyZSBNaXJhZ2UgY29kZQo+IGN1cnJlbnRseSBtYXRjaGVzIG9uIHNwZWNpZmljIHJldHVybmVk IEVycm9yIGNvZGVzIGFuZCB0YWtlcyBzcGVjaWZpYwo+IGFjdGlvbnMuIE15IGd1ZXNzIGlzIHRo ZXJlIGFyZW4ndCBlbm91Z2ggdG8ganVzdGlmeSB0aGUgY29tcGxleGl0eQo+IHRob3VnaC4KClRo YXQgd291bGQgYmUgbmljZS4gIEkgZG9uJ3QgaGF2ZSBtdWNoIGZhbWlsaWFyaXR5IHdpdGggYSBs b3Qgb2YgcGFydHMKb2YgTWlyYWdlIHNvIEkgbWF5IGJlIG1pc3NpbmcgdXNlIGNhc2VzLiAgQXMg SSB1bmRlcnN0YW5kIHRoZQpkaXNjdXNzaW9uLCBNaXJhZ2UgY29kZSBzaG91bGQgYmUgcmV2aXNp dGVkLCBub3Qgb25seSB0byBzZWUgaG93CnRoaW5ncyBhcmUgZG9uZSBub3cgYnV0IGFsc28gd2hh dCB0aGUgcHJvYmxlbXMgYXJlICh3aXRoIHRoZSBjdXJyZW50CnNjaGVtZSkgYW5kIHdoYXQgcHJv cGVydGllcyBvZiB0aGUgZXJyb3IgaGFuZGxpbmcgd2Ugd291bGQgbGlrZSBpbgp0aGVzZSBjYXNl cy4KCj4gWy4uLl0gaW4gZXZlcnkgb25lIG9mIHRoZXNlIGNhc2VzIHdoZXJlIHdlIG1hdGNoIG9u IGFuIGBFcnJvciwgd2UganVzdAo+IHByb3BhZ2F0ZSBpdCAoaS5lLiB0aGUgZGVmYXVsdCBiZWhh dmlvdXIgb2YgYW4gZXhjZXB0aW9uIHdvdWxkIGhhdmUKPiBiZWVuIGNvcnJlY3QpLgo+IAo+IEhl cmUgYXJlIHNvbWUgZXhhbXBsZXM6Cj4gCj4gfCBgRXJyb3IgKGBJbnZhbGlkX2NvbnNvbGUgeCkg LT4gZmFpbCAoRmFpbHVyZSAoUHJpbnRmLnNwcmludGYgIkludmFsaWRfY29uc29sZSAlcyIgeCkp Cj4gfCBgRXJyb3IgKGBCbG9ja19kZXZpY2UgZSkgLT4gZmFpbCAoRmFpbHVyZSAoRnMuc3RyaW5n X29mX2Jsb2NrX2Vycm9yIGUpKQo+IHwgYEVycm9yIChLVi5Vbmtub3duX2tleSBrZXkpIC0+IGZh aWwgKEludmFsaWRfYXJndW1lbnQga2V5KQo+IHwgYEVycm9yIChgVW5rbm93biBtc2cpIC0+IEx3 dC5mYWlsIChGYWlsdXJlIG1zZykKCkkgZG9uJ3QgdW5kZXJzdGFuZCB0aGUgcG9pbnQgb2YgdGhp cyB0eXBlIG9mIGNvZGUuICBXaHkgd2Fzbid0IOKAnEVycm9y4oCdCmRlY2xhcmVkIGFzIGFuIGV4 Y2VwdGlvbiAocG9zc2libHkgd2l0aCBhbiBleGNlcHRpb24gcHJpbnRlcikgYW5kCuKAnGZhaWzi gJ0gZGlyZWN0bHkgaW52b2tlZCBvbiBpdD8gIFRoaXMgYWxzbyBoaWdobGlnaHRzIHRoYXQgcGVv cGxlIHNoeQphd2F5IGZyb20gaGF2aW5nIHRvIGhhbmRsZSBldmVuIGEgc2ltcGxlIGBFcnJvciB0 byB0aGUgcG9pbnQgdGhhdCBpdApzZWVtcyBwcmVmZXJhYmxlIHRvIGRlZ2VuZXJhdGUgaXQgYXMg YSBzdHJpbmchCgo+IFRoZSBvbmx5IGNhc2Ugd2hlcmUgd2UgZG8gc29tZXRoaW5nIGludGVyZXN0 aW5nIGlzIGBFcnJvciAoVW5rbm93bl9rZXkKPiBfKSwgd2hlcmUgd2Ugbm90ZSB0aGF0IGl0IHdh cyBhIHJlYWQ6Cj4gCj4gfCBgRXJyb3IgKFRNUEwuVW5rbm93bl9rZXkgXykgLT4gZmFpbCAoRmFp bHVyZSAoInJlYWQgIiBeIG5hbWUpKQo+IAo+IEhvd2V2ZXIsIFVua25vd25fa2V5IHdvdWxkbid0 IGJlIGFuIGV4Y2VwdGlvbiB1bmRlciBhbnkgcHJvcG9zZWQgc2NoZW1lIGFueXdheQoKSW4gdGhl IHByZXZpb3VzIGRpc2N1c3Npb24sIEkgaGFkIHRoZSBpbXByZXNzaW9uIHRoYXQgaGF2aW5nIGEg c2NoZW1lCnRvIHByb3BhZ2F0ZSBlcnJvcnMgc2VhbWxlc3NseSB3aGlsZSBmb3JjaW5nIGNlcnRh aW4gKGNsYXNzZXMgb2YpCmVycm9ycyB0byBiZSBoYW5kbGVkIGJlZm9yZSB0aGV5IHJlYWNoIHRo ZSBtYWluIGxvb3Agd2FzIGltcG9ydGFudC4KSWYgd2UgZG8gbm90IGNhcmUgYWJvdXQgdGhpcywg d2hhdCBpcyB3cm9uZyB3aXRoIHRoZSDigJxmYWls4oCdIG1lY2hhbmlzbQpvZiBMd3Q/CgpCZXN0 LApDLgoKX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KTWly YWdlT1MtZGV2ZWwgbWFpbGluZyBsaXN0Ck1pcmFnZU9TLWRldmVsQGxpc3RzLnhlbnByb2plY3Qu b3JnCmh0dHA6Ly9saXN0cy54ZW5wcm9qZWN0Lm9yZy9jZ2ktYmluL21haWxtYW4vbGlzdGluZm8v bWlyYWdlb3MtZGV2ZWwK From mirageos-devel-bounces@lists.xenproject.org Tue Feb 03 23:30:42 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 03 Feb 2015 23:30:42 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YImvZ-0003qQ-3v; Tue, 03 Feb 2015 23:30:41 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YImvY-0003qL-3z for mirageos-devel@lists.xenproject.org; Tue, 03 Feb 2015 23:30:40 +0000 Received: from [85.158.143.35] by server-3.bemta-4.messagelabs.com id BF/AD-02754-F1A51D45; Tue, 03 Feb 2015 23:30:39 +0000 X-Env-Sender: Christophe.TROESTLER@umons.ac.be X-Msg-Ref: server-3.tower-21.messagelabs.com!1423006238!11968392!1 X-Originating-IP: [157.55.234.82] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29589 invoked from network); 3 Feb 2015 23:30:39 -0000 Received: from mail-db3on0082.outbound.protection.outlook.com (HELO emea01-db3-obe.outbound.protection.outlook.com) (157.55.234.82) by server-3.tower-21.messagelabs.com with AES256-SHA encrypted SMTP; 3 Feb 2015 23:30:39 -0000 Received: from DB4PR05CA0036.eurprd05.prod.outlook.com (25.160.40.46) by AMXPR05MB244.eurprd05.prod.outlook.com (10.242.71.142) with Microsoft SMTP Server (TLS) id 15.1.81.19; Tue, 3 Feb 2015 23:30:38 +0000 Received: from DB3FFO11FD039.protection.gbl (2a01:111:f400:7e04::130) by DB4PR05CA0036.outlook.office365.com (2a01:111:e400:9850::46) with Microsoft SMTP Server (TLS) id 15.1.75.20 via Frontend Transport; Tue, 3 Feb 2015 23:30:38 +0000 Received: from smtp.umons.ac.be (193.190.208.132) by DB3FFO11FD039.mail.protection.outlook.com (10.47.217.70) with Microsoft SMTP Server (TLS) id 15.1.87.10 via Frontend Transport; Tue, 3 Feb 2015 23:30:37 +0000 Received: from poincare (10.104.2.63) by smtp.umons.ac.be (10.104.2.84) with Microsoft SMTP Server (TLS) id 14.3.224.2; Wed, 4 Feb 2015 00:30:30 +0100 Received: from localhost ([::1]) by poincare with esmtp (Exim 4.84) (envelope-from ) id 1YImvN-0000Q7-8M; Wed, 04 Feb 2015 00:30:29 +0100 Date: Wed, 4 Feb 2015 00:30:29 +0100 Message-ID: <20150204.003029.1138853194858080279.Christophe.Troestler@umons.ac.be> To: From: Christophe Troestler In-Reply-To: References: X-Face: #2fb%mPx>rRL@4ff~TVgZ"<[:,oL"`TUEGK/[8/qb58~C>jR(x4A+v/n)7BgpEtIph_neoLKJBq0JBY9:}8v|j Organization: Universite de Mons (http://math.umons.ac.be/anum/) X-Mailer: Mew version 6.6 on Emacs 24.4 / Mule 6.0 (HANACHIRUSATO) MIME-Version: 1.0 X-Originating-IP: [10.104.2.63] X-EOPAttributedMessage: 0 X-Matching-Connectors: 130674798378612804; (9b551343-d075-4328-d154-08d0574c44b8,aa519c6d-c5b7-417d-4ec3-08d1170c20a9); (9b551343-d075-4328-d154-08d0574c44b8,aa519c6d-c5b7-417d-4ec3-08d1170c20a9) Received-SPF: Pass (protection.outlook.com: domain of umons.ac.be designates 193.190.208.132 as permitted sender) receiver=protection.outlook.com; client-ip=193.190.208.132; helo=smtp.umons.ac.be; X-Forefront-Antispam-Report: CIP:193.190.208.132; CTRY:BE; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(10009020)(6009001)(438002)(76104003)(2950100001)(87936001)(86362001)(46406003)(46102003)(23726002)(16796002)(74482002)(57986006)(76506005)(36756003)(103116003)(50226001)(6806004)(92566002)(107886001)(2351001)(50986999)(76176999)(50466002)(47776003)(450100001)(62966003)(110136001)(77156002)(226693001)(97756001)(106466001); DIR:OUT; SFP:1101; SCL:1; SRVR:AMXPR05MB244; H:smtp.umons.ac.be; FPR:; SPF:Pass; MLV:sfv; LANG:en; X-Microsoft-Antispam: UriScan:; X-Microsoft-Antispam: BCL:0;PCL:0;RULEID:;SRVR:AMXPR05MB244; X-Exchange-Antispam-Report-Test: UriScan:; X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(601004); SRVR:AMXPR05MB244; X-Forefront-PRVS: 0476D4AB88 X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(400005)(401004); SRVR:AMXPR05MB244; X-MS-Exchange-CrossTenant-OriginalArrivalTime: 03 Feb 2015 23:30:37.5960 (UTC) X-MS-Exchange-CrossTenant-Id: 5afe0b00-7697-4969-b663-5eab37d5f47e X-MS-Exchange-CrossTenant-OriginalAttributedTenantConnectingIp: TenantId=5afe0b00-7697-4969-b663-5eab37d5f47e; Ip=[193.190.208.132] X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem X-MS-Exchange-Transport-CrossTenantHeadersStamped: AMXPR05MB244 Subject: Re: [MirageOS-devel] Error handling in Mirage - request for comments! X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org Regardless of the final scheme adopted for error handling, it seems that a type such as Result.t is important to share among libraries. Since depending on Core_kernel will stir debate, why not release an OPAM package "result" declaring Result.t together with a few useful functions (including monadic combinators) and ask Jane Street if they would agree that Core_kernel reexports it in order to be compatible? I know that one could dispense with that using polymorphic variants but, apart from the better efficiency, I think the slightly stricter type checking would also be beneficial. What do you think? _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Tue Feb 03 23:30:42 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 03 Feb 2015 23:30:42 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YImvZ-0003qQ-3v; Tue, 03 Feb 2015 23:30:41 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YImvY-0003qL-3z for mirageos-devel@lists.xenproject.org; Tue, 03 Feb 2015 23:30:40 +0000 Received: from [85.158.143.35] by server-3.bemta-4.messagelabs.com id BF/AD-02754-F1A51D45; Tue, 03 Feb 2015 23:30:39 +0000 X-Env-Sender: Christophe.TROESTLER@umons.ac.be X-Msg-Ref: server-3.tower-21.messagelabs.com!1423006238!11968392!1 X-Originating-IP: [157.55.234.82] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29589 invoked from network); 3 Feb 2015 23:30:39 -0000 Received: from mail-db3on0082.outbound.protection.outlook.com (HELO emea01-db3-obe.outbound.protection.outlook.com) (157.55.234.82) by server-3.tower-21.messagelabs.com with AES256-SHA encrypted SMTP; 3 Feb 2015 23:30:39 -0000 Received: from DB4PR05CA0036.eurprd05.prod.outlook.com (25.160.40.46) by AMXPR05MB244.eurprd05.prod.outlook.com (10.242.71.142) with Microsoft SMTP Server (TLS) id 15.1.81.19; Tue, 3 Feb 2015 23:30:38 +0000 Received: from DB3FFO11FD039.protection.gbl (2a01:111:f400:7e04::130) by DB4PR05CA0036.outlook.office365.com (2a01:111:e400:9850::46) with Microsoft SMTP Server (TLS) id 15.1.75.20 via Frontend Transport; Tue, 3 Feb 2015 23:30:38 +0000 Received: from smtp.umons.ac.be (193.190.208.132) by DB3FFO11FD039.mail.protection.outlook.com (10.47.217.70) with Microsoft SMTP Server (TLS) id 15.1.87.10 via Frontend Transport; Tue, 3 Feb 2015 23:30:37 +0000 Received: from poincare (10.104.2.63) by smtp.umons.ac.be (10.104.2.84) with Microsoft SMTP Server (TLS) id 14.3.224.2; Wed, 4 Feb 2015 00:30:30 +0100 Received: from localhost ([::1]) by poincare with esmtp (Exim 4.84) (envelope-from ) id 1YImvN-0000Q7-8M; Wed, 04 Feb 2015 00:30:29 +0100 Date: Wed, 4 Feb 2015 00:30:29 +0100 Message-ID: <20150204.003029.1138853194858080279.Christophe.Troestler@umons.ac.be> To: From: Christophe Troestler In-Reply-To: References: X-Face: #2fb%mPx>rRL@4ff~TVgZ"<[:,oL"`TUEGK/[8/qb58~C>jR(x4A+v/n)7BgpEtIph_neoLKJBq0JBY9:}8v|j Organization: Universite de Mons (http://math.umons.ac.be/anum/) X-Mailer: Mew version 6.6 on Emacs 24.4 / Mule 6.0 (HANACHIRUSATO) MIME-Version: 1.0 X-Originating-IP: [10.104.2.63] X-EOPAttributedMessage: 0 X-Matching-Connectors: 130674798378612804; (9b551343-d075-4328-d154-08d0574c44b8,aa519c6d-c5b7-417d-4ec3-08d1170c20a9); (9b551343-d075-4328-d154-08d0574c44b8,aa519c6d-c5b7-417d-4ec3-08d1170c20a9) Received-SPF: Pass (protection.outlook.com: domain of umons.ac.be designates 193.190.208.132 as permitted sender) receiver=protection.outlook.com; client-ip=193.190.208.132; helo=smtp.umons.ac.be; X-Forefront-Antispam-Report: CIP:193.190.208.132; CTRY:BE; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(10009020)(6009001)(438002)(76104003)(2950100001)(87936001)(86362001)(46406003)(46102003)(23726002)(16796002)(74482002)(57986006)(76506005)(36756003)(103116003)(50226001)(6806004)(92566002)(107886001)(2351001)(50986999)(76176999)(50466002)(47776003)(450100001)(62966003)(110136001)(77156002)(226693001)(97756001)(106466001); DIR:OUT; SFP:1101; SCL:1; SRVR:AMXPR05MB244; H:smtp.umons.ac.be; FPR:; SPF:Pass; MLV:sfv; LANG:en; X-Microsoft-Antispam: UriScan:; X-Microsoft-Antispam: BCL:0;PCL:0;RULEID:;SRVR:AMXPR05MB244; X-Exchange-Antispam-Report-Test: UriScan:; X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(601004); SRVR:AMXPR05MB244; X-Forefront-PRVS: 0476D4AB88 X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(400005)(401004); SRVR:AMXPR05MB244; X-MS-Exchange-CrossTenant-OriginalArrivalTime: 03 Feb 2015 23:30:37.5960 (UTC) X-MS-Exchange-CrossTenant-Id: 5afe0b00-7697-4969-b663-5eab37d5f47e X-MS-Exchange-CrossTenant-OriginalAttributedTenantConnectingIp: TenantId=5afe0b00-7697-4969-b663-5eab37d5f47e; Ip=[193.190.208.132] X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem X-MS-Exchange-Transport-CrossTenantHeadersStamped: AMXPR05MB244 Subject: Re: [MirageOS-devel] Error handling in Mirage - request for comments! X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org Regardless of the final scheme adopted for error handling, it seems that a type such as Result.t is important to share among libraries. Since depending on Core_kernel will stir debate, why not release an OPAM package "result" declaring Result.t together with a few useful functions (including monadic combinators) and ask Jane Street if they would agree that Core_kernel reexports it in order to be compatible? I know that one could dispense with that using polymorphic variants but, apart from the better efficiency, I think the slightly stricter type checking would also be beneficial. What do you think? _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Tue Feb 03 23:53:14 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 03 Feb 2015 23:53:14 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YInHM-00064P-SP; Tue, 03 Feb 2015 23:53:12 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YInHM-00064K-3z for mirageos-devel@lists.xenproject.org; Tue, 03 Feb 2015 23:53:12 +0000 Received: from [193.109.254.147] by server-10.bemta-14.messagelabs.com id 3C/D2-02750-76F51D45; Tue, 03 Feb 2015 23:53:11 +0000 X-Env-Sender: daniel.buenzli@erratique.ch X-Msg-Ref: server-5.tower-27.messagelabs.com!1423007590!7991085!1 X-Originating-IP: [74.55.86.74] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNzQuNTUuODYuNzQgPT4gMzA4NTYz\n X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15449 invoked from network); 3 Feb 2015 23:53:10 -0000 Received: from mail6.webfaction.com (HELO smtp.webfaction.com) (74.55.86.74) by server-5.tower-27.messagelabs.com with SMTP; 3 Feb 2015 23:53:10 -0000 Received: from [172.20.10.2] (227-224.197-178.cust.bluewin.ch [178.197.224.227]) by smtp.webfaction.com (Postfix) with ESMTP id 33C6E20790FA; Tue, 3 Feb 2015 23:53:08 +0000 (UTC) Date: Wed, 4 Feb 2015 00:53:07 +0100 From: =?utf-8?Q?Daniel_B=C3=BCnzli?= To: Christophe Troestler Message-ID: <16390DA9F0BA4EED9507CA2012993CD5@erratique.ch> In-Reply-To: <20150204.003029.1138853194858080279.Christophe.Troestler@umons.ac.be> References: <20150204.003029.1138853194858080279.Christophe.Troestler@umons.ac.be> X-Mailer: sparrow 1.6.4 (build 1178) MIME-Version: 1.0 Content-Disposition: inline Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Error handling in Mirage - request for comments! X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org TGUgbWVyY3JlZGksIDQgZsOpdnJpZXIgMjAxNSDDoCAwMDozMCwgQ2hyaXN0b3BoZSBUcm9lc3Rs ZXIgYSDDqWNyaXQgOgo+IFJlZ2FyZGxlc3Mgb2YgdGhlIGZpbmFsIHNjaGVtZSBhZG9wdGVkIGZv ciBlcnJvciBoYW5kbGluZywgaXQgc2VlbXMKPiB0aGF0IGEgdHlwZSBzdWNoIGFzIFJlc3VsdC50 IGlzIGltcG9ydGFudCB0byBzaGFyZSBhbW9uZyBsaWJyYXJpZXMuCj4gU2luY2UgZGVwZW5kaW5n IG9uIENvcmVfa2VybmVsIHdpbGwgc3RpciBkZWJhdGUsIHdoeSBub3QgcmVsZWFzZSBhbgo+IE9Q QU0gcGFja2FnZSAicmVzdWx0IiBkZWNsYXJpbmcgUmVzdWx0LnQgdG9nZXRoZXIgd2l0aCBhIGZl dyB1c2VmdWwKPiBmdW5jdGlvbnMgKGluY2x1ZGluZyBtb25hZGljIGNvbWJpbmF0b3JzKSBhbmQg YXNrIEphbmUgU3RyZWV0IGlmIHRoZXkKPiB3b3VsZCBhZ3JlZSB0aGF0IENvcmVfa2VybmVsIHJl ZXhwb3J0cyBpdCBpbiBvcmRlciB0byBiZSBjb21wYXRpYmxlPwo+IEkga25vdyB0aGF0IG9uZSBj b3VsZCBkaXNwZW5zZSB3aXRoIHRoYXQgdXNpbmcgcG9seW1vcnBoaWMgdmFyaWFudHMKPiBidXQs IGFwYXJ0IGZyb20gdGhlIGJldHRlciBlZmZpY2llbmN5LCBJIHRoaW5rIHRoZSBzbGlnaHRseSBz dHJpY3Rlcgo+IHR5cGUgY2hlY2tpbmcgd291bGQgYWxzbyBiZSBiZW5lZmljaWFsLgo+ICAKPiBX aGF0IGRvIHlvdSB0aGluaz8KSSdtIG5vdCBzdXJlIHRoYXQncyB2ZXJ5IHVzZWZ1bCBzaW5jZSBv ZnRlbiB5b3Ugd2lsbCB3YW50IHRvIHdvcmsgd2l0aCB0aGlzIHR5cGUgb3ZlciBhIG1vbmFkaWMg Y29uY3VycmVuY3kgbGlicmFyeSBhbmQvb3IgcHJvdmlkZSBjb21iaW5hdG9ycyB0aGF0IGludGVy YWN0IHdpdGggYSBsb2dnaW5nIGxpYnJhcnkgKGUuZy4gc2VlIHRoZSBhc3NlbWJsYWdlIGNvbWJp bmF0b3JzIEkgbGlua2VkIHRvIGVhcmxpZXIpLiBJdCBzZWVtcyB0byBtZSB0aGVyZSB3aWxsIGJl IHZlcnkgbGl0dGxlIGxlZnQgYW5kIGxvb3NlIGNvdXBsaW5nIGJldHdlZW4gcGFja2FnZXMgc2Vl bXMgZmluZSB0byBtZSBpbiB0aGF0IGNhc2UuIEkgcmF0aGVyIHRoaW5rIHRoYXQgbWlyYWdlIGl0 c2VsZiBzaG91bGQgZGVmaW5lIGEgbGlicmFyeSB3aXRoIGFsbCB0aGUgZ29vZCB0b29scyB0byBl bmZvcmNlIGl0cyBjaG9zZW4gZXJyb3IgaGFuZGxpbmcgc2NoZW1lLiAgCgpCZXN0LAoKRGFuaWVs CgoKCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fCk1pcmFn ZU9TLWRldmVsIG1haWxpbmcgbGlzdApNaXJhZ2VPUy1kZXZlbEBsaXN0cy54ZW5wcm9qZWN0Lm9y ZwpodHRwOi8vbGlzdHMueGVucHJvamVjdC5vcmcvY2dpLWJpbi9tYWlsbWFuL2xpc3RpbmZvL21p cmFnZW9zLWRldmVsCg== From mirageos-devel-bounces@lists.xenproject.org Tue Feb 03 23:53:14 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 03 Feb 2015 23:53:14 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YInHM-00064P-SP; Tue, 03 Feb 2015 23:53:12 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YInHM-00064K-3z for mirageos-devel@lists.xenproject.org; Tue, 03 Feb 2015 23:53:12 +0000 Received: from [193.109.254.147] by server-10.bemta-14.messagelabs.com id 3C/D2-02750-76F51D45; Tue, 03 Feb 2015 23:53:11 +0000 X-Env-Sender: daniel.buenzli@erratique.ch X-Msg-Ref: server-5.tower-27.messagelabs.com!1423007590!7991085!1 X-Originating-IP: [74.55.86.74] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNzQuNTUuODYuNzQgPT4gMzA4NTYz\n X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15449 invoked from network); 3 Feb 2015 23:53:10 -0000 Received: from mail6.webfaction.com (HELO smtp.webfaction.com) (74.55.86.74) by server-5.tower-27.messagelabs.com with SMTP; 3 Feb 2015 23:53:10 -0000 Received: from [172.20.10.2] (227-224.197-178.cust.bluewin.ch [178.197.224.227]) by smtp.webfaction.com (Postfix) with ESMTP id 33C6E20790FA; Tue, 3 Feb 2015 23:53:08 +0000 (UTC) Date: Wed, 4 Feb 2015 00:53:07 +0100 From: =?utf-8?Q?Daniel_B=C3=BCnzli?= To: Christophe Troestler Message-ID: <16390DA9F0BA4EED9507CA2012993CD5@erratique.ch> In-Reply-To: <20150204.003029.1138853194858080279.Christophe.Troestler@umons.ac.be> References: <20150204.003029.1138853194858080279.Christophe.Troestler@umons.ac.be> X-Mailer: sparrow 1.6.4 (build 1178) MIME-Version: 1.0 Content-Disposition: inline Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Error handling in Mirage - request for comments! X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org TGUgbWVyY3JlZGksIDQgZsOpdnJpZXIgMjAxNSDDoCAwMDozMCwgQ2hyaXN0b3BoZSBUcm9lc3Rs ZXIgYSDDqWNyaXQgOgo+IFJlZ2FyZGxlc3Mgb2YgdGhlIGZpbmFsIHNjaGVtZSBhZG9wdGVkIGZv ciBlcnJvciBoYW5kbGluZywgaXQgc2VlbXMKPiB0aGF0IGEgdHlwZSBzdWNoIGFzIFJlc3VsdC50 IGlzIGltcG9ydGFudCB0byBzaGFyZSBhbW9uZyBsaWJyYXJpZXMuCj4gU2luY2UgZGVwZW5kaW5n IG9uIENvcmVfa2VybmVsIHdpbGwgc3RpciBkZWJhdGUsIHdoeSBub3QgcmVsZWFzZSBhbgo+IE9Q QU0gcGFja2FnZSAicmVzdWx0IiBkZWNsYXJpbmcgUmVzdWx0LnQgdG9nZXRoZXIgd2l0aCBhIGZl dyB1c2VmdWwKPiBmdW5jdGlvbnMgKGluY2x1ZGluZyBtb25hZGljIGNvbWJpbmF0b3JzKSBhbmQg YXNrIEphbmUgU3RyZWV0IGlmIHRoZXkKPiB3b3VsZCBhZ3JlZSB0aGF0IENvcmVfa2VybmVsIHJl ZXhwb3J0cyBpdCBpbiBvcmRlciB0byBiZSBjb21wYXRpYmxlPwo+IEkga25vdyB0aGF0IG9uZSBj b3VsZCBkaXNwZW5zZSB3aXRoIHRoYXQgdXNpbmcgcG9seW1vcnBoaWMgdmFyaWFudHMKPiBidXQs IGFwYXJ0IGZyb20gdGhlIGJldHRlciBlZmZpY2llbmN5LCBJIHRoaW5rIHRoZSBzbGlnaHRseSBz dHJpY3Rlcgo+IHR5cGUgY2hlY2tpbmcgd291bGQgYWxzbyBiZSBiZW5lZmljaWFsLgo+ICAKPiBX aGF0IGRvIHlvdSB0aGluaz8KSSdtIG5vdCBzdXJlIHRoYXQncyB2ZXJ5IHVzZWZ1bCBzaW5jZSBv ZnRlbiB5b3Ugd2lsbCB3YW50IHRvIHdvcmsgd2l0aCB0aGlzIHR5cGUgb3ZlciBhIG1vbmFkaWMg Y29uY3VycmVuY3kgbGlicmFyeSBhbmQvb3IgcHJvdmlkZSBjb21iaW5hdG9ycyB0aGF0IGludGVy YWN0IHdpdGggYSBsb2dnaW5nIGxpYnJhcnkgKGUuZy4gc2VlIHRoZSBhc3NlbWJsYWdlIGNvbWJp bmF0b3JzIEkgbGlua2VkIHRvIGVhcmxpZXIpLiBJdCBzZWVtcyB0byBtZSB0aGVyZSB3aWxsIGJl IHZlcnkgbGl0dGxlIGxlZnQgYW5kIGxvb3NlIGNvdXBsaW5nIGJldHdlZW4gcGFja2FnZXMgc2Vl bXMgZmluZSB0byBtZSBpbiB0aGF0IGNhc2UuIEkgcmF0aGVyIHRoaW5rIHRoYXQgbWlyYWdlIGl0 c2VsZiBzaG91bGQgZGVmaW5lIGEgbGlicmFyeSB3aXRoIGFsbCB0aGUgZ29vZCB0b29scyB0byBl bmZvcmNlIGl0cyBjaG9zZW4gZXJyb3IgaGFuZGxpbmcgc2NoZW1lLiAgCgpCZXN0LAoKRGFuaWVs CgoKCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fCk1pcmFn ZU9TLWRldmVsIG1haWxpbmcgbGlzdApNaXJhZ2VPUy1kZXZlbEBsaXN0cy54ZW5wcm9qZWN0Lm9y ZwpodHRwOi8vbGlzdHMueGVucHJvamVjdC5vcmcvY2dpLWJpbi9tYWlsbWFuL2xpc3RpbmZvL21p cmFnZW9zLWRldmVsCg== From mirageos-devel-bounces@lists.xenproject.org Wed Feb 04 11:15:03 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 04 Feb 2015 11:15:03 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YIxv7-0007vz-SS; Wed, 04 Feb 2015 11:14:57 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YIxv6-0007vI-GL; Wed, 04 Feb 2015 11:14:56 +0000 Received: from [85.158.137.68] by server-9.bemta-3.messagelabs.com id 77/FB-02995-F2FF1D45; Wed, 04 Feb 2015 11:14:55 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-7.tower-31.messagelabs.com!1423048494!11928134!1 X-Originating-IP: [74.125.82.42] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.12.5; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27036 invoked from network); 4 Feb 2015 11:14:54 -0000 Received: from mail-wg0-f42.google.com (HELO mail-wg0-f42.google.com) (74.125.82.42) by server-7.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 4 Feb 2015 11:14:54 -0000 Received: by mail-wg0-f42.google.com with SMTP id x13so1105542wgg.1; Wed, 04 Feb 2015 03:14:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=LXYcHNXz+EcjevHF4CbfI47K8BzeCks1jAI5xShO6ao=; b=dodC8CPIB4UizZlIolx0pA8A/5gJT62YEsl3+zr+T1CsJUD57UKCqY/KnzzcZPSwZ1 ebsRWz4GyN9yC/URHY6v/QD1aYJVQ0o1aF3TWUHaCnqGm+oyDyoB3jHYl4fsrjrgCCud thhTdUa9rNqPji4b/o1wvHKkv2Py4Ko962/SM+kpcfgTYClSR2D9QrYOzz51F0z215A1 HNk54ZGV01ERbMHbCWzO4So+duIi1We7IForlEOuBD7KlRxQ/TwqmcTJP7r1AmUyNrZN IbR7NK5rwzpom4R0uz9CLhAMCwAb/4JzjWd+U7PcVKnP9I8aP/7ychEHYgdPDr0geCCY SJcw== X-Received: by 10.180.10.131 with SMTP id i3mr3477982wib.54.1423048493877; Wed, 04 Feb 2015 03:14:53 -0800 (PST) Received: from [192.168.0.12] (97e5a0c2.skybroadband.com. [151.229.160.194]) by mx.google.com with ESMTPSA id hr1sm28786389wib.1.2015.02.04.03.14.52 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 04 Feb 2015 03:14:53 -0800 (PST) Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Lars Kurth In-Reply-To: <851C4ADF-6236-443B-B7BA-5A7A68AC8819@gmail.com> Date: Wed, 4 Feb 2015 11:14:50 +0000 Message-Id: <93E2E849-D786-47EC-8100-9EED6B1F7D96@gmail.com> References: <851C4ADF-6236-443B-B7BA-5A7A68AC8819@gmail.com> To: xen-devel , Win-pv-devel@lists.xenproject.org, mirageos-devel , xen-api@lists.xenproject.org, embedded-pv-devel@lists.xenproject.org X-Mailer: Apple Mail (2.1878.6) Cc: advisory-board@lists.xenproject.org Subject: Re: [MirageOS-devel] Hackathon date options in Shanghai : please vote for a preference by Wed the 3rd of Feb (confirmed Option 2: April 28-29) X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org Hi all, seems the overwhelming majority has chosen - Option 2: April 28-29 - I will work with Intel on the details and send these out as soon as I have final confirmation Best Regards Lars On 28 Jan 2015, at 10:09, Lars Kurth wrote: > Dear community members, > > Intel has volunteered to host the next Xen Project Hackathon in Shanghai in China. We were originally looking at an April/May time-frame, but due to Easter holidays and the OpenStack summit in May, the following two date options look most sensible. > > Remember, this is a two day event. > > The options are: > * Option 1: 2 days from Tue April 21 to Fri 24th ... In this case I would suggest maybe the 22 - 23rd, giving people a chance to meet customers on Friday and/or do a bit of sightseeing. It also means that attendees from other Chinese cities will be able to get to their home cities more easily (Friday is always extremely busy) > * Option 2: April 28-29 > > Please let me know if you have any preferences and vote for option 1 or 2 (if you vote for option 1 let me know if you care about any specific dates) > > Regards > Lars _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Wed Feb 04 11:15:03 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 04 Feb 2015 11:15:03 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YIxv7-0007vz-SS; Wed, 04 Feb 2015 11:14:57 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YIxv6-0007vI-GL; Wed, 04 Feb 2015 11:14:56 +0000 Received: from [85.158.137.68] by server-9.bemta-3.messagelabs.com id 77/FB-02995-F2FF1D45; Wed, 04 Feb 2015 11:14:55 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-7.tower-31.messagelabs.com!1423048494!11928134!1 X-Originating-IP: [74.125.82.42] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.12.5; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27036 invoked from network); 4 Feb 2015 11:14:54 -0000 Received: from mail-wg0-f42.google.com (HELO mail-wg0-f42.google.com) (74.125.82.42) by server-7.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 4 Feb 2015 11:14:54 -0000 Received: by mail-wg0-f42.google.com with SMTP id x13so1105542wgg.1; Wed, 04 Feb 2015 03:14:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=LXYcHNXz+EcjevHF4CbfI47K8BzeCks1jAI5xShO6ao=; b=dodC8CPIB4UizZlIolx0pA8A/5gJT62YEsl3+zr+T1CsJUD57UKCqY/KnzzcZPSwZ1 ebsRWz4GyN9yC/URHY6v/QD1aYJVQ0o1aF3TWUHaCnqGm+oyDyoB3jHYl4fsrjrgCCud thhTdUa9rNqPji4b/o1wvHKkv2Py4Ko962/SM+kpcfgTYClSR2D9QrYOzz51F0z215A1 HNk54ZGV01ERbMHbCWzO4So+duIi1We7IForlEOuBD7KlRxQ/TwqmcTJP7r1AmUyNrZN IbR7NK5rwzpom4R0uz9CLhAMCwAb/4JzjWd+U7PcVKnP9I8aP/7ychEHYgdPDr0geCCY SJcw== X-Received: by 10.180.10.131 with SMTP id i3mr3477982wib.54.1423048493877; Wed, 04 Feb 2015 03:14:53 -0800 (PST) Received: from [192.168.0.12] (97e5a0c2.skybroadband.com. [151.229.160.194]) by mx.google.com with ESMTPSA id hr1sm28786389wib.1.2015.02.04.03.14.52 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 04 Feb 2015 03:14:53 -0800 (PST) Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Lars Kurth In-Reply-To: <851C4ADF-6236-443B-B7BA-5A7A68AC8819@gmail.com> Date: Wed, 4 Feb 2015 11:14:50 +0000 Message-Id: <93E2E849-D786-47EC-8100-9EED6B1F7D96@gmail.com> References: <851C4ADF-6236-443B-B7BA-5A7A68AC8819@gmail.com> To: xen-devel , Win-pv-devel@lists.xenproject.org, mirageos-devel , xen-api@lists.xenproject.org, embedded-pv-devel@lists.xenproject.org X-Mailer: Apple Mail (2.1878.6) Cc: advisory-board@lists.xenproject.org Subject: Re: [MirageOS-devel] Hackathon date options in Shanghai : please vote for a preference by Wed the 3rd of Feb (confirmed Option 2: April 28-29) X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org Hi all, seems the overwhelming majority has chosen - Option 2: April 28-29 - I will work with Intel on the details and send these out as soon as I have final confirmation Best Regards Lars On 28 Jan 2015, at 10:09, Lars Kurth wrote: > Dear community members, > > Intel has volunteered to host the next Xen Project Hackathon in Shanghai in China. We were originally looking at an April/May time-frame, but due to Easter holidays and the OpenStack summit in May, the following two date options look most sensible. > > Remember, this is a two day event. > > The options are: > * Option 1: 2 days from Tue April 21 to Fri 24th ... In this case I would suggest maybe the 22 - 23rd, giving people a chance to meet customers on Friday and/or do a bit of sightseeing. It also means that attendees from other Chinese cities will be able to get to their home cities more easily (Friday is always extremely busy) > * Option 2: April 28-29 > > Please let me know if you have any preferences and vote for option 1 or 2 (if you vote for option 1 let me know if you care about any specific dates) > > Regards > Lars _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Wed Feb 04 11:52:33 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 04 Feb 2015 11:52:33 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YIyVU-0003OL-6R; Wed, 04 Feb 2015 11:52:32 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YIyVT-0003OB-4w for mirageos-devel@lists.xenproject.org; Wed, 04 Feb 2015 11:52:31 +0000 Received: from [85.158.139.211] by server-16.bemta-5.messagelabs.com id 13/05-02804-EF702D45; Wed, 04 Feb 2015 11:52:30 +0000 X-Env-Sender: talex5@gmail.com X-Msg-Ref: server-12.tower-206.messagelabs.com!1423050749!11084997!1 X-Originating-IP: [209.85.217.181] X-SpamReason: No, hits=0.8 required=7.0 tests=BODY_RANDOM_LONG, RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8666 invoked from network); 4 Feb 2015 11:52:29 -0000 Received: from mail-lb0-f181.google.com (HELO mail-lb0-f181.google.com) (209.85.217.181) by server-12.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 4 Feb 2015 11:52:29 -0000 Received: by mail-lb0-f181.google.com with SMTP id u10so1002158lbd.12 for ; Wed, 04 Feb 2015 03:52:28 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=4hKLhz1uY5snnnyUG2GHxxHWYuQGJ0mvvibt8U82bLk=; b=BV5Sj2GC3rGV7eRTdsbl4dsmoC4yuPem8UaVbu0rjpCQAV/7o4PzvfDNpN43KxtrVd 88RSPPaGCjK6F55A+15uWLirN3sKC0jiSOQaf/BYjTV0X6J6rRL8r3tZ7D9qvePTOIDE UH3TUHn79wDsXiPFPdpl1YgIdO2MqTNIqFWkAyvs2fidDcMbhjPANRUlur0sgVkE94JJ dAJea6uQVNXo7IKynIV6EwzhM9CJpvi0gRnbQFiUqpzQpvbWn3l5UmIxVMSMsIAd/V57 TARV7kgx/YYsIuY5u2F/6JabTfQlwO7q2uK3JnlQYCr8w+3VK7UYstehG+B4fcFWGuBl dTag== MIME-Version: 1.0 X-Received: by 10.152.183.196 with SMTP id eo4mr30143358lac.0.1423050748653; Wed, 04 Feb 2015 03:52:28 -0800 (PST) Received: by 10.25.207.206 with HTTP; Wed, 4 Feb 2015 03:52:28 -0800 (PST) In-Reply-To: <20150204.001614.26478837567139584.Christophe.Troestler@umons.ac.be> References: <20150202.014549.1883720051237442569.Christophe.Troestler@umons.ac.be> <20150204.001614.26478837567139584.Christophe.Troestler@umons.ac.be> Date: Wed, 4 Feb 2015 11:52:28 +0000 Message-ID: From: Thomas Leonard To: Christophe Troestler Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Error handling in Mirage - request for comments! X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org T24gMyBGZWJydWFyeSAyMDE1IGF0IDIzOjE2LCBDaHJpc3RvcGhlIFRyb2VzdGxlcgo8Q2hyaXN0 b3BoZS5Ucm9lc3RsZXJAdW1vbnMuYWMuYmU+IHdyb3RlOgo+IE9uIE1vbiwgMiBGZWIgMjAxNSAx MjozMDozOSArMDAwMCwgVGhvbWFzIExlb25hcmQgd3JvdGU6Cj4+Cj4+IE9uIDIgRmVicnVhcnkg MjAxNSBhdCAwMDo0NSwgQ2hyaXN0b3BoZSBUcm9lc3RsZXIKPj4gPENocmlzdG9waGUuVHJvZXN0 bGVyQHVtb25zLmFjLmJlPiB3cm90ZToKPj4gPiBPbiBTYXQsIDMxIEphbiAyMDE1IDIxOjA3OjIy ICswMDAwLCBUaG9tYXMgTGVvbmFyZCB3cm90ZToKPj4gPj4KPj4gPj4gW+KApl0gQnV0IHRoZSBy ZWFsIHByb2JsZW0gaGVyZSBpcyB0aGF0IGJ5IG1ha2luZyBleGNlcHRpb25zIGZhdGFsIHdlCj4+ ID4+IHR1cm4gZXZlcnkgZXhjZXB0aW9uIHVzZWQgaW4gZXhpc3RpbmcgT0NhbWwgY29kZSBpbnRv IGEgc2VjdXJpdHkKPj4gPj4gdnVsbmVyYWJpbGl0eS4gW+KApl0KPj4gPgo+PiA+IFNpbmNlIE9D YW1sIHN1cHBvcnRzIGV4Y2VwdGlvbnMsIEkgdGhpbmsgdGhlcmUgaXMgbm8gZG91YnQgdGhhdCB3 ZQo+PiA+IG11c3QgaGFuZGxlIHRoZW0gZWZmZWN0aXZlbHkg4oCUIG5vdCBqdXN0IHdpcGUgdGhl bSB1bmRlciB0aGUgY2FycGV0IGFuZAo+PiA+IGxldCB0aGVtIGFib3J0IHRoZSBwcm9ncmFtL3Vu aWtlcm5lbC4gIElkZWFsbHkgTHd0IHNob3VsZCBkZWFsCj4+ID4gc2Vuc2libHkgd2l0aCBleGNl cHRpb25zIChhbmQgdGhlIGRpc2N1c3Npb24gc2VlbXMgdG8gaW1wbHkgdGhlcmUgYXJlCj4+ID4g YXJlYXMgb2YgaW1wcm92ZW1lbnQg4oCUIGJ1dCBpdCBpcyB1bmNsZWFyIHRvIG1lIGhvdyB5b3Ug Y2FuIGRvIHRoYXQKPj4gPiBlZmZpY2llbnRseSB3aXRob3V0IHVzaW5nIGEgdHJ5IGJsb2NrIGlu IGFsbCBiaW5kcykuCj4+Cj4+IEx3dCBhbHJlYWR5IHB1dHMgYSB0cnkgYmxvY2sgaW4gYWxsIChz bGVlcGluZykgYmluZHMsIHNvIHRoaXMgaXMKPj4gaGFuZGxlZCBmb3IgeW91Ogo+Pgo+PiBsZXQg YmluZCB0IGYgPQo+PiAgIGxldCB0ID0gcmVwciB0IGluCj4+ICAgbWF0Y2ggdC5zdGF0ZSB3aXRo Cj4+ICAgICB8IFJldHVybiB2IC0+Cj4+ICAgICAgICAgZiB2Cj4+ICAgICB8IEZhaWwgXyBhcyBz dGF0ZSAtPgo+PiAgICAgICAgIHRocmVhZCB7IHN0YXRlIH0KPj4gICAgIHwgU2xlZXAgc2xlZXBl ciAtPgo+PiAgICAgICAgIGxldCByZXMgPSB0ZW1wIHQgaW4KPj4gICAgICAgICBsZXQgZGF0YSA9 ICFjdXJyZW50X2RhdGEgaW4KPj4gICAgICAgICBhZGRfaW1tdXRhYmxlX3dhaXRlciBzbGVlcGVy Cj4+ICAgICAgICAgICAoZnVuY3Rpb24KPj4gICAgICAgICAgICAgIHwgUmV0dXJuIHYgLT4gY3Vy cmVudF9kYXRhIDo9IGRhdGE7IGNvbm5lY3QgcmVzICh0cnkgZiB2Cj4+IHdpdGggZXhuIC0+IGZh aWwgZXhuKQo+PiAgICAgICAgICAgICAgfCBGYWlsIF8gYXMgc3RhdGUgLT4gZmFzdF9jb25uZWN0 IHJlcyBzdGF0ZQo+PiAgICAgICAgICAgICAgfCBfIC0+IGFzc2VydCBmYWxzZSk7Cj4+ICAgICAg ICAgcmVzCj4KPiBUaGFua3MgZm9yIGNoZWNraW5nLiAgQXQgZmlyc3QsIHRoZSBkaWZmZXJlbmNl IG9mIHRyZWF0bWVudCBiZXR3ZWVuCj4gdGhlIHR3byDigJxmIHbigJ0gaXMgYSBsaXR0bGUgb2Rk LiAgRG8geW91IGhhcHBlbiB0byBrbm93IHRoZSByZWFzb24gZm9yCj4gaXQ/CgpJIGFzc3VtZSBp dCdzIGEgc3BlZWQgb3B0aW1pc2F0aW9uLCBhdm9pZGluZyBzZXR0aW5nIHVwIGFuIGV4Y2VwdGlv bgpoYW5kbGVyIGluIHRoZSBmYXN0IHBhdGggYnV0IGF0IHRoZSBjb3N0IG9mIG1ha2luZyAocmFp c2VkKSBleGNlcHRpb25zCmxlc3MgcHJlZGljdGFibGUuIFdoZXRoZXIgdGhpcyB0cmFkZS1vZmYg aXMgd29ydGggaXQsIEkgZG9uJ3Qga25vdy4KClRoZSBjYXNlIHdoZXJlIGl0IG1ha2VzIGEgZGlm ZmVyZW5jZSBpcyB3aGVuIHlvdSBzdGFydCBhIHRocmVhZAp3aXRob3V0IHdhaXRpbmcgZm9yIGl0 IGFuZCB0aGVuIGdldCBvbiB3aXRoIHNvbWV0aGluZyBlbHNlOgoKbGV0IHByb2Nlc3MgeCA9CiAg bGV0IGEgPSAoeCA+Pj0gZikgaW4KICBzdHVmZiAoKSA+Pj0gZnVuICgpIC0+CiAgYQoKSWYgeCBp cyBhbHJlYWR5IHJldHVybmVkICphbmQqIGYgaW1tZWRpYXRlbHkgdGhyb3dzIChyYXRoZXIgdGhh biB1c2luZwpmYWlsKSB0aGVuIHdlIGFib3J0IGJlZm9yZSBjYWxsaW5nIHN0dWZmLCBvdGhlcndp c2Ugd2UgY2FsbCBpdCBhbmQKdGhlbiByZXNvbHZlIHRvIGEgZmFpbGVkIHRocmVhZCBsYXRlci4K CkVpdGhlciBiZWhhdmlvdXIgaXMgInNhZmUiLCBpbiB0aGF0IHdlIGRvbid0IGxlYWsgcmVzb3Vy Y2VzLiBUaGUgY2FzZQp3ZSByZWFsbHkgbmVlZCB0byBhdm9pZCBpcyB3aGVyZSB3ZSByZXR1cm4g YSB0aHJlYWQgdGhhdCB3aWxsIG5ldmVyCnJlc29sdmUsIHNpbmNlIGFueXRoaW5nIHRoYXQgd2Fp dHMgb24gdGhhdCB3aGlsZSBob2xkaW5nIHNvbWUgcmVzb3VyY2UKd2lsbCBsZWFrIGl0LiBMd3Qu YmluZCBvbmx5IGNyZWF0ZXMgc3VjaCBhIHRocmVhZCAocmVzKSBpbiB0aGUgU2xlZXAKY2FzZSwg c28gb25seSB0aGF0IHRyeS4ud2l0aCBpcyB2aXRhbC4KCj4+ID4gVGhlcmUgYXJlIGhvd2V2ZXIg ZXJyb3JzIHRoYXQgeW91IHdhbnQgdG8gbWFuZGF0ZSB0aGF0IHRoZXkgYXJlIGRlYWx0Cj4+ID4g d2l0aCBidXQgbm90IG5lY2Vzc2FyaWx5IGF0IHRoZSBjYWxsaW5nIHBvaW50LiAgQSB0eXBpY2Fs IGV4YW1wbGUgdG8KPj4gPiBtZSBpcyDigJxyZWFk4oCdIGJlY2F1c2UgaXQgaXMgb2Z0ZW4gbXVj aCAiaGlnaGVyIiBpbiB0aGUgcHJvZ3JhbSB0aGF0IGFuCj4+ID4gYXBwcm9wcmlhdGUgcmVzcG9u c2UgdG8gYSBmYWlsaW5nIHJlYWQgY2FuIGJlIG1hZGUg4oCUIHRoaXMgaXMgaW1wb3J0YW50Cj4+ ID4gZm9yIGxpYnJhcmllcyB0aGF0IHdpbGwgcG9zdC1wcm9jZXNzIOKAnHJlYWTigJ1zIGFuZCB3 aWxsIGhhdmUgbm8gaWRlYQo+PiA+IHdoYXQgdG8gZG8gaWYg4oCccmVhZOKAnSBmYWlscy4KPj4K Pj4gWWVzLCB0aGlzIGlzIGEgY2FzZSB3aGVyZSB5b3UgbWlnaHQgd2FudCBhbiBPcl9lcnJvci50 IHRocmVhZGVkCj4+IHRocm91Z2ggZXZlcnl0aGluZy4gT3IsIGl0IG1pZ2h0IGJlIGVhc2llciB0 byB3cmFwIHRoZSB3aG9sZSB0aGluZwo+PiBzbyB0aGF0IGFueSBlcnJvciBjb2RlIHJldHVybmVk IGJ5IHRoZSByZWFkIGlzIHRocm93biBhbmQgdGhlbgo+PiBjYXVnaHQgYWdhaW4uCj4KPiBUaGUg cHJvYmxlbSB3aXRoIE9yX2Vycm9yLnQgaXMgdGhhdCB5b3UgaGF2ZSB0byB3cml0ZSB0ZWRpb3Vz IGNvZGUgdG8KPiBwcm9wYWdhdGUgaXQgYXQgZXZlcnkgYmluZC4gIElmIHdlIGFkb3B0IHRoaXMs IGFuIGJpbmQgaW5maXggb3BlcmF0b3IKPiB0aGF0IHByb3BhZ2F0ZXMgdGhlIGVycm9yIGF1dG9t YXRpY2FsbHkgaXMgcmVhbGx5IG5lZWRlZCAodHJ5aW5nIHRvCj4gY2F0Y2ggd2l0aCB0b2RheSdz IG1lc3NhZ2VzLCBJIHNlZSB0aGF0ID4+PT8gaXMgYWxyZWFkeSB1c2VkIGZvciB0aGF0Cj4gcHVy cG9zZSkuICBBbHNvLCB3aXRoIE9yX2Vycm9yLnQgKG9yIGV4Y2VwdGlvbnMpLCB0aGVyZSBpcyBu byB3YXkgdG8KPiBlbnN1cmUgdGhhdCB0aGUgZXJyb3IgaXMgZXZlbnR1YWxseSBhY3RlZCB1cG9u IHNvIHdoeSBub3QgdG8gc2ltcGx5Cj4gdXNlIOKAnGZhaWzigJ0/CgpUaGF0IG1ha2VzIHNlbnNl IHRvIG1lLiBBcmd1YWJseSwgTHd0J3MgPj49IGlzIGFscmVhZHkgdGhlCmVycm9yLXByb3BhZ2F0 aW5nID4+PT8sIGFuZCBmb3IgcGVvcGxlIHdobyB3YW50IHRvIGhhbmRsZSBlcnJvcnMgd2UKc2hv dWxkIHByb3ZpZGUgYW4gb3BlcmF0b3IgdGhhdCBleHBvc2VzIEZhaWwgYW5kIFJldHVybiB1c2lu ZyBhCk9yX2Vycm9yLnQuCgo+PiBUaGUgcHJvYmxlbSB3ZSBoYXZlIGluIE1pcmFnZSBpcyB0aGF0 IG91ciB0eXBlcyBhcmUgYWJzdHJhY3QuIEZvcgo+PiBleGFtcGxlLCBpZiB5b3UgaGF2ZSBhIGZ1 bmN0b3IKPj4KPj4gICBtb2R1bGUgRlMgKEIgOiBCTE9DSykgID0gLi4uCj4+Cj4+IHRoZW4gdGhl IGF1dGhvciBvZiB0aGUgRlMgZnVuY3RvciBkb2Vzbid0IGtub3cgZXhhY3RseSB3aGF0IGVycm9y cyB0aGUKPj4gY29uY3JldGUgQiBtaWdodCB0aHJvdy4gRm9yIGV4YW1wbGUsIGlmIEIgaXMgYSBy ZW1vdGUgZGlzayB0aGVuIGl0Cj4+IG1pZ2h0IHRocm93IG5ldHdvcmsgZXJyb3JzLiBTbyBlbnN1 cmluZyB0aGF0IGNhbGxlcnMgZW51bWVyYXRlIGFsbAo+PiBlcnJvcnMgaXNuJ3QgdmVyeSBoZWxw ZnVsIGluIHRoaXMgY2FzZS4KPj4KPj4gWW91IGNhbiBnaXZlIEZTIGFuIGVycm9yIGNvZGUgb2Yg W2BCbG9ja19lcnJvciBvZiBCLmVycm9yXSBhbmQganVzdAo+PiBwcm9wYWdhdGUgaXQgdG8gdGhl IGNhbGxlciwgd2hpY2ggaXMgd2hhdCB3ZSBkbyBub3cuIFRoYXQgc2VlbXMgcXVpdGUKPj4gY2xl dmVyLCBidXQgSSdtIHN0cnVnZ2xpbmcgdG8gaW1hZ2luZSBhIGNhc2Ugd2hlcmUgaXQncyBhY3R1 YWxseQo+PiB1c2VmdWwuCj4KPiBUaGF0J3Mgd2hhdCBJIHdhcyBnb2luZyB0byBzdWdnZXN0Li4u ICBEZWNsYXJpbmcgc2V2ZXJhbCBgQmxvY2tfZXJyb3IKPiBpZiBuZWNlc3NhcnkgYWxsb3dzIHRv IGFjdCBvbiAiY2xhc3NlcyIgb2YgZXJyb3JzIOKAlCB3aGljaCBpcyBhbGwgb25lCj4gY2FuIGhv cGUgZm9yIGdpdmVuIHRoZSBhYnN0cmFjdGlvbi4KPgo+PiBJdCdzIHByb2JhYmx5IHdvcnRoIGNv bXBpbGluZyBhIGxpc3Qgb2YgZXhhbXBsZXMgd2hlcmUgTWlyYWdlIGNvZGUKPj4gY3VycmVudGx5 IG1hdGNoZXMgb24gc3BlY2lmaWMgcmV0dXJuZWQgRXJyb3IgY29kZXMgYW5kIHRha2VzIHNwZWNp ZmljCj4+IGFjdGlvbnMuIE15IGd1ZXNzIGlzIHRoZXJlIGFyZW4ndCBlbm91Z2ggdG8ganVzdGlm eSB0aGUgY29tcGxleGl0eQo+PiB0aG91Z2guCj4KPiBUaGF0IHdvdWxkIGJlIG5pY2UuICBJIGRv bid0IGhhdmUgbXVjaCBmYW1pbGlhcml0eSB3aXRoIGEgbG90IG9mIHBhcnRzCj4gb2YgTWlyYWdl IHNvIEkgbWF5IGJlIG1pc3NpbmcgdXNlIGNhc2VzLiAgQXMgSSB1bmRlcnN0YW5kIHRoZQo+IGRp c2N1c3Npb24sIE1pcmFnZSBjb2RlIHNob3VsZCBiZSByZXZpc2l0ZWQsIG5vdCBvbmx5IHRvIHNl ZSBob3cKPiB0aGluZ3MgYXJlIGRvbmUgbm93IGJ1dCBhbHNvIHdoYXQgdGhlIHByb2JsZW1zIGFy ZSAod2l0aCB0aGUgY3VycmVudAo+IHNjaGVtZSkgYW5kIHdoYXQgcHJvcGVydGllcyBvZiB0aGUg ZXJyb3IgaGFuZGxpbmcgd2Ugd291bGQgbGlrZSBpbgo+IHRoZXNlIGNhc2VzLgoKTWlnaHQgYmUg dXNlZnVsIHRvIGFkZCBzb21lIHRlc3QgY2FzZXMgdG8gdGhlIGRvY3VtZW50YXRpb24uIEZvcgpl eGFtcGxlLCB0cnlpbmcgdG8gY29ubmVjdCB0byBhIGRpc2sgbm93IHJlc3VsdHMgaW4gZS5nLgoK RmF0YWwgZXJyb3I6IGV4Y2VwdGlvbiBGYWlsdXJlKCJibG9jazEiKQoKSWRlYWxseSwgSSdkIHdh bnQgc29tZXRoaW5nIGxpa2U6CgpCbG9jay5jb25uZWN0OiB1bmFibGUgdG8gbWF0Y2gKJy9ob21l L21pcmFnZS9taXJhZ2Utc2tlbGV0b24vYmxvY2svZGlzay5pbWcnIHRvIGFueSBhdmFpbGFibGUg WGVuCmRpc2sgKGF2YWlsYWJsZTogJ3h2ZGExJykKLi4uIGF0dGVtcHRpbmcgdG8gY29ubmVjdCAi YmxvY2sxIgoKQ3VycmVudGx5LCB3ZSB3b3JrIGFyb3VuZCB0aGlzIHVzaW5nICJwcmludGYiIGNh bGxzIGluIGxpYnJhcmllcywgc28KaG9wZWZ1bGx5IHRoZSB1c2VyIHdpbGwgc2VlIHRoZSByZWFs IGNhdXNlIGluIHRoZSBjb25zb2xlIG91dHB1dCwgYnV0CnRoYXQncyBub3QgaWRlYWwuIEluIGEg YnVzeSBzeXN0ZW0sIHRyeWluZyB0byBjb3JyZWxhdGUgbWVzc2FnZXMKbG9nZ2VkIGF0IHZhcmlv dXMgcG9pbnRzIGluIHRoZSBsb2cgZmlsZXMgaXNuJ3QgZnVuLgoKPj4gWy4uLl0gaW4gZXZlcnkg b25lIG9mIHRoZXNlIGNhc2VzIHdoZXJlIHdlIG1hdGNoIG9uIGFuIGBFcnJvciwgd2UganVzdAo+ PiBwcm9wYWdhdGUgaXQgKGkuZS4gdGhlIGRlZmF1bHQgYmVoYXZpb3VyIG9mIGFuIGV4Y2VwdGlv biB3b3VsZCBoYXZlCj4+IGJlZW4gY29ycmVjdCkuCj4+Cj4+IEhlcmUgYXJlIHNvbWUgZXhhbXBs ZXM6Cj4+Cj4+IHwgYEVycm9yIChgSW52YWxpZF9jb25zb2xlIHgpIC0+IGZhaWwgKEZhaWx1cmUg KFByaW50Zi5zcHJpbnRmICJJbnZhbGlkX2NvbnNvbGUgJXMiIHgpKQo+PiB8IGBFcnJvciAoYEJs b2NrX2RldmljZSBlKSAtPiBmYWlsIChGYWlsdXJlIChGcy5zdHJpbmdfb2ZfYmxvY2tfZXJyb3Ig ZSkpCj4+IHwgYEVycm9yIChLVi5Vbmtub3duX2tleSBrZXkpIC0+IGZhaWwgKEludmFsaWRfYXJn dW1lbnQga2V5KQo+PiB8IGBFcnJvciAoYFVua25vd24gbXNnKSAtPiBMd3QuZmFpbCAoRmFpbHVy ZSBtc2cpCj4KPiBJIGRvbid0IHVuZGVyc3RhbmQgdGhlIHBvaW50IG9mIHRoaXMgdHlwZSBvZiBj b2RlLiAgV2h5IHdhc24ndCDigJxFcnJvcuKAnQo+IGRlY2xhcmVkIGFzIGFuIGV4Y2VwdGlvbiAo cG9zc2libHkgd2l0aCBhbiBleGNlcHRpb24gcHJpbnRlcikgYW5kCj4g4oCcZmFpbOKAnSBkaXJl Y3RseSBpbnZva2VkIG9uIGl0PyAgVGhpcyBhbHNvIGhpZ2hsaWdodHMgdGhhdCBwZW9wbGUgc2h5 Cj4gYXdheSBmcm9tIGhhdmluZyB0byBoYW5kbGUgZXZlbiBhIHNpbXBsZSBgRXJyb3IgdG8gdGhl IHBvaW50IHRoYXQgaXQKPiBzZWVtcyBwcmVmZXJhYmxlIHRvIGRlZ2VuZXJhdGUgaXQgYXMgYSBz dHJpbmchCgpZZXMsIHRoaXMgaXMgdGhlIGtpbmQgb2YgY29kZSBJJ2QgbGlrZSB0byBnZXQgcmlk IG9mLgoKPj4gVGhlIG9ubHkgY2FzZSB3aGVyZSB3ZSBkbyBzb21ldGhpbmcgaW50ZXJlc3Rpbmcg aXMgYEVycm9yIChVbmtub3duX2tleQo+PiBfKSwgd2hlcmUgd2Ugbm90ZSB0aGF0IGl0IHdhcyBh IHJlYWQ6Cj4+Cj4+IHwgYEVycm9yIChUTVBMLlVua25vd25fa2V5IF8pIC0+IGZhaWwgKEZhaWx1 cmUgKCJyZWFkICIgXiBuYW1lKSkKPj4KPj4gSG93ZXZlciwgVW5rbm93bl9rZXkgd291bGRuJ3Qg YmUgYW4gZXhjZXB0aW9uIHVuZGVyIGFueSBwcm9wb3NlZCBzY2hlbWUgYW55d2F5Cj4KPiBJbiB0 aGUgcHJldmlvdXMgZGlzY3Vzc2lvbiwgSSBoYWQgdGhlIGltcHJlc3Npb24gdGhhdCBoYXZpbmcg YSBzY2hlbWUKPiB0byBwcm9wYWdhdGUgZXJyb3JzIHNlYW1sZXNzbHkgd2hpbGUgZm9yY2luZyBj ZXJ0YWluIChjbGFzc2VzIG9mKQo+IGVycm9ycyB0byBiZSBoYW5kbGVkIGJlZm9yZSB0aGV5IHJl YWNoIHRoZSBtYWluIGxvb3Agd2FzIGltcG9ydGFudC4KPiBJZiB3ZSBkbyBub3QgY2FyZSBhYm91 dCB0aGlzLCB3aGF0IGlzIHdyb25nIHdpdGggdGhlIOKAnGZhaWzigJ0gbWVjaGFuaXNtCj4gb2Yg THd0PwoKSXQncyBub3QgeWV0IGNsZWFyIHdoZXRoZXIgd2Ugc2hvdWxkIGNhcmUgYWJvdXQgaXQg b3Igbm90LiBNeSBjdXJyZW50CmZlZWxpbmcgaXMgdGhhdCB3ZSBzaG91bGRuJ3QsIGFuZCBzaG91 bGQgaW5zdGVhZCBhZG9wdCBhbiBFcmxhbmctc3R5bGUKImxldCBpdCBjcmFzaCIgcG9saWN5LCB3 aXRoIGEgZ2VuZXJpYyBleGNlcHRpb24gaGFuZGxlciBpbiB0aGUgSFRUUApzZXJ2ZXIgYW5kIGFu eSBzaW1pbGFyIHBvbGxpbmcgbG9vcHMgKHdoaWNoIGFwcGVhcnMgdG8gYmUgZWZmZWN0aXZlbHkK d2hhdCB3ZSdyZSBkb2luZyBhbnl3YXksIHNpbmNlIHdlIGFsd2F5cyBzZWVtIHRvIHVzZSBhbiBl eGNlcHRpb24gaW4KdGhlIGVuZCkuCgpIb3dldmVyLCB0aGVyZSBpcyBhbiBhcmd1bWVudCB0aGF0 IGl0IGlzIG1vcmUgY29ycmVjdCB0byBjb25zaWRlcgplcnJvcnMgd2hlcmUgdGhleSBvY2N1ciBh bmQgZGVjaWRlIGhvdyB0byBoYW5kbGUgdGhlbSBhdCBlYWNoIHBvaW50LgpJZiB0aGVyZSdzIGEg d2F5IHRvIGxldCBwZW9wbGUgd2hvIHdhbnQgdG8gY2F0Y2ggYW5kIGhhbmRsZSBpbmRpdmlkdWFs CmVycm9ycyBkbyBzbyByZWxpYWJseSwgd2l0aG91dCBhZGRpbmcgc28gbXVjaCBib2lsZXJwbGF0 ZSB0aGF0IHdlIGFkZAptb3JlIGJ1Z3MgdGhhbiB3ZSByZW1vdmUsIEknbSBoYXBweSB0byBoZWFy IGl0LgoKVGhlcmUgYXJlIHNvbWUgdGhpbmcgdGhhdCBzaG91bGQgY2VydGFpbmx5IGJlIGVycm9y IGNvZGVzCihVbmtub3duX2tleSkgYW5kIHNvbWUgdGhpbmdzIHRoYXQgSSB0aGluayBjZXJ0YWlu bHkgc2hvdWxkIGJlCmV4Y2VwdGlvbnMgKGBVbmtub3duKSwgYnV0IHRoZSBvbmVzIGluIHRoZSBt aWRkbGUgKGBEaXNjb25uZWN0ZWQpIGFyZQpsZXNzIG9idmlvdXMuCgpQcm9iYWJseSBpdCBkb2Vz bid0IG1hdHRlciB0b28gbXVjaC4gSWYgRGlzY29ubmVjdGVkIGlzIGFuIGVycm9yIGNvZGUKaXQn cyBub3QgYSBiaWcgcHJvYmxlbSwgcHJvdmlkZWQgSSBjYW4gZWFzaWx5IHR1cm4gaXQgaW50byBh bgpleGNlcHRpb24gaWYgaXQgcmVhbGx5IGlzbid0IGEgY2FzZSBJIHdhbnQgdG8gaGFuZGxlLiBB bmQgaWYgaXQncyBhbgpleGNlcHRpb24gdGhlbiB0aGF0J3MgZmluZSwgYXMgbG9uZyBhcyBJIGNh biBlYXNpbHkgY2F0Y2ggaXQgYW5kCmhhbmRsZSBpdC4KCgotLSAKRHIgVGhvbWFzIExlb25hcmQg ICAgICAgIGh0dHA6Ly8waW5zdGFsbC5uZXQvCkdQRzogOTI0MiA5ODA3IEM5ODUgM0MwNyA0NEE2 ICA4QjlBIEFFMDcgODI4MCA1OUE1IDNDQzEKR1BHOiBEQTk4IDI1QUUgQ0FEMCA4OTc1IDdDREEg IEJEOEUgMDcxMyAzRjk2IENBNzQgRDhCQQoKX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX18KTWlyYWdlT1MtZGV2ZWwgbWFpbGluZyBsaXN0Ck1pcmFnZU9TLWRl dmVsQGxpc3RzLnhlbnByb2plY3Qub3JnCmh0dHA6Ly9saXN0cy54ZW5wcm9qZWN0Lm9yZy9jZ2kt YmluL21haWxtYW4vbGlzdGluZm8vbWlyYWdlb3MtZGV2ZWwK From mirageos-devel-bounces@lists.xenproject.org Wed Feb 04 11:52:33 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 04 Feb 2015 11:52:33 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YIyVU-0003OL-6R; Wed, 04 Feb 2015 11:52:32 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YIyVT-0003OB-4w for mirageos-devel@lists.xenproject.org; Wed, 04 Feb 2015 11:52:31 +0000 Received: from [85.158.139.211] by server-16.bemta-5.messagelabs.com id 13/05-02804-EF702D45; Wed, 04 Feb 2015 11:52:30 +0000 X-Env-Sender: talex5@gmail.com X-Msg-Ref: server-12.tower-206.messagelabs.com!1423050749!11084997!1 X-Originating-IP: [209.85.217.181] X-SpamReason: No, hits=0.8 required=7.0 tests=BODY_RANDOM_LONG, RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8666 invoked from network); 4 Feb 2015 11:52:29 -0000 Received: from mail-lb0-f181.google.com (HELO mail-lb0-f181.google.com) (209.85.217.181) by server-12.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 4 Feb 2015 11:52:29 -0000 Received: by mail-lb0-f181.google.com with SMTP id u10so1002158lbd.12 for ; Wed, 04 Feb 2015 03:52:28 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=4hKLhz1uY5snnnyUG2GHxxHWYuQGJ0mvvibt8U82bLk=; b=BV5Sj2GC3rGV7eRTdsbl4dsmoC4yuPem8UaVbu0rjpCQAV/7o4PzvfDNpN43KxtrVd 88RSPPaGCjK6F55A+15uWLirN3sKC0jiSOQaf/BYjTV0X6J6rRL8r3tZ7D9qvePTOIDE UH3TUHn79wDsXiPFPdpl1YgIdO2MqTNIqFWkAyvs2fidDcMbhjPANRUlur0sgVkE94JJ dAJea6uQVNXo7IKynIV6EwzhM9CJpvi0gRnbQFiUqpzQpvbWn3l5UmIxVMSMsIAd/V57 TARV7kgx/YYsIuY5u2F/6JabTfQlwO7q2uK3JnlQYCr8w+3VK7UYstehG+B4fcFWGuBl dTag== MIME-Version: 1.0 X-Received: by 10.152.183.196 with SMTP id eo4mr30143358lac.0.1423050748653; Wed, 04 Feb 2015 03:52:28 -0800 (PST) Received: by 10.25.207.206 with HTTP; Wed, 4 Feb 2015 03:52:28 -0800 (PST) In-Reply-To: <20150204.001614.26478837567139584.Christophe.Troestler@umons.ac.be> References: <20150202.014549.1883720051237442569.Christophe.Troestler@umons.ac.be> <20150204.001614.26478837567139584.Christophe.Troestler@umons.ac.be> Date: Wed, 4 Feb 2015 11:52:28 +0000 Message-ID: From: Thomas Leonard To: Christophe Troestler Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Error handling in Mirage - request for comments! X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org T24gMyBGZWJydWFyeSAyMDE1IGF0IDIzOjE2LCBDaHJpc3RvcGhlIFRyb2VzdGxlcgo8Q2hyaXN0 b3BoZS5Ucm9lc3RsZXJAdW1vbnMuYWMuYmU+IHdyb3RlOgo+IE9uIE1vbiwgMiBGZWIgMjAxNSAx MjozMDozOSArMDAwMCwgVGhvbWFzIExlb25hcmQgd3JvdGU6Cj4+Cj4+IE9uIDIgRmVicnVhcnkg MjAxNSBhdCAwMDo0NSwgQ2hyaXN0b3BoZSBUcm9lc3RsZXIKPj4gPENocmlzdG9waGUuVHJvZXN0 bGVyQHVtb25zLmFjLmJlPiB3cm90ZToKPj4gPiBPbiBTYXQsIDMxIEphbiAyMDE1IDIxOjA3OjIy ICswMDAwLCBUaG9tYXMgTGVvbmFyZCB3cm90ZToKPj4gPj4KPj4gPj4gW+KApl0gQnV0IHRoZSBy ZWFsIHByb2JsZW0gaGVyZSBpcyB0aGF0IGJ5IG1ha2luZyBleGNlcHRpb25zIGZhdGFsIHdlCj4+ ID4+IHR1cm4gZXZlcnkgZXhjZXB0aW9uIHVzZWQgaW4gZXhpc3RpbmcgT0NhbWwgY29kZSBpbnRv IGEgc2VjdXJpdHkKPj4gPj4gdnVsbmVyYWJpbGl0eS4gW+KApl0KPj4gPgo+PiA+IFNpbmNlIE9D YW1sIHN1cHBvcnRzIGV4Y2VwdGlvbnMsIEkgdGhpbmsgdGhlcmUgaXMgbm8gZG91YnQgdGhhdCB3 ZQo+PiA+IG11c3QgaGFuZGxlIHRoZW0gZWZmZWN0aXZlbHkg4oCUIG5vdCBqdXN0IHdpcGUgdGhl bSB1bmRlciB0aGUgY2FycGV0IGFuZAo+PiA+IGxldCB0aGVtIGFib3J0IHRoZSBwcm9ncmFtL3Vu aWtlcm5lbC4gIElkZWFsbHkgTHd0IHNob3VsZCBkZWFsCj4+ID4gc2Vuc2libHkgd2l0aCBleGNl cHRpb25zIChhbmQgdGhlIGRpc2N1c3Npb24gc2VlbXMgdG8gaW1wbHkgdGhlcmUgYXJlCj4+ID4g YXJlYXMgb2YgaW1wcm92ZW1lbnQg4oCUIGJ1dCBpdCBpcyB1bmNsZWFyIHRvIG1lIGhvdyB5b3Ug Y2FuIGRvIHRoYXQKPj4gPiBlZmZpY2llbnRseSB3aXRob3V0IHVzaW5nIGEgdHJ5IGJsb2NrIGlu IGFsbCBiaW5kcykuCj4+Cj4+IEx3dCBhbHJlYWR5IHB1dHMgYSB0cnkgYmxvY2sgaW4gYWxsIChz bGVlcGluZykgYmluZHMsIHNvIHRoaXMgaXMKPj4gaGFuZGxlZCBmb3IgeW91Ogo+Pgo+PiBsZXQg YmluZCB0IGYgPQo+PiAgIGxldCB0ID0gcmVwciB0IGluCj4+ICAgbWF0Y2ggdC5zdGF0ZSB3aXRo Cj4+ICAgICB8IFJldHVybiB2IC0+Cj4+ICAgICAgICAgZiB2Cj4+ICAgICB8IEZhaWwgXyBhcyBz dGF0ZSAtPgo+PiAgICAgICAgIHRocmVhZCB7IHN0YXRlIH0KPj4gICAgIHwgU2xlZXAgc2xlZXBl ciAtPgo+PiAgICAgICAgIGxldCByZXMgPSB0ZW1wIHQgaW4KPj4gICAgICAgICBsZXQgZGF0YSA9 ICFjdXJyZW50X2RhdGEgaW4KPj4gICAgICAgICBhZGRfaW1tdXRhYmxlX3dhaXRlciBzbGVlcGVy Cj4+ICAgICAgICAgICAoZnVuY3Rpb24KPj4gICAgICAgICAgICAgIHwgUmV0dXJuIHYgLT4gY3Vy cmVudF9kYXRhIDo9IGRhdGE7IGNvbm5lY3QgcmVzICh0cnkgZiB2Cj4+IHdpdGggZXhuIC0+IGZh aWwgZXhuKQo+PiAgICAgICAgICAgICAgfCBGYWlsIF8gYXMgc3RhdGUgLT4gZmFzdF9jb25uZWN0 IHJlcyBzdGF0ZQo+PiAgICAgICAgICAgICAgfCBfIC0+IGFzc2VydCBmYWxzZSk7Cj4+ICAgICAg ICAgcmVzCj4KPiBUaGFua3MgZm9yIGNoZWNraW5nLiAgQXQgZmlyc3QsIHRoZSBkaWZmZXJlbmNl IG9mIHRyZWF0bWVudCBiZXR3ZWVuCj4gdGhlIHR3byDigJxmIHbigJ0gaXMgYSBsaXR0bGUgb2Rk LiAgRG8geW91IGhhcHBlbiB0byBrbm93IHRoZSByZWFzb24gZm9yCj4gaXQ/CgpJIGFzc3VtZSBp dCdzIGEgc3BlZWQgb3B0aW1pc2F0aW9uLCBhdm9pZGluZyBzZXR0aW5nIHVwIGFuIGV4Y2VwdGlv bgpoYW5kbGVyIGluIHRoZSBmYXN0IHBhdGggYnV0IGF0IHRoZSBjb3N0IG9mIG1ha2luZyAocmFp c2VkKSBleGNlcHRpb25zCmxlc3MgcHJlZGljdGFibGUuIFdoZXRoZXIgdGhpcyB0cmFkZS1vZmYg aXMgd29ydGggaXQsIEkgZG9uJ3Qga25vdy4KClRoZSBjYXNlIHdoZXJlIGl0IG1ha2VzIGEgZGlm ZmVyZW5jZSBpcyB3aGVuIHlvdSBzdGFydCBhIHRocmVhZAp3aXRob3V0IHdhaXRpbmcgZm9yIGl0 IGFuZCB0aGVuIGdldCBvbiB3aXRoIHNvbWV0aGluZyBlbHNlOgoKbGV0IHByb2Nlc3MgeCA9CiAg bGV0IGEgPSAoeCA+Pj0gZikgaW4KICBzdHVmZiAoKSA+Pj0gZnVuICgpIC0+CiAgYQoKSWYgeCBp cyBhbHJlYWR5IHJldHVybmVkICphbmQqIGYgaW1tZWRpYXRlbHkgdGhyb3dzIChyYXRoZXIgdGhh biB1c2luZwpmYWlsKSB0aGVuIHdlIGFib3J0IGJlZm9yZSBjYWxsaW5nIHN0dWZmLCBvdGhlcndp c2Ugd2UgY2FsbCBpdCBhbmQKdGhlbiByZXNvbHZlIHRvIGEgZmFpbGVkIHRocmVhZCBsYXRlci4K CkVpdGhlciBiZWhhdmlvdXIgaXMgInNhZmUiLCBpbiB0aGF0IHdlIGRvbid0IGxlYWsgcmVzb3Vy Y2VzLiBUaGUgY2FzZQp3ZSByZWFsbHkgbmVlZCB0byBhdm9pZCBpcyB3aGVyZSB3ZSByZXR1cm4g YSB0aHJlYWQgdGhhdCB3aWxsIG5ldmVyCnJlc29sdmUsIHNpbmNlIGFueXRoaW5nIHRoYXQgd2Fp dHMgb24gdGhhdCB3aGlsZSBob2xkaW5nIHNvbWUgcmVzb3VyY2UKd2lsbCBsZWFrIGl0LiBMd3Qu YmluZCBvbmx5IGNyZWF0ZXMgc3VjaCBhIHRocmVhZCAocmVzKSBpbiB0aGUgU2xlZXAKY2FzZSwg c28gb25seSB0aGF0IHRyeS4ud2l0aCBpcyB2aXRhbC4KCj4+ID4gVGhlcmUgYXJlIGhvd2V2ZXIg ZXJyb3JzIHRoYXQgeW91IHdhbnQgdG8gbWFuZGF0ZSB0aGF0IHRoZXkgYXJlIGRlYWx0Cj4+ID4g d2l0aCBidXQgbm90IG5lY2Vzc2FyaWx5IGF0IHRoZSBjYWxsaW5nIHBvaW50LiAgQSB0eXBpY2Fs IGV4YW1wbGUgdG8KPj4gPiBtZSBpcyDigJxyZWFk4oCdIGJlY2F1c2UgaXQgaXMgb2Z0ZW4gbXVj aCAiaGlnaGVyIiBpbiB0aGUgcHJvZ3JhbSB0aGF0IGFuCj4+ID4gYXBwcm9wcmlhdGUgcmVzcG9u c2UgdG8gYSBmYWlsaW5nIHJlYWQgY2FuIGJlIG1hZGUg4oCUIHRoaXMgaXMgaW1wb3J0YW50Cj4+ ID4gZm9yIGxpYnJhcmllcyB0aGF0IHdpbGwgcG9zdC1wcm9jZXNzIOKAnHJlYWTigJ1zIGFuZCB3 aWxsIGhhdmUgbm8gaWRlYQo+PiA+IHdoYXQgdG8gZG8gaWYg4oCccmVhZOKAnSBmYWlscy4KPj4K Pj4gWWVzLCB0aGlzIGlzIGEgY2FzZSB3aGVyZSB5b3UgbWlnaHQgd2FudCBhbiBPcl9lcnJvci50 IHRocmVhZGVkCj4+IHRocm91Z2ggZXZlcnl0aGluZy4gT3IsIGl0IG1pZ2h0IGJlIGVhc2llciB0 byB3cmFwIHRoZSB3aG9sZSB0aGluZwo+PiBzbyB0aGF0IGFueSBlcnJvciBjb2RlIHJldHVybmVk IGJ5IHRoZSByZWFkIGlzIHRocm93biBhbmQgdGhlbgo+PiBjYXVnaHQgYWdhaW4uCj4KPiBUaGUg cHJvYmxlbSB3aXRoIE9yX2Vycm9yLnQgaXMgdGhhdCB5b3UgaGF2ZSB0byB3cml0ZSB0ZWRpb3Vz IGNvZGUgdG8KPiBwcm9wYWdhdGUgaXQgYXQgZXZlcnkgYmluZC4gIElmIHdlIGFkb3B0IHRoaXMs IGFuIGJpbmQgaW5maXggb3BlcmF0b3IKPiB0aGF0IHByb3BhZ2F0ZXMgdGhlIGVycm9yIGF1dG9t YXRpY2FsbHkgaXMgcmVhbGx5IG5lZWRlZCAodHJ5aW5nIHRvCj4gY2F0Y2ggd2l0aCB0b2RheSdz IG1lc3NhZ2VzLCBJIHNlZSB0aGF0ID4+PT8gaXMgYWxyZWFkeSB1c2VkIGZvciB0aGF0Cj4gcHVy cG9zZSkuICBBbHNvLCB3aXRoIE9yX2Vycm9yLnQgKG9yIGV4Y2VwdGlvbnMpLCB0aGVyZSBpcyBu byB3YXkgdG8KPiBlbnN1cmUgdGhhdCB0aGUgZXJyb3IgaXMgZXZlbnR1YWxseSBhY3RlZCB1cG9u IHNvIHdoeSBub3QgdG8gc2ltcGx5Cj4gdXNlIOKAnGZhaWzigJ0/CgpUaGF0IG1ha2VzIHNlbnNl IHRvIG1lLiBBcmd1YWJseSwgTHd0J3MgPj49IGlzIGFscmVhZHkgdGhlCmVycm9yLXByb3BhZ2F0 aW5nID4+PT8sIGFuZCBmb3IgcGVvcGxlIHdobyB3YW50IHRvIGhhbmRsZSBlcnJvcnMgd2UKc2hv dWxkIHByb3ZpZGUgYW4gb3BlcmF0b3IgdGhhdCBleHBvc2VzIEZhaWwgYW5kIFJldHVybiB1c2lu ZyBhCk9yX2Vycm9yLnQuCgo+PiBUaGUgcHJvYmxlbSB3ZSBoYXZlIGluIE1pcmFnZSBpcyB0aGF0 IG91ciB0eXBlcyBhcmUgYWJzdHJhY3QuIEZvcgo+PiBleGFtcGxlLCBpZiB5b3UgaGF2ZSBhIGZ1 bmN0b3IKPj4KPj4gICBtb2R1bGUgRlMgKEIgOiBCTE9DSykgID0gLi4uCj4+Cj4+IHRoZW4gdGhl IGF1dGhvciBvZiB0aGUgRlMgZnVuY3RvciBkb2Vzbid0IGtub3cgZXhhY3RseSB3aGF0IGVycm9y cyB0aGUKPj4gY29uY3JldGUgQiBtaWdodCB0aHJvdy4gRm9yIGV4YW1wbGUsIGlmIEIgaXMgYSBy ZW1vdGUgZGlzayB0aGVuIGl0Cj4+IG1pZ2h0IHRocm93IG5ldHdvcmsgZXJyb3JzLiBTbyBlbnN1 cmluZyB0aGF0IGNhbGxlcnMgZW51bWVyYXRlIGFsbAo+PiBlcnJvcnMgaXNuJ3QgdmVyeSBoZWxw ZnVsIGluIHRoaXMgY2FzZS4KPj4KPj4gWW91IGNhbiBnaXZlIEZTIGFuIGVycm9yIGNvZGUgb2Yg W2BCbG9ja19lcnJvciBvZiBCLmVycm9yXSBhbmQganVzdAo+PiBwcm9wYWdhdGUgaXQgdG8gdGhl IGNhbGxlciwgd2hpY2ggaXMgd2hhdCB3ZSBkbyBub3cuIFRoYXQgc2VlbXMgcXVpdGUKPj4gY2xl dmVyLCBidXQgSSdtIHN0cnVnZ2xpbmcgdG8gaW1hZ2luZSBhIGNhc2Ugd2hlcmUgaXQncyBhY3R1 YWxseQo+PiB1c2VmdWwuCj4KPiBUaGF0J3Mgd2hhdCBJIHdhcyBnb2luZyB0byBzdWdnZXN0Li4u ICBEZWNsYXJpbmcgc2V2ZXJhbCBgQmxvY2tfZXJyb3IKPiBpZiBuZWNlc3NhcnkgYWxsb3dzIHRv IGFjdCBvbiAiY2xhc3NlcyIgb2YgZXJyb3JzIOKAlCB3aGljaCBpcyBhbGwgb25lCj4gY2FuIGhv cGUgZm9yIGdpdmVuIHRoZSBhYnN0cmFjdGlvbi4KPgo+PiBJdCdzIHByb2JhYmx5IHdvcnRoIGNv bXBpbGluZyBhIGxpc3Qgb2YgZXhhbXBsZXMgd2hlcmUgTWlyYWdlIGNvZGUKPj4gY3VycmVudGx5 IG1hdGNoZXMgb24gc3BlY2lmaWMgcmV0dXJuZWQgRXJyb3IgY29kZXMgYW5kIHRha2VzIHNwZWNp ZmljCj4+IGFjdGlvbnMuIE15IGd1ZXNzIGlzIHRoZXJlIGFyZW4ndCBlbm91Z2ggdG8ganVzdGlm eSB0aGUgY29tcGxleGl0eQo+PiB0aG91Z2guCj4KPiBUaGF0IHdvdWxkIGJlIG5pY2UuICBJIGRv bid0IGhhdmUgbXVjaCBmYW1pbGlhcml0eSB3aXRoIGEgbG90IG9mIHBhcnRzCj4gb2YgTWlyYWdl IHNvIEkgbWF5IGJlIG1pc3NpbmcgdXNlIGNhc2VzLiAgQXMgSSB1bmRlcnN0YW5kIHRoZQo+IGRp c2N1c3Npb24sIE1pcmFnZSBjb2RlIHNob3VsZCBiZSByZXZpc2l0ZWQsIG5vdCBvbmx5IHRvIHNl ZSBob3cKPiB0aGluZ3MgYXJlIGRvbmUgbm93IGJ1dCBhbHNvIHdoYXQgdGhlIHByb2JsZW1zIGFy ZSAod2l0aCB0aGUgY3VycmVudAo+IHNjaGVtZSkgYW5kIHdoYXQgcHJvcGVydGllcyBvZiB0aGUg ZXJyb3IgaGFuZGxpbmcgd2Ugd291bGQgbGlrZSBpbgo+IHRoZXNlIGNhc2VzLgoKTWlnaHQgYmUg dXNlZnVsIHRvIGFkZCBzb21lIHRlc3QgY2FzZXMgdG8gdGhlIGRvY3VtZW50YXRpb24uIEZvcgpl eGFtcGxlLCB0cnlpbmcgdG8gY29ubmVjdCB0byBhIGRpc2sgbm93IHJlc3VsdHMgaW4gZS5nLgoK RmF0YWwgZXJyb3I6IGV4Y2VwdGlvbiBGYWlsdXJlKCJibG9jazEiKQoKSWRlYWxseSwgSSdkIHdh bnQgc29tZXRoaW5nIGxpa2U6CgpCbG9jay5jb25uZWN0OiB1bmFibGUgdG8gbWF0Y2gKJy9ob21l L21pcmFnZS9taXJhZ2Utc2tlbGV0b24vYmxvY2svZGlzay5pbWcnIHRvIGFueSBhdmFpbGFibGUg WGVuCmRpc2sgKGF2YWlsYWJsZTogJ3h2ZGExJykKLi4uIGF0dGVtcHRpbmcgdG8gY29ubmVjdCAi YmxvY2sxIgoKQ3VycmVudGx5LCB3ZSB3b3JrIGFyb3VuZCB0aGlzIHVzaW5nICJwcmludGYiIGNh bGxzIGluIGxpYnJhcmllcywgc28KaG9wZWZ1bGx5IHRoZSB1c2VyIHdpbGwgc2VlIHRoZSByZWFs IGNhdXNlIGluIHRoZSBjb25zb2xlIG91dHB1dCwgYnV0CnRoYXQncyBub3QgaWRlYWwuIEluIGEg YnVzeSBzeXN0ZW0sIHRyeWluZyB0byBjb3JyZWxhdGUgbWVzc2FnZXMKbG9nZ2VkIGF0IHZhcmlv dXMgcG9pbnRzIGluIHRoZSBsb2cgZmlsZXMgaXNuJ3QgZnVuLgoKPj4gWy4uLl0gaW4gZXZlcnkg b25lIG9mIHRoZXNlIGNhc2VzIHdoZXJlIHdlIG1hdGNoIG9uIGFuIGBFcnJvciwgd2UganVzdAo+ PiBwcm9wYWdhdGUgaXQgKGkuZS4gdGhlIGRlZmF1bHQgYmVoYXZpb3VyIG9mIGFuIGV4Y2VwdGlv biB3b3VsZCBoYXZlCj4+IGJlZW4gY29ycmVjdCkuCj4+Cj4+IEhlcmUgYXJlIHNvbWUgZXhhbXBs ZXM6Cj4+Cj4+IHwgYEVycm9yIChgSW52YWxpZF9jb25zb2xlIHgpIC0+IGZhaWwgKEZhaWx1cmUg KFByaW50Zi5zcHJpbnRmICJJbnZhbGlkX2NvbnNvbGUgJXMiIHgpKQo+PiB8IGBFcnJvciAoYEJs b2NrX2RldmljZSBlKSAtPiBmYWlsIChGYWlsdXJlIChGcy5zdHJpbmdfb2ZfYmxvY2tfZXJyb3Ig ZSkpCj4+IHwgYEVycm9yIChLVi5Vbmtub3duX2tleSBrZXkpIC0+IGZhaWwgKEludmFsaWRfYXJn dW1lbnQga2V5KQo+PiB8IGBFcnJvciAoYFVua25vd24gbXNnKSAtPiBMd3QuZmFpbCAoRmFpbHVy ZSBtc2cpCj4KPiBJIGRvbid0IHVuZGVyc3RhbmQgdGhlIHBvaW50IG9mIHRoaXMgdHlwZSBvZiBj b2RlLiAgV2h5IHdhc24ndCDigJxFcnJvcuKAnQo+IGRlY2xhcmVkIGFzIGFuIGV4Y2VwdGlvbiAo cG9zc2libHkgd2l0aCBhbiBleGNlcHRpb24gcHJpbnRlcikgYW5kCj4g4oCcZmFpbOKAnSBkaXJl Y3RseSBpbnZva2VkIG9uIGl0PyAgVGhpcyBhbHNvIGhpZ2hsaWdodHMgdGhhdCBwZW9wbGUgc2h5 Cj4gYXdheSBmcm9tIGhhdmluZyB0byBoYW5kbGUgZXZlbiBhIHNpbXBsZSBgRXJyb3IgdG8gdGhl IHBvaW50IHRoYXQgaXQKPiBzZWVtcyBwcmVmZXJhYmxlIHRvIGRlZ2VuZXJhdGUgaXQgYXMgYSBz dHJpbmchCgpZZXMsIHRoaXMgaXMgdGhlIGtpbmQgb2YgY29kZSBJJ2QgbGlrZSB0byBnZXQgcmlk IG9mLgoKPj4gVGhlIG9ubHkgY2FzZSB3aGVyZSB3ZSBkbyBzb21ldGhpbmcgaW50ZXJlc3Rpbmcg aXMgYEVycm9yIChVbmtub3duX2tleQo+PiBfKSwgd2hlcmUgd2Ugbm90ZSB0aGF0IGl0IHdhcyBh IHJlYWQ6Cj4+Cj4+IHwgYEVycm9yIChUTVBMLlVua25vd25fa2V5IF8pIC0+IGZhaWwgKEZhaWx1 cmUgKCJyZWFkICIgXiBuYW1lKSkKPj4KPj4gSG93ZXZlciwgVW5rbm93bl9rZXkgd291bGRuJ3Qg YmUgYW4gZXhjZXB0aW9uIHVuZGVyIGFueSBwcm9wb3NlZCBzY2hlbWUgYW55d2F5Cj4KPiBJbiB0 aGUgcHJldmlvdXMgZGlzY3Vzc2lvbiwgSSBoYWQgdGhlIGltcHJlc3Npb24gdGhhdCBoYXZpbmcg YSBzY2hlbWUKPiB0byBwcm9wYWdhdGUgZXJyb3JzIHNlYW1sZXNzbHkgd2hpbGUgZm9yY2luZyBj ZXJ0YWluIChjbGFzc2VzIG9mKQo+IGVycm9ycyB0byBiZSBoYW5kbGVkIGJlZm9yZSB0aGV5IHJl YWNoIHRoZSBtYWluIGxvb3Agd2FzIGltcG9ydGFudC4KPiBJZiB3ZSBkbyBub3QgY2FyZSBhYm91 dCB0aGlzLCB3aGF0IGlzIHdyb25nIHdpdGggdGhlIOKAnGZhaWzigJ0gbWVjaGFuaXNtCj4gb2Yg THd0PwoKSXQncyBub3QgeWV0IGNsZWFyIHdoZXRoZXIgd2Ugc2hvdWxkIGNhcmUgYWJvdXQgaXQg b3Igbm90LiBNeSBjdXJyZW50CmZlZWxpbmcgaXMgdGhhdCB3ZSBzaG91bGRuJ3QsIGFuZCBzaG91 bGQgaW5zdGVhZCBhZG9wdCBhbiBFcmxhbmctc3R5bGUKImxldCBpdCBjcmFzaCIgcG9saWN5LCB3 aXRoIGEgZ2VuZXJpYyBleGNlcHRpb24gaGFuZGxlciBpbiB0aGUgSFRUUApzZXJ2ZXIgYW5kIGFu eSBzaW1pbGFyIHBvbGxpbmcgbG9vcHMgKHdoaWNoIGFwcGVhcnMgdG8gYmUgZWZmZWN0aXZlbHkK d2hhdCB3ZSdyZSBkb2luZyBhbnl3YXksIHNpbmNlIHdlIGFsd2F5cyBzZWVtIHRvIHVzZSBhbiBl eGNlcHRpb24gaW4KdGhlIGVuZCkuCgpIb3dldmVyLCB0aGVyZSBpcyBhbiBhcmd1bWVudCB0aGF0 IGl0IGlzIG1vcmUgY29ycmVjdCB0byBjb25zaWRlcgplcnJvcnMgd2hlcmUgdGhleSBvY2N1ciBh bmQgZGVjaWRlIGhvdyB0byBoYW5kbGUgdGhlbSBhdCBlYWNoIHBvaW50LgpJZiB0aGVyZSdzIGEg d2F5IHRvIGxldCBwZW9wbGUgd2hvIHdhbnQgdG8gY2F0Y2ggYW5kIGhhbmRsZSBpbmRpdmlkdWFs CmVycm9ycyBkbyBzbyByZWxpYWJseSwgd2l0aG91dCBhZGRpbmcgc28gbXVjaCBib2lsZXJwbGF0 ZSB0aGF0IHdlIGFkZAptb3JlIGJ1Z3MgdGhhbiB3ZSByZW1vdmUsIEknbSBoYXBweSB0byBoZWFy IGl0LgoKVGhlcmUgYXJlIHNvbWUgdGhpbmcgdGhhdCBzaG91bGQgY2VydGFpbmx5IGJlIGVycm9y IGNvZGVzCihVbmtub3duX2tleSkgYW5kIHNvbWUgdGhpbmdzIHRoYXQgSSB0aGluayBjZXJ0YWlu bHkgc2hvdWxkIGJlCmV4Y2VwdGlvbnMgKGBVbmtub3duKSwgYnV0IHRoZSBvbmVzIGluIHRoZSBt aWRkbGUgKGBEaXNjb25uZWN0ZWQpIGFyZQpsZXNzIG9idmlvdXMuCgpQcm9iYWJseSBpdCBkb2Vz bid0IG1hdHRlciB0b28gbXVjaC4gSWYgRGlzY29ubmVjdGVkIGlzIGFuIGVycm9yIGNvZGUKaXQn cyBub3QgYSBiaWcgcHJvYmxlbSwgcHJvdmlkZWQgSSBjYW4gZWFzaWx5IHR1cm4gaXQgaW50byBh bgpleGNlcHRpb24gaWYgaXQgcmVhbGx5IGlzbid0IGEgY2FzZSBJIHdhbnQgdG8gaGFuZGxlLiBB bmQgaWYgaXQncyBhbgpleGNlcHRpb24gdGhlbiB0aGF0J3MgZmluZSwgYXMgbG9uZyBhcyBJIGNh biBlYXNpbHkgY2F0Y2ggaXQgYW5kCmhhbmRsZSBpdC4KCgotLSAKRHIgVGhvbWFzIExlb25hcmQg ICAgICAgIGh0dHA6Ly8waW5zdGFsbC5uZXQvCkdQRzogOTI0MiA5ODA3IEM5ODUgM0MwNyA0NEE2 ICA4QjlBIEFFMDcgODI4MCA1OUE1IDNDQzEKR1BHOiBEQTk4IDI1QUUgQ0FEMCA4OTc1IDdDREEg IEJEOEUgMDcxMyAzRjk2IENBNzQgRDhCQQoKX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX18KTWlyYWdlT1MtZGV2ZWwgbWFpbGluZyBsaXN0Ck1pcmFnZU9TLWRl dmVsQGxpc3RzLnhlbnByb2plY3Qub3JnCmh0dHA6Ly9saXN0cy54ZW5wcm9qZWN0Lm9yZy9jZ2kt YmluL21haWxtYW4vbGlzdGluZm8vbWlyYWdlb3MtZGV2ZWwK From mirageos-devel-bounces@lists.xenproject.org Wed Feb 04 12:51:36 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 04 Feb 2015 12:51:36 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YIzQX-000866-GD; Wed, 04 Feb 2015 12:51:29 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YIzQW-000861-Ou for MirageOS-devel@lists.xenproject.org; Wed, 04 Feb 2015 12:51:28 +0000 Received: from [85.158.137.68] by server-4.bemta-3.messagelabs.com id 04/7B-03185-0D512D45; Wed, 04 Feb 2015 12:51:28 +0000 X-Env-Sender: richard.mortier@gmail.com X-Msg-Ref: server-12.tower-31.messagelabs.com!1423054287!11904598!1 X-Originating-IP: [209.85.212.170] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.12.5; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21580 invoked from network); 4 Feb 2015 12:51:27 -0000 Received: from mail-wi0-f170.google.com (HELO mail-wi0-f170.google.com) (209.85.212.170) by server-12.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 4 Feb 2015 12:51:27 -0000 Received: by mail-wi0-f170.google.com with SMTP id bs8so28916413wib.1 for ; Wed, 04 Feb 2015 04:51:27 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=mime-version:date:message-id:subject:from:to:content-type; bh=eIvciAvokVa7P6p37r9cG48h6elm3Ag3IZC7B9YNXBE=; b=buJSffdRy0UrwUzq5Kq9WE8R0wABp4M7LEYqWotOwGbmNew0s4K3iBGAFBA3Jj9WDt dhI5g49FzB/yz7WHfV/ebWl2zx6UEuYbJtnYHqL7HMyfFay0+pDZvmV3Bf66CqqE6LRH 0gpJ7uWOYnrHVyY5r7fjboXGOo+2o6glckabUl2BfF47YNb2PqeO6U+RtFZbxrQancsN 0ZnViTDtooU1hHBjYhLGT6oNAsiglCdvS9Yh3KhsOithMbgKbqsHFNZE8KbtXswW7let J0rt3OIgtPbgE6PZzmKM1+BDGytoeeqVuhCTXYFkXlqK2hMyeBNjU5qi1aMTBHGry5fq YPqw== X-Received: by 10.194.157.38 with SMTP id wj6mr9774181wjb.62.1423054287053; Wed, 04 Feb 2015 04:51:27 -0800 (PST) Received: from mail-wg0-f54.google.com (mail-wg0-f54.google.com. [74.125.82.54]) by mx.google.com with ESMTPSA id lk2sm3100115wic.22.2015.02.04.04.51.26 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 04 Feb 2015 04:51:26 -0800 (PST) Received: by mail-wg0-f54.google.com with SMTP id b13so1474134wgh.13 for ; Wed, 04 Feb 2015 04:51:26 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.180.90.177 with SMTP id bx17mr4262186wib.36.1423054286248; Wed, 04 Feb 2015 04:51:26 -0800 (PST) Received: by 10.217.83.83 with HTTP; Wed, 4 Feb 2015 04:51:26 -0800 (PST) Date: Wed, 4 Feb 2015 12:51:26 +0000 Message-ID: From: Richard Mortier To: mirageos-devel Subject: [MirageOS-devel] opam / mirage X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org i'm probably missing something obvious here but i can't spot it so-- i'm trying to setup travis for `mirage-tutorial`. i thought i'd use @samoht fine travis/opam skeleton (https://github.com/ocaml/ocaml-travisci-skeleton). this assumes that it's an opam package being tested, so assumes a `./opam` file and uses `opam` to install dependencies, etc. using `./opam` to record the dependencies and other metadata seems appealing, but always fails because (after pinning) `opam install mirage-tutorial` calls `make configure` calls `mirage configure` calls `opam` -- which collides on the opam lock file. this seems like a showstopper for doing it this way at all -- is there an easy way to resolve this? in particular, as an alternative, i'm tempted to write and submit a PR to the opam travis skeleton repo to add an alternative travis script that uses the same ubuntu setup runes, but then simply calls make rather than relying on opam to drive the installation. comments? -- Richard Mortier richard.mortier@cl.cam.ac.uk _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Wed Feb 04 12:51:36 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 04 Feb 2015 12:51:36 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YIzQX-000866-GD; Wed, 04 Feb 2015 12:51:29 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YIzQW-000861-Ou for MirageOS-devel@lists.xenproject.org; Wed, 04 Feb 2015 12:51:28 +0000 Received: from [85.158.137.68] by server-4.bemta-3.messagelabs.com id 04/7B-03185-0D512D45; Wed, 04 Feb 2015 12:51:28 +0000 X-Env-Sender: richard.mortier@gmail.com X-Msg-Ref: server-12.tower-31.messagelabs.com!1423054287!11904598!1 X-Originating-IP: [209.85.212.170] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.12.5; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21580 invoked from network); 4 Feb 2015 12:51:27 -0000 Received: from mail-wi0-f170.google.com (HELO mail-wi0-f170.google.com) (209.85.212.170) by server-12.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 4 Feb 2015 12:51:27 -0000 Received: by mail-wi0-f170.google.com with SMTP id bs8so28916413wib.1 for ; Wed, 04 Feb 2015 04:51:27 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=mime-version:date:message-id:subject:from:to:content-type; bh=eIvciAvokVa7P6p37r9cG48h6elm3Ag3IZC7B9YNXBE=; b=buJSffdRy0UrwUzq5Kq9WE8R0wABp4M7LEYqWotOwGbmNew0s4K3iBGAFBA3Jj9WDt dhI5g49FzB/yz7WHfV/ebWl2zx6UEuYbJtnYHqL7HMyfFay0+pDZvmV3Bf66CqqE6LRH 0gpJ7uWOYnrHVyY5r7fjboXGOo+2o6glckabUl2BfF47YNb2PqeO6U+RtFZbxrQancsN 0ZnViTDtooU1hHBjYhLGT6oNAsiglCdvS9Yh3KhsOithMbgKbqsHFNZE8KbtXswW7let J0rt3OIgtPbgE6PZzmKM1+BDGytoeeqVuhCTXYFkXlqK2hMyeBNjU5qi1aMTBHGry5fq YPqw== X-Received: by 10.194.157.38 with SMTP id wj6mr9774181wjb.62.1423054287053; Wed, 04 Feb 2015 04:51:27 -0800 (PST) Received: from mail-wg0-f54.google.com (mail-wg0-f54.google.com. [74.125.82.54]) by mx.google.com with ESMTPSA id lk2sm3100115wic.22.2015.02.04.04.51.26 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 04 Feb 2015 04:51:26 -0800 (PST) Received: by mail-wg0-f54.google.com with SMTP id b13so1474134wgh.13 for ; Wed, 04 Feb 2015 04:51:26 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.180.90.177 with SMTP id bx17mr4262186wib.36.1423054286248; Wed, 04 Feb 2015 04:51:26 -0800 (PST) Received: by 10.217.83.83 with HTTP; Wed, 4 Feb 2015 04:51:26 -0800 (PST) Date: Wed, 4 Feb 2015 12:51:26 +0000 Message-ID: From: Richard Mortier To: mirageos-devel Subject: [MirageOS-devel] opam / mirage X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org i'm probably missing something obvious here but i can't spot it so-- i'm trying to setup travis for `mirage-tutorial`. i thought i'd use @samoht fine travis/opam skeleton (https://github.com/ocaml/ocaml-travisci-skeleton). this assumes that it's an opam package being tested, so assumes a `./opam` file and uses `opam` to install dependencies, etc. using `./opam` to record the dependencies and other metadata seems appealing, but always fails because (after pinning) `opam install mirage-tutorial` calls `make configure` calls `mirage configure` calls `opam` -- which collides on the opam lock file. this seems like a showstopper for doing it this way at all -- is there an easy way to resolve this? in particular, as an alternative, i'm tempted to write and submit a PR to the opam travis skeleton repo to add an alternative travis script that uses the same ubuntu setup runes, but then simply calls make rather than relying on opam to drive the installation. comments? -- Richard Mortier richard.mortier@cl.cam.ac.uk _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Wed Feb 04 12:52:21 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 04 Feb 2015 12:52:21 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YIzRN-0000Fl-Km; Wed, 04 Feb 2015 12:52:21 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YIzRL-0000Fg-V9 for mirageos-devel@lists.xenproject.org; Wed, 04 Feb 2015 12:52:20 +0000 Received: from [193.109.254.147] by server-16.bemta-14.messagelabs.com id 7A/A2-02639-30612D45; Wed, 04 Feb 2015 12:52:19 +0000 X-Env-Sender: Christophe.TROESTLER@umons.ac.be X-Msg-Ref: server-6.tower-27.messagelabs.com!1423054338!12746287!1 X-Originating-IP: [157.55.234.85] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 19177 invoked from network); 4 Feb 2015 12:52:18 -0000 Received: from mail-db3on0085.outbound.protection.outlook.com (HELO emea01-db3-obe.outbound.protection.outlook.com) (157.55.234.85) by server-6.tower-27.messagelabs.com with AES256-SHA encrypted SMTP; 4 Feb 2015 12:52:18 -0000 Received: from DB3PR05CA0011.eurprd05.prod.outlook.com (25.160.41.139) by DB4PR05MB526.eurprd05.prod.outlook.com (10.242.154.28) with Microsoft SMTP Server (TLS) id 15.1.75.20; Wed, 4 Feb 2015 12:52:17 +0000 Received: from AM1FFO11FD018.protection.gbl (2a01:111:f400:7e00::112) by DB3PR05CA0011.outlook.office365.com (2a01:111:e400:9428::11) with Microsoft SMTP Server (TLS) id 15.1.75.20 via Frontend Transport; Wed, 4 Feb 2015 12:52:17 +0000 Received: from smtp.umons.ac.be (193.190.208.132) by AM1FFO11FD018.mail.protection.outlook.com (10.174.64.207) with Microsoft SMTP Server (TLS) id 15.1.87.10 via Frontend Transport; Wed, 4 Feb 2015 12:52:17 +0000 Received: from poincare (10.104.2.68) by smtp.umons.ac.be (10.104.2.84) with Microsoft SMTP Server (TLS) id 14.3.224.2; Wed, 4 Feb 2015 13:52:10 +0100 Received: from localhost ([::1]) by poincare with esmtp (Exim 4.84) (envelope-from ) id 1YIzR0-0007B6-0A; Wed, 04 Feb 2015 13:51:58 +0100 Date: Wed, 4 Feb 2015 13:51:57 +0100 Message-ID: <20150204.135157.1973363912663016089.Christophe.Troestler@umons.ac.be> To: From: Christophe Troestler In-Reply-To: References: <20150204.001614.26478837567139584.Christophe.Troestler@umons.ac.be> X-Face: #2fb%mPx>rRL@4ff~TVgZ"<[:,oL"`TUEGK/[8/qb58~C>jR(x4A+v/n)7BgpEtIph_neoLKJBq0JBY9:}8v|j Organization: Universite de Mons (http://math.umons.ac.be/anum/) X-Mailer: Mew version 6.6 on Emacs 24.4 / Mule 6.0 (HANACHIRUSATO) MIME-Version: 1.0 Content-Length: 2096 X-Originating-IP: [10.104.2.68] X-EOPAttributedMessage: 0 X-Matching-Connectors: 130675279373242042; (9b551343-d075-4328-d154-08d0574c44b8,aa519c6d-c5b7-417d-4ec3-08d1170c20a9); (9b551343-d075-4328-d154-08d0574c44b8,aa519c6d-c5b7-417d-4ec3-08d1170c20a9) Received-SPF: Pass (protection.outlook.com: domain of umons.ac.be designates 193.190.208.132 as permitted sender) receiver=protection.outlook.com; client-ip=193.190.208.132; helo=smtp.umons.ac.be; X-Forefront-Antispam-Report: CIP:193.190.208.132; CTRY:BE; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(10009020)(6009001)(438002)(51704005)(52604005)(2351001)(46102003)(74482002)(50466002)(19580395003)(23676002)(87936001)(50226001)(19580405001)(106466001)(77156002)(62966003)(36756003)(110136001)(47776003)(16796002)(50986999)(76176999)(103116003)(86362001)(76506005)(226693001)(92566002)(6806004)(2950100001)(57986006); DIR:OUT; SFP:1101; SCL:1; SRVR:DB4PR05MB526; H:smtp.umons.ac.be; FPR:; SPF:Pass; MLV:sfv; LANG:en; X-Microsoft-Antispam: UriScan:; X-Microsoft-Antispam: BCL:0;PCL:0;RULEID:;SRVR:DB4PR05MB526; X-Exchange-Antispam-Report-Test: UriScan:; X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(601004); SRVR:DB4PR05MB526; X-Forefront-PRVS: 04772EA191 X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(401004)(400005); SRVR:DB4PR05MB526; X-MS-Exchange-CrossTenant-OriginalArrivalTime: 04 Feb 2015 12:52:17.0902 (UTC) X-MS-Exchange-CrossTenant-Id: 5afe0b00-7697-4969-b663-5eab37d5f47e X-MS-Exchange-CrossTenant-OriginalAttributedTenantConnectingIp: TenantId=5afe0b00-7697-4969-b663-5eab37d5f47e; Ip=[193.190.208.132] X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB4PR05MB526 Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Error handling in Mirage - request for comments! X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org T24gV2VkLCA0IEZlYiAyMDE1IDExOjUyOjI4ICswMDAwLCBUaG9tYXMgTGVvbmFyZCB3cm90ZToK PiAKPiBPbiAzIEZlYnJ1YXJ5IDIwMTUgYXQgMjM6MTYsIENocmlzdG9waGUgVHJvZXN0bGVyCj4g PENocmlzdG9waGUuVHJvZXN0bGVyQHVtb25zLmFjLmJlPiB3cm90ZToKPiA+IE9uIE1vbiwgMiBG ZWIgMjAxNSAxMjozMDozOSArMDAwMCwgVGhvbWFzIExlb25hcmQgd3JvdGU6Cj4gPj4KPiA+PiBs ZXQgYmluZCB0IGYgPQo+ID4+ICAgbGV0IHQgPSByZXByIHQgaW4KPiA+PiAgIG1hdGNoIHQuc3Rh dGUgd2l0aAo+ID4+ICAgICB8IFJldHVybiB2IC0+Cj4gPj4gICAgICAgICBmIHYKPiA+PiAgICAg fCBGYWlsIF8gYXMgc3RhdGUgLT4KPiA+PiAgICAgICAgIHRocmVhZCB7IHN0YXRlIH0KPiA+PiAg ICAgfCBTbGVlcCBzbGVlcGVyIC0+Cj4gPj4gICAgICAgICBsZXQgcmVzID0gdGVtcCB0IGluCj4g Pj4gICAgICAgICBsZXQgZGF0YSA9ICFjdXJyZW50X2RhdGEgaW4KPiA+PiAgICAgICAgIGFkZF9p bW11dGFibGVfd2FpdGVyIHNsZWVwZXIKPiA+PiAgICAgICAgICAgKGZ1bmN0aW9uCj4gPj4gICAg ICAgICAgICAgIHwgUmV0dXJuIHYgLT4gY3VycmVudF9kYXRhIDo9IGRhdGE7IGNvbm5lY3QgcmVz ICh0cnkgZiB2Cj4gPj4gd2l0aCBleG4gLT4gZmFpbCBleG4pCj4gPj4gICAgICAgICAgICAgIHwg RmFpbCBfIGFzIHN0YXRlIC0+IGZhc3RfY29ubmVjdCByZXMgc3RhdGUKPiA+PiAgICAgICAgICAg ICAgfCBfIC0+IGFzc2VydCBmYWxzZSk7Cj4gPj4gICAgICAgICByZXMKPiA+Cj4gPiBUaGFua3Mg Zm9yIGNoZWNraW5nLiAgQXQgZmlyc3QsIHRoZSBkaWZmZXJlbmNlIG9mIHRyZWF0bWVudCBiZXR3 ZWVuCj4gPiB0aGUgdHdvIOKAnGYgduKAnSBpcyBhIGxpdHRsZSBvZGQuICBEbyB5b3UgaGFwcGVu IHRvIGtub3cgdGhlIHJlYXNvbiBmb3IKPiA+IGl0Pwo+IAo+IEkgYXNzdW1lIGl0J3MgYSBzcGVl ZCBvcHRpbWlzYXRpb24KClRoaW5raW5nIGEgYml0IG1vcmUgYWJvdXQgdGhpcywgSSB3b25kZXIg d2hldGhlciBpdCBtYXkgYmUgbW9yZQpmdW5kYW1lbnRhbDogd2hlbiB0aGUgc3RhdGUgaXMg4oCc UmV0dXJu4oCdLCB0aGUgZXhjZXB0aW9uIHdpbGwgdHJhdmVsIHRoZQpjaGFpbiBvZiBjYWxscyBv ZiB0aGUgc2FtZSAidGhyZWFkIiB1cCB1bnRpbCBpdCByZWFjaGVzIGEgaGFuZGxlciDigJQgc28K b25lIGNhbiBkaXNwZW5zZSBwdXR0aW5nIGEgaGFuZGxlciDigJQsIHdoZW4gaXQgaXMg4oCcU2xl ZXDigJ0sIGl0IGlzCnBvc3NpYmxlIHRoYXQgaXQgZXNjYXBlIHRoZSBjdXJyZW50IHRocmVhZC4K CltXaWxsIHJlYWQgdGhlIHJlc3QgbGF0ZXIg4oCUIGF0IGEgbWVldGluZy4uLl0KCkJlc3QsCkMu CgpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwpNaXJhZ2VP Uy1kZXZlbCBtYWlsaW5nIGxpc3QKTWlyYWdlT1MtZGV2ZWxAbGlzdHMueGVucHJvamVjdC5vcmcK aHR0cDovL2xpc3RzLnhlbnByb2plY3Qub3JnL2NnaS1iaW4vbWFpbG1hbi9saXN0aW5mby9taXJh Z2Vvcy1kZXZlbAo= From mirageos-devel-bounces@lists.xenproject.org Wed Feb 04 12:52:21 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 04 Feb 2015 12:52:21 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YIzRN-0000Fl-Km; Wed, 04 Feb 2015 12:52:21 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YIzRL-0000Fg-V9 for mirageos-devel@lists.xenproject.org; Wed, 04 Feb 2015 12:52:20 +0000 Received: from [193.109.254.147] by server-16.bemta-14.messagelabs.com id 7A/A2-02639-30612D45; Wed, 04 Feb 2015 12:52:19 +0000 X-Env-Sender: Christophe.TROESTLER@umons.ac.be X-Msg-Ref: server-6.tower-27.messagelabs.com!1423054338!12746287!1 X-Originating-IP: [157.55.234.85] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 19177 invoked from network); 4 Feb 2015 12:52:18 -0000 Received: from mail-db3on0085.outbound.protection.outlook.com (HELO emea01-db3-obe.outbound.protection.outlook.com) (157.55.234.85) by server-6.tower-27.messagelabs.com with AES256-SHA encrypted SMTP; 4 Feb 2015 12:52:18 -0000 Received: from DB3PR05CA0011.eurprd05.prod.outlook.com (25.160.41.139) by DB4PR05MB526.eurprd05.prod.outlook.com (10.242.154.28) with Microsoft SMTP Server (TLS) id 15.1.75.20; Wed, 4 Feb 2015 12:52:17 +0000 Received: from AM1FFO11FD018.protection.gbl (2a01:111:f400:7e00::112) by DB3PR05CA0011.outlook.office365.com (2a01:111:e400:9428::11) with Microsoft SMTP Server (TLS) id 15.1.75.20 via Frontend Transport; Wed, 4 Feb 2015 12:52:17 +0000 Received: from smtp.umons.ac.be (193.190.208.132) by AM1FFO11FD018.mail.protection.outlook.com (10.174.64.207) with Microsoft SMTP Server (TLS) id 15.1.87.10 via Frontend Transport; Wed, 4 Feb 2015 12:52:17 +0000 Received: from poincare (10.104.2.68) by smtp.umons.ac.be (10.104.2.84) with Microsoft SMTP Server (TLS) id 14.3.224.2; Wed, 4 Feb 2015 13:52:10 +0100 Received: from localhost ([::1]) by poincare with esmtp (Exim 4.84) (envelope-from ) id 1YIzR0-0007B6-0A; Wed, 04 Feb 2015 13:51:58 +0100 Date: Wed, 4 Feb 2015 13:51:57 +0100 Message-ID: <20150204.135157.1973363912663016089.Christophe.Troestler@umons.ac.be> To: From: Christophe Troestler In-Reply-To: References: <20150204.001614.26478837567139584.Christophe.Troestler@umons.ac.be> X-Face: #2fb%mPx>rRL@4ff~TVgZ"<[:,oL"`TUEGK/[8/qb58~C>jR(x4A+v/n)7BgpEtIph_neoLKJBq0JBY9:}8v|j Organization: Universite de Mons (http://math.umons.ac.be/anum/) X-Mailer: Mew version 6.6 on Emacs 24.4 / Mule 6.0 (HANACHIRUSATO) MIME-Version: 1.0 Content-Length: 2096 X-Originating-IP: [10.104.2.68] X-EOPAttributedMessage: 0 X-Matching-Connectors: 130675279373242042; (9b551343-d075-4328-d154-08d0574c44b8,aa519c6d-c5b7-417d-4ec3-08d1170c20a9); (9b551343-d075-4328-d154-08d0574c44b8,aa519c6d-c5b7-417d-4ec3-08d1170c20a9) Received-SPF: Pass (protection.outlook.com: domain of umons.ac.be designates 193.190.208.132 as permitted sender) receiver=protection.outlook.com; client-ip=193.190.208.132; helo=smtp.umons.ac.be; X-Forefront-Antispam-Report: CIP:193.190.208.132; CTRY:BE; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(10009020)(6009001)(438002)(51704005)(52604005)(2351001)(46102003)(74482002)(50466002)(19580395003)(23676002)(87936001)(50226001)(19580405001)(106466001)(77156002)(62966003)(36756003)(110136001)(47776003)(16796002)(50986999)(76176999)(103116003)(86362001)(76506005)(226693001)(92566002)(6806004)(2950100001)(57986006); DIR:OUT; SFP:1101; SCL:1; SRVR:DB4PR05MB526; H:smtp.umons.ac.be; FPR:; SPF:Pass; MLV:sfv; LANG:en; X-Microsoft-Antispam: UriScan:; X-Microsoft-Antispam: BCL:0;PCL:0;RULEID:;SRVR:DB4PR05MB526; X-Exchange-Antispam-Report-Test: UriScan:; X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(601004); SRVR:DB4PR05MB526; X-Forefront-PRVS: 04772EA191 X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(401004)(400005); SRVR:DB4PR05MB526; X-MS-Exchange-CrossTenant-OriginalArrivalTime: 04 Feb 2015 12:52:17.0902 (UTC) X-MS-Exchange-CrossTenant-Id: 5afe0b00-7697-4969-b663-5eab37d5f47e X-MS-Exchange-CrossTenant-OriginalAttributedTenantConnectingIp: TenantId=5afe0b00-7697-4969-b663-5eab37d5f47e; Ip=[193.190.208.132] X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB4PR05MB526 Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Error handling in Mirage - request for comments! X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org T24gV2VkLCA0IEZlYiAyMDE1IDExOjUyOjI4ICswMDAwLCBUaG9tYXMgTGVvbmFyZCB3cm90ZToK PiAKPiBPbiAzIEZlYnJ1YXJ5IDIwMTUgYXQgMjM6MTYsIENocmlzdG9waGUgVHJvZXN0bGVyCj4g PENocmlzdG9waGUuVHJvZXN0bGVyQHVtb25zLmFjLmJlPiB3cm90ZToKPiA+IE9uIE1vbiwgMiBG ZWIgMjAxNSAxMjozMDozOSArMDAwMCwgVGhvbWFzIExlb25hcmQgd3JvdGU6Cj4gPj4KPiA+PiBs ZXQgYmluZCB0IGYgPQo+ID4+ICAgbGV0IHQgPSByZXByIHQgaW4KPiA+PiAgIG1hdGNoIHQuc3Rh dGUgd2l0aAo+ID4+ICAgICB8IFJldHVybiB2IC0+Cj4gPj4gICAgICAgICBmIHYKPiA+PiAgICAg fCBGYWlsIF8gYXMgc3RhdGUgLT4KPiA+PiAgICAgICAgIHRocmVhZCB7IHN0YXRlIH0KPiA+PiAg ICAgfCBTbGVlcCBzbGVlcGVyIC0+Cj4gPj4gICAgICAgICBsZXQgcmVzID0gdGVtcCB0IGluCj4g Pj4gICAgICAgICBsZXQgZGF0YSA9ICFjdXJyZW50X2RhdGEgaW4KPiA+PiAgICAgICAgIGFkZF9p bW11dGFibGVfd2FpdGVyIHNsZWVwZXIKPiA+PiAgICAgICAgICAgKGZ1bmN0aW9uCj4gPj4gICAg ICAgICAgICAgIHwgUmV0dXJuIHYgLT4gY3VycmVudF9kYXRhIDo9IGRhdGE7IGNvbm5lY3QgcmVz ICh0cnkgZiB2Cj4gPj4gd2l0aCBleG4gLT4gZmFpbCBleG4pCj4gPj4gICAgICAgICAgICAgIHwg RmFpbCBfIGFzIHN0YXRlIC0+IGZhc3RfY29ubmVjdCByZXMgc3RhdGUKPiA+PiAgICAgICAgICAg ICAgfCBfIC0+IGFzc2VydCBmYWxzZSk7Cj4gPj4gICAgICAgICByZXMKPiA+Cj4gPiBUaGFua3Mg Zm9yIGNoZWNraW5nLiAgQXQgZmlyc3QsIHRoZSBkaWZmZXJlbmNlIG9mIHRyZWF0bWVudCBiZXR3 ZWVuCj4gPiB0aGUgdHdvIOKAnGYgduKAnSBpcyBhIGxpdHRsZSBvZGQuICBEbyB5b3UgaGFwcGVu IHRvIGtub3cgdGhlIHJlYXNvbiBmb3IKPiA+IGl0Pwo+IAo+IEkgYXNzdW1lIGl0J3MgYSBzcGVl ZCBvcHRpbWlzYXRpb24KClRoaW5raW5nIGEgYml0IG1vcmUgYWJvdXQgdGhpcywgSSB3b25kZXIg d2hldGhlciBpdCBtYXkgYmUgbW9yZQpmdW5kYW1lbnRhbDogd2hlbiB0aGUgc3RhdGUgaXMg4oCc UmV0dXJu4oCdLCB0aGUgZXhjZXB0aW9uIHdpbGwgdHJhdmVsIHRoZQpjaGFpbiBvZiBjYWxscyBv ZiB0aGUgc2FtZSAidGhyZWFkIiB1cCB1bnRpbCBpdCByZWFjaGVzIGEgaGFuZGxlciDigJQgc28K b25lIGNhbiBkaXNwZW5zZSBwdXR0aW5nIGEgaGFuZGxlciDigJQsIHdoZW4gaXQgaXMg4oCcU2xl ZXDigJ0sIGl0IGlzCnBvc3NpYmxlIHRoYXQgaXQgZXNjYXBlIHRoZSBjdXJyZW50IHRocmVhZC4K CltXaWxsIHJlYWQgdGhlIHJlc3QgbGF0ZXIg4oCUIGF0IGEgbWVldGluZy4uLl0KCkJlc3QsCkMu CgpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwpNaXJhZ2VP Uy1kZXZlbCBtYWlsaW5nIGxpc3QKTWlyYWdlT1MtZGV2ZWxAbGlzdHMueGVucHJvamVjdC5vcmcK aHR0cDovL2xpc3RzLnhlbnByb2plY3Qub3JnL2NnaS1iaW4vbWFpbG1hbi9saXN0aW5mby9taXJh Z2Vvcy1kZXZlbAo= From mirageos-devel-bounces@lists.xenproject.org Wed Feb 04 13:01:37 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 04 Feb 2015 13:01:37 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YIzaL-0000xq-1h; Wed, 04 Feb 2015 13:01:37 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YIzaJ-0000xM-23 for mirageos-devel@lists.xenproject.org; Wed, 04 Feb 2015 13:01:35 +0000 Received: from [85.158.137.68] by server-8.bemta-3.messagelabs.com id 06/67-03710-E2812D45; Wed, 04 Feb 2015 13:01:34 +0000 X-Env-Sender: lpw25@cam.ac.uk X-Msg-Ref: server-6.tower-31.messagelabs.com!1423054893!7530807!1 X-Originating-IP: [131.111.8.152] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTMxLjExMS44LjE1MiA9PiA4MDU1Mw==\n X-StarScan-Received: X-StarScan-Version: 6.12.5; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3338 invoked from network); 4 Feb 2015 13:01:33 -0000 Received: from ppsw-52.csi.cam.ac.uk (HELO ppsw-52.csi.cam.ac.uk) (131.111.8.152) by server-6.tower-31.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 4 Feb 2015 13:01:33 -0000 X-Cam-AntiVirus: no malware found X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/ Received: from host86-190-253-201.range86-190.btcentralplus.com ([86.190.253.201]:33350 helo=study.localdomain) by ppsw-52.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.159]:587) with esmtpsa (PLAIN:lpw25) (TLSv1.2:AES128-GCM-SHA256:128) id 1YIzaH-0001o1-E5 (Exim 4.82_3-c0e5623) (return-path ); Wed, 04 Feb 2015 13:01:33 +0000 From: Leo White To: Thomas Leonard References: <20150202.014549.1883720051237442569.Christophe.Troestler@umons.ac.be> <20150204.001614.26478837567139584.Christophe.Troestler@umons.ac.be> X-Face: "XWxb[u_Z\PA_Y?9@|IA!!+jTb(/290-*ea/Un$I0B98.$n%eL.; 2w*,z]WR#T:,p[ NBd++M7l]#7zj7!{~iw $W-"/=|dVjhT[D{4~gE}gK<2`.6fs!;uqqud]vs2N/3^m7{aS1V, Date: Wed, 04 Feb 2015 13:01:07 +0000 In-Reply-To: (Thomas Leonard's message of "Wed, 4 Feb 2015 11:52:28 +0000") Message-ID: <87oap97rvw.fsf@study.localdomain> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) MIME-Version: 1.0 Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Error handling in Mirage - request for comments! X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org Hi all, As this discussion keeps on running, I thought I would add a couple of thoughts: - The problem with using exceptions for returning errors is that it becomes very difficult to distinguish between a dynamic error that is part of normal use (e.g. this network connection failed) from a programming error (e.g. Not_found accidently leaked from a use of List.find, an assert false triggering). This makes it hard to produce the correct behaviour in all cases: there are applications for which it would be better to kill everyting on detecting a programmer error rather than risk continuing in an unstable state. - The problem with using Lwt.t as your error monad is that it becomes difficult to distiunguish between synchronous things that may return errors, asynchronous things that may return errors, and asynchornous things that should not return errors. It also seems tied up with the exception mechanism, which leads to the same problem as my previous point. Personally, I would probably suggest that all Mirage modules/module types include in their signatures: type error val pp_error : formatter -> error -> string For cases where an error can reasonably be matched on and handled specially, this should be exposed in the signature: type error = private [> `Foo of foo | `Bar of bar] val pp_error : formatter -> error -> string Some nice combinators should be provided for using ('a, 'b) Result.t and ('a, 'b) Result.t Lwt. and for lifting an ('a, Foo.error) Result.t into an ('a, Bar.error) Result.t. Exceptions that escape their intended scope, should always be treated as a programming error. The various "finally" functions for resources should catch and reraise them, so that they can reach the outermost scope which knows how best to deal with a programming error in the particular application. The same goes for binding on an Lwt thread which raised an exception or failed: it should cause an exception to be raised to reach the outermost level. The aim here is still to take the erlang-style kill the component that failed and try again approach, but to ensure that there are two distinct return paths for regular errors and programming errors. The secondary aim is to have module signatures which give a clear indication of intended use. Regards, Leo _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Wed Feb 04 13:01:37 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 04 Feb 2015 13:01:37 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YIzaL-0000xq-1h; Wed, 04 Feb 2015 13:01:37 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YIzaJ-0000xM-23 for mirageos-devel@lists.xenproject.org; Wed, 04 Feb 2015 13:01:35 +0000 Received: from [85.158.137.68] by server-8.bemta-3.messagelabs.com id 06/67-03710-E2812D45; Wed, 04 Feb 2015 13:01:34 +0000 X-Env-Sender: lpw25@cam.ac.uk X-Msg-Ref: server-6.tower-31.messagelabs.com!1423054893!7530807!1 X-Originating-IP: [131.111.8.152] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTMxLjExMS44LjE1MiA9PiA4MDU1Mw==\n X-StarScan-Received: X-StarScan-Version: 6.12.5; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3338 invoked from network); 4 Feb 2015 13:01:33 -0000 Received: from ppsw-52.csi.cam.ac.uk (HELO ppsw-52.csi.cam.ac.uk) (131.111.8.152) by server-6.tower-31.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 4 Feb 2015 13:01:33 -0000 X-Cam-AntiVirus: no malware found X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/ Received: from host86-190-253-201.range86-190.btcentralplus.com ([86.190.253.201]:33350 helo=study.localdomain) by ppsw-52.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.159]:587) with esmtpsa (PLAIN:lpw25) (TLSv1.2:AES128-GCM-SHA256:128) id 1YIzaH-0001o1-E5 (Exim 4.82_3-c0e5623) (return-path ); Wed, 04 Feb 2015 13:01:33 +0000 From: Leo White To: Thomas Leonard References: <20150202.014549.1883720051237442569.Christophe.Troestler@umons.ac.be> <20150204.001614.26478837567139584.Christophe.Troestler@umons.ac.be> X-Face: "XWxb[u_Z\PA_Y?9@|IA!!+jTb(/290-*ea/Un$I0B98.$n%eL.; 2w*,z]WR#T:,p[ NBd++M7l]#7zj7!{~iw $W-"/=|dVjhT[D{4~gE}gK<2`.6fs!;uqqud]vs2N/3^m7{aS1V, Date: Wed, 04 Feb 2015 13:01:07 +0000 In-Reply-To: (Thomas Leonard's message of "Wed, 4 Feb 2015 11:52:28 +0000") Message-ID: <87oap97rvw.fsf@study.localdomain> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) MIME-Version: 1.0 Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Error handling in Mirage - request for comments! X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org Hi all, As this discussion keeps on running, I thought I would add a couple of thoughts: - The problem with using exceptions for returning errors is that it becomes very difficult to distinguish between a dynamic error that is part of normal use (e.g. this network connection failed) from a programming error (e.g. Not_found accidently leaked from a use of List.find, an assert false triggering). This makes it hard to produce the correct behaviour in all cases: there are applications for which it would be better to kill everyting on detecting a programmer error rather than risk continuing in an unstable state. - The problem with using Lwt.t as your error monad is that it becomes difficult to distiunguish between synchronous things that may return errors, asynchronous things that may return errors, and asynchornous things that should not return errors. It also seems tied up with the exception mechanism, which leads to the same problem as my previous point. Personally, I would probably suggest that all Mirage modules/module types include in their signatures: type error val pp_error : formatter -> error -> string For cases where an error can reasonably be matched on and handled specially, this should be exposed in the signature: type error = private [> `Foo of foo | `Bar of bar] val pp_error : formatter -> error -> string Some nice combinators should be provided for using ('a, 'b) Result.t and ('a, 'b) Result.t Lwt. and for lifting an ('a, Foo.error) Result.t into an ('a, Bar.error) Result.t. Exceptions that escape their intended scope, should always be treated as a programming error. The various "finally" functions for resources should catch and reraise them, so that they can reach the outermost scope which knows how best to deal with a programming error in the particular application. The same goes for binding on an Lwt thread which raised an exception or failed: it should cause an exception to be raised to reach the outermost level. The aim here is still to take the erlang-style kill the component that failed and try again approach, but to ensure that there are two distinct return paths for regular errors and programming errors. The secondary aim is to have module signatures which give a clear indication of intended use. Regards, Leo _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Wed Feb 04 13:58:42 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 04 Feb 2015 13:58:42 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YJ0TW-0006DA-UN; Wed, 04 Feb 2015 13:58:38 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YJ0TV-0006D4-A5 for MirageOS-devel@lists.xenproject.org; Wed, 04 Feb 2015 13:58:37 +0000 Received: from [85.158.143.35] by server-3.bemta-4.messagelabs.com id 6A/91-02754-C8522D45; Wed, 04 Feb 2015 13:58:36 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-5.tower-21.messagelabs.com!1423058316!12449618!1 X-Originating-IP: [74.125.82.175] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 1120 invoked from network); 4 Feb 2015 13:58:36 -0000 Received: from mail-we0-f175.google.com (HELO mail-we0-f175.google.com) (74.125.82.175) by server-5.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 4 Feb 2015 13:58:36 -0000 Received: by mail-we0-f175.google.com with SMTP id p10so1898741wes.6 for ; Wed, 04 Feb 2015 05:58:35 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=zvnHE2nik7jd2vW8pFtA5CFef670HMUyhpp6vB26eOk=; b=rLkcsreZqgl6ue02uyyGMYLMgJYpZcqYncmeBOXh2yioOrmKQDBXIDffQyNA1eTRCd BdqSHD4N7QZfelyYe4YIiQ/n/KHI/qGj2Oiq/Apvkk3MiIU4s4pZRU6kgp9T6Aj/sj+i Ffxn/j+EBRtUQfW/Vzpgt7Tn7bb2g8IErH/4m1XbbQ33RLCuPy5EvyxcJBvHHOwX1FSw /+7kSeO7/G/+Y+pd355ND6SQSGoix/7822Ut7RlIGJyOxiv2IeUfwzNUuN/k7i0rW/ik /D0ZJKSdXcJ81xy8FAzDWlfHwhMGPm+WMRFTzf0RkXYKGSzM65tlLDRHtuesOjzYT3M4 eMwA== X-Received: by 10.194.57.199 with SMTP id k7mr68109220wjq.1.1423058315779; Wed, 04 Feb 2015 05:58:35 -0800 (PST) Received: from ?IPv6:2001:630:212:248:99a8:cf61:12f7:823a? ([2001:630:212:248:99a8:cf61:12f7:823a]) by mx.google.com with ESMTPSA id hm6sm2844597wjb.32.2015.02.04.05.58.34 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 04 Feb 2015 05:58:34 -0800 (PST) Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\)) From: Thomas Gazagnaire In-Reply-To: Date: Wed, 4 Feb 2015 13:58:33 +0000 Message-Id: <0BF46653-9D71-4B56-A1F2-80F6B0B1DDA6@gazagnaire.org> References: To: Richard Mortier X-Mailer: Apple Mail (2.1993) Cc: mirageos-devel Subject: Re: [MirageOS-devel] opam / mirage X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org > i'm probably missing something obvious here but i can't spot it so-- > > i'm trying to setup travis for `mirage-tutorial`. i thought i'd use > @samoht fine travis/opam skeleton > (https://github.com/ocaml/ocaml-travisci-skeleton). this assumes that > it's an opam package being tested, so assumes a `./opam` file and uses > `opam` to install dependencies, etc. > > using `./opam` to record the dependencies and other metadata seems > appealing, but always fails because (after pinning) `opam install > mirage-tutorial` calls `make configure` calls `mirage configure` calls > `opam` -- which collides on the opam lock file. > > this seems like a showstopper for doing it this way at all -- is there > an easy way to resolve this? > > in particular, as an alternative, i'm tempted to write and submit a PR > to the opam travis skeleton repo to add an alternative travis script > that uses the same ubuntu setup runes, but then simply calls make > rather than relying on opam to drive the installation. comments? In the short term, a solution would be: - let the `build` field of your opam file empty - add POST_INSTALL_HOOKS="make configure" In the longer term, a better solution would be to let the mirage tool to generate a proper opam file on configure, and we could add a POST_PIN_HOOK to call `mirage configure` before pinning the package. Thomas _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Wed Feb 04 13:58:42 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 04 Feb 2015 13:58:42 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YJ0TW-0006DA-UN; Wed, 04 Feb 2015 13:58:38 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YJ0TV-0006D4-A5 for MirageOS-devel@lists.xenproject.org; Wed, 04 Feb 2015 13:58:37 +0000 Received: from [85.158.143.35] by server-3.bemta-4.messagelabs.com id 6A/91-02754-C8522D45; Wed, 04 Feb 2015 13:58:36 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-5.tower-21.messagelabs.com!1423058316!12449618!1 X-Originating-IP: [74.125.82.175] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 1120 invoked from network); 4 Feb 2015 13:58:36 -0000 Received: from mail-we0-f175.google.com (HELO mail-we0-f175.google.com) (74.125.82.175) by server-5.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 4 Feb 2015 13:58:36 -0000 Received: by mail-we0-f175.google.com with SMTP id p10so1898741wes.6 for ; Wed, 04 Feb 2015 05:58:35 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=zvnHE2nik7jd2vW8pFtA5CFef670HMUyhpp6vB26eOk=; b=rLkcsreZqgl6ue02uyyGMYLMgJYpZcqYncmeBOXh2yioOrmKQDBXIDffQyNA1eTRCd BdqSHD4N7QZfelyYe4YIiQ/n/KHI/qGj2Oiq/Apvkk3MiIU4s4pZRU6kgp9T6Aj/sj+i Ffxn/j+EBRtUQfW/Vzpgt7Tn7bb2g8IErH/4m1XbbQ33RLCuPy5EvyxcJBvHHOwX1FSw /+7kSeO7/G/+Y+pd355ND6SQSGoix/7822Ut7RlIGJyOxiv2IeUfwzNUuN/k7i0rW/ik /D0ZJKSdXcJ81xy8FAzDWlfHwhMGPm+WMRFTzf0RkXYKGSzM65tlLDRHtuesOjzYT3M4 eMwA== X-Received: by 10.194.57.199 with SMTP id k7mr68109220wjq.1.1423058315779; Wed, 04 Feb 2015 05:58:35 -0800 (PST) Received: from ?IPv6:2001:630:212:248:99a8:cf61:12f7:823a? ([2001:630:212:248:99a8:cf61:12f7:823a]) by mx.google.com with ESMTPSA id hm6sm2844597wjb.32.2015.02.04.05.58.34 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 04 Feb 2015 05:58:34 -0800 (PST) Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\)) From: Thomas Gazagnaire In-Reply-To: Date: Wed, 4 Feb 2015 13:58:33 +0000 Message-Id: <0BF46653-9D71-4B56-A1F2-80F6B0B1DDA6@gazagnaire.org> References: To: Richard Mortier X-Mailer: Apple Mail (2.1993) Cc: mirageos-devel Subject: Re: [MirageOS-devel] opam / mirage X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org > i'm probably missing something obvious here but i can't spot it so-- > > i'm trying to setup travis for `mirage-tutorial`. i thought i'd use > @samoht fine travis/opam skeleton > (https://github.com/ocaml/ocaml-travisci-skeleton). this assumes that > it's an opam package being tested, so assumes a `./opam` file and uses > `opam` to install dependencies, etc. > > using `./opam` to record the dependencies and other metadata seems > appealing, but always fails because (after pinning) `opam install > mirage-tutorial` calls `make configure` calls `mirage configure` calls > `opam` -- which collides on the opam lock file. > > this seems like a showstopper for doing it this way at all -- is there > an easy way to resolve this? > > in particular, as an alternative, i'm tempted to write and submit a PR > to the opam travis skeleton repo to add an alternative travis script > that uses the same ubuntu setup runes, but then simply calls make > rather than relying on opam to drive the installation. comments? In the short term, a solution would be: - let the `build` field of your opam file empty - add POST_INSTALL_HOOKS="make configure" In the longer term, a better solution would be to let the mirage tool to generate a proper opam file on configure, and we could add a POST_PIN_HOOK to call `mirage configure` before pinning the package. Thomas _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Wed Feb 04 14:09:33 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 04 Feb 2015 14:09:33 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YJ0e4-0003Ml-Mc; Wed, 04 Feb 2015 14:09:32 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YJ0e4-0003MT-4a for mirageos-devel@lists.xenproject.org; Wed, 04 Feb 2015 14:09:32 +0000 Received: from [193.109.254.147] by server-6.bemta-14.messagelabs.com id 44/14-03164-B1822D45; Wed, 04 Feb 2015 14:09:31 +0000 X-Env-Sender: talex5@gmail.com X-Msg-Ref: server-5.tower-27.messagelabs.com!1423058970!8147663!1 X-Originating-IP: [209.85.215.43] X-SpamReason: No, hits=0.6 required=7.0 tests=MAILTO_TO_SPAM_ADDR, RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6003 invoked from network); 4 Feb 2015 14:09:30 -0000 Received: from mail-la0-f43.google.com (HELO mail-la0-f43.google.com) (209.85.215.43) by server-5.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 4 Feb 2015 14:09:30 -0000 Received: by mail-la0-f43.google.com with SMTP id pn19so1746467lab.2 for ; Wed, 04 Feb 2015 06:09:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=u/f9O4iPJ2uMkyWNyCyKl6bisnnec5UXcpTXPA1MoBg=; b=lJNgkh5HsSxWnEAdNMPSbexnh2nG4lgraJ/f7BpVoe4g/Z28eb96GoywXrnZdZGPum 19xk46KfIsBul/OxD9br+eTtfKy6SmZn6GNJ1hBvmC/i3tSlzidByZmHrqbDMwlQM7gX rQvigyS95VxZ3tKSeWOI3C7r+OJOLlpSdHBNnVsSUiSfX2kZuETMv6FgZtEcjE9n5k6T RtirOzHeEG/+TdiCZJILkOhsr64KLFqTaVZCvxXV2730812eYQv1FayGO7uyr+17fNo/ rk+7tRf2ATKWr8XcEP2IzDwBeY2aE9IF6BE9DQowbKl01vf3LVPlkKw727dFs2yyUGBX msIg== MIME-Version: 1.0 X-Received: by 10.152.29.129 with SMTP id k1mr18666084lah.10.1423058969664; Wed, 04 Feb 2015 06:09:29 -0800 (PST) Received: by 10.25.207.206 with HTTP; Wed, 4 Feb 2015 06:09:29 -0800 (PST) In-Reply-To: <87oap97rvw.fsf@study.localdomain> References: <20150202.014549.1883720051237442569.Christophe.Troestler@umons.ac.be> <20150204.001614.26478837567139584.Christophe.Troestler@umons.ac.be> <87oap97rvw.fsf@study.localdomain> Date: Wed, 4 Feb 2015 14:09:29 +0000 Message-ID: From: Thomas Leonard To: Leo White Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Error handling in Mirage - request for comments! X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 4 February 2015 at 13:01, Leo White wrote: > Hi all, > > As this discussion keeps on running, I thought I would add a couple of > thoughts: > > - The problem with using exceptions for returning errors is that it > becomes very difficult to distinguish between a dynamic error that is > part of normal use (e.g. this network connection failed) from a > programming error (e.g. Not_found accidently leaked from a use of > List.find, an assert false triggering). This makes it hard to produce > the correct behaviour in all cases: there are applications for which > it would be better to kill everyting on detecting a programmer error > rather than risk continuing in an unstable state. I don't think exception vs error code is a reliable way to divide these cases up. Having your FS return `Block_error indicates a serious problem that might require terminating the unikernel, whereas getting a Division_by_zero exception from your HTTP handler is likely fairly harmless. Whether an exception/error is serious depends more on the importance of the thing that raised it. Consider the case of a filesystem that reads a corrupted disk and throws an exception (e.g. an assert fails). This is probably the most extreme case where you'd want to abort. Should it terminate the unikernel? It depends what the disk is being used for. If it's the main hard-disk then possibly. If it's some removable media the user has just inserted then certainly not. A good principle here is that a broken component should only be able to harm itself. If a filesystem fails to handle a corrupted disk correctly then it may further corrupt that disk, but it should not abort the unikernel (and thus possibly corrupt other disks in the middle of being written). In this case, we can imagine a fail-safe FS functor that wraps all the calls in the FS API so that if any one of them throws an unexpected exception then it unplugs the underlying block device. No need to kill everything. > - The problem with using Lwt.t as your error monad is that it becomes > difficult to distiunguish between synchronous things that may return > errors, asynchronous things that may return errors, and asynchornous > things that should not return errors. It also seems tied up with the > exception mechanism, which leads to the same problem as my previous > point. > > Personally, I would probably suggest that all Mirage modules/module > types include in their signatures: > > type error > > val pp_error : formatter -> error -> string > > For cases where an error can reasonably be matched on and handled > specially, this should be exposed in the signature: > > type error = private [> `Foo of foo | `Bar of bar] Aha! I knew you'd know a trick to make this work! However, different functions return different sets of errors. For example, BLOCK.read shouldn't return `Is_read_only. Can we handle that? > val pp_error : formatter -> error -> string I've added some error_message (error -> string) functions, but this might be better. I haven't used formatters much, so don't have an opinion here. But I think we still need an additional "exn_of_error" here because whether something is a "dynamic" (expected) error or a bug changes as the error is propagated. For example, an XML parser probably regards a malformed document as a dynamic error (`Malformed of malformed), which its caller may want to handle. But if the caller is trying to load its configuration file from a crunch FS, then malformed XML is a programming bug and should be thrown as an exception. > Some nice combinators should be provided for using ('a, 'b) Result.t and > ('a, 'b) Result.t Lwt. and for lifting an ('a, Foo.error) Result.t into > an ('a, Bar.error) Result.t. > > Exceptions that escape their intended scope, should always be treated as > a programming error. The various "finally" functions for resources > should catch and reraise them, so that they can reach the outermost > scope which knows how best to deal with a programming error in the > particular application. The same goes for binding on an Lwt thread which > raised an exception or failed: it should cause an exception to be raised > to reach the outermost level. Yes, I think it does this. > The aim here is still to take the erlang-style kill the component that > failed and try again approach, but to ensure that there are two distinct > return paths for regular errors and programming errors. The secondary > aim is to have module signatures which give a clear indication of > intended use. > > Regards, > > Leo -- Dr Thomas Leonard http://0install.net/ GPG: 9242 9807 C985 3C07 44A6 8B9A AE07 8280 59A5 3CC1 GPG: DA98 25AE CAD0 8975 7CDA BD8E 0713 3F96 CA74 D8BA _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Wed Feb 04 14:09:33 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 04 Feb 2015 14:09:33 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YJ0e4-0003Ml-Mc; Wed, 04 Feb 2015 14:09:32 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YJ0e4-0003MT-4a for mirageos-devel@lists.xenproject.org; Wed, 04 Feb 2015 14:09:32 +0000 Received: from [193.109.254.147] by server-6.bemta-14.messagelabs.com id 44/14-03164-B1822D45; Wed, 04 Feb 2015 14:09:31 +0000 X-Env-Sender: talex5@gmail.com X-Msg-Ref: server-5.tower-27.messagelabs.com!1423058970!8147663!1 X-Originating-IP: [209.85.215.43] X-SpamReason: No, hits=0.6 required=7.0 tests=MAILTO_TO_SPAM_ADDR, RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6003 invoked from network); 4 Feb 2015 14:09:30 -0000 Received: from mail-la0-f43.google.com (HELO mail-la0-f43.google.com) (209.85.215.43) by server-5.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 4 Feb 2015 14:09:30 -0000 Received: by mail-la0-f43.google.com with SMTP id pn19so1746467lab.2 for ; Wed, 04 Feb 2015 06:09:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=u/f9O4iPJ2uMkyWNyCyKl6bisnnec5UXcpTXPA1MoBg=; b=lJNgkh5HsSxWnEAdNMPSbexnh2nG4lgraJ/f7BpVoe4g/Z28eb96GoywXrnZdZGPum 19xk46KfIsBul/OxD9br+eTtfKy6SmZn6GNJ1hBvmC/i3tSlzidByZmHrqbDMwlQM7gX rQvigyS95VxZ3tKSeWOI3C7r+OJOLlpSdHBNnVsSUiSfX2kZuETMv6FgZtEcjE9n5k6T RtirOzHeEG/+TdiCZJILkOhsr64KLFqTaVZCvxXV2730812eYQv1FayGO7uyr+17fNo/ rk+7tRf2ATKWr8XcEP2IzDwBeY2aE9IF6BE9DQowbKl01vf3LVPlkKw727dFs2yyUGBX msIg== MIME-Version: 1.0 X-Received: by 10.152.29.129 with SMTP id k1mr18666084lah.10.1423058969664; Wed, 04 Feb 2015 06:09:29 -0800 (PST) Received: by 10.25.207.206 with HTTP; Wed, 4 Feb 2015 06:09:29 -0800 (PST) In-Reply-To: <87oap97rvw.fsf@study.localdomain> References: <20150202.014549.1883720051237442569.Christophe.Troestler@umons.ac.be> <20150204.001614.26478837567139584.Christophe.Troestler@umons.ac.be> <87oap97rvw.fsf@study.localdomain> Date: Wed, 4 Feb 2015 14:09:29 +0000 Message-ID: From: Thomas Leonard To: Leo White Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Error handling in Mirage - request for comments! X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 4 February 2015 at 13:01, Leo White wrote: > Hi all, > > As this discussion keeps on running, I thought I would add a couple of > thoughts: > > - The problem with using exceptions for returning errors is that it > becomes very difficult to distinguish between a dynamic error that is > part of normal use (e.g. this network connection failed) from a > programming error (e.g. Not_found accidently leaked from a use of > List.find, an assert false triggering). This makes it hard to produce > the correct behaviour in all cases: there are applications for which > it would be better to kill everyting on detecting a programmer error > rather than risk continuing in an unstable state. I don't think exception vs error code is a reliable way to divide these cases up. Having your FS return `Block_error indicates a serious problem that might require terminating the unikernel, whereas getting a Division_by_zero exception from your HTTP handler is likely fairly harmless. Whether an exception/error is serious depends more on the importance of the thing that raised it. Consider the case of a filesystem that reads a corrupted disk and throws an exception (e.g. an assert fails). This is probably the most extreme case where you'd want to abort. Should it terminate the unikernel? It depends what the disk is being used for. If it's the main hard-disk then possibly. If it's some removable media the user has just inserted then certainly not. A good principle here is that a broken component should only be able to harm itself. If a filesystem fails to handle a corrupted disk correctly then it may further corrupt that disk, but it should not abort the unikernel (and thus possibly corrupt other disks in the middle of being written). In this case, we can imagine a fail-safe FS functor that wraps all the calls in the FS API so that if any one of them throws an unexpected exception then it unplugs the underlying block device. No need to kill everything. > - The problem with using Lwt.t as your error monad is that it becomes > difficult to distiunguish between synchronous things that may return > errors, asynchronous things that may return errors, and asynchornous > things that should not return errors. It also seems tied up with the > exception mechanism, which leads to the same problem as my previous > point. > > Personally, I would probably suggest that all Mirage modules/module > types include in their signatures: > > type error > > val pp_error : formatter -> error -> string > > For cases where an error can reasonably be matched on and handled > specially, this should be exposed in the signature: > > type error = private [> `Foo of foo | `Bar of bar] Aha! I knew you'd know a trick to make this work! However, different functions return different sets of errors. For example, BLOCK.read shouldn't return `Is_read_only. Can we handle that? > val pp_error : formatter -> error -> string I've added some error_message (error -> string) functions, but this might be better. I haven't used formatters much, so don't have an opinion here. But I think we still need an additional "exn_of_error" here because whether something is a "dynamic" (expected) error or a bug changes as the error is propagated. For example, an XML parser probably regards a malformed document as a dynamic error (`Malformed of malformed), which its caller may want to handle. But if the caller is trying to load its configuration file from a crunch FS, then malformed XML is a programming bug and should be thrown as an exception. > Some nice combinators should be provided for using ('a, 'b) Result.t and > ('a, 'b) Result.t Lwt. and for lifting an ('a, Foo.error) Result.t into > an ('a, Bar.error) Result.t. > > Exceptions that escape their intended scope, should always be treated as > a programming error. The various "finally" functions for resources > should catch and reraise them, so that they can reach the outermost > scope which knows how best to deal with a programming error in the > particular application. The same goes for binding on an Lwt thread which > raised an exception or failed: it should cause an exception to be raised > to reach the outermost level. Yes, I think it does this. > The aim here is still to take the erlang-style kill the component that > failed and try again approach, but to ensure that there are two distinct > return paths for regular errors and programming errors. The secondary > aim is to have module signatures which give a clear indication of > intended use. > > Regards, > > Leo -- Dr Thomas Leonard http://0install.net/ GPG: 9242 9807 C985 3C07 44A6 8B9A AE07 8280 59A5 3CC1 GPG: DA98 25AE CAD0 8975 7CDA BD8E 0713 3F96 CA74 D8BA _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Wed Feb 04 14:40:06 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 04 Feb 2015 14:40:06 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YJ17d-0006F8-ID; Wed, 04 Feb 2015 14:40:05 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YJ17b-0006Ev-S5 for MirageOS-devel@lists.xenproject.org; Wed, 04 Feb 2015 14:40:03 +0000 Received: from [85.158.137.68] by server-10.bemta-3.messagelabs.com id C8/DC-02745-34F22D45; Wed, 04 Feb 2015 14:40:03 +0000 X-Env-Sender: richard.mortier@gmail.com X-Msg-Ref: server-15.tower-31.messagelabs.com!1423060802!11877046!1 X-Originating-IP: [209.85.212.177] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.12.5; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11507 invoked from network); 4 Feb 2015 14:40:02 -0000 Received: from mail-wi0-f177.google.com (HELO mail-wi0-f177.google.com) (209.85.212.177) by server-15.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 4 Feb 2015 14:40:02 -0000 Received: by mail-wi0-f177.google.com with SMTP id r20so4077859wiv.4 for ; Wed, 04 Feb 2015 06:40:01 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=VYD1s7cmeNuBlmPulnD6clMaIorstYORuOA51bNCdO4=; b=YORlUjBANoGaguUNXfYUj/4+wZpXyFjvIsFm4XB/QS4oa6DyjD9PvUTbVnm6Rbz+wp bB5vaG9owuOkS0dRM1YrrV7aT7dE5IzqrefCiVVpSeohLecNuYZK3QTBtP7fC6N78xKu GCP8KdpoR6P5o3fOpH1nsEZx3PUP1wGGi1DwDmZGT8wfXRg6KnfVaMrodd4dcecZelCl h0fAhQwhRPDDg1ezvsTXLZqCEODqTbe4glgmbH0i9fQpKKRHznLXsKlWkFPvXSzdhgdv dnrBDpz2VM/lavKixRIPMDTbQXyjEXQ0s9sfqkNv8QmG8/xducOJRP5Y9/RQMZz2dSdl bGxw== X-Received: by 10.180.149.197 with SMTP id uc5mr45515762wib.80.1423060801724; Wed, 04 Feb 2015 06:40:01 -0800 (PST) Received: from mail-wg0-f46.google.com (mail-wg0-f46.google.com. [74.125.82.46]) by mx.google.com with ESMTPSA id ub1sm2983892wjc.43.2015.02.04.06.40.00 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 04 Feb 2015 06:40:01 -0800 (PST) Received: by mail-wg0-f46.google.com with SMTP id l2so2109878wgh.5 for ; Wed, 04 Feb 2015 06:40:00 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.180.109.46 with SMTP id hp14mr47153055wib.50.1423060800608; Wed, 04 Feb 2015 06:40:00 -0800 (PST) Received: by 10.217.83.83 with HTTP; Wed, 4 Feb 2015 06:40:00 -0800 (PST) In-Reply-To: <0BF46653-9D71-4B56-A1F2-80F6B0B1DDA6@gazagnaire.org> References: <0BF46653-9D71-4B56-A1F2-80F6B0B1DDA6@gazagnaire.org> Date: Wed, 4 Feb 2015 14:40:00 +0000 Message-ID: From: Richard Mortier To: Thomas Gazagnaire Cc: mirageos-devel Subject: Re: [MirageOS-devel] opam / mirage X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 4 February 2015 at 13:58, Thomas Gazagnaire wrote: >> ...this seems like a showstopper for doing it this way at all -- is there >> an easy way to resolve this? >> >> in particular, as an alternative, i'm tempted to write and submit a PR >> to the opam travis skeleton repo to add an alternative travis script >> that uses the same ubuntu setup runes, but then simply calls make >> rather than relying on opam to drive the installation. comments? fwiw (for others, thomas saw already :) i went ahead and did this anyway... > > In the short term, a solution would be: > - let the `build` field of your opam file empty > - add POST_INSTALL_HOOKS="make configure" would that still actually build the repo though, or just configure it? > In the longer term, a better solution would be to let the mirage tool to generate a proper opam file on configure, and we could add a POST_PIN_HOOK to call `mirage configure` before pinning the package. > (presume you mean PRE_PIN_HOOK there, as called before pinning?) having the mirage tool generate an opam file, rather than invoking the opam tool directly seems a good idea to me. if i understand correctly, i guess one would run `mirage configure config.ml` first, then `opam pin . `, then `opam install ` (the latter two taking the place of `make depend && mirage build config.ml`)? -- Richard Mortier richard.mortier@cl.cam.ac.uk _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Wed Feb 04 14:40:06 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 04 Feb 2015 14:40:06 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YJ17d-0006F8-ID; Wed, 04 Feb 2015 14:40:05 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YJ17b-0006Ev-S5 for MirageOS-devel@lists.xenproject.org; Wed, 04 Feb 2015 14:40:03 +0000 Received: from [85.158.137.68] by server-10.bemta-3.messagelabs.com id C8/DC-02745-34F22D45; Wed, 04 Feb 2015 14:40:03 +0000 X-Env-Sender: richard.mortier@gmail.com X-Msg-Ref: server-15.tower-31.messagelabs.com!1423060802!11877046!1 X-Originating-IP: [209.85.212.177] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.12.5; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11507 invoked from network); 4 Feb 2015 14:40:02 -0000 Received: from mail-wi0-f177.google.com (HELO mail-wi0-f177.google.com) (209.85.212.177) by server-15.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 4 Feb 2015 14:40:02 -0000 Received: by mail-wi0-f177.google.com with SMTP id r20so4077859wiv.4 for ; Wed, 04 Feb 2015 06:40:01 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=VYD1s7cmeNuBlmPulnD6clMaIorstYORuOA51bNCdO4=; b=YORlUjBANoGaguUNXfYUj/4+wZpXyFjvIsFm4XB/QS4oa6DyjD9PvUTbVnm6Rbz+wp bB5vaG9owuOkS0dRM1YrrV7aT7dE5IzqrefCiVVpSeohLecNuYZK3QTBtP7fC6N78xKu GCP8KdpoR6P5o3fOpH1nsEZx3PUP1wGGi1DwDmZGT8wfXRg6KnfVaMrodd4dcecZelCl h0fAhQwhRPDDg1ezvsTXLZqCEODqTbe4glgmbH0i9fQpKKRHznLXsKlWkFPvXSzdhgdv dnrBDpz2VM/lavKixRIPMDTbQXyjEXQ0s9sfqkNv8QmG8/xducOJRP5Y9/RQMZz2dSdl bGxw== X-Received: by 10.180.149.197 with SMTP id uc5mr45515762wib.80.1423060801724; Wed, 04 Feb 2015 06:40:01 -0800 (PST) Received: from mail-wg0-f46.google.com (mail-wg0-f46.google.com. [74.125.82.46]) by mx.google.com with ESMTPSA id ub1sm2983892wjc.43.2015.02.04.06.40.00 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 04 Feb 2015 06:40:01 -0800 (PST) Received: by mail-wg0-f46.google.com with SMTP id l2so2109878wgh.5 for ; Wed, 04 Feb 2015 06:40:00 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.180.109.46 with SMTP id hp14mr47153055wib.50.1423060800608; Wed, 04 Feb 2015 06:40:00 -0800 (PST) Received: by 10.217.83.83 with HTTP; Wed, 4 Feb 2015 06:40:00 -0800 (PST) In-Reply-To: <0BF46653-9D71-4B56-A1F2-80F6B0B1DDA6@gazagnaire.org> References: <0BF46653-9D71-4B56-A1F2-80F6B0B1DDA6@gazagnaire.org> Date: Wed, 4 Feb 2015 14:40:00 +0000 Message-ID: From: Richard Mortier To: Thomas Gazagnaire Cc: mirageos-devel Subject: Re: [MirageOS-devel] opam / mirage X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 4 February 2015 at 13:58, Thomas Gazagnaire wrote: >> ...this seems like a showstopper for doing it this way at all -- is there >> an easy way to resolve this? >> >> in particular, as an alternative, i'm tempted to write and submit a PR >> to the opam travis skeleton repo to add an alternative travis script >> that uses the same ubuntu setup runes, but then simply calls make >> rather than relying on opam to drive the installation. comments? fwiw (for others, thomas saw already :) i went ahead and did this anyway... > > In the short term, a solution would be: > - let the `build` field of your opam file empty > - add POST_INSTALL_HOOKS="make configure" would that still actually build the repo though, or just configure it? > In the longer term, a better solution would be to let the mirage tool to generate a proper opam file on configure, and we could add a POST_PIN_HOOK to call `mirage configure` before pinning the package. > (presume you mean PRE_PIN_HOOK there, as called before pinning?) having the mirage tool generate an opam file, rather than invoking the opam tool directly seems a good idea to me. if i understand correctly, i guess one would run `mirage configure config.ml` first, then `opam pin . `, then `opam install ` (the latter two taking the place of `make depend && mirage build config.ml`)? -- Richard Mortier richard.mortier@cl.cam.ac.uk _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Wed Feb 04 15:27:49 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 04 Feb 2015 15:27:49 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YJ1rn-0005S3-Hp; Wed, 04 Feb 2015 15:27:47 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YJ1rm-0005Rl-AD for mirageos-devel@lists.xenproject.org; Wed, 04 Feb 2015 15:27:46 +0000 Received: from [85.158.137.68] by server-6.bemta-3.messagelabs.com id F3/B2-03164-17A32D45; Wed, 04 Feb 2015 15:27:45 +0000 X-Env-Sender: agarwal1975@gmail.com X-Msg-Ref: server-12.tower-31.messagelabs.com!1423063663!11956115!1 X-Originating-IP: [74.125.82.176] X-SpamReason: No, hits=1.5 required=7.0 tests=HTML_20_30,HTML_MESSAGE, MAILTO_TO_SPAM_ADDR,RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.12.5; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7227 invoked from network); 4 Feb 2015 15:27:44 -0000 Received: from mail-we0-f176.google.com (HELO mail-we0-f176.google.com) (74.125.82.176) by server-12.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 4 Feb 2015 15:27:44 -0000 Received: by mail-we0-f176.google.com with SMTP id w62so2413147wes.7 for ; Wed, 04 Feb 2015 07:27:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=jYOM8UKCAw3lMU2+QonMDVyxBRQGEqCImd93+HZqiEQ=; b=E/oy8OmBSq1BBz6gMjSoDV7SlakSLi0Mupi46VyX6nBvpFr+/Nt7CJSCZSFmi5ufnq fvntZydycifJg3lCtUFor1Jvs8Np8cu6dViUIvoqPLCPx5VOG58y4MIoQuOSErLBpSZB V9sg2dbwbES0YopWkv5Trk4H/6azv1DclFjOPUXUW6IImt76uWxuQiXg73gBA4t1sNE9 tuSOkQgPqDIaG+m35v+ucQuWWzhLH/kB6DIPQlpMeFA1AsL8JMp0hAjnWXtCmligmlZ0 1uX4G+VXRlHugkdMliGnvZgv0s8Fa6vE+ObvokCzWTZyAWmUEhUbe2S+PphgbatVHwoO p9dw== X-Received: by 10.180.182.72 with SMTP id ec8mr5610393wic.53.1423063663502; Wed, 04 Feb 2015 07:27:43 -0800 (PST) MIME-Version: 1.0 Received: by 10.27.15.4 with HTTP; Wed, 4 Feb 2015 07:27:23 -0800 (PST) In-Reply-To: References: <20150202.014549.1883720051237442569.Christophe.Troestler@umons.ac.be> <20150204.001614.26478837567139584.Christophe.Troestler@umons.ac.be> <87oap97rvw.fsf@study.localdomain> From: Ashish Agarwal Date: Wed, 4 Feb 2015 10:27:23 -0500 Message-ID: To: Thomas Leonard Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Error handling in Mirage - request for comments! X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============6570188241860577841==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============6570188241860577841== Content-Type: multipart/alternative; boundary=047d7b62494227ecf1050e44d4f5 --047d7b62494227ecf1050e44d4f5 Content-Type: text/plain; charset=UTF-8 > I think we still need an additional "exn_of_error" FYI, Core provides `ok_exn : 'a Or_error.t -> 'a`, which I find very useful. On Wed, Feb 4, 2015 at 9:09 AM, Thomas Leonard wrote: > On 4 February 2015 at 13:01, Leo White wrote: > > Hi all, > > > > As this discussion keeps on running, I thought I would add a couple of > > thoughts: > > > > - The problem with using exceptions for returning errors is that it > > becomes very difficult to distinguish between a dynamic error that is > > part of normal use (e.g. this network connection failed) from a > > programming error (e.g. Not_found accidently leaked from a use of > > List.find, an assert false triggering). This makes it hard to produce > > the correct behaviour in all cases: there are applications for which > > it would be better to kill everyting on detecting a programmer error > > rather than risk continuing in an unstable state. > > I don't think exception vs error code is a reliable way to divide > these cases up. Having your FS return `Block_error indicates a serious > problem that might require terminating the unikernel, whereas getting > a Division_by_zero exception from your HTTP handler is likely fairly > harmless. Whether an exception/error is serious depends more on the > importance of the thing that raised it. > > Consider the case of a filesystem that reads a corrupted disk and > throws an exception (e.g. an assert fails). This is probably the most > extreme case where you'd want to abort. Should it terminate the > unikernel? > > It depends what the disk is being used for. If it's the main hard-disk > then possibly. If it's some removable media the user has just inserted > then certainly not. > > A good principle here is that a broken component should only be able > to harm itself. If a filesystem fails to handle a corrupted disk > correctly then it may further corrupt that disk, but it should not > abort the unikernel (and thus possibly corrupt other disks in the > middle of being written). > > In this case, we can imagine a fail-safe FS functor that wraps all the > calls in the FS API so that if any one of them throws an unexpected > exception then it unplugs the underlying block device. No need to kill > everything. > > > - The problem with using Lwt.t as your error monad is that it becomes > > difficult to distiunguish between synchronous things that may return > > errors, asynchronous things that may return errors, and asynchornous > > things that should not return errors. It also seems tied up with the > > exception mechanism, which leads to the same problem as my previous > > point. > > > > Personally, I would probably suggest that all Mirage modules/module > > types include in their signatures: > > > > type error > > > > val pp_error : formatter -> error -> string > > > > For cases where an error can reasonably be matched on and handled > > specially, this should be exposed in the signature: > > > > type error = private [> `Foo of foo | `Bar of bar] > > Aha! I knew you'd know a trick to make this work! > > However, different functions return different sets of errors. For > example, BLOCK.read shouldn't return `Is_read_only. Can we handle > that? > > > val pp_error : formatter -> error -> string > > I've added some error_message (error -> string) functions, but this > might be better. I haven't used formatters much, so don't have an > opinion here. > > But I think we still need an additional "exn_of_error" here because > whether something is a "dynamic" (expected) error or a bug changes as > the error is propagated. > > For example, an XML parser probably regards a malformed document as a > dynamic error (`Malformed of malformed), which its caller may want to > handle. But if the caller is trying to load its configuration file > from a crunch FS, then malformed XML is a programming bug and should > be thrown as an exception. > > > Some nice combinators should be provided for using ('a, 'b) Result.t and > > ('a, 'b) Result.t Lwt. and for lifting an ('a, Foo.error) Result.t into > > an ('a, Bar.error) Result.t. > > > > Exceptions that escape their intended scope, should always be treated as > > a programming error. The various "finally" functions for resources > > should catch and reraise them, so that they can reach the outermost > > scope which knows how best to deal with a programming error in the > > particular application. The same goes for binding on an Lwt thread which > > raised an exception or failed: it should cause an exception to be raised > > to reach the outermost level. > > Yes, I think it does this. > > > The aim here is still to take the erlang-style kill the component that > > failed and try again approach, but to ensure that there are two distinct > > return paths for regular errors and programming errors. The secondary > > aim is to have module signatures which give a clear indication of > > intended use. > > > > Regards, > > > > Leo > > > > -- > Dr Thomas Leonard http://0install.net/ > GPG: 9242 9807 C985 3C07 44A6 8B9A AE07 8280 59A5 3CC1 > GPG: DA98 25AE CAD0 8975 7CDA BD8E 0713 3F96 CA74 D8BA > > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > --047d7b62494227ecf1050e44d4f5 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
>=C2=A0I t= hink we still need an additional "exn_of_error"

FYI, Core provides `ok_exn : 'a Or_error= .t -> 'a`, which I find very useful.


On Wed, Feb 4, 2015 at 9:09 AM, Thomas= Leonard <talex5@gmail.com> wrote:
On 4 February 2015 at 13:01, Leo White <lpw25@cam.ac.uk> wrote:
> Hi all,
>
> As this discussion keeps on running, I thought I would add a couple of=
> thoughts:
>
> - The problem with using exceptions for returning errors is that it >=C2=A0 =C2=A0becomes very difficult to distinguish between a dynamic er= ror that is
>=C2=A0 =C2=A0part of normal use (e.g. this network connection failed) f= rom a
>=C2=A0 =C2=A0programming error (e.g. Not_found accidently leaked from a= use of
>=C2=A0 =C2=A0List.find, an assert false triggering). This makes it hard= to produce
>=C2=A0 =C2=A0the correct behaviour in all cases: there are applications= for which
>=C2=A0 =C2=A0it would be better to kill everyting on detecting a progra= mmer error
>=C2=A0 =C2=A0rather than risk continuing in an unstable state.

I don't think exception vs error code is a reliable way to divid= e
these cases up. Having your FS return `Block_error indicates a serious
problem that might require terminating the unikernel, whereas getting
a Division_by_zero exception from your HTTP handler is likely fairly
harmless. Whether an exception/error is serious depends more on the
importance of the thing that raised it.

Consider the case of a filesystem that reads a corrupted disk and
throws an exception (e.g. an assert fails). This is probably the most
extreme case where you'd want to abort. Should it terminate the
unikernel?

It depends what the disk is being used for. If it's the main hard-disk<= br> then possibly. If it's some removable media the user has just inserted<= br> then certainly not.

A good principle here is that a broken component should only be able
to harm itself. If a filesystem fails to handle a corrupted disk
correctly then it may further corrupt that disk, but it should not
abort the unikernel (and thus possibly corrupt other disks in the
middle of being written).

In this case, we can imagine a fail-safe FS functor that wraps all the
calls in the FS API so that if any one of them throws an unexpected
exception then it unplugs the underlying block device. No need to kill
everything.

> - The problem with using Lwt.t as your error monad is that it becomes<= br> >=C2=A0 =C2=A0difficult to distiunguish between synchronous things that = may return
>=C2=A0 =C2=A0errors, asynchronous things that may return errors, and as= ynchornous
>=C2=A0 =C2=A0things that should not return errors. It also seems tied u= p with the
>=C2=A0 =C2=A0exception mechanism, which leads to the same problem as my= previous
>=C2=A0 =C2=A0point.
>
> Personally, I would probably suggest that all Mirage modules/module > types include in their signatures:
>
>=C2=A0 =C2=A0type error
>
>=C2=A0 =C2=A0val pp_error : formatter -> error -> string
>
> For cases where an error can reasonably be matched on and handled
> specially, this should be exposed in the signature:
>
>=C2=A0 =C2=A0type error =3D private [> `Foo of foo | `Bar of bar]
Aha! I knew you'd know a trick to make this work!

However, different functions return different sets of errors. For
example, BLOCK.read shouldn't return `Is_read_only. Can we handle
that?

>=C2=A0 =C2=A0val pp_error : formatter -> error -> string

I've added some error_message (error -> string) functions, bu= t this
might be better. I haven't used formatters much, so don't have an opinion here.

But I think we still need an additional "exn_of_error" here becau= se
whether something is a "dynamic" (expected) error or a bug change= s as
the error is propagated.

For example, an XML parser probably regards a malformed document as a
dynamic error (`Malformed of malformed), which its caller may want to
handle. But if the caller is trying to load its configuration file
from a crunch FS, then malformed XML is a programming bug and should
be thrown as an exception.

> Some nice combinators should be provided for using ('a, 'b) Re= sult.t and
> ('a, 'b) Result.t Lwt. and for lifting an ('a, Foo.error) = Result.t into
> an ('a, Bar.error) Result.t.
>
> Exceptions that escape their intended scope, should always be treated = as
> a programming error. The various "finally" functions for res= ources
> should catch and reraise them, so that they can reach the outermost > scope which knows how best to deal with a programming error in the
> particular application. The same goes for binding on an Lwt thread whi= ch
> raised an exception or failed: it should cause an exception to be rais= ed
> to reach the outermost level.

Yes, I think it does this.

> The aim here is still to take the erlang-style kill the component that=
> failed and try again approach, but to ensure that there are two distin= ct
> return paths for regular errors and programming errors. The secondary<= br> > aim is to have module signatures which give a clear indication of
> intended use.
>
> Regards,
>
> Leo



--
Dr Thomas Leonard=C2=A0 =C2=A0 =C2=A0 =C2=A0 http://0install.net/
GPG: 9242 9807 C985 3C07 44A6=C2=A0 8B9A AE07 8280 59A5 3CC1
GPG: DA98 25AE CAD0 8975 7CDA=C2=A0 BD8E 0713 3F96 CA74 D8BA

____________________________= ___________________
MirageOS-devel mailing list
MirageOS-devel@lists= .xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo= /mirageos-devel

--047d7b62494227ecf1050e44d4f5-- --===============6570188241860577841== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --===============6570188241860577841==-- From mirageos-devel-bounces@lists.xenproject.org Wed Feb 04 15:27:49 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 04 Feb 2015 15:27:49 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YJ1rn-0005S3-Hp; Wed, 04 Feb 2015 15:27:47 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YJ1rm-0005Rl-AD for mirageos-devel@lists.xenproject.org; Wed, 04 Feb 2015 15:27:46 +0000 Received: from [85.158.137.68] by server-6.bemta-3.messagelabs.com id F3/B2-03164-17A32D45; Wed, 04 Feb 2015 15:27:45 +0000 X-Env-Sender: agarwal1975@gmail.com X-Msg-Ref: server-12.tower-31.messagelabs.com!1423063663!11956115!1 X-Originating-IP: [74.125.82.176] X-SpamReason: No, hits=1.5 required=7.0 tests=HTML_20_30,HTML_MESSAGE, MAILTO_TO_SPAM_ADDR,RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.12.5; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7227 invoked from network); 4 Feb 2015 15:27:44 -0000 Received: from mail-we0-f176.google.com (HELO mail-we0-f176.google.com) (74.125.82.176) by server-12.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 4 Feb 2015 15:27:44 -0000 Received: by mail-we0-f176.google.com with SMTP id w62so2413147wes.7 for ; Wed, 04 Feb 2015 07:27:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=jYOM8UKCAw3lMU2+QonMDVyxBRQGEqCImd93+HZqiEQ=; b=E/oy8OmBSq1BBz6gMjSoDV7SlakSLi0Mupi46VyX6nBvpFr+/Nt7CJSCZSFmi5ufnq fvntZydycifJg3lCtUFor1Jvs8Np8cu6dViUIvoqPLCPx5VOG58y4MIoQuOSErLBpSZB V9sg2dbwbES0YopWkv5Trk4H/6azv1DclFjOPUXUW6IImt76uWxuQiXg73gBA4t1sNE9 tuSOkQgPqDIaG+m35v+ucQuWWzhLH/kB6DIPQlpMeFA1AsL8JMp0hAjnWXtCmligmlZ0 1uX4G+VXRlHugkdMliGnvZgv0s8Fa6vE+ObvokCzWTZyAWmUEhUbe2S+PphgbatVHwoO p9dw== X-Received: by 10.180.182.72 with SMTP id ec8mr5610393wic.53.1423063663502; Wed, 04 Feb 2015 07:27:43 -0800 (PST) MIME-Version: 1.0 Received: by 10.27.15.4 with HTTP; Wed, 4 Feb 2015 07:27:23 -0800 (PST) In-Reply-To: References: <20150202.014549.1883720051237442569.Christophe.Troestler@umons.ac.be> <20150204.001614.26478837567139584.Christophe.Troestler@umons.ac.be> <87oap97rvw.fsf@study.localdomain> From: Ashish Agarwal Date: Wed, 4 Feb 2015 10:27:23 -0500 Message-ID: To: Thomas Leonard Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Error handling in Mirage - request for comments! X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============6570188241860577841==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============6570188241860577841== Content-Type: multipart/alternative; boundary=047d7b62494227ecf1050e44d4f5 --047d7b62494227ecf1050e44d4f5 Content-Type: text/plain; charset=UTF-8 > I think we still need an additional "exn_of_error" FYI, Core provides `ok_exn : 'a Or_error.t -> 'a`, which I find very useful. On Wed, Feb 4, 2015 at 9:09 AM, Thomas Leonard wrote: > On 4 February 2015 at 13:01, Leo White wrote: > > Hi all, > > > > As this discussion keeps on running, I thought I would add a couple of > > thoughts: > > > > - The problem with using exceptions for returning errors is that it > > becomes very difficult to distinguish between a dynamic error that is > > part of normal use (e.g. this network connection failed) from a > > programming error (e.g. Not_found accidently leaked from a use of > > List.find, an assert false triggering). This makes it hard to produce > > the correct behaviour in all cases: there are applications for which > > it would be better to kill everyting on detecting a programmer error > > rather than risk continuing in an unstable state. > > I don't think exception vs error code is a reliable way to divide > these cases up. Having your FS return `Block_error indicates a serious > problem that might require terminating the unikernel, whereas getting > a Division_by_zero exception from your HTTP handler is likely fairly > harmless. Whether an exception/error is serious depends more on the > importance of the thing that raised it. > > Consider the case of a filesystem that reads a corrupted disk and > throws an exception (e.g. an assert fails). This is probably the most > extreme case where you'd want to abort. Should it terminate the > unikernel? > > It depends what the disk is being used for. If it's the main hard-disk > then possibly. If it's some removable media the user has just inserted > then certainly not. > > A good principle here is that a broken component should only be able > to harm itself. If a filesystem fails to handle a corrupted disk > correctly then it may further corrupt that disk, but it should not > abort the unikernel (and thus possibly corrupt other disks in the > middle of being written). > > In this case, we can imagine a fail-safe FS functor that wraps all the > calls in the FS API so that if any one of them throws an unexpected > exception then it unplugs the underlying block device. No need to kill > everything. > > > - The problem with using Lwt.t as your error monad is that it becomes > > difficult to distiunguish between synchronous things that may return > > errors, asynchronous things that may return errors, and asynchornous > > things that should not return errors. It also seems tied up with the > > exception mechanism, which leads to the same problem as my previous > > point. > > > > Personally, I would probably suggest that all Mirage modules/module > > types include in their signatures: > > > > type error > > > > val pp_error : formatter -> error -> string > > > > For cases where an error can reasonably be matched on and handled > > specially, this should be exposed in the signature: > > > > type error = private [> `Foo of foo | `Bar of bar] > > Aha! I knew you'd know a trick to make this work! > > However, different functions return different sets of errors. For > example, BLOCK.read shouldn't return `Is_read_only. Can we handle > that? > > > val pp_error : formatter -> error -> string > > I've added some error_message (error -> string) functions, but this > might be better. I haven't used formatters much, so don't have an > opinion here. > > But I think we still need an additional "exn_of_error" here because > whether something is a "dynamic" (expected) error or a bug changes as > the error is propagated. > > For example, an XML parser probably regards a malformed document as a > dynamic error (`Malformed of malformed), which its caller may want to > handle. But if the caller is trying to load its configuration file > from a crunch FS, then malformed XML is a programming bug and should > be thrown as an exception. > > > Some nice combinators should be provided for using ('a, 'b) Result.t and > > ('a, 'b) Result.t Lwt. and for lifting an ('a, Foo.error) Result.t into > > an ('a, Bar.error) Result.t. > > > > Exceptions that escape their intended scope, should always be treated as > > a programming error. The various "finally" functions for resources > > should catch and reraise them, so that they can reach the outermost > > scope which knows how best to deal with a programming error in the > > particular application. The same goes for binding on an Lwt thread which > > raised an exception or failed: it should cause an exception to be raised > > to reach the outermost level. > > Yes, I think it does this. > > > The aim here is still to take the erlang-style kill the component that > > failed and try again approach, but to ensure that there are two distinct > > return paths for regular errors and programming errors. The secondary > > aim is to have module signatures which give a clear indication of > > intended use. > > > > Regards, > > > > Leo > > > > -- > Dr Thomas Leonard http://0install.net/ > GPG: 9242 9807 C985 3C07 44A6 8B9A AE07 8280 59A5 3CC1 > GPG: DA98 25AE CAD0 8975 7CDA BD8E 0713 3F96 CA74 D8BA > > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > --047d7b62494227ecf1050e44d4f5 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
>=C2=A0I t= hink we still need an additional "exn_of_error"

FYI, Core provides `ok_exn : 'a Or_error= .t -> 'a`, which I find very useful.


On Wed, Feb 4, 2015 at 9:09 AM, Thomas= Leonard <talex5@gmail.com> wrote:
On 4 February 2015 at 13:01, Leo White <lpw25@cam.ac.uk> wrote:
> Hi all,
>
> As this discussion keeps on running, I thought I would add a couple of=
> thoughts:
>
> - The problem with using exceptions for returning errors is that it >=C2=A0 =C2=A0becomes very difficult to distinguish between a dynamic er= ror that is
>=C2=A0 =C2=A0part of normal use (e.g. this network connection failed) f= rom a
>=C2=A0 =C2=A0programming error (e.g. Not_found accidently leaked from a= use of
>=C2=A0 =C2=A0List.find, an assert false triggering). This makes it hard= to produce
>=C2=A0 =C2=A0the correct behaviour in all cases: there are applications= for which
>=C2=A0 =C2=A0it would be better to kill everyting on detecting a progra= mmer error
>=C2=A0 =C2=A0rather than risk continuing in an unstable state.

I don't think exception vs error code is a reliable way to divid= e
these cases up. Having your FS return `Block_error indicates a serious
problem that might require terminating the unikernel, whereas getting
a Division_by_zero exception from your HTTP handler is likely fairly
harmless. Whether an exception/error is serious depends more on the
importance of the thing that raised it.

Consider the case of a filesystem that reads a corrupted disk and
throws an exception (e.g. an assert fails). This is probably the most
extreme case where you'd want to abort. Should it terminate the
unikernel?

It depends what the disk is being used for. If it's the main hard-disk<= br> then possibly. If it's some removable media the user has just inserted<= br> then certainly not.

A good principle here is that a broken component should only be able
to harm itself. If a filesystem fails to handle a corrupted disk
correctly then it may further corrupt that disk, but it should not
abort the unikernel (and thus possibly corrupt other disks in the
middle of being written).

In this case, we can imagine a fail-safe FS functor that wraps all the
calls in the FS API so that if any one of them throws an unexpected
exception then it unplugs the underlying block device. No need to kill
everything.

> - The problem with using Lwt.t as your error monad is that it becomes<= br> >=C2=A0 =C2=A0difficult to distiunguish between synchronous things that = may return
>=C2=A0 =C2=A0errors, asynchronous things that may return errors, and as= ynchornous
>=C2=A0 =C2=A0things that should not return errors. It also seems tied u= p with the
>=C2=A0 =C2=A0exception mechanism, which leads to the same problem as my= previous
>=C2=A0 =C2=A0point.
>
> Personally, I would probably suggest that all Mirage modules/module > types include in their signatures:
>
>=C2=A0 =C2=A0type error
>
>=C2=A0 =C2=A0val pp_error : formatter -> error -> string
>
> For cases where an error can reasonably be matched on and handled
> specially, this should be exposed in the signature:
>
>=C2=A0 =C2=A0type error =3D private [> `Foo of foo | `Bar of bar]
Aha! I knew you'd know a trick to make this work!

However, different functions return different sets of errors. For
example, BLOCK.read shouldn't return `Is_read_only. Can we handle
that?

>=C2=A0 =C2=A0val pp_error : formatter -> error -> string

I've added some error_message (error -> string) functions, bu= t this
might be better. I haven't used formatters much, so don't have an opinion here.

But I think we still need an additional "exn_of_error" here becau= se
whether something is a "dynamic" (expected) error or a bug change= s as
the error is propagated.

For example, an XML parser probably regards a malformed document as a
dynamic error (`Malformed of malformed), which its caller may want to
handle. But if the caller is trying to load its configuration file
from a crunch FS, then malformed XML is a programming bug and should
be thrown as an exception.

> Some nice combinators should be provided for using ('a, 'b) Re= sult.t and
> ('a, 'b) Result.t Lwt. and for lifting an ('a, Foo.error) = Result.t into
> an ('a, Bar.error) Result.t.
>
> Exceptions that escape their intended scope, should always be treated = as
> a programming error. The various "finally" functions for res= ources
> should catch and reraise them, so that they can reach the outermost > scope which knows how best to deal with a programming error in the
> particular application. The same goes for binding on an Lwt thread whi= ch
> raised an exception or failed: it should cause an exception to be rais= ed
> to reach the outermost level.

Yes, I think it does this.

> The aim here is still to take the erlang-style kill the component that=
> failed and try again approach, but to ensure that there are two distin= ct
> return paths for regular errors and programming errors. The secondary<= br> > aim is to have module signatures which give a clear indication of
> intended use.
>
> Regards,
>
> Leo



--
Dr Thomas Leonard=C2=A0 =C2=A0 =C2=A0 =C2=A0 http://0install.net/
GPG: 9242 9807 C985 3C07 44A6=C2=A0 8B9A AE07 8280 59A5 3CC1
GPG: DA98 25AE CAD0 8975 7CDA=C2=A0 BD8E 0713 3F96 CA74 D8BA

____________________________= ___________________
MirageOS-devel mailing list
MirageOS-devel@lists= .xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo= /mirageos-devel

--047d7b62494227ecf1050e44d4f5-- --===============6570188241860577841== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --===============6570188241860577841==-- From mirageos-devel-bounces@lists.xenproject.org Wed Feb 04 15:28:51 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 04 Feb 2015 15:28:51 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YJ1sp-0005oN-0Y; Wed, 04 Feb 2015 15:28:51 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YJ1sn-0005no-4L for mirageos-devel@lists.xenproject.org; Wed, 04 Feb 2015 15:28:49 +0000 Received: from [85.158.143.35] by server-3.bemta-4.messagelabs.com id 81/FB-02754-0BA32D45; Wed, 04 Feb 2015 15:28:48 +0000 X-Env-Sender: talex5@gmail.com X-Msg-Ref: server-13.tower-21.messagelabs.com!1423063727!5200927!1 X-Originating-IP: [209.85.215.51] X-SpamReason: No, hits=0.8 required=7.0 tests=BODY_RANDOM_LONG, RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11661 invoked from network); 4 Feb 2015 15:28:47 -0000 Received: from mail-la0-f51.google.com (HELO mail-la0-f51.google.com) (209.85.215.51) by server-13.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 4 Feb 2015 15:28:47 -0000 Received: by mail-la0-f51.google.com with SMTP id hv19so926365lab.10 for ; Wed, 04 Feb 2015 07:28:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=LL2bOTyLzamG5CkfgxQvS3IVRBpPEU80uFGs1fX7yzI=; b=rIB1hCQoCf+mmnsyPDfyMe4HogyoVoJdkF947Wc2+gVjYNWIaYLxS6mKOVfmCPyJd8 5a0Bmjjorw1wgWmpmN4GFdQTdyCsgNsk2FGKBdXmPE1Q081RxPUByPHBGHfO2+XM0mE5 x/KFaLlpxzQsEfflPBu6zQX77NZ1qWc1elzglErN03Gy/gqc4XD1sDGzrL0d1UAvvEAr FE2bqvMnLgnBabkhci2XgAn232v2HW0Em+q7m9dqEfGrJcFtMZeiLIZ3cLVUbWwhzFKD 8VFWKK99rk+CSLvv3oWgi0jcnB16nTqVAM12Kv+yESwelh4POyg7dsMKv0mAF5IXQLBA 7HuQ== MIME-Version: 1.0 X-Received: by 10.152.245.44 with SMTP id xl12mr31073632lac.81.1423063727098; Wed, 04 Feb 2015 07:28:47 -0800 (PST) Received: by 10.25.207.206 with HTTP; Wed, 4 Feb 2015 07:28:47 -0800 (PST) In-Reply-To: References: Date: Wed, 4 Feb 2015 15:28:47 +0000 Message-ID: From: Thomas Leonard To: Anil Madhavapeddy Cc: Thomas Gazagnaire , "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Remove DEVICE.connect? X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 26 January 2015 at 11:53, Anil Madhavapeddy wrote: > On 22 Jan 2015, at 14:02, Thomas Gazagnaire wrote: >> >>>>>> So, I propose removing connect from the type signatures (but keeping >>>>>> it in the implementations). Then, being given a device only implies >>>>>> the ability to use it, not the ability to create more devices. >>>> >>>> Can you still easily compose devices together if you don't have a way to connect? Who will be responsible for calling the implementation-dependant connect function? Only the mirage tool in main.ml? (I guess that's already the case) >>> >>> Yes, code that wants to call connect (such as the generated main.ml) >>> has to know the concrete module type. But this is already the case, >>> because the "id" types are all abstract in V1_LWT. >> >> indeed, the mirage tool already has to deal with id of various types, so the changes you are proposing should be fine (and saner). >> >>> It will also mean we can use other signatures for connect (e.g. >>> allowing multiple arguments or optional arguments) if needed. >> >> That's indeed a good argument. If we don't expose the connect fonction, we can use more complex function creators when needed - that's good (and we already kind of quite do that, for instance to init the http stack where we need to construct callbacks in main.ml) > > Sounds like there's consensus here. Thomas, are you cooking up this patch? We might be able to get away with simply hiding the `connect` function and revving the signatures, and not doing a lot of minor releases. Most libraries now explicitly declare "connect" (in their master branches), which means they'll still work when we remove it from mirage-types. These can be released at any time, as they also work with the old signature. There are three remaining patches, which need to be applied together: - Modifying tcpip's stackv4 to take devices rather than IDs. - Modifying mirage to pass devices to stackv4. - Removing "connect" from DEVICE in mirage-types They're all tracked here: https://github.com/mirage/mirage/pull/350 If necessary, we could modify the tcpip patch to add the new constructor while keeping the old one, which would avoid needing to synchronise across packages, but I think we decided to do it all at once in the last call. Once all this is released, we can remove the "with type id" bits from the various libraries and then remove the "id" type from DEVICE too, but there's no hurry there. I've made a mirage-dev branch to test it here: https://github.com/mirage/mirage-dev/pull/54 -- Dr Thomas Leonard http://0install.net/ GPG: 9242 9807 C985 3C07 44A6 8B9A AE07 8280 59A5 3CC1 GPG: DA98 25AE CAD0 8975 7CDA BD8E 0713 3F96 CA74 D8BA _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Wed Feb 04 15:28:51 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 04 Feb 2015 15:28:51 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YJ1sp-0005oN-0Y; Wed, 04 Feb 2015 15:28:51 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YJ1sn-0005no-4L for mirageos-devel@lists.xenproject.org; Wed, 04 Feb 2015 15:28:49 +0000 Received: from [85.158.143.35] by server-3.bemta-4.messagelabs.com id 81/FB-02754-0BA32D45; Wed, 04 Feb 2015 15:28:48 +0000 X-Env-Sender: talex5@gmail.com X-Msg-Ref: server-13.tower-21.messagelabs.com!1423063727!5200927!1 X-Originating-IP: [209.85.215.51] X-SpamReason: No, hits=0.8 required=7.0 tests=BODY_RANDOM_LONG, RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11661 invoked from network); 4 Feb 2015 15:28:47 -0000 Received: from mail-la0-f51.google.com (HELO mail-la0-f51.google.com) (209.85.215.51) by server-13.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 4 Feb 2015 15:28:47 -0000 Received: by mail-la0-f51.google.com with SMTP id hv19so926365lab.10 for ; Wed, 04 Feb 2015 07:28:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=LL2bOTyLzamG5CkfgxQvS3IVRBpPEU80uFGs1fX7yzI=; b=rIB1hCQoCf+mmnsyPDfyMe4HogyoVoJdkF947Wc2+gVjYNWIaYLxS6mKOVfmCPyJd8 5a0Bmjjorw1wgWmpmN4GFdQTdyCsgNsk2FGKBdXmPE1Q081RxPUByPHBGHfO2+XM0mE5 x/KFaLlpxzQsEfflPBu6zQX77NZ1qWc1elzglErN03Gy/gqc4XD1sDGzrL0d1UAvvEAr FE2bqvMnLgnBabkhci2XgAn232v2HW0Em+q7m9dqEfGrJcFtMZeiLIZ3cLVUbWwhzFKD 8VFWKK99rk+CSLvv3oWgi0jcnB16nTqVAM12Kv+yESwelh4POyg7dsMKv0mAF5IXQLBA 7HuQ== MIME-Version: 1.0 X-Received: by 10.152.245.44 with SMTP id xl12mr31073632lac.81.1423063727098; Wed, 04 Feb 2015 07:28:47 -0800 (PST) Received: by 10.25.207.206 with HTTP; Wed, 4 Feb 2015 07:28:47 -0800 (PST) In-Reply-To: References: Date: Wed, 4 Feb 2015 15:28:47 +0000 Message-ID: From: Thomas Leonard To: Anil Madhavapeddy Cc: Thomas Gazagnaire , "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Remove DEVICE.connect? X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 26 January 2015 at 11:53, Anil Madhavapeddy wrote: > On 22 Jan 2015, at 14:02, Thomas Gazagnaire wrote: >> >>>>>> So, I propose removing connect from the type signatures (but keeping >>>>>> it in the implementations). Then, being given a device only implies >>>>>> the ability to use it, not the ability to create more devices. >>>> >>>> Can you still easily compose devices together if you don't have a way to connect? Who will be responsible for calling the implementation-dependant connect function? Only the mirage tool in main.ml? (I guess that's already the case) >>> >>> Yes, code that wants to call connect (such as the generated main.ml) >>> has to know the concrete module type. But this is already the case, >>> because the "id" types are all abstract in V1_LWT. >> >> indeed, the mirage tool already has to deal with id of various types, so the changes you are proposing should be fine (and saner). >> >>> It will also mean we can use other signatures for connect (e.g. >>> allowing multiple arguments or optional arguments) if needed. >> >> That's indeed a good argument. If we don't expose the connect fonction, we can use more complex function creators when needed - that's good (and we already kind of quite do that, for instance to init the http stack where we need to construct callbacks in main.ml) > > Sounds like there's consensus here. Thomas, are you cooking up this patch? We might be able to get away with simply hiding the `connect` function and revving the signatures, and not doing a lot of minor releases. Most libraries now explicitly declare "connect" (in their master branches), which means they'll still work when we remove it from mirage-types. These can be released at any time, as they also work with the old signature. There are three remaining patches, which need to be applied together: - Modifying tcpip's stackv4 to take devices rather than IDs. - Modifying mirage to pass devices to stackv4. - Removing "connect" from DEVICE in mirage-types They're all tracked here: https://github.com/mirage/mirage/pull/350 If necessary, we could modify the tcpip patch to add the new constructor while keeping the old one, which would avoid needing to synchronise across packages, but I think we decided to do it all at once in the last call. Once all this is released, we can remove the "with type id" bits from the various libraries and then remove the "id" type from DEVICE too, but there's no hurry there. I've made a mirage-dev branch to test it here: https://github.com/mirage/mirage-dev/pull/54 -- Dr Thomas Leonard http://0install.net/ GPG: 9242 9807 C985 3C07 44A6 8B9A AE07 8280 59A5 3CC1 GPG: DA98 25AE CAD0 8975 7CDA BD8E 0713 3F96 CA74 D8BA _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Wed Feb 04 15:56:52 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 04 Feb 2015 15:56:52 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YJ2Js-0000uF-KR; Wed, 04 Feb 2015 15:56:48 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YJ2Jq-0000uA-GC for mirageos-devel@lists.xenproject.org; Wed, 04 Feb 2015 15:56:46 +0000 Received: from [85.158.139.211] by server-1.bemta-5.messagelabs.com id 78/A6-25903-D3142D45; Wed, 04 Feb 2015 15:56:45 +0000 X-Env-Sender: daniel.buenzli@erratique.ch X-Msg-Ref: server-11.tower-206.messagelabs.com!1423065404!7031632!1 X-Originating-IP: [74.55.86.74] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNzQuNTUuODYuNzQgPT4gMzA4NTYz\n X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21692 invoked from network); 4 Feb 2015 15:56:44 -0000 Received: from mail6.webfaction.com (HELO smtp.webfaction.com) (74.55.86.74) by server-11.tower-206.messagelabs.com with SMTP; 4 Feb 2015 15:56:44 -0000 Received: from [172.20.10.2] (196-236.197-178.cust.bluewin.ch [178.197.236.196]) by smtp.webfaction.com (Postfix) with ESMTP id D72452093943; Wed, 4 Feb 2015 15:56:37 +0000 (UTC) Date: Wed, 4 Feb 2015 16:56:32 +0100 From: =?utf-8?Q?Daniel_B=C3=BCnzli?= To: Thomas Leonard Message-ID: In-Reply-To: References: <20150202.014549.1883720051237442569.Christophe.Troestler@umons.ac.be> <20150204.001614.26478837567139584.Christophe.Troestler@umons.ac.be> <87oap97rvw.fsf@study.localdomain> X-Mailer: sparrow 1.6.4 (build 1178) MIME-Version: 1.0 Content-Disposition: inline Cc: "=?utf-8?Q?mirageos-devel=40lists.xenproject.org?=" Subject: Re: [MirageOS-devel] Error handling in Mirage - request for comments! X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org TGUgbWVyY3JlZGksIDQgZsOpdnJpZXIgMjAxNSDDoCAxNTowOSwgVGhvbWFzIExlb25hcmQgYSDD qWNyaXQgOgo+IEkgZG9uJ3QgdGhpbmsgZXhjZXB0aW9uIHZzIGVycm9yIGNvZGUgaXMgYSByZWxp YWJsZSB3YXkgdG8gZGl2aWRlCj4gdGhlc2UgY2FzZXMgdXAuIEhhdmluZyB5b3VyIEZTIHJldHVy biBgQmxvY2tfZXJyb3IgaW5kaWNhdGVzIGEgc2VyaW91cwo+IHByb2JsZW0gdGhhdCBtaWdodCBy ZXF1aXJlIHRlcm1pbmF0aW5nIHRoZSB1bmlrZXJuZWwsIHdoZXJlYXMgZ2V0dGluZwo+IGEgRGl2 aXNpb25fYnlfemVybyBleGNlcHRpb24gZnJvbSB5b3VyIEhUVFAgaGFuZGxlciBpcyBsaWtlbHkg ZmFpcmx5Cj4gaGFybWxlc3MuIFdoZXRoZXIgYW4gZXhjZXB0aW9uL2Vycm9yIGlzIHNlcmlvdXMg ZGVwZW5kcyBtb3JlIG9uIHRoZQo+IGltcG9ydGFuY2Ugb2YgdGhlIHRoaW5nIHRoYXQgcmFpc2Vk IGl0LgoKCllvdSBtYXkgd2FudCB0byBoYW5kbGUgdW5leHBlY3RlZCBleGNlcHRpb25zIGJlZm9y ZSB0aGUgdG9wbGV2ZWwgb2YgeW91ciBwcm9ncmFtIGJ1dCB5b3Ugd2FudCB0byBrZWVwIHRoZSB0 d28gZXJyb3IgcmVwb3J0aW5nIG1lY2FuaXNtcyBzZXBhcmF0ZSAodW5leHBlY3RlZCBwcm9ncmFt bWluZyBlcnJvcnMgdnMgZXhwZWN0ZWQgZXJyb3JzKS4gQm90aCBhcmUgYWJsZSB0byBmbG93IHVw IGFuZCBiZSBoYW5kbGVkIHVwIHRvIHdoZXJldmVyIHlvdSB3aXNoLgoKPiBJbiB0aGlzIGNhc2Us IHdlIGNhbiBpbWFnaW5lIGEgZmFpbC1zYWZlIEZTIGZ1bmN0b3IgdGhhdCB3cmFwcyBhbGwgdGhl Cj4gY2FsbHMgaW4gdGhlIEZTIEFQSSBzbyB0aGF0IGlmIGFueSBvbmUgb2YgdGhlbSB0aHJvd3Mg YW4gdW5leHBlY3RlZAo+IGV4Y2VwdGlvbiB0aGVuIGl0IHVucGx1Z3MgdGhlIHVuZGVybHlpbmcg YmxvY2sgZGV2aWNlLiBObyBuZWVkIHRvIGtpbGwKPiBldmVyeXRoaW5nLgoKICAKWW91IGNvdWxk IHR1cm4gdGhlc2UgaW50ZXJuYWwgKnVuZXhwZWN0ZWQqIHByb2dyYW1taW5nIGVycm9ycyBpbnRv IGFuIFtgSW50ZXJuYWxfZXJyb3Igb2YgZXhuXSAqZXhwZWN0ZWQqIGVycm9yIHdoaWNoIGFsbG93 cyBjbGllbnQgdG8gZS5nLiB1bnBsdWcgdGhlIGRldmljZSBpbiB0aGlzIGNhc2UuIEhlcmUgYWdh aW4gSSdkIHN1Z2dlc3QgYSB0cmFwIGFic3RyYWN0aW9uIHRoYXQgaGFzIGEgY2F0Y2ggYWxsIGhh bmRsZXIgZm9yIHRoZSBleGNlcHRpb25zOiAgCgoKCnR5cGUgJ2EgdHJhcAp2YWwgdHJhcCA6ICgn YSAtPiAnYikgLT4gJ2EgLT4gJ2IgdHJhcAp2YWwgdW50cmFwIDogJ2EgdHJhcCAtPiAoJ2EsIFs+ IGBJbnRlcm5hbF9lcnJvciBvZiBleG5dKSByZXN1bHQK4oCmICgqIG1heWJlIGEgZmV3IG90aGVy IGNvbWJpbmF0b3JzIHRoYXQgaGFuZGxlIG5pY2VseSAnYSB0cmFwIHdoZW4gJ2EgPSAoJ2IsICdj KSByZXN1bHQgYW5kIGEgZmV3IG90aGVyIHRvIGFjdCBkaXJlY3RseSBvbiB0b3Agb2YgdGhlIGNv bmN1cmVuY3kgbW9uYWQgKikKCkJ5IGp1ZGljaW91c2x5IHBsYWNpbmcgdHJhcCB2YWx1ZXMgaW4g bWlyYWdlIHNpZ25hdHVyZXMgeW91IGNvdWxkIGVuZm9yY2Ugc2FmZSBwb2ludHMgaW4gdGhlIHN5 c3RlbSBhbmQgdGhlaXIgaGFuZGxpbmcgKG9yIG5vdCBpZiB0aGUgdXNlcnMgbGV0cyB0aGUgZXhw ZWN0ZWQgZXJyb3IgZmxvdyB1cCkgYnkgdGhlIGNvbXBvbmVudCB1c2Vycy4gIAoKSSBkaWRuJ3Qg dGhpbmsgbXVjaCBhYm91dCB0aGlzIGJ1dCBJIHN1c3BlY3QgdGhlIHRyYXAgY291bGQgYmUgZGly ZWN0bHkgYnVuZGxlZCBpbiBtaXJhZ2UncyBkZWZpbml0aW9uIG9mIHRoZSBgcmVzdWx0YCB0eXBl LiAgCiAgCgo+IEhvd2V2ZXIsIGRpZmZlcmVudCBmdW5jdGlvbnMgcmV0dXJuIGRpZmZlcmVudCBz ZXRzIG9mIGVycm9ycy4gRm9yCj4gZXhhbXBsZSwgQkxPQ0sucmVhZCBzaG91bGRuJ3QgcmV0dXJu IGBJc19yZWFkX29ubHkuIENhbiB3ZSBoYW5kbGUKPiB0aGF0PwoKCnR5cGUgd3JpdGVfZXJyb3Ig PSBbIGBSZWFkX29ubHkgfCDigKYgXQp0eXBlIHJlYWRfZXJyb3IgPSBbIGBXcml0ZV9vbmx5IHwg 4oCmIF0KdHlwZSBlcnJvciA9IFsgcmVhZF9lcnJvciB8IHdyaXRlX2Vycm9yIF0KCnZhbCBCTE9D Sy5yZWFkIDog4oCmIC0+IChpbnQsIFs+IHJlYWRfZXJyb3JdKSByZXN1bHQKICAKPiBJJ3ZlIGFk ZGVkIHNvbWUgZXJyb3JfbWVzc2FnZSAoZXJyb3IgLT4gc3RyaW5nKSBmdW5jdGlvbnMsIGJ1dCB0 aGlzCj4gbWlnaHQgYmUgYmV0dGVyLiBJIGhhdmVuJ3QgdXNlZCBmb3JtYXR0ZXJzIG11Y2gsIHNv IGRvbid0IGhhdmUgYW4KPiBvcGluaW9uIGhlcmUuCgpBY3R1YWxseSB0aGlzIHNob3VsZCBoYXZl IHJlYWQgYHBwX2Vycm9yIDogZm9ybWF0dGVyIC0+IGVycm9yIC0+IHVuaXRgLiBGb3JtYXR0ZXJz IGFyZSBuaWNlciBpZiB5b3Ugd2FudCB0byBwcmV0dHkgcHJpbnQgZXJyb3JzLiBPbmNlIHlvdSBo YXZlIGEgYmFzZSBzZXQgb2YgY29tYmluYXRvcnMgZm9yIHByaW50aW5nIG9wdGlvbnMsIGxpc3Rz LCBldGMuICh3aGljaCBhcmUgc2FkbHkgbWlzc2luZyBmcm9tIHRoZSBzdGRsaWIpIHRoZXkgY29t cG9zZSB3ZWxsLiBUbyBzdHJpbmcgZnVuY3Rpb25zIGFyZSBqdXN0IGEgYEZvcm1hdC5hc3ByaW50 ZiAiJWEiIHBwX2Vycm9yYCwgYXdheS4gIAoKPiBCdXQgSSB0aGluayB3ZSBzdGlsbCBuZWVkIGFu IGFkZGl0aW9uYWwgImV4bl9vZl9lcnJvciIgaGVyZSBiZWNhdXNlCj4gd2hldGhlciBzb21ldGhp bmcgaXMgYSAiZHluYW1pYyIgKGV4cGVjdGVkKSBlcnJvciBvciBhIGJ1ZyBjaGFuZ2VzIGFzCj4g dGhlIGVycm9yIGlzIHByb3BhZ2F0ZWQuCj4gIAo+IEZvciBleGFtcGxlLCBhbiBYTUwgcGFyc2Vy IHByb2JhYmx5IHJlZ2FyZHMgYSBtYWxmb3JtZWQgZG9jdW1lbnQgYXMgYQo+IGR5bmFtaWMgZXJy b3IgKGBNYWxmb3JtZWQgb2YgbWFsZm9ybWVkKSwgd2hpY2ggaXRzIGNhbGxlciBtYXkgd2FudCB0 bwo+IGhhbmRsZS4gQnV0IGlmIHRoZSBjYWxsZXIgaXMgdHJ5aW5nIHRvIGxvYWQgaXRzIGNvbmZp Z3VyYXRpb24gZmlsZQo+IGZyb20gYSBjcnVuY2ggRlMsIHRoZW4gbWFsZm9ybWVkIFhNTCBpcyBh IHByb2dyYW1taW5nIGJ1ZyBhbmQgc2hvdWxkCj4gYmUgdGhyb3duIGFzIGFuIGV4Y2VwdGlvbi4K CldvdWxkbid0IHlvdSBzaW1wbHkgdHVybiB0aGF0IGludG8gYW4gYXNzZXJ0IGZhbHNlIChvciBs ZXQncyBzYXkgaW52YWxpZF9hcmd1bWVudCBpZiB5b3Ugd2FudCB0byBwcCB0aGUgbWVzc2FnZSkg PyAgCgpCZXN0LAoKRGFuaWVsCgpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fXwpNaXJhZ2VPUy1kZXZlbCBtYWlsaW5nIGxpc3QKTWlyYWdlT1MtZGV2ZWxAbGlz dHMueGVucHJvamVjdC5vcmcKaHR0cDovL2xpc3RzLnhlbnByb2plY3Qub3JnL2NnaS1iaW4vbWFp bG1hbi9saXN0aW5mby9taXJhZ2Vvcy1kZXZlbAo= From mirageos-devel-bounces@lists.xenproject.org Wed Feb 04 15:56:52 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 04 Feb 2015 15:56:52 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YJ2Js-0000uF-KR; Wed, 04 Feb 2015 15:56:48 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YJ2Jq-0000uA-GC for mirageos-devel@lists.xenproject.org; Wed, 04 Feb 2015 15:56:46 +0000 Received: from [85.158.139.211] by server-1.bemta-5.messagelabs.com id 78/A6-25903-D3142D45; Wed, 04 Feb 2015 15:56:45 +0000 X-Env-Sender: daniel.buenzli@erratique.ch X-Msg-Ref: server-11.tower-206.messagelabs.com!1423065404!7031632!1 X-Originating-IP: [74.55.86.74] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNzQuNTUuODYuNzQgPT4gMzA4NTYz\n X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21692 invoked from network); 4 Feb 2015 15:56:44 -0000 Received: from mail6.webfaction.com (HELO smtp.webfaction.com) (74.55.86.74) by server-11.tower-206.messagelabs.com with SMTP; 4 Feb 2015 15:56:44 -0000 Received: from [172.20.10.2] (196-236.197-178.cust.bluewin.ch [178.197.236.196]) by smtp.webfaction.com (Postfix) with ESMTP id D72452093943; Wed, 4 Feb 2015 15:56:37 +0000 (UTC) Date: Wed, 4 Feb 2015 16:56:32 +0100 From: =?utf-8?Q?Daniel_B=C3=BCnzli?= To: Thomas Leonard Message-ID: In-Reply-To: References: <20150202.014549.1883720051237442569.Christophe.Troestler@umons.ac.be> <20150204.001614.26478837567139584.Christophe.Troestler@umons.ac.be> <87oap97rvw.fsf@study.localdomain> X-Mailer: sparrow 1.6.4 (build 1178) MIME-Version: 1.0 Content-Disposition: inline Cc: "=?utf-8?Q?mirageos-devel=40lists.xenproject.org?=" Subject: Re: [MirageOS-devel] Error handling in Mirage - request for comments! X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org TGUgbWVyY3JlZGksIDQgZsOpdnJpZXIgMjAxNSDDoCAxNTowOSwgVGhvbWFzIExlb25hcmQgYSDD qWNyaXQgOgo+IEkgZG9uJ3QgdGhpbmsgZXhjZXB0aW9uIHZzIGVycm9yIGNvZGUgaXMgYSByZWxp YWJsZSB3YXkgdG8gZGl2aWRlCj4gdGhlc2UgY2FzZXMgdXAuIEhhdmluZyB5b3VyIEZTIHJldHVy biBgQmxvY2tfZXJyb3IgaW5kaWNhdGVzIGEgc2VyaW91cwo+IHByb2JsZW0gdGhhdCBtaWdodCBy ZXF1aXJlIHRlcm1pbmF0aW5nIHRoZSB1bmlrZXJuZWwsIHdoZXJlYXMgZ2V0dGluZwo+IGEgRGl2 aXNpb25fYnlfemVybyBleGNlcHRpb24gZnJvbSB5b3VyIEhUVFAgaGFuZGxlciBpcyBsaWtlbHkg ZmFpcmx5Cj4gaGFybWxlc3MuIFdoZXRoZXIgYW4gZXhjZXB0aW9uL2Vycm9yIGlzIHNlcmlvdXMg ZGVwZW5kcyBtb3JlIG9uIHRoZQo+IGltcG9ydGFuY2Ugb2YgdGhlIHRoaW5nIHRoYXQgcmFpc2Vk IGl0LgoKCllvdSBtYXkgd2FudCB0byBoYW5kbGUgdW5leHBlY3RlZCBleGNlcHRpb25zIGJlZm9y ZSB0aGUgdG9wbGV2ZWwgb2YgeW91ciBwcm9ncmFtIGJ1dCB5b3Ugd2FudCB0byBrZWVwIHRoZSB0 d28gZXJyb3IgcmVwb3J0aW5nIG1lY2FuaXNtcyBzZXBhcmF0ZSAodW5leHBlY3RlZCBwcm9ncmFt bWluZyBlcnJvcnMgdnMgZXhwZWN0ZWQgZXJyb3JzKS4gQm90aCBhcmUgYWJsZSB0byBmbG93IHVw IGFuZCBiZSBoYW5kbGVkIHVwIHRvIHdoZXJldmVyIHlvdSB3aXNoLgoKPiBJbiB0aGlzIGNhc2Us IHdlIGNhbiBpbWFnaW5lIGEgZmFpbC1zYWZlIEZTIGZ1bmN0b3IgdGhhdCB3cmFwcyBhbGwgdGhl Cj4gY2FsbHMgaW4gdGhlIEZTIEFQSSBzbyB0aGF0IGlmIGFueSBvbmUgb2YgdGhlbSB0aHJvd3Mg YW4gdW5leHBlY3RlZAo+IGV4Y2VwdGlvbiB0aGVuIGl0IHVucGx1Z3MgdGhlIHVuZGVybHlpbmcg YmxvY2sgZGV2aWNlLiBObyBuZWVkIHRvIGtpbGwKPiBldmVyeXRoaW5nLgoKICAKWW91IGNvdWxk IHR1cm4gdGhlc2UgaW50ZXJuYWwgKnVuZXhwZWN0ZWQqIHByb2dyYW1taW5nIGVycm9ycyBpbnRv IGFuIFtgSW50ZXJuYWxfZXJyb3Igb2YgZXhuXSAqZXhwZWN0ZWQqIGVycm9yIHdoaWNoIGFsbG93 cyBjbGllbnQgdG8gZS5nLiB1bnBsdWcgdGhlIGRldmljZSBpbiB0aGlzIGNhc2UuIEhlcmUgYWdh aW4gSSdkIHN1Z2dlc3QgYSB0cmFwIGFic3RyYWN0aW9uIHRoYXQgaGFzIGEgY2F0Y2ggYWxsIGhh bmRsZXIgZm9yIHRoZSBleGNlcHRpb25zOiAgCgoKCnR5cGUgJ2EgdHJhcAp2YWwgdHJhcCA6ICgn YSAtPiAnYikgLT4gJ2EgLT4gJ2IgdHJhcAp2YWwgdW50cmFwIDogJ2EgdHJhcCAtPiAoJ2EsIFs+ IGBJbnRlcm5hbF9lcnJvciBvZiBleG5dKSByZXN1bHQK4oCmICgqIG1heWJlIGEgZmV3IG90aGVy IGNvbWJpbmF0b3JzIHRoYXQgaGFuZGxlIG5pY2VseSAnYSB0cmFwIHdoZW4gJ2EgPSAoJ2IsICdj KSByZXN1bHQgYW5kIGEgZmV3IG90aGVyIHRvIGFjdCBkaXJlY3RseSBvbiB0b3Agb2YgdGhlIGNv bmN1cmVuY3kgbW9uYWQgKikKCkJ5IGp1ZGljaW91c2x5IHBsYWNpbmcgdHJhcCB2YWx1ZXMgaW4g bWlyYWdlIHNpZ25hdHVyZXMgeW91IGNvdWxkIGVuZm9yY2Ugc2FmZSBwb2ludHMgaW4gdGhlIHN5 c3RlbSBhbmQgdGhlaXIgaGFuZGxpbmcgKG9yIG5vdCBpZiB0aGUgdXNlcnMgbGV0cyB0aGUgZXhw ZWN0ZWQgZXJyb3IgZmxvdyB1cCkgYnkgdGhlIGNvbXBvbmVudCB1c2Vycy4gIAoKSSBkaWRuJ3Qg dGhpbmsgbXVjaCBhYm91dCB0aGlzIGJ1dCBJIHN1c3BlY3QgdGhlIHRyYXAgY291bGQgYmUgZGly ZWN0bHkgYnVuZGxlZCBpbiBtaXJhZ2UncyBkZWZpbml0aW9uIG9mIHRoZSBgcmVzdWx0YCB0eXBl LiAgCiAgCgo+IEhvd2V2ZXIsIGRpZmZlcmVudCBmdW5jdGlvbnMgcmV0dXJuIGRpZmZlcmVudCBz ZXRzIG9mIGVycm9ycy4gRm9yCj4gZXhhbXBsZSwgQkxPQ0sucmVhZCBzaG91bGRuJ3QgcmV0dXJu IGBJc19yZWFkX29ubHkuIENhbiB3ZSBoYW5kbGUKPiB0aGF0PwoKCnR5cGUgd3JpdGVfZXJyb3Ig PSBbIGBSZWFkX29ubHkgfCDigKYgXQp0eXBlIHJlYWRfZXJyb3IgPSBbIGBXcml0ZV9vbmx5IHwg 4oCmIF0KdHlwZSBlcnJvciA9IFsgcmVhZF9lcnJvciB8IHdyaXRlX2Vycm9yIF0KCnZhbCBCTE9D Sy5yZWFkIDog4oCmIC0+IChpbnQsIFs+IHJlYWRfZXJyb3JdKSByZXN1bHQKICAKPiBJJ3ZlIGFk ZGVkIHNvbWUgZXJyb3JfbWVzc2FnZSAoZXJyb3IgLT4gc3RyaW5nKSBmdW5jdGlvbnMsIGJ1dCB0 aGlzCj4gbWlnaHQgYmUgYmV0dGVyLiBJIGhhdmVuJ3QgdXNlZCBmb3JtYXR0ZXJzIG11Y2gsIHNv IGRvbid0IGhhdmUgYW4KPiBvcGluaW9uIGhlcmUuCgpBY3R1YWxseSB0aGlzIHNob3VsZCBoYXZl IHJlYWQgYHBwX2Vycm9yIDogZm9ybWF0dGVyIC0+IGVycm9yIC0+IHVuaXRgLiBGb3JtYXR0ZXJz IGFyZSBuaWNlciBpZiB5b3Ugd2FudCB0byBwcmV0dHkgcHJpbnQgZXJyb3JzLiBPbmNlIHlvdSBo YXZlIGEgYmFzZSBzZXQgb2YgY29tYmluYXRvcnMgZm9yIHByaW50aW5nIG9wdGlvbnMsIGxpc3Rz LCBldGMuICh3aGljaCBhcmUgc2FkbHkgbWlzc2luZyBmcm9tIHRoZSBzdGRsaWIpIHRoZXkgY29t cG9zZSB3ZWxsLiBUbyBzdHJpbmcgZnVuY3Rpb25zIGFyZSBqdXN0IGEgYEZvcm1hdC5hc3ByaW50 ZiAiJWEiIHBwX2Vycm9yYCwgYXdheS4gIAoKPiBCdXQgSSB0aGluayB3ZSBzdGlsbCBuZWVkIGFu IGFkZGl0aW9uYWwgImV4bl9vZl9lcnJvciIgaGVyZSBiZWNhdXNlCj4gd2hldGhlciBzb21ldGhp bmcgaXMgYSAiZHluYW1pYyIgKGV4cGVjdGVkKSBlcnJvciBvciBhIGJ1ZyBjaGFuZ2VzIGFzCj4g dGhlIGVycm9yIGlzIHByb3BhZ2F0ZWQuCj4gIAo+IEZvciBleGFtcGxlLCBhbiBYTUwgcGFyc2Vy IHByb2JhYmx5IHJlZ2FyZHMgYSBtYWxmb3JtZWQgZG9jdW1lbnQgYXMgYQo+IGR5bmFtaWMgZXJy b3IgKGBNYWxmb3JtZWQgb2YgbWFsZm9ybWVkKSwgd2hpY2ggaXRzIGNhbGxlciBtYXkgd2FudCB0 bwo+IGhhbmRsZS4gQnV0IGlmIHRoZSBjYWxsZXIgaXMgdHJ5aW5nIHRvIGxvYWQgaXRzIGNvbmZp Z3VyYXRpb24gZmlsZQo+IGZyb20gYSBjcnVuY2ggRlMsIHRoZW4gbWFsZm9ybWVkIFhNTCBpcyBh IHByb2dyYW1taW5nIGJ1ZyBhbmQgc2hvdWxkCj4gYmUgdGhyb3duIGFzIGFuIGV4Y2VwdGlvbi4K CldvdWxkbid0IHlvdSBzaW1wbHkgdHVybiB0aGF0IGludG8gYW4gYXNzZXJ0IGZhbHNlIChvciBs ZXQncyBzYXkgaW52YWxpZF9hcmd1bWVudCBpZiB5b3Ugd2FudCB0byBwcCB0aGUgbWVzc2FnZSkg PyAgCgpCZXN0LAoKRGFuaWVsCgpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fXwpNaXJhZ2VPUy1kZXZlbCBtYWlsaW5nIGxpc3QKTWlyYWdlT1MtZGV2ZWxAbGlz dHMueGVucHJvamVjdC5vcmcKaHR0cDovL2xpc3RzLnhlbnByb2plY3Qub3JnL2NnaS1iaW4vbWFp bG1hbi9saXN0aW5mby9taXJhZ2Vvcy1kZXZlbAo= From mirageos-devel-bounces@lists.xenproject.org Wed Feb 04 17:51:37 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 04 Feb 2015 17:51:37 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YJ46v-0008Js-3v; Wed, 04 Feb 2015 17:51:33 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YJ46u-0008Jn-4s for mirageos-devel@lists.xenproject.org; Wed, 04 Feb 2015 17:51:32 +0000 Received: from [193.109.254.147] by server-14.bemta-14.messagelabs.com id D2/F3-02753-32C52D45; Wed, 04 Feb 2015 17:51:31 +0000 X-Env-Sender: lpw25@cam.ac.uk X-Msg-Ref: server-16.tower-27.messagelabs.com!1423072290!7435495!1 X-Originating-IP: [131.111.8.140] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 24213 invoked from network); 4 Feb 2015 17:51:30 -0000 Received: from ppsw-40.csi.cam.ac.uk (HELO ppsw-40.csi.cam.ac.uk) (131.111.8.140) by server-16.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 4 Feb 2015 17:51:30 -0000 X-Cam-AntiVirus: no malware found X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/ Received: from host86-190-253-201.range86-190.btcentralplus.com ([86.190.253.201]:33175 helo=study.localdomain) by ppsw-40.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.156]:587) with esmtpsa (PLAIN:lpw25) (TLSv1.2:AES128-GCM-SHA256:128) id 1YJ46s-0005Gz-jJ (Exim 4.82_3-c0e5623) (return-path ); Wed, 04 Feb 2015 17:51:30 +0000 From: Leo White To: Thomas Leonard References: <20150202.014549.1883720051237442569.Christophe.Troestler@umons.ac.be> <20150204.001614.26478837567139584.Christophe.Troestler@umons.ac.be> <87oap97rvw.fsf@study.localdomain> X-Face: "XWxb[u_Z\PA_Y?9@|IA!!+jTb(/290-*ea/Un$I0B98.$n%eL.; 2w*,z]WR#T:,p[ NBd++M7l]#7zj7!{~iw $W-"/=|dVjhT[D{4~gE}gK<2`.6fs!;uqqud]vs2N/3^m7{aS1V, Date: Wed, 04 Feb 2015 17:51:04 +0000 In-Reply-To: (Thomas Leonard's message of "Wed, 4 Feb 2015 14:09:29 +0000") Message-ID: <87h9v17egn.fsf@study.localdomain> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) MIME-Version: 1.0 Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Error handling in Mirage - request for comments! X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org > I don't think exception vs error code is a reliable way to divide > these cases up. Having your FS return `Block_error indicates a serious > problem that might require terminating the unikernel, whereas getting > a Division_by_zero exception from your HTTP handler is likely fairly > harmless. Whether an exception/error is serious depends more on the > importance of the thing that raised it. > > Consider the case of a filesystem that reads a corrupted disk and > throws an exception (e.g. an assert fails). This is probably the most > extreme case where you'd want to abort. Should it terminate the > unikernel? > > It depends what the disk is being used for. If it's the main hard-disk > then possibly. If it's some removable media the user has just inserted > then certainly not. > > A good principle here is that a broken component should only be able > to harm itself. If a filesystem fails to handle a corrupted disk > correctly then it may further corrupt that disk, but it should not > abort the unikernel (and thus possibly corrupt other disks in the > middle of being written). > > In this case, we can imagine a fail-safe FS functor that wraps all the > calls in the FS API so that if any one of them throws an unexpected > exception then it unplugs the underlying block device. No need to kill > everything. > I think Daniel summed this up quite well. You are quite right that in different components the correct way to deal with programmer errors differs, but the point is that you need to keep the two kinds of errors (dynamic/expected and programmer/unexpected) separate in order to deal with them appropriately. Unexpected errors mean that there is a bug in the code and in some components they should be treated extremely seriously. They should also probably be reported differently to encourage bug reports. >> - The problem with using Lwt.t as your error monad is that it becomes >> difficult to distiunguish between synchronous things that may return >> errors, asynchronous things that may return errors, and asynchornous >> things that should not return errors. It also seems tied up with the >> exception mechanism, which leads to the same problem as my previous >> point. >> >> Personally, I would probably suggest that all Mirage modules/module >> types include in their signatures: >> >> type error >> >> val pp_error : formatter -> error -> string >> >> For cases where an error can reasonably be matched on and handled >> specially, this should be exposed in the signature: >> >> type error = private [> `Foo of foo | `Bar of bar] > > Aha! I knew you'd know a trick to make this work! > > However, different functions return different sets of errors. For > example, BLOCK.read shouldn't return `Is_read_only. Can we handle > that? > When defining the error types internally you can use: type write_error = [`Read_only | `Foo ] type read_error = [`Write_only | `Bar ] type error = [read_error | write_error ] However, when writing the signatures, the thing that you would naturally like to write for this: type write_error = [> `Read_only ] type read_error = [> `Write_only ] type error = [> read_error | write_error ] doesn't work because OCaml's row polymorphism is annoyingly weak (one day I shall find time to have my way with it and fix this problem). However, all you are really gaining from: type error = [> read_error | write_error ] are free (and sometimes implicit) coercions from write_error and read_error into error. So the following signature is a reasonable substitute: type write_error = [> `Read_only ] type read_error = [> `Write_only ] type error = [> `Read_only | `Write_only ] val error_of_write_error : write_error -> error val error_of_read_error : read_error -> error you could also provide some conveniences like: pp_error : formatter -> error -> unit pp_write_error : formatter -> write_error -> unit pp_read_error : formatter -> read_error -> unit > But I think we still need an additional "exn_of_error" here because > whether something is a "dynamic" (expected) error or a bug changes as > the error is propagated. Sure, sometimes an "expected" error is not actually expected. It seems to me that: exception Error : 'a * (formatter -> 'a -> unit) -> exn should do the trick, allowing you to wrap up the error and its printer as an exception. (Note using existential variables directly in exceptions like this requires 4.02, for earlier versions you must nest a GADT within the exception). Regards, Leo _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Wed Feb 04 17:51:37 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 04 Feb 2015 17:51:37 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YJ46v-0008Js-3v; Wed, 04 Feb 2015 17:51:33 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YJ46u-0008Jn-4s for mirageos-devel@lists.xenproject.org; Wed, 04 Feb 2015 17:51:32 +0000 Received: from [193.109.254.147] by server-14.bemta-14.messagelabs.com id D2/F3-02753-32C52D45; Wed, 04 Feb 2015 17:51:31 +0000 X-Env-Sender: lpw25@cam.ac.uk X-Msg-Ref: server-16.tower-27.messagelabs.com!1423072290!7435495!1 X-Originating-IP: [131.111.8.140] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 24213 invoked from network); 4 Feb 2015 17:51:30 -0000 Received: from ppsw-40.csi.cam.ac.uk (HELO ppsw-40.csi.cam.ac.uk) (131.111.8.140) by server-16.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 4 Feb 2015 17:51:30 -0000 X-Cam-AntiVirus: no malware found X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/ Received: from host86-190-253-201.range86-190.btcentralplus.com ([86.190.253.201]:33175 helo=study.localdomain) by ppsw-40.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.156]:587) with esmtpsa (PLAIN:lpw25) (TLSv1.2:AES128-GCM-SHA256:128) id 1YJ46s-0005Gz-jJ (Exim 4.82_3-c0e5623) (return-path ); Wed, 04 Feb 2015 17:51:30 +0000 From: Leo White To: Thomas Leonard References: <20150202.014549.1883720051237442569.Christophe.Troestler@umons.ac.be> <20150204.001614.26478837567139584.Christophe.Troestler@umons.ac.be> <87oap97rvw.fsf@study.localdomain> X-Face: "XWxb[u_Z\PA_Y?9@|IA!!+jTb(/290-*ea/Un$I0B98.$n%eL.; 2w*,z]WR#T:,p[ NBd++M7l]#7zj7!{~iw $W-"/=|dVjhT[D{4~gE}gK<2`.6fs!;uqqud]vs2N/3^m7{aS1V, Date: Wed, 04 Feb 2015 17:51:04 +0000 In-Reply-To: (Thomas Leonard's message of "Wed, 4 Feb 2015 14:09:29 +0000") Message-ID: <87h9v17egn.fsf@study.localdomain> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) MIME-Version: 1.0 Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Error handling in Mirage - request for comments! X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org > I don't think exception vs error code is a reliable way to divide > these cases up. Having your FS return `Block_error indicates a serious > problem that might require terminating the unikernel, whereas getting > a Division_by_zero exception from your HTTP handler is likely fairly > harmless. Whether an exception/error is serious depends more on the > importance of the thing that raised it. > > Consider the case of a filesystem that reads a corrupted disk and > throws an exception (e.g. an assert fails). This is probably the most > extreme case where you'd want to abort. Should it terminate the > unikernel? > > It depends what the disk is being used for. If it's the main hard-disk > then possibly. If it's some removable media the user has just inserted > then certainly not. > > A good principle here is that a broken component should only be able > to harm itself. If a filesystem fails to handle a corrupted disk > correctly then it may further corrupt that disk, but it should not > abort the unikernel (and thus possibly corrupt other disks in the > middle of being written). > > In this case, we can imagine a fail-safe FS functor that wraps all the > calls in the FS API so that if any one of them throws an unexpected > exception then it unplugs the underlying block device. No need to kill > everything. > I think Daniel summed this up quite well. You are quite right that in different components the correct way to deal with programmer errors differs, but the point is that you need to keep the two kinds of errors (dynamic/expected and programmer/unexpected) separate in order to deal with them appropriately. Unexpected errors mean that there is a bug in the code and in some components they should be treated extremely seriously. They should also probably be reported differently to encourage bug reports. >> - The problem with using Lwt.t as your error monad is that it becomes >> difficult to distiunguish between synchronous things that may return >> errors, asynchronous things that may return errors, and asynchornous >> things that should not return errors. It also seems tied up with the >> exception mechanism, which leads to the same problem as my previous >> point. >> >> Personally, I would probably suggest that all Mirage modules/module >> types include in their signatures: >> >> type error >> >> val pp_error : formatter -> error -> string >> >> For cases where an error can reasonably be matched on and handled >> specially, this should be exposed in the signature: >> >> type error = private [> `Foo of foo | `Bar of bar] > > Aha! I knew you'd know a trick to make this work! > > However, different functions return different sets of errors. For > example, BLOCK.read shouldn't return `Is_read_only. Can we handle > that? > When defining the error types internally you can use: type write_error = [`Read_only | `Foo ] type read_error = [`Write_only | `Bar ] type error = [read_error | write_error ] However, when writing the signatures, the thing that you would naturally like to write for this: type write_error = [> `Read_only ] type read_error = [> `Write_only ] type error = [> read_error | write_error ] doesn't work because OCaml's row polymorphism is annoyingly weak (one day I shall find time to have my way with it and fix this problem). However, all you are really gaining from: type error = [> read_error | write_error ] are free (and sometimes implicit) coercions from write_error and read_error into error. So the following signature is a reasonable substitute: type write_error = [> `Read_only ] type read_error = [> `Write_only ] type error = [> `Read_only | `Write_only ] val error_of_write_error : write_error -> error val error_of_read_error : read_error -> error you could also provide some conveniences like: pp_error : formatter -> error -> unit pp_write_error : formatter -> write_error -> unit pp_read_error : formatter -> read_error -> unit > But I think we still need an additional "exn_of_error" here because > whether something is a "dynamic" (expected) error or a bug changes as > the error is propagated. Sure, sometimes an "expected" error is not actually expected. It seems to me that: exception Error : 'a * (formatter -> 'a -> unit) -> exn should do the trick, allowing you to wrap up the error and its printer as an exception. (Note using existential variables directly in exceptions like this requires 4.02, for earlier versions you must nest a GADT within the exception). Regards, Leo _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Wed Feb 04 18:04:35 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 04 Feb 2015 18:04:35 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YJ4JU-0001OZ-Gv; Wed, 04 Feb 2015 18:04:32 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YJ4JT-0001OU-53 for mirageos-devel@lists.xenproject.org; Wed, 04 Feb 2015 18:04:31 +0000 Received: from [85.158.143.35] by server-3.bemta-4.messagelabs.com id B5/99-02754-E2F52D45; Wed, 04 Feb 2015 18:04:30 +0000 X-Env-Sender: jdy22@hermes.cam.ac.uk X-Msg-Ref: server-14.tower-21.messagelabs.com!1423073070!12568566!1 X-Originating-IP: [131.111.8.152] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTMxLjExMS44LjE1MiA9PiA4MDU1Mw==\n X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12486 invoked from network); 4 Feb 2015 18:04:30 -0000 Received: from ppsw-52.csi.cam.ac.uk (HELO ppsw-52.csi.cam.ac.uk) (131.111.8.152) by server-14.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 4 Feb 2015 18:04:30 -0000 X-Cam-AntiVirus: no malware found X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/ Received: from mail-wi0-f178.google.com ([209.85.212.178]:53723) by ppsw-52.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.159]:587) with esmtpsa (PLAIN:jdy22) (TLSv1.2:AES128-GCM-SHA256:128) id 1YJ4JR-0006vN-Fs (Exim 4.82_3-c0e5623) for mirageos-devel@lists.xenproject.org (return-path ); Wed, 04 Feb 2015 18:04:29 +0000 Received: by mail-wi0-f178.google.com with SMTP id bs8so5463157wib.5 for ; Wed, 04 Feb 2015 10:04:26 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.194.110.233 with SMTP id id9mr69614692wjb.136.1423073066710; Wed, 04 Feb 2015 10:04:26 -0800 (PST) Received: by 10.217.13.73 with HTTP; Wed, 4 Feb 2015 10:04:26 -0800 (PST) In-Reply-To: <87h9v17egn.fsf@study.localdomain> References: <20150202.014549.1883720051237442569.Christophe.Troestler@umons.ac.be> <20150204.001614.26478837567139584.Christophe.Troestler@umons.ac.be> <87oap97rvw.fsf@study.localdomain> <87h9v17egn.fsf@study.localdomain> Date: Wed, 4 Feb 2015 18:04:26 +0000 Message-ID: From: Jeremy Yallop To: Leo White Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Error handling in Mirage - request for comments! X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 4 February 2015 at 17:51, Leo White wrote: > It seems to me that: > > exception Error : 'a * (formatter -> 'a -> unit) -> exn > > should do the trick, allowing you to wrap up the error and its printer > as an exception. (Note using existential variables directly in exceptions > like this requires 4.02, for earlier versions you must nest a GADT within > the exception). There's a simpler solution than either an existential or a nested GADT here: simply eliminate the type variable altogether: exception Error of (formatter -> unit) A function of this type is just as convenient to use with Format.printf etc., since you can use '%t' instead of '%a'. _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Wed Feb 04 18:04:35 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 04 Feb 2015 18:04:35 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YJ4JU-0001OZ-Gv; Wed, 04 Feb 2015 18:04:32 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YJ4JT-0001OU-53 for mirageos-devel@lists.xenproject.org; Wed, 04 Feb 2015 18:04:31 +0000 Received: from [85.158.143.35] by server-3.bemta-4.messagelabs.com id B5/99-02754-E2F52D45; Wed, 04 Feb 2015 18:04:30 +0000 X-Env-Sender: jdy22@hermes.cam.ac.uk X-Msg-Ref: server-14.tower-21.messagelabs.com!1423073070!12568566!1 X-Originating-IP: [131.111.8.152] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTMxLjExMS44LjE1MiA9PiA4MDU1Mw==\n X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12486 invoked from network); 4 Feb 2015 18:04:30 -0000 Received: from ppsw-52.csi.cam.ac.uk (HELO ppsw-52.csi.cam.ac.uk) (131.111.8.152) by server-14.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 4 Feb 2015 18:04:30 -0000 X-Cam-AntiVirus: no malware found X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/ Received: from mail-wi0-f178.google.com ([209.85.212.178]:53723) by ppsw-52.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.159]:587) with esmtpsa (PLAIN:jdy22) (TLSv1.2:AES128-GCM-SHA256:128) id 1YJ4JR-0006vN-Fs (Exim 4.82_3-c0e5623) for mirageos-devel@lists.xenproject.org (return-path ); Wed, 04 Feb 2015 18:04:29 +0000 Received: by mail-wi0-f178.google.com with SMTP id bs8so5463157wib.5 for ; Wed, 04 Feb 2015 10:04:26 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.194.110.233 with SMTP id id9mr69614692wjb.136.1423073066710; Wed, 04 Feb 2015 10:04:26 -0800 (PST) Received: by 10.217.13.73 with HTTP; Wed, 4 Feb 2015 10:04:26 -0800 (PST) In-Reply-To: <87h9v17egn.fsf@study.localdomain> References: <20150202.014549.1883720051237442569.Christophe.Troestler@umons.ac.be> <20150204.001614.26478837567139584.Christophe.Troestler@umons.ac.be> <87oap97rvw.fsf@study.localdomain> <87h9v17egn.fsf@study.localdomain> Date: Wed, 4 Feb 2015 18:04:26 +0000 Message-ID: From: Jeremy Yallop To: Leo White Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Error handling in Mirage - request for comments! X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 4 February 2015 at 17:51, Leo White wrote: > It seems to me that: > > exception Error : 'a * (formatter -> 'a -> unit) -> exn > > should do the trick, allowing you to wrap up the error and its printer > as an exception. (Note using existential variables directly in exceptions > like this requires 4.02, for earlier versions you must nest a GADT within > the exception). There's a simpler solution than either an existential or a nested GADT here: simply eliminate the type variable altogether: exception Error of (formatter -> unit) A function of this type is just as convenient to use with Format.printf etc., since you can use '%t' instead of '%a'. _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Wed Feb 04 21:33:52 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 04 Feb 2015 21:33:52 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YJ7a1-0002BJ-JH; Wed, 04 Feb 2015 21:33:49 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YJ7a0-0002AY-HA for mirageos-devel@lists.xenproject.org; Wed, 04 Feb 2015 21:33:48 +0000 Received: from [85.158.137.68] by server-3.bemta-3.messagelabs.com id 19/E2-02997-B3092D45; Wed, 04 Feb 2015 21:33:47 +0000 X-Env-Sender: Christophe.TROESTLER@umons.ac.be X-Msg-Ref: server-14.tower-31.messagelabs.com!1423085626!9640921!1 X-Originating-IP: [157.55.234.66] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.12.5; banners=-,-,- X-VirusChecked: Checked Received: (qmail 1156 invoked from network); 4 Feb 2015 21:33:47 -0000 Received: from mail-db3on0066.outbound.protection.outlook.com (HELO emea01-db3-obe.outbound.protection.outlook.com) (157.55.234.66) by server-14.tower-31.messagelabs.com with AES256-SHA encrypted SMTP; 4 Feb 2015 21:33:47 -0000 Received: from DB3PR05CA0047.eurprd05.prod.outlook.com (25.160.41.175) by AMSPR05MB520.eurprd05.prod.outlook.com (10.242.224.23) with Microsoft SMTP Server (TLS) id 15.1.75.20; Wed, 4 Feb 2015 21:33:46 +0000 Received: from DB3FFO11FD054.protection.gbl (2a01:111:f400:7e04::161) by DB3PR05CA0047.outlook.office365.com (2a01:111:e400:9428::47) with Microsoft SMTP Server (TLS) id 15.1.75.20 via Frontend Transport; Wed, 4 Feb 2015 21:33:43 +0000 Received: from smtp.umons.ac.be (193.190.208.132) by DB3FFO11FD054.mail.protection.outlook.com (10.47.217.126) with Microsoft SMTP Server (TLS) id 15.1.87.10 via Frontend Transport; Wed, 4 Feb 2015 21:33:42 +0000 Received: from poincare (10.104.2.68) by smtp.umons.ac.be (10.104.2.84) with Microsoft SMTP Server (TLS) id 14.3.224.2; Wed, 4 Feb 2015 22:33:40 +0100 Received: from localhost ([::1]) by poincare with esmtp (Exim 4.84) (envelope-from ) id 1YJ7Zm-000633-9Z; Wed, 04 Feb 2015 22:33:34 +0100 Date: Wed, 4 Feb 2015 22:33:34 +0100 Message-ID: <20150204.223334.212749587315612608.Christophe.Troestler@umons.ac.be> To: From: Christophe Troestler In-Reply-To: <16390DA9F0BA4EED9507CA2012993CD5@erratique.ch> References: <20150204.003029.1138853194858080279.Christophe.Troestler@umons.ac.be> <16390DA9F0BA4EED9507CA2012993CD5@erratique.ch> X-Face: #2fb%mPx>rRL@4ff~TVgZ"<[:,oL"`TUEGK/[8/qb58~C>jR(x4A+v/n)7BgpEtIph_neoLKJBq0JBY9:}8v|j Organization: Universite de Mons (http://math.umons.ac.be/anum/) X-Mailer: Mew version 6.6 on Emacs 24.4 / Mule 6.0 (HANACHIRUSATO) MIME-Version: 1.0 Content-Length: 1901 X-Originating-IP: [10.104.2.68] X-EOPAttributedMessage: 0 X-Matching-Connectors: 130675592229245894; (9b551343-d075-4328-d154-08d0574c44b8,aa519c6d-c5b7-417d-4ec3-08d1170c20a9); (9b551343-d075-4328-d154-08d0574c44b8,aa519c6d-c5b7-417d-4ec3-08d1170c20a9) Received-SPF: Pass (protection.outlook.com: domain of umons.ac.be designates 193.190.208.132 as permitted sender) receiver=protection.outlook.com; client-ip=193.190.208.132; helo=smtp.umons.ac.be; X-Forefront-Antispam-Report: CIP:193.190.208.132; CTRY:BE; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(10009020)(6009001)(438002)(51704005)(24454002)(87936001)(74482002)(76506005)(62966003)(23676002)(6806004)(77156002)(76176999)(226693001)(50986999)(46102003)(50226001)(47776003)(86362001)(57986006)(92566002)(103116003)(16796002)(36756003)(106466001)(2950100001)(110136001)(2351001)(50466002); DIR:OUT; SFP:1101; SCL:1; SRVR:AMSPR05MB520; H:smtp.umons.ac.be; FPR:; SPF:Pass; MLV:sfv; LANG:en; X-Microsoft-Antispam: UriScan:; X-Microsoft-Antispam: BCL:0;PCL:0;RULEID:;SRVR:AMSPR05MB520; X-Exchange-Antispam-Report-Test: UriScan:; X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(601004); SRVR:AMSPR05MB520; X-Forefront-PRVS: 04772EA191 X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(401004)(400005); SRVR:AMSPR05MB520; X-MS-Exchange-CrossTenant-OriginalArrivalTime: 04 Feb 2015 21:33:42.6437 (UTC) X-MS-Exchange-CrossTenant-Id: 5afe0b00-7697-4969-b663-5eab37d5f47e X-MS-Exchange-CrossTenant-OriginalAttributedTenantConnectingIp: TenantId=5afe0b00-7697-4969-b663-5eab37d5f47e; Ip=[193.190.208.132] X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem X-MS-Exchange-Transport-CrossTenantHeadersStamped: AMSPR05MB520 Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Error handling in Mirage - request for comments! X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org T24gV2VkLCA0IEZlYiAyMDE1IDAwOjUzOjA3ICswMTAwLCBEYW5pZWwgQsO8bnpsaSB3cm90ZToK PiAKPiBMZSBtZXJjcmVkaSwgNCBmw6l2cmllciAyMDE1IMOgIDAwOjMwLCBDaHJpc3RvcGhlIFRy b2VzdGxlciBhIMOpY3JpdCA6Cj4gPiBb4oCmfSBPUEFNIHBhY2thZ2UgInJlc3VsdCIgZGVjbGFy aW5nIFJlc3VsdC50IHRvZ2V0aGVyIHdpdGggYSBmZXcgdXNlZnVsCj4gPiBmdW5jdGlvbnMgW+KA pl0KPiAgCj4gSSdtIG5vdCBzdXJlIHRoYXQncyB2ZXJ5IHVzZWZ1bCBzaW5jZSBvZnRlbiB5b3Ug d2lsbCB3YW50IHRvIHdvcmsKPiB3aXRoIHRoaXMgdHlwZSBvdmVyIGEgbW9uYWRpYyBjb25jdXJy ZW5jeSBsaWJyYXJ5IGFuZC9vciBwcm92aWRlCj4gY29tYmluYXRvcnMgdGhhdCBpbnRlcmFjdCB3 aXRoIGEgbG9nZ2luZyBsaWJyYXJ5IChlLmcuIHNlZSB0aGUKPiBhc3NlbWJsYWdlIGNvbWJpbmF0 b3JzIEkgbGlua2VkIHRvIGVhcmxpZXIpLgo+Cj4gSXQgc2VlbXMgdG8gbWUgdGhlcmUgd2lsbCBi ZSB2ZXJ5IGxpdHRsZSBsZWZ0IGFuZCBsb29zZSBjb3VwbGluZwo+IGJldHdlZW4gcGFja2FnZXMg c2VlbXMgZmluZSB0byBtZSBpbiB0aGF0IGNhc2UuIEkgcmF0aGVyIHRoaW5rIHRoYXQKPiBtaXJh Z2UgaXRzZWxmIHNob3VsZCBkZWZpbmUgYSBsaWJyYXJ5IHdpdGggYWxsIHRoZSBnb29kIHRvb2xz IHRvCj4gZW5mb3JjZSBpdHMgY2hvc2VuIGVycm9yIGhhbmRsaW5nIHNjaGVtZS4KCkl0IHNlZW1z IHRvIG1lIHRoYXQgbGlicmFyaWVzIHRoYXQgYXJlIG5vdCBpbnRlbmRlZCB0byBiZSBleGNsdXNp dmVseQp1c2VkIHdpdGggbWlyYWdlIGNvdWxkIHVzZSB0aGlzIHRvIHJlcG9ydCBlcnJvci12YWx1 ZXMuICBUaGUgZnVuY3Rpb25zCnByb3ZpZGVkIGJ5IHRoZSBtb2R1bGUg4oCcUmVzdWx04oCdIHdv dWxkIGJlIHRhaWxvcmVkIHRvIHRob3NlIHdobyBvbmx5CndhbnQgdG8gdXNlIGl0IGRpcmVjdGx5 LiAgQnkgcHJvdmlkaW5nIGEgY29tbW9uIHJlcHJlc2VudGF0aW9uLCBpdAp3b3VsZCBiZSBlYXN5 IHRvIHVzZSBhIGxpYnJhcnkgbWFraW5nIHVzZSBvZiBSZXN1bHQudCBpbiBNaXJhZ2Ug4oCUCndo ZXJlIHRoZXJlIHdvdWxkIGJlIGNvbWJpbmF0b3JzIChzdWNoIGFzIOKAnD4+PT/igJ0gb24g4oCc UmVzdWx0LnQgTHd0LnTigJ0pCnRoYXQgY291bGQgcHJvcGVybHkgaW50ZXJhY3Qgd2l0aCBhIGxv Z2dpbmcgZmFjaWxpdHkgaWYgZGVzaXJlZC4KCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fCk1pcmFnZU9TLWRldmVsIG1haWxpbmcgbGlzdApNaXJhZ2VPUy1k ZXZlbEBsaXN0cy54ZW5wcm9qZWN0Lm9yZwpodHRwOi8vbGlzdHMueGVucHJvamVjdC5vcmcvY2dp LWJpbi9tYWlsbWFuL2xpc3RpbmZvL21pcmFnZW9zLWRldmVsCg== From mirageos-devel-bounces@lists.xenproject.org Wed Feb 04 21:33:52 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 04 Feb 2015 21:33:52 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YJ7a1-0002BJ-JH; Wed, 04 Feb 2015 21:33:49 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YJ7a0-0002AY-HA for mirageos-devel@lists.xenproject.org; Wed, 04 Feb 2015 21:33:48 +0000 Received: from [85.158.137.68] by server-3.bemta-3.messagelabs.com id 19/E2-02997-B3092D45; Wed, 04 Feb 2015 21:33:47 +0000 X-Env-Sender: Christophe.TROESTLER@umons.ac.be X-Msg-Ref: server-14.tower-31.messagelabs.com!1423085626!9640921!1 X-Originating-IP: [157.55.234.66] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.12.5; banners=-,-,- X-VirusChecked: Checked Received: (qmail 1156 invoked from network); 4 Feb 2015 21:33:47 -0000 Received: from mail-db3on0066.outbound.protection.outlook.com (HELO emea01-db3-obe.outbound.protection.outlook.com) (157.55.234.66) by server-14.tower-31.messagelabs.com with AES256-SHA encrypted SMTP; 4 Feb 2015 21:33:47 -0000 Received: from DB3PR05CA0047.eurprd05.prod.outlook.com (25.160.41.175) by AMSPR05MB520.eurprd05.prod.outlook.com (10.242.224.23) with Microsoft SMTP Server (TLS) id 15.1.75.20; Wed, 4 Feb 2015 21:33:46 +0000 Received: from DB3FFO11FD054.protection.gbl (2a01:111:f400:7e04::161) by DB3PR05CA0047.outlook.office365.com (2a01:111:e400:9428::47) with Microsoft SMTP Server (TLS) id 15.1.75.20 via Frontend Transport; Wed, 4 Feb 2015 21:33:43 +0000 Received: from smtp.umons.ac.be (193.190.208.132) by DB3FFO11FD054.mail.protection.outlook.com (10.47.217.126) with Microsoft SMTP Server (TLS) id 15.1.87.10 via Frontend Transport; Wed, 4 Feb 2015 21:33:42 +0000 Received: from poincare (10.104.2.68) by smtp.umons.ac.be (10.104.2.84) with Microsoft SMTP Server (TLS) id 14.3.224.2; Wed, 4 Feb 2015 22:33:40 +0100 Received: from localhost ([::1]) by poincare with esmtp (Exim 4.84) (envelope-from ) id 1YJ7Zm-000633-9Z; Wed, 04 Feb 2015 22:33:34 +0100 Date: Wed, 4 Feb 2015 22:33:34 +0100 Message-ID: <20150204.223334.212749587315612608.Christophe.Troestler@umons.ac.be> To: From: Christophe Troestler In-Reply-To: <16390DA9F0BA4EED9507CA2012993CD5@erratique.ch> References: <20150204.003029.1138853194858080279.Christophe.Troestler@umons.ac.be> <16390DA9F0BA4EED9507CA2012993CD5@erratique.ch> X-Face: #2fb%mPx>rRL@4ff~TVgZ"<[:,oL"`TUEGK/[8/qb58~C>jR(x4A+v/n)7BgpEtIph_neoLKJBq0JBY9:}8v|j Organization: Universite de Mons (http://math.umons.ac.be/anum/) X-Mailer: Mew version 6.6 on Emacs 24.4 / Mule 6.0 (HANACHIRUSATO) MIME-Version: 1.0 Content-Length: 1901 X-Originating-IP: [10.104.2.68] X-EOPAttributedMessage: 0 X-Matching-Connectors: 130675592229245894; (9b551343-d075-4328-d154-08d0574c44b8,aa519c6d-c5b7-417d-4ec3-08d1170c20a9); (9b551343-d075-4328-d154-08d0574c44b8,aa519c6d-c5b7-417d-4ec3-08d1170c20a9) Received-SPF: Pass (protection.outlook.com: domain of umons.ac.be designates 193.190.208.132 as permitted sender) receiver=protection.outlook.com; client-ip=193.190.208.132; helo=smtp.umons.ac.be; X-Forefront-Antispam-Report: CIP:193.190.208.132; CTRY:BE; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(10009020)(6009001)(438002)(51704005)(24454002)(87936001)(74482002)(76506005)(62966003)(23676002)(6806004)(77156002)(76176999)(226693001)(50986999)(46102003)(50226001)(47776003)(86362001)(57986006)(92566002)(103116003)(16796002)(36756003)(106466001)(2950100001)(110136001)(2351001)(50466002); DIR:OUT; SFP:1101; SCL:1; SRVR:AMSPR05MB520; H:smtp.umons.ac.be; FPR:; SPF:Pass; MLV:sfv; LANG:en; X-Microsoft-Antispam: UriScan:; X-Microsoft-Antispam: BCL:0;PCL:0;RULEID:;SRVR:AMSPR05MB520; X-Exchange-Antispam-Report-Test: UriScan:; X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(601004); SRVR:AMSPR05MB520; X-Forefront-PRVS: 04772EA191 X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(401004)(400005); SRVR:AMSPR05MB520; X-MS-Exchange-CrossTenant-OriginalArrivalTime: 04 Feb 2015 21:33:42.6437 (UTC) X-MS-Exchange-CrossTenant-Id: 5afe0b00-7697-4969-b663-5eab37d5f47e X-MS-Exchange-CrossTenant-OriginalAttributedTenantConnectingIp: TenantId=5afe0b00-7697-4969-b663-5eab37d5f47e; Ip=[193.190.208.132] X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem X-MS-Exchange-Transport-CrossTenantHeadersStamped: AMSPR05MB520 Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Error handling in Mirage - request for comments! X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org T24gV2VkLCA0IEZlYiAyMDE1IDAwOjUzOjA3ICswMTAwLCBEYW5pZWwgQsO8bnpsaSB3cm90ZToK PiAKPiBMZSBtZXJjcmVkaSwgNCBmw6l2cmllciAyMDE1IMOgIDAwOjMwLCBDaHJpc3RvcGhlIFRy b2VzdGxlciBhIMOpY3JpdCA6Cj4gPiBb4oCmfSBPUEFNIHBhY2thZ2UgInJlc3VsdCIgZGVjbGFy aW5nIFJlc3VsdC50IHRvZ2V0aGVyIHdpdGggYSBmZXcgdXNlZnVsCj4gPiBmdW5jdGlvbnMgW+KA pl0KPiAgCj4gSSdtIG5vdCBzdXJlIHRoYXQncyB2ZXJ5IHVzZWZ1bCBzaW5jZSBvZnRlbiB5b3Ug d2lsbCB3YW50IHRvIHdvcmsKPiB3aXRoIHRoaXMgdHlwZSBvdmVyIGEgbW9uYWRpYyBjb25jdXJy ZW5jeSBsaWJyYXJ5IGFuZC9vciBwcm92aWRlCj4gY29tYmluYXRvcnMgdGhhdCBpbnRlcmFjdCB3 aXRoIGEgbG9nZ2luZyBsaWJyYXJ5IChlLmcuIHNlZSB0aGUKPiBhc3NlbWJsYWdlIGNvbWJpbmF0 b3JzIEkgbGlua2VkIHRvIGVhcmxpZXIpLgo+Cj4gSXQgc2VlbXMgdG8gbWUgdGhlcmUgd2lsbCBi ZSB2ZXJ5IGxpdHRsZSBsZWZ0IGFuZCBsb29zZSBjb3VwbGluZwo+IGJldHdlZW4gcGFja2FnZXMg c2VlbXMgZmluZSB0byBtZSBpbiB0aGF0IGNhc2UuIEkgcmF0aGVyIHRoaW5rIHRoYXQKPiBtaXJh Z2UgaXRzZWxmIHNob3VsZCBkZWZpbmUgYSBsaWJyYXJ5IHdpdGggYWxsIHRoZSBnb29kIHRvb2xz IHRvCj4gZW5mb3JjZSBpdHMgY2hvc2VuIGVycm9yIGhhbmRsaW5nIHNjaGVtZS4KCkl0IHNlZW1z IHRvIG1lIHRoYXQgbGlicmFyaWVzIHRoYXQgYXJlIG5vdCBpbnRlbmRlZCB0byBiZSBleGNsdXNp dmVseQp1c2VkIHdpdGggbWlyYWdlIGNvdWxkIHVzZSB0aGlzIHRvIHJlcG9ydCBlcnJvci12YWx1 ZXMuICBUaGUgZnVuY3Rpb25zCnByb3ZpZGVkIGJ5IHRoZSBtb2R1bGUg4oCcUmVzdWx04oCdIHdv dWxkIGJlIHRhaWxvcmVkIHRvIHRob3NlIHdobyBvbmx5CndhbnQgdG8gdXNlIGl0IGRpcmVjdGx5 LiAgQnkgcHJvdmlkaW5nIGEgY29tbW9uIHJlcHJlc2VudGF0aW9uLCBpdAp3b3VsZCBiZSBlYXN5 IHRvIHVzZSBhIGxpYnJhcnkgbWFraW5nIHVzZSBvZiBSZXN1bHQudCBpbiBNaXJhZ2Ug4oCUCndo ZXJlIHRoZXJlIHdvdWxkIGJlIGNvbWJpbmF0b3JzIChzdWNoIGFzIOKAnD4+PT/igJ0gb24g4oCc UmVzdWx0LnQgTHd0LnTigJ0pCnRoYXQgY291bGQgcHJvcGVybHkgaW50ZXJhY3Qgd2l0aCBhIGxv Z2dpbmcgZmFjaWxpdHkgaWYgZGVzaXJlZC4KCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fCk1pcmFnZU9TLWRldmVsIG1haWxpbmcgbGlzdApNaXJhZ2VPUy1k ZXZlbEBsaXN0cy54ZW5wcm9qZWN0Lm9yZwpodHRwOi8vbGlzdHMueGVucHJvamVjdC5vcmcvY2dp LWJpbi9tYWlsbWFuL2xpc3RpbmZvL21pcmFnZW9zLWRldmVsCg== From mirageos-devel-bounces@lists.xenproject.org Thu Feb 05 15:19:34 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 05 Feb 2015 15:19:34 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YJODK-00072F-OY; Thu, 05 Feb 2015 15:19:30 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YJODJ-000729-7m for mirageos-devel@lists.xenproject.org; Thu, 05 Feb 2015 15:19:29 +0000 Received: from [85.158.139.211] by server-7.bemta-5.messagelabs.com id 31/57-03736-00A83D45; Thu, 05 Feb 2015 15:19:28 +0000 X-Env-Sender: m.dobsicek@gmail.com X-Msg-Ref: server-2.tower-206.messagelabs.com!1423149567!11358207!1 X-Originating-IP: [209.85.217.182] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6172 invoked from network); 5 Feb 2015 15:19:28 -0000 Received: from mail-lb0-f182.google.com (HELO mail-lb0-f182.google.com) (209.85.217.182) by server-2.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 5 Feb 2015 15:19:28 -0000 Received: by mail-lb0-f182.google.com with SMTP id l4so8232369lbv.13 for ; Thu, 05 Feb 2015 07:19:27 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; bh=RKbt1Fwsc5wJPlFSnYnlEB1dyaYdUYXEYMJZIUOv8yM=; b=aomxv0ZAcxXd0s7DA+Hzzcqc9VVnB1Wpxm12JY+WXgpgD+rYB+6dsC3PZpROZr6cnt lFNhRBaxBn0mvpP7ERgqlSzJXuahQvlQXDuGVCr7tGtAPpFK4avCTN1POJj6wwtIt8CO psaigtpImaaNu47zG35EVtPOStBYBtoYADkqxVz2pqmNeg1xhT7YiVQJbEsUjP/6o+ck TxJcbP2UNjvRYzx6Y/4SvPuakySSDaYjIv2Xi8ubrJdTei2+8FN1pR9AzMud6BVS3d8e xiW7FIHEAox9NL4Oy3+lUtDg6C0lCURtgedAy1Gh1fdWCqOBACMCdJufX3VvBNbOhiss XF+g== X-Received: by 10.112.202.227 with SMTP id kl3mr4014948lbc.81.1423149567388; Thu, 05 Feb 2015 07:19:27 -0800 (PST) Received: from [192.168.1.6] (m176-68-3-48.cust.tele2.se. [176.68.3.48]) by mx.google.com with ESMTPSA id f5sm1021350laf.9.2015.02.05.07.19.25 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 05 Feb 2015 07:19:26 -0800 (PST) Message-ID: <54D389FC.20209@gmail.com> Date: Thu, 05 Feb 2015 16:19:24 +0100 From: Miroslav Dobsicek User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:34.0) Gecko/20100101 Thunderbird/34.0 MIME-Version: 1.0 To: mirageos-devel@lists.xenproject.org Subject: [MirageOS-devel] Mirage OS on Cubieboard - beginner question X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org Hi, I got interested in Mirage OS as it provides me with a good excuse to start playing with Ocaml and single board computers. To get started, - I am better of buying Cubieboard 3 or rather the newer Cubieboard 4 with the hope that Xen will support Allwinner A80 soon? - What is the recommended debugging environment, I guess a serial console is must. Something more to consider? Note: I have no particular preference for Cubieboards as such, they are just boards I noticed some Mirage developers are using. Thanks for advices, Miroslav _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Thu Feb 05 15:19:34 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 05 Feb 2015 15:19:34 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YJODK-00072F-OY; Thu, 05 Feb 2015 15:19:30 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YJODJ-000729-7m for mirageos-devel@lists.xenproject.org; Thu, 05 Feb 2015 15:19:29 +0000 Received: from [85.158.139.211] by server-7.bemta-5.messagelabs.com id 31/57-03736-00A83D45; Thu, 05 Feb 2015 15:19:28 +0000 X-Env-Sender: m.dobsicek@gmail.com X-Msg-Ref: server-2.tower-206.messagelabs.com!1423149567!11358207!1 X-Originating-IP: [209.85.217.182] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6172 invoked from network); 5 Feb 2015 15:19:28 -0000 Received: from mail-lb0-f182.google.com (HELO mail-lb0-f182.google.com) (209.85.217.182) by server-2.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 5 Feb 2015 15:19:28 -0000 Received: by mail-lb0-f182.google.com with SMTP id l4so8232369lbv.13 for ; Thu, 05 Feb 2015 07:19:27 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; bh=RKbt1Fwsc5wJPlFSnYnlEB1dyaYdUYXEYMJZIUOv8yM=; b=aomxv0ZAcxXd0s7DA+Hzzcqc9VVnB1Wpxm12JY+WXgpgD+rYB+6dsC3PZpROZr6cnt lFNhRBaxBn0mvpP7ERgqlSzJXuahQvlQXDuGVCr7tGtAPpFK4avCTN1POJj6wwtIt8CO psaigtpImaaNu47zG35EVtPOStBYBtoYADkqxVz2pqmNeg1xhT7YiVQJbEsUjP/6o+ck TxJcbP2UNjvRYzx6Y/4SvPuakySSDaYjIv2Xi8ubrJdTei2+8FN1pR9AzMud6BVS3d8e xiW7FIHEAox9NL4Oy3+lUtDg6C0lCURtgedAy1Gh1fdWCqOBACMCdJufX3VvBNbOhiss XF+g== X-Received: by 10.112.202.227 with SMTP id kl3mr4014948lbc.81.1423149567388; Thu, 05 Feb 2015 07:19:27 -0800 (PST) Received: from [192.168.1.6] (m176-68-3-48.cust.tele2.se. [176.68.3.48]) by mx.google.com with ESMTPSA id f5sm1021350laf.9.2015.02.05.07.19.25 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 05 Feb 2015 07:19:26 -0800 (PST) Message-ID: <54D389FC.20209@gmail.com> Date: Thu, 05 Feb 2015 16:19:24 +0100 From: Miroslav Dobsicek User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:34.0) Gecko/20100101 Thunderbird/34.0 MIME-Version: 1.0 To: mirageos-devel@lists.xenproject.org Subject: [MirageOS-devel] Mirage OS on Cubieboard - beginner question X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org Hi, I got interested in Mirage OS as it provides me with a good excuse to start playing with Ocaml and single board computers. To get started, - I am better of buying Cubieboard 3 or rather the newer Cubieboard 4 with the hope that Xen will support Allwinner A80 soon? - What is the recommended debugging environment, I guess a serial console is must. Something more to consider? Note: I have no particular preference for Cubieboards as such, they are just boards I noticed some Mirage developers are using. Thanks for advices, Miroslav _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Thu Feb 05 21:11:38 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 05 Feb 2015 21:11:38 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YJTi2-0006Mg-RG; Thu, 05 Feb 2015 21:11:34 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YJTi1-0006MC-IZ for mirageos-devel@lists.xenproject.org; Thu, 05 Feb 2015 21:11:33 +0000 Received: from [85.158.143.35] by server-3.bemta-4.messagelabs.com id 9A/6B-02754-48CD3D45; Thu, 05 Feb 2015 21:11:32 +0000 X-Env-Sender: talex5@gmail.com X-Msg-Ref: server-5.tower-21.messagelabs.com!1423170691!11994040!1 X-Originating-IP: [209.85.217.179] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11736 invoked from network); 5 Feb 2015 21:11:31 -0000 Received: from mail-lb0-f179.google.com (HELO mail-lb0-f179.google.com) (209.85.217.179) by server-5.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 5 Feb 2015 21:11:31 -0000 Received: by mail-lb0-f179.google.com with SMTP id z11so10757855lbi.10 for ; Thu, 05 Feb 2015 13:11:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=+aZp6fiKl638YwtYJROlPd6vZdDzxdjiN3uvUHpsYRY=; b=mLYJwMFDvFK52QcnohCX7+x3x8jl3oRIiHcwxiHjn5Hmsm1jeccUvshwRrvCmlG+Qe r+6uLzvFK2Mm2cnfI5mE1CKdxOwgEQc4mL9EaibZTrdZnh4O0KBdNqx0nHV3CSFs1k4G 0+++LhNcir4/Fw82qdVy+Kf11IqyRY4aJSrIQQsKrNHvSHnjL/1opt/fj9ZrQ1d2/9FD WW4DqW2vh6B2z/dPmjv4q6z2kcI2ZxqeRhqsJcjpAU7dO282z0fD4L8uhwGS2gxXTvNV T2TAdR7Nz9guIKnw4tHf2FCtXq0gBNN+XM4R8ur78W5kzikIurPs4eSm5R7Nik5yD3qt foNQ== MIME-Version: 1.0 X-Received: by 10.112.167.228 with SMTP id zr4mr120014lbb.20.1423170691168; Thu, 05 Feb 2015 13:11:31 -0800 (PST) Received: by 10.25.207.206 with HTTP; Thu, 5 Feb 2015 13:11:31 -0800 (PST) In-Reply-To: <54D389FC.20209@gmail.com> References: <54D389FC.20209@gmail.com> Date: Thu, 5 Feb 2015 21:11:31 +0000 Message-ID: From: Thomas Leonard To: Miroslav Dobsicek Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Mirage OS on Cubieboard - beginner question X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 5 February 2015 at 15:19, Miroslav Dobsicek wrote: > Hi, > > I got interested in Mirage OS as it provides me with a good excuse to start > playing with Ocaml and single board computers. > > To get started, > - I am better of buying Cubieboard 3 or rather the newer Cubieboard 4 with > the hope that Xen will support Allwinner A80 soon? I'd go with the Cubieboard 3. Otherwise, you'll have to figure out how to make it boot yourself. With the CB 3, you can use our pre-built image: https://github.com/mirage/xen-arm-builder > - What is the recommended debugging environment, I guess a serial console > is must. Something more to consider? For the CB3, it should just boot and be accessible over the network (it uses DHCP to get an address), so you might get away without the serial cable. If you get the CB4, I'm sure you'll need it though! > Note: I have no particular preference for Cubieboards as such, they are just > boards I noticed some Mirage developers are using. I think that's the easiest one to get started with. Has anyone tried the Raspberry Pi 2 yet? It's ARMv7, so it should work with Xen. -- Dr Thomas Leonard http://0install.net/ GPG: 9242 9807 C985 3C07 44A6 8B9A AE07 8280 59A5 3CC1 GPG: DA98 25AE CAD0 8975 7CDA BD8E 0713 3F96 CA74 D8BA _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Thu Feb 05 21:11:38 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 05 Feb 2015 21:11:38 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YJTi2-0006Mg-RG; Thu, 05 Feb 2015 21:11:34 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YJTi1-0006MC-IZ for mirageos-devel@lists.xenproject.org; Thu, 05 Feb 2015 21:11:33 +0000 Received: from [85.158.143.35] by server-3.bemta-4.messagelabs.com id 9A/6B-02754-48CD3D45; Thu, 05 Feb 2015 21:11:32 +0000 X-Env-Sender: talex5@gmail.com X-Msg-Ref: server-5.tower-21.messagelabs.com!1423170691!11994040!1 X-Originating-IP: [209.85.217.179] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11736 invoked from network); 5 Feb 2015 21:11:31 -0000 Received: from mail-lb0-f179.google.com (HELO mail-lb0-f179.google.com) (209.85.217.179) by server-5.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 5 Feb 2015 21:11:31 -0000 Received: by mail-lb0-f179.google.com with SMTP id z11so10757855lbi.10 for ; Thu, 05 Feb 2015 13:11:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=+aZp6fiKl638YwtYJROlPd6vZdDzxdjiN3uvUHpsYRY=; b=mLYJwMFDvFK52QcnohCX7+x3x8jl3oRIiHcwxiHjn5Hmsm1jeccUvshwRrvCmlG+Qe r+6uLzvFK2Mm2cnfI5mE1CKdxOwgEQc4mL9EaibZTrdZnh4O0KBdNqx0nHV3CSFs1k4G 0+++LhNcir4/Fw82qdVy+Kf11IqyRY4aJSrIQQsKrNHvSHnjL/1opt/fj9ZrQ1d2/9FD WW4DqW2vh6B2z/dPmjv4q6z2kcI2ZxqeRhqsJcjpAU7dO282z0fD4L8uhwGS2gxXTvNV T2TAdR7Nz9guIKnw4tHf2FCtXq0gBNN+XM4R8ur78W5kzikIurPs4eSm5R7Nik5yD3qt foNQ== MIME-Version: 1.0 X-Received: by 10.112.167.228 with SMTP id zr4mr120014lbb.20.1423170691168; Thu, 05 Feb 2015 13:11:31 -0800 (PST) Received: by 10.25.207.206 with HTTP; Thu, 5 Feb 2015 13:11:31 -0800 (PST) In-Reply-To: <54D389FC.20209@gmail.com> References: <54D389FC.20209@gmail.com> Date: Thu, 5 Feb 2015 21:11:31 +0000 Message-ID: From: Thomas Leonard To: Miroslav Dobsicek Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Mirage OS on Cubieboard - beginner question X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 5 February 2015 at 15:19, Miroslav Dobsicek wrote: > Hi, > > I got interested in Mirage OS as it provides me with a good excuse to start > playing with Ocaml and single board computers. > > To get started, > - I am better of buying Cubieboard 3 or rather the newer Cubieboard 4 with > the hope that Xen will support Allwinner A80 soon? I'd go with the Cubieboard 3. Otherwise, you'll have to figure out how to make it boot yourself. With the CB 3, you can use our pre-built image: https://github.com/mirage/xen-arm-builder > - What is the recommended debugging environment, I guess a serial console > is must. Something more to consider? For the CB3, it should just boot and be accessible over the network (it uses DHCP to get an address), so you might get away without the serial cable. If you get the CB4, I'm sure you'll need it though! > Note: I have no particular preference for Cubieboards as such, they are just > boards I noticed some Mirage developers are using. I think that's the easiest one to get started with. Has anyone tried the Raspberry Pi 2 yet? It's ARMv7, so it should work with Xen. -- Dr Thomas Leonard http://0install.net/ GPG: 9242 9807 C985 3C07 44A6 8B9A AE07 8280 59A5 3CC1 GPG: DA98 25AE CAD0 8975 7CDA BD8E 0713 3F96 CA74 D8BA _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Thu Feb 05 21:15:38 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 05 Feb 2015 21:15:38 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YJTly-0006vX-85; Thu, 05 Feb 2015 21:15:38 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YJTlx-0006vS-3o for mirageos-devel@lists.xenproject.org; Thu, 05 Feb 2015 21:15:37 +0000 Received: from [85.158.137.68] by server-13.bemta-3.messagelabs.com id CD/D7-02898-87DD3D45; Thu, 05 Feb 2015 21:15:36 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-11.tower-31.messagelabs.com!1423170935!11007558!1 X-Originating-IP: [5.153.225.51] X-SpamReason: No, hits=0.2 required=7.0 tests=RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6161 invoked from network); 5 Feb 2015 21:15:35 -0000 Received: from bark.recoil.org (HELO bark.recoil.org) (5.153.225.51) by server-11.tower-31.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 5 Feb 2015 21:15:35 -0000 Received: from [192.168.1.69] (cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net [86.30.244.239]); by bark.recoil.org (OpenSMTPD) with ESMTPSA id aa09134c; TLS version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO; Thu, 5 Feb 2015 21:15:34 +0000 (GMT) Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\)) From: Anil Madhavapeddy In-Reply-To: Date: Thu, 5 Feb 2015 21:15:34 +0000 Message-Id: <8C96FF3E-3F46-4383-B54B-D1834C600CB6@recoil.org> References: <54D389FC.20209@gmail.com> To: Thomas Leonard X-Mailer: Apple Mail (2.1993) Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Mirage OS on Cubieboard - beginner question X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 5 Feb 2015, at 21:11, Thomas Leonard wrote: > > On 5 February 2015 at 15:19, Miroslav Dobsicek wrote: >> Hi, >> >> I got interested in Mirage OS as it provides me with a good excuse to start >> playing with Ocaml and single board computers. >> >> To get started, >> - I am better of buying Cubieboard 3 or rather the newer Cubieboard 4 with >> the hope that Xen will support Allwinner A80 soon? > > I'd go with the Cubieboard 3. Otherwise, you'll have to figure out how > to make it boot yourself. With the CB 3, you can use our pre-built > image: > > https://github.com/mirage/xen-arm-builder (and precompiled SDcard images at http://blobs.openmirage.org/) > >> - What is the recommended debugging environment, I guess a serial console >> is must. Something more to consider? > > For the CB3, it should just boot and be accessible over the network > (it uses DHCP to get an address), so you might get away without the > serial cable. If you get the CB4, I'm sure you'll need it though! > >> Note: I have no particular preference for Cubieboards as such, they are just >> boards I noticed some Mirage developers are using. > > I think that's the easiest one to get started with. > > Has anyone tried the Raspberry Pi 2 yet? It's ARMv7, so it should work with Xen. Not yet. Last I heard, it didn't have a proper GIC and so would have trouble running Xen out of the box. I haven't looked at the released hardware though, and would be most interested in seeing a dmesg. -anil _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Thu Feb 05 21:15:38 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 05 Feb 2015 21:15:38 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YJTly-0006vX-85; Thu, 05 Feb 2015 21:15:38 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YJTlx-0006vS-3o for mirageos-devel@lists.xenproject.org; Thu, 05 Feb 2015 21:15:37 +0000 Received: from [85.158.137.68] by server-13.bemta-3.messagelabs.com id CD/D7-02898-87DD3D45; Thu, 05 Feb 2015 21:15:36 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-11.tower-31.messagelabs.com!1423170935!11007558!1 X-Originating-IP: [5.153.225.51] X-SpamReason: No, hits=0.2 required=7.0 tests=RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6161 invoked from network); 5 Feb 2015 21:15:35 -0000 Received: from bark.recoil.org (HELO bark.recoil.org) (5.153.225.51) by server-11.tower-31.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 5 Feb 2015 21:15:35 -0000 Received: from [192.168.1.69] (cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net [86.30.244.239]); by bark.recoil.org (OpenSMTPD) with ESMTPSA id aa09134c; TLS version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO; Thu, 5 Feb 2015 21:15:34 +0000 (GMT) Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\)) From: Anil Madhavapeddy In-Reply-To: Date: Thu, 5 Feb 2015 21:15:34 +0000 Message-Id: <8C96FF3E-3F46-4383-B54B-D1834C600CB6@recoil.org> References: <54D389FC.20209@gmail.com> To: Thomas Leonard X-Mailer: Apple Mail (2.1993) Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Mirage OS on Cubieboard - beginner question X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 5 Feb 2015, at 21:11, Thomas Leonard wrote: > > On 5 February 2015 at 15:19, Miroslav Dobsicek wrote: >> Hi, >> >> I got interested in Mirage OS as it provides me with a good excuse to start >> playing with Ocaml and single board computers. >> >> To get started, >> - I am better of buying Cubieboard 3 or rather the newer Cubieboard 4 with >> the hope that Xen will support Allwinner A80 soon? > > I'd go with the Cubieboard 3. Otherwise, you'll have to figure out how > to make it boot yourself. With the CB 3, you can use our pre-built > image: > > https://github.com/mirage/xen-arm-builder (and precompiled SDcard images at http://blobs.openmirage.org/) > >> - What is the recommended debugging environment, I guess a serial console >> is must. Something more to consider? > > For the CB3, it should just boot and be accessible over the network > (it uses DHCP to get an address), so you might get away without the > serial cable. If you get the CB4, I'm sure you'll need it though! > >> Note: I have no particular preference for Cubieboards as such, they are just >> boards I noticed some Mirage developers are using. > > I think that's the easiest one to get started with. > > Has anyone tried the Raspberry Pi 2 yet? It's ARMv7, so it should work with Xen. Not yet. Last I heard, it didn't have a proper GIC and so would have trouble running Xen out of the box. I haven't looked at the released hardware though, and would be most interested in seeing a dmesg. -anil _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Thu Feb 05 21:22:46 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 05 Feb 2015 21:22:46 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YJTsq-0007Cx-Iy; Thu, 05 Feb 2015 21:22:44 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YJTso-0007Cj-N4 for mirageos-devel@lists.xenproject.org; Thu, 05 Feb 2015 21:22:42 +0000 Received: from [193.109.254.147] by server-15.bemta-14.messagelabs.com id BF/1E-02770-22FD3D45; Thu, 05 Feb 2015 21:22:42 +0000 X-Env-Sender: m.dobsicek@gmail.com X-Msg-Ref: server-14.tower-27.messagelabs.com!1423171360!13132183!1 X-Originating-IP: [209.85.217.174] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15204 invoked from network); 5 Feb 2015 21:22:41 -0000 Received: from mail-lb0-f174.google.com (HELO mail-lb0-f174.google.com) (209.85.217.174) by server-14.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 5 Feb 2015 21:22:41 -0000 Received: by mail-lb0-f174.google.com with SMTP id f15so11818437lbj.5 for ; Thu, 05 Feb 2015 13:22:40 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=H8ApdFve/AVS+0JfEz5qb3L1iflRm1rMOurj4mD+0Ug=; b=LDeDvLl1Byro9u3IyyWjEhwKYp/baKyW1tj5av9cK/NzN0+ns9e+EOfz/BX5qv0tdQ tPOHTcmJUvYsZEBaXrZe8tupirLMpmsgPPBI3gIQhF9F0+1qLjnlIrQBf0XOqXp7rNIu Z83iv1CqoAtVgRgHhLOZISeyKqWxisnd/HQqT8FEwXHtBv3ZKv+BuDxSAdEhaZWnLCaK 9wdGTfqC/Aas+fseZMxGRM9RJInraxkGu+STjLTUetRdP2ExLZ05kwbv4g7R3IfbhO83 D49FXpW9Mtxp6akRnoKaxv0yCgpBHsOD7k64cw2xiJgg08cfoEDOrW2IDEcYqUuxcFYH PybQ== X-Received: by 10.112.255.104 with SMTP id ap8mr98659lbd.105.1423171360454; Thu, 05 Feb 2015 13:22:40 -0800 (PST) Received: from [192.168.1.6] (m176-68-3-48.cust.tele2.se. [176.68.3.48]) by mx.google.com with ESMTPSA id g5sm67148lag.11.2015.02.05.13.22.38 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 05 Feb 2015 13:22:39 -0800 (PST) Message-ID: <54D3DF1D.3060306@gmail.com> Date: Thu, 05 Feb 2015 22:22:37 +0100 From: Miroslav Dobsicek User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:34.0) Gecko/20100101 Thunderbird/34.0 MIME-Version: 1.0 To: Thomas Leonard References: <54D389FC.20209@gmail.com> In-Reply-To: Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Mirage OS on Cubieboard - beginner question X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org Thank you! I'll go with CB3 then. Miroslav On 2015-02-05 22:11, Thomas Leonard wrote: > On 5 February 2015 at 15:19, Miroslav Dobsicek wrote: >> Hi, >> >> I got interested in Mirage OS as it provides me with a good excuse to start >> playing with Ocaml and single board computers. >> >> To get started, >> - I am better of buying Cubieboard 3 or rather the newer Cubieboard 4 with >> the hope that Xen will support Allwinner A80 soon? > I'd go with the Cubieboard 3. Otherwise, you'll have to figure out how > to make it boot yourself. With the CB 3, you can use our pre-built > image: > > https://github.com/mirage/xen-arm-builder > >> - What is the recommended debugging environment, I guess a serial console >> is must. Something more to consider? > For the CB3, it should just boot and be accessible over the network > (it uses DHCP to get an address), so you might get away without the > serial cable. If you get the CB4, I'm sure you'll need it though! > >> Note: I have no particular preference for Cubieboards as such, they are just >> boards I noticed some Mirage developers are using. > I think that's the easiest one to get started with. > > Has anyone tried the Raspberry Pi 2 yet? It's ARMv7, so it should work with Xen. > > _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Thu Feb 05 21:22:46 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 05 Feb 2015 21:22:46 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YJTsq-0007Cx-Iy; Thu, 05 Feb 2015 21:22:44 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YJTso-0007Cj-N4 for mirageos-devel@lists.xenproject.org; Thu, 05 Feb 2015 21:22:42 +0000 Received: from [193.109.254.147] by server-15.bemta-14.messagelabs.com id BF/1E-02770-22FD3D45; Thu, 05 Feb 2015 21:22:42 +0000 X-Env-Sender: m.dobsicek@gmail.com X-Msg-Ref: server-14.tower-27.messagelabs.com!1423171360!13132183!1 X-Originating-IP: [209.85.217.174] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15204 invoked from network); 5 Feb 2015 21:22:41 -0000 Received: from mail-lb0-f174.google.com (HELO mail-lb0-f174.google.com) (209.85.217.174) by server-14.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 5 Feb 2015 21:22:41 -0000 Received: by mail-lb0-f174.google.com with SMTP id f15so11818437lbj.5 for ; Thu, 05 Feb 2015 13:22:40 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=H8ApdFve/AVS+0JfEz5qb3L1iflRm1rMOurj4mD+0Ug=; b=LDeDvLl1Byro9u3IyyWjEhwKYp/baKyW1tj5av9cK/NzN0+ns9e+EOfz/BX5qv0tdQ tPOHTcmJUvYsZEBaXrZe8tupirLMpmsgPPBI3gIQhF9F0+1qLjnlIrQBf0XOqXp7rNIu Z83iv1CqoAtVgRgHhLOZISeyKqWxisnd/HQqT8FEwXHtBv3ZKv+BuDxSAdEhaZWnLCaK 9wdGTfqC/Aas+fseZMxGRM9RJInraxkGu+STjLTUetRdP2ExLZ05kwbv4g7R3IfbhO83 D49FXpW9Mtxp6akRnoKaxv0yCgpBHsOD7k64cw2xiJgg08cfoEDOrW2IDEcYqUuxcFYH PybQ== X-Received: by 10.112.255.104 with SMTP id ap8mr98659lbd.105.1423171360454; Thu, 05 Feb 2015 13:22:40 -0800 (PST) Received: from [192.168.1.6] (m176-68-3-48.cust.tele2.se. [176.68.3.48]) by mx.google.com with ESMTPSA id g5sm67148lag.11.2015.02.05.13.22.38 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 05 Feb 2015 13:22:39 -0800 (PST) Message-ID: <54D3DF1D.3060306@gmail.com> Date: Thu, 05 Feb 2015 22:22:37 +0100 From: Miroslav Dobsicek User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:34.0) Gecko/20100101 Thunderbird/34.0 MIME-Version: 1.0 To: Thomas Leonard References: <54D389FC.20209@gmail.com> In-Reply-To: Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Mirage OS on Cubieboard - beginner question X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org Thank you! I'll go with CB3 then. Miroslav On 2015-02-05 22:11, Thomas Leonard wrote: > On 5 February 2015 at 15:19, Miroslav Dobsicek wrote: >> Hi, >> >> I got interested in Mirage OS as it provides me with a good excuse to start >> playing with Ocaml and single board computers. >> >> To get started, >> - I am better of buying Cubieboard 3 or rather the newer Cubieboard 4 with >> the hope that Xen will support Allwinner A80 soon? > I'd go with the Cubieboard 3. Otherwise, you'll have to figure out how > to make it boot yourself. With the CB 3, you can use our pre-built > image: > > https://github.com/mirage/xen-arm-builder > >> - What is the recommended debugging environment, I guess a serial console >> is must. Something more to consider? > For the CB3, it should just boot and be accessible over the network > (it uses DHCP to get an address), so you might get away without the > serial cable. If you get the CB4, I'm sure you'll need it though! > >> Note: I have no particular preference for Cubieboards as such, they are just >> boards I noticed some Mirage developers are using. > I think that's the easiest one to get started with. > > Has anyone tried the Raspberry Pi 2 yet? It's ARMv7, so it should work with Xen. > > _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Fri Feb 06 10:58:41 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 06 Feb 2015 10:58:41 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YJgcN-0005rF-Eq; Fri, 06 Feb 2015 10:58:35 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YJgcL-0005r3-HJ for mirageos-devel@lists.xenproject.org; Fri, 06 Feb 2015 10:58:33 +0000 Received: from [85.158.137.68] by server-16.bemta-3.messagelabs.com id 87/DE-02745-85E94D45; Fri, 06 Feb 2015 10:58:32 +0000 X-Env-Sender: yallop@gmail.com X-Msg-Ref: server-6.tower-31.messagelabs.com!1423220311!6683375!1 X-Originating-IP: [209.85.212.173] X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_20_30,HTML_MESSAGE, RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 9737 invoked from network); 6 Feb 2015 10:58:31 -0000 Received: from mail-wi0-f173.google.com (HELO mail-wi0-f173.google.com) (209.85.212.173) by server-6.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 6 Feb 2015 10:58:31 -0000 Received: by mail-wi0-f173.google.com with SMTP id r20so1509520wiv.0 for ; Fri, 06 Feb 2015 02:58:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=LECE6qawVTx79SQQCb+8ym14Dzme4ykKADqVd9EwDak=; b=r4oswv5GANWVy5z705vlez05znznoXpOJD4i6FpwuF8Y+7k74tUV1//WfaYqjT5VwH FtGs4qucIIW+YJCp5l4HId/DeqKeU3GtQh4CfY94g8A30mKqoBKnHV2qhTeaDzKcObPV S29ix9NnwXLvG/Vp/g0gS9vfVZc5egNpNtc/n6rRb9hJ2Kw7hB6wePm4YJzAaZxdqM3u +S3hRnmvZ/Fiyta0NtgxJE6mES5SKRxjaqDOvZow0Q0uB+u6nj8RIZj2h13pQjFeThQH g29Jlm64dkH6A9sl9A57KRwCAHshK1EtjOKaVHR4pH59uu9oRJA5OX/gC4unnx2pQ/yt PcQA== MIME-Version: 1.0 X-Received: by 10.180.98.228 with SMTP id el4mr1990971wib.77.1423220311323; Fri, 06 Feb 2015 02:58:31 -0800 (PST) Received: by 10.217.13.73 with HTTP; Fri, 6 Feb 2015 02:58:31 -0800 (PST) Date: Fri, 6 Feb 2015 10:58:31 +0000 Message-ID: From: Jeremy Yallop To: cam-compiler-hacking@lists.ocaml.org, "cl-ocamllabs@lists.cam.ac.uk" , "cl-ocamllabs-staff@lists.cam.ac.uk" , "mirageos-devel@lists.xenproject.org" Subject: [MirageOS-devel] Compiler hacking evening next Tuesday (10th February) X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============4530893168984382989==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============4530893168984382989== Content-Type: multipart/alternative; boundary=f46d0445199f17fc69050e694d0b --f46d0445199f17fc69050e694d0b Content-Type: text/plain; charset=UTF-8 It's time for another evening of OCaml compiler hacking! We'll be meeting next Tuesday evening (10th February) in the Computer Lab. If you're planning to come along, please add yourself to the Doodle poll: http://doodle.com/zxmeyn2ih92mke85 Schedule: 1800 - Start, set up 1830 - Talk: Generating code with polymorphic let (Oleg Kiselyov) 1900 - Pizza 1930-2200 Compiler hacking Further details are on the blog: http://ocamllabs.github.io/compiler-hacking/2015/02/05/back-in-the-lab.html All welcome: if you're local to Cambridge and interested in contributing to the OCaml compiler, please come along! --f46d0445199f17fc69050e694d0b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
It's time for another evening of OCaml compiler hackin= g!=C2=A0 We'll be meeting next Tuesday evening (10th February) in the C= omputer Lab.=C2=A0 If you're planning to come along, please add yoursel= f to the Doodle poll:

=C2=A0 =C2=A0 http://doodle.com/zxmeyn2ih92mke85

Schedule:
<= br>=C2=A0 =C2=A0 1800 - Start, set up
=C2=A0 =C2=A0 1830 - Talk: Generat= ing code with polymorphic let (Oleg Kiselyov)
=C2=A0 =C2=A0 1900 - Pizza=
=C2=A0 =C2=A0 1930-2200=C2=A0 Compiler hacking

Further details a= re on the blog:

=C2=A0 http://ocamllabs.github.io/compi= ler-hacking/2015/02/05/back-in-the-lab.html

All welcome: if you&= #39;re local to Cambridge and interested in contributing to the OCaml compi= ler, please come along!
--f46d0445199f17fc69050e694d0b-- --===============4530893168984382989== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --===============4530893168984382989==-- From mirageos-devel-bounces@lists.xenproject.org Fri Feb 06 10:58:41 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 06 Feb 2015 10:58:41 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YJgcN-0005rF-Eq; Fri, 06 Feb 2015 10:58:35 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YJgcL-0005r3-HJ for mirageos-devel@lists.xenproject.org; Fri, 06 Feb 2015 10:58:33 +0000 Received: from [85.158.137.68] by server-16.bemta-3.messagelabs.com id 87/DE-02745-85E94D45; Fri, 06 Feb 2015 10:58:32 +0000 X-Env-Sender: yallop@gmail.com X-Msg-Ref: server-6.tower-31.messagelabs.com!1423220311!6683375!1 X-Originating-IP: [209.85.212.173] X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_20_30,HTML_MESSAGE, RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 9737 invoked from network); 6 Feb 2015 10:58:31 -0000 Received: from mail-wi0-f173.google.com (HELO mail-wi0-f173.google.com) (209.85.212.173) by server-6.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 6 Feb 2015 10:58:31 -0000 Received: by mail-wi0-f173.google.com with SMTP id r20so1509520wiv.0 for ; Fri, 06 Feb 2015 02:58:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=LECE6qawVTx79SQQCb+8ym14Dzme4ykKADqVd9EwDak=; b=r4oswv5GANWVy5z705vlez05znznoXpOJD4i6FpwuF8Y+7k74tUV1//WfaYqjT5VwH FtGs4qucIIW+YJCp5l4HId/DeqKeU3GtQh4CfY94g8A30mKqoBKnHV2qhTeaDzKcObPV S29ix9NnwXLvG/Vp/g0gS9vfVZc5egNpNtc/n6rRb9hJ2Kw7hB6wePm4YJzAaZxdqM3u +S3hRnmvZ/Fiyta0NtgxJE6mES5SKRxjaqDOvZow0Q0uB+u6nj8RIZj2h13pQjFeThQH g29Jlm64dkH6A9sl9A57KRwCAHshK1EtjOKaVHR4pH59uu9oRJA5OX/gC4unnx2pQ/yt PcQA== MIME-Version: 1.0 X-Received: by 10.180.98.228 with SMTP id el4mr1990971wib.77.1423220311323; Fri, 06 Feb 2015 02:58:31 -0800 (PST) Received: by 10.217.13.73 with HTTP; Fri, 6 Feb 2015 02:58:31 -0800 (PST) Date: Fri, 6 Feb 2015 10:58:31 +0000 Message-ID: From: Jeremy Yallop To: cam-compiler-hacking@lists.ocaml.org, "cl-ocamllabs@lists.cam.ac.uk" , "cl-ocamllabs-staff@lists.cam.ac.uk" , "mirageos-devel@lists.xenproject.org" Subject: [MirageOS-devel] Compiler hacking evening next Tuesday (10th February) X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============4530893168984382989==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============4530893168984382989== Content-Type: multipart/alternative; boundary=f46d0445199f17fc69050e694d0b --f46d0445199f17fc69050e694d0b Content-Type: text/plain; charset=UTF-8 It's time for another evening of OCaml compiler hacking! We'll be meeting next Tuesday evening (10th February) in the Computer Lab. If you're planning to come along, please add yourself to the Doodle poll: http://doodle.com/zxmeyn2ih92mke85 Schedule: 1800 - Start, set up 1830 - Talk: Generating code with polymorphic let (Oleg Kiselyov) 1900 - Pizza 1930-2200 Compiler hacking Further details are on the blog: http://ocamllabs.github.io/compiler-hacking/2015/02/05/back-in-the-lab.html All welcome: if you're local to Cambridge and interested in contributing to the OCaml compiler, please come along! --f46d0445199f17fc69050e694d0b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
It's time for another evening of OCaml compiler hackin= g!=C2=A0 We'll be meeting next Tuesday evening (10th February) in the C= omputer Lab.=C2=A0 If you're planning to come along, please add yoursel= f to the Doodle poll:

=C2=A0 =C2=A0 http://doodle.com/zxmeyn2ih92mke85

Schedule:
<= br>=C2=A0 =C2=A0 1800 - Start, set up
=C2=A0 =C2=A0 1830 - Talk: Generat= ing code with polymorphic let (Oleg Kiselyov)
=C2=A0 =C2=A0 1900 - Pizza=
=C2=A0 =C2=A0 1930-2200=C2=A0 Compiler hacking

Further details a= re on the blog:

=C2=A0 http://ocamllabs.github.io/compi= ler-hacking/2015/02/05/back-in-the-lab.html

All welcome: if you&= #39;re local to Cambridge and interested in contributing to the OCaml compi= ler, please come along!
--f46d0445199f17fc69050e694d0b-- --===============4530893168984382989== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --===============4530893168984382989==-- From mirageos-devel-bounces@lists.xenproject.org Fri Feb 06 17:55:48 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 06 Feb 2015 17:55:48 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YJn84-0001T9-0g; Fri, 06 Feb 2015 17:55:44 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YJn4V-00017O-Ez; Fri, 06 Feb 2015 17:52:03 +0000 Received: from [85.158.139.211] by server-4.bemta-5.messagelabs.com id 6E/CE-03164-24FF4D45; Fri, 06 Feb 2015 17:52:02 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-8.tower-206.messagelabs.com!1423245120!11589630!1 X-Originating-IP: [209.85.212.177] X-SpamReason: No, hits=1.1 required=7.0 tests=BODY_RANDOM_LONG, HTML_40_50,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7598 invoked from network); 6 Feb 2015 17:52:00 -0000 Received: from mail-wi0-f177.google.com (HELO mail-wi0-f177.google.com) (209.85.212.177) by server-8.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 6 Feb 2015 17:52:00 -0000 Received: by mail-wi0-f177.google.com with SMTP id r20so4214048wiv.4; Fri, 06 Feb 2015 09:52:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:content-type:subject:date:message-id:cc:to:mime-version; bh=M5VS8USFB8tmWoWTw8gcgrLOhUG6Xw1PmMZXMfY37Y4=; b=M/sK5DsruHbM5YktWT/37EzYnzrnUvgG7aCBa1OfGg9aOH8dNd0TjVNt7/e6VAjM0a FHUsKIEUj2cy2YRf7bsxOP/mMQREFMCc+8A7o077sUxGjJJ2nyBcOAp/vBgOAdhf+CRO mY4WbtumVC8lSfbiUElP+bzRT53sJsJgBy1y5dLUQjIcbqB91fn3lPd/DDDahp9pyBHl l/6aJKtf3ZoHp+X5isTX3j6eea1ABBH6/HhrU1uZTnRJx9XPmfHm5a8qiSaTyO78aA6H mnWGPpjrcd+4GcJNOP74YmI/wBHu40Dkg+yzUD4d3UvA9r8KMKqX1miK9hrFN8k3d7rV IIqQ== X-Received: by 10.194.62.235 with SMTP id b11mr10222337wjs.73.1423245120177; Fri, 06 Feb 2015 09:52:00 -0800 (PST) Received: from [192.168.0.8] (97e5a0c2.skybroadband.com. [151.229.160.194]) by mx.google.com with ESMTPSA id ev7sm4231563wjb.47.2015.02.06.09.51.57 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 06 Feb 2015 09:51:58 -0800 (PST) From: Lars Kurth Date: Fri, 6 Feb 2015 17:51:26 +0000 Message-Id: <2B0C0681-8266-420A-A74B-1BCCFDCD3F23@gmail.com> To: xen-devel , xen-api@lists.xenproject.org, mirageos-devel , Win-pv-devel@lists.xenproject.org, embedded-pv-devel@lists.xenproject.org Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) X-Mailer: Apple Mail (2.2070.6) X-Mailman-Approved-At: Fri, 06 Feb 2015 17:55:43 +0000 Cc: Wei Liu , Konrad Rzeszutek Wilk , George Dunlap , Andrew Cooper , Anil Madhavapeddy , Pasi Karkkainen , Paul Durrant , Andres Lagar-Cavilla , Matt Wilson , Ian Campbell , John Morris , =?utf-8?Q?Roger_Pau_Monn=C3=A9?= Subject: [MirageOS-devel] IMPORTANT: GSoC 2015 page created - Need to confirm old projects, create/review new ones and fix projects with issues before Feb 22nd X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============8684915582972183745==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============8684915582972183745== Content-Type: multipart/alternative; boundary="Apple-Mail=_60486751-6232-4E1C-911F-5F28FC8CEF6B" --Apple-Mail=_60486751-6232-4E1C-911F-5F28FC8CEF6B Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Hi all, the deadline for Orgs to apply for GSoc 2015 is coming up. Organisations = need to apply before Feb 22nd. One of the things that is crucial that = the project list is up-to-date and that there is activity on the wiki = page. Google uses this as one of the main criteria to accept projects. =3D Verifying Projects =3D I created http://wiki.xenproject.org/wiki/GSoC_2015 = based on the 2014 list. = Everyone who has a project is CC'ed and should check whether their = projects are still valid. You can confirm by adding |Verified=3D=20 e.g. |Verified=3DFeb 6th 2015 to your project. I will go through the page and throw out projects that = are not verified before the application deadline. If you know a project = is invalid, either delete it or reply to this thread. =3D Verifying Mentors =3D It is also possible that a project mentor does not want to mentor a = project any more. If this is the case, please reply to the thread = stating the name of the project(s) that you do not want to mentor any = more. Ideally I would appreciate if you could add |Contact=3DLooking for Mentor to the project also =3D Adding New Projects =3D If you have a new project, add it under = http://wiki.xenproject.org/wiki/GSoC_2015#New_Project_Ideas = using the = following template: http://wiki.xenproject.org/wiki/Template:Project = Please set=20 |GSoC=3DYes You may want to reply to the thread also and invite others to review = your project. =3D Peer Reviews =3D Also, please help ensure that projects are peer reviewed, such that we = can move them into Reviewed section. = http://wiki.xenproject.org/wiki/GSoC_2015#Peer_Review_Conventions = = explains how.=20 It would also be good to move projects from = http://wiki.xenproject.org/wiki/GSoC_2015#List_of_projects_that_need_more_= work = to = http://wiki.xenproject.org/wiki/GSoC_2015#List_of_peer_reviewed_Projects = = . This requires that some of the issues in them are addressed. Best Regards Lars --Apple-Mail=_60486751-6232-4E1C-911F-5F28FC8CEF6B Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii Hi all,

the= deadline for Orgs to apply for GSoc 2015 is coming up. Organisations = need to apply before Feb 22nd. One of the things that is crucial that = the project list is up-to-date and that there is activity on the wiki = page. Google uses this as one of the main criteria to accept = projects.

=3D = Verifying Projects =3D
I created http://wiki.xenproject.org/wiki/GSoC_2015 based on = the 2014 list. Everyone who has a project is CC'ed and should check = whether their projects are still valid. You can confirm by = adding

|Verified=3D<current = date> 
e.g.
|Verified=3DFeb 6th 2015

to your project. I will go through the = page and throw out projects that are not verified before the application = deadline. If you know a project is invalid, either delete it or reply to = this thread.

=3D= Verifying Mentors =3D
It is also possible that a = project mentor does not want to mentor a project any more. If this is = the case, please reply to the thread stating the name of the project(s) = that you do not want to mentor any more. Ideally I would appreciate if = you could add

|Contact=3DLooking for Mentor to the project also

=3D Adding New Projects = =3D
If you have a new project, add it under http://wiki.xenproject.org/wiki/GSoC_2015#New_Project_Ideas=  using the following template: http://wiki.xenproject.org/wiki/Template:Project

Please = set 

|GSoC=3DYes

You may want to reply to the thread = also and invite others to review your project.

=3D Peer Reviews =3D

Also, please help ensure = that projects are peer reviewed, such that we can move them into = Reviewed section. http://wiki.xenproject.org/wiki/GSoC_2015#Peer_Review_Conventio= ns explains how. 

It would also be good to move projects = from http://wiki.xenproject.org/wiki/GSoC_2015#List_of_projects_that= _need_more_work to http://wiki.xenproject.org/wiki/GSoC_2015#List_of_peer_reviewed= _Projects. This requires that some of the issues in them are = addressed.

Best = Regards
Lars

= --Apple-Mail=_60486751-6232-4E1C-911F-5F28FC8CEF6B-- --===============8684915582972183745== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --===============8684915582972183745==-- From mirageos-devel-bounces@lists.xenproject.org Fri Feb 06 17:55:48 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 06 Feb 2015 17:55:48 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YJn84-0001T9-0g; Fri, 06 Feb 2015 17:55:44 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YJn4V-00017O-Ez; Fri, 06 Feb 2015 17:52:03 +0000 Received: from [85.158.139.211] by server-4.bemta-5.messagelabs.com id 6E/CE-03164-24FF4D45; Fri, 06 Feb 2015 17:52:02 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-8.tower-206.messagelabs.com!1423245120!11589630!1 X-Originating-IP: [209.85.212.177] X-SpamReason: No, hits=1.1 required=7.0 tests=BODY_RANDOM_LONG, HTML_40_50,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7598 invoked from network); 6 Feb 2015 17:52:00 -0000 Received: from mail-wi0-f177.google.com (HELO mail-wi0-f177.google.com) (209.85.212.177) by server-8.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 6 Feb 2015 17:52:00 -0000 Received: by mail-wi0-f177.google.com with SMTP id r20so4214048wiv.4; Fri, 06 Feb 2015 09:52:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:content-type:subject:date:message-id:cc:to:mime-version; bh=M5VS8USFB8tmWoWTw8gcgrLOhUG6Xw1PmMZXMfY37Y4=; b=M/sK5DsruHbM5YktWT/37EzYnzrnUvgG7aCBa1OfGg9aOH8dNd0TjVNt7/e6VAjM0a FHUsKIEUj2cy2YRf7bsxOP/mMQREFMCc+8A7o077sUxGjJJ2nyBcOAp/vBgOAdhf+CRO mY4WbtumVC8lSfbiUElP+bzRT53sJsJgBy1y5dLUQjIcbqB91fn3lPd/DDDahp9pyBHl l/6aJKtf3ZoHp+X5isTX3j6eea1ABBH6/HhrU1uZTnRJx9XPmfHm5a8qiSaTyO78aA6H mnWGPpjrcd+4GcJNOP74YmI/wBHu40Dkg+yzUD4d3UvA9r8KMKqX1miK9hrFN8k3d7rV IIqQ== X-Received: by 10.194.62.235 with SMTP id b11mr10222337wjs.73.1423245120177; Fri, 06 Feb 2015 09:52:00 -0800 (PST) Received: from [192.168.0.8] (97e5a0c2.skybroadband.com. [151.229.160.194]) by mx.google.com with ESMTPSA id ev7sm4231563wjb.47.2015.02.06.09.51.57 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 06 Feb 2015 09:51:58 -0800 (PST) From: Lars Kurth Date: Fri, 6 Feb 2015 17:51:26 +0000 Message-Id: <2B0C0681-8266-420A-A74B-1BCCFDCD3F23@gmail.com> To: xen-devel , xen-api@lists.xenproject.org, mirageos-devel , Win-pv-devel@lists.xenproject.org, embedded-pv-devel@lists.xenproject.org Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) X-Mailer: Apple Mail (2.2070.6) X-Mailman-Approved-At: Fri, 06 Feb 2015 17:55:43 +0000 Cc: Wei Liu , Konrad Rzeszutek Wilk , George Dunlap , Andrew Cooper , Anil Madhavapeddy , Pasi Karkkainen , Paul Durrant , Andres Lagar-Cavilla , Matt Wilson , Ian Campbell , John Morris , =?utf-8?Q?Roger_Pau_Monn=C3=A9?= Subject: [MirageOS-devel] IMPORTANT: GSoC 2015 page created - Need to confirm old projects, create/review new ones and fix projects with issues before Feb 22nd X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============8684915582972183745==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============8684915582972183745== Content-Type: multipart/alternative; boundary="Apple-Mail=_60486751-6232-4E1C-911F-5F28FC8CEF6B" --Apple-Mail=_60486751-6232-4E1C-911F-5F28FC8CEF6B Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Hi all, the deadline for Orgs to apply for GSoc 2015 is coming up. Organisations = need to apply before Feb 22nd. One of the things that is crucial that = the project list is up-to-date and that there is activity on the wiki = page. Google uses this as one of the main criteria to accept projects. =3D Verifying Projects =3D I created http://wiki.xenproject.org/wiki/GSoC_2015 = based on the 2014 list. = Everyone who has a project is CC'ed and should check whether their = projects are still valid. You can confirm by adding |Verified=3D=20 e.g. |Verified=3DFeb 6th 2015 to your project. I will go through the page and throw out projects that = are not verified before the application deadline. If you know a project = is invalid, either delete it or reply to this thread. =3D Verifying Mentors =3D It is also possible that a project mentor does not want to mentor a = project any more. If this is the case, please reply to the thread = stating the name of the project(s) that you do not want to mentor any = more. Ideally I would appreciate if you could add |Contact=3DLooking for Mentor to the project also =3D Adding New Projects =3D If you have a new project, add it under = http://wiki.xenproject.org/wiki/GSoC_2015#New_Project_Ideas = using the = following template: http://wiki.xenproject.org/wiki/Template:Project = Please set=20 |GSoC=3DYes You may want to reply to the thread also and invite others to review = your project. =3D Peer Reviews =3D Also, please help ensure that projects are peer reviewed, such that we = can move them into Reviewed section. = http://wiki.xenproject.org/wiki/GSoC_2015#Peer_Review_Conventions = = explains how.=20 It would also be good to move projects from = http://wiki.xenproject.org/wiki/GSoC_2015#List_of_projects_that_need_more_= work = to = http://wiki.xenproject.org/wiki/GSoC_2015#List_of_peer_reviewed_Projects = = . This requires that some of the issues in them are addressed. Best Regards Lars --Apple-Mail=_60486751-6232-4E1C-911F-5F28FC8CEF6B Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii Hi all,

the= deadline for Orgs to apply for GSoc 2015 is coming up. Organisations = need to apply before Feb 22nd. One of the things that is crucial that = the project list is up-to-date and that there is activity on the wiki = page. Google uses this as one of the main criteria to accept = projects.

=3D = Verifying Projects =3D
I created http://wiki.xenproject.org/wiki/GSoC_2015 based on = the 2014 list. Everyone who has a project is CC'ed and should check = whether their projects are still valid. You can confirm by = adding

|Verified=3D<current = date> 
e.g.
|Verified=3DFeb 6th 2015

to your project. I will go through the = page and throw out projects that are not verified before the application = deadline. If you know a project is invalid, either delete it or reply to = this thread.

=3D= Verifying Mentors =3D
It is also possible that a = project mentor does not want to mentor a project any more. If this is = the case, please reply to the thread stating the name of the project(s) = that you do not want to mentor any more. Ideally I would appreciate if = you could add

|Contact=3DLooking for Mentor to the project also

=3D Adding New Projects = =3D
If you have a new project, add it under http://wiki.xenproject.org/wiki/GSoC_2015#New_Project_Ideas=  using the following template: http://wiki.xenproject.org/wiki/Template:Project

Please = set 

|GSoC=3DYes

You may want to reply to the thread = also and invite others to review your project.

=3D Peer Reviews =3D

Also, please help ensure = that projects are peer reviewed, such that we can move them into = Reviewed section. http://wiki.xenproject.org/wiki/GSoC_2015#Peer_Review_Conventio= ns explains how. 

It would also be good to move projects = from http://wiki.xenproject.org/wiki/GSoC_2015#List_of_projects_that= _need_more_work to http://wiki.xenproject.org/wiki/GSoC_2015#List_of_peer_reviewed= _Projects. This requires that some of the issues in them are = addressed.

Best = Regards
Lars

= --Apple-Mail=_60486751-6232-4E1C-911F-5F28FC8CEF6B-- --===============8684915582972183745== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --===============8684915582972183745==-- From mirageos-devel-bounces@lists.xenproject.org Fri Feb 06 18:19:50 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 06 Feb 2015 18:19:50 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YJnVN-0003dj-Fy; Fri, 06 Feb 2015 18:19:49 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YJnVM-0003dX-DZ for mirageos-devel@lists.xenproject.org; Fri, 06 Feb 2015 18:19:48 +0000 Received: from [193.109.254.147] by server-14.bemta-14.messagelabs.com id F2/3E-02753-3C505D45; Fri, 06 Feb 2015 18:19:47 +0000 X-Env-Sender: amc79@cam.ac.uk X-Msg-Ref: server-7.tower-27.messagelabs.com!1423246786!11833319!1 X-Originating-IP: [131.111.8.152] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTMxLjExMS44LjE1MiA9PiA4MDU1Mw==\n X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 14630 invoked from network); 6 Feb 2015 18:19:46 -0000 Received: from ppsw-52.csi.cam.ac.uk (HELO ppsw-52.csi.cam.ac.uk) (131.111.8.152) by server-7.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 6 Feb 2015 18:19:46 -0000 X-Cam-AntiVirus: no malware found X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/ Received: from cpc17-cmbg14-2-0-cust360.5-4.cable.virginm.net ([86.6.155.105]:62959 helo=[192.168.0.8]) by ppsw-52.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.159]:587) with esmtpsa (PLAIN:amc79) (TLSv1:AES128-SHA:128) id 1YJnVK-0000Uu-Ds (Exim 4.82_3-c0e5623) for mirageos-devel@lists.xenproject.org (return-path ); Fri, 06 Feb 2015 18:19:46 +0000 Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) From: Amir Chaudhry In-Reply-To: <2B0C0681-8266-420A-A74B-1BCCFDCD3F23@gmail.com> Date: Fri, 6 Feb 2015 18:19:45 +0000 Message-Id: <0A2884DD-0391-4E50-A68B-71D8A8A68296@cam.ac.uk> References: <2B0C0681-8266-420A-A74B-1BCCFDCD3F23@gmail.com> To: mirageos-devel X-Mailer: Apple Mail (2.1510) Subject: [MirageOS-devel] MirageOS and GSoC (was: Re: IMPORTANT: GSoC 2015 page created - Need to confirm old projects, create/review new ones and fix projects with issues before Feb 22nd) X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: quoted-printable Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org [removed others so we can continue discussion ourselves] Last year we had three projects (see below) but since we're curating a set = of our own, I'd like to make sure we've filled that out too. Last year's list - are these still valid? =95 Create a tiny VM for easy load testing =95 Fuzz testing Xen with Mirage =95 Mirage OS web stack testing (via http://wiki.xenproject.org/wiki/GSoC_2015#Mirage_OS) If you have ideas for projects, please add them to the wiki and we can then= add them to the pool for GSoC. We have a number of projects already listed but I'm sure there are several = others we can think of. I'll bring this up during the next call. https://github.com/mirage/mirage-www/wiki/Pioneer-Projects Best wishes, Amir On 6 Feb 2015, at 17:51, Lars Kurth wrote: > Hi all, > = > the deadline for Orgs to apply for GSoc 2015 is coming up. Organisations = need to apply before Feb 22nd. One of the things that is crucial that the p= roject list is up-to-date and that there is activity on the wiki page. Goog= le uses this as one of the main criteria to accept projects. > = > =3D Verifying Projects =3D > I created http://wiki.xenproject.org/wiki/GSoC_2015 based on the 2014 lis= t. Everyone who has a project is CC'ed and should check whether their proje= cts are still valid. You can confirm by adding > = > |Verified=3D = > e.g. > |Verified=3DFeb 6th 2015 > = > to your project. I will go through the page and throw out projects that a= re not verified before the application deadline. If you know a project is i= nvalid, either delete it or reply to this thread. > = > =3D Verifying Mentors =3D > It is also possible that a project mentor does not want to mentor a proje= ct any more. If this is the case, please reply to the thread stating the na= me of the project(s) that you do not want to mentor any more. Ideally I wou= ld appreciate if you could add > = > |Contact=3DLooking for Mentor to the project also > = > =3D Adding New Projects =3D > If you have a new project, add it under http://wiki.xenproject.org/wiki/G= SoC_2015#New_Project_Ideas using the following template: http://wiki.xenpro= ject.org/wiki/Template:Project > = > Please set = > = > |GSoC=3DYes > = > You may want to reply to the thread also and invite others to review your= project. > = > =3D Peer Reviews =3D > = > Also, please help ensure that projects are peer reviewed, such that we ca= n move them into Reviewed section. http://wiki.xenproject.org/wiki/GSoC_201= 5#Peer_Review_Conventions explains how. = > = > It would also be good to move projects from http://wiki.xenproject.org/wi= ki/GSoC_2015#List_of_projects_that_need_more_work to http://wiki.xenproject= .org/wiki/GSoC_2015#List_of_peer_reviewed_Projects. This requires that some= of the issues in them are addressed. > = > Best Regards > Lars > = > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Fri Feb 06 18:19:50 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 06 Feb 2015 18:19:50 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YJnVN-0003dj-Fy; Fri, 06 Feb 2015 18:19:49 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YJnVM-0003dX-DZ for mirageos-devel@lists.xenproject.org; Fri, 06 Feb 2015 18:19:48 +0000 Received: from [193.109.254.147] by server-14.bemta-14.messagelabs.com id F2/3E-02753-3C505D45; Fri, 06 Feb 2015 18:19:47 +0000 X-Env-Sender: amc79@cam.ac.uk X-Msg-Ref: server-7.tower-27.messagelabs.com!1423246786!11833319!1 X-Originating-IP: [131.111.8.152] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTMxLjExMS44LjE1MiA9PiA4MDU1Mw==\n X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 14630 invoked from network); 6 Feb 2015 18:19:46 -0000 Received: from ppsw-52.csi.cam.ac.uk (HELO ppsw-52.csi.cam.ac.uk) (131.111.8.152) by server-7.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 6 Feb 2015 18:19:46 -0000 X-Cam-AntiVirus: no malware found X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/ Received: from cpc17-cmbg14-2-0-cust360.5-4.cable.virginm.net ([86.6.155.105]:62959 helo=[192.168.0.8]) by ppsw-52.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.159]:587) with esmtpsa (PLAIN:amc79) (TLSv1:AES128-SHA:128) id 1YJnVK-0000Uu-Ds (Exim 4.82_3-c0e5623) for mirageos-devel@lists.xenproject.org (return-path ); Fri, 06 Feb 2015 18:19:46 +0000 Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) From: Amir Chaudhry In-Reply-To: <2B0C0681-8266-420A-A74B-1BCCFDCD3F23@gmail.com> Date: Fri, 6 Feb 2015 18:19:45 +0000 Message-Id: <0A2884DD-0391-4E50-A68B-71D8A8A68296@cam.ac.uk> References: <2B0C0681-8266-420A-A74B-1BCCFDCD3F23@gmail.com> To: mirageos-devel X-Mailer: Apple Mail (2.1510) Subject: [MirageOS-devel] MirageOS and GSoC (was: Re: IMPORTANT: GSoC 2015 page created - Need to confirm old projects, create/review new ones and fix projects with issues before Feb 22nd) X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: quoted-printable Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org [removed others so we can continue discussion ourselves] Last year we had three projects (see below) but since we're curating a set = of our own, I'd like to make sure we've filled that out too. Last year's list - are these still valid? =95 Create a tiny VM for easy load testing =95 Fuzz testing Xen with Mirage =95 Mirage OS web stack testing (via http://wiki.xenproject.org/wiki/GSoC_2015#Mirage_OS) If you have ideas for projects, please add them to the wiki and we can then= add them to the pool for GSoC. We have a number of projects already listed but I'm sure there are several = others we can think of. I'll bring this up during the next call. https://github.com/mirage/mirage-www/wiki/Pioneer-Projects Best wishes, Amir On 6 Feb 2015, at 17:51, Lars Kurth wrote: > Hi all, > = > the deadline for Orgs to apply for GSoc 2015 is coming up. Organisations = need to apply before Feb 22nd. One of the things that is crucial that the p= roject list is up-to-date and that there is activity on the wiki page. Goog= le uses this as one of the main criteria to accept projects. > = > =3D Verifying Projects =3D > I created http://wiki.xenproject.org/wiki/GSoC_2015 based on the 2014 lis= t. Everyone who has a project is CC'ed and should check whether their proje= cts are still valid. You can confirm by adding > = > |Verified=3D = > e.g. > |Verified=3DFeb 6th 2015 > = > to your project. I will go through the page and throw out projects that a= re not verified before the application deadline. If you know a project is i= nvalid, either delete it or reply to this thread. > = > =3D Verifying Mentors =3D > It is also possible that a project mentor does not want to mentor a proje= ct any more. If this is the case, please reply to the thread stating the na= me of the project(s) that you do not want to mentor any more. Ideally I wou= ld appreciate if you could add > = > |Contact=3DLooking for Mentor to the project also > = > =3D Adding New Projects =3D > If you have a new project, add it under http://wiki.xenproject.org/wiki/G= SoC_2015#New_Project_Ideas using the following template: http://wiki.xenpro= ject.org/wiki/Template:Project > = > Please set = > = > |GSoC=3DYes > = > You may want to reply to the thread also and invite others to review your= project. > = > =3D Peer Reviews =3D > = > Also, please help ensure that projects are peer reviewed, such that we ca= n move them into Reviewed section. http://wiki.xenproject.org/wiki/GSoC_201= 5#Peer_Review_Conventions explains how. = > = > It would also be good to move projects from http://wiki.xenproject.org/wi= ki/GSoC_2015#List_of_projects_that_need_more_work to http://wiki.xenproject= .org/wiki/GSoC_2015#List_of_peer_reviewed_Projects. This requires that some= of the issues in them are addressed. > = > Best Regards > Lars > = > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Sun Feb 08 18:45:32 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 08 Feb 2015 18:45:32 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YKWrH-0003Ap-Ge; Sun, 08 Feb 2015 18:45:27 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YJlwE-0003CF-QE for mirageos-devel@lists.xenproject.org; Fri, 06 Feb 2015 16:39:27 +0000 Received: from [193.109.254.147] by server-5.bemta-14.messagelabs.com id 52/EB-03170-E3EE4D45; Fri, 06 Feb 2015 16:39:26 +0000 X-Env-Sender: yotambarnoy@gmail.com X-Msg-Ref: server-14.tower-27.messagelabs.com!1423240764!11855717!1 X-Originating-IP: [74.125.82.170] X-SpamReason: No, hits=0.9 required=7.0 tests=HTML_40_50,HTML_MESSAGE, RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3468 invoked from network); 6 Feb 2015 16:39:24 -0000 Received: from mail-we0-f170.google.com (HELO mail-we0-f170.google.com) (74.125.82.170) by server-14.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 6 Feb 2015 16:39:24 -0000 Received: by mail-we0-f170.google.com with SMTP id q59so5935560wes.1 for ; Fri, 06 Feb 2015 08:39:24 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=ddGzaqXg6Ww0hWo22WXixwUtFiuUvpWX14tyEjpIbrU=; b=Zpiyc4OEwy1YE4sF7Q/EQnLygmnGP1PfzK8WYR1F2+Amf+5n1N5YzvX9eU6GXOW6K0 JtRKtETQ8XiR8pQS7epLa7g4DBHleFxKmqh/KCfdgcpTTM3O8gtqDBxCPlcpqQOQ6VMP KAaWkfZN3+dft7pDl5CuHIyEPHAW9nX948PUo4umU/2JEP7B8vAGf5IIv8t0o93tT+vy A6xtirMI9pErvk1o5oNAHknjZvVm37FZUs3CF0OClmEVCVCJ9We8e7e2cgtEqoxte8Fx OQ0TASCL0eJywZBiCLkEPdYS1Ol/moyegmSvHFAu99RNmZ89iW501z8lOjDiINUWAPLM xq5A== X-Received: by 10.194.192.98 with SMTP id hf2mr9456765wjc.52.1423240764575; Fri, 06 Feb 2015 08:39:24 -0800 (PST) MIME-Version: 1.0 Received: by 10.194.17.229 with HTTP; Fri, 6 Feb 2015 08:39:04 -0800 (PST) In-Reply-To: References: From: Yotam Barnoy Date: Fri, 6 Feb 2015 11:39:04 -0500 Message-ID: To: Jeremy Yallop X-Mailman-Approved-At: Sun, 08 Feb 2015 18:45:26 +0000 Cc: "cl-ocamllabs-staff@lists.cam.ac.uk" , "mirageos-devel@lists.xenproject.org" , "cl-ocamllabs@lists.cam.ac.uk" , cam-compiler-hacking@lists.ocaml.org Subject: Re: [MirageOS-devel] [compiler-hacking] Compiler hacking evening next Tuesday (10th February) X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============4061035887571379047==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============4061035887571379047== Content-Type: multipart/alternative; boundary=047d7bae426c33d7aa050e6e1085 --047d7bae426c33d7aa050e6e1085 Content-Type: text/plain; charset=UTF-8 Hey Jeremy -- any thoughts of broadcasting this on the web? I'd love to be involved to some degree. Perhaps you could hook up a webcam on twitch.tv or youtube and have someone monitoring the chat feed or IRC? -Yotam On Fri, Feb 6, 2015 at 5:58 AM, Jeremy Yallop wrote: > It's time for another evening of OCaml compiler hacking! We'll be meeting > next Tuesday evening (10th February) in the Computer Lab. If you're > planning to come along, please add yourself to the Doodle poll: > > http://doodle.com/zxmeyn2ih92mke85 > > Schedule: > > 1800 - Start, set up > 1830 - Talk: Generating code with polymorphic let (Oleg Kiselyov) > 1900 - Pizza > 1930-2200 Compiler hacking > > Further details are on the blog: > > > http://ocamllabs.github.io/compiler-hacking/2015/02/05/back-in-the-lab.html > > All welcome: if you're local to Cambridge and interested in contributing > to the OCaml compiler, please come along! > > _______________________________________________ > Cam-compiler-hacking mailing list > Cam-compiler-hacking@lists.ocaml.org > http://lists.ocaml.org/listinfo/cam-compiler-hacking > > --047d7bae426c33d7aa050e6e1085 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hey Jeremy -- any thoughts of broadcasting this on the web= ? I'd love to be involved to some degree. Perhaps you could hook up a w= ebcam on twitch.tv or youtube and have som= eone monitoring the chat feed or IRC?

-Yotam
=

On Fri, Feb 6, 20= 15 at 5:58 AM, Jeremy Yallop <yallop@gmail.com> wrote:
It's time for another even= ing of OCaml compiler hacking!=C2=A0 We'll be meeting next Tuesday even= ing (10th February) in the Computer Lab.=C2=A0 If you're planning to co= me along, please add yourself to the Doodle poll:

=C2=A0 =C2=A0 http://doodle.= com/zxmeyn2ih92mke85

Schedule:

=C2=A0 =C2=A0 1800 - Start= , set up
=C2=A0 =C2=A0 1830 - Talk: Generating code with polymorphic let= (Oleg Kiselyov)
=C2=A0 =C2=A0 1900 - Pizza
=C2=A0 =C2=A0 1930-2200= =C2=A0 Compiler hacking

Further details are on the blog:

=C2= =A0 http://ocamllabs.github.io/compiler-hack= ing/2015/02/05/back-in-the-lab.html

All welcome: if you're l= ocal to Cambridge and interested in contributing to the OCaml compiler, ple= ase come along!

_______________________________________________
Cam-compiler-hacking mailing list
Cam-compiler-hackin= g@lists.ocaml.org
http://lists.ocaml.org/listinfo/cam-compiler-hacking


--047d7bae426c33d7aa050e6e1085-- --===============4061035887571379047== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --===============4061035887571379047==-- From mirageos-devel-bounces@lists.xenproject.org Sun Feb 08 18:45:32 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 08 Feb 2015 18:45:32 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YKWrH-0003Ap-Ge; Sun, 08 Feb 2015 18:45:27 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YJlwE-0003CF-QE for mirageos-devel@lists.xenproject.org; Fri, 06 Feb 2015 16:39:27 +0000 Received: from [193.109.254.147] by server-5.bemta-14.messagelabs.com id 52/EB-03170-E3EE4D45; Fri, 06 Feb 2015 16:39:26 +0000 X-Env-Sender: yotambarnoy@gmail.com X-Msg-Ref: server-14.tower-27.messagelabs.com!1423240764!11855717!1 X-Originating-IP: [74.125.82.170] X-SpamReason: No, hits=0.9 required=7.0 tests=HTML_40_50,HTML_MESSAGE, RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3468 invoked from network); 6 Feb 2015 16:39:24 -0000 Received: from mail-we0-f170.google.com (HELO mail-we0-f170.google.com) (74.125.82.170) by server-14.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 6 Feb 2015 16:39:24 -0000 Received: by mail-we0-f170.google.com with SMTP id q59so5935560wes.1 for ; Fri, 06 Feb 2015 08:39:24 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=ddGzaqXg6Ww0hWo22WXixwUtFiuUvpWX14tyEjpIbrU=; b=Zpiyc4OEwy1YE4sF7Q/EQnLygmnGP1PfzK8WYR1F2+Amf+5n1N5YzvX9eU6GXOW6K0 JtRKtETQ8XiR8pQS7epLa7g4DBHleFxKmqh/KCfdgcpTTM3O8gtqDBxCPlcpqQOQ6VMP KAaWkfZN3+dft7pDl5CuHIyEPHAW9nX948PUo4umU/2JEP7B8vAGf5IIv8t0o93tT+vy A6xtirMI9pErvk1o5oNAHknjZvVm37FZUs3CF0OClmEVCVCJ9We8e7e2cgtEqoxte8Fx OQ0TASCL0eJywZBiCLkEPdYS1Ol/moyegmSvHFAu99RNmZ89iW501z8lOjDiINUWAPLM xq5A== X-Received: by 10.194.192.98 with SMTP id hf2mr9456765wjc.52.1423240764575; Fri, 06 Feb 2015 08:39:24 -0800 (PST) MIME-Version: 1.0 Received: by 10.194.17.229 with HTTP; Fri, 6 Feb 2015 08:39:04 -0800 (PST) In-Reply-To: References: From: Yotam Barnoy Date: Fri, 6 Feb 2015 11:39:04 -0500 Message-ID: To: Jeremy Yallop X-Mailman-Approved-At: Sun, 08 Feb 2015 18:45:26 +0000 Cc: "cl-ocamllabs-staff@lists.cam.ac.uk" , "mirageos-devel@lists.xenproject.org" , "cl-ocamllabs@lists.cam.ac.uk" , cam-compiler-hacking@lists.ocaml.org Subject: Re: [MirageOS-devel] [compiler-hacking] Compiler hacking evening next Tuesday (10th February) X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============4061035887571379047==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============4061035887571379047== Content-Type: multipart/alternative; boundary=047d7bae426c33d7aa050e6e1085 --047d7bae426c33d7aa050e6e1085 Content-Type: text/plain; charset=UTF-8 Hey Jeremy -- any thoughts of broadcasting this on the web? I'd love to be involved to some degree. Perhaps you could hook up a webcam on twitch.tv or youtube and have someone monitoring the chat feed or IRC? -Yotam On Fri, Feb 6, 2015 at 5:58 AM, Jeremy Yallop wrote: > It's time for another evening of OCaml compiler hacking! We'll be meeting > next Tuesday evening (10th February) in the Computer Lab. If you're > planning to come along, please add yourself to the Doodle poll: > > http://doodle.com/zxmeyn2ih92mke85 > > Schedule: > > 1800 - Start, set up > 1830 - Talk: Generating code with polymorphic let (Oleg Kiselyov) > 1900 - Pizza > 1930-2200 Compiler hacking > > Further details are on the blog: > > > http://ocamllabs.github.io/compiler-hacking/2015/02/05/back-in-the-lab.html > > All welcome: if you're local to Cambridge and interested in contributing > to the OCaml compiler, please come along! > > _______________________________________________ > Cam-compiler-hacking mailing list > Cam-compiler-hacking@lists.ocaml.org > http://lists.ocaml.org/listinfo/cam-compiler-hacking > > --047d7bae426c33d7aa050e6e1085 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hey Jeremy -- any thoughts of broadcasting this on the web= ? I'd love to be involved to some degree. Perhaps you could hook up a w= ebcam on twitch.tv or youtube and have som= eone monitoring the chat feed or IRC?

-Yotam
=

On Fri, Feb 6, 20= 15 at 5:58 AM, Jeremy Yallop <yallop@gmail.com> wrote:
It's time for another even= ing of OCaml compiler hacking!=C2=A0 We'll be meeting next Tuesday even= ing (10th February) in the Computer Lab.=C2=A0 If you're planning to co= me along, please add yourself to the Doodle poll:

=C2=A0 =C2=A0 http://doodle.= com/zxmeyn2ih92mke85

Schedule:

=C2=A0 =C2=A0 1800 - Start= , set up
=C2=A0 =C2=A0 1830 - Talk: Generating code with polymorphic let= (Oleg Kiselyov)
=C2=A0 =C2=A0 1900 - Pizza
=C2=A0 =C2=A0 1930-2200= =C2=A0 Compiler hacking

Further details are on the blog:

=C2= =A0 http://ocamllabs.github.io/compiler-hack= ing/2015/02/05/back-in-the-lab.html

All welcome: if you're l= ocal to Cambridge and interested in contributing to the OCaml compiler, ple= ase come along!

_______________________________________________
Cam-compiler-hacking mailing list
Cam-compiler-hackin= g@lists.ocaml.org
http://lists.ocaml.org/listinfo/cam-compiler-hacking


--047d7bae426c33d7aa050e6e1085-- --===============4061035887571379047== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --===============4061035887571379047==-- From mirageos-devel-bounces@lists.xenproject.org Sun Feb 08 18:58:19 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 08 Feb 2015 18:58:19 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YKX3i-0003PP-2F; Sun, 08 Feb 2015 18:58:18 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YKX3h-0003PK-8C for mirageos-devel@lists.xenproject.org; Sun, 08 Feb 2015 18:58:17 +0000 Received: from [193.109.254.147] by server-12.bemta-14.messagelabs.com id B4/92-02755-8C1B7D45; Sun, 08 Feb 2015 18:58:16 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-10.tower-27.messagelabs.com!1423421895!12097601!1 X-Originating-IP: [74.125.82.47] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17270 invoked from network); 8 Feb 2015 18:58:15 -0000 Received: from mail-wg0-f47.google.com (HELO mail-wg0-f47.google.com) (74.125.82.47) by server-10.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 8 Feb 2015 18:58:15 -0000 Received: by mail-wg0-f47.google.com with SMTP id n12so22830257wgh.6 for ; Sun, 08 Feb 2015 10:58:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:from:content-type:content-transfer-encoding:subject :message-id:date:to:mime-version; bh=v/qfAD1Cd+B3rVVYO+ZFrrVHzxdKzj9iajNaB+wTER0=; b=vc0JkkJTdxo9vV9kAxQ+czT1HXzh+4OKb4gAFrZh2vwOrYNPdKE3sMNwX3iQ8KjLbo RL7YyDQboktnZOFWkoP8Dtmxa8Q/Bc+bnKGAEbKnjM8du0n+TSTQV/d1IMdcSxRdrBW1 x7hcZpFnJYFBW9Xj8bKsbm89UtG3ns/Zv7+R1vnvAyOqyuYtDpsJl/hzy91W/dhd01g0 k9ga5ME2z07gQJKcvFUzj3oNmnMJmlEbpambuuAHTxmoV/T9jluT+IyVAEd5IjzJXXsk mOmwsMHYjfBmGQ6sdpstMkUlC5v9ypmCKJjKR6g7ACXIDs0kfeyxxOh7rG0OpKphMOwd 2Eow== X-Received: by 10.180.207.83 with SMTP id lu19mr27088125wic.52.1423421895196; Sun, 08 Feb 2015 10:58:15 -0800 (PST) Received: from [192.168.0.2] (cpc25-cmbg14-2-0-cust121.5-4.cable.virginm.net. [213.106.112.122]) by mx.google.com with ESMTPSA id fm10sm11144394wib.7.2015.02.08.10.58.13 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 08 Feb 2015 10:58:14 -0800 (PST) From: Thomas Gazagnaire Message-Id: Date: Sun, 8 Feb 2015 18:58:13 +0000 To: mirageos-devel Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\)) X-Mailer: Apple Mail (2.1993) Subject: [MirageOS-devel] network stack issues X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org Hi all, this is a summary of the issues we met to make synjitsu works again. We managed to get a working snapshot to run the experiments, but there are few issues which needs fixing in the longer term. - There is still a deadlock/race in mirage-net-xen which cause packet loss when someone write on the network very early (the whole point of synjitsu). I was not really able to track down the issue precisely, but it appears in 1.3.0 (so we reverted back to 1.2 to run the experiments). This is tracked by https://github.com/mirage/mirage-net-xen/issues/20 The bug causes the initial SYNACK to not be sent at all, so the unikernel is receiving the next SYN after the timeout (after 1s). - TCP option unmarshalling sometimes goes wrong. This bug is not very bad, it just causes some packets to get dropped, and I can reproduce it quite easily on my home network but not in the lab. This is tracked by https://github.com/mirage/mirage-tcpip/issues/106 This might be caused by malformed packets living on my network, though ... - The stack should destroy connection after receiving a RST. This is tracked by https://github.com/mirage/mirage-tcpip/issues/107. This is not critical, but will cause a lot of unnecessary traffic on the network. Thomas _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Sun Feb 08 18:58:19 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 08 Feb 2015 18:58:19 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YKX3i-0003PP-2F; Sun, 08 Feb 2015 18:58:18 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YKX3h-0003PK-8C for mirageos-devel@lists.xenproject.org; Sun, 08 Feb 2015 18:58:17 +0000 Received: from [193.109.254.147] by server-12.bemta-14.messagelabs.com id B4/92-02755-8C1B7D45; Sun, 08 Feb 2015 18:58:16 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-10.tower-27.messagelabs.com!1423421895!12097601!1 X-Originating-IP: [74.125.82.47] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17270 invoked from network); 8 Feb 2015 18:58:15 -0000 Received: from mail-wg0-f47.google.com (HELO mail-wg0-f47.google.com) (74.125.82.47) by server-10.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 8 Feb 2015 18:58:15 -0000 Received: by mail-wg0-f47.google.com with SMTP id n12so22830257wgh.6 for ; Sun, 08 Feb 2015 10:58:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:from:content-type:content-transfer-encoding:subject :message-id:date:to:mime-version; bh=v/qfAD1Cd+B3rVVYO+ZFrrVHzxdKzj9iajNaB+wTER0=; b=vc0JkkJTdxo9vV9kAxQ+czT1HXzh+4OKb4gAFrZh2vwOrYNPdKE3sMNwX3iQ8KjLbo RL7YyDQboktnZOFWkoP8Dtmxa8Q/Bc+bnKGAEbKnjM8du0n+TSTQV/d1IMdcSxRdrBW1 x7hcZpFnJYFBW9Xj8bKsbm89UtG3ns/Zv7+R1vnvAyOqyuYtDpsJl/hzy91W/dhd01g0 k9ga5ME2z07gQJKcvFUzj3oNmnMJmlEbpambuuAHTxmoV/T9jluT+IyVAEd5IjzJXXsk mOmwsMHYjfBmGQ6sdpstMkUlC5v9ypmCKJjKR6g7ACXIDs0kfeyxxOh7rG0OpKphMOwd 2Eow== X-Received: by 10.180.207.83 with SMTP id lu19mr27088125wic.52.1423421895196; Sun, 08 Feb 2015 10:58:15 -0800 (PST) Received: from [192.168.0.2] (cpc25-cmbg14-2-0-cust121.5-4.cable.virginm.net. [213.106.112.122]) by mx.google.com with ESMTPSA id fm10sm11144394wib.7.2015.02.08.10.58.13 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 08 Feb 2015 10:58:14 -0800 (PST) From: Thomas Gazagnaire Message-Id: Date: Sun, 8 Feb 2015 18:58:13 +0000 To: mirageos-devel Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\)) X-Mailer: Apple Mail (2.1993) Subject: [MirageOS-devel] network stack issues X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org Hi all, this is a summary of the issues we met to make synjitsu works again. We managed to get a working snapshot to run the experiments, but there are few issues which needs fixing in the longer term. - There is still a deadlock/race in mirage-net-xen which cause packet loss when someone write on the network very early (the whole point of synjitsu). I was not really able to track down the issue precisely, but it appears in 1.3.0 (so we reverted back to 1.2 to run the experiments). This is tracked by https://github.com/mirage/mirage-net-xen/issues/20 The bug causes the initial SYNACK to not be sent at all, so the unikernel is receiving the next SYN after the timeout (after 1s). - TCP option unmarshalling sometimes goes wrong. This bug is not very bad, it just causes some packets to get dropped, and I can reproduce it quite easily on my home network but not in the lab. This is tracked by https://github.com/mirage/mirage-tcpip/issues/106 This might be caused by malformed packets living on my network, though ... - The stack should destroy connection after receiving a RST. This is tracked by https://github.com/mirage/mirage-tcpip/issues/107. This is not critical, but will cause a lot of unnecessary traffic on the network. Thomas _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Sun Feb 08 19:03:38 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 08 Feb 2015 19:03:38 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YKX8r-0004Qc-Hg; Sun, 08 Feb 2015 19:03:37 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YKX8q-0004QX-Cc for mirageos-devel@lists.xenproject.org; Sun, 08 Feb 2015 19:03:36 +0000 Received: from [85.158.137.68] by server-16.bemta-3.messagelabs.com id 8F/F1-02745-703B7D45; Sun, 08 Feb 2015 19:03:35 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-6.tower-31.messagelabs.com!1423422212!7050225!1 X-Originating-IP: [5.153.225.51] X-SpamReason: No, hits=0.5 required=7.0 tests=MAILTO_TO_SPAM_ADDR, RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 18804 invoked from network); 8 Feb 2015 19:03:33 -0000 Received: from bark.recoil.org (HELO bark.recoil.org) (5.153.225.51) by server-6.tower-31.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 8 Feb 2015 19:03:33 -0000 Received: from [192.168.1.39] (cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net [86.30.244.239]); by bark.recoil.org (OpenSMTPD) with ESMTPSA id 6997f298; TLS version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO; Sun, 8 Feb 2015 19:03:32 +0000 (GMT) Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) From: Anil Madhavapeddy In-Reply-To: <0A2884DD-0391-4E50-A68B-71D8A8A68296@cam.ac.uk> Date: Sun, 8 Feb 2015 19:03:31 +0000 Message-Id: References: <2B0C0681-8266-420A-A74B-1BCCFDCD3F23@gmail.com> <0A2884DD-0391-4E50-A68B-71D8A8A68296@cam.ac.uk> To: Amir M Chaudhry X-Mailer: Apple Mail (2.2070.6) Cc: mirageos-devel Subject: Re: [MirageOS-devel] MirageOS and GSoC (was: Re: IMPORTANT: GSoC 2015 page created - Need to confirm old projects, create/review new ones and fix projects with issues before Feb 22nd) X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: quoted-printable Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 6 Feb 2015, at 18:19, Amir Chaudhry wrote: > = > [removed others so we can continue discussion ourselves] > = > Last year we had three projects (see below) but since we're curating a se= t of our own, I'd like to make sure we've filled that out too. > = > Last year's list - are these still valid? > =95 Create a tiny VM for easy load testing > =95 Fuzz testing Xen with Mirage > =95 Mirage OS web stack testing > (via http://wiki.xenproject.org/wiki/GSoC_2015#Mirage_OS) These are all still valid. > If you have ideas for projects, please add them to the wiki and we can th= en add them to the pool for GSoC. > We have a number of projects already listed but I'm sure there are severa= l others we can think of. I'll bring this up during the next call. > https://github.com/mirage/mirage-www/wiki/Pioneer-Projects How about we just link the Pioneer Projects page to the Xen Project wiki? = It'll be useful not to duplicate these things. Anil _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Sun Feb 08 19:03:38 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 08 Feb 2015 19:03:38 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YKX8r-0004Qc-Hg; Sun, 08 Feb 2015 19:03:37 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YKX8q-0004QX-Cc for mirageos-devel@lists.xenproject.org; Sun, 08 Feb 2015 19:03:36 +0000 Received: from [85.158.137.68] by server-16.bemta-3.messagelabs.com id 8F/F1-02745-703B7D45; Sun, 08 Feb 2015 19:03:35 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-6.tower-31.messagelabs.com!1423422212!7050225!1 X-Originating-IP: [5.153.225.51] X-SpamReason: No, hits=0.5 required=7.0 tests=MAILTO_TO_SPAM_ADDR, RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 18804 invoked from network); 8 Feb 2015 19:03:33 -0000 Received: from bark.recoil.org (HELO bark.recoil.org) (5.153.225.51) by server-6.tower-31.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 8 Feb 2015 19:03:33 -0000 Received: from [192.168.1.39] (cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net [86.30.244.239]); by bark.recoil.org (OpenSMTPD) with ESMTPSA id 6997f298; TLS version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO; Sun, 8 Feb 2015 19:03:32 +0000 (GMT) Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) From: Anil Madhavapeddy In-Reply-To: <0A2884DD-0391-4E50-A68B-71D8A8A68296@cam.ac.uk> Date: Sun, 8 Feb 2015 19:03:31 +0000 Message-Id: References: <2B0C0681-8266-420A-A74B-1BCCFDCD3F23@gmail.com> <0A2884DD-0391-4E50-A68B-71D8A8A68296@cam.ac.uk> To: Amir M Chaudhry X-Mailer: Apple Mail (2.2070.6) Cc: mirageos-devel Subject: Re: [MirageOS-devel] MirageOS and GSoC (was: Re: IMPORTANT: GSoC 2015 page created - Need to confirm old projects, create/review new ones and fix projects with issues before Feb 22nd) X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: quoted-printable Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 6 Feb 2015, at 18:19, Amir Chaudhry wrote: > = > [removed others so we can continue discussion ourselves] > = > Last year we had three projects (see below) but since we're curating a se= t of our own, I'd like to make sure we've filled that out too. > = > Last year's list - are these still valid? > =95 Create a tiny VM for easy load testing > =95 Fuzz testing Xen with Mirage > =95 Mirage OS web stack testing > (via http://wiki.xenproject.org/wiki/GSoC_2015#Mirage_OS) These are all still valid. > If you have ideas for projects, please add them to the wiki and we can th= en add them to the pool for GSoC. > We have a number of projects already listed but I'm sure there are severa= l others we can think of. I'll bring this up during the next call. > https://github.com/mirage/mirage-www/wiki/Pioneer-Projects How about we just link the Pioneer Projects page to the Xen Project wiki? = It'll be useful not to duplicate these things. Anil _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Sun Feb 08 19:49:46 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 08 Feb 2015 19:49:46 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YKXrP-0006Xw-TB; Sun, 08 Feb 2015 19:49:39 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YKXrO-0006Xr-Fm for mirageos-devel@lists.xenproject.org; Sun, 08 Feb 2015 19:49:38 +0000 Received: from [85.158.137.68] by server-14.bemta-3.messagelabs.com id 26/E7-02885-1DDB7D45; Sun, 08 Feb 2015 19:49:37 +0000 X-Env-Sender: amc79@cam.ac.uk X-Msg-Ref: server-4.tower-31.messagelabs.com!1423424976!11427251!1 X-Originating-IP: [131.111.8.152] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTMxLjExMS44LjE1MiA9PiA4MDU1Mw==\n X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12618 invoked from network); 8 Feb 2015 19:49:36 -0000 Received: from ppsw-52.csi.cam.ac.uk (HELO ppsw-52.csi.cam.ac.uk) (131.111.8.152) by server-4.tower-31.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 8 Feb 2015 19:49:36 -0000 X-Cam-AntiVirus: no malware found X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/ Received: from m.cb1.com ([217.155.139.150]:35952 helo=[192.168.1.228]) by ppsw-52.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.159]:587) with esmtpsa (PLAIN:amc79) (TLSv1:DHE-RSA-AES256-SHA:256) id 1YKXrM-0004ET-D7 (Exim 4.82_3-c0e5623) (return-path ); Sun, 08 Feb 2015 19:49:36 +0000 References: <2B0C0681-8266-420A-A74B-1BCCFDCD3F23@gmail.com> <0A2884DD-0391-4E50-A68B-71D8A8A68296@cam.ac.uk> Mime-Version: 1.0 (1.0) In-Reply-To: Message-Id: X-Mailer: iPhone Mail (12B440) From: Amir Chaudhry Date: Sun, 8 Feb 2015 19:49:35 +0000 To: Anil Madhavapeddy Cc: mirageos-devel Subject: Re: [MirageOS-devel] MirageOS and GSoC (was: Re: IMPORTANT: GSoC 2015 page created - Need to confirm old projects, create/review new ones and fix projects with issues before Feb 22nd) X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org > On 8 Feb 2015, at 19:03, Anil Madhavapeddy wrote: > >> On 6 Feb 2015, at 18:19, Amir Chaudhry wrote: >> >> https://github.com/mirage/mirage-www/wiki/Pioneer-Projects > > How about we just link the Pioneer Projects page to the Xen Project wiki? It'll be useful not to duplicate these things. I'll add a link back regardless but not sure how it would fare with the GSoC assessors/students if we *only* had a link-back. None of the other Xen Projects are listed this way so for the time-being I'll just assume this is how GSoC likes it. In any case, it's a one-time cost for me to copy over the projects before the deadline so we're represented on the actual page. AC _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Sun Feb 08 19:49:46 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 08 Feb 2015 19:49:46 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YKXrP-0006Xw-TB; Sun, 08 Feb 2015 19:49:39 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YKXrO-0006Xr-Fm for mirageos-devel@lists.xenproject.org; Sun, 08 Feb 2015 19:49:38 +0000 Received: from [85.158.137.68] by server-14.bemta-3.messagelabs.com id 26/E7-02885-1DDB7D45; Sun, 08 Feb 2015 19:49:37 +0000 X-Env-Sender: amc79@cam.ac.uk X-Msg-Ref: server-4.tower-31.messagelabs.com!1423424976!11427251!1 X-Originating-IP: [131.111.8.152] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTMxLjExMS44LjE1MiA9PiA4MDU1Mw==\n X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12618 invoked from network); 8 Feb 2015 19:49:36 -0000 Received: from ppsw-52.csi.cam.ac.uk (HELO ppsw-52.csi.cam.ac.uk) (131.111.8.152) by server-4.tower-31.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 8 Feb 2015 19:49:36 -0000 X-Cam-AntiVirus: no malware found X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/ Received: from m.cb1.com ([217.155.139.150]:35952 helo=[192.168.1.228]) by ppsw-52.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.159]:587) with esmtpsa (PLAIN:amc79) (TLSv1:DHE-RSA-AES256-SHA:256) id 1YKXrM-0004ET-D7 (Exim 4.82_3-c0e5623) (return-path ); Sun, 08 Feb 2015 19:49:36 +0000 References: <2B0C0681-8266-420A-A74B-1BCCFDCD3F23@gmail.com> <0A2884DD-0391-4E50-A68B-71D8A8A68296@cam.ac.uk> Mime-Version: 1.0 (1.0) In-Reply-To: Message-Id: X-Mailer: iPhone Mail (12B440) From: Amir Chaudhry Date: Sun, 8 Feb 2015 19:49:35 +0000 To: Anil Madhavapeddy Cc: mirageos-devel Subject: Re: [MirageOS-devel] MirageOS and GSoC (was: Re: IMPORTANT: GSoC 2015 page created - Need to confirm old projects, create/review new ones and fix projects with issues before Feb 22nd) X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org > On 8 Feb 2015, at 19:03, Anil Madhavapeddy wrote: > >> On 6 Feb 2015, at 18:19, Amir Chaudhry wrote: >> >> https://github.com/mirage/mirage-www/wiki/Pioneer-Projects > > How about we just link the Pioneer Projects page to the Xen Project wiki? It'll be useful not to duplicate these things. I'll add a link back regardless but not sure how it would fare with the GSoC assessors/students if we *only* had a link-back. None of the other Xen Projects are listed this way so for the time-being I'll just assume this is how GSoC likes it. In any case, it's a one-time cost for me to copy over the projects before the deadline so we're represented on the actual page. AC _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Mon Feb 09 11:52:22 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 09 Feb 2015 11:52:22 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YKmsy-0004dy-Uf; Mon, 09 Feb 2015 11:52:16 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YKmsx-0004dt-M2 for mirageos-devel@lists.xenproject.org; Mon, 09 Feb 2015 11:52:15 +0000 Received: from [85.158.137.68] by server-2.bemta-3.messagelabs.com id BD/C9-02991-E6F98D45; Mon, 09 Feb 2015 11:52:14 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-15.tower-31.messagelabs.com!1423482733!11507233!1 X-Originating-IP: [74.125.82.44] X-SpamReason: No, hits=0.3 required=7.0 tests=MAILTO_TO_SPAM_ADDR X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10784 invoked from network); 9 Feb 2015 11:52:14 -0000 Received: from mail-wg0-f44.google.com (HELO mail-wg0-f44.google.com) (74.125.82.44) by server-15.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 9 Feb 2015 11:52:14 -0000 Received: by mail-wg0-f44.google.com with SMTP id z12so26198558wgg.3 for ; Mon, 09 Feb 2015 03:52:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=Rt0Fr9aOKmOnw17XiltnrYmr8siqEIny6RUVNhaizPc=; b=Td2E9//a8KI6I3aydIDBqnwf1VwiE2rspxcNaZSfpq5soeZhjFhE9aWXqP8TZxJyVE i5C8kuE3IA5MbtgMLq3RgqIHDWhJl2i0hJIe7U3Nxz9NEzlsm57rIiJJISxjFNasgsdB rjvgJlsetd1m14yXRGvSJDnw071gvruBo+v+PpluNbASjnXXiULKxESjymTZ6c7e6n0O S3ifHctUnm6SvRJ5I9wJ4oQo7wBDMHmWHRF4aYhssOUactI+Ixfs/BTPkDreOhy00LkU zR8urbRbFpOlN4JJAupJ0dGHzhcVFhL2vmzB85Uahk+Q4GhQs+O6V5m5qhBYzwLXeEHn FfVg== X-Received: by 10.180.80.67 with SMTP id p3mr27056351wix.55.1423482732571; Mon, 09 Feb 2015 03:52:12 -0800 (PST) Received: from [192.168.0.8] (97e5a0c2.skybroadband.com. [151.229.160.194]) by mx.google.com with ESMTPSA id x6sm16026591wjf.24.2015.02.09.03.52.11 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 09 Feb 2015 03:52:11 -0800 (PST) Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) From: Lars Kurth In-Reply-To: Date: Mon, 9 Feb 2015 11:52:09 +0000 Message-Id: <707E3CE1-4C4D-4F3F-9BB1-F5D31D8668EB@gmail.com> References: <2B0C0681-8266-420A-A74B-1BCCFDCD3F23@gmail.com> <0A2884DD-0391-4E50-A68B-71D8A8A68296@cam.ac.uk> To: Anil Madhavapeddy X-Mailer: Apple Mail (2.2070.6) Cc: mirageos-devel Subject: Re: [MirageOS-devel] MirageOS and GSoC (was: Re: IMPORTANT: GSoC 2015 page created - Need to confirm old projects, create/review new ones and fix projects with issues before Feb 22nd) X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: quoted-printable Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org > On 8 Feb 2015, at 19:03, Anil Madhavapeddy wrote: > = > On 6 Feb 2015, at 18:19, Amir Chaudhry wrote: >> = >> [removed others so we can continue discussion ourselves] >> = >> Last year we had three projects (see below) but since we're curating a s= et of our own, I'd like to make sure we've filled that out too. >> = >> Last year's list - are these still valid? >> =95 Create a tiny VM for easy load testing >> =95 Fuzz testing Xen with Mirage >> =95 Mirage OS web stack testing >> (via http://wiki.xenproject.org/wiki/GSoC_2015#Mirage_OS) > = > These are all still valid. I marked these as verified, linking to this thread > = >> If you have ideas for projects, please add them to the wiki and we can t= hen add them to the pool for GSoC. >> We have a number of projects already listed but I'm sure there are sever= al others we can think of. I'll bring this up during the next call. >> https://github.com/mirage/mirage-www/wiki/Pioneer-Projects > = > How about we just link the Pioneer Projects page to the Xen Project wiki?= It'll be useful not to duplicate these things. That works for me, with maybe with a list of the projects and a set of inst= ructions on how to apply for them as part of GSoC. I would suggest to add s= omething like =3D=3D=3D=3D Additional Pioneer Projects =3D=3D=3D=3D {{project |Project=3DAdditional Pioneer Projects |Date=3D01/30/2015 |Verified=3DFeb 8th, 2015 (see this [http://lists.xenproject.org/archives/h= tml/mirageos-devel/2015-02/msg00046.html conversation]) |Contact=3DSend a mail to mirageos-devel@lists.xenproject.org if you're int= erested in starting on one or several of these projects. = |Difficulty=3DVarious levels of difficulty |Skills=3DOCaml |Desc=3DThis is a list of pioneer projects for Mirage OS, covering area suc= h as '''Build Tools''', '''New Libraries''', '''Storage Technologies''', ''= 'Networking Technologies''', '''Interfaces to Non-Ocaml (aka foreign) Langu= ages''' and other topics. Note that some of these projects may be too small= or too big for a single GSoC project. If you are interested in one of thes= e, make sure you discuss first on mirageos-devel@lists.xenproject.org - we = can then merge or split these as needed for GSoC. References: * [https://github.com/mirage/mirage-www/wiki/Pioneer-Projects Complete list= of Pioneer Projects] = |GSoC=3Dyes, but do check mirageos-devel@lists.xenproject.org first }} Regards Lars _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Mon Feb 09 11:52:22 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 09 Feb 2015 11:52:22 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YKmsy-0004dy-Uf; Mon, 09 Feb 2015 11:52:16 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YKmsx-0004dt-M2 for mirageos-devel@lists.xenproject.org; Mon, 09 Feb 2015 11:52:15 +0000 Received: from [85.158.137.68] by server-2.bemta-3.messagelabs.com id BD/C9-02991-E6F98D45; Mon, 09 Feb 2015 11:52:14 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-15.tower-31.messagelabs.com!1423482733!11507233!1 X-Originating-IP: [74.125.82.44] X-SpamReason: No, hits=0.3 required=7.0 tests=MAILTO_TO_SPAM_ADDR X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10784 invoked from network); 9 Feb 2015 11:52:14 -0000 Received: from mail-wg0-f44.google.com (HELO mail-wg0-f44.google.com) (74.125.82.44) by server-15.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 9 Feb 2015 11:52:14 -0000 Received: by mail-wg0-f44.google.com with SMTP id z12so26198558wgg.3 for ; Mon, 09 Feb 2015 03:52:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=Rt0Fr9aOKmOnw17XiltnrYmr8siqEIny6RUVNhaizPc=; b=Td2E9//a8KI6I3aydIDBqnwf1VwiE2rspxcNaZSfpq5soeZhjFhE9aWXqP8TZxJyVE i5C8kuE3IA5MbtgMLq3RgqIHDWhJl2i0hJIe7U3Nxz9NEzlsm57rIiJJISxjFNasgsdB rjvgJlsetd1m14yXRGvSJDnw071gvruBo+v+PpluNbASjnXXiULKxESjymTZ6c7e6n0O S3ifHctUnm6SvRJ5I9wJ4oQo7wBDMHmWHRF4aYhssOUactI+Ixfs/BTPkDreOhy00LkU zR8urbRbFpOlN4JJAupJ0dGHzhcVFhL2vmzB85Uahk+Q4GhQs+O6V5m5qhBYzwLXeEHn FfVg== X-Received: by 10.180.80.67 with SMTP id p3mr27056351wix.55.1423482732571; Mon, 09 Feb 2015 03:52:12 -0800 (PST) Received: from [192.168.0.8] (97e5a0c2.skybroadband.com. [151.229.160.194]) by mx.google.com with ESMTPSA id x6sm16026591wjf.24.2015.02.09.03.52.11 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 09 Feb 2015 03:52:11 -0800 (PST) Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) From: Lars Kurth In-Reply-To: Date: Mon, 9 Feb 2015 11:52:09 +0000 Message-Id: <707E3CE1-4C4D-4F3F-9BB1-F5D31D8668EB@gmail.com> References: <2B0C0681-8266-420A-A74B-1BCCFDCD3F23@gmail.com> <0A2884DD-0391-4E50-A68B-71D8A8A68296@cam.ac.uk> To: Anil Madhavapeddy X-Mailer: Apple Mail (2.2070.6) Cc: mirageos-devel Subject: Re: [MirageOS-devel] MirageOS and GSoC (was: Re: IMPORTANT: GSoC 2015 page created - Need to confirm old projects, create/review new ones and fix projects with issues before Feb 22nd) X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: quoted-printable Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org > On 8 Feb 2015, at 19:03, Anil Madhavapeddy wrote: > = > On 6 Feb 2015, at 18:19, Amir Chaudhry wrote: >> = >> [removed others so we can continue discussion ourselves] >> = >> Last year we had three projects (see below) but since we're curating a s= et of our own, I'd like to make sure we've filled that out too. >> = >> Last year's list - are these still valid? >> =95 Create a tiny VM for easy load testing >> =95 Fuzz testing Xen with Mirage >> =95 Mirage OS web stack testing >> (via http://wiki.xenproject.org/wiki/GSoC_2015#Mirage_OS) > = > These are all still valid. I marked these as verified, linking to this thread > = >> If you have ideas for projects, please add them to the wiki and we can t= hen add them to the pool for GSoC. >> We have a number of projects already listed but I'm sure there are sever= al others we can think of. I'll bring this up during the next call. >> https://github.com/mirage/mirage-www/wiki/Pioneer-Projects > = > How about we just link the Pioneer Projects page to the Xen Project wiki?= It'll be useful not to duplicate these things. That works for me, with maybe with a list of the projects and a set of inst= ructions on how to apply for them as part of GSoC. I would suggest to add s= omething like =3D=3D=3D=3D Additional Pioneer Projects =3D=3D=3D=3D {{project |Project=3DAdditional Pioneer Projects |Date=3D01/30/2015 |Verified=3DFeb 8th, 2015 (see this [http://lists.xenproject.org/archives/h= tml/mirageos-devel/2015-02/msg00046.html conversation]) |Contact=3DSend a mail to mirageos-devel@lists.xenproject.org if you're int= erested in starting on one or several of these projects. = |Difficulty=3DVarious levels of difficulty |Skills=3DOCaml |Desc=3DThis is a list of pioneer projects for Mirage OS, covering area suc= h as '''Build Tools''', '''New Libraries''', '''Storage Technologies''', ''= 'Networking Technologies''', '''Interfaces to Non-Ocaml (aka foreign) Langu= ages''' and other topics. Note that some of these projects may be too small= or too big for a single GSoC project. If you are interested in one of thes= e, make sure you discuss first on mirageos-devel@lists.xenproject.org - we = can then merge or split these as needed for GSoC. References: * [https://github.com/mirage/mirage-www/wiki/Pioneer-Projects Complete list= of Pioneer Projects] = |GSoC=3Dyes, but do check mirageos-devel@lists.xenproject.org first }} Regards Lars _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Mon Feb 09 12:03:14 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 09 Feb 2015 12:03:14 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YKn3a-0006r5-4C; Mon, 09 Feb 2015 12:03:14 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YKn3Y-0006oM-TR for mirageos-devel@lists.xenproject.org; Mon, 09 Feb 2015 12:03:13 +0000 Received: from [85.158.139.211] by server-14.bemta-5.messagelabs.com id EC/6C-02809-002A8D45; Mon, 09 Feb 2015 12:03:12 +0000 X-Env-Sender: talex5@gmail.com X-Msg-Ref: server-11.tower-206.messagelabs.com!1423483390!6732147!1 X-Originating-IP: [209.85.217.181] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27792 invoked from network); 9 Feb 2015 12:03:11 -0000 Received: from mail-lb0-f181.google.com (HELO mail-lb0-f181.google.com) (209.85.217.181) by server-11.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 9 Feb 2015 12:03:11 -0000 Received: by mail-lb0-f181.google.com with SMTP id b6so6661031lbj.12 for ; Mon, 09 Feb 2015 04:03:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=+PeJX36Z3UFPbOOY+gXRzb5ntFizZbj9D8r+GsT8GO8=; b=u2XuU/YXz9QPx+Y7fIEAI2/MMrNP29BPvWnl24ao98Eq2iCiHFJgJgWwMEVhK5tg8V NcJpaeC2Aj1/VqauYpszQwDmwVymyRIKtDZaf2eRZZ8HwifSxAzwOjsYhxg81auJzQcz J5YyODpYqOKjmGM5SKnWzk5uak+Pz94+PGiWP2UB1CDEVyg68wgEM0lQv9h/S7d2PIZ+ A7A8m+WK9H9Ney3Q0vdSuPOBvuzZN31ajWrvy4/DZp6Ze2y1xrgTqQW0OB+ioiGNpOE1 eojlXlC8egZguWuz6zq7XucNeyL0nX4sOm0Whc/d7IIQJ6z4NPBzYENFNaNbXLRM3cAB I5oQ== MIME-Version: 1.0 X-Received: by 10.152.170.170 with SMTP id an10mr16308906lac.121.1423483389598; Mon, 09 Feb 2015 04:03:09 -0800 (PST) Received: by 10.25.207.206 with HTTP; Mon, 9 Feb 2015 04:03:09 -0800 (PST) Date: Mon, 9 Feb 2015 12:03:09 +0000 Message-ID: From: Thomas Leonard To: "mirageos-devel@lists.xenproject.org" Subject: [MirageOS-devel] Irmin API newbie questions X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org I'm trying to understand the Irmin API. The current documentation is good, but I'm still having trouble with some of the concepts. I'm looking at these sources: https://mirage.github.io/irmin/ https://github.com/mirage/irmin/wiki/Using-the-Irmin-API (BTW, I think it might be useful to add the equivalent git command next to functions in the documentation, since most people will understand that already) Anyway, my questions: The BASIC docs are missing (https://mirage.github.io/irmin/Irmin.BASIC.html), but the code shows: type ('a, 'b) basic = (module BASIC with type key = 'a and type value = 'b) It seems that using Irmin.Contents.String gets me "key = string list", but "step" remains abstract. How do I use cons, decons, etc? If I have a RW store, I can watch a key: val watch : t -> key -> value option Lwt_stream.t Presumably, I also need to take care to stop watching it when I'm done, otherwise the stream will grow without limit, right? I guess there should be an unwatch, or maybe this should be a React signal or something. I got a bit confused when I reached the BC page: https://mirage.github.io/irmin/Irmin.BC.html It uses 'tag' to mean a pointer to a commit that is updates on each operation (i.e. what Git would call a 'branch'). I realise that tags and branches are the same thing internally, but 'branch' seems to capture better what Irmin is using them for ("The tag value is updated every time the store is updated, so every handle connected or which will be connected to the same tag will see the changes."). [ BTW, what's a "handle"? ] val update_tag : t -> tag -> unit Lwt.t update_tag t tag updates t's current branch with the contents of the branch named tag. What does "update" mean here? Is this "git reset --hard tag"? A merge? A "--ff-only" merge? My mental model of Git is that the store is a DAG and I can append to any branch. e.g. we have: git commit-tree [(-p )...] < changelog If I'm understanding the Irmin API correctly, each "store" (repository? branch?) has a current "tag" (branch) and I need to set the tag I want to work on, e.g. val switch : Store.t -> tag -> unit Lwt.t If I want to work on another branch without changing the current branch for other users, I should "clone" the store: val clone_force : ('a -> Irmin.task) -> t -> tag -> ('a -> t) Lwt.t But, this is not a "git clone", it's like "git branch tag" - a new branch I can work on without affecting the repository's default branch. It seems strange that Irmin has a mutable "current branch" at all - this seems like a UI concept that's only needed for command-line use (to save typing). A "head" is defined as "a given store revision" (i.e. what Git would call a commit). It wasn't clear to me at first whether a head was a commit or an anonymous branch. e.g. val rename_tag : t -> tag -> [ `Duplicated_tag | `Ok ] Lwt.t Change the current tag name. Fail if a tag with the same name already exists. The head is unchanged. "The head is unchanged" suggests that heads might change in other cases. Looking at the code, I see a "type head = Commit.key" in one place, so I guess they're (usually?) commits. Does "head" here mean "the default branch"? Finally, how do I get history? e.g. if I want to show users the recent changes to a document. I see a "slice" type, but it's not clear what I can do with it. Thanks! -- Dr Thomas Leonard http://0install.net/ GPG: 9242 9807 C985 3C07 44A6 8B9A AE07 8280 59A5 3CC1 GPG: DA98 25AE CAD0 8975 7CDA BD8E 0713 3F96 CA74 D8BA _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Mon Feb 09 12:03:14 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 09 Feb 2015 12:03:14 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YKn3a-0006r5-4C; Mon, 09 Feb 2015 12:03:14 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YKn3Y-0006oM-TR for mirageos-devel@lists.xenproject.org; Mon, 09 Feb 2015 12:03:13 +0000 Received: from [85.158.139.211] by server-14.bemta-5.messagelabs.com id EC/6C-02809-002A8D45; Mon, 09 Feb 2015 12:03:12 +0000 X-Env-Sender: talex5@gmail.com X-Msg-Ref: server-11.tower-206.messagelabs.com!1423483390!6732147!1 X-Originating-IP: [209.85.217.181] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27792 invoked from network); 9 Feb 2015 12:03:11 -0000 Received: from mail-lb0-f181.google.com (HELO mail-lb0-f181.google.com) (209.85.217.181) by server-11.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 9 Feb 2015 12:03:11 -0000 Received: by mail-lb0-f181.google.com with SMTP id b6so6661031lbj.12 for ; Mon, 09 Feb 2015 04:03:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=+PeJX36Z3UFPbOOY+gXRzb5ntFizZbj9D8r+GsT8GO8=; b=u2XuU/YXz9QPx+Y7fIEAI2/MMrNP29BPvWnl24ao98Eq2iCiHFJgJgWwMEVhK5tg8V NcJpaeC2Aj1/VqauYpszQwDmwVymyRIKtDZaf2eRZZ8HwifSxAzwOjsYhxg81auJzQcz J5YyODpYqOKjmGM5SKnWzk5uak+Pz94+PGiWP2UB1CDEVyg68wgEM0lQv9h/S7d2PIZ+ A7A8m+WK9H9Ney3Q0vdSuPOBvuzZN31ajWrvy4/DZp6Ze2y1xrgTqQW0OB+ioiGNpOE1 eojlXlC8egZguWuz6zq7XucNeyL0nX4sOm0Whc/d7IIQJ6z4NPBzYENFNaNbXLRM3cAB I5oQ== MIME-Version: 1.0 X-Received: by 10.152.170.170 with SMTP id an10mr16308906lac.121.1423483389598; Mon, 09 Feb 2015 04:03:09 -0800 (PST) Received: by 10.25.207.206 with HTTP; Mon, 9 Feb 2015 04:03:09 -0800 (PST) Date: Mon, 9 Feb 2015 12:03:09 +0000 Message-ID: From: Thomas Leonard To: "mirageos-devel@lists.xenproject.org" Subject: [MirageOS-devel] Irmin API newbie questions X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org I'm trying to understand the Irmin API. The current documentation is good, but I'm still having trouble with some of the concepts. I'm looking at these sources: https://mirage.github.io/irmin/ https://github.com/mirage/irmin/wiki/Using-the-Irmin-API (BTW, I think it might be useful to add the equivalent git command next to functions in the documentation, since most people will understand that already) Anyway, my questions: The BASIC docs are missing (https://mirage.github.io/irmin/Irmin.BASIC.html), but the code shows: type ('a, 'b) basic = (module BASIC with type key = 'a and type value = 'b) It seems that using Irmin.Contents.String gets me "key = string list", but "step" remains abstract. How do I use cons, decons, etc? If I have a RW store, I can watch a key: val watch : t -> key -> value option Lwt_stream.t Presumably, I also need to take care to stop watching it when I'm done, otherwise the stream will grow without limit, right? I guess there should be an unwatch, or maybe this should be a React signal or something. I got a bit confused when I reached the BC page: https://mirage.github.io/irmin/Irmin.BC.html It uses 'tag' to mean a pointer to a commit that is updates on each operation (i.e. what Git would call a 'branch'). I realise that tags and branches are the same thing internally, but 'branch' seems to capture better what Irmin is using them for ("The tag value is updated every time the store is updated, so every handle connected or which will be connected to the same tag will see the changes."). [ BTW, what's a "handle"? ] val update_tag : t -> tag -> unit Lwt.t update_tag t tag updates t's current branch with the contents of the branch named tag. What does "update" mean here? Is this "git reset --hard tag"? A merge? A "--ff-only" merge? My mental model of Git is that the store is a DAG and I can append to any branch. e.g. we have: git commit-tree [(-p )...] < changelog If I'm understanding the Irmin API correctly, each "store" (repository? branch?) has a current "tag" (branch) and I need to set the tag I want to work on, e.g. val switch : Store.t -> tag -> unit Lwt.t If I want to work on another branch without changing the current branch for other users, I should "clone" the store: val clone_force : ('a -> Irmin.task) -> t -> tag -> ('a -> t) Lwt.t But, this is not a "git clone", it's like "git branch tag" - a new branch I can work on without affecting the repository's default branch. It seems strange that Irmin has a mutable "current branch" at all - this seems like a UI concept that's only needed for command-line use (to save typing). A "head" is defined as "a given store revision" (i.e. what Git would call a commit). It wasn't clear to me at first whether a head was a commit or an anonymous branch. e.g. val rename_tag : t -> tag -> [ `Duplicated_tag | `Ok ] Lwt.t Change the current tag name. Fail if a tag with the same name already exists. The head is unchanged. "The head is unchanged" suggests that heads might change in other cases. Looking at the code, I see a "type head = Commit.key" in one place, so I guess they're (usually?) commits. Does "head" here mean "the default branch"? Finally, how do I get history? e.g. if I want to show users the recent changes to a document. I see a "slice" type, but it's not clear what I can do with it. Thanks! -- Dr Thomas Leonard http://0install.net/ GPG: 9242 9807 C985 3C07 44A6 8B9A AE07 8280 59A5 3CC1 GPG: DA98 25AE CAD0 8975 7CDA BD8E 0713 3F96 CA74 D8BA _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Mon Feb 09 13:01:40 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 09 Feb 2015 13:01:40 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YKny5-0002kb-If; Mon, 09 Feb 2015 13:01:37 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YKny4-0002kW-NO for mirageos-devel@lists.xenproject.org; Mon, 09 Feb 2015 13:01:36 +0000 Received: from [85.158.143.35] by server-1.bemta-4.messagelabs.com id 25/4A-03000-0BFA8D45; Mon, 09 Feb 2015 13:01:36 +0000 X-Env-Sender: amc79@cam.ac.uk X-Msg-Ref: server-12.tower-21.messagelabs.com!1423486894!12655948!1 X-Originating-IP: [131.111.8.150] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTMxLjExMS44LjE1MCA9PiAxNDk0MDU=\n X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6633 invoked from network); 9 Feb 2015 13:01:35 -0000 Received: from ppsw-50.csi.cam.ac.uk (HELO ppsw-50.csi.cam.ac.uk) (131.111.8.150) by server-12.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 9 Feb 2015 13:01:35 -0000 X-Cam-AntiVirus: no malware found X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/ Received: from dhcp-172-17-152-130.eduroam.wireless.private.cam.ac.uk ([172.17.152.130]:57460) by ppsw-50.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.158]:587) with esmtpsa (PLAIN:amc79) (TLSv1:AES128-SHA:128) id 1YKny2-0004FB-pe (Exim 4.82_3-c0e5623) (return-path ); Mon, 09 Feb 2015 13:01:34 +0000 Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) From: Amir Chaudhry In-Reply-To: <707E3CE1-4C4D-4F3F-9BB1-F5D31D8668EB@gmail.com> Date: Mon, 9 Feb 2015 13:01:33 +0000 Message-Id: <2A47AAA1-5915-4715-B9A7-6ADC1375110F@cam.ac.uk> References: <2B0C0681-8266-420A-A74B-1BCCFDCD3F23@gmail.com> <0A2884DD-0391-4E50-A68B-71D8A8A68296@cam.ac.uk> <707E3CE1-4C4D-4F3F-9BB1-F5D31D8668EB@gmail.com> To: Lars Kurth X-Mailer: Apple Mail (2.1510) Cc: mirageos-devel , Anil Madhavapeddy Subject: Re: [MirageOS-devel] MirageOS and GSoC (was: Re: IMPORTANT: GSoC 2015 page created - Need to confirm old projects, create/review new ones and fix projects with issues before Feb 22nd) X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 9 Feb 2015, at 11:52, Lars Kurth wrote: > >> On 8 Feb 2015, at 19:03, Anil Madhavapeddy wrote: >> >> On 6 Feb 2015, at 18:19, Amir Chaudhry wrote: >>> >> >> How about we just link the Pioneer Projects page to the Xen Project wiki? It'll be useful not to duplicate these things. > > That works for me, with maybe with a list of the projects and a set of instructions on how to apply for them as part of GSoC. I would suggest to add something like > > ==== Additional Pioneer Projects ==== > {{project > |Project=Additional Pioneer Projects > |Date=01/30/2015 > |Verified=Feb 8th, 2015 (see this [http://lists.xenproject.org/archives/html/mirageos-devel/2015-02/msg00046.html conversation]) > |Contact=Send a mail to mirageos-devel@lists.xenproject.org if you're interested in starting on one or several of these projects. > |Difficulty=Various levels of difficulty > |Skills=OCaml > |Desc=This is a list of pioneer projects for Mirage OS, covering area such as '''Build Tools''', '''New Libraries''', '''Storage Technologies''', '''Networking Technologies''', '''Interfaces to Non-Ocaml (aka foreign) Languages''' and other topics. Note that some of these projects may be too small or too big for a single GSoC project. If you are interested in one of these, make sure you discuss first on mirageos-devel@lists.xenproject.org - we can then merge or split these as needed for GSoC. > > References: > * [https://github.com/mirage/mirage-www/wiki/Pioneer-Projects Complete list of Pioneer Projects] > > |GSoC=yes, but do check mirageos-devel@lists.xenproject.org first > }} If it works for you, then that's fine with me. I've made an edit to the Xen GSoC Project page (with the above suggestion) and will copy back the existing three projects over to the Pioneer's page. Then it's just about collating more projects. AC _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Mon Feb 09 13:01:40 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 09 Feb 2015 13:01:40 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YKny5-0002kb-If; Mon, 09 Feb 2015 13:01:37 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YKny4-0002kW-NO for mirageos-devel@lists.xenproject.org; Mon, 09 Feb 2015 13:01:36 +0000 Received: from [85.158.143.35] by server-1.bemta-4.messagelabs.com id 25/4A-03000-0BFA8D45; Mon, 09 Feb 2015 13:01:36 +0000 X-Env-Sender: amc79@cam.ac.uk X-Msg-Ref: server-12.tower-21.messagelabs.com!1423486894!12655948!1 X-Originating-IP: [131.111.8.150] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTMxLjExMS44LjE1MCA9PiAxNDk0MDU=\n X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6633 invoked from network); 9 Feb 2015 13:01:35 -0000 Received: from ppsw-50.csi.cam.ac.uk (HELO ppsw-50.csi.cam.ac.uk) (131.111.8.150) by server-12.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 9 Feb 2015 13:01:35 -0000 X-Cam-AntiVirus: no malware found X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/ Received: from dhcp-172-17-152-130.eduroam.wireless.private.cam.ac.uk ([172.17.152.130]:57460) by ppsw-50.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.158]:587) with esmtpsa (PLAIN:amc79) (TLSv1:AES128-SHA:128) id 1YKny2-0004FB-pe (Exim 4.82_3-c0e5623) (return-path ); Mon, 09 Feb 2015 13:01:34 +0000 Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) From: Amir Chaudhry In-Reply-To: <707E3CE1-4C4D-4F3F-9BB1-F5D31D8668EB@gmail.com> Date: Mon, 9 Feb 2015 13:01:33 +0000 Message-Id: <2A47AAA1-5915-4715-B9A7-6ADC1375110F@cam.ac.uk> References: <2B0C0681-8266-420A-A74B-1BCCFDCD3F23@gmail.com> <0A2884DD-0391-4E50-A68B-71D8A8A68296@cam.ac.uk> <707E3CE1-4C4D-4F3F-9BB1-F5D31D8668EB@gmail.com> To: Lars Kurth X-Mailer: Apple Mail (2.1510) Cc: mirageos-devel , Anil Madhavapeddy Subject: Re: [MirageOS-devel] MirageOS and GSoC (was: Re: IMPORTANT: GSoC 2015 page created - Need to confirm old projects, create/review new ones and fix projects with issues before Feb 22nd) X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 9 Feb 2015, at 11:52, Lars Kurth wrote: > >> On 8 Feb 2015, at 19:03, Anil Madhavapeddy wrote: >> >> On 6 Feb 2015, at 18:19, Amir Chaudhry wrote: >>> >> >> How about we just link the Pioneer Projects page to the Xen Project wiki? It'll be useful not to duplicate these things. > > That works for me, with maybe with a list of the projects and a set of instructions on how to apply for them as part of GSoC. I would suggest to add something like > > ==== Additional Pioneer Projects ==== > {{project > |Project=Additional Pioneer Projects > |Date=01/30/2015 > |Verified=Feb 8th, 2015 (see this [http://lists.xenproject.org/archives/html/mirageos-devel/2015-02/msg00046.html conversation]) > |Contact=Send a mail to mirageos-devel@lists.xenproject.org if you're interested in starting on one or several of these projects. > |Difficulty=Various levels of difficulty > |Skills=OCaml > |Desc=This is a list of pioneer projects for Mirage OS, covering area such as '''Build Tools''', '''New Libraries''', '''Storage Technologies''', '''Networking Technologies''', '''Interfaces to Non-Ocaml (aka foreign) Languages''' and other topics. Note that some of these projects may be too small or too big for a single GSoC project. If you are interested in one of these, make sure you discuss first on mirageos-devel@lists.xenproject.org - we can then merge or split these as needed for GSoC. > > References: > * [https://github.com/mirage/mirage-www/wiki/Pioneer-Projects Complete list of Pioneer Projects] > > |GSoC=yes, but do check mirageos-devel@lists.xenproject.org first > }} If it works for you, then that's fine with me. I've made an edit to the Xen GSoC Project page (with the above suggestion) and will copy back the existing three projects over to the Pioneer's page. Then it's just about collating more projects. AC _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Mon Feb 09 14:03:03 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 09 Feb 2015 14:03:03 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YKovQ-0001OT-EM; Mon, 09 Feb 2015 14:02:56 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YKovP-0001OK-JM for mirageos-devel@lists.xenproject.org; Mon, 09 Feb 2015 14:02:55 +0000 Received: from [85.158.137.68] by server-10.bemta-3.messagelabs.com id B1/E6-02745-E0EB8D45; Mon, 09 Feb 2015 14:02:54 +0000 X-Env-Sender: yallop@gmail.com X-Msg-Ref: server-4.tower-31.messagelabs.com!1423490574!11618355!1 X-Originating-IP: [209.85.212.181] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8444 invoked from network); 9 Feb 2015 14:02:54 -0000 Received: from mail-wi0-f181.google.com (HELO mail-wi0-f181.google.com) (209.85.212.181) by server-4.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 9 Feb 2015 14:02:54 -0000 Received: by mail-wi0-f181.google.com with SMTP id r20so993437wiv.2 for ; Mon, 09 Feb 2015 06:02:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=P+GZd2nivrpRux2yMUxG9sH8QuFF49kBfyg0CtvSSN4=; b=U3JtZDxC1bk8dYUq2f7bCysTAdlUYbe6Ojc/+KooIS+5NBDMjYNW7uhRbznCALkfOD Bv/yQtvAAHH6LmZhj80u3G3zHF0MhkJTZMsqZHGlSm+YVX9Dfrdy82VR5EdDHyxAXUBA 3nZmKkQ49N+i2eTW+gEhygvuFHRHwCQvgFqlH3gdZ/0yHzHPWq5xIXDt23aDsBpL8DlQ vwkHzq2GUArSLGAl6v/Ex5oZ+0dedxoWiHU/YdfAwRUUDuDqRNQ4b9kwx3ifzamNmgNc +WCJG+P/FDH6/hDBZtUysfVdZXLY1TLVsgiyjJ8nhei+xOSU6FEekRqZKX52eWVWNFgL vDoQ== MIME-Version: 1.0 X-Received: by 10.194.110.233 with SMTP id id9mr41704239wjb.136.1423490573876; Mon, 09 Feb 2015 06:02:53 -0800 (PST) Received: by 10.217.13.73 with HTTP; Mon, 9 Feb 2015 06:02:53 -0800 (PST) In-Reply-To: References: Date: Mon, 9 Feb 2015 14:02:53 +0000 Message-ID: From: Jeremy Yallop To: cam-compiler-hacking@lists.ocaml.org, "cl-ocamllabs@lists.cam.ac.uk" , "cl-ocamllabs-staff@lists.cam.ac.uk" , "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Compiler hacking evening next Tuesday (10th February) X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org Reminder: compiler hacking tomorrow! If you're planning to come along, please add your name to the poll: http://doodle.com/zxmeyn2ih92mke85 On 6 February 2015 at 10:58, Jeremy Yallop wrote: > It's time for another evening of OCaml compiler hacking! We'll be meeting > next Tuesday evening (10th February) in the Computer Lab. If you're > planning to come along, please add yourself to the Doodle poll: > > http://doodle.com/zxmeyn2ih92mke85 > > Schedule: > > 1800 - Start, set up > 1830 - Talk: Generating code with polymorphic let (Oleg Kiselyov) > 1900 - Pizza > 1930-2200 Compiler hacking > > Further details are on the blog: > > > http://ocamllabs.github.io/compiler-hacking/2015/02/05/back-in-the-lab.html > > All welcome: if you're local to Cambridge and interested in contributing to > the OCaml compiler, please come along! _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Mon Feb 09 14:03:03 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 09 Feb 2015 14:03:03 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YKovQ-0001OT-EM; Mon, 09 Feb 2015 14:02:56 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YKovP-0001OK-JM for mirageos-devel@lists.xenproject.org; Mon, 09 Feb 2015 14:02:55 +0000 Received: from [85.158.137.68] by server-10.bemta-3.messagelabs.com id B1/E6-02745-E0EB8D45; Mon, 09 Feb 2015 14:02:54 +0000 X-Env-Sender: yallop@gmail.com X-Msg-Ref: server-4.tower-31.messagelabs.com!1423490574!11618355!1 X-Originating-IP: [209.85.212.181] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8444 invoked from network); 9 Feb 2015 14:02:54 -0000 Received: from mail-wi0-f181.google.com (HELO mail-wi0-f181.google.com) (209.85.212.181) by server-4.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 9 Feb 2015 14:02:54 -0000 Received: by mail-wi0-f181.google.com with SMTP id r20so993437wiv.2 for ; Mon, 09 Feb 2015 06:02:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=P+GZd2nivrpRux2yMUxG9sH8QuFF49kBfyg0CtvSSN4=; b=U3JtZDxC1bk8dYUq2f7bCysTAdlUYbe6Ojc/+KooIS+5NBDMjYNW7uhRbznCALkfOD Bv/yQtvAAHH6LmZhj80u3G3zHF0MhkJTZMsqZHGlSm+YVX9Dfrdy82VR5EdDHyxAXUBA 3nZmKkQ49N+i2eTW+gEhygvuFHRHwCQvgFqlH3gdZ/0yHzHPWq5xIXDt23aDsBpL8DlQ vwkHzq2GUArSLGAl6v/Ex5oZ+0dedxoWiHU/YdfAwRUUDuDqRNQ4b9kwx3ifzamNmgNc +WCJG+P/FDH6/hDBZtUysfVdZXLY1TLVsgiyjJ8nhei+xOSU6FEekRqZKX52eWVWNFgL vDoQ== MIME-Version: 1.0 X-Received: by 10.194.110.233 with SMTP id id9mr41704239wjb.136.1423490573876; Mon, 09 Feb 2015 06:02:53 -0800 (PST) Received: by 10.217.13.73 with HTTP; Mon, 9 Feb 2015 06:02:53 -0800 (PST) In-Reply-To: References: Date: Mon, 9 Feb 2015 14:02:53 +0000 Message-ID: From: Jeremy Yallop To: cam-compiler-hacking@lists.ocaml.org, "cl-ocamllabs@lists.cam.ac.uk" , "cl-ocamllabs-staff@lists.cam.ac.uk" , "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Compiler hacking evening next Tuesday (10th February) X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org Reminder: compiler hacking tomorrow! If you're planning to come along, please add your name to the poll: http://doodle.com/zxmeyn2ih92mke85 On 6 February 2015 at 10:58, Jeremy Yallop wrote: > It's time for another evening of OCaml compiler hacking! We'll be meeting > next Tuesday evening (10th February) in the Computer Lab. If you're > planning to come along, please add yourself to the Doodle poll: > > http://doodle.com/zxmeyn2ih92mke85 > > Schedule: > > 1800 - Start, set up > 1830 - Talk: Generating code with polymorphic let (Oleg Kiselyov) > 1900 - Pizza > 1930-2200 Compiler hacking > > Further details are on the blog: > > > http://ocamllabs.github.io/compiler-hacking/2015/02/05/back-in-the-lab.html > > All welcome: if you're local to Cambridge and interested in contributing to > the OCaml compiler, please come along! _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Mon Feb 09 14:41:16 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 09 Feb 2015 14:41:16 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YKpWV-0004Ah-Kb; Mon, 09 Feb 2015 14:41:15 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YKpWU-0004Aa-Tc for mirageos-devel@lists.xenproject.org; Mon, 09 Feb 2015 14:41:15 +0000 Received: from [193.109.254.147] by server-12.bemta-14.messagelabs.com id 7A/25-02755-A07C8D45; Mon, 09 Feb 2015 14:41:14 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-4.tower-27.messagelabs.com!1423492870!12287617!1 X-Originating-IP: [74.125.82.176] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3179 invoked from network); 9 Feb 2015 14:41:11 -0000 Received: from mail-we0-f176.google.com (HELO mail-we0-f176.google.com) (74.125.82.176) by server-4.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 9 Feb 2015 14:41:11 -0000 Received: by mail-we0-f176.google.com with SMTP id x3so2338606wes.7 for ; Mon, 09 Feb 2015 06:41:10 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=356O0mLTc91tGPKA0HBUQiKcOC4D79y62mkDsbpk63k=; b=nB3IjV6YgbexslzJwgQF0UWGxGQDOum6OHQkWPT+zHU39A8UiRNN5dfir18h0//OsK iZFMelfJ0opiukEBKbP4PivMTswNoHGA+9K65HJD/ML0+0oZ2CjYXRpeG9USk8WVQrA0 +fgD0tJZBvTsZbmtgrlz84SfYfmrI/kVRgSwDJA4ouyx7Bs+mM1hGgv+9dlTi7zPd+qn K8ShmNVci/jbnb9q7eTlsPlLEDM70rvZ5VmUADU5V4AZ8ZHOzi8t/kBvoV9ye8EL0qzZ XsFRrP1FagsgFcA/v2jOa/ES+OsbGEJ/8Lz1TgyVMZXoHsrfwA87VmAbN//3pjEaBmqY K8YA== X-Received: by 10.180.212.113 with SMTP id nj17mr36538423wic.54.1423492870330; Mon, 09 Feb 2015 06:41:10 -0800 (PST) Received: from ?IPv6:2001:630:212:248:397d:e69c:d6e2:1606? ([2001:630:212:248:397d:e69c:d6e2:1606]) by mx.google.com with ESMTPSA id tc2sm14665959wic.21.2015.02.09.06.41.08 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 09 Feb 2015 06:41:09 -0800 (PST) Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\)) From: Thomas Gazagnaire In-Reply-To: Date: Mon, 9 Feb 2015 14:41:08 +0000 Message-Id: <8CEDB416-6238-4888-BA4B-B7305FDDE2D9@gazagnaire.org> References: To: Thomas Leonard X-Mailer: Apple Mail (2.1993) Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Irmin API newbie questions X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org Hi Thomas, > (BTW, I think it might be useful to add the equivalent git command > next to functions in the documentation, since most people will > understand that already) ack, I'll do this. > The BASIC docs are missing > (https://mirage.github.io/irmin/Irmin.BASIC.html), but the code shows: > > type ('a, 'b) basic = (module BASIC with type key = 'a and type value = 'b) > > It seems that using Irmin.Contents.String gets me "key = string list", > but "step" remains abstract. How do I use cons, decons, etc? Why do you need to use cons and decons? Normally you should just need to use the usual list operators (ie. (::) for cons and pattern-matching for decons). If you have a use-case where this is not enough, please share it! It's possible that I forgot to export a type constraint somewhere. > If I have a RW store, I can watch a key: > > val watch : t -> key -> value option Lwt_stream.t > > Presumably, I also need to take care to stop watching it when I'm > done, otherwise the stream will grow without limit, right? I guess > there should be an unwatch, or maybe this should be a React signal or > something. Yes the watch API still needs some work. It's working-ish enough to demo small examples (for instance you can run some of the examples and connect to http://127.0.0.1:8080/graph to see a nice animated graph of the store), but as you noticed there is no GC of ressources, maybe some leaks and the behaviour under load is not satisfactory (see issue https://github.com/mirage/irmin/issues/124). > I got a bit confused when I reached the BC page: > > https://mirage.github.io/irmin/Irmin.BC.html > > It uses 'tag' to mean a pointer to a commit that is updates on each > operation (i.e. what Git would call a 'branch'). I realise that tags > and branches are the same thing internally, but 'branch' seems to > capture better what Irmin is using them for ("The tag value is updated > every time the store is updated, so every handle connected or which > will be connected to the same tag will see the changes."). [ BTW, > what's a "handle"? ] The documentation is not totally clear here, you're right. You have two ways to identify a branch: either by name or by hash. In Irmin terminology, a branch name is a "tag". A commit hash is a "head". > val update_tag : t -> tag -> unit Lwt.t > update_tag t tag updates t's current branch with the contents of the > branch named tag. > > What does "update" mean here? Is this "git reset --hard tag"? A merge? > A "--ff-only" merge? `update_tag` is similar to `git reset --hard `. merge_tag is similar to `git merge `. I've tried to keep the update/merge duality in most of the places (you can update/merge a head, a view, an other branch). > My mental model of Git is that the store is a DAG and I can append to > any branch. e.g. we have: > > git commit-tree [(-p )...] < changelog > > If I'm understanding the Irmin API correctly, each "store" > (repository? branch?) has a current "tag" (branch) and I need to set > the tag I want to work on, e.g. > > val switch : Store.t -> tag -> unit Lwt.t The simplest way to initialise a branch using a tag is to use `Irmin.of_tag ... `. If you want to create a branch in a "detached" mode, use `Irmin.of_head ... `. But yes, you can use switch to switch to another named branch. > If I want to work on another branch without changing the current > branch for other users, I should "clone" the store: > > val clone_force : ('a -> Irmin.task) -> t -> tag -> ('a -> t) Lwt.t > > But, this is not a "git clone", it's like "git branch tag" - a new > branch I can work on without affecting the repository's default > branch. It seems strange that Irmin has a mutable "current branch" at > all - this seems like a UI concept that's only needed for command-line > use (to save typing). Irmin has a concept of default branch (ie. "master") which is used when you use "Irmin.create". I choose that because the simplest use-case is to use Irmin as a normal k/v store, without having to worry about branches and such. > A "head" is defined as "a given store revision" (i.e. what Git would > call a commit). It wasn't clear to me at first whether a head was a > commit or an anonymous branch. e.g. A head is a commit hash. You can use a head with Irmin.of_head to create an anonymous branch. I agree that the documentation is not very clear on that. > val rename_tag : t -> tag -> [ `Duplicated_tag | `Ok ] Lwt.t > Change the current tag name. Fail if a tag with the same name already > exists. The head is unchanged. > > "The head is unchanged" suggests that heads might change in other > cases. Looking at the code, I see a "type head = Commit.key" in one > place, so I guess they're (usually?) commits. Does "head" here mean > "the default branch"? I'll make another pass on that part of the documentation to try to make all of these concepts clearer. I'll try to relate the API functions to Git command-line arguments, although I'm not sure the Git command-line is a model of clarity as well: `git reset --hard` is very different from `git reset --soft` for instance, and there are no direct notion on index file in Irmin (although the views can be seen as a kind of staging area). > Finally, how do I get history? e.g. if I want to show users the recent > changes to a document. I see a "slice" type, but it's not clear what I > can do with it. Anil asked me the question recently, and I promise him to add the missing function in the "simple" API. For now on, the functions are well-hidden inside the private API: The History[1] functor gives you a "closure" function, which gives you a slice of the history graph. The functor needs a contents store (if S is of type Irmin.S, then S,Private.Contents) and a node store (S.Private.Node). But that's far too hard to use, I'll add an helper function in the API to get you a OCamlgraph graph of commits (and optionally tree and blobs) instead. Thanks for that very helpful report! I hope it makes things a little bit clearer. Thomas [1] http://mirage.github.io/irmin/Irmin.Private.Commit.History.html > > > Thanks! > > > -- > Dr Thomas Leonard http://0install.net/ > GPG: 9242 9807 C985 3C07 44A6 8B9A AE07 8280 59A5 3CC1 > GPG: DA98 25AE CAD0 8975 7CDA BD8E 0713 3F96 CA74 D8BA > > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Mon Feb 09 14:41:16 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 09 Feb 2015 14:41:16 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YKpWV-0004Ah-Kb; Mon, 09 Feb 2015 14:41:15 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YKpWU-0004Aa-Tc for mirageos-devel@lists.xenproject.org; Mon, 09 Feb 2015 14:41:15 +0000 Received: from [193.109.254.147] by server-12.bemta-14.messagelabs.com id 7A/25-02755-A07C8D45; Mon, 09 Feb 2015 14:41:14 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-4.tower-27.messagelabs.com!1423492870!12287617!1 X-Originating-IP: [74.125.82.176] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3179 invoked from network); 9 Feb 2015 14:41:11 -0000 Received: from mail-we0-f176.google.com (HELO mail-we0-f176.google.com) (74.125.82.176) by server-4.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 9 Feb 2015 14:41:11 -0000 Received: by mail-we0-f176.google.com with SMTP id x3so2338606wes.7 for ; Mon, 09 Feb 2015 06:41:10 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=356O0mLTc91tGPKA0HBUQiKcOC4D79y62mkDsbpk63k=; b=nB3IjV6YgbexslzJwgQF0UWGxGQDOum6OHQkWPT+zHU39A8UiRNN5dfir18h0//OsK iZFMelfJ0opiukEBKbP4PivMTswNoHGA+9K65HJD/ML0+0oZ2CjYXRpeG9USk8WVQrA0 +fgD0tJZBvTsZbmtgrlz84SfYfmrI/kVRgSwDJA4ouyx7Bs+mM1hGgv+9dlTi7zPd+qn K8ShmNVci/jbnb9q7eTlsPlLEDM70rvZ5VmUADU5V4AZ8ZHOzi8t/kBvoV9ye8EL0qzZ XsFRrP1FagsgFcA/v2jOa/ES+OsbGEJ/8Lz1TgyVMZXoHsrfwA87VmAbN//3pjEaBmqY K8YA== X-Received: by 10.180.212.113 with SMTP id nj17mr36538423wic.54.1423492870330; Mon, 09 Feb 2015 06:41:10 -0800 (PST) Received: from ?IPv6:2001:630:212:248:397d:e69c:d6e2:1606? ([2001:630:212:248:397d:e69c:d6e2:1606]) by mx.google.com with ESMTPSA id tc2sm14665959wic.21.2015.02.09.06.41.08 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 09 Feb 2015 06:41:09 -0800 (PST) Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\)) From: Thomas Gazagnaire In-Reply-To: Date: Mon, 9 Feb 2015 14:41:08 +0000 Message-Id: <8CEDB416-6238-4888-BA4B-B7305FDDE2D9@gazagnaire.org> References: To: Thomas Leonard X-Mailer: Apple Mail (2.1993) Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Irmin API newbie questions X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org Hi Thomas, > (BTW, I think it might be useful to add the equivalent git command > next to functions in the documentation, since most people will > understand that already) ack, I'll do this. > The BASIC docs are missing > (https://mirage.github.io/irmin/Irmin.BASIC.html), but the code shows: > > type ('a, 'b) basic = (module BASIC with type key = 'a and type value = 'b) > > It seems that using Irmin.Contents.String gets me "key = string list", > but "step" remains abstract. How do I use cons, decons, etc? Why do you need to use cons and decons? Normally you should just need to use the usual list operators (ie. (::) for cons and pattern-matching for decons). If you have a use-case where this is not enough, please share it! It's possible that I forgot to export a type constraint somewhere. > If I have a RW store, I can watch a key: > > val watch : t -> key -> value option Lwt_stream.t > > Presumably, I also need to take care to stop watching it when I'm > done, otherwise the stream will grow without limit, right? I guess > there should be an unwatch, or maybe this should be a React signal or > something. Yes the watch API still needs some work. It's working-ish enough to demo small examples (for instance you can run some of the examples and connect to http://127.0.0.1:8080/graph to see a nice animated graph of the store), but as you noticed there is no GC of ressources, maybe some leaks and the behaviour under load is not satisfactory (see issue https://github.com/mirage/irmin/issues/124). > I got a bit confused when I reached the BC page: > > https://mirage.github.io/irmin/Irmin.BC.html > > It uses 'tag' to mean a pointer to a commit that is updates on each > operation (i.e. what Git would call a 'branch'). I realise that tags > and branches are the same thing internally, but 'branch' seems to > capture better what Irmin is using them for ("The tag value is updated > every time the store is updated, so every handle connected or which > will be connected to the same tag will see the changes."). [ BTW, > what's a "handle"? ] The documentation is not totally clear here, you're right. You have two ways to identify a branch: either by name or by hash. In Irmin terminology, a branch name is a "tag". A commit hash is a "head". > val update_tag : t -> tag -> unit Lwt.t > update_tag t tag updates t's current branch with the contents of the > branch named tag. > > What does "update" mean here? Is this "git reset --hard tag"? A merge? > A "--ff-only" merge? `update_tag` is similar to `git reset --hard `. merge_tag is similar to `git merge `. I've tried to keep the update/merge duality in most of the places (you can update/merge a head, a view, an other branch). > My mental model of Git is that the store is a DAG and I can append to > any branch. e.g. we have: > > git commit-tree [(-p )...] < changelog > > If I'm understanding the Irmin API correctly, each "store" > (repository? branch?) has a current "tag" (branch) and I need to set > the tag I want to work on, e.g. > > val switch : Store.t -> tag -> unit Lwt.t The simplest way to initialise a branch using a tag is to use `Irmin.of_tag ... `. If you want to create a branch in a "detached" mode, use `Irmin.of_head ... `. But yes, you can use switch to switch to another named branch. > If I want to work on another branch without changing the current > branch for other users, I should "clone" the store: > > val clone_force : ('a -> Irmin.task) -> t -> tag -> ('a -> t) Lwt.t > > But, this is not a "git clone", it's like "git branch tag" - a new > branch I can work on without affecting the repository's default > branch. It seems strange that Irmin has a mutable "current branch" at > all - this seems like a UI concept that's only needed for command-line > use (to save typing). Irmin has a concept of default branch (ie. "master") which is used when you use "Irmin.create". I choose that because the simplest use-case is to use Irmin as a normal k/v store, without having to worry about branches and such. > A "head" is defined as "a given store revision" (i.e. what Git would > call a commit). It wasn't clear to me at first whether a head was a > commit or an anonymous branch. e.g. A head is a commit hash. You can use a head with Irmin.of_head to create an anonymous branch. I agree that the documentation is not very clear on that. > val rename_tag : t -> tag -> [ `Duplicated_tag | `Ok ] Lwt.t > Change the current tag name. Fail if a tag with the same name already > exists. The head is unchanged. > > "The head is unchanged" suggests that heads might change in other > cases. Looking at the code, I see a "type head = Commit.key" in one > place, so I guess they're (usually?) commits. Does "head" here mean > "the default branch"? I'll make another pass on that part of the documentation to try to make all of these concepts clearer. I'll try to relate the API functions to Git command-line arguments, although I'm not sure the Git command-line is a model of clarity as well: `git reset --hard` is very different from `git reset --soft` for instance, and there are no direct notion on index file in Irmin (although the views can be seen as a kind of staging area). > Finally, how do I get history? e.g. if I want to show users the recent > changes to a document. I see a "slice" type, but it's not clear what I > can do with it. Anil asked me the question recently, and I promise him to add the missing function in the "simple" API. For now on, the functions are well-hidden inside the private API: The History[1] functor gives you a "closure" function, which gives you a slice of the history graph. The functor needs a contents store (if S is of type Irmin.S, then S,Private.Contents) and a node store (S.Private.Node). But that's far too hard to use, I'll add an helper function in the API to get you a OCamlgraph graph of commits (and optionally tree and blobs) instead. Thanks for that very helpful report! I hope it makes things a little bit clearer. Thomas [1] http://mirage.github.io/irmin/Irmin.Private.Commit.History.html > > > Thanks! > > > -- > Dr Thomas Leonard http://0install.net/ > GPG: 9242 9807 C985 3C07 44A6 8B9A AE07 8280 59A5 3CC1 > GPG: DA98 25AE CAD0 8975 7CDA BD8E 0713 3F96 CA74 D8BA > > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Mon Feb 09 14:52:18 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 09 Feb 2015 14:52:18 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YKphA-0004dw-GY; Mon, 09 Feb 2015 14:52:16 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YKph9-0004d5-7X for mirageos-devel@lists.xenproject.org; Mon, 09 Feb 2015 14:52:15 +0000 Received: from [85.158.143.35] by server-1.bemta-4.messagelabs.com id 1B/D1-03000-E99C8D45; Mon, 09 Feb 2015 14:52:14 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-6.tower-21.messagelabs.com!1423493533!12625533!1 X-Originating-IP: [5.153.225.51] X-SpamReason: No, hits=0.2 required=7.0 tests=RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20899 invoked from network); 9 Feb 2015 14:52:13 -0000 Received: from bark.recoil.org (HELO bark.recoil.org) (5.153.225.51) by server-6.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 9 Feb 2015 14:52:13 -0000 Received: from dhcp-172-17-152-63.eduroam.wireless.private.cam.ac.uk (global-1-26.nat.csx.cam.ac.uk [131.111.184.26]); by bark.recoil.org (OpenSMTPD) with ESMTPSA id dc1001b1; TLS version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO; Mon, 9 Feb 2015 14:52:13 +0000 (GMT) Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) From: Anil Madhavapeddy In-Reply-To: <8CEDB416-6238-4888-BA4B-B7305FDDE2D9@gazagnaire.org> Date: Mon, 9 Feb 2015 14:52:12 +0000 Message-Id: <9349273A-0BB4-40C4-BF06-4307085AA90C@recoil.org> References: <8CEDB416-6238-4888-BA4B-B7305FDDE2D9@gazagnaire.org> To: Thomas Gazagnaire X-Mailer: Apple Mail (2.2070.6) Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Irmin API newbie questions X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 9 Feb 2015, at 14:41, Thomas Gazagnaire wrote: > >> Finally, how do I get history? e.g. if I want to show users the recent >> changes to a document. I see a "slice" type, but it's not clear what I >> can do with it. > > Anil asked me the question recently, and I promise him to add the missing function in the "simple" API. For now on, the functions are well-hidden inside the private API: The History[1] functor gives you a "closure" function, which gives you a slice of the history graph. The functor needs a contents store (if S is of type Irmin.S, then S,Private.Contents) and a node store (S.Private.Node). But that's far too hard to use, I'll add an helper function in the API to get you a OCamlgraph graph of commits (and optionally tree and blobs) instead. One layer that would be very useful over this commit graph is some notion of diffs. I'd quite like to be able to describe a data structure in terms of patches, since that's quite often the reason why I'm traversing the history in the first place. If I just want to go back in time, I can stash relevant points in a tag and never need to walk the commit history. -anil _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Mon Feb 09 14:52:18 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 09 Feb 2015 14:52:18 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YKphA-0004dw-GY; Mon, 09 Feb 2015 14:52:16 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YKph9-0004d5-7X for mirageos-devel@lists.xenproject.org; Mon, 09 Feb 2015 14:52:15 +0000 Received: from [85.158.143.35] by server-1.bemta-4.messagelabs.com id 1B/D1-03000-E99C8D45; Mon, 09 Feb 2015 14:52:14 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-6.tower-21.messagelabs.com!1423493533!12625533!1 X-Originating-IP: [5.153.225.51] X-SpamReason: No, hits=0.2 required=7.0 tests=RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20899 invoked from network); 9 Feb 2015 14:52:13 -0000 Received: from bark.recoil.org (HELO bark.recoil.org) (5.153.225.51) by server-6.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 9 Feb 2015 14:52:13 -0000 Received: from dhcp-172-17-152-63.eduroam.wireless.private.cam.ac.uk (global-1-26.nat.csx.cam.ac.uk [131.111.184.26]); by bark.recoil.org (OpenSMTPD) with ESMTPSA id dc1001b1; TLS version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO; Mon, 9 Feb 2015 14:52:13 +0000 (GMT) Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) From: Anil Madhavapeddy In-Reply-To: <8CEDB416-6238-4888-BA4B-B7305FDDE2D9@gazagnaire.org> Date: Mon, 9 Feb 2015 14:52:12 +0000 Message-Id: <9349273A-0BB4-40C4-BF06-4307085AA90C@recoil.org> References: <8CEDB416-6238-4888-BA4B-B7305FDDE2D9@gazagnaire.org> To: Thomas Gazagnaire X-Mailer: Apple Mail (2.2070.6) Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Irmin API newbie questions X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 9 Feb 2015, at 14:41, Thomas Gazagnaire wrote: > >> Finally, how do I get history? e.g. if I want to show users the recent >> changes to a document. I see a "slice" type, but it's not clear what I >> can do with it. > > Anil asked me the question recently, and I promise him to add the missing function in the "simple" API. For now on, the functions are well-hidden inside the private API: The History[1] functor gives you a "closure" function, which gives you a slice of the history graph. The functor needs a contents store (if S is of type Irmin.S, then S,Private.Contents) and a node store (S.Private.Node). But that's far too hard to use, I'll add an helper function in the API to get you a OCamlgraph graph of commits (and optionally tree and blobs) instead. One layer that would be very useful over this commit graph is some notion of diffs. I'd quite like to be able to describe a data structure in terms of patches, since that's quite often the reason why I'm traversing the history in the first place. If I just want to go back in time, I can stash relevant points in a tag and never need to walk the commit history. -anil _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Mon Feb 09 16:18:54 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 09 Feb 2015 16:18:54 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YKr2u-0003ol-R7; Mon, 09 Feb 2015 16:18:48 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YKr2u-0003og-5I for mirageos-devel@lists.xenproject.org; Mon, 09 Feb 2015 16:18:48 +0000 Received: from [85.158.143.35] by server-1.bemta-4.messagelabs.com id F6/61-03000-7EDD8D45; Mon, 09 Feb 2015 16:18:47 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-7.tower-21.messagelabs.com!1423498726!12725380!1 X-Originating-IP: [74.125.82.179] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28964 invoked from network); 9 Feb 2015 16:18:46 -0000 Received: from mail-we0-f179.google.com (HELO mail-we0-f179.google.com) (74.125.82.179) by server-7.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 9 Feb 2015 16:18:46 -0000 Received: by mail-we0-f179.google.com with SMTP id u56so22451226wes.10 for ; Mon, 09 Feb 2015 08:18:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=wKb+boRTdVUzM4NiB50EB4P3QB27KmGR/6YyowJXLDw=; b=Wx6lerrZ7RQ/GF4unRZ1BHNA0mFrIqi4wOBsZL7sU3L/Yw4Fh7E3Su8lf+RS9r0QaN xHXNxXWelHfwovzr9mWIh6C7A3+jotTAne3wx6uBP1Th3AljrCPfOfB8a0AAmU4eaAUG WDfK5PtkqVvncvEF55p6bjopVEWrDNXeQkyf48vaUKM8HzTPAoxMu4BExjdG5y8Ra+CZ zPLLIyh2Zu1iD7ZBKezPi2fwwjTSledGBZowQfbM05Qf51B1ODhmXvdtUBsL0g+QOen/ XwAwnNqhlBvu1XZ7DBI/pAhcSNHA3wBRGHpGIoRF9lWPwzZWmv52TKxUa6UfuDfym+pt rcpw== X-Received: by 10.194.59.232 with SMTP id c8mr44487093wjr.76.1423498726410; Mon, 09 Feb 2015 08:18:46 -0800 (PST) Received: from piana.mac.cl.cam.ac.uk (piana.mac.cl.cam.ac.uk. [128.232.56.38]) by mx.google.com with ESMTPSA id l6sm16968818wjx.33.2015.02.09.08.18.45 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 09 Feb 2015 08:18:45 -0800 (PST) Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\)) From: Thomas Gazagnaire In-Reply-To: <9349273A-0BB4-40C4-BF06-4307085AA90C@recoil.org> Date: Mon, 9 Feb 2015 16:18:44 +0000 Message-Id: References: <8CEDB416-6238-4888-BA4B-B7305FDDE2D9@gazagnaire.org> <9349273A-0BB4-40C4-BF06-4307085AA90C@recoil.org> To: Anil Madhavapeddy X-Mailer: Apple Mail (2.1993) Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Irmin API newbie questions X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org >>> Finally, how do I get history? e.g. if I want to show users the recent >>> changes to a document. I see a "slice" type, but it's not clear what I >>> can do with it. >> >> Anil asked me the question recently, and I promise him to add the missing function in the "simple" API. For now on, the functions are well-hidden inside the private API: The History[1] functor gives you a "closure" function, which gives you a slice of the history graph. The functor needs a contents store (if S is of type Irmin.S, then S,Private.Contents) and a node store (S.Private.Node). But that's far too hard to use, I'll add an helper function in the API to get you a OCamlgraph graph of commits (and optionally tree and blobs) instead. > > One layer that would be very useful over this commit graph is some notion of > diffs. I'd quite like to be able to describe a data structure in terms of > patches, since that's quite often the reason why I'm traversing the history > in the first place. If I just want to go back in time, I can stash relevant > points in a tag and never need to walk the commit history. Good idea, I'll try to see if I can add a diff on the graph edges (via a user-provided function to compute diffs) Thomas _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Mon Feb 09 16:18:54 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 09 Feb 2015 16:18:54 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YKr2u-0003ol-R7; Mon, 09 Feb 2015 16:18:48 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YKr2u-0003og-5I for mirageos-devel@lists.xenproject.org; Mon, 09 Feb 2015 16:18:48 +0000 Received: from [85.158.143.35] by server-1.bemta-4.messagelabs.com id F6/61-03000-7EDD8D45; Mon, 09 Feb 2015 16:18:47 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-7.tower-21.messagelabs.com!1423498726!12725380!1 X-Originating-IP: [74.125.82.179] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28964 invoked from network); 9 Feb 2015 16:18:46 -0000 Received: from mail-we0-f179.google.com (HELO mail-we0-f179.google.com) (74.125.82.179) by server-7.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 9 Feb 2015 16:18:46 -0000 Received: by mail-we0-f179.google.com with SMTP id u56so22451226wes.10 for ; Mon, 09 Feb 2015 08:18:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=wKb+boRTdVUzM4NiB50EB4P3QB27KmGR/6YyowJXLDw=; b=Wx6lerrZ7RQ/GF4unRZ1BHNA0mFrIqi4wOBsZL7sU3L/Yw4Fh7E3Su8lf+RS9r0QaN xHXNxXWelHfwovzr9mWIh6C7A3+jotTAne3wx6uBP1Th3AljrCPfOfB8a0AAmU4eaAUG WDfK5PtkqVvncvEF55p6bjopVEWrDNXeQkyf48vaUKM8HzTPAoxMu4BExjdG5y8Ra+CZ zPLLIyh2Zu1iD7ZBKezPi2fwwjTSledGBZowQfbM05Qf51B1ODhmXvdtUBsL0g+QOen/ XwAwnNqhlBvu1XZ7DBI/pAhcSNHA3wBRGHpGIoRF9lWPwzZWmv52TKxUa6UfuDfym+pt rcpw== X-Received: by 10.194.59.232 with SMTP id c8mr44487093wjr.76.1423498726410; Mon, 09 Feb 2015 08:18:46 -0800 (PST) Received: from piana.mac.cl.cam.ac.uk (piana.mac.cl.cam.ac.uk. [128.232.56.38]) by mx.google.com with ESMTPSA id l6sm16968818wjx.33.2015.02.09.08.18.45 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 09 Feb 2015 08:18:45 -0800 (PST) Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\)) From: Thomas Gazagnaire In-Reply-To: <9349273A-0BB4-40C4-BF06-4307085AA90C@recoil.org> Date: Mon, 9 Feb 2015 16:18:44 +0000 Message-Id: References: <8CEDB416-6238-4888-BA4B-B7305FDDE2D9@gazagnaire.org> <9349273A-0BB4-40C4-BF06-4307085AA90C@recoil.org> To: Anil Madhavapeddy X-Mailer: Apple Mail (2.1993) Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Irmin API newbie questions X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org >>> Finally, how do I get history? e.g. if I want to show users the recent >>> changes to a document. I see a "slice" type, but it's not clear what I >>> can do with it. >> >> Anil asked me the question recently, and I promise him to add the missing function in the "simple" API. For now on, the functions are well-hidden inside the private API: The History[1] functor gives you a "closure" function, which gives you a slice of the history graph. The functor needs a contents store (if S is of type Irmin.S, then S,Private.Contents) and a node store (S.Private.Node). But that's far too hard to use, I'll add an helper function in the API to get you a OCamlgraph graph of commits (and optionally tree and blobs) instead. > > One layer that would be very useful over this commit graph is some notion of > diffs. I'd quite like to be able to describe a data structure in terms of > patches, since that's quite often the reason why I'm traversing the history > in the first place. If I just want to go back in time, I can stash relevant > points in a tag and never need to walk the commit history. Good idea, I'll try to see if I can add a diff on the graph edges (via a user-provided function to compute diffs) Thomas _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Mon Feb 09 16:39:41 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 09 Feb 2015 16:39:41 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YKrN7-0005pq-3B; Mon, 09 Feb 2015 16:39:41 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YKrN5-0005pk-Ul for mirageos-devel@lists.xenproject.org; Mon, 09 Feb 2015 16:39:40 +0000 Received: from [193.109.254.147] by server-9.bemta-14.messagelabs.com id BC/2B-02777-BC2E8D45; Mon, 09 Feb 2015 16:39:39 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-11.tower-27.messagelabs.com!1423499978!8974994!1 X-Originating-IP: [74.125.82.45] X-SpamReason: No, hits=0.3 required=7.0 tests=MAILTO_TO_SPAM_ADDR X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29218 invoked from network); 9 Feb 2015 16:39:38 -0000 Received: from mail-wg0-f45.google.com (HELO mail-wg0-f45.google.com) (74.125.82.45) by server-11.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 9 Feb 2015 16:39:38 -0000 Received: by mail-wg0-f45.google.com with SMTP id x12so27881327wgg.4 for ; Mon, 09 Feb 2015 08:39:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=F8JHRjkQbF5b80r3UZB4D3MsgmpJDkwEyfnYTgQdybM=; b=bc2iogXwhKM0D+NhQRDehFCii+2ApQHnSjaLgUjZt2t7jUkstDggrcXwr2AlghegNP hcJXtxkSM54u2VcI6aqBFphE5nFeVBdHWkgH+l3Ss0N9FUV3El0KNF9YUHLbv2696xaK CYlV7wQvN9Ok97EJKUq5ZhOhPSkS0+4lX/dQ0ve+OqOsS9h56HtY9aa5bDNfAJI4HNIw qy2T0q3xLJRtOoXUh+/8shUvDj+nw67snygUwua52pPeKoGgTzq+7LYWznot7Y5sUt/j pARsUQ7zUS0tr29bB0Nr2uKxLI69YQdGmN7XRfk2U6k7+TYbVLxAuLNgIIdSI9loi3Lo wosw== X-Received: by 10.180.95.97 with SMTP id dj1mr27933114wib.43.1423499976876; Mon, 09 Feb 2015 08:39:36 -0800 (PST) Received: from [192.168.0.8] (97e5a0c2.skybroadband.com. [151.229.160.194]) by mx.google.com with ESMTPSA id r7sm17054443wjw.23.2015.02.09.08.39.35 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 09 Feb 2015 08:39:35 -0800 (PST) Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) From: Lars Kurth In-Reply-To: <2A47AAA1-5915-4715-B9A7-6ADC1375110F@cam.ac.uk> Date: Mon, 9 Feb 2015 16:39:35 +0000 Message-Id: <522D4B73-374E-4B86-A771-769FBB31AD21@gmail.com> References: <2B0C0681-8266-420A-A74B-1BCCFDCD3F23@gmail.com> <0A2884DD-0391-4E50-A68B-71D8A8A68296@cam.ac.uk> <707E3CE1-4C4D-4F3F-9BB1-F5D31D8668EB@gmail.com> <2A47AAA1-5915-4715-B9A7-6ADC1375110F@cam.ac.uk> To: Amir Chaudhry X-Mailer: Apple Mail (2.2070.6) Cc: mirageos-devel , Anil Madhavapeddy Subject: Re: [MirageOS-devel] MirageOS and GSoC (was: Re: IMPORTANT: GSoC 2015 page created - Need to confirm old projects, create/review new ones and fix projects with issues before Feb 22nd) X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org > On 9 Feb 2015, at 13:01, Amir Chaudhry wrote: > > If it works for you, then that's fine with me. I've made an edit to the Xen GSoC Project page (with the above suggestion) and will copy back the existing three projects over to the Pioneer's page. > > Then it's just about collating more projects. > > AC Works for me Lars _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Mon Feb 09 16:39:41 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 09 Feb 2015 16:39:41 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YKrN7-0005pq-3B; Mon, 09 Feb 2015 16:39:41 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YKrN5-0005pk-Ul for mirageos-devel@lists.xenproject.org; Mon, 09 Feb 2015 16:39:40 +0000 Received: from [193.109.254.147] by server-9.bemta-14.messagelabs.com id BC/2B-02777-BC2E8D45; Mon, 09 Feb 2015 16:39:39 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-11.tower-27.messagelabs.com!1423499978!8974994!1 X-Originating-IP: [74.125.82.45] X-SpamReason: No, hits=0.3 required=7.0 tests=MAILTO_TO_SPAM_ADDR X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29218 invoked from network); 9 Feb 2015 16:39:38 -0000 Received: from mail-wg0-f45.google.com (HELO mail-wg0-f45.google.com) (74.125.82.45) by server-11.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 9 Feb 2015 16:39:38 -0000 Received: by mail-wg0-f45.google.com with SMTP id x12so27881327wgg.4 for ; Mon, 09 Feb 2015 08:39:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=F8JHRjkQbF5b80r3UZB4D3MsgmpJDkwEyfnYTgQdybM=; b=bc2iogXwhKM0D+NhQRDehFCii+2ApQHnSjaLgUjZt2t7jUkstDggrcXwr2AlghegNP hcJXtxkSM54u2VcI6aqBFphE5nFeVBdHWkgH+l3Ss0N9FUV3El0KNF9YUHLbv2696xaK CYlV7wQvN9Ok97EJKUq5ZhOhPSkS0+4lX/dQ0ve+OqOsS9h56HtY9aa5bDNfAJI4HNIw qy2T0q3xLJRtOoXUh+/8shUvDj+nw67snygUwua52pPeKoGgTzq+7LYWznot7Y5sUt/j pARsUQ7zUS0tr29bB0Nr2uKxLI69YQdGmN7XRfk2U6k7+TYbVLxAuLNgIIdSI9loi3Lo wosw== X-Received: by 10.180.95.97 with SMTP id dj1mr27933114wib.43.1423499976876; Mon, 09 Feb 2015 08:39:36 -0800 (PST) Received: from [192.168.0.8] (97e5a0c2.skybroadband.com. [151.229.160.194]) by mx.google.com with ESMTPSA id r7sm17054443wjw.23.2015.02.09.08.39.35 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 09 Feb 2015 08:39:35 -0800 (PST) Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) From: Lars Kurth In-Reply-To: <2A47AAA1-5915-4715-B9A7-6ADC1375110F@cam.ac.uk> Date: Mon, 9 Feb 2015 16:39:35 +0000 Message-Id: <522D4B73-374E-4B86-A771-769FBB31AD21@gmail.com> References: <2B0C0681-8266-420A-A74B-1BCCFDCD3F23@gmail.com> <0A2884DD-0391-4E50-A68B-71D8A8A68296@cam.ac.uk> <707E3CE1-4C4D-4F3F-9BB1-F5D31D8668EB@gmail.com> <2A47AAA1-5915-4715-B9A7-6ADC1375110F@cam.ac.uk> To: Amir Chaudhry X-Mailer: Apple Mail (2.2070.6) Cc: mirageos-devel , Anil Madhavapeddy Subject: Re: [MirageOS-devel] MirageOS and GSoC (was: Re: IMPORTANT: GSoC 2015 page created - Need to confirm old projects, create/review new ones and fix projects with issues before Feb 22nd) X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org > On 9 Feb 2015, at 13:01, Amir Chaudhry wrote: > > If it works for you, then that's fine with me. I've made an edit to the Xen GSoC Project page (with the above suggestion) and will copy back the existing three projects over to the Pioneer's page. > > Then it's just about collating more projects. > > AC Works for me Lars _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Tue Feb 10 14:12:13 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 10 Feb 2015 14:12:13 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YLBXs-0006Sb-76; Tue, 10 Feb 2015 14:12:08 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YLBXr-0006SW-48 for mirageos-devel@lists.xenproject.org; Tue, 10 Feb 2015 14:12:07 +0000 Received: from [85.158.143.35] by server-3.bemta-4.messagelabs.com id 78/22-02754-6B11AD45; Tue, 10 Feb 2015 14:12:06 +0000 X-Env-Sender: amirmc@gmail.com X-Msg-Ref: server-7.tower-21.messagelabs.com!1423577524!12960180!1 X-Originating-IP: [74.125.82.173] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5381 invoked from network); 10 Feb 2015 14:12:04 -0000 Received: from mail-we0-f173.google.com (HELO mail-we0-f173.google.com) (74.125.82.173) by server-7.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 10 Feb 2015 14:12:04 -0000 Received: by mail-we0-f173.google.com with SMTP id w55so22324848wes.4 for ; Tue, 10 Feb 2015 06:12:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:content-type:content-transfer-encoding:subject:message-id:date :to:mime-version; bh=LrIi8B6oXsO3c1Np3tbx+nselEeyUEWaby75ekzq5/g=; b=UdItalPSJ3uQrV2857xUEWkXXKVmqS62mA2wyltFKYFFpQmchzgQhXETS8bIWohfJG 7Q6ZpfSP5S8Zo7h7YDEGATnf025QSI3jANI+abRlMEtIGKYzXN0fKIOPt8u0WbKLA9Do EMEsYR2M34h9cpoP1zwNBnjDVfj+OWHEQDgaH9a7cgblnzAqJ4FLBgkQVg75Bu73Wr6k uU4wafEEhlbXcu3HwwTrWnjY614TP88m6ZmdKeXML02YsB07Gl0L7YIZ+U0+6TehnWhh vfV/LvE2aums/bRUU3BS4h8NNsqdhsIl4sgKhe/EDaVMZ1IjmhEhOiohoaeyLjFDuAyF BPcg== X-Received: by 10.180.74.206 with SMTP id w14mr3900986wiv.71.1423577522210; Tue, 10 Feb 2015 06:12:02 -0800 (PST) Received: from dhcp-172-17-153-215.eduroam.wireless.private.cam.ac.uk (global-1-26.nat.csx.cam.ac.uk. [131.111.184.26]) by mx.google.com with ESMTPSA id n10sm14509570wic.11.2015.02.10.06.12.00 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 10 Feb 2015 06:12:01 -0800 (PST) From: Amir Chaudhry Message-Id: <79441473-AA54-45B0-9D7C-9F0D1E61068C@gmail.com> Date: Tue, 10 Feb 2015 14:12:00 +0000 To: mirageos-devel Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) X-Mailer: Apple Mail (2.1510) Subject: [MirageOS-devel] Mirage fortnightly call - Wednesday 11th at 4pm GMT X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: quoted-printable Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org Hi folks, The next Mirage call will take place this Wednesday afternoon at 4pm GMT an= d is open to all. Notes from last time are delayed but they'll be up soon! = The agenda is currently as follows: =95 Quality =95 Error Handling RFC =95 TLS merge progress =95 FOSDEM demo =95 GSoC Projects If you have things to add/edit, please do so at https://github.com/mirage/m= irage-www/wiki/Call-Agenda GoToMeeting details are below but if there are any hiccups/delays then I'll= switch to a public Google Hangout. If that happens, I'll post the link he= re and also in the IRC channel (#mirage on freenode). Join us at 4pm GMT on Wednesday! 1. Please join my meeting. https://www1.gotomeeting.com/join/591890401 Dial in numbers (ask if you need a specific country): United Kingdom: +44 (0) 20 3657 6778 United States: +1 (213) 493-0014 Access Code: 591-890-401 Audio PIN: Shown after joining the meeting Best wishes, Amir _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Tue Feb 10 14:12:13 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 10 Feb 2015 14:12:13 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YLBXs-0006Sb-76; Tue, 10 Feb 2015 14:12:08 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YLBXr-0006SW-48 for mirageos-devel@lists.xenproject.org; Tue, 10 Feb 2015 14:12:07 +0000 Received: from [85.158.143.35] by server-3.bemta-4.messagelabs.com id 78/22-02754-6B11AD45; Tue, 10 Feb 2015 14:12:06 +0000 X-Env-Sender: amirmc@gmail.com X-Msg-Ref: server-7.tower-21.messagelabs.com!1423577524!12960180!1 X-Originating-IP: [74.125.82.173] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5381 invoked from network); 10 Feb 2015 14:12:04 -0000 Received: from mail-we0-f173.google.com (HELO mail-we0-f173.google.com) (74.125.82.173) by server-7.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 10 Feb 2015 14:12:04 -0000 Received: by mail-we0-f173.google.com with SMTP id w55so22324848wes.4 for ; Tue, 10 Feb 2015 06:12:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:content-type:content-transfer-encoding:subject:message-id:date :to:mime-version; bh=LrIi8B6oXsO3c1Np3tbx+nselEeyUEWaby75ekzq5/g=; b=UdItalPSJ3uQrV2857xUEWkXXKVmqS62mA2wyltFKYFFpQmchzgQhXETS8bIWohfJG 7Q6ZpfSP5S8Zo7h7YDEGATnf025QSI3jANI+abRlMEtIGKYzXN0fKIOPt8u0WbKLA9Do EMEsYR2M34h9cpoP1zwNBnjDVfj+OWHEQDgaH9a7cgblnzAqJ4FLBgkQVg75Bu73Wr6k uU4wafEEhlbXcu3HwwTrWnjY614TP88m6ZmdKeXML02YsB07Gl0L7YIZ+U0+6TehnWhh vfV/LvE2aums/bRUU3BS4h8NNsqdhsIl4sgKhe/EDaVMZ1IjmhEhOiohoaeyLjFDuAyF BPcg== X-Received: by 10.180.74.206 with SMTP id w14mr3900986wiv.71.1423577522210; Tue, 10 Feb 2015 06:12:02 -0800 (PST) Received: from dhcp-172-17-153-215.eduroam.wireless.private.cam.ac.uk (global-1-26.nat.csx.cam.ac.uk. [131.111.184.26]) by mx.google.com with ESMTPSA id n10sm14509570wic.11.2015.02.10.06.12.00 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 10 Feb 2015 06:12:01 -0800 (PST) From: Amir Chaudhry Message-Id: <79441473-AA54-45B0-9D7C-9F0D1E61068C@gmail.com> Date: Tue, 10 Feb 2015 14:12:00 +0000 To: mirageos-devel Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) X-Mailer: Apple Mail (2.1510) Subject: [MirageOS-devel] Mirage fortnightly call - Wednesday 11th at 4pm GMT X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: quoted-printable Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org Hi folks, The next Mirage call will take place this Wednesday afternoon at 4pm GMT an= d is open to all. Notes from last time are delayed but they'll be up soon! = The agenda is currently as follows: =95 Quality =95 Error Handling RFC =95 TLS merge progress =95 FOSDEM demo =95 GSoC Projects If you have things to add/edit, please do so at https://github.com/mirage/m= irage-www/wiki/Call-Agenda GoToMeeting details are below but if there are any hiccups/delays then I'll= switch to a public Google Hangout. If that happens, I'll post the link he= re and also in the IRC channel (#mirage on freenode). Join us at 4pm GMT on Wednesday! 1. Please join my meeting. https://www1.gotomeeting.com/join/591890401 Dial in numbers (ask if you need a specific country): United Kingdom: +44 (0) 20 3657 6778 United States: +1 (213) 493-0014 Access Code: 591-890-401 Audio PIN: Shown after joining the meeting Best wishes, Amir _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Tue Feb 10 14:45:48 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 10 Feb 2015 14:45:48 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YLC4Q-0000Up-SW; Tue, 10 Feb 2015 14:45:46 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YLC4P-0000Uk-UY for mirageos-devel@lists.xenproject.org; Tue, 10 Feb 2015 14:45:46 +0000 Received: from [85.158.143.35] by server-1.bemta-4.messagelabs.com id 65/E6-03000-9991AD45; Tue, 10 Feb 2015 14:45:45 +0000 X-Env-Sender: talex5@gmail.com X-Msg-Ref: server-16.tower-21.messagelabs.com!1423579543!9518108!1 X-Originating-IP: [209.85.217.182] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5699 invoked from network); 10 Feb 2015 14:45:44 -0000 Received: from mail-lb0-f182.google.com (HELO mail-lb0-f182.google.com) (209.85.217.182) by server-16.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 10 Feb 2015 14:45:44 -0000 Received: by mail-lb0-f182.google.com with SMTP id l4so36547834lbv.13 for ; Tue, 10 Feb 2015 06:45:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=WNz1NqcS25IqSyswfN/HeLJVtZSm6iVZnvZ22hq73Po=; b=a8MXYuSoxlFj5V2EA4VQ490mtvuuaR3r/cRTlOkIm1jRpYn9lJ2kQz7Us7UdfzYJS2 mP3q1Gtr9xdl0w7hm6g7uWz0SEZI7VCknM6bkLi3pPxMQgVvYsQfcIZO/ya6Cv8aALwd uwZ++xNFkD/co5lMa+vy+VCFe6D16IT+B1An6pyxo69WIrldGCcrPbQEvQkT6ZQfii4P IJJ5jhazmR3WzUCFt38/bQH9IXocaCzIIpI6N5OPjch/MJamHfyEAbOBjjG7nlxObuo2 tE6BHi9N9TNQixJK0Y9OQMmLYGb36Etw1w4GKh1SVLXjPBUIfAMaoCQ5Wcuyt5ESTN3J Uf3g== MIME-Version: 1.0 X-Received: by 10.112.147.66 with SMTP id ti2mr23442908lbb.124.1423579543616; Tue, 10 Feb 2015 06:45:43 -0800 (PST) Received: by 10.25.207.206 with HTTP; Tue, 10 Feb 2015 06:45:43 -0800 (PST) In-Reply-To: <8CEDB416-6238-4888-BA4B-B7305FDDE2D9@gazagnaire.org> References: <8CEDB416-6238-4888-BA4B-B7305FDDE2D9@gazagnaire.org> Date: Tue, 10 Feb 2015 14:45:43 +0000 Message-ID: From: Thomas Leonard To: Thomas Gazagnaire Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Irmin API newbie questions X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 9 February 2015 at 14:41, Thomas Gazagnaire wrote: > Hi Thomas, > >> (BTW, I think it might be useful to add the equivalent git command >> next to functions in the documentation, since most people will >> understand that already) > > ack, I'll do this. > >> The BASIC docs are missing >> (https://mirage.github.io/irmin/Irmin.BASIC.html), but the code shows: >> >> type ('a, 'b) basic = (module BASIC with type key = 'a and type value = 'b) >> >> It seems that using Irmin.Contents.String gets me "key = string list", >> but "step" remains abstract. How do I use cons, decons, etc? > > Why do you need to use cons and decons? Normally you should just need to use the usual list operators (ie. (::) for cons and pattern-matching for decons). If you have a use-case where this is not enough, please share it! It's possible that I forgot to export a type constraint somewhere. When walking the tree it's useful to get the last component with rdecons, since there's no built-in function for this. Easy enough to work around, of course. It's actually a bit strange that "list" returns a "key list" rather than a "step list" (i.e. it returns full paths). The docs say "list t k list the sub-paths of the path k in t", but it looks like it's just the immediate children. Returning a step would make that clear, if so. >> If I have a RW store, I can watch a key: >> >> val watch : t -> key -> value option Lwt_stream.t >> >> Presumably, I also need to take care to stop watching it when I'm >> done, otherwise the stream will grow without limit, right? I guess >> there should be an unwatch, or maybe this should be a React signal or >> something. > > Yes the watch API still needs some work. It's working-ish enough to demo small examples (for instance you can run some of the examples and connect to http://127.0.0.1:8080/graph to see a nice animated graph of the store), but as you noticed there is no GC of ressources, maybe some leaks and the behaviour under load is not satisfactory (see issue https://github.com/mirage/irmin/issues/124). > >> I got a bit confused when I reached the BC page: >> >> https://mirage.github.io/irmin/Irmin.BC.html >> >> It uses 'tag' to mean a pointer to a commit that is updates on each >> operation (i.e. what Git would call a 'branch'). I realise that tags >> and branches are the same thing internally, but 'branch' seems to >> capture better what Irmin is using them for ("The tag value is updated >> every time the store is updated, so every handle connected or which >> will be connected to the same tag will see the changes."). [ BTW, >> what's a "handle"? ] > > The documentation is not totally clear here, you're right. You have two ways to identify a branch: either by name or by hash. In Irmin terminology, a branch name is a "tag". A commit hash is a "head". > >> val update_tag : t -> tag -> unit Lwt.t >> update_tag t tag updates t's current branch with the contents of the >> branch named tag. >> >> What does "update" mean here? Is this "git reset --hard tag"? A merge? >> A "--ff-only" merge? > > `update_tag` is similar to `git reset --hard `. merge_tag is similar to `git merge `. I've tried to keep the update/merge duality in most of the places (you can update/merge a head, a view, an other branch). Might be worth mentioning that this may cause data-loss then (I don't think that's clear from "update"). >> My mental model of Git is that the store is a DAG and I can append to >> any branch. e.g. we have: >> >> git commit-tree [(-p )...] < changelog >> >> If I'm understanding the Irmin API correctly, each "store" >> (repository? branch?) has a current "tag" (branch) and I need to set >> the tag I want to work on, e.g. >> >> val switch : Store.t -> tag -> unit Lwt.t > > The simplest way to initialise a branch using a tag is to use `Irmin.of_tag ... `. If you want to create a branch in a "detached" mode, use `Irmin.of_head ... `. But yes, you can use switch to switch to another named branch. > >> If I want to work on another branch without changing the current >> branch for other users, I should "clone" the store: >> >> val clone_force : ('a -> Irmin.task) -> t -> tag -> ('a -> t) Lwt.t >> >> But, this is not a "git clone", it's like "git branch tag" - a new >> branch I can work on without affecting the repository's default >> branch. It seems strange that Irmin has a mutable "current branch" at >> all - this seems like a UI concept that's only needed for command-line >> use (to save typing). > > Irmin has a concept of default branch (ie. "master") which is used when you use "Irmin.create". I choose that because the simplest use-case is to use Irmin as a normal k/v store, without having to worry about branches and such. OK, I think my confusion here is because (in my mind) there are two separate concepts here: a repository is a collection of branches and a branch head is a k/v store. But these are both combined into a single "store" type. >> A "head" is defined as "a given store revision" (i.e. what Git would >> call a commit). It wasn't clear to me at first whether a head was a >> commit or an anonymous branch. e.g. > > A head is a commit hash. You can use a head with Irmin.of_head to create an anonymous branch. I agree that the documentation is not very clear on that. > >> val rename_tag : t -> tag -> [ `Duplicated_tag | `Ok ] Lwt.t >> Change the current tag name. Fail if a tag with the same name already >> exists. The head is unchanged. >> >> "The head is unchanged" suggests that heads might change in other >> cases. Looking at the code, I see a "type head = Commit.key" in one >> place, so I guess they're (usually?) commits. Does "head" here mean >> "the default branch"? > > I'll make another pass on that part of the documentation to try to make all of these concepts clearer. I'll try to relate the API functions to Git command-line arguments, although I'm not sure the Git command-line is a model of clarity as well: `git reset --hard` is very different from `git reset --soft` for instance, and there are no direct notion on index file in Irmin (although the views can be seen as a kind of staging area). > >> Finally, how do I get history? e.g. if I want to show users the recent >> changes to a document. I see a "slice" type, but it's not clear what I >> can do with it. > > Anil asked me the question recently, and I promise him to add the missing function in the "simple" API. For now on, the functions are well-hidden inside the private API: The History[1] functor gives you a "closure" function, which gives you a slice of the history graph. The functor needs a contents store (if S is of type Irmin.S, then S,Private.Contents) and a node store (S.Private.Node). But that's far too hard to use, I'll add an helper function in the API to get you a OCamlgraph graph of commits (and optionally tree and blobs) instead. > > Thanks for that very helpful report! I hope it makes things a little bit clearer. Yes, much clearer, thanks! > Thomas > > [1] http://mirage.github.io/irmin/Irmin.Private.Commit.History.html > > >> >> >> Thanks! >> >> >> -- >> Dr Thomas Leonard http://0install.net/ >> GPG: 9242 9807 C985 3C07 44A6 8B9A AE07 8280 59A5 3CC1 >> GPG: DA98 25AE CAD0 8975 7CDA BD8E 0713 3F96 CA74 D8BA >> >> _______________________________________________ >> MirageOS-devel mailing list >> MirageOS-devel@lists.xenproject.org >> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > -- Dr Thomas Leonard http://0install.net/ GPG: 9242 9807 C985 3C07 44A6 8B9A AE07 8280 59A5 3CC1 GPG: DA98 25AE CAD0 8975 7CDA BD8E 0713 3F96 CA74 D8BA _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Tue Feb 10 14:45:48 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 10 Feb 2015 14:45:48 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YLC4Q-0000Up-SW; Tue, 10 Feb 2015 14:45:46 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YLC4P-0000Uk-UY for mirageos-devel@lists.xenproject.org; Tue, 10 Feb 2015 14:45:46 +0000 Received: from [85.158.143.35] by server-1.bemta-4.messagelabs.com id 65/E6-03000-9991AD45; Tue, 10 Feb 2015 14:45:45 +0000 X-Env-Sender: talex5@gmail.com X-Msg-Ref: server-16.tower-21.messagelabs.com!1423579543!9518108!1 X-Originating-IP: [209.85.217.182] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5699 invoked from network); 10 Feb 2015 14:45:44 -0000 Received: from mail-lb0-f182.google.com (HELO mail-lb0-f182.google.com) (209.85.217.182) by server-16.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 10 Feb 2015 14:45:44 -0000 Received: by mail-lb0-f182.google.com with SMTP id l4so36547834lbv.13 for ; Tue, 10 Feb 2015 06:45:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=WNz1NqcS25IqSyswfN/HeLJVtZSm6iVZnvZ22hq73Po=; b=a8MXYuSoxlFj5V2EA4VQ490mtvuuaR3r/cRTlOkIm1jRpYn9lJ2kQz7Us7UdfzYJS2 mP3q1Gtr9xdl0w7hm6g7uWz0SEZI7VCknM6bkLi3pPxMQgVvYsQfcIZO/ya6Cv8aALwd uwZ++xNFkD/co5lMa+vy+VCFe6D16IT+B1An6pyxo69WIrldGCcrPbQEvQkT6ZQfii4P IJJ5jhazmR3WzUCFt38/bQH9IXocaCzIIpI6N5OPjch/MJamHfyEAbOBjjG7nlxObuo2 tE6BHi9N9TNQixJK0Y9OQMmLYGb36Etw1w4GKh1SVLXjPBUIfAMaoCQ5Wcuyt5ESTN3J Uf3g== MIME-Version: 1.0 X-Received: by 10.112.147.66 with SMTP id ti2mr23442908lbb.124.1423579543616; Tue, 10 Feb 2015 06:45:43 -0800 (PST) Received: by 10.25.207.206 with HTTP; Tue, 10 Feb 2015 06:45:43 -0800 (PST) In-Reply-To: <8CEDB416-6238-4888-BA4B-B7305FDDE2D9@gazagnaire.org> References: <8CEDB416-6238-4888-BA4B-B7305FDDE2D9@gazagnaire.org> Date: Tue, 10 Feb 2015 14:45:43 +0000 Message-ID: From: Thomas Leonard To: Thomas Gazagnaire Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Irmin API newbie questions X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 9 February 2015 at 14:41, Thomas Gazagnaire wrote: > Hi Thomas, > >> (BTW, I think it might be useful to add the equivalent git command >> next to functions in the documentation, since most people will >> understand that already) > > ack, I'll do this. > >> The BASIC docs are missing >> (https://mirage.github.io/irmin/Irmin.BASIC.html), but the code shows: >> >> type ('a, 'b) basic = (module BASIC with type key = 'a and type value = 'b) >> >> It seems that using Irmin.Contents.String gets me "key = string list", >> but "step" remains abstract. How do I use cons, decons, etc? > > Why do you need to use cons and decons? Normally you should just need to use the usual list operators (ie. (::) for cons and pattern-matching for decons). If you have a use-case where this is not enough, please share it! It's possible that I forgot to export a type constraint somewhere. When walking the tree it's useful to get the last component with rdecons, since there's no built-in function for this. Easy enough to work around, of course. It's actually a bit strange that "list" returns a "key list" rather than a "step list" (i.e. it returns full paths). The docs say "list t k list the sub-paths of the path k in t", but it looks like it's just the immediate children. Returning a step would make that clear, if so. >> If I have a RW store, I can watch a key: >> >> val watch : t -> key -> value option Lwt_stream.t >> >> Presumably, I also need to take care to stop watching it when I'm >> done, otherwise the stream will grow without limit, right? I guess >> there should be an unwatch, or maybe this should be a React signal or >> something. > > Yes the watch API still needs some work. It's working-ish enough to demo small examples (for instance you can run some of the examples and connect to http://127.0.0.1:8080/graph to see a nice animated graph of the store), but as you noticed there is no GC of ressources, maybe some leaks and the behaviour under load is not satisfactory (see issue https://github.com/mirage/irmin/issues/124). > >> I got a bit confused when I reached the BC page: >> >> https://mirage.github.io/irmin/Irmin.BC.html >> >> It uses 'tag' to mean a pointer to a commit that is updates on each >> operation (i.e. what Git would call a 'branch'). I realise that tags >> and branches are the same thing internally, but 'branch' seems to >> capture better what Irmin is using them for ("The tag value is updated >> every time the store is updated, so every handle connected or which >> will be connected to the same tag will see the changes."). [ BTW, >> what's a "handle"? ] > > The documentation is not totally clear here, you're right. You have two ways to identify a branch: either by name or by hash. In Irmin terminology, a branch name is a "tag". A commit hash is a "head". > >> val update_tag : t -> tag -> unit Lwt.t >> update_tag t tag updates t's current branch with the contents of the >> branch named tag. >> >> What does "update" mean here? Is this "git reset --hard tag"? A merge? >> A "--ff-only" merge? > > `update_tag` is similar to `git reset --hard `. merge_tag is similar to `git merge `. I've tried to keep the update/merge duality in most of the places (you can update/merge a head, a view, an other branch). Might be worth mentioning that this may cause data-loss then (I don't think that's clear from "update"). >> My mental model of Git is that the store is a DAG and I can append to >> any branch. e.g. we have: >> >> git commit-tree [(-p )...] < changelog >> >> If I'm understanding the Irmin API correctly, each "store" >> (repository? branch?) has a current "tag" (branch) and I need to set >> the tag I want to work on, e.g. >> >> val switch : Store.t -> tag -> unit Lwt.t > > The simplest way to initialise a branch using a tag is to use `Irmin.of_tag ... `. If you want to create a branch in a "detached" mode, use `Irmin.of_head ... `. But yes, you can use switch to switch to another named branch. > >> If I want to work on another branch without changing the current >> branch for other users, I should "clone" the store: >> >> val clone_force : ('a -> Irmin.task) -> t -> tag -> ('a -> t) Lwt.t >> >> But, this is not a "git clone", it's like "git branch tag" - a new >> branch I can work on without affecting the repository's default >> branch. It seems strange that Irmin has a mutable "current branch" at >> all - this seems like a UI concept that's only needed for command-line >> use (to save typing). > > Irmin has a concept of default branch (ie. "master") which is used when you use "Irmin.create". I choose that because the simplest use-case is to use Irmin as a normal k/v store, without having to worry about branches and such. OK, I think my confusion here is because (in my mind) there are two separate concepts here: a repository is a collection of branches and a branch head is a k/v store. But these are both combined into a single "store" type. >> A "head" is defined as "a given store revision" (i.e. what Git would >> call a commit). It wasn't clear to me at first whether a head was a >> commit or an anonymous branch. e.g. > > A head is a commit hash. You can use a head with Irmin.of_head to create an anonymous branch. I agree that the documentation is not very clear on that. > >> val rename_tag : t -> tag -> [ `Duplicated_tag | `Ok ] Lwt.t >> Change the current tag name. Fail if a tag with the same name already >> exists. The head is unchanged. >> >> "The head is unchanged" suggests that heads might change in other >> cases. Looking at the code, I see a "type head = Commit.key" in one >> place, so I guess they're (usually?) commits. Does "head" here mean >> "the default branch"? > > I'll make another pass on that part of the documentation to try to make all of these concepts clearer. I'll try to relate the API functions to Git command-line arguments, although I'm not sure the Git command-line is a model of clarity as well: `git reset --hard` is very different from `git reset --soft` for instance, and there are no direct notion on index file in Irmin (although the views can be seen as a kind of staging area). > >> Finally, how do I get history? e.g. if I want to show users the recent >> changes to a document. I see a "slice" type, but it's not clear what I >> can do with it. > > Anil asked me the question recently, and I promise him to add the missing function in the "simple" API. For now on, the functions are well-hidden inside the private API: The History[1] functor gives you a "closure" function, which gives you a slice of the history graph. The functor needs a contents store (if S is of type Irmin.S, then S,Private.Contents) and a node store (S.Private.Node). But that's far too hard to use, I'll add an helper function in the API to get you a OCamlgraph graph of commits (and optionally tree and blobs) instead. > > Thanks for that very helpful report! I hope it makes things a little bit clearer. Yes, much clearer, thanks! > Thomas > > [1] http://mirage.github.io/irmin/Irmin.Private.Commit.History.html > > >> >> >> Thanks! >> >> >> -- >> Dr Thomas Leonard http://0install.net/ >> GPG: 9242 9807 C985 3C07 44A6 8B9A AE07 8280 59A5 3CC1 >> GPG: DA98 25AE CAD0 8975 7CDA BD8E 0713 3F96 CA74 D8BA >> >> _______________________________________________ >> MirageOS-devel mailing list >> MirageOS-devel@lists.xenproject.org >> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > -- Dr Thomas Leonard http://0install.net/ GPG: 9242 9807 C985 3C07 44A6 8B9A AE07 8280 59A5 3CC1 GPG: DA98 25AE CAD0 8975 7CDA BD8E 0713 3F96 CA74 D8BA _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Tue Feb 10 17:09:19 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 10 Feb 2015 17:09:19 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YLEJG-0004Il-NC; Tue, 10 Feb 2015 17:09:14 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YLEJF-0004Ig-Vm for mirageos-devel@lists.xenproject.org; Tue, 10 Feb 2015 17:09:14 +0000 Received: from [193.109.254.147] by server-1.bemta-14.messagelabs.com id F2/A2-02601-93B3AD45; Tue, 10 Feb 2015 17:09:13 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-4.tower-27.messagelabs.com!1423588151!12587386!1 X-Originating-IP: [209.85.212.181] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3843 invoked from network); 10 Feb 2015 17:09:11 -0000 Received: from mail-wi0-f181.google.com (HELO mail-wi0-f181.google.com) (209.85.212.181) by server-4.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 10 Feb 2015 17:09:11 -0000 Received: by mail-wi0-f181.google.com with SMTP id r20so10526258wiv.2 for ; Tue, 10 Feb 2015 09:09:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=Ol8zEHj+deSkn35owq6UYJblImMzutvuCaL3z89O4Rs=; b=aBnDT9Y1iObieXaPkzouLbX+kkCy1NMVOlpKlEyhmFQPwyXMuaFvLTt1Qf+Xy+MNN3 VBOjG/vxKy0pqSaZ+vUnUvaKs2z/pu4YBoGS3xH6g8gZJeuMD5eWjW5NT+gkyPPhnWoP 5DokYFWtp1f7OL5s9gzwNI36QiSQevLpMpCfFIZMUcRTQJ+sscfbkOmEn/GJT9v7nw5D tq3rWBn76sj4UWUHH2DXOuZGUAJmA7aZ2FhpFYR5rf6We46O/Pv4vowGYhAGEHmzfZlk Uz/Tixnh45w+R2V+ZHFU0zML5gpg//lyQcusYXp3ZMqLl1uzfdRVA1xTGKl6t91QqFu5 pXlg== X-Received: by 10.180.126.102 with SMTP id mx6mr48276875wib.12.1423588151358; Tue, 10 Feb 2015 09:09:11 -0800 (PST) Received: from ?IPv6:2001:630:212:248:5895:67c1:2cb1:2d56? ([2001:630:212:248:5895:67c1:2cb1:2d56]) by mx.google.com with ESMTPSA id vq9sm21592575wjc.6.2015.02.10.09.09.09 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 10 Feb 2015 09:09:10 -0800 (PST) Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\)) From: Thomas Gazagnaire In-Reply-To: Date: Tue, 10 Feb 2015 17:09:09 +0000 Message-Id: References: <8CEDB416-6238-4888-BA4B-B7305FDDE2D9@gazagnaire.org> To: Thomas Leonard X-Mailer: Apple Mail (2.1993) Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Irmin API newbie questions X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org I've updated http://mirage.github.io/irmin/Irmin.BC.html, it should hopefully get a bit clearer. Please feel free to reword/improve bits. Working on exposing the underlying history in a more friendly way now. Best, Thomas > On 10 Feb 2015, at 14:45, Thomas Leonard wrote: > > On 9 February 2015 at 14:41, Thomas Gazagnaire wrote: >> Hi Thomas, >> >>> (BTW, I think it might be useful to add the equivalent git command >>> next to functions in the documentation, since most people will >>> understand that already) >> >> ack, I'll do this. >> >>> The BASIC docs are missing >>> (https://mirage.github.io/irmin/Irmin.BASIC.html), but the code shows: >>> >>> type ('a, 'b) basic = (module BASIC with type key = 'a and type value = 'b) >>> >>> It seems that using Irmin.Contents.String gets me "key = string list", >>> but "step" remains abstract. How do I use cons, decons, etc? >> >> Why do you need to use cons and decons? Normally you should just need to use the usual list operators (ie. (::) for cons and pattern-matching for decons). If you have a use-case where this is not enough, please share it! It's possible that I forgot to export a type constraint somewhere. > > When walking the tree it's useful to get the last component with > rdecons, since there's no built-in function for this. Easy enough to > work around, of course. It's actually a bit strange that "list" > returns a "key list" rather than a "step list" (i.e. it returns full > paths). The docs say "list t k list the sub-paths of the path k in t", > but it looks like it's just the immediate children. Returning a step > would make that clear, if so. > >>> If I have a RW store, I can watch a key: >>> >>> val watch : t -> key -> value option Lwt_stream.t >>> >>> Presumably, I also need to take care to stop watching it when I'm >>> done, otherwise the stream will grow without limit, right? I guess >>> there should be an unwatch, or maybe this should be a React signal or >>> something. >> >> Yes the watch API still needs some work. It's working-ish enough to demo small examples (for instance you can run some of the examples and connect to http://127.0.0.1:8080/graph to see a nice animated graph of the store), but as you noticed there is no GC of ressources, maybe some leaks and the behaviour under load is not satisfactory (see issue https://github.com/mirage/irmin/issues/124). >> >>> I got a bit confused when I reached the BC page: >>> >>> https://mirage.github.io/irmin/Irmin.BC.html >>> >>> It uses 'tag' to mean a pointer to a commit that is updates on each >>> operation (i.e. what Git would call a 'branch'). I realise that tags >>> and branches are the same thing internally, but 'branch' seems to >>> capture better what Irmin is using them for ("The tag value is updated >>> every time the store is updated, so every handle connected or which >>> will be connected to the same tag will see the changes."). [ BTW, >>> what's a "handle"? ] >> >> The documentation is not totally clear here, you're right. You have two ways to identify a branch: either by name or by hash. In Irmin terminology, a branch name is a "tag". A commit hash is a "head". >> >>> val update_tag : t -> tag -> unit Lwt.t >>> update_tag t tag updates t's current branch with the contents of the >>> branch named tag. >>> >>> What does "update" mean here? Is this "git reset --hard tag"? A merge? >>> A "--ff-only" merge? >> >> `update_tag` is similar to `git reset --hard `. merge_tag is similar to `git merge `. I've tried to keep the update/merge duality in most of the places (you can update/merge a head, a view, an other branch). > > Might be worth mentioning that this may cause data-loss then (I don't > think that's clear from "update"). > >>> My mental model of Git is that the store is a DAG and I can append to >>> any branch. e.g. we have: >>> >>> git commit-tree [(-p )...] < changelog >>> >>> If I'm understanding the Irmin API correctly, each "store" >>> (repository? branch?) has a current "tag" (branch) and I need to set >>> the tag I want to work on, e.g. >>> >>> val switch : Store.t -> tag -> unit Lwt.t >> >> The simplest way to initialise a branch using a tag is to use `Irmin.of_tag ... `. If you want to create a branch in a "detached" mode, use `Irmin.of_head ... `. But yes, you can use switch to switch to another named branch. >> >>> If I want to work on another branch without changing the current >>> branch for other users, I should "clone" the store: >>> >>> val clone_force : ('a -> Irmin.task) -> t -> tag -> ('a -> t) Lwt.t >>> >>> But, this is not a "git clone", it's like "git branch tag" - a new >>> branch I can work on without affecting the repository's default >>> branch. It seems strange that Irmin has a mutable "current branch" at >>> all - this seems like a UI concept that's only needed for command-line >>> use (to save typing). >> >> Irmin has a concept of default branch (ie. "master") which is used when you use "Irmin.create". I choose that because the simplest use-case is to use Irmin as a normal k/v store, without having to worry about branches and such. > > OK, I think my confusion here is because (in my mind) there are two > separate concepts here: a repository is a collection of branches and a > branch head is a k/v store. But these are both combined into a single > "store" type. > >>> A "head" is defined as "a given store revision" (i.e. what Git would >>> call a commit). It wasn't clear to me at first whether a head was a >>> commit or an anonymous branch. e.g. >> >> A head is a commit hash. You can use a head with Irmin.of_head to create an anonymous branch. I agree that the documentation is not very clear on that. >> >>> val rename_tag : t -> tag -> [ `Duplicated_tag | `Ok ] Lwt.t >>> Change the current tag name. Fail if a tag with the same name already >>> exists. The head is unchanged. >>> >>> "The head is unchanged" suggests that heads might change in other >>> cases. Looking at the code, I see a "type head = Commit.key" in one >>> place, so I guess they're (usually?) commits. Does "head" here mean >>> "the default branch"? >> >> I'll make another pass on that part of the documentation to try to make all of these concepts clearer. I'll try to relate the API functions to Git command-line arguments, although I'm not sure the Git command-line is a model of clarity as well: `git reset --hard` is very different from `git reset --soft` for instance, and there are no direct notion on index file in Irmin (although the views can be seen as a kind of staging area). >> >>> Finally, how do I get history? e.g. if I want to show users the recent >>> changes to a document. I see a "slice" type, but it's not clear what I >>> can do with it. >> >> Anil asked me the question recently, and I promise him to add the missing function in the "simple" API. For now on, the functions are well-hidden inside the private API: The History[1] functor gives you a "closure" function, which gives you a slice of the history graph. The functor needs a contents store (if S is of type Irmin.S, then S,Private.Contents) and a node store (S.Private.Node). But that's far too hard to use, I'll add an helper function in the API to get you a OCamlgraph graph of commits (and optionally tree and blobs) instead. >> >> Thanks for that very helpful report! I hope it makes things a little bit clearer. > > Yes, much clearer, thanks! > >> Thomas >> >> [1] http://mirage.github.io/irmin/Irmin.Private.Commit.History.html >> >> >>> >>> >>> Thanks! >>> >>> >>> -- >>> Dr Thomas Leonard http://0install.net/ >>> GPG: 9242 9807 C985 3C07 44A6 8B9A AE07 8280 59A5 3CC1 >>> GPG: DA98 25AE CAD0 8975 7CDA BD8E 0713 3F96 CA74 D8BA >>> >>> _______________________________________________ >>> MirageOS-devel mailing list >>> MirageOS-devel@lists.xenproject.org >>> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel >> > > > > -- > Dr Thomas Leonard http://0install.net/ > GPG: 9242 9807 C985 3C07 44A6 8B9A AE07 8280 59A5 3CC1 > GPG: DA98 25AE CAD0 8975 7CDA BD8E 0713 3F96 CA74 D8BA > > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Tue Feb 10 17:09:19 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 10 Feb 2015 17:09:19 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YLEJG-0004Il-NC; Tue, 10 Feb 2015 17:09:14 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YLEJF-0004Ig-Vm for mirageos-devel@lists.xenproject.org; Tue, 10 Feb 2015 17:09:14 +0000 Received: from [193.109.254.147] by server-1.bemta-14.messagelabs.com id F2/A2-02601-93B3AD45; Tue, 10 Feb 2015 17:09:13 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-4.tower-27.messagelabs.com!1423588151!12587386!1 X-Originating-IP: [209.85.212.181] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3843 invoked from network); 10 Feb 2015 17:09:11 -0000 Received: from mail-wi0-f181.google.com (HELO mail-wi0-f181.google.com) (209.85.212.181) by server-4.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 10 Feb 2015 17:09:11 -0000 Received: by mail-wi0-f181.google.com with SMTP id r20so10526258wiv.2 for ; Tue, 10 Feb 2015 09:09:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=Ol8zEHj+deSkn35owq6UYJblImMzutvuCaL3z89O4Rs=; b=aBnDT9Y1iObieXaPkzouLbX+kkCy1NMVOlpKlEyhmFQPwyXMuaFvLTt1Qf+Xy+MNN3 VBOjG/vxKy0pqSaZ+vUnUvaKs2z/pu4YBoGS3xH6g8gZJeuMD5eWjW5NT+gkyPPhnWoP 5DokYFWtp1f7OL5s9gzwNI36QiSQevLpMpCfFIZMUcRTQJ+sscfbkOmEn/GJT9v7nw5D tq3rWBn76sj4UWUHH2DXOuZGUAJmA7aZ2FhpFYR5rf6We46O/Pv4vowGYhAGEHmzfZlk Uz/Tixnh45w+R2V+ZHFU0zML5gpg//lyQcusYXp3ZMqLl1uzfdRVA1xTGKl6t91QqFu5 pXlg== X-Received: by 10.180.126.102 with SMTP id mx6mr48276875wib.12.1423588151358; Tue, 10 Feb 2015 09:09:11 -0800 (PST) Received: from ?IPv6:2001:630:212:248:5895:67c1:2cb1:2d56? ([2001:630:212:248:5895:67c1:2cb1:2d56]) by mx.google.com with ESMTPSA id vq9sm21592575wjc.6.2015.02.10.09.09.09 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 10 Feb 2015 09:09:10 -0800 (PST) Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\)) From: Thomas Gazagnaire In-Reply-To: Date: Tue, 10 Feb 2015 17:09:09 +0000 Message-Id: References: <8CEDB416-6238-4888-BA4B-B7305FDDE2D9@gazagnaire.org> To: Thomas Leonard X-Mailer: Apple Mail (2.1993) Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Irmin API newbie questions X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org I've updated http://mirage.github.io/irmin/Irmin.BC.html, it should hopefully get a bit clearer. Please feel free to reword/improve bits. Working on exposing the underlying history in a more friendly way now. Best, Thomas > On 10 Feb 2015, at 14:45, Thomas Leonard wrote: > > On 9 February 2015 at 14:41, Thomas Gazagnaire wrote: >> Hi Thomas, >> >>> (BTW, I think it might be useful to add the equivalent git command >>> next to functions in the documentation, since most people will >>> understand that already) >> >> ack, I'll do this. >> >>> The BASIC docs are missing >>> (https://mirage.github.io/irmin/Irmin.BASIC.html), but the code shows: >>> >>> type ('a, 'b) basic = (module BASIC with type key = 'a and type value = 'b) >>> >>> It seems that using Irmin.Contents.String gets me "key = string list", >>> but "step" remains abstract. How do I use cons, decons, etc? >> >> Why do you need to use cons and decons? Normally you should just need to use the usual list operators (ie. (::) for cons and pattern-matching for decons). If you have a use-case where this is not enough, please share it! It's possible that I forgot to export a type constraint somewhere. > > When walking the tree it's useful to get the last component with > rdecons, since there's no built-in function for this. Easy enough to > work around, of course. It's actually a bit strange that "list" > returns a "key list" rather than a "step list" (i.e. it returns full > paths). The docs say "list t k list the sub-paths of the path k in t", > but it looks like it's just the immediate children. Returning a step > would make that clear, if so. > >>> If I have a RW store, I can watch a key: >>> >>> val watch : t -> key -> value option Lwt_stream.t >>> >>> Presumably, I also need to take care to stop watching it when I'm >>> done, otherwise the stream will grow without limit, right? I guess >>> there should be an unwatch, or maybe this should be a React signal or >>> something. >> >> Yes the watch API still needs some work. It's working-ish enough to demo small examples (for instance you can run some of the examples and connect to http://127.0.0.1:8080/graph to see a nice animated graph of the store), but as you noticed there is no GC of ressources, maybe some leaks and the behaviour under load is not satisfactory (see issue https://github.com/mirage/irmin/issues/124). >> >>> I got a bit confused when I reached the BC page: >>> >>> https://mirage.github.io/irmin/Irmin.BC.html >>> >>> It uses 'tag' to mean a pointer to a commit that is updates on each >>> operation (i.e. what Git would call a 'branch'). I realise that tags >>> and branches are the same thing internally, but 'branch' seems to >>> capture better what Irmin is using them for ("The tag value is updated >>> every time the store is updated, so every handle connected or which >>> will be connected to the same tag will see the changes."). [ BTW, >>> what's a "handle"? ] >> >> The documentation is not totally clear here, you're right. You have two ways to identify a branch: either by name or by hash. In Irmin terminology, a branch name is a "tag". A commit hash is a "head". >> >>> val update_tag : t -> tag -> unit Lwt.t >>> update_tag t tag updates t's current branch with the contents of the >>> branch named tag. >>> >>> What does "update" mean here? Is this "git reset --hard tag"? A merge? >>> A "--ff-only" merge? >> >> `update_tag` is similar to `git reset --hard `. merge_tag is similar to `git merge `. I've tried to keep the update/merge duality in most of the places (you can update/merge a head, a view, an other branch). > > Might be worth mentioning that this may cause data-loss then (I don't > think that's clear from "update"). > >>> My mental model of Git is that the store is a DAG and I can append to >>> any branch. e.g. we have: >>> >>> git commit-tree [(-p )...] < changelog >>> >>> If I'm understanding the Irmin API correctly, each "store" >>> (repository? branch?) has a current "tag" (branch) and I need to set >>> the tag I want to work on, e.g. >>> >>> val switch : Store.t -> tag -> unit Lwt.t >> >> The simplest way to initialise a branch using a tag is to use `Irmin.of_tag ... `. If you want to create a branch in a "detached" mode, use `Irmin.of_head ... `. But yes, you can use switch to switch to another named branch. >> >>> If I want to work on another branch without changing the current >>> branch for other users, I should "clone" the store: >>> >>> val clone_force : ('a -> Irmin.task) -> t -> tag -> ('a -> t) Lwt.t >>> >>> But, this is not a "git clone", it's like "git branch tag" - a new >>> branch I can work on without affecting the repository's default >>> branch. It seems strange that Irmin has a mutable "current branch" at >>> all - this seems like a UI concept that's only needed for command-line >>> use (to save typing). >> >> Irmin has a concept of default branch (ie. "master") which is used when you use "Irmin.create". I choose that because the simplest use-case is to use Irmin as a normal k/v store, without having to worry about branches and such. > > OK, I think my confusion here is because (in my mind) there are two > separate concepts here: a repository is a collection of branches and a > branch head is a k/v store. But these are both combined into a single > "store" type. > >>> A "head" is defined as "a given store revision" (i.e. what Git would >>> call a commit). It wasn't clear to me at first whether a head was a >>> commit or an anonymous branch. e.g. >> >> A head is a commit hash. You can use a head with Irmin.of_head to create an anonymous branch. I agree that the documentation is not very clear on that. >> >>> val rename_tag : t -> tag -> [ `Duplicated_tag | `Ok ] Lwt.t >>> Change the current tag name. Fail if a tag with the same name already >>> exists. The head is unchanged. >>> >>> "The head is unchanged" suggests that heads might change in other >>> cases. Looking at the code, I see a "type head = Commit.key" in one >>> place, so I guess they're (usually?) commits. Does "head" here mean >>> "the default branch"? >> >> I'll make another pass on that part of the documentation to try to make all of these concepts clearer. I'll try to relate the API functions to Git command-line arguments, although I'm not sure the Git command-line is a model of clarity as well: `git reset --hard` is very different from `git reset --soft` for instance, and there are no direct notion on index file in Irmin (although the views can be seen as a kind of staging area). >> >>> Finally, how do I get history? e.g. if I want to show users the recent >>> changes to a document. I see a "slice" type, but it's not clear what I >>> can do with it. >> >> Anil asked me the question recently, and I promise him to add the missing function in the "simple" API. For now on, the functions are well-hidden inside the private API: The History[1] functor gives you a "closure" function, which gives you a slice of the history graph. The functor needs a contents store (if S is of type Irmin.S, then S,Private.Contents) and a node store (S.Private.Node). But that's far too hard to use, I'll add an helper function in the API to get you a OCamlgraph graph of commits (and optionally tree and blobs) instead. >> >> Thanks for that very helpful report! I hope it makes things a little bit clearer. > > Yes, much clearer, thanks! > >> Thomas >> >> [1] http://mirage.github.io/irmin/Irmin.Private.Commit.History.html >> >> >>> >>> >>> Thanks! >>> >>> >>> -- >>> Dr Thomas Leonard http://0install.net/ >>> GPG: 9242 9807 C985 3C07 44A6 8B9A AE07 8280 59A5 3CC1 >>> GPG: DA98 25AE CAD0 8975 7CDA BD8E 0713 3F96 CA74 D8BA >>> >>> _______________________________________________ >>> MirageOS-devel mailing list >>> MirageOS-devel@lists.xenproject.org >>> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel >> > > > > -- > Dr Thomas Leonard http://0install.net/ > GPG: 9242 9807 C985 3C07 44A6 8B9A AE07 8280 59A5 3CC1 > GPG: DA98 25AE CAD0 8975 7CDA BD8E 0713 3F96 CA74 D8BA > > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Tue Feb 10 17:58:45 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 10 Feb 2015 17:58:45 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YLF5A-0008Pv-6k; Tue, 10 Feb 2015 17:58:44 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YLF59-0008Pq-6b for mirageos-devel@lists.xenproject.org; Tue, 10 Feb 2015 17:58:43 +0000 Received: from [193.109.254.147] by server-6.bemta-14.messagelabs.com id D7/29-03164-2D64AD45; Tue, 10 Feb 2015 17:58:42 +0000 X-Env-Sender: yotambarnoy@gmail.com X-Msg-Ref: server-11.tower-27.messagelabs.com!1423591121!9245885!1 X-Originating-IP: [209.85.212.181] X-SpamReason: No, hits=0.9 required=7.0 tests=HTML_40_50,HTML_MESSAGE, RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11636 invoked from network); 10 Feb 2015 17:58:41 -0000 Received: from mail-wi0-f181.google.com (HELO mail-wi0-f181.google.com) (209.85.212.181) by server-11.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 10 Feb 2015 17:58:41 -0000 Received: by mail-wi0-f181.google.com with SMTP id r20so10888119wiv.2 for ; Tue, 10 Feb 2015 09:58:41 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=VOY5SJyMjOdVEGg65jRpW0dbWzB5C1MhULVwGQBc8VU=; b=jAbm6C91ocZHWv9eklCzgUfw+ZD85c5VlqaoM5i9ZLF1pFSSIFV4l2rowS5cuj0+jR cK2RDFS5nNfE3n6M7vi8kbLd6SB7H+Xz97JZlSEDpeOtG7tKGULKGAbwBjU61QJvcGt6 nc6vVS6jehsfoT39YXGAuDpZe6u8e/oE7RDlAdMwPGZxzegqAl1jezVk0PsFdIvQBsiR uUllZ76TmdWgHxE/aB/Lf0J+Pjtzkx9zucx9Qp3xHmvECN3fSo4iNtCuLPRmv63wCDUc 3zs/m1NucxqHg5GpUkoHcWqoFsBY7VcgMy0hpNO5vvGVnANsZnvBTACkjDzcDeJqlCjv tlDQ== X-Received: by 10.180.81.134 with SMTP id a6mr11603076wiy.88.1423591121000; Tue, 10 Feb 2015 09:58:41 -0800 (PST) MIME-Version: 1.0 Received: by 10.194.17.229 with HTTP; Tue, 10 Feb 2015 09:58:20 -0800 (PST) In-Reply-To: References: From: Yotam Barnoy Date: Tue, 10 Feb 2015 12:58:20 -0500 Message-ID: To: Jeremy Yallop Cc: "cl-ocamllabs-staff@lists.cam.ac.uk" , "mirageos-devel@lists.xenproject.org" , "cl-ocamllabs@lists.cam.ac.uk" , "cam-compiler-hacking@lists.ocaml.org" Subject: Re: [MirageOS-devel] [compiler-hacking] Compiler hacking evening next Tuesday (10th February) X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============6548817626061660132==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============6548817626061660132== Content-Type: multipart/alternative; boundary=f46d04428cba129f59050ebfa35a --f46d04428cba129f59050ebfa35a Content-Type: text/plain; charset=UTF-8 Any chance the web thing is happening, or is it off the table? On Mon, Feb 9, 2015 at 9:02 AM, Jeremy Yallop wrote: > Reminder: compiler hacking tomorrow! If you're planning to come > along, please add your name to the poll: > > http://doodle.com/zxmeyn2ih92mke85 > > On 6 February 2015 at 10:58, Jeremy Yallop wrote: > > It's time for another evening of OCaml compiler hacking! We'll be > meeting > > next Tuesday evening (10th February) in the Computer Lab. If you're > > planning to come along, please add yourself to the Doodle poll: > > > > http://doodle.com/zxmeyn2ih92mke85 > > > > Schedule: > > > > 1800 - Start, set up > > 1830 - Talk: Generating code with polymorphic let (Oleg Kiselyov) > > 1900 - Pizza > > 1930-2200 Compiler hacking > > > > Further details are on the blog: > > > > > > > http://ocamllabs.github.io/compiler-hacking/2015/02/05/back-in-the-lab.html > > > > All welcome: if you're local to Cambridge and interested in contributing > to > > the OCaml compiler, please come along! > _______________________________________________ > Cam-compiler-hacking mailing list > Cam-compiler-hacking@lists.ocaml.org > http://lists.ocaml.org/listinfo/cam-compiler-hacking > --f46d04428cba129f59050ebfa35a Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Any chance the web thing is happening, or is it off the ta= ble?

On Mon,= Feb 9, 2015 at 9:02 AM, Jeremy Yallop <yallop@gmail.com> wro= te:
Reminder: compiler hacking tomorrow!= =C2=A0 If you're planning to come
along, please add your name to the poll:

=C2=A0 =C2=A0 http://doodle.com/zxmeyn2ih92mke85

On 6 February 2015 at 10:58, Jeremy Yallop <yallop@gmail.com> wrote:
> It's time for another evening of OCaml compiler hacking!=C2=A0 We&= #39;ll be meeting
> next Tuesday evening (10th February) in the Computer Lab.=C2=A0 If you= 're
> planning to come along, please add yourself to the Doodle poll:
>
>=C2=A0 =C2=A0 =C2=A0http://doodle.com/zxmeyn2ih92mke85
>
> Schedule:
>
>=C2=A0 =C2=A0 =C2=A01800 - Start, set up
>=C2=A0 =C2=A0 =C2=A01830 - Talk: Generating code with polymorphic let (= Oleg Kiselyov)
>=C2=A0 =C2=A0 =C2=A01900 - Pizza
>=C2=A0 =C2=A0 =C2=A01930-2200=C2=A0 Compiler hacking
>
> Further details are on the blog:
>
>
> http://ocamllabs.github.io/compiler-hac= king/2015/02/05/back-in-the-lab.html
>
> All welcome: if you're local to Cambridge and interested in contri= buting to
> the OCaml compiler, please come along!
_______________________= ________________________
Cam-compiler-hacking mailing list
Cam-compiler-hackin= g@lists.ocaml.org
http://lists.ocaml.org/listinfo/cam-compiler-hacking

--f46d04428cba129f59050ebfa35a-- --===============6548817626061660132== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --===============6548817626061660132==-- From mirageos-devel-bounces@lists.xenproject.org Tue Feb 10 17:58:45 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 10 Feb 2015 17:58:45 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YLF5A-0008Pv-6k; Tue, 10 Feb 2015 17:58:44 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YLF59-0008Pq-6b for mirageos-devel@lists.xenproject.org; Tue, 10 Feb 2015 17:58:43 +0000 Received: from [193.109.254.147] by server-6.bemta-14.messagelabs.com id D7/29-03164-2D64AD45; Tue, 10 Feb 2015 17:58:42 +0000 X-Env-Sender: yotambarnoy@gmail.com X-Msg-Ref: server-11.tower-27.messagelabs.com!1423591121!9245885!1 X-Originating-IP: [209.85.212.181] X-SpamReason: No, hits=0.9 required=7.0 tests=HTML_40_50,HTML_MESSAGE, RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11636 invoked from network); 10 Feb 2015 17:58:41 -0000 Received: from mail-wi0-f181.google.com (HELO mail-wi0-f181.google.com) (209.85.212.181) by server-11.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 10 Feb 2015 17:58:41 -0000 Received: by mail-wi0-f181.google.com with SMTP id r20so10888119wiv.2 for ; Tue, 10 Feb 2015 09:58:41 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=VOY5SJyMjOdVEGg65jRpW0dbWzB5C1MhULVwGQBc8VU=; b=jAbm6C91ocZHWv9eklCzgUfw+ZD85c5VlqaoM5i9ZLF1pFSSIFV4l2rowS5cuj0+jR cK2RDFS5nNfE3n6M7vi8kbLd6SB7H+Xz97JZlSEDpeOtG7tKGULKGAbwBjU61QJvcGt6 nc6vVS6jehsfoT39YXGAuDpZe6u8e/oE7RDlAdMwPGZxzegqAl1jezVk0PsFdIvQBsiR uUllZ76TmdWgHxE/aB/Lf0J+Pjtzkx9zucx9Qp3xHmvECN3fSo4iNtCuLPRmv63wCDUc 3zs/m1NucxqHg5GpUkoHcWqoFsBY7VcgMy0hpNO5vvGVnANsZnvBTACkjDzcDeJqlCjv tlDQ== X-Received: by 10.180.81.134 with SMTP id a6mr11603076wiy.88.1423591121000; Tue, 10 Feb 2015 09:58:41 -0800 (PST) MIME-Version: 1.0 Received: by 10.194.17.229 with HTTP; Tue, 10 Feb 2015 09:58:20 -0800 (PST) In-Reply-To: References: From: Yotam Barnoy Date: Tue, 10 Feb 2015 12:58:20 -0500 Message-ID: To: Jeremy Yallop Cc: "cl-ocamllabs-staff@lists.cam.ac.uk" , "mirageos-devel@lists.xenproject.org" , "cl-ocamllabs@lists.cam.ac.uk" , "cam-compiler-hacking@lists.ocaml.org" Subject: Re: [MirageOS-devel] [compiler-hacking] Compiler hacking evening next Tuesday (10th February) X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============6548817626061660132==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============6548817626061660132== Content-Type: multipart/alternative; boundary=f46d04428cba129f59050ebfa35a --f46d04428cba129f59050ebfa35a Content-Type: text/plain; charset=UTF-8 Any chance the web thing is happening, or is it off the table? On Mon, Feb 9, 2015 at 9:02 AM, Jeremy Yallop wrote: > Reminder: compiler hacking tomorrow! If you're planning to come > along, please add your name to the poll: > > http://doodle.com/zxmeyn2ih92mke85 > > On 6 February 2015 at 10:58, Jeremy Yallop wrote: > > It's time for another evening of OCaml compiler hacking! We'll be > meeting > > next Tuesday evening (10th February) in the Computer Lab. If you're > > planning to come along, please add yourself to the Doodle poll: > > > > http://doodle.com/zxmeyn2ih92mke85 > > > > Schedule: > > > > 1800 - Start, set up > > 1830 - Talk: Generating code with polymorphic let (Oleg Kiselyov) > > 1900 - Pizza > > 1930-2200 Compiler hacking > > > > Further details are on the blog: > > > > > > > http://ocamllabs.github.io/compiler-hacking/2015/02/05/back-in-the-lab.html > > > > All welcome: if you're local to Cambridge and interested in contributing > to > > the OCaml compiler, please come along! > _______________________________________________ > Cam-compiler-hacking mailing list > Cam-compiler-hacking@lists.ocaml.org > http://lists.ocaml.org/listinfo/cam-compiler-hacking > --f46d04428cba129f59050ebfa35a Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Any chance the web thing is happening, or is it off the ta= ble?

On Mon,= Feb 9, 2015 at 9:02 AM, Jeremy Yallop <yallop@gmail.com> wro= te:
Reminder: compiler hacking tomorrow!= =C2=A0 If you're planning to come
along, please add your name to the poll:

=C2=A0 =C2=A0 http://doodle.com/zxmeyn2ih92mke85

On 6 February 2015 at 10:58, Jeremy Yallop <yallop@gmail.com> wrote:
> It's time for another evening of OCaml compiler hacking!=C2=A0 We&= #39;ll be meeting
> next Tuesday evening (10th February) in the Computer Lab.=C2=A0 If you= 're
> planning to come along, please add yourself to the Doodle poll:
>
>=C2=A0 =C2=A0 =C2=A0http://doodle.com/zxmeyn2ih92mke85
>
> Schedule:
>
>=C2=A0 =C2=A0 =C2=A01800 - Start, set up
>=C2=A0 =C2=A0 =C2=A01830 - Talk: Generating code with polymorphic let (= Oleg Kiselyov)
>=C2=A0 =C2=A0 =C2=A01900 - Pizza
>=C2=A0 =C2=A0 =C2=A01930-2200=C2=A0 Compiler hacking
>
> Further details are on the blog:
>
>
> http://ocamllabs.github.io/compiler-hac= king/2015/02/05/back-in-the-lab.html
>
> All welcome: if you're local to Cambridge and interested in contri= buting to
> the OCaml compiler, please come along!
_______________________= ________________________
Cam-compiler-hacking mailing list
Cam-compiler-hackin= g@lists.ocaml.org
http://lists.ocaml.org/listinfo/cam-compiler-hacking

--f46d04428cba129f59050ebfa35a-- --===============6548817626061660132== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --===============6548817626061660132==-- From mirageos-devel-bounces@lists.xenproject.org Wed Feb 11 15:18:49 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 11 Feb 2015 15:18:49 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YLZ3r-0006YX-6u; Wed, 11 Feb 2015 15:18:43 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YLZ3o-0006YS-SW for mirageos-devel@lists.xenproject.org; Wed, 11 Feb 2015 15:18:41 +0000 Received: from [193.109.254.147] by server-15.bemta-14.messagelabs.com id 6D/3A-02770-0D27BD45; Wed, 11 Feb 2015 15:18:40 +0000 X-Env-Sender: talex5@gmail.com X-Msg-Ref: server-5.tower-27.messagelabs.com!1423667918!8166706!1 X-Originating-IP: [209.85.217.180] X-SpamReason: No, hits=0.6 required=7.0 tests=MAILTO_TO_SPAM_ADDR, RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31107 invoked from network); 11 Feb 2015 15:18:39 -0000 Received: from mail-lb0-f180.google.com (HELO mail-lb0-f180.google.com) (209.85.217.180) by server-5.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 11 Feb 2015 15:18:39 -0000 Received: by mail-lb0-f180.google.com with SMTP id z12so3767633lbi.11 for ; Wed, 11 Feb 2015 07:18:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=NvQx4am99vEuSmhwqNp6zJ5QSOV6wFVgXWAxXM5BkDc=; b=sBiiqZeSzqxwy39n4UNd5D/sigyMpUkNtP20h43JBSRL5HE6R75XO3i6Jzjbp9S58v Zb9BUB2YS5ScFoQ/JHB036xiR8pjJA7eDU1XIyiVouAHEiumyKQtKPYU3OFG60UowM0f QceD1TERU9ofLMk2py1fL5Z7b8aaCJlz1OHf5I6NwGHyV2pFSV1mGfhRFz8fhYgItLoe YCnJi1KdDx6XNHi0SGj5IGEHJ+NKvbf/JfB5W2VW09ACKn+brQIZ970vCfoutEEl1NGM DIgco32ArO1tRG4N3SwEoln6Qc77V/B24DyDJuEtISqMprxaGitnN01uk31kLlTyw2eF wKkw== MIME-Version: 1.0 X-Received: by 10.112.40.65 with SMTP id v1mr28331191lbk.26.1423667918601; Wed, 11 Feb 2015 07:18:38 -0800 (PST) Received: by 10.25.207.206 with HTTP; Wed, 11 Feb 2015 07:18:38 -0800 (PST) In-Reply-To: <87oap97rvw.fsf@study.localdomain> References: <20150202.014549.1883720051237442569.Christophe.Troestler@umons.ac.be> <20150204.001614.26478837567139584.Christophe.Troestler@umons.ac.be> <87oap97rvw.fsf@study.localdomain> Date: Wed, 11 Feb 2015 15:18:38 +0000 Message-ID: From: Thomas Leonard To: Leo White Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Error handling in Mirage - request for comments! X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 4 February 2015 at 13:01, Leo White wrote: > Hi all, > > As this discussion keeps on running, I thought I would add a couple of > thoughts: > > - The problem with using exceptions for returning errors is that it > becomes very difficult to distinguish between a dynamic error that is > part of normal use (e.g. this network connection failed) from a > programming error (e.g. Not_found accidently leaked from a use of > List.find, an assert false triggering). This makes it hard to produce > the correct behaviour in all cases: there are applications for which > it would be better to kill everyting on detecting a programmer error > rather than risk continuing in an unstable state. > > - The problem with using Lwt.t as your error monad is that it becomes > difficult to distiunguish between synchronous things that may return > errors, asynchronous things that may return errors, and asynchornous > things that should not return errors. It also seems tied up with the > exception mechanism, which leads to the same problem as my previous > point. > > Personally, I would probably suggest that all Mirage modules/module > types include in their signatures: > > type error > > val pp_error : formatter -> error -> string > > For cases where an error can reasonably be matched on and handled > specially, this should be exposed in the signature: > > type error = private [> `Foo of foo | `Bar of bar] > > val pp_error : formatter -> error -> string I've had a go at writing this proposal up ("system 5"): https://github.com/talex5/mirage-www/blob/errors/tmpl/wiki/error-handling.md I think someone who wants to advocate this style should check it / change it. It probably needs some worked examples showing it being used too. > Some nice combinators should be provided for using ('a, 'b) Result.t and > ('a, 'b) Result.t Lwt. and for lifting an ('a, Foo.error) Result.t into > an ('a, Bar.error) Result.t. > > Exceptions that escape their intended scope, should always be treated as > a programming error. Yes, by definition. But what should the "intended scope" be, and how do we ensure the producer and consumers of the exception agree? In 0install, for example, there is a single "Safe_exception" constructor used for any non-bug human-readable error that should abort without showing a stack trace ("File '...' not found", etc). If they make it to the top-level, they get printed to stderr. In the GUI, they appear in an error dialog box. Any other kind of exception reaching the top-level is considered a bug. For a library, these kinds of thing need to be documented. > The various "finally" functions for resources > should catch and reraise them, so that they can reach the outermost > scope which knows how best to deal with a programming error in the > particular application. The same goes for binding on an Lwt thread which > raised an exception or failed: it should cause an exception to be raised > to reach the outermost level. > > The aim here is still to take the erlang-style kill the component that > failed and try again approach, but to ensure that there are two distinct > return paths for regular errors and programming errors. The secondary > aim is to have module signatures which give a clear indication of > intended use. -- Dr Thomas Leonard http://0install.net/ GPG: 9242 9807 C985 3C07 44A6 8B9A AE07 8280 59A5 3CC1 GPG: DA98 25AE CAD0 8975 7CDA BD8E 0713 3F96 CA74 D8BA _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Wed Feb 11 15:18:49 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 11 Feb 2015 15:18:49 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YLZ3r-0006YX-6u; Wed, 11 Feb 2015 15:18:43 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YLZ3o-0006YS-SW for mirageos-devel@lists.xenproject.org; Wed, 11 Feb 2015 15:18:41 +0000 Received: from [193.109.254.147] by server-15.bemta-14.messagelabs.com id 6D/3A-02770-0D27BD45; Wed, 11 Feb 2015 15:18:40 +0000 X-Env-Sender: talex5@gmail.com X-Msg-Ref: server-5.tower-27.messagelabs.com!1423667918!8166706!1 X-Originating-IP: [209.85.217.180] X-SpamReason: No, hits=0.6 required=7.0 tests=MAILTO_TO_SPAM_ADDR, RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31107 invoked from network); 11 Feb 2015 15:18:39 -0000 Received: from mail-lb0-f180.google.com (HELO mail-lb0-f180.google.com) (209.85.217.180) by server-5.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 11 Feb 2015 15:18:39 -0000 Received: by mail-lb0-f180.google.com with SMTP id z12so3767633lbi.11 for ; Wed, 11 Feb 2015 07:18:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=NvQx4am99vEuSmhwqNp6zJ5QSOV6wFVgXWAxXM5BkDc=; b=sBiiqZeSzqxwy39n4UNd5D/sigyMpUkNtP20h43JBSRL5HE6R75XO3i6Jzjbp9S58v Zb9BUB2YS5ScFoQ/JHB036xiR8pjJA7eDU1XIyiVouAHEiumyKQtKPYU3OFG60UowM0f QceD1TERU9ofLMk2py1fL5Z7b8aaCJlz1OHf5I6NwGHyV2pFSV1mGfhRFz8fhYgItLoe YCnJi1KdDx6XNHi0SGj5IGEHJ+NKvbf/JfB5W2VW09ACKn+brQIZ970vCfoutEEl1NGM DIgco32ArO1tRG4N3SwEoln6Qc77V/B24DyDJuEtISqMprxaGitnN01uk31kLlTyw2eF wKkw== MIME-Version: 1.0 X-Received: by 10.112.40.65 with SMTP id v1mr28331191lbk.26.1423667918601; Wed, 11 Feb 2015 07:18:38 -0800 (PST) Received: by 10.25.207.206 with HTTP; Wed, 11 Feb 2015 07:18:38 -0800 (PST) In-Reply-To: <87oap97rvw.fsf@study.localdomain> References: <20150202.014549.1883720051237442569.Christophe.Troestler@umons.ac.be> <20150204.001614.26478837567139584.Christophe.Troestler@umons.ac.be> <87oap97rvw.fsf@study.localdomain> Date: Wed, 11 Feb 2015 15:18:38 +0000 Message-ID: From: Thomas Leonard To: Leo White Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Error handling in Mirage - request for comments! X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 4 February 2015 at 13:01, Leo White wrote: > Hi all, > > As this discussion keeps on running, I thought I would add a couple of > thoughts: > > - The problem with using exceptions for returning errors is that it > becomes very difficult to distinguish between a dynamic error that is > part of normal use (e.g. this network connection failed) from a > programming error (e.g. Not_found accidently leaked from a use of > List.find, an assert false triggering). This makes it hard to produce > the correct behaviour in all cases: there are applications for which > it would be better to kill everyting on detecting a programmer error > rather than risk continuing in an unstable state. > > - The problem with using Lwt.t as your error monad is that it becomes > difficult to distiunguish between synchronous things that may return > errors, asynchronous things that may return errors, and asynchornous > things that should not return errors. It also seems tied up with the > exception mechanism, which leads to the same problem as my previous > point. > > Personally, I would probably suggest that all Mirage modules/module > types include in their signatures: > > type error > > val pp_error : formatter -> error -> string > > For cases where an error can reasonably be matched on and handled > specially, this should be exposed in the signature: > > type error = private [> `Foo of foo | `Bar of bar] > > val pp_error : formatter -> error -> string I've had a go at writing this proposal up ("system 5"): https://github.com/talex5/mirage-www/blob/errors/tmpl/wiki/error-handling.md I think someone who wants to advocate this style should check it / change it. It probably needs some worked examples showing it being used too. > Some nice combinators should be provided for using ('a, 'b) Result.t and > ('a, 'b) Result.t Lwt. and for lifting an ('a, Foo.error) Result.t into > an ('a, Bar.error) Result.t. > > Exceptions that escape their intended scope, should always be treated as > a programming error. Yes, by definition. But what should the "intended scope" be, and how do we ensure the producer and consumers of the exception agree? In 0install, for example, there is a single "Safe_exception" constructor used for any non-bug human-readable error that should abort without showing a stack trace ("File '...' not found", etc). If they make it to the top-level, they get printed to stderr. In the GUI, they appear in an error dialog box. Any other kind of exception reaching the top-level is considered a bug. For a library, these kinds of thing need to be documented. > The various "finally" functions for resources > should catch and reraise them, so that they can reach the outermost > scope which knows how best to deal with a programming error in the > particular application. The same goes for binding on an Lwt thread which > raised an exception or failed: it should cause an exception to be raised > to reach the outermost level. > > The aim here is still to take the erlang-style kill the component that > failed and try again approach, but to ensure that there are two distinct > return paths for regular errors and programming errors. The secondary > aim is to have module signatures which give a clear indication of > intended use. -- Dr Thomas Leonard http://0install.net/ GPG: 9242 9807 C985 3C07 44A6 8B9A AE07 8280 59A5 3CC1 GPG: DA98 25AE CAD0 8975 7CDA BD8E 0713 3F96 CA74 D8BA _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Wed Feb 11 16:05:54 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 11 Feb 2015 16:05:54 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YLZnV-0002YU-GE; Wed, 11 Feb 2015 16:05:53 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YLZnT-0002YP-Of for mirageos-devel@lists.xenproject.org; Wed, 11 Feb 2015 16:05:51 +0000 Received: from [85.158.137.68] by server-15.bemta-3.messagelabs.com id D8/33-02884-FDD7BD45; Wed, 11 Feb 2015 16:05:51 +0000 X-Env-Sender: amirmc@gmail.com X-Msg-Ref: server-2.tower-31.messagelabs.com!1423670750!10930422!1 X-Originating-IP: [74.125.82.42] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2405 invoked from network); 11 Feb 2015 16:05:50 -0000 Received: from mail-wg0-f42.google.com (HELO mail-wg0-f42.google.com) (74.125.82.42) by server-2.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 11 Feb 2015 16:05:50 -0000 Received: by mail-wg0-f42.google.com with SMTP id x13so4445144wgg.1 for ; Wed, 11 Feb 2015 08:05:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=2upWKrpB620n+7LuxAyHOcPhsAsWTUhrSIK85eIqjQA=; b=m21F91EiHPEBt7p4D/8Fk/WlCe31MxcUNDkMK8MsLx0lbCIpWUmNDE7gEb+J5sUjtA KEnIzTtXPeE8yv44fEjjtTbGjsAjJ/cBbcrvnCvqdRDj2jzNzcfj9jA2+NFYrdFIsr91 QiiOsEyWEMWaKirDys15+2bjbrBgtYdFGOUm17nNQ6WTqrzpwijLnlU0F9LOslnJe+YR qrUbd6KaQt6sImWIgZ21rgSUPb2fAJtie4nzpFofuErAHuCQ6xbC+4e8u1668ZGhDlCp pEMDiVVJUCT/430FUBzlgbmBQubT92Ksex/+SzqHN97QjdZ4hovk2qFl0M/JJUYKoysj 9S9A== X-Received: by 10.194.61.51 with SMTP id m19mr1072602wjr.39.1423670748438; Wed, 11 Feb 2015 08:05:48 -0800 (PST) Received: from dhcp-172-17-153-0.eduroam.wireless.private.cam.ac.uk (global-1-26.nat.csx.cam.ac.uk. [131.111.184.26]) by mx.google.com with ESMTPSA id n6sm1869309wjy.8.2015.02.11.08.05.46 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 11 Feb 2015 08:05:47 -0800 (PST) Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) From: Amir Chaudhry In-Reply-To: <79441473-AA54-45B0-9D7C-9F0D1E61068C@gmail.com> Date: Wed, 11 Feb 2015 16:05:45 +0000 Message-Id: References: <79441473-AA54-45B0-9D7C-9F0D1E61068C@gmail.com> To: Amir Chaudhry X-Mailer: Apple Mail (2.1510) Cc: mirageos-devel Subject: Re: [MirageOS-devel] Mirage fortnightly call - Wednesday 11th at 4pm GMT X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: quoted-printable Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org switching to Hangout due to issues with GTM https://plus.google.com/hangouts/_/gq7e36svyh3okzlban3s65nwnya AC On 10 Feb 2015, at 14:12, Amir Chaudhry wrote: > Hi folks, > = > The next Mirage call will take place this Wednesday afternoon at 4pm GMT = and is open to all. > = > Notes from last time are delayed but they'll be up soon! = > = > The agenda is currently as follows: > = > =95 Quality > =95 Error Handling RFC > =95 TLS merge progress > =95 FOSDEM demo > =95 GSoC Projects > = > If you have things to add/edit, please do so at https://github.com/mirage= /mirage-www/wiki/Call-Agenda > = > GoToMeeting details are below but if there are any hiccups/delays then I'= ll switch to a public Google Hangout. If that happens, I'll post the link = here and also in the IRC channel (#mirage on freenode). > = > Join us at 4pm GMT on Wednesday! > = > 1. Please join my meeting. > https://www1.gotomeeting.com/join/591890401 > = > Dial in numbers (ask if you need a specific country): > United Kingdom: +44 (0) 20 3657 6778 > United States: +1 (213) 493-0014 > Access Code: 591-890-401 > Audio PIN: Shown after joining the meeting > = > Best wishes, > Amir _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Wed Feb 11 16:05:54 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 11 Feb 2015 16:05:54 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YLZnV-0002YU-GE; Wed, 11 Feb 2015 16:05:53 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YLZnT-0002YP-Of for mirageos-devel@lists.xenproject.org; Wed, 11 Feb 2015 16:05:51 +0000 Received: from [85.158.137.68] by server-15.bemta-3.messagelabs.com id D8/33-02884-FDD7BD45; Wed, 11 Feb 2015 16:05:51 +0000 X-Env-Sender: amirmc@gmail.com X-Msg-Ref: server-2.tower-31.messagelabs.com!1423670750!10930422!1 X-Originating-IP: [74.125.82.42] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2405 invoked from network); 11 Feb 2015 16:05:50 -0000 Received: from mail-wg0-f42.google.com (HELO mail-wg0-f42.google.com) (74.125.82.42) by server-2.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 11 Feb 2015 16:05:50 -0000 Received: by mail-wg0-f42.google.com with SMTP id x13so4445144wgg.1 for ; Wed, 11 Feb 2015 08:05:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=2upWKrpB620n+7LuxAyHOcPhsAsWTUhrSIK85eIqjQA=; b=m21F91EiHPEBt7p4D/8Fk/WlCe31MxcUNDkMK8MsLx0lbCIpWUmNDE7gEb+J5sUjtA KEnIzTtXPeE8yv44fEjjtTbGjsAjJ/cBbcrvnCvqdRDj2jzNzcfj9jA2+NFYrdFIsr91 QiiOsEyWEMWaKirDys15+2bjbrBgtYdFGOUm17nNQ6WTqrzpwijLnlU0F9LOslnJe+YR qrUbd6KaQt6sImWIgZ21rgSUPb2fAJtie4nzpFofuErAHuCQ6xbC+4e8u1668ZGhDlCp pEMDiVVJUCT/430FUBzlgbmBQubT92Ksex/+SzqHN97QjdZ4hovk2qFl0M/JJUYKoysj 9S9A== X-Received: by 10.194.61.51 with SMTP id m19mr1072602wjr.39.1423670748438; Wed, 11 Feb 2015 08:05:48 -0800 (PST) Received: from dhcp-172-17-153-0.eduroam.wireless.private.cam.ac.uk (global-1-26.nat.csx.cam.ac.uk. [131.111.184.26]) by mx.google.com with ESMTPSA id n6sm1869309wjy.8.2015.02.11.08.05.46 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 11 Feb 2015 08:05:47 -0800 (PST) Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) From: Amir Chaudhry In-Reply-To: <79441473-AA54-45B0-9D7C-9F0D1E61068C@gmail.com> Date: Wed, 11 Feb 2015 16:05:45 +0000 Message-Id: References: <79441473-AA54-45B0-9D7C-9F0D1E61068C@gmail.com> To: Amir Chaudhry X-Mailer: Apple Mail (2.1510) Cc: mirageos-devel Subject: Re: [MirageOS-devel] Mirage fortnightly call - Wednesday 11th at 4pm GMT X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: quoted-printable Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org switching to Hangout due to issues with GTM https://plus.google.com/hangouts/_/gq7e36svyh3okzlban3s65nwnya AC On 10 Feb 2015, at 14:12, Amir Chaudhry wrote: > Hi folks, > = > The next Mirage call will take place this Wednesday afternoon at 4pm GMT = and is open to all. > = > Notes from last time are delayed but they'll be up soon! = > = > The agenda is currently as follows: > = > =95 Quality > =95 Error Handling RFC > =95 TLS merge progress > =95 FOSDEM demo > =95 GSoC Projects > = > If you have things to add/edit, please do so at https://github.com/mirage= /mirage-www/wiki/Call-Agenda > = > GoToMeeting details are below but if there are any hiccups/delays then I'= ll switch to a public Google Hangout. If that happens, I'll post the link = here and also in the IRC channel (#mirage on freenode). > = > Join us at 4pm GMT on Wednesday! > = > 1. Please join my meeting. > https://www1.gotomeeting.com/join/591890401 > = > Dial in numbers (ask if you need a specific country): > United Kingdom: +44 (0) 20 3657 6778 > United States: +1 (213) 493-0014 > Access Code: 591-890-401 > Audio PIN: Shown after joining the meeting > = > Best wishes, > Amir _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Wed Feb 11 16:37:02 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 11 Feb 2015 16:37:02 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YLaHb-0004qj-F7; Wed, 11 Feb 2015 16:36:59 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YLaHa-0004qe-6y for mirageos-devel@lists.xenproject.org; Wed, 11 Feb 2015 16:36:58 +0000 Received: from [85.158.137.68] by server-4.bemta-3.messagelabs.com id 67/85-03185-9258BD45; Wed, 11 Feb 2015 16:36:57 +0000 X-Env-Sender: daniel.buenzli@erratique.ch X-Msg-Ref: server-7.tower-31.messagelabs.com!1423672616!10934840!1 X-Originating-IP: [74.55.86.74] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNzQuNTUuODYuNzQgPT4gMzA4NTYz\n X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 18945 invoked from network); 11 Feb 2015 16:36:56 -0000 Received: from mail6.webfaction.com (HELO smtp.webfaction.com) (74.55.86.74) by server-7.tower-31.messagelabs.com with SMTP; 11 Feb 2015 16:36:56 -0000 Received: from [172.20.10.2] (38.232.197.178.dynamic.wless.lssmb00p-cgnat.res.cust.swisscom.ch [178.197.232.38]) by smtp.webfaction.com (Postfix) with ESMTP id 2356B20D36CE; Wed, 11 Feb 2015 16:36:54 +0000 (UTC) Date: Wed, 11 Feb 2015 17:36:52 +0100 From: =?utf-8?Q?Daniel_B=C3=BCnzli?= To: Thomas Leonard Message-ID: In-Reply-To: References: <20150202.014549.1883720051237442569.Christophe.Troestler@umons.ac.be> <20150204.001614.26478837567139584.Christophe.Troestler@umons.ac.be> <87oap97rvw.fsf@study.localdomain> X-Mailer: sparrow 1.6.4 (build 1178) MIME-Version: 1.0 Content-Disposition: inline Cc: "=?utf-8?Q?mirageos-devel=40lists.xenproject.org?=" Subject: Re: [MirageOS-devel] Error handling in Mirage - request for comments! X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org CgpMZSBtZXJjcmVkaSwgMTEgZsOpdnJpZXIgMjAxNSDDoCAxNjoxOCwgVGhvbWFzIExlb25hcmQg YSDDqWNyaXQgOgoKPiBJIHRoaW5rIHNvbWVvbmUgd2hvIHdhbnRzIHRvIGFkdm9jYXRlIHRoaXMg c3R5bGUgc2hvdWxkIGNoZWNrIGl0IC8KPiBjaGFuZ2UgaXQuIEl0IHByb2JhYmx5IG5lZWRzIHNv bWUgd29ya2VkIGV4YW1wbGVzIHNob3dpbmcgaXQgYmVpbmcKPiB1c2VkIHRvby4KClNlZW1zIGZp bmUuICAKCkhvd2V2ZXIgSSBkaXNhZ3JlZSB3aXRoIG1vc3Qgb2YgdGhlIHN5c3RlbSA1ICJwcm9i bGVtcyI6IEkgdGhpbmsgbW9zdCBvZiB0aGUgcHJlc2VudGVkIHByb2JsZW1zIGFyZSBzb2x2ZWQg YnkgcHJvdmlkaW5nIHRoZSBtb25hZGljIGNvbWJpbmF0b3JzL29wZXJhdG9ycyBmb3IgdGhlIGVy cm9yIHR5cGUgYW5kIEkgZG9uJ3Qgc2VlIHdoeSB0aGlzIHN5c3RlbSBpcyBoYXJkZXIgdG8gZXhw bGFpbiB0byBuZXcgdXNlcnM6IG1hbnkgT0NhbWwgbGlicmFyaWVzIGFscmVhZHkgdXNlIHRoYXQg c2NoZW1lLiAgCgpUd28gcHJvYmxlbSB0aGF0IGV4aXN0IGFuZCB0aGF0IGFyZSBub3QgbWVudGlv bmVkIGlzIHRoYXQgeW91J2xsIHNvbWV0aW1lcyBoYXZlIHRvIHdyaXRlIGV4cGxpY2l0IGNvZXJj aW9ucyAod2hpY2ggc2hvdWxkbid0IGJlIHRvbyBiYWQgaWYgeW91IGFsd2F5cyB0YWtlIGNhcmUg dG8gZ2l2ZSBhIHR5cGUgbmFtZSB0byBzZXRzIG9mIHBvbHl2YXJzKSBhbmQgdGhhdCB0eXBlIGVy cm9ycyBjb3VsZCBzb21ldGltZXMgZ2V0IHdpbGQuICAKCj4gWWVzLCBieSBkZWZpbml0aW9uLiBC dXQgd2hhdCBzaG91bGQgdGhlICJpbnRlbmRlZCBzY29wZSIgYmUsIGFuZCBob3cKPiBkbyB3ZSBl bnN1cmUgdGhlIHByb2R1Y2VyIGFuZCBjb25zdW1lcnMgb2YgdGhlIGV4Y2VwdGlvbiBhZ3JlZT8K CklmIHlvdSBhc3N1bWUgdGhlIG9ubHkgZXhjZXB0aW9ucyB5b3UnbGwgZ2V0IGFyZSBwcm9ncmFt bWluZyBlcnJvcnMgdGhlbiBvbmUgcG9pbnQgb2YgdmlldyBpcyB0aGUgZm9sbG93aW5nOiBubyBl eGNlcHRpb24gc2hvdWxkIGNyb3NzIGEgY29tcG9uZW50IGJvdW5kYXJ5LiAgCgpNaXJhZ2UgY29t cG9uZW50cyBhcmUgYWtpbiB0byBwbHVnaW5zIChleGNlcHQgdGhleSBhcmUgc3RhdGljYWxseSBs aW5rZWQgaW4pLCB0aGUgb25seSB3YXkgdG8gcm9idXN0bHkgZGVhbCB3aXRoIHRoYXQgaXMgdG8g cHJvdGVjdCBhbnkgY2FsbCB0byB0aGUgY29tcG9uZW50IGFnYWluc3Qgc3B1cmlvdXMgZXhjZXB0 aW9ucyAoaGVyZSdzIGFuIGV4YW1wbGUgdXNpbmcgZHlubGluayBhbmQgZmlyc3QgY2xhc3MgbW9k dWxlIFsxXSkuICAKClRoaXMgYnVyZGVuIGNhbiBiZSBwdXQgZWl0aGVyIG9uIHRoZSBjb21wb25l bnQgd3JpdGVyIGJ5IHR5cGUtZm9yY2luZyBoZXIgdG8gdXNlIGEgdHJhcCBhYnN0cmFjdGlvbiBv ciBhdCB0aGUgY29tcG9uZW50IGNvbXBvc2l0aW9uIGxldmVsIGJ5IGhhdmluZyBhIHdyYXBwaW5n IGZ1bmN0b3IgdGhhdCBmb3J3YXJkcyB0aGUgY2FsbHMgYnV0IGNhdGNoZXMgYW55IHNwdXJpb3Vz IGV4Y2VwdGlvbnMuICAKCkluIGJvdGggY2FzZXMgdGhlIHNwdXJpb3VzIGV4Y2VwdGlvbiBzaG91 bGQgYmUgY29udmVydGVkIHRvIGFuIGFwcHJvcHJpYXRlIGAoJ2EsIFs+YEludGVybmFsX2Vycm9y IG9mIGV4bl0pIHJlc3VsdGAgdmFsdWUgc28gdGhhdCB0aGUgdXNlciBvZiB0aGUgY29tcG9uZW50 IGNhbiBmdXJ0aGVyIG1ha2UgYSBkZWNpc2lvbiBvZiB3aGF0IGl0IHdhbnRzIHRvIGRvIHdpdGgg dGhhdC4gKEluIHRoZSBsaW5rZWQgZXhhbXBsZSB3ZSBsb2cgdGhlIHNwdXJpb3VzIGV4Y2VwdGlv biBhbmQgcmV0dXJuIGEgZGVmYXVsdCB+ZmFpbCB2YWx1ZSB0byBhbGxvdyB0byBjb250aW51ZSB0 aGUgY29tcHV0YXRpb24sIGEgY29tYmluYXRvciBjb3VsZCBiZSBwcm92aWRlZCBmb3IgdGhhdCku CgpUaGlzIG1heSBzZWVtIGhlYXZ5IChhbGwgY29tcG9uZW50IGZ1bmN0aW9ucyByZXR1cm4gYXQg bGVhc3QgYCgnYSwgWz5gSW50ZXJuYWxfZXJyb3Igb2YgZXhuXSkgcmVzdWx0YCB2YWx1ZXMpIHVu dGlsIHlvdSByZWFsaXplIHlvdSBjYW4gcHJvdmlkZSB1c2VycyB3aXRoIGZ1bmN0b3JzIHRoYXQg Y2FuIGltcGxlbWVudCBlcnJvciBoYW5kbGluZyBzdHJhdGVnaWVzIHRvIGtub3dpbmdseSBhbmQg cm9idXN0bHkgbGliZXJhdGUgeW91IGZyb20gcGFydCBvZiB0aGUgZXJyb3IgaGFuZGxpbmcuIEUu Zy4gdGhlIGJlaGF2aW91ciBvZiB0aGUgbGlua2VkIGV4YW1wbGUgY291bGQgYmUgaW1wbGVtZW50 ZWQgYnkgYSBmdW5jdG9yIHRoYXQgdGFrZXMgYSBMb2cgbW9kdWxlIGFuZCBhIGNvbXBvbmVudCBp bXBsZW1lbnRhdGlvbiwgaW50ZXJuYWwgZXJyb3JzIHdvdWxkIGJlIGxvZ2dlZCBhbmQgdGhlIGZ1 bmN0b3Igd291bGQgZGVmaW5lIGEgZGVmYXVsdCBiZWhhdmlvdXIgZm9yIHRoZSBgSW50ZXJuYWxf ZXJyb3IgY2FzZXMuIEFsdG9nZXRoZXIgSSB0aGluayB0aGlzIHN5c3RlbSBpcyBtdWNoIG1vcmUg cm9idXN0IGFuZCBoYXMgbXVjaCBiZXR0ZXIgY29tcG9zaXRpb25hbCBwcm9wZXJ0aWVzIHRoYW4g dXNpbmcgaW1wbGljaXQgZXhjZXB0aW9ucy4gIAoKQmVzdCwKCkRhbmllbAoKWzFdIEFueSBjYWxs IHRvIHRoZSBkeW5saW5rZWQgbW9kdWxlIGlzIHByb3RlY3RlZCBieSB0aGlzIGZ1bmN0aW9uOgoK aHR0cHM6Ly9naXRodWIuY29tL2RidWVuemxpL3dlYmdsdWUvYmxvYi9tYXN0ZXIvc3JjL2FwaS93 Zy5tbCNMMTM2NAoKSGVyZSdzIGFuIGV4YW1wbGUgb2YgdXNlOgoKaHR0cHM6Ly9naXRodWIuY29t L2RidWVuemxpL3dlYmdsdWUvYmxvYi9tYXN0ZXIvc3JjL2FwaS93Zy5tbCNMMTU3NC1MMTU3OAoK CgoKX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KTWlyYWdl T1MtZGV2ZWwgbWFpbGluZyBsaXN0Ck1pcmFnZU9TLWRldmVsQGxpc3RzLnhlbnByb2plY3Qub3Jn Cmh0dHA6Ly9saXN0cy54ZW5wcm9qZWN0Lm9yZy9jZ2ktYmluL21haWxtYW4vbGlzdGluZm8vbWly YWdlb3MtZGV2ZWwK From mirageos-devel-bounces@lists.xenproject.org Wed Feb 11 16:37:02 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 11 Feb 2015 16:37:02 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YLaHb-0004qj-F7; Wed, 11 Feb 2015 16:36:59 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YLaHa-0004qe-6y for mirageos-devel@lists.xenproject.org; Wed, 11 Feb 2015 16:36:58 +0000 Received: from [85.158.137.68] by server-4.bemta-3.messagelabs.com id 67/85-03185-9258BD45; Wed, 11 Feb 2015 16:36:57 +0000 X-Env-Sender: daniel.buenzli@erratique.ch X-Msg-Ref: server-7.tower-31.messagelabs.com!1423672616!10934840!1 X-Originating-IP: [74.55.86.74] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNzQuNTUuODYuNzQgPT4gMzA4NTYz\n X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 18945 invoked from network); 11 Feb 2015 16:36:56 -0000 Received: from mail6.webfaction.com (HELO smtp.webfaction.com) (74.55.86.74) by server-7.tower-31.messagelabs.com with SMTP; 11 Feb 2015 16:36:56 -0000 Received: from [172.20.10.2] (38.232.197.178.dynamic.wless.lssmb00p-cgnat.res.cust.swisscom.ch [178.197.232.38]) by smtp.webfaction.com (Postfix) with ESMTP id 2356B20D36CE; Wed, 11 Feb 2015 16:36:54 +0000 (UTC) Date: Wed, 11 Feb 2015 17:36:52 +0100 From: =?utf-8?Q?Daniel_B=C3=BCnzli?= To: Thomas Leonard Message-ID: In-Reply-To: References: <20150202.014549.1883720051237442569.Christophe.Troestler@umons.ac.be> <20150204.001614.26478837567139584.Christophe.Troestler@umons.ac.be> <87oap97rvw.fsf@study.localdomain> X-Mailer: sparrow 1.6.4 (build 1178) MIME-Version: 1.0 Content-Disposition: inline Cc: "=?utf-8?Q?mirageos-devel=40lists.xenproject.org?=" Subject: Re: [MirageOS-devel] Error handling in Mirage - request for comments! X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org CgpMZSBtZXJjcmVkaSwgMTEgZsOpdnJpZXIgMjAxNSDDoCAxNjoxOCwgVGhvbWFzIExlb25hcmQg YSDDqWNyaXQgOgoKPiBJIHRoaW5rIHNvbWVvbmUgd2hvIHdhbnRzIHRvIGFkdm9jYXRlIHRoaXMg c3R5bGUgc2hvdWxkIGNoZWNrIGl0IC8KPiBjaGFuZ2UgaXQuIEl0IHByb2JhYmx5IG5lZWRzIHNv bWUgd29ya2VkIGV4YW1wbGVzIHNob3dpbmcgaXQgYmVpbmcKPiB1c2VkIHRvby4KClNlZW1zIGZp bmUuICAKCkhvd2V2ZXIgSSBkaXNhZ3JlZSB3aXRoIG1vc3Qgb2YgdGhlIHN5c3RlbSA1ICJwcm9i bGVtcyI6IEkgdGhpbmsgbW9zdCBvZiB0aGUgcHJlc2VudGVkIHByb2JsZW1zIGFyZSBzb2x2ZWQg YnkgcHJvdmlkaW5nIHRoZSBtb25hZGljIGNvbWJpbmF0b3JzL29wZXJhdG9ycyBmb3IgdGhlIGVy cm9yIHR5cGUgYW5kIEkgZG9uJ3Qgc2VlIHdoeSB0aGlzIHN5c3RlbSBpcyBoYXJkZXIgdG8gZXhw bGFpbiB0byBuZXcgdXNlcnM6IG1hbnkgT0NhbWwgbGlicmFyaWVzIGFscmVhZHkgdXNlIHRoYXQg c2NoZW1lLiAgCgpUd28gcHJvYmxlbSB0aGF0IGV4aXN0IGFuZCB0aGF0IGFyZSBub3QgbWVudGlv bmVkIGlzIHRoYXQgeW91J2xsIHNvbWV0aW1lcyBoYXZlIHRvIHdyaXRlIGV4cGxpY2l0IGNvZXJj aW9ucyAod2hpY2ggc2hvdWxkbid0IGJlIHRvbyBiYWQgaWYgeW91IGFsd2F5cyB0YWtlIGNhcmUg dG8gZ2l2ZSBhIHR5cGUgbmFtZSB0byBzZXRzIG9mIHBvbHl2YXJzKSBhbmQgdGhhdCB0eXBlIGVy cm9ycyBjb3VsZCBzb21ldGltZXMgZ2V0IHdpbGQuICAKCj4gWWVzLCBieSBkZWZpbml0aW9uLiBC dXQgd2hhdCBzaG91bGQgdGhlICJpbnRlbmRlZCBzY29wZSIgYmUsIGFuZCBob3cKPiBkbyB3ZSBl bnN1cmUgdGhlIHByb2R1Y2VyIGFuZCBjb25zdW1lcnMgb2YgdGhlIGV4Y2VwdGlvbiBhZ3JlZT8K CklmIHlvdSBhc3N1bWUgdGhlIG9ubHkgZXhjZXB0aW9ucyB5b3UnbGwgZ2V0IGFyZSBwcm9ncmFt bWluZyBlcnJvcnMgdGhlbiBvbmUgcG9pbnQgb2YgdmlldyBpcyB0aGUgZm9sbG93aW5nOiBubyBl eGNlcHRpb24gc2hvdWxkIGNyb3NzIGEgY29tcG9uZW50IGJvdW5kYXJ5LiAgCgpNaXJhZ2UgY29t cG9uZW50cyBhcmUgYWtpbiB0byBwbHVnaW5zIChleGNlcHQgdGhleSBhcmUgc3RhdGljYWxseSBs aW5rZWQgaW4pLCB0aGUgb25seSB3YXkgdG8gcm9idXN0bHkgZGVhbCB3aXRoIHRoYXQgaXMgdG8g cHJvdGVjdCBhbnkgY2FsbCB0byB0aGUgY29tcG9uZW50IGFnYWluc3Qgc3B1cmlvdXMgZXhjZXB0 aW9ucyAoaGVyZSdzIGFuIGV4YW1wbGUgdXNpbmcgZHlubGluayBhbmQgZmlyc3QgY2xhc3MgbW9k dWxlIFsxXSkuICAKClRoaXMgYnVyZGVuIGNhbiBiZSBwdXQgZWl0aGVyIG9uIHRoZSBjb21wb25l bnQgd3JpdGVyIGJ5IHR5cGUtZm9yY2luZyBoZXIgdG8gdXNlIGEgdHJhcCBhYnN0cmFjdGlvbiBv ciBhdCB0aGUgY29tcG9uZW50IGNvbXBvc2l0aW9uIGxldmVsIGJ5IGhhdmluZyBhIHdyYXBwaW5n IGZ1bmN0b3IgdGhhdCBmb3J3YXJkcyB0aGUgY2FsbHMgYnV0IGNhdGNoZXMgYW55IHNwdXJpb3Vz IGV4Y2VwdGlvbnMuICAKCkluIGJvdGggY2FzZXMgdGhlIHNwdXJpb3VzIGV4Y2VwdGlvbiBzaG91 bGQgYmUgY29udmVydGVkIHRvIGFuIGFwcHJvcHJpYXRlIGAoJ2EsIFs+YEludGVybmFsX2Vycm9y IG9mIGV4bl0pIHJlc3VsdGAgdmFsdWUgc28gdGhhdCB0aGUgdXNlciBvZiB0aGUgY29tcG9uZW50 IGNhbiBmdXJ0aGVyIG1ha2UgYSBkZWNpc2lvbiBvZiB3aGF0IGl0IHdhbnRzIHRvIGRvIHdpdGgg dGhhdC4gKEluIHRoZSBsaW5rZWQgZXhhbXBsZSB3ZSBsb2cgdGhlIHNwdXJpb3VzIGV4Y2VwdGlv biBhbmQgcmV0dXJuIGEgZGVmYXVsdCB+ZmFpbCB2YWx1ZSB0byBhbGxvdyB0byBjb250aW51ZSB0 aGUgY29tcHV0YXRpb24sIGEgY29tYmluYXRvciBjb3VsZCBiZSBwcm92aWRlZCBmb3IgdGhhdCku CgpUaGlzIG1heSBzZWVtIGhlYXZ5IChhbGwgY29tcG9uZW50IGZ1bmN0aW9ucyByZXR1cm4gYXQg bGVhc3QgYCgnYSwgWz5gSW50ZXJuYWxfZXJyb3Igb2YgZXhuXSkgcmVzdWx0YCB2YWx1ZXMpIHVu dGlsIHlvdSByZWFsaXplIHlvdSBjYW4gcHJvdmlkZSB1c2VycyB3aXRoIGZ1bmN0b3JzIHRoYXQg Y2FuIGltcGxlbWVudCBlcnJvciBoYW5kbGluZyBzdHJhdGVnaWVzIHRvIGtub3dpbmdseSBhbmQg cm9idXN0bHkgbGliZXJhdGUgeW91IGZyb20gcGFydCBvZiB0aGUgZXJyb3IgaGFuZGxpbmcuIEUu Zy4gdGhlIGJlaGF2aW91ciBvZiB0aGUgbGlua2VkIGV4YW1wbGUgY291bGQgYmUgaW1wbGVtZW50 ZWQgYnkgYSBmdW5jdG9yIHRoYXQgdGFrZXMgYSBMb2cgbW9kdWxlIGFuZCBhIGNvbXBvbmVudCBp bXBsZW1lbnRhdGlvbiwgaW50ZXJuYWwgZXJyb3JzIHdvdWxkIGJlIGxvZ2dlZCBhbmQgdGhlIGZ1 bmN0b3Igd291bGQgZGVmaW5lIGEgZGVmYXVsdCBiZWhhdmlvdXIgZm9yIHRoZSBgSW50ZXJuYWxf ZXJyb3IgY2FzZXMuIEFsdG9nZXRoZXIgSSB0aGluayB0aGlzIHN5c3RlbSBpcyBtdWNoIG1vcmUg cm9idXN0IGFuZCBoYXMgbXVjaCBiZXR0ZXIgY29tcG9zaXRpb25hbCBwcm9wZXJ0aWVzIHRoYW4g dXNpbmcgaW1wbGljaXQgZXhjZXB0aW9ucy4gIAoKQmVzdCwKCkRhbmllbAoKWzFdIEFueSBjYWxs IHRvIHRoZSBkeW5saW5rZWQgbW9kdWxlIGlzIHByb3RlY3RlZCBieSB0aGlzIGZ1bmN0aW9uOgoK aHR0cHM6Ly9naXRodWIuY29tL2RidWVuemxpL3dlYmdsdWUvYmxvYi9tYXN0ZXIvc3JjL2FwaS93 Zy5tbCNMMTM2NAoKSGVyZSdzIGFuIGV4YW1wbGUgb2YgdXNlOgoKaHR0cHM6Ly9naXRodWIuY29t L2RidWVuemxpL3dlYmdsdWUvYmxvYi9tYXN0ZXIvc3JjL2FwaS93Zy5tbCNMMTU3NC1MMTU3OAoK CgoKX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KTWlyYWdl T1MtZGV2ZWwgbWFpbGluZyBsaXN0Ck1pcmFnZU9TLWRldmVsQGxpc3RzLnhlbnByb2plY3Qub3Jn Cmh0dHA6Ly9saXN0cy54ZW5wcm9qZWN0Lm9yZy9jZ2ktYmluL21haWxtYW4vbGlzdGluZm8vbWly YWdlb3MtZGV2ZWwK From mirageos-devel-bounces@lists.xenproject.org Wed Feb 11 16:41:32 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 11 Feb 2015 16:41:32 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YLaLy-0004vp-TD; Wed, 11 Feb 2015 16:41:30 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YLaLx-0004vY-6b for mirageos-devel@lists.xenproject.org; Wed, 11 Feb 2015 16:41:29 +0000 Received: from [85.158.137.68] by server-2.bemta-3.messagelabs.com id F2/40-02991-8368BD45; Wed, 11 Feb 2015 16:41:28 +0000 X-Env-Sender: lpw25@cam.ac.uk X-Msg-Ref: server-5.tower-31.messagelabs.com!1423672887!10979763!1 X-Originating-IP: [131.111.8.150] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTMxLjExMS44LjE1MCA9PiAxNDk0MDU=\n X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 13154 invoked from network); 11 Feb 2015 16:41:28 -0000 Received: from ppsw-50.csi.cam.ac.uk (HELO ppsw-50.csi.cam.ac.uk) (131.111.8.150) by server-5.tower-31.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 11 Feb 2015 16:41:28 -0000 X-Cam-AntiVirus: no malware found X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/ Received: from host86-190-253-201.range86-190.btcentralplus.com ([86.190.253.201]:36574 helo=study.localdomain) by ppsw-50.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.158]:587) with esmtpsa (PLAIN:lpw25) (TLSv1.2:AES128-GCM-SHA256:128) id 1YLaLv-0001je-rD (Exim 4.82_3-c0e5623) (return-path ); Wed, 11 Feb 2015 16:41:27 +0000 From: Leo White To: Thomas Leonard References: <20150202.014549.1883720051237442569.Christophe.Troestler@umons.ac.be> <20150204.001614.26478837567139584.Christophe.Troestler@umons.ac.be> <87oap97rvw.fsf@study.localdomain> X-Face: "XWxb[u_Z\PA_Y?9@|IA!!+jTb(/290-*ea/Un$I0B98.$n%eL.; 2w*,z]WR#T:,p[ NBd++M7l]#7zj7!{~iw $W-"/=|dVjhT[D{4~gE}gK<2`.6fs!;uqqud]vs2N/3^m7{aS1V, Date: Wed, 11 Feb 2015 16:41:11 +0000 In-Reply-To: (Thomas Leonard's message of "Wed, 11 Feb 2015 15:18:38 +0000") Message-ID: <87lhk4csew.fsf@study.localdomain> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) MIME-Version: 1.0 Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Error handling in Mirage - request for comments! X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org > > I've had a go at writing this proposal up ("system 5"): > > https://github.com/talex5/mirage-www/blob/errors/tmpl/wiki/error-handling.md > > I think someone who wants to advocate this style should check it / > change it. It probably needs some worked examples showing it being > used too. > The interface given for "system 5" is not comparable for the one given for "system 4", giving a false sense of verbosity to the "system 5" example. The equivalent to the "system 4" example, would just be: type error val pp_error : formatter -> error -> string val read : t -> int64 -> page_aligned_buffer list -> (int, error) result Constructors of `error` should only be exposed if they are intended to be matched on. So if `read` has a kind of error ``Foo` which was intended to be matched on then the "system 5" approach would be: type error = private [> `Foo] val pp_error : formatter -> error -> string val read : t -> int64 -> page_aligned_buffer list -> (int, error) result whilst "system 4" would probably look like: exception Foo val read : t -> int64 -> page_aligned_buffer list -> int The splitting of `error` up into `write_error` and `read_error` is only needed if you have an interface with different sets of matchable errors. So if you had a `read` function with a matchable error ``Foo` and a `write` function with matchable error ``Bar`, then you would get the following: type read_error = private [> `Foo] type write_error = private [> `Bar] type error val pp_error : formatter -> error -> string val write_error : write_error -> error val read_error : read_error -> error val read : t -> int64 -> page_aligned_buffer list -> (int, read_error) result val write : t -> int64 -> page_aligned_buffer list -> (int, write_error) result whilst "system 4" would probably look like: exception Foo exception Bar val read : t -> int64 -> page_aligned_buffer list -> int val write : t -> int64 -> page_aligned_buffer list -> int A key benefit of "system 5" is that the signature contains all the interesting information about `read` and `write`. It clearly states that they are expected to fail sometimes, and that the only errors on which it is reasonable to behave specially are a `Foo` returned by `read` or a `Bar` returned by `write`. `System 4` does not convey any of this information. >> Some nice combinators should be provided for using ('a, 'b) Result.t and >> ('a, 'b) Result.t Lwt. and for lifting an ('a, Foo.error) Result.t into >> an ('a, Bar.error) Result.t. >> >> Exceptions that escape their intended scope, should always be treated as >> a programming error. > > Yes, by definition. But what should the "intended scope" be, and how > do we ensure the producer and consumers of the exception agree? Exceptions should basically never delibrately cross module boundaries. They should certainly not be part of the exposed API of a library. By "exceptions that escape their scope" I essentially meant exceptions used in third-party APIs (e.g. Not_found produced by List.find), these should always be caught as early as possible and handled appropriately. Occasionally it is reasonable for an exception like "Invalid_argument" to be part of a library API, where the exception is not intended to be caught but merely to indicate that there has been a programmer error. It is also reasonable to use exceptions locally for control-flow, but again these should not escape into the visible API. Regards, Leo _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Wed Feb 11 16:41:32 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 11 Feb 2015 16:41:32 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YLaLy-0004vp-TD; Wed, 11 Feb 2015 16:41:30 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YLaLx-0004vY-6b for mirageos-devel@lists.xenproject.org; Wed, 11 Feb 2015 16:41:29 +0000 Received: from [85.158.137.68] by server-2.bemta-3.messagelabs.com id F2/40-02991-8368BD45; Wed, 11 Feb 2015 16:41:28 +0000 X-Env-Sender: lpw25@cam.ac.uk X-Msg-Ref: server-5.tower-31.messagelabs.com!1423672887!10979763!1 X-Originating-IP: [131.111.8.150] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTMxLjExMS44LjE1MCA9PiAxNDk0MDU=\n X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 13154 invoked from network); 11 Feb 2015 16:41:28 -0000 Received: from ppsw-50.csi.cam.ac.uk (HELO ppsw-50.csi.cam.ac.uk) (131.111.8.150) by server-5.tower-31.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 11 Feb 2015 16:41:28 -0000 X-Cam-AntiVirus: no malware found X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/ Received: from host86-190-253-201.range86-190.btcentralplus.com ([86.190.253.201]:36574 helo=study.localdomain) by ppsw-50.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.158]:587) with esmtpsa (PLAIN:lpw25) (TLSv1.2:AES128-GCM-SHA256:128) id 1YLaLv-0001je-rD (Exim 4.82_3-c0e5623) (return-path ); Wed, 11 Feb 2015 16:41:27 +0000 From: Leo White To: Thomas Leonard References: <20150202.014549.1883720051237442569.Christophe.Troestler@umons.ac.be> <20150204.001614.26478837567139584.Christophe.Troestler@umons.ac.be> <87oap97rvw.fsf@study.localdomain> X-Face: "XWxb[u_Z\PA_Y?9@|IA!!+jTb(/290-*ea/Un$I0B98.$n%eL.; 2w*,z]WR#T:,p[ NBd++M7l]#7zj7!{~iw $W-"/=|dVjhT[D{4~gE}gK<2`.6fs!;uqqud]vs2N/3^m7{aS1V, Date: Wed, 11 Feb 2015 16:41:11 +0000 In-Reply-To: (Thomas Leonard's message of "Wed, 11 Feb 2015 15:18:38 +0000") Message-ID: <87lhk4csew.fsf@study.localdomain> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) MIME-Version: 1.0 Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Error handling in Mirage - request for comments! X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org > > I've had a go at writing this proposal up ("system 5"): > > https://github.com/talex5/mirage-www/blob/errors/tmpl/wiki/error-handling.md > > I think someone who wants to advocate this style should check it / > change it. It probably needs some worked examples showing it being > used too. > The interface given for "system 5" is not comparable for the one given for "system 4", giving a false sense of verbosity to the "system 5" example. The equivalent to the "system 4" example, would just be: type error val pp_error : formatter -> error -> string val read : t -> int64 -> page_aligned_buffer list -> (int, error) result Constructors of `error` should only be exposed if they are intended to be matched on. So if `read` has a kind of error ``Foo` which was intended to be matched on then the "system 5" approach would be: type error = private [> `Foo] val pp_error : formatter -> error -> string val read : t -> int64 -> page_aligned_buffer list -> (int, error) result whilst "system 4" would probably look like: exception Foo val read : t -> int64 -> page_aligned_buffer list -> int The splitting of `error` up into `write_error` and `read_error` is only needed if you have an interface with different sets of matchable errors. So if you had a `read` function with a matchable error ``Foo` and a `write` function with matchable error ``Bar`, then you would get the following: type read_error = private [> `Foo] type write_error = private [> `Bar] type error val pp_error : formatter -> error -> string val write_error : write_error -> error val read_error : read_error -> error val read : t -> int64 -> page_aligned_buffer list -> (int, read_error) result val write : t -> int64 -> page_aligned_buffer list -> (int, write_error) result whilst "system 4" would probably look like: exception Foo exception Bar val read : t -> int64 -> page_aligned_buffer list -> int val write : t -> int64 -> page_aligned_buffer list -> int A key benefit of "system 5" is that the signature contains all the interesting information about `read` and `write`. It clearly states that they are expected to fail sometimes, and that the only errors on which it is reasonable to behave specially are a `Foo` returned by `read` or a `Bar` returned by `write`. `System 4` does not convey any of this information. >> Some nice combinators should be provided for using ('a, 'b) Result.t and >> ('a, 'b) Result.t Lwt. and for lifting an ('a, Foo.error) Result.t into >> an ('a, Bar.error) Result.t. >> >> Exceptions that escape their intended scope, should always be treated as >> a programming error. > > Yes, by definition. But what should the "intended scope" be, and how > do we ensure the producer and consumers of the exception agree? Exceptions should basically never delibrately cross module boundaries. They should certainly not be part of the exposed API of a library. By "exceptions that escape their scope" I essentially meant exceptions used in third-party APIs (e.g. Not_found produced by List.find), these should always be caught as early as possible and handled appropriately. Occasionally it is reasonable for an exception like "Invalid_argument" to be part of a library API, where the exception is not intended to be caught but merely to indicate that there has been a programmer error. It is also reasonable to use exceptions locally for control-flow, but again these should not escape into the visible API. Regards, Leo _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Fri Feb 13 17:00:58 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 13 Feb 2015 17:00:58 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YMJbp-0001C7-ES; Fri, 13 Feb 2015 17:00:53 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YMJbn-0001BZ-ML; Fri, 13 Feb 2015 17:00:51 +0000 Received: from [85.158.139.211] by server-9.bemta-5.messagelabs.com id 7F/22-02991-2CD2ED45; Fri, 13 Feb 2015 17:00:50 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-6.tower-206.messagelabs.com!1423846848!11854721!1 X-Originating-IP: [74.125.82.179] X-SpamReason: No, hits=2.5 required=7.0 tests=HTML_60_70,HTML_MESSAGE, SUSPICIOUS_RECIPS X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16945 invoked from network); 13 Feb 2015 17:00:50 -0000 Received: from mail-we0-f179.google.com (HELO mail-we0-f179.google.com) (74.125.82.179) by server-6.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 13 Feb 2015 17:00:50 -0000 Received: by mail-we0-f179.google.com with SMTP id u56so17772833wes.10; Fri, 13 Feb 2015 09:00:48 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:content-type:subject:message-id:date:to:mime-version; bh=VDbY9W7yhm+hO0WTSIHNarqbd8x71rsDdRNnW+2jMxE=; b=j6mWDkoUqhiVZUBbIZVUoSlDen7NMAi9FRfyToi5Qr7v7uVmUGarADP7Re3FB6N68x 6rBkwdHwKleK3cZJdogDX0jNkrgOvYAbEdC79PDobMDMlhPo9wqIkG+SbUMPtbuQSMv7 Utif5CC8HNh2QuenyGhw2xdETS0+B3AcxHBiq10SVelhAjXTh2YwOu1S0r07iu1e0Q1D 8t+0UamH67impQQNjUe0F1mRuxsDOwXMeRPS9PjeuIXGIO2okokIhg6rDC9hcL4YxMZU xzhCPVO3IFedqF5mwprcRBjPTN1PaHp1Nly60NJRLof4B4gKHB6145NKHlWfz2R+0MuK q+9A== X-Received: by 10.180.73.168 with SMTP id m8mr17873045wiv.22.1423846847899; Fri, 13 Feb 2015 09:00:47 -0800 (PST) Received: from [192.168.0.12] (97e5a0c2.skybroadband.com. [151.229.160.194]) by mx.google.com with ESMTPSA id l4sm3674920wiw.9.2015.02.13.09.00.46 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 13 Feb 2015 09:00:47 -0800 (PST) From: Lars Kurth Message-Id: <7ACF8382-5727-4BF7-919F-A7811FB7D6C7@gmail.com> Date: Fri, 13 Feb 2015 17:00:45 +0000 To: xen-devel , Xen API mailing list , mirageos-devel , Win-pv-devel@lists.xenproject.org, embedded-pv-devel@lists.xenproject.org Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) X-Mailer: Apple Mail (2.2070.6) Subject: [MirageOS-devel] 2015 GSoC Application : Tick X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============9058217648756453961==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============9058217648756453961== Content-Type: multipart/alternative; boundary="Apple-Mail=_AD1560DD-FD21-4F8F-9176-53CC7A3E93F1" --Apple-Mail=_AD1560DD-FD21-4F8F-9176-53CC7A3E93F1 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Just a quick note that I filled out the GSoC Mentoring Organisation = application today If you have not done so, please read and act on = http://lists.xenproject.org/archives/html/xen-devel/2015-02/msg00902.html = before Feb 22nd Best Regards Lars= --Apple-Mail=_AD1560DD-FD21-4F8F-9176-53CC7A3E93F1 Content-Transfer-Encoding: 7bit Content-Type: text/html; charset=us-ascii Just a quick note that I filled out the GSoC Mentoring Organisation application today

If you have not done so, please read and act on http://lists.xenproject.org/archives/html/xen-devel/2015-02/msg00902.html before Feb 22nd

Best Regards
Lars
--Apple-Mail=_AD1560DD-FD21-4F8F-9176-53CC7A3E93F1-- --===============9058217648756453961== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --===============9058217648756453961==-- From mirageos-devel-bounces@lists.xenproject.org Fri Feb 13 17:00:58 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 13 Feb 2015 17:00:58 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YMJbp-0001C7-ES; Fri, 13 Feb 2015 17:00:53 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YMJbn-0001BZ-ML; Fri, 13 Feb 2015 17:00:51 +0000 Received: from [85.158.139.211] by server-9.bemta-5.messagelabs.com id 7F/22-02991-2CD2ED45; Fri, 13 Feb 2015 17:00:50 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-6.tower-206.messagelabs.com!1423846848!11854721!1 X-Originating-IP: [74.125.82.179] X-SpamReason: No, hits=2.5 required=7.0 tests=HTML_60_70,HTML_MESSAGE, SUSPICIOUS_RECIPS X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16945 invoked from network); 13 Feb 2015 17:00:50 -0000 Received: from mail-we0-f179.google.com (HELO mail-we0-f179.google.com) (74.125.82.179) by server-6.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 13 Feb 2015 17:00:50 -0000 Received: by mail-we0-f179.google.com with SMTP id u56so17772833wes.10; Fri, 13 Feb 2015 09:00:48 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:content-type:subject:message-id:date:to:mime-version; bh=VDbY9W7yhm+hO0WTSIHNarqbd8x71rsDdRNnW+2jMxE=; b=j6mWDkoUqhiVZUBbIZVUoSlDen7NMAi9FRfyToi5Qr7v7uVmUGarADP7Re3FB6N68x 6rBkwdHwKleK3cZJdogDX0jNkrgOvYAbEdC79PDobMDMlhPo9wqIkG+SbUMPtbuQSMv7 Utif5CC8HNh2QuenyGhw2xdETS0+B3AcxHBiq10SVelhAjXTh2YwOu1S0r07iu1e0Q1D 8t+0UamH67impQQNjUe0F1mRuxsDOwXMeRPS9PjeuIXGIO2okokIhg6rDC9hcL4YxMZU xzhCPVO3IFedqF5mwprcRBjPTN1PaHp1Nly60NJRLof4B4gKHB6145NKHlWfz2R+0MuK q+9A== X-Received: by 10.180.73.168 with SMTP id m8mr17873045wiv.22.1423846847899; Fri, 13 Feb 2015 09:00:47 -0800 (PST) Received: from [192.168.0.12] (97e5a0c2.skybroadband.com. [151.229.160.194]) by mx.google.com with ESMTPSA id l4sm3674920wiw.9.2015.02.13.09.00.46 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 13 Feb 2015 09:00:47 -0800 (PST) From: Lars Kurth Message-Id: <7ACF8382-5727-4BF7-919F-A7811FB7D6C7@gmail.com> Date: Fri, 13 Feb 2015 17:00:45 +0000 To: xen-devel , Xen API mailing list , mirageos-devel , Win-pv-devel@lists.xenproject.org, embedded-pv-devel@lists.xenproject.org Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) X-Mailer: Apple Mail (2.2070.6) Subject: [MirageOS-devel] 2015 GSoC Application : Tick X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============9058217648756453961==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============9058217648756453961== Content-Type: multipart/alternative; boundary="Apple-Mail=_AD1560DD-FD21-4F8F-9176-53CC7A3E93F1" --Apple-Mail=_AD1560DD-FD21-4F8F-9176-53CC7A3E93F1 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Just a quick note that I filled out the GSoC Mentoring Organisation = application today If you have not done so, please read and act on = http://lists.xenproject.org/archives/html/xen-devel/2015-02/msg00902.html = before Feb 22nd Best Regards Lars= --Apple-Mail=_AD1560DD-FD21-4F8F-9176-53CC7A3E93F1 Content-Transfer-Encoding: 7bit Content-Type: text/html; charset=us-ascii Just a quick note that I filled out the GSoC Mentoring Organisation application today

If you have not done so, please read and act on http://lists.xenproject.org/archives/html/xen-devel/2015-02/msg00902.html before Feb 22nd

Best Regards
Lars
--Apple-Mail=_AD1560DD-FD21-4F8F-9176-53CC7A3E93F1-- --===============9058217648756453961== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --===============9058217648756453961==-- From mirageos-devel-bounces@lists.xenproject.org Fri Feb 13 17:24:01 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 13 Feb 2015 17:24:01 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YMJyA-0003hg-24; Fri, 13 Feb 2015 17:23:58 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YMJy8-0003gq-1W; Fri, 13 Feb 2015 17:23:56 +0000 Received: from [85.158.139.211] by server-17.bemta-5.messagelabs.com id 1A/45-03132-B233ED45; Fri, 13 Feb 2015 17:23:55 +0000 X-Env-Sender: amc79@cam.ac.uk X-Msg-Ref: server-8.tower-206.messagelabs.com!1423848234!11842122!1 X-Originating-IP: [131.111.8.152] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTMxLjExMS44LjE1MiA9PiA4MDU1Mw==\n X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6510 invoked from network); 13 Feb 2015 17:23:54 -0000 Received: from ppsw-52.csi.cam.ac.uk (HELO ppsw-52.csi.cam.ac.uk) (131.111.8.152) by server-8.tower-206.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 13 Feb 2015 17:23:54 -0000 X-Cam-AntiVirus: no malware found X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/ Received: from dhcp-172-17-154-113.eduroam.wireless.private.cam.ac.uk ([172.17.154.113]:53995) by ppsw-52.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.159]:587) with esmtpsa (PLAIN:amc79) (TLSv1:AES128-SHA:128) id 1YMJy6-0004sy-Cv (Exim 4.82_3-c0e5623) (return-path ); Fri, 13 Feb 2015 17:23:54 +0000 Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) From: Amir Chaudhry In-Reply-To: <7ACF8382-5727-4BF7-919F-A7811FB7D6C7@gmail.com> Date: Fri, 13 Feb 2015 17:23:53 +0000 Message-Id: <4C171AB3-8179-404F-B1E6-9E271D6365E5@cam.ac.uk> References: <7ACF8382-5727-4BF7-919F-A7811FB7D6C7@gmail.com> To: Lars Kurth X-Mailer: Apple Mail (2.1510) Cc: embedded-pv-devel@lists.xenproject.org, Win-pv-devel@lists.xenproject.org, Xen API mailing list , mirageos-devel , xen-devel Subject: Re: [MirageOS-devel] 2015 GSoC Application : Tick X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org MirageOS projects are done. I edited the Xen GSoC wiki page with one item that points to our curated list at: https://github.com/mirage/mirage-www/wiki/Pioneer-Projects AC On 13 Feb 2015, at 17:00, Lars Kurth wrote: > Just a quick note that I filled out the GSoC Mentoring Organisation application today > > If you have not done so, please read and act on http://lists.xenproject.org/archives/html/xen-devel/2015-02/msg00902.html before Feb 22nd > > Best Regards > Lars > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Fri Feb 13 17:24:01 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 13 Feb 2015 17:24:01 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YMJyA-0003hg-24; Fri, 13 Feb 2015 17:23:58 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YMJy8-0003gq-1W; Fri, 13 Feb 2015 17:23:56 +0000 Received: from [85.158.139.211] by server-17.bemta-5.messagelabs.com id 1A/45-03132-B233ED45; Fri, 13 Feb 2015 17:23:55 +0000 X-Env-Sender: amc79@cam.ac.uk X-Msg-Ref: server-8.tower-206.messagelabs.com!1423848234!11842122!1 X-Originating-IP: [131.111.8.152] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTMxLjExMS44LjE1MiA9PiA4MDU1Mw==\n X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6510 invoked from network); 13 Feb 2015 17:23:54 -0000 Received: from ppsw-52.csi.cam.ac.uk (HELO ppsw-52.csi.cam.ac.uk) (131.111.8.152) by server-8.tower-206.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 13 Feb 2015 17:23:54 -0000 X-Cam-AntiVirus: no malware found X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/ Received: from dhcp-172-17-154-113.eduroam.wireless.private.cam.ac.uk ([172.17.154.113]:53995) by ppsw-52.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.159]:587) with esmtpsa (PLAIN:amc79) (TLSv1:AES128-SHA:128) id 1YMJy6-0004sy-Cv (Exim 4.82_3-c0e5623) (return-path ); Fri, 13 Feb 2015 17:23:54 +0000 Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) From: Amir Chaudhry In-Reply-To: <7ACF8382-5727-4BF7-919F-A7811FB7D6C7@gmail.com> Date: Fri, 13 Feb 2015 17:23:53 +0000 Message-Id: <4C171AB3-8179-404F-B1E6-9E271D6365E5@cam.ac.uk> References: <7ACF8382-5727-4BF7-919F-A7811FB7D6C7@gmail.com> To: Lars Kurth X-Mailer: Apple Mail (2.1510) Cc: embedded-pv-devel@lists.xenproject.org, Win-pv-devel@lists.xenproject.org, Xen API mailing list , mirageos-devel , xen-devel Subject: Re: [MirageOS-devel] 2015 GSoC Application : Tick X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org MirageOS projects are done. I edited the Xen GSoC wiki page with one item that points to our curated list at: https://github.com/mirage/mirage-www/wiki/Pioneer-Projects AC On 13 Feb 2015, at 17:00, Lars Kurth wrote: > Just a quick note that I filled out the GSoC Mentoring Organisation application today > > If you have not done so, please read and act on http://lists.xenproject.org/archives/html/xen-devel/2015-02/msg00902.html before Feb 22nd > > Best Regards > Lars > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Sat Feb 14 09:27:45 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sat, 14 Feb 2015 09:27:45 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YMZ0h-0005yt-R2; Sat, 14 Feb 2015 09:27:35 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YMZ0h-0005yo-41 for mirageos-devel@lists.xenproject.org; Sat, 14 Feb 2015 09:27:35 +0000 Received: from [85.158.137.68] by server-9.bemta-3.messagelabs.com id 86/14-02995-5051FD45; Sat, 14 Feb 2015 09:27:33 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-5.tower-31.messagelabs.com!1423906052!11679198!1 X-Originating-IP: [5.153.225.51] X-SpamReason: No, hits=0.5 required=7.0 tests=MAILTO_TO_SPAM_ADDR, RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30968 invoked from network); 14 Feb 2015 09:27:33 -0000 Received: from bark.recoil.org (HELO bark.recoil.org) (5.153.225.51) by server-5.tower-31.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 14 Feb 2015 09:27:33 -0000 Received: from [192.168.1.69] (cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net [86.30.244.239]); by bark.recoil.org (OpenSMTPD) with ESMTPSA id 4c604251; TLS version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO; Sat, 14 Feb 2015 09:27:32 +0000 (GMT) Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) From: Anil Madhavapeddy In-Reply-To: <8B5157E9-7C05-4B16-A529-F9999E5E8D3C@cam.ac.uk> Date: Sat, 14 Feb 2015 09:27:35 +0000 Message-Id: <0E9C4EA7-B5FF-4BDE-99CE-C0570C380164@recoil.org> References: <8B5157E9-7C05-4B16-A529-F9999E5E8D3C@cam.ac.uk> To: Gregory Tsipenyuk X-Mailer: Apple Mail (2.2070.6) Cc: Thomas Gazagnaire , mirageos-devel Subject: Re: [MirageOS-devel] installing irmin on raspbery pi X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org T24gMTQgRmViIDIwMTUsIGF0IDA3OjM3LCBHcmVnb3J5IFRzaXBlbnl1ayA8Z3QzMDNAY2FtLmFj LnVrPiB3cm90ZToKPiAKPiBIaSBUaG9tYXMsCj4gCj4gSeKAmW0gdHJ5aW5nIHRvIGluc3RhbGwg SXJtaW4gb24gcnBpLiBXaGF0IGFwcGVhcnMgdG8gYmUgYSBzdGlja2luZyBwb2ludCBpcyDigJhs d3TigJkgcGFja2FnZS4gSW5zdGVhZCBvZiBsYXRlc3Qg4oCYbHd0LjIuNC434oCZIG9wYW0ga2Vl cHMgb24gdHJ5aW5nIHRvIGluc3RhbGwg4oCYbHd0LjIuNC414oCZLiBJIGluc3RhbGxlZCDigJhs d3QuMi40LjfigJkgbWFudWFsbHkgYW5kIHVwZGF0ZWQgYWxsIHJlcXVpcmVkIG1ldGFkYXRhIGZp bGVzIGJ1dCB0aGlzIGRvZXNu4oCZdCBoZWxwLiBJdCBzZWVtcyBsaWtlIEkgY2FuIGluc3RhbGwg KGF0IGxlYXN0IHNvIGZhcikgYWxsIHJlcXVpcmVkIHBhY2thZ2VzIG1hbnVhbGx5IGJ1dCBpdCBp cyBqdXN0IHBhaW5mdWwuIENhbiB5b3UgZ2l2ZSBhbmQgc3VnZ2VzdGlvbiBvbiBob3cgdGhpcyBt aWdodCBiZSBmaXhlZD8KClRoZSBiZXN0IHdheSB0byBkZWJ1ZyBjb25zdHJhaW50IHByb2JsZW1z IGxpa2UgdGhpcyBpcyB0byBmb3JjZSB0aGUgaW5zdGFsbGF0aW9uIG9mIHRoZSB0d28gcGFja2Fn ZXMgdGhhdCB5b3Ugd2FudCB3aXRoIHZlcnNpb25zIHNwZWNpZmllZC4gIFNvIHRyeToKCiAgICBv cGFtIGluc3RhbGwgbHd0LjIuNC43IGlybWluLjx2ZXJzaW9uPgoKYW5kIGV4YW1pbmUgb3IgcmVw b3J0IHRoZSBlcnJvci4KCi1hbmlsCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fCk1pcmFnZU9TLWRldmVsIG1haWxpbmcgbGlzdApNaXJhZ2VPUy1kZXZlbEBs aXN0cy54ZW5wcm9qZWN0Lm9yZwpodHRwOi8vbGlzdHMueGVucHJvamVjdC5vcmcvY2dpLWJpbi9t YWlsbWFuL2xpc3RpbmZvL21pcmFnZW9zLWRldmVsCg== From mirageos-devel-bounces@lists.xenproject.org Sat Feb 14 09:27:45 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sat, 14 Feb 2015 09:27:45 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YMZ0h-0005yt-R2; Sat, 14 Feb 2015 09:27:35 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YMZ0h-0005yo-41 for mirageos-devel@lists.xenproject.org; Sat, 14 Feb 2015 09:27:35 +0000 Received: from [85.158.137.68] by server-9.bemta-3.messagelabs.com id 86/14-02995-5051FD45; Sat, 14 Feb 2015 09:27:33 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-5.tower-31.messagelabs.com!1423906052!11679198!1 X-Originating-IP: [5.153.225.51] X-SpamReason: No, hits=0.5 required=7.0 tests=MAILTO_TO_SPAM_ADDR, RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30968 invoked from network); 14 Feb 2015 09:27:33 -0000 Received: from bark.recoil.org (HELO bark.recoil.org) (5.153.225.51) by server-5.tower-31.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 14 Feb 2015 09:27:33 -0000 Received: from [192.168.1.69] (cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net [86.30.244.239]); by bark.recoil.org (OpenSMTPD) with ESMTPSA id 4c604251; TLS version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO; Sat, 14 Feb 2015 09:27:32 +0000 (GMT) Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) From: Anil Madhavapeddy In-Reply-To: <8B5157E9-7C05-4B16-A529-F9999E5E8D3C@cam.ac.uk> Date: Sat, 14 Feb 2015 09:27:35 +0000 Message-Id: <0E9C4EA7-B5FF-4BDE-99CE-C0570C380164@recoil.org> References: <8B5157E9-7C05-4B16-A529-F9999E5E8D3C@cam.ac.uk> To: Gregory Tsipenyuk X-Mailer: Apple Mail (2.2070.6) Cc: Thomas Gazagnaire , mirageos-devel Subject: Re: [MirageOS-devel] installing irmin on raspbery pi X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org T24gMTQgRmViIDIwMTUsIGF0IDA3OjM3LCBHcmVnb3J5IFRzaXBlbnl1ayA8Z3QzMDNAY2FtLmFj LnVrPiB3cm90ZToKPiAKPiBIaSBUaG9tYXMsCj4gCj4gSeKAmW0gdHJ5aW5nIHRvIGluc3RhbGwg SXJtaW4gb24gcnBpLiBXaGF0IGFwcGVhcnMgdG8gYmUgYSBzdGlja2luZyBwb2ludCBpcyDigJhs d3TigJkgcGFja2FnZS4gSW5zdGVhZCBvZiBsYXRlc3Qg4oCYbHd0LjIuNC434oCZIG9wYW0ga2Vl cHMgb24gdHJ5aW5nIHRvIGluc3RhbGwg4oCYbHd0LjIuNC414oCZLiBJIGluc3RhbGxlZCDigJhs d3QuMi40LjfigJkgbWFudWFsbHkgYW5kIHVwZGF0ZWQgYWxsIHJlcXVpcmVkIG1ldGFkYXRhIGZp bGVzIGJ1dCB0aGlzIGRvZXNu4oCZdCBoZWxwLiBJdCBzZWVtcyBsaWtlIEkgY2FuIGluc3RhbGwg KGF0IGxlYXN0IHNvIGZhcikgYWxsIHJlcXVpcmVkIHBhY2thZ2VzIG1hbnVhbGx5IGJ1dCBpdCBp cyBqdXN0IHBhaW5mdWwuIENhbiB5b3UgZ2l2ZSBhbmQgc3VnZ2VzdGlvbiBvbiBob3cgdGhpcyBt aWdodCBiZSBmaXhlZD8KClRoZSBiZXN0IHdheSB0byBkZWJ1ZyBjb25zdHJhaW50IHByb2JsZW1z IGxpa2UgdGhpcyBpcyB0byBmb3JjZSB0aGUgaW5zdGFsbGF0aW9uIG9mIHRoZSB0d28gcGFja2Fn ZXMgdGhhdCB5b3Ugd2FudCB3aXRoIHZlcnNpb25zIHNwZWNpZmllZC4gIFNvIHRyeToKCiAgICBv cGFtIGluc3RhbGwgbHd0LjIuNC43IGlybWluLjx2ZXJzaW9uPgoKYW5kIGV4YW1pbmUgb3IgcmVw b3J0IHRoZSBlcnJvci4KCi1hbmlsCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fCk1pcmFnZU9TLWRldmVsIG1haWxpbmcgbGlzdApNaXJhZ2VPUy1kZXZlbEBs aXN0cy54ZW5wcm9qZWN0Lm9yZwpodHRwOi8vbGlzdHMueGVucHJvamVjdC5vcmcvY2dpLWJpbi9t YWlsbWFuL2xpc3RpbmZvL21pcmFnZW9zLWRldmVsCg== From mirageos-devel-bounces@lists.xenproject.org Sat Feb 14 09:31:25 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sat, 14 Feb 2015 09:31:25 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YMZ4P-0006CI-8Y; Sat, 14 Feb 2015 09:31:25 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YMZ4O-0006AB-KF for mirageos-devel@lists.xenproject.org; Sat, 14 Feb 2015 09:31:24 +0000 Received: from [85.158.143.35] by server-2.bemta-4.messagelabs.com id F8/9E-02830-BE51FD45; Sat, 14 Feb 2015 09:31:23 +0000 X-Env-Sender: gt303@cam.ac.uk X-Msg-Ref: server-10.tower-21.messagelabs.com!1423906282!11870934!1 X-Originating-IP: [131.111.8.140] X-SpamReason: No, hits=0.3 required=7.0 tests=MAILTO_TO_SPAM_ADDR X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29303 invoked from network); 14 Feb 2015 09:31:22 -0000 Received: from ppsw-40.csi.cam.ac.uk (HELO ppsw-40.csi.cam.ac.uk) (131.111.8.140) by server-10.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 14 Feb 2015 09:31:22 -0000 X-Cam-AntiVirus: no malware found X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/ Received: from [217.137.224.42] (port=61804 helo=[192.168.1.104]) by ppsw-40.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.156]:587) with esmtpsa (PLAIN:gt303) (TLSv1:DHE-RSA-AES256-SHA:256) id 1YMZ4L-0003cb-mB (Exim 4.82_3-c0e5623) (return-path ); Sat, 14 Feb 2015 09:31:22 +0000 Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) From: Gregory Tsipenyuk In-Reply-To: <0E9C4EA7-B5FF-4BDE-99CE-C0570C380164@recoil.org> Date: Sat, 14 Feb 2015 09:31:21 +0000 Message-Id: <3F69AE1F-6F55-48BF-945D-EB764CE48D61@cam.ac.uk> References: <8B5157E9-7C05-4B16-A529-F9999E5E8D3C@cam.ac.uk> <0E9C4EA7-B5FF-4BDE-99CE-C0570C380164@recoil.org> To: Anil Madhavapeddy X-Mailer: Apple Mail (2.2070.6) Cc: Thomas Gazagnaire , mirageos-devel Subject: Re: [MirageOS-devel] installing irmin on raspbery pi X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org VGhhbmtzLCBnb29kIHRvIGtub3chCgpJdCBsb29rcyBsaWtlIHRoaXMgaXNzdWUgZ290IGZpeGVk IGFmdGVyIGluc3RhbGxpbmcgYXNwY3VkIGFuZCB0aGVuIG9wYW0gdXBncmFkZS4KCkdyZWdvcnkK Cj4gT24gRmViIDE0LCAyMDE1LCBhdCA5OjI3IEFNLCBBbmlsIE1hZGhhdmFwZWRkeSA8YW5pbEBy ZWNvaWwub3JnPiB3cm90ZToKPiAKPiBPbiAxNCBGZWIgMjAxNSwgYXQgMDc6MzcsIEdyZWdvcnkg VHNpcGVueXVrIDxndDMwM0BjYW0uYWMudWs+IHdyb3RlOgo+PiAKPj4gSGkgVGhvbWFzLAo+PiAK Pj4gSeKAmW0gdHJ5aW5nIHRvIGluc3RhbGwgSXJtaW4gb24gcnBpLiBXaGF0IGFwcGVhcnMgdG8g YmUgYSBzdGlja2luZyBwb2ludCBpcyDigJhsd3TigJkgcGFja2FnZS4gSW5zdGVhZCBvZiBsYXRl c3Qg4oCYbHd0LjIuNC434oCZIG9wYW0ga2VlcHMgb24gdHJ5aW5nIHRvIGluc3RhbGwg4oCYbHd0 LjIuNC414oCZLiBJIGluc3RhbGxlZCDigJhsd3QuMi40LjfigJkgbWFudWFsbHkgYW5kIHVwZGF0 ZWQgYWxsIHJlcXVpcmVkIG1ldGFkYXRhIGZpbGVzIGJ1dCB0aGlzIGRvZXNu4oCZdCBoZWxwLiBJ dCBzZWVtcyBsaWtlIEkgY2FuIGluc3RhbGwgKGF0IGxlYXN0IHNvIGZhcikgYWxsIHJlcXVpcmVk IHBhY2thZ2VzIG1hbnVhbGx5IGJ1dCBpdCBpcyBqdXN0IHBhaW5mdWwuIENhbiB5b3UgZ2l2ZSBh bmQgc3VnZ2VzdGlvbiBvbiBob3cgdGhpcyBtaWdodCBiZSBmaXhlZD8KPiAKPiBUaGUgYmVzdCB3 YXkgdG8gZGVidWcgY29uc3RyYWludCBwcm9ibGVtcyBsaWtlIHRoaXMgaXMgdG8gZm9yY2UgdGhl IGluc3RhbGxhdGlvbiBvZiB0aGUgdHdvIHBhY2thZ2VzIHRoYXQgeW91IHdhbnQgd2l0aCB2ZXJz aW9ucyBzcGVjaWZpZWQuICBTbyB0cnk6Cj4gCj4gICAgb3BhbSBpbnN0YWxsIGx3dC4yLjQuNyBp cm1pbi48dmVyc2lvbj4KPiAKPiBhbmQgZXhhbWluZSBvciByZXBvcnQgdGhlIGVycm9yLgo+IAo+ IC1hbmlsCgoKX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18K TWlyYWdlT1MtZGV2ZWwgbWFpbGluZyBsaXN0Ck1pcmFnZU9TLWRldmVsQGxpc3RzLnhlbnByb2pl Y3Qub3JnCmh0dHA6Ly9saXN0cy54ZW5wcm9qZWN0Lm9yZy9jZ2ktYmluL21haWxtYW4vbGlzdGlu Zm8vbWlyYWdlb3MtZGV2ZWwK From mirageos-devel-bounces@lists.xenproject.org Sat Feb 14 09:31:25 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sat, 14 Feb 2015 09:31:25 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YMZ4P-0006CI-8Y; Sat, 14 Feb 2015 09:31:25 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YMZ4O-0006AB-KF for mirageos-devel@lists.xenproject.org; Sat, 14 Feb 2015 09:31:24 +0000 Received: from [85.158.143.35] by server-2.bemta-4.messagelabs.com id F8/9E-02830-BE51FD45; Sat, 14 Feb 2015 09:31:23 +0000 X-Env-Sender: gt303@cam.ac.uk X-Msg-Ref: server-10.tower-21.messagelabs.com!1423906282!11870934!1 X-Originating-IP: [131.111.8.140] X-SpamReason: No, hits=0.3 required=7.0 tests=MAILTO_TO_SPAM_ADDR X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29303 invoked from network); 14 Feb 2015 09:31:22 -0000 Received: from ppsw-40.csi.cam.ac.uk (HELO ppsw-40.csi.cam.ac.uk) (131.111.8.140) by server-10.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 14 Feb 2015 09:31:22 -0000 X-Cam-AntiVirus: no malware found X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/ Received: from [217.137.224.42] (port=61804 helo=[192.168.1.104]) by ppsw-40.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.156]:587) with esmtpsa (PLAIN:gt303) (TLSv1:DHE-RSA-AES256-SHA:256) id 1YMZ4L-0003cb-mB (Exim 4.82_3-c0e5623) (return-path ); Sat, 14 Feb 2015 09:31:22 +0000 Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) From: Gregory Tsipenyuk In-Reply-To: <0E9C4EA7-B5FF-4BDE-99CE-C0570C380164@recoil.org> Date: Sat, 14 Feb 2015 09:31:21 +0000 Message-Id: <3F69AE1F-6F55-48BF-945D-EB764CE48D61@cam.ac.uk> References: <8B5157E9-7C05-4B16-A529-F9999E5E8D3C@cam.ac.uk> <0E9C4EA7-B5FF-4BDE-99CE-C0570C380164@recoil.org> To: Anil Madhavapeddy X-Mailer: Apple Mail (2.2070.6) Cc: Thomas Gazagnaire , mirageos-devel Subject: Re: [MirageOS-devel] installing irmin on raspbery pi X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org VGhhbmtzLCBnb29kIHRvIGtub3chCgpJdCBsb29rcyBsaWtlIHRoaXMgaXNzdWUgZ290IGZpeGVk IGFmdGVyIGluc3RhbGxpbmcgYXNwY3VkIGFuZCB0aGVuIG9wYW0gdXBncmFkZS4KCkdyZWdvcnkK Cj4gT24gRmViIDE0LCAyMDE1LCBhdCA5OjI3IEFNLCBBbmlsIE1hZGhhdmFwZWRkeSA8YW5pbEBy ZWNvaWwub3JnPiB3cm90ZToKPiAKPiBPbiAxNCBGZWIgMjAxNSwgYXQgMDc6MzcsIEdyZWdvcnkg VHNpcGVueXVrIDxndDMwM0BjYW0uYWMudWs+IHdyb3RlOgo+PiAKPj4gSGkgVGhvbWFzLAo+PiAK Pj4gSeKAmW0gdHJ5aW5nIHRvIGluc3RhbGwgSXJtaW4gb24gcnBpLiBXaGF0IGFwcGVhcnMgdG8g YmUgYSBzdGlja2luZyBwb2ludCBpcyDigJhsd3TigJkgcGFja2FnZS4gSW5zdGVhZCBvZiBsYXRl c3Qg4oCYbHd0LjIuNC434oCZIG9wYW0ga2VlcHMgb24gdHJ5aW5nIHRvIGluc3RhbGwg4oCYbHd0 LjIuNC414oCZLiBJIGluc3RhbGxlZCDigJhsd3QuMi40LjfigJkgbWFudWFsbHkgYW5kIHVwZGF0 ZWQgYWxsIHJlcXVpcmVkIG1ldGFkYXRhIGZpbGVzIGJ1dCB0aGlzIGRvZXNu4oCZdCBoZWxwLiBJ dCBzZWVtcyBsaWtlIEkgY2FuIGluc3RhbGwgKGF0IGxlYXN0IHNvIGZhcikgYWxsIHJlcXVpcmVk IHBhY2thZ2VzIG1hbnVhbGx5IGJ1dCBpdCBpcyBqdXN0IHBhaW5mdWwuIENhbiB5b3UgZ2l2ZSBh bmQgc3VnZ2VzdGlvbiBvbiBob3cgdGhpcyBtaWdodCBiZSBmaXhlZD8KPiAKPiBUaGUgYmVzdCB3 YXkgdG8gZGVidWcgY29uc3RyYWludCBwcm9ibGVtcyBsaWtlIHRoaXMgaXMgdG8gZm9yY2UgdGhl IGluc3RhbGxhdGlvbiBvZiB0aGUgdHdvIHBhY2thZ2VzIHRoYXQgeW91IHdhbnQgd2l0aCB2ZXJz aW9ucyBzcGVjaWZpZWQuICBTbyB0cnk6Cj4gCj4gICAgb3BhbSBpbnN0YWxsIGx3dC4yLjQuNyBp cm1pbi48dmVyc2lvbj4KPiAKPiBhbmQgZXhhbWluZSBvciByZXBvcnQgdGhlIGVycm9yLgo+IAo+ IC1hbmlsCgoKX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18K TWlyYWdlT1MtZGV2ZWwgbWFpbGluZyBsaXN0Ck1pcmFnZU9TLWRldmVsQGxpc3RzLnhlbnByb2pl Y3Qub3JnCmh0dHA6Ly9saXN0cy54ZW5wcm9qZWN0Lm9yZy9jZ2ktYmluL21haWxtYW4vbGlzdGlu Zm8vbWlyYWdlb3MtZGV2ZWwK From mirageos-devel-bounces@lists.xenproject.org Sat Feb 14 22:42:46 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sat, 14 Feb 2015 22:42:46 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YMlQ5-0008AI-S7; Sat, 14 Feb 2015 22:42:37 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YMlQ5-0008AD-6c for MirageOS-devel@lists.xenproject.org; Sat, 14 Feb 2015 22:42:37 +0000 Received: from [85.158.143.35] by server-3.bemta-4.messagelabs.com id 28/C6-09822-C5FCFD45; Sat, 14 Feb 2015 22:42:36 +0000 X-Env-Sender: richard.mortier@gmail.com X-Msg-Ref: server-12.tower-21.messagelabs.com!1423953755!11919182!1 X-Originating-IP: [209.85.216.169] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 9570 invoked from network); 14 Feb 2015 22:42:35 -0000 Received: from mail-qc0-f169.google.com (HELO mail-qc0-f169.google.com) (209.85.216.169) by server-12.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 14 Feb 2015 22:42:35 -0000 Received: by mail-qc0-f169.google.com with SMTP id m20so19055497qcx.0 for ; Sat, 14 Feb 2015 14:42:34 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=mime-version:date:message-id:subject:from:to:cc:content-type; bh=LfmMvnz6SpeklgjTLP82t6I65XGokvlAQ5dSS8T2whQ=; b=CAqrQuJavshDS3PibMADu+sJ4NW83bPrn+HeV6jflwpxCEksyYPGhkzKJp4jxlBKXe JFh1fF99NyhDQuOfifnAa+1++zQ/74evfJyhhqdB068yeZ7rJcgWao1BtSHKXEFOAxvz d4rg+UDDBHSqAL8HnLdALPMLb1p7aNaJCNMjwDBQKiExvTb4FIN5QsQUlIcT52qTzcwC MvLcRgmkrW3yd1g8MP2mC8z8UammE0JZl/C7oG/ZgG1xX3ccrgNizbxU04XX97XnF0U3 iXqz1pzHG2ZgzX8NIwXTEmK1OQa0fb7n6BUyBoBUpHIjCPfWVTU30cG+KQ0sv99tfsOK 2Oog== X-Received: by 10.140.86.75 with SMTP id o69mr39809899qgd.98.1423953754892; Sat, 14 Feb 2015 14:42:34 -0800 (PST) Received: from mail-qg0-f46.google.com (mail-qg0-f46.google.com. [209.85.192.46]) by mx.google.com with ESMTPSA id v65sm10343131qgd.20.2015.02.14.14.42.34 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 14 Feb 2015 14:42:34 -0800 (PST) Received: by mail-qg0-f46.google.com with SMTP id z107so18469230qgd.5 for ; Sat, 14 Feb 2015 14:42:34 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.140.93.195 with SMTP id d61mr23601115qge.48.1423953754337; Sat, 14 Feb 2015 14:42:34 -0800 (PST) Received: by 10.140.92.245 with HTTP; Sat, 14 Feb 2015 14:42:34 -0800 (PST) Date: Sat, 14 Feb 2015 22:42:34 +0000 Message-ID: From: Richard Mortier To: mirageos-devel Subject: [MirageOS-devel] performance regression tests X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org it has been said that regression testing, particularly performance regression testing, is something that we should probably get better at... :) so-- masoud has started rebuilding the `mirage-perf` repo to provide some simple, standard performance regression tests. the idea is to provide a battery of tests that can be fired off against specific versions of libraries, ultimately in tandem. there're several TODO items already, so this is clearly a work in progress, but if anyone's got any thoughts/suggestions already, please pass them on either to the list, or file them as issues against the repo at https://github.com/koleini/mirage-perf in particular, if anyone would like to try using the current test setup, against mirage-net-xen only at the moment, please do pass on any feedback! thanks! -- Richard Mortier richard.mortier@cl.cam.ac.uk _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Sat Feb 14 22:42:46 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sat, 14 Feb 2015 22:42:46 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YMlQ5-0008AI-S7; Sat, 14 Feb 2015 22:42:37 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YMlQ5-0008AD-6c for MirageOS-devel@lists.xenproject.org; Sat, 14 Feb 2015 22:42:37 +0000 Received: from [85.158.143.35] by server-3.bemta-4.messagelabs.com id 28/C6-09822-C5FCFD45; Sat, 14 Feb 2015 22:42:36 +0000 X-Env-Sender: richard.mortier@gmail.com X-Msg-Ref: server-12.tower-21.messagelabs.com!1423953755!11919182!1 X-Originating-IP: [209.85.216.169] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 9570 invoked from network); 14 Feb 2015 22:42:35 -0000 Received: from mail-qc0-f169.google.com (HELO mail-qc0-f169.google.com) (209.85.216.169) by server-12.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 14 Feb 2015 22:42:35 -0000 Received: by mail-qc0-f169.google.com with SMTP id m20so19055497qcx.0 for ; Sat, 14 Feb 2015 14:42:34 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=mime-version:date:message-id:subject:from:to:cc:content-type; bh=LfmMvnz6SpeklgjTLP82t6I65XGokvlAQ5dSS8T2whQ=; b=CAqrQuJavshDS3PibMADu+sJ4NW83bPrn+HeV6jflwpxCEksyYPGhkzKJp4jxlBKXe JFh1fF99NyhDQuOfifnAa+1++zQ/74evfJyhhqdB068yeZ7rJcgWao1BtSHKXEFOAxvz d4rg+UDDBHSqAL8HnLdALPMLb1p7aNaJCNMjwDBQKiExvTb4FIN5QsQUlIcT52qTzcwC MvLcRgmkrW3yd1g8MP2mC8z8UammE0JZl/C7oG/ZgG1xX3ccrgNizbxU04XX97XnF0U3 iXqz1pzHG2ZgzX8NIwXTEmK1OQa0fb7n6BUyBoBUpHIjCPfWVTU30cG+KQ0sv99tfsOK 2Oog== X-Received: by 10.140.86.75 with SMTP id o69mr39809899qgd.98.1423953754892; Sat, 14 Feb 2015 14:42:34 -0800 (PST) Received: from mail-qg0-f46.google.com (mail-qg0-f46.google.com. [209.85.192.46]) by mx.google.com with ESMTPSA id v65sm10343131qgd.20.2015.02.14.14.42.34 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 14 Feb 2015 14:42:34 -0800 (PST) Received: by mail-qg0-f46.google.com with SMTP id z107so18469230qgd.5 for ; Sat, 14 Feb 2015 14:42:34 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.140.93.195 with SMTP id d61mr23601115qge.48.1423953754337; Sat, 14 Feb 2015 14:42:34 -0800 (PST) Received: by 10.140.92.245 with HTTP; Sat, 14 Feb 2015 14:42:34 -0800 (PST) Date: Sat, 14 Feb 2015 22:42:34 +0000 Message-ID: From: Richard Mortier To: mirageos-devel Subject: [MirageOS-devel] performance regression tests X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org it has been said that regression testing, particularly performance regression testing, is something that we should probably get better at... :) so-- masoud has started rebuilding the `mirage-perf` repo to provide some simple, standard performance regression tests. the idea is to provide a battery of tests that can be fired off against specific versions of libraries, ultimately in tandem. there're several TODO items already, so this is clearly a work in progress, but if anyone's got any thoughts/suggestions already, please pass them on either to the list, or file them as issues against the repo at https://github.com/koleini/mirage-perf in particular, if anyone would like to try using the current test setup, against mirage-net-xen only at the moment, please do pass on any feedback! thanks! -- Richard Mortier richard.mortier@cl.cam.ac.uk _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Sun Feb 15 11:15:23 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 15 Feb 2015 11:15:23 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YMxAS-0003zS-9z; Sun, 15 Feb 2015 11:15:16 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YMxAQ-0003zN-8G for MirageOS-devel@lists.xenproject.org; Sun, 15 Feb 2015 11:15:14 +0000 Received: from [85.158.143.35] by server-3.bemta-4.messagelabs.com id 9B/BC-09822-1CF70E45; Sun, 15 Feb 2015 11:15:13 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-11.tower-21.messagelabs.com!1423998911!11951664!1 X-Originating-IP: [5.153.225.51] X-SpamReason: No, hits=0.2 required=7.0 tests=RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2674 invoked from network); 15 Feb 2015 11:15:12 -0000 Received: from bark.recoil.org (HELO bark.recoil.org) (5.153.225.51) by server-11.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 15 Feb 2015 11:15:12 -0000 Received: from [192.168.1.69] (cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net [86.30.244.239]); by bark.recoil.org (OpenSMTPD) with ESMTPSA id 9ee49d1a; TLS version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO; Sun, 15 Feb 2015 11:15:09 +0000 (GMT) Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) From: Anil Madhavapeddy In-Reply-To: Date: Sun, 15 Feb 2015 11:15:08 +0000 Message-Id: References: To: Richard Mortier X-Mailer: Apple Mail (2.2070.6) Cc: mirageos-devel Subject: Re: [MirageOS-devel] performance regression tests X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org This is great to see -- thanks for working on this Masoud! In particular, having even a simple iperf test would let us test several interesting combinations straight away: - vary OCaml version (4.01 vs 4.02 is now supported), and there is an experimental inlining branch in 4.03dev that could directly be tested using this infrastructure. - evaluate the impact of some features incoming such as the open RFC for checksum offload. In terms of immediate feedback, I'd request a version that just does iperf so that it has no dependencies on the host dom0 kernel. See: https://github.com/mirage/mirage-skeleton/pull/75 For this repository, what is the supported dom0 kernel that is expected? The script tried to insmod a kmod that I didn't have. Once there's even a minimal test, I'd like to recreate it on an infrastructure machine in Cambridge and have it run daily via cron alongside the is-mirage-broken scripts. cheers, Anil > On 14 Feb 2015, at 22:42, Richard Mortier wrote: > > it has been said that regression testing, particularly performance > regression testing, is something that we should probably get better > at... :) > > so-- masoud has started rebuilding the `mirage-perf` repo to provide > some simple, standard performance regression tests. the idea is to > provide a battery of tests that can be fired off against specific > versions of libraries, ultimately in tandem. > > there're several TODO items already, so this is clearly a work in > progress, but if anyone's got any thoughts/suggestions already, please > pass them on either to the list, or file them as issues against the > repo at https://github.com/koleini/mirage-perf > > in particular, if anyone would like to try using the current test > setup, against mirage-net-xen only at the moment, please do pass on > any feedback! > > thanks! > > -- > Richard Mortier > richard.mortier@cl.cam.ac.uk > > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Sun Feb 15 11:15:23 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 15 Feb 2015 11:15:23 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YMxAS-0003zS-9z; Sun, 15 Feb 2015 11:15:16 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YMxAQ-0003zN-8G for MirageOS-devel@lists.xenproject.org; Sun, 15 Feb 2015 11:15:14 +0000 Received: from [85.158.143.35] by server-3.bemta-4.messagelabs.com id 9B/BC-09822-1CF70E45; Sun, 15 Feb 2015 11:15:13 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-11.tower-21.messagelabs.com!1423998911!11951664!1 X-Originating-IP: [5.153.225.51] X-SpamReason: No, hits=0.2 required=7.0 tests=RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2674 invoked from network); 15 Feb 2015 11:15:12 -0000 Received: from bark.recoil.org (HELO bark.recoil.org) (5.153.225.51) by server-11.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 15 Feb 2015 11:15:12 -0000 Received: from [192.168.1.69] (cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net [86.30.244.239]); by bark.recoil.org (OpenSMTPD) with ESMTPSA id 9ee49d1a; TLS version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO; Sun, 15 Feb 2015 11:15:09 +0000 (GMT) Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) From: Anil Madhavapeddy In-Reply-To: Date: Sun, 15 Feb 2015 11:15:08 +0000 Message-Id: References: To: Richard Mortier X-Mailer: Apple Mail (2.2070.6) Cc: mirageos-devel Subject: Re: [MirageOS-devel] performance regression tests X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org This is great to see -- thanks for working on this Masoud! In particular, having even a simple iperf test would let us test several interesting combinations straight away: - vary OCaml version (4.01 vs 4.02 is now supported), and there is an experimental inlining branch in 4.03dev that could directly be tested using this infrastructure. - evaluate the impact of some features incoming such as the open RFC for checksum offload. In terms of immediate feedback, I'd request a version that just does iperf so that it has no dependencies on the host dom0 kernel. See: https://github.com/mirage/mirage-skeleton/pull/75 For this repository, what is the supported dom0 kernel that is expected? The script tried to insmod a kmod that I didn't have. Once there's even a minimal test, I'd like to recreate it on an infrastructure machine in Cambridge and have it run daily via cron alongside the is-mirage-broken scripts. cheers, Anil > On 14 Feb 2015, at 22:42, Richard Mortier wrote: > > it has been said that regression testing, particularly performance > regression testing, is something that we should probably get better > at... :) > > so-- masoud has started rebuilding the `mirage-perf` repo to provide > some simple, standard performance regression tests. the idea is to > provide a battery of tests that can be fired off against specific > versions of libraries, ultimately in tandem. > > there're several TODO items already, so this is clearly a work in > progress, but if anyone's got any thoughts/suggestions already, please > pass them on either to the list, or file them as issues against the > repo at https://github.com/koleini/mirage-perf > > in particular, if anyone would like to try using the current test > setup, against mirage-net-xen only at the moment, please do pass on > any feedback! > > thanks! > > -- > Richard Mortier > richard.mortier@cl.cam.ac.uk > > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Sun Feb 15 11:19:59 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 15 Feb 2015 11:19:59 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YMxF1-00041i-R5; Sun, 15 Feb 2015 11:19:59 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YMxF1-00041d-40 for MirageOS-devel@lists.xenproject.org; Sun, 15 Feb 2015 11:19:59 +0000 Received: from [85.158.139.211] by server-3.bemta-5.messagelabs.com id AE/3A-02994-ED080E45; Sun, 15 Feb 2015 11:19:58 +0000 X-Env-Sender: richard.mortier@gmail.com X-Msg-Ref: server-15.tower-206.messagelabs.com!1423999196!8665883!1 X-Originating-IP: [209.85.216.176] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7682 invoked from network); 15 Feb 2015 11:19:57 -0000 Received: from mail-qc0-f176.google.com (HELO mail-qc0-f176.google.com) (209.85.216.176) by server-15.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 15 Feb 2015 11:19:57 -0000 Received: by mail-qc0-f176.google.com with SMTP id b13so14423978qcw.7 for ; Sun, 15 Feb 2015 03:19:56 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Zv3BOmMdQigVRmTOhzi5spgvlRvASMznsCYj/Dsi/is=; b=dpBlIeWiBAuWys4JjCwSDtp7MoJyVINAcnkZQtW7W/Es7mTNiBpxaznPIld/IM0Jfv QdAMPwY7oOVT4V65YQ7MtxZlMU0NjBALulRegokdTPNtUDOKjWQTdP4aW2ybRYVb1Dnh rRF71ETRW4N54J9pGRgvdds0bw4jkhofkBMWAzrnZrJXTl99P6seoD0GX7aiaO82/AJa 9WwvdeZL3rIZoBzKPTKwn/SJx/TdPw3hYKpIFLo9CPD+pwA2Q0t/ajWtLhr/cf3rJ3Ee WQy3ir0bifJignuB+axb67asdLMH1SbmbYnpgu/X3FaK82cHDMmwzzHNl+WZmB1WueNI oqDg== X-Received: by 10.140.145.3 with SMTP id 3mr17451090qhr.42.1423999196439; Sun, 15 Feb 2015 03:19:56 -0800 (PST) Received: from mail-qa0-f44.google.com (mail-qa0-f44.google.com. [209.85.216.44]) by mx.google.com with ESMTPSA id 79sm11421064qgn.36.2015.02.15.03.19.55 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 15 Feb 2015 03:19:56 -0800 (PST) Received: by mail-qa0-f44.google.com with SMTP id n8so18520690qaq.3 for ; Sun, 15 Feb 2015 03:19:55 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.140.202.144 with SMTP id x138mr17083868qha.14.1423999195442; Sun, 15 Feb 2015 03:19:55 -0800 (PST) Received: by 10.140.92.245 with HTTP; Sun, 15 Feb 2015 03:19:55 -0800 (PST) In-Reply-To: References: Date: Sun, 15 Feb 2015 11:19:55 +0000 Message-ID: From: Richard Mortier To: Anil Madhavapeddy Cc: mirageos-devel Subject: Re: [MirageOS-devel] performance regression tests X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 15 February 2015 at 11:15, Anil Madhavapeddy wrote: > This is great to see -- thanks for working on this Masoud! > > In particular, having even a simple iperf test would let us test > several interesting combinations straight away: > > - vary OCaml version (4.01 vs 4.02 is now supported), and there > is an experimental inlining branch in 4.03dev that could directly > be tested using this infrastructure. ok-- so i guess that needs a switch/env var to specify the `opam switch` to use? > - evaluate the impact of some features incoming such as the open > RFC for checksum offload. how are they specified -- as a PR? in which case, masoud-- i guess that https://help.github.com/articles/checking-out-pull-requests-locally/ is a starting point for how to specify a particular PR rather than simply a commit rev. > In terms of immediate feedback, I'd request a version that just does > iperf so that it has no dependencies on the host dom0 kernel. > See: https://github.com/mirage/mirage-skeleton/pull/75 just to be clear -- you mean does iperf via unikernels, ie., all the tests that are executed should also be unikernels rather than standard tools so that we don't take dependencies on an underlying platform like the dom0? > For this repository, what is the supported dom0 kernel that is expected? > The script tried to insmod a kmod that I didn't have. over to masoud... > Once there's even a minimal test, I'd like to recreate it on an > infrastructure machine in Cambridge and have it run daily via cron > alongside the is-mirage-broken scripts. cool... (one day i must learn about the cambridge infrastructure machines :) -- Richard Mortier richard.mortier@cl.cam.ac.uk _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Sun Feb 15 11:19:59 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 15 Feb 2015 11:19:59 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YMxF1-00041i-R5; Sun, 15 Feb 2015 11:19:59 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YMxF1-00041d-40 for MirageOS-devel@lists.xenproject.org; Sun, 15 Feb 2015 11:19:59 +0000 Received: from [85.158.139.211] by server-3.bemta-5.messagelabs.com id AE/3A-02994-ED080E45; Sun, 15 Feb 2015 11:19:58 +0000 X-Env-Sender: richard.mortier@gmail.com X-Msg-Ref: server-15.tower-206.messagelabs.com!1423999196!8665883!1 X-Originating-IP: [209.85.216.176] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7682 invoked from network); 15 Feb 2015 11:19:57 -0000 Received: from mail-qc0-f176.google.com (HELO mail-qc0-f176.google.com) (209.85.216.176) by server-15.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 15 Feb 2015 11:19:57 -0000 Received: by mail-qc0-f176.google.com with SMTP id b13so14423978qcw.7 for ; Sun, 15 Feb 2015 03:19:56 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Zv3BOmMdQigVRmTOhzi5spgvlRvASMznsCYj/Dsi/is=; b=dpBlIeWiBAuWys4JjCwSDtp7MoJyVINAcnkZQtW7W/Es7mTNiBpxaznPIld/IM0Jfv QdAMPwY7oOVT4V65YQ7MtxZlMU0NjBALulRegokdTPNtUDOKjWQTdP4aW2ybRYVb1Dnh rRF71ETRW4N54J9pGRgvdds0bw4jkhofkBMWAzrnZrJXTl99P6seoD0GX7aiaO82/AJa 9WwvdeZL3rIZoBzKPTKwn/SJx/TdPw3hYKpIFLo9CPD+pwA2Q0t/ajWtLhr/cf3rJ3Ee WQy3ir0bifJignuB+axb67asdLMH1SbmbYnpgu/X3FaK82cHDMmwzzHNl+WZmB1WueNI oqDg== X-Received: by 10.140.145.3 with SMTP id 3mr17451090qhr.42.1423999196439; Sun, 15 Feb 2015 03:19:56 -0800 (PST) Received: from mail-qa0-f44.google.com (mail-qa0-f44.google.com. [209.85.216.44]) by mx.google.com with ESMTPSA id 79sm11421064qgn.36.2015.02.15.03.19.55 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 15 Feb 2015 03:19:56 -0800 (PST) Received: by mail-qa0-f44.google.com with SMTP id n8so18520690qaq.3 for ; Sun, 15 Feb 2015 03:19:55 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.140.202.144 with SMTP id x138mr17083868qha.14.1423999195442; Sun, 15 Feb 2015 03:19:55 -0800 (PST) Received: by 10.140.92.245 with HTTP; Sun, 15 Feb 2015 03:19:55 -0800 (PST) In-Reply-To: References: Date: Sun, 15 Feb 2015 11:19:55 +0000 Message-ID: From: Richard Mortier To: Anil Madhavapeddy Cc: mirageos-devel Subject: Re: [MirageOS-devel] performance regression tests X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 15 February 2015 at 11:15, Anil Madhavapeddy wrote: > This is great to see -- thanks for working on this Masoud! > > In particular, having even a simple iperf test would let us test > several interesting combinations straight away: > > - vary OCaml version (4.01 vs 4.02 is now supported), and there > is an experimental inlining branch in 4.03dev that could directly > be tested using this infrastructure. ok-- so i guess that needs a switch/env var to specify the `opam switch` to use? > - evaluate the impact of some features incoming such as the open > RFC for checksum offload. how are they specified -- as a PR? in which case, masoud-- i guess that https://help.github.com/articles/checking-out-pull-requests-locally/ is a starting point for how to specify a particular PR rather than simply a commit rev. > In terms of immediate feedback, I'd request a version that just does > iperf so that it has no dependencies on the host dom0 kernel. > See: https://github.com/mirage/mirage-skeleton/pull/75 just to be clear -- you mean does iperf via unikernels, ie., all the tests that are executed should also be unikernels rather than standard tools so that we don't take dependencies on an underlying platform like the dom0? > For this repository, what is the supported dom0 kernel that is expected? > The script tried to insmod a kmod that I didn't have. over to masoud... > Once there's even a minimal test, I'd like to recreate it on an > infrastructure machine in Cambridge and have it run daily via cron > alongside the is-mirage-broken scripts. cool... (one day i must learn about the cambridge infrastructure machines :) -- Richard Mortier richard.mortier@cl.cam.ac.uk _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Sun Feb 15 11:28:09 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 15 Feb 2015 11:28:09 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YMxMt-0004dc-Gt; Sun, 15 Feb 2015 11:28:07 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YMxMs-0004dX-94 for MirageOS-devel@lists.xenproject.org; Sun, 15 Feb 2015 11:28:06 +0000 Received: from [85.158.143.35] by server-2.bemta-4.messagelabs.com id A0/C2-02830-5C280E45; Sun, 15 Feb 2015 11:28:05 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-13.tower-21.messagelabs.com!1423999684!4680055!1 X-Originating-IP: [5.153.225.51] X-SpamReason: No, hits=0.2 required=7.0 tests=RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 13940 invoked from network); 15 Feb 2015 11:28:04 -0000 Received: from bark.recoil.org (HELO bark.recoil.org) (5.153.225.51) by server-13.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 15 Feb 2015 11:28:04 -0000 Received: from [192.168.1.69] (cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net [86.30.244.239]); by bark.recoil.org (OpenSMTPD) with ESMTPSA id 72ddc54a; TLS version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO; Sun, 15 Feb 2015 11:28:04 +0000 (GMT) Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) From: Anil Madhavapeddy In-Reply-To: Date: Sun, 15 Feb 2015 11:28:02 +0000 Message-Id: <9C6275D4-2397-45E7-B18A-81A47C317545@recoil.org> References: To: Richard Mortier X-Mailer: Apple Mail (2.2070.6) Cc: mirageos-devel Subject: Re: [MirageOS-devel] performance regression tests X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 15 Feb 2015, at 11:19, Richard Mortier wrote: > > On 15 February 2015 at 11:15, Anil Madhavapeddy wrote: >> This is great to see -- thanks for working on this Masoud! >> >> In particular, having even a simple iperf test would let us test >> several interesting combinations straight away: >> >> - vary OCaml version (4.01 vs 4.02 is now supported), and there >> is an experimental inlining branch in 4.03dev that could directly >> be tested using this infrastructure. > > ok-- so i guess that needs a switch/env var to specify the `opam switch` to use? Yeah. Although from the performance scripts' perspective, it's better if they just assume that there is a working OPAM environment. It would be easier to control these parameters from outside, and keep the perf scripts as easy to run as possible. A couple of other things that might help: - Luke Dunstan has a rather comprehensive acceptance test suite for MDNS: https://github.com/infidel/ocaml-mdns/tree/master/lib_test/acceptance - OCamlPro has a benchmarking system for core OCaml here that may have some useful libraries: https://github.com/OCamlPro/operf-macro - Performance tests could be wrapped using Core_bench, which does linear regression across runs. https://realworldocaml.org/v1/en/html/understanding-the-garbage-collector.html#the-mutable-write-barrier > >> - evaluate the impact of some features incoming such as the open >> RFC for checksum offload. > > how are they specified -- as a PR? > in which case, masoud-- i guess that > https://help.github.com/articles/checking-out-pull-requests-locally/ > is a starting point for how to specify a particular PR rather than > simply a commit rev. Yes, although again this would be better done outside the performance harness as an OPAM pin for the local environment. Just having the ability to quickly run a performance test would be invaluable at this stage. > >> In terms of immediate feedback, I'd request a version that just does >> iperf so that it has no dependencies on the host dom0 kernel. >> See: https://github.com/mirage/mirage-skeleton/pull/75 > > just to be clear -- you mean does iperf via unikernels, ie., all the > tests that are executed should also be unikernels rather than standard > tools so that we don't take dependencies on an underlying platform > like the dom0? Yes -- Xen unikernels would be the primary target. Starting and stopping VMs in open source Xen can be bit of a pain, so it would be ok if the test harness used XenServer (which the ARM SDcard images now include). Jon or Dave could comment on the state of the XMLRPC OCaml bindings to XenServer... > >> For this repository, what is the supported dom0 kernel that is expected? >> The script tried to insmod a kmod that I didn't have. > > over to masoud... > >> Once there's even a minimal test, I'd like to recreate it on an >> infrastructure machine in Cambridge and have it run daily via cron >> alongside the is-mirage-broken scripts. > > cool... (one day i must learn about the cambridge infrastructure machines :) Be careful what you wish for :) Anil _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Sun Feb 15 11:28:09 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 15 Feb 2015 11:28:09 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YMxMt-0004dc-Gt; Sun, 15 Feb 2015 11:28:07 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YMxMs-0004dX-94 for MirageOS-devel@lists.xenproject.org; Sun, 15 Feb 2015 11:28:06 +0000 Received: from [85.158.143.35] by server-2.bemta-4.messagelabs.com id A0/C2-02830-5C280E45; Sun, 15 Feb 2015 11:28:05 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-13.tower-21.messagelabs.com!1423999684!4680055!1 X-Originating-IP: [5.153.225.51] X-SpamReason: No, hits=0.2 required=7.0 tests=RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 13940 invoked from network); 15 Feb 2015 11:28:04 -0000 Received: from bark.recoil.org (HELO bark.recoil.org) (5.153.225.51) by server-13.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 15 Feb 2015 11:28:04 -0000 Received: from [192.168.1.69] (cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net [86.30.244.239]); by bark.recoil.org (OpenSMTPD) with ESMTPSA id 72ddc54a; TLS version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO; Sun, 15 Feb 2015 11:28:04 +0000 (GMT) Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) From: Anil Madhavapeddy In-Reply-To: Date: Sun, 15 Feb 2015 11:28:02 +0000 Message-Id: <9C6275D4-2397-45E7-B18A-81A47C317545@recoil.org> References: To: Richard Mortier X-Mailer: Apple Mail (2.2070.6) Cc: mirageos-devel Subject: Re: [MirageOS-devel] performance regression tests X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 15 Feb 2015, at 11:19, Richard Mortier wrote: > > On 15 February 2015 at 11:15, Anil Madhavapeddy wrote: >> This is great to see -- thanks for working on this Masoud! >> >> In particular, having even a simple iperf test would let us test >> several interesting combinations straight away: >> >> - vary OCaml version (4.01 vs 4.02 is now supported), and there >> is an experimental inlining branch in 4.03dev that could directly >> be tested using this infrastructure. > > ok-- so i guess that needs a switch/env var to specify the `opam switch` to use? Yeah. Although from the performance scripts' perspective, it's better if they just assume that there is a working OPAM environment. It would be easier to control these parameters from outside, and keep the perf scripts as easy to run as possible. A couple of other things that might help: - Luke Dunstan has a rather comprehensive acceptance test suite for MDNS: https://github.com/infidel/ocaml-mdns/tree/master/lib_test/acceptance - OCamlPro has a benchmarking system for core OCaml here that may have some useful libraries: https://github.com/OCamlPro/operf-macro - Performance tests could be wrapped using Core_bench, which does linear regression across runs. https://realworldocaml.org/v1/en/html/understanding-the-garbage-collector.html#the-mutable-write-barrier > >> - evaluate the impact of some features incoming such as the open >> RFC for checksum offload. > > how are they specified -- as a PR? > in which case, masoud-- i guess that > https://help.github.com/articles/checking-out-pull-requests-locally/ > is a starting point for how to specify a particular PR rather than > simply a commit rev. Yes, although again this would be better done outside the performance harness as an OPAM pin for the local environment. Just having the ability to quickly run a performance test would be invaluable at this stage. > >> In terms of immediate feedback, I'd request a version that just does >> iperf so that it has no dependencies on the host dom0 kernel. >> See: https://github.com/mirage/mirage-skeleton/pull/75 > > just to be clear -- you mean does iperf via unikernels, ie., all the > tests that are executed should also be unikernels rather than standard > tools so that we don't take dependencies on an underlying platform > like the dom0? Yes -- Xen unikernels would be the primary target. Starting and stopping VMs in open source Xen can be bit of a pain, so it would be ok if the test harness used XenServer (which the ARM SDcard images now include). Jon or Dave could comment on the state of the XMLRPC OCaml bindings to XenServer... > >> For this repository, what is the supported dom0 kernel that is expected? >> The script tried to insmod a kmod that I didn't have. > > over to masoud... > >> Once there's even a minimal test, I'd like to recreate it on an >> infrastructure machine in Cambridge and have it run daily via cron >> alongside the is-mirage-broken scripts. > > cool... (one day i must learn about the cambridge infrastructure machines :) Be careful what you wish for :) Anil _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Sun Feb 15 11:52:54 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 15 Feb 2015 11:52:54 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YMxkq-0006NV-Dn; Sun, 15 Feb 2015 11:52:52 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YMxkp-0006NQ-Cq for MirageOS-devel@lists.xenproject.org; Sun, 15 Feb 2015 11:52:51 +0000 Received: from [193.109.254.147] by server-12.bemta-14.messagelabs.com id D9/16-02755-29880E45; Sun, 15 Feb 2015 11:52:50 +0000 X-Env-Sender: richard.mortier@gmail.com X-Msg-Ref: server-13.tower-27.messagelabs.com!1424001168!13564921!1 X-Originating-IP: [209.85.216.44] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7662 invoked from network); 15 Feb 2015 11:52:49 -0000 Received: from mail-qa0-f44.google.com (HELO mail-qa0-f44.google.com) (209.85.216.44) by server-13.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 15 Feb 2015 11:52:49 -0000 Received: by mail-qa0-f44.google.com with SMTP id n8so18570340qaq.3 for ; Sun, 15 Feb 2015 03:52:48 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=+ryZXIWfp263SFFanpB4hjLvdbL6kOhWzZ6wB6piNZk=; b=SzFl7SttUCvnt/tsKgOA+UtWdJUChiym7ZvIIvAH+609y8HF0isD60cU4pbj7DRrUF vatWTkQUkGicEbfFYFnVh1bv0KmWY6x/wTxs8uPqSwzQICn2KhxvK7fj/GCclNRHzaSq 6UdrU9phPTf1M4hdtB8HRi5qOzJUAvHmYZYI4ggsP6p9e0u4ObqbDIAau0qLSowRB5s4 ujap77YK+a06GWBxDFPmfs/nwZPVloR9l0n7WvQDjdnf/qAeyGMPugzxW9QTdH3rPatB LobaFZlqEZRQx0wiqAU4PwvV01rkOyv03F89Lbus4YsjUwnm/0U1fmI4c7XLXq+G/h2m gdfw== X-Received: by 10.140.134.198 with SMTP id 189mr16864365qhg.7.1424001168044; Sun, 15 Feb 2015 03:52:48 -0800 (PST) Received: from mail-qg0-f52.google.com (mail-qg0-f52.google.com. [209.85.192.52]) by mx.google.com with ESMTPSA id z75sm2488923qhd.9.2015.02.15.03.52.47 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 15 Feb 2015 03:52:47 -0800 (PST) Received: by mail-qg0-f52.google.com with SMTP id h3so19674218qgf.11 for ; Sun, 15 Feb 2015 03:52:47 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.140.151.13 with SMTP id 13mr17627845qhx.68.1424001167163; Sun, 15 Feb 2015 03:52:47 -0800 (PST) Received: by 10.140.92.245 with HTTP; Sun, 15 Feb 2015 03:52:47 -0800 (PST) In-Reply-To: <9C6275D4-2397-45E7-B18A-81A47C317545@recoil.org> References: <9C6275D4-2397-45E7-B18A-81A47C317545@recoil.org> Date: Sun, 15 Feb 2015 11:52:47 +0000 Message-ID: From: Richard Mortier To: Anil Madhavapeddy Cc: mirageos-devel Subject: Re: [MirageOS-devel] performance regression tests X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 15 February 2015 at 11:28, Anil Madhavapeddy wrote: > On 15 Feb 2015, at 11:19, Richard Mortier wrote: >> >> On 15 February 2015 at 11:15, Anil Madhavapeddy wrote: >>> This is great to see -- thanks for working on this Masoud! >>> >>> In particular, having even a simple iperf test would let us test >>> several interesting combinations straight away: >>> >>> - vary OCaml version (4.01 vs 4.02 is now supported), and there >>> is an experimental inlining branch in 4.03dev that could directly >>> be tested using this infrastructure. >> >> ok-- so i guess that needs a switch/env var to specify the `opam switch` to use? > > Yeah. Although from the performance scripts' perspective, it's better > if they just assume that there is a working OPAM environment. It would > be easier to control these parameters from outside, and keep the perf > scripts as easy to run as possible. ah-- original thinking was to make `mir-perf.sh` a harness that might be fired by `git-bisect`. if it's just to be a script to run a single experiment (parameter set) in a pre-configured environment, then that's a lot simpler. > A couple of other things that might help: > > - Luke Dunstan has a rather comprehensive acceptance test suite for > MDNS: https://github.com/infidel/ocaml-mdns/tree/master/lib_test/acceptance > > - OCamlPro has a benchmarking system for core OCaml here that may have > some useful libraries: https://github.com/OCamlPro/operf-macro > > - Performance tests could be wrapped using Core_bench, which > does linear regression across runs. > https://realworldocaml.org/v1/en/html/understanding-the-garbage-collector.html#the-mutable-write-barrier > cool, ta. >>> - evaluate the impact of some features incoming such as the open >>> RFC for checksum offload. >> >> how are they specified -- as a PR? >> in which case, masoud-- i guess that >> https://help.github.com/articles/checking-out-pull-requests-locally/ >> is a starting point for how to specify a particular PR rather than >> simply a commit rev. > > Yes, although again this would be better done outside the performance > harness as an OPAM pin for the local environment. Just having the > ability to quickly run a performance test would be invaluable at this > stage. so the caller of the script will + select their opam switch + pin any libraries, whether to PRs or particular commit-revs + record the environment configuration + then run the script, specifying the test to run, which will + start the unikernel-under-test + start any testing-unikernels (eg., iperf-client, iperf-server) + collect and record test results ...right? ultimately i was thinking to have the recorded test results put in a repo somewhere too, so that they could be visualised, compared to a benchmark, etc. >> just to be clear -- you mean does iperf via unikernels, ie., all the >> tests that are executed should also be unikernels rather than standard >> tools so that we don't take dependencies on an underlying platform >> like the dom0? > > Yes -- Xen unikernels would be the primary target. cool. less shell hacking, more unikernel hacking :) > Starting and stopping VMs in open source Xen can be bit of a pain, so > it would be ok if the test harness used XenServer (which the ARM SDcard > images now include). Jon or Dave could comment on the state of the XMLRPC > OCaml bindings to XenServer... that would be useful. is it easy to get xenserver installed on x86 as well? (that's the platform masoud is mostly working on.) >> cool... (one day i must learn about the cambridge infrastructure machines :) > > Be careful what you wish for :) now i'm genuinely curious... :) -- Richard Mortier richard.mortier@cl.cam.ac.uk _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Sun Feb 15 11:52:54 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 15 Feb 2015 11:52:54 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YMxkq-0006NV-Dn; Sun, 15 Feb 2015 11:52:52 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YMxkp-0006NQ-Cq for MirageOS-devel@lists.xenproject.org; Sun, 15 Feb 2015 11:52:51 +0000 Received: from [193.109.254.147] by server-12.bemta-14.messagelabs.com id D9/16-02755-29880E45; Sun, 15 Feb 2015 11:52:50 +0000 X-Env-Sender: richard.mortier@gmail.com X-Msg-Ref: server-13.tower-27.messagelabs.com!1424001168!13564921!1 X-Originating-IP: [209.85.216.44] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7662 invoked from network); 15 Feb 2015 11:52:49 -0000 Received: from mail-qa0-f44.google.com (HELO mail-qa0-f44.google.com) (209.85.216.44) by server-13.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 15 Feb 2015 11:52:49 -0000 Received: by mail-qa0-f44.google.com with SMTP id n8so18570340qaq.3 for ; Sun, 15 Feb 2015 03:52:48 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=+ryZXIWfp263SFFanpB4hjLvdbL6kOhWzZ6wB6piNZk=; b=SzFl7SttUCvnt/tsKgOA+UtWdJUChiym7ZvIIvAH+609y8HF0isD60cU4pbj7DRrUF vatWTkQUkGicEbfFYFnVh1bv0KmWY6x/wTxs8uPqSwzQICn2KhxvK7fj/GCclNRHzaSq 6UdrU9phPTf1M4hdtB8HRi5qOzJUAvHmYZYI4ggsP6p9e0u4ObqbDIAau0qLSowRB5s4 ujap77YK+a06GWBxDFPmfs/nwZPVloR9l0n7WvQDjdnf/qAeyGMPugzxW9QTdH3rPatB LobaFZlqEZRQx0wiqAU4PwvV01rkOyv03F89Lbus4YsjUwnm/0U1fmI4c7XLXq+G/h2m gdfw== X-Received: by 10.140.134.198 with SMTP id 189mr16864365qhg.7.1424001168044; Sun, 15 Feb 2015 03:52:48 -0800 (PST) Received: from mail-qg0-f52.google.com (mail-qg0-f52.google.com. [209.85.192.52]) by mx.google.com with ESMTPSA id z75sm2488923qhd.9.2015.02.15.03.52.47 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 15 Feb 2015 03:52:47 -0800 (PST) Received: by mail-qg0-f52.google.com with SMTP id h3so19674218qgf.11 for ; Sun, 15 Feb 2015 03:52:47 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.140.151.13 with SMTP id 13mr17627845qhx.68.1424001167163; Sun, 15 Feb 2015 03:52:47 -0800 (PST) Received: by 10.140.92.245 with HTTP; Sun, 15 Feb 2015 03:52:47 -0800 (PST) In-Reply-To: <9C6275D4-2397-45E7-B18A-81A47C317545@recoil.org> References: <9C6275D4-2397-45E7-B18A-81A47C317545@recoil.org> Date: Sun, 15 Feb 2015 11:52:47 +0000 Message-ID: From: Richard Mortier To: Anil Madhavapeddy Cc: mirageos-devel Subject: Re: [MirageOS-devel] performance regression tests X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 15 February 2015 at 11:28, Anil Madhavapeddy wrote: > On 15 Feb 2015, at 11:19, Richard Mortier wrote: >> >> On 15 February 2015 at 11:15, Anil Madhavapeddy wrote: >>> This is great to see -- thanks for working on this Masoud! >>> >>> In particular, having even a simple iperf test would let us test >>> several interesting combinations straight away: >>> >>> - vary OCaml version (4.01 vs 4.02 is now supported), and there >>> is an experimental inlining branch in 4.03dev that could directly >>> be tested using this infrastructure. >> >> ok-- so i guess that needs a switch/env var to specify the `opam switch` to use? > > Yeah. Although from the performance scripts' perspective, it's better > if they just assume that there is a working OPAM environment. It would > be easier to control these parameters from outside, and keep the perf > scripts as easy to run as possible. ah-- original thinking was to make `mir-perf.sh` a harness that might be fired by `git-bisect`. if it's just to be a script to run a single experiment (parameter set) in a pre-configured environment, then that's a lot simpler. > A couple of other things that might help: > > - Luke Dunstan has a rather comprehensive acceptance test suite for > MDNS: https://github.com/infidel/ocaml-mdns/tree/master/lib_test/acceptance > > - OCamlPro has a benchmarking system for core OCaml here that may have > some useful libraries: https://github.com/OCamlPro/operf-macro > > - Performance tests could be wrapped using Core_bench, which > does linear regression across runs. > https://realworldocaml.org/v1/en/html/understanding-the-garbage-collector.html#the-mutable-write-barrier > cool, ta. >>> - evaluate the impact of some features incoming such as the open >>> RFC for checksum offload. >> >> how are they specified -- as a PR? >> in which case, masoud-- i guess that >> https://help.github.com/articles/checking-out-pull-requests-locally/ >> is a starting point for how to specify a particular PR rather than >> simply a commit rev. > > Yes, although again this would be better done outside the performance > harness as an OPAM pin for the local environment. Just having the > ability to quickly run a performance test would be invaluable at this > stage. so the caller of the script will + select their opam switch + pin any libraries, whether to PRs or particular commit-revs + record the environment configuration + then run the script, specifying the test to run, which will + start the unikernel-under-test + start any testing-unikernels (eg., iperf-client, iperf-server) + collect and record test results ...right? ultimately i was thinking to have the recorded test results put in a repo somewhere too, so that they could be visualised, compared to a benchmark, etc. >> just to be clear -- you mean does iperf via unikernels, ie., all the >> tests that are executed should also be unikernels rather than standard >> tools so that we don't take dependencies on an underlying platform >> like the dom0? > > Yes -- Xen unikernels would be the primary target. cool. less shell hacking, more unikernel hacking :) > Starting and stopping VMs in open source Xen can be bit of a pain, so > it would be ok if the test harness used XenServer (which the ARM SDcard > images now include). Jon or Dave could comment on the state of the XMLRPC > OCaml bindings to XenServer... that would be useful. is it easy to get xenserver installed on x86 as well? (that's the platform masoud is mostly working on.) >> cool... (one day i must learn about the cambridge infrastructure machines :) > > Be careful what you wish for :) now i'm genuinely curious... :) -- Richard Mortier richard.mortier@cl.cam.ac.uk _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Sun Feb 15 12:04:08 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 15 Feb 2015 12:04:08 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YMxvi-00074Q-Po; Sun, 15 Feb 2015 12:04:06 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YMxvi-00074L-6I for MirageOS-devel@lists.xenproject.org; Sun, 15 Feb 2015 12:04:06 +0000 Received: from [193.109.254.147] by server-12.bemta-14.messagelabs.com id 7F/5A-02755-53B80E45; Sun, 15 Feb 2015 12:04:05 +0000 X-Env-Sender: scott.dj@gmail.com X-Msg-Ref: server-5.tower-27.messagelabs.com!1424001841!8914615!1 X-Originating-IP: [209.85.192.182] X-SpamReason: No, hits=0.9 required=7.0 tests=BODY_RANDOM_LONG, HTML_30_40,HTML_MESSAGE,RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20713 invoked from network); 15 Feb 2015 12:04:03 -0000 Received: from mail-pd0-f182.google.com (HELO mail-pd0-f182.google.com) (209.85.192.182) by server-5.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 15 Feb 2015 12:04:03 -0000 Received: by pdbfl12 with SMTP id fl12so29146092pdb.4 for ; Sun, 15 Feb 2015 04:04:01 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=e4Cvy6CKd5onMum4pwj/OPYl6BXjMFgdWgXwCu+KLKk=; b=FxDZIQCCMvFTYqh8b8n0r2RLE/BfGVFPvzJPXH47pzpRluBzDU3T0P1ZQ6sNBj6LNZ XXjXTDWF+nA9/wKTUp1Ea/a3CcWwH02TI5XWEDX6K7lnQgC00A7rRHnyCAkl+skg49ye snI79YgBADRkpLkPyDRiBRvoHmhMitywJohcroqhLazu5jJfbiQnlhjOTLLBU1O/OYWM DRwAiiCGwIW1oPFq3B5/S4zPa2LCHu5dWpVdlcvmn5r40oXR+hKVkGnNk6aIFGiPvSpO pU9bwij5gqjhjWWiy08whE79EPBzQ6TtAFXeONqUJs4hUhMZS5ruHAQaEccK17/FBPsP HzXw== MIME-Version: 1.0 X-Received: by 10.66.66.166 with SMTP id g6mr31283161pat.88.1424001841422; Sun, 15 Feb 2015 04:04:01 -0800 (PST) Received: by 10.70.102.39 with HTTP; Sun, 15 Feb 2015 04:04:01 -0800 (PST) In-Reply-To: <9C6275D4-2397-45E7-B18A-81A47C317545@recoil.org> References: <9C6275D4-2397-45E7-B18A-81A47C317545@recoil.org> Date: Sun, 15 Feb 2015 12:04:01 +0000 Message-ID: From: David Scott To: Anil Madhavapeddy Cc: mirageos-devel Subject: Re: [MirageOS-devel] performance regression tests X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============5857896622639102408==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============5857896622639102408== Content-Type: multipart/alternative; boundary=001a1134b4f8eaeac4050f1f43aa --001a1134b4f8eaeac4050f1f43aa Content-Type: text/plain; charset=UTF-8 On Sun, Feb 15, 2015 at 11:28 AM, Anil Madhavapeddy wrote: > On 15 Feb 2015, at 11:19, Richard Mortier > wrote: > > > > On 15 February 2015 at 11:15, Anil Madhavapeddy wrote: > >> This is great to see -- thanks for working on this Masoud! > >> > >> In particular, having even a simple iperf test would let us test > >> several interesting combinations straight away: > >> > >> - vary OCaml version (4.01 vs 4.02 is now supported), and there > >> is an experimental inlining branch in 4.03dev that could directly > >> be tested using this infrastructure. > > > > ok-- so i guess that needs a switch/env var to specify the `opam switch` > to use? > > Yeah. Although from the performance scripts' perspective, it's better > if they just assume that there is a working OPAM environment. It would > be easier to control these parameters from outside, and keep the perf > scripts as easy to run as possible. > > A couple of other things that might help: > > - Luke Dunstan has a rather comprehensive acceptance test suite for > MDNS: > https://github.com/infidel/ocaml-mdns/tree/master/lib_test/acceptance > > - OCamlPro has a benchmarking system for core OCaml here that may have > some useful libraries: https://github.com/OCamlPro/operf-macro > > - Performance tests could be wrapped using Core_bench, which > does linear regression across runs. > > https://realworldocaml.org/v1/en/html/understanding-the-garbage-collector.html#the-mutable-write-barrier > > > > >> - evaluate the impact of some features incoming such as the open > >> RFC for checksum offload. > > > > how are they specified -- as a PR? > > in which case, masoud-- i guess that > > https://help.github.com/articles/checking-out-pull-requests-locally/ > > is a starting point for how to specify a particular PR rather than > > simply a commit rev. > > Yes, although again this would be better done outside the performance > harness as an OPAM pin for the local environment. Just having the > ability to quickly run a performance test would be invaluable at this > stage. > > > > >> In terms of immediate feedback, I'd request a version that just does > >> iperf so that it has no dependencies on the host dom0 kernel. > >> See: https://github.com/mirage/mirage-skeleton/pull/75 > > > > just to be clear -- you mean does iperf via unikernels, ie., all the > > tests that are executed should also be unikernels rather than standard > > tools so that we don't take dependencies on an underlying platform > > like the dom0? > > Yes -- Xen unikernels would be the primary target. > > Starting and stopping VMs in open source Xen can be bit of a pain, so > it would be ok if the test harness used XenServer (which the ARM SDcard > images now include). Jon or Dave could comment on the state of the XMLRPC > OCaml bindings to XenServer... > The cubieboard images are working ok for me-- I've got 2 of them and am using XMLRPC to manage them remotely. The OCaml XenAPI bindings are in the opam "xen-api-client" package and in this repo: https://github.com/xapi-project/xen-api-client There are simple examples in there including $ ./list_vms.native -uri http://cubieboard2.local. -u mirage -pw mirage 2> /dev/null VM Control domain on host: cubieboard2 VM www The client bindings are slightly tweaked versions of the ones used in xenserver, which are battle-tested. There are lots of things about their style which I don't like and would like to improve, but they do work. Feel free to create issues in the issue tracker if you find bugs, or have improvement suggestions. I'd like to fix lots of issues and make a single new major release, and then take the time to port the xapi/xenserver codebase over. For talking to test VMs I recommend writing the IP address to xenstore which will then be available via the XenAPI. You can then connect to the unikernel via TCP/IP. Eventually we might be able to switch to vchan but I think TCP over netfront is more reliable. Jon: where is your Mirage "guest agent" that can do shutdown (and could be extended to report info like IP address)? Dave > > > > >> For this repository, what is the supported dom0 kernel that is expected? > >> The script tried to insmod a kmod that I didn't have. > > > > over to masoud... > > > >> Once there's even a minimal test, I'd like to recreate it on an > >> infrastructure machine in Cambridge and have it run daily via cron > >> alongside the is-mirage-broken scripts. > > > > cool... (one day i must learn about the cambridge infrastructure > machines :) > > Be careful what you wish for :) > > Anil > > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > -- Dave Scott --001a1134b4f8eaeac4050f1f43aa Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


On Sun, Feb 15, 2015 at 11:28 AM, Anil Madhavapeddy &= lt;anil@recoil.org= > wrote:
On 15 Feb 2015, at = 11:19, Richard Mortier <= richard.mortier@cl.cam.ac.uk> wrote:
>
> On 15 February 2015 at 11:15, Anil Madhavapeddy <anil@recoil.org> wrote:
>> This is great to see -- thanks for working on this Masoud!
>>
>> In particular, having even a simple iperf test would let us test >> several interesting combinations straight away:
>>
>> - vary OCaml version (4.01 vs 4.02 is now supported), and there >>=C2=A0 is an experimental inlining branch in 4.03dev that could dir= ectly
>>=C2=A0 be tested using this infrastructure.
>
> ok-- so i guess that needs a switch/env var to specify the `opam switc= h` to use?

Yeah.=C2=A0 Although from the performance scripts' perspective, = it's better
if they just assume that there is a working OPAM environment.=C2=A0 It woul= d
be easier to control these parameters from outside, and keep the perf
scripts as easy to run as possible.

A couple of other things that might help:

- Luke Dunstan has a rather comprehensive acceptance test suite for
=C2=A0 MDNS: https://github.com/infidel/ocaml-mdns= /tree/master/lib_test/acceptance

- OCamlPro has a benchmarking system for core OCaml here that may have
=C2=A0 some useful libraries: https://github.com/OCamlPro/operf-macro

- Performance tests could be wrapped using Core_bench, which
=C2=A0 does linear regression across runs.
=C2=A0 https://= realworldocaml.org/v1/en/html/understanding-the-garbage-collector.html#the-= mutable-write-barrier

>
>> - evaluate the impact of some features incoming such as the open >>=C2=A0 RFC for checksum offload.
>
> how are they specified -- as a PR?
> in which case, masoud-- i guess that
> https://help.github.com/articles/checking-out-= pull-requests-locally/
> is a starting point for how to specify a particular PR rather than
> simply a commit rev.

Yes, although again this would be better done outside the performanc= e
harness as an OPAM pin for the local environment.=C2=A0 Just having the
ability to quickly run a performance test would be invaluable at this
stage.

>
>> In terms of immediate feedback, I'd request a version that jus= t does
>> iperf so that it has no dependencies on the host dom0 kernel.
>> See: https://github.com/mirage/mirage-skeleton/pull/75 >
> just to be clear -- you mean does iperf via unikernels, ie., all the > tests that are executed should also be unikernels rather than standard=
> tools so that we don't take dependencies on an underlying platform=
> like the dom0?

Yes -- Xen unikernels would be the primary target.

Starting and stopping VMs in open source Xen can be bit of a pain, so
it would be ok if the test harness used XenServer (which the ARM SDcard
images now include).=C2=A0 Jon or Dave could comment on the state of the XM= LRPC
OCaml bindings to XenServer...

The cubi= eboard images are working ok for me-- I've got 2 of them and am using X= MLRPC to manage them remotely.

The OCaml XenAPI bi= ndings are in the opam "xen-api-client" package and in this repo:=

=
There are simple examples in there including

<= /div>
$ ./list_vms.native -uri http://cubieboard2.local. -u mirage -pw mirage 2> /dev/null
<= div>VM Control domain on host: cubieboard2
VM www

The client bindings are slightly tweaked versions of the on= es used in xenserver, which are battle-tested. There are lots of things abo= ut their style which I don't like and would like to improve, but they d= o work. Feel free to create issues in the issue tracker if you find bugs, o= r have improvement suggestions. I'd like to fix lots of issues and make= a single new major release, and then take the time to port the xapi/xenser= ver codebase over.

For talking to test VMs I recom= mend writing the IP address to xenstore which will then be available via th= e XenAPI. You can then connect to the unikernel via TCP/IP. Eventually we m= ight be able to switch to vchan but I think TCP over netfront is more relia= ble.

Jon: where is your Mirage "guest agent&q= uot; that can do shutdown (and could be extended to report info like IP add= ress)?

Dave

=C2=A0
<= blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-l= eft-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;pa= dding-left:1ex">
>
>> For this repository, what is the supported dom0 kernel that is exp= ected?
>> The script tried to insmod a kmod that I didn't have.
>
> over to masoud...
>
>> Once there's even a minimal test, I'd like to recreate it = on an
>> infrastructure machine in Cambridge and have it run daily via cron=
>> alongside the is-mirage-broken scripts.
>
> cool... (one day i must learn about the cambridge infrastructure machi= nes :)

Be careful what you wish for :)

Anil

_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists= .xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo= /mirageos-devel



--
=
Dave Scott
--001a1134b4f8eaeac4050f1f43aa-- --===============5857896622639102408== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --===============5857896622639102408==-- From mirageos-devel-bounces@lists.xenproject.org Sun Feb 15 12:04:08 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 15 Feb 2015 12:04:08 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YMxvi-00074Q-Po; Sun, 15 Feb 2015 12:04:06 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YMxvi-00074L-6I for MirageOS-devel@lists.xenproject.org; Sun, 15 Feb 2015 12:04:06 +0000 Received: from [193.109.254.147] by server-12.bemta-14.messagelabs.com id 7F/5A-02755-53B80E45; Sun, 15 Feb 2015 12:04:05 +0000 X-Env-Sender: scott.dj@gmail.com X-Msg-Ref: server-5.tower-27.messagelabs.com!1424001841!8914615!1 X-Originating-IP: [209.85.192.182] X-SpamReason: No, hits=0.9 required=7.0 tests=BODY_RANDOM_LONG, HTML_30_40,HTML_MESSAGE,RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20713 invoked from network); 15 Feb 2015 12:04:03 -0000 Received: from mail-pd0-f182.google.com (HELO mail-pd0-f182.google.com) (209.85.192.182) by server-5.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 15 Feb 2015 12:04:03 -0000 Received: by pdbfl12 with SMTP id fl12so29146092pdb.4 for ; Sun, 15 Feb 2015 04:04:01 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=e4Cvy6CKd5onMum4pwj/OPYl6BXjMFgdWgXwCu+KLKk=; b=FxDZIQCCMvFTYqh8b8n0r2RLE/BfGVFPvzJPXH47pzpRluBzDU3T0P1ZQ6sNBj6LNZ XXjXTDWF+nA9/wKTUp1Ea/a3CcWwH02TI5XWEDX6K7lnQgC00A7rRHnyCAkl+skg49ye snI79YgBADRkpLkPyDRiBRvoHmhMitywJohcroqhLazu5jJfbiQnlhjOTLLBU1O/OYWM DRwAiiCGwIW1oPFq3B5/S4zPa2LCHu5dWpVdlcvmn5r40oXR+hKVkGnNk6aIFGiPvSpO pU9bwij5gqjhjWWiy08whE79EPBzQ6TtAFXeONqUJs4hUhMZS5ruHAQaEccK17/FBPsP HzXw== MIME-Version: 1.0 X-Received: by 10.66.66.166 with SMTP id g6mr31283161pat.88.1424001841422; Sun, 15 Feb 2015 04:04:01 -0800 (PST) Received: by 10.70.102.39 with HTTP; Sun, 15 Feb 2015 04:04:01 -0800 (PST) In-Reply-To: <9C6275D4-2397-45E7-B18A-81A47C317545@recoil.org> References: <9C6275D4-2397-45E7-B18A-81A47C317545@recoil.org> Date: Sun, 15 Feb 2015 12:04:01 +0000 Message-ID: From: David Scott To: Anil Madhavapeddy Cc: mirageos-devel Subject: Re: [MirageOS-devel] performance regression tests X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============5857896622639102408==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============5857896622639102408== Content-Type: multipart/alternative; boundary=001a1134b4f8eaeac4050f1f43aa --001a1134b4f8eaeac4050f1f43aa Content-Type: text/plain; charset=UTF-8 On Sun, Feb 15, 2015 at 11:28 AM, Anil Madhavapeddy wrote: > On 15 Feb 2015, at 11:19, Richard Mortier > wrote: > > > > On 15 February 2015 at 11:15, Anil Madhavapeddy wrote: > >> This is great to see -- thanks for working on this Masoud! > >> > >> In particular, having even a simple iperf test would let us test > >> several interesting combinations straight away: > >> > >> - vary OCaml version (4.01 vs 4.02 is now supported), and there > >> is an experimental inlining branch in 4.03dev that could directly > >> be tested using this infrastructure. > > > > ok-- so i guess that needs a switch/env var to specify the `opam switch` > to use? > > Yeah. Although from the performance scripts' perspective, it's better > if they just assume that there is a working OPAM environment. It would > be easier to control these parameters from outside, and keep the perf > scripts as easy to run as possible. > > A couple of other things that might help: > > - Luke Dunstan has a rather comprehensive acceptance test suite for > MDNS: > https://github.com/infidel/ocaml-mdns/tree/master/lib_test/acceptance > > - OCamlPro has a benchmarking system for core OCaml here that may have > some useful libraries: https://github.com/OCamlPro/operf-macro > > - Performance tests could be wrapped using Core_bench, which > does linear regression across runs. > > https://realworldocaml.org/v1/en/html/understanding-the-garbage-collector.html#the-mutable-write-barrier > > > > >> - evaluate the impact of some features incoming such as the open > >> RFC for checksum offload. > > > > how are they specified -- as a PR? > > in which case, masoud-- i guess that > > https://help.github.com/articles/checking-out-pull-requests-locally/ > > is a starting point for how to specify a particular PR rather than > > simply a commit rev. > > Yes, although again this would be better done outside the performance > harness as an OPAM pin for the local environment. Just having the > ability to quickly run a performance test would be invaluable at this > stage. > > > > >> In terms of immediate feedback, I'd request a version that just does > >> iperf so that it has no dependencies on the host dom0 kernel. > >> See: https://github.com/mirage/mirage-skeleton/pull/75 > > > > just to be clear -- you mean does iperf via unikernels, ie., all the > > tests that are executed should also be unikernels rather than standard > > tools so that we don't take dependencies on an underlying platform > > like the dom0? > > Yes -- Xen unikernels would be the primary target. > > Starting and stopping VMs in open source Xen can be bit of a pain, so > it would be ok if the test harness used XenServer (which the ARM SDcard > images now include). Jon or Dave could comment on the state of the XMLRPC > OCaml bindings to XenServer... > The cubieboard images are working ok for me-- I've got 2 of them and am using XMLRPC to manage them remotely. The OCaml XenAPI bindings are in the opam "xen-api-client" package and in this repo: https://github.com/xapi-project/xen-api-client There are simple examples in there including $ ./list_vms.native -uri http://cubieboard2.local. -u mirage -pw mirage 2> /dev/null VM Control domain on host: cubieboard2 VM www The client bindings are slightly tweaked versions of the ones used in xenserver, which are battle-tested. There are lots of things about their style which I don't like and would like to improve, but they do work. Feel free to create issues in the issue tracker if you find bugs, or have improvement suggestions. I'd like to fix lots of issues and make a single new major release, and then take the time to port the xapi/xenserver codebase over. For talking to test VMs I recommend writing the IP address to xenstore which will then be available via the XenAPI. You can then connect to the unikernel via TCP/IP. Eventually we might be able to switch to vchan but I think TCP over netfront is more reliable. Jon: where is your Mirage "guest agent" that can do shutdown (and could be extended to report info like IP address)? Dave > > > > >> For this repository, what is the supported dom0 kernel that is expected? > >> The script tried to insmod a kmod that I didn't have. > > > > over to masoud... > > > >> Once there's even a minimal test, I'd like to recreate it on an > >> infrastructure machine in Cambridge and have it run daily via cron > >> alongside the is-mirage-broken scripts. > > > > cool... (one day i must learn about the cambridge infrastructure > machines :) > > Be careful what you wish for :) > > Anil > > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > -- Dave Scott --001a1134b4f8eaeac4050f1f43aa Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


On Sun, Feb 15, 2015 at 11:28 AM, Anil Madhavapeddy &= lt;anil@recoil.org= > wrote:
On 15 Feb 2015, at = 11:19, Richard Mortier <= richard.mortier@cl.cam.ac.uk> wrote:
>
> On 15 February 2015 at 11:15, Anil Madhavapeddy <anil@recoil.org> wrote:
>> This is great to see -- thanks for working on this Masoud!
>>
>> In particular, having even a simple iperf test would let us test >> several interesting combinations straight away:
>>
>> - vary OCaml version (4.01 vs 4.02 is now supported), and there >>=C2=A0 is an experimental inlining branch in 4.03dev that could dir= ectly
>>=C2=A0 be tested using this infrastructure.
>
> ok-- so i guess that needs a switch/env var to specify the `opam switc= h` to use?

Yeah.=C2=A0 Although from the performance scripts' perspective, = it's better
if they just assume that there is a working OPAM environment.=C2=A0 It woul= d
be easier to control these parameters from outside, and keep the perf
scripts as easy to run as possible.

A couple of other things that might help:

- Luke Dunstan has a rather comprehensive acceptance test suite for
=C2=A0 MDNS: https://github.com/infidel/ocaml-mdns= /tree/master/lib_test/acceptance

- OCamlPro has a benchmarking system for core OCaml here that may have
=C2=A0 some useful libraries: https://github.com/OCamlPro/operf-macro

- Performance tests could be wrapped using Core_bench, which
=C2=A0 does linear regression across runs.
=C2=A0 https://= realworldocaml.org/v1/en/html/understanding-the-garbage-collector.html#the-= mutable-write-barrier

>
>> - evaluate the impact of some features incoming such as the open >>=C2=A0 RFC for checksum offload.
>
> how are they specified -- as a PR?
> in which case, masoud-- i guess that
> https://help.github.com/articles/checking-out-= pull-requests-locally/
> is a starting point for how to specify a particular PR rather than
> simply a commit rev.

Yes, although again this would be better done outside the performanc= e
harness as an OPAM pin for the local environment.=C2=A0 Just having the
ability to quickly run a performance test would be invaluable at this
stage.

>
>> In terms of immediate feedback, I'd request a version that jus= t does
>> iperf so that it has no dependencies on the host dom0 kernel.
>> See: https://github.com/mirage/mirage-skeleton/pull/75 >
> just to be clear -- you mean does iperf via unikernels, ie., all the > tests that are executed should also be unikernels rather than standard=
> tools so that we don't take dependencies on an underlying platform=
> like the dom0?

Yes -- Xen unikernels would be the primary target.

Starting and stopping VMs in open source Xen can be bit of a pain, so
it would be ok if the test harness used XenServer (which the ARM SDcard
images now include).=C2=A0 Jon or Dave could comment on the state of the XM= LRPC
OCaml bindings to XenServer...

The cubi= eboard images are working ok for me-- I've got 2 of them and am using X= MLRPC to manage them remotely.

The OCaml XenAPI bi= ndings are in the opam "xen-api-client" package and in this repo:=

=
There are simple examples in there including

<= /div>
$ ./list_vms.native -uri http://cubieboard2.local. -u mirage -pw mirage 2> /dev/null
<= div>VM Control domain on host: cubieboard2
VM www

The client bindings are slightly tweaked versions of the on= es used in xenserver, which are battle-tested. There are lots of things abo= ut their style which I don't like and would like to improve, but they d= o work. Feel free to create issues in the issue tracker if you find bugs, o= r have improvement suggestions. I'd like to fix lots of issues and make= a single new major release, and then take the time to port the xapi/xenser= ver codebase over.

For talking to test VMs I recom= mend writing the IP address to xenstore which will then be available via th= e XenAPI. You can then connect to the unikernel via TCP/IP. Eventually we m= ight be able to switch to vchan but I think TCP over netfront is more relia= ble.

Jon: where is your Mirage "guest agent&q= uot; that can do shutdown (and could be extended to report info like IP add= ress)?

Dave

=C2=A0
<= blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-l= eft-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;pa= dding-left:1ex">
>
>> For this repository, what is the supported dom0 kernel that is exp= ected?
>> The script tried to insmod a kmod that I didn't have.
>
> over to masoud...
>
>> Once there's even a minimal test, I'd like to recreate it = on an
>> infrastructure machine in Cambridge and have it run daily via cron=
>> alongside the is-mirage-broken scripts.
>
> cool... (one day i must learn about the cambridge infrastructure machi= nes :)

Be careful what you wish for :)

Anil

_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists= .xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo= /mirageos-devel



--
=
Dave Scott
--001a1134b4f8eaeac4050f1f43aa-- --===============5857896622639102408== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --===============5857896622639102408==-- From mirageos-devel-bounces@lists.xenproject.org Sun Feb 15 12:18:42 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 15 Feb 2015 12:18:42 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YMy9j-0007gq-UU; Sun, 15 Feb 2015 12:18:35 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YMy9i-0007gl-FS for MirageOS-devel@lists.xenproject.org; Sun, 15 Feb 2015 12:18:34 +0000 Received: from [193.109.254.147] by server-15.bemta-14.messagelabs.com id 04/EE-02770-99E80E45; Sun, 15 Feb 2015 12:18:33 +0000 X-Env-Sender: scott.dj@gmail.com X-Msg-Ref: server-13.tower-27.messagelabs.com!1424002709!13567074!1 X-Originating-IP: [209.85.192.170] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE, RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27974 invoked from network); 15 Feb 2015 12:18:31 -0000 Received: from mail-pd0-f170.google.com (HELO mail-pd0-f170.google.com) (209.85.192.170) by server-13.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 15 Feb 2015 12:18:31 -0000 Received: by pdbfl12 with SMTP id fl12so29210988pdb.2 for ; Sun, 15 Feb 2015 04:18:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=H7zI46H5fuZxuToICoL+Q9JsUNjX8HbaZ51IErmVioY=; b=cK2lDbBYvqWWuLywudddHy0YmitN7n+Fw9cq9Z9Uca8hsuqURtVPl4oYmklLzDg+pp Gen3zaSAiCrnB56mokRHqEHxV9hzZ6B/1EnnEOOA5rg4hIyrLDH7kCnjjc0aW+hgpbA0 MGzcx41qu/C33ICJzp3tmR72eo/IjOZjqP+BtDYZ45J1TOXvmfwm57iqxYdc5jl8IpyW oY8UKRdUCyVlknBOgpbW/Df/PMpT7nsrSXagfZGZbt0TaU0K/i3WuP0dPcHcZmK6RVvN GXgoNzR9isut+jq+2jMqEZBI6q6msti7cMvpOujP6t8aARhpHA01201K/EU1iCm6IKTK gKjg== MIME-Version: 1.0 X-Received: by 10.66.164.66 with SMTP id yo2mr24790603pab.59.1424002709335; Sun, 15 Feb 2015 04:18:29 -0800 (PST) Received: by 10.70.102.39 with HTTP; Sun, 15 Feb 2015 04:18:29 -0800 (PST) In-Reply-To: References: <9C6275D4-2397-45E7-B18A-81A47C317545@recoil.org> Date: Sun, 15 Feb 2015 12:18:29 +0000 Message-ID: From: David Scott To: Richard Mortier Cc: mirageos-devel , Anil Madhavapeddy Subject: Re: [MirageOS-devel] performance regression tests X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============6935924776236578710==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============6935924776236578710== Content-Type: multipart/alternative; boundary=047d7b6d9472a63305050f1f7727 --047d7b6d9472a63305050f1f7727 Content-Type: text/plain; charset=UTF-8 On Sun, Feb 15, 2015 at 11:52 AM, Richard Mortier < richard.mortier@cl.cam.ac.uk> wrote: > On 15 February 2015 at 11:28, Anil Madhavapeddy wrote: > > On 15 Feb 2015, at 11:19, Richard Mortier > wrote: > >> > >> On 15 February 2015 at 11:15, Anil Madhavapeddy > wrote: > >>> This is great to see -- thanks for working on this Masoud! > >>> > >>> In particular, having even a simple iperf test would let us test > >>> several interesting combinations straight away: > >>> > >>> - vary OCaml version (4.01 vs 4.02 is now supported), and there > >>> is an experimental inlining branch in 4.03dev that could directly > >>> be tested using this infrastructure. > >> > >> ok-- so i guess that needs a switch/env var to specify the `opam > switch` to use? > > > > Yeah. Although from the performance scripts' perspective, it's better > > if they just assume that there is a working OPAM environment. It would > > be easier to control these parameters from outside, and keep the perf > > scripts as easy to run as possible. > > ah-- original thinking was to make `mir-perf.sh` a harness that might > be fired by `git-bisect`. > > if it's just to be a script to run a single experiment (parameter set) > in a pre-configured environment, then that's a lot simpler. > > > A couple of other things that might help: > > > > - Luke Dunstan has a rather comprehensive acceptance test suite for > > MDNS: > https://github.com/infidel/ocaml-mdns/tree/master/lib_test/acceptance > > > > - OCamlPro has a benchmarking system for core OCaml here that may have > > some useful libraries: https://github.com/OCamlPro/operf-macro > > > > - Performance tests could be wrapped using Core_bench, which > > does linear regression across runs. > > > https://realworldocaml.org/v1/en/html/understanding-the-garbage-collector.html#the-mutable-write-barrier > > > > cool, ta. > > >>> - evaluate the impact of some features incoming such as the open > >>> RFC for checksum offload. > >> > >> how are they specified -- as a PR? > >> in which case, masoud-- i guess that > >> https://help.github.com/articles/checking-out-pull-requests-locally/ > >> is a starting point for how to specify a particular PR rather than > >> simply a commit rev. > > > > Yes, although again this would be better done outside the performance > > harness as an OPAM pin for the local environment. Just having the > > ability to quickly run a performance test would be invaluable at this > > stage. > > so the caller of the script will > > + select their opam switch > + pin any libraries, whether to PRs or particular commit-revs > + record the environment configuration > > + then run the script, specifying the test to run, which will > + start the unikernel-under-test > + start any testing-unikernels (eg., iperf-client, iperf-server) > + collect and record test results > > ...right? > > ultimately i was thinking to have the recorded test results put in a > repo somewhere too, so that they could be visualised, compared to a > benchmark, etc. > > >> just to be clear -- you mean does iperf via unikernels, ie., all the > >> tests that are executed should also be unikernels rather than standard > >> tools so that we don't take dependencies on an underlying platform > >> like the dom0? > > > > Yes -- Xen unikernels would be the primary target. > > cool. less shell hacking, more unikernel hacking :) > > > Starting and stopping VMs in open source Xen can be bit of a pain, so > > it would be ok if the test harness used XenServer (which the ARM SDcard > > images now include). Jon or Dave could comment on the state of the > XMLRPC > > OCaml bindings to XenServer... > > that would be useful. is it easy to get xenserver installed on x86 as > well? (that's the platform masoud is mostly working on.) > x86 as well? What is this, 2014? :-) Your options are: 1. install the latest 6.5 release of xenserver on bare metal Pros: this is well tested and will work very well as a virtualisation platform Cons: it takes over a whole machine. To do unikernel development you'll need to install a dev VM i.e. you can't do it in dom0. It's good practice to leave dom0 alone anyway. Think of it like a black box which can run VMs. 2. build the latest version from source and install on a CentOS 6/7 or maybe Ubuntu box Pros: you can do whatever you want with dom0 Cons: some aspect of running VMs/ managing networks / managing storage is bound to not work and you'll need to debug it. There is little automated testing of this configuration, I (also Euan, Jon) try to fix bugs when I/we encounter them on a best-effort basis. If you want to focus on unikernel dev and test, I recommend option 1. If you want a new hobby of debugging VM hosting software, then try option 2. In the long run ... we'll converge option 1 and option 2... but I wouldn't wait. Cheers, Dave > > >> cool... (one day i must learn about the cambridge infrastructure > machines :) > > > > Be careful what you wish for :) > > now i'm genuinely curious... :) > > -- > Richard Mortier > richard.mortier@cl.cam.ac.uk > > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > -- Dave Scott --047d7b6d9472a63305050f1f7727 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


On Sun, Feb 15, 2015 at 11:52 AM, Richard Mortier <= ;richard.= mortier@cl.cam.ac.uk> wrote:
On 15 February 2015 at 11:28, Anil Madhavapeddy <anil@recoil.org> wrote:
> On 15 Feb 2015, at 11:19, Richard Mortier <richard.mortier@cl.cam.ac.uk> wrote:
>>
>> On 15 February 2015 at 11:15, Anil Madhavapeddy <anil@recoil.org> wrote:
>>> This is great to see -- thanks for working on this Masoud!
>>>
>>> In particular, having even a simple iperf test would let us te= st
>>> several interesting combinations straight away:
>>>
>>> - vary OCaml version (4.01 vs 4.02 is now supported), and ther= e
>>>=C2=A0 is an experimental inlining branch in 4.03dev that could= directly
>>>=C2=A0 be tested using this infrastructure.
>>
>> ok-- so i guess that needs a switch/env var to specify the `opam s= witch` to use?
>
> Yeah.=C2=A0 Although from the performance scripts' perspective, it= 's better
> if they just assume that there is a working OPAM environment.=C2=A0 It= would
> be easier to control these parameters from outside, and keep the perf<= br> > scripts as easy to run as possible.

ah-- original thinking was to make `mir-perf.sh` a harness that migh= t
be fired by `git-bisect`.

if it's just to be a script to run a single experiment (parameter set)<= br> in a pre-configured environment, then that's a lot simpler.

> A couple of other things that might help:
>
> - Luke Dunstan has a rather comprehensive acceptance test suite for >=C2=A0 =C2=A0MDNS: https://github.com/infidel/= ocaml-mdns/tree/master/lib_test/acceptance
>
> - OCamlPro has a benchmarking system for core OCaml here that may have=
>=C2=A0 =C2=A0some useful libraries: https://github.com/OCamlPro/operf-macro<= /a>
>
> - Performance tests could be wrapped using Core_bench, which
>=C2=A0 =C2=A0does linear regression across runs.
>=C2=A0 =C2=A0https://realworldocaml.org/v1/en/html/understanding-the-garbage-collector= .html#the-mutable-write-barrier
>

cool, ta.

>>> - evaluate the impact of some features incoming such as the op= en
>>>=C2=A0 RFC for checksum offload.
>>
>> how are they specified -- as a PR?
>> in which case, masoud-- i guess that
>> https://help.github.com/articles/checking-= out-pull-requests-locally/
>> is a starting point for how to specify a particular PR rather than=
>> simply a commit rev.
>
> Yes, although again this would be better done outside the performance<= br> > harness as an OPAM pin for the local environment.=C2=A0 Just having th= e
> ability to quickly run a performance test would be invaluable at this<= br> > stage.

so the caller of the script will

+ select their opam switch
+ pin any libraries, whether to PRs or particular commit-revs
+ record the environment configuration

+ then run the script, specifying the test to run, which will
=C2=A0 + start the unikernel-under-test
=C2=A0 + start any testing-unikernels (eg., iperf-client, iperf-server)
=C2=A0 + collect and record test results

...right?

ultimately i was thinking to have the recorded test results put in a
repo somewhere too, so that they could be visualised, compared to a
benchmark, etc.

>> just to be clear -- you mean does iperf via unikernels, ie., all t= he
>> tests that are executed should also be unikernels rather than stan= dard
>> tools so that we don't take dependencies on an underlying plat= form
>> like the dom0?
>
> Yes -- Xen unikernels would be the primary target.

cool. less shell hacking, more unikernel hacking :)

> Starting and stopping VMs in open source Xen can be bit of a pain, so<= br> > it would be ok if the test harness used XenServer (which the ARM SDcar= d
> images now include).=C2=A0 Jon or Dave could comment on the state of t= he XMLRPC
> OCaml bindings to XenServer...

that would be useful. is it easy to get xenserver installed on x86 a= s
well? (that's the platform masoud is mostly working on.)

x86 as well? What is this, 2014? :-) Your options are= :

1. install the latest 6.5 release of xenserver o= n bare metal

Pros: this is well tested and will wo= rk very well as a virtualisation platform
Cons: it takes over a w= hole machine. To do unikernel development you'll need to install a dev = VM i.e. you can't do it in dom0. It's good practice to leave dom0 a= lone anyway. Think of it like a black box which can run VMs.

=
2. build the latest version from source and install on a CentOS = 6/7 or maybe Ubuntu box

Pros: you can do whatever = you want with dom0
Cons: some aspect of running VMs/ managing net= works / managing storage is bound to not work and you'll need to debug = it. There is little automated testing of this configuration, I (also Euan, = Jon) try to fix bugs when I/we encounter them on a best-effort basis.
=

If you want to focus on unikernel dev and test, I recom= mend option 1. If you want a new hobby of debugging VM hosting software, th= en try option 2.

In the long run ... we'll con= verge option 1 and option 2... but I wouldn't wait.

Cheers,
Dave
=C2=A0

>> cool... (one day i must learn about the cambridge infrastructure m= achines :)
>
> Be careful what you wish for :)

now i'm genuinely curious... :)

--
Richard Mortier
richard.mortier@cl.cam.ac.u= k

_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists= .xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo= /mirageos-devel



--
=
Dave Scott
--047d7b6d9472a63305050f1f7727-- --===============6935924776236578710== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --===============6935924776236578710==-- From mirageos-devel-bounces@lists.xenproject.org Sun Feb 15 12:18:42 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 15 Feb 2015 12:18:42 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YMy9j-0007gq-UU; Sun, 15 Feb 2015 12:18:35 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YMy9i-0007gl-FS for MirageOS-devel@lists.xenproject.org; Sun, 15 Feb 2015 12:18:34 +0000 Received: from [193.109.254.147] by server-15.bemta-14.messagelabs.com id 04/EE-02770-99E80E45; Sun, 15 Feb 2015 12:18:33 +0000 X-Env-Sender: scott.dj@gmail.com X-Msg-Ref: server-13.tower-27.messagelabs.com!1424002709!13567074!1 X-Originating-IP: [209.85.192.170] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE, RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27974 invoked from network); 15 Feb 2015 12:18:31 -0000 Received: from mail-pd0-f170.google.com (HELO mail-pd0-f170.google.com) (209.85.192.170) by server-13.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 15 Feb 2015 12:18:31 -0000 Received: by pdbfl12 with SMTP id fl12so29210988pdb.2 for ; Sun, 15 Feb 2015 04:18:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=H7zI46H5fuZxuToICoL+Q9JsUNjX8HbaZ51IErmVioY=; b=cK2lDbBYvqWWuLywudddHy0YmitN7n+Fw9cq9Z9Uca8hsuqURtVPl4oYmklLzDg+pp Gen3zaSAiCrnB56mokRHqEHxV9hzZ6B/1EnnEOOA5rg4hIyrLDH7kCnjjc0aW+hgpbA0 MGzcx41qu/C33ICJzp3tmR72eo/IjOZjqP+BtDYZ45J1TOXvmfwm57iqxYdc5jl8IpyW oY8UKRdUCyVlknBOgpbW/Df/PMpT7nsrSXagfZGZbt0TaU0K/i3WuP0dPcHcZmK6RVvN GXgoNzR9isut+jq+2jMqEZBI6q6msti7cMvpOujP6t8aARhpHA01201K/EU1iCm6IKTK gKjg== MIME-Version: 1.0 X-Received: by 10.66.164.66 with SMTP id yo2mr24790603pab.59.1424002709335; Sun, 15 Feb 2015 04:18:29 -0800 (PST) Received: by 10.70.102.39 with HTTP; Sun, 15 Feb 2015 04:18:29 -0800 (PST) In-Reply-To: References: <9C6275D4-2397-45E7-B18A-81A47C317545@recoil.org> Date: Sun, 15 Feb 2015 12:18:29 +0000 Message-ID: From: David Scott To: Richard Mortier Cc: mirageos-devel , Anil Madhavapeddy Subject: Re: [MirageOS-devel] performance regression tests X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============6935924776236578710==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============6935924776236578710== Content-Type: multipart/alternative; boundary=047d7b6d9472a63305050f1f7727 --047d7b6d9472a63305050f1f7727 Content-Type: text/plain; charset=UTF-8 On Sun, Feb 15, 2015 at 11:52 AM, Richard Mortier < richard.mortier@cl.cam.ac.uk> wrote: > On 15 February 2015 at 11:28, Anil Madhavapeddy wrote: > > On 15 Feb 2015, at 11:19, Richard Mortier > wrote: > >> > >> On 15 February 2015 at 11:15, Anil Madhavapeddy > wrote: > >>> This is great to see -- thanks for working on this Masoud! > >>> > >>> In particular, having even a simple iperf test would let us test > >>> several interesting combinations straight away: > >>> > >>> - vary OCaml version (4.01 vs 4.02 is now supported), and there > >>> is an experimental inlining branch in 4.03dev that could directly > >>> be tested using this infrastructure. > >> > >> ok-- so i guess that needs a switch/env var to specify the `opam > switch` to use? > > > > Yeah. Although from the performance scripts' perspective, it's better > > if they just assume that there is a working OPAM environment. It would > > be easier to control these parameters from outside, and keep the perf > > scripts as easy to run as possible. > > ah-- original thinking was to make `mir-perf.sh` a harness that might > be fired by `git-bisect`. > > if it's just to be a script to run a single experiment (parameter set) > in a pre-configured environment, then that's a lot simpler. > > > A couple of other things that might help: > > > > - Luke Dunstan has a rather comprehensive acceptance test suite for > > MDNS: > https://github.com/infidel/ocaml-mdns/tree/master/lib_test/acceptance > > > > - OCamlPro has a benchmarking system for core OCaml here that may have > > some useful libraries: https://github.com/OCamlPro/operf-macro > > > > - Performance tests could be wrapped using Core_bench, which > > does linear regression across runs. > > > https://realworldocaml.org/v1/en/html/understanding-the-garbage-collector.html#the-mutable-write-barrier > > > > cool, ta. > > >>> - evaluate the impact of some features incoming such as the open > >>> RFC for checksum offload. > >> > >> how are they specified -- as a PR? > >> in which case, masoud-- i guess that > >> https://help.github.com/articles/checking-out-pull-requests-locally/ > >> is a starting point for how to specify a particular PR rather than > >> simply a commit rev. > > > > Yes, although again this would be better done outside the performance > > harness as an OPAM pin for the local environment. Just having the > > ability to quickly run a performance test would be invaluable at this > > stage. > > so the caller of the script will > > + select their opam switch > + pin any libraries, whether to PRs or particular commit-revs > + record the environment configuration > > + then run the script, specifying the test to run, which will > + start the unikernel-under-test > + start any testing-unikernels (eg., iperf-client, iperf-server) > + collect and record test results > > ...right? > > ultimately i was thinking to have the recorded test results put in a > repo somewhere too, so that they could be visualised, compared to a > benchmark, etc. > > >> just to be clear -- you mean does iperf via unikernels, ie., all the > >> tests that are executed should also be unikernels rather than standard > >> tools so that we don't take dependencies on an underlying platform > >> like the dom0? > > > > Yes -- Xen unikernels would be the primary target. > > cool. less shell hacking, more unikernel hacking :) > > > Starting and stopping VMs in open source Xen can be bit of a pain, so > > it would be ok if the test harness used XenServer (which the ARM SDcard > > images now include). Jon or Dave could comment on the state of the > XMLRPC > > OCaml bindings to XenServer... > > that would be useful. is it easy to get xenserver installed on x86 as > well? (that's the platform masoud is mostly working on.) > x86 as well? What is this, 2014? :-) Your options are: 1. install the latest 6.5 release of xenserver on bare metal Pros: this is well tested and will work very well as a virtualisation platform Cons: it takes over a whole machine. To do unikernel development you'll need to install a dev VM i.e. you can't do it in dom0. It's good practice to leave dom0 alone anyway. Think of it like a black box which can run VMs. 2. build the latest version from source and install on a CentOS 6/7 or maybe Ubuntu box Pros: you can do whatever you want with dom0 Cons: some aspect of running VMs/ managing networks / managing storage is bound to not work and you'll need to debug it. There is little automated testing of this configuration, I (also Euan, Jon) try to fix bugs when I/we encounter them on a best-effort basis. If you want to focus on unikernel dev and test, I recommend option 1. If you want a new hobby of debugging VM hosting software, then try option 2. In the long run ... we'll converge option 1 and option 2... but I wouldn't wait. Cheers, Dave > > >> cool... (one day i must learn about the cambridge infrastructure > machines :) > > > > Be careful what you wish for :) > > now i'm genuinely curious... :) > > -- > Richard Mortier > richard.mortier@cl.cam.ac.uk > > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > -- Dave Scott --047d7b6d9472a63305050f1f7727 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


On Sun, Feb 15, 2015 at 11:52 AM, Richard Mortier <= ;richard.= mortier@cl.cam.ac.uk> wrote:
On 15 February 2015 at 11:28, Anil Madhavapeddy <anil@recoil.org> wrote:
> On 15 Feb 2015, at 11:19, Richard Mortier <richard.mortier@cl.cam.ac.uk> wrote:
>>
>> On 15 February 2015 at 11:15, Anil Madhavapeddy <anil@recoil.org> wrote:
>>> This is great to see -- thanks for working on this Masoud!
>>>
>>> In particular, having even a simple iperf test would let us te= st
>>> several interesting combinations straight away:
>>>
>>> - vary OCaml version (4.01 vs 4.02 is now supported), and ther= e
>>>=C2=A0 is an experimental inlining branch in 4.03dev that could= directly
>>>=C2=A0 be tested using this infrastructure.
>>
>> ok-- so i guess that needs a switch/env var to specify the `opam s= witch` to use?
>
> Yeah.=C2=A0 Although from the performance scripts' perspective, it= 's better
> if they just assume that there is a working OPAM environment.=C2=A0 It= would
> be easier to control these parameters from outside, and keep the perf<= br> > scripts as easy to run as possible.

ah-- original thinking was to make `mir-perf.sh` a harness that migh= t
be fired by `git-bisect`.

if it's just to be a script to run a single experiment (parameter set)<= br> in a pre-configured environment, then that's a lot simpler.

> A couple of other things that might help:
>
> - Luke Dunstan has a rather comprehensive acceptance test suite for >=C2=A0 =C2=A0MDNS: https://github.com/infidel/= ocaml-mdns/tree/master/lib_test/acceptance
>
> - OCamlPro has a benchmarking system for core OCaml here that may have=
>=C2=A0 =C2=A0some useful libraries: https://github.com/OCamlPro/operf-macro<= /a>
>
> - Performance tests could be wrapped using Core_bench, which
>=C2=A0 =C2=A0does linear regression across runs.
>=C2=A0 =C2=A0https://realworldocaml.org/v1/en/html/understanding-the-garbage-collector= .html#the-mutable-write-barrier
>

cool, ta.

>>> - evaluate the impact of some features incoming such as the op= en
>>>=C2=A0 RFC for checksum offload.
>>
>> how are they specified -- as a PR?
>> in which case, masoud-- i guess that
>> https://help.github.com/articles/checking-= out-pull-requests-locally/
>> is a starting point for how to specify a particular PR rather than=
>> simply a commit rev.
>
> Yes, although again this would be better done outside the performance<= br> > harness as an OPAM pin for the local environment.=C2=A0 Just having th= e
> ability to quickly run a performance test would be invaluable at this<= br> > stage.

so the caller of the script will

+ select their opam switch
+ pin any libraries, whether to PRs or particular commit-revs
+ record the environment configuration

+ then run the script, specifying the test to run, which will
=C2=A0 + start the unikernel-under-test
=C2=A0 + start any testing-unikernels (eg., iperf-client, iperf-server)
=C2=A0 + collect and record test results

...right?

ultimately i was thinking to have the recorded test results put in a
repo somewhere too, so that they could be visualised, compared to a
benchmark, etc.

>> just to be clear -- you mean does iperf via unikernels, ie., all t= he
>> tests that are executed should also be unikernels rather than stan= dard
>> tools so that we don't take dependencies on an underlying plat= form
>> like the dom0?
>
> Yes -- Xen unikernels would be the primary target.

cool. less shell hacking, more unikernel hacking :)

> Starting and stopping VMs in open source Xen can be bit of a pain, so<= br> > it would be ok if the test harness used XenServer (which the ARM SDcar= d
> images now include).=C2=A0 Jon or Dave could comment on the state of t= he XMLRPC
> OCaml bindings to XenServer...

that would be useful. is it easy to get xenserver installed on x86 a= s
well? (that's the platform masoud is mostly working on.)

x86 as well? What is this, 2014? :-) Your options are= :

1. install the latest 6.5 release of xenserver o= n bare metal

Pros: this is well tested and will wo= rk very well as a virtualisation platform
Cons: it takes over a w= hole machine. To do unikernel development you'll need to install a dev = VM i.e. you can't do it in dom0. It's good practice to leave dom0 a= lone anyway. Think of it like a black box which can run VMs.

=
2. build the latest version from source and install on a CentOS = 6/7 or maybe Ubuntu box

Pros: you can do whatever = you want with dom0
Cons: some aspect of running VMs/ managing net= works / managing storage is bound to not work and you'll need to debug = it. There is little automated testing of this configuration, I (also Euan, = Jon) try to fix bugs when I/we encounter them on a best-effort basis.
=

If you want to focus on unikernel dev and test, I recom= mend option 1. If you want a new hobby of debugging VM hosting software, th= en try option 2.

In the long run ... we'll con= verge option 1 and option 2... but I wouldn't wait.

Cheers,
Dave
=C2=A0

>> cool... (one day i must learn about the cambridge infrastructure m= achines :)
>
> Be careful what you wish for :)

now i'm genuinely curious... :)

--
Richard Mortier
richard.mortier@cl.cam.ac.u= k

_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists= .xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo= /mirageos-devel



--
=
Dave Scott
--047d7b6d9472a63305050f1f7727-- --===============6935924776236578710== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --===============6935924776236578710==-- From mirageos-devel-bounces@lists.xenproject.org Sun Feb 15 12:50:33 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 15 Feb 2015 12:50:33 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YMyed-00018N-QE; Sun, 15 Feb 2015 12:50:31 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YMyec-00018I-Co for MirageOS-devel@lists.xenproject.org; Sun, 15 Feb 2015 12:50:30 +0000 Received: from [193.109.254.147] by server-14.bemta-14.messagelabs.com id C4/24-02753-51690E45; Sun, 15 Feb 2015 12:50:29 +0000 X-Env-Sender: richard.mortier@gmail.com X-Msg-Ref: server-8.tower-27.messagelabs.com!1424004627!13584825!1 X-Originating-IP: [209.85.216.182] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 1939 invoked from network); 15 Feb 2015 12:50:28 -0000 Received: from mail-qc0-f182.google.com (HELO mail-qc0-f182.google.com) (209.85.216.182) by server-8.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 15 Feb 2015 12:50:28 -0000 Received: by mail-qc0-f182.google.com with SMTP id r5so6956424qcx.13 for ; Sun, 15 Feb 2015 04:50:27 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=MxR86TNrNjigjHHfthepxkV8wOJAAKe5lR/JaD07V1g=; b=me+ToaCWEntulBXXrkWDsKZlirV8Law1lxymErSe7ZRfZpJpeE6V0uJQthdMbos8OQ 67cGahlaJMRnWvo00m2Ra26dZbVRQLnzxTbIwpI1Wk4RI44yZkfqC/86bdEA9PmPRMvS IRT3Kd0c83daS0ShcDPeDDBJwOGHxr079rk9k00MbkUS/eSMWFK4l1joiIpQW8A8zCXA C4cMcdvrBYHj2sFSFmGlDTdSpK1Q62uPXO6wU+IE6PJHfOGjfWvjHdVRYRYumNy2RSN1 vRxbbKC25NK42tgK2hnqq007dJ6pBFpJVPaoaj71IibcLTkHcUZohiHAT2MZI2kL4fK3 Tg0g== X-Received: by 10.140.88.80 with SMTP id s74mr8377434qgd.28.1424004627221; Sun, 15 Feb 2015 04:50:27 -0800 (PST) Received: from mail-qc0-f176.google.com (mail-qc0-f176.google.com. [209.85.216.176]) by mx.google.com with ESMTPSA id w107sm11566123qge.5.2015.02.15.04.50.26 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 15 Feb 2015 04:50:27 -0800 (PST) Received: by mail-qc0-f176.google.com with SMTP id b13so14571703qcw.7 for ; Sun, 15 Feb 2015 04:50:26 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.140.134.198 with SMTP id 189mr17297958qhg.7.1424004626355; Sun, 15 Feb 2015 04:50:26 -0800 (PST) Received: by 10.140.92.245 with HTTP; Sun, 15 Feb 2015 04:50:26 -0800 (PST) In-Reply-To: References: <9C6275D4-2397-45E7-B18A-81A47C317545@recoil.org> Date: Sun, 15 Feb 2015 12:50:26 +0000 Message-ID: From: Richard Mortier To: David Scott Cc: mirageos-devel , Anil Madhavapeddy Subject: Re: [MirageOS-devel] performance regression tests X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org yes, it's still the 2014/15 academic year :p i suspect i know the answer to this but just in case: i presume by "bare metal" you really do mean bare metal? ie., inside a virtualbox is not going to work? masoud-- if that's the case, i'll pick this up with you offline. there's a server in nottingham that you should be able to get access to and do what you want with. i originally put xen on it by hand and used the xm/xl tools, but it sounds like it might be time to wipe it and start again with xenserver. On 15 February 2015 at 12:18, David Scott wrote: > > > On Sun, Feb 15, 2015 at 11:52 AM, Richard Mortier > wrote: >> >> On 15 February 2015 at 11:28, Anil Madhavapeddy wrote: >> > On 15 Feb 2015, at 11:19, Richard Mortier >> > wrote: >> >> >> >> On 15 February 2015 at 11:15, Anil Madhavapeddy >> >> wrote: >> >>> This is great to see -- thanks for working on this Masoud! >> >>> >> >>> In particular, having even a simple iperf test would let us test >> >>> several interesting combinations straight away: >> >>> >> >>> - vary OCaml version (4.01 vs 4.02 is now supported), and there >> >>> is an experimental inlining branch in 4.03dev that could directly >> >>> be tested using this infrastructure. >> >> >> >> ok-- so i guess that needs a switch/env var to specify the `opam >> >> switch` to use? >> > >> > Yeah. Although from the performance scripts' perspective, it's better >> > if they just assume that there is a working OPAM environment. It would >> > be easier to control these parameters from outside, and keep the perf >> > scripts as easy to run as possible. >> >> ah-- original thinking was to make `mir-perf.sh` a harness that might >> be fired by `git-bisect`. >> >> if it's just to be a script to run a single experiment (parameter set) >> in a pre-configured environment, then that's a lot simpler. >> >> > A couple of other things that might help: >> > >> > - Luke Dunstan has a rather comprehensive acceptance test suite for >> > MDNS: >> > https://github.com/infidel/ocaml-mdns/tree/master/lib_test/acceptance >> > >> > - OCamlPro has a benchmarking system for core OCaml here that may have >> > some useful libraries: https://github.com/OCamlPro/operf-macro >> > >> > - Performance tests could be wrapped using Core_bench, which >> > does linear regression across runs. >> > >> > https://realworldocaml.org/v1/en/html/understanding-the-garbage-collector.html#the-mutable-write-barrier >> > >> >> cool, ta. >> >> >>> - evaluate the impact of some features incoming such as the open >> >>> RFC for checksum offload. >> >> >> >> how are they specified -- as a PR? >> >> in which case, masoud-- i guess that >> >> https://help.github.com/articles/checking-out-pull-requests-locally/ >> >> is a starting point for how to specify a particular PR rather than >> >> simply a commit rev. >> > >> > Yes, although again this would be better done outside the performance >> > harness as an OPAM pin for the local environment. Just having the >> > ability to quickly run a performance test would be invaluable at this >> > stage. >> >> so the caller of the script will >> >> + select their opam switch >> + pin any libraries, whether to PRs or particular commit-revs >> + record the environment configuration >> >> + then run the script, specifying the test to run, which will >> + start the unikernel-under-test >> + start any testing-unikernels (eg., iperf-client, iperf-server) >> + collect and record test results >> >> ...right? >> >> ultimately i was thinking to have the recorded test results put in a >> repo somewhere too, so that they could be visualised, compared to a >> benchmark, etc. >> >> >> just to be clear -- you mean does iperf via unikernels, ie., all the >> >> tests that are executed should also be unikernels rather than standard >> >> tools so that we don't take dependencies on an underlying platform >> >> like the dom0? >> > >> > Yes -- Xen unikernels would be the primary target. >> >> cool. less shell hacking, more unikernel hacking :) >> >> > Starting and stopping VMs in open source Xen can be bit of a pain, so >> > it would be ok if the test harness used XenServer (which the ARM SDcard >> > images now include). Jon or Dave could comment on the state of the >> > XMLRPC >> > OCaml bindings to XenServer... >> >> that would be useful. is it easy to get xenserver installed on x86 as >> well? (that's the platform masoud is mostly working on.) > > > x86 as well? What is this, 2014? :-) Your options are: > > 1. install the latest 6.5 release of xenserver on bare metal > > Pros: this is well tested and will work very well as a virtualisation > platform > Cons: it takes over a whole machine. To do unikernel development you'll need > to install a dev VM i.e. you can't do it in dom0. It's good practice to > leave dom0 alone anyway. Think of it like a black box which can run VMs. > > 2. build the latest version from source and install on a CentOS 6/7 or maybe > Ubuntu box > > Pros: you can do whatever you want with dom0 > Cons: some aspect of running VMs/ managing networks / managing storage is > bound to not work and you'll need to debug it. There is little automated > testing of this configuration, I (also Euan, Jon) try to fix bugs when I/we > encounter them on a best-effort basis. > > If you want to focus on unikernel dev and test, I recommend option 1. If you > want a new hobby of debugging VM hosting software, then try option 2. > > In the long run ... we'll converge option 1 and option 2... but I wouldn't > wait. > > Cheers, > Dave > >> >> >> >> cool... (one day i must learn about the cambridge infrastructure >> >> machines :) >> > >> > Be careful what you wish for :) >> >> now i'm genuinely curious... :) >> >> -- >> Richard Mortier >> richard.mortier@cl.cam.ac.uk >> >> _______________________________________________ >> MirageOS-devel mailing list >> MirageOS-devel@lists.xenproject.org >> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > > > > > -- > Dave Scott -- Richard Mortier richard.mortier@cl.cam.ac.uk _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Sun Feb 15 12:50:33 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 15 Feb 2015 12:50:33 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YMyed-00018N-QE; Sun, 15 Feb 2015 12:50:31 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YMyec-00018I-Co for MirageOS-devel@lists.xenproject.org; Sun, 15 Feb 2015 12:50:30 +0000 Received: from [193.109.254.147] by server-14.bemta-14.messagelabs.com id C4/24-02753-51690E45; Sun, 15 Feb 2015 12:50:29 +0000 X-Env-Sender: richard.mortier@gmail.com X-Msg-Ref: server-8.tower-27.messagelabs.com!1424004627!13584825!1 X-Originating-IP: [209.85.216.182] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 1939 invoked from network); 15 Feb 2015 12:50:28 -0000 Received: from mail-qc0-f182.google.com (HELO mail-qc0-f182.google.com) (209.85.216.182) by server-8.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 15 Feb 2015 12:50:28 -0000 Received: by mail-qc0-f182.google.com with SMTP id r5so6956424qcx.13 for ; Sun, 15 Feb 2015 04:50:27 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=MxR86TNrNjigjHHfthepxkV8wOJAAKe5lR/JaD07V1g=; b=me+ToaCWEntulBXXrkWDsKZlirV8Law1lxymErSe7ZRfZpJpeE6V0uJQthdMbos8OQ 67cGahlaJMRnWvo00m2Ra26dZbVRQLnzxTbIwpI1Wk4RI44yZkfqC/86bdEA9PmPRMvS IRT3Kd0c83daS0ShcDPeDDBJwOGHxr079rk9k00MbkUS/eSMWFK4l1joiIpQW8A8zCXA C4cMcdvrBYHj2sFSFmGlDTdSpK1Q62uPXO6wU+IE6PJHfOGjfWvjHdVRYRYumNy2RSN1 vRxbbKC25NK42tgK2hnqq007dJ6pBFpJVPaoaj71IibcLTkHcUZohiHAT2MZI2kL4fK3 Tg0g== X-Received: by 10.140.88.80 with SMTP id s74mr8377434qgd.28.1424004627221; Sun, 15 Feb 2015 04:50:27 -0800 (PST) Received: from mail-qc0-f176.google.com (mail-qc0-f176.google.com. [209.85.216.176]) by mx.google.com with ESMTPSA id w107sm11566123qge.5.2015.02.15.04.50.26 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 15 Feb 2015 04:50:27 -0800 (PST) Received: by mail-qc0-f176.google.com with SMTP id b13so14571703qcw.7 for ; Sun, 15 Feb 2015 04:50:26 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.140.134.198 with SMTP id 189mr17297958qhg.7.1424004626355; Sun, 15 Feb 2015 04:50:26 -0800 (PST) Received: by 10.140.92.245 with HTTP; Sun, 15 Feb 2015 04:50:26 -0800 (PST) In-Reply-To: References: <9C6275D4-2397-45E7-B18A-81A47C317545@recoil.org> Date: Sun, 15 Feb 2015 12:50:26 +0000 Message-ID: From: Richard Mortier To: David Scott Cc: mirageos-devel , Anil Madhavapeddy Subject: Re: [MirageOS-devel] performance regression tests X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org yes, it's still the 2014/15 academic year :p i suspect i know the answer to this but just in case: i presume by "bare metal" you really do mean bare metal? ie., inside a virtualbox is not going to work? masoud-- if that's the case, i'll pick this up with you offline. there's a server in nottingham that you should be able to get access to and do what you want with. i originally put xen on it by hand and used the xm/xl tools, but it sounds like it might be time to wipe it and start again with xenserver. On 15 February 2015 at 12:18, David Scott wrote: > > > On Sun, Feb 15, 2015 at 11:52 AM, Richard Mortier > wrote: >> >> On 15 February 2015 at 11:28, Anil Madhavapeddy wrote: >> > On 15 Feb 2015, at 11:19, Richard Mortier >> > wrote: >> >> >> >> On 15 February 2015 at 11:15, Anil Madhavapeddy >> >> wrote: >> >>> This is great to see -- thanks for working on this Masoud! >> >>> >> >>> In particular, having even a simple iperf test would let us test >> >>> several interesting combinations straight away: >> >>> >> >>> - vary OCaml version (4.01 vs 4.02 is now supported), and there >> >>> is an experimental inlining branch in 4.03dev that could directly >> >>> be tested using this infrastructure. >> >> >> >> ok-- so i guess that needs a switch/env var to specify the `opam >> >> switch` to use? >> > >> > Yeah. Although from the performance scripts' perspective, it's better >> > if they just assume that there is a working OPAM environment. It would >> > be easier to control these parameters from outside, and keep the perf >> > scripts as easy to run as possible. >> >> ah-- original thinking was to make `mir-perf.sh` a harness that might >> be fired by `git-bisect`. >> >> if it's just to be a script to run a single experiment (parameter set) >> in a pre-configured environment, then that's a lot simpler. >> >> > A couple of other things that might help: >> > >> > - Luke Dunstan has a rather comprehensive acceptance test suite for >> > MDNS: >> > https://github.com/infidel/ocaml-mdns/tree/master/lib_test/acceptance >> > >> > - OCamlPro has a benchmarking system for core OCaml here that may have >> > some useful libraries: https://github.com/OCamlPro/operf-macro >> > >> > - Performance tests could be wrapped using Core_bench, which >> > does linear regression across runs. >> > >> > https://realworldocaml.org/v1/en/html/understanding-the-garbage-collector.html#the-mutable-write-barrier >> > >> >> cool, ta. >> >> >>> - evaluate the impact of some features incoming such as the open >> >>> RFC for checksum offload. >> >> >> >> how are they specified -- as a PR? >> >> in which case, masoud-- i guess that >> >> https://help.github.com/articles/checking-out-pull-requests-locally/ >> >> is a starting point for how to specify a particular PR rather than >> >> simply a commit rev. >> > >> > Yes, although again this would be better done outside the performance >> > harness as an OPAM pin for the local environment. Just having the >> > ability to quickly run a performance test would be invaluable at this >> > stage. >> >> so the caller of the script will >> >> + select their opam switch >> + pin any libraries, whether to PRs or particular commit-revs >> + record the environment configuration >> >> + then run the script, specifying the test to run, which will >> + start the unikernel-under-test >> + start any testing-unikernels (eg., iperf-client, iperf-server) >> + collect and record test results >> >> ...right? >> >> ultimately i was thinking to have the recorded test results put in a >> repo somewhere too, so that they could be visualised, compared to a >> benchmark, etc. >> >> >> just to be clear -- you mean does iperf via unikernels, ie., all the >> >> tests that are executed should also be unikernels rather than standard >> >> tools so that we don't take dependencies on an underlying platform >> >> like the dom0? >> > >> > Yes -- Xen unikernels would be the primary target. >> >> cool. less shell hacking, more unikernel hacking :) >> >> > Starting and stopping VMs in open source Xen can be bit of a pain, so >> > it would be ok if the test harness used XenServer (which the ARM SDcard >> > images now include). Jon or Dave could comment on the state of the >> > XMLRPC >> > OCaml bindings to XenServer... >> >> that would be useful. is it easy to get xenserver installed on x86 as >> well? (that's the platform masoud is mostly working on.) > > > x86 as well? What is this, 2014? :-) Your options are: > > 1. install the latest 6.5 release of xenserver on bare metal > > Pros: this is well tested and will work very well as a virtualisation > platform > Cons: it takes over a whole machine. To do unikernel development you'll need > to install a dev VM i.e. you can't do it in dom0. It's good practice to > leave dom0 alone anyway. Think of it like a black box which can run VMs. > > 2. build the latest version from source and install on a CentOS 6/7 or maybe > Ubuntu box > > Pros: you can do whatever you want with dom0 > Cons: some aspect of running VMs/ managing networks / managing storage is > bound to not work and you'll need to debug it. There is little automated > testing of this configuration, I (also Euan, Jon) try to fix bugs when I/we > encounter them on a best-effort basis. > > If you want to focus on unikernel dev and test, I recommend option 1. If you > want a new hobby of debugging VM hosting software, then try option 2. > > In the long run ... we'll converge option 1 and option 2... but I wouldn't > wait. > > Cheers, > Dave > >> >> >> >> cool... (one day i must learn about the cambridge infrastructure >> >> machines :) >> > >> > Be careful what you wish for :) >> >> now i'm genuinely curious... :) >> >> -- >> Richard Mortier >> richard.mortier@cl.cam.ac.uk >> >> _______________________________________________ >> MirageOS-devel mailing list >> MirageOS-devel@lists.xenproject.org >> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > > > > > -- > Dave Scott -- Richard Mortier richard.mortier@cl.cam.ac.uk _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Sun Feb 15 13:54:40 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 15 Feb 2015 13:54:40 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YMzef-0005El-TJ; Sun, 15 Feb 2015 13:54:37 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YMzef-0005Ee-79 for MirageOS-devel@lists.xenproject.org; Sun, 15 Feb 2015 13:54:37 +0000 Received: from [85.158.139.211] by server-9.bemta-5.messagelabs.com id C7/40-02991-C15A0E45; Sun, 15 Feb 2015 13:54:36 +0000 X-Env-Sender: jjl25@cam.ac.uk X-Msg-Ref: server-13.tower-206.messagelabs.com!1424008475!12048007!1 X-Originating-IP: [131.111.8.152] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTMxLjExMS44LjE1MiA9PiA4MDU1Mw==\n X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4180 invoked from network); 15 Feb 2015 13:54:35 -0000 Received: from ppsw-52.csi.cam.ac.uk (HELO ppsw-52.csi.cam.ac.uk) (131.111.8.152) by server-13.tower-206.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 15 Feb 2015 13:54:35 -0000 X-Cam-AntiVirus: no malware found X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/ Received: from cpc16-cmbg14-2-0-cust188.5-4.cable.virginm.net ([86.6.156.189]:53310 helo=[192.168.1.139]) by ppsw-52.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.159]:587) with esmtpsa (PLAIN:jjl25) (TLSv1:DHE-RSA-AES256-SHA:256) id 1YMzeb-0000ql-Cv (Exim 4.82_3-c0e5623) (return-path ); Sun, 15 Feb 2015 13:54:33 +0000 References: <9C6275D4-2397-45E7-B18A-81A47C317545@recoil.org> Mime-Version: 1.0 (1.0) In-Reply-To: Message-Id: <88230342-7010-413A-8270-D36D1CD0D1D4@cam.ac.uk> X-Mailer: iPad Mail (12B466) From: Jon Ludlam Date: Sun, 15 Feb 2015 13:54:33 +0000 To: Richard Mortier Cc: mirageos-devel , Anil Madhavapeddy Subject: Re: [MirageOS-devel] performance regression tests X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org Virtualbox should work actually. I did have a vagrant box with xenserver 6.2 sp1 on it, but it was hosted on jon.recoil.org which has now been replaced with a tiny unikernel. I can try to dig it up this evening to see if it still works. I could stick it on blobs.openmirage.org maybe? Jon Sent from my iPad > On 15 Feb 2015, at 12:50, Richard Mortier wrote: > > yes, it's still the 2014/15 academic year :p > > i suspect i know the answer to this but just in case: i presume by > "bare metal" you really do mean bare metal? ie., inside a virtualbox > is not going to work? > > masoud-- if that's the case, i'll pick this up with you offline. > there's a server in nottingham that you should be able to get access > to and do what you want with. i originally put xen on it by hand and > used the xm/xl tools, but it sounds like it might be time to wipe it > and start again with xenserver. > > >> On 15 February 2015 at 12:18, David Scott wrote: >> >> >> On Sun, Feb 15, 2015 at 11:52 AM, Richard Mortier >> wrote: >>> >>>> On 15 February 2015 at 11:28, Anil Madhavapeddy wrote: >>>> On 15 Feb 2015, at 11:19, Richard Mortier >>>> wrote: >>>>> >>>>> On 15 February 2015 at 11:15, Anil Madhavapeddy >>>>> wrote: >>>>>> This is great to see -- thanks for working on this Masoud! >>>>>> >>>>>> In particular, having even a simple iperf test would let us test >>>>>> several interesting combinations straight away: >>>>>> >>>>>> - vary OCaml version (4.01 vs 4.02 is now supported), and there >>>>>> is an experimental inlining branch in 4.03dev that could directly >>>>>> be tested using this infrastructure. >>>>> >>>>> ok-- so i guess that needs a switch/env var to specify the `opam >>>>> switch` to use? >>>> >>>> Yeah. Although from the performance scripts' perspective, it's better >>>> if they just assume that there is a working OPAM environment. It would >>>> be easier to control these parameters from outside, and keep the perf >>>> scripts as easy to run as possible. >>> >>> ah-- original thinking was to make `mir-perf.sh` a harness that might >>> be fired by `git-bisect`. >>> >>> if it's just to be a script to run a single experiment (parameter set) >>> in a pre-configured environment, then that's a lot simpler. >>> >>>> A couple of other things that might help: >>>> >>>> - Luke Dunstan has a rather comprehensive acceptance test suite for >>>> MDNS: >>>> https://github.com/infidel/ocaml-mdns/tree/master/lib_test/acceptance >>>> >>>> - OCamlPro has a benchmarking system for core OCaml here that may have >>>> some useful libraries: https://github.com/OCamlPro/operf-macro >>>> >>>> - Performance tests could be wrapped using Core_bench, which >>>> does linear regression across runs. >>>> >>>> https://realworldocaml.org/v1/en/html/understanding-the-garbage-collector.html#the-mutable-write-barrier >>>> >>> >>> cool, ta. >>> >>>>>> - evaluate the impact of some features incoming such as the open >>>>>> RFC for checksum offload. >>>>> >>>>> how are they specified -- as a PR? >>>>> in which case, masoud-- i guess that >>>>> https://help.github.com/articles/checking-out-pull-requests-locally/ >>>>> is a starting point for how to specify a particular PR rather than >>>>> simply a commit rev. >>>> >>>> Yes, although again this would be better done outside the performance >>>> harness as an OPAM pin for the local environment. Just having the >>>> ability to quickly run a performance test would be invaluable at this >>>> stage. >>> >>> so the caller of the script will >>> >>> + select their opam switch >>> + pin any libraries, whether to PRs or particular commit-revs >>> + record the environment configuration >>> >>> + then run the script, specifying the test to run, which will >>> + start the unikernel-under-test >>> + start any testing-unikernels (eg., iperf-client, iperf-server) >>> + collect and record test results >>> >>> ...right? >>> >>> ultimately i was thinking to have the recorded test results put in a >>> repo somewhere too, so that they could be visualised, compared to a >>> benchmark, etc. >>> >>>>> just to be clear -- you mean does iperf via unikernels, ie., all the >>>>> tests that are executed should also be unikernels rather than standard >>>>> tools so that we don't take dependencies on an underlying platform >>>>> like the dom0? >>>> >>>> Yes -- Xen unikernels would be the primary target. >>> >>> cool. less shell hacking, more unikernel hacking :) >>> >>>> Starting and stopping VMs in open source Xen can be bit of a pain, so >>>> it would be ok if the test harness used XenServer (which the ARM SDcard >>>> images now include). Jon or Dave could comment on the state of the >>>> XMLRPC >>>> OCaml bindings to XenServer... >>> >>> that would be useful. is it easy to get xenserver installed on x86 as >>> well? (that's the platform masoud is mostly working on.) >> >> >> x86 as well? What is this, 2014? :-) Your options are: >> >> 1. install the latest 6.5 release of xenserver on bare metal >> >> Pros: this is well tested and will work very well as a virtualisation >> platform >> Cons: it takes over a whole machine. To do unikernel development you'll need >> to install a dev VM i.e. you can't do it in dom0. It's good practice to >> leave dom0 alone anyway. Think of it like a black box which can run VMs. >> >> 2. build the latest version from source and install on a CentOS 6/7 or maybe >> Ubuntu box >> >> Pros: you can do whatever you want with dom0 >> Cons: some aspect of running VMs/ managing networks / managing storage is >> bound to not work and you'll need to debug it. There is little automated >> testing of this configuration, I (also Euan, Jon) try to fix bugs when I/we >> encounter them on a best-effort basis. >> >> If you want to focus on unikernel dev and test, I recommend option 1. If you >> want a new hobby of debugging VM hosting software, then try option 2. >> >> In the long run ... we'll converge option 1 and option 2... but I wouldn't >> wait. >> >> Cheers, >> Dave >> >>> >>> >>>>> cool... (one day i must learn about the cambridge infrastructure >>>>> machines :) >>>> >>>> Be careful what you wish for :) >>> >>> now i'm genuinely curious... :) >>> >>> -- >>> Richard Mortier >>> richard.mortier@cl.cam.ac.uk >>> >>> _______________________________________________ >>> MirageOS-devel mailing list >>> MirageOS-devel@lists.xenproject.org >>> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel >> >> >> >> >> -- >> Dave Scott > > > > -- > Richard Mortier > richard.mortier@cl.cam.ac.uk > > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Sun Feb 15 13:54:40 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 15 Feb 2015 13:54:40 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YMzef-0005El-TJ; Sun, 15 Feb 2015 13:54:37 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YMzef-0005Ee-79 for MirageOS-devel@lists.xenproject.org; Sun, 15 Feb 2015 13:54:37 +0000 Received: from [85.158.139.211] by server-9.bemta-5.messagelabs.com id C7/40-02991-C15A0E45; Sun, 15 Feb 2015 13:54:36 +0000 X-Env-Sender: jjl25@cam.ac.uk X-Msg-Ref: server-13.tower-206.messagelabs.com!1424008475!12048007!1 X-Originating-IP: [131.111.8.152] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTMxLjExMS44LjE1MiA9PiA4MDU1Mw==\n X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4180 invoked from network); 15 Feb 2015 13:54:35 -0000 Received: from ppsw-52.csi.cam.ac.uk (HELO ppsw-52.csi.cam.ac.uk) (131.111.8.152) by server-13.tower-206.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 15 Feb 2015 13:54:35 -0000 X-Cam-AntiVirus: no malware found X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/ Received: from cpc16-cmbg14-2-0-cust188.5-4.cable.virginm.net ([86.6.156.189]:53310 helo=[192.168.1.139]) by ppsw-52.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.159]:587) with esmtpsa (PLAIN:jjl25) (TLSv1:DHE-RSA-AES256-SHA:256) id 1YMzeb-0000ql-Cv (Exim 4.82_3-c0e5623) (return-path ); Sun, 15 Feb 2015 13:54:33 +0000 References: <9C6275D4-2397-45E7-B18A-81A47C317545@recoil.org> Mime-Version: 1.0 (1.0) In-Reply-To: Message-Id: <88230342-7010-413A-8270-D36D1CD0D1D4@cam.ac.uk> X-Mailer: iPad Mail (12B466) From: Jon Ludlam Date: Sun, 15 Feb 2015 13:54:33 +0000 To: Richard Mortier Cc: mirageos-devel , Anil Madhavapeddy Subject: Re: [MirageOS-devel] performance regression tests X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org Virtualbox should work actually. I did have a vagrant box with xenserver 6.2 sp1 on it, but it was hosted on jon.recoil.org which has now been replaced with a tiny unikernel. I can try to dig it up this evening to see if it still works. I could stick it on blobs.openmirage.org maybe? Jon Sent from my iPad > On 15 Feb 2015, at 12:50, Richard Mortier wrote: > > yes, it's still the 2014/15 academic year :p > > i suspect i know the answer to this but just in case: i presume by > "bare metal" you really do mean bare metal? ie., inside a virtualbox > is not going to work? > > masoud-- if that's the case, i'll pick this up with you offline. > there's a server in nottingham that you should be able to get access > to and do what you want with. i originally put xen on it by hand and > used the xm/xl tools, but it sounds like it might be time to wipe it > and start again with xenserver. > > >> On 15 February 2015 at 12:18, David Scott wrote: >> >> >> On Sun, Feb 15, 2015 at 11:52 AM, Richard Mortier >> wrote: >>> >>>> On 15 February 2015 at 11:28, Anil Madhavapeddy wrote: >>>> On 15 Feb 2015, at 11:19, Richard Mortier >>>> wrote: >>>>> >>>>> On 15 February 2015 at 11:15, Anil Madhavapeddy >>>>> wrote: >>>>>> This is great to see -- thanks for working on this Masoud! >>>>>> >>>>>> In particular, having even a simple iperf test would let us test >>>>>> several interesting combinations straight away: >>>>>> >>>>>> - vary OCaml version (4.01 vs 4.02 is now supported), and there >>>>>> is an experimental inlining branch in 4.03dev that could directly >>>>>> be tested using this infrastructure. >>>>> >>>>> ok-- so i guess that needs a switch/env var to specify the `opam >>>>> switch` to use? >>>> >>>> Yeah. Although from the performance scripts' perspective, it's better >>>> if they just assume that there is a working OPAM environment. It would >>>> be easier to control these parameters from outside, and keep the perf >>>> scripts as easy to run as possible. >>> >>> ah-- original thinking was to make `mir-perf.sh` a harness that might >>> be fired by `git-bisect`. >>> >>> if it's just to be a script to run a single experiment (parameter set) >>> in a pre-configured environment, then that's a lot simpler. >>> >>>> A couple of other things that might help: >>>> >>>> - Luke Dunstan has a rather comprehensive acceptance test suite for >>>> MDNS: >>>> https://github.com/infidel/ocaml-mdns/tree/master/lib_test/acceptance >>>> >>>> - OCamlPro has a benchmarking system for core OCaml here that may have >>>> some useful libraries: https://github.com/OCamlPro/operf-macro >>>> >>>> - Performance tests could be wrapped using Core_bench, which >>>> does linear regression across runs. >>>> >>>> https://realworldocaml.org/v1/en/html/understanding-the-garbage-collector.html#the-mutable-write-barrier >>>> >>> >>> cool, ta. >>> >>>>>> - evaluate the impact of some features incoming such as the open >>>>>> RFC for checksum offload. >>>>> >>>>> how are they specified -- as a PR? >>>>> in which case, masoud-- i guess that >>>>> https://help.github.com/articles/checking-out-pull-requests-locally/ >>>>> is a starting point for how to specify a particular PR rather than >>>>> simply a commit rev. >>>> >>>> Yes, although again this would be better done outside the performance >>>> harness as an OPAM pin for the local environment. Just having the >>>> ability to quickly run a performance test would be invaluable at this >>>> stage. >>> >>> so the caller of the script will >>> >>> + select their opam switch >>> + pin any libraries, whether to PRs or particular commit-revs >>> + record the environment configuration >>> >>> + then run the script, specifying the test to run, which will >>> + start the unikernel-under-test >>> + start any testing-unikernels (eg., iperf-client, iperf-server) >>> + collect and record test results >>> >>> ...right? >>> >>> ultimately i was thinking to have the recorded test results put in a >>> repo somewhere too, so that they could be visualised, compared to a >>> benchmark, etc. >>> >>>>> just to be clear -- you mean does iperf via unikernels, ie., all the >>>>> tests that are executed should also be unikernels rather than standard >>>>> tools so that we don't take dependencies on an underlying platform >>>>> like the dom0? >>>> >>>> Yes -- Xen unikernels would be the primary target. >>> >>> cool. less shell hacking, more unikernel hacking :) >>> >>>> Starting and stopping VMs in open source Xen can be bit of a pain, so >>>> it would be ok if the test harness used XenServer (which the ARM SDcard >>>> images now include). Jon or Dave could comment on the state of the >>>> XMLRPC >>>> OCaml bindings to XenServer... >>> >>> that would be useful. is it easy to get xenserver installed on x86 as >>> well? (that's the platform masoud is mostly working on.) >> >> >> x86 as well? What is this, 2014? :-) Your options are: >> >> 1. install the latest 6.5 release of xenserver on bare metal >> >> Pros: this is well tested and will work very well as a virtualisation >> platform >> Cons: it takes over a whole machine. To do unikernel development you'll need >> to install a dev VM i.e. you can't do it in dom0. It's good practice to >> leave dom0 alone anyway. Think of it like a black box which can run VMs. >> >> 2. build the latest version from source and install on a CentOS 6/7 or maybe >> Ubuntu box >> >> Pros: you can do whatever you want with dom0 >> Cons: some aspect of running VMs/ managing networks / managing storage is >> bound to not work and you'll need to debug it. There is little automated >> testing of this configuration, I (also Euan, Jon) try to fix bugs when I/we >> encounter them on a best-effort basis. >> >> If you want to focus on unikernel dev and test, I recommend option 1. If you >> want a new hobby of debugging VM hosting software, then try option 2. >> >> In the long run ... we'll converge option 1 and option 2... but I wouldn't >> wait. >> >> Cheers, >> Dave >> >>> >>> >>>>> cool... (one day i must learn about the cambridge infrastructure >>>>> machines :) >>>> >>>> Be careful what you wish for :) >>> >>> now i'm genuinely curious... :) >>> >>> -- >>> Richard Mortier >>> richard.mortier@cl.cam.ac.uk >>> >>> _______________________________________________ >>> MirageOS-devel mailing list >>> MirageOS-devel@lists.xenproject.org >>> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel >> >> >> >> >> -- >> Dave Scott > > > > -- > Richard Mortier > richard.mortier@cl.cam.ac.uk > > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Sun Feb 15 14:16:23 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 15 Feb 2015 14:16:23 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YMzzh-0006Zl-IP; Sun, 15 Feb 2015 14:16:21 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YMzzg-0006Zg-Ex for MirageOS-devel@lists.xenproject.org; Sun, 15 Feb 2015 14:16:20 +0000 Received: from [85.158.139.211] by server-6.bemta-5.messagelabs.com id 16/95-03165-33AA0E45; Sun, 15 Feb 2015 14:16:19 +0000 X-Env-Sender: richard.mortier@gmail.com X-Msg-Ref: server-6.tower-206.messagelabs.com!1424009777!12025920!1 X-Originating-IP: [209.85.192.44] X-SpamReason: No, hits=0.6 required=7.0 tests=MAILTO_TO_SPAM_ADDR, RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11309 invoked from network); 15 Feb 2015 14:16:18 -0000 Received: from mail-qg0-f44.google.com (HELO mail-qg0-f44.google.com) (209.85.192.44) by server-6.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 15 Feb 2015 14:16:18 -0000 Received: by mail-qg0-f44.google.com with SMTP id j5so20002321qga.3 for ; Sun, 15 Feb 2015 06:16:17 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=qnQ+QfmTVsRqNZKR9EQIG/m4QOdRURG/mMYIRteicpw=; b=fhyVGQ/I8wDLxDqye8572f8J9NKfZ8l0fLxLszIRLenLfdVMGUUaS+mSgGIYeNfyKm fMwuopNzklithOkzIf6Ah9LUjfNrQXs7xVSU1s9U/1N2cCZlI3GHp8MpL4nZSZgUjHWt 9q4EWLBwviWVM5vChoAdNGdQWjF+3JWGcqULbmN6wZIF2fpmHQmmBwEJxNVJuHcp6w38 j53x8OCrmU4XmihjFdDfMPQgSxG50fILvGdVCemlc3E6G4masr5oA39fUcZ6pTlWdjOk cf9CUbawSF4Dkey6cavh2xXb5lGtqUgmeoYxvKQ0p20L9QnDGFWlUeDl50EXpWHpjjFG sPgw== X-Received: by 10.140.150.87 with SMTP id 84mr18989489qhw.64.1424009776941; Sun, 15 Feb 2015 06:16:16 -0800 (PST) Received: from mail-qc0-f169.google.com (mail-qc0-f169.google.com. [209.85.216.169]) by mx.google.com with ESMTPSA id u3sm11719425qat.22.2015.02.15.06.16.15 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 15 Feb 2015 06:16:16 -0800 (PST) Received: by mail-qc0-f169.google.com with SMTP id m20so20512642qcx.0 for ; Sun, 15 Feb 2015 06:16:15 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.229.65.8 with SMTP id g8mr20627893qci.15.1424009775859; Sun, 15 Feb 2015 06:16:15 -0800 (PST) Received: by 10.140.92.245 with HTTP; Sun, 15 Feb 2015 06:16:15 -0800 (PST) In-Reply-To: <88230342-7010-413A-8270-D36D1CD0D1D4@cam.ac.uk> References: <9C6275D4-2397-45E7-B18A-81A47C317545@recoil.org> <88230342-7010-413A-8270-D36D1CD0D1D4@cam.ac.uk> Date: Sun, 15 Feb 2015 14:16:15 +0000 Message-ID: From: Richard Mortier To: Jon Ludlam Cc: mirageos-devel , Anil Madhavapeddy Subject: Re: [MirageOS-devel] performance regression tests X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org oh cool-- i'll give that a go sometime then (recently nuked all my vbox vms so have to rebuild anyway). blobs might be useful, or perhaps update the vagrant-vms repo with appropriate build scripts? On 15 February 2015 at 13:54, Jon Ludlam wrote: > Virtualbox should work actually. I did have a vagrant box with xenserver 6.2 sp1 on it, but it was hosted on jon.recoil.org which has now been replaced with a tiny unikernel. I can try to dig it up this evening to see if it still works. I could stick it on blobs.openmirage.org maybe? > > Jon > > Sent from my iPad > >> On 15 Feb 2015, at 12:50, Richard Mortier wrote: >> >> yes, it's still the 2014/15 academic year :p >> >> i suspect i know the answer to this but just in case: i presume by >> "bare metal" you really do mean bare metal? ie., inside a virtualbox >> is not going to work? >> >> masoud-- if that's the case, i'll pick this up with you offline. >> there's a server in nottingham that you should be able to get access >> to and do what you want with. i originally put xen on it by hand and >> used the xm/xl tools, but it sounds like it might be time to wipe it >> and start again with xenserver. >> >> >>> On 15 February 2015 at 12:18, David Scott wrote: >>> >>> >>> On Sun, Feb 15, 2015 at 11:52 AM, Richard Mortier >>> wrote: >>>> >>>>> On 15 February 2015 at 11:28, Anil Madhavapeddy wrote: >>>>> On 15 Feb 2015, at 11:19, Richard Mortier >>>>> wrote: >>>>>> >>>>>> On 15 February 2015 at 11:15, Anil Madhavapeddy >>>>>> wrote: >>>>>>> This is great to see -- thanks for working on this Masoud! >>>>>>> >>>>>>> In particular, having even a simple iperf test would let us test >>>>>>> several interesting combinations straight away: >>>>>>> >>>>>>> - vary OCaml version (4.01 vs 4.02 is now supported), and there >>>>>>> is an experimental inlining branch in 4.03dev that could directly >>>>>>> be tested using this infrastructure. >>>>>> >>>>>> ok-- so i guess that needs a switch/env var to specify the `opam >>>>>> switch` to use? >>>>> >>>>> Yeah. Although from the performance scripts' perspective, it's better >>>>> if they just assume that there is a working OPAM environment. It would >>>>> be easier to control these parameters from outside, and keep the perf >>>>> scripts as easy to run as possible. >>>> >>>> ah-- original thinking was to make `mir-perf.sh` a harness that might >>>> be fired by `git-bisect`. >>>> >>>> if it's just to be a script to run a single experiment (parameter set) >>>> in a pre-configured environment, then that's a lot simpler. >>>> >>>>> A couple of other things that might help: >>>>> >>>>> - Luke Dunstan has a rather comprehensive acceptance test suite for >>>>> MDNS: >>>>> https://github.com/infidel/ocaml-mdns/tree/master/lib_test/acceptance >>>>> >>>>> - OCamlPro has a benchmarking system for core OCaml here that may have >>>>> some useful libraries: https://github.com/OCamlPro/operf-macro >>>>> >>>>> - Performance tests could be wrapped using Core_bench, which >>>>> does linear regression across runs. >>>>> >>>>> https://realworldocaml.org/v1/en/html/understanding-the-garbage-collector.html#the-mutable-write-barrier >>>>> >>>> >>>> cool, ta. >>>> >>>>>>> - evaluate the impact of some features incoming such as the open >>>>>>> RFC for checksum offload. >>>>>> >>>>>> how are they specified -- as a PR? >>>>>> in which case, masoud-- i guess that >>>>>> https://help.github.com/articles/checking-out-pull-requests-locally/ >>>>>> is a starting point for how to specify a particular PR rather than >>>>>> simply a commit rev. >>>>> >>>>> Yes, although again this would be better done outside the performance >>>>> harness as an OPAM pin for the local environment. Just having the >>>>> ability to quickly run a performance test would be invaluable at this >>>>> stage. >>>> >>>> so the caller of the script will >>>> >>>> + select their opam switch >>>> + pin any libraries, whether to PRs or particular commit-revs >>>> + record the environment configuration >>>> >>>> + then run the script, specifying the test to run, which will >>>> + start the unikernel-under-test >>>> + start any testing-unikernels (eg., iperf-client, iperf-server) >>>> + collect and record test results >>>> >>>> ...right? >>>> >>>> ultimately i was thinking to have the recorded test results put in a >>>> repo somewhere too, so that they could be visualised, compared to a >>>> benchmark, etc. >>>> >>>>>> just to be clear -- you mean does iperf via unikernels, ie., all the >>>>>> tests that are executed should also be unikernels rather than standard >>>>>> tools so that we don't take dependencies on an underlying platform >>>>>> like the dom0? >>>>> >>>>> Yes -- Xen unikernels would be the primary target. >>>> >>>> cool. less shell hacking, more unikernel hacking :) >>>> >>>>> Starting and stopping VMs in open source Xen can be bit of a pain, so >>>>> it would be ok if the test harness used XenServer (which the ARM SDcard >>>>> images now include). Jon or Dave could comment on the state of the >>>>> XMLRPC >>>>> OCaml bindings to XenServer... >>>> >>>> that would be useful. is it easy to get xenserver installed on x86 as >>>> well? (that's the platform masoud is mostly working on.) >>> >>> >>> x86 as well? What is this, 2014? :-) Your options are: >>> >>> 1. install the latest 6.5 release of xenserver on bare metal >>> >>> Pros: this is well tested and will work very well as a virtualisation >>> platform >>> Cons: it takes over a whole machine. To do unikernel development you'll need >>> to install a dev VM i.e. you can't do it in dom0. It's good practice to >>> leave dom0 alone anyway. Think of it like a black box which can run VMs. >>> >>> 2. build the latest version from source and install on a CentOS 6/7 or maybe >>> Ubuntu box >>> >>> Pros: you can do whatever you want with dom0 >>> Cons: some aspect of running VMs/ managing networks / managing storage is >>> bound to not work and you'll need to debug it. There is little automated >>> testing of this configuration, I (also Euan, Jon) try to fix bugs when I/we >>> encounter them on a best-effort basis. >>> >>> If you want to focus on unikernel dev and test, I recommend option 1. If you >>> want a new hobby of debugging VM hosting software, then try option 2. >>> >>> In the long run ... we'll converge option 1 and option 2... but I wouldn't >>> wait. >>> >>> Cheers, >>> Dave >>> >>>> >>>> >>>>>> cool... (one day i must learn about the cambridge infrastructure >>>>>> machines :) >>>>> >>>>> Be careful what you wish for :) >>>> >>>> now i'm genuinely curious... :) >>>> >>>> -- >>>> Richard Mortier >>>> richard.mortier@cl.cam.ac.uk >>>> >>>> _______________________________________________ >>>> MirageOS-devel mailing list >>>> MirageOS-devel@lists.xenproject.org >>>> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel >>> >>> >>> >>> >>> -- >>> Dave Scott >> >> >> >> -- >> Richard Mortier >> richard.mortier@cl.cam.ac.uk >> >> _______________________________________________ >> MirageOS-devel mailing list >> MirageOS-devel@lists.xenproject.org >> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel -- Richard Mortier richard.mortier@cl.cam.ac.uk _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Sun Feb 15 14:16:23 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 15 Feb 2015 14:16:23 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YMzzh-0006Zl-IP; Sun, 15 Feb 2015 14:16:21 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YMzzg-0006Zg-Ex for MirageOS-devel@lists.xenproject.org; Sun, 15 Feb 2015 14:16:20 +0000 Received: from [85.158.139.211] by server-6.bemta-5.messagelabs.com id 16/95-03165-33AA0E45; Sun, 15 Feb 2015 14:16:19 +0000 X-Env-Sender: richard.mortier@gmail.com X-Msg-Ref: server-6.tower-206.messagelabs.com!1424009777!12025920!1 X-Originating-IP: [209.85.192.44] X-SpamReason: No, hits=0.6 required=7.0 tests=MAILTO_TO_SPAM_ADDR, RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11309 invoked from network); 15 Feb 2015 14:16:18 -0000 Received: from mail-qg0-f44.google.com (HELO mail-qg0-f44.google.com) (209.85.192.44) by server-6.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 15 Feb 2015 14:16:18 -0000 Received: by mail-qg0-f44.google.com with SMTP id j5so20002321qga.3 for ; Sun, 15 Feb 2015 06:16:17 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=qnQ+QfmTVsRqNZKR9EQIG/m4QOdRURG/mMYIRteicpw=; b=fhyVGQ/I8wDLxDqye8572f8J9NKfZ8l0fLxLszIRLenLfdVMGUUaS+mSgGIYeNfyKm fMwuopNzklithOkzIf6Ah9LUjfNrQXs7xVSU1s9U/1N2cCZlI3GHp8MpL4nZSZgUjHWt 9q4EWLBwviWVM5vChoAdNGdQWjF+3JWGcqULbmN6wZIF2fpmHQmmBwEJxNVJuHcp6w38 j53x8OCrmU4XmihjFdDfMPQgSxG50fILvGdVCemlc3E6G4masr5oA39fUcZ6pTlWdjOk cf9CUbawSF4Dkey6cavh2xXb5lGtqUgmeoYxvKQ0p20L9QnDGFWlUeDl50EXpWHpjjFG sPgw== X-Received: by 10.140.150.87 with SMTP id 84mr18989489qhw.64.1424009776941; Sun, 15 Feb 2015 06:16:16 -0800 (PST) Received: from mail-qc0-f169.google.com (mail-qc0-f169.google.com. [209.85.216.169]) by mx.google.com with ESMTPSA id u3sm11719425qat.22.2015.02.15.06.16.15 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 15 Feb 2015 06:16:16 -0800 (PST) Received: by mail-qc0-f169.google.com with SMTP id m20so20512642qcx.0 for ; Sun, 15 Feb 2015 06:16:15 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.229.65.8 with SMTP id g8mr20627893qci.15.1424009775859; Sun, 15 Feb 2015 06:16:15 -0800 (PST) Received: by 10.140.92.245 with HTTP; Sun, 15 Feb 2015 06:16:15 -0800 (PST) In-Reply-To: <88230342-7010-413A-8270-D36D1CD0D1D4@cam.ac.uk> References: <9C6275D4-2397-45E7-B18A-81A47C317545@recoil.org> <88230342-7010-413A-8270-D36D1CD0D1D4@cam.ac.uk> Date: Sun, 15 Feb 2015 14:16:15 +0000 Message-ID: From: Richard Mortier To: Jon Ludlam Cc: mirageos-devel , Anil Madhavapeddy Subject: Re: [MirageOS-devel] performance regression tests X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org oh cool-- i'll give that a go sometime then (recently nuked all my vbox vms so have to rebuild anyway). blobs might be useful, or perhaps update the vagrant-vms repo with appropriate build scripts? On 15 February 2015 at 13:54, Jon Ludlam wrote: > Virtualbox should work actually. I did have a vagrant box with xenserver 6.2 sp1 on it, but it was hosted on jon.recoil.org which has now been replaced with a tiny unikernel. I can try to dig it up this evening to see if it still works. I could stick it on blobs.openmirage.org maybe? > > Jon > > Sent from my iPad > >> On 15 Feb 2015, at 12:50, Richard Mortier wrote: >> >> yes, it's still the 2014/15 academic year :p >> >> i suspect i know the answer to this but just in case: i presume by >> "bare metal" you really do mean bare metal? ie., inside a virtualbox >> is not going to work? >> >> masoud-- if that's the case, i'll pick this up with you offline. >> there's a server in nottingham that you should be able to get access >> to and do what you want with. i originally put xen on it by hand and >> used the xm/xl tools, but it sounds like it might be time to wipe it >> and start again with xenserver. >> >> >>> On 15 February 2015 at 12:18, David Scott wrote: >>> >>> >>> On Sun, Feb 15, 2015 at 11:52 AM, Richard Mortier >>> wrote: >>>> >>>>> On 15 February 2015 at 11:28, Anil Madhavapeddy wrote: >>>>> On 15 Feb 2015, at 11:19, Richard Mortier >>>>> wrote: >>>>>> >>>>>> On 15 February 2015 at 11:15, Anil Madhavapeddy >>>>>> wrote: >>>>>>> This is great to see -- thanks for working on this Masoud! >>>>>>> >>>>>>> In particular, having even a simple iperf test would let us test >>>>>>> several interesting combinations straight away: >>>>>>> >>>>>>> - vary OCaml version (4.01 vs 4.02 is now supported), and there >>>>>>> is an experimental inlining branch in 4.03dev that could directly >>>>>>> be tested using this infrastructure. >>>>>> >>>>>> ok-- so i guess that needs a switch/env var to specify the `opam >>>>>> switch` to use? >>>>> >>>>> Yeah. Although from the performance scripts' perspective, it's better >>>>> if they just assume that there is a working OPAM environment. It would >>>>> be easier to control these parameters from outside, and keep the perf >>>>> scripts as easy to run as possible. >>>> >>>> ah-- original thinking was to make `mir-perf.sh` a harness that might >>>> be fired by `git-bisect`. >>>> >>>> if it's just to be a script to run a single experiment (parameter set) >>>> in a pre-configured environment, then that's a lot simpler. >>>> >>>>> A couple of other things that might help: >>>>> >>>>> - Luke Dunstan has a rather comprehensive acceptance test suite for >>>>> MDNS: >>>>> https://github.com/infidel/ocaml-mdns/tree/master/lib_test/acceptance >>>>> >>>>> - OCamlPro has a benchmarking system for core OCaml here that may have >>>>> some useful libraries: https://github.com/OCamlPro/operf-macro >>>>> >>>>> - Performance tests could be wrapped using Core_bench, which >>>>> does linear regression across runs. >>>>> >>>>> https://realworldocaml.org/v1/en/html/understanding-the-garbage-collector.html#the-mutable-write-barrier >>>>> >>>> >>>> cool, ta. >>>> >>>>>>> - evaluate the impact of some features incoming such as the open >>>>>>> RFC for checksum offload. >>>>>> >>>>>> how are they specified -- as a PR? >>>>>> in which case, masoud-- i guess that >>>>>> https://help.github.com/articles/checking-out-pull-requests-locally/ >>>>>> is a starting point for how to specify a particular PR rather than >>>>>> simply a commit rev. >>>>> >>>>> Yes, although again this would be better done outside the performance >>>>> harness as an OPAM pin for the local environment. Just having the >>>>> ability to quickly run a performance test would be invaluable at this >>>>> stage. >>>> >>>> so the caller of the script will >>>> >>>> + select their opam switch >>>> + pin any libraries, whether to PRs or particular commit-revs >>>> + record the environment configuration >>>> >>>> + then run the script, specifying the test to run, which will >>>> + start the unikernel-under-test >>>> + start any testing-unikernels (eg., iperf-client, iperf-server) >>>> + collect and record test results >>>> >>>> ...right? >>>> >>>> ultimately i was thinking to have the recorded test results put in a >>>> repo somewhere too, so that they could be visualised, compared to a >>>> benchmark, etc. >>>> >>>>>> just to be clear -- you mean does iperf via unikernels, ie., all the >>>>>> tests that are executed should also be unikernels rather than standard >>>>>> tools so that we don't take dependencies on an underlying platform >>>>>> like the dom0? >>>>> >>>>> Yes -- Xen unikernels would be the primary target. >>>> >>>> cool. less shell hacking, more unikernel hacking :) >>>> >>>>> Starting and stopping VMs in open source Xen can be bit of a pain, so >>>>> it would be ok if the test harness used XenServer (which the ARM SDcard >>>>> images now include). Jon or Dave could comment on the state of the >>>>> XMLRPC >>>>> OCaml bindings to XenServer... >>>> >>>> that would be useful. is it easy to get xenserver installed on x86 as >>>> well? (that's the platform masoud is mostly working on.) >>> >>> >>> x86 as well? What is this, 2014? :-) Your options are: >>> >>> 1. install the latest 6.5 release of xenserver on bare metal >>> >>> Pros: this is well tested and will work very well as a virtualisation >>> platform >>> Cons: it takes over a whole machine. To do unikernel development you'll need >>> to install a dev VM i.e. you can't do it in dom0. It's good practice to >>> leave dom0 alone anyway. Think of it like a black box which can run VMs. >>> >>> 2. build the latest version from source and install on a CentOS 6/7 or maybe >>> Ubuntu box >>> >>> Pros: you can do whatever you want with dom0 >>> Cons: some aspect of running VMs/ managing networks / managing storage is >>> bound to not work and you'll need to debug it. There is little automated >>> testing of this configuration, I (also Euan, Jon) try to fix bugs when I/we >>> encounter them on a best-effort basis. >>> >>> If you want to focus on unikernel dev and test, I recommend option 1. If you >>> want a new hobby of debugging VM hosting software, then try option 2. >>> >>> In the long run ... we'll converge option 1 and option 2... but I wouldn't >>> wait. >>> >>> Cheers, >>> Dave >>> >>>> >>>> >>>>>> cool... (one day i must learn about the cambridge infrastructure >>>>>> machines :) >>>>> >>>>> Be careful what you wish for :) >>>> >>>> now i'm genuinely curious... :) >>>> >>>> -- >>>> Richard Mortier >>>> richard.mortier@cl.cam.ac.uk >>>> >>>> _______________________________________________ >>>> MirageOS-devel mailing list >>>> MirageOS-devel@lists.xenproject.org >>>> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel >>> >>> >>> >>> >>> -- >>> Dave Scott >> >> >> >> -- >> Richard Mortier >> richard.mortier@cl.cam.ac.uk >> >> _______________________________________________ >> MirageOS-devel mailing list >> MirageOS-devel@lists.xenproject.org >> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel -- Richard Mortier richard.mortier@cl.cam.ac.uk _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Sun Feb 15 18:46:54 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 15 Feb 2015 18:46:54 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YN4DO-0006Kt-65; Sun, 15 Feb 2015 18:46:46 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YN4DN-0006Ko-7A for MirageOS-devel@lists.xenproject.org; Sun, 15 Feb 2015 18:46:45 +0000 Received: from [85.158.143.35] by server-1.bemta-4.messagelabs.com id 4A/C1-03004-499E0E45; Sun, 15 Feb 2015 18:46:44 +0000 X-Env-Sender: lpw25@cam.ac.uk X-Msg-Ref: server-8.tower-21.messagelabs.com!1424026003!12023940!1 X-Originating-IP: [131.111.8.151] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTMxLjExMS44LjE1MSA9PiAxNDE4OTU=\n X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 13531 invoked from network); 15 Feb 2015 18:46:44 -0000 Received: from ppsw-51.csi.cam.ac.uk (HELO ppsw-51.csi.cam.ac.uk) (131.111.8.151) by server-8.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 15 Feb 2015 18:46:44 -0000 X-Cam-AntiVirus: no malware found X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/ Received: from host86-159-4-23.range86-159.btcentralplus.com ([86.159.4.23]:43430 helo=study.localdomain) by ppsw-51.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.157]:587) with esmtpsa (PLAIN:lpw25) (TLSv1.2:AES128-GCM-SHA256:128) id 1YN4DL-0001e3-XX (Exim 4.82_3-c0e5623) (return-path ); Sun, 15 Feb 2015 18:46:43 +0000 From: Leo White To: Anil Madhavapeddy References: X-Face: "XWxb[u_Z\PA_Y?9@|IA!!+jTb(/290-*ea/Un$I0B98.$n%eL.; 2w*,z]WR#T:,p[ NBd++M7l]#7zj7!{~iw $W-"/=|dVjhT[D{4~gE}gK<2`.6fs!;uqqud]vs2N/3^m7{aS1V, Date: Sun, 15 Feb 2015 18:46:32 +0000 In-Reply-To: (Anil Madhavapeddy's message of "Sun, 15 Feb 2015 11:15:08 +0000") Message-ID: <87wq3jui5z.fsf@study.localdomain> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) MIME-Version: 1.0 Cc: mirageos-devel Subject: Re: [MirageOS-devel] performance regression tests X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org > In particular, having even a simple iperf test would let us test > several interesting combinations straight away: > > - vary OCaml version (4.01 vs 4.02 is now supported), and there > is an experimental inlining branch in 4.03dev that could directly > be tested using this infrastructure. And soon this could be useful for 4.02.1+multicore. Regards, Leo _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Sun Feb 15 18:46:54 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 15 Feb 2015 18:46:54 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YN4DO-0006Kt-65; Sun, 15 Feb 2015 18:46:46 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YN4DN-0006Ko-7A for MirageOS-devel@lists.xenproject.org; Sun, 15 Feb 2015 18:46:45 +0000 Received: from [85.158.143.35] by server-1.bemta-4.messagelabs.com id 4A/C1-03004-499E0E45; Sun, 15 Feb 2015 18:46:44 +0000 X-Env-Sender: lpw25@cam.ac.uk X-Msg-Ref: server-8.tower-21.messagelabs.com!1424026003!12023940!1 X-Originating-IP: [131.111.8.151] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTMxLjExMS44LjE1MSA9PiAxNDE4OTU=\n X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 13531 invoked from network); 15 Feb 2015 18:46:44 -0000 Received: from ppsw-51.csi.cam.ac.uk (HELO ppsw-51.csi.cam.ac.uk) (131.111.8.151) by server-8.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 15 Feb 2015 18:46:44 -0000 X-Cam-AntiVirus: no malware found X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/ Received: from host86-159-4-23.range86-159.btcentralplus.com ([86.159.4.23]:43430 helo=study.localdomain) by ppsw-51.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.157]:587) with esmtpsa (PLAIN:lpw25) (TLSv1.2:AES128-GCM-SHA256:128) id 1YN4DL-0001e3-XX (Exim 4.82_3-c0e5623) (return-path ); Sun, 15 Feb 2015 18:46:43 +0000 From: Leo White To: Anil Madhavapeddy References: X-Face: "XWxb[u_Z\PA_Y?9@|IA!!+jTb(/290-*ea/Un$I0B98.$n%eL.; 2w*,z]WR#T:,p[ NBd++M7l]#7zj7!{~iw $W-"/=|dVjhT[D{4~gE}gK<2`.6fs!;uqqud]vs2N/3^m7{aS1V, Date: Sun, 15 Feb 2015 18:46:32 +0000 In-Reply-To: (Anil Madhavapeddy's message of "Sun, 15 Feb 2015 11:15:08 +0000") Message-ID: <87wq3jui5z.fsf@study.localdomain> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) MIME-Version: 1.0 Cc: mirageos-devel Subject: Re: [MirageOS-devel] performance regression tests X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org > In particular, having even a simple iperf test would let us test > several interesting combinations straight away: > > - vary OCaml version (4.01 vs 4.02 is now supported), and there > is an experimental inlining branch in 4.03dev that could directly > be tested using this infrastructure. And soon this could be useful for 4.02.1+multicore. Regards, Leo _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Mon Feb 16 01:24:03 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 16 Feb 2015 01:24:03 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YNAPg-00013I-Ne; Mon, 16 Feb 2015 01:23:52 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YNAPf-00013D-82 for MirageOS-devel@lists.xenproject.org; Mon, 16 Feb 2015 01:23:51 +0000 Received: from [85.158.139.211] by server-3.bemta-5.messagelabs.com id 6C/A5-02994-6A641E45; Mon, 16 Feb 2015 01:23:50 +0000 X-Env-Sender: jjl25@cam.ac.uk X-Msg-Ref: server-16.tower-206.messagelabs.com!1424049829!9184737!1 X-Originating-IP: [131.111.8.151] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTMxLjExMS44LjE1MSA9PiAxNDE4OTU=\n X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 32281 invoked from network); 16 Feb 2015 01:23:49 -0000 Received: from ppsw-51.csi.cam.ac.uk (HELO ppsw-51.csi.cam.ac.uk) (131.111.8.151) by server-16.tower-206.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 16 Feb 2015 01:23:49 -0000 X-Cam-AntiVirus: no malware found X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/ Received: from 88-111-127-167.dynamic.dsl.as9105.com ([88.111.127.167]:58538 helo=localhost) by ppsw-51.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.157]:587) with esmtpsa (PLAIN:jjl25) (TLSv1.2:AES128-GCM-SHA256:128) id 1YNAPc-0006lF-XD (Exim 4.82_3-c0e5623) (return-path ); Mon, 16 Feb 2015 01:23:48 +0000 Date: Mon, 16 Feb 2015 01:11:44 +0000 From: Jon Ludlam To: Richard Mortier Message-ID: <20150216011144.GB26571@humongous.Belkin> References: <9C6275D4-2397-45E7-B18A-81A47C317545@recoil.org> <88230342-7010-413A-8270-D36D1CD0D1D4@cam.ac.uk> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) Cc: mirageos-devel , Anil Madhavapeddy Subject: Re: [MirageOS-devel] performance regression tests X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On Sun, Feb 15, 2015 at 02:16:15PM +0000, Richard Mortier wrote: > oh cool-- i'll give that a go sometime then (recently nuked all my > vbox vms so have to rebuild anyway). > > blobs might be useful, or perhaps update the vagrant-vms repo with > appropriate build scripts? > I've updated imduffy15's xenserver packer scripts to the latest 6.5 release of XS - the result is here: https://github.com/jonludlam/packer-xenserver I can probably integrate it with the vagrant-vms repo once I've ironed out the kinks. I don't think I have access to blobs now, though I've just had to reinstall this computer so it's conceivable I've lost an ssh key somewhere. In any case, the box doesn't take long to build. It boots OK and the toolstack is all running and I can run unikernels, but I'm having difficulty with forwarded ports right now. I'll give it another go tomorrow. Jon > On 15 February 2015 at 13:54, Jon Ludlam wrote: > > Virtualbox should work actually. I did have a vagrant box with xenserver 6.2 sp1 on it, but it was hosted on jon.recoil.org which has now been replaced with a tiny unikernel. I can try to dig it up this evening to see if it still works. I could stick it on blobs.openmirage.org maybe? > > > > Jon > > > > Sent from my iPad > > > >> On 15 Feb 2015, at 12:50, Richard Mortier wrote: > >> > >> yes, it's still the 2014/15 academic year :p > >> > >> i suspect i know the answer to this but just in case: i presume by > >> "bare metal" you really do mean bare metal? ie., inside a virtualbox > >> is not going to work? > >> > >> masoud-- if that's the case, i'll pick this up with you offline. > >> there's a server in nottingham that you should be able to get access > >> to and do what you want with. i originally put xen on it by hand and > >> used the xm/xl tools, but it sounds like it might be time to wipe it > >> and start again with xenserver. > >> > >> > >>> On 15 February 2015 at 12:18, David Scott wrote: > >>> > >>> > >>> On Sun, Feb 15, 2015 at 11:52 AM, Richard Mortier > >>> wrote: > >>>> > >>>>> On 15 February 2015 at 11:28, Anil Madhavapeddy wrote: > >>>>> On 15 Feb 2015, at 11:19, Richard Mortier > >>>>> wrote: > >>>>>> > >>>>>> On 15 February 2015 at 11:15, Anil Madhavapeddy > >>>>>> wrote: > >>>>>>> This is great to see -- thanks for working on this Masoud! > >>>>>>> > >>>>>>> In particular, having even a simple iperf test would let us test > >>>>>>> several interesting combinations straight away: > >>>>>>> > >>>>>>> - vary OCaml version (4.01 vs 4.02 is now supported), and there > >>>>>>> is an experimental inlining branch in 4.03dev that could directly > >>>>>>> be tested using this infrastructure. > >>>>>> > >>>>>> ok-- so i guess that needs a switch/env var to specify the `opam > >>>>>> switch` to use? > >>>>> > >>>>> Yeah. Although from the performance scripts' perspective, it's better > >>>>> if they just assume that there is a working OPAM environment. It would > >>>>> be easier to control these parameters from outside, and keep the perf > >>>>> scripts as easy to run as possible. > >>>> > >>>> ah-- original thinking was to make `mir-perf.sh` a harness that might > >>>> be fired by `git-bisect`. > >>>> > >>>> if it's just to be a script to run a single experiment (parameter set) > >>>> in a pre-configured environment, then that's a lot simpler. > >>>> > >>>>> A couple of other things that might help: > >>>>> > >>>>> - Luke Dunstan has a rather comprehensive acceptance test suite for > >>>>> MDNS: > >>>>> https://github.com/infidel/ocaml-mdns/tree/master/lib_test/acceptance > >>>>> > >>>>> - OCamlPro has a benchmarking system for core OCaml here that may have > >>>>> some useful libraries: https://github.com/OCamlPro/operf-macro > >>>>> > >>>>> - Performance tests could be wrapped using Core_bench, which > >>>>> does linear regression across runs. > >>>>> > >>>>> https://realworldocaml.org/v1/en/html/understanding-the-garbage-collector.html#the-mutable-write-barrier > >>>>> > >>>> > >>>> cool, ta. > >>>> > >>>>>>> - evaluate the impact of some features incoming such as the open > >>>>>>> RFC for checksum offload. > >>>>>> > >>>>>> how are they specified -- as a PR? > >>>>>> in which case, masoud-- i guess that > >>>>>> https://help.github.com/articles/checking-out-pull-requests-locally/ > >>>>>> is a starting point for how to specify a particular PR rather than > >>>>>> simply a commit rev. > >>>>> > >>>>> Yes, although again this would be better done outside the performance > >>>>> harness as an OPAM pin for the local environment. Just having the > >>>>> ability to quickly run a performance test would be invaluable at this > >>>>> stage. > >>>> > >>>> so the caller of the script will > >>>> > >>>> + select their opam switch > >>>> + pin any libraries, whether to PRs or particular commit-revs > >>>> + record the environment configuration > >>>> > >>>> + then run the script, specifying the test to run, which will > >>>> + start the unikernel-under-test > >>>> + start any testing-unikernels (eg., iperf-client, iperf-server) > >>>> + collect and record test results > >>>> > >>>> ...right? > >>>> > >>>> ultimately i was thinking to have the recorded test results put in a > >>>> repo somewhere too, so that they could be visualised, compared to a > >>>> benchmark, etc. > >>>> > >>>>>> just to be clear -- you mean does iperf via unikernels, ie., all the > >>>>>> tests that are executed should also be unikernels rather than standard > >>>>>> tools so that we don't take dependencies on an underlying platform > >>>>>> like the dom0? > >>>>> > >>>>> Yes -- Xen unikernels would be the primary target. > >>>> > >>>> cool. less shell hacking, more unikernel hacking :) > >>>> > >>>>> Starting and stopping VMs in open source Xen can be bit of a pain, so > >>>>> it would be ok if the test harness used XenServer (which the ARM SDcard > >>>>> images now include). Jon or Dave could comment on the state of the > >>>>> XMLRPC > >>>>> OCaml bindings to XenServer... > >>>> > >>>> that would be useful. is it easy to get xenserver installed on x86 as > >>>> well? (that's the platform masoud is mostly working on.) > >>> > >>> > >>> x86 as well? What is this, 2014? :-) Your options are: > >>> > >>> 1. install the latest 6.5 release of xenserver on bare metal > >>> > >>> Pros: this is well tested and will work very well as a virtualisation > >>> platform > >>> Cons: it takes over a whole machine. To do unikernel development you'll need > >>> to install a dev VM i.e. you can't do it in dom0. It's good practice to > >>> leave dom0 alone anyway. Think of it like a black box which can run VMs. > >>> > >>> 2. build the latest version from source and install on a CentOS 6/7 or maybe > >>> Ubuntu box > >>> > >>> Pros: you can do whatever you want with dom0 > >>> Cons: some aspect of running VMs/ managing networks / managing storage is > >>> bound to not work and you'll need to debug it. There is little automated > >>> testing of this configuration, I (also Euan, Jon) try to fix bugs when I/we > >>> encounter them on a best-effort basis. > >>> > >>> If you want to focus on unikernel dev and test, I recommend option 1. If you > >>> want a new hobby of debugging VM hosting software, then try option 2. > >>> > >>> In the long run ... we'll converge option 1 and option 2... but I wouldn't > >>> wait. > >>> > >>> Cheers, > >>> Dave > >>> > >>>> > >>>> > >>>>>> cool... (one day i must learn about the cambridge infrastructure > >>>>>> machines :) > >>>>> > >>>>> Be careful what you wish for :) > >>>> > >>>> now i'm genuinely curious... :) > >>>> > >>>> -- > >>>> Richard Mortier > >>>> richard.mortier@cl.cam.ac.uk > >>>> > >>>> _______________________________________________ > >>>> MirageOS-devel mailing list > >>>> MirageOS-devel@lists.xenproject.org > >>>> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > >>> > >>> > >>> > >>> > >>> -- > >>> Dave Scott > >> > >> > >> > >> -- > >> Richard Mortier > >> richard.mortier@cl.cam.ac.uk > >> > >> _______________________________________________ > >> MirageOS-devel mailing list > >> MirageOS-devel@lists.xenproject.org > >> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > > > > -- > Richard Mortier > richard.mortier@cl.cam.ac.uk _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Mon Feb 16 01:24:03 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 16 Feb 2015 01:24:03 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YNAPg-00013I-Ne; Mon, 16 Feb 2015 01:23:52 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YNAPf-00013D-82 for MirageOS-devel@lists.xenproject.org; Mon, 16 Feb 2015 01:23:51 +0000 Received: from [85.158.139.211] by server-3.bemta-5.messagelabs.com id 6C/A5-02994-6A641E45; Mon, 16 Feb 2015 01:23:50 +0000 X-Env-Sender: jjl25@cam.ac.uk X-Msg-Ref: server-16.tower-206.messagelabs.com!1424049829!9184737!1 X-Originating-IP: [131.111.8.151] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTMxLjExMS44LjE1MSA9PiAxNDE4OTU=\n X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 32281 invoked from network); 16 Feb 2015 01:23:49 -0000 Received: from ppsw-51.csi.cam.ac.uk (HELO ppsw-51.csi.cam.ac.uk) (131.111.8.151) by server-16.tower-206.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 16 Feb 2015 01:23:49 -0000 X-Cam-AntiVirus: no malware found X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/ Received: from 88-111-127-167.dynamic.dsl.as9105.com ([88.111.127.167]:58538 helo=localhost) by ppsw-51.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.157]:587) with esmtpsa (PLAIN:jjl25) (TLSv1.2:AES128-GCM-SHA256:128) id 1YNAPc-0006lF-XD (Exim 4.82_3-c0e5623) (return-path ); Mon, 16 Feb 2015 01:23:48 +0000 Date: Mon, 16 Feb 2015 01:11:44 +0000 From: Jon Ludlam To: Richard Mortier Message-ID: <20150216011144.GB26571@humongous.Belkin> References: <9C6275D4-2397-45E7-B18A-81A47C317545@recoil.org> <88230342-7010-413A-8270-D36D1CD0D1D4@cam.ac.uk> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) Cc: mirageos-devel , Anil Madhavapeddy Subject: Re: [MirageOS-devel] performance regression tests X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On Sun, Feb 15, 2015 at 02:16:15PM +0000, Richard Mortier wrote: > oh cool-- i'll give that a go sometime then (recently nuked all my > vbox vms so have to rebuild anyway). > > blobs might be useful, or perhaps update the vagrant-vms repo with > appropriate build scripts? > I've updated imduffy15's xenserver packer scripts to the latest 6.5 release of XS - the result is here: https://github.com/jonludlam/packer-xenserver I can probably integrate it with the vagrant-vms repo once I've ironed out the kinks. I don't think I have access to blobs now, though I've just had to reinstall this computer so it's conceivable I've lost an ssh key somewhere. In any case, the box doesn't take long to build. It boots OK and the toolstack is all running and I can run unikernels, but I'm having difficulty with forwarded ports right now. I'll give it another go tomorrow. Jon > On 15 February 2015 at 13:54, Jon Ludlam wrote: > > Virtualbox should work actually. I did have a vagrant box with xenserver 6.2 sp1 on it, but it was hosted on jon.recoil.org which has now been replaced with a tiny unikernel. I can try to dig it up this evening to see if it still works. I could stick it on blobs.openmirage.org maybe? > > > > Jon > > > > Sent from my iPad > > > >> On 15 Feb 2015, at 12:50, Richard Mortier wrote: > >> > >> yes, it's still the 2014/15 academic year :p > >> > >> i suspect i know the answer to this but just in case: i presume by > >> "bare metal" you really do mean bare metal? ie., inside a virtualbox > >> is not going to work? > >> > >> masoud-- if that's the case, i'll pick this up with you offline. > >> there's a server in nottingham that you should be able to get access > >> to and do what you want with. i originally put xen on it by hand and > >> used the xm/xl tools, but it sounds like it might be time to wipe it > >> and start again with xenserver. > >> > >> > >>> On 15 February 2015 at 12:18, David Scott wrote: > >>> > >>> > >>> On Sun, Feb 15, 2015 at 11:52 AM, Richard Mortier > >>> wrote: > >>>> > >>>>> On 15 February 2015 at 11:28, Anil Madhavapeddy wrote: > >>>>> On 15 Feb 2015, at 11:19, Richard Mortier > >>>>> wrote: > >>>>>> > >>>>>> On 15 February 2015 at 11:15, Anil Madhavapeddy > >>>>>> wrote: > >>>>>>> This is great to see -- thanks for working on this Masoud! > >>>>>>> > >>>>>>> In particular, having even a simple iperf test would let us test > >>>>>>> several interesting combinations straight away: > >>>>>>> > >>>>>>> - vary OCaml version (4.01 vs 4.02 is now supported), and there > >>>>>>> is an experimental inlining branch in 4.03dev that could directly > >>>>>>> be tested using this infrastructure. > >>>>>> > >>>>>> ok-- so i guess that needs a switch/env var to specify the `opam > >>>>>> switch` to use? > >>>>> > >>>>> Yeah. Although from the performance scripts' perspective, it's better > >>>>> if they just assume that there is a working OPAM environment. It would > >>>>> be easier to control these parameters from outside, and keep the perf > >>>>> scripts as easy to run as possible. > >>>> > >>>> ah-- original thinking was to make `mir-perf.sh` a harness that might > >>>> be fired by `git-bisect`. > >>>> > >>>> if it's just to be a script to run a single experiment (parameter set) > >>>> in a pre-configured environment, then that's a lot simpler. > >>>> > >>>>> A couple of other things that might help: > >>>>> > >>>>> - Luke Dunstan has a rather comprehensive acceptance test suite for > >>>>> MDNS: > >>>>> https://github.com/infidel/ocaml-mdns/tree/master/lib_test/acceptance > >>>>> > >>>>> - OCamlPro has a benchmarking system for core OCaml here that may have > >>>>> some useful libraries: https://github.com/OCamlPro/operf-macro > >>>>> > >>>>> - Performance tests could be wrapped using Core_bench, which > >>>>> does linear regression across runs. > >>>>> > >>>>> https://realworldocaml.org/v1/en/html/understanding-the-garbage-collector.html#the-mutable-write-barrier > >>>>> > >>>> > >>>> cool, ta. > >>>> > >>>>>>> - evaluate the impact of some features incoming such as the open > >>>>>>> RFC for checksum offload. > >>>>>> > >>>>>> how are they specified -- as a PR? > >>>>>> in which case, masoud-- i guess that > >>>>>> https://help.github.com/articles/checking-out-pull-requests-locally/ > >>>>>> is a starting point for how to specify a particular PR rather than > >>>>>> simply a commit rev. > >>>>> > >>>>> Yes, although again this would be better done outside the performance > >>>>> harness as an OPAM pin for the local environment. Just having the > >>>>> ability to quickly run a performance test would be invaluable at this > >>>>> stage. > >>>> > >>>> so the caller of the script will > >>>> > >>>> + select their opam switch > >>>> + pin any libraries, whether to PRs or particular commit-revs > >>>> + record the environment configuration > >>>> > >>>> + then run the script, specifying the test to run, which will > >>>> + start the unikernel-under-test > >>>> + start any testing-unikernels (eg., iperf-client, iperf-server) > >>>> + collect and record test results > >>>> > >>>> ...right? > >>>> > >>>> ultimately i was thinking to have the recorded test results put in a > >>>> repo somewhere too, so that they could be visualised, compared to a > >>>> benchmark, etc. > >>>> > >>>>>> just to be clear -- you mean does iperf via unikernels, ie., all the > >>>>>> tests that are executed should also be unikernels rather than standard > >>>>>> tools so that we don't take dependencies on an underlying platform > >>>>>> like the dom0? > >>>>> > >>>>> Yes -- Xen unikernels would be the primary target. > >>>> > >>>> cool. less shell hacking, more unikernel hacking :) > >>>> > >>>>> Starting and stopping VMs in open source Xen can be bit of a pain, so > >>>>> it would be ok if the test harness used XenServer (which the ARM SDcard > >>>>> images now include). Jon or Dave could comment on the state of the > >>>>> XMLRPC > >>>>> OCaml bindings to XenServer... > >>>> > >>>> that would be useful. is it easy to get xenserver installed on x86 as > >>>> well? (that's the platform masoud is mostly working on.) > >>> > >>> > >>> x86 as well? What is this, 2014? :-) Your options are: > >>> > >>> 1. install the latest 6.5 release of xenserver on bare metal > >>> > >>> Pros: this is well tested and will work very well as a virtualisation > >>> platform > >>> Cons: it takes over a whole machine. To do unikernel development you'll need > >>> to install a dev VM i.e. you can't do it in dom0. It's good practice to > >>> leave dom0 alone anyway. Think of it like a black box which can run VMs. > >>> > >>> 2. build the latest version from source and install on a CentOS 6/7 or maybe > >>> Ubuntu box > >>> > >>> Pros: you can do whatever you want with dom0 > >>> Cons: some aspect of running VMs/ managing networks / managing storage is > >>> bound to not work and you'll need to debug it. There is little automated > >>> testing of this configuration, I (also Euan, Jon) try to fix bugs when I/we > >>> encounter them on a best-effort basis. > >>> > >>> If you want to focus on unikernel dev and test, I recommend option 1. If you > >>> want a new hobby of debugging VM hosting software, then try option 2. > >>> > >>> In the long run ... we'll converge option 1 and option 2... but I wouldn't > >>> wait. > >>> > >>> Cheers, > >>> Dave > >>> > >>>> > >>>> > >>>>>> cool... (one day i must learn about the cambridge infrastructure > >>>>>> machines :) > >>>>> > >>>>> Be careful what you wish for :) > >>>> > >>>> now i'm genuinely curious... :) > >>>> > >>>> -- > >>>> Richard Mortier > >>>> richard.mortier@cl.cam.ac.uk > >>>> > >>>> _______________________________________________ > >>>> MirageOS-devel mailing list > >>>> MirageOS-devel@lists.xenproject.org > >>>> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > >>> > >>> > >>> > >>> > >>> -- > >>> Dave Scott > >> > >> > >> > >> -- > >> Richard Mortier > >> richard.mortier@cl.cam.ac.uk > >> > >> _______________________________________________ > >> MirageOS-devel mailing list > >> MirageOS-devel@lists.xenproject.org > >> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > > > > -- > Richard Mortier > richard.mortier@cl.cam.ac.uk _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Mon Feb 16 13:56:20 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 16 Feb 2015 13:56:20 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YNM9k-0004Vv-HY; Mon, 16 Feb 2015 13:56:12 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YNHpM-0003eO-UL for mirageos-devel@lists.xenproject.org; Mon, 16 Feb 2015 09:18:53 +0000 Received: from [193.109.254.147] by server-15.bemta-14.messagelabs.com id 64/F9-02770-CF5B1E45; Mon, 16 Feb 2015 09:18:52 +0000 X-Env-Sender: francois.berenger@inria.fr X-Msg-Ref: server-5.tower-27.messagelabs.com!1424078331!9029153!1 X-Originating-IP: [192.134.164.83] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29621 invoked from network); 16 Feb 2015 09:18:51 -0000 Received: from mail2-relais-roc.national.inria.fr (HELO mail2-relais-roc.national.inria.fr) (192.134.164.83) by server-5.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 16 Feb 2015 09:18:51 -0000 X-IronPort-AV: E=Sophos;i="5.09,586,1418079600"; d="scan'208";a="121903238" Received: from meleze.ens.fr (HELO [129.199.99.114]) ([129.199.99.114]) by mail2-relais-roc.national.inria.fr with ESMTP/TLS/DHE-RSA-AES128-SHA; 16 Feb 2015 10:18:38 +0100 Message-ID: <54E1B5EA.9010301@inria.fr> Date: Mon, 16 Feb 2015 10:18:34 +0100 From: Francois Berenger User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: mirageos-devel@lists.xenproject.org X-Mailman-Approved-At: Mon, 16 Feb 2015 13:56:11 +0000 Subject: [MirageOS-devel] Would it be be useful to add DAFT in the pioneer projects of mirage? X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org Hello, There is some code and a small specification but nothing working yet: https://github.com/UnixJunkie/daft If it is useful, I can prepare and submit a description. -- Regards, Francois. _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Mon Feb 16 13:56:20 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 16 Feb 2015 13:56:20 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YNM9k-0004Vv-HY; Mon, 16 Feb 2015 13:56:12 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YNHpM-0003eO-UL for mirageos-devel@lists.xenproject.org; Mon, 16 Feb 2015 09:18:53 +0000 Received: from [193.109.254.147] by server-15.bemta-14.messagelabs.com id 64/F9-02770-CF5B1E45; Mon, 16 Feb 2015 09:18:52 +0000 X-Env-Sender: francois.berenger@inria.fr X-Msg-Ref: server-5.tower-27.messagelabs.com!1424078331!9029153!1 X-Originating-IP: [192.134.164.83] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29621 invoked from network); 16 Feb 2015 09:18:51 -0000 Received: from mail2-relais-roc.national.inria.fr (HELO mail2-relais-roc.national.inria.fr) (192.134.164.83) by server-5.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 16 Feb 2015 09:18:51 -0000 X-IronPort-AV: E=Sophos;i="5.09,586,1418079600"; d="scan'208";a="121903238" Received: from meleze.ens.fr (HELO [129.199.99.114]) ([129.199.99.114]) by mail2-relais-roc.national.inria.fr with ESMTP/TLS/DHE-RSA-AES128-SHA; 16 Feb 2015 10:18:38 +0100 Message-ID: <54E1B5EA.9010301@inria.fr> Date: Mon, 16 Feb 2015 10:18:34 +0100 From: Francois Berenger User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: mirageos-devel@lists.xenproject.org X-Mailman-Approved-At: Mon, 16 Feb 2015 13:56:11 +0000 Subject: [MirageOS-devel] Would it be be useful to add DAFT in the pioneer projects of mirage? X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org Hello, There is some code and a small specification but nothing working yet: https://github.com/UnixJunkie/daft If it is useful, I can prepare and submit a description. -- Regards, Francois. _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Mon Feb 16 14:04:04 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 16 Feb 2015 14:04:04 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YNMHM-0005Cv-A6; Mon, 16 Feb 2015 14:04:04 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YNMHK-0005CW-Dd for mirageos-devel@lists.xenproject.org; Mon, 16 Feb 2015 14:04:02 +0000 Received: from [85.158.143.35] by server-2.bemta-4.messagelabs.com id 7F/17-02830-1D8F1E45; Mon, 16 Feb 2015 14:04:01 +0000 X-Env-Sender: talex5@gmail.com X-Msg-Ref: server-12.tower-21.messagelabs.com!1424095432!12175422!1 X-Originating-IP: [209.85.215.50] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20327 invoked from network); 16 Feb 2015 14:04:00 -0000 Received: from mail-la0-f50.google.com (HELO mail-la0-f50.google.com) (209.85.215.50) by server-12.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 16 Feb 2015 14:04:00 -0000 Received: by labpn19 with SMTP id pn19so28769257lab.4 for ; Mon, 16 Feb 2015 06:03:52 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=UrZHrxaNLz0CfXdyWznqv07udix6nZo5r5w6kaMsMYQ=; b=LEahnRCYB6ZZEV/l1GZ8QAQsZd3JI2NB+jcL4b77r3lXnonBWm0MSUndmqvNBSDM+v 77ZB9p9g7InQJQ1Jj3Kbz+XExMkhMgY//xIGunk50l6vKURMQtcilZKAi9lgNT3OFIIH 2gqt8pMWIRTzTh60k5VoERWYBxdJHTRlda9pU5rFH+c8FDVFRsbwaKgdaPOymdaUDguH ZM7ThoBM6eofG0CwZxfsd+AZoUfcMPOEudrXUoNMh2X7ISW3un6uolLihMPmsM77iZNw 8EQh0tLtceOQj2v5OBY7mfiK74gMoZF/VXGKSi2UDJzd96SZvaj0UKFhMP85hY12iJzk n4JA== MIME-Version: 1.0 X-Received: by 10.153.4.44 with SMTP id cb12mr11570314lad.26.1424095431929; Mon, 16 Feb 2015 06:03:51 -0800 (PST) Received: by 10.25.207.206 with HTTP; Mon, 16 Feb 2015 06:03:51 -0800 (PST) Date: Mon, 16 Feb 2015 14:03:51 +0000 Message-ID: From: Thomas Leonard To: "mirageos-devel@lists.xenproject.org" Subject: [MirageOS-devel] Irmin and js_of_ocaml X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org Is it possible to use Irmin under js_of_ocaml? I tried it, but I got this in the browser console at startup: uncaught exception: 0,0,Failure,ml_z_init not implemented It looks like Irmin pulls in Nocrypto (and thus zarith) only for the SHA1.digest function. There are also lots of warnings about missing cstruct stubs. I was thinking of running Irmin in the browser with HTML 5 storage as a backend, but perhaps it would be easier to keep Irmin on the server. Any suggestions? -- Dr Thomas Leonard http://0install.net/ GPG: 9242 9807 C985 3C07 44A6 8B9A AE07 8280 59A5 3CC1 GPG: DA98 25AE CAD0 8975 7CDA BD8E 0713 3F96 CA74 D8BA _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Mon Feb 16 14:04:04 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 16 Feb 2015 14:04:04 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YNMHM-0005Cv-A6; Mon, 16 Feb 2015 14:04:04 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YNMHK-0005CW-Dd for mirageos-devel@lists.xenproject.org; Mon, 16 Feb 2015 14:04:02 +0000 Received: from [85.158.143.35] by server-2.bemta-4.messagelabs.com id 7F/17-02830-1D8F1E45; Mon, 16 Feb 2015 14:04:01 +0000 X-Env-Sender: talex5@gmail.com X-Msg-Ref: server-12.tower-21.messagelabs.com!1424095432!12175422!1 X-Originating-IP: [209.85.215.50] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20327 invoked from network); 16 Feb 2015 14:04:00 -0000 Received: from mail-la0-f50.google.com (HELO mail-la0-f50.google.com) (209.85.215.50) by server-12.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 16 Feb 2015 14:04:00 -0000 Received: by labpn19 with SMTP id pn19so28769257lab.4 for ; Mon, 16 Feb 2015 06:03:52 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=UrZHrxaNLz0CfXdyWznqv07udix6nZo5r5w6kaMsMYQ=; b=LEahnRCYB6ZZEV/l1GZ8QAQsZd3JI2NB+jcL4b77r3lXnonBWm0MSUndmqvNBSDM+v 77ZB9p9g7InQJQ1Jj3Kbz+XExMkhMgY//xIGunk50l6vKURMQtcilZKAi9lgNT3OFIIH 2gqt8pMWIRTzTh60k5VoERWYBxdJHTRlda9pU5rFH+c8FDVFRsbwaKgdaPOymdaUDguH ZM7ThoBM6eofG0CwZxfsd+AZoUfcMPOEudrXUoNMh2X7ISW3un6uolLihMPmsM77iZNw 8EQh0tLtceOQj2v5OBY7mfiK74gMoZF/VXGKSi2UDJzd96SZvaj0UKFhMP85hY12iJzk n4JA== MIME-Version: 1.0 X-Received: by 10.153.4.44 with SMTP id cb12mr11570314lad.26.1424095431929; Mon, 16 Feb 2015 06:03:51 -0800 (PST) Received: by 10.25.207.206 with HTTP; Mon, 16 Feb 2015 06:03:51 -0800 (PST) Date: Mon, 16 Feb 2015 14:03:51 +0000 Message-ID: From: Thomas Leonard To: "mirageos-devel@lists.xenproject.org" Subject: [MirageOS-devel] Irmin and js_of_ocaml X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org Is it possible to use Irmin under js_of_ocaml? I tried it, but I got this in the browser console at startup: uncaught exception: 0,0,Failure,ml_z_init not implemented It looks like Irmin pulls in Nocrypto (and thus zarith) only for the SHA1.digest function. There are also lots of warnings about missing cstruct stubs. I was thinking of running Irmin in the browser with HTML 5 storage as a backend, but perhaps it would be easier to keep Irmin on the server. Any suggestions? -- Dr Thomas Leonard http://0install.net/ GPG: 9242 9807 C985 3C07 44A6 8B9A AE07 8280 59A5 3CC1 GPG: DA98 25AE CAD0 8975 7CDA BD8E 0713 3F96 CA74 D8BA _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Mon Feb 16 14:15:52 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 16 Feb 2015 14:15:52 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YNMSl-0006Vk-Lj; Mon, 16 Feb 2015 14:15:51 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YNMSl-0006Vf-8q for mirageos-devel@lists.xenproject.org; Mon, 16 Feb 2015 14:15:51 +0000 Received: from [85.158.137.68] by server-5.bemta-3.messagelabs.com id B1/45-03219-69BF1E45; Mon, 16 Feb 2015 14:15:50 +0000 X-Env-Sender: drupyog+caml@zoho.com X-Msg-Ref: server-3.tower-31.messagelabs.com!1424096147!12032585!1 X-Originating-IP: [74.201.84.156] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11403 invoked from network); 16 Feb 2015 14:15:49 -0000 Received: from sender1.zohomail.com (HELO sender1.zohomail.com) (74.201.84.156) by server-3.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 16 Feb 2015 14:15:49 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=zapps768; d=zoho.com; h=message-id:date:from:user-agent:mime-version:to:subject:references:in-reply-to:content-type; b=ZDPnIDMrviwA0JGKb2WhQ+bidVoBpBiu9yYLo4HqKl5uETGhWGB0YcLVBY837gZfjnhhELJo7MP+ fVEV361GMHCosL/W5FKVSVBE6DD61HhHkCzhK904/HAqVJVqSnOS Received: from [10.0.0.178] (ursae.inria.fr [128.93.132.58]) by mx.zohomail.com with SMTPS id 1424096144898208.53426847115645; Mon, 16 Feb 2015 06:15:44 -0800 (PST) Message-ID: <54E1FB8E.5060009@zoho.com> Date: Mon, 16 Feb 2015 15:15:42 +0100 From: Drup User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: Thomas Leonard , "mirageos-devel@lists.xenproject.org" References: In-Reply-To: Content-Length:1117 X-ZohoMailClient: External X-Zoho-Virus-Status: 2 Subject: Re: [MirageOS-devel] Irmin and js_of_ocaml X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="windows-1252"; Format="flowed" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org 1) Irmin on the browser would be very useful! 2) No opinion on the nocrypto usage in Irmin, maybe it should be = isolated away. However we have a bigint implementation in javascript in = order to have num in js_of_ocaml, so it should be possible to reuse that = for zarith. Having zarith in js_of_ocaml would be great too (several = person expressed interests about that). Le 16/02/2015 15:03, Thomas Leonard a =E9crit : > Is it possible to use Irmin under js_of_ocaml? I tried it, but I got > this in the browser console at startup: > > uncaught exception: 0,0,Failure,ml_z_init not implemented > > It looks like Irmin pulls in Nocrypto (and thus zarith) only for the > SHA1.digest function. There are also lots of warnings about missing > cstruct stubs. > > I was thinking of running Irmin in the browser with HTML 5 storage as > a backend, but perhaps it would be easier to keep Irmin on the server. > Any suggestions? > > _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Mon Feb 16 14:15:52 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 16 Feb 2015 14:15:52 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YNMSl-0006Vk-Lj; Mon, 16 Feb 2015 14:15:51 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YNMSl-0006Vf-8q for mirageos-devel@lists.xenproject.org; Mon, 16 Feb 2015 14:15:51 +0000 Received: from [85.158.137.68] by server-5.bemta-3.messagelabs.com id B1/45-03219-69BF1E45; Mon, 16 Feb 2015 14:15:50 +0000 X-Env-Sender: drupyog+caml@zoho.com X-Msg-Ref: server-3.tower-31.messagelabs.com!1424096147!12032585!1 X-Originating-IP: [74.201.84.156] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11403 invoked from network); 16 Feb 2015 14:15:49 -0000 Received: from sender1.zohomail.com (HELO sender1.zohomail.com) (74.201.84.156) by server-3.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 16 Feb 2015 14:15:49 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=zapps768; d=zoho.com; h=message-id:date:from:user-agent:mime-version:to:subject:references:in-reply-to:content-type; b=ZDPnIDMrviwA0JGKb2WhQ+bidVoBpBiu9yYLo4HqKl5uETGhWGB0YcLVBY837gZfjnhhELJo7MP+ fVEV361GMHCosL/W5FKVSVBE6DD61HhHkCzhK904/HAqVJVqSnOS Received: from [10.0.0.178] (ursae.inria.fr [128.93.132.58]) by mx.zohomail.com with SMTPS id 1424096144898208.53426847115645; Mon, 16 Feb 2015 06:15:44 -0800 (PST) Message-ID: <54E1FB8E.5060009@zoho.com> Date: Mon, 16 Feb 2015 15:15:42 +0100 From: Drup User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: Thomas Leonard , "mirageos-devel@lists.xenproject.org" References: In-Reply-To: Content-Length:1117 X-ZohoMailClient: External X-Zoho-Virus-Status: 2 Subject: Re: [MirageOS-devel] Irmin and js_of_ocaml X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="windows-1252"; Format="flowed" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org 1) Irmin on the browser would be very useful! 2) No opinion on the nocrypto usage in Irmin, maybe it should be = isolated away. However we have a bigint implementation in javascript in = order to have num in js_of_ocaml, so it should be possible to reuse that = for zarith. Having zarith in js_of_ocaml would be great too (several = person expressed interests about that). Le 16/02/2015 15:03, Thomas Leonard a =E9crit : > Is it possible to use Irmin under js_of_ocaml? I tried it, but I got > this in the browser console at startup: > > uncaught exception: 0,0,Failure,ml_z_init not implemented > > It looks like Irmin pulls in Nocrypto (and thus zarith) only for the > SHA1.digest function. There are also lots of warnings about missing > cstruct stubs. > > I was thinking of running Irmin in the browser with HTML 5 storage as > a backend, but perhaps it would be easier to keep Irmin on the server. > Any suggestions? > > _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Mon Feb 16 15:46:55 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 16 Feb 2015 15:46:55 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YNNsp-0007vq-Bh; Mon, 16 Feb 2015 15:46:51 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YNNsn-0007vl-Jz for mirageos-devel@lists.xenproject.org; Mon, 16 Feb 2015 15:46:49 +0000 Received: from [85.158.143.35] by server-3.bemta-4.messagelabs.com id F9/1E-29399-8E012E45; Mon, 16 Feb 2015 15:46:48 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-12.tower-21.messagelabs.com!1424101605!12199138!1 X-Originating-IP: [209.85.212.174] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30367 invoked from network); 16 Feb 2015 15:46:47 -0000 Received: from mail-wi0-f174.google.com (HELO mail-wi0-f174.google.com) (209.85.212.174) by server-12.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 16 Feb 2015 15:46:47 -0000 Received: by mail-wi0-f174.google.com with SMTP id em10so26962808wid.1 for ; Mon, 16 Feb 2015 07:46:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=7R97DCHiXXWOMfpaua7OORV45dFRJuWfR+SNdeRvEFg=; b=mxj6q/v8G/5yRW47N0lOSv2hFUS7D8DRC93Lwm/JJuhUsdx2wUwrmQ+FHt6vCa7Khp YdiixgY69ubbf0z1qHOK5W7ZMeRE8ssSmmDA84T39HtoB49ObkPwgTvXGmCq1xkiiBOS rXYS/DWWGHk5n8zkyejqSEsZdLaijQb1oxwFac6lPclVkJRskcHI5Jyhn90vWOZ964kv I2kTlL8U89H1qlczbzuSHq7AwQsXhqhokIke5Akchr9YKV080sFC0OcTO7hb9atXXQwx Ihyk8Pvx1zXSVmtPiRAb8iWf/z1jUUk02BnTHdzjK0S+ubyUd2k0lPrIMzeSuUacQ18N TKdQ== X-Received: by 10.180.24.65 with SMTP id s1mr18392818wif.30.1424101604492; Mon, 16 Feb 2015 07:46:44 -0800 (PST) Received: from piana.mac.cl.cam.ac.uk (piana.mac.cl.cam.ac.uk. [128.232.56.38]) by mx.google.com with ESMTPSA id hz9sm23379812wjb.17.2015.02.16.07.46.43 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 16 Feb 2015 07:46:43 -0800 (PST) Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) From: Thomas Gazagnaire In-Reply-To: Date: Mon, 16 Feb 2015 15:47:06 +0000 Message-Id: References: To: Thomas Leonard X-Mailer: Apple Mail (2.2070.6) Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Irmin and js_of_ocaml X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org > Is it possible to use Irmin under js_of_ocaml? I tried it, but I got > this in the browser console at startup: > > uncaught exception: 0,0,Failure,ml_z_init not implemented > > It looks like Irmin pulls in Nocrypto (and thus zarith) only for the > SHA1.digest function. There are also lots of warnings about missing > cstruct stubs. > > I was thinking of running Irmin in the browser with HTML 5 storage as > a backend, but perhaps it would be easier to keep Irmin on the server. > Any suggestions? Basic stuff used to work in JS at one point, but not anymore: I'd be *very* interested to get the support back in good shape though. I think the shorter way is to forget about the Git format (at least for a first step) and write a custom backend for local storage: a mix between https://github.com/mirage/irmin/blob/master/lib/mem/irmin_mem.ml and https://github.com/avsm/ocaml-js-localstorage/blob/master/lib/localStorage.ml. You won't be able to sync using Git, but you can still use the custom Irmin sync protocol. Having a proper support for the Git format is a bit more involved: you indeed need nocrypto (for SHA1) and camlzip (for zlib). But being able to Git clone/push from your browser would be quite cool and crazy :-) Thomas _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Mon Feb 16 15:46:55 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 16 Feb 2015 15:46:55 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YNNsp-0007vq-Bh; Mon, 16 Feb 2015 15:46:51 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YNNsn-0007vl-Jz for mirageos-devel@lists.xenproject.org; Mon, 16 Feb 2015 15:46:49 +0000 Received: from [85.158.143.35] by server-3.bemta-4.messagelabs.com id F9/1E-29399-8E012E45; Mon, 16 Feb 2015 15:46:48 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-12.tower-21.messagelabs.com!1424101605!12199138!1 X-Originating-IP: [209.85.212.174] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30367 invoked from network); 16 Feb 2015 15:46:47 -0000 Received: from mail-wi0-f174.google.com (HELO mail-wi0-f174.google.com) (209.85.212.174) by server-12.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 16 Feb 2015 15:46:47 -0000 Received: by mail-wi0-f174.google.com with SMTP id em10so26962808wid.1 for ; Mon, 16 Feb 2015 07:46:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=7R97DCHiXXWOMfpaua7OORV45dFRJuWfR+SNdeRvEFg=; b=mxj6q/v8G/5yRW47N0lOSv2hFUS7D8DRC93Lwm/JJuhUsdx2wUwrmQ+FHt6vCa7Khp YdiixgY69ubbf0z1qHOK5W7ZMeRE8ssSmmDA84T39HtoB49ObkPwgTvXGmCq1xkiiBOS rXYS/DWWGHk5n8zkyejqSEsZdLaijQb1oxwFac6lPclVkJRskcHI5Jyhn90vWOZ964kv I2kTlL8U89H1qlczbzuSHq7AwQsXhqhokIke5Akchr9YKV080sFC0OcTO7hb9atXXQwx Ihyk8Pvx1zXSVmtPiRAb8iWf/z1jUUk02BnTHdzjK0S+ubyUd2k0lPrIMzeSuUacQ18N TKdQ== X-Received: by 10.180.24.65 with SMTP id s1mr18392818wif.30.1424101604492; Mon, 16 Feb 2015 07:46:44 -0800 (PST) Received: from piana.mac.cl.cam.ac.uk (piana.mac.cl.cam.ac.uk. [128.232.56.38]) by mx.google.com with ESMTPSA id hz9sm23379812wjb.17.2015.02.16.07.46.43 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 16 Feb 2015 07:46:43 -0800 (PST) Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) From: Thomas Gazagnaire In-Reply-To: Date: Mon, 16 Feb 2015 15:47:06 +0000 Message-Id: References: To: Thomas Leonard X-Mailer: Apple Mail (2.2070.6) Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Irmin and js_of_ocaml X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org > Is it possible to use Irmin under js_of_ocaml? I tried it, but I got > this in the browser console at startup: > > uncaught exception: 0,0,Failure,ml_z_init not implemented > > It looks like Irmin pulls in Nocrypto (and thus zarith) only for the > SHA1.digest function. There are also lots of warnings about missing > cstruct stubs. > > I was thinking of running Irmin in the browser with HTML 5 storage as > a backend, but perhaps it would be easier to keep Irmin on the server. > Any suggestions? Basic stuff used to work in JS at one point, but not anymore: I'd be *very* interested to get the support back in good shape though. I think the shorter way is to forget about the Git format (at least for a first step) and write a custom backend for local storage: a mix between https://github.com/mirage/irmin/blob/master/lib/mem/irmin_mem.ml and https://github.com/avsm/ocaml-js-localstorage/blob/master/lib/localStorage.ml. You won't be able to sync using Git, but you can still use the custom Irmin sync protocol. Having a proper support for the Git format is a bit more involved: you indeed need nocrypto (for SHA1) and camlzip (for zlib). But being able to Git clone/push from your browser would be quite cool and crazy :-) Thomas _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Mon Feb 16 19:01:20 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 16 Feb 2015 19:01:20 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YNQux-0005N9-ME; Mon, 16 Feb 2015 19:01:15 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YNQuw-0005N4-JR for mirageos-devel@lists.xenproject.org; Mon, 16 Feb 2015 19:01:14 +0000 Received: from [193.109.254.147] by server-8.bemta-14.messagelabs.com id F0/29-03168-97E32E45; Mon, 16 Feb 2015 19:01:13 +0000 X-Env-Sender: richard.mortier@gmail.com X-Msg-Ref: server-7.tower-27.messagelabs.com!1424113272!13772137!1 X-Originating-IP: [209.85.216.171] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5365 invoked from network); 16 Feb 2015 19:01:12 -0000 Received: from mail-qc0-f171.google.com (HELO mail-qc0-f171.google.com) (209.85.216.171) by server-7.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 16 Feb 2015 19:01:12 -0000 Received: by mail-qc0-f171.google.com with SMTP id l6so25544781qcy.2 for ; Mon, 16 Feb 2015 11:01:11 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=GqEjMrKxjfseYlKAONtOFGtHVF0cj0QmclmEniCBQu8=; b=GUkYLun71AGhXEjoZHn5LS101GuTjUYfH7P3hL9Tn0FSjs4cf37FDogt9Nldm8+Yec BvG2vYJUobNJtEHpGLlxASx8o1814O1X20ZaPZaqBmP2Kx8hFZf1K1B8zMp46ckR3OxQ JpdkirEMZo/1XZTEwrcTe9B4+EYqeQOb/KTcxl4nLEL37NtW0NnxpCOTlgC0xRCUGEkp BTeIc99Uo7NOhs2XYOOXY/bOqm09KI5U0phFH2VDEejv90Wl4ON1i1YPbM6xn7r+SwPQ uG7yekm35G6zqNfjubCHvycNzc9skKLw3d6KQl7OFOu5pFKcx2HXkArLoNET1IG6mJD5 XGWg== X-Received: by 10.229.201.1 with SMTP id ey1mr76605qcb.10.1424113271803; Mon, 16 Feb 2015 11:01:11 -0800 (PST) Received: from mail-qg0-f50.google.com (mail-qg0-f50.google.com. [209.85.192.50]) by mx.google.com with ESMTPSA id s63sm14337572qgd.26.2015.02.16.11.01.10 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 16 Feb 2015 11:01:11 -0800 (PST) Received: by mail-qg0-f50.google.com with SMTP id e89so24676727qgf.9 for ; Mon, 16 Feb 2015 11:01:10 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.229.70.201 with SMTP id e9mr969855qcj.6.1424113270568; Mon, 16 Feb 2015 11:01:10 -0800 (PST) Received: by 10.140.92.245 with HTTP; Mon, 16 Feb 2015 11:01:10 -0800 (PST) In-Reply-To: References: Date: Mon, 16 Feb 2015 19:01:10 +0000 Message-ID: From: Richard Mortier To: Thomas Gazagnaire Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Irmin and js_of_ocaml X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 16 February 2015 at 15:47, Thomas Gazagnaire wrote: >> Is it possible to use Irmin under js_of_ocaml? I tried it, but I got >> this in the browser console at startup: >> >> uncaught exception: 0,0,Failure,ml_z_init not implemented >> >> It looks like Irmin pulls in Nocrypto (and thus zarith) only for the >> SHA1.digest function. There are also lots of warnings about missing >> cstruct stubs. if not, I guess one might make use of http://code.google.com/p/crypto-js/ to provide the SHA1.digest function...? [ apologies if that's a repeat, sent from the wrong address previously. ] >> I was thinking of running Irmin in the browser with HTML 5 storage as >> a backend, but perhaps it would be easier to keep Irmin on the server. >> Any suggestions? > > Basic stuff used to work in JS at one point, but not anymore: I'd be *very* interested to get the support back in good shape though. > > I think the shorter way is to forget about the Git format (at least for a first step) and write a custom backend for local storage: a mix between https://github.com/mirage/irmin/blob/master/lib/mem/irmin_mem.ml and https://github.com/avsm/ocaml-js-localstorage/blob/master/lib/localStorage.ml. You won't be able to sync using Git, but you can still use the custom Irmin sync protocol. > > Having a proper support for the Git format is a bit more involved: you indeed need nocrypto (for SHA1) and camlzip (for zlib). But being able to Git clone/push from your browser would be quite cool and crazy :-) > istr one of the notts programmers crowd was doing a javascript git implementation; came across https://github.com/creationix/js-git after a quick search... -- Richard Mortier richard.mortier@cl.cam.ac.uk _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Mon Feb 16 19:01:20 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 16 Feb 2015 19:01:20 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YNQux-0005N9-ME; Mon, 16 Feb 2015 19:01:15 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YNQuw-0005N4-JR for mirageos-devel@lists.xenproject.org; Mon, 16 Feb 2015 19:01:14 +0000 Received: from [193.109.254.147] by server-8.bemta-14.messagelabs.com id F0/29-03168-97E32E45; Mon, 16 Feb 2015 19:01:13 +0000 X-Env-Sender: richard.mortier@gmail.com X-Msg-Ref: server-7.tower-27.messagelabs.com!1424113272!13772137!1 X-Originating-IP: [209.85.216.171] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5365 invoked from network); 16 Feb 2015 19:01:12 -0000 Received: from mail-qc0-f171.google.com (HELO mail-qc0-f171.google.com) (209.85.216.171) by server-7.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 16 Feb 2015 19:01:12 -0000 Received: by mail-qc0-f171.google.com with SMTP id l6so25544781qcy.2 for ; Mon, 16 Feb 2015 11:01:11 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=GqEjMrKxjfseYlKAONtOFGtHVF0cj0QmclmEniCBQu8=; b=GUkYLun71AGhXEjoZHn5LS101GuTjUYfH7P3hL9Tn0FSjs4cf37FDogt9Nldm8+Yec BvG2vYJUobNJtEHpGLlxASx8o1814O1X20ZaPZaqBmP2Kx8hFZf1K1B8zMp46ckR3OxQ JpdkirEMZo/1XZTEwrcTe9B4+EYqeQOb/KTcxl4nLEL37NtW0NnxpCOTlgC0xRCUGEkp BTeIc99Uo7NOhs2XYOOXY/bOqm09KI5U0phFH2VDEejv90Wl4ON1i1YPbM6xn7r+SwPQ uG7yekm35G6zqNfjubCHvycNzc9skKLw3d6KQl7OFOu5pFKcx2HXkArLoNET1IG6mJD5 XGWg== X-Received: by 10.229.201.1 with SMTP id ey1mr76605qcb.10.1424113271803; Mon, 16 Feb 2015 11:01:11 -0800 (PST) Received: from mail-qg0-f50.google.com (mail-qg0-f50.google.com. [209.85.192.50]) by mx.google.com with ESMTPSA id s63sm14337572qgd.26.2015.02.16.11.01.10 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 16 Feb 2015 11:01:11 -0800 (PST) Received: by mail-qg0-f50.google.com with SMTP id e89so24676727qgf.9 for ; Mon, 16 Feb 2015 11:01:10 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.229.70.201 with SMTP id e9mr969855qcj.6.1424113270568; Mon, 16 Feb 2015 11:01:10 -0800 (PST) Received: by 10.140.92.245 with HTTP; Mon, 16 Feb 2015 11:01:10 -0800 (PST) In-Reply-To: References: Date: Mon, 16 Feb 2015 19:01:10 +0000 Message-ID: From: Richard Mortier To: Thomas Gazagnaire Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Irmin and js_of_ocaml X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 16 February 2015 at 15:47, Thomas Gazagnaire wrote: >> Is it possible to use Irmin under js_of_ocaml? I tried it, but I got >> this in the browser console at startup: >> >> uncaught exception: 0,0,Failure,ml_z_init not implemented >> >> It looks like Irmin pulls in Nocrypto (and thus zarith) only for the >> SHA1.digest function. There are also lots of warnings about missing >> cstruct stubs. if not, I guess one might make use of http://code.google.com/p/crypto-js/ to provide the SHA1.digest function...? [ apologies if that's a repeat, sent from the wrong address previously. ] >> I was thinking of running Irmin in the browser with HTML 5 storage as >> a backend, but perhaps it would be easier to keep Irmin on the server. >> Any suggestions? > > Basic stuff used to work in JS at one point, but not anymore: I'd be *very* interested to get the support back in good shape though. > > I think the shorter way is to forget about the Git format (at least for a first step) and write a custom backend for local storage: a mix between https://github.com/mirage/irmin/blob/master/lib/mem/irmin_mem.ml and https://github.com/avsm/ocaml-js-localstorage/blob/master/lib/localStorage.ml. You won't be able to sync using Git, but you can still use the custom Irmin sync protocol. > > Having a proper support for the Git format is a bit more involved: you indeed need nocrypto (for SHA1) and camlzip (for zlib). But being able to Git clone/push from your browser would be quite cool and crazy :-) > istr one of the notts programmers crowd was doing a javascript git implementation; came across https://github.com/creationix/js-git after a quick search... -- Richard Mortier richard.mortier@cl.cam.ac.uk _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Mon Feb 16 19:23:14 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 16 Feb 2015 19:23:14 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YNRGB-0007F4-OA; Mon, 16 Feb 2015 19:23:11 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YNRGB-0007Ez-9j for mirageos-devel@lists.xenproject.org; Mon, 16 Feb 2015 19:23:11 +0000 Received: from [85.158.143.35] by server-1.bemta-4.messagelabs.com id 76/0E-03004-E9342E45; Mon, 16 Feb 2015 19:23:10 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-7.tower-21.messagelabs.com!1424114589!12247846!1 X-Originating-IP: [209.85.212.178] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 1822 invoked from network); 16 Feb 2015 19:23:09 -0000 Received: from mail-wi0-f178.google.com (HELO mail-wi0-f178.google.com) (209.85.212.178) by server-7.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 16 Feb 2015 19:23:09 -0000 Received: by mail-wi0-f178.google.com with SMTP id em10so28347918wid.5 for ; Mon, 16 Feb 2015 11:23:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=xMCaFW6GpC7RATBvQMvRTINreTxKzB4PdKDYG3erk24=; b=Sb4N0YOFk3WsureUrBAhL+ScZPCFgzJ/8RLVRtoTPpBsa9ws7kPOP94j/jXxB0qzaa qjn+3S9tEPkyNPq1fp+ZIp9UfhlIUgyPsnbogkPLOgMHKZ4VOSLWxICFlGzj3wONO/OC 1vziNqCPbVUqTk4y2JcatqWmMYeDkCDSZpcTEN2encxFfmRiXwTMGnGvJuSqYiUChqUd kEqFaWmDa5ItQfgsTJ0sQehEYpWRGSJPtBpBd0+ltoBS3/VlqkodkaeHEMG/ftpJDzPf Z2UXLDyRISGe/ZV2rZSUVeyarLVrfzXJJJVrj7NI01VoDOjzxTf0w0d0pb1Pg8YifKij Y7Bw== X-Received: by 10.194.71.110 with SMTP id t14mr54226829wju.58.1424114589517; Mon, 16 Feb 2015 11:23:09 -0800 (PST) Received: from [192.168.0.2] (cpc25-cmbg14-2-0-cust121.5-4.cable.virginm.net. [213.106.112.122]) by mx.google.com with ESMTPSA id d10sm24121800wjn.45.2015.02.16.11.23.08 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 16 Feb 2015 11:23:08 -0800 (PST) Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) From: Thomas Gazagnaire In-Reply-To: Date: Mon, 16 Feb 2015 19:23:07 +0000 Message-Id: References: To: Richard Mortier X-Mailer: Apple Mail (2.2070.6) Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Irmin and js_of_ocaml X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org >> Having a proper support for the Git format is a bit more involved: you indeed need nocrypto (for SHA1) and camlzip (for zlib). But being able to Git clone/push from your browser would be quite cool and crazy :-) >> > > istr one of the notts programmers crowd was doing a javascript git > implementation; came across https://github.com/creationix/js-git after > a quick search... indeed. They seem to use https://github.com/nodeca/pako for zlib which looks nice. Thomas _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Mon Feb 16 19:23:14 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 16 Feb 2015 19:23:14 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YNRGB-0007F4-OA; Mon, 16 Feb 2015 19:23:11 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YNRGB-0007Ez-9j for mirageos-devel@lists.xenproject.org; Mon, 16 Feb 2015 19:23:11 +0000 Received: from [85.158.143.35] by server-1.bemta-4.messagelabs.com id 76/0E-03004-E9342E45; Mon, 16 Feb 2015 19:23:10 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-7.tower-21.messagelabs.com!1424114589!12247846!1 X-Originating-IP: [209.85.212.178] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 1822 invoked from network); 16 Feb 2015 19:23:09 -0000 Received: from mail-wi0-f178.google.com (HELO mail-wi0-f178.google.com) (209.85.212.178) by server-7.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 16 Feb 2015 19:23:09 -0000 Received: by mail-wi0-f178.google.com with SMTP id em10so28347918wid.5 for ; Mon, 16 Feb 2015 11:23:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=xMCaFW6GpC7RATBvQMvRTINreTxKzB4PdKDYG3erk24=; b=Sb4N0YOFk3WsureUrBAhL+ScZPCFgzJ/8RLVRtoTPpBsa9ws7kPOP94j/jXxB0qzaa qjn+3S9tEPkyNPq1fp+ZIp9UfhlIUgyPsnbogkPLOgMHKZ4VOSLWxICFlGzj3wONO/OC 1vziNqCPbVUqTk4y2JcatqWmMYeDkCDSZpcTEN2encxFfmRiXwTMGnGvJuSqYiUChqUd kEqFaWmDa5ItQfgsTJ0sQehEYpWRGSJPtBpBd0+ltoBS3/VlqkodkaeHEMG/ftpJDzPf Z2UXLDyRISGe/ZV2rZSUVeyarLVrfzXJJJVrj7NI01VoDOjzxTf0w0d0pb1Pg8YifKij Y7Bw== X-Received: by 10.194.71.110 with SMTP id t14mr54226829wju.58.1424114589517; Mon, 16 Feb 2015 11:23:09 -0800 (PST) Received: from [192.168.0.2] (cpc25-cmbg14-2-0-cust121.5-4.cable.virginm.net. [213.106.112.122]) by mx.google.com with ESMTPSA id d10sm24121800wjn.45.2015.02.16.11.23.08 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 16 Feb 2015 11:23:08 -0800 (PST) Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) From: Thomas Gazagnaire In-Reply-To: Date: Mon, 16 Feb 2015 19:23:07 +0000 Message-Id: References: To: Richard Mortier X-Mailer: Apple Mail (2.2070.6) Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Irmin and js_of_ocaml X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org >> Having a proper support for the Git format is a bit more involved: you indeed need nocrypto (for SHA1) and camlzip (for zlib). But being able to Git clone/push from your browser would be quite cool and crazy :-) >> > > istr one of the notts programmers crowd was doing a javascript git > implementation; came across https://github.com/creationix/js-git after > a quick search... indeed. They seem to use https://github.com/nodeca/pako for zlib which looks nice. Thomas _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Mon Feb 16 20:55:19 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 16 Feb 2015 20:55:19 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YNShH-0004dK-C2; Mon, 16 Feb 2015 20:55:15 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YNShG-0004dF-5h for mirageos-devel@lists.xenproject.org; Mon, 16 Feb 2015 20:55:14 +0000 Received: from [85.158.143.35] by server-1.bemta-4.messagelabs.com id 62/0F-03004-13952E45; Mon, 16 Feb 2015 20:55:13 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-15.tower-21.messagelabs.com!1424120112!12227380!1 X-Originating-IP: [209.85.212.175] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28472 invoked from network); 16 Feb 2015 20:55:12 -0000 Received: from mail-wi0-f175.google.com (HELO mail-wi0-f175.google.com) (209.85.212.175) by server-15.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 16 Feb 2015 20:55:12 -0000 Received: by mail-wi0-f175.google.com with SMTP id r20so28609072wiv.2 for ; Mon, 16 Feb 2015 12:55:12 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:from:content-type:content-transfer-encoding:subject :message-id:date:to:mime-version; bh=fnpBouY66wKlaTM4234jcQMANeRO5LoanpIQn301+7g=; b=RWR1GwJdsrZQUJuaekV9+0v3NqAuIOFTYbJiXolGdr4yh+xMia39amJg6LrvkC/xTz 988VwtjnNR/r7caSCsH8lRYUnhOAdHfZHbKO8QsBggiH4d1WAWyCMt9ZCQA7PHNg5RGf ryCOWrda4KsR8P9GiJ+tv8F75sdnpCH/IjraZ9brl/FM5uKDaIEEUj7YhyX/S/Ud9T07 iFJbzzLgjmQpUxnKCXxfNjyybHfIM3uaRQJWxymhOvYC5qozNoBKsk5REOEVANksBO2Q AH3Dvb64Gi9911hUCX4qoNIw5CJpa+W0zFaJhXv/2H2ANakXRSY81uTKAmyjiixD2eQ/ sp0g== X-Received: by 10.180.206.14 with SMTP id lk14mr50608860wic.71.1424120112451; Mon, 16 Feb 2015 12:55:12 -0800 (PST) Received: from [192.168.0.2] (cpc25-cmbg14-2-0-cust121.5-4.cable.virginm.net. [213.106.112.122]) by mx.google.com with ESMTPSA id hd5sm21253787wib.21.2015.02.16.12.55.11 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 16 Feb 2015 12:55:11 -0800 (PST) From: Thomas Gazagnaire Message-Id: <7772C602-E0F4-43E2-96EF-CCBD58B43596@gazagnaire.org> Date: Mon, 16 Feb 2015 20:55:10 +0000 To: mirageos-devel Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) X-Mailer: Apple Mail (2.2070.6) Subject: [MirageOS-devel] [ANN] release of dog 0.1.0 X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org I'd like to announce the first (very alpha) release of a new synchronisation tool: "dog" To install it: `opam install dog` The tool is built using Irmin and it demonstrate a simple distributed log server. Every client has a local (and partial) state of the system (a valid Git repository, whose active branch is the name of the client), and they synchronise explicitly with a server using the Irmin synchronisation protocol. The server listens for new clients and rebase every client branches into a sub-directory of the master branch. The server state is also stored in a Git repository, and it contains all the client history as well. So if you have: Client A: branch A: - foo.txt and Client B: branch B: - foo.txt On the server you'll have: branch A: - foo.txt branch B: - foo.txt branch master: A/foo.txt B/foo.txt This is very simple but already quite useful. As usual, feedback appreciated on https://github.com/samoht/dog/issues. Best, Thomas _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Mon Feb 16 20:55:19 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 16 Feb 2015 20:55:19 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YNShH-0004dK-C2; Mon, 16 Feb 2015 20:55:15 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YNShG-0004dF-5h for mirageos-devel@lists.xenproject.org; Mon, 16 Feb 2015 20:55:14 +0000 Received: from [85.158.143.35] by server-1.bemta-4.messagelabs.com id 62/0F-03004-13952E45; Mon, 16 Feb 2015 20:55:13 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-15.tower-21.messagelabs.com!1424120112!12227380!1 X-Originating-IP: [209.85.212.175] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28472 invoked from network); 16 Feb 2015 20:55:12 -0000 Received: from mail-wi0-f175.google.com (HELO mail-wi0-f175.google.com) (209.85.212.175) by server-15.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 16 Feb 2015 20:55:12 -0000 Received: by mail-wi0-f175.google.com with SMTP id r20so28609072wiv.2 for ; Mon, 16 Feb 2015 12:55:12 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:from:content-type:content-transfer-encoding:subject :message-id:date:to:mime-version; bh=fnpBouY66wKlaTM4234jcQMANeRO5LoanpIQn301+7g=; b=RWR1GwJdsrZQUJuaekV9+0v3NqAuIOFTYbJiXolGdr4yh+xMia39amJg6LrvkC/xTz 988VwtjnNR/r7caSCsH8lRYUnhOAdHfZHbKO8QsBggiH4d1WAWyCMt9ZCQA7PHNg5RGf ryCOWrda4KsR8P9GiJ+tv8F75sdnpCH/IjraZ9brl/FM5uKDaIEEUj7YhyX/S/Ud9T07 iFJbzzLgjmQpUxnKCXxfNjyybHfIM3uaRQJWxymhOvYC5qozNoBKsk5REOEVANksBO2Q AH3Dvb64Gi9911hUCX4qoNIw5CJpa+W0zFaJhXv/2H2ANakXRSY81uTKAmyjiixD2eQ/ sp0g== X-Received: by 10.180.206.14 with SMTP id lk14mr50608860wic.71.1424120112451; Mon, 16 Feb 2015 12:55:12 -0800 (PST) Received: from [192.168.0.2] (cpc25-cmbg14-2-0-cust121.5-4.cable.virginm.net. [213.106.112.122]) by mx.google.com with ESMTPSA id hd5sm21253787wib.21.2015.02.16.12.55.11 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 16 Feb 2015 12:55:11 -0800 (PST) From: Thomas Gazagnaire Message-Id: <7772C602-E0F4-43E2-96EF-CCBD58B43596@gazagnaire.org> Date: Mon, 16 Feb 2015 20:55:10 +0000 To: mirageos-devel Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) X-Mailer: Apple Mail (2.2070.6) Subject: [MirageOS-devel] [ANN] release of dog 0.1.0 X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org I'd like to announce the first (very alpha) release of a new synchronisation tool: "dog" To install it: `opam install dog` The tool is built using Irmin and it demonstrate a simple distributed log server. Every client has a local (and partial) state of the system (a valid Git repository, whose active branch is the name of the client), and they synchronise explicitly with a server using the Irmin synchronisation protocol. The server listens for new clients and rebase every client branches into a sub-directory of the master branch. The server state is also stored in a Git repository, and it contains all the client history as well. So if you have: Client A: branch A: - foo.txt and Client B: branch B: - foo.txt On the server you'll have: branch A: - foo.txt branch B: - foo.txt branch master: A/foo.txt B/foo.txt This is very simple but already quite useful. As usual, feedback appreciated on https://github.com/samoht/dog/issues. Best, Thomas _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Mon Feb 16 23:09:46 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 16 Feb 2015 23:09:46 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YNUnN-0000IO-JQ; Mon, 16 Feb 2015 23:09:41 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YNUnM-0000I4-KM for mirageos-devel@lists.xenproject.org; Mon, 16 Feb 2015 23:09:40 +0000 Received: from [193.109.254.147] by server-4.bemta-14.messagelabs.com id D8/18-02994-3B872E45; Mon, 16 Feb 2015 23:09:39 +0000 X-Env-Sender: richard.mortier@gmail.com X-Msg-Ref: server-13.tower-27.messagelabs.com!1424128178!13839040!1 X-Originating-IP: [209.85.192.50] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 1986 invoked from network); 16 Feb 2015 23:09:38 -0000 Received: from mail-qg0-f50.google.com (HELO mail-qg0-f50.google.com) (209.85.192.50) by server-13.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 16 Feb 2015 23:09:38 -0000 Received: by mail-qg0-f50.google.com with SMTP id e89so25580425qgf.9 for ; Mon, 16 Feb 2015 15:09:37 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=oIo/DQUlGB8EXY/PP9njkYjRyQ4k9kunhrn3PRlkzIg=; b=DSEeNp83RtFEoB6VNel3EeJi8yvTQ6PqRx96GP10F/FMDqWmn5f2YCgfffvEkFRz9v GD4djs5qWIrGVbllGdt88U7IAhMaskyG+WK3BXRazjzTiVD0KjxzOo2D5QVe3i7td9nN 7ldxJelksiSfj7+1mOz3KdUax6T+w+j+gwn3lGJT3rVDawJL1jZNKON6NCMEcYV26Jj0 L7bi9UCSQg/pwP+ulGdFp13VnwxzDfXtoSOE+2NgS16S+eVLuOKNC30/4NKALrbe3V2N AgAXraKvAXNUtD3WqBI4O/eH0f6PiOZITOb1GAZeIhtKunGXJXP7vsKjFHA/Ajus2ZsV YMRg== X-Received: by 10.140.108.201 with SMTP id j67mr1887994qgf.86.1424128177875; Mon, 16 Feb 2015 15:09:37 -0800 (PST) Received: from mail-qc0-f174.google.com (mail-qc0-f174.google.com. [209.85.216.174]) by mx.google.com with ESMTPSA id w107sm14741191qge.5.2015.02.16.15.09.37 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 16 Feb 2015 15:09:37 -0800 (PST) Received: by mail-qc0-f174.google.com with SMTP id c9so14804637qcz.5 for ; Mon, 16 Feb 2015 15:09:37 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.140.134.198 with SMTP id 189mr100947qhg.7.1424128177269; Mon, 16 Feb 2015 15:09:37 -0800 (PST) Received: by 10.140.92.245 with HTTP; Mon, 16 Feb 2015 15:09:37 -0800 (PST) In-Reply-To: <7772C602-E0F4-43E2-96EF-CCBD58B43596@gazagnaire.org> References: <7772C602-E0F4-43E2-96EF-CCBD58B43596@gazagnaire.org> Date: Tue, 17 Feb 2015 00:09:37 +0100 Message-ID: From: Richard Mortier To: Thomas Gazagnaire Cc: mirageos-devel Subject: Re: [MirageOS-devel] [ANN] release of dog 0.1.0 X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org [ resending as sent from incorrect mail address originally ] On 16 February 2015 at 21:55, Thomas Gazagnaire wrote: > I'd like to announce the first (very alpha) release of a new synchronisation tool: "dog" > > To install it: `opam install dog` > > The tool is built using Irmin and it demonstrate a simple distributed log server. Every client has a local (and partial) state of the system (a valid Git repository, whose active branch is the name of the client), and they synchronise explicitly with a server using the Irmin synchronisation protocol. The server listens for new clients and rebase every client branches into a sub-directory of the master branch. The server state is also stored in a Git repository, and it contains all the client history as well. So if you have: > cool! just given it a quick go and i suspect i'm missing something obvious... :) in ~/t/dog: ``` : mort@greyjay:dog$; dog listen Server started on port 8080. ``` in ~/t/dogc: ``` : mort@greyjay:dogc$; dog push -m "bark bark" http://localhost:8080 Unix.Unix_error(Unix.ECONNREFUSED, "connect", "") ``` how should i be trying to get a message logged? -- Richard Mortier richard.mortier@cl.cam.ac.uk _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Mon Feb 16 23:09:46 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 16 Feb 2015 23:09:46 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YNUnN-0000IO-JQ; Mon, 16 Feb 2015 23:09:41 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YNUnM-0000I4-KM for mirageos-devel@lists.xenproject.org; Mon, 16 Feb 2015 23:09:40 +0000 Received: from [193.109.254.147] by server-4.bemta-14.messagelabs.com id D8/18-02994-3B872E45; Mon, 16 Feb 2015 23:09:39 +0000 X-Env-Sender: richard.mortier@gmail.com X-Msg-Ref: server-13.tower-27.messagelabs.com!1424128178!13839040!1 X-Originating-IP: [209.85.192.50] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 1986 invoked from network); 16 Feb 2015 23:09:38 -0000 Received: from mail-qg0-f50.google.com (HELO mail-qg0-f50.google.com) (209.85.192.50) by server-13.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 16 Feb 2015 23:09:38 -0000 Received: by mail-qg0-f50.google.com with SMTP id e89so25580425qgf.9 for ; Mon, 16 Feb 2015 15:09:37 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=oIo/DQUlGB8EXY/PP9njkYjRyQ4k9kunhrn3PRlkzIg=; b=DSEeNp83RtFEoB6VNel3EeJi8yvTQ6PqRx96GP10F/FMDqWmn5f2YCgfffvEkFRz9v GD4djs5qWIrGVbllGdt88U7IAhMaskyG+WK3BXRazjzTiVD0KjxzOo2D5QVe3i7td9nN 7ldxJelksiSfj7+1mOz3KdUax6T+w+j+gwn3lGJT3rVDawJL1jZNKON6NCMEcYV26Jj0 L7bi9UCSQg/pwP+ulGdFp13VnwxzDfXtoSOE+2NgS16S+eVLuOKNC30/4NKALrbe3V2N AgAXraKvAXNUtD3WqBI4O/eH0f6PiOZITOb1GAZeIhtKunGXJXP7vsKjFHA/Ajus2ZsV YMRg== X-Received: by 10.140.108.201 with SMTP id j67mr1887994qgf.86.1424128177875; Mon, 16 Feb 2015 15:09:37 -0800 (PST) Received: from mail-qc0-f174.google.com (mail-qc0-f174.google.com. [209.85.216.174]) by mx.google.com with ESMTPSA id w107sm14741191qge.5.2015.02.16.15.09.37 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 16 Feb 2015 15:09:37 -0800 (PST) Received: by mail-qc0-f174.google.com with SMTP id c9so14804637qcz.5 for ; Mon, 16 Feb 2015 15:09:37 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.140.134.198 with SMTP id 189mr100947qhg.7.1424128177269; Mon, 16 Feb 2015 15:09:37 -0800 (PST) Received: by 10.140.92.245 with HTTP; Mon, 16 Feb 2015 15:09:37 -0800 (PST) In-Reply-To: <7772C602-E0F4-43E2-96EF-CCBD58B43596@gazagnaire.org> References: <7772C602-E0F4-43E2-96EF-CCBD58B43596@gazagnaire.org> Date: Tue, 17 Feb 2015 00:09:37 +0100 Message-ID: From: Richard Mortier To: Thomas Gazagnaire Cc: mirageos-devel Subject: Re: [MirageOS-devel] [ANN] release of dog 0.1.0 X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org [ resending as sent from incorrect mail address originally ] On 16 February 2015 at 21:55, Thomas Gazagnaire wrote: > I'd like to announce the first (very alpha) release of a new synchronisation tool: "dog" > > To install it: `opam install dog` > > The tool is built using Irmin and it demonstrate a simple distributed log server. Every client has a local (and partial) state of the system (a valid Git repository, whose active branch is the name of the client), and they synchronise explicitly with a server using the Irmin synchronisation protocol. The server listens for new clients and rebase every client branches into a sub-directory of the master branch. The server state is also stored in a Git repository, and it contains all the client history as well. So if you have: > cool! just given it a quick go and i suspect i'm missing something obvious... :) in ~/t/dog: ``` : mort@greyjay:dog$; dog listen Server started on port 8080. ``` in ~/t/dogc: ``` : mort@greyjay:dogc$; dog push -m "bark bark" http://localhost:8080 Unix.Unix_error(Unix.ECONNREFUSED, "connect", "") ``` how should i be trying to get a message logged? -- Richard Mortier richard.mortier@cl.cam.ac.uk _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Mon Feb 16 23:45:41 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 16 Feb 2015 23:45:41 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YNVMA-0002X3-DZ; Mon, 16 Feb 2015 23:45:38 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YNVM8-0002VY-Vk for mirageos-devel@lists.xenproject.org; Mon, 16 Feb 2015 23:45:37 +0000 Received: from [193.109.254.147] by server-10.bemta-14.messagelabs.com id D9/11-02750-02182E45; Mon, 16 Feb 2015 23:45:36 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-16.tower-27.messagelabs.com!1424130335!8421805!1 X-Originating-IP: [74.125.82.177] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27020 invoked from network); 16 Feb 2015 23:45:35 -0000 Received: from mail-we0-f177.google.com (HELO mail-we0-f177.google.com) (74.125.82.177) by server-16.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 16 Feb 2015 23:45:35 -0000 Received: by mail-we0-f177.google.com with SMTP id m14so26097554wev.8 for ; Mon, 16 Feb 2015 15:45:35 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=htEkz1d4UzZKZcu7I02G44EwNfzQsntf1fzY0Q0yb2w=; b=XpQi4dBGG4dqlubqG2aM6C0JM26WRt2YeWgvW3LXeOQ9NsfWnKx38YjELziglZSZKi MF/dZNDxPBFyM7RwDx+okKsrGwM6aYIrLqa3iOkUjsECUe9ItHIZGGXCge3BCAtPYz8m J3X1NuEC66Eul6IhzLshHJVYuaRw0rrET+6UM8e+Nk7AgtSaC8FuwiniRRtd82SpVqFL eOUKbC87bL+H6HPiw4It1J7rwuSLqX1BxCw5kMY/4TvBuFlRV8SIb4wnYvHVosttD2Bn auGTTFnK/AEtDqO6ojezx1YhYQRm14bL7fqvec3W4c6H4l/lg1FpLNPoqHq796p1xQLD l0vA== X-Received: by 10.180.20.177 with SMTP id o17mr41306691wie.66.1424130334938; Mon, 16 Feb 2015 15:45:34 -0800 (PST) Received: from [192.168.0.2] (cpc25-cmbg14-2-0-cust121.5-4.cable.virginm.net. [213.106.112.122]) by mx.google.com with ESMTPSA id ax10sm24899341wjc.26.2015.02.16.15.45.33 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 16 Feb 2015 15:45:33 -0800 (PST) Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) From: Thomas Gazagnaire In-Reply-To: Date: Mon, 16 Feb 2015 23:45:34 +0000 Message-Id: References: <7772C602-E0F4-43E2-96EF-CCBD58B43596@gazagnaire.org> To: Richard Mortier X-Mailer: Apple Mail (2.2070.6) Cc: mirageos-devel Subject: Re: [MirageOS-devel] [ANN] release of dog 0.1.0 X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org > just given it a quick go and i suspect i'm missing something obvious... :) > > in ~/t/dog: > > ``` > : mort@greyjay:dog$; dog listen > Server started on port 8080. > ``` Can you connect to the server direcly? ie. does http://localhost:8080 returns something useful in your browser (and http://localhost:8080/graph)? > in ~/t/dogc: > > ``` > : mort@greyjay:dogc$; dog push -m "bark bark" http://localhost:8080 > Unix.Unix_error(Unix.ECONNREFUSED, "connect", "") > ``` > > how should i be trying to get a message logged? > > > On 16 February 2015 at 21:55, Thomas Gazagnaire wrote: >> I'd like to announce the first (very alpha) release of a new synchronisation tool: "dog" >> >> To install it: `opam install dog` >> >> The tool is built using Irmin and it demonstrate a simple distributed log server. Every client has a local (and partial) state of the system (a valid Git repository, whose active branch is the name of the client), and they synchronise explicitly with a server using the Irmin synchronisation protocol. The server listens for new clients and rebase every client branches into a sub-directory of the master branch. The server state is also stored in a Git repository, and it contains all the client history as well. So if you have: >> >> Client A: >> branch A: >> - foo.txt >> >> and Client B: >> branch B: >> - foo.txt >> >> On the server you'll have: >> branch A: >> - foo.txt >> branch B: >> - foo.txt >> branch master: >> A/foo.txt >> B/foo.txt >> >> This is very simple but already quite useful. As usual, feedback appreciated on https://github.com/samoht/dog/issues. >> >> Best, >> Thomas >> _______________________________________________ >> MirageOS-devel mailing list >> MirageOS-devel@lists.xenproject.org >> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > > > > -- > Richard Mortier > mort@cantab.net _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Mon Feb 16 23:45:41 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 16 Feb 2015 23:45:41 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YNVMA-0002X3-DZ; Mon, 16 Feb 2015 23:45:38 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YNVM8-0002VY-Vk for mirageos-devel@lists.xenproject.org; Mon, 16 Feb 2015 23:45:37 +0000 Received: from [193.109.254.147] by server-10.bemta-14.messagelabs.com id D9/11-02750-02182E45; Mon, 16 Feb 2015 23:45:36 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-16.tower-27.messagelabs.com!1424130335!8421805!1 X-Originating-IP: [74.125.82.177] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27020 invoked from network); 16 Feb 2015 23:45:35 -0000 Received: from mail-we0-f177.google.com (HELO mail-we0-f177.google.com) (74.125.82.177) by server-16.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 16 Feb 2015 23:45:35 -0000 Received: by mail-we0-f177.google.com with SMTP id m14so26097554wev.8 for ; Mon, 16 Feb 2015 15:45:35 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=htEkz1d4UzZKZcu7I02G44EwNfzQsntf1fzY0Q0yb2w=; b=XpQi4dBGG4dqlubqG2aM6C0JM26WRt2YeWgvW3LXeOQ9NsfWnKx38YjELziglZSZKi MF/dZNDxPBFyM7RwDx+okKsrGwM6aYIrLqa3iOkUjsECUe9ItHIZGGXCge3BCAtPYz8m J3X1NuEC66Eul6IhzLshHJVYuaRw0rrET+6UM8e+Nk7AgtSaC8FuwiniRRtd82SpVqFL eOUKbC87bL+H6HPiw4It1J7rwuSLqX1BxCw5kMY/4TvBuFlRV8SIb4wnYvHVosttD2Bn auGTTFnK/AEtDqO6ojezx1YhYQRm14bL7fqvec3W4c6H4l/lg1FpLNPoqHq796p1xQLD l0vA== X-Received: by 10.180.20.177 with SMTP id o17mr41306691wie.66.1424130334938; Mon, 16 Feb 2015 15:45:34 -0800 (PST) Received: from [192.168.0.2] (cpc25-cmbg14-2-0-cust121.5-4.cable.virginm.net. [213.106.112.122]) by mx.google.com with ESMTPSA id ax10sm24899341wjc.26.2015.02.16.15.45.33 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 16 Feb 2015 15:45:33 -0800 (PST) Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) From: Thomas Gazagnaire In-Reply-To: Date: Mon, 16 Feb 2015 23:45:34 +0000 Message-Id: References: <7772C602-E0F4-43E2-96EF-CCBD58B43596@gazagnaire.org> To: Richard Mortier X-Mailer: Apple Mail (2.2070.6) Cc: mirageos-devel Subject: Re: [MirageOS-devel] [ANN] release of dog 0.1.0 X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org > just given it a quick go and i suspect i'm missing something obvious... :) > > in ~/t/dog: > > ``` > : mort@greyjay:dog$; dog listen > Server started on port 8080. > ``` Can you connect to the server direcly? ie. does http://localhost:8080 returns something useful in your browser (and http://localhost:8080/graph)? > in ~/t/dogc: > > ``` > : mort@greyjay:dogc$; dog push -m "bark bark" http://localhost:8080 > Unix.Unix_error(Unix.ECONNREFUSED, "connect", "") > ``` > > how should i be trying to get a message logged? > > > On 16 February 2015 at 21:55, Thomas Gazagnaire wrote: >> I'd like to announce the first (very alpha) release of a new synchronisation tool: "dog" >> >> To install it: `opam install dog` >> >> The tool is built using Irmin and it demonstrate a simple distributed log server. Every client has a local (and partial) state of the system (a valid Git repository, whose active branch is the name of the client), and they synchronise explicitly with a server using the Irmin synchronisation protocol. The server listens for new clients and rebase every client branches into a sub-directory of the master branch. The server state is also stored in a Git repository, and it contains all the client history as well. So if you have: >> >> Client A: >> branch A: >> - foo.txt >> >> and Client B: >> branch B: >> - foo.txt >> >> On the server you'll have: >> branch A: >> - foo.txt >> branch B: >> - foo.txt >> branch master: >> A/foo.txt >> B/foo.txt >> >> This is very simple but already quite useful. As usual, feedback appreciated on https://github.com/samoht/dog/issues. >> >> Best, >> Thomas >> _______________________________________________ >> MirageOS-devel mailing list >> MirageOS-devel@lists.xenproject.org >> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > > > > -- > Richard Mortier > mort@cantab.net _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Tue Feb 17 06:48:45 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 17 Feb 2015 06:48:45 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YNbxW-0000TS-Fn; Tue, 17 Feb 2015 06:48:38 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YNbxV-0000TN-JL for mirageos-devel@lists.xenproject.org; Tue, 17 Feb 2015 06:48:37 +0000 Received: from [85.158.143.35] by server-1.bemta-4.messagelabs.com id DB/27-03004-444E2E45; Tue, 17 Feb 2015 06:48:36 +0000 X-Env-Sender: richard.mortier@gmail.com X-Msg-Ref: server-12.tower-21.messagelabs.com!1424155715!12299390!1 X-Originating-IP: [209.85.216.178] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15988 invoked from network); 17 Feb 2015 06:48:36 -0000 Received: from mail-qc0-f178.google.com (HELO mail-qc0-f178.google.com) (209.85.216.178) by server-12.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 17 Feb 2015 06:48:36 -0000 Received: by mail-qc0-f178.google.com with SMTP id p6so27498458qcv.9 for ; Mon, 16 Feb 2015 22:48:35 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=WDQRKfIVE2TPAT8C19E/w/exOg6xK591K5s/gvGmoSg=; b=Hk7SF88RyBO7PhWnnLiHiNou3loU47b61LqnlYAAgd04gebAiC5v9u4dOEzU3CVpsm Z18iqaQKujRO2m1/ZMIesTpBZ7qwnpjNBl7Edq9UlPhwssnlRio2uidt8CbDqX+go4+i jx/jm12Mp9no7YxBv049YOISnPrXKVMrlqrxjgktCorxkEKu++pA/U6NQLNRMw5VLmGY DPMaP1I95QMns8twILHZeZnoOgHPCiUj1vOVwIXv0Te5uYa4FUUpqgdvpyVR3WR+eFu5 Z14+u3EIjh0bPT1upE2Eggyy8FFBf2//fB15UDEmKPqRG8MKB77baYDiIQ39x0fe3hd4 Slkg== X-Received: by 10.141.18.6 with SMTP id u6mr818065qhd.9.1424155715280; Mon, 16 Feb 2015 22:48:35 -0800 (PST) Received: from mail-qa0-f53.google.com (mail-qa0-f53.google.com. [209.85.216.53]) by mx.google.com with ESMTPSA id i46sm15362778qgd.35.2015.02.16.22.48.34 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 16 Feb 2015 22:48:35 -0800 (PST) Received: by mail-qa0-f53.google.com with SMTP id k15so25242924qaq.12 for ; Mon, 16 Feb 2015 22:48:34 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.140.39.84 with SMTP id u78mr610935qgu.63.1424155714351; Mon, 16 Feb 2015 22:48:34 -0800 (PST) Received: by 10.140.92.245 with HTTP; Mon, 16 Feb 2015 22:48:34 -0800 (PST) In-Reply-To: References: <7772C602-E0F4-43E2-96EF-CCBD58B43596@gazagnaire.org> Date: Tue, 17 Feb 2015 07:48:34 +0100 Message-ID: From: Richard Mortier To: Thomas Gazagnaire Cc: mirageos-devel Subject: Re: [MirageOS-devel] [ANN] release of dog 0.1.0 X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 17 February 2015 at 00:45, Thomas Gazagnaire wrote: > >> just given it a quick go and i suspect i'm missing something obvious... :) >> >> in ~/t/dog: >> >> ``` >> : mort@greyjay:dog$; dog listen >> Server started on port 8080. >> ``` > > Can you connect to the server direcly? ie. does http://localhost:8080 returns something useful in your browser (and http://localhost:8080/graph)? > yes, to both. in the first case: ``` {"result":["read","mem","iter","update","remove","watch","list","remove-rec","rename-tag","update-tag","merge-tag","switch","head","heads","update-head","merge-head","watch-head","watch-tags","clone","clone-force","export","import","lcas-tag","lcas-head","graph","contents","node","commit","tag","tree"]} ``` in the second, a graph with a green "master" node at the top, and then several blue nodes labelled "starting the server" beneath. -- Richard Mortier richard.mortier@cl.cam.ac.uk _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Tue Feb 17 06:48:45 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 17 Feb 2015 06:48:45 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YNbxW-0000TS-Fn; Tue, 17 Feb 2015 06:48:38 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YNbxV-0000TN-JL for mirageos-devel@lists.xenproject.org; Tue, 17 Feb 2015 06:48:37 +0000 Received: from [85.158.143.35] by server-1.bemta-4.messagelabs.com id DB/27-03004-444E2E45; Tue, 17 Feb 2015 06:48:36 +0000 X-Env-Sender: richard.mortier@gmail.com X-Msg-Ref: server-12.tower-21.messagelabs.com!1424155715!12299390!1 X-Originating-IP: [209.85.216.178] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15988 invoked from network); 17 Feb 2015 06:48:36 -0000 Received: from mail-qc0-f178.google.com (HELO mail-qc0-f178.google.com) (209.85.216.178) by server-12.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 17 Feb 2015 06:48:36 -0000 Received: by mail-qc0-f178.google.com with SMTP id p6so27498458qcv.9 for ; Mon, 16 Feb 2015 22:48:35 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=WDQRKfIVE2TPAT8C19E/w/exOg6xK591K5s/gvGmoSg=; b=Hk7SF88RyBO7PhWnnLiHiNou3loU47b61LqnlYAAgd04gebAiC5v9u4dOEzU3CVpsm Z18iqaQKujRO2m1/ZMIesTpBZ7qwnpjNBl7Edq9UlPhwssnlRio2uidt8CbDqX+go4+i jx/jm12Mp9no7YxBv049YOISnPrXKVMrlqrxjgktCorxkEKu++pA/U6NQLNRMw5VLmGY DPMaP1I95QMns8twILHZeZnoOgHPCiUj1vOVwIXv0Te5uYa4FUUpqgdvpyVR3WR+eFu5 Z14+u3EIjh0bPT1upE2Eggyy8FFBf2//fB15UDEmKPqRG8MKB77baYDiIQ39x0fe3hd4 Slkg== X-Received: by 10.141.18.6 with SMTP id u6mr818065qhd.9.1424155715280; Mon, 16 Feb 2015 22:48:35 -0800 (PST) Received: from mail-qa0-f53.google.com (mail-qa0-f53.google.com. [209.85.216.53]) by mx.google.com with ESMTPSA id i46sm15362778qgd.35.2015.02.16.22.48.34 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 16 Feb 2015 22:48:35 -0800 (PST) Received: by mail-qa0-f53.google.com with SMTP id k15so25242924qaq.12 for ; Mon, 16 Feb 2015 22:48:34 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.140.39.84 with SMTP id u78mr610935qgu.63.1424155714351; Mon, 16 Feb 2015 22:48:34 -0800 (PST) Received: by 10.140.92.245 with HTTP; Mon, 16 Feb 2015 22:48:34 -0800 (PST) In-Reply-To: References: <7772C602-E0F4-43E2-96EF-CCBD58B43596@gazagnaire.org> Date: Tue, 17 Feb 2015 07:48:34 +0100 Message-ID: From: Richard Mortier To: Thomas Gazagnaire Cc: mirageos-devel Subject: Re: [MirageOS-devel] [ANN] release of dog 0.1.0 X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 17 February 2015 at 00:45, Thomas Gazagnaire wrote: > >> just given it a quick go and i suspect i'm missing something obvious... :) >> >> in ~/t/dog: >> >> ``` >> : mort@greyjay:dog$; dog listen >> Server started on port 8080. >> ``` > > Can you connect to the server direcly? ie. does http://localhost:8080 returns something useful in your browser (and http://localhost:8080/graph)? > yes, to both. in the first case: ``` {"result":["read","mem","iter","update","remove","watch","list","remove-rec","rename-tag","update-tag","merge-tag","switch","head","heads","update-head","merge-head","watch-head","watch-tags","clone","clone-force","export","import","lcas-tag","lcas-head","graph","contents","node","commit","tag","tree"]} ``` in the second, a graph with a green "master" node at the top, and then several blue nodes labelled "starting the server" beneath. -- Richard Mortier richard.mortier@cl.cam.ac.uk _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Tue Feb 17 06:58:46 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 17 Feb 2015 06:58:46 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YNc7I-0001CX-Lp; Tue, 17 Feb 2015 06:58:44 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YNc7H-0001CS-JD for mirageos-devel@lists.xenproject.org; Tue, 17 Feb 2015 06:58:43 +0000 Received: from [85.158.137.68] by server-5.bemta-3.messagelabs.com id B2/EA-03219-2A6E2E45; Tue, 17 Feb 2015 06:58:42 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-11.tower-31.messagelabs.com!1424156321!12134413!1 X-Originating-IP: [5.153.225.51] X-SpamReason: No, hits=0.2 required=7.0 tests=RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 19421 invoked from network); 17 Feb 2015 06:58:42 -0000 Received: from bark.recoil.org (HELO bark.recoil.org) (5.153.225.51) by server-11.tower-31.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 17 Feb 2015 06:58:42 -0000 Received: from [192.168.1.39] (cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net [86.30.244.239]); by bark.recoil.org (OpenSMTPD) with ESMTPSA id aa4bf50e; TLS version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO; Tue, 17 Feb 2015 06:58:41 +0000 (GMT) Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) From: Anil Madhavapeddy In-Reply-To: Date: Tue, 17 Feb 2015 06:58:40 +0000 Message-Id: <0D5A2ABF-A68D-4336-8D7C-58AAAF6E482B@recoil.org> References: <7772C602-E0F4-43E2-96EF-CCBD58B43596@gazagnaire.org> To: Thomas Gazagnaire X-Mailer: Apple Mail (2.2070.6) Cc: Richard Mortier , mirageos-devel Subject: Re: [MirageOS-devel] [ANN] release of dog 0.1.0 X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 16 Feb 2015, at 23:45, Thomas Gazagnaire wrote: > > >> just given it a quick go and i suspect i'm missing something obvious... :) >> >> in ~/t/dog: >> >> ``` >> : mort@greyjay:dog$; dog listen >> Server started on port 8080. >> ``` > > Can you connect to the server direcly? ie. does http://localhost:8080 returns something useful in your browser (and http://localhost:8080/graph)? That particular set of commands works for me, so I suspect this is something to do with Conduit binding to an unexpected interface. If it does turn out to be this, could you leave a comment on: https://github.com/mirage/ocaml-conduit/issues/42 -anil > > >> in ~/t/dogc: >> >> ``` >> : mort@greyjay:dogc$; dog push -m "bark bark" http://localhost:8080 >> Unix.Unix_error(Unix.ECONNREFUSED, "connect", "") >> ``` >> >> how should i be trying to get a message logged? >> >> >> On 16 February 2015 at 21:55, Thomas Gazagnaire wrote: >>> I'd like to announce the first (very alpha) release of a new synchronisation tool: "dog" >>> >>> To install it: `opam install dog` >>> >>> The tool is built using Irmin and it demonstrate a simple distributed log server. Every client has a local (and partial) state of the system (a valid Git repository, whose active branch is the name of the client), and they synchronise explicitly with a server using the Irmin synchronisation protocol. The server listens for new clients and rebase every client branches into a sub-directory of the master branch. The server state is also stored in a Git repository, and it contains all the client history as well. So if you have: >>> >>> Client A: >>> branch A: >>> - foo.txt >>> >>> and Client B: >>> branch B: >>> - foo.txt >>> >>> On the server you'll have: >>> branch A: >>> - foo.txt >>> branch B: >>> - foo.txt >>> branch master: >>> A/foo.txt >>> B/foo.txt >>> >>> This is very simple but already quite useful. As usual, feedback appreciated on https://github.com/samoht/dog/issues. >>> >>> Best, >>> Thomas >>> _______________________________________________ >>> MirageOS-devel mailing list >>> MirageOS-devel@lists.xenproject.org >>> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel >> >> >> >> -- >> Richard Mortier >> mort@cantab.net > > > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Tue Feb 17 06:58:46 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 17 Feb 2015 06:58:46 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YNc7I-0001CX-Lp; Tue, 17 Feb 2015 06:58:44 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YNc7H-0001CS-JD for mirageos-devel@lists.xenproject.org; Tue, 17 Feb 2015 06:58:43 +0000 Received: from [85.158.137.68] by server-5.bemta-3.messagelabs.com id B2/EA-03219-2A6E2E45; Tue, 17 Feb 2015 06:58:42 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-11.tower-31.messagelabs.com!1424156321!12134413!1 X-Originating-IP: [5.153.225.51] X-SpamReason: No, hits=0.2 required=7.0 tests=RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 19421 invoked from network); 17 Feb 2015 06:58:42 -0000 Received: from bark.recoil.org (HELO bark.recoil.org) (5.153.225.51) by server-11.tower-31.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 17 Feb 2015 06:58:42 -0000 Received: from [192.168.1.39] (cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net [86.30.244.239]); by bark.recoil.org (OpenSMTPD) with ESMTPSA id aa4bf50e; TLS version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO; Tue, 17 Feb 2015 06:58:41 +0000 (GMT) Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) From: Anil Madhavapeddy In-Reply-To: Date: Tue, 17 Feb 2015 06:58:40 +0000 Message-Id: <0D5A2ABF-A68D-4336-8D7C-58AAAF6E482B@recoil.org> References: <7772C602-E0F4-43E2-96EF-CCBD58B43596@gazagnaire.org> To: Thomas Gazagnaire X-Mailer: Apple Mail (2.2070.6) Cc: Richard Mortier , mirageos-devel Subject: Re: [MirageOS-devel] [ANN] release of dog 0.1.0 X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 16 Feb 2015, at 23:45, Thomas Gazagnaire wrote: > > >> just given it a quick go and i suspect i'm missing something obvious... :) >> >> in ~/t/dog: >> >> ``` >> : mort@greyjay:dog$; dog listen >> Server started on port 8080. >> ``` > > Can you connect to the server direcly? ie. does http://localhost:8080 returns something useful in your browser (and http://localhost:8080/graph)? That particular set of commands works for me, so I suspect this is something to do with Conduit binding to an unexpected interface. If it does turn out to be this, could you leave a comment on: https://github.com/mirage/ocaml-conduit/issues/42 -anil > > >> in ~/t/dogc: >> >> ``` >> : mort@greyjay:dogc$; dog push -m "bark bark" http://localhost:8080 >> Unix.Unix_error(Unix.ECONNREFUSED, "connect", "") >> ``` >> >> how should i be trying to get a message logged? >> >> >> On 16 February 2015 at 21:55, Thomas Gazagnaire wrote: >>> I'd like to announce the first (very alpha) release of a new synchronisation tool: "dog" >>> >>> To install it: `opam install dog` >>> >>> The tool is built using Irmin and it demonstrate a simple distributed log server. Every client has a local (and partial) state of the system (a valid Git repository, whose active branch is the name of the client), and they synchronise explicitly with a server using the Irmin synchronisation protocol. The server listens for new clients and rebase every client branches into a sub-directory of the master branch. The server state is also stored in a Git repository, and it contains all the client history as well. So if you have: >>> >>> Client A: >>> branch A: >>> - foo.txt >>> >>> and Client B: >>> branch B: >>> - foo.txt >>> >>> On the server you'll have: >>> branch A: >>> - foo.txt >>> branch B: >>> - foo.txt >>> branch master: >>> A/foo.txt >>> B/foo.txt >>> >>> This is very simple but already quite useful. As usual, feedback appreciated on https://github.com/samoht/dog/issues. >>> >>> Best, >>> Thomas >>> _______________________________________________ >>> MirageOS-devel mailing list >>> MirageOS-devel@lists.xenproject.org >>> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel >> >> >> >> -- >> Richard Mortier >> mort@cantab.net > > > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Tue Feb 17 10:26:54 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 17 Feb 2015 10:26:54 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YNfMg-00082V-UB; Tue, 17 Feb 2015 10:26:50 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YNfMf-00082P-Lm for mirageos-devel@lists.xenproject.org; Tue, 17 Feb 2015 10:26:49 +0000 Received: from [85.158.137.68] by server-3.bemta-3.messagelabs.com id CC/99-02997-86713E45; Tue, 17 Feb 2015 10:26:48 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-15.tower-31.messagelabs.com!1424168808!12046272!1 X-Originating-IP: [5.153.225.51] X-SpamReason: No, hits=0.2 required=7.0 tests=RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28989 invoked from network); 17 Feb 2015 10:26:48 -0000 Received: from bark.recoil.org (HELO bark.recoil.org) (5.153.225.51) by server-15.tower-31.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 17 Feb 2015 10:26:48 -0000 Received: from [192.168.1.39] (cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net [86.30.244.239]); by bark.recoil.org (OpenSMTPD) with ESMTPSA id 2a11679f; TLS version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO; Tue, 17 Feb 2015 10:26:47 +0000 (GMT) Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) From: Anil Madhavapeddy In-Reply-To: <54E1B5EA.9010301@inria.fr> Date: Tue, 17 Feb 2015 10:26:47 +0000 Message-Id: <65617E2B-8916-4779-A57F-7F5327FC7764@recoil.org> References: <54E1B5EA.9010301@inria.fr> To: Francois Berenger X-Mailer: Apple Mail (2.2070.6) Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Would it be be useful to add DAFT in the pioneer projects of mirage? X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 16 Feb 2015, at 09:18, Francois Berenger wrote: > > Hello, > > There is some code and a small specification but nothing working yet: > > https://github.com/UnixJunkie/daft > > If it is useful, I can prepare and submit a description. Thanks for this -- before putting this one up, I'd suggest a pioneer project to add support for ZeroMQ. This could be done via mfp's implementation in OCaml, but is a prerequisite for DAFT. -anil _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Tue Feb 17 10:26:54 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 17 Feb 2015 10:26:54 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YNfMg-00082V-UB; Tue, 17 Feb 2015 10:26:50 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YNfMf-00082P-Lm for mirageos-devel@lists.xenproject.org; Tue, 17 Feb 2015 10:26:49 +0000 Received: from [85.158.137.68] by server-3.bemta-3.messagelabs.com id CC/99-02997-86713E45; Tue, 17 Feb 2015 10:26:48 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-15.tower-31.messagelabs.com!1424168808!12046272!1 X-Originating-IP: [5.153.225.51] X-SpamReason: No, hits=0.2 required=7.0 tests=RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28989 invoked from network); 17 Feb 2015 10:26:48 -0000 Received: from bark.recoil.org (HELO bark.recoil.org) (5.153.225.51) by server-15.tower-31.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 17 Feb 2015 10:26:48 -0000 Received: from [192.168.1.39] (cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net [86.30.244.239]); by bark.recoil.org (OpenSMTPD) with ESMTPSA id 2a11679f; TLS version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO; Tue, 17 Feb 2015 10:26:47 +0000 (GMT) Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) From: Anil Madhavapeddy In-Reply-To: <54E1B5EA.9010301@inria.fr> Date: Tue, 17 Feb 2015 10:26:47 +0000 Message-Id: <65617E2B-8916-4779-A57F-7F5327FC7764@recoil.org> References: <54E1B5EA.9010301@inria.fr> To: Francois Berenger X-Mailer: Apple Mail (2.2070.6) Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Would it be be useful to add DAFT in the pioneer projects of mirage? X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 16 Feb 2015, at 09:18, Francois Berenger wrote: > > Hello, > > There is some code and a small specification but nothing working yet: > > https://github.com/UnixJunkie/daft > > If it is useful, I can prepare and submit a description. Thanks for this -- before putting this one up, I'd suggest a pioneer project to add support for ZeroMQ. This could be done via mfp's implementation in OCaml, but is a prerequisite for DAFT. -anil _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Tue Feb 17 10:38:47 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 17 Feb 2015 10:38:47 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YNfYF-0000XD-73; Tue, 17 Feb 2015 10:38:47 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YNfYE-0000X1-0A for mirageos-devel@lists.xenproject.org; Tue, 17 Feb 2015 10:38:46 +0000 Received: from [85.158.139.211] by server-10.bemta-5.messagelabs.com id E4/A5-02756-53A13E45; Tue, 17 Feb 2015 10:38:45 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-5.tower-206.messagelabs.com!1424169524!12315538!1 X-Originating-IP: [209.85.212.178] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27831 invoked from network); 17 Feb 2015 10:38:44 -0000 Received: from mail-wi0-f178.google.com (HELO mail-wi0-f178.google.com) (209.85.212.178) by server-5.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 17 Feb 2015 10:38:44 -0000 Received: by mail-wi0-f178.google.com with SMTP id em10so31968901wid.5 for ; Tue, 17 Feb 2015 02:38:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=zMMvdOar8j3iWLYam6h5DqgEkXCrPcJ7sdfodjLdedQ=; b=Q49HfuD/gJDKGyzksEJaYA3YALxAEbs77s/+V0uXpUPM0BQ4aTnsvNAfSN07gTjea9 XhItc+Y7LlNTVj/eV50aDOG+KU5NS1kfTVBViVX1e2QYFzqosazXIUMPOPTVDJEUVC+O N1XFYMubaK8R3RYBRZ+Me4UpqPxJeFYoFglkDIE6kF1wAswZkcaPt9nwZLS18RpK1MSZ X7fOhk/d7KtYKWEGmVkQQxtu2PN2o0p2QJ/vFq7aXxs/zLQIAH15800hqFsLzZxGWa1a rSNsGmGmfP/RUTXAnO1oov2aztL+HkOQ1UruYBOVKzR0xMw2eMJ4bNd6ZCjAZgSIdT5E uJzg== X-Received: by 10.194.20.67 with SMTP id l3mr58994416wje.94.1424169524236; Tue, 17 Feb 2015 02:38:44 -0800 (PST) Received: from [192.168.0.2] (cpc25-cmbg14-2-0-cust121.5-4.cable.virginm.net. [213.106.112.122]) by mx.google.com with ESMTPSA id fo17sm26753094wjc.19.2015.02.17.02.38.42 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 17 Feb 2015 02:38:43 -0800 (PST) Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) From: Thomas Gazagnaire In-Reply-To: Date: Tue, 17 Feb 2015 10:38:41 +0000 Message-Id: <47D39FA3-050E-46E6-89D2-4253484E24A8@gazagnaire.org> References: <8CEDB416-6238-4888-BA4B-B7305FDDE2D9@gazagnaire.org> <9349273A-0BB4-40C4-BF06-4307085AA90C@recoil.org> To: Anil Madhavapeddy X-Mailer: Apple Mail (2.2070.6) Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Irmin API newbie questions X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org >> One layer that would be very useful over this commit graph is some notion of >> diffs. I'd quite like to be able to describe a data structure in terms of >> patches, since that's quite often the reason why I'm traversing the history >> in the first place. If I just want to go back in time, I can stash relevant >> points in a tag and never need to walk the commit history. > > Good idea, I'll try to see if I can add a diff on the graph edges (via a user-provided function to compute diffs) I've added a simple `Irmin.history` function to get the graph of commits: http://mirage.github.io/irmin/Irmin.html#VALhistory There is no diff on the edges yet (see https://github.com/mirage/irmin/issues/151 which keeps track of that). Thomas _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Tue Feb 17 10:38:47 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 17 Feb 2015 10:38:47 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YNfYF-0000XD-73; Tue, 17 Feb 2015 10:38:47 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YNfYE-0000X1-0A for mirageos-devel@lists.xenproject.org; Tue, 17 Feb 2015 10:38:46 +0000 Received: from [85.158.139.211] by server-10.bemta-5.messagelabs.com id E4/A5-02756-53A13E45; Tue, 17 Feb 2015 10:38:45 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-5.tower-206.messagelabs.com!1424169524!12315538!1 X-Originating-IP: [209.85.212.178] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27831 invoked from network); 17 Feb 2015 10:38:44 -0000 Received: from mail-wi0-f178.google.com (HELO mail-wi0-f178.google.com) (209.85.212.178) by server-5.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 17 Feb 2015 10:38:44 -0000 Received: by mail-wi0-f178.google.com with SMTP id em10so31968901wid.5 for ; Tue, 17 Feb 2015 02:38:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=zMMvdOar8j3iWLYam6h5DqgEkXCrPcJ7sdfodjLdedQ=; b=Q49HfuD/gJDKGyzksEJaYA3YALxAEbs77s/+V0uXpUPM0BQ4aTnsvNAfSN07gTjea9 XhItc+Y7LlNTVj/eV50aDOG+KU5NS1kfTVBViVX1e2QYFzqosazXIUMPOPTVDJEUVC+O N1XFYMubaK8R3RYBRZ+Me4UpqPxJeFYoFglkDIE6kF1wAswZkcaPt9nwZLS18RpK1MSZ X7fOhk/d7KtYKWEGmVkQQxtu2PN2o0p2QJ/vFq7aXxs/zLQIAH15800hqFsLzZxGWa1a rSNsGmGmfP/RUTXAnO1oov2aztL+HkOQ1UruYBOVKzR0xMw2eMJ4bNd6ZCjAZgSIdT5E uJzg== X-Received: by 10.194.20.67 with SMTP id l3mr58994416wje.94.1424169524236; Tue, 17 Feb 2015 02:38:44 -0800 (PST) Received: from [192.168.0.2] (cpc25-cmbg14-2-0-cust121.5-4.cable.virginm.net. [213.106.112.122]) by mx.google.com with ESMTPSA id fo17sm26753094wjc.19.2015.02.17.02.38.42 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 17 Feb 2015 02:38:43 -0800 (PST) Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) From: Thomas Gazagnaire In-Reply-To: Date: Tue, 17 Feb 2015 10:38:41 +0000 Message-Id: <47D39FA3-050E-46E6-89D2-4253484E24A8@gazagnaire.org> References: <8CEDB416-6238-4888-BA4B-B7305FDDE2D9@gazagnaire.org> <9349273A-0BB4-40C4-BF06-4307085AA90C@recoil.org> To: Anil Madhavapeddy X-Mailer: Apple Mail (2.2070.6) Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Irmin API newbie questions X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org >> One layer that would be very useful over this commit graph is some notion of >> diffs. I'd quite like to be able to describe a data structure in terms of >> patches, since that's quite often the reason why I'm traversing the history >> in the first place. If I just want to go back in time, I can stash relevant >> points in a tag and never need to walk the commit history. > > Good idea, I'll try to see if I can add a diff on the graph edges (via a user-provided function to compute diffs) I've added a simple `Irmin.history` function to get the graph of commits: http://mirage.github.io/irmin/Irmin.html#VALhistory There is no diff on the edges yet (see https://github.com/mirage/irmin/issues/151 which keeps track of that). Thomas _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Tue Feb 17 10:55:02 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 17 Feb 2015 10:55:02 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YNfnx-0002J7-3j; Tue, 17 Feb 2015 10:55:01 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YNfnv-0002J2-Hu for mirageos-devel@lists.xenproject.org; Tue, 17 Feb 2015 10:54:59 +0000 Received: from [85.158.139.211] by server-9.bemta-5.messagelabs.com id B7/AD-02991-20E13E45; Tue, 17 Feb 2015 10:54:58 +0000 X-Env-Sender: daniel.buenzli@erratique.ch X-Msg-Ref: server-3.tower-206.messagelabs.com!1424170496!4757044!1 X-Originating-IP: [74.55.86.74] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNzQuNTUuODYuNzQgPT4gMzA4NTYz\n X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23918 invoked from network); 17 Feb 2015 10:54:56 -0000 Received: from mail6.webfaction.com (HELO smtp.webfaction.com) (74.55.86.74) by server-3.tower-206.messagelabs.com with SMTP; 17 Feb 2015 10:54:56 -0000 Received: from [172.20.10.2] (243.226.197.178.dynamic.wless.zhbmb00p-cgnat.res.cust.swisscom.ch [178.197.226.243]) by smtp.webfaction.com (Postfix) with ESMTP id A2F8A20D1B84; Tue, 17 Feb 2015 10:54:54 +0000 (UTC) Date: Tue, 17 Feb 2015 11:54:50 +0100 From: =?utf-8?Q?Daniel_B=C3=BCnzli?= To: Anil Madhavapeddy Message-ID: In-Reply-To: <65617E2B-8916-4779-A57F-7F5327FC7764@recoil.org> References: <54E1B5EA.9010301@inria.fr> <65617E2B-8916-4779-A57F-7F5327FC7764@recoil.org> X-Mailer: sparrow 1.6.4 (build 1178) MIME-Version: 1.0 Content-Disposition: inline Cc: Francois Berenger , mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Would it be be useful to add DAFT in the pioneer projects of mirage? X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org TGUgbWFyZGksIDE3IGbDqXZyaWVyIDIwMTUgw6AgMTE6MjYsIEFuaWwgTWFkaGF2YXBlZGR5IGEg w6ljcml0IDoKPiBUaGFua3MgZm9yIHRoaXMgLS0gYmVmb3JlIHB1dHRpbmcgdGhpcyBvbmUgdXAs IEknZCBzdWdnZXN0IGEgcGlvbmVlciBwcm9qZWN0IHRvIGFkZCBzdXBwb3J0IGZvciBaZXJvTVEu CgpUaG91Z2ggbWF5YmUgbW9yZSBleHBlcmltZW50YWwsIG5hbm9tc2cgKGh0dHA6Ly9uYW5vbXNn Lm9yZy8pIGNvdWxkIGJlIGFuIGFsdGVybmF0aXZlLiBUaGUgaW50ZXJlc3RpbmcgdGhpbmcgYmVp bmcgdGhhdCB0aGVzZSBhcmUgZGVzaWducyB0aGF0IGxlYXJuZWQgZnJvbSBaZXJvTVEgYW5kIHRo ZXkgaGF2ZSBpbmZvcm1hdGlvbmFsIFJGQ3MgZm9yIHRoZWlyICJzY2FsYWJpbGl0eSIgcHJvdG9j b2xzOgoKaHR0cHM6Ly9naXRodWIuY29tL25hbm9tc2cvbmFub21zZy90cmVlL21hc3Rlci9yZmMK ClRoZXJlIGlzIGF0IGxlYXN0IGFub3RoZXIgaW5kZXBlbmRlbnQgaW1wbGVtZW50YXRpb24gb2Yg dGhlIHByb3RvY29scyBpbiBwdXJlIEdvIChodHRwczovL2dpdGh1Yi5jb20vZ2RhbW9yZS9tYW5n b3MpCgpCZXN0LAoKRGFuaWVsCgoKCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fCk1pcmFnZU9TLWRldmVsIG1haWxpbmcgbGlzdApNaXJhZ2VPUy1kZXZlbEBs aXN0cy54ZW5wcm9qZWN0Lm9yZwpodHRwOi8vbGlzdHMueGVucHJvamVjdC5vcmcvY2dpLWJpbi9t YWlsbWFuL2xpc3RpbmZvL21pcmFnZW9zLWRldmVsCg== From mirageos-devel-bounces@lists.xenproject.org Tue Feb 17 10:55:02 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 17 Feb 2015 10:55:02 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YNfnx-0002J7-3j; Tue, 17 Feb 2015 10:55:01 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YNfnv-0002J2-Hu for mirageos-devel@lists.xenproject.org; Tue, 17 Feb 2015 10:54:59 +0000 Received: from [85.158.139.211] by server-9.bemta-5.messagelabs.com id B7/AD-02991-20E13E45; Tue, 17 Feb 2015 10:54:58 +0000 X-Env-Sender: daniel.buenzli@erratique.ch X-Msg-Ref: server-3.tower-206.messagelabs.com!1424170496!4757044!1 X-Originating-IP: [74.55.86.74] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNzQuNTUuODYuNzQgPT4gMzA4NTYz\n X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23918 invoked from network); 17 Feb 2015 10:54:56 -0000 Received: from mail6.webfaction.com (HELO smtp.webfaction.com) (74.55.86.74) by server-3.tower-206.messagelabs.com with SMTP; 17 Feb 2015 10:54:56 -0000 Received: from [172.20.10.2] (243.226.197.178.dynamic.wless.zhbmb00p-cgnat.res.cust.swisscom.ch [178.197.226.243]) by smtp.webfaction.com (Postfix) with ESMTP id A2F8A20D1B84; Tue, 17 Feb 2015 10:54:54 +0000 (UTC) Date: Tue, 17 Feb 2015 11:54:50 +0100 From: =?utf-8?Q?Daniel_B=C3=BCnzli?= To: Anil Madhavapeddy Message-ID: In-Reply-To: <65617E2B-8916-4779-A57F-7F5327FC7764@recoil.org> References: <54E1B5EA.9010301@inria.fr> <65617E2B-8916-4779-A57F-7F5327FC7764@recoil.org> X-Mailer: sparrow 1.6.4 (build 1178) MIME-Version: 1.0 Content-Disposition: inline Cc: Francois Berenger , mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Would it be be useful to add DAFT in the pioneer projects of mirage? X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org TGUgbWFyZGksIDE3IGbDqXZyaWVyIDIwMTUgw6AgMTE6MjYsIEFuaWwgTWFkaGF2YXBlZGR5IGEg w6ljcml0IDoKPiBUaGFua3MgZm9yIHRoaXMgLS0gYmVmb3JlIHB1dHRpbmcgdGhpcyBvbmUgdXAs IEknZCBzdWdnZXN0IGEgcGlvbmVlciBwcm9qZWN0IHRvIGFkZCBzdXBwb3J0IGZvciBaZXJvTVEu CgpUaG91Z2ggbWF5YmUgbW9yZSBleHBlcmltZW50YWwsIG5hbm9tc2cgKGh0dHA6Ly9uYW5vbXNn Lm9yZy8pIGNvdWxkIGJlIGFuIGFsdGVybmF0aXZlLiBUaGUgaW50ZXJlc3RpbmcgdGhpbmcgYmVp bmcgdGhhdCB0aGVzZSBhcmUgZGVzaWducyB0aGF0IGxlYXJuZWQgZnJvbSBaZXJvTVEgYW5kIHRo ZXkgaGF2ZSBpbmZvcm1hdGlvbmFsIFJGQ3MgZm9yIHRoZWlyICJzY2FsYWJpbGl0eSIgcHJvdG9j b2xzOgoKaHR0cHM6Ly9naXRodWIuY29tL25hbm9tc2cvbmFub21zZy90cmVlL21hc3Rlci9yZmMK ClRoZXJlIGlzIGF0IGxlYXN0IGFub3RoZXIgaW5kZXBlbmRlbnQgaW1wbGVtZW50YXRpb24gb2Yg dGhlIHByb3RvY29scyBpbiBwdXJlIEdvIChodHRwczovL2dpdGh1Yi5jb20vZ2RhbW9yZS9tYW5n b3MpCgpCZXN0LAoKRGFuaWVsCgoKCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fCk1pcmFnZU9TLWRldmVsIG1haWxpbmcgbGlzdApNaXJhZ2VPUy1kZXZlbEBs aXN0cy54ZW5wcm9qZWN0Lm9yZwpodHRwOi8vbGlzdHMueGVucHJvamVjdC5vcmcvY2dpLWJpbi9t YWlsbWFuL2xpc3RpbmZvL21pcmFnZW9zLWRldmVsCg== From mirageos-devel-bounces@lists.xenproject.org Tue Feb 17 10:55:32 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 17 Feb 2015 10:55:32 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YNfoS-0002Kd-7m; Tue, 17 Feb 2015 10:55:32 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YNfoR-0002KX-Ps for mirageos-devel@lists.xenproject.org; Tue, 17 Feb 2015 10:55:31 +0000 Received: from [85.158.139.211] by server-13.bemta-5.messagelabs.com id 3F/D6-02801-32E13E45; Tue, 17 Feb 2015 10:55:31 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-3.tower-206.messagelabs.com!1424170530!4757181!1 X-Originating-IP: [74.125.82.45] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28542 invoked from network); 17 Feb 2015 10:55:30 -0000 Received: from mail-wg0-f45.google.com (HELO mail-wg0-f45.google.com) (74.125.82.45) by server-3.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 17 Feb 2015 10:55:30 -0000 Received: by mail-wg0-f45.google.com with SMTP id k14so31421599wgh.4 for ; Tue, 17 Feb 2015 02:55:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=0N9+lCl8Agt2+Oi6pDxlhTe3SlELPHzllamAkdEP52Q=; b=eYvWonw+RR/L/42GSvhdm8Xm4VLSDT4l66arm3+GN+ZSbA1exembYWz2gCNYK5oT9W mQvZ8X0ItpUJkpaZb+09p9I5n+pW63fqwNmtlGgSuNft2b87RRyqEv8k5byc5NSzGKSa i6evs1ogBvgYGF/U5DD+y5v39A8spQ++WLcn96zOLfZMDKULVbOD6p+VTKrewDrpV/Jq jSwXmqEU8MkV85cAkxbait0//6XmlieX2B0jzRKqQQYTQ6tQdpB7d01DO6OmBFjOfTbm WdsHRofd9+GvXCa771YeWbXAhehGZuL7p+gXKKTiuMXPbqjVR1IkeslnHiX7VPPewgCQ vPbA== X-Received: by 10.194.6.70 with SMTP id y6mr58857498wjy.97.1424170529858; Tue, 17 Feb 2015 02:55:29 -0800 (PST) Received: from [192.168.0.2] (cpc25-cmbg14-2-0-cust121.5-4.cable.virginm.net. [213.106.112.122]) by mx.google.com with ESMTPSA id ha5sm7332481wib.1.2015.02.17.02.55.28 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 17 Feb 2015 02:55:29 -0800 (PST) Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) From: Thomas Gazagnaire In-Reply-To: <0D5A2ABF-A68D-4336-8D7C-58AAAF6E482B@recoil.org> Date: Tue, 17 Feb 2015 10:55:27 +0000 Message-Id: <8FE14DB8-DF5D-4F29-BC49-63CE12B6D5EB@gazagnaire.org> References: <7772C602-E0F4-43E2-96EF-CCBD58B43596@gazagnaire.org> <0D5A2ABF-A68D-4336-8D7C-58AAAF6E482B@recoil.org> To: Anil Madhavapeddy X-Mailer: Apple Mail (2.2070.6) Cc: Richard Mortier , mirageos-devel Subject: Re: [MirageOS-devel] [ANN] release of dog 0.1.0 X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org >>> just given it a quick go and i suspect i'm missing something obvious... :) >>> >>> in ~/t/dog: >>> >>> ``` >>> : mort@greyjay:dog$; dog listen >>> Server started on port 8080. >>> ``` >> >> Can you connect to the server direcly? ie. does http://localhost:8080 returns something useful in your browser (and http://localhost:8080/graph)? > > That particular set of commands works for me, so I suspect this is something to do with Conduit binding to an unexpected interface. If it does turn out to be this, could you leave a comment on: > > https://github.com/mirage/ocaml-conduit/issues/42 Any more instructions on how to debug that? What kind of trace would be helpful to fix that issue? Thomas > > -anil > > > >> >> >>> in ~/t/dogc: >>> >>> ``` >>> : mort@greyjay:dogc$; dog push -m "bark bark" http://localhost:8080 >>> Unix.Unix_error(Unix.ECONNREFUSED, "connect", "") >>> ``` >>> >>> how should i be trying to get a message logged? >>> >>> >>> On 16 February 2015 at 21:55, Thomas Gazagnaire wrote: >>>> I'd like to announce the first (very alpha) release of a new synchronisation tool: "dog" >>>> >>>> To install it: `opam install dog` >>>> >>>> The tool is built using Irmin and it demonstrate a simple distributed log server. Every client has a local (and partial) state of the system (a valid Git repository, whose active branch is the name of the client), and they synchronise explicitly with a server using the Irmin synchronisation protocol. The server listens for new clients and rebase every client branches into a sub-directory of the master branch. The server state is also stored in a Git repository, and it contains all the client history as well. So if you have: >>>> >>>> Client A: >>>> branch A: >>>> - foo.txt >>>> >>>> and Client B: >>>> branch B: >>>> - foo.txt >>>> >>>> On the server you'll have: >>>> branch A: >>>> - foo.txt >>>> branch B: >>>> - foo.txt >>>> branch master: >>>> A/foo.txt >>>> B/foo.txt >>>> >>>> This is very simple but already quite useful. As usual, feedback appreciated on https://github.com/samoht/dog/issues. >>>> >>>> Best, >>>> Thomas >>>> _______________________________________________ >>>> MirageOS-devel mailing list >>>> MirageOS-devel@lists.xenproject.org >>>> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel >>> >>> >>> >>> -- >>> Richard Mortier >>> mort@cantab.net >> >> >> _______________________________________________ >> MirageOS-devel mailing list >> MirageOS-devel@lists.xenproject.org >> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel >> > _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Tue Feb 17 10:55:32 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 17 Feb 2015 10:55:32 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YNfoS-0002Kd-7m; Tue, 17 Feb 2015 10:55:32 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YNfoR-0002KX-Ps for mirageos-devel@lists.xenproject.org; Tue, 17 Feb 2015 10:55:31 +0000 Received: from [85.158.139.211] by server-13.bemta-5.messagelabs.com id 3F/D6-02801-32E13E45; Tue, 17 Feb 2015 10:55:31 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-3.tower-206.messagelabs.com!1424170530!4757181!1 X-Originating-IP: [74.125.82.45] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28542 invoked from network); 17 Feb 2015 10:55:30 -0000 Received: from mail-wg0-f45.google.com (HELO mail-wg0-f45.google.com) (74.125.82.45) by server-3.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 17 Feb 2015 10:55:30 -0000 Received: by mail-wg0-f45.google.com with SMTP id k14so31421599wgh.4 for ; Tue, 17 Feb 2015 02:55:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=0N9+lCl8Agt2+Oi6pDxlhTe3SlELPHzllamAkdEP52Q=; b=eYvWonw+RR/L/42GSvhdm8Xm4VLSDT4l66arm3+GN+ZSbA1exembYWz2gCNYK5oT9W mQvZ8X0ItpUJkpaZb+09p9I5n+pW63fqwNmtlGgSuNft2b87RRyqEv8k5byc5NSzGKSa i6evs1ogBvgYGF/U5DD+y5v39A8spQ++WLcn96zOLfZMDKULVbOD6p+VTKrewDrpV/Jq jSwXmqEU8MkV85cAkxbait0//6XmlieX2B0jzRKqQQYTQ6tQdpB7d01DO6OmBFjOfTbm WdsHRofd9+GvXCa771YeWbXAhehGZuL7p+gXKKTiuMXPbqjVR1IkeslnHiX7VPPewgCQ vPbA== X-Received: by 10.194.6.70 with SMTP id y6mr58857498wjy.97.1424170529858; Tue, 17 Feb 2015 02:55:29 -0800 (PST) Received: from [192.168.0.2] (cpc25-cmbg14-2-0-cust121.5-4.cable.virginm.net. [213.106.112.122]) by mx.google.com with ESMTPSA id ha5sm7332481wib.1.2015.02.17.02.55.28 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 17 Feb 2015 02:55:29 -0800 (PST) Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) From: Thomas Gazagnaire In-Reply-To: <0D5A2ABF-A68D-4336-8D7C-58AAAF6E482B@recoil.org> Date: Tue, 17 Feb 2015 10:55:27 +0000 Message-Id: <8FE14DB8-DF5D-4F29-BC49-63CE12B6D5EB@gazagnaire.org> References: <7772C602-E0F4-43E2-96EF-CCBD58B43596@gazagnaire.org> <0D5A2ABF-A68D-4336-8D7C-58AAAF6E482B@recoil.org> To: Anil Madhavapeddy X-Mailer: Apple Mail (2.2070.6) Cc: Richard Mortier , mirageos-devel Subject: Re: [MirageOS-devel] [ANN] release of dog 0.1.0 X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org >>> just given it a quick go and i suspect i'm missing something obvious... :) >>> >>> in ~/t/dog: >>> >>> ``` >>> : mort@greyjay:dog$; dog listen >>> Server started on port 8080. >>> ``` >> >> Can you connect to the server direcly? ie. does http://localhost:8080 returns something useful in your browser (and http://localhost:8080/graph)? > > That particular set of commands works for me, so I suspect this is something to do with Conduit binding to an unexpected interface. If it does turn out to be this, could you leave a comment on: > > https://github.com/mirage/ocaml-conduit/issues/42 Any more instructions on how to debug that? What kind of trace would be helpful to fix that issue? Thomas > > -anil > > > >> >> >>> in ~/t/dogc: >>> >>> ``` >>> : mort@greyjay:dogc$; dog push -m "bark bark" http://localhost:8080 >>> Unix.Unix_error(Unix.ECONNREFUSED, "connect", "") >>> ``` >>> >>> how should i be trying to get a message logged? >>> >>> >>> On 16 February 2015 at 21:55, Thomas Gazagnaire wrote: >>>> I'd like to announce the first (very alpha) release of a new synchronisation tool: "dog" >>>> >>>> To install it: `opam install dog` >>>> >>>> The tool is built using Irmin and it demonstrate a simple distributed log server. Every client has a local (and partial) state of the system (a valid Git repository, whose active branch is the name of the client), and they synchronise explicitly with a server using the Irmin synchronisation protocol. The server listens for new clients and rebase every client branches into a sub-directory of the master branch. The server state is also stored in a Git repository, and it contains all the client history as well. So if you have: >>>> >>>> Client A: >>>> branch A: >>>> - foo.txt >>>> >>>> and Client B: >>>> branch B: >>>> - foo.txt >>>> >>>> On the server you'll have: >>>> branch A: >>>> - foo.txt >>>> branch B: >>>> - foo.txt >>>> branch master: >>>> A/foo.txt >>>> B/foo.txt >>>> >>>> This is very simple but already quite useful. As usual, feedback appreciated on https://github.com/samoht/dog/issues. >>>> >>>> Best, >>>> Thomas >>>> _______________________________________________ >>>> MirageOS-devel mailing list >>>> MirageOS-devel@lists.xenproject.org >>>> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel >>> >>> >>> >>> -- >>> Richard Mortier >>> mort@cantab.net >> >> >> _______________________________________________ >> MirageOS-devel mailing list >> MirageOS-devel@lists.xenproject.org >> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel >> > _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Tue Feb 17 10:56:32 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 17 Feb 2015 10:56:32 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YNfpQ-0002N2-EL; Tue, 17 Feb 2015 10:56:32 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YNfpP-0002Mx-4Z for mirageos-devel@lists.xenproject.org; Tue, 17 Feb 2015 10:56:31 +0000 Received: from [85.158.137.68] by server-15.bemta-3.messagelabs.com id 8A/DB-02884-E5E13E45; Tue, 17 Feb 2015 10:56:30 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-14.tower-31.messagelabs.com!1424170589!9743312!1 X-Originating-IP: [5.153.225.51] X-SpamReason: No, hits=0.2 required=7.0 tests=RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 24070 invoked from network); 17 Feb 2015 10:56:29 -0000 Received: from bark.recoil.org (HELO bark.recoil.org) (5.153.225.51) by server-14.tower-31.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 17 Feb 2015 10:56:29 -0000 Received: from [192.168.1.39] (cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net [86.30.244.239]); by bark.recoil.org (OpenSMTPD) with ESMTPSA id 2f37b3e5; TLS version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO; Tue, 17 Feb 2015 10:56:29 +0000 (GMT) Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) From: Anil Madhavapeddy In-Reply-To: <8FE14DB8-DF5D-4F29-BC49-63CE12B6D5EB@gazagnaire.org> Date: Tue, 17 Feb 2015 10:56:28 +0000 Message-Id: References: <7772C602-E0F4-43E2-96EF-CCBD58B43596@gazagnaire.org> <0D5A2ABF-A68D-4336-8D7C-58AAAF6E482B@recoil.org> <8FE14DB8-DF5D-4F29-BC49-63CE12B6D5EB@gazagnaire.org> To: Thomas Gazagnaire X-Mailer: Apple Mail (2.2070.6) Cc: Richard Mortier , mirageos-devel Subject: Re: [MirageOS-devel] [ANN] release of dog 0.1.0 X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 17 Feb 2015, at 10:55, Thomas Gazagnaire wrote: > >>>> just given it a quick go and i suspect i'm missing something obvious... :) >>>> >>>> in ~/t/dog: >>>> >>>> ``` >>>> : mort@greyjay:dog$; dog listen >>>> Server started on port 8080. >>>> ``` >>> >>> Can you connect to the server direcly? ie. does http://localhost:8080 returns something useful in your browser (and http://localhost:8080/graph)? >> >> That particular set of commands works for me, so I suspect this is something to do with Conduit binding to an unexpected interface. If it does turn out to be this, could you leave a comment on: >> >> https://github.com/mirage/ocaml-conduit/issues/42 > > Any more instructions on how to debug that? What kind of trace would be helpful to fix that issue? Just tracing through cohttp-server-lwt and seeing why it's not binding to localhost only when `cohttp-server-lwt -s localhost` is specified would be most useful. -anil _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Tue Feb 17 10:56:32 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 17 Feb 2015 10:56:32 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YNfpQ-0002N2-EL; Tue, 17 Feb 2015 10:56:32 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YNfpP-0002Mx-4Z for mirageos-devel@lists.xenproject.org; Tue, 17 Feb 2015 10:56:31 +0000 Received: from [85.158.137.68] by server-15.bemta-3.messagelabs.com id 8A/DB-02884-E5E13E45; Tue, 17 Feb 2015 10:56:30 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-14.tower-31.messagelabs.com!1424170589!9743312!1 X-Originating-IP: [5.153.225.51] X-SpamReason: No, hits=0.2 required=7.0 tests=RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 24070 invoked from network); 17 Feb 2015 10:56:29 -0000 Received: from bark.recoil.org (HELO bark.recoil.org) (5.153.225.51) by server-14.tower-31.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 17 Feb 2015 10:56:29 -0000 Received: from [192.168.1.39] (cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net [86.30.244.239]); by bark.recoil.org (OpenSMTPD) with ESMTPSA id 2f37b3e5; TLS version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO; Tue, 17 Feb 2015 10:56:29 +0000 (GMT) Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) From: Anil Madhavapeddy In-Reply-To: <8FE14DB8-DF5D-4F29-BC49-63CE12B6D5EB@gazagnaire.org> Date: Tue, 17 Feb 2015 10:56:28 +0000 Message-Id: References: <7772C602-E0F4-43E2-96EF-CCBD58B43596@gazagnaire.org> <0D5A2ABF-A68D-4336-8D7C-58AAAF6E482B@recoil.org> <8FE14DB8-DF5D-4F29-BC49-63CE12B6D5EB@gazagnaire.org> To: Thomas Gazagnaire X-Mailer: Apple Mail (2.2070.6) Cc: Richard Mortier , mirageos-devel Subject: Re: [MirageOS-devel] [ANN] release of dog 0.1.0 X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 17 Feb 2015, at 10:55, Thomas Gazagnaire wrote: > >>>> just given it a quick go and i suspect i'm missing something obvious... :) >>>> >>>> in ~/t/dog: >>>> >>>> ``` >>>> : mort@greyjay:dog$; dog listen >>>> Server started on port 8080. >>>> ``` >>> >>> Can you connect to the server direcly? ie. does http://localhost:8080 returns something useful in your browser (and http://localhost:8080/graph)? >> >> That particular set of commands works for me, so I suspect this is something to do with Conduit binding to an unexpected interface. If it does turn out to be this, could you leave a comment on: >> >> https://github.com/mirage/ocaml-conduit/issues/42 > > Any more instructions on how to debug that? What kind of trace would be helpful to fix that issue? Just tracing through cohttp-server-lwt and seeing why it's not binding to localhost only when `cohttp-server-lwt -s localhost` is specified would be most useful. -anil _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Tue Feb 17 10:57:33 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 17 Feb 2015 10:57:33 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YNfqP-0002Ov-JF; Tue, 17 Feb 2015 10:57:33 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YNfqO-0002Oq-B9 for mirageos-devel@lists.xenproject.org; Tue, 17 Feb 2015 10:57:32 +0000 Received: from [85.158.137.68] by server-17.bemta-3.messagelabs.com id CB/49-02896-B9E13E45; Tue, 17 Feb 2015 10:57:31 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-12.tower-31.messagelabs.com!1424170650!12121400!1 X-Originating-IP: [5.153.225.51] X-SpamReason: No, hits=0.2 required=7.0 tests=RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2613 invoked from network); 17 Feb 2015 10:57:30 -0000 Received: from bark.recoil.org (HELO bark.recoil.org) (5.153.225.51) by server-12.tower-31.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 17 Feb 2015 10:57:30 -0000 Received: from [192.168.1.39] (cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net [86.30.244.239]); by bark.recoil.org (OpenSMTPD) with ESMTPSA id a3d34c08; TLS version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO; Tue, 17 Feb 2015 10:57:30 +0000 (GMT) Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) From: Anil Madhavapeddy In-Reply-To: Date: Tue, 17 Feb 2015 10:57:29 +0000 Message-Id: <88196D02-7688-4413-8178-377149602527@recoil.org> References: <54E1B5EA.9010301@inria.fr> <65617E2B-8916-4779-A57F-7F5327FC7764@recoil.org> To: =?utf-8?Q?Daniel_B=C3=BCnzli?= X-Mailer: Apple Mail (2.2070.6) Cc: Francois Berenger , mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Would it be be useful to add DAFT in the pioneer projects of mirage? X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org Cj4gT24gMTcgRmViIDIwMTUsIGF0IDEwOjU0LCBEYW5pZWwgQsO8bnpsaSA8ZGFuaWVsLmJ1ZW56 bGlAZXJyYXRpcXVlLmNoPiB3cm90ZToKPiAKPiBMZSBtYXJkaSwgMTcgZsOpdnJpZXIgMjAxNSDD oCAxMToyNiwgQW5pbCBNYWRoYXZhcGVkZHkgYSDDqWNyaXQgOgo+PiBUaGFua3MgZm9yIHRoaXMg LS0gYmVmb3JlIHB1dHRpbmcgdGhpcyBvbmUgdXAsIEknZCBzdWdnZXN0IGEgcGlvbmVlciBwcm9q ZWN0IHRvIGFkZCBzdXBwb3J0IGZvciBaZXJvTVEuCj4gCj4gVGhvdWdoIG1heWJlIG1vcmUgZXhw ZXJpbWVudGFsLCBuYW5vbXNnIChodHRwOi8vbmFub21zZy5vcmcvKSBjb3VsZCBiZSBhbiBhbHRl cm5hdGl2ZS4gVGhlIGludGVyZXN0aW5nIHRoaW5nIGJlaW5nIHRoYXQgdGhlc2UgYXJlIGRlc2ln bnMgdGhhdCBsZWFybmVkIGZyb20gWmVyb01RIGFuZCB0aGV5IGhhdmUgaW5mb3JtYXRpb25hbCBS RkNzIGZvciB0aGVpciAic2NhbGFiaWxpdHkiIHByb3RvY29sczoKPiAKPiBodHRwczovL2dpdGh1 Yi5jb20vbmFub21zZy9uYW5vbXNnL3RyZWUvbWFzdGVyL3JmYwo+IAo+IFRoZXJlIGlzIGF0IGxl YXN0IGFub3RoZXIgaW5kZXBlbmRlbnQgaW1wbGVtZW50YXRpb24gb2YgdGhlIHByb3RvY29scyBp biBwdXJlIEdvIChodHRwczovL2dpdGh1Yi5jb20vZ2RhbW9yZS9tYW5nb3MpCgpZZXAsIGJ1dCBa ZXJvTVEgaXMgYWxyZWFkeSBlc3RhYmxpc2hlZCBhcyBhIGJpbmFyeSBwcm90b2NvbCBmb3Igc29t ZSBhcHBsaWNhdGlvbnMgLS0gbW9zdCBub3RhYmx5IElPQ2FtbC4gIFNvIHdlIHdvdWxkIG5lZWQg dG8gcG9ydCB0aGVtIHRvIE5hbm9tc2cgKHByb2JhYmx5IG5vdCB0b28gYmFkIGluIElPQ2FtbCdz IGNhc2UpLgoKLWEKCgpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fXwpNaXJhZ2VPUy1kZXZlbCBtYWlsaW5nIGxpc3QKTWlyYWdlT1MtZGV2ZWxAbGlzdHMueGVu cHJvamVjdC5vcmcKaHR0cDovL2xpc3RzLnhlbnByb2plY3Qub3JnL2NnaS1iaW4vbWFpbG1hbi9s aXN0aW5mby9taXJhZ2Vvcy1kZXZlbAo= From mirageos-devel-bounces@lists.xenproject.org Tue Feb 17 10:57:33 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 17 Feb 2015 10:57:33 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YNfqP-0002Ov-JF; Tue, 17 Feb 2015 10:57:33 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YNfqO-0002Oq-B9 for mirageos-devel@lists.xenproject.org; Tue, 17 Feb 2015 10:57:32 +0000 Received: from [85.158.137.68] by server-17.bemta-3.messagelabs.com id CB/49-02896-B9E13E45; Tue, 17 Feb 2015 10:57:31 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-12.tower-31.messagelabs.com!1424170650!12121400!1 X-Originating-IP: [5.153.225.51] X-SpamReason: No, hits=0.2 required=7.0 tests=RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2613 invoked from network); 17 Feb 2015 10:57:30 -0000 Received: from bark.recoil.org (HELO bark.recoil.org) (5.153.225.51) by server-12.tower-31.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 17 Feb 2015 10:57:30 -0000 Received: from [192.168.1.39] (cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net [86.30.244.239]); by bark.recoil.org (OpenSMTPD) with ESMTPSA id a3d34c08; TLS version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO; Tue, 17 Feb 2015 10:57:30 +0000 (GMT) Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) From: Anil Madhavapeddy In-Reply-To: Date: Tue, 17 Feb 2015 10:57:29 +0000 Message-Id: <88196D02-7688-4413-8178-377149602527@recoil.org> References: <54E1B5EA.9010301@inria.fr> <65617E2B-8916-4779-A57F-7F5327FC7764@recoil.org> To: =?utf-8?Q?Daniel_B=C3=BCnzli?= X-Mailer: Apple Mail (2.2070.6) Cc: Francois Berenger , mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Would it be be useful to add DAFT in the pioneer projects of mirage? X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org Cj4gT24gMTcgRmViIDIwMTUsIGF0IDEwOjU0LCBEYW5pZWwgQsO8bnpsaSA8ZGFuaWVsLmJ1ZW56 bGlAZXJyYXRpcXVlLmNoPiB3cm90ZToKPiAKPiBMZSBtYXJkaSwgMTcgZsOpdnJpZXIgMjAxNSDD oCAxMToyNiwgQW5pbCBNYWRoYXZhcGVkZHkgYSDDqWNyaXQgOgo+PiBUaGFua3MgZm9yIHRoaXMg LS0gYmVmb3JlIHB1dHRpbmcgdGhpcyBvbmUgdXAsIEknZCBzdWdnZXN0IGEgcGlvbmVlciBwcm9q ZWN0IHRvIGFkZCBzdXBwb3J0IGZvciBaZXJvTVEuCj4gCj4gVGhvdWdoIG1heWJlIG1vcmUgZXhw ZXJpbWVudGFsLCBuYW5vbXNnIChodHRwOi8vbmFub21zZy5vcmcvKSBjb3VsZCBiZSBhbiBhbHRl cm5hdGl2ZS4gVGhlIGludGVyZXN0aW5nIHRoaW5nIGJlaW5nIHRoYXQgdGhlc2UgYXJlIGRlc2ln bnMgdGhhdCBsZWFybmVkIGZyb20gWmVyb01RIGFuZCB0aGV5IGhhdmUgaW5mb3JtYXRpb25hbCBS RkNzIGZvciB0aGVpciAic2NhbGFiaWxpdHkiIHByb3RvY29sczoKPiAKPiBodHRwczovL2dpdGh1 Yi5jb20vbmFub21zZy9uYW5vbXNnL3RyZWUvbWFzdGVyL3JmYwo+IAo+IFRoZXJlIGlzIGF0IGxl YXN0IGFub3RoZXIgaW5kZXBlbmRlbnQgaW1wbGVtZW50YXRpb24gb2YgdGhlIHByb3RvY29scyBp biBwdXJlIEdvIChodHRwczovL2dpdGh1Yi5jb20vZ2RhbW9yZS9tYW5nb3MpCgpZZXAsIGJ1dCBa ZXJvTVEgaXMgYWxyZWFkeSBlc3RhYmxpc2hlZCBhcyBhIGJpbmFyeSBwcm90b2NvbCBmb3Igc29t ZSBhcHBsaWNhdGlvbnMgLS0gbW9zdCBub3RhYmx5IElPQ2FtbC4gIFNvIHdlIHdvdWxkIG5lZWQg dG8gcG9ydCB0aGVtIHRvIE5hbm9tc2cgKHByb2JhYmx5IG5vdCB0b28gYmFkIGluIElPQ2FtbCdz IGNhc2UpLgoKLWEKCgpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fXwpNaXJhZ2VPUy1kZXZlbCBtYWlsaW5nIGxpc3QKTWlyYWdlT1MtZGV2ZWxAbGlzdHMueGVu cHJvamVjdC5vcmcKaHR0cDovL2xpc3RzLnhlbnByb2plY3Qub3JnL2NnaS1iaW4vbWFpbG1hbi9s aXN0aW5mby9taXJhZ2Vvcy1kZXZlbAo= From mirageos-devel-bounces@lists.xenproject.org Wed Feb 18 19:50:13 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 18 Feb 2015 19:50:13 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YOAdI-000818-Ir; Wed, 18 Feb 2015 19:50:04 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YOAdG-00080p-1a for MirageOS-devel@lists.xenproject.org; Wed, 18 Feb 2015 19:50:02 +0000 Received: from [85.158.139.211] by server-4.bemta-5.messagelabs.com id BE/61-03164-9ECE4E45; Wed, 18 Feb 2015 19:50:01 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-4.tower-206.messagelabs.com!1424289000!12663999!1 X-Originating-IP: [5.153.225.51] X-SpamReason: No, hits=0.5 required=7.0 tests=MAILTO_TO_SPAM_ADDR, RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7323 invoked from network); 18 Feb 2015 19:50:00 -0000 Received: from bark.recoil.org (HELO bark.recoil.org) (5.153.225.51) by server-4.tower-206.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 18 Feb 2015 19:50:00 -0000 Received: from [192.168.1.39] (cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net [86.30.244.239]); by bark.recoil.org (OpenSMTPD) with ESMTPSA id 088005da; TLS version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO; Wed, 18 Feb 2015 19:50:00 +0000 (GMT) Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) From: Anil Madhavapeddy In-Reply-To: <20150216011144.GB26571@humongous.Belkin> Date: Wed, 18 Feb 2015 19:49:59 +0000 Message-Id: References: <9C6275D4-2397-45E7-B18A-81A47C317545@recoil.org> <88230342-7010-413A-8270-D36D1CD0D1D4@cam.ac.uk> <20150216011144.GB26571@humongous.Belkin> To: Jon Ludlam X-Mailer: Apple Mail (2.2070.6) Cc: mirageos-devel Subject: Re: [MirageOS-devel] performance regression tests X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 16 Feb 2015, at 01:11, Jon Ludlam wrote: > > On Sun, Feb 15, 2015 at 02:16:15PM +0000, Richard Mortier wrote: >> oh cool-- i'll give that a go sometime then (recently nuked all my >> vbox vms so have to rebuild anyway). >> >> blobs might be useful, or perhaps update the vagrant-vms repo with >> appropriate build scripts? >> > > I've updated imduffy15's xenserver packer scripts to the latest 6.5 release of XS - the result is here: > > https://github.com/jonludlam/packer-xenserver > > I can probably integrate it with the vagrant-vms repo once I've ironed out the kinks. I don't think I have access to blobs now, though I've just had to reinstall this computer so it's conceivable I've lost an ssh key somewhere. In any case, the box doesn't take long to build. It boots OK and the toolstack is all running and I can run unikernels, but I'm having difficulty with forwarded ports right now. I'll give it another go tomorrow. I'll provision a dedicated box with more storage -- blobs is a little underpowered for building Vagrant images. Anil _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Wed Feb 18 19:50:13 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 18 Feb 2015 19:50:13 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YOAdI-000818-Ir; Wed, 18 Feb 2015 19:50:04 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YOAdG-00080p-1a for MirageOS-devel@lists.xenproject.org; Wed, 18 Feb 2015 19:50:02 +0000 Received: from [85.158.139.211] by server-4.bemta-5.messagelabs.com id BE/61-03164-9ECE4E45; Wed, 18 Feb 2015 19:50:01 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-4.tower-206.messagelabs.com!1424289000!12663999!1 X-Originating-IP: [5.153.225.51] X-SpamReason: No, hits=0.5 required=7.0 tests=MAILTO_TO_SPAM_ADDR, RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7323 invoked from network); 18 Feb 2015 19:50:00 -0000 Received: from bark.recoil.org (HELO bark.recoil.org) (5.153.225.51) by server-4.tower-206.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 18 Feb 2015 19:50:00 -0000 Received: from [192.168.1.39] (cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net [86.30.244.239]); by bark.recoil.org (OpenSMTPD) with ESMTPSA id 088005da; TLS version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO; Wed, 18 Feb 2015 19:50:00 +0000 (GMT) Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) From: Anil Madhavapeddy In-Reply-To: <20150216011144.GB26571@humongous.Belkin> Date: Wed, 18 Feb 2015 19:49:59 +0000 Message-Id: References: <9C6275D4-2397-45E7-B18A-81A47C317545@recoil.org> <88230342-7010-413A-8270-D36D1CD0D1D4@cam.ac.uk> <20150216011144.GB26571@humongous.Belkin> To: Jon Ludlam X-Mailer: Apple Mail (2.2070.6) Cc: mirageos-devel Subject: Re: [MirageOS-devel] performance regression tests X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 16 Feb 2015, at 01:11, Jon Ludlam wrote: > > On Sun, Feb 15, 2015 at 02:16:15PM +0000, Richard Mortier wrote: >> oh cool-- i'll give that a go sometime then (recently nuked all my >> vbox vms so have to rebuild anyway). >> >> blobs might be useful, or perhaps update the vagrant-vms repo with >> appropriate build scripts? >> > > I've updated imduffy15's xenserver packer scripts to the latest 6.5 release of XS - the result is here: > > https://github.com/jonludlam/packer-xenserver > > I can probably integrate it with the vagrant-vms repo once I've ironed out the kinks. I don't think I have access to blobs now, though I've just had to reinstall this computer so it's conceivable I've lost an ssh key somewhere. In any case, the box doesn't take long to build. It boots OK and the toolstack is all running and I can run unikernels, but I'm having difficulty with forwarded ports right now. I'll give it another go tomorrow. I'll provision a dedicated box with more storage -- blobs is a little underpowered for building Vagrant images. Anil _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Fri Feb 20 15:10:29 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 20 Feb 2015 15:10:29 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YOpDi-0004bT-IR; Fri, 20 Feb 2015 15:10:22 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YOpDh-0004bN-Tu for mirageos-devel@lists.xenproject.org; Fri, 20 Feb 2015 15:10:22 +0000 Received: from [85.158.143.35] by server-3.bemta-4.messagelabs.com id 7C/92-29399-D5E47E45; Fri, 20 Feb 2015 15:10:21 +0000 X-Env-Sender: russell.pavlicek.xen@gmail.com X-Msg-Ref: server-10.tower-21.messagelabs.com!1424445016!12075772!1 X-Originating-IP: [209.85.215.49] X-SpamReason: No, hits=2.5 required=7.0 tests=RCVD_BY_IP, SUSPICIOUS_RECIPS X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22955 invoked from network); 20 Feb 2015 15:10:19 -0000 Received: from mail-la0-f49.google.com (HELO mail-la0-f49.google.com) (209.85.215.49) by server-10.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 20 Feb 2015 15:10:19 -0000 Received: by labgq15 with SMTP id gq15so6713313lab.3 for ; Fri, 20 Feb 2015 07:10:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:message-id:subject:from:to:content-type; bh=FFYBj1tA0NLlzykg+5J4uBNMQD2hDR6AzHE2GdUAm9I=; b=keZwXZetX2OKKqsxBgd0d/QEnjj1jvI/Km1ciWqgHhq/L6tanT/PmZjcG7vByvwnFA yfmvmgXxDfZ33iez9Bzsdd+JhYUIje1TxYMNzaI1GCc+Mg/psEX8pCXckqiRwHaRF+zp f67WCaPn2hvBunWcpue5N/DAQD7Zz0TFTBytUaSHTKiC9+A/RRFTgLV26GW81Z8hd7Oz LWn/1X7HIW4+H3DbIjiYw7vN3D7ck3O6ooDTjCFhNuEQM+kbHdnLK+TOpZEoTSVv6lFr T+68N35qzHXa04L+czl4YSaXFObAB2FNEmqmarBjdYWf5xvorHDmzSw7FOGQetHEN+F7 z12Q== MIME-Version: 1.0 X-Received: by 10.112.185.101 with SMTP id fb5mr9248181lbc.12.1424445015130; Fri, 20 Feb 2015 07:10:15 -0800 (PST) Received: by 10.112.147.135 with HTTP; Fri, 20 Feb 2015 07:10:15 -0800 (PST) Date: Fri, 20 Feb 2015 10:10:15 -0500 X-Google-Sender-Auth: bx5QvbkEn11sa2j7Wlo_lawvZIA Message-ID: From: Russ Pavlicek To: "xen-users@lists.xen.org" , xen-devel@lists.xen.org, xen-api@lists.xen.org, xs-devel@lists.xenserver.org, mirageos-devel@lists.xenproject.org Subject: [MirageOS-devel] Xen Project Document Day is Wednesday, February 25: The Great 4.5 Clean-Up (Part II) X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org The documentation around the recent 4.5 release is improving, but there is still need for more clean-up. We still have a number of pages which talk in terms of xend rather than libxenlight. For example, check the TODO list (see below) for a list of pages which we know still feature the "xm" command instead of "xl". Have you seen a page which needs updating? If you can't update it, please add it to the list under "THE GREAT 4.5 CLEAN-UP" on the TODO list. If we can identify and update these pages, we'll help new users tremendously. There are few things as bad as trying a command which does not exist and is not available. Let's not frustrate our newbies. All the information you need to participate in Document Day is here: http://wiki.xenproject.org/wiki/Xen_Document_Days Also take a look at the current TODO list to see other items which need attention: http://wiki.xenproject.org/wiki/Xen_Document_Days/TODO Please think about how you can help out. If you haven't requested to be made a Wiki editor, save time and do it now so you are ready to go on Document Day. Just fill out the form below: http://xenproject.org/component/content/article/100-misc/145-request-to-be-made-a-wiki-editor.html We hope to see you Wednesday in #xendocs! _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Fri Feb 20 15:10:29 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 20 Feb 2015 15:10:29 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YOpDi-0004bT-IR; Fri, 20 Feb 2015 15:10:22 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YOpDh-0004bN-Tu for mirageos-devel@lists.xenproject.org; Fri, 20 Feb 2015 15:10:22 +0000 Received: from [85.158.143.35] by server-3.bemta-4.messagelabs.com id 7C/92-29399-D5E47E45; Fri, 20 Feb 2015 15:10:21 +0000 X-Env-Sender: russell.pavlicek.xen@gmail.com X-Msg-Ref: server-10.tower-21.messagelabs.com!1424445016!12075772!1 X-Originating-IP: [209.85.215.49] X-SpamReason: No, hits=2.5 required=7.0 tests=RCVD_BY_IP, SUSPICIOUS_RECIPS X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22955 invoked from network); 20 Feb 2015 15:10:19 -0000 Received: from mail-la0-f49.google.com (HELO mail-la0-f49.google.com) (209.85.215.49) by server-10.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 20 Feb 2015 15:10:19 -0000 Received: by labgq15 with SMTP id gq15so6713313lab.3 for ; Fri, 20 Feb 2015 07:10:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:message-id:subject:from:to:content-type; bh=FFYBj1tA0NLlzykg+5J4uBNMQD2hDR6AzHE2GdUAm9I=; b=keZwXZetX2OKKqsxBgd0d/QEnjj1jvI/Km1ciWqgHhq/L6tanT/PmZjcG7vByvwnFA yfmvmgXxDfZ33iez9Bzsdd+JhYUIje1TxYMNzaI1GCc+Mg/psEX8pCXckqiRwHaRF+zp f67WCaPn2hvBunWcpue5N/DAQD7Zz0TFTBytUaSHTKiC9+A/RRFTgLV26GW81Z8hd7Oz LWn/1X7HIW4+H3DbIjiYw7vN3D7ck3O6ooDTjCFhNuEQM+kbHdnLK+TOpZEoTSVv6lFr T+68N35qzHXa04L+czl4YSaXFObAB2FNEmqmarBjdYWf5xvorHDmzSw7FOGQetHEN+F7 z12Q== MIME-Version: 1.0 X-Received: by 10.112.185.101 with SMTP id fb5mr9248181lbc.12.1424445015130; Fri, 20 Feb 2015 07:10:15 -0800 (PST) Received: by 10.112.147.135 with HTTP; Fri, 20 Feb 2015 07:10:15 -0800 (PST) Date: Fri, 20 Feb 2015 10:10:15 -0500 X-Google-Sender-Auth: bx5QvbkEn11sa2j7Wlo_lawvZIA Message-ID: From: Russ Pavlicek To: "xen-users@lists.xen.org" , xen-devel@lists.xen.org, xen-api@lists.xen.org, xs-devel@lists.xenserver.org, mirageos-devel@lists.xenproject.org Subject: [MirageOS-devel] Xen Project Document Day is Wednesday, February 25: The Great 4.5 Clean-Up (Part II) X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org The documentation around the recent 4.5 release is improving, but there is still need for more clean-up. We still have a number of pages which talk in terms of xend rather than libxenlight. For example, check the TODO list (see below) for a list of pages which we know still feature the "xm" command instead of "xl". Have you seen a page which needs updating? If you can't update it, please add it to the list under "THE GREAT 4.5 CLEAN-UP" on the TODO list. If we can identify and update these pages, we'll help new users tremendously. There are few things as bad as trying a command which does not exist and is not available. Let's not frustrate our newbies. All the information you need to participate in Document Day is here: http://wiki.xenproject.org/wiki/Xen_Document_Days Also take a look at the current TODO list to see other items which need attention: http://wiki.xenproject.org/wiki/Xen_Document_Days/TODO Please think about how you can help out. If you haven't requested to be made a Wiki editor, save time and do it now so you are ready to go on Document Day. Just fill out the form below: http://xenproject.org/component/content/article/100-misc/145-request-to-be-made-a-wiki-editor.html We hope to see you Wednesday in #xendocs! _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Tue Feb 24 11:30:48 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 24 Feb 2015 11:30:48 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YQDhL-0004mh-Vv; Tue, 24 Feb 2015 11:30:43 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YQDNo-0002is-Ng for mirageos-devel@lists.xenproject.org; Tue, 24 Feb 2015 11:10:32 +0000 Received: from [85.158.143.35] by server-1.bemta-4.messagelabs.com id 48/CF-03004-82C5CE45; Tue, 24 Feb 2015 11:10:32 +0000 X-Env-Sender: mic.alberti@gmail.com X-Msg-Ref: server-16.tower-21.messagelabs.com!1424776219!9333038!1 X-Originating-IP: [209.85.213.176] X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_10_20,HTML_MESSAGE, RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5982 invoked from network); 24 Feb 2015 11:10:28 -0000 Received: from mail-ig0-f176.google.com (HELO mail-ig0-f176.google.com) (209.85.213.176) by server-16.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 24 Feb 2015 11:10:28 -0000 Received: by mail-ig0-f176.google.com with SMTP id hl2so25666003igb.3 for ; Tue, 24 Feb 2015 03:10:14 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=85jUWTLqDfFYcVDYDNPvfgscbSJmFUyoESlPjgt9ZB0=; b=NidyG8+fZBzc2HZtDEevucao1ftle028L6Oz9vZ2FfT1EB3DUIqGDjaWy1MJ9ornJo B6MoXG3EDnOlry61yLpwkJVMgrdvyTeqdwQ7mRh938AY03tOJvUiewTYow5407s9kYlc 0DY6OgBzNbwOzVf10W+5V8IsaVtqh9s5wLXbdVatMFKe/YEtTlHXBcXEfVEdCWxEAWH9 7Zqm3sDLB6rFHeAgBdeFhKkiNT8VbfWYIadMhE2Iaw6sotQhTCXCVUDE+1deMIKUayuZ BoUyJGJLlCfC5DwLxGKU6SkAKIkeJhKB9O7TRVRN97dYDUfKAFVjs9vm6gZz/hDd9RFv N98A== MIME-Version: 1.0 X-Received: by 10.107.27.143 with SMTP id b137mr19856449iob.76.1424776214101; Tue, 24 Feb 2015 03:10:14 -0800 (PST) Received: by 10.64.33.131 with HTTP; Tue, 24 Feb 2015 03:10:14 -0800 (PST) Date: Tue, 24 Feb 2015 12:10:14 +0100 Message-ID: From: Michele Alberti To: mirageos-devel@lists.xenproject.org X-Mailman-Approved-At: Tue, 24 Feb 2015 11:30:43 +0000 Subject: [MirageOS-devel] Question about pioneer projects X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============9135665107861494205==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============9135665107861494205== Content-Type: multipart/alternative; boundary=001a1140a87c2045b5050fd39014 --001a1140a87c2045b5050fd39014 Content-Type: text/plain; charset=UTF-8 Hello, First of all let me say that all the MirageOS idea and implementation sounds really great. Not so many years ago I used OCaml for a University CS project, and I've recently rediscovered it (RWO book). I'd love participating into a MirageOS related project to do some real work in OCaml, though I am a newcomer (even if I have a CS background). I've given a look at your projects github webpage and I must admit that they all are very cool. However, let me ask a question to see whether I can be a good fit: what is the working knowledge of OCaml you expect for a 3-starred project (i.e. medium difficulty)? Sorry for being pedantic, but I'm really interested in participating. Best regards, michele alberti --001a1140a87c2045b5050fd39014 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hello,

First of all let m= e say that all the MirageOS idea and implementation sounds really great.
Not so many years ago I used OCaml for a University CS project, = and I've recently rediscovered it (RWO book).

I'd lov= e participating into a MirageOS related project to do some real work in OCa= ml, though I am a newcomer (even if I have a CS background). I've given= a look at your projects github webpage and I must admit that they all are = very cool. However, let me ask a question to see whether I can be a good fi= t:

what is the working knowledge of OCaml you expect for = a 3-starred project (i.e. medium difficulty)?

= Sorry for being pedantic, but I'm really interested in participating.

Best regards,

michele alberti=
--001a1140a87c2045b5050fd39014-- --===============9135665107861494205== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --===============9135665107861494205==-- From mirageos-devel-bounces@lists.xenproject.org Tue Feb 24 11:30:48 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 24 Feb 2015 11:30:48 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YQDhL-0004mh-Vv; Tue, 24 Feb 2015 11:30:43 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YQDNo-0002is-Ng for mirageos-devel@lists.xenproject.org; Tue, 24 Feb 2015 11:10:32 +0000 Received: from [85.158.143.35] by server-1.bemta-4.messagelabs.com id 48/CF-03004-82C5CE45; Tue, 24 Feb 2015 11:10:32 +0000 X-Env-Sender: mic.alberti@gmail.com X-Msg-Ref: server-16.tower-21.messagelabs.com!1424776219!9333038!1 X-Originating-IP: [209.85.213.176] X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_10_20,HTML_MESSAGE, RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5982 invoked from network); 24 Feb 2015 11:10:28 -0000 Received: from mail-ig0-f176.google.com (HELO mail-ig0-f176.google.com) (209.85.213.176) by server-16.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 24 Feb 2015 11:10:28 -0000 Received: by mail-ig0-f176.google.com with SMTP id hl2so25666003igb.3 for ; Tue, 24 Feb 2015 03:10:14 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=85jUWTLqDfFYcVDYDNPvfgscbSJmFUyoESlPjgt9ZB0=; b=NidyG8+fZBzc2HZtDEevucao1ftle028L6Oz9vZ2FfT1EB3DUIqGDjaWy1MJ9ornJo B6MoXG3EDnOlry61yLpwkJVMgrdvyTeqdwQ7mRh938AY03tOJvUiewTYow5407s9kYlc 0DY6OgBzNbwOzVf10W+5V8IsaVtqh9s5wLXbdVatMFKe/YEtTlHXBcXEfVEdCWxEAWH9 7Zqm3sDLB6rFHeAgBdeFhKkiNT8VbfWYIadMhE2Iaw6sotQhTCXCVUDE+1deMIKUayuZ BoUyJGJLlCfC5DwLxGKU6SkAKIkeJhKB9O7TRVRN97dYDUfKAFVjs9vm6gZz/hDd9RFv N98A== MIME-Version: 1.0 X-Received: by 10.107.27.143 with SMTP id b137mr19856449iob.76.1424776214101; Tue, 24 Feb 2015 03:10:14 -0800 (PST) Received: by 10.64.33.131 with HTTP; Tue, 24 Feb 2015 03:10:14 -0800 (PST) Date: Tue, 24 Feb 2015 12:10:14 +0100 Message-ID: From: Michele Alberti To: mirageos-devel@lists.xenproject.org X-Mailman-Approved-At: Tue, 24 Feb 2015 11:30:43 +0000 Subject: [MirageOS-devel] Question about pioneer projects X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============9135665107861494205==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============9135665107861494205== Content-Type: multipart/alternative; boundary=001a1140a87c2045b5050fd39014 --001a1140a87c2045b5050fd39014 Content-Type: text/plain; charset=UTF-8 Hello, First of all let me say that all the MirageOS idea and implementation sounds really great. Not so many years ago I used OCaml for a University CS project, and I've recently rediscovered it (RWO book). I'd love participating into a MirageOS related project to do some real work in OCaml, though I am a newcomer (even if I have a CS background). I've given a look at your projects github webpage and I must admit that they all are very cool. However, let me ask a question to see whether I can be a good fit: what is the working knowledge of OCaml you expect for a 3-starred project (i.e. medium difficulty)? Sorry for being pedantic, but I'm really interested in participating. Best regards, michele alberti --001a1140a87c2045b5050fd39014 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hello,

First of all let m= e say that all the MirageOS idea and implementation sounds really great.
Not so many years ago I used OCaml for a University CS project, = and I've recently rediscovered it (RWO book).

I'd lov= e participating into a MirageOS related project to do some real work in OCa= ml, though I am a newcomer (even if I have a CS background). I've given= a look at your projects github webpage and I must admit that they all are = very cool. However, let me ask a question to see whether I can be a good fi= t:

what is the working knowledge of OCaml you expect for = a 3-starred project (i.e. medium difficulty)?

= Sorry for being pedantic, but I'm really interested in participating.

Best regards,

michele alberti=
--001a1140a87c2045b5050fd39014-- --===============9135665107861494205== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --===============9135665107861494205==-- From mirageos-devel-bounces@lists.xenproject.org Tue Feb 24 11:42:56 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 24 Feb 2015 11:42:56 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YQDt8-0006tM-AO; Tue, 24 Feb 2015 11:42:54 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YQDt6-0006rH-OE for mirageos-devel@lists.xenproject.org; Tue, 24 Feb 2015 11:42:52 +0000 Received: from [85.158.137.68] by server-9.bemta-3.messagelabs.com id 82/7E-02995-BB36CE45; Tue, 24 Feb 2015 11:42:51 +0000 X-Env-Sender: amc79@cam.ac.uk X-Msg-Ref: server-11.tower-31.messagelabs.com!1424778170!11808182!1 X-Originating-IP: [131.111.8.150] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTMxLjExMS44LjE1MCA9PiAxNDk0MDU=\n X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5497 invoked from network); 24 Feb 2015 11:42:50 -0000 Received: from ppsw-50.csi.cam.ac.uk (HELO ppsw-50.csi.cam.ac.uk) (131.111.8.150) by server-11.tower-31.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 24 Feb 2015 11:42:50 -0000 X-Cam-AntiVirus: no malware found X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/ Received: from host81-149-102-120.in-addr.btopenworld.com ([81.149.102.120]:53462 helo=[10.0.0.143]) by ppsw-50.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.158]:587) with esmtpsa (PLAIN:amc79) (TLSv1:AES128-SHA:128) id 1YQDt4-0004ND-qV (Exim 4.82_3-c0e5623) (return-path ); Tue, 24 Feb 2015 11:42:50 +0000 Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) From: Amir Chaudhry In-Reply-To: Date: Tue, 24 Feb 2015 11:42:52 +0000 Message-Id: References: To: Michele Alberti X-Mailer: Apple Mail (2.1510) Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Question about pioneer projects X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org Hi Michele! Thanks for looking over the projects and getting in touch. It's an *excellent* question and it's one I've also been meaning to ask. :) I think it would be useful for us to provide (on the page itself [1]) some idea of what each difficulty level entails. I'll bring that up in the next Mirage call [2] -- which anyone is welcome to join, by the way. In the meantime, if there are specific projects you're interested in perhaps we can discuss them here? (Links are mostly to remind others of their existence) [1] https://github.com/mirage/mirage-www/wiki/Pioneer-Projects [2] https://github.com/mirage/mirage-www/wiki/Call-Agenda Best wishes, Amir On 24 Feb 2015, at 11:10, Michele Alberti wrote: > Hello, > > First of all let me say that all the MirageOS idea and implementation sounds really great. > > Not so many years ago I used OCaml for a University CS project, and I've recently rediscovered it (RWO book). > > I'd love participating into a MirageOS related project to do some real work in OCaml, though I am a newcomer (even if I have a CS background). I've given a look at your projects github webpage and I must admit that they all are very cool. However, let me ask a question to see whether I can be a good fit: > > what is the working knowledge of OCaml you expect for a 3-starred project (i.e. medium difficulty)? > > Sorry for being pedantic, but I'm really interested in participating. > > Best regards, > > michele alberti > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Tue Feb 24 11:42:56 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 24 Feb 2015 11:42:56 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YQDt8-0006tM-AO; Tue, 24 Feb 2015 11:42:54 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YQDt6-0006rH-OE for mirageos-devel@lists.xenproject.org; Tue, 24 Feb 2015 11:42:52 +0000 Received: from [85.158.137.68] by server-9.bemta-3.messagelabs.com id 82/7E-02995-BB36CE45; Tue, 24 Feb 2015 11:42:51 +0000 X-Env-Sender: amc79@cam.ac.uk X-Msg-Ref: server-11.tower-31.messagelabs.com!1424778170!11808182!1 X-Originating-IP: [131.111.8.150] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTMxLjExMS44LjE1MCA9PiAxNDk0MDU=\n X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5497 invoked from network); 24 Feb 2015 11:42:50 -0000 Received: from ppsw-50.csi.cam.ac.uk (HELO ppsw-50.csi.cam.ac.uk) (131.111.8.150) by server-11.tower-31.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 24 Feb 2015 11:42:50 -0000 X-Cam-AntiVirus: no malware found X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/ Received: from host81-149-102-120.in-addr.btopenworld.com ([81.149.102.120]:53462 helo=[10.0.0.143]) by ppsw-50.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.158]:587) with esmtpsa (PLAIN:amc79) (TLSv1:AES128-SHA:128) id 1YQDt4-0004ND-qV (Exim 4.82_3-c0e5623) (return-path ); Tue, 24 Feb 2015 11:42:50 +0000 Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) From: Amir Chaudhry In-Reply-To: Date: Tue, 24 Feb 2015 11:42:52 +0000 Message-Id: References: To: Michele Alberti X-Mailer: Apple Mail (2.1510) Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Question about pioneer projects X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org Hi Michele! Thanks for looking over the projects and getting in touch. It's an *excellent* question and it's one I've also been meaning to ask. :) I think it would be useful for us to provide (on the page itself [1]) some idea of what each difficulty level entails. I'll bring that up in the next Mirage call [2] -- which anyone is welcome to join, by the way. In the meantime, if there are specific projects you're interested in perhaps we can discuss them here? (Links are mostly to remind others of their existence) [1] https://github.com/mirage/mirage-www/wiki/Pioneer-Projects [2] https://github.com/mirage/mirage-www/wiki/Call-Agenda Best wishes, Amir On 24 Feb 2015, at 11:10, Michele Alberti wrote: > Hello, > > First of all let me say that all the MirageOS idea and implementation sounds really great. > > Not so many years ago I used OCaml for a University CS project, and I've recently rediscovered it (RWO book). > > I'd love participating into a MirageOS related project to do some real work in OCaml, though I am a newcomer (even if I have a CS background). I've given a look at your projects github webpage and I must admit that they all are very cool. However, let me ask a question to see whether I can be a good fit: > > what is the working knowledge of OCaml you expect for a 3-starred project (i.e. medium difficulty)? > > Sorry for being pedantic, but I'm really interested in participating. > > Best regards, > > michele alberti > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Tue Feb 24 11:46:30 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 24 Feb 2015 11:46:30 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YQDwc-0006zC-23; Tue, 24 Feb 2015 11:46:30 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YQDwa-0006yt-5z for mirageos-devel@lists.xenproject.org; Tue, 24 Feb 2015 11:46:28 +0000 Received: from [85.158.137.68] by server-3.bemta-3.messagelabs.com id 38/30-02997-3946CE45; Tue, 24 Feb 2015 11:46:27 +0000 X-Env-Sender: amc79@cam.ac.uk X-Msg-Ref: server-11.tower-31.messagelabs.com!1424778384!11809851!1 X-Originating-IP: [131.111.8.151] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTMxLjExMS44LjE1MSA9PiAxNDE4OTU=\n X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20210 invoked from network); 24 Feb 2015 11:46:24 -0000 Received: from ppsw-51.csi.cam.ac.uk (HELO ppsw-51.csi.cam.ac.uk) (131.111.8.151) by server-11.tower-31.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 24 Feb 2015 11:46:24 -0000 X-Cam-AntiVirus: no malware found X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/ Received: from host81-149-102-120.in-addr.btopenworld.com ([81.149.102.120]:53498 helo=[10.0.0.143]) by ppsw-51.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.157]:587) with esmtpsa (PLAIN:amc79) (TLSv1:AES128-SHA:128) id 1YQDwW-0005A6-XN (Exim 4.82_3-c0e5623) for mirageos-devel@lists.xenproject.org (return-path ); Tue, 24 Feb 2015 11:46:24 +0000 From: Amir Chaudhry Message-Id: Date: Tue, 24 Feb 2015 11:46:26 +0000 To: "mirageos-devel@lists.xenproject.org" Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) X-Mailer: Apple Mail (2.1510) Subject: [MirageOS-devel] Mirage fortnightly call - Wednesday 25th at 4pm GMT X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: quoted-printable Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org Hi folks, The next Mirage call will take place this Wednesday afternoon at 4pm GMT an= d is open to all. Notes from last time are up at http://openmirage.org/wiki/weekly-2015-02-11 = The agenda is currently as follows: =95 mirage-net-xen 1.3.0 dead-lock/race (see https://github.com/mirage/mira= ge-net-xen/issues/20) =95 Quality and Test Infra =95 Automate all the things =95 Mirage.io =95 Irmin progress =95 Pioneer Projects =95 3.0 Planning If you have things to add/edit, please do so at https://github.com/mirage/m= irage-www/wiki/Call-Agenda GoToMeeting details are below but if there are any hiccups/delays then I'll= switch to a public Google Hangout. If that happens, I'll post the link he= re and also in the IRC channel (#mirage on freenode). Join us at 4pm GMT on Wednesday! 1. Please join my meeting. https://www1.gotomeeting.com/join/591890401 Dial in numbers (ask if you need a specific country): United Kingdom: +44 (0) 20 3657 6778 United States: +1 (213) 493-0014 Access Code: 591-890-401 Audio PIN: Shown after joining the meeting Best wishes, Amir _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Tue Feb 24 11:46:30 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 24 Feb 2015 11:46:30 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YQDwc-0006zC-23; Tue, 24 Feb 2015 11:46:30 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YQDwa-0006yt-5z for mirageos-devel@lists.xenproject.org; Tue, 24 Feb 2015 11:46:28 +0000 Received: from [85.158.137.68] by server-3.bemta-3.messagelabs.com id 38/30-02997-3946CE45; Tue, 24 Feb 2015 11:46:27 +0000 X-Env-Sender: amc79@cam.ac.uk X-Msg-Ref: server-11.tower-31.messagelabs.com!1424778384!11809851!1 X-Originating-IP: [131.111.8.151] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTMxLjExMS44LjE1MSA9PiAxNDE4OTU=\n X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20210 invoked from network); 24 Feb 2015 11:46:24 -0000 Received: from ppsw-51.csi.cam.ac.uk (HELO ppsw-51.csi.cam.ac.uk) (131.111.8.151) by server-11.tower-31.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 24 Feb 2015 11:46:24 -0000 X-Cam-AntiVirus: no malware found X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/ Received: from host81-149-102-120.in-addr.btopenworld.com ([81.149.102.120]:53498 helo=[10.0.0.143]) by ppsw-51.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.157]:587) with esmtpsa (PLAIN:amc79) (TLSv1:AES128-SHA:128) id 1YQDwW-0005A6-XN (Exim 4.82_3-c0e5623) for mirageos-devel@lists.xenproject.org (return-path ); Tue, 24 Feb 2015 11:46:24 +0000 From: Amir Chaudhry Message-Id: Date: Tue, 24 Feb 2015 11:46:26 +0000 To: "mirageos-devel@lists.xenproject.org" Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) X-Mailer: Apple Mail (2.1510) Subject: [MirageOS-devel] Mirage fortnightly call - Wednesday 25th at 4pm GMT X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: quoted-printable Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org Hi folks, The next Mirage call will take place this Wednesday afternoon at 4pm GMT an= d is open to all. Notes from last time are up at http://openmirage.org/wiki/weekly-2015-02-11 = The agenda is currently as follows: =95 mirage-net-xen 1.3.0 dead-lock/race (see https://github.com/mirage/mira= ge-net-xen/issues/20) =95 Quality and Test Infra =95 Automate all the things =95 Mirage.io =95 Irmin progress =95 Pioneer Projects =95 3.0 Planning If you have things to add/edit, please do so at https://github.com/mirage/m= irage-www/wiki/Call-Agenda GoToMeeting details are below but if there are any hiccups/delays then I'll= switch to a public Google Hangout. If that happens, I'll post the link he= re and also in the IRC channel (#mirage on freenode). Join us at 4pm GMT on Wednesday! 1. Please join my meeting. https://www1.gotomeeting.com/join/591890401 Dial in numbers (ask if you need a specific country): United Kingdom: +44 (0) 20 3657 6778 United States: +1 (213) 493-0014 Access Code: 591-890-401 Audio PIN: Shown after joining the meeting Best wishes, Amir _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Tue Feb 24 11:49:36 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 24 Feb 2015 11:49:36 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YQDzc-00077g-D5; Tue, 24 Feb 2015 11:49:36 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YQDza-00077R-Fp for mirageos-devel@lists.xenproject.org; Tue, 24 Feb 2015 11:49:34 +0000 Received: from [193.109.254.147] by server-3.bemta-14.messagelabs.com id 18/1E-10964-D456CE45; Tue, 24 Feb 2015 11:49:33 +0000 X-Env-Sender: robin@badgermind.net X-Msg-Ref: server-6.tower-27.messagelabs.com!1424778572!12432934!1 X-Originating-IP: [66.111.4.25] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTExLjQuMjUgPT4gNDQ5ODE=\n X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 24760 invoked from network); 24 Feb 2015 11:49:32 -0000 Received: from out1-smtp.messagingengine.com (HELO out1-smtp.messagingengine.com) (66.111.4.25) by server-6.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 24 Feb 2015 11:49:32 -0000 Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 08EFB20751 for ; Tue, 24 Feb 2015 06:49:31 -0500 (EST) Received: from frontend1 ([10.202.2.160]) by compute6.internal (MEProxy); Tue, 24 Feb 2015 06:49:31 -0500 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=badgermind.net; h= x-sasl-enc:subject:mime-version:content-type:from:in-reply-to :date:cc:content-transfer-encoding:message-id:references:to; s= mesmtp; bh=S0+hii6s84tZuYUi6CiO0wpP2r8=; b=de4U5d9MlViOu6e6uJkfz OlFBmBf/Wb/wBfmHJnXR3Zw11+9vuUYSe3hUeUo66h6ZdyTfpKWF3x9ua3FMvxhb iCycEEnDeBRx0tDDC1GKTLWRIPPf5LmcIijiokD9qHdJy+CclnM9FaTTJKR80yjC VU2N/3QjEyCGMfc0Ybopgk= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=x-sasl-enc:subject:mime-version :content-type:from:in-reply-to:date:cc:content-transfer-encoding :message-id:references:to; s=smtpout; bh=S0+hii6s84tZuYUi6CiO0wp P2r8=; b=kNMAICbtav4dATdm+SUB4irAXjaC2FhoyFUfPJNFVKSLPsU2X7T1kPI QhElOHCbGvTTD2htbSM7EdLYyLWACbmwV6vnmPu7Kj5640m2EvQ9evETHMSqzLE5 ZAnjHRCdQx+RLz2qH4J8o0RiYOQP+scvTOiSGECth9qLq6r1qFhM= X-Sasl-enc: u3iq6VyE1I15cWnL19ebtTChPApUovK+qIkMivKovIjf 1424778571 Received: from robintaorsmbp17.lan (unknown [81.187.18.99]) by mail.messagingengine.com (Postfix) with ESMTPA id 561A7C002A3; Tue, 24 Feb 2015 06:49:30 -0500 (EST) Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Robin Taylor In-Reply-To: Date: Tue, 24 Feb 2015 11:49:28 +0000 Message-Id: <17F3E677-EB2E-4465-B213-B1C682F33C21@badgermind.net> References: To: Amir Chaudhry X-Mailer: Apple Mail (2.1878.6) Cc: Michele Alberti , mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Question about pioneer projects X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org Thanks Amir and Michele I'd been thinking of asking exactly the same question (although my experience is more F# than OCaml) Best wishes Robin On 24 Feb 2015, at 11:42, Amir Chaudhry wrote: > Hi Michele! > > Thanks for looking over the projects and getting in touch. > > It's an *excellent* question and it's one I've also been meaning to ask. :) > I think it would be useful for us to provide (on the page itself [1]) some idea of what each difficulty level entails. I'll bring that up in the next Mirage call [2] -- which anyone is welcome to join, by the way. > > In the meantime, if there are specific projects you're interested in perhaps we can discuss them here? > > (Links are mostly to remind others of their existence) > > [1] https://github.com/mirage/mirage-www/wiki/Pioneer-Projects > [2] https://github.com/mirage/mirage-www/wiki/Call-Agenda > > Best wishes, > Amir > > On 24 Feb 2015, at 11:10, Michele Alberti wrote: > >> Hello, >> >> First of all let me say that all the MirageOS idea and implementation sounds really great. >> >> Not so many years ago I used OCaml for a University CS project, and I've recently rediscovered it (RWO book). >> >> I'd love participating into a MirageOS related project to do some real work in OCaml, though I am a newcomer (even if I have a CS background). I've given a look at your projects github webpage and I must admit that they all are very cool. However, let me ask a question to see whether I can be a good fit: >> >> what is the working knowledge of OCaml you expect for a 3-starred project (i.e. medium difficulty)? >> >> Sorry for being pedantic, but I'm really interested in participating. >> >> Best regards, >> >> michele alberti >> _______________________________________________ >> MirageOS-devel mailing list >> MirageOS-devel@lists.xenproject.org >> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > > > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Tue Feb 24 11:49:36 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 24 Feb 2015 11:49:36 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YQDzc-00077g-D5; Tue, 24 Feb 2015 11:49:36 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YQDza-00077R-Fp for mirageos-devel@lists.xenproject.org; Tue, 24 Feb 2015 11:49:34 +0000 Received: from [193.109.254.147] by server-3.bemta-14.messagelabs.com id 18/1E-10964-D456CE45; Tue, 24 Feb 2015 11:49:33 +0000 X-Env-Sender: robin@badgermind.net X-Msg-Ref: server-6.tower-27.messagelabs.com!1424778572!12432934!1 X-Originating-IP: [66.111.4.25] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTExLjQuMjUgPT4gNDQ5ODE=\n X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 24760 invoked from network); 24 Feb 2015 11:49:32 -0000 Received: from out1-smtp.messagingengine.com (HELO out1-smtp.messagingengine.com) (66.111.4.25) by server-6.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 24 Feb 2015 11:49:32 -0000 Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 08EFB20751 for ; Tue, 24 Feb 2015 06:49:31 -0500 (EST) Received: from frontend1 ([10.202.2.160]) by compute6.internal (MEProxy); Tue, 24 Feb 2015 06:49:31 -0500 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=badgermind.net; h= x-sasl-enc:subject:mime-version:content-type:from:in-reply-to :date:cc:content-transfer-encoding:message-id:references:to; s= mesmtp; bh=S0+hii6s84tZuYUi6CiO0wpP2r8=; b=de4U5d9MlViOu6e6uJkfz OlFBmBf/Wb/wBfmHJnXR3Zw11+9vuUYSe3hUeUo66h6ZdyTfpKWF3x9ua3FMvxhb iCycEEnDeBRx0tDDC1GKTLWRIPPf5LmcIijiokD9qHdJy+CclnM9FaTTJKR80yjC VU2N/3QjEyCGMfc0Ybopgk= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=x-sasl-enc:subject:mime-version :content-type:from:in-reply-to:date:cc:content-transfer-encoding :message-id:references:to; s=smtpout; bh=S0+hii6s84tZuYUi6CiO0wp P2r8=; b=kNMAICbtav4dATdm+SUB4irAXjaC2FhoyFUfPJNFVKSLPsU2X7T1kPI QhElOHCbGvTTD2htbSM7EdLYyLWACbmwV6vnmPu7Kj5640m2EvQ9evETHMSqzLE5 ZAnjHRCdQx+RLz2qH4J8o0RiYOQP+scvTOiSGECth9qLq6r1qFhM= X-Sasl-enc: u3iq6VyE1I15cWnL19ebtTChPApUovK+qIkMivKovIjf 1424778571 Received: from robintaorsmbp17.lan (unknown [81.187.18.99]) by mail.messagingengine.com (Postfix) with ESMTPA id 561A7C002A3; Tue, 24 Feb 2015 06:49:30 -0500 (EST) Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Robin Taylor In-Reply-To: Date: Tue, 24 Feb 2015 11:49:28 +0000 Message-Id: <17F3E677-EB2E-4465-B213-B1C682F33C21@badgermind.net> References: To: Amir Chaudhry X-Mailer: Apple Mail (2.1878.6) Cc: Michele Alberti , mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Question about pioneer projects X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org Thanks Amir and Michele I'd been thinking of asking exactly the same question (although my experience is more F# than OCaml) Best wishes Robin On 24 Feb 2015, at 11:42, Amir Chaudhry wrote: > Hi Michele! > > Thanks for looking over the projects and getting in touch. > > It's an *excellent* question and it's one I've also been meaning to ask. :) > I think it would be useful for us to provide (on the page itself [1]) some idea of what each difficulty level entails. I'll bring that up in the next Mirage call [2] -- which anyone is welcome to join, by the way. > > In the meantime, if there are specific projects you're interested in perhaps we can discuss them here? > > (Links are mostly to remind others of their existence) > > [1] https://github.com/mirage/mirage-www/wiki/Pioneer-Projects > [2] https://github.com/mirage/mirage-www/wiki/Call-Agenda > > Best wishes, > Amir > > On 24 Feb 2015, at 11:10, Michele Alberti wrote: > >> Hello, >> >> First of all let me say that all the MirageOS idea and implementation sounds really great. >> >> Not so many years ago I used OCaml for a University CS project, and I've recently rediscovered it (RWO book). >> >> I'd love participating into a MirageOS related project to do some real work in OCaml, though I am a newcomer (even if I have a CS background). I've given a look at your projects github webpage and I must admit that they all are very cool. However, let me ask a question to see whether I can be a good fit: >> >> what is the working knowledge of OCaml you expect for a 3-starred project (i.e. medium difficulty)? >> >> Sorry for being pedantic, but I'm really interested in participating. >> >> Best regards, >> >> michele alberti >> _______________________________________________ >> MirageOS-devel mailing list >> MirageOS-devel@lists.xenproject.org >> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > > > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Tue Feb 24 11:54:17 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 24 Feb 2015 11:54:17 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YQE48-0008LY-JN; Tue, 24 Feb 2015 11:54:16 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YQE47-0008LT-3j for mirageos-devel@lists.xenproject.org; Tue, 24 Feb 2015 11:54:15 +0000 Received: from [85.158.137.68] by server-17.bemta-3.messagelabs.com id FF/7F-02896-6666CE45; Tue, 24 Feb 2015 11:54:14 +0000 X-Env-Sender: matthew.thomas.gray@gmail.com X-Msg-Ref: server-11.tower-31.messagelabs.com!1424778852!11812924!1 X-Originating-IP: [209.85.192.47] X-SpamReason: No, hits=0.7 required=7.0 tests=HTML_30_40,HTML_MESSAGE, MAILTO_TO_SPAM_ADDR,RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10864 invoked from network); 24 Feb 2015 11:54:12 -0000 Received: from mail-qg0-f47.google.com (HELO mail-qg0-f47.google.com) (209.85.192.47) by server-11.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 24 Feb 2015 11:54:12 -0000 Received: by mail-qg0-f47.google.com with SMTP id q107so29442819qgd.6 for ; Tue, 24 Feb 2015 03:54:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=wHzw3kjYNwfG4upvAet9Mn02n47ySS2kfDZdJqzE8W8=; b=LvYhE7YKVYJoEbKQm+W5u+CfRJg6WmmI/7ulxwNEw11u3Akx/mIO2/kTt3sL0A0uy/ 7ODuV1pbExuAHzHNJzPMQRZSX2cTj0q6g4ghXQqKwtl8fNKVksUFjLupm8YaCVmqYq/9 4SqUYP6t6d8awJTn9RUubyUxkdCUdcks1cJ3xmoZrnBRZt3B3SIkXIsY4LABvOHWsd3s NKx/h3eZzd9QPPKtDRm4Vr9tThxpOGW9pem8upxg31ho0+zVbBvueKd2rMd+UrwehMpI l2of06Kw1X9waqApTooy+KgqbW6X5gNdXPr9cn75PYj0cxcKdE/xcXByoQ9Rl8EQwGIj MPqQ== MIME-Version: 1.0 X-Received: by 10.140.48.133 with SMTP id o5mr34574833qga.8.1424778851879; Tue, 24 Feb 2015 03:54:11 -0800 (PST) Received: by 10.140.46.168 with HTTP; Tue, 24 Feb 2015 03:54:11 -0800 (PST) In-Reply-To: <17F3E677-EB2E-4465-B213-B1C682F33C21@badgermind.net> References: <17F3E677-EB2E-4465-B213-B1C682F33C21@badgermind.net> Date: Tue, 24 Feb 2015 11:54:11 +0000 Message-ID: From: Matthew Gray To: Robin Taylor Cc: Michele Alberti , mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Question about pioneer projects X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1139791385877962437==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============1139791385877962437== Content-Type: multipart/alternative; boundary=001a11351808599118050fd42dc6 --001a11351808599118050fd42dc6 Content-Type: text/plain; charset=UTF-8 And me! New to OCaml, but keen to learn more and contribute to MirageOS if I can. Matt On Tue, Feb 24, 2015 at 11:49 AM, Robin Taylor wrote: > Thanks Amir and Michele > > I'd been thinking of asking exactly the same question (although my > experience is more F# than OCaml) > > Best wishes > > Robin > > > On 24 Feb 2015, at 11:42, Amir Chaudhry wrote: > > > Hi Michele! > > > > Thanks for looking over the projects and getting in touch. > > > > It's an *excellent* question and it's one I've also been meaning to ask. > :) > > I think it would be useful for us to provide (on the page itself [1]) > some idea of what each difficulty level entails. I'll bring that up in the > next Mirage call [2] -- which anyone is welcome to join, by the way. > > > > In the meantime, if there are specific projects you're interested in > perhaps we can discuss them here? > > > > (Links are mostly to remind others of their existence) > > > > [1] https://github.com/mirage/mirage-www/wiki/Pioneer-Projects > > [2] https://github.com/mirage/mirage-www/wiki/Call-Agenda > > > > Best wishes, > > Amir > > > > On 24 Feb 2015, at 11:10, Michele Alberti wrote: > > > >> Hello, > >> > >> First of all let me say that all the MirageOS idea and implementation > sounds really great. > >> > >> Not so many years ago I used OCaml for a University CS project, and > I've recently rediscovered it (RWO book). > >> > >> I'd love participating into a MirageOS related project to do some real > work in OCaml, though I am a newcomer (even if I have a CS background). > I've given a look at your projects github webpage and I must admit that > they all are very cool. However, let me ask a question to see whether I can > be a good fit: > >> > >> what is the working knowledge of OCaml you expect for a 3-starred > project (i.e. medium difficulty)? > >> > >> Sorry for being pedantic, but I'm really interested in participating. > >> > >> Best regards, > >> > >> michele alberti > >> _______________________________________________ > >> MirageOS-devel mailing list > >> MirageOS-devel@lists.xenproject.org > >> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > > > > > > _______________________________________________ > > MirageOS-devel mailing list > > MirageOS-devel@lists.xenproject.org > > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > > > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > --001a11351808599118050fd42dc6 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
And me! New to OCaml, but keen to learn more and contribut= e to MirageOS if I can.

Matt

On Tue, Feb 24, 2015 at 11:49 AM,= Robin Taylor <robin@badgermind.net> wrote:
Thanks Amir and Michele

I'd been thinking of asking exactly the same question (although my expe= rience is more F# than OCaml)

Best wishes

Robin


On 24 Feb 2015, at 11:42, Amir Chaudhry <amc79@cam.ac.uk> wrote:

> Hi Michele!
>
> Thanks for looking over the projects and getting in touch.
>
> It's an *excellent* question and it's one I've also been m= eaning to ask. :)
> I think it would be useful for us to provide (on the page itself [1]) = some idea of what each difficulty level entails.=C2=A0 I'll bring that = up in the next Mirage call [2] -- which anyone is welcome to join, by the w= ay.
>
> In the meantime, if there are specific projects you're interested = in perhaps we can discuss them here?
>
> (Links are mostly to remind others of their existence)
>
> [1] https://github.com/mirage/mirage-www/wiki/Pioneer-Pr= ojects
> [2] https://github.com/mirage/mirage-www/wiki/Call-Agenda=
>
> Best wishes,
> Amir
>
> On 24 Feb 2015, at 11:10, Michele Alberti <mic.alberti@gmail.com> wrote:
>
>> Hello,
>>
>> First of all let me say that all the MirageOS idea and implementat= ion sounds really great.
>>
>> Not so many years ago I used OCaml for a University CS project, an= d I've recently rediscovered it (RWO book).
>>
>> I'd love participating into a MirageOS related project to do s= ome real work in OCaml, though I am a newcomer (even if I have a CS backgro= und). I've given a look at your projects github webpage and I must admi= t that they all are very cool. However, let me ask a question to see whethe= r I can be a good fit:
>>
>> what is the working knowledge of OCaml you expect for a 3-starred = project (i.e. medium difficulty)?
>>
>> Sorry for being pedantic, but I'm really interested in partici= pating.
>>
>> Best regards,
>>
>> michele alberti
>> _______________________________________________
>> MirageOS-devel mailing list
>> MirageOS-de= vel@lists.xenproject.org
>> http://lists.xenproject.org/cgi-bin/mailman= /listinfo/mirageos-devel
>
>
> _______________________________________________
> MirageOS-devel mailing list
> MirageOS-devel@= lists.xenproject.org
> http://lists.xenproject.org/cgi-bin/mailman/lis= tinfo/mirageos-devel


_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists= .xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo= /mirageos-devel

--001a11351808599118050fd42dc6-- --===============1139791385877962437== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --===============1139791385877962437==-- From mirageos-devel-bounces@lists.xenproject.org Tue Feb 24 11:54:17 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 24 Feb 2015 11:54:17 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YQE48-0008LY-JN; Tue, 24 Feb 2015 11:54:16 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YQE47-0008LT-3j for mirageos-devel@lists.xenproject.org; Tue, 24 Feb 2015 11:54:15 +0000 Received: from [85.158.137.68] by server-17.bemta-3.messagelabs.com id FF/7F-02896-6666CE45; Tue, 24 Feb 2015 11:54:14 +0000 X-Env-Sender: matthew.thomas.gray@gmail.com X-Msg-Ref: server-11.tower-31.messagelabs.com!1424778852!11812924!1 X-Originating-IP: [209.85.192.47] X-SpamReason: No, hits=0.7 required=7.0 tests=HTML_30_40,HTML_MESSAGE, MAILTO_TO_SPAM_ADDR,RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10864 invoked from network); 24 Feb 2015 11:54:12 -0000 Received: from mail-qg0-f47.google.com (HELO mail-qg0-f47.google.com) (209.85.192.47) by server-11.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 24 Feb 2015 11:54:12 -0000 Received: by mail-qg0-f47.google.com with SMTP id q107so29442819qgd.6 for ; Tue, 24 Feb 2015 03:54:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=wHzw3kjYNwfG4upvAet9Mn02n47ySS2kfDZdJqzE8W8=; b=LvYhE7YKVYJoEbKQm+W5u+CfRJg6WmmI/7ulxwNEw11u3Akx/mIO2/kTt3sL0A0uy/ 7ODuV1pbExuAHzHNJzPMQRZSX2cTj0q6g4ghXQqKwtl8fNKVksUFjLupm8YaCVmqYq/9 4SqUYP6t6d8awJTn9RUubyUxkdCUdcks1cJ3xmoZrnBRZt3B3SIkXIsY4LABvOHWsd3s NKx/h3eZzd9QPPKtDRm4Vr9tThxpOGW9pem8upxg31ho0+zVbBvueKd2rMd+UrwehMpI l2of06Kw1X9waqApTooy+KgqbW6X5gNdXPr9cn75PYj0cxcKdE/xcXByoQ9Rl8EQwGIj MPqQ== MIME-Version: 1.0 X-Received: by 10.140.48.133 with SMTP id o5mr34574833qga.8.1424778851879; Tue, 24 Feb 2015 03:54:11 -0800 (PST) Received: by 10.140.46.168 with HTTP; Tue, 24 Feb 2015 03:54:11 -0800 (PST) In-Reply-To: <17F3E677-EB2E-4465-B213-B1C682F33C21@badgermind.net> References: <17F3E677-EB2E-4465-B213-B1C682F33C21@badgermind.net> Date: Tue, 24 Feb 2015 11:54:11 +0000 Message-ID: From: Matthew Gray To: Robin Taylor Cc: Michele Alberti , mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Question about pioneer projects X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1139791385877962437==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============1139791385877962437== Content-Type: multipart/alternative; boundary=001a11351808599118050fd42dc6 --001a11351808599118050fd42dc6 Content-Type: text/plain; charset=UTF-8 And me! New to OCaml, but keen to learn more and contribute to MirageOS if I can. Matt On Tue, Feb 24, 2015 at 11:49 AM, Robin Taylor wrote: > Thanks Amir and Michele > > I'd been thinking of asking exactly the same question (although my > experience is more F# than OCaml) > > Best wishes > > Robin > > > On 24 Feb 2015, at 11:42, Amir Chaudhry wrote: > > > Hi Michele! > > > > Thanks for looking over the projects and getting in touch. > > > > It's an *excellent* question and it's one I've also been meaning to ask. > :) > > I think it would be useful for us to provide (on the page itself [1]) > some idea of what each difficulty level entails. I'll bring that up in the > next Mirage call [2] -- which anyone is welcome to join, by the way. > > > > In the meantime, if there are specific projects you're interested in > perhaps we can discuss them here? > > > > (Links are mostly to remind others of their existence) > > > > [1] https://github.com/mirage/mirage-www/wiki/Pioneer-Projects > > [2] https://github.com/mirage/mirage-www/wiki/Call-Agenda > > > > Best wishes, > > Amir > > > > On 24 Feb 2015, at 11:10, Michele Alberti wrote: > > > >> Hello, > >> > >> First of all let me say that all the MirageOS idea and implementation > sounds really great. > >> > >> Not so many years ago I used OCaml for a University CS project, and > I've recently rediscovered it (RWO book). > >> > >> I'd love participating into a MirageOS related project to do some real > work in OCaml, though I am a newcomer (even if I have a CS background). > I've given a look at your projects github webpage and I must admit that > they all are very cool. However, let me ask a question to see whether I can > be a good fit: > >> > >> what is the working knowledge of OCaml you expect for a 3-starred > project (i.e. medium difficulty)? > >> > >> Sorry for being pedantic, but I'm really interested in participating. > >> > >> Best regards, > >> > >> michele alberti > >> _______________________________________________ > >> MirageOS-devel mailing list > >> MirageOS-devel@lists.xenproject.org > >> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > > > > > > _______________________________________________ > > MirageOS-devel mailing list > > MirageOS-devel@lists.xenproject.org > > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > > > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > --001a11351808599118050fd42dc6 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
And me! New to OCaml, but keen to learn more and contribut= e to MirageOS if I can.

Matt

On Tue, Feb 24, 2015 at 11:49 AM,= Robin Taylor <robin@badgermind.net> wrote:
Thanks Amir and Michele

I'd been thinking of asking exactly the same question (although my expe= rience is more F# than OCaml)

Best wishes

Robin


On 24 Feb 2015, at 11:42, Amir Chaudhry <amc79@cam.ac.uk> wrote:

> Hi Michele!
>
> Thanks for looking over the projects and getting in touch.
>
> It's an *excellent* question and it's one I've also been m= eaning to ask. :)
> I think it would be useful for us to provide (on the page itself [1]) = some idea of what each difficulty level entails.=C2=A0 I'll bring that = up in the next Mirage call [2] -- which anyone is welcome to join, by the w= ay.
>
> In the meantime, if there are specific projects you're interested = in perhaps we can discuss them here?
>
> (Links are mostly to remind others of their existence)
>
> [1] https://github.com/mirage/mirage-www/wiki/Pioneer-Pr= ojects
> [2] https://github.com/mirage/mirage-www/wiki/Call-Agenda=
>
> Best wishes,
> Amir
>
> On 24 Feb 2015, at 11:10, Michele Alberti <mic.alberti@gmail.com> wrote:
>
>> Hello,
>>
>> First of all let me say that all the MirageOS idea and implementat= ion sounds really great.
>>
>> Not so many years ago I used OCaml for a University CS project, an= d I've recently rediscovered it (RWO book).
>>
>> I'd love participating into a MirageOS related project to do s= ome real work in OCaml, though I am a newcomer (even if I have a CS backgro= und). I've given a look at your projects github webpage and I must admi= t that they all are very cool. However, let me ask a question to see whethe= r I can be a good fit:
>>
>> what is the working knowledge of OCaml you expect for a 3-starred = project (i.e. medium difficulty)?
>>
>> Sorry for being pedantic, but I'm really interested in partici= pating.
>>
>> Best regards,
>>
>> michele alberti
>> _______________________________________________
>> MirageOS-devel mailing list
>> MirageOS-de= vel@lists.xenproject.org
>> http://lists.xenproject.org/cgi-bin/mailman= /listinfo/mirageos-devel
>
>
> _______________________________________________
> MirageOS-devel mailing list
> MirageOS-devel@= lists.xenproject.org
> http://lists.xenproject.org/cgi-bin/mailman/lis= tinfo/mirageos-devel


_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists= .xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo= /mirageos-devel

--001a11351808599118050fd42dc6-- --===============1139791385877962437== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --===============1139791385877962437==-- From mirageos-devel-bounces@lists.xenproject.org Tue Feb 24 12:44:17 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 24 Feb 2015 12:44:17 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YQEqT-0005Il-LY; Tue, 24 Feb 2015 12:44:13 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YQEqS-0005Id-9n for mirageos-devel@lists.xenproject.org; Tue, 24 Feb 2015 12:44:12 +0000 Received: from [85.158.137.68] by server-9.bemta-3.messagelabs.com id B2/1E-02995-B127CE45; Tue, 24 Feb 2015 12:44:11 +0000 X-Env-Sender: gtsiour@softlab.ntua.gr X-Msg-Ref: server-9.tower-31.messagelabs.com!1424781850!8090290!1 X-Originating-IP: [147.102.222.220] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 19337 invoked from network); 24 Feb 2015 12:44:10 -0000 Received: from diomedes.noc.ntua.gr (HELO diomedes.noc.ntua.gr) (147.102.222.220) by server-9.tower-31.messagelabs.com with SMTP; 24 Feb 2015 12:44:10 -0000 Received: from lazy.softlab.ece.ntua.gr (lazy.softlab.ece.ntua.gr [IPv6:2001:648:2000:1::6] (may be forged)) by diomedes.noc.ntua.gr (8.14.5/8.14.5) with ESMTP id t1OCi63x000681 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 24 Feb 2015 14:44:06 +0200 (EET) (envelope-from gtsiour@softlab.ntua.gr) Received: from n0de (conf-nat.admin.grnet.gr [195.251.28.254]) (authenticated bits=0) by lazy.softlab.ece.ntua.gr (8.14.3/8.14.3/Debian-9.4) with ESMTP id t1OCi5fU016715 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Tue, 24 Feb 2015 14:44:05 +0200 Date: Tue, 24 Feb 2015 14:44:00 +0200 From: Yiannis Tsiouris To: Matthew Gray Message-ID: <20150224144400.54f84a44@n0de> In-Reply-To: References: <17F3E677-EB2E-4465-B213-B1C682F33C21@badgermind.net> X-Mailer: Claws Mail 3.11.1 (GTK+ 2.24.25; x86_64-pc-linux-gnu) MIME-Version: 1.0 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (diomedes.noc.ntua.gr [IPv6:2001:648:2000:de::220]); Tue, 24 Feb 2015 14:44:06 +0200 (EET) X-Virus-Scanned: clamav-milter 0.97.5 at diomedes.noc.ntua.gr X-Virus-Status: Clean Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Question about pioneer projects X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============3147015882436223843==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============3147015882436223843== Content-Type: multipart/signed; micalg=pgp-sha512; boundary="Sig_/UxKENrG.l_hS9tx3joNsW2O"; protocol="application/pgp-signature" --Sig_/UxKENrG.l_hS9tx3joNsW2O Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Tue, 24 Feb 2015 11:54:11 +0000 Matthew Gray wrote: > And me! New to OCaml, but keen to learn more and contribute to MirageOS if > I can. +1 guys! Cheers! -yiannis --Sig_/UxKENrG.l_hS9tx3joNsW2O Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iQIcBAEBCgAGBQJU7HIVAAoJEC0qeiNZHf+xYgcP/2akiNzzZPTFKME3Ll0DB0Lu 1irvkO8yeg6RQEpv2qlXpM6UNdvXHp9B2XFocGPHzibu2z7teF6b8X62NuzfdQQm JiNaaZusSqL6BbUZMBZOd2ZSOxEKgPrAXK3tjRtjxItkASQyvnCNrMypN7UymXi4 JCJyF+tX0O7Pg8jh5NVJYnwVq0N6gpznDvYrkWYvtJ0UDO/5h1TILLKU0LMXhQL9 oK8VpWT8vL4EHyBsAq0o2y7pCT2Tu+wXrLqS6x9c1y5sOF8pInHs1PlPfPUIctdy Z5wWp2VQm4E6JWAcg4o6GU5ar3fXFvn8HVFJfDLBOyztSiTDMgA5MdR+OEOFC4dQ L6Y9fEC58Uoxdw89/ssYfvBNciSQEvuI7mRx1MFA+vWoRH08occqGA45QiyJ7g/o DBnCQIkgSm39RSVqzKT/xbdPv9Hqokc9cKj+anJiY3Xx3jZsgyyoJNSfve0EIl6j KxEM3luGSbpR9ysgs5hq92/yiPHUElMKyJc31z3UWYpoxtrE/fYhaIxNKT98Pn/n YHONemo6bzllzJdIxuWAaqMVAWMKPD5TlXx8ENNhWQuLn56MrPEctvafQj2hDrgx 5ALb7wQ52xJAPcm4LP+8NZ4VGw7c6MtbgdiqmgETLZGbLY3+h/P4UOy/i9Sl3u/U iiFeXXDfJoluZPG9h5QQ =Ga0F -----END PGP SIGNATURE----- --Sig_/UxKENrG.l_hS9tx3joNsW2O-- --===============3147015882436223843== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --===============3147015882436223843==-- From mirageos-devel-bounces@lists.xenproject.org Tue Feb 24 12:44:17 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 24 Feb 2015 12:44:17 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YQEqT-0005Il-LY; Tue, 24 Feb 2015 12:44:13 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YQEqS-0005Id-9n for mirageos-devel@lists.xenproject.org; Tue, 24 Feb 2015 12:44:12 +0000 Received: from [85.158.137.68] by server-9.bemta-3.messagelabs.com id B2/1E-02995-B127CE45; Tue, 24 Feb 2015 12:44:11 +0000 X-Env-Sender: gtsiour@softlab.ntua.gr X-Msg-Ref: server-9.tower-31.messagelabs.com!1424781850!8090290!1 X-Originating-IP: [147.102.222.220] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 19337 invoked from network); 24 Feb 2015 12:44:10 -0000 Received: from diomedes.noc.ntua.gr (HELO diomedes.noc.ntua.gr) (147.102.222.220) by server-9.tower-31.messagelabs.com with SMTP; 24 Feb 2015 12:44:10 -0000 Received: from lazy.softlab.ece.ntua.gr (lazy.softlab.ece.ntua.gr [IPv6:2001:648:2000:1::6] (may be forged)) by diomedes.noc.ntua.gr (8.14.5/8.14.5) with ESMTP id t1OCi63x000681 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 24 Feb 2015 14:44:06 +0200 (EET) (envelope-from gtsiour@softlab.ntua.gr) Received: from n0de (conf-nat.admin.grnet.gr [195.251.28.254]) (authenticated bits=0) by lazy.softlab.ece.ntua.gr (8.14.3/8.14.3/Debian-9.4) with ESMTP id t1OCi5fU016715 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Tue, 24 Feb 2015 14:44:05 +0200 Date: Tue, 24 Feb 2015 14:44:00 +0200 From: Yiannis Tsiouris To: Matthew Gray Message-ID: <20150224144400.54f84a44@n0de> In-Reply-To: References: <17F3E677-EB2E-4465-B213-B1C682F33C21@badgermind.net> X-Mailer: Claws Mail 3.11.1 (GTK+ 2.24.25; x86_64-pc-linux-gnu) MIME-Version: 1.0 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (diomedes.noc.ntua.gr [IPv6:2001:648:2000:de::220]); Tue, 24 Feb 2015 14:44:06 +0200 (EET) X-Virus-Scanned: clamav-milter 0.97.5 at diomedes.noc.ntua.gr X-Virus-Status: Clean Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Question about pioneer projects X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============3147015882436223843==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============3147015882436223843== Content-Type: multipart/signed; micalg=pgp-sha512; boundary="Sig_/UxKENrG.l_hS9tx3joNsW2O"; protocol="application/pgp-signature" --Sig_/UxKENrG.l_hS9tx3joNsW2O Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Tue, 24 Feb 2015 11:54:11 +0000 Matthew Gray wrote: > And me! New to OCaml, but keen to learn more and contribute to MirageOS if > I can. +1 guys! Cheers! -yiannis --Sig_/UxKENrG.l_hS9tx3joNsW2O Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iQIcBAEBCgAGBQJU7HIVAAoJEC0qeiNZHf+xYgcP/2akiNzzZPTFKME3Ll0DB0Lu 1irvkO8yeg6RQEpv2qlXpM6UNdvXHp9B2XFocGPHzibu2z7teF6b8X62NuzfdQQm JiNaaZusSqL6BbUZMBZOd2ZSOxEKgPrAXK3tjRtjxItkASQyvnCNrMypN7UymXi4 JCJyF+tX0O7Pg8jh5NVJYnwVq0N6gpznDvYrkWYvtJ0UDO/5h1TILLKU0LMXhQL9 oK8VpWT8vL4EHyBsAq0o2y7pCT2Tu+wXrLqS6x9c1y5sOF8pInHs1PlPfPUIctdy Z5wWp2VQm4E6JWAcg4o6GU5ar3fXFvn8HVFJfDLBOyztSiTDMgA5MdR+OEOFC4dQ L6Y9fEC58Uoxdw89/ssYfvBNciSQEvuI7mRx1MFA+vWoRH08occqGA45QiyJ7g/o DBnCQIkgSm39RSVqzKT/xbdPv9Hqokc9cKj+anJiY3Xx3jZsgyyoJNSfve0EIl6j KxEM3luGSbpR9ysgs5hq92/yiPHUElMKyJc31z3UWYpoxtrE/fYhaIxNKT98Pn/n YHONemo6bzllzJdIxuWAaqMVAWMKPD5TlXx8ENNhWQuLn56MrPEctvafQj2hDrgx 5ALb7wQ52xJAPcm4LP+8NZ4VGw7c6MtbgdiqmgETLZGbLY3+h/P4UOy/i9Sl3u/U iiFeXXDfJoluZPG9h5QQ =Ga0F -----END PGP SIGNATURE----- --Sig_/UxKENrG.l_hS9tx3joNsW2O-- --===============3147015882436223843== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --===============3147015882436223843==-- From mirageos-devel-bounces@lists.xenproject.org Tue Feb 24 12:57:03 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 24 Feb 2015 12:57:03 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YQF2r-0006rI-Ak; Tue, 24 Feb 2015 12:57:01 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YQF2p-0006rD-8Z for mirageos-devel@lists.xenproject.org; Tue, 24 Feb 2015 12:56:59 +0000 Received: from [85.158.137.68] by server-6.bemta-3.messagelabs.com id 86/D4-03164-7157CE45; Tue, 24 Feb 2015 12:56:55 +0000 X-Env-Sender: antibra@hotmail.com X-Msg-Ref: server-11.tower-31.messagelabs.com!1424782613!11836099!1 X-Originating-IP: [65.55.116.77] X-SpamReason: No, hits=0.4 required=7.0 tests=FORGED_HOTMAIL_RCVD, MAILTO_TO_SPAM_ADDR X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21733 invoked from network); 24 Feb 2015 12:56:55 -0000 Received: from blu004-omc3s2.hotmail.com (HELO BLU004-OMC3S2.hotmail.com) (65.55.116.77) by server-11.tower-31.messagelabs.com with AES256-SHA encrypted SMTP; 24 Feb 2015 12:56:55 -0000 Received: from BLU436-SMTP78 ([65.55.116.73]) by BLU004-OMC3S2.hotmail.com over TLS secured channel with Microsoft SMTPSVC(7.5.7601.22751); Tue, 24 Feb 2015 04:56:53 -0800 X-TMN: [V27Oh2yaiSbyz7W4HmDLSkbt/vZHgM2I] X-Originating-Email: [antibra@hotmail.com] Message-ID: Date: Tue, 24 Feb 2015 14:56:37 +0200 From: yiorgos User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: mirageos-devel@lists.xenproject.org References: <17F3E677-EB2E-4465-B213-B1C682F33C21@badgermind.net> In-Reply-To: X-OriginalArrivalTime: 24 Feb 2015 12:56:51.0815 (UTC) FILETIME=[5BD68770:01D05031] Subject: Re: [MirageOS-devel] Question about pioneer projects X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org KzEhCgpJIGtub3cgYWJvdXQgdGhyZWUgd2F5cyBzZXQgdXAgYSBkZXZlbG9waW5nIE1pcmFnZU9T IGVudmlyb25tZW50LgoKMSkgVmlydHVhbEJveCArIFhlbiArIE1pcmFnZU9TIFZNcwoyKSBYZW4g b24gYmFyZSBtZXRhbAozKSBDdWJpZUJvYXJkICsgWGVuICsgTWlyYWdlT1MKCldheXMgMSwgMiBs b29rIG1vcmUgZWFzaWx5IGFjY2Vzc2libGUgdG8gcGVvcGxlLgoKQWJvdXQgMSkgRG8geW91IGd1 eXMgdGhpbmsgdGhhdApkZXZlbG9waW5nIGNhbiBiZSBkb25lIHVzaW5nIHRoaXMgd2F5IG9yIHRo ZXJlIHdpbGwgYmUgYSBxdWl0ZSBncmVhdAphbW91bnQgb2Ygc2V0dGluZyB1cC9kZWJ1Z2dpbmcg VmlydHVhbEJveCAoZWcgbmV0d29yayBpbnRlcmZhY2VzIGV0YykKCkFib3V0IDIpIERvIHlvdSBo YXZlIGEgcHJlZmVyYWJsZSBob3N0IE9TIGZvciBkb20wPwoKR3JlYXQgdGhhbmtzLAp5fi4KCk9u IDI0LzAyLzIwMTUgMDE6NTQgzrzOvCwgTWF0dGhldyBHcmF5IHdyb3RlOgo+IEFuZCBtZSEgTmV3 IHRvIE9DYW1sLCBidXQga2VlbiB0byBsZWFybiBtb3JlIGFuZCBjb250cmlidXRlIHRvIE1pcmFn ZU9TCj4gaWYgSSBjYW4uCj4gCj4gTWF0dAo+IAo+IE9uIFR1ZSwgRmViIDI0LCAyMDE1IGF0IDEx OjQ5IEFNLCBSb2JpbiBUYXlsb3IgPHJvYmluQGJhZGdlcm1pbmQubmV0Cj4gPG1haWx0bzpyb2Jp bkBiYWRnZXJtaW5kLm5ldD4+IHdyb3RlOgo+IAo+ICAgICBUaGFua3MgQW1pciBhbmQgTWljaGVs ZQo+IAo+ICAgICBJJ2QgYmVlbiB0aGlua2luZyBvZiBhc2tpbmcgZXhhY3RseSB0aGUgc2FtZSBx dWVzdGlvbiAoYWx0aG91Z2ggbXkKPiAgICAgZXhwZXJpZW5jZSBpcyBtb3JlIEYjIHRoYW4gT0Nh bWwpCj4gCj4gICAgIEJlc3Qgd2lzaGVzCj4gCj4gICAgIFJvYmluCj4gCj4gCj4gICAgIE9uIDI0 IEZlYiAyMDE1LCBhdCAxMTo0MiwgQW1pciBDaGF1ZGhyeSA8YW1jNzlAY2FtLmFjLnVrCj4gICAg IDxtYWlsdG86YW1jNzlAY2FtLmFjLnVrPj4gd3JvdGU6Cj4gCj4gICAgID4gSGkgTWljaGVsZSEK PiAgICAgPgo+ICAgICA+IFRoYW5rcyBmb3IgbG9va2luZyBvdmVyIHRoZSBwcm9qZWN0cyBhbmQg Z2V0dGluZyBpbiB0b3VjaC4KPiAgICAgPgo+ICAgICA+IEl0J3MgYW4gKmV4Y2VsbGVudCogcXVl c3Rpb24gYW5kIGl0J3Mgb25lIEkndmUgYWxzbyBiZWVuIG1lYW5pbmcKPiAgICAgdG8gYXNrLiA6 KQo+ICAgICA+IEkgdGhpbmsgaXQgd291bGQgYmUgdXNlZnVsIGZvciB1cyB0byBwcm92aWRlIChv biB0aGUgcGFnZSBpdHNlbGYKPiAgICAgWzFdKSBzb21lIGlkZWEgb2Ygd2hhdCBlYWNoIGRpZmZp Y3VsdHkgbGV2ZWwgZW50YWlscy4gIEknbGwgYnJpbmcKPiAgICAgdGhhdCB1cCBpbiB0aGUgbmV4 dCBNaXJhZ2UgY2FsbCBbMl0gLS0gd2hpY2ggYW55b25lIGlzIHdlbGNvbWUgdG8KPiAgICAgam9p biwgYnkgdGhlIHdheS4KPiAgICAgPgo+ICAgICA+IEluIHRoZSBtZWFudGltZSwgaWYgdGhlcmUg YXJlIHNwZWNpZmljIHByb2plY3RzIHlvdSdyZSBpbnRlcmVzdGVkCj4gICAgIGluIHBlcmhhcHMg d2UgY2FuIGRpc2N1c3MgdGhlbSBoZXJlPwo+ICAgICA+Cj4gICAgID4gKExpbmtzIGFyZSBtb3N0 bHkgdG8gcmVtaW5kIG90aGVycyBvZiB0aGVpciBleGlzdGVuY2UpCj4gICAgID4KPiAgICAgPiBb MV0gaHR0cHM6Ly9naXRodWIuY29tL21pcmFnZS9taXJhZ2Utd3d3L3dpa2kvUGlvbmVlci1Qcm9q ZWN0cwo+ICAgICA+IFsyXSBodHRwczovL2dpdGh1Yi5jb20vbWlyYWdlL21pcmFnZS13d3cvd2lr aS9DYWxsLUFnZW5kYQo+ICAgICA+Cj4gICAgID4gQmVzdCB3aXNoZXMsCj4gICAgID4gQW1pcgo+ ICAgICA+Cj4gICAgID4gT24gMjQgRmViIDIwMTUsIGF0IDExOjEwLCBNaWNoZWxlIEFsYmVydGkg PG1pYy5hbGJlcnRpQGdtYWlsLmNvbQo+ICAgICA8bWFpbHRvOm1pYy5hbGJlcnRpQGdtYWlsLmNv bT4+IHdyb3RlOgo+ICAgICA+Cj4gICAgID4+IEhlbGxvLAo+ICAgICA+Pgo+ICAgICA+PiBGaXJz dCBvZiBhbGwgbGV0IG1lIHNheSB0aGF0IGFsbCB0aGUgTWlyYWdlT1MgaWRlYSBhbmQKPiAgICAg aW1wbGVtZW50YXRpb24gc291bmRzIHJlYWxseSBncmVhdC4KPiAgICAgPj4KPiAgICAgPj4gTm90 IHNvIG1hbnkgeWVhcnMgYWdvIEkgdXNlZCBPQ2FtbCBmb3IgYSBVbml2ZXJzaXR5IENTIHByb2pl Y3QsCj4gICAgIGFuZCBJJ3ZlIHJlY2VudGx5IHJlZGlzY292ZXJlZCBpdCAoUldPIGJvb2spLgo+ ICAgICA+Pgo+ICAgICA+PiBJJ2QgbG92ZSBwYXJ0aWNpcGF0aW5nIGludG8gYSBNaXJhZ2VPUyBy ZWxhdGVkIHByb2plY3QgdG8gZG8gc29tZQo+ICAgICByZWFsIHdvcmsgaW4gT0NhbWwsIHRob3Vn aCBJIGFtIGEgbmV3Y29tZXIgKGV2ZW4gaWYgSSBoYXZlIGEgQ1MKPiAgICAgYmFja2dyb3VuZCku IEkndmUgZ2l2ZW4gYSBsb29rIGF0IHlvdXIgcHJvamVjdHMgZ2l0aHViIHdlYnBhZ2UgYW5kIEkK PiAgICAgbXVzdCBhZG1pdCB0aGF0IHRoZXkgYWxsIGFyZSB2ZXJ5IGNvb2wuIEhvd2V2ZXIsIGxl dCBtZSBhc2sgYQo+ICAgICBxdWVzdGlvbiB0byBzZWUgd2hldGhlciBJIGNhbiBiZSBhIGdvb2Qg Zml0Ogo+ICAgICA+Pgo+ICAgICA+PiB3aGF0IGlzIHRoZSB3b3JraW5nIGtub3dsZWRnZSBvZiBP Q2FtbCB5b3UgZXhwZWN0IGZvciBhIDMtc3RhcnJlZAo+ICAgICBwcm9qZWN0IChpLmUuIG1lZGl1 bSBkaWZmaWN1bHR5KT8KPiAgICAgPj4KPiAgICAgPj4gU29ycnkgZm9yIGJlaW5nIHBlZGFudGlj LCBidXQgSSdtIHJlYWxseSBpbnRlcmVzdGVkIGluIHBhcnRpY2lwYXRpbmcuCj4gICAgID4+Cj4g ICAgID4+IEJlc3QgcmVnYXJkcywKPiAgICAgPj4KPiAgICAgPj4gbWljaGVsZSBhbGJlcnRpCj4g ICAgID4+IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fCj4g IAo+IAoKLS0gCk1hcmluZWxsaXMsIFlpb3Jnb3MKCl9fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fCk1pcmFnZU9TLWRldmVsIG1haWxpbmcgbGlzdApNaXJhZ2VP Uy1kZXZlbEBsaXN0cy54ZW5wcm9qZWN0Lm9yZwpodHRwOi8vbGlzdHMueGVucHJvamVjdC5vcmcv Y2dpLWJpbi9tYWlsbWFuL2xpc3RpbmZvL21pcmFnZW9zLWRldmVsCg== From mirageos-devel-bounces@lists.xenproject.org Tue Feb 24 12:57:03 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 24 Feb 2015 12:57:03 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YQF2r-0006rI-Ak; Tue, 24 Feb 2015 12:57:01 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YQF2p-0006rD-8Z for mirageos-devel@lists.xenproject.org; Tue, 24 Feb 2015 12:56:59 +0000 Received: from [85.158.137.68] by server-6.bemta-3.messagelabs.com id 86/D4-03164-7157CE45; Tue, 24 Feb 2015 12:56:55 +0000 X-Env-Sender: antibra@hotmail.com X-Msg-Ref: server-11.tower-31.messagelabs.com!1424782613!11836099!1 X-Originating-IP: [65.55.116.77] X-SpamReason: No, hits=0.4 required=7.0 tests=FORGED_HOTMAIL_RCVD, MAILTO_TO_SPAM_ADDR X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21733 invoked from network); 24 Feb 2015 12:56:55 -0000 Received: from blu004-omc3s2.hotmail.com (HELO BLU004-OMC3S2.hotmail.com) (65.55.116.77) by server-11.tower-31.messagelabs.com with AES256-SHA encrypted SMTP; 24 Feb 2015 12:56:55 -0000 Received: from BLU436-SMTP78 ([65.55.116.73]) by BLU004-OMC3S2.hotmail.com over TLS secured channel with Microsoft SMTPSVC(7.5.7601.22751); Tue, 24 Feb 2015 04:56:53 -0800 X-TMN: [V27Oh2yaiSbyz7W4HmDLSkbt/vZHgM2I] X-Originating-Email: [antibra@hotmail.com] Message-ID: Date: Tue, 24 Feb 2015 14:56:37 +0200 From: yiorgos User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: mirageos-devel@lists.xenproject.org References: <17F3E677-EB2E-4465-B213-B1C682F33C21@badgermind.net> In-Reply-To: X-OriginalArrivalTime: 24 Feb 2015 12:56:51.0815 (UTC) FILETIME=[5BD68770:01D05031] Subject: Re: [MirageOS-devel] Question about pioneer projects X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org KzEhCgpJIGtub3cgYWJvdXQgdGhyZWUgd2F5cyBzZXQgdXAgYSBkZXZlbG9waW5nIE1pcmFnZU9T IGVudmlyb25tZW50LgoKMSkgVmlydHVhbEJveCArIFhlbiArIE1pcmFnZU9TIFZNcwoyKSBYZW4g b24gYmFyZSBtZXRhbAozKSBDdWJpZUJvYXJkICsgWGVuICsgTWlyYWdlT1MKCldheXMgMSwgMiBs b29rIG1vcmUgZWFzaWx5IGFjY2Vzc2libGUgdG8gcGVvcGxlLgoKQWJvdXQgMSkgRG8geW91IGd1 eXMgdGhpbmsgdGhhdApkZXZlbG9waW5nIGNhbiBiZSBkb25lIHVzaW5nIHRoaXMgd2F5IG9yIHRo ZXJlIHdpbGwgYmUgYSBxdWl0ZSBncmVhdAphbW91bnQgb2Ygc2V0dGluZyB1cC9kZWJ1Z2dpbmcg VmlydHVhbEJveCAoZWcgbmV0d29yayBpbnRlcmZhY2VzIGV0YykKCkFib3V0IDIpIERvIHlvdSBo YXZlIGEgcHJlZmVyYWJsZSBob3N0IE9TIGZvciBkb20wPwoKR3JlYXQgdGhhbmtzLAp5fi4KCk9u IDI0LzAyLzIwMTUgMDE6NTQgzrzOvCwgTWF0dGhldyBHcmF5IHdyb3RlOgo+IEFuZCBtZSEgTmV3 IHRvIE9DYW1sLCBidXQga2VlbiB0byBsZWFybiBtb3JlIGFuZCBjb250cmlidXRlIHRvIE1pcmFn ZU9TCj4gaWYgSSBjYW4uCj4gCj4gTWF0dAo+IAo+IE9uIFR1ZSwgRmViIDI0LCAyMDE1IGF0IDEx OjQ5IEFNLCBSb2JpbiBUYXlsb3IgPHJvYmluQGJhZGdlcm1pbmQubmV0Cj4gPG1haWx0bzpyb2Jp bkBiYWRnZXJtaW5kLm5ldD4+IHdyb3RlOgo+IAo+ICAgICBUaGFua3MgQW1pciBhbmQgTWljaGVs ZQo+IAo+ICAgICBJJ2QgYmVlbiB0aGlua2luZyBvZiBhc2tpbmcgZXhhY3RseSB0aGUgc2FtZSBx dWVzdGlvbiAoYWx0aG91Z2ggbXkKPiAgICAgZXhwZXJpZW5jZSBpcyBtb3JlIEYjIHRoYW4gT0Nh bWwpCj4gCj4gICAgIEJlc3Qgd2lzaGVzCj4gCj4gICAgIFJvYmluCj4gCj4gCj4gICAgIE9uIDI0 IEZlYiAyMDE1LCBhdCAxMTo0MiwgQW1pciBDaGF1ZGhyeSA8YW1jNzlAY2FtLmFjLnVrCj4gICAg IDxtYWlsdG86YW1jNzlAY2FtLmFjLnVrPj4gd3JvdGU6Cj4gCj4gICAgID4gSGkgTWljaGVsZSEK PiAgICAgPgo+ICAgICA+IFRoYW5rcyBmb3IgbG9va2luZyBvdmVyIHRoZSBwcm9qZWN0cyBhbmQg Z2V0dGluZyBpbiB0b3VjaC4KPiAgICAgPgo+ICAgICA+IEl0J3MgYW4gKmV4Y2VsbGVudCogcXVl c3Rpb24gYW5kIGl0J3Mgb25lIEkndmUgYWxzbyBiZWVuIG1lYW5pbmcKPiAgICAgdG8gYXNrLiA6 KQo+ICAgICA+IEkgdGhpbmsgaXQgd291bGQgYmUgdXNlZnVsIGZvciB1cyB0byBwcm92aWRlIChv biB0aGUgcGFnZSBpdHNlbGYKPiAgICAgWzFdKSBzb21lIGlkZWEgb2Ygd2hhdCBlYWNoIGRpZmZp Y3VsdHkgbGV2ZWwgZW50YWlscy4gIEknbGwgYnJpbmcKPiAgICAgdGhhdCB1cCBpbiB0aGUgbmV4 dCBNaXJhZ2UgY2FsbCBbMl0gLS0gd2hpY2ggYW55b25lIGlzIHdlbGNvbWUgdG8KPiAgICAgam9p biwgYnkgdGhlIHdheS4KPiAgICAgPgo+ICAgICA+IEluIHRoZSBtZWFudGltZSwgaWYgdGhlcmUg YXJlIHNwZWNpZmljIHByb2plY3RzIHlvdSdyZSBpbnRlcmVzdGVkCj4gICAgIGluIHBlcmhhcHMg d2UgY2FuIGRpc2N1c3MgdGhlbSBoZXJlPwo+ICAgICA+Cj4gICAgID4gKExpbmtzIGFyZSBtb3N0 bHkgdG8gcmVtaW5kIG90aGVycyBvZiB0aGVpciBleGlzdGVuY2UpCj4gICAgID4KPiAgICAgPiBb MV0gaHR0cHM6Ly9naXRodWIuY29tL21pcmFnZS9taXJhZ2Utd3d3L3dpa2kvUGlvbmVlci1Qcm9q ZWN0cwo+ICAgICA+IFsyXSBodHRwczovL2dpdGh1Yi5jb20vbWlyYWdlL21pcmFnZS13d3cvd2lr aS9DYWxsLUFnZW5kYQo+ICAgICA+Cj4gICAgID4gQmVzdCB3aXNoZXMsCj4gICAgID4gQW1pcgo+ ICAgICA+Cj4gICAgID4gT24gMjQgRmViIDIwMTUsIGF0IDExOjEwLCBNaWNoZWxlIEFsYmVydGkg PG1pYy5hbGJlcnRpQGdtYWlsLmNvbQo+ICAgICA8bWFpbHRvOm1pYy5hbGJlcnRpQGdtYWlsLmNv bT4+IHdyb3RlOgo+ICAgICA+Cj4gICAgID4+IEhlbGxvLAo+ICAgICA+Pgo+ICAgICA+PiBGaXJz dCBvZiBhbGwgbGV0IG1lIHNheSB0aGF0IGFsbCB0aGUgTWlyYWdlT1MgaWRlYSBhbmQKPiAgICAg aW1wbGVtZW50YXRpb24gc291bmRzIHJlYWxseSBncmVhdC4KPiAgICAgPj4KPiAgICAgPj4gTm90 IHNvIG1hbnkgeWVhcnMgYWdvIEkgdXNlZCBPQ2FtbCBmb3IgYSBVbml2ZXJzaXR5IENTIHByb2pl Y3QsCj4gICAgIGFuZCBJJ3ZlIHJlY2VudGx5IHJlZGlzY292ZXJlZCBpdCAoUldPIGJvb2spLgo+ ICAgICA+Pgo+ICAgICA+PiBJJ2QgbG92ZSBwYXJ0aWNpcGF0aW5nIGludG8gYSBNaXJhZ2VPUyBy ZWxhdGVkIHByb2plY3QgdG8gZG8gc29tZQo+ICAgICByZWFsIHdvcmsgaW4gT0NhbWwsIHRob3Vn aCBJIGFtIGEgbmV3Y29tZXIgKGV2ZW4gaWYgSSBoYXZlIGEgQ1MKPiAgICAgYmFja2dyb3VuZCku IEkndmUgZ2l2ZW4gYSBsb29rIGF0IHlvdXIgcHJvamVjdHMgZ2l0aHViIHdlYnBhZ2UgYW5kIEkK PiAgICAgbXVzdCBhZG1pdCB0aGF0IHRoZXkgYWxsIGFyZSB2ZXJ5IGNvb2wuIEhvd2V2ZXIsIGxl dCBtZSBhc2sgYQo+ICAgICBxdWVzdGlvbiB0byBzZWUgd2hldGhlciBJIGNhbiBiZSBhIGdvb2Qg Zml0Ogo+ICAgICA+Pgo+ICAgICA+PiB3aGF0IGlzIHRoZSB3b3JraW5nIGtub3dsZWRnZSBvZiBP Q2FtbCB5b3UgZXhwZWN0IGZvciBhIDMtc3RhcnJlZAo+ICAgICBwcm9qZWN0IChpLmUuIG1lZGl1 bSBkaWZmaWN1bHR5KT8KPiAgICAgPj4KPiAgICAgPj4gU29ycnkgZm9yIGJlaW5nIHBlZGFudGlj LCBidXQgSSdtIHJlYWxseSBpbnRlcmVzdGVkIGluIHBhcnRpY2lwYXRpbmcuCj4gICAgID4+Cj4g ICAgID4+IEJlc3QgcmVnYXJkcywKPiAgICAgPj4KPiAgICAgPj4gbWljaGVsZSBhbGJlcnRpCj4g ICAgID4+IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fCj4g IAo+IAoKLS0gCk1hcmluZWxsaXMsIFlpb3Jnb3MKCl9fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fCk1pcmFnZU9TLWRldmVsIG1haWxpbmcgbGlzdApNaXJhZ2VP Uy1kZXZlbEBsaXN0cy54ZW5wcm9qZWN0Lm9yZwpodHRwOi8vbGlzdHMueGVucHJvamVjdC5vcmcv Y2dpLWJpbi9tYWlsbWFuL2xpc3RpbmZvL21pcmFnZW9zLWRldmVsCg== From mirageos-devel-bounces@lists.xenproject.org Tue Feb 24 13:01:02 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 24 Feb 2015 13:01:02 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YQF6k-00078s-QV; Tue, 24 Feb 2015 13:01:02 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YQF6j-00078Y-53 for mirageos-devel@lists.xenproject.org; Tue, 24 Feb 2015 13:01:01 +0000 Received: from [85.158.143.35] by server-3.bemta-4.messagelabs.com id 0B/60-02791-C067CE45; Tue, 24 Feb 2015 13:01:00 +0000 X-Env-Sender: mic.alberti@gmail.com X-Msg-Ref: server-7.tower-21.messagelabs.com!1424782816!12820837!1 X-Originating-IP: [209.85.223.180] X-SpamReason: No, hits=0.9 required=7.0 tests=BODY_RANDOM_LONG, HTML_30_40,HTML_MESSAGE,RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2335 invoked from network); 24 Feb 2015 13:00:56 -0000 Received: from mail-ie0-f180.google.com (HELO mail-ie0-f180.google.com) (209.85.223.180) by server-7.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 24 Feb 2015 13:00:56 -0000 Received: by iecrl12 with SMTP id rl12so31659601iec.4 for ; Tue, 24 Feb 2015 05:00:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=zwGNf4+Ne/5OU30K7CdCPKBxvWi1W06FY1TkOiggohQ=; b=q7PXEpGMva1NfFdyMxoW0V0mvX/f9+3c63YPZlZzzpHJi5HUaSvAnh/kI2CXPMZuTl lIzMqsEllEXqFHNMLgJwMGKN6vD1o3PNOc0+TndHRPtfhsPTBA6nZxFtEaIsj1lklxU9 ibnMh92TYyScK12Cqh06TRy/W9Vu0Jtvyrzv1G6CZv2EvkXvTIem/nUkwIrKPgqt26kI HhCzMZsYIrmehRig93bRzQMeIZi6JsLgf91nWxRId5U4Z227t358uJPbnq4MubXa+ZKk gqy1FspNQPeU6XHBXXHOpvhlo/COilsXBNC4T0CkOzIJSYohEA7Un3sE+WmJNT0zEsoi 26tA== MIME-Version: 1.0 X-Received: by 10.43.126.196 with SMTP id gx4mr6465398icc.40.1424782808612; Tue, 24 Feb 2015 05:00:08 -0800 (PST) Received: by 10.64.33.131 with HTTP; Tue, 24 Feb 2015 05:00:08 -0800 (PST) In-Reply-To: References: Date: Tue, 24 Feb 2015 14:00:08 +0100 Message-ID: From: Michele Alberti To: Amir Chaudhry Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Question about pioneer projects X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============7424923575211415281==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============7424923575211415281== Content-Type: multipart/alternative; boundary=001a11c1fe143088d5050fd519f7 --001a11c1fe143088d5050fd519f7 Content-Type: text/plain; charset=UTF-8 Hi Amir! Thanks for your quick reply. I think it would be useful for us to provide (on the page itself [1]) some > idea of what each difficulty level entails. I'll bring that up in the next > Mirage call [2] -- which anyone is welcome to join, by the way. > That would be great. In the meantime, if there are specific projects you're interested in > perhaps we can discuss them here? > Well, all the Irmin related projects sounds really cool. Especially those on semantics (I've started reading JFLA's paper) and GC, though they are 4-starred projects. One can start doing something less difficult I guess, like the local sync project, and then move on. Otherwise, the DHCP server project (even if I don't know DHCP protocol details). Anyway, I am keen on taking these opportunities to learn stuff. I don't know if this is OK for you and your expectations. Best regards, michele --001a11c1fe143088d5050fd519f7 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi Amir!

Thanks for your quick reply.

I think it would be useful for us to provide (on the page itself [1]) some = idea of what each difficulty level entails.=C2=A0 I'll bring that up in= the next Mirage call [2] -- which anyone is welcome to join, by the way.

That would be great.

In the meantime, if there are specific projects you're interested in pe= rhaps we can discuss them here?

Well, a= ll the Irmin related projects sounds really cool. Especially those on seman= tics (I've started reading JFLA's paper) and GC, though they are 4-= starred projects. One can start doing something less difficult I guess, lik= e the local sync project, and then move on.

Otherwise, th= e DHCP server project (even if I don't know DHCP protocol details).
=
Anyway, I am keen on taking these opportunities to learn stu= ff. I don't know if this is OK for you and your expectations.

Best regards,

michele
--001a11c1fe143088d5050fd519f7-- --===============7424923575211415281== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --===============7424923575211415281==-- From mirageos-devel-bounces@lists.xenproject.org Tue Feb 24 13:01:02 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 24 Feb 2015 13:01:02 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YQF6k-00078s-QV; Tue, 24 Feb 2015 13:01:02 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YQF6j-00078Y-53 for mirageos-devel@lists.xenproject.org; Tue, 24 Feb 2015 13:01:01 +0000 Received: from [85.158.143.35] by server-3.bemta-4.messagelabs.com id 0B/60-02791-C067CE45; Tue, 24 Feb 2015 13:01:00 +0000 X-Env-Sender: mic.alberti@gmail.com X-Msg-Ref: server-7.tower-21.messagelabs.com!1424782816!12820837!1 X-Originating-IP: [209.85.223.180] X-SpamReason: No, hits=0.9 required=7.0 tests=BODY_RANDOM_LONG, HTML_30_40,HTML_MESSAGE,RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2335 invoked from network); 24 Feb 2015 13:00:56 -0000 Received: from mail-ie0-f180.google.com (HELO mail-ie0-f180.google.com) (209.85.223.180) by server-7.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 24 Feb 2015 13:00:56 -0000 Received: by iecrl12 with SMTP id rl12so31659601iec.4 for ; Tue, 24 Feb 2015 05:00:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=zwGNf4+Ne/5OU30K7CdCPKBxvWi1W06FY1TkOiggohQ=; b=q7PXEpGMva1NfFdyMxoW0V0mvX/f9+3c63YPZlZzzpHJi5HUaSvAnh/kI2CXPMZuTl lIzMqsEllEXqFHNMLgJwMGKN6vD1o3PNOc0+TndHRPtfhsPTBA6nZxFtEaIsj1lklxU9 ibnMh92TYyScK12Cqh06TRy/W9Vu0Jtvyrzv1G6CZv2EvkXvTIem/nUkwIrKPgqt26kI HhCzMZsYIrmehRig93bRzQMeIZi6JsLgf91nWxRId5U4Z227t358uJPbnq4MubXa+ZKk gqy1FspNQPeU6XHBXXHOpvhlo/COilsXBNC4T0CkOzIJSYohEA7Un3sE+WmJNT0zEsoi 26tA== MIME-Version: 1.0 X-Received: by 10.43.126.196 with SMTP id gx4mr6465398icc.40.1424782808612; Tue, 24 Feb 2015 05:00:08 -0800 (PST) Received: by 10.64.33.131 with HTTP; Tue, 24 Feb 2015 05:00:08 -0800 (PST) In-Reply-To: References: Date: Tue, 24 Feb 2015 14:00:08 +0100 Message-ID: From: Michele Alberti To: Amir Chaudhry Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Question about pioneer projects X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============7424923575211415281==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============7424923575211415281== Content-Type: multipart/alternative; boundary=001a11c1fe143088d5050fd519f7 --001a11c1fe143088d5050fd519f7 Content-Type: text/plain; charset=UTF-8 Hi Amir! Thanks for your quick reply. I think it would be useful for us to provide (on the page itself [1]) some > idea of what each difficulty level entails. I'll bring that up in the next > Mirage call [2] -- which anyone is welcome to join, by the way. > That would be great. In the meantime, if there are specific projects you're interested in > perhaps we can discuss them here? > Well, all the Irmin related projects sounds really cool. Especially those on semantics (I've started reading JFLA's paper) and GC, though they are 4-starred projects. One can start doing something less difficult I guess, like the local sync project, and then move on. Otherwise, the DHCP server project (even if I don't know DHCP protocol details). Anyway, I am keen on taking these opportunities to learn stuff. I don't know if this is OK for you and your expectations. Best regards, michele --001a11c1fe143088d5050fd519f7 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi Amir!

Thanks for your quick reply.

I think it would be useful for us to provide (on the page itself [1]) some = idea of what each difficulty level entails.=C2=A0 I'll bring that up in= the next Mirage call [2] -- which anyone is welcome to join, by the way.

That would be great.

In the meantime, if there are specific projects you're interested in pe= rhaps we can discuss them here?

Well, a= ll the Irmin related projects sounds really cool. Especially those on seman= tics (I've started reading JFLA's paper) and GC, though they are 4-= starred projects. One can start doing something less difficult I guess, lik= e the local sync project, and then move on.

Otherwise, th= e DHCP server project (even if I don't know DHCP protocol details).
=
Anyway, I am keen on taking these opportunities to learn stu= ff. I don't know if this is OK for you and your expectations.

Best regards,

michele
--001a11c1fe143088d5050fd519f7-- --===============7424923575211415281== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --===============7424923575211415281==-- From mirageos-devel-bounces@lists.xenproject.org Tue Feb 24 13:05:44 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 24 Feb 2015 13:05:44 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YQFBI-0008I4-85; Tue, 24 Feb 2015 13:05:44 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YQFBG-0008Hz-Bd for mirageos-devel@lists.xenproject.org; Tue, 24 Feb 2015 13:05:42 +0000 Received: from [85.158.137.68] by server-4.bemta-3.messagelabs.com id D4/0C-03185-5277CE45; Tue, 24 Feb 2015 13:05:41 +0000 X-Env-Sender: amc79@cam.ac.uk X-Msg-Ref: server-14.tower-31.messagelabs.com!1424783137!9377019!1 X-Originating-IP: [131.111.8.151] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTMxLjExMS44LjE1MSA9PiAxNDE4OTU=\n X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16918 invoked from network); 24 Feb 2015 13:05:38 -0000 Received: from ppsw-51.csi.cam.ac.uk (HELO ppsw-51.csi.cam.ac.uk) (131.111.8.151) by server-14.tower-31.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 24 Feb 2015 13:05:38 -0000 X-Cam-AntiVirus: no malware found X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/ Received: from host81-149-102-120.in-addr.btopenworld.com ([81.149.102.120]:54046 helo=[10.0.0.65]) by ppsw-51.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.157]:587) with esmtpsa (PLAIN:amc79) (TLSv1:AES128-SHA:128) id 1YQFBB-0002ml-YG (Exim 4.82_3-c0e5623) (return-path ); Tue, 24 Feb 2015 13:05:37 +0000 Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) From: Amir Chaudhry In-Reply-To: Date: Tue, 24 Feb 2015 13:05:36 +0000 Message-Id: <99F4240E-C4E6-4BD9-BA99-E986A48C45A4@cam.ac.uk> References: <17F3E677-EB2E-4465-B213-B1C682F33C21@badgermind.net> To: yiorgos X-Mailer: Apple Mail (2.1510) Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Question about pioneer projects X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 24 Feb 2015, at 12:56, yiorgos wrote: > +1! > > I know about three ways set up a developing MirageOS environment. > > 1) VirtualBox + Xen + MirageOS VMs > 2) Xen on bare metal > 3) CubieBoard + Xen + MirageOS > > Ways 1, 2 look more easily accessible to people. > > About 1) Do you guys think that > developing can be done using this way or there will be a quite great > amount of setting up/debugging VirtualBox (eg network interfaces etc) Magnus wrote a post about his VirtualBox set up for Mirage development. http://www.skjegstad.com/blog/2015/01/19/mirageos-xen-virtualbox/ AC _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Tue Feb 24 13:05:44 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 24 Feb 2015 13:05:44 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YQFBI-0008I4-85; Tue, 24 Feb 2015 13:05:44 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YQFBG-0008Hz-Bd for mirageos-devel@lists.xenproject.org; Tue, 24 Feb 2015 13:05:42 +0000 Received: from [85.158.137.68] by server-4.bemta-3.messagelabs.com id D4/0C-03185-5277CE45; Tue, 24 Feb 2015 13:05:41 +0000 X-Env-Sender: amc79@cam.ac.uk X-Msg-Ref: server-14.tower-31.messagelabs.com!1424783137!9377019!1 X-Originating-IP: [131.111.8.151] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTMxLjExMS44LjE1MSA9PiAxNDE4OTU=\n X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16918 invoked from network); 24 Feb 2015 13:05:38 -0000 Received: from ppsw-51.csi.cam.ac.uk (HELO ppsw-51.csi.cam.ac.uk) (131.111.8.151) by server-14.tower-31.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 24 Feb 2015 13:05:38 -0000 X-Cam-AntiVirus: no malware found X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/ Received: from host81-149-102-120.in-addr.btopenworld.com ([81.149.102.120]:54046 helo=[10.0.0.65]) by ppsw-51.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.157]:587) with esmtpsa (PLAIN:amc79) (TLSv1:AES128-SHA:128) id 1YQFBB-0002ml-YG (Exim 4.82_3-c0e5623) (return-path ); Tue, 24 Feb 2015 13:05:37 +0000 Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) From: Amir Chaudhry In-Reply-To: Date: Tue, 24 Feb 2015 13:05:36 +0000 Message-Id: <99F4240E-C4E6-4BD9-BA99-E986A48C45A4@cam.ac.uk> References: <17F3E677-EB2E-4465-B213-B1C682F33C21@badgermind.net> To: yiorgos X-Mailer: Apple Mail (2.1510) Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Question about pioneer projects X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 24 Feb 2015, at 12:56, yiorgos wrote: > +1! > > I know about three ways set up a developing MirageOS environment. > > 1) VirtualBox + Xen + MirageOS VMs > 2) Xen on bare metal > 3) CubieBoard + Xen + MirageOS > > Ways 1, 2 look more easily accessible to people. > > About 1) Do you guys think that > developing can be done using this way or there will be a quite great > amount of setting up/debugging VirtualBox (eg network interfaces etc) Magnus wrote a post about his VirtualBox set up for Mirage development. http://www.skjegstad.com/blog/2015/01/19/mirageos-xen-virtualbox/ AC _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Tue Feb 24 13:10:35 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 24 Feb 2015 13:10:35 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YQFFy-0008Kx-TZ; Tue, 24 Feb 2015 13:10:34 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YQFFx-0008Ks-AK for mirageos-devel@lists.xenproject.org; Tue, 24 Feb 2015 13:10:33 +0000 Received: from [85.158.143.35] by server-2.bemta-4.messagelabs.com id 08/A9-02830-8487CE45; Tue, 24 Feb 2015 13:10:32 +0000 X-Env-Sender: talex5@gmail.com X-Msg-Ref: server-4.tower-21.messagelabs.com!1424783394!12773097!1 X-Originating-IP: [209.85.217.178] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 24090 invoked from network); 24 Feb 2015 13:10:31 -0000 Received: from mail-lb0-f178.google.com (HELO mail-lb0-f178.google.com) (209.85.217.178) by server-4.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 24 Feb 2015 13:10:31 -0000 Received: by lbdu14 with SMTP id u14so24648022lbd.1 for ; Tue, 24 Feb 2015 05:09:48 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=GjG3+GEchE1MQvnn/Sogv4LGc6fQtqLi7FNaA8Kxbjs=; b=B00gQYKvcLqSEXoFtems1KoFGEDREl1FpHv/Z8EGTaETeS/iq5ciNVbDB1/TOvXPF1 H9Y4jS64KCrAKl0EGEcAt4EMUj4+p0J1e2mqQrmFFyhx3qDICX7MGCthUtbKt2usYr6A e5NmxV2wF3HVNTCkeAAFzqU2Y4mI5U/ouZwD65XMqIOF1KZMT+q8QSDsC7jmn9y954TF /PqTbrQeQMXTx7WTQJ8aW2joima4fGrJbT3dIrZU3B5yFFtWG2/53HV5JgdF7dk+hOHf kjAElvjqBgPsP7J1W2Ery44fSH0178rpySq5whpF1OwqVpMX0D9aQXe+9eHxQ1XbRpqc L2xw== MIME-Version: 1.0 X-Received: by 10.112.147.66 with SMTP id ti2mr14567430lbb.124.1424783388018; Tue, 24 Feb 2015 05:09:48 -0800 (PST) Received: by 10.25.207.17 with HTTP; Tue, 24 Feb 2015 05:09:47 -0800 (PST) In-Reply-To: <47D39FA3-050E-46E6-89D2-4253484E24A8@gazagnaire.org> References: <8CEDB416-6238-4888-BA4B-B7305FDDE2D9@gazagnaire.org> <9349273A-0BB4-40C4-BF06-4307085AA90C@recoil.org> <47D39FA3-050E-46E6-89D2-4253484E24A8@gazagnaire.org> Date: Tue, 24 Feb 2015 13:09:47 +0000 Message-ID: From: Thomas Leonard To: Thomas Gazagnaire Cc: "mirageos-devel@lists.xenproject.org" , Anil Madhavapeddy Subject: Re: [MirageOS-devel] Irmin API newbie questions X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org T24gMTcgRmVicnVhcnkgMjAxNSBhdCAxMDozOCwgVGhvbWFzIEdhemFnbmFpcmUgPHRob21hc0Bn YXphZ25haXJlLm9yZz4gd3JvdGU6Cj4+PiBPbmUgbGF5ZXIgdGhhdCB3b3VsZCBiZSB2ZXJ5IHVz ZWZ1bCBvdmVyIHRoaXMgY29tbWl0IGdyYXBoIGlzIHNvbWUgbm90aW9uIG9mCj4+PiBkaWZmcy4g IEknZCBxdWl0ZSBsaWtlIHRvIGJlIGFibGUgdG8gZGVzY3JpYmUgYSBkYXRhIHN0cnVjdHVyZSBp biB0ZXJtcyBvZgo+Pj4gcGF0Y2hlcywgc2luY2UgdGhhdCdzIHF1aXRlIG9mdGVuIHRoZSByZWFz b24gd2h5IEknbSB0cmF2ZXJzaW5nIHRoZSBoaXN0b3J5Cj4+PiBpbiB0aGUgZmlyc3QgcGxhY2Uu ICBJZiBJIGp1c3Qgd2FudCB0byBnbyBiYWNrIGluIHRpbWUsIEkgY2FuIHN0YXNoIHJlbGV2YW50 Cj4+PiBwb2ludHMgaW4gYSB0YWcgYW5kIG5ldmVyIG5lZWQgdG8gd2FsayB0aGUgY29tbWl0IGhp c3RvcnkuCj4+Cj4+IEdvb2QgaWRlYSwgSSdsbCB0cnkgdG8gc2VlIGlmIEkgY2FuIGFkZCBhIGRp ZmYgb24gdGhlIGdyYXBoIGVkZ2VzICh2aWEgYSB1c2VyLXByb3ZpZGVkIGZ1bmN0aW9uIHRvIGNv bXB1dGUgZGlmZnMpCj4KPiBJJ3ZlIGFkZGVkIGEgc2ltcGxlIGBJcm1pbi5oaXN0b3J5YCBmdW5j dGlvbiB0byBnZXQgdGhlIGdyYXBoIG9mIGNvbW1pdHM6IGh0dHA6Ly9taXJhZ2UuZ2l0aHViLmlv L2lybWluL0lybWluLmh0bWwjVkFMaGlzdG9yeQoKVGhhbmtzIC0gdGhhdCdzIHdvcmtpbmcgbmlj ZWx5LiBJJ3ZlIGFkZGVkIGEgcGFnZSB0byBteSBqc19vZl9vY2FtbAphcHAgdGhhdCBzaG93cyB0 aGUgbGFzdCBmZXcgY29tbWl0cy4KCk5vdGU6IGl0J3MgcHJvYmFibHkgd29ydGggcmVtb3Zpbmcg IklybWluIGluc2lkZSB0aGUgYnJvd3NlciIgZnJvbSB0aGUKUGlvbmVlciBQcm9qZWN0cyBsaXN0 IG5vdy4gSXQncyB3b3JraW5nIGZpbmUgKHdpdGggSFRNTDUgc3RvcmFnZSkuCkdldHRpbmcgaXQg dG8gd29yayBpcyBqdXN0IGEgY2FzZSBvZiBtb2RpZnlpbmcgSXJtaW4gdG8gdXNlIERhbmllbApC w7xuemxpJ3MgcHVyZS1PQ2FtbCBpbXBsZW1lbnRhdGlvbiBvZiBTSEEtMSBhbmQgaW1wbGVtZW50 aW5nIGEgZmV3IEpTCmhlbHBlcnMgZm9yIGJsaXR0aW5nIHdpdGggYmlnYXJyYXlzLgoKPiBUaGVy ZSBpcyBubyBkaWZmIG9uIHRoZSBlZGdlcyB5ZXQgKHNlZSBodHRwczovL2dpdGh1Yi5jb20vbWly YWdlL2lybWluL2lzc3Vlcy8xNTEgd2hpY2gga2VlcHMgdHJhY2sgb2YgdGhhdCkuCgoKLS0gCkRy IFRob21hcyBMZW9uYXJkICAgICAgICBodHRwOi8vMGluc3RhbGwubmV0LwpHUEc6IDkyNDIgOTgw NyBDOTg1IDNDMDcgNDRBNiAgOEI5QSBBRTA3IDgyODAgNTlBNSAzQ0MxCkdQRzogREE5OCAyNUFF IENBRDAgODk3NSA3Q0RBICBCRDhFIDA3MTMgM0Y5NiBDQTc0IEQ4QkEKCl9fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fCk1pcmFnZU9TLWRldmVsIG1haWxpbmcg bGlzdApNaXJhZ2VPUy1kZXZlbEBsaXN0cy54ZW5wcm9qZWN0Lm9yZwpodHRwOi8vbGlzdHMueGVu cHJvamVjdC5vcmcvY2dpLWJpbi9tYWlsbWFuL2xpc3RpbmZvL21pcmFnZW9zLWRldmVsCg== From mirageos-devel-bounces@lists.xenproject.org Tue Feb 24 13:10:35 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 24 Feb 2015 13:10:35 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YQFFy-0008Kx-TZ; Tue, 24 Feb 2015 13:10:34 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YQFFx-0008Ks-AK for mirageos-devel@lists.xenproject.org; Tue, 24 Feb 2015 13:10:33 +0000 Received: from [85.158.143.35] by server-2.bemta-4.messagelabs.com id 08/A9-02830-8487CE45; Tue, 24 Feb 2015 13:10:32 +0000 X-Env-Sender: talex5@gmail.com X-Msg-Ref: server-4.tower-21.messagelabs.com!1424783394!12773097!1 X-Originating-IP: [209.85.217.178] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 24090 invoked from network); 24 Feb 2015 13:10:31 -0000 Received: from mail-lb0-f178.google.com (HELO mail-lb0-f178.google.com) (209.85.217.178) by server-4.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 24 Feb 2015 13:10:31 -0000 Received: by lbdu14 with SMTP id u14so24648022lbd.1 for ; Tue, 24 Feb 2015 05:09:48 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=GjG3+GEchE1MQvnn/Sogv4LGc6fQtqLi7FNaA8Kxbjs=; b=B00gQYKvcLqSEXoFtems1KoFGEDREl1FpHv/Z8EGTaETeS/iq5ciNVbDB1/TOvXPF1 H9Y4jS64KCrAKl0EGEcAt4EMUj4+p0J1e2mqQrmFFyhx3qDICX7MGCthUtbKt2usYr6A e5NmxV2wF3HVNTCkeAAFzqU2Y4mI5U/ouZwD65XMqIOF1KZMT+q8QSDsC7jmn9y954TF /PqTbrQeQMXTx7WTQJ8aW2joima4fGrJbT3dIrZU3B5yFFtWG2/53HV5JgdF7dk+hOHf kjAElvjqBgPsP7J1W2Ery44fSH0178rpySq5whpF1OwqVpMX0D9aQXe+9eHxQ1XbRpqc L2xw== MIME-Version: 1.0 X-Received: by 10.112.147.66 with SMTP id ti2mr14567430lbb.124.1424783388018; Tue, 24 Feb 2015 05:09:48 -0800 (PST) Received: by 10.25.207.17 with HTTP; Tue, 24 Feb 2015 05:09:47 -0800 (PST) In-Reply-To: <47D39FA3-050E-46E6-89D2-4253484E24A8@gazagnaire.org> References: <8CEDB416-6238-4888-BA4B-B7305FDDE2D9@gazagnaire.org> <9349273A-0BB4-40C4-BF06-4307085AA90C@recoil.org> <47D39FA3-050E-46E6-89D2-4253484E24A8@gazagnaire.org> Date: Tue, 24 Feb 2015 13:09:47 +0000 Message-ID: From: Thomas Leonard To: Thomas Gazagnaire Cc: "mirageos-devel@lists.xenproject.org" , Anil Madhavapeddy Subject: Re: [MirageOS-devel] Irmin API newbie questions X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org T24gMTcgRmVicnVhcnkgMjAxNSBhdCAxMDozOCwgVGhvbWFzIEdhemFnbmFpcmUgPHRob21hc0Bn YXphZ25haXJlLm9yZz4gd3JvdGU6Cj4+PiBPbmUgbGF5ZXIgdGhhdCB3b3VsZCBiZSB2ZXJ5IHVz ZWZ1bCBvdmVyIHRoaXMgY29tbWl0IGdyYXBoIGlzIHNvbWUgbm90aW9uIG9mCj4+PiBkaWZmcy4g IEknZCBxdWl0ZSBsaWtlIHRvIGJlIGFibGUgdG8gZGVzY3JpYmUgYSBkYXRhIHN0cnVjdHVyZSBp biB0ZXJtcyBvZgo+Pj4gcGF0Y2hlcywgc2luY2UgdGhhdCdzIHF1aXRlIG9mdGVuIHRoZSByZWFz b24gd2h5IEknbSB0cmF2ZXJzaW5nIHRoZSBoaXN0b3J5Cj4+PiBpbiB0aGUgZmlyc3QgcGxhY2Uu ICBJZiBJIGp1c3Qgd2FudCB0byBnbyBiYWNrIGluIHRpbWUsIEkgY2FuIHN0YXNoIHJlbGV2YW50 Cj4+PiBwb2ludHMgaW4gYSB0YWcgYW5kIG5ldmVyIG5lZWQgdG8gd2FsayB0aGUgY29tbWl0IGhp c3RvcnkuCj4+Cj4+IEdvb2QgaWRlYSwgSSdsbCB0cnkgdG8gc2VlIGlmIEkgY2FuIGFkZCBhIGRp ZmYgb24gdGhlIGdyYXBoIGVkZ2VzICh2aWEgYSB1c2VyLXByb3ZpZGVkIGZ1bmN0aW9uIHRvIGNv bXB1dGUgZGlmZnMpCj4KPiBJJ3ZlIGFkZGVkIGEgc2ltcGxlIGBJcm1pbi5oaXN0b3J5YCBmdW5j dGlvbiB0byBnZXQgdGhlIGdyYXBoIG9mIGNvbW1pdHM6IGh0dHA6Ly9taXJhZ2UuZ2l0aHViLmlv L2lybWluL0lybWluLmh0bWwjVkFMaGlzdG9yeQoKVGhhbmtzIC0gdGhhdCdzIHdvcmtpbmcgbmlj ZWx5LiBJJ3ZlIGFkZGVkIGEgcGFnZSB0byBteSBqc19vZl9vY2FtbAphcHAgdGhhdCBzaG93cyB0 aGUgbGFzdCBmZXcgY29tbWl0cy4KCk5vdGU6IGl0J3MgcHJvYmFibHkgd29ydGggcmVtb3Zpbmcg IklybWluIGluc2lkZSB0aGUgYnJvd3NlciIgZnJvbSB0aGUKUGlvbmVlciBQcm9qZWN0cyBsaXN0 IG5vdy4gSXQncyB3b3JraW5nIGZpbmUgKHdpdGggSFRNTDUgc3RvcmFnZSkuCkdldHRpbmcgaXQg dG8gd29yayBpcyBqdXN0IGEgY2FzZSBvZiBtb2RpZnlpbmcgSXJtaW4gdG8gdXNlIERhbmllbApC w7xuemxpJ3MgcHVyZS1PQ2FtbCBpbXBsZW1lbnRhdGlvbiBvZiBTSEEtMSBhbmQgaW1wbGVtZW50 aW5nIGEgZmV3IEpTCmhlbHBlcnMgZm9yIGJsaXR0aW5nIHdpdGggYmlnYXJyYXlzLgoKPiBUaGVy ZSBpcyBubyBkaWZmIG9uIHRoZSBlZGdlcyB5ZXQgKHNlZSBodHRwczovL2dpdGh1Yi5jb20vbWly YWdlL2lybWluL2lzc3Vlcy8xNTEgd2hpY2gga2VlcHMgdHJhY2sgb2YgdGhhdCkuCgoKLS0gCkRy IFRob21hcyBMZW9uYXJkICAgICAgICBodHRwOi8vMGluc3RhbGwubmV0LwpHUEc6IDkyNDIgOTgw NyBDOTg1IDNDMDcgNDRBNiAgOEI5QSBBRTA3IDgyODAgNTlBNSAzQ0MxCkdQRzogREE5OCAyNUFF IENBRDAgODk3NSA3Q0RBICBCRDhFIDA3MTMgM0Y5NiBDQTc0IEQ4QkEKCl9fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fCk1pcmFnZU9TLWRldmVsIG1haWxpbmcg bGlzdApNaXJhZ2VPUy1kZXZlbEBsaXN0cy54ZW5wcm9qZWN0Lm9yZwpodHRwOi8vbGlzdHMueGVu cHJvamVjdC5vcmcvY2dpLWJpbi9tYWlsbWFuL2xpc3RpbmZvL21pcmFnZW9zLWRldmVsCg== From mirageos-devel-bounces@lists.xenproject.org Tue Feb 24 13:34:37 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 24 Feb 2015 13:34:37 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YQFdD-00038A-54; Tue, 24 Feb 2015 13:34:35 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YQFdB-00037w-ST for mirageos-devel@lists.xenproject.org; Tue, 24 Feb 2015 13:34:33 +0000 Received: from [85.158.139.211] by server-11.bemta-5.messagelabs.com id FF/AF-02757-8ED7CE45; Tue, 24 Feb 2015 13:34:32 +0000 X-Env-Sender: buzzheavyyear@hotmail.com X-Msg-Ref: server-10.tower-206.messagelabs.com!1424784871!5741580!1 X-Originating-IP: [157.55.2.30] X-SpamReason: No, hits=0.2 required=7.0 tests=FORGED_HOTMAIL_RCVD, HTML_30_40,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7438 invoked from network); 24 Feb 2015 13:34:32 -0000 Received: from dub004-omc3s21.hotmail.com (HELO DUB004-OMC3S21.hotmail.com) (157.55.2.30) by server-10.tower-206.messagelabs.com with AES256-SHA encrypted SMTP; 24 Feb 2015 13:34:32 -0000 Received: from DUB128-W26 ([157.55.2.9]) by DUB004-OMC3S21.hotmail.com over TLS secured channel with Microsoft SMTPSVC(7.5.7601.22751); Tue, 24 Feb 2015 05:34:31 -0800 X-TMN: [NOvG4N7r33CQySgq3rQBvAp2P9epjOo0] X-Originating-Email: [buzzheavyyear@hotmail.com] Message-ID: From: Nick Betteridge To: "mirageos-devel@lists.xenproject.org" Date: Tue, 24 Feb 2015 13:34:31 +0000 Importance: Normal In-Reply-To: References: , <8CEDB416-6238-4888-BA4B-B7305FDDE2D9@gazagnaire.org>, <9349273A-0BB4-40C4-BF06-4307085AA90C@recoil.org>, , <47D39FA3-050E-46E6-89D2-4253484E24A8@gazagnaire.org>, MIME-Version: 1.0 X-OriginalArrivalTime: 24 Feb 2015 13:34:31.0570 (UTC) FILETIME=[9EC1C720:01D05036] Subject: Re: [MirageOS-devel] Irmin API newbie questions X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1034115908044884914==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============1034115908044884914== Content-Type: multipart/alternative; boundary="_7bbd4f82-c7a4-4e18-9a4f-8b75836c118c_" --_7bbd4f82-c7a4-4e18-9a4f-8b75836c118c_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable >=20 > Note: it's probably worth removing "Irmin inside the browser" from the > Pioneer Projects list now. It's working fine (with HTML5 storage). > Getting it to work is just a case of modifying Irmin to use Daniel > B=FCnzli's pure-OCaml implementation of SHA-1 and implementing a few JS > helpers for blitting with bigarrays. >=20 Is this viewable anywhere? It would be great to have this functionality bui= lt into Irmin + extension. = --_7bbd4f82-c7a4-4e18-9a4f-8b75836c118c_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

>=3B
>=3B Note:= it's probably worth removing "Irmin inside the browser" from the
>=3B= Pioneer Projects list now. It's working fine (with HTML5 storage).
>= =3B Getting it to work is just a case of modifying Irmin to use Daniel
&= gt=3B B=FCnzli's pure-OCaml implementation of SHA-1 and implementing a few = JS
>=3B helpers for blitting with bigarrays.
>=3B

Is this= viewable anywhere? It would be great to have this functionality built into= Irmin + extension.
= --_7bbd4f82-c7a4-4e18-9a4f-8b75836c118c_-- --===============1034115908044884914== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --===============1034115908044884914==-- From mirageos-devel-bounces@lists.xenproject.org Tue Feb 24 13:34:37 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 24 Feb 2015 13:34:37 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YQFdD-00038A-54; Tue, 24 Feb 2015 13:34:35 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YQFdB-00037w-ST for mirageos-devel@lists.xenproject.org; Tue, 24 Feb 2015 13:34:33 +0000 Received: from [85.158.139.211] by server-11.bemta-5.messagelabs.com id FF/AF-02757-8ED7CE45; Tue, 24 Feb 2015 13:34:32 +0000 X-Env-Sender: buzzheavyyear@hotmail.com X-Msg-Ref: server-10.tower-206.messagelabs.com!1424784871!5741580!1 X-Originating-IP: [157.55.2.30] X-SpamReason: No, hits=0.2 required=7.0 tests=FORGED_HOTMAIL_RCVD, HTML_30_40,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7438 invoked from network); 24 Feb 2015 13:34:32 -0000 Received: from dub004-omc3s21.hotmail.com (HELO DUB004-OMC3S21.hotmail.com) (157.55.2.30) by server-10.tower-206.messagelabs.com with AES256-SHA encrypted SMTP; 24 Feb 2015 13:34:32 -0000 Received: from DUB128-W26 ([157.55.2.9]) by DUB004-OMC3S21.hotmail.com over TLS secured channel with Microsoft SMTPSVC(7.5.7601.22751); Tue, 24 Feb 2015 05:34:31 -0800 X-TMN: [NOvG4N7r33CQySgq3rQBvAp2P9epjOo0] X-Originating-Email: [buzzheavyyear@hotmail.com] Message-ID: From: Nick Betteridge To: "mirageos-devel@lists.xenproject.org" Date: Tue, 24 Feb 2015 13:34:31 +0000 Importance: Normal In-Reply-To: References: , <8CEDB416-6238-4888-BA4B-B7305FDDE2D9@gazagnaire.org>, <9349273A-0BB4-40C4-BF06-4307085AA90C@recoil.org>, , <47D39FA3-050E-46E6-89D2-4253484E24A8@gazagnaire.org>, MIME-Version: 1.0 X-OriginalArrivalTime: 24 Feb 2015 13:34:31.0570 (UTC) FILETIME=[9EC1C720:01D05036] Subject: Re: [MirageOS-devel] Irmin API newbie questions X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1034115908044884914==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============1034115908044884914== Content-Type: multipart/alternative; boundary="_7bbd4f82-c7a4-4e18-9a4f-8b75836c118c_" --_7bbd4f82-c7a4-4e18-9a4f-8b75836c118c_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable >=20 > Note: it's probably worth removing "Irmin inside the browser" from the > Pioneer Projects list now. It's working fine (with HTML5 storage). > Getting it to work is just a case of modifying Irmin to use Daniel > B=FCnzli's pure-OCaml implementation of SHA-1 and implementing a few JS > helpers for blitting with bigarrays. >=20 Is this viewable anywhere? It would be great to have this functionality bui= lt into Irmin + extension. = --_7bbd4f82-c7a4-4e18-9a4f-8b75836c118c_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

>=3B
>=3B Note:= it's probably worth removing "Irmin inside the browser" from the
>=3B= Pioneer Projects list now. It's working fine (with HTML5 storage).
>= =3B Getting it to work is just a case of modifying Irmin to use Daniel
&= gt=3B B=FCnzli's pure-OCaml implementation of SHA-1 and implementing a few = JS
>=3B helpers for blitting with bigarrays.
>=3B

Is this= viewable anywhere? It would be great to have this functionality built into= Irmin + extension.
= --_7bbd4f82-c7a4-4e18-9a4f-8b75836c118c_-- --===============1034115908044884914== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --===============1034115908044884914==-- From mirageos-devel-bounces@lists.xenproject.org Tue Feb 24 13:37:50 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 24 Feb 2015 13:37:50 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YQFgM-0003g9-FH; Tue, 24 Feb 2015 13:37:50 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YQFgK-0003g4-Js for mirageos-devel@lists.xenproject.org; Tue, 24 Feb 2015 13:37:48 +0000 Received: from [193.109.254.147] by server-6.bemta-14.messagelabs.com id C1/71-03164-BAE7CE45; Tue, 24 Feb 2015 13:37:47 +0000 X-Env-Sender: talex5@gmail.com X-Msg-Ref: server-3.tower-27.messagelabs.com!1424785065!12399315!1 X-Originating-IP: [209.85.215.42] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 26967 invoked from network); 24 Feb 2015 13:37:46 -0000 Received: from mail-la0-f42.google.com (HELO mail-la0-f42.google.com) (209.85.215.42) by server-3.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 24 Feb 2015 13:37:46 -0000 Received: by labhs14 with SMTP id hs14so3016410lab.4 for ; Tue, 24 Feb 2015 05:37:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=l0RZmbE6jYZJX2vTEBWXehwZSfnJHTAVcdjGBIMU+Ws=; b=VIlb8WSg4ojzMtNCFgL+N2SqilVWuBC39gEgNs6KqxLT5ealdzxUiXd2kMRRPxj4/z YbITwRw7uBsA7/oH+iRUgdSwRH5z97AAxTFPjCoeQ09tY0PJc69q0XSY3X81Lv0KDSuO KiATgYjyxFP41XBaoI7tssKXMJodZP96G/ZpytqcJoWJqNvJgMRF/O3pr2Ci3C/FbX+x bNiljHnAH0RkGGOmf0zdhH4+wPBh5B+OrksdsjHu8NO+ux+c7JsfVWJRbkE8r04msOow FhXU0NR8Uper/s/nBtMM+sBloKieVchfhVpRdVD0eUmyDIT228WkhjNpvSakm2KT/oYG BdRQ== MIME-Version: 1.0 X-Received: by 10.112.147.66 with SMTP id ti2mr14670471lbb.124.1424785065506; Tue, 24 Feb 2015 05:37:45 -0800 (PST) Received: by 10.25.207.17 with HTTP; Tue, 24 Feb 2015 05:37:45 -0800 (PST) In-Reply-To: References: <8CEDB416-6238-4888-BA4B-B7305FDDE2D9@gazagnaire.org> <9349273A-0BB4-40C4-BF06-4307085AA90C@recoil.org> <47D39FA3-050E-46E6-89D2-4253484E24A8@gazagnaire.org> Date: Tue, 24 Feb 2015 13:37:45 +0000 Message-ID: From: Thomas Leonard To: Nick Betteridge Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Irmin API newbie questions X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org T24gMjQgRmVicnVhcnkgMjAxNSBhdCAxMzozNCwgTmljayBCZXR0ZXJpZGdlIDxidXp6aGVhdnl5 ZWFyQGhvdG1haWwuY29tPiB3cm90ZToKPgo+Pgo+PiBOb3RlOiBpdCdzIHByb2JhYmx5IHdvcnRo IHJlbW92aW5nICJJcm1pbiBpbnNpZGUgdGhlIGJyb3dzZXIiIGZyb20gdGhlCj4+IFBpb25lZXIg UHJvamVjdHMgbGlzdCBub3cuIEl0J3Mgd29ya2luZyBmaW5lICh3aXRoIEhUTUw1IHN0b3JhZ2Up Lgo+PiBHZXR0aW5nIGl0IHRvIHdvcmsgaXMganVzdCBhIGNhc2Ugb2YgbW9kaWZ5aW5nIElybWlu IHRvIHVzZSBEYW5pZWwKPj4gQsO8bnpsaSdzIHB1cmUtT0NhbWwgaW1wbGVtZW50YXRpb24gb2Yg U0hBLTEgYW5kIGltcGxlbWVudGluZyBhIGZldyBKUwo+PiBoZWxwZXJzIGZvciBibGl0dGluZyB3 aXRoIGJpZ2FycmF5cy4KPj4KPgo+IElzIHRoaXMgdmlld2FibGUgYW55d2hlcmU/IEl0IHdvdWxk IGJlIGdyZWF0IHRvIGhhdmUgdGhpcyBmdW5jdGlvbmFsaXR5Cj4gYnVpbHQgaW50byBJcm1pbiAr IGV4dGVuc2lvbi4KClllcywgYWx0aG91Z2ggSSdtIHBsYW5uaW5nIG9uIGRvaW5nIG1vcmUgdGVz dGluZyBiZWZvcmUgdXBzdHJlYW1pbmcuCkhvd2V2ZXIsIGZvciB0aGUgY3VyaW91cyB0aGUgY3Vy cmVudCB2ZXJzaW9ucyBjYW4gYmUgZm91bmQgaGVyZToKCkhUTUwgNSBzdG9yYWdlIGJhY2tlbmQg Zm9yIElybWluOgoKaHR0cHM6Ly9naXRodWIuY29tL3RhbGV4NS9jdWVrZWVwZXIvYmxvYi9tYXN0 ZXIvaHRtbF9zdG9yYWdlLm1sCgpKUyB3cmFwcGVycyBmb3IgQ3N0cnVzdCBhbmQgQmlucHJvdDoK Cmh0dHBzOi8vZ2l0aHViLmNvbS90YWxleDUvY3Vla2VlcGVyL2Jsb2IvbWFzdGVyL2hlbHBlcnMu anMKCgotLSAKRHIgVGhvbWFzIExlb25hcmQgICAgICAgIGh0dHA6Ly8waW5zdGFsbC5uZXQvCkdQ RzogOTI0MiA5ODA3IEM5ODUgM0MwNyA0NEE2ICA4QjlBIEFFMDcgODI4MCA1OUE1IDNDQzEKR1BH OiBEQTk4IDI1QUUgQ0FEMCA4OTc1IDdDREEgIEJEOEUgMDcxMyAzRjk2IENBNzQgRDhCQQoKX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KTWlyYWdlT1MtZGV2 ZWwgbWFpbGluZyBsaXN0Ck1pcmFnZU9TLWRldmVsQGxpc3RzLnhlbnByb2plY3Qub3JnCmh0dHA6 Ly9saXN0cy54ZW5wcm9qZWN0Lm9yZy9jZ2ktYmluL21haWxtYW4vbGlzdGluZm8vbWlyYWdlb3Mt ZGV2ZWwK From mirageos-devel-bounces@lists.xenproject.org Tue Feb 24 13:37:50 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 24 Feb 2015 13:37:50 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YQFgM-0003g9-FH; Tue, 24 Feb 2015 13:37:50 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YQFgK-0003g4-Js for mirageos-devel@lists.xenproject.org; Tue, 24 Feb 2015 13:37:48 +0000 Received: from [193.109.254.147] by server-6.bemta-14.messagelabs.com id C1/71-03164-BAE7CE45; Tue, 24 Feb 2015 13:37:47 +0000 X-Env-Sender: talex5@gmail.com X-Msg-Ref: server-3.tower-27.messagelabs.com!1424785065!12399315!1 X-Originating-IP: [209.85.215.42] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 26967 invoked from network); 24 Feb 2015 13:37:46 -0000 Received: from mail-la0-f42.google.com (HELO mail-la0-f42.google.com) (209.85.215.42) by server-3.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 24 Feb 2015 13:37:46 -0000 Received: by labhs14 with SMTP id hs14so3016410lab.4 for ; Tue, 24 Feb 2015 05:37:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=l0RZmbE6jYZJX2vTEBWXehwZSfnJHTAVcdjGBIMU+Ws=; b=VIlb8WSg4ojzMtNCFgL+N2SqilVWuBC39gEgNs6KqxLT5ealdzxUiXd2kMRRPxj4/z YbITwRw7uBsA7/oH+iRUgdSwRH5z97AAxTFPjCoeQ09tY0PJc69q0XSY3X81Lv0KDSuO KiATgYjyxFP41XBaoI7tssKXMJodZP96G/ZpytqcJoWJqNvJgMRF/O3pr2Ci3C/FbX+x bNiljHnAH0RkGGOmf0zdhH4+wPBh5B+OrksdsjHu8NO+ux+c7JsfVWJRbkE8r04msOow FhXU0NR8Uper/s/nBtMM+sBloKieVchfhVpRdVD0eUmyDIT228WkhjNpvSakm2KT/oYG BdRQ== MIME-Version: 1.0 X-Received: by 10.112.147.66 with SMTP id ti2mr14670471lbb.124.1424785065506; Tue, 24 Feb 2015 05:37:45 -0800 (PST) Received: by 10.25.207.17 with HTTP; Tue, 24 Feb 2015 05:37:45 -0800 (PST) In-Reply-To: References: <8CEDB416-6238-4888-BA4B-B7305FDDE2D9@gazagnaire.org> <9349273A-0BB4-40C4-BF06-4307085AA90C@recoil.org> <47D39FA3-050E-46E6-89D2-4253484E24A8@gazagnaire.org> Date: Tue, 24 Feb 2015 13:37:45 +0000 Message-ID: From: Thomas Leonard To: Nick Betteridge Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Irmin API newbie questions X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org T24gMjQgRmVicnVhcnkgMjAxNSBhdCAxMzozNCwgTmljayBCZXR0ZXJpZGdlIDxidXp6aGVhdnl5 ZWFyQGhvdG1haWwuY29tPiB3cm90ZToKPgo+Pgo+PiBOb3RlOiBpdCdzIHByb2JhYmx5IHdvcnRo IHJlbW92aW5nICJJcm1pbiBpbnNpZGUgdGhlIGJyb3dzZXIiIGZyb20gdGhlCj4+IFBpb25lZXIg UHJvamVjdHMgbGlzdCBub3cuIEl0J3Mgd29ya2luZyBmaW5lICh3aXRoIEhUTUw1IHN0b3JhZ2Up Lgo+PiBHZXR0aW5nIGl0IHRvIHdvcmsgaXMganVzdCBhIGNhc2Ugb2YgbW9kaWZ5aW5nIElybWlu IHRvIHVzZSBEYW5pZWwKPj4gQsO8bnpsaSdzIHB1cmUtT0NhbWwgaW1wbGVtZW50YXRpb24gb2Yg U0hBLTEgYW5kIGltcGxlbWVudGluZyBhIGZldyBKUwo+PiBoZWxwZXJzIGZvciBibGl0dGluZyB3 aXRoIGJpZ2FycmF5cy4KPj4KPgo+IElzIHRoaXMgdmlld2FibGUgYW55d2hlcmU/IEl0IHdvdWxk IGJlIGdyZWF0IHRvIGhhdmUgdGhpcyBmdW5jdGlvbmFsaXR5Cj4gYnVpbHQgaW50byBJcm1pbiAr IGV4dGVuc2lvbi4KClllcywgYWx0aG91Z2ggSSdtIHBsYW5uaW5nIG9uIGRvaW5nIG1vcmUgdGVz dGluZyBiZWZvcmUgdXBzdHJlYW1pbmcuCkhvd2V2ZXIsIGZvciB0aGUgY3VyaW91cyB0aGUgY3Vy cmVudCB2ZXJzaW9ucyBjYW4gYmUgZm91bmQgaGVyZToKCkhUTUwgNSBzdG9yYWdlIGJhY2tlbmQg Zm9yIElybWluOgoKaHR0cHM6Ly9naXRodWIuY29tL3RhbGV4NS9jdWVrZWVwZXIvYmxvYi9tYXN0 ZXIvaHRtbF9zdG9yYWdlLm1sCgpKUyB3cmFwcGVycyBmb3IgQ3N0cnVzdCBhbmQgQmlucHJvdDoK Cmh0dHBzOi8vZ2l0aHViLmNvbS90YWxleDUvY3Vla2VlcGVyL2Jsb2IvbWFzdGVyL2hlbHBlcnMu anMKCgotLSAKRHIgVGhvbWFzIExlb25hcmQgICAgICAgIGh0dHA6Ly8waW5zdGFsbC5uZXQvCkdQ RzogOTI0MiA5ODA3IEM5ODUgM0MwNyA0NEE2ICA4QjlBIEFFMDcgODI4MCA1OUE1IDNDQzEKR1BH OiBEQTk4IDI1QUUgQ0FEMCA4OTc1IDdDREEgIEJEOEUgMDcxMyAzRjk2IENBNzQgRDhCQQoKX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KTWlyYWdlT1MtZGV2 ZWwgbWFpbGluZyBsaXN0Ck1pcmFnZU9TLWRldmVsQGxpc3RzLnhlbnByb2plY3Qub3JnCmh0dHA6 Ly9saXN0cy54ZW5wcm9qZWN0Lm9yZy9jZ2ktYmluL21haWxtYW4vbGlzdGluZm8vbWlyYWdlb3Mt ZGV2ZWwK From mirageos-devel-bounces@lists.xenproject.org Tue Feb 24 14:08:15 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 24 Feb 2015 14:08:15 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YQG9i-0007CG-4W; Tue, 24 Feb 2015 14:08:10 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YQG9g-0007CB-3L for mirageos-devel@lists.xenproject.org; Tue, 24 Feb 2015 14:08:08 +0000 Received: from [85.158.137.68] by server-6.bemta-3.messagelabs.com id 4A/CB-03164-7C58CE45; Tue, 24 Feb 2015 14:08:07 +0000 X-Env-Sender: eireann.leverett@cantab.net X-Msg-Ref: server-9.tower-31.messagelabs.com!1424786885!8126306!1 X-Originating-IP: [72.9.247.210] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNzIuOS4yNDcuMjEwID0+IDg5NTg=\n X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11981 invoked from network); 24 Feb 2015 14:08:06 -0000 Received: from jackal.aluminati.org (HELO jackal.aluminati.org) (72.9.247.210) by server-9.tower-31.messagelabs.com with SMTP; 24 Feb 2015 14:08:06 -0000 Received: from localhost (localhost [127.0.0.1]) by jackal.aluminati.org (Postfix) with ESMTP id 4837A866011 for ; Tue, 24 Feb 2015 14:08:02 +0000 (GMT) X-Quarantine-ID: X-Virus-Scanned: Debian amavisd-new at serval.aluminati.org X-Spam-Flag: NO X-Spam-Score: -2.999 X-Spam-Level: X-Spam-Status: No, score=-2.999 tagged_above=-9999 required=6.31 tests=[ALL_TRUSTED=-1, BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, URIBL_BLOCKED=0.001] autolearn=no Received: from jackal.aluminati.org ([127.0.0.1]) by localhost (jackal.aluminati.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id fRlv4GI8tHLJ for ; Tue, 24 Feb 2015 14:08:00 +0000 (GMT) Received: from pichi.aluminati.org (pichi.aluminati.org [10.0.16.50]) by jackal.aluminati.org (Postfix) with ESMTP id CA7E2866005 for ; Tue, 24 Feb 2015 14:07:58 +0000 (GMT) Received: from localhost (localhost [127.0.0.1]) by pichi.aluminati.org (Postfix) with ESMTP id 67EB4161E6CD for ; Tue, 24 Feb 2015 12:40:15 +0000 (GMT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cantab.net; h= content-transfer-encoding:in-reply-to:references:subject:subject :mime-version:user-agent:from:from:date:date:message-id:received :received; s=postfix; t=1424781586; bh=jWhGYDD/ZEo++0y02bK6CaPUg UZ3QMmGSbO1/+nOlQc=; b=PjRz32ygPkE2meocJz50RVtC9MxRMGLrAknKws6Gu rXGG/Fn+CC+f5KJ7Looe1Htd7jpHyiwNMZQgfBpsRfAR8EsKGQdIKvr7AjT+3Lxu LA6rVoQ3q8+D/c+Kkknvd/yYt/dxl9TV30yrK2lL15bDeMsc1QeEwROdIqG1q5nY zs= X-Quarantine-ID: X-Virus-Scanned: Debian amavisd-new at aluminati.org Received: from pichi.aluminati.org ([127.0.0.1]) by localhost (pichi.aluminati.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id YhwYBO3KQxQh for ; Tue, 24 Feb 2015 12:39:46 +0000 (GMT) Received: from [131.111.178.120] (griffin.aluminati.org [10.0.7.182]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by pichi.aluminati.org (Postfix) with ESMTPSA id A6184161E6B9 for ; Tue, 24 Feb 2015 12:39:44 +0000 (GMT) Message-ID: <54EC710F.9030000@cantab.net> Date: Tue, 24 Feb 2015 12:39:43 +0000 From: Eireann Leverett User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: mirageos-devel@lists.xenproject.org References: In-Reply-To: Subject: Re: [MirageOS-devel] MirageOS-devel Digest, Vol 15, Issue 28 X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org Noobish ocaml developer and quality assurance person reporting in! me++ to the others interested but slightly intimidated with where to start, and how to catch up on the good work already done. Eireann Leverett On 24/02/2015 12:00, mirageos-devel-request@lists.xenproject.org wrote: > Send MirageOS-devel mailing list submissions to > mirageos-devel@lists.xenproject.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > or, via email, send a message with subject or body 'help' to > mirageos-devel-request@lists.xenproject.org > > You can reach the person managing the list at > mirageos-devel-owner@lists.xenproject.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of MirageOS-devel digest..." > > > Today's Topics: > > 1. Question about pioneer projects (Michele Alberti) > 2. Re: Question about pioneer projects (Amir Chaudhry) > 3. Mirage fortnightly call - Wednesday 25th at 4pm GMT > (Amir Chaudhry) > 4. Re: Question about pioneer projects (Robin Taylor) > 5. Re: Question about pioneer projects (Matthew Gray) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 24 Feb 2015 12:10:14 +0100 > From: Michele Alberti > To: mirageos-devel@lists.xenproject.org > Subject: [MirageOS-devel] Question about pioneer projects > Message-ID: > > Content-Type: text/plain; charset="utf-8" > > Hello, > > First of all let me say that all the MirageOS idea and implementation > sounds really great. > > Not so many years ago I used OCaml for a University CS project, and I've > recently rediscovered it (RWO book). > > I'd love participating into a MirageOS related project to do some real work > in OCaml, though I am a newcomer (even if I have a CS background). I've > given a look at your projects github webpage and I must admit that they all > are very cool. However, let me ask a question to see whether I can be a > good fit: > > what is the working knowledge of OCaml you expect for a 3-starred project > (i.e. medium difficulty)? > > Sorry for being pedantic, but I'm really interested in participating. > > Best regards, > > michele alberti > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > > ------------------------------ > > Message: 2 > Date: Tue, 24 Feb 2015 11:42:52 +0000 > From: Amir Chaudhry > To: Michele Alberti > Cc: mirageos-devel@lists.xenproject.org > Subject: Re: [MirageOS-devel] Question about pioneer projects > Message-ID: > Content-Type: text/plain; charset=us-ascii > > Hi Michele! > > Thanks for looking over the projects and getting in touch. > > It's an *excellent* question and it's one I've also been meaning to ask. :) > I think it would be useful for us to provide (on the page itself [1]) some idea of what each difficulty level entails. I'll bring that up in the next Mirage call [2] -- which anyone is welcome to join, by the way. > > In the meantime, if there are specific projects you're interested in perhaps we can discuss them here? > > (Links are mostly to remind others of their existence) > > [1] https://github.com/mirage/mirage-www/wiki/Pioneer-Projects > [2] https://github.com/mirage/mirage-www/wiki/Call-Agenda > > Best wishes, > Amir > > On 24 Feb 2015, at 11:10, Michele Alberti wrote: > >> Hello, >> >> First of all let me say that all the MirageOS idea and implementation sounds really great. >> >> Not so many years ago I used OCaml for a University CS project, and I've recently rediscovered it (RWO book). >> >> I'd love participating into a MirageOS related project to do some real work in OCaml, though I am a newcomer (even if I have a CS background). I've given a look at your projects github webpage and I must admit that they all are very cool. However, let me ask a question to see whether I can be a good fit: >> >> what is the working knowledge of OCaml you expect for a 3-starred project (i.e. medium difficulty)? >> >> Sorry for being pedantic, but I'm really interested in participating. >> >> Best regards, >> >> michele alberti >> _______________________________________________ >> MirageOS-devel mailing list >> MirageOS-devel@lists.xenproject.org >> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > > > > ------------------------------ > > Message: 3 > Date: Tue, 24 Feb 2015 11:46:26 +0000 > From: Amir Chaudhry > To: "mirageos-devel@lists.xenproject.org" > > Subject: [MirageOS-devel] Mirage fortnightly call - Wednesday 25th at > 4pm GMT > Message-ID: > Content-Type: text/plain; charset=windows-1252 > > Hi folks, > > The next Mirage call will take place this Wednesday afternoon at 4pm GMT and is open to all. > > Notes from last time are up at http://openmirage.org/wiki/weekly-2015-02-11 > > The agenda is currently as follows: > > ? mirage-net-xen 1.3.0 dead-lock/race (see https://github.com/mirage/mirage-net-xen/issues/20) > ? Quality and Test Infra > ? Automate all the things > ? Mirage.io > ? Irmin progress > ? Pioneer Projects > ? 3.0 Planning > > If you have things to add/edit, please do so at https://github.com/mirage/mirage-www/wiki/Call-Agenda > > GoToMeeting details are below but if there are any hiccups/delays then I'll switch to a public Google Hangout. If that happens, I'll post the link here and also in the IRC channel (#mirage on freenode). > > Join us at 4pm GMT on Wednesday! > > 1. Please join my meeting. > https://www1.gotomeeting.com/join/591890401 > > Dial in numbers (ask if you need a specific country): > United Kingdom: +44 (0) 20 3657 6778 > United States: +1 (213) 493-0014 > Access Code: 591-890-401 > Audio PIN: Shown after joining the meeting > > Best wishes, > Amir > > > ------------------------------ > > Message: 4 > Date: Tue, 24 Feb 2015 11:49:28 +0000 > From: Robin Taylor > To: Amir Chaudhry > Cc: Michele Alberti , > mirageos-devel@lists.xenproject.org > Subject: Re: [MirageOS-devel] Question about pioneer projects > Message-ID: <17F3E677-EB2E-4465-B213-B1C682F33C21@badgermind.net> > Content-Type: text/plain; charset=us-ascii > > Thanks Amir and Michele > > I'd been thinking of asking exactly the same question (although my experience is more F# than OCaml) > > Best wishes > > Robin > > > On 24 Feb 2015, at 11:42, Amir Chaudhry wrote: > >> Hi Michele! >> >> Thanks for looking over the projects and getting in touch. >> >> It's an *excellent* question and it's one I've also been meaning to ask. :) >> I think it would be useful for us to provide (on the page itself [1]) some idea of what each difficulty level entails. I'll bring that up in the next Mirage call [2] -- which anyone is welcome to join, by the way. >> >> In the meantime, if there are specific projects you're interested in perhaps we can discuss them here? >> >> (Links are mostly to remind others of their existence) >> >> [1] https://github.com/mirage/mirage-www/wiki/Pioneer-Projects >> [2] https://github.com/mirage/mirage-www/wiki/Call-Agenda >> >> Best wishes, >> Amir >> >> On 24 Feb 2015, at 11:10, Michele Alberti wrote: >> >>> Hello, >>> >>> First of all let me say that all the MirageOS idea and implementation sounds really great. >>> >>> Not so many years ago I used OCaml for a University CS project, and I've recently rediscovered it (RWO book). >>> >>> I'd love participating into a MirageOS related project to do some real work in OCaml, though I am a newcomer (even if I have a CS background). I've given a look at your projects github webpage and I must admit that they all are very cool. However, let me ask a question to see whether I can be a good fit: >>> >>> what is the working knowledge of OCaml you expect for a 3-starred project (i.e. medium difficulty)? >>> >>> Sorry for being pedantic, but I'm really interested in participating. >>> >>> Best regards, >>> >>> michele alberti >>> _______________________________________________ >>> MirageOS-devel mailing list >>> MirageOS-devel@lists.xenproject.org >>> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel >> >> _______________________________________________ >> MirageOS-devel mailing list >> MirageOS-devel@lists.xenproject.org >> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > > > > ------------------------------ > > Message: 5 > Date: Tue, 24 Feb 2015 11:54:11 +0000 > From: Matthew Gray > To: Robin Taylor > Cc: Michele Alberti , > mirageos-devel@lists.xenproject.org > Subject: Re: [MirageOS-devel] Question about pioneer projects > Message-ID: > > Content-Type: text/plain; charset="utf-8" > > And me! New to OCaml, but keen to learn more and contribute to MirageOS if > I can. > > Matt > > On Tue, Feb 24, 2015 at 11:49 AM, Robin Taylor wrote: > >> Thanks Amir and Michele >> >> I'd been thinking of asking exactly the same question (although my >> experience is more F# than OCaml) >> >> Best wishes >> >> Robin >> >> >> On 24 Feb 2015, at 11:42, Amir Chaudhry wrote: >> >>> Hi Michele! >>> >>> Thanks for looking over the projects and getting in touch. >>> >>> It's an *excellent* question and it's one I've also been meaning to ask. >> :) >>> I think it would be useful for us to provide (on the page itself [1]) >> some idea of what each difficulty level entails. I'll bring that up in the >> next Mirage call [2] -- which anyone is welcome to join, by the way. >>> In the meantime, if there are specific projects you're interested in >> perhaps we can discuss them here? >>> (Links are mostly to remind others of their existence) >>> >>> [1] https://github.com/mirage/mirage-www/wiki/Pioneer-Projects >>> [2] https://github.com/mirage/mirage-www/wiki/Call-Agenda >>> >>> Best wishes, >>> Amir >>> >>> On 24 Feb 2015, at 11:10, Michele Alberti wrote: >>> >>>> Hello, >>>> >>>> First of all let me say that all the MirageOS idea and implementation >> sounds really great. >>>> Not so many years ago I used OCaml for a University CS project, and >> I've recently rediscovered it (RWO book). >>>> I'd love participating into a MirageOS related project to do some real >> work in OCaml, though I am a newcomer (even if I have a CS background). >> I've given a look at your projects github webpage and I must admit that >> they all are very cool. However, let me ask a question to see whether I can >> be a good fit: >>>> what is the working knowledge of OCaml you expect for a 3-starred >> project (i.e. medium difficulty)? >>>> Sorry for being pedantic, but I'm really interested in participating. >>>> >>>> Best regards, >>>> >>>> michele alberti >>>> _______________________________________________ >>>> MirageOS-devel mailing list >>>> MirageOS-devel@lists.xenproject.org >>>> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel >>> >>> _______________________________________________ >>> MirageOS-devel mailing list >>> MirageOS-devel@lists.xenproject.org >>> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel >> >> _______________________________________________ >> MirageOS-devel mailing list >> MirageOS-devel@lists.xenproject.org >> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel >> > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > > ------------------------------ > > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > > > End of MirageOS-devel Digest, Vol 15, Issue 28 > ********************************************** _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Tue Feb 24 14:08:15 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 24 Feb 2015 14:08:15 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YQG9i-0007CG-4W; Tue, 24 Feb 2015 14:08:10 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YQG9g-0007CB-3L for mirageos-devel@lists.xenproject.org; Tue, 24 Feb 2015 14:08:08 +0000 Received: from [85.158.137.68] by server-6.bemta-3.messagelabs.com id 4A/CB-03164-7C58CE45; Tue, 24 Feb 2015 14:08:07 +0000 X-Env-Sender: eireann.leverett@cantab.net X-Msg-Ref: server-9.tower-31.messagelabs.com!1424786885!8126306!1 X-Originating-IP: [72.9.247.210] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNzIuOS4yNDcuMjEwID0+IDg5NTg=\n X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11981 invoked from network); 24 Feb 2015 14:08:06 -0000 Received: from jackal.aluminati.org (HELO jackal.aluminati.org) (72.9.247.210) by server-9.tower-31.messagelabs.com with SMTP; 24 Feb 2015 14:08:06 -0000 Received: from localhost (localhost [127.0.0.1]) by jackal.aluminati.org (Postfix) with ESMTP id 4837A866011 for ; Tue, 24 Feb 2015 14:08:02 +0000 (GMT) X-Quarantine-ID: X-Virus-Scanned: Debian amavisd-new at serval.aluminati.org X-Spam-Flag: NO X-Spam-Score: -2.999 X-Spam-Level: X-Spam-Status: No, score=-2.999 tagged_above=-9999 required=6.31 tests=[ALL_TRUSTED=-1, BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, URIBL_BLOCKED=0.001] autolearn=no Received: from jackal.aluminati.org ([127.0.0.1]) by localhost (jackal.aluminati.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id fRlv4GI8tHLJ for ; Tue, 24 Feb 2015 14:08:00 +0000 (GMT) Received: from pichi.aluminati.org (pichi.aluminati.org [10.0.16.50]) by jackal.aluminati.org (Postfix) with ESMTP id CA7E2866005 for ; Tue, 24 Feb 2015 14:07:58 +0000 (GMT) Received: from localhost (localhost [127.0.0.1]) by pichi.aluminati.org (Postfix) with ESMTP id 67EB4161E6CD for ; Tue, 24 Feb 2015 12:40:15 +0000 (GMT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cantab.net; h= content-transfer-encoding:in-reply-to:references:subject:subject :mime-version:user-agent:from:from:date:date:message-id:received :received; s=postfix; t=1424781586; bh=jWhGYDD/ZEo++0y02bK6CaPUg UZ3QMmGSbO1/+nOlQc=; b=PjRz32ygPkE2meocJz50RVtC9MxRMGLrAknKws6Gu rXGG/Fn+CC+f5KJ7Looe1Htd7jpHyiwNMZQgfBpsRfAR8EsKGQdIKvr7AjT+3Lxu LA6rVoQ3q8+D/c+Kkknvd/yYt/dxl9TV30yrK2lL15bDeMsc1QeEwROdIqG1q5nY zs= X-Quarantine-ID: X-Virus-Scanned: Debian amavisd-new at aluminati.org Received: from pichi.aluminati.org ([127.0.0.1]) by localhost (pichi.aluminati.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id YhwYBO3KQxQh for ; Tue, 24 Feb 2015 12:39:46 +0000 (GMT) Received: from [131.111.178.120] (griffin.aluminati.org [10.0.7.182]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by pichi.aluminati.org (Postfix) with ESMTPSA id A6184161E6B9 for ; Tue, 24 Feb 2015 12:39:44 +0000 (GMT) Message-ID: <54EC710F.9030000@cantab.net> Date: Tue, 24 Feb 2015 12:39:43 +0000 From: Eireann Leverett User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: mirageos-devel@lists.xenproject.org References: In-Reply-To: Subject: Re: [MirageOS-devel] MirageOS-devel Digest, Vol 15, Issue 28 X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org Noobish ocaml developer and quality assurance person reporting in! me++ to the others interested but slightly intimidated with where to start, and how to catch up on the good work already done. Eireann Leverett On 24/02/2015 12:00, mirageos-devel-request@lists.xenproject.org wrote: > Send MirageOS-devel mailing list submissions to > mirageos-devel@lists.xenproject.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > or, via email, send a message with subject or body 'help' to > mirageos-devel-request@lists.xenproject.org > > You can reach the person managing the list at > mirageos-devel-owner@lists.xenproject.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of MirageOS-devel digest..." > > > Today's Topics: > > 1. Question about pioneer projects (Michele Alberti) > 2. Re: Question about pioneer projects (Amir Chaudhry) > 3. Mirage fortnightly call - Wednesday 25th at 4pm GMT > (Amir Chaudhry) > 4. Re: Question about pioneer projects (Robin Taylor) > 5. Re: Question about pioneer projects (Matthew Gray) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 24 Feb 2015 12:10:14 +0100 > From: Michele Alberti > To: mirageos-devel@lists.xenproject.org > Subject: [MirageOS-devel] Question about pioneer projects > Message-ID: > > Content-Type: text/plain; charset="utf-8" > > Hello, > > First of all let me say that all the MirageOS idea and implementation > sounds really great. > > Not so many years ago I used OCaml for a University CS project, and I've > recently rediscovered it (RWO book). > > I'd love participating into a MirageOS related project to do some real work > in OCaml, though I am a newcomer (even if I have a CS background). I've > given a look at your projects github webpage and I must admit that they all > are very cool. However, let me ask a question to see whether I can be a > good fit: > > what is the working knowledge of OCaml you expect for a 3-starred project > (i.e. medium difficulty)? > > Sorry for being pedantic, but I'm really interested in participating. > > Best regards, > > michele alberti > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > > ------------------------------ > > Message: 2 > Date: Tue, 24 Feb 2015 11:42:52 +0000 > From: Amir Chaudhry > To: Michele Alberti > Cc: mirageos-devel@lists.xenproject.org > Subject: Re: [MirageOS-devel] Question about pioneer projects > Message-ID: > Content-Type: text/plain; charset=us-ascii > > Hi Michele! > > Thanks for looking over the projects and getting in touch. > > It's an *excellent* question and it's one I've also been meaning to ask. :) > I think it would be useful for us to provide (on the page itself [1]) some idea of what each difficulty level entails. I'll bring that up in the next Mirage call [2] -- which anyone is welcome to join, by the way. > > In the meantime, if there are specific projects you're interested in perhaps we can discuss them here? > > (Links are mostly to remind others of their existence) > > [1] https://github.com/mirage/mirage-www/wiki/Pioneer-Projects > [2] https://github.com/mirage/mirage-www/wiki/Call-Agenda > > Best wishes, > Amir > > On 24 Feb 2015, at 11:10, Michele Alberti wrote: > >> Hello, >> >> First of all let me say that all the MirageOS idea and implementation sounds really great. >> >> Not so many years ago I used OCaml for a University CS project, and I've recently rediscovered it (RWO book). >> >> I'd love participating into a MirageOS related project to do some real work in OCaml, though I am a newcomer (even if I have a CS background). I've given a look at your projects github webpage and I must admit that they all are very cool. However, let me ask a question to see whether I can be a good fit: >> >> what is the working knowledge of OCaml you expect for a 3-starred project (i.e. medium difficulty)? >> >> Sorry for being pedantic, but I'm really interested in participating. >> >> Best regards, >> >> michele alberti >> _______________________________________________ >> MirageOS-devel mailing list >> MirageOS-devel@lists.xenproject.org >> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > > > > ------------------------------ > > Message: 3 > Date: Tue, 24 Feb 2015 11:46:26 +0000 > From: Amir Chaudhry > To: "mirageos-devel@lists.xenproject.org" > > Subject: [MirageOS-devel] Mirage fortnightly call - Wednesday 25th at > 4pm GMT > Message-ID: > Content-Type: text/plain; charset=windows-1252 > > Hi folks, > > The next Mirage call will take place this Wednesday afternoon at 4pm GMT and is open to all. > > Notes from last time are up at http://openmirage.org/wiki/weekly-2015-02-11 > > The agenda is currently as follows: > > ? mirage-net-xen 1.3.0 dead-lock/race (see https://github.com/mirage/mirage-net-xen/issues/20) > ? Quality and Test Infra > ? Automate all the things > ? Mirage.io > ? Irmin progress > ? Pioneer Projects > ? 3.0 Planning > > If you have things to add/edit, please do so at https://github.com/mirage/mirage-www/wiki/Call-Agenda > > GoToMeeting details are below but if there are any hiccups/delays then I'll switch to a public Google Hangout. If that happens, I'll post the link here and also in the IRC channel (#mirage on freenode). > > Join us at 4pm GMT on Wednesday! > > 1. Please join my meeting. > https://www1.gotomeeting.com/join/591890401 > > Dial in numbers (ask if you need a specific country): > United Kingdom: +44 (0) 20 3657 6778 > United States: +1 (213) 493-0014 > Access Code: 591-890-401 > Audio PIN: Shown after joining the meeting > > Best wishes, > Amir > > > ------------------------------ > > Message: 4 > Date: Tue, 24 Feb 2015 11:49:28 +0000 > From: Robin Taylor > To: Amir Chaudhry > Cc: Michele Alberti , > mirageos-devel@lists.xenproject.org > Subject: Re: [MirageOS-devel] Question about pioneer projects > Message-ID: <17F3E677-EB2E-4465-B213-B1C682F33C21@badgermind.net> > Content-Type: text/plain; charset=us-ascii > > Thanks Amir and Michele > > I'd been thinking of asking exactly the same question (although my experience is more F# than OCaml) > > Best wishes > > Robin > > > On 24 Feb 2015, at 11:42, Amir Chaudhry wrote: > >> Hi Michele! >> >> Thanks for looking over the projects and getting in touch. >> >> It's an *excellent* question and it's one I've also been meaning to ask. :) >> I think it would be useful for us to provide (on the page itself [1]) some idea of what each difficulty level entails. I'll bring that up in the next Mirage call [2] -- which anyone is welcome to join, by the way. >> >> In the meantime, if there are specific projects you're interested in perhaps we can discuss them here? >> >> (Links are mostly to remind others of their existence) >> >> [1] https://github.com/mirage/mirage-www/wiki/Pioneer-Projects >> [2] https://github.com/mirage/mirage-www/wiki/Call-Agenda >> >> Best wishes, >> Amir >> >> On 24 Feb 2015, at 11:10, Michele Alberti wrote: >> >>> Hello, >>> >>> First of all let me say that all the MirageOS idea and implementation sounds really great. >>> >>> Not so many years ago I used OCaml for a University CS project, and I've recently rediscovered it (RWO book). >>> >>> I'd love participating into a MirageOS related project to do some real work in OCaml, though I am a newcomer (even if I have a CS background). I've given a look at your projects github webpage and I must admit that they all are very cool. However, let me ask a question to see whether I can be a good fit: >>> >>> what is the working knowledge of OCaml you expect for a 3-starred project (i.e. medium difficulty)? >>> >>> Sorry for being pedantic, but I'm really interested in participating. >>> >>> Best regards, >>> >>> michele alberti >>> _______________________________________________ >>> MirageOS-devel mailing list >>> MirageOS-devel@lists.xenproject.org >>> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel >> >> _______________________________________________ >> MirageOS-devel mailing list >> MirageOS-devel@lists.xenproject.org >> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > > > > ------------------------------ > > Message: 5 > Date: Tue, 24 Feb 2015 11:54:11 +0000 > From: Matthew Gray > To: Robin Taylor > Cc: Michele Alberti , > mirageos-devel@lists.xenproject.org > Subject: Re: [MirageOS-devel] Question about pioneer projects > Message-ID: > > Content-Type: text/plain; charset="utf-8" > > And me! New to OCaml, but keen to learn more and contribute to MirageOS if > I can. > > Matt > > On Tue, Feb 24, 2015 at 11:49 AM, Robin Taylor wrote: > >> Thanks Amir and Michele >> >> I'd been thinking of asking exactly the same question (although my >> experience is more F# than OCaml) >> >> Best wishes >> >> Robin >> >> >> On 24 Feb 2015, at 11:42, Amir Chaudhry wrote: >> >>> Hi Michele! >>> >>> Thanks for looking over the projects and getting in touch. >>> >>> It's an *excellent* question and it's one I've also been meaning to ask. >> :) >>> I think it would be useful for us to provide (on the page itself [1]) >> some idea of what each difficulty level entails. I'll bring that up in the >> next Mirage call [2] -- which anyone is welcome to join, by the way. >>> In the meantime, if there are specific projects you're interested in >> perhaps we can discuss them here? >>> (Links are mostly to remind others of their existence) >>> >>> [1] https://github.com/mirage/mirage-www/wiki/Pioneer-Projects >>> [2] https://github.com/mirage/mirage-www/wiki/Call-Agenda >>> >>> Best wishes, >>> Amir >>> >>> On 24 Feb 2015, at 11:10, Michele Alberti wrote: >>> >>>> Hello, >>>> >>>> First of all let me say that all the MirageOS idea and implementation >> sounds really great. >>>> Not so many years ago I used OCaml for a University CS project, and >> I've recently rediscovered it (RWO book). >>>> I'd love participating into a MirageOS related project to do some real >> work in OCaml, though I am a newcomer (even if I have a CS background). >> I've given a look at your projects github webpage and I must admit that >> they all are very cool. However, let me ask a question to see whether I can >> be a good fit: >>>> what is the working knowledge of OCaml you expect for a 3-starred >> project (i.e. medium difficulty)? >>>> Sorry for being pedantic, but I'm really interested in participating. >>>> >>>> Best regards, >>>> >>>> michele alberti >>>> _______________________________________________ >>>> MirageOS-devel mailing list >>>> MirageOS-devel@lists.xenproject.org >>>> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel >>> >>> _______________________________________________ >>> MirageOS-devel mailing list >>> MirageOS-devel@lists.xenproject.org >>> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel >> >> _______________________________________________ >> MirageOS-devel mailing list >> MirageOS-devel@lists.xenproject.org >> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel >> > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > > ------------------------------ > > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > > > End of MirageOS-devel Digest, Vol 15, Issue 28 > ********************************************** _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Tue Feb 24 14:10:25 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 24 Feb 2015 14:10:25 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YQGBt-0007EG-CK; Tue, 24 Feb 2015 14:10:25 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YQGBs-0007EB-6h for mirageos-devel@lists.xenproject.org; Tue, 24 Feb 2015 14:10:24 +0000 Received: from [85.158.137.68] by server-9.bemta-3.messagelabs.com id 1B/50-02995-F468CE45; Tue, 24 Feb 2015 14:10:23 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-2.tower-31.messagelabs.com!1424787020!11838210!1 X-Originating-IP: [74.125.82.170] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23724 invoked from network); 24 Feb 2015 14:10:20 -0000 Received: from mail-we0-f170.google.com (HELO mail-we0-f170.google.com) (74.125.82.170) by server-2.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 24 Feb 2015 14:10:20 -0000 Received: by wesq59 with SMTP id q59so25482034wes.1 for ; Tue, 24 Feb 2015 06:10:20 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=nhMn9d3QePcRmE1lpgqLslheNeudyRsYsb/4K9ZwvsY=; b=QgDdzL2gbzVzWDf8jxTLB0iOy3lPZWB7/Q+zqeVKHI8OgcE6RvvyQ7sIdqcAELHpzz cjrvsRbcMmfDq5+alJQAf9DkVdm1wRlDUWCLDMoYJbeLuN5gAi6CXHB2zwOInkcWHsHq ek1WfzsTX8u19gp4qJj3/LPDBesJuDYNmZbQOGewXO6bLyoOPU9eYAMOJHCpgog6aMge IFeSThVrWVd315ZwpG99GoaBFFTviUOtzHUn0VPUKXa+jcJNgv5sJMFlc4LGnZ10XgnI uqkuhBe+auYCmS0woFezS89vp41c9lXew89qVRozoi0N7yUaXEragW8DEwPInradg31t TpTQ== X-Received: by 10.180.11.205 with SMTP id s13mr30578572wib.32.1424787019048; Tue, 24 Feb 2015 06:10:19 -0800 (PST) Received: from [192.168.0.2] (cpc25-cmbg14-2-0-cust121.5-4.cable.virginm.net. [213.106.112.122]) by mx.google.com with ESMTPSA id s19sm20685570wik.18.2015.02.24.06.10.17 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 24 Feb 2015 06:10:18 -0800 (PST) Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) From: Thomas Gazagnaire In-Reply-To: Date: Tue, 24 Feb 2015 14:10:17 +0000 Message-Id: References: To: Anil Madhavapeddy X-Mailer: Apple Mail (2.2070.6) Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] An HTTP server with TLS X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org >> module Conduit1 = Conduit_mirage.Make(Stackv41)(Vchan1) >> module Http1 = HTTP.Make(Conduit1) >> >> Can conduit deal with TLS for me? The conduit docs say "The reason >> this library exists is to provide a degree of abstraction from the >> precise SSL library used", which suggests that it should. > > Conduit_mirage doesn't support this yet -- just Conduit_lwt_unix. > Before adding it in, I was waiting for xentropyd and the C bindings > to work, which should all be in the trees. If we could now get a > mirage-skeleton example of a manual SSL server using the TCP/IP > stack directly, then the Conduit_mirage version won't be too far > behind. What are the magic runes to make that work with Conduit_lwt_unix? module H = HTTP.Make(Conduit_lwt_unix) Error: Signature mismatch: ... The type `peer' is required but not provided The type `stack' is required but not provided The module `Flow' is required but not provided I'm using conduit 0.7.2. Thomas _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Tue Feb 24 14:10:25 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 24 Feb 2015 14:10:25 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YQGBt-0007EG-CK; Tue, 24 Feb 2015 14:10:25 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YQGBs-0007EB-6h for mirageos-devel@lists.xenproject.org; Tue, 24 Feb 2015 14:10:24 +0000 Received: from [85.158.137.68] by server-9.bemta-3.messagelabs.com id 1B/50-02995-F468CE45; Tue, 24 Feb 2015 14:10:23 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-2.tower-31.messagelabs.com!1424787020!11838210!1 X-Originating-IP: [74.125.82.170] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23724 invoked from network); 24 Feb 2015 14:10:20 -0000 Received: from mail-we0-f170.google.com (HELO mail-we0-f170.google.com) (74.125.82.170) by server-2.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 24 Feb 2015 14:10:20 -0000 Received: by wesq59 with SMTP id q59so25482034wes.1 for ; Tue, 24 Feb 2015 06:10:20 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=nhMn9d3QePcRmE1lpgqLslheNeudyRsYsb/4K9ZwvsY=; b=QgDdzL2gbzVzWDf8jxTLB0iOy3lPZWB7/Q+zqeVKHI8OgcE6RvvyQ7sIdqcAELHpzz cjrvsRbcMmfDq5+alJQAf9DkVdm1wRlDUWCLDMoYJbeLuN5gAi6CXHB2zwOInkcWHsHq ek1WfzsTX8u19gp4qJj3/LPDBesJuDYNmZbQOGewXO6bLyoOPU9eYAMOJHCpgog6aMge IFeSThVrWVd315ZwpG99GoaBFFTviUOtzHUn0VPUKXa+jcJNgv5sJMFlc4LGnZ10XgnI uqkuhBe+auYCmS0woFezS89vp41c9lXew89qVRozoi0N7yUaXEragW8DEwPInradg31t TpTQ== X-Received: by 10.180.11.205 with SMTP id s13mr30578572wib.32.1424787019048; Tue, 24 Feb 2015 06:10:19 -0800 (PST) Received: from [192.168.0.2] (cpc25-cmbg14-2-0-cust121.5-4.cable.virginm.net. [213.106.112.122]) by mx.google.com with ESMTPSA id s19sm20685570wik.18.2015.02.24.06.10.17 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 24 Feb 2015 06:10:18 -0800 (PST) Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) From: Thomas Gazagnaire In-Reply-To: Date: Tue, 24 Feb 2015 14:10:17 +0000 Message-Id: References: To: Anil Madhavapeddy X-Mailer: Apple Mail (2.2070.6) Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] An HTTP server with TLS X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org >> module Conduit1 = Conduit_mirage.Make(Stackv41)(Vchan1) >> module Http1 = HTTP.Make(Conduit1) >> >> Can conduit deal with TLS for me? The conduit docs say "The reason >> this library exists is to provide a degree of abstraction from the >> precise SSL library used", which suggests that it should. > > Conduit_mirage doesn't support this yet -- just Conduit_lwt_unix. > Before adding it in, I was waiting for xentropyd and the C bindings > to work, which should all be in the trees. If we could now get a > mirage-skeleton example of a manual SSL server using the TCP/IP > stack directly, then the Conduit_mirage version won't be too far > behind. What are the magic runes to make that work with Conduit_lwt_unix? module H = HTTP.Make(Conduit_lwt_unix) Error: Signature mismatch: ... The type `peer' is required but not provided The type `stack' is required but not provided The module `Flow' is required but not provided I'm using conduit 0.7.2. Thomas _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Tue Feb 24 14:28:52 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 24 Feb 2015 14:28:52 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YQGTj-0001Zy-Dd; Tue, 24 Feb 2015 14:28:51 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YQGTh-0001Zo-Td for mirageos-devel@lists.xenproject.org; Tue, 24 Feb 2015 14:28:50 +0000 Received: from [85.158.137.68] by server-8.bemta-3.messagelabs.com id EC/03-03710-1AA8CE45; Tue, 24 Feb 2015 14:28:49 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-12.tower-31.messagelabs.com!1424788127!11783291!1 X-Originating-IP: [209.85.212.177] X-SpamReason: No, hits=0.1 required=7.0 tests=HTML_30_40,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2456 invoked from network); 24 Feb 2015 14:28:48 -0000 Received: from mail-wi0-f177.google.com (HELO mail-wi0-f177.google.com) (209.85.212.177) by server-12.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 24 Feb 2015 14:28:48 -0000 Received: by mail-wi0-f177.google.com with SMTP id bs8so25567390wib.4 for ; Tue, 24 Feb 2015 06:28:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:content-type:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; bh=J0UpOpSkYx2tZ1ta4CaRd/VriROmqnuPDYeo5c70Yeo=; b=ba4bEQEBudAt3rogm3qCDGuhxsDF7lW8XglRGmp44djoWlRfnt8Ufhw/cJ+kNws7QV pK3BfDCHqMthmewnTQVmA3ccILIw5ZNsnu+i4UvePyDsCNZSd4+JqtGyHYhNjvMJTJfn IPuwXXFODcVyjZD+TJ5EKkSOGXgEi/CEsd9NHRA0OEaJrCs8KRUId9dUeGfcNyzfP8wr oysWlps503jvjJnJ8It8d5Z6rUosL07AyYBDTJNcqiMbF0uGz3NotRfg7iAzYBDgsYzw pfcvNvWPV5mz6deicvY/c/wfv7d452awmPkzKDVapc5jWt3WvFOHi8wIl1toImxuRmiI BJIg== X-Received: by 10.194.242.6 with SMTP id wm6mr32424667wjc.7.1424788127609; Tue, 24 Feb 2015 06:28:47 -0800 (PST) Received: from [192.168.0.2] (cpc25-cmbg14-2-0-cust121.5-4.cable.virginm.net. [213.106.112.122]) by mx.google.com with ESMTPSA id u18sm60478687wjq.42.2015.02.24.06.28.46 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 24 Feb 2015 06:28:46 -0800 (PST) Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) From: Thomas Gazagnaire In-Reply-To: Date: Tue, 24 Feb 2015 14:28:46 +0000 Message-Id: References: To: Michele Alberti X-Mailer: Apple Mail (2.2070.6) Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Question about pioneer projects X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============4248067630666255208==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============4248067630666255208== Content-Type: multipart/alternative; boundary="Apple-Mail=_A3CA78FA-F394-450D-8869-EBA5FBFF18AF" --Apple-Mail=_A3CA78FA-F394-450D-8869-EBA5FBFF18AF Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Hi, Thanks for your interest. I can try to reply to your questions, but = other people on the list might maybe different opinions. > what is the working knowledge of OCaml you expect for a 3-starred = project (i.e. medium difficulty)? Don't take the number of stars as a very precise indicator. If you = already know a bit of OCaml, my advice is to pick a project in a field = you are already a bit familiar. So you will be able to improve both your = OCaml skills and to learn new things in a field you already know a = little bit. If you don't know OCaml at all, pick a field you are already = very familiar with. If you are already a good OCaml developper, simply = pick a project in a field you want to know more about. Usually = understanding complex protocols and systems requires much more effort = than improving some OCaml skills. If you are already familiar with OCaml, and If you want to know more = about Git internals and you already know a little how GC works (or if = you already know about Git but you want to know more about GCs), the GC = for Irmin would be a nice project. Feel free to ask questions on that = list of on the Irmin bug tracker[1]. One of the first step would be to = read how the Git GC works, and see if you/we can try to do something = similar in OCaml - and then later try to integrate this to ocaml-git[2] = - and finally integrate this properly into Irmin. In summary: try to connect with things you already know and like, = otherwise trying to learn both a new language and new protocol/systems = might be a bit a challenge. Thomas [1] https://github.com/mirage/irmin/issues = [2] https://github.com/mirage/ocaml-git = --Apple-Mail=_A3CA78FA-F394-450D-8869-EBA5FBFF18AF Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii Hi,

Thanks = for your interest. I can try to reply to your questions, but other = people on the list might maybe different opinions.

what is the working knowledge of OCaml you expect for a = 3-starred project (i.e. medium difficulty)?

Don't take the number of stars as a very precise = indicator. If you already know a bit of OCaml, my advice is to pick a = project in a field you are already a bit familiar. So you will be able = to improve both your OCaml skills and to learn new things in a field you = already know a little bit. If you don't know OCaml at all, pick a field = you are already very familiar with. If you are already a good OCaml = developper, simply pick a project in a field you want to know more = about. Usually understanding complex protocols and systems requires much = more effort than improving some OCaml skills.

If you are already familiar with OCaml, and If you = want to know more about Git internals and you already know a little how = GC works (or if you already know about Git but you want to know more = about GCs), the GC for Irmin would be a nice project. Feel free to ask = questions on that list of on the Irmin bug tracker[1]. One of the first = step would be to read how the Git GC works, and see if you/we can try to = do something similar in OCaml - and then later try to integrate this to = ocaml-git[2] - and finally integrate this properly into = Irmin.

In summary: try to connect = with things you already know and like, otherwise trying to learn both a = new language and new protocol/systems might be a bit a = challenge.

Thomas
[2] <= a href=3D"https://github.com/mirage/ocaml-git" = class=3D"">https://github.com/mirage/ocaml-git

= --Apple-Mail=_A3CA78FA-F394-450D-8869-EBA5FBFF18AF-- --===============4248067630666255208== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --===============4248067630666255208==-- From mirageos-devel-bounces@lists.xenproject.org Tue Feb 24 14:28:52 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 24 Feb 2015 14:28:52 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YQGTj-0001Zy-Dd; Tue, 24 Feb 2015 14:28:51 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YQGTh-0001Zo-Td for mirageos-devel@lists.xenproject.org; Tue, 24 Feb 2015 14:28:50 +0000 Received: from [85.158.137.68] by server-8.bemta-3.messagelabs.com id EC/03-03710-1AA8CE45; Tue, 24 Feb 2015 14:28:49 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-12.tower-31.messagelabs.com!1424788127!11783291!1 X-Originating-IP: [209.85.212.177] X-SpamReason: No, hits=0.1 required=7.0 tests=HTML_30_40,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2456 invoked from network); 24 Feb 2015 14:28:48 -0000 Received: from mail-wi0-f177.google.com (HELO mail-wi0-f177.google.com) (209.85.212.177) by server-12.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 24 Feb 2015 14:28:48 -0000 Received: by mail-wi0-f177.google.com with SMTP id bs8so25567390wib.4 for ; Tue, 24 Feb 2015 06:28:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:content-type:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; bh=J0UpOpSkYx2tZ1ta4CaRd/VriROmqnuPDYeo5c70Yeo=; b=ba4bEQEBudAt3rogm3qCDGuhxsDF7lW8XglRGmp44djoWlRfnt8Ufhw/cJ+kNws7QV pK3BfDCHqMthmewnTQVmA3ccILIw5ZNsnu+i4UvePyDsCNZSd4+JqtGyHYhNjvMJTJfn IPuwXXFODcVyjZD+TJ5EKkSOGXgEi/CEsd9NHRA0OEaJrCs8KRUId9dUeGfcNyzfP8wr oysWlps503jvjJnJ8It8d5Z6rUosL07AyYBDTJNcqiMbF0uGz3NotRfg7iAzYBDgsYzw pfcvNvWPV5mz6deicvY/c/wfv7d452awmPkzKDVapc5jWt3WvFOHi8wIl1toImxuRmiI BJIg== X-Received: by 10.194.242.6 with SMTP id wm6mr32424667wjc.7.1424788127609; Tue, 24 Feb 2015 06:28:47 -0800 (PST) Received: from [192.168.0.2] (cpc25-cmbg14-2-0-cust121.5-4.cable.virginm.net. [213.106.112.122]) by mx.google.com with ESMTPSA id u18sm60478687wjq.42.2015.02.24.06.28.46 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 24 Feb 2015 06:28:46 -0800 (PST) Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) From: Thomas Gazagnaire In-Reply-To: Date: Tue, 24 Feb 2015 14:28:46 +0000 Message-Id: References: To: Michele Alberti X-Mailer: Apple Mail (2.2070.6) Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Question about pioneer projects X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============4248067630666255208==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============4248067630666255208== Content-Type: multipart/alternative; boundary="Apple-Mail=_A3CA78FA-F394-450D-8869-EBA5FBFF18AF" --Apple-Mail=_A3CA78FA-F394-450D-8869-EBA5FBFF18AF Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Hi, Thanks for your interest. I can try to reply to your questions, but = other people on the list might maybe different opinions. > what is the working knowledge of OCaml you expect for a 3-starred = project (i.e. medium difficulty)? Don't take the number of stars as a very precise indicator. If you = already know a bit of OCaml, my advice is to pick a project in a field = you are already a bit familiar. So you will be able to improve both your = OCaml skills and to learn new things in a field you already know a = little bit. If you don't know OCaml at all, pick a field you are already = very familiar with. If you are already a good OCaml developper, simply = pick a project in a field you want to know more about. Usually = understanding complex protocols and systems requires much more effort = than improving some OCaml skills. If you are already familiar with OCaml, and If you want to know more = about Git internals and you already know a little how GC works (or if = you already know about Git but you want to know more about GCs), the GC = for Irmin would be a nice project. Feel free to ask questions on that = list of on the Irmin bug tracker[1]. One of the first step would be to = read how the Git GC works, and see if you/we can try to do something = similar in OCaml - and then later try to integrate this to ocaml-git[2] = - and finally integrate this properly into Irmin. In summary: try to connect with things you already know and like, = otherwise trying to learn both a new language and new protocol/systems = might be a bit a challenge. Thomas [1] https://github.com/mirage/irmin/issues = [2] https://github.com/mirage/ocaml-git = --Apple-Mail=_A3CA78FA-F394-450D-8869-EBA5FBFF18AF Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii Hi,

Thanks = for your interest. I can try to reply to your questions, but other = people on the list might maybe different opinions.

what is the working knowledge of OCaml you expect for a = 3-starred project (i.e. medium difficulty)?

Don't take the number of stars as a very precise = indicator. If you already know a bit of OCaml, my advice is to pick a = project in a field you are already a bit familiar. So you will be able = to improve both your OCaml skills and to learn new things in a field you = already know a little bit. If you don't know OCaml at all, pick a field = you are already very familiar with. If you are already a good OCaml = developper, simply pick a project in a field you want to know more = about. Usually understanding complex protocols and systems requires much = more effort than improving some OCaml skills.

If you are already familiar with OCaml, and If you = want to know more about Git internals and you already know a little how = GC works (or if you already know about Git but you want to know more = about GCs), the GC for Irmin would be a nice project. Feel free to ask = questions on that list of on the Irmin bug tracker[1]. One of the first = step would be to read how the Git GC works, and see if you/we can try to = do something similar in OCaml - and then later try to integrate this to = ocaml-git[2] - and finally integrate this properly into = Irmin.

In summary: try to connect = with things you already know and like, otherwise trying to learn both a = new language and new protocol/systems might be a bit a = challenge.

Thomas
[2] <= a href=3D"https://github.com/mirage/ocaml-git" = class=3D"">https://github.com/mirage/ocaml-git

= --Apple-Mail=_A3CA78FA-F394-450D-8869-EBA5FBFF18AF-- --===============4248067630666255208== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --===============4248067630666255208==-- From mirageos-devel-bounces@lists.xenproject.org Tue Feb 24 15:36:52 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 24 Feb 2015 15:36:52 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YQHXU-0003Ex-38; Tue, 24 Feb 2015 15:36:48 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YQHXS-0003Ei-QB for mirageos-devel@lists.xenproject.org; Tue, 24 Feb 2015 15:36:46 +0000 Received: from [85.158.137.68] by server-16.bemta-3.messagelabs.com id 5B/51-02745-E8A9CE45; Tue, 24 Feb 2015 15:36:46 +0000 X-Env-Sender: richard.mortier@gmail.com X-Msg-Ref: server-3.tower-31.messagelabs.com!1424792204!11929705!1 X-Originating-IP: [209.85.192.41] X-SpamReason: No, hits=0.6 required=7.0 tests=MAILTO_TO_SPAM_ADDR, RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17146 invoked from network); 24 Feb 2015 15:36:45 -0000 Received: from mail-qg0-f41.google.com (HELO mail-qg0-f41.google.com) (209.85.192.41) by server-3.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 24 Feb 2015 15:36:45 -0000 Received: by mail-qg0-f41.google.com with SMTP id i50so30444719qgf.0 for ; Tue, 24 Feb 2015 07:36:44 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=BVV5XJbb8I00CuJUBCnxCPkf0lPK13QZ0NsdXJwmNtA=; b=mdt6lbwvQdxBQhMT3nHsC0hva6xBimc3cnGHWZX/KHFXJvfQtvpZxxA2gQ+GcoliiX 00PRFwLFRGDMlBZBoOAEPmTJp6h9h0vK4h06XaQsFZ//JOZBh7cOMpHX3Ve27vJOy2de 94Yx0nfwvUeOUXaAgq+jCx4FK+WEhvka+3GW2gr0y/abi1WAsZnCaQ7EKRBFWWHt5QJ5 PBfUoduped7OQhwbDRsOy8SlJeM65kvO29l/TWEdkuGVd3RROzs3Ezzoi51DtMKX0E7J H8lSFT7qRZd2ifbeIHG7KXP7UNXROgNJa54DP18HptcbshOPxDxkN2PfoNpj0ycBc39w BPGw== X-Received: by 10.229.175.131 with SMTP id ba3mr38065653qcb.3.1424792203993; Tue, 24 Feb 2015 07:36:43 -0800 (PST) Received: from mail-qg0-f49.google.com (mail-qg0-f49.google.com. [209.85.192.49]) by mx.google.com with ESMTPSA id k76sm9960837qhc.28.2015.02.24.07.36.42 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 24 Feb 2015 07:36:43 -0800 (PST) Received: by mail-qg0-f49.google.com with SMTP id q107so30450832qgd.8 for ; Tue, 24 Feb 2015 07:36:42 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.140.238.79 with SMTP id j76mr21546334qhc.83.1424792202865; Tue, 24 Feb 2015 07:36:42 -0800 (PST) Received: by 10.140.92.245 with HTTP; Tue, 24 Feb 2015 07:36:42 -0800 (PST) In-Reply-To: <99F4240E-C4E6-4BD9-BA99-E986A48C45A4@cam.ac.uk> References: <17F3E677-EB2E-4465-B213-B1C682F33C21@badgermind.net> <99F4240E-C4E6-4BD9-BA99-E986A48C45A4@cam.ac.uk> Date: Tue, 24 Feb 2015 15:36:42 +0000 Message-ID: From: Richard Mortier To: Amir Chaudhry Cc: mirageos-devel Subject: Re: [MirageOS-devel] Question about pioneer projects X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 24 February 2015 at 13:05, Amir Chaudhry wrote: > > On 24 Feb 2015, at 12:56, yiorgos wrote: > >> ...Do you guys think that >> developing can be done using this way or there will be a quite great >> amount of setting up/debugging VirtualBox (eg network interfaces etc) > > Magnus wrote a post about his VirtualBox set up for Mirage development. > http://www.skjegstad.com/blog/2015/01/19/mirageos-xen-virtualbox/ We also have a repo with scripts/config for setting up vagrant boxes using packer. Might be a little out of date now but used to work. https://github.com/mirage/mirage-vagrant-vms (FWIW I've been trying to update it in the background to implement Magnus' instructions from the post mentioned above, but haven't finished yet. https://github.com/mor1/mirage-vagrant-vms if anyone wants to pick up from where I've currently stalled... :) -- Richard Mortier richard.mortier@cl.cam.ac.uk _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Tue Feb 24 15:36:52 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 24 Feb 2015 15:36:52 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YQHXU-0003Ex-38; Tue, 24 Feb 2015 15:36:48 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YQHXS-0003Ei-QB for mirageos-devel@lists.xenproject.org; Tue, 24 Feb 2015 15:36:46 +0000 Received: from [85.158.137.68] by server-16.bemta-3.messagelabs.com id 5B/51-02745-E8A9CE45; Tue, 24 Feb 2015 15:36:46 +0000 X-Env-Sender: richard.mortier@gmail.com X-Msg-Ref: server-3.tower-31.messagelabs.com!1424792204!11929705!1 X-Originating-IP: [209.85.192.41] X-SpamReason: No, hits=0.6 required=7.0 tests=MAILTO_TO_SPAM_ADDR, RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17146 invoked from network); 24 Feb 2015 15:36:45 -0000 Received: from mail-qg0-f41.google.com (HELO mail-qg0-f41.google.com) (209.85.192.41) by server-3.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 24 Feb 2015 15:36:45 -0000 Received: by mail-qg0-f41.google.com with SMTP id i50so30444719qgf.0 for ; Tue, 24 Feb 2015 07:36:44 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=BVV5XJbb8I00CuJUBCnxCPkf0lPK13QZ0NsdXJwmNtA=; b=mdt6lbwvQdxBQhMT3nHsC0hva6xBimc3cnGHWZX/KHFXJvfQtvpZxxA2gQ+GcoliiX 00PRFwLFRGDMlBZBoOAEPmTJp6h9h0vK4h06XaQsFZ//JOZBh7cOMpHX3Ve27vJOy2de 94Yx0nfwvUeOUXaAgq+jCx4FK+WEhvka+3GW2gr0y/abi1WAsZnCaQ7EKRBFWWHt5QJ5 PBfUoduped7OQhwbDRsOy8SlJeM65kvO29l/TWEdkuGVd3RROzs3Ezzoi51DtMKX0E7J H8lSFT7qRZd2ifbeIHG7KXP7UNXROgNJa54DP18HptcbshOPxDxkN2PfoNpj0ycBc39w BPGw== X-Received: by 10.229.175.131 with SMTP id ba3mr38065653qcb.3.1424792203993; Tue, 24 Feb 2015 07:36:43 -0800 (PST) Received: from mail-qg0-f49.google.com (mail-qg0-f49.google.com. [209.85.192.49]) by mx.google.com with ESMTPSA id k76sm9960837qhc.28.2015.02.24.07.36.42 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 24 Feb 2015 07:36:43 -0800 (PST) Received: by mail-qg0-f49.google.com with SMTP id q107so30450832qgd.8 for ; Tue, 24 Feb 2015 07:36:42 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.140.238.79 with SMTP id j76mr21546334qhc.83.1424792202865; Tue, 24 Feb 2015 07:36:42 -0800 (PST) Received: by 10.140.92.245 with HTTP; Tue, 24 Feb 2015 07:36:42 -0800 (PST) In-Reply-To: <99F4240E-C4E6-4BD9-BA99-E986A48C45A4@cam.ac.uk> References: <17F3E677-EB2E-4465-B213-B1C682F33C21@badgermind.net> <99F4240E-C4E6-4BD9-BA99-E986A48C45A4@cam.ac.uk> Date: Tue, 24 Feb 2015 15:36:42 +0000 Message-ID: From: Richard Mortier To: Amir Chaudhry Cc: mirageos-devel Subject: Re: [MirageOS-devel] Question about pioneer projects X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 24 February 2015 at 13:05, Amir Chaudhry wrote: > > On 24 Feb 2015, at 12:56, yiorgos wrote: > >> ...Do you guys think that >> developing can be done using this way or there will be a quite great >> amount of setting up/debugging VirtualBox (eg network interfaces etc) > > Magnus wrote a post about his VirtualBox set up for Mirage development. > http://www.skjegstad.com/blog/2015/01/19/mirageos-xen-virtualbox/ We also have a repo with scripts/config for setting up vagrant boxes using packer. Might be a little out of date now but used to work. https://github.com/mirage/mirage-vagrant-vms (FWIW I've been trying to update it in the background to implement Magnus' instructions from the post mentioned above, but haven't finished yet. https://github.com/mor1/mirage-vagrant-vms if anyone wants to pick up from where I've currently stalled... :) -- Richard Mortier richard.mortier@cl.cam.ac.uk _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Tue Feb 24 16:53:35 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 24 Feb 2015 16:53:35 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YQIji-0007dS-7j; Tue, 24 Feb 2015 16:53:30 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YQIjg-0007cZ-8N for mirageos-devel@lists.xenproject.org; Tue, 24 Feb 2015 16:53:28 +0000 Received: from [193.109.254.147] by server-5.bemta-14.messagelabs.com id BD/81-03170-78CACE45; Tue, 24 Feb 2015 16:53:27 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-6.tower-27.messagelabs.com!1424796804!12533828!1 X-Originating-IP: [5.153.225.51] X-SpamReason: No, hits=0.3 required=7.0 tests=HTML_30_40,HTML_MESSAGE, RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3410 invoked from network); 24 Feb 2015 16:53:25 -0000 Received: from bark.recoil.org (HELO bark.recoil.org) (5.153.225.51) by server-6.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 24 Feb 2015 16:53:25 -0000 Received: from [192.168.1.39] (cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net [86.30.244.239]); by bark.recoil.org (OpenSMTPD) with ESMTPSA id b40d4459; TLS version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO; Tue, 24 Feb 2015 16:53:23 +0000 (GMT) Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) From: Anil Madhavapeddy In-Reply-To: Date: Tue, 24 Feb 2015 16:53:22 +0000 Message-Id: <82DDA917-66F6-451E-B51A-9A007BD34682@recoil.org> References: To: Thomas Gazagnaire X-Mailer: Apple Mail (2.2070.6) Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Question about pioneer projects X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0365134697455150229==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============0365134697455150229== Content-Type: multipart/alternative; boundary="Apple-Mail=_0ADD84CE-3465-4CA7-9B8C-E7B0E09C73D7" --Apple-Mail=_0ADD84CE-3465-4CA7-9B8C-E7B0E09C73D7 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On 24 Feb 2015, at 14:28, Thomas Gazagnaire = wrote: >=20 > In summary: try to connect with things you already know and like, = otherwise trying to learn both a new language and new protocol/systems = might be a bit a challenge. I can't agree with this enough. The way I personally engage with new = systems is to be quite goal oriented. E.g., your goals could be: - 'have fun': you can't beat just deploying a homepage unikernel and = prodding it in interesting ways or switching your personal homepage over = it (see Mindy's blog posts on this topic). I'd recommend buying a = Cubieboard2 and using the xen-arm-builder to get your own home = deployment up and running with a minimum of fuss. Writing blog posts = about your learning process is *extremely* useful to help document = common problems for other people. - 'learn OCaml': I'd again recommend the web framework angle for this, = since it's a very quick way to get results. Rudi's Opium framework is a = nice route into getting into building some real tools. Although it's = often viewed as boring, a *really* good way to learn the language is to = fork a protocol library and add some test cases. You will learn your = way through the build systems, basic abstraction facilities and use of = APIs quite quickly, as well as contributing very valuable tests back to = the project. - 'implement a protocol': if you know one protocol (e.g. uPNP) and would = like to scratch an itch ('turn on my Sonos speakers') then starting a = standalone project and letting the list know works well. Luke Dunstan = has been doing this with his multicast DNS implementation (which I'm = myself itching to try shortly!). - 'learn hypervisors': Mirage has a wealth of libraries that make it the = easiest way to learn how Xen works. If you want to really dive into = cloud computing, then the Xen stack and Mirage libraries are a quite = superb way to pick up the concepts. The pioneer projects are just guidelines to spark off your thinking -- = you should mostly be motivated by your own problems and interests, and = we're happy to swap things around on that list as appropriate or useful. = Above all: please don't be afraid to ask questions on the list. -anil= --Apple-Mail=_0ADD84CE-3465-4CA7-9B8C-E7B0E09C73D7 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii On 24 Feb 2015, at 14:28, Thomas Gazagnaire <thomas@gazagnaire.org> wrote:

In summary: try to = connect with things you already know and like, otherwise trying to learn = both a new language and new protocol/systems might be a bit a = challenge.

I = can't agree with this enough.  The way I personally engage with new = systems is to be quite goal oriented. E.g.,  your goals could = be:

- 'have = fun': you can't beat just deploying a homepage unikernel and prodding it = in interesting ways or switching your personal homepage over it (see = Mindy's blog posts on this topic).  I'd recommend buying a = Cubieboard2 and using the xen-arm-builder to get your own home = deployment up and running with a minimum of fuss.  Writing blog = posts about your learning process is *extremely* useful to help document = common problems for other people.

- 'learn OCaml': I'd again recommend = the web framework angle for this, since it's a very quick way to get = results. Rudi's Opium framework is a nice route into getting into = building some real tools.  Although it's often viewed as boring, a = *really* good way to learn the language is to fork a protocol library = and add some test cases.  You will learn your way through the build = systems, basic abstraction facilities and use of APIs quite quickly, as = well as contributing very valuable tests back to the project.

- 'implement a = protocol': if you know one protocol (e.g. uPNP) and would like to = scratch an itch ('turn on my Sonos speakers') then starting a standalone = project and letting the list know works well.  Luke Dunstan has = been doing this with his multicast DNS implementation (which I'm myself = itching to try shortly!).

- 'learn hypervisors': Mirage has a wealth of libraries that = make it the easiest way to learn how Xen works.  If you want to = really dive into cloud computing, then the Xen stack and Mirage = libraries are a quite superb way to pick up the concepts.

The pioneer projects are = just guidelines to spark off your thinking -- you should mostly be = motivated by your own problems and interests, and we're happy to swap = things around on that list as appropriate or useful.  Above all: = please don't be afraid to ask questions on the list.

-anil
= --Apple-Mail=_0ADD84CE-3465-4CA7-9B8C-E7B0E09C73D7-- --===============0365134697455150229== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --===============0365134697455150229==-- From mirageos-devel-bounces@lists.xenproject.org Tue Feb 24 16:53:35 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 24 Feb 2015 16:53:35 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YQIji-0007dS-7j; Tue, 24 Feb 2015 16:53:30 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YQIjg-0007cZ-8N for mirageos-devel@lists.xenproject.org; Tue, 24 Feb 2015 16:53:28 +0000 Received: from [193.109.254.147] by server-5.bemta-14.messagelabs.com id BD/81-03170-78CACE45; Tue, 24 Feb 2015 16:53:27 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-6.tower-27.messagelabs.com!1424796804!12533828!1 X-Originating-IP: [5.153.225.51] X-SpamReason: No, hits=0.3 required=7.0 tests=HTML_30_40,HTML_MESSAGE, RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3410 invoked from network); 24 Feb 2015 16:53:25 -0000 Received: from bark.recoil.org (HELO bark.recoil.org) (5.153.225.51) by server-6.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 24 Feb 2015 16:53:25 -0000 Received: from [192.168.1.39] (cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net [86.30.244.239]); by bark.recoil.org (OpenSMTPD) with ESMTPSA id b40d4459; TLS version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO; Tue, 24 Feb 2015 16:53:23 +0000 (GMT) Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) From: Anil Madhavapeddy In-Reply-To: Date: Tue, 24 Feb 2015 16:53:22 +0000 Message-Id: <82DDA917-66F6-451E-B51A-9A007BD34682@recoil.org> References: To: Thomas Gazagnaire X-Mailer: Apple Mail (2.2070.6) Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Question about pioneer projects X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0365134697455150229==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============0365134697455150229== Content-Type: multipart/alternative; boundary="Apple-Mail=_0ADD84CE-3465-4CA7-9B8C-E7B0E09C73D7" --Apple-Mail=_0ADD84CE-3465-4CA7-9B8C-E7B0E09C73D7 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On 24 Feb 2015, at 14:28, Thomas Gazagnaire = wrote: >=20 > In summary: try to connect with things you already know and like, = otherwise trying to learn both a new language and new protocol/systems = might be a bit a challenge. I can't agree with this enough. The way I personally engage with new = systems is to be quite goal oriented. E.g., your goals could be: - 'have fun': you can't beat just deploying a homepage unikernel and = prodding it in interesting ways or switching your personal homepage over = it (see Mindy's blog posts on this topic). I'd recommend buying a = Cubieboard2 and using the xen-arm-builder to get your own home = deployment up and running with a minimum of fuss. Writing blog posts = about your learning process is *extremely* useful to help document = common problems for other people. - 'learn OCaml': I'd again recommend the web framework angle for this, = since it's a very quick way to get results. Rudi's Opium framework is a = nice route into getting into building some real tools. Although it's = often viewed as boring, a *really* good way to learn the language is to = fork a protocol library and add some test cases. You will learn your = way through the build systems, basic abstraction facilities and use of = APIs quite quickly, as well as contributing very valuable tests back to = the project. - 'implement a protocol': if you know one protocol (e.g. uPNP) and would = like to scratch an itch ('turn on my Sonos speakers') then starting a = standalone project and letting the list know works well. Luke Dunstan = has been doing this with his multicast DNS implementation (which I'm = myself itching to try shortly!). - 'learn hypervisors': Mirage has a wealth of libraries that make it the = easiest way to learn how Xen works. If you want to really dive into = cloud computing, then the Xen stack and Mirage libraries are a quite = superb way to pick up the concepts. The pioneer projects are just guidelines to spark off your thinking -- = you should mostly be motivated by your own problems and interests, and = we're happy to swap things around on that list as appropriate or useful. = Above all: please don't be afraid to ask questions on the list. -anil= --Apple-Mail=_0ADD84CE-3465-4CA7-9B8C-E7B0E09C73D7 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii On 24 Feb 2015, at 14:28, Thomas Gazagnaire <thomas@gazagnaire.org> wrote:

In summary: try to = connect with things you already know and like, otherwise trying to learn = both a new language and new protocol/systems might be a bit a = challenge.

I = can't agree with this enough.  The way I personally engage with new = systems is to be quite goal oriented. E.g.,  your goals could = be:

- 'have = fun': you can't beat just deploying a homepage unikernel and prodding it = in interesting ways or switching your personal homepage over it (see = Mindy's blog posts on this topic).  I'd recommend buying a = Cubieboard2 and using the xen-arm-builder to get your own home = deployment up and running with a minimum of fuss.  Writing blog = posts about your learning process is *extremely* useful to help document = common problems for other people.

- 'learn OCaml': I'd again recommend = the web framework angle for this, since it's a very quick way to get = results. Rudi's Opium framework is a nice route into getting into = building some real tools.  Although it's often viewed as boring, a = *really* good way to learn the language is to fork a protocol library = and add some test cases.  You will learn your way through the build = systems, basic abstraction facilities and use of APIs quite quickly, as = well as contributing very valuable tests back to the project.

- 'implement a = protocol': if you know one protocol (e.g. uPNP) and would like to = scratch an itch ('turn on my Sonos speakers') then starting a standalone = project and letting the list know works well.  Luke Dunstan has = been doing this with his multicast DNS implementation (which I'm myself = itching to try shortly!).

- 'learn hypervisors': Mirage has a wealth of libraries that = make it the easiest way to learn how Xen works.  If you want to = really dive into cloud computing, then the Xen stack and Mirage = libraries are a quite superb way to pick up the concepts.

The pioneer projects are = just guidelines to spark off your thinking -- you should mostly be = motivated by your own problems and interests, and we're happy to swap = things around on that list as appropriate or useful.  Above all: = please don't be afraid to ask questions on the list.

-anil
= --Apple-Mail=_0ADD84CE-3465-4CA7-9B8C-E7B0E09C73D7-- --===============0365134697455150229== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --===============0365134697455150229==-- From mirageos-devel-bounces@lists.xenproject.org Tue Feb 24 17:07:16 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 24 Feb 2015 17:07:16 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YQIx1-00012G-J7; Tue, 24 Feb 2015 17:07:15 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YQIwz-00010y-Ec for mirageos-devel@lists.xenproject.org; Tue, 24 Feb 2015 17:07:13 +0000 Received: from [193.109.254.147] by server-4.bemta-14.messagelabs.com id 8D/95-02994-0CFACE45; Tue, 24 Feb 2015 17:07:12 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-4.tower-27.messagelabs.com!1424797630!12569132!1 X-Originating-IP: [5.153.225.51] X-SpamReason: No, hits=0.5 required=7.0 tests=MAILTO_TO_SPAM_ADDR, RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 18560 invoked from network); 24 Feb 2015 17:07:12 -0000 Received: from bark.recoil.org (HELO bark.recoil.org) (5.153.225.51) by server-4.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 24 Feb 2015 17:07:12 -0000 Received: from [192.168.1.39] (cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net [86.30.244.239]); by bark.recoil.org (OpenSMTPD) with ESMTPSA id 19e0a56f; TLS version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO; Tue, 24 Feb 2015 17:07:10 +0000 (GMT) Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) From: Anil Madhavapeddy In-Reply-To: <99F4240E-C4E6-4BD9-BA99-E986A48C45A4@cam.ac.uk> Date: Tue, 24 Feb 2015 17:07:09 +0000 Message-Id: <56721876-196E-447E-AB41-4F2714A1C3C5@recoil.org> References: <17F3E677-EB2E-4465-B213-B1C682F33C21@badgermind.net> <99F4240E-C4E6-4BD9-BA99-E986A48C45A4@cam.ac.uk> To: Amir M Chaudhry X-Mailer: Apple Mail (2.2070.6) Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Question about pioneer projects X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 24 Feb 2015, at 13:05, Amir Chaudhry wrote: > > > On 24 Feb 2015, at 12:56, yiorgos wrote: > >> +1! >> >> I know about three ways set up a developing MirageOS environment. >> >> 1) VirtualBox + Xen + MirageOS VMs >> 2) Xen on bare metal >> 3) CubieBoard + Xen + MirageOS >> >> Ways 1, 2 look more easily accessible to people. >> >> About 1) Do you guys think that >> developing can be done using this way or there will be a quite great >> amount of setting up/debugging VirtualBox (eg network interfaces etc) > > Magnus wrote a post about his VirtualBox set up for Mirage development. > http://www.skjegstad.com/blog/2015/01/19/mirageos-xen-virtualbox/ It would be great to get these instructions up on the main openmirage.org page somewhere. -anil _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Tue Feb 24 17:07:16 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 24 Feb 2015 17:07:16 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YQIx1-00012G-J7; Tue, 24 Feb 2015 17:07:15 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YQIwz-00010y-Ec for mirageos-devel@lists.xenproject.org; Tue, 24 Feb 2015 17:07:13 +0000 Received: from [193.109.254.147] by server-4.bemta-14.messagelabs.com id 8D/95-02994-0CFACE45; Tue, 24 Feb 2015 17:07:12 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-4.tower-27.messagelabs.com!1424797630!12569132!1 X-Originating-IP: [5.153.225.51] X-SpamReason: No, hits=0.5 required=7.0 tests=MAILTO_TO_SPAM_ADDR, RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 18560 invoked from network); 24 Feb 2015 17:07:12 -0000 Received: from bark.recoil.org (HELO bark.recoil.org) (5.153.225.51) by server-4.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 24 Feb 2015 17:07:12 -0000 Received: from [192.168.1.39] (cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net [86.30.244.239]); by bark.recoil.org (OpenSMTPD) with ESMTPSA id 19e0a56f; TLS version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO; Tue, 24 Feb 2015 17:07:10 +0000 (GMT) Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) From: Anil Madhavapeddy In-Reply-To: <99F4240E-C4E6-4BD9-BA99-E986A48C45A4@cam.ac.uk> Date: Tue, 24 Feb 2015 17:07:09 +0000 Message-Id: <56721876-196E-447E-AB41-4F2714A1C3C5@recoil.org> References: <17F3E677-EB2E-4465-B213-B1C682F33C21@badgermind.net> <99F4240E-C4E6-4BD9-BA99-E986A48C45A4@cam.ac.uk> To: Amir M Chaudhry X-Mailer: Apple Mail (2.2070.6) Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Question about pioneer projects X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 24 Feb 2015, at 13:05, Amir Chaudhry wrote: > > > On 24 Feb 2015, at 12:56, yiorgos wrote: > >> +1! >> >> I know about three ways set up a developing MirageOS environment. >> >> 1) VirtualBox + Xen + MirageOS VMs >> 2) Xen on bare metal >> 3) CubieBoard + Xen + MirageOS >> >> Ways 1, 2 look more easily accessible to people. >> >> About 1) Do you guys think that >> developing can be done using this way or there will be a quite great >> amount of setting up/debugging VirtualBox (eg network interfaces etc) > > Magnus wrote a post about his VirtualBox set up for Mirage development. > http://www.skjegstad.com/blog/2015/01/19/mirageos-xen-virtualbox/ It would be great to get these instructions up on the main openmirage.org page somewhere. -anil _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Tue Feb 24 17:11:05 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 24 Feb 2015 17:11:05 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YQJ0j-0001tT-E4; Tue, 24 Feb 2015 17:11:05 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YQJ0i-0001tM-MN for mirageos-devel@lists.xenproject.org; Tue, 24 Feb 2015 17:11:04 +0000 Received: from [85.158.137.68] by server-4.bemta-3.messagelabs.com id E2/40-03185-7A0BCE45; Tue, 24 Feb 2015 17:11:03 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-3.tower-31.messagelabs.com!1424797862!11953845!1 X-Originating-IP: [5.153.225.51] X-SpamReason: No, hits=0.2 required=7.0 tests=RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22578 invoked from network); 24 Feb 2015 17:11:03 -0000 Received: from bark.recoil.org (HELO bark.recoil.org) (5.153.225.51) by server-3.tower-31.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 24 Feb 2015 17:11:03 -0000 Received: from [192.168.1.39] (cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net [86.30.244.239]); by bark.recoil.org (OpenSMTPD) with ESMTPSA id 330c3db3; TLS version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO; Tue, 24 Feb 2015 17:11:02 +0000 (GMT) Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) From: Anil Madhavapeddy In-Reply-To: Date: Tue, 24 Feb 2015 17:11:01 +0000 Message-Id: References: <17F3E677-EB2E-4465-B213-B1C682F33C21@badgermind.net> To: yiorgos X-Mailer: Apple Mail (2.2070.6) Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Question about pioneer projects X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 24 Feb 2015, at 12:56, yiorgos wrote: > > +1! > > I know about three ways set up a developing MirageOS environment. > > 1) VirtualBox + Xen + MirageOS VMs > 2) Xen on bare metal > 3) CubieBoard + Xen + MirageOS > > Ways 1, 2 look more easily accessible to people. > > About 1) Do you guys think that > developing can be done using this way or there will be a quite great > amount of setting up/debugging VirtualBox (eg network interfaces etc) > > About 2) Do you have a preferable host OS for dom0? The secret to MirageOS hacking is that most of the time, you don't really need a Xen environment at all. The vast bulk of protocol development can be done in Unix with user-level networking, and then a final switch to a Cubieboard2 or x86 Xen host is an easy way to check that the Xen mode works. So things like the DHCP server can all just be done without any particular need for a Xen installation. -anil _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Tue Feb 24 17:11:05 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 24 Feb 2015 17:11:05 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YQJ0j-0001tT-E4; Tue, 24 Feb 2015 17:11:05 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YQJ0i-0001tM-MN for mirageos-devel@lists.xenproject.org; Tue, 24 Feb 2015 17:11:04 +0000 Received: from [85.158.137.68] by server-4.bemta-3.messagelabs.com id E2/40-03185-7A0BCE45; Tue, 24 Feb 2015 17:11:03 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-3.tower-31.messagelabs.com!1424797862!11953845!1 X-Originating-IP: [5.153.225.51] X-SpamReason: No, hits=0.2 required=7.0 tests=RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22578 invoked from network); 24 Feb 2015 17:11:03 -0000 Received: from bark.recoil.org (HELO bark.recoil.org) (5.153.225.51) by server-3.tower-31.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 24 Feb 2015 17:11:03 -0000 Received: from [192.168.1.39] (cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net [86.30.244.239]); by bark.recoil.org (OpenSMTPD) with ESMTPSA id 330c3db3; TLS version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO; Tue, 24 Feb 2015 17:11:02 +0000 (GMT) Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) From: Anil Madhavapeddy In-Reply-To: Date: Tue, 24 Feb 2015 17:11:01 +0000 Message-Id: References: <17F3E677-EB2E-4465-B213-B1C682F33C21@badgermind.net> To: yiorgos X-Mailer: Apple Mail (2.2070.6) Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Question about pioneer projects X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 24 Feb 2015, at 12:56, yiorgos wrote: > > +1! > > I know about three ways set up a developing MirageOS environment. > > 1) VirtualBox + Xen + MirageOS VMs > 2) Xen on bare metal > 3) CubieBoard + Xen + MirageOS > > Ways 1, 2 look more easily accessible to people. > > About 1) Do you guys think that > developing can be done using this way or there will be a quite great > amount of setting up/debugging VirtualBox (eg network interfaces etc) > > About 2) Do you have a preferable host OS for dom0? The secret to MirageOS hacking is that most of the time, you don't really need a Xen environment at all. The vast bulk of protocol development can be done in Unix with user-level networking, and then a final switch to a Cubieboard2 or x86 Xen host is an easy way to check that the Xen mode works. So things like the DHCP server can all just be done without any particular need for a Xen installation. -anil _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Tue Feb 24 17:46:54 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 24 Feb 2015 17:46:54 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YQJZN-0007uU-Lq; Tue, 24 Feb 2015 17:46:53 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YQJZM-0007uN-1F for mirageos-devel@lists.xenproject.org; Tue, 24 Feb 2015 17:46:52 +0000 Received: from [193.109.254.147] by server-3.bemta-14.messagelabs.com id 8E/7A-10964-B09BCE45; Tue, 24 Feb 2015 17:46:51 +0000 X-Env-Sender: matthew.thomas.gray@gmail.com X-Msg-Ref: server-4.tower-27.messagelabs.com!1424800009!12575425!1 X-Originating-IP: [209.85.192.53] X-SpamReason: No, hits=0.7 required=7.0 tests=HTML_30_40,HTML_MESSAGE, MAILTO_TO_SPAM_ADDR,RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5673 invoked from network); 24 Feb 2015 17:46:50 -0000 Received: from mail-qg0-f53.google.com (HELO mail-qg0-f53.google.com) (209.85.192.53) by server-4.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 24 Feb 2015 17:46:50 -0000 Received: by mail-qg0-f53.google.com with SMTP id f51so31281306qge.12 for ; Tue, 24 Feb 2015 09:46:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=3oFlwHhKb4EkyK8iImY8lpsNcxw5EA9MVRxBcybV+q8=; b=H41UJ2Ey/mDGYf6xX+UlU1UQ4Lq2LOqxXi4ANldyLX5ym0DHlxmS6GHyIpDPfdu/s8 4hyJ3/aP2CZX2q6hoFXmyXkgxiIhZZjgHa1s1matq4PooodMQS3Yn+5Ww5JBbQ1A119T 7elATUlvZj+w7ia5DK7ju+sOg9gIvyKTkX0OrShf3FXU3TO6PbKSLEWpbInUygdJ12gr 6e1fED3zUokK1AzxXjofHpuHUcoxI+8buI2+y5k5AlULRgpvRPp5NWLEwFrUH0ti0Uto Ym+2cQZPJ5jTbq3idRQNmFtxhKeigj9TZ2sr2oYI8gKpx6IVHVbtEsvypJMJkoKCchfe dtUg== MIME-Version: 1.0 X-Received: by 10.140.17.9 with SMTP id 9mr36717904qgc.21.1424800009008; Tue, 24 Feb 2015 09:46:49 -0800 (PST) Received: by 10.140.46.168 with HTTP; Tue, 24 Feb 2015 09:46:48 -0800 (PST) In-Reply-To: References: <17F3E677-EB2E-4465-B213-B1C682F33C21@badgermind.net> <99F4240E-C4E6-4BD9-BA99-E986A48C45A4@cam.ac.uk> Date: Tue, 24 Feb 2015 17:46:48 +0000 Message-ID: From: Matthew Gray To: Richard Mortier Cc: mirageos-devel Subject: Re: [MirageOS-devel] Question about pioneer projects X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2132860737361179157==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============2132860737361179157== Content-Type: multipart/alternative; boundary=001a11c0b36a69bbe2050fd91ae2 --001a11c0b36a69bbe2050fd91ae2 Content-Type: text/plain; charset=UTF-8 On Tue, Feb 24, 2015 at 3:36 PM, Richard Mortier < richard.mortier@cl.cam.ac.uk> wrote: > On 24 February 2015 at 13:05, Amir Chaudhry wrote: > > > > On 24 Feb 2015, at 12:56, yiorgos wrote: > > > >> ...Do you guys think that > >> developing can be done using this way or there will be a quite great > >> amount of setting up/debugging VirtualBox (eg network interfaces etc) > > > > Magnus wrote a post about his VirtualBox set up for Mirage development. > > http://www.skjegstad.com/blog/2015/01/19/mirageos-xen-virtualbox/ > > We also have a repo with scripts/config for setting up vagrant boxes > using packer. Might be a little out of date now but used to work. > > https://github.com/mirage/mirage-vagrant-vms > > (FWIW I've been trying to update it in the background to implement > Magnus' instructions from the post mentioned above, but haven't > finished yet. https://github.com/mor1/mirage-vagrant-vms if anyone > wants to pick up from where I've currently stalled... :) I've been working away slowly at this: https://github.com/mattgray/mirage-xen-virtualbox which is basically Magnus' blog post made into a packer template. I'm aiming at a system where I can compile a unikernel on my host machine, and then run a command that will push the kernel to the vagrant VM, run it (exposing the console somehow), and assign a DNS name using Avahi to the DHCP-assigned IPv4 address. Still pondering that one, but at the moment the box there is able the build and run MirageOS apps. You'll just need to share a directory using NFS. I'll update the docs now with a simple walkthrough. Matt --001a11c0b36a69bbe2050fd91ae2 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On T= ue, Feb 24, 2015 at 3:36 PM, Richard Mortier <richard.mortier@= cl.cam.ac.uk> wrote:
On = 24 February 2015 at 13:05, Amir Chaudhry <amc79@cam.ac.uk> wrote:
>
> On 24 Feb 2015, at 12:56, yiorgos <antibra@hotmail.com> wrote:
>
>> ...Do you guys think that
>> developing can be done using this way or there wi= ll be a quite great
>> amount of setting up/debugging VirtualBox (eg network interfaces e= tc)
>
> Magnus wrote a post about his VirtualBox set up for Mirage development= .
> http://www.skjegstad.com/blog/2015/01/19/mirageos= -xen-virtualbox/

We also have a repo with scripts/config for setting up vagrant boxes=
using packer. Might be a little out of date now but used to work.

= https://github.com/mirage/mirage-vagrant-vms

(FWIW I've been trying to update it in the background to implement
Magnus' instructions from the post mentioned above, but haven't
finished yet.=C2=A0 https://github.com/mor1/mirage-vagrant-vms if anyone<= br> wants to pick up from where I've currently stalled... :)

I've been working away slowly at this: https://github.com/mattgray= /mirage-xen-virtualbox which is basically Magnus' blog post made in= to a packer template.

I'm aiming at a system w= here I can compile a unikernel on my host machine, and then run a command t= hat will push the kernel to the vagrant VM, run it (exposing the console so= mehow), and assign a DNS name using Avahi to the DHCP-assigned IPv4 address= . Still pondering that one, but at the moment the box there is able the bui= ld and run MirageOS apps. You'll just need to share a directory using N= FS. I'll update the docs now with a simple walkthrough.

<= /div>
Matt =C2=A0

--001a11c0b36a69bbe2050fd91ae2-- --===============2132860737361179157== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --===============2132860737361179157==-- From mirageos-devel-bounces@lists.xenproject.org Tue Feb 24 17:46:54 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 24 Feb 2015 17:46:54 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YQJZN-0007uU-Lq; Tue, 24 Feb 2015 17:46:53 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YQJZM-0007uN-1F for mirageos-devel@lists.xenproject.org; Tue, 24 Feb 2015 17:46:52 +0000 Received: from [193.109.254.147] by server-3.bemta-14.messagelabs.com id 8E/7A-10964-B09BCE45; Tue, 24 Feb 2015 17:46:51 +0000 X-Env-Sender: matthew.thomas.gray@gmail.com X-Msg-Ref: server-4.tower-27.messagelabs.com!1424800009!12575425!1 X-Originating-IP: [209.85.192.53] X-SpamReason: No, hits=0.7 required=7.0 tests=HTML_30_40,HTML_MESSAGE, MAILTO_TO_SPAM_ADDR,RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5673 invoked from network); 24 Feb 2015 17:46:50 -0000 Received: from mail-qg0-f53.google.com (HELO mail-qg0-f53.google.com) (209.85.192.53) by server-4.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 24 Feb 2015 17:46:50 -0000 Received: by mail-qg0-f53.google.com with SMTP id f51so31281306qge.12 for ; Tue, 24 Feb 2015 09:46:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=3oFlwHhKb4EkyK8iImY8lpsNcxw5EA9MVRxBcybV+q8=; b=H41UJ2Ey/mDGYf6xX+UlU1UQ4Lq2LOqxXi4ANldyLX5ym0DHlxmS6GHyIpDPfdu/s8 4hyJ3/aP2CZX2q6hoFXmyXkgxiIhZZjgHa1s1matq4PooodMQS3Yn+5Ww5JBbQ1A119T 7elATUlvZj+w7ia5DK7ju+sOg9gIvyKTkX0OrShf3FXU3TO6PbKSLEWpbInUygdJ12gr 6e1fED3zUokK1AzxXjofHpuHUcoxI+8buI2+y5k5AlULRgpvRPp5NWLEwFrUH0ti0Uto Ym+2cQZPJ5jTbq3idRQNmFtxhKeigj9TZ2sr2oYI8gKpx6IVHVbtEsvypJMJkoKCchfe dtUg== MIME-Version: 1.0 X-Received: by 10.140.17.9 with SMTP id 9mr36717904qgc.21.1424800009008; Tue, 24 Feb 2015 09:46:49 -0800 (PST) Received: by 10.140.46.168 with HTTP; Tue, 24 Feb 2015 09:46:48 -0800 (PST) In-Reply-To: References: <17F3E677-EB2E-4465-B213-B1C682F33C21@badgermind.net> <99F4240E-C4E6-4BD9-BA99-E986A48C45A4@cam.ac.uk> Date: Tue, 24 Feb 2015 17:46:48 +0000 Message-ID: From: Matthew Gray To: Richard Mortier Cc: mirageos-devel Subject: Re: [MirageOS-devel] Question about pioneer projects X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2132860737361179157==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============2132860737361179157== Content-Type: multipart/alternative; boundary=001a11c0b36a69bbe2050fd91ae2 --001a11c0b36a69bbe2050fd91ae2 Content-Type: text/plain; charset=UTF-8 On Tue, Feb 24, 2015 at 3:36 PM, Richard Mortier < richard.mortier@cl.cam.ac.uk> wrote: > On 24 February 2015 at 13:05, Amir Chaudhry wrote: > > > > On 24 Feb 2015, at 12:56, yiorgos wrote: > > > >> ...Do you guys think that > >> developing can be done using this way or there will be a quite great > >> amount of setting up/debugging VirtualBox (eg network interfaces etc) > > > > Magnus wrote a post about his VirtualBox set up for Mirage development. > > http://www.skjegstad.com/blog/2015/01/19/mirageos-xen-virtualbox/ > > We also have a repo with scripts/config for setting up vagrant boxes > using packer. Might be a little out of date now but used to work. > > https://github.com/mirage/mirage-vagrant-vms > > (FWIW I've been trying to update it in the background to implement > Magnus' instructions from the post mentioned above, but haven't > finished yet. https://github.com/mor1/mirage-vagrant-vms if anyone > wants to pick up from where I've currently stalled... :) I've been working away slowly at this: https://github.com/mattgray/mirage-xen-virtualbox which is basically Magnus' blog post made into a packer template. I'm aiming at a system where I can compile a unikernel on my host machine, and then run a command that will push the kernel to the vagrant VM, run it (exposing the console somehow), and assign a DNS name using Avahi to the DHCP-assigned IPv4 address. Still pondering that one, but at the moment the box there is able the build and run MirageOS apps. You'll just need to share a directory using NFS. I'll update the docs now with a simple walkthrough. Matt --001a11c0b36a69bbe2050fd91ae2 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On T= ue, Feb 24, 2015 at 3:36 PM, Richard Mortier <richard.mortier@= cl.cam.ac.uk> wrote:
On = 24 February 2015 at 13:05, Amir Chaudhry <amc79@cam.ac.uk> wrote:
>
> On 24 Feb 2015, at 12:56, yiorgos <antibra@hotmail.com> wrote:
>
>> ...Do you guys think that
>> developing can be done using this way or there wi= ll be a quite great
>> amount of setting up/debugging VirtualBox (eg network interfaces e= tc)
>
> Magnus wrote a post about his VirtualBox set up for Mirage development= .
> http://www.skjegstad.com/blog/2015/01/19/mirageos= -xen-virtualbox/

We also have a repo with scripts/config for setting up vagrant boxes=
using packer. Might be a little out of date now but used to work.

= https://github.com/mirage/mirage-vagrant-vms

(FWIW I've been trying to update it in the background to implement
Magnus' instructions from the post mentioned above, but haven't
finished yet.=C2=A0 https://github.com/mor1/mirage-vagrant-vms if anyone<= br> wants to pick up from where I've currently stalled... :)

I've been working away slowly at this: https://github.com/mattgray= /mirage-xen-virtualbox which is basically Magnus' blog post made in= to a packer template.

I'm aiming at a system w= here I can compile a unikernel on my host machine, and then run a command t= hat will push the kernel to the vagrant VM, run it (exposing the console so= mehow), and assign a DNS name using Avahi to the DHCP-assigned IPv4 address= . Still pondering that one, but at the moment the box there is able the bui= ld and run MirageOS apps. You'll just need to share a directory using N= FS. I'll update the docs now with a simple walkthrough.

<= /div>
Matt =C2=A0

--001a11c0b36a69bbe2050fd91ae2-- --===============2132860737361179157== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --===============2132860737361179157==-- From mirageos-devel-bounces@lists.xenproject.org Tue Feb 24 17:51:56 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 24 Feb 2015 17:51:56 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YQJeG-0008Go-41; Tue, 24 Feb 2015 17:51:56 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YQJeE-0008GX-BX for mirageos-devel@lists.xenproject.org; Tue, 24 Feb 2015 17:51:54 +0000 Received: from [85.158.139.211] by server-8.bemta-5.messagelabs.com id 60/5C-03712-93ABCE45; Tue, 24 Feb 2015 17:51:53 +0000 X-Env-Sender: richard.mortier@gmail.com X-Msg-Ref: server-10.tower-206.messagelabs.com!1424800312!5800153!1 X-Originating-IP: [209.85.192.47] X-SpamReason: No, hits=0.6 required=7.0 tests=MAILTO_TO_SPAM_ADDR, RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8847 invoked from network); 24 Feb 2015 17:51:53 -0000 Received: from mail-qg0-f47.google.com (HELO mail-qg0-f47.google.com) (209.85.192.47) by server-10.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 24 Feb 2015 17:51:53 -0000 Received: by mail-qg0-f47.google.com with SMTP id q107so31359764qgd.6 for ; Tue, 24 Feb 2015 09:51:52 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=W0mqpyW5XoPa+2qXhBgxvzfNGuK9tsGulDFXVxZctGw=; b=FwaISkD3Uo5d4a/HvJEsM2kJVLzWWzb581zDzoVCqSaJv7ZpxxcE9T/s//xRWDrEma rlIEqRtG2vlFipZOLqbjQpELfjwxPWu3Vk/Fop4v3xq05VSsfo+t1LK+kkMZYu8Ye9DJ jQFxtQOtZDwEEf0bss1ZKn7/JPXdkwk+bLGgAYhZzAKCByYyHvxYYc4X9Lt5wvdRLzto MiktT5VPq+aNhWTCCIwFAbkn8dafYS+likE/1bkG41DA8sDNz2M/jZBSVWTIp9/5ESHn jp94+19Fm3efyXSmW+vsPwBXVyNV3TL9Y/lIkEjCXLoBakpqhkhNz9+c65F3C9QxUfRO /DdQ== X-Received: by 10.140.195.5 with SMTP id q5mr2931251qha.58.1424800312204; Tue, 24 Feb 2015 09:51:52 -0800 (PST) Received: from mail-qc0-f172.google.com (mail-qc0-f172.google.com. [209.85.216.172]) by mx.google.com with ESMTPSA id b74sm22338595qga.40.2015.02.24.09.51.50 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 24 Feb 2015 09:51:51 -0800 (PST) Received: by qcxm20 with SMTP id m20so17835379qcx.0 for ; Tue, 24 Feb 2015 09:51:50 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.140.134.198 with SMTP id 189mr11557874qhg.7.1424800310626; Tue, 24 Feb 2015 09:51:50 -0800 (PST) Received: by 10.140.92.245 with HTTP; Tue, 24 Feb 2015 09:51:50 -0800 (PST) In-Reply-To: References: <17F3E677-EB2E-4465-B213-B1C682F33C21@badgermind.net> <99F4240E-C4E6-4BD9-BA99-E986A48C45A4@cam.ac.uk> Date: Tue, 24 Feb 2015 17:51:50 +0000 Message-ID: From: Richard Mortier To: Matthew Gray Cc: mirageos-devel Subject: Re: [MirageOS-devel] Question about pioneer projects X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org Awesome! I shall ditch my stalled attempt and use yours then :) The `Vagrantfile` in the mirage-vagrant-vms directory should expose a host-shared directory via NFS if that's any use. On 24 February 2015 at 17:46, Matthew Gray wrote: > On Tue, Feb 24, 2015 at 3:36 PM, Richard Mortier > wrote: >> >> On 24 February 2015 at 13:05, Amir Chaudhry wrote: >> > >> > On 24 Feb 2015, at 12:56, yiorgos wrote: >> > >> >> ...Do you guys think that >> >> developing can be done using this way or there will be a quite great >> >> amount of setting up/debugging VirtualBox (eg network interfaces etc) >> > >> > Magnus wrote a post about his VirtualBox set up for Mirage development. >> > http://www.skjegstad.com/blog/2015/01/19/mirageos-xen-virtualbox/ >> >> We also have a repo with scripts/config for setting up vagrant boxes >> using packer. Might be a little out of date now but used to work. >> >> https://github.com/mirage/mirage-vagrant-vms >> >> (FWIW I've been trying to update it in the background to implement >> Magnus' instructions from the post mentioned above, but haven't >> finished yet. https://github.com/mor1/mirage-vagrant-vms if anyone >> wants to pick up from where I've currently stalled... :) > > > I've been working away slowly at this: > https://github.com/mattgray/mirage-xen-virtualbox which is basically Magnus' > blog post made into a packer template. > > I'm aiming at a system where I can compile a unikernel on my host machine, > and then run a command that will push the kernel to the vagrant VM, run it > (exposing the console somehow), and assign a DNS name using Avahi to the > DHCP-assigned IPv4 address. Still pondering that one, but at the moment the > box there is able the build and run MirageOS apps. You'll just need to share > a directory using NFS. I'll update the docs now with a simple walkthrough. > > Matt > -- Richard Mortier richard.mortier@cl.cam.ac.uk _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Tue Feb 24 17:51:56 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 24 Feb 2015 17:51:56 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YQJeG-0008Go-41; Tue, 24 Feb 2015 17:51:56 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YQJeE-0008GX-BX for mirageos-devel@lists.xenproject.org; Tue, 24 Feb 2015 17:51:54 +0000 Received: from [85.158.139.211] by server-8.bemta-5.messagelabs.com id 60/5C-03712-93ABCE45; Tue, 24 Feb 2015 17:51:53 +0000 X-Env-Sender: richard.mortier@gmail.com X-Msg-Ref: server-10.tower-206.messagelabs.com!1424800312!5800153!1 X-Originating-IP: [209.85.192.47] X-SpamReason: No, hits=0.6 required=7.0 tests=MAILTO_TO_SPAM_ADDR, RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8847 invoked from network); 24 Feb 2015 17:51:53 -0000 Received: from mail-qg0-f47.google.com (HELO mail-qg0-f47.google.com) (209.85.192.47) by server-10.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 24 Feb 2015 17:51:53 -0000 Received: by mail-qg0-f47.google.com with SMTP id q107so31359764qgd.6 for ; Tue, 24 Feb 2015 09:51:52 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=W0mqpyW5XoPa+2qXhBgxvzfNGuK9tsGulDFXVxZctGw=; b=FwaISkD3Uo5d4a/HvJEsM2kJVLzWWzb581zDzoVCqSaJv7ZpxxcE9T/s//xRWDrEma rlIEqRtG2vlFipZOLqbjQpELfjwxPWu3Vk/Fop4v3xq05VSsfo+t1LK+kkMZYu8Ye9DJ jQFxtQOtZDwEEf0bss1ZKn7/JPXdkwk+bLGgAYhZzAKCByYyHvxYYc4X9Lt5wvdRLzto MiktT5VPq+aNhWTCCIwFAbkn8dafYS+likE/1bkG41DA8sDNz2M/jZBSVWTIp9/5ESHn jp94+19Fm3efyXSmW+vsPwBXVyNV3TL9Y/lIkEjCXLoBakpqhkhNz9+c65F3C9QxUfRO /DdQ== X-Received: by 10.140.195.5 with SMTP id q5mr2931251qha.58.1424800312204; Tue, 24 Feb 2015 09:51:52 -0800 (PST) Received: from mail-qc0-f172.google.com (mail-qc0-f172.google.com. [209.85.216.172]) by mx.google.com with ESMTPSA id b74sm22338595qga.40.2015.02.24.09.51.50 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 24 Feb 2015 09:51:51 -0800 (PST) Received: by qcxm20 with SMTP id m20so17835379qcx.0 for ; Tue, 24 Feb 2015 09:51:50 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.140.134.198 with SMTP id 189mr11557874qhg.7.1424800310626; Tue, 24 Feb 2015 09:51:50 -0800 (PST) Received: by 10.140.92.245 with HTTP; Tue, 24 Feb 2015 09:51:50 -0800 (PST) In-Reply-To: References: <17F3E677-EB2E-4465-B213-B1C682F33C21@badgermind.net> <99F4240E-C4E6-4BD9-BA99-E986A48C45A4@cam.ac.uk> Date: Tue, 24 Feb 2015 17:51:50 +0000 Message-ID: From: Richard Mortier To: Matthew Gray Cc: mirageos-devel Subject: Re: [MirageOS-devel] Question about pioneer projects X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org Awesome! I shall ditch my stalled attempt and use yours then :) The `Vagrantfile` in the mirage-vagrant-vms directory should expose a host-shared directory via NFS if that's any use. On 24 February 2015 at 17:46, Matthew Gray wrote: > On Tue, Feb 24, 2015 at 3:36 PM, Richard Mortier > wrote: >> >> On 24 February 2015 at 13:05, Amir Chaudhry wrote: >> > >> > On 24 Feb 2015, at 12:56, yiorgos wrote: >> > >> >> ...Do you guys think that >> >> developing can be done using this way or there will be a quite great >> >> amount of setting up/debugging VirtualBox (eg network interfaces etc) >> > >> > Magnus wrote a post about his VirtualBox set up for Mirage development. >> > http://www.skjegstad.com/blog/2015/01/19/mirageos-xen-virtualbox/ >> >> We also have a repo with scripts/config for setting up vagrant boxes >> using packer. Might be a little out of date now but used to work. >> >> https://github.com/mirage/mirage-vagrant-vms >> >> (FWIW I've been trying to update it in the background to implement >> Magnus' instructions from the post mentioned above, but haven't >> finished yet. https://github.com/mor1/mirage-vagrant-vms if anyone >> wants to pick up from where I've currently stalled... :) > > > I've been working away slowly at this: > https://github.com/mattgray/mirage-xen-virtualbox which is basically Magnus' > blog post made into a packer template. > > I'm aiming at a system where I can compile a unikernel on my host machine, > and then run a command that will push the kernel to the vagrant VM, run it > (exposing the console somehow), and assign a DNS name using Avahi to the > DHCP-assigned IPv4 address. Still pondering that one, but at the moment the > box there is able the build and run MirageOS apps. You'll just need to share > a directory using NFS. I'll update the docs now with a simple walkthrough. > > Matt > -- Richard Mortier richard.mortier@cl.cam.ac.uk _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Tue Feb 24 18:30:31 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 24 Feb 2015 18:30:31 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YQKFY-000053-Ep; Tue, 24 Feb 2015 18:30:28 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YQKFW-0008WO-Vf for mirageos-devel@lists.xenproject.org; Tue, 24 Feb 2015 18:30:27 +0000 Received: from [85.158.137.68] by server-13.bemta-3.messagelabs.com id 6C/61-02898-243CCE45; Tue, 24 Feb 2015 18:30:26 +0000 X-Env-Sender: matthew.thomas.gray@gmail.com X-Msg-Ref: server-10.tower-31.messagelabs.com!1424802621!11887388!1 X-Originating-IP: [209.85.192.49] X-SpamReason: No, hits=1.2 required=7.0 tests=BODY_RANDOM_LONG, HTML_30_40,HTML_MESSAGE,MAILTO_TO_SPAM_ADDR,RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23439 invoked from network); 24 Feb 2015 18:30:22 -0000 Received: from mail-qg0-f49.google.com (HELO mail-qg0-f49.google.com) (209.85.192.49) by server-10.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 24 Feb 2015 18:30:22 -0000 Received: by mail-qg0-f49.google.com with SMTP id q107so31450228qgd.8 for ; Tue, 24 Feb 2015 10:30:21 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=HV6655ktNhAQGYMjOvVi+Zi1RY5GiKJ7RhIYnrZuUz8=; b=xwTkppWzEK/hCjMX2ET4CHCBamktR+aWrwLqo8iCDY0YllXh113CxfUMLBy21MnkTo cb9CtD6QVb+1xu6x4Dkkpt5ZejrhYATBYnVXAM4HpKydZQjlu/qnrEzMnJSvjrRZlRqR 4ZIixmbbQtBI2w0R4X3geYle9j4gYxY8As0pZaTvUmBLI0K32zsXJZhGF/GFPcQcppKL 4zhuPhDRDWuDczof/r1MKhy5FIQZ7SUVTurh4B6Qy96ACZPyStbuRRX3Xz2gH/nqIxfb hQh2xa7a90LA/hN4i6v5vWSYf+5yJ2kQ71CTkNDQcRUuE7sDQW3VGJLk+gPhlu3pOWLU wjgQ== MIME-Version: 1.0 X-Received: by 10.141.28.145 with SMTP id f139mr39912557qhe.36.1424802621142; Tue, 24 Feb 2015 10:30:21 -0800 (PST) Received: by 10.140.46.168 with HTTP; Tue, 24 Feb 2015 10:30:21 -0800 (PST) In-Reply-To: References: <17F3E677-EB2E-4465-B213-B1C682F33C21@badgermind.net> <99F4240E-C4E6-4BD9-BA99-E986A48C45A4@cam.ac.uk> Date: Tue, 24 Feb 2015 18:30:21 +0000 Message-ID: From: Matthew Gray To: Richard Mortier Cc: mirageos-devel Subject: Re: [MirageOS-devel] Question about pioneer projects X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0842546597031793609==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============0842546597031793609== Content-Type: multipart/alternative; boundary=001a11423cae1bbda9050fd9b60a --001a11423cae1bbda9050fd9b60a Content-Type: text/plain; charset=UTF-8 Great! I've left mapping a shared drive up to the users of the box, as it will vary by use-case. Also, I've tried to make it possible that one can customise the Vagrantfile to allow a different private subnet within virtualbox - but both these are untested / undocumented so far. Otherwise, I've updated the README on https://github.com/mattgray/mirage-xen-virtualbox with instructions on how to build and use. On Tue, Feb 24, 2015 at 5:51 PM, Richard Mortier < richard.mortier@cl.cam.ac.uk> wrote: > Awesome! I shall ditch my stalled attempt and use yours then :) > The `Vagrantfile` in the mirage-vagrant-vms directory should expose a > host-shared directory via NFS if that's any use. > > On 24 February 2015 at 17:46, Matthew Gray > wrote: > > On Tue, Feb 24, 2015 at 3:36 PM, Richard Mortier > > wrote: > >> > >> On 24 February 2015 at 13:05, Amir Chaudhry wrote: > >> > > >> > On 24 Feb 2015, at 12:56, yiorgos wrote: > >> > > >> >> ...Do you guys think that > >> >> developing can be done using this way or there will be a quite great > >> >> amount of setting up/debugging VirtualBox (eg network interfaces etc) > >> > > >> > Magnus wrote a post about his VirtualBox set up for Mirage > development. > >> > http://www.skjegstad.com/blog/2015/01/19/mirageos-xen-virtualbox/ > >> > >> We also have a repo with scripts/config for setting up vagrant boxes > >> using packer. Might be a little out of date now but used to work. > >> > >> https://github.com/mirage/mirage-vagrant-vms > >> > >> (FWIW I've been trying to update it in the background to implement > >> Magnus' instructions from the post mentioned above, but haven't > >> finished yet. https://github.com/mor1/mirage-vagrant-vms if anyone > >> wants to pick up from where I've currently stalled... :) > > > > > > I've been working away slowly at this: > > https://github.com/mattgray/mirage-xen-virtualbox which is basically > Magnus' > > blog post made into a packer template. > > > > I'm aiming at a system where I can compile a unikernel on my host > machine, > > and then run a command that will push the kernel to the vagrant VM, run > it > > (exposing the console somehow), and assign a DNS name using Avahi to the > > DHCP-assigned IPv4 address. Still pondering that one, but at the moment > the > > box there is able the build and run MirageOS apps. You'll just need to > share > > a directory using NFS. I'll update the docs now with a simple > walkthrough. > > > > Matt > > > > > > -- > Richard Mortier > richard.mortier@cl.cam.ac.uk > --001a11423cae1bbda9050fd9b60a Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Great! I've left mapping a shared drive up to the user= s of the box, as it will vary by use-case. Also, I've tried to make it = possible that one can customise the Vagrantfile to allow a different privat= e subnet within virtualbox - but both these are untested / undocumented so = far. Otherwise, I've updated the README on=C2=A0https://github.com/mattgray/mirage-x= en-virtualbox with instructions on how to build and use.

On Tue, Feb 24, 2015 at 5:= 51 PM, Richard Mortier <richard.mortier@cl.cam.ac.uk> wrote:
Awesome! I shall ditch my sta= lled attempt and use yours then :)
The `Vagrantfile` in the mirage-vagrant-vms directory should expose a
host-shared directory via NFS if that's any use.

On 24 February 2015 at 17:46, Matthew Gray
<matthew.thomas.gray@gmail.com> wrote:
> On Tue, Feb 24, 2015 at 3:36 PM, Richard Mortier
> <richard.mortier@cl= .cam.ac.uk> wrote:
>>
>> On 24 February 2015 at 13:05, Amir Chaudhry <amc79@cam.ac.uk> wrote:
>> >
>> > On 24 Feb 2015, at 12:56, yiorgos <antibra@hotmail.com> wrote:
>> >
>> >> ...Do you guys think that
>> >> developing can be done using this way or there will be a = quite great
>> >> amount of setting up/debugging VirtualBox (eg network int= erfaces etc)
>> >
>> > Magnus wrote a post about his VirtualBox set up for Mirage de= velopment.
>> > http://www.skjegstad.com/blog/2015/01/19= /mirageos-xen-virtualbox/
>>
>> We also have a repo with scripts/config for setting up vagrant box= es
>> using packer. Might be a little out of date now but used to work.<= br> >>
>> https://github.com/mirage/mirage-vagrant-vms
>>
>> (FWIW I've been trying to update it in the background to imple= ment
>> Magnus' instructions from the post mentioned above, but haven&= #39;t
>> finished yet.=C2=A0 https://github.com/mor1/mirage-vagrant-vms i= f anyone
>> wants to pick up from where I've currently stalled... :)
>
>
> I've been working away slowly at this:
> https://github.com/mattgray/mirage-xen-virtualbox which is = basically Magnus'
> blog post made into a packer template.
>
> I'm aiming at a system where I can compile a unikernel on my host = machine,
> and then run a command that will push the kernel to the vagrant VM, ru= n it
> (exposing the console somehow), and assign a DNS name using Avahi to t= he
> DHCP-assigned IPv4 address. Still pondering that one, but at the momen= t the
> box there is able the build and run MirageOS apps. You'll just nee= d to share
> a directory using NFS. I'll update the docs now with a simple walk= through.
>
> Matt
>



--
Richard Mortier
richard.mortier@cl.cam.ac.u= k

--001a11423cae1bbda9050fd9b60a-- --===============0842546597031793609== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --===============0842546597031793609==-- From mirageos-devel-bounces@lists.xenproject.org Tue Feb 24 18:30:31 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 24 Feb 2015 18:30:31 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YQKFY-000053-Ep; Tue, 24 Feb 2015 18:30:28 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YQKFW-0008WO-Vf for mirageos-devel@lists.xenproject.org; Tue, 24 Feb 2015 18:30:27 +0000 Received: from [85.158.137.68] by server-13.bemta-3.messagelabs.com id 6C/61-02898-243CCE45; Tue, 24 Feb 2015 18:30:26 +0000 X-Env-Sender: matthew.thomas.gray@gmail.com X-Msg-Ref: server-10.tower-31.messagelabs.com!1424802621!11887388!1 X-Originating-IP: [209.85.192.49] X-SpamReason: No, hits=1.2 required=7.0 tests=BODY_RANDOM_LONG, HTML_30_40,HTML_MESSAGE,MAILTO_TO_SPAM_ADDR,RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23439 invoked from network); 24 Feb 2015 18:30:22 -0000 Received: from mail-qg0-f49.google.com (HELO mail-qg0-f49.google.com) (209.85.192.49) by server-10.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 24 Feb 2015 18:30:22 -0000 Received: by mail-qg0-f49.google.com with SMTP id q107so31450228qgd.8 for ; Tue, 24 Feb 2015 10:30:21 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=HV6655ktNhAQGYMjOvVi+Zi1RY5GiKJ7RhIYnrZuUz8=; b=xwTkppWzEK/hCjMX2ET4CHCBamktR+aWrwLqo8iCDY0YllXh113CxfUMLBy21MnkTo cb9CtD6QVb+1xu6x4Dkkpt5ZejrhYATBYnVXAM4HpKydZQjlu/qnrEzMnJSvjrRZlRqR 4ZIixmbbQtBI2w0R4X3geYle9j4gYxY8As0pZaTvUmBLI0K32zsXJZhGF/GFPcQcppKL 4zhuPhDRDWuDczof/r1MKhy5FIQZ7SUVTurh4B6Qy96ACZPyStbuRRX3Xz2gH/nqIxfb hQh2xa7a90LA/hN4i6v5vWSYf+5yJ2kQ71CTkNDQcRUuE7sDQW3VGJLk+gPhlu3pOWLU wjgQ== MIME-Version: 1.0 X-Received: by 10.141.28.145 with SMTP id f139mr39912557qhe.36.1424802621142; Tue, 24 Feb 2015 10:30:21 -0800 (PST) Received: by 10.140.46.168 with HTTP; Tue, 24 Feb 2015 10:30:21 -0800 (PST) In-Reply-To: References: <17F3E677-EB2E-4465-B213-B1C682F33C21@badgermind.net> <99F4240E-C4E6-4BD9-BA99-E986A48C45A4@cam.ac.uk> Date: Tue, 24 Feb 2015 18:30:21 +0000 Message-ID: From: Matthew Gray To: Richard Mortier Cc: mirageos-devel Subject: Re: [MirageOS-devel] Question about pioneer projects X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0842546597031793609==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============0842546597031793609== Content-Type: multipart/alternative; boundary=001a11423cae1bbda9050fd9b60a --001a11423cae1bbda9050fd9b60a Content-Type: text/plain; charset=UTF-8 Great! I've left mapping a shared drive up to the users of the box, as it will vary by use-case. Also, I've tried to make it possible that one can customise the Vagrantfile to allow a different private subnet within virtualbox - but both these are untested / undocumented so far. Otherwise, I've updated the README on https://github.com/mattgray/mirage-xen-virtualbox with instructions on how to build and use. On Tue, Feb 24, 2015 at 5:51 PM, Richard Mortier < richard.mortier@cl.cam.ac.uk> wrote: > Awesome! I shall ditch my stalled attempt and use yours then :) > The `Vagrantfile` in the mirage-vagrant-vms directory should expose a > host-shared directory via NFS if that's any use. > > On 24 February 2015 at 17:46, Matthew Gray > wrote: > > On Tue, Feb 24, 2015 at 3:36 PM, Richard Mortier > > wrote: > >> > >> On 24 February 2015 at 13:05, Amir Chaudhry wrote: > >> > > >> > On 24 Feb 2015, at 12:56, yiorgos wrote: > >> > > >> >> ...Do you guys think that > >> >> developing can be done using this way or there will be a quite great > >> >> amount of setting up/debugging VirtualBox (eg network interfaces etc) > >> > > >> > Magnus wrote a post about his VirtualBox set up for Mirage > development. > >> > http://www.skjegstad.com/blog/2015/01/19/mirageos-xen-virtualbox/ > >> > >> We also have a repo with scripts/config for setting up vagrant boxes > >> using packer. Might be a little out of date now but used to work. > >> > >> https://github.com/mirage/mirage-vagrant-vms > >> > >> (FWIW I've been trying to update it in the background to implement > >> Magnus' instructions from the post mentioned above, but haven't > >> finished yet. https://github.com/mor1/mirage-vagrant-vms if anyone > >> wants to pick up from where I've currently stalled... :) > > > > > > I've been working away slowly at this: > > https://github.com/mattgray/mirage-xen-virtualbox which is basically > Magnus' > > blog post made into a packer template. > > > > I'm aiming at a system where I can compile a unikernel on my host > machine, > > and then run a command that will push the kernel to the vagrant VM, run > it > > (exposing the console somehow), and assign a DNS name using Avahi to the > > DHCP-assigned IPv4 address. Still pondering that one, but at the moment > the > > box there is able the build and run MirageOS apps. You'll just need to > share > > a directory using NFS. I'll update the docs now with a simple > walkthrough. > > > > Matt > > > > > > -- > Richard Mortier > richard.mortier@cl.cam.ac.uk > --001a11423cae1bbda9050fd9b60a Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Great! I've left mapping a shared drive up to the user= s of the box, as it will vary by use-case. Also, I've tried to make it = possible that one can customise the Vagrantfile to allow a different privat= e subnet within virtualbox - but both these are untested / undocumented so = far. Otherwise, I've updated the README on=C2=A0https://github.com/mattgray/mirage-x= en-virtualbox with instructions on how to build and use.

On Tue, Feb 24, 2015 at 5:= 51 PM, Richard Mortier <richard.mortier@cl.cam.ac.uk> wrote:
Awesome! I shall ditch my sta= lled attempt and use yours then :)
The `Vagrantfile` in the mirage-vagrant-vms directory should expose a
host-shared directory via NFS if that's any use.

On 24 February 2015 at 17:46, Matthew Gray
<matthew.thomas.gray@gmail.com> wrote:
> On Tue, Feb 24, 2015 at 3:36 PM, Richard Mortier
> <richard.mortier@cl= .cam.ac.uk> wrote:
>>
>> On 24 February 2015 at 13:05, Amir Chaudhry <amc79@cam.ac.uk> wrote:
>> >
>> > On 24 Feb 2015, at 12:56, yiorgos <antibra@hotmail.com> wrote:
>> >
>> >> ...Do you guys think that
>> >> developing can be done using this way or there will be a = quite great
>> >> amount of setting up/debugging VirtualBox (eg network int= erfaces etc)
>> >
>> > Magnus wrote a post about his VirtualBox set up for Mirage de= velopment.
>> > http://www.skjegstad.com/blog/2015/01/19= /mirageos-xen-virtualbox/
>>
>> We also have a repo with scripts/config for setting up vagrant box= es
>> using packer. Might be a little out of date now but used to work.<= br> >>
>> https://github.com/mirage/mirage-vagrant-vms
>>
>> (FWIW I've been trying to update it in the background to imple= ment
>> Magnus' instructions from the post mentioned above, but haven&= #39;t
>> finished yet.=C2=A0 https://github.com/mor1/mirage-vagrant-vms i= f anyone
>> wants to pick up from where I've currently stalled... :)
>
>
> I've been working away slowly at this:
> https://github.com/mattgray/mirage-xen-virtualbox which is = basically Magnus'
> blog post made into a packer template.
>
> I'm aiming at a system where I can compile a unikernel on my host = machine,
> and then run a command that will push the kernel to the vagrant VM, ru= n it
> (exposing the console somehow), and assign a DNS name using Avahi to t= he
> DHCP-assigned IPv4 address. Still pondering that one, but at the momen= t the
> box there is able the build and run MirageOS apps. You'll just nee= d to share
> a directory using NFS. I'll update the docs now with a simple walk= through.
>
> Matt
>



--
Richard Mortier
richard.mortier@cl.cam.ac.u= k

--001a11423cae1bbda9050fd9b60a-- --===============0842546597031793609== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --===============0842546597031793609==-- From mirageos-devel-bounces@lists.xenproject.org Tue Feb 24 18:30:56 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 24 Feb 2015 18:30:56 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YQKG0-00009O-Ku; Tue, 24 Feb 2015 18:30:56 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YQKFy-000095-TE for mirageos-devel@lists.xenproject.org; Tue, 24 Feb 2015 18:30:55 +0000 Received: from [85.158.137.68] by server-8.bemta-3.messagelabs.com id BC/61-03710-E53CCE45; Tue, 24 Feb 2015 18:30:54 +0000 X-Env-Sender: matthew.thomas.gray@gmail.com X-Msg-Ref: server-4.tower-31.messagelabs.com!1424802651!11098295!1 X-Originating-IP: [209.85.216.170] X-SpamReason: No, hits=1.7 required=7.0 tests=BODY_RANDOM_LONG, HTML_40_50,HTML_MESSAGE,MAILTO_TO_SPAM_ADDR,RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 14675 invoked from network); 24 Feb 2015 18:30:52 -0000 Received: from mail-qc0-f170.google.com (HELO mail-qc0-f170.google.com) (209.85.216.170) by server-4.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 24 Feb 2015 18:30:52 -0000 Received: by qcwr17 with SMTP id r17so5648408qcw.1 for ; Tue, 24 Feb 2015 10:30:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=81SgvDRYB2n8rKyL95eLrncE5PFQ4rMogNn4TGJyyJs=; b=UC1+oTPziJ20dJGBkiiLm5b4FDgIxFmK5BApYTxWtmGXLGow2mIjEg/H0FdRbNqa+7 qN9Q9y0/NajC3lOQsn31aUqcENWGTVKLA5oMj7UgJTDYvlXZ92ydee/chln1gD6VMUN1 fXwMg9eQ7A+F2tpj4N4pv3OkSFY2xzHVR3aoPqAGIsCEoLdXvaPVB+i8drfTEE+EE282 jO+jsETw/NJ887DEaCchRjEsmkm08FAjvAfycVdHzqDT5beMrmPdyp+uRQLf13TExPN8 p/Lhc21KvBnATId0bAsoRGzWm9QJR97eUPZAL5XzLO+wkxIzzr9yeku7n/qSyn19DdUJ NYzA== MIME-Version: 1.0 X-Received: by 10.141.28.145 with SMTP id f139mr39917477qhe.36.1424802651206; Tue, 24 Feb 2015 10:30:51 -0800 (PST) Received: by 10.140.46.168 with HTTP; Tue, 24 Feb 2015 10:30:51 -0800 (PST) In-Reply-To: References: <17F3E677-EB2E-4465-B213-B1C682F33C21@badgermind.net> <99F4240E-C4E6-4BD9-BA99-E986A48C45A4@cam.ac.uk> Date: Tue, 24 Feb 2015 18:30:51 +0000 Message-ID: From: Matthew Gray To: Richard Mortier Cc: mirageos-devel Subject: Re: [MirageOS-devel] Question about pioneer projects X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1476431023516927674==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============1476431023516927674== Content-Type: multipart/alternative; boundary=001a11423caee68dcb050fd9b788 --001a11423caee68dcb050fd9b788 Content-Type: text/plain; charset=UTF-8 s/shared drive/shared directory/ On Tue, Feb 24, 2015 at 6:30 PM, Matthew Gray wrote: > Great! I've left mapping a shared drive up to the users of the box, as it > will vary by use-case. Also, I've tried to make it possible that one can > customise the Vagrantfile to allow a different private subnet within > virtualbox - but both these are untested / undocumented so far. Otherwise, > I've updated the README on > https://github.com/mattgray/mirage-xen-virtualbox with instructions on > how to build and use. > > On Tue, Feb 24, 2015 at 5:51 PM, Richard Mortier < > richard.mortier@cl.cam.ac.uk> wrote: > >> Awesome! I shall ditch my stalled attempt and use yours then :) >> The `Vagrantfile` in the mirage-vagrant-vms directory should expose a >> host-shared directory via NFS if that's any use. >> >> On 24 February 2015 at 17:46, Matthew Gray >> wrote: >> > On Tue, Feb 24, 2015 at 3:36 PM, Richard Mortier >> > wrote: >> >> >> >> On 24 February 2015 at 13:05, Amir Chaudhry wrote: >> >> > >> >> > On 24 Feb 2015, at 12:56, yiorgos wrote: >> >> > >> >> >> ...Do you guys think that >> >> >> developing can be done using this way or there will be a quite great >> >> >> amount of setting up/debugging VirtualBox (eg network interfaces >> etc) >> >> > >> >> > Magnus wrote a post about his VirtualBox set up for Mirage >> development. >> >> > http://www.skjegstad.com/blog/2015/01/19/mirageos-xen-virtualbox/ >> >> >> >> We also have a repo with scripts/config for setting up vagrant boxes >> >> using packer. Might be a little out of date now but used to work. >> >> >> >> https://github.com/mirage/mirage-vagrant-vms >> >> >> >> (FWIW I've been trying to update it in the background to implement >> >> Magnus' instructions from the post mentioned above, but haven't >> >> finished yet. https://github.com/mor1/mirage-vagrant-vms if anyone >> >> wants to pick up from where I've currently stalled... :) >> > >> > >> > I've been working away slowly at this: >> > https://github.com/mattgray/mirage-xen-virtualbox which is basically >> Magnus' >> > blog post made into a packer template. >> > >> > I'm aiming at a system where I can compile a unikernel on my host >> machine, >> > and then run a command that will push the kernel to the vagrant VM, run >> it >> > (exposing the console somehow), and assign a DNS name using Avahi to the >> > DHCP-assigned IPv4 address. Still pondering that one, but at the moment >> the >> > box there is able the build and run MirageOS apps. You'll just need to >> share >> > a directory using NFS. I'll update the docs now with a simple >> walkthrough. >> > >> > Matt >> > >> >> >> >> -- >> Richard Mortier >> richard.mortier@cl.cam.ac.uk >> > > --001a11423caee68dcb050fd9b788 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
s/shared drive/shared directory/=C2=A0

On Tue, Feb 24, 2015 at 6:30 PM= , Matthew Gray <matthew.thomas.gray@gmail.com> w= rote:
Great! I've le= ft mapping a shared drive up to the users of the box, as it will vary by us= e-case. Also, I've tried to make it possible that one can customise the= Vagrantfile to allow a different private subnet within virtualbox - but bo= th these are untested / undocumented so far. Otherwise, I've updated th= e README on=C2=A0https://github.com/mattgray/mirage-xen-virtualbox= with instructions on how to build and use.

On = Tue, Feb 24, 2015 at 5:51 PM, Richard Mortier <richard.mortier@= cl.cam.ac.uk> wrote:
Awesom= e! I shall ditch my stalled attempt and use yours then :)
The `Vagrantfile` in the mirage-vagrant-vms directory should expose a
host-shared directory via NFS if that's any use.

On 24 February 2015 at 17:46, Matthew Gray
<matthew.thomas.gray@gmail.com> wrote:
> On Tue, Feb 24, 2015 at 3:36 PM, Richard Mortier
> <= richard.mortier@cl.cam.ac.uk> wrote:
>>
>> On 24 February 2015 at 13:05, Amir Chaudhry <amc79@cam.ac.uk> wrote:
>> >
>> > On 24 Feb 2015, at 12:56, yiorgos <antibra@hotmail.com> wrote:
>> >
>> >> ...Do you guys think that
>> >> developing can be done using this way or there will be a = quite great
>> >> amount of setting up/debugging VirtualBox (eg network int= erfaces etc)
>> >
>> > Magnus wrote a post about his VirtualBox set up for Mirage de= velopment.
>> > http://www.skjegstad.com/blog/2015/01/19= /mirageos-xen-virtualbox/
>>
>> We also have a repo with scripts/config for setting up vagrant box= es
>> using packer. Might be a little out of date now but used to work.<= br> >>
>> https://github.com/mirage/mirage-vagrant-vms
>>
>> (FWIW I've been trying to update it in the background to imple= ment
>> Magnus' instructions from the post mentioned above, but haven&= #39;t
>> finished yet.=C2=A0 https://github.com/mor1/mirage-vagrant-vms i= f anyone
>> wants to pick up from where I've currently stalled... :)
>
>
> I've been working away slowly at this:
> https://github.com/mattgray/mirage-xen-virtualbox which is = basically Magnus'
> blog post made into a packer template.
>
> I'm aiming at a system where I can compile a unikernel on my host = machine,
> and then run a command that will push the kernel to the vagrant VM, ru= n it
> (exposing the console somehow), and assign a DNS name using Avahi to t= he
> DHCP-assigned IPv4 address. Still pondering that one, but at the momen= t the
> box there is able the build and run MirageOS apps. You'll just nee= d to share
> a directory using NFS. I'll update the docs now with a simple walk= through.
>
> Matt
>



--
Richard Mortier
richard.m= ortier@cl.cam.ac.uk


--001a11423caee68dcb050fd9b788-- --===============1476431023516927674== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --===============1476431023516927674==-- From mirageos-devel-bounces@lists.xenproject.org Tue Feb 24 18:30:56 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 24 Feb 2015 18:30:56 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YQKG0-00009O-Ku; Tue, 24 Feb 2015 18:30:56 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YQKFy-000095-TE for mirageos-devel@lists.xenproject.org; Tue, 24 Feb 2015 18:30:55 +0000 Received: from [85.158.137.68] by server-8.bemta-3.messagelabs.com id BC/61-03710-E53CCE45; Tue, 24 Feb 2015 18:30:54 +0000 X-Env-Sender: matthew.thomas.gray@gmail.com X-Msg-Ref: server-4.tower-31.messagelabs.com!1424802651!11098295!1 X-Originating-IP: [209.85.216.170] X-SpamReason: No, hits=1.7 required=7.0 tests=BODY_RANDOM_LONG, HTML_40_50,HTML_MESSAGE,MAILTO_TO_SPAM_ADDR,RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 14675 invoked from network); 24 Feb 2015 18:30:52 -0000 Received: from mail-qc0-f170.google.com (HELO mail-qc0-f170.google.com) (209.85.216.170) by server-4.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 24 Feb 2015 18:30:52 -0000 Received: by qcwr17 with SMTP id r17so5648408qcw.1 for ; Tue, 24 Feb 2015 10:30:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=81SgvDRYB2n8rKyL95eLrncE5PFQ4rMogNn4TGJyyJs=; b=UC1+oTPziJ20dJGBkiiLm5b4FDgIxFmK5BApYTxWtmGXLGow2mIjEg/H0FdRbNqa+7 qN9Q9y0/NajC3lOQsn31aUqcENWGTVKLA5oMj7UgJTDYvlXZ92ydee/chln1gD6VMUN1 fXwMg9eQ7A+F2tpj4N4pv3OkSFY2xzHVR3aoPqAGIsCEoLdXvaPVB+i8drfTEE+EE282 jO+jsETw/NJ887DEaCchRjEsmkm08FAjvAfycVdHzqDT5beMrmPdyp+uRQLf13TExPN8 p/Lhc21KvBnATId0bAsoRGzWm9QJR97eUPZAL5XzLO+wkxIzzr9yeku7n/qSyn19DdUJ NYzA== MIME-Version: 1.0 X-Received: by 10.141.28.145 with SMTP id f139mr39917477qhe.36.1424802651206; Tue, 24 Feb 2015 10:30:51 -0800 (PST) Received: by 10.140.46.168 with HTTP; Tue, 24 Feb 2015 10:30:51 -0800 (PST) In-Reply-To: References: <17F3E677-EB2E-4465-B213-B1C682F33C21@badgermind.net> <99F4240E-C4E6-4BD9-BA99-E986A48C45A4@cam.ac.uk> Date: Tue, 24 Feb 2015 18:30:51 +0000 Message-ID: From: Matthew Gray To: Richard Mortier Cc: mirageos-devel Subject: Re: [MirageOS-devel] Question about pioneer projects X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1476431023516927674==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============1476431023516927674== Content-Type: multipart/alternative; boundary=001a11423caee68dcb050fd9b788 --001a11423caee68dcb050fd9b788 Content-Type: text/plain; charset=UTF-8 s/shared drive/shared directory/ On Tue, Feb 24, 2015 at 6:30 PM, Matthew Gray wrote: > Great! I've left mapping a shared drive up to the users of the box, as it > will vary by use-case. Also, I've tried to make it possible that one can > customise the Vagrantfile to allow a different private subnet within > virtualbox - but both these are untested / undocumented so far. Otherwise, > I've updated the README on > https://github.com/mattgray/mirage-xen-virtualbox with instructions on > how to build and use. > > On Tue, Feb 24, 2015 at 5:51 PM, Richard Mortier < > richard.mortier@cl.cam.ac.uk> wrote: > >> Awesome! I shall ditch my stalled attempt and use yours then :) >> The `Vagrantfile` in the mirage-vagrant-vms directory should expose a >> host-shared directory via NFS if that's any use. >> >> On 24 February 2015 at 17:46, Matthew Gray >> wrote: >> > On Tue, Feb 24, 2015 at 3:36 PM, Richard Mortier >> > wrote: >> >> >> >> On 24 February 2015 at 13:05, Amir Chaudhry wrote: >> >> > >> >> > On 24 Feb 2015, at 12:56, yiorgos wrote: >> >> > >> >> >> ...Do you guys think that >> >> >> developing can be done using this way or there will be a quite great >> >> >> amount of setting up/debugging VirtualBox (eg network interfaces >> etc) >> >> > >> >> > Magnus wrote a post about his VirtualBox set up for Mirage >> development. >> >> > http://www.skjegstad.com/blog/2015/01/19/mirageos-xen-virtualbox/ >> >> >> >> We also have a repo with scripts/config for setting up vagrant boxes >> >> using packer. Might be a little out of date now but used to work. >> >> >> >> https://github.com/mirage/mirage-vagrant-vms >> >> >> >> (FWIW I've been trying to update it in the background to implement >> >> Magnus' instructions from the post mentioned above, but haven't >> >> finished yet. https://github.com/mor1/mirage-vagrant-vms if anyone >> >> wants to pick up from where I've currently stalled... :) >> > >> > >> > I've been working away slowly at this: >> > https://github.com/mattgray/mirage-xen-virtualbox which is basically >> Magnus' >> > blog post made into a packer template. >> > >> > I'm aiming at a system where I can compile a unikernel on my host >> machine, >> > and then run a command that will push the kernel to the vagrant VM, run >> it >> > (exposing the console somehow), and assign a DNS name using Avahi to the >> > DHCP-assigned IPv4 address. Still pondering that one, but at the moment >> the >> > box there is able the build and run MirageOS apps. You'll just need to >> share >> > a directory using NFS. I'll update the docs now with a simple >> walkthrough. >> > >> > Matt >> > >> >> >> >> -- >> Richard Mortier >> richard.mortier@cl.cam.ac.uk >> > > --001a11423caee68dcb050fd9b788 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
s/shared drive/shared directory/=C2=A0

On Tue, Feb 24, 2015 at 6:30 PM= , Matthew Gray <matthew.thomas.gray@gmail.com> w= rote:
Great! I've le= ft mapping a shared drive up to the users of the box, as it will vary by us= e-case. Also, I've tried to make it possible that one can customise the= Vagrantfile to allow a different private subnet within virtualbox - but bo= th these are untested / undocumented so far. Otherwise, I've updated th= e README on=C2=A0https://github.com/mattgray/mirage-xen-virtualbox= with instructions on how to build and use.

On = Tue, Feb 24, 2015 at 5:51 PM, Richard Mortier <richard.mortier@= cl.cam.ac.uk> wrote:
Awesom= e! I shall ditch my stalled attempt and use yours then :)
The `Vagrantfile` in the mirage-vagrant-vms directory should expose a
host-shared directory via NFS if that's any use.

On 24 February 2015 at 17:46, Matthew Gray
<matthew.thomas.gray@gmail.com> wrote:
> On Tue, Feb 24, 2015 at 3:36 PM, Richard Mortier
> <= richard.mortier@cl.cam.ac.uk> wrote:
>>
>> On 24 February 2015 at 13:05, Amir Chaudhry <amc79@cam.ac.uk> wrote:
>> >
>> > On 24 Feb 2015, at 12:56, yiorgos <antibra@hotmail.com> wrote:
>> >
>> >> ...Do you guys think that
>> >> developing can be done using this way or there will be a = quite great
>> >> amount of setting up/debugging VirtualBox (eg network int= erfaces etc)
>> >
>> > Magnus wrote a post about his VirtualBox set up for Mirage de= velopment.
>> > http://www.skjegstad.com/blog/2015/01/19= /mirageos-xen-virtualbox/
>>
>> We also have a repo with scripts/config for setting up vagrant box= es
>> using packer. Might be a little out of date now but used to work.<= br> >>
>> https://github.com/mirage/mirage-vagrant-vms
>>
>> (FWIW I've been trying to update it in the background to imple= ment
>> Magnus' instructions from the post mentioned above, but haven&= #39;t
>> finished yet.=C2=A0 https://github.com/mor1/mirage-vagrant-vms i= f anyone
>> wants to pick up from where I've currently stalled... :)
>
>
> I've been working away slowly at this:
> https://github.com/mattgray/mirage-xen-virtualbox which is = basically Magnus'
> blog post made into a packer template.
>
> I'm aiming at a system where I can compile a unikernel on my host = machine,
> and then run a command that will push the kernel to the vagrant VM, ru= n it
> (exposing the console somehow), and assign a DNS name using Avahi to t= he
> DHCP-assigned IPv4 address. Still pondering that one, but at the momen= t the
> box there is able the build and run MirageOS apps. You'll just nee= d to share
> a directory using NFS. I'll update the docs now with a simple walk= through.
>
> Matt
>



--
Richard Mortier
richard.m= ortier@cl.cam.ac.uk


--001a11423caee68dcb050fd9b788-- --===============1476431023516927674== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --===============1476431023516927674==-- From mirageos-devel-bounces@lists.xenproject.org Tue Feb 24 19:17:51 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 24 Feb 2015 19:17:51 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YQKzO-0001Ry-JI; Tue, 24 Feb 2015 19:17:50 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YQKzM-0001Ri-Na for mirageos-devel@lists.xenproject.org; Tue, 24 Feb 2015 19:17:48 +0000 Received: from [85.158.139.211] by server-5.bemta-5.messagelabs.com id 10/89-03164-C5ECCE45; Tue, 24 Feb 2015 19:17:48 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-10.tower-206.messagelabs.com!1424805467!5811955!1 X-Originating-IP: [74.125.82.180] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 19430 invoked from network); 24 Feb 2015 19:17:47 -0000 Received: from mail-we0-f180.google.com (HELO mail-we0-f180.google.com) (74.125.82.180) by server-10.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 24 Feb 2015 19:17:47 -0000 Received: by wesq59 with SMTP id q59so27328206wes.1 for ; Tue, 24 Feb 2015 11:17:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=1f6TCwOwzwZT+qJqA2jEBOZrbiBJHDikVGNKjl+sVK0=; b=QJjZh6PgioV90OIpHBXsya4WBC9IBp1IbS33dhaC04MECAkyvfSvhM+RQlI/+mgpig sGJ8e7C2vUcP0EJYFZiqMOfAG1n0uGF+qMRCeaN/aMPrPeh468Aj8R2WdWexNWSOSK2r wixfhm7EfVFqA2khkUZMahgwvutlowE6R/pl6dmmRvKIxRIpIbpTmwgIfJBzm4KgF0Cx vhGF/oUJus1jtPRY24T5TCYL/5GgaK46KqwUUtJwCpOt6/t3wKfYXhw7hyFgmRcbebwN hQstttwCYwKSQxCzhOvzJhgPtkPrHGgKFEtNRNrq+VTeRmmHLE7qDn7R7kONmsNN6AO5 4M7Q== X-Received: by 10.180.108.84 with SMTP id hi20mr7627423wib.86.1424805467018; Tue, 24 Feb 2015 11:17:47 -0800 (PST) Received: from [192.168.0.2] (cpc25-cmbg14-2-0-cust121.5-4.cable.virginm.net. [213.106.112.122]) by mx.google.com with ESMTPSA id jy7sm11931341wid.22.2015.02.24.11.17.45 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 24 Feb 2015 11:17:46 -0800 (PST) Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) From: Thomas Gazagnaire In-Reply-To: Date: Tue, 24 Feb 2015 19:17:47 +0000 Message-Id: References: <8CEDB416-6238-4888-BA4B-B7305FDDE2D9@gazagnaire.org> <9349273A-0BB4-40C4-BF06-4307085AA90C@recoil.org> <47D39FA3-050E-46E6-89D2-4253484E24A8@gazagnaire.org> To: Thomas Leonard X-Mailer: Apple Mail (2.2070.6) Cc: "mirageos-devel@lists.xenproject.org" , Anil Madhavapeddy Subject: Re: [MirageOS-devel] Irmin API newbie questions X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org Pj4+PiBPbmUgbGF5ZXIgdGhhdCB3b3VsZCBiZSB2ZXJ5IHVzZWZ1bCBvdmVyIHRoaXMgY29tbWl0 IGdyYXBoIGlzIHNvbWUgbm90aW9uIG9mCj4+Pj4gZGlmZnMuICBJJ2QgcXVpdGUgbGlrZSB0byBi ZSBhYmxlIHRvIGRlc2NyaWJlIGEgZGF0YSBzdHJ1Y3R1cmUgaW4gdGVybXMgb2YKPj4+PiBwYXRj aGVzLCBzaW5jZSB0aGF0J3MgcXVpdGUgb2Z0ZW4gdGhlIHJlYXNvbiB3aHkgSSdtIHRyYXZlcnNp bmcgdGhlIGhpc3RvcnkKPj4+PiBpbiB0aGUgZmlyc3QgcGxhY2UuICBJZiBJIGp1c3Qgd2FudCB0 byBnbyBiYWNrIGluIHRpbWUsIEkgY2FuIHN0YXNoIHJlbGV2YW50Cj4+Pj4gcG9pbnRzIGluIGEg dGFnIGFuZCBuZXZlciBuZWVkIHRvIHdhbGsgdGhlIGNvbW1pdCBoaXN0b3J5Lgo+Pj4gCj4+PiBH b29kIGlkZWEsIEknbGwgdHJ5IHRvIHNlZSBpZiBJIGNhbiBhZGQgYSBkaWZmIG9uIHRoZSBncmFw aCBlZGdlcyAodmlhIGEgdXNlci1wcm92aWRlZCBmdW5jdGlvbiB0byBjb21wdXRlIGRpZmZzKQo+ PiAKPj4gSSd2ZSBhZGRlZCBhIHNpbXBsZSBgSXJtaW4uaGlzdG9yeWAgZnVuY3Rpb24gdG8gZ2V0 IHRoZSBncmFwaCBvZiBjb21taXRzOiBodHRwOi8vbWlyYWdlLmdpdGh1Yi5pby9pcm1pbi9Jcm1p bi5odG1sI1ZBTGhpc3RvcnkKPiAKPiBUaGFua3MgLSB0aGF0J3Mgd29ya2luZyBuaWNlbHkuIEkn dmUgYWRkZWQgYSBwYWdlIHRvIG15IGpzX29mX29jYW1sCj4gYXBwIHRoYXQgc2hvd3MgdGhlIGxh c3QgZmV3IGNvbW1pdHMuCgpHcmVhdCEKCkxhdGVzdCBuZXdzIG9uIHRoZSBYZW4gZnJvbnQ6IEkn dmUgbWFuYWdlZCB0byBkbyBhIGBnaXQgY2xvbmVgIHVzaW5nIHRoZSBtaXJhZ2UgZGlyZWN0IFRD UElQIHN0YWNrIChpbiB1bml4KSBhbmQgdGhlIHJhdyBHaXQgcHJvdG9jb2wgKGdpdDovLykuIApU aGF0J3Mgc3RpbGwgYSBiaXQgY3VtYmVyc29tZToKLSBvbiBPU1gsIHRoZSBtaXJhZ2Ugc3RhY2sg bmVlZHMgdG8gaGF2ZSBhIERIQ1AgbGVhc2UgYmVmb3JlIGJlZW4gYWJsZSB0byBkbyBhIFRDUCBj b25uZWN0aW9uCi0gdGhlIFRMUyBzdGFjayBpcyBub3QgeWV0IGludGVncmF0ZWQgaW50byBjb25k dWl0IChzbyBJIGNhbm5vdCByZWFsbHkgdGVzdCB0aGUgc21hcnQgSFRUUCBwcm90b2NvbCB3aXRo IEdpdGh1YidzIGh0dHBzKQotIGFuZCB0aGVyZSBhIGZldyBiaXRzIGFuZCBwaWVjZXMgd2hpY2gg bmVlZHMgdG8gYmUgY2xlYW4tdXAuCgp3b3JraW5nIG9uIHRoZSBmdWxsIElybWluK1hlbiBpbnRl Z3JhdGlvbiB1bnRpbCB0aGUgZW5kIG9mIHRoZSB3ZWVrLgoKVGhvbWFzCgo+IAo+IE5vdGU6IGl0 J3MgcHJvYmFibHkgd29ydGggcmVtb3ZpbmcgIklybWluIGluc2lkZSB0aGUgYnJvd3NlciIgZnJv bSB0aGUKPiBQaW9uZWVyIFByb2plY3RzIGxpc3Qgbm93LiBJdCdzIHdvcmtpbmcgZmluZSAod2l0 aCBIVE1MNSBzdG9yYWdlKS4KPiBHZXR0aW5nIGl0IHRvIHdvcmsgaXMganVzdCBhIGNhc2Ugb2Yg bW9kaWZ5aW5nIElybWluIHRvIHVzZSBEYW5pZWwKPiBCw7xuemxpJ3MgcHVyZS1PQ2FtbCBpbXBs ZW1lbnRhdGlvbiBvZiBTSEEtMSBhbmQgaW1wbGVtZW50aW5nIGEgZmV3IEpTCj4gaGVscGVycyBm b3IgYmxpdHRpbmcgd2l0aCBiaWdhcnJheXMuCj4gCj4+IFRoZXJlIGlzIG5vIGRpZmYgb24gdGhl IGVkZ2VzIHlldCAoc2VlIGh0dHBzOi8vZ2l0aHViLmNvbS9taXJhZ2UvaXJtaW4vaXNzdWVzLzE1 MSB3aGljaCBrZWVwcyB0cmFjayBvZiB0aGF0KS4KPiAKPiAKPiAtLSAKPiBEciBUaG9tYXMgTGVv bmFyZCAgICAgICAgaHR0cDovLzBpbnN0YWxsLm5ldC8KPiBHUEc6IDkyNDIgOTgwNyBDOTg1IDND MDcgNDRBNiAgOEI5QSBBRTA3IDgyODAgNTlBNSAzQ0MxCj4gR1BHOiBEQTk4IDI1QUUgQ0FEMCA4 OTc1IDdDREEgIEJEOEUgMDcxMyAzRjk2IENBNzQgRDhCQQoKCl9fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fCk1pcmFnZU9TLWRldmVsIG1haWxpbmcgbGlzdApN aXJhZ2VPUy1kZXZlbEBsaXN0cy54ZW5wcm9qZWN0Lm9yZwpodHRwOi8vbGlzdHMueGVucHJvamVj dC5vcmcvY2dpLWJpbi9tYWlsbWFuL2xpc3RpbmZvL21pcmFnZW9zLWRldmVsCg== From mirageos-devel-bounces@lists.xenproject.org Tue Feb 24 19:17:51 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 24 Feb 2015 19:17:51 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YQKzO-0001Ry-JI; Tue, 24 Feb 2015 19:17:50 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YQKzM-0001Ri-Na for mirageos-devel@lists.xenproject.org; Tue, 24 Feb 2015 19:17:48 +0000 Received: from [85.158.139.211] by server-5.bemta-5.messagelabs.com id 10/89-03164-C5ECCE45; Tue, 24 Feb 2015 19:17:48 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-10.tower-206.messagelabs.com!1424805467!5811955!1 X-Originating-IP: [74.125.82.180] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 19430 invoked from network); 24 Feb 2015 19:17:47 -0000 Received: from mail-we0-f180.google.com (HELO mail-we0-f180.google.com) (74.125.82.180) by server-10.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 24 Feb 2015 19:17:47 -0000 Received: by wesq59 with SMTP id q59so27328206wes.1 for ; Tue, 24 Feb 2015 11:17:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=1f6TCwOwzwZT+qJqA2jEBOZrbiBJHDikVGNKjl+sVK0=; b=QJjZh6PgioV90OIpHBXsya4WBC9IBp1IbS33dhaC04MECAkyvfSvhM+RQlI/+mgpig sGJ8e7C2vUcP0EJYFZiqMOfAG1n0uGF+qMRCeaN/aMPrPeh468Aj8R2WdWexNWSOSK2r wixfhm7EfVFqA2khkUZMahgwvutlowE6R/pl6dmmRvKIxRIpIbpTmwgIfJBzm4KgF0Cx vhGF/oUJus1jtPRY24T5TCYL/5GgaK46KqwUUtJwCpOt6/t3wKfYXhw7hyFgmRcbebwN hQstttwCYwKSQxCzhOvzJhgPtkPrHGgKFEtNRNrq+VTeRmmHLE7qDn7R7kONmsNN6AO5 4M7Q== X-Received: by 10.180.108.84 with SMTP id hi20mr7627423wib.86.1424805467018; Tue, 24 Feb 2015 11:17:47 -0800 (PST) Received: from [192.168.0.2] (cpc25-cmbg14-2-0-cust121.5-4.cable.virginm.net. [213.106.112.122]) by mx.google.com with ESMTPSA id jy7sm11931341wid.22.2015.02.24.11.17.45 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 24 Feb 2015 11:17:46 -0800 (PST) Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) From: Thomas Gazagnaire In-Reply-To: Date: Tue, 24 Feb 2015 19:17:47 +0000 Message-Id: References: <8CEDB416-6238-4888-BA4B-B7305FDDE2D9@gazagnaire.org> <9349273A-0BB4-40C4-BF06-4307085AA90C@recoil.org> <47D39FA3-050E-46E6-89D2-4253484E24A8@gazagnaire.org> To: Thomas Leonard X-Mailer: Apple Mail (2.2070.6) Cc: "mirageos-devel@lists.xenproject.org" , Anil Madhavapeddy Subject: Re: [MirageOS-devel] Irmin API newbie questions X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org Pj4+PiBPbmUgbGF5ZXIgdGhhdCB3b3VsZCBiZSB2ZXJ5IHVzZWZ1bCBvdmVyIHRoaXMgY29tbWl0 IGdyYXBoIGlzIHNvbWUgbm90aW9uIG9mCj4+Pj4gZGlmZnMuICBJJ2QgcXVpdGUgbGlrZSB0byBi ZSBhYmxlIHRvIGRlc2NyaWJlIGEgZGF0YSBzdHJ1Y3R1cmUgaW4gdGVybXMgb2YKPj4+PiBwYXRj aGVzLCBzaW5jZSB0aGF0J3MgcXVpdGUgb2Z0ZW4gdGhlIHJlYXNvbiB3aHkgSSdtIHRyYXZlcnNp bmcgdGhlIGhpc3RvcnkKPj4+PiBpbiB0aGUgZmlyc3QgcGxhY2UuICBJZiBJIGp1c3Qgd2FudCB0 byBnbyBiYWNrIGluIHRpbWUsIEkgY2FuIHN0YXNoIHJlbGV2YW50Cj4+Pj4gcG9pbnRzIGluIGEg dGFnIGFuZCBuZXZlciBuZWVkIHRvIHdhbGsgdGhlIGNvbW1pdCBoaXN0b3J5Lgo+Pj4gCj4+PiBH b29kIGlkZWEsIEknbGwgdHJ5IHRvIHNlZSBpZiBJIGNhbiBhZGQgYSBkaWZmIG9uIHRoZSBncmFw aCBlZGdlcyAodmlhIGEgdXNlci1wcm92aWRlZCBmdW5jdGlvbiB0byBjb21wdXRlIGRpZmZzKQo+ PiAKPj4gSSd2ZSBhZGRlZCBhIHNpbXBsZSBgSXJtaW4uaGlzdG9yeWAgZnVuY3Rpb24gdG8gZ2V0 IHRoZSBncmFwaCBvZiBjb21taXRzOiBodHRwOi8vbWlyYWdlLmdpdGh1Yi5pby9pcm1pbi9Jcm1p bi5odG1sI1ZBTGhpc3RvcnkKPiAKPiBUaGFua3MgLSB0aGF0J3Mgd29ya2luZyBuaWNlbHkuIEkn dmUgYWRkZWQgYSBwYWdlIHRvIG15IGpzX29mX29jYW1sCj4gYXBwIHRoYXQgc2hvd3MgdGhlIGxh c3QgZmV3IGNvbW1pdHMuCgpHcmVhdCEKCkxhdGVzdCBuZXdzIG9uIHRoZSBYZW4gZnJvbnQ6IEkn dmUgbWFuYWdlZCB0byBkbyBhIGBnaXQgY2xvbmVgIHVzaW5nIHRoZSBtaXJhZ2UgZGlyZWN0IFRD UElQIHN0YWNrIChpbiB1bml4KSBhbmQgdGhlIHJhdyBHaXQgcHJvdG9jb2wgKGdpdDovLykuIApU aGF0J3Mgc3RpbGwgYSBiaXQgY3VtYmVyc29tZToKLSBvbiBPU1gsIHRoZSBtaXJhZ2Ugc3RhY2sg bmVlZHMgdG8gaGF2ZSBhIERIQ1AgbGVhc2UgYmVmb3JlIGJlZW4gYWJsZSB0byBkbyBhIFRDUCBj b25uZWN0aW9uCi0gdGhlIFRMUyBzdGFjayBpcyBub3QgeWV0IGludGVncmF0ZWQgaW50byBjb25k dWl0IChzbyBJIGNhbm5vdCByZWFsbHkgdGVzdCB0aGUgc21hcnQgSFRUUCBwcm90b2NvbCB3aXRo IEdpdGh1YidzIGh0dHBzKQotIGFuZCB0aGVyZSBhIGZldyBiaXRzIGFuZCBwaWVjZXMgd2hpY2gg bmVlZHMgdG8gYmUgY2xlYW4tdXAuCgp3b3JraW5nIG9uIHRoZSBmdWxsIElybWluK1hlbiBpbnRl Z3JhdGlvbiB1bnRpbCB0aGUgZW5kIG9mIHRoZSB3ZWVrLgoKVGhvbWFzCgo+IAo+IE5vdGU6IGl0 J3MgcHJvYmFibHkgd29ydGggcmVtb3ZpbmcgIklybWluIGluc2lkZSB0aGUgYnJvd3NlciIgZnJv bSB0aGUKPiBQaW9uZWVyIFByb2plY3RzIGxpc3Qgbm93LiBJdCdzIHdvcmtpbmcgZmluZSAod2l0 aCBIVE1MNSBzdG9yYWdlKS4KPiBHZXR0aW5nIGl0IHRvIHdvcmsgaXMganVzdCBhIGNhc2Ugb2Yg bW9kaWZ5aW5nIElybWluIHRvIHVzZSBEYW5pZWwKPiBCw7xuemxpJ3MgcHVyZS1PQ2FtbCBpbXBs ZW1lbnRhdGlvbiBvZiBTSEEtMSBhbmQgaW1wbGVtZW50aW5nIGEgZmV3IEpTCj4gaGVscGVycyBm b3IgYmxpdHRpbmcgd2l0aCBiaWdhcnJheXMuCj4gCj4+IFRoZXJlIGlzIG5vIGRpZmYgb24gdGhl IGVkZ2VzIHlldCAoc2VlIGh0dHBzOi8vZ2l0aHViLmNvbS9taXJhZ2UvaXJtaW4vaXNzdWVzLzE1 MSB3aGljaCBrZWVwcyB0cmFjayBvZiB0aGF0KS4KPiAKPiAKPiAtLSAKPiBEciBUaG9tYXMgTGVv bmFyZCAgICAgICAgaHR0cDovLzBpbnN0YWxsLm5ldC8KPiBHUEc6IDkyNDIgOTgwNyBDOTg1IDND MDcgNDRBNiAgOEI5QSBBRTA3IDgyODAgNTlBNSAzQ0MxCj4gR1BHOiBEQTk4IDI1QUUgQ0FEMCA4 OTc1IDdDREEgIEJEOEUgMDcxMyAzRjk2IENBNzQgRDhCQQoKCl9fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fCk1pcmFnZU9TLWRldmVsIG1haWxpbmcgbGlzdApN aXJhZ2VPUy1kZXZlbEBsaXN0cy54ZW5wcm9qZWN0Lm9yZwpodHRwOi8vbGlzdHMueGVucHJvamVj dC5vcmcvY2dpLWJpbi9tYWlsbWFuL2xpc3RpbmZvL21pcmFnZW9zLWRldmVsCg== From mirageos-devel-bounces@lists.xenproject.org Tue Feb 24 21:04:04 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 24 Feb 2015 21:04:04 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YQMe6-0008Hy-Lu; Tue, 24 Feb 2015 21:03:58 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YQMe5-0008H3-IF for mirageos-devel@lists.xenproject.org; Tue, 24 Feb 2015 21:03:57 +0000 Received: from [85.158.137.68] by server-13.bemta-3.messagelabs.com id 24/33-02898-C37ECE45; Tue, 24 Feb 2015 21:03:56 +0000 X-Env-Sender: stefanxe@gmx.net X-Msg-Ref: server-12.tower-31.messagelabs.com!1424811834!11869604!1 X-Originating-IP: [212.227.15.19] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: QmFkIElQOiAyMTIuMjI3LjE1LjE5ID0+IDI1MjI5\n,sa_preprocessor: QmFkIElQOiAyMTIuMjI3LjE1LjE5ID0+IDI1MjI5\n X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15061 invoked from network); 24 Feb 2015 21:03:54 -0000 Received: from mout.gmx.net (HELO mout.gmx.net) (212.227.15.19) by server-12.tower-31.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 24 Feb 2015 21:03:54 -0000 Received: from [192.168.178.37] ([93.220.116.75]) by mail.gmx.com (mrgmx002) with ESMTPSA (Nemesis) id 0Lck9X-1Xhuft0bTD-00k5vf for ; Tue, 24 Feb 2015 22:03:54 +0100 Message-ID: <54ECE738.4040103@gmx.net> Date: Tue, 24 Feb 2015 22:03:52 +0100 From: Stefan Xenon User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: mirageos-devel@lists.xenproject.org X-Provags-ID: V03:K0:krBCq3FWNLFc1pKVs5eY3QY2ornXfOt5Y31ns4iqEujIdFy7Ag4 J3YbMUvfSLfePUWjIvIJUDwxoZg9cfJo2ASmEuT6CAqFvhdN6wNF2ZRTkcVqhwk3lS5IfjI 8rlp0eOCf0wl3OvJ1bS+PlPehf0clC5OzVufEHJPO3YWI+99VtRTVLj0dR6CBb1cHY923Lp 0T4m7lliJxVW61pmjxfKQ== X-UI-Out-Filterresults: notjunk:1; Subject: [MirageOS-devel] kernel and security guarantees X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org Hi! I have two questions on MirageOS' general security: I understand a significant portion of MirageOS and the entire Xen are written in type-unsafe C. Even though Ocaml has strong guarantees, how much does it help as long as the kernel is potentially unsafe? What is the impact on practical system security? Is there any track record of exploitable bugs which could help to compare it with other systems? The micro kernel "seL4 (formally) Verified" has been released as open source. It sounds like a potentially powerful combination with Mirage. Would it be feasible to port MirageOS to seL4? Are there any plans to do so? Regards, Stefan _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Tue Feb 24 21:04:04 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 24 Feb 2015 21:04:04 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YQMe6-0008Hy-Lu; Tue, 24 Feb 2015 21:03:58 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YQMe5-0008H3-IF for mirageos-devel@lists.xenproject.org; Tue, 24 Feb 2015 21:03:57 +0000 Received: from [85.158.137.68] by server-13.bemta-3.messagelabs.com id 24/33-02898-C37ECE45; Tue, 24 Feb 2015 21:03:56 +0000 X-Env-Sender: stefanxe@gmx.net X-Msg-Ref: server-12.tower-31.messagelabs.com!1424811834!11869604!1 X-Originating-IP: [212.227.15.19] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: QmFkIElQOiAyMTIuMjI3LjE1LjE5ID0+IDI1MjI5\n,sa_preprocessor: QmFkIElQOiAyMTIuMjI3LjE1LjE5ID0+IDI1MjI5\n X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15061 invoked from network); 24 Feb 2015 21:03:54 -0000 Received: from mout.gmx.net (HELO mout.gmx.net) (212.227.15.19) by server-12.tower-31.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 24 Feb 2015 21:03:54 -0000 Received: from [192.168.178.37] ([93.220.116.75]) by mail.gmx.com (mrgmx002) with ESMTPSA (Nemesis) id 0Lck9X-1Xhuft0bTD-00k5vf for ; Tue, 24 Feb 2015 22:03:54 +0100 Message-ID: <54ECE738.4040103@gmx.net> Date: Tue, 24 Feb 2015 22:03:52 +0100 From: Stefan Xenon User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: mirageos-devel@lists.xenproject.org X-Provags-ID: V03:K0:krBCq3FWNLFc1pKVs5eY3QY2ornXfOt5Y31ns4iqEujIdFy7Ag4 J3YbMUvfSLfePUWjIvIJUDwxoZg9cfJo2ASmEuT6CAqFvhdN6wNF2ZRTkcVqhwk3lS5IfjI 8rlp0eOCf0wl3OvJ1bS+PlPehf0clC5OzVufEHJPO3YWI+99VtRTVLj0dR6CBb1cHY923Lp 0T4m7lliJxVW61pmjxfKQ== X-UI-Out-Filterresults: notjunk:1; Subject: [MirageOS-devel] kernel and security guarantees X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org Hi! I have two questions on MirageOS' general security: I understand a significant portion of MirageOS and the entire Xen are written in type-unsafe C. Even though Ocaml has strong guarantees, how much does it help as long as the kernel is potentially unsafe? What is the impact on practical system security? Is there any track record of exploitable bugs which could help to compare it with other systems? The micro kernel "seL4 (formally) Verified" has been released as open source. It sounds like a potentially powerful combination with Mirage. Would it be feasible to port MirageOS to seL4? Are there any plans to do so? Regards, Stefan _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Wed Feb 25 04:21:43 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 25 Feb 2015 04:21:43 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YQTTd-00048A-8E; Wed, 25 Feb 2015 04:21:37 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YQTTb-00047B-Ky; Wed, 25 Feb 2015 04:21:35 +0000 Received: from [85.158.139.211] by server-6.bemta-5.messagelabs.com id CB/A4-03165-ECD4DE45; Wed, 25 Feb 2015 04:21:34 +0000 X-Env-Sender: russell.pavlicek.xen@gmail.com X-Msg-Ref: server-14.tower-206.messagelabs.com!1424838093!5741793!1 X-Originating-IP: [209.85.217.173] X-SpamReason: No, hits=2.5 required=7.0 tests=RCVD_BY_IP, SUSPICIOUS_RECIPS X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21928 invoked from network); 25 Feb 2015 04:21:33 -0000 Received: from mail-lb0-f173.google.com (HELO mail-lb0-f173.google.com) (209.85.217.173) by server-14.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 25 Feb 2015 04:21:33 -0000 Received: by lbiw7 with SMTP id w7so1278668lbi.10; Tue, 24 Feb 2015 20:21:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:message-id:subject:from:to:content-type; bh=F1WrkDTJiK5ivOBbAWxZzjZGiv87kyaWGuHMz8mcDs8=; b=Xv9/MD5rF/pW/aPdUOy6HjvpkxvxvM2SvryOcajaE3FkoLL+nVEpiTOqAI0aH1tnXf g8GXMdofTTVjLk5W4Cq6Fif5VehYc06DtaXx+m0PZi5sSqAt4MhoQbjW5kYPSDMotIHL pUXYN1KTkd9Jrj8KlJV1ZohNVgATT4dJD0iXVXY+yGq5aiYUf+ZZ1YV8Z5gg1BpxXhrC dI+maOl+sTUXBmowhNGYWvR31j4jovhCnQ+mCx4PVQB/GSrLs15duPMJ1PoWp47v380p ikgvzxdSxOMIYspn8dLKaeHX15Wf2CLZK+cVl5G5TuWbMGKidcBY+Z7rX2SO+ncbOuup ES6g== MIME-Version: 1.0 X-Received: by 10.152.1.40 with SMTP id 8mr901354laj.97.1424838092995; Tue, 24 Feb 2015 20:21:32 -0800 (PST) Received: by 10.112.147.135 with HTTP; Tue, 24 Feb 2015 20:21:32 -0800 (PST) Date: Tue, 24 Feb 2015 23:21:32 -0500 X-Google-Sender-Auth: GMM4h6YWDAXq-1kQ-hO8q1SRGYA Message-ID: From: Russ Pavlicek To: xen-users@lists.xenproject.org, xen-devel@lists.xenproject.org, mirageos-devel@lists.xenproject.org, xen-api@lists.xen.org, xs-devel@lists.xenserver.org Subject: [MirageOS-devel] Welcome to Xen Project Document Day for February: The Great 4.5 Clean-Up (Part II) X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org Today, Wednesday, is Xen Project Document Day for February! The documentation around the recent 4.5 release is improving, but there is still need for more clean-up. We still have a number of pages which talk in terms of xend rather than libxenlight. For example, check the TODO list (see below) for a list of pages which we know still feature the "xm" command instead of "xl". Have you seen a page which needs updating? If you can't update it, please add it to the list under "THE GREAT 4.5 CLEAN-UP" on the TODO list. If we can identify and update these pages, we'll help new users tremendously. There are few things as bad as trying a command which does not exist and is not available. Let's not frustrate our newbies. All the information you need to participate in Document Day is here: http://wiki.xenproject.org/wiki/Xen_Document_Days Also take a look at the current TODO list to see other items which need attention: http://wiki.xenproject.org/wiki/Xen_Document_Days/TODO Please think about how you can help out. If you haven't requested to be made a Wiki editor, just fill out the form below: http://xenproject.org/component/content/article/100-misc/145-request-to-be-made-a-wiki-editor.html We hope to see you today in #xendocs! _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Wed Feb 25 04:21:43 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 25 Feb 2015 04:21:43 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YQTTd-00048A-8E; Wed, 25 Feb 2015 04:21:37 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YQTTb-00047B-Ky; Wed, 25 Feb 2015 04:21:35 +0000 Received: from [85.158.139.211] by server-6.bemta-5.messagelabs.com id CB/A4-03165-ECD4DE45; Wed, 25 Feb 2015 04:21:34 +0000 X-Env-Sender: russell.pavlicek.xen@gmail.com X-Msg-Ref: server-14.tower-206.messagelabs.com!1424838093!5741793!1 X-Originating-IP: [209.85.217.173] X-SpamReason: No, hits=2.5 required=7.0 tests=RCVD_BY_IP, SUSPICIOUS_RECIPS X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21928 invoked from network); 25 Feb 2015 04:21:33 -0000 Received: from mail-lb0-f173.google.com (HELO mail-lb0-f173.google.com) (209.85.217.173) by server-14.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 25 Feb 2015 04:21:33 -0000 Received: by lbiw7 with SMTP id w7so1278668lbi.10; Tue, 24 Feb 2015 20:21:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:message-id:subject:from:to:content-type; bh=F1WrkDTJiK5ivOBbAWxZzjZGiv87kyaWGuHMz8mcDs8=; b=Xv9/MD5rF/pW/aPdUOy6HjvpkxvxvM2SvryOcajaE3FkoLL+nVEpiTOqAI0aH1tnXf g8GXMdofTTVjLk5W4Cq6Fif5VehYc06DtaXx+m0PZi5sSqAt4MhoQbjW5kYPSDMotIHL pUXYN1KTkd9Jrj8KlJV1ZohNVgATT4dJD0iXVXY+yGq5aiYUf+ZZ1YV8Z5gg1BpxXhrC dI+maOl+sTUXBmowhNGYWvR31j4jovhCnQ+mCx4PVQB/GSrLs15duPMJ1PoWp47v380p ikgvzxdSxOMIYspn8dLKaeHX15Wf2CLZK+cVl5G5TuWbMGKidcBY+Z7rX2SO+ncbOuup ES6g== MIME-Version: 1.0 X-Received: by 10.152.1.40 with SMTP id 8mr901354laj.97.1424838092995; Tue, 24 Feb 2015 20:21:32 -0800 (PST) Received: by 10.112.147.135 with HTTP; Tue, 24 Feb 2015 20:21:32 -0800 (PST) Date: Tue, 24 Feb 2015 23:21:32 -0500 X-Google-Sender-Auth: GMM4h6YWDAXq-1kQ-hO8q1SRGYA Message-ID: From: Russ Pavlicek To: xen-users@lists.xenproject.org, xen-devel@lists.xenproject.org, mirageos-devel@lists.xenproject.org, xen-api@lists.xen.org, xs-devel@lists.xenserver.org Subject: [MirageOS-devel] Welcome to Xen Project Document Day for February: The Great 4.5 Clean-Up (Part II) X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org Today, Wednesday, is Xen Project Document Day for February! The documentation around the recent 4.5 release is improving, but there is still need for more clean-up. We still have a number of pages which talk in terms of xend rather than libxenlight. For example, check the TODO list (see below) for a list of pages which we know still feature the "xm" command instead of "xl". Have you seen a page which needs updating? If you can't update it, please add it to the list under "THE GREAT 4.5 CLEAN-UP" on the TODO list. If we can identify and update these pages, we'll help new users tremendously. There are few things as bad as trying a command which does not exist and is not available. Let's not frustrate our newbies. All the information you need to participate in Document Day is here: http://wiki.xenproject.org/wiki/Xen_Document_Days Also take a look at the current TODO list to see other items which need attention: http://wiki.xenproject.org/wiki/Xen_Document_Days/TODO Please think about how you can help out. If you haven't requested to be made a Wiki editor, just fill out the form below: http://xenproject.org/component/content/article/100-misc/145-request-to-be-made-a-wiki-editor.html We hope to see you today in #xendocs! _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Wed Feb 25 16:04:56 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 25 Feb 2015 16:04:56 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YQeSA-0000vG-TO; Wed, 25 Feb 2015 16:04:50 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YQeS9-0000ui-M7 for mirageos-devel@lists.xenproject.org; Wed, 25 Feb 2015 16:04:49 +0000 Received: from [85.158.139.211] by server-14.bemta-5.messagelabs.com id FB/4F-02809-0A2FDE45; Wed, 25 Feb 2015 16:04:48 +0000 X-Env-Sender: amc79@cam.ac.uk X-Msg-Ref: server-4.tower-206.messagelabs.com!1424880288!11340100!1 X-Originating-IP: [131.111.8.150] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTMxLjExMS44LjE1MCA9PiAxNDk0MDU=\n X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12536 invoked from network); 25 Feb 2015 16:04:48 -0000 Received: from ppsw-50.csi.cam.ac.uk (HELO ppsw-50.csi.cam.ac.uk) (131.111.8.150) by server-4.tower-206.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 25 Feb 2015 16:04:48 -0000 X-Cam-AntiVirus: no malware found X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/ Received: from cpc17-cmbg14-2-0-cust360.5-4.cable.virginm.net ([86.6.155.105]:56129 helo=[192.168.0.15]) by ppsw-50.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.158]:587) with esmtpsa (PLAIN:amc79) (TLSv1:AES128-SHA:128) id 1YQeS7-0000Su-rz (Exim 4.82_3-c0e5623) for mirageos-devel@lists.xenproject.org (return-path ); Wed, 25 Feb 2015 16:04:47 +0000 Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) From: Amir Chaudhry In-Reply-To: Date: Wed, 25 Feb 2015 16:04:46 +0000 Message-Id: <9EF9294F-7561-4A72-B83B-B8D7ACC5B1BE@cam.ac.uk> References: To: "mirageos-devel@lists.xenproject.org" X-Mailer: Apple Mail (2.1510) Subject: Re: [MirageOS-devel] Mirage fortnightly call - Wednesday 25th at 4pm GMT X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: quoted-printable Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org We'll be on Google Hangout. https://plus.google.com/hangouts/_/gq7e36svyh3okzlban3s65nwnya On 24 Feb 2015, at 11:46, Amir Chaudhry wrote: > Hi folks, > = > The next Mirage call will take place this Wednesday afternoon at 4pm GMT = and is open to all. > = > Notes from last time are up at http://openmirage.org/wiki/weekly-2015-02-= 11 = > = > The agenda is currently as follows: > = > =95 mirage-net-xen 1.3.0 dead-lock/race (see https://github.com/mirage/mi= rage-net-xen/issues/20) > =95 Quality and Test Infra > =95 Automate all the things > =95 Mirage.io > =95 Irmin progress > =95 Pioneer Projects > =95 3.0 Planning > = > If you have things to add/edit, please do so at https://github.com/mirage= /mirage-www/wiki/Call-Agenda > = > GoToMeeting details are below but if there are any hiccups/delays then I'= ll switch to a public Google Hangout. If that happens, I'll post the link = here and also in the IRC channel (#mirage on freenode). > = > Join us at 4pm GMT on Wednesday! > = > 1. Please join my meeting. > https://www1.gotomeeting.com/join/591890401 > = > Dial in numbers (ask if you need a specific country): > United Kingdom: +44 (0) 20 3657 6778 > United States: +1 (213) 493-0014 > Access Code: 591-890-401 > Audio PIN: Shown after joining the meeting > = > Best wishes, > Amir _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Wed Feb 25 16:04:56 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 25 Feb 2015 16:04:56 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YQeSA-0000vG-TO; Wed, 25 Feb 2015 16:04:50 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YQeS9-0000ui-M7 for mirageos-devel@lists.xenproject.org; Wed, 25 Feb 2015 16:04:49 +0000 Received: from [85.158.139.211] by server-14.bemta-5.messagelabs.com id FB/4F-02809-0A2FDE45; Wed, 25 Feb 2015 16:04:48 +0000 X-Env-Sender: amc79@cam.ac.uk X-Msg-Ref: server-4.tower-206.messagelabs.com!1424880288!11340100!1 X-Originating-IP: [131.111.8.150] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTMxLjExMS44LjE1MCA9PiAxNDk0MDU=\n X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12536 invoked from network); 25 Feb 2015 16:04:48 -0000 Received: from ppsw-50.csi.cam.ac.uk (HELO ppsw-50.csi.cam.ac.uk) (131.111.8.150) by server-4.tower-206.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 25 Feb 2015 16:04:48 -0000 X-Cam-AntiVirus: no malware found X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/ Received: from cpc17-cmbg14-2-0-cust360.5-4.cable.virginm.net ([86.6.155.105]:56129 helo=[192.168.0.15]) by ppsw-50.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.158]:587) with esmtpsa (PLAIN:amc79) (TLSv1:AES128-SHA:128) id 1YQeS7-0000Su-rz (Exim 4.82_3-c0e5623) for mirageos-devel@lists.xenproject.org (return-path ); Wed, 25 Feb 2015 16:04:47 +0000 Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) From: Amir Chaudhry In-Reply-To: Date: Wed, 25 Feb 2015 16:04:46 +0000 Message-Id: <9EF9294F-7561-4A72-B83B-B8D7ACC5B1BE@cam.ac.uk> References: To: "mirageos-devel@lists.xenproject.org" X-Mailer: Apple Mail (2.1510) Subject: Re: [MirageOS-devel] Mirage fortnightly call - Wednesday 25th at 4pm GMT X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: quoted-printable Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org We'll be on Google Hangout. https://plus.google.com/hangouts/_/gq7e36svyh3okzlban3s65nwnya On 24 Feb 2015, at 11:46, Amir Chaudhry wrote: > Hi folks, > = > The next Mirage call will take place this Wednesday afternoon at 4pm GMT = and is open to all. > = > Notes from last time are up at http://openmirage.org/wiki/weekly-2015-02-= 11 = > = > The agenda is currently as follows: > = > =95 mirage-net-xen 1.3.0 dead-lock/race (see https://github.com/mirage/mi= rage-net-xen/issues/20) > =95 Quality and Test Infra > =95 Automate all the things > =95 Mirage.io > =95 Irmin progress > =95 Pioneer Projects > =95 3.0 Planning > = > If you have things to add/edit, please do so at https://github.com/mirage= /mirage-www/wiki/Call-Agenda > = > GoToMeeting details are below but if there are any hiccups/delays then I'= ll switch to a public Google Hangout. If that happens, I'll post the link = here and also in the IRC channel (#mirage on freenode). > = > Join us at 4pm GMT on Wednesday! > = > 1. Please join my meeting. > https://www1.gotomeeting.com/join/591890401 > = > Dial in numbers (ask if you need a specific country): > United Kingdom: +44 (0) 20 3657 6778 > United States: +1 (213) 493-0014 > Access Code: 591-890-401 > Audio PIN: Shown after joining the meeting > = > Best wishes, > Amir _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Wed Feb 25 19:06:37 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 25 Feb 2015 19:06:37 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YQhHy-0000jE-3c; Wed, 25 Feb 2015 19:06:30 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YQhHx-0000it-4l for mirageos-devel@lists.xenproject.org; Wed, 25 Feb 2015 19:06:29 +0000 Received: from [85.158.139.211] by server-17.bemta-5.messagelabs.com id 33/E1-03132-43D1EE45; Wed, 25 Feb 2015 19:06:28 +0000 X-Env-Sender: talex5@gmail.com X-Msg-Ref: server-2.tower-206.messagelabs.com!1424891187!11348706!1 X-Originating-IP: [209.85.215.49] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16331 invoked from network); 25 Feb 2015 19:06:27 -0000 Received: from mail-la0-f49.google.com (HELO mail-la0-f49.google.com) (209.85.215.49) by server-2.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 25 Feb 2015 19:06:27 -0000 Received: by labgq15 with SMTP id gq15so6114610lab.3 for ; Wed, 25 Feb 2015 11:06:27 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=HHyz0nUmWSkrRh0p5pz8DVhZ4l1cSUcofsqmEC+tI4E=; b=XZf5oNqzea1eUUbBILd1snKTg+ZrKUaKcuDtSuxIrEW+YxhD6OWjKNC/Np7WNN86Ll QP6TOwAfsgopRsfnT0DMfc8/sw4EpNDjNrJ/qGXY2u0KCoSWytGItq88fTpnBOCSLnCZ 13cJRQGYVACg2PfJDPL2LzPsyE0s2YriDC34aNTuAbhPZoDklJkp24ZWhsEqqziSq14R 3HipIEgvHJvAR1f1VzPx3lV727zhg5d/1rjKaagMf6OkFLKaxW0SxKkM+gqBltR9dNcq pRZ0NCr22prtqOsqfKfJReQrYYSHRcS2lNydi9yghSQWwEEg2A374vOE6QL0aVZnx+P7 MLpw== MIME-Version: 1.0 X-Received: by 10.153.4.44 with SMTP id cb12mr4291777lad.26.1424891187178; Wed, 25 Feb 2015 11:06:27 -0800 (PST) Received: by 10.25.207.17 with HTTP; Wed, 25 Feb 2015 11:06:27 -0800 (PST) In-Reply-To: <54ECE738.4040103@gmx.net> References: <54ECE738.4040103@gmx.net> Date: Wed, 25 Feb 2015 19:06:27 +0000 Message-ID: From: Thomas Leonard To: Stefan Xenon Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] kernel and security guarantees X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 24 February 2015 at 21:03, Stefan Xenon wrote: > Hi! > I have two questions on MirageOS' general security: > > I understand a significant portion of MirageOS and the entire Xen are > written in type-unsafe C. Even though Ocaml has strong guarantees, how > much does it help as long as the kernel is potentially unsafe? Hi Stefan, For the Xen version of Mirage, the C code that runs in the guest is roughly: - Mini-OS (prink, malloc, assert, assembler boot code, interrupt handler) - openlibm (standard maths functions, sin, cos, etc) - OCaml runtime (the garbage collector basically) - OCaml C bindings for Mini-OS, memory barriers, etc There's no libc. Some OCaml libraries may pull in more C code. e.g. ocaml-tls requires libgmp to provide fast big ints for crypto stuff. It's unlikely there's much you could remove from here. In terms of security problems from C code, the Linux dom0 is likely to be the weakest point. It is possible to move some of these functions (network drivers, USB drivers, etc) into their own Xen guests, as Qubes does, which should help a lot. > What is > the impact on practical system security? Is there any track record of > exploitable bugs which could help to compare it with other systems? I'm not aware of any. > The micro kernel "seL4 (formally) Verified" has been released as open > source. It sounds like a potentially powerful combination with Mirage. > Would it be feasible to port MirageOS to seL4? Are there any plans to do so? As far as I know, the process for porting Mirage goes something like this: 1. Get the OCaml runtime working on the target (enough to run hello world). You'll need to provide malloc for this, although it doesn't need to be very good (OCaml will just allocate some large blocks of memory for its GC pool). You'll want some kind of debug interface so printing debug messages works. 2. Implement a Lwt event loop (checking for events from the host system and sleeping if there aren't any). The main loop function you provide is normally called OS.Main.run. 3. Start writing libraries, implementing the Mirage interfaces (e.g. make a mirage-console-sel4 library implementing the CONSOLE module type). Once you have a few low-level ones done, the higher-level libraries should work automatically (e.g. once you implement NETWORK, you should find TCP/IP works). 4. Update the mirage tool to generate a suitable main.ml for your platform when invokes as "mirage configure --sel4". Your biggest problem will likely be drivers for the physical hardware. You'll probably want to start with some existing C ones and run them as separate sel4 processes. -- Dr Thomas Leonard http://0install.net/ GPG: 9242 9807 C985 3C07 44A6 8B9A AE07 8280 59A5 3CC1 GPG: DA98 25AE CAD0 8975 7CDA BD8E 0713 3F96 CA74 D8BA _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Wed Feb 25 19:06:37 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 25 Feb 2015 19:06:37 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YQhHy-0000jE-3c; Wed, 25 Feb 2015 19:06:30 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YQhHx-0000it-4l for mirageos-devel@lists.xenproject.org; Wed, 25 Feb 2015 19:06:29 +0000 Received: from [85.158.139.211] by server-17.bemta-5.messagelabs.com id 33/E1-03132-43D1EE45; Wed, 25 Feb 2015 19:06:28 +0000 X-Env-Sender: talex5@gmail.com X-Msg-Ref: server-2.tower-206.messagelabs.com!1424891187!11348706!1 X-Originating-IP: [209.85.215.49] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16331 invoked from network); 25 Feb 2015 19:06:27 -0000 Received: from mail-la0-f49.google.com (HELO mail-la0-f49.google.com) (209.85.215.49) by server-2.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 25 Feb 2015 19:06:27 -0000 Received: by labgq15 with SMTP id gq15so6114610lab.3 for ; Wed, 25 Feb 2015 11:06:27 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=HHyz0nUmWSkrRh0p5pz8DVhZ4l1cSUcofsqmEC+tI4E=; b=XZf5oNqzea1eUUbBILd1snKTg+ZrKUaKcuDtSuxIrEW+YxhD6OWjKNC/Np7WNN86Ll QP6TOwAfsgopRsfnT0DMfc8/sw4EpNDjNrJ/qGXY2u0KCoSWytGItq88fTpnBOCSLnCZ 13cJRQGYVACg2PfJDPL2LzPsyE0s2YriDC34aNTuAbhPZoDklJkp24ZWhsEqqziSq14R 3HipIEgvHJvAR1f1VzPx3lV727zhg5d/1rjKaagMf6OkFLKaxW0SxKkM+gqBltR9dNcq pRZ0NCr22prtqOsqfKfJReQrYYSHRcS2lNydi9yghSQWwEEg2A374vOE6QL0aVZnx+P7 MLpw== MIME-Version: 1.0 X-Received: by 10.153.4.44 with SMTP id cb12mr4291777lad.26.1424891187178; Wed, 25 Feb 2015 11:06:27 -0800 (PST) Received: by 10.25.207.17 with HTTP; Wed, 25 Feb 2015 11:06:27 -0800 (PST) In-Reply-To: <54ECE738.4040103@gmx.net> References: <54ECE738.4040103@gmx.net> Date: Wed, 25 Feb 2015 19:06:27 +0000 Message-ID: From: Thomas Leonard To: Stefan Xenon Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] kernel and security guarantees X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 24 February 2015 at 21:03, Stefan Xenon wrote: > Hi! > I have two questions on MirageOS' general security: > > I understand a significant portion of MirageOS and the entire Xen are > written in type-unsafe C. Even though Ocaml has strong guarantees, how > much does it help as long as the kernel is potentially unsafe? Hi Stefan, For the Xen version of Mirage, the C code that runs in the guest is roughly: - Mini-OS (prink, malloc, assert, assembler boot code, interrupt handler) - openlibm (standard maths functions, sin, cos, etc) - OCaml runtime (the garbage collector basically) - OCaml C bindings for Mini-OS, memory barriers, etc There's no libc. Some OCaml libraries may pull in more C code. e.g. ocaml-tls requires libgmp to provide fast big ints for crypto stuff. It's unlikely there's much you could remove from here. In terms of security problems from C code, the Linux dom0 is likely to be the weakest point. It is possible to move some of these functions (network drivers, USB drivers, etc) into their own Xen guests, as Qubes does, which should help a lot. > What is > the impact on practical system security? Is there any track record of > exploitable bugs which could help to compare it with other systems? I'm not aware of any. > The micro kernel "seL4 (formally) Verified" has been released as open > source. It sounds like a potentially powerful combination with Mirage. > Would it be feasible to port MirageOS to seL4? Are there any plans to do so? As far as I know, the process for porting Mirage goes something like this: 1. Get the OCaml runtime working on the target (enough to run hello world). You'll need to provide malloc for this, although it doesn't need to be very good (OCaml will just allocate some large blocks of memory for its GC pool). You'll want some kind of debug interface so printing debug messages works. 2. Implement a Lwt event loop (checking for events from the host system and sleeping if there aren't any). The main loop function you provide is normally called OS.Main.run. 3. Start writing libraries, implementing the Mirage interfaces (e.g. make a mirage-console-sel4 library implementing the CONSOLE module type). Once you have a few low-level ones done, the higher-level libraries should work automatically (e.g. once you implement NETWORK, you should find TCP/IP works). 4. Update the mirage tool to generate a suitable main.ml for your platform when invokes as "mirage configure --sel4". Your biggest problem will likely be drivers for the physical hardware. You'll probably want to start with some existing C ones and run them as separate sel4 processes. -- Dr Thomas Leonard http://0install.net/ GPG: 9242 9807 C985 3C07 44A6 8B9A AE07 8280 59A5 3CC1 GPG: DA98 25AE CAD0 8975 7CDA BD8E 0713 3F96 CA74 D8BA _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Thu Feb 26 15:17:27 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 26 Feb 2015 15:17:27 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YR0Bm-0006AB-8i; Thu, 26 Feb 2015 15:17:22 +0000 Message-Id: Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YR0Bk-0006A3-Vz for mirageos-devel@lists.xenproject.org; Thu, 26 Feb 2015 15:17:21 +0000 Received: from [193.109.254.147] by server-15.bemta-14.messagelabs.com id 8A/40-02770-0093FE45; Thu, 26 Feb 2015 15:17:20 +0000 X-Env-Sender: guweha@web.de X-Msg-Ref: server-8.tower-27.messagelabs.com!1424963838!13137362!1 X-Originating-IP: [217.140.73.121] X-SpamReason: No, hits=2.0 required=7.0 tests=msgid: No Message-ID, received_headers: No Received headers X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21778 invoked from network); 26 Feb 2015 15:17:19 -0000 Received: from mx1.ig-haase.de (HELO mx1.ig-haase.de) (217.140.73.121) by server-8.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 26 Feb 2015 15:17:19 -0000 Date: Thu, 26 Feb 2015 16:17:16 +0100 From: Guido Haase MIME-Version: 1.0 To: mirageos-devel@lists.xenproject.org Subject: [MirageOS-devel] 3 newbie question about mirage xen image on cubietruck X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org Hello everybody, first of all I don't know it I'm right here in this list. If not, please excuse me for asking here. I'm running xen 4.4. openmirage image on Cubietruck downloaded from http://blobs.openmirage.org/cubietruck.tar . All things are working fine and I'd like to say a big thank you to the whole developer team! This was my first step into the ARM environment. I'm switching over from INTEL/AMD based x64 systems running debian with OpenVZ kernel. For saving time on my first steps I downloaded and wrote the precompiled cubietruck mirage image (see above) to SDcard only. Having done so and got my first DomUs up and running for a while I'd like to get my Cubietruck with mirage xen image a little bit more comfortable. But, I don't know where I can get the required informations (i.e. which forums, mailinglists, blogs, etc.). Well, common questions are answered but may be my ones are to special. So any hint from you would be greatly appreciated! In detail I'm looking for information about: - making the mirage image not headless, i.e. add VGA and USB keyboard support to it so I can login if ssh access over ethernet isn't possible (a little bit like using a remote insight board at boot stage or later). - switch on some of the LEDs on Cubieboard related to dedicated actions - using OpenXenManager to connect to mirage xen 4.4 on cubietruck. As I read OpenXenManger expects an open TCP port 80 or 443, but netstat -tulpn shows me xen server (dom0) isn't listening on one of this ports. The only ports the system is listening on are ssh (TCP) an few ports where avahi daemon. Again, if I'm wrong in this list please let me know which one(s) may fit better to my needs. Thanks for reading! Greetinx Guido _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Thu Feb 26 15:17:27 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 26 Feb 2015 15:17:27 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YR0Bm-0006AB-8i; Thu, 26 Feb 2015 15:17:22 +0000 Message-Id: Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YR0Bk-0006A3-Vz for mirageos-devel@lists.xenproject.org; Thu, 26 Feb 2015 15:17:21 +0000 Received: from [193.109.254.147] by server-15.bemta-14.messagelabs.com id 8A/40-02770-0093FE45; Thu, 26 Feb 2015 15:17:20 +0000 X-Env-Sender: guweha@web.de X-Msg-Ref: server-8.tower-27.messagelabs.com!1424963838!13137362!1 X-Originating-IP: [217.140.73.121] X-SpamReason: No, hits=2.0 required=7.0 tests=msgid: No Message-ID, received_headers: No Received headers X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21778 invoked from network); 26 Feb 2015 15:17:19 -0000 Received: from mx1.ig-haase.de (HELO mx1.ig-haase.de) (217.140.73.121) by server-8.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 26 Feb 2015 15:17:19 -0000 Date: Thu, 26 Feb 2015 16:17:16 +0100 From: Guido Haase MIME-Version: 1.0 To: mirageos-devel@lists.xenproject.org Subject: [MirageOS-devel] 3 newbie question about mirage xen image on cubietruck X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org Hello everybody, first of all I don't know it I'm right here in this list. If not, please excuse me for asking here. I'm running xen 4.4. openmirage image on Cubietruck downloaded from http://blobs.openmirage.org/cubietruck.tar . All things are working fine and I'd like to say a big thank you to the whole developer team! This was my first step into the ARM environment. I'm switching over from INTEL/AMD based x64 systems running debian with OpenVZ kernel. For saving time on my first steps I downloaded and wrote the precompiled cubietruck mirage image (see above) to SDcard only. Having done so and got my first DomUs up and running for a while I'd like to get my Cubietruck with mirage xen image a little bit more comfortable. But, I don't know where I can get the required informations (i.e. which forums, mailinglists, blogs, etc.). Well, common questions are answered but may be my ones are to special. So any hint from you would be greatly appreciated! In detail I'm looking for information about: - making the mirage image not headless, i.e. add VGA and USB keyboard support to it so I can login if ssh access over ethernet isn't possible (a little bit like using a remote insight board at boot stage or later). - switch on some of the LEDs on Cubieboard related to dedicated actions - using OpenXenManager to connect to mirage xen 4.4 on cubietruck. As I read OpenXenManger expects an open TCP port 80 or 443, but netstat -tulpn shows me xen server (dom0) isn't listening on one of this ports. The only ports the system is listening on are ssh (TCP) an few ports where avahi daemon. Again, if I'm wrong in this list please let me know which one(s) may fit better to my needs. Thanks for reading! Greetinx Guido _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Fri Feb 27 09:55:20 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 27 Feb 2015 09:55:20 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YRHda-0004us-AT; Fri, 27 Feb 2015 09:55:14 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YRHdY-0004ul-KR for mirageos-devel@lists.xenproject.org; Fri, 27 Feb 2015 09:55:13 +0000 Received: from [193.109.254.147] by server-12.bemta-14.messagelabs.com id DC/ED-02755-FFE30F45; Fri, 27 Feb 2015 09:55:11 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-14.tower-27.messagelabs.com!1425030911!13310677!1 X-Originating-IP: [5.153.225.51] X-SpamReason: No, hits=0.2 required=7.0 tests=RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 9944 invoked from network); 27 Feb 2015 09:55:11 -0000 Received: from bark.recoil.org (HELO bark.recoil.org) (5.153.225.51) by server-14.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 27 Feb 2015 09:55:11 -0000 Received: from [10.0.0.94] (host31-48-188-224.range31-48.btcentralplus.com [31.48.188.224]); by bark.recoil.org (OpenSMTPD) with ESMTPSA id 9e026758; TLS version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO; Fri, 27 Feb 2015 09:54:58 +0000 (GMT) Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) From: Anil Madhavapeddy In-Reply-To: Date: Fri, 27 Feb 2015 09:54:44 +0000 Message-Id: References: To: Guido Haase X-Mailer: Apple Mail (2.2070.6) Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] 3 newbie question about mirage xen image on cubietruck X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 26 Feb 2015, at 15:17, Guido Haase wrote: > > Hello everybody, > > first of all I don't know it I'm right here in this list. If not, please > excuse me for asking here. This list is just fine. > > I'm running xen 4.4. openmirage image on Cubietruck downloaded from > > http://blobs.openmirage.org/cubietruck.tar . > > All things are working fine and I'd like to say a big thank you to the > whole developer team! > > This was my first step into the ARM environment. I'm switching over from > INTEL/AMD based x64 systems running debian with OpenVZ kernel. > > For saving time on my first steps I downloaded and wrote the precompiled > cubietruck mirage image (see above) to SDcard only. > > Having done so and got my first DomUs up and running for a while I'd > like to get my Cubietruck with mirage xen image a little bit more > comfortable. But, I don't know where I can get the required informations > (i.e. which forums, mailinglists, blogs, etc.). Well, common questions > are answered but may be my ones are to special. > So any hint from you would be greatly appreciated! As a background to that image, we were one of the first groups to start using Xen/ARM, and so had to build that ARM/Linux image to have a convenient way to share effort with setting up development environments. So although it's not directly related to Mirage, we're happy to continue improving and extending it on these lists. > In detail I'm looking for information about: > > - making the mirage image not headless, i.e. add VGA and USB keyboard > support to it so I can login if ssh access over ethernet isn't > possible (a little bit like using a remote insight board at boot > stage or later). > This one's purely a Linux configuration issue. You'll need to figure out the right kernel modules to drive the GPU and add those to the xen-arm-builder configuration process. I would very much like to see this, but I think that Magnus had a look a few months ago and ran into issues with GPU binary blobs. The situation may have improved since then, so any > - switch on some of the LEDs on Cubieboard related to dedicated actions Again, this one should be the standard Linux Cubie way of doing that. Magnus -- how did you get the LEDs to turn off on kernel boot? (is it CONFIG_LEDS_TRIGGER or some userspace action?) > > - using OpenXenManager to connect to mirage xen 4.4 on cubietruck. > As I read OpenXenManger expects an open TCP port 80 or 443, but > netstat -tulpn shows me xen server (dom0) isn't listening on one > of this ports. The only ports the system is listening on are ssh > (TCP) an few ports where avahi daemon. The latest Cubieboard images include the XenServer management stack, so perhaps Dave can describe how to use the various XAPI management tools to attach to the board. cheers, Anil _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Fri Feb 27 09:55:20 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 27 Feb 2015 09:55:20 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YRHda-0004us-AT; Fri, 27 Feb 2015 09:55:14 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YRHdY-0004ul-KR for mirageos-devel@lists.xenproject.org; Fri, 27 Feb 2015 09:55:13 +0000 Received: from [193.109.254.147] by server-12.bemta-14.messagelabs.com id DC/ED-02755-FFE30F45; Fri, 27 Feb 2015 09:55:11 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-14.tower-27.messagelabs.com!1425030911!13310677!1 X-Originating-IP: [5.153.225.51] X-SpamReason: No, hits=0.2 required=7.0 tests=RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 9944 invoked from network); 27 Feb 2015 09:55:11 -0000 Received: from bark.recoil.org (HELO bark.recoil.org) (5.153.225.51) by server-14.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 27 Feb 2015 09:55:11 -0000 Received: from [10.0.0.94] (host31-48-188-224.range31-48.btcentralplus.com [31.48.188.224]); by bark.recoil.org (OpenSMTPD) with ESMTPSA id 9e026758; TLS version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO; Fri, 27 Feb 2015 09:54:58 +0000 (GMT) Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) From: Anil Madhavapeddy In-Reply-To: Date: Fri, 27 Feb 2015 09:54:44 +0000 Message-Id: References: To: Guido Haase X-Mailer: Apple Mail (2.2070.6) Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] 3 newbie question about mirage xen image on cubietruck X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 26 Feb 2015, at 15:17, Guido Haase wrote: > > Hello everybody, > > first of all I don't know it I'm right here in this list. If not, please > excuse me for asking here. This list is just fine. > > I'm running xen 4.4. openmirage image on Cubietruck downloaded from > > http://blobs.openmirage.org/cubietruck.tar . > > All things are working fine and I'd like to say a big thank you to the > whole developer team! > > This was my first step into the ARM environment. I'm switching over from > INTEL/AMD based x64 systems running debian with OpenVZ kernel. > > For saving time on my first steps I downloaded and wrote the precompiled > cubietruck mirage image (see above) to SDcard only. > > Having done so and got my first DomUs up and running for a while I'd > like to get my Cubietruck with mirage xen image a little bit more > comfortable. But, I don't know where I can get the required informations > (i.e. which forums, mailinglists, blogs, etc.). Well, common questions > are answered but may be my ones are to special. > So any hint from you would be greatly appreciated! As a background to that image, we were one of the first groups to start using Xen/ARM, and so had to build that ARM/Linux image to have a convenient way to share effort with setting up development environments. So although it's not directly related to Mirage, we're happy to continue improving and extending it on these lists. > In detail I'm looking for information about: > > - making the mirage image not headless, i.e. add VGA and USB keyboard > support to it so I can login if ssh access over ethernet isn't > possible (a little bit like using a remote insight board at boot > stage or later). > This one's purely a Linux configuration issue. You'll need to figure out the right kernel modules to drive the GPU and add those to the xen-arm-builder configuration process. I would very much like to see this, but I think that Magnus had a look a few months ago and ran into issues with GPU binary blobs. The situation may have improved since then, so any > - switch on some of the LEDs on Cubieboard related to dedicated actions Again, this one should be the standard Linux Cubie way of doing that. Magnus -- how did you get the LEDs to turn off on kernel boot? (is it CONFIG_LEDS_TRIGGER or some userspace action?) > > - using OpenXenManager to connect to mirage xen 4.4 on cubietruck. > As I read OpenXenManger expects an open TCP port 80 or 443, but > netstat -tulpn shows me xen server (dom0) isn't listening on one > of this ports. The only ports the system is listening on are ssh > (TCP) an few ports where avahi daemon. The latest Cubieboard images include the XenServer management stack, so perhaps Dave can describe how to use the various XAPI management tools to attach to the board. cheers, Anil _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Fri Feb 27 13:20:14 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 27 Feb 2015 13:20:14 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YRKpt-0005km-30; Fri, 27 Feb 2015 13:20:09 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YRKpr-0005ke-Qt for mirageos-devel@lists.xenproject.org; Fri, 27 Feb 2015 13:20:07 +0000 Received: from [193.109.254.147] by server-13.bemta-14.messagelabs.com id 1D/37-02635-70F60F45; Fri, 27 Feb 2015 13:20:07 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-3.tower-27.messagelabs.com!1425043204!13296997!1 X-Originating-IP: [66.165.176.63] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni42MyA9PiAzMDYwNDg=\n, received_headers: No Received headers X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22507 invoked from network); 27 Feb 2015 13:20:06 -0000 Received: from smtp02.citrix.com (HELO SMTP02.CITRIX.COM) (66.165.176.63) by server-3.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 27 Feb 2015 13:20:06 -0000 X-IronPort-AV: E=Sophos;i="5.09,659,1418083200"; d="scan'208";a="239795582" Message-ID: <1425043129.14641.191.camel@citrix.com> From: Ian Campbell To: Stefano Stabellini Date: Fri, 27 Feb 2015 13:18:49 +0000 In-Reply-To: References: <0EEB9201-A222-4EF2-96A2-790FFDB78970@citrix.com> Content-Length: 3174 X-Mailer: Evolution 3.12.9-1+b1 MIME-Version: 1.0 X-DLP: MIA2 Cc: Dave Scott , mirageos-devel , Xen-devel Subject: Re: [MirageOS-devel] [Xen-devel] entropy for VMs X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org T24gTW9uLCAyMDE1LTAyLTAyIGF0IDE3OjQwICswMDAwLCBTdGVmYW5vIFN0YWJlbGxpbmkgd3Jv dGU6Cj4gT24gU3VuLCAxIEZlYiAyMDE1LCBEYXZlIFNjb3R0IHdyb3RlOgo+ID4gSGksCj4gPiAK PiA+IE1pcmFnZSBub3cgaGFzIG5pY2UgZmVhdHVyZXMgbGlrZSBUTFNbMV0gYW5kIHRoZXJlZm9y ZSBuZWVkcyBhIGdvb2Qgc291cmNlIG9mIHJhbmRvbW5lc3MgdG8gZ2VuZXJhdGUgc2Vzc2lvbiBr ZXlzLiBNaXJhZ2UgVk1zIGFyZSBQViwgc28gd2UgY2Fu4oCZdCB1c2UgdmlydGlvLXJuZy4gV2Un dmUgY3JlYXRlZCBhIHByb3RvdHlwZSBlbnRyb3B5IHNlcnZlciB3aGljaCBtYXkgYmUgb2YgaW50 ZXJlc3QgdG8gb3RoZXIgcGVvcGxlIHRvbzoKPiA+IAo+ID4gaHR0cHM6Ly9naXRodWIuY29tL21p cmFnZS94ZW50cm9weWQKPiA+IAo+ID4gVGhpcyBiZWhhdmVzIGEgYml0IGxpa2UgeGVuY29uc29s ZWQ6IGl0IHdhdGNoZXMgZm9yIGRvbWFpbnMgYmVpbmcgY3JlYXRlZCBhbmQgdGhlbiBjb25uZWN0 cyB0byB0aGVtIHZpYSB0aGUgY29uc29sZSBwcm90b2NvbC4gVGhlcmUgaXMgYSBsaXR0bGUgaGFu ZHNoYWtlWzJdICh0byBjYXRjaCBhY2NpZGVudGFsIHNjcmV3dXBzIHdpdGggdGhlIHdyb25nIGNv bnNvbGUpIGFuZCB0aGVuIHRoZSBkYWVtb24gZmVlZHMgcmFuZG9tIGRhdGEgaW50byB0aGUgY29u c29sZSB0aHJvdWdoIGEgcmF0ZS1saW1pdGVyLiBNaXJhZ2XigJlzIGVudHJvcHkgZHJpdmVyIGNh biByZWFkIHRoZSBkYXRhIGZyb20gdGhlIGNvbnNvbGUgZmFpcmx5IGVhc2lseVszXS4gSSBhc3N1 bWUgd2UgY291bGQgd3JpdGUgYSBzaW1pbGFyIHRoaW5nIGZvciBsaW51eCB0b28uCj4gPiAKPiA+ IFdoYXQgZG8geW91IHRoaW5rPyAoQW5kIGRvZXMgYW55b25lIGtub3cgYSBiZXR0ZXIgd2F5IChU TSk/KQo+IAo+IEkgdGhpbmsgaXQgd291bGQgYmUgdmVyeSB1c2VmdWwgaW4gTGludXggdG9vLgoK SSBhZ3JlZS4gT3RoZXIgdGhhbiB2aXJ0aW8tcm5nICh3aGljaCBhcyBEYXZlIG5vdGVzIGlzbid0 IGF2YWlsYWJsZSBmb3IKUFYpIEkgZG9uJ3Qga25vdyBvZiBhbnkgb3RoZXIgc29sdXRpb24sIGxl dCBhbG9uZSBhIGJldHRlciBvbmUuCgpJIGRvbid0IGtub3cgd2hhdCB0aGUgdmlydGlvLXJuZyBw cm90b2NvbCBsb29rcyBsaWtlLCBidXQgQUlVSSBpdCdzCmJhc2VkIG9uIGVpdGhlciB2aXJ0aW8t c2VyaWFsIG9yIHZpcnRpby1jaGFubmVscyAtLSBhcyBzdWNoIEkgd29uZGVyIGlmCnRoZXJlIGlz IHNjb3BlIGZvciBhdCBsZWFzdCB1c2luZyBhIGNvbW1vbiBwcm90b2NvbCAoaS5lLiB0aGUgaGFu ZHNoYWtlCmJpdCkgb3ZlciB0aGUgdHdvIHRyYW5zcG9ydHMuIFRoYXQgbWlnaHQgdGhlbiBhbGxv dyBhIGNvbW1vbiBybmdkIGluIHRoZQpndWVzdCB0byBjb25zdW1lIHRoZSBjaGFubmVsIGFuZCBm ZWVkIGl0IHRvIC9kZXYvcmFuZG9tPwoKSWFuLgoKPiAKPiAKPiAKPiA+IFRoZSBjb2RlIGlzIHN0 aWxsIGEgYml0IG9mIGEgcHJvdG90eXBlLCBhbmQgY29udGFpbnMgc2xpZ2h0bHkgZm9ya2VkIHZl cnNpb25zIG9mIGNvcmUgTWlyYWdlIGxpYnJhcmllcy0tIEkgbmVlZCB0byBzb3J0IHRoYXQgb3V0 IGJlZm9yZSBhIDEuMC4KPiA+IAo+ID4gQ2hlZXJzLAo+ID4gRGF2ZQo+ID4gCj4gPiBbMV0gaHR0 cDovL29wZW5taXJhZ2Uub3JnL2Jsb2cvaW50cm9kdWNpbmctb2NhbWwtdGxzCj4gPiBbMl0gaHR0 cHM6Ly9naXRodWIuY29tL21pcmFnZS94ZW50cm9weWQvYmxvYi9tYXN0ZXIvZG9jL3Byb3RvY29s Lm1kCj4gPiBbM10gaHR0cHM6Ly9naXRodWIuY29tL2RqczU1L21pcmFnZS1lbnRyb3B5L2Jsb2Iv OTgxYjA3MGQ3OGFlNDA3MDE1YjFlOGRlZGIzMTQxYjA1NDU0MzY2Zi94ZW4vZW50cm9weV94ZW4u bWwjTDEzMAo+ID4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X18KPiA+IFhlbi1kZXZlbCBtYWlsaW5nIGxpc3QKPiA+IFhlbi1kZXZlbEBsaXN0cy54ZW4ub3Jn Cj4gPiBodHRwOi8vbGlzdHMueGVuLm9yZy94ZW4tZGV2ZWwKPiA+IAo+IF9fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fIFhlbi1kZXZlbCBtYWlsaW5nIGxpc3Qg WGVuLWRldmVsQGxpc3RzLnhlbi5vcmcgaHR0cDovL2xpc3RzLnhlbi5vcmcveGVuLWRldmVsCgoK Cl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fCk1pcmFnZU9T LWRldmVsIG1haWxpbmcgbGlzdApNaXJhZ2VPUy1kZXZlbEBsaXN0cy54ZW5wcm9qZWN0Lm9yZwpo dHRwOi8vbGlzdHMueGVucHJvamVjdC5vcmcvY2dpLWJpbi9tYWlsbWFuL2xpc3RpbmZvL21pcmFn ZW9zLWRldmVsCg== From mirageos-devel-bounces@lists.xenproject.org Fri Feb 27 13:20:14 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 27 Feb 2015 13:20:14 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YRKpt-0005km-30; Fri, 27 Feb 2015 13:20:09 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YRKpr-0005ke-Qt for mirageos-devel@lists.xenproject.org; Fri, 27 Feb 2015 13:20:07 +0000 Received: from [193.109.254.147] by server-13.bemta-14.messagelabs.com id 1D/37-02635-70F60F45; Fri, 27 Feb 2015 13:20:07 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-3.tower-27.messagelabs.com!1425043204!13296997!1 X-Originating-IP: [66.165.176.63] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni42MyA9PiAzMDYwNDg=\n, received_headers: No Received headers X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22507 invoked from network); 27 Feb 2015 13:20:06 -0000 Received: from smtp02.citrix.com (HELO SMTP02.CITRIX.COM) (66.165.176.63) by server-3.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 27 Feb 2015 13:20:06 -0000 X-IronPort-AV: E=Sophos;i="5.09,659,1418083200"; d="scan'208";a="239795582" Message-ID: <1425043129.14641.191.camel@citrix.com> From: Ian Campbell To: Stefano Stabellini Date: Fri, 27 Feb 2015 13:18:49 +0000 In-Reply-To: References: <0EEB9201-A222-4EF2-96A2-790FFDB78970@citrix.com> Content-Length: 3174 X-Mailer: Evolution 3.12.9-1+b1 MIME-Version: 1.0 X-DLP: MIA2 Cc: Dave Scott , mirageos-devel , Xen-devel Subject: Re: [MirageOS-devel] [Xen-devel] entropy for VMs X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org T24gTW9uLCAyMDE1LTAyLTAyIGF0IDE3OjQwICswMDAwLCBTdGVmYW5vIFN0YWJlbGxpbmkgd3Jv dGU6Cj4gT24gU3VuLCAxIEZlYiAyMDE1LCBEYXZlIFNjb3R0IHdyb3RlOgo+ID4gSGksCj4gPiAK PiA+IE1pcmFnZSBub3cgaGFzIG5pY2UgZmVhdHVyZXMgbGlrZSBUTFNbMV0gYW5kIHRoZXJlZm9y ZSBuZWVkcyBhIGdvb2Qgc291cmNlIG9mIHJhbmRvbW5lc3MgdG8gZ2VuZXJhdGUgc2Vzc2lvbiBr ZXlzLiBNaXJhZ2UgVk1zIGFyZSBQViwgc28gd2UgY2Fu4oCZdCB1c2UgdmlydGlvLXJuZy4gV2Un dmUgY3JlYXRlZCBhIHByb3RvdHlwZSBlbnRyb3B5IHNlcnZlciB3aGljaCBtYXkgYmUgb2YgaW50 ZXJlc3QgdG8gb3RoZXIgcGVvcGxlIHRvbzoKPiA+IAo+ID4gaHR0cHM6Ly9naXRodWIuY29tL21p cmFnZS94ZW50cm9weWQKPiA+IAo+ID4gVGhpcyBiZWhhdmVzIGEgYml0IGxpa2UgeGVuY29uc29s ZWQ6IGl0IHdhdGNoZXMgZm9yIGRvbWFpbnMgYmVpbmcgY3JlYXRlZCBhbmQgdGhlbiBjb25uZWN0 cyB0byB0aGVtIHZpYSB0aGUgY29uc29sZSBwcm90b2NvbC4gVGhlcmUgaXMgYSBsaXR0bGUgaGFu ZHNoYWtlWzJdICh0byBjYXRjaCBhY2NpZGVudGFsIHNjcmV3dXBzIHdpdGggdGhlIHdyb25nIGNv bnNvbGUpIGFuZCB0aGVuIHRoZSBkYWVtb24gZmVlZHMgcmFuZG9tIGRhdGEgaW50byB0aGUgY29u c29sZSB0aHJvdWdoIGEgcmF0ZS1saW1pdGVyLiBNaXJhZ2XigJlzIGVudHJvcHkgZHJpdmVyIGNh biByZWFkIHRoZSBkYXRhIGZyb20gdGhlIGNvbnNvbGUgZmFpcmx5IGVhc2lseVszXS4gSSBhc3N1 bWUgd2UgY291bGQgd3JpdGUgYSBzaW1pbGFyIHRoaW5nIGZvciBsaW51eCB0b28uCj4gPiAKPiA+ IFdoYXQgZG8geW91IHRoaW5rPyAoQW5kIGRvZXMgYW55b25lIGtub3cgYSBiZXR0ZXIgd2F5IChU TSk/KQo+IAo+IEkgdGhpbmsgaXQgd291bGQgYmUgdmVyeSB1c2VmdWwgaW4gTGludXggdG9vLgoK SSBhZ3JlZS4gT3RoZXIgdGhhbiB2aXJ0aW8tcm5nICh3aGljaCBhcyBEYXZlIG5vdGVzIGlzbid0 IGF2YWlsYWJsZSBmb3IKUFYpIEkgZG9uJ3Qga25vdyBvZiBhbnkgb3RoZXIgc29sdXRpb24sIGxl dCBhbG9uZSBhIGJldHRlciBvbmUuCgpJIGRvbid0IGtub3cgd2hhdCB0aGUgdmlydGlvLXJuZyBw cm90b2NvbCBsb29rcyBsaWtlLCBidXQgQUlVSSBpdCdzCmJhc2VkIG9uIGVpdGhlciB2aXJ0aW8t c2VyaWFsIG9yIHZpcnRpby1jaGFubmVscyAtLSBhcyBzdWNoIEkgd29uZGVyIGlmCnRoZXJlIGlz IHNjb3BlIGZvciBhdCBsZWFzdCB1c2luZyBhIGNvbW1vbiBwcm90b2NvbCAoaS5lLiB0aGUgaGFu ZHNoYWtlCmJpdCkgb3ZlciB0aGUgdHdvIHRyYW5zcG9ydHMuIFRoYXQgbWlnaHQgdGhlbiBhbGxv dyBhIGNvbW1vbiBybmdkIGluIHRoZQpndWVzdCB0byBjb25zdW1lIHRoZSBjaGFubmVsIGFuZCBm ZWVkIGl0IHRvIC9kZXYvcmFuZG9tPwoKSWFuLgoKPiAKPiAKPiAKPiA+IFRoZSBjb2RlIGlzIHN0 aWxsIGEgYml0IG9mIGEgcHJvdG90eXBlLCBhbmQgY29udGFpbnMgc2xpZ2h0bHkgZm9ya2VkIHZl cnNpb25zIG9mIGNvcmUgTWlyYWdlIGxpYnJhcmllcy0tIEkgbmVlZCB0byBzb3J0IHRoYXQgb3V0 IGJlZm9yZSBhIDEuMC4KPiA+IAo+ID4gQ2hlZXJzLAo+ID4gRGF2ZQo+ID4gCj4gPiBbMV0gaHR0 cDovL29wZW5taXJhZ2Uub3JnL2Jsb2cvaW50cm9kdWNpbmctb2NhbWwtdGxzCj4gPiBbMl0gaHR0 cHM6Ly9naXRodWIuY29tL21pcmFnZS94ZW50cm9weWQvYmxvYi9tYXN0ZXIvZG9jL3Byb3RvY29s Lm1kCj4gPiBbM10gaHR0cHM6Ly9naXRodWIuY29tL2RqczU1L21pcmFnZS1lbnRyb3B5L2Jsb2Iv OTgxYjA3MGQ3OGFlNDA3MDE1YjFlOGRlZGIzMTQxYjA1NDU0MzY2Zi94ZW4vZW50cm9weV94ZW4u bWwjTDEzMAo+ID4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X18KPiA+IFhlbi1kZXZlbCBtYWlsaW5nIGxpc3QKPiA+IFhlbi1kZXZlbEBsaXN0cy54ZW4ub3Jn Cj4gPiBodHRwOi8vbGlzdHMueGVuLm9yZy94ZW4tZGV2ZWwKPiA+IAo+IF9fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fIFhlbi1kZXZlbCBtYWlsaW5nIGxpc3Qg WGVuLWRldmVsQGxpc3RzLnhlbi5vcmcgaHR0cDovL2xpc3RzLnhlbi5vcmcveGVuLWRldmVsCgoK Cl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fCk1pcmFnZU9T LWRldmVsIG1haWxpbmcgbGlzdApNaXJhZ2VPUy1kZXZlbEBsaXN0cy54ZW5wcm9qZWN0Lm9yZwpo dHRwOi8vbGlzdHMueGVucHJvamVjdC5vcmcvY2dpLWJpbi9tYWlsbWFuL2xpc3RpbmZvL21pcmFn ZW9zLWRldmVsCg== From mirageos-devel-bounces@lists.xenproject.org Sat Feb 28 14:19:26 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sat, 28 Feb 2015 14:19:26 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YRiEe-0005xL-TN; Sat, 28 Feb 2015 14:19:16 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YRiEd-0005xG-FF for mirageos-devel@lists.xenproject.org; Sat, 28 Feb 2015 14:19:15 +0000 Received: from [85.158.139.211] by server-1.bemta-5.messagelabs.com id 48/C1-25903-26EC1F45; Sat, 28 Feb 2015 14:19:14 +0000 X-Env-Sender: trevorsummerssmith@gmail.com X-Msg-Ref: server-5.tower-206.messagelabs.com!1425133152!12008121!1 X-Originating-IP: [209.85.216.169] X-SpamReason: No, hits=0.9 required=7.0 tests=HTML_20_30,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23078 invoked from network); 28 Feb 2015 14:19:13 -0000 Received: from mail-qc0-f169.google.com (HELO mail-qc0-f169.google.com) (209.85.216.169) by server-5.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 28 Feb 2015 14:19:13 -0000 Received: by qcyl6 with SMTP id l6so18386525qcy.2 for ; Sat, 28 Feb 2015 06:19:12 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type; bh=d3oRXudanBRXm+MXhkpcJeNNydi+ZT8NG0OSSDHShis=; b=QbLAJNHnWf5tdzw8nMmYWd7AHG7aKv9YxrSMzu8vlJX/OSKy9H5PEycMA2rYFNRvQc RqDLBByJYJ/P0xbJ9BdJuYqh5+6oYJJw9dMoSVBVupZ93yQIdjAAKKf9DGHabi3nfrhD h8IZEPu/AFep2rXmh+RtfUEM1YnYJZ5oebgQg0bnL/dOwxL1L2s1/Cvf2rvU5OvxoMwj JC7uhoZLmkUdOmhCO9nkXo3rhoMqDfCs6PRDrBKhV5a1xGu0sc3LAWsBW0KyT+ZS6aT3 P3i/ru8s7Yhj5QAGb+pKiNvlbVyDkfIpWJJcpZ/ySJz5U7gzJBhvF+0qs6rWXad+wYSb 01/Q== X-Received: by 10.140.232.6 with SMTP id d6mr37253339qhc.99.1425133151960; Sat, 28 Feb 2015 06:19:11 -0800 (PST) MIME-Version: 1.0 From: Trevor Smith Date: Sat, 28 Feb 2015 14:19:11 +0000 Message-ID: To: mirageos-devel@lists.xenproject.org Subject: [MirageOS-devel] ocaml-cohttp, async and https X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============7018351735520933614==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============7018351735520933614== Content-Type: multipart/alternative; boundary=001a1135432447dbc5051026ab82 --001a1135432447dbc5051026ab82 Content-Type: text/plain; charset=UTF-8 Hello, I am not sure if this is the right mailing list for this. I am looking to use ocaml cohttp with async and https in a production setting. I could not find any examples online that demonstrate this. Could someone please point me to some examples? I am happy to contribute my findings back into the ocaml-cohttp codebase as an example. I have read Thomas' excellent post ( http://roscidus.com/blog/blog/2015/01/21/securing-the-unikernel/) however I cannot use the HTTPSY because I need to integrate with .NET services and they do not appear to support that. Furthermore, I would like to use the non-ocaml-native tls implementation for the time being. Thoughts? Thank you. Trevor --001a1135432447dbc5051026ab82 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hello,

I am not sure if this is the rig= ht mailing list for this.

I am looking to use ocam= l cohttp with async and https in a production setting. I could not find any= examples online that demonstrate this. Could someone please point me to so= me examples? I am happy to contribute my findings back into the ocaml-cohtt= p codebase as an example.

I have read Thomas' = excellent post (http://roscidus.com/blog/blog/2015/01/21/securing-the-uni= kernel/) however I cannot use the HTTPSY because I need to integrate wi= th .NET services and they do not appear to support that. Furthermore, I wou= ld like to use the non-ocaml-native tls implementation for the time being.<= /div>

Thoughts? Thank you.

Trev= or
--001a1135432447dbc5051026ab82-- --===============7018351735520933614== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --===============7018351735520933614==-- From mirageos-devel-bounces@lists.xenproject.org Sat Feb 28 14:19:26 2015 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sat, 28 Feb 2015 14:19:26 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YRiEe-0005xL-TN; Sat, 28 Feb 2015 14:19:16 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YRiEd-0005xG-FF for mirageos-devel@lists.xenproject.org; Sat, 28 Feb 2015 14:19:15 +0000 Received: from [85.158.139.211] by server-1.bemta-5.messagelabs.com id 48/C1-25903-26EC1F45; Sat, 28 Feb 2015 14:19:14 +0000 X-Env-Sender: trevorsummerssmith@gmail.com X-Msg-Ref: server-5.tower-206.messagelabs.com!1425133152!12008121!1 X-Originating-IP: [209.85.216.169] X-SpamReason: No, hits=0.9 required=7.0 tests=HTML_20_30,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.13.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23078 invoked from network); 28 Feb 2015 14:19:13 -0000 Received: from mail-qc0-f169.google.com (HELO mail-qc0-f169.google.com) (209.85.216.169) by server-5.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 28 Feb 2015 14:19:13 -0000 Received: by qcyl6 with SMTP id l6so18386525qcy.2 for ; Sat, 28 Feb 2015 06:19:12 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type; bh=d3oRXudanBRXm+MXhkpcJeNNydi+ZT8NG0OSSDHShis=; b=QbLAJNHnWf5tdzw8nMmYWd7AHG7aKv9YxrSMzu8vlJX/OSKy9H5PEycMA2rYFNRvQc RqDLBByJYJ/P0xbJ9BdJuYqh5+6oYJJw9dMoSVBVupZ93yQIdjAAKKf9DGHabi3nfrhD h8IZEPu/AFep2rXmh+RtfUEM1YnYJZ5oebgQg0bnL/dOwxL1L2s1/Cvf2rvU5OvxoMwj JC7uhoZLmkUdOmhCO9nkXo3rhoMqDfCs6PRDrBKhV5a1xGu0sc3LAWsBW0KyT+ZS6aT3 P3i/ru8s7Yhj5QAGb+pKiNvlbVyDkfIpWJJcpZ/ySJz5U7gzJBhvF+0qs6rWXad+wYSb 01/Q== X-Received: by 10.140.232.6 with SMTP id d6mr37253339qhc.99.1425133151960; Sat, 28 Feb 2015 06:19:11 -0800 (PST) MIME-Version: 1.0 From: Trevor Smith Date: Sat, 28 Feb 2015 14:19:11 +0000 Message-ID: To: mirageos-devel@lists.xenproject.org Subject: [MirageOS-devel] ocaml-cohttp, async and https X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============7018351735520933614==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============7018351735520933614== Content-Type: multipart/alternative; boundary=001a1135432447dbc5051026ab82 --001a1135432447dbc5051026ab82 Content-Type: text/plain; charset=UTF-8 Hello, I am not sure if this is the right mailing list for this. I am looking to use ocaml cohttp with async and https in a production setting. I could not find any examples online that demonstrate this. Could someone please point me to some examples? I am happy to contribute my findings back into the ocaml-cohttp codebase as an example. I have read Thomas' excellent post ( http://roscidus.com/blog/blog/2015/01/21/securing-the-unikernel/) however I cannot use the HTTPSY because I need to integrate with .NET services and they do not appear to support that. Furthermore, I would like to use the non-ocaml-native tls implementation for the time being. Thoughts? Thank you. Trevor --001a1135432447dbc5051026ab82 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hello,

I am not sure if this is the rig= ht mailing list for this.

I am looking to use ocam= l cohttp with async and https in a production setting. I could not find any= examples online that demonstrate this. Could someone please point me to so= me examples? I am happy to contribute my findings back into the ocaml-cohtt= p codebase as an example.

I have read Thomas' = excellent post (http://roscidus.com/blog/blog/2015/01/21/securing-the-uni= kernel/) however I cannot use the HTTPSY because I need to integrate wi= th .NET services and they do not appear to support that. Furthermore, I wou= ld like to use the non-ocaml-native tls implementation for the time being.<= /div>

Thoughts? Thank you.

Trev= or
--001a1135432447dbc5051026ab82-- --===============7018351735520933614== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --===============7018351735520933614==--