From mirageos-devel-bounces@lists.xenproject.org Mon Jun 02 10:22:36 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 02 Jun 2014 10:22: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 1WrPNt-0002rS-Ug; Mon, 02 Jun 2014 10:22:29 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WrPNr-0002qm-PZ; Mon, 02 Jun 2014 10:22:27 +0000 Received: from [85.158.143.35:45792] by server-3.bemta-4.messagelabs.com id D0/9F-13602-1605C835; Mon, 02 Jun 2014 10:22:25 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-7.tower-21.messagelabs.com!1401704545!8641103!1 X-Originating-IP: [209.85.212.172] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17177 invoked from network); 2 Jun 2014 10:22:25 -0000 Received: from mail-wi0-f172.google.com (HELO mail-wi0-f172.google.com) (209.85.212.172) by server-7.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 2 Jun 2014 10:22:25 -0000 Received: by mail-wi0-f172.google.com with SMTP id hi2so4229523wib.11 for ; Mon, 02 Jun 2014 03:22:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:reply-to:user-agent:mime-version:to :subject:content-type:content-transfer-encoding; bh=mAZfg+BtQYxjhPbDeo93EOBLc+ELlagNpA4Z7rbCgl0=; b=z3RZixMXgCFDEz4o4zcwfHVuK1Y4mAGWyCcWe0NhlkUY9D8qqb6XohuAbUuaj+NrLV uIRKTUYSz6gPhhAh+2L1ZxBsKhUqY7OatL1Rq0Qn9RLJCKL01m5ZYE8a6H0hKY5bKrdc Lw2AKltpcKMayhq9nu3OZnYJRkXRBKWkgiFEX7PK++gYNK9aqUZ8YqMBspjb/Fkd4nZk B5MIqAwQFg97zi3S908hzIYx2danyglXOzmg28hs5BK+ivPJxLFQTGJ2NP1wxEOGetFm 4pfcEibUML1krL7iSiM9oeTIOlgIbJURTuGX+52jU38M17SkUNUWDiIuN8Vf9XaEquB0 dTRg== X-Received: by 10.180.87.165 with SMTP id az5mr21265494wib.10.1401704545036; Mon, 02 Jun 2014 03:22:25 -0700 (PDT) Received: from [172.16.25.10] (97e5a5cd.skybroadband.com. [151.229.165.205]) by mx.google.com with ESMTPSA id p15sm31343200wiv.8.2014.06.02.03.22.23 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 02 Jun 2014 03:22:24 -0700 (PDT) Message-ID: <538C505F.4050107@xen.org> Date: Mon, 02 Jun 2014 11:22:23 +0100 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: "publicity@lists.xenproject.org" , "xen-devel@lists.xen.org" , "xen-api@lists.xen.org" , "mirageos-devel@lists.xenproject.org" Subject: [MirageOS-devel] Hackathon Follow-up @ Please post session notes on the list (and send me picture) X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: lars.kurth@xen.org 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 all, I trust the remainder of the Hackathon went well and I hope the evening event was fun. I have to apologize again for having to leave on Thursday night and hope I didn't give the flu I am still battling with to anyone. May I ask you to post session notes on the mailing list labelling them [Hackathon] or add them to the wiki and post a link to the lists labelled [Hackathon] , such that others can participate off-line. I still have a few posts I need to make myself. They will follow shortly. Also, if you took photos, please send them to me. And of course I am looking for a volunteer to write up an event report. 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 Jun 02 10:22:36 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 02 Jun 2014 10:22: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 1WrPNt-0002rS-Ug; Mon, 02 Jun 2014 10:22:29 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WrPNr-0002qm-PZ; Mon, 02 Jun 2014 10:22:27 +0000 Received: from [85.158.143.35:45792] by server-3.bemta-4.messagelabs.com id D0/9F-13602-1605C835; Mon, 02 Jun 2014 10:22:25 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-7.tower-21.messagelabs.com!1401704545!8641103!1 X-Originating-IP: [209.85.212.172] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17177 invoked from network); 2 Jun 2014 10:22:25 -0000 Received: from mail-wi0-f172.google.com (HELO mail-wi0-f172.google.com) (209.85.212.172) by server-7.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 2 Jun 2014 10:22:25 -0000 Received: by mail-wi0-f172.google.com with SMTP id hi2so4229523wib.11 for ; Mon, 02 Jun 2014 03:22:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:reply-to:user-agent:mime-version:to :subject:content-type:content-transfer-encoding; bh=mAZfg+BtQYxjhPbDeo93EOBLc+ELlagNpA4Z7rbCgl0=; b=z3RZixMXgCFDEz4o4zcwfHVuK1Y4mAGWyCcWe0NhlkUY9D8qqb6XohuAbUuaj+NrLV uIRKTUYSz6gPhhAh+2L1ZxBsKhUqY7OatL1Rq0Qn9RLJCKL01m5ZYE8a6H0hKY5bKrdc Lw2AKltpcKMayhq9nu3OZnYJRkXRBKWkgiFEX7PK++gYNK9aqUZ8YqMBspjb/Fkd4nZk B5MIqAwQFg97zi3S908hzIYx2danyglXOzmg28hs5BK+ivPJxLFQTGJ2NP1wxEOGetFm 4pfcEibUML1krL7iSiM9oeTIOlgIbJURTuGX+52jU38M17SkUNUWDiIuN8Vf9XaEquB0 dTRg== X-Received: by 10.180.87.165 with SMTP id az5mr21265494wib.10.1401704545036; Mon, 02 Jun 2014 03:22:25 -0700 (PDT) Received: from [172.16.25.10] (97e5a5cd.skybroadband.com. [151.229.165.205]) by mx.google.com with ESMTPSA id p15sm31343200wiv.8.2014.06.02.03.22.23 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 02 Jun 2014 03:22:24 -0700 (PDT) Message-ID: <538C505F.4050107@xen.org> Date: Mon, 02 Jun 2014 11:22:23 +0100 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: "publicity@lists.xenproject.org" , "xen-devel@lists.xen.org" , "xen-api@lists.xen.org" , "mirageos-devel@lists.xenproject.org" Subject: [MirageOS-devel] Hackathon Follow-up @ Please post session notes on the list (and send me picture) X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: lars.kurth@xen.org 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 all, I trust the remainder of the Hackathon went well and I hope the evening event was fun. I have to apologize again for having to leave on Thursday night and hope I didn't give the flu I am still battling with to anyone. May I ask you to post session notes on the mailing list labelling them [Hackathon] or add them to the wiki and post a link to the lists labelled [Hackathon] , such that others can participate off-line. I still have a few posts I need to make myself. They will follow shortly. Also, if you took photos, please send them to me. And of course I am looking for a volunteer to write up an event report. 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 Jun 02 16:02:47 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 02 Jun 2014 16:02: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 1WrUh8-00006h-Km; Mon, 02 Jun 2014 16:02:42 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WrUh6-00006V-E1 for mirageos-devel@lists.xenproject.org; Mon, 02 Jun 2014 16:02:40 +0000 Received: from [193.109.254.147:58401] by server-6.bemta-14.messagelabs.com id B5/5A-13066-F10AC835; Mon, 02 Jun 2014 16:02:39 +0000 X-Env-Sender: mindy@somerandomidiot.com X-Msg-Ref: server-4.tower-27.messagelabs.com!1401724959!8611034!1 X-Originating-IP: [217.70.183.198] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25281 invoked from network); 2 Jun 2014 16:02:39 -0000 Received: from relay6-d.mail.gandi.net (HELO relay6-d.mail.gandi.net) (217.70.183.198) by server-4.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 2 Jun 2014 16:02:39 -0000 Received: from mfilter30-d.gandi.net (mfilter30-d.gandi.net [217.70.178.161]) by relay6-d.mail.gandi.net (Postfix) with ESMTP id EFD98FB8CC for ; Mon, 2 Jun 2014 18:02:38 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at mfilter30-d.gandi.net Received: from relay6-d.mail.gandi.net ([217.70.183.198]) by mfilter30-d.gandi.net (mfilter30-d.gandi.net [10.0.15.180]) (amavisd-new, port 10024) with ESMTP id amzSLAqITv9J for ; Mon, 2 Jun 2014 18:00:58 +0200 (CEST) X-Originating-IP: 66.188.116.94 Received: from [192.168.1.103] (66-188-116-94.static.ftbg.wi.charter.com [66.188.116.94]) (Authenticated sender: guybrush@somerandomidiot.com) by relay6-d.mail.gandi.net (Postfix) with ESMTPSA id 0CB9EFB887 for ; Mon, 2 Jun 2014 18:00:57 +0200 (CEST) Message-ID: <538C9FB9.7070001@somerandomidiot.com> Date: Mon, 02 Jun 2014 11:00:57 -0500 From: Mindy User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: mirageos-devel@lists.xenproject.org References: <537A1EAD.5090906@somerandomidiot.com> In-Reply-To: <537A1EAD.5090906@somerandomidiot.com> Subject: Re: [MirageOS-devel] OPW intern checking in! X-BeenThere: mirageos-devel@lists.xenproject.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, folks! Here's a quick summary of what I've been up to Late last week: dug more into observed lack of FINs from listening unikernels, found the problem, and submitted a pull request to mirage-tcpip Today: make blog post on looking into that readable by humans who wish not to be bored to death; finish unit test for upstream error reporting in a `test_net_lwt` module in lib_test; send PR for error condition unit tests to Cohttp upstream; fuzz harder! _______________________________________________ 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 Jun 02 16:02:47 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 02 Jun 2014 16:02: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 1WrUh8-00006h-Km; Mon, 02 Jun 2014 16:02:42 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WrUh6-00006V-E1 for mirageos-devel@lists.xenproject.org; Mon, 02 Jun 2014 16:02:40 +0000 Received: from [193.109.254.147:58401] by server-6.bemta-14.messagelabs.com id B5/5A-13066-F10AC835; Mon, 02 Jun 2014 16:02:39 +0000 X-Env-Sender: mindy@somerandomidiot.com X-Msg-Ref: server-4.tower-27.messagelabs.com!1401724959!8611034!1 X-Originating-IP: [217.70.183.198] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25281 invoked from network); 2 Jun 2014 16:02:39 -0000 Received: from relay6-d.mail.gandi.net (HELO relay6-d.mail.gandi.net) (217.70.183.198) by server-4.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 2 Jun 2014 16:02:39 -0000 Received: from mfilter30-d.gandi.net (mfilter30-d.gandi.net [217.70.178.161]) by relay6-d.mail.gandi.net (Postfix) with ESMTP id EFD98FB8CC for ; Mon, 2 Jun 2014 18:02:38 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at mfilter30-d.gandi.net Received: from relay6-d.mail.gandi.net ([217.70.183.198]) by mfilter30-d.gandi.net (mfilter30-d.gandi.net [10.0.15.180]) (amavisd-new, port 10024) with ESMTP id amzSLAqITv9J for ; Mon, 2 Jun 2014 18:00:58 +0200 (CEST) X-Originating-IP: 66.188.116.94 Received: from [192.168.1.103] (66-188-116-94.static.ftbg.wi.charter.com [66.188.116.94]) (Authenticated sender: guybrush@somerandomidiot.com) by relay6-d.mail.gandi.net (Postfix) with ESMTPSA id 0CB9EFB887 for ; Mon, 2 Jun 2014 18:00:57 +0200 (CEST) Message-ID: <538C9FB9.7070001@somerandomidiot.com> Date: Mon, 02 Jun 2014 11:00:57 -0500 From: Mindy User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: mirageos-devel@lists.xenproject.org References: <537A1EAD.5090906@somerandomidiot.com> In-Reply-To: <537A1EAD.5090906@somerandomidiot.com> Subject: Re: [MirageOS-devel] OPW intern checking in! X-BeenThere: mirageos-devel@lists.xenproject.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, folks! Here's a quick summary of what I've been up to Late last week: dug more into observed lack of FINs from listening unikernels, found the problem, and submitted a pull request to mirage-tcpip Today: make blog post on looking into that readable by humans who wish not to be bored to death; finish unit test for upstream error reporting in a `test_net_lwt` module in lib_test; send PR for error condition unit tests to Cohttp upstream; fuzz harder! _______________________________________________ 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 Jun 02 16:23:08 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 02 Jun 2014 16:23: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 1WrV0t-0002PN-M9; Mon, 02 Jun 2014 16:23:07 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WrV0r-0002Oo-Oy for mirageos-devel@lists.xenproject.org; Mon, 02 Jun 2014 16:23:05 +0000 Received: from [193.109.254.147:3189] by server-12.bemta-14.messagelabs.com id FA/8B-27473-9E4AC835; Mon, 02 Jun 2014 16:23:05 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-3.tower-27.messagelabs.com!1401726184!8543058!1 X-Originating-IP: [74.125.82.52] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8573 invoked from network); 2 Jun 2014 16:23:04 -0000 Received: from mail-wg0-f52.google.com (HELO mail-wg0-f52.google.com) (74.125.82.52) by server-3.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 2 Jun 2014 16:23:04 -0000 Received: by mail-wg0-f52.google.com with SMTP id l18so5326747wgh.11 for ; Mon, 02 Jun 2014 09:23:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:reply-to:user-agent:mime-version:to :subject:content-type:content-transfer-encoding; bh=9ibQr2KcvTZkXDRgXOYNKGRxVC+OJ9n5ZapRY53ETmA=; b=DG9FfgSB2h56xOPGL5joxGJurKfBsuR4REdqYVGEG1kmRnJU9bjGy6SB4jHgKAquZC 97WUcTVnx8Sju+tLx5pN6LdUr4Dq92FMZQYwc0Sn+hIOgEnR9/ugYwJYeYsYi126dvts TZaZovHJM/NteJEdj2uOc5n17U5qdjvSHOZJxJtHNCMnkyQoB3Mk0wUpcrBY2jlq9fEz exN862ocZRV/saDpX34SlIhG1p8TiKXr6Gd/jiy9a43+PNh0rw+GgAFe67MB2Ixb+TO1 bsv/O96wVSzcxpiIiUF54/7B5A6EX+RFkj/ereYtuJpV44JjgwfmWWjePrYyUQRhrtLG tUZw== X-Received: by 10.194.242.66 with SMTP id wo2mr51240054wjc.37.1401726182957; Mon, 02 Jun 2014 09:23:02 -0700 (PDT) Received: from [172.16.25.10] (97e5a5cd.skybroadband.com. [151.229.165.205]) by mx.google.com with ESMTPSA id qq5sm33798326wic.10.2014.06.02.09.23.01 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 02 Jun 2014 09:23:02 -0700 (PDT) Message-ID: <538CA4E3.40506@xen.org> Date: Mon, 02 Jun 2014 17:22:59 +0100 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: "xen-devel@lists.xen.org" , "xen-api@lists.xen.org" , "mirageos-devel@lists.xenproject.org" Subject: [MirageOS-devel] Xen Project Developer Meeting on August 20th AM in Chicago - please include into travel plans X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: lars.kurth@xen.org 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 all, I am pleased to announce that I secured space for a 1/2 day developer meeting the day after the Xen Project Developer Summit. As in the past, I suggest that the meeting lasts 3.5 - 4 hours. I suggest we start at 9:30 and run until 1pm, but could start a little bit later. If you have any preferences, let me know. As I will need to get a sense re numbers and order food and drinks, please reply to the thread for now, if you are planning to attend the meeting. Once I have more information, I will create a wiki page, and you can sign up on the wiki page. We will also have an Advisory Board meeting either before or after. Best 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 Jun 02 16:23:08 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 02 Jun 2014 16:23: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 1WrV0t-0002PN-M9; Mon, 02 Jun 2014 16:23:07 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WrV0r-0002Oo-Oy for mirageos-devel@lists.xenproject.org; Mon, 02 Jun 2014 16:23:05 +0000 Received: from [193.109.254.147:3189] by server-12.bemta-14.messagelabs.com id FA/8B-27473-9E4AC835; Mon, 02 Jun 2014 16:23:05 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-3.tower-27.messagelabs.com!1401726184!8543058!1 X-Originating-IP: [74.125.82.52] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8573 invoked from network); 2 Jun 2014 16:23:04 -0000 Received: from mail-wg0-f52.google.com (HELO mail-wg0-f52.google.com) (74.125.82.52) by server-3.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 2 Jun 2014 16:23:04 -0000 Received: by mail-wg0-f52.google.com with SMTP id l18so5326747wgh.11 for ; Mon, 02 Jun 2014 09:23:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:reply-to:user-agent:mime-version:to :subject:content-type:content-transfer-encoding; bh=9ibQr2KcvTZkXDRgXOYNKGRxVC+OJ9n5ZapRY53ETmA=; b=DG9FfgSB2h56xOPGL5joxGJurKfBsuR4REdqYVGEG1kmRnJU9bjGy6SB4jHgKAquZC 97WUcTVnx8Sju+tLx5pN6LdUr4Dq92FMZQYwc0Sn+hIOgEnR9/ugYwJYeYsYi126dvts TZaZovHJM/NteJEdj2uOc5n17U5qdjvSHOZJxJtHNCMnkyQoB3Mk0wUpcrBY2jlq9fEz exN862ocZRV/saDpX34SlIhG1p8TiKXr6Gd/jiy9a43+PNh0rw+GgAFe67MB2Ixb+TO1 bsv/O96wVSzcxpiIiUF54/7B5A6EX+RFkj/ereYtuJpV44JjgwfmWWjePrYyUQRhrtLG tUZw== X-Received: by 10.194.242.66 with SMTP id wo2mr51240054wjc.37.1401726182957; Mon, 02 Jun 2014 09:23:02 -0700 (PDT) Received: from [172.16.25.10] (97e5a5cd.skybroadband.com. [151.229.165.205]) by mx.google.com with ESMTPSA id qq5sm33798326wic.10.2014.06.02.09.23.01 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 02 Jun 2014 09:23:02 -0700 (PDT) Message-ID: <538CA4E3.40506@xen.org> Date: Mon, 02 Jun 2014 17:22:59 +0100 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: "xen-devel@lists.xen.org" , "xen-api@lists.xen.org" , "mirageos-devel@lists.xenproject.org" Subject: [MirageOS-devel] Xen Project Developer Meeting on August 20th AM in Chicago - please include into travel plans X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: lars.kurth@xen.org 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 all, I am pleased to announce that I secured space for a 1/2 day developer meeting the day after the Xen Project Developer Summit. As in the past, I suggest that the meeting lasts 3.5 - 4 hours. I suggest we start at 9:30 and run until 1pm, but could start a little bit later. If you have any preferences, let me know. As I will need to get a sense re numbers and order food and drinks, please reply to the thread for now, if you are planning to attend the meeting. Once I have more information, I will create a wiki page, and you can sign up on the wiki page. We will also have an Advisory Board meeting either before or after. Best 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 Jun 02 20:35:53 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 02 Jun 2014 20:35: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 1WrYxO-0004yg-HK; Mon, 02 Jun 2014 20:35:46 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WrYxN-0004yZ-2J for mirageos-devel@lists.xenproject.org; Mon, 02 Jun 2014 20:35:45 +0000 Received: from [85.158.143.35:20447] by server-1.bemta-4.messagelabs.com id 7D/61-09853-020EC835; Mon, 02 Jun 2014 20:35:44 +0000 X-Env-Sender: Richard.Mortier@nottingham.ac.uk X-Msg-Ref: server-13.tower-21.messagelabs.com!1401741343!1461263!1 X-Originating-IP: [93.159.202.52] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30672 invoked from network); 2 Jun 2014 20:35:43 -0000 Received: from engine03-20433-8.icritical.com (HELO engine03-20433-8.icritical.com) (93.159.202.52) by server-13.tower-21.messagelabs.com with SMTP; 2 Jun 2014 20:35:43 -0000 Received: (qmail 28315 invoked from network); 2 Jun 2014 20:35:53 -0000 Received: from localhost (127.0.0.1) by engine03-20433-8.icritical.com with SMTP; 2 Jun 2014 20:35:53 -0000 Received: from engine03-20433-8.icritical.com ([127.0.0.1]) by localhost (engine03-20433-8.icritical.com [127.0.0.1]) (amavisd-new, port 10024) with SMTP id 27931-05 for ; Mon, 2 Jun 2014 21:35:46 +0100 (BST) Received: (qmail 28292 invoked by uid 599); 2 Jun 2014 20:35:46 -0000 Received: from unknown (HELO smtp3.nottingham.ac.uk) (128.243.44.55) by engine03-20433-8.icritical.com (qpsmtpd/0.28) with ESMTP; Mon, 02 Jun 2014 21:35:46 +0100 Received: from uiwexhub01.ad.nottingham.ac.uk ([128.243.15.133]) by smtp3.nottingham.ac.uk with esmtps (TLSv1:AES128-SHA:128) (Exim 4.77) (envelope-from ) id 1WrYxD-0000Eb-05; Mon, 02 Jun 2014 21:35:35 +0100 From: Richard Mortier To: Mindy Date: Mon, 2 Jun 2014 21:35:34 +0100 Thread-Topic: [MirageOS-devel] OPW intern checking in! Thread-Index: Ac9+ojRlxtKlzNZhS7qGL8YTTVqfMg== Message-ID: References: <537A1EAD.5090906@somerandomidiot.com> <538C9FB9.7070001@somerandomidiot.com> In-Reply-To: <538C9FB9.7070001@somerandomidiot.com> Accept-Language: en-US, en-GB Content-Language: en-US X-MS-Has-Attach: yes X-MS-TNEF-Correlator: acceptlanguage: en-US, en-GB MIME-Version: 1.0 X-Virus-Scanned: by iCritical at engine03-20433-8.icritical.com Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] OPW intern checking in! X-BeenThere: mirageos-devel@lists.xenproject.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="===============3792462640894675940==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============3792462640894675940== Content-Language: en-US Content-Type: multipart/signed; boundary="Apple-Mail=_755637EE-51AB-49EB-BD50-2B544005AC19"; protocol="application/pgp-signature"; micalg=pgp-sha512 --Apple-Mail=_755637EE-51AB-49EB-BD50-2B544005AC19 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On 2 Jun 2014, at 17:00, Mindy wrote: > Hi, folks! Here's a quick summary of what I've been up to >=20 > Late last week: dug more into observed lack of FINs from listening=20 > unikernels, found the problem, and submitted a pull request to = mirage-tcpip > Today: make blog post on looking into that readable by humans who wish=20= > not to be bored to death; read it, looks good :) > finish unit test for upstream error reporting=20 > in a `test_net_lwt` module in lib_test; send PR for error condition = unit=20 > tests to Cohttp upstream; fuzz harder! fuzzfuzzfuzz! :) btw, to respond to one of your comments that i noticed after a quick = glance through the dhcp fuzzer-- RFC951 (BOOTP, precursor to DHCP) = states "For simplicity it is assumed that the BOOTP packet is never = fragmented". i can't see mention of fragmentation in RFC2131 (DHCP = itself), though there is an internet draft i found that seeks to define = an application layer fragmentation process for DHCP.=20 it doesn't appear to be actually forbidden though -- given that DHCP is = in the process of configuring the stack anyway, i could well imagine = this is a corner case that isn't particularly well defined or = consistently (or well) handled... --=20 Cheers, R. --Apple-Mail=_755637EE-51AB-49EB-BD50-2B544005AC19 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="signature.asc" Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJTjOAXAAoJEOLF27JWwSg3dDIQAICfVd1FXmUK2HJKrDAvX2PU L4EoGNdv4ZwyuBC5Ja05VU68Paj82ANUNhyj/EnvUURIS4Jpz2lvgFMKig47So1R z2X7re7TH8Vl+F1W+qoisBG28A2CgEecfXX9eDfGnVa4eo2zwnZOwitw1Kn4luPo 083hDOVcu/n9V94lzXVuL1pTFOBtYSA5criPF940pRk3TGQrqy3gvaBELhw9yAMz AAV6lNPGwbQjOgk/JGBKwmLeNKcD61/W44r8YTtaM7sjcKZz7UyekYs6IQqIx8ra fDoz9/Zp6gouAttk1ww2X5VHG0OL9+KMUg7tYAZRTkzVQD3oZKGNf6mMIdRv8c5K skkqOR0a7ZDf7IyHWV2mf0JMMbRYlAYvTh8LzrFNdFNllRFgJaFrH9Dv3JWnkx0c OToDM9LWGXwyyq1GfEUNPozugyw+s/4k+XCisbYUBKM0XxhyVm5aHE+GRpPx5JDU 84cFoB4zGOPc7TG/t0oF5cmcofpAEEEOPsoaxUniFakJUj3usWAU7h/bi+ySIgdp tsYwMTvNvrxh0id6rI1VKt0YVnjb2yvmQx/NIwbLo61w09fa3EZ8L3EEAZBGD08b N799jCSCFd8nRuyit+37nFW7WpkOnmNG9IaRLek2f7gq/miOVEkmvibaGACYfoE0 92rk3jfgSbQNRbj/7dX8 =9OQh -----END PGP SIGNATURE----- --Apple-Mail=_755637EE-51AB-49EB-BD50-2B544005AC19-- --===============3792462640894675940== 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 --===============3792462640894675940==-- From mirageos-devel-bounces@lists.xenproject.org Mon Jun 02 20:35:53 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 02 Jun 2014 20:35: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 1WrYxO-0004yg-HK; Mon, 02 Jun 2014 20:35:46 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WrYxN-0004yZ-2J for mirageos-devel@lists.xenproject.org; Mon, 02 Jun 2014 20:35:45 +0000 Received: from [85.158.143.35:20447] by server-1.bemta-4.messagelabs.com id 7D/61-09853-020EC835; Mon, 02 Jun 2014 20:35:44 +0000 X-Env-Sender: Richard.Mortier@nottingham.ac.uk X-Msg-Ref: server-13.tower-21.messagelabs.com!1401741343!1461263!1 X-Originating-IP: [93.159.202.52] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30672 invoked from network); 2 Jun 2014 20:35:43 -0000 Received: from engine03-20433-8.icritical.com (HELO engine03-20433-8.icritical.com) (93.159.202.52) by server-13.tower-21.messagelabs.com with SMTP; 2 Jun 2014 20:35:43 -0000 Received: (qmail 28315 invoked from network); 2 Jun 2014 20:35:53 -0000 Received: from localhost (127.0.0.1) by engine03-20433-8.icritical.com with SMTP; 2 Jun 2014 20:35:53 -0000 Received: from engine03-20433-8.icritical.com ([127.0.0.1]) by localhost (engine03-20433-8.icritical.com [127.0.0.1]) (amavisd-new, port 10024) with SMTP id 27931-05 for ; Mon, 2 Jun 2014 21:35:46 +0100 (BST) Received: (qmail 28292 invoked by uid 599); 2 Jun 2014 20:35:46 -0000 Received: from unknown (HELO smtp3.nottingham.ac.uk) (128.243.44.55) by engine03-20433-8.icritical.com (qpsmtpd/0.28) with ESMTP; Mon, 02 Jun 2014 21:35:46 +0100 Received: from uiwexhub01.ad.nottingham.ac.uk ([128.243.15.133]) by smtp3.nottingham.ac.uk with esmtps (TLSv1:AES128-SHA:128) (Exim 4.77) (envelope-from ) id 1WrYxD-0000Eb-05; Mon, 02 Jun 2014 21:35:35 +0100 From: Richard Mortier To: Mindy Date: Mon, 2 Jun 2014 21:35:34 +0100 Thread-Topic: [MirageOS-devel] OPW intern checking in! Thread-Index: Ac9+ojRlxtKlzNZhS7qGL8YTTVqfMg== Message-ID: References: <537A1EAD.5090906@somerandomidiot.com> <538C9FB9.7070001@somerandomidiot.com> In-Reply-To: <538C9FB9.7070001@somerandomidiot.com> Accept-Language: en-US, en-GB Content-Language: en-US X-MS-Has-Attach: yes X-MS-TNEF-Correlator: acceptlanguage: en-US, en-GB MIME-Version: 1.0 X-Virus-Scanned: by iCritical at engine03-20433-8.icritical.com Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] OPW intern checking in! X-BeenThere: mirageos-devel@lists.xenproject.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="===============3792462640894675940==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============3792462640894675940== Content-Language: en-US Content-Type: multipart/signed; boundary="Apple-Mail=_755637EE-51AB-49EB-BD50-2B544005AC19"; protocol="application/pgp-signature"; micalg=pgp-sha512 --Apple-Mail=_755637EE-51AB-49EB-BD50-2B544005AC19 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On 2 Jun 2014, at 17:00, Mindy wrote: > Hi, folks! Here's a quick summary of what I've been up to >=20 > Late last week: dug more into observed lack of FINs from listening=20 > unikernels, found the problem, and submitted a pull request to = mirage-tcpip > Today: make blog post on looking into that readable by humans who wish=20= > not to be bored to death; read it, looks good :) > finish unit test for upstream error reporting=20 > in a `test_net_lwt` module in lib_test; send PR for error condition = unit=20 > tests to Cohttp upstream; fuzz harder! fuzzfuzzfuzz! :) btw, to respond to one of your comments that i noticed after a quick = glance through the dhcp fuzzer-- RFC951 (BOOTP, precursor to DHCP) = states "For simplicity it is assumed that the BOOTP packet is never = fragmented". i can't see mention of fragmentation in RFC2131 (DHCP = itself), though there is an internet draft i found that seeks to define = an application layer fragmentation process for DHCP.=20 it doesn't appear to be actually forbidden though -- given that DHCP is = in the process of configuring the stack anyway, i could well imagine = this is a corner case that isn't particularly well defined or = consistently (or well) handled... --=20 Cheers, R. --Apple-Mail=_755637EE-51AB-49EB-BD50-2B544005AC19 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="signature.asc" Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJTjOAXAAoJEOLF27JWwSg3dDIQAICfVd1FXmUK2HJKrDAvX2PU L4EoGNdv4ZwyuBC5Ja05VU68Paj82ANUNhyj/EnvUURIS4Jpz2lvgFMKig47So1R z2X7re7TH8Vl+F1W+qoisBG28A2CgEecfXX9eDfGnVa4eo2zwnZOwitw1Kn4luPo 083hDOVcu/n9V94lzXVuL1pTFOBtYSA5criPF940pRk3TGQrqy3gvaBELhw9yAMz AAV6lNPGwbQjOgk/JGBKwmLeNKcD61/W44r8YTtaM7sjcKZz7UyekYs6IQqIx8ra fDoz9/Zp6gouAttk1ww2X5VHG0OL9+KMUg7tYAZRTkzVQD3oZKGNf6mMIdRv8c5K skkqOR0a7ZDf7IyHWV2mf0JMMbRYlAYvTh8LzrFNdFNllRFgJaFrH9Dv3JWnkx0c OToDM9LWGXwyyq1GfEUNPozugyw+s/4k+XCisbYUBKM0XxhyVm5aHE+GRpPx5JDU 84cFoB4zGOPc7TG/t0oF5cmcofpAEEEOPsoaxUniFakJUj3usWAU7h/bi+ySIgdp tsYwMTvNvrxh0id6rI1VKt0YVnjb2yvmQx/NIwbLo61w09fa3EZ8L3EEAZBGD08b N799jCSCFd8nRuyit+37nFW7WpkOnmNG9IaRLek2f7gq/miOVEkmvibaGACYfoE0 92rk3jfgSbQNRbj/7dX8 =9OQh -----END PGP SIGNATURE----- --Apple-Mail=_755637EE-51AB-49EB-BD50-2B544005AC19-- --===============3792462640894675940== 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 --===============3792462640894675940==-- From mirageos-devel-bounces@lists.xenproject.org Tue Jun 03 10:00:41 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 03 Jun 2014 10:00: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 1WrlWF-0003ch-UK; Tue, 03 Jun 2014 10:00:35 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WrlWE-0003c4-0H for mirageos-devel@lists.xenproject.org; Tue, 03 Jun 2014 10:00:34 +0000 Received: from [193.109.254.147:51069] by server-10.bemta-14.messagelabs.com id 1D/67-04546-1CC9D835; Tue, 03 Jun 2014 10:00:33 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-3.tower-27.messagelabs.com!1401789632!8698819!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.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 18425 invoked from network); 3 Jun 2014 10:00:32 -0000 Received: from mail-lb0-f182.google.com (HELO mail-lb0-f182.google.com) (209.85.217.182) by server-3.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 3 Jun 2014 10:00:32 -0000 Received: by mail-lb0-f182.google.com with SMTP id z11so3330715lbi.27 for ; Tue, 03 Jun 2014 03:00:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:reply-to:user-agent:mime-version:to:cc :subject:content-type:content-transfer-encoding; bh=PzXk46oqn6N/znqR7I0kq69q3TMFzkybKC00dHeO16M=; b=ZT+YQYreJjbxXZpapAO+7wexoboe+Q6JvO4fl/EO0R283UbNAjDDDPsZ1MqdslwGHI 3S8JZJi/Pe92If9FUF6MGtRcMBf+jtNdAMqIdcVpjybKbxE2f7nRxJTH9p8PIpX6WuPU aYYwLK3P/ATffVPUBv0G6FiJ5ilBDpWwQKZvoC04o0rDEbfr9MjPNmPoxKUVGEfyoGJv zCb1VDJ/0MK70SZNOfava/7oGatI1X5AoEJFnxJtJWDYWK6PrIaVbPNoSCePUQmUuX2f elrzHfSUpXxFcna8RHUG1P6+iv5rShkHTRd09u2vuqyo1Y90uahG2I/KQdB+d4lj+ZDD U/yg== X-Received: by 10.112.40.101 with SMTP id w5mr31405685lbk.19.1401789631617; Tue, 03 Jun 2014 03:00:31 -0700 (PDT) Received: from [172.16.25.10] (97e5a5cd.skybroadband.com. [151.229.165.205]) by mx.google.com with ESMTPSA id i10sm15565760lbc.16.2014.06.03.03.00.29 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 03 Jun 2014 03:00:30 -0700 (PDT) Message-ID: <538D9CBC.2040100@xen.org> Date: Tue, 03 Jun 2014 11:00:28 +0100 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: "xen-devel@lists.xen.org" , "mirageos-devel@lists.xenproject.org" Cc: Marc Zyngier , michail.flouris@onapp.com, Srinivas Kalaga Subject: [MirageOS-devel] [Hackathon] Xen/arm session notes X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: lars.kurth@xen.org 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 Thanks to Stefano and Anil for writing these up. Please add to it as needed, as these are a little sparese. Added people who are likely off list Regards == Attendees == anil madhavapeddy (cambridge) thomas leonard (cambridge) anthony perrard (citrix) srinivas kalaga (samsung) - primarily on xen and power management filipe manco (nec) - adding support for suspend/resume in MiniOS joao martins (nec) - clickos/minios interested in pvh tim deegan (x86 and arm maintainer, has hacked on minios) michail flouris (onapp) - working on arm-pv 32 port of xen for server market hwanju kim (cambridge) - minios for pvh x86, also building netfpga device driver for xen nik sultana (cambridge) - network function virtualization ian jackson (citrix) - tools maintainer for minios. working with rump kernel stefano stabellini (citrix) - arm maintainer dave scott (citrix) - xenserver and mirage arm jon ludlam (citrix) - cubieboard interested hanger on julian chesterfield (onapp) - minios in the board euroserver project (http://www.euroserver-project.eu/) marc zyngier (arm) == Outline of discussions == - patch review of arm code (marc) - libc choices - newlib (clickos) - libm - libm choices - suspend/resume patches - mirage - pvh === Anil's Notes === MiniOS enables MMU and does 1:1 mapping. ARM guests are allowed to assume one bank of memory. We need to document this in the ABI. ARM guests should assume the presence of an FDT. How do we make MiniOS more modular? We could make start_kernel tweak. Should we move it to a separate tree? To encourage collaboration, add KVM support to Mirage?, and make it more generic. Libc choices: newlib has to go away. * Bionic from Android, too complex * libc from FreeBSD is good, but there is no easy way to build it out of the FreeBSD tree * uclibc is LGPL so it cannot be used * musl libc seems to be the best option * Could we upstream MiniOS support into musl libc or newlib? A prerequisite would be MiniOS providing a stable API. We also need a libm. OpenBSD libm has been moved out of tree to a separate project, called openlibm. _______________________________________________ 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 Jun 03 10:00:41 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 03 Jun 2014 10:00: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 1WrlWF-0003ch-UK; Tue, 03 Jun 2014 10:00:35 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WrlWE-0003c4-0H for mirageos-devel@lists.xenproject.org; Tue, 03 Jun 2014 10:00:34 +0000 Received: from [193.109.254.147:51069] by server-10.bemta-14.messagelabs.com id 1D/67-04546-1CC9D835; Tue, 03 Jun 2014 10:00:33 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-3.tower-27.messagelabs.com!1401789632!8698819!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.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 18425 invoked from network); 3 Jun 2014 10:00:32 -0000 Received: from mail-lb0-f182.google.com (HELO mail-lb0-f182.google.com) (209.85.217.182) by server-3.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 3 Jun 2014 10:00:32 -0000 Received: by mail-lb0-f182.google.com with SMTP id z11so3330715lbi.27 for ; Tue, 03 Jun 2014 03:00:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:reply-to:user-agent:mime-version:to:cc :subject:content-type:content-transfer-encoding; bh=PzXk46oqn6N/znqR7I0kq69q3TMFzkybKC00dHeO16M=; b=ZT+YQYreJjbxXZpapAO+7wexoboe+Q6JvO4fl/EO0R283UbNAjDDDPsZ1MqdslwGHI 3S8JZJi/Pe92If9FUF6MGtRcMBf+jtNdAMqIdcVpjybKbxE2f7nRxJTH9p8PIpX6WuPU aYYwLK3P/ATffVPUBv0G6FiJ5ilBDpWwQKZvoC04o0rDEbfr9MjPNmPoxKUVGEfyoGJv zCb1VDJ/0MK70SZNOfava/7oGatI1X5AoEJFnxJtJWDYWK6PrIaVbPNoSCePUQmUuX2f elrzHfSUpXxFcna8RHUG1P6+iv5rShkHTRd09u2vuqyo1Y90uahG2I/KQdB+d4lj+ZDD U/yg== X-Received: by 10.112.40.101 with SMTP id w5mr31405685lbk.19.1401789631617; Tue, 03 Jun 2014 03:00:31 -0700 (PDT) Received: from [172.16.25.10] (97e5a5cd.skybroadband.com. [151.229.165.205]) by mx.google.com with ESMTPSA id i10sm15565760lbc.16.2014.06.03.03.00.29 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 03 Jun 2014 03:00:30 -0700 (PDT) Message-ID: <538D9CBC.2040100@xen.org> Date: Tue, 03 Jun 2014 11:00:28 +0100 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: "xen-devel@lists.xen.org" , "mirageos-devel@lists.xenproject.org" Cc: Marc Zyngier , michail.flouris@onapp.com, Srinivas Kalaga Subject: [MirageOS-devel] [Hackathon] Xen/arm session notes X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: lars.kurth@xen.org 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 Thanks to Stefano and Anil for writing these up. Please add to it as needed, as these are a little sparese. Added people who are likely off list Regards == Attendees == anil madhavapeddy (cambridge) thomas leonard (cambridge) anthony perrard (citrix) srinivas kalaga (samsung) - primarily on xen and power management filipe manco (nec) - adding support for suspend/resume in MiniOS joao martins (nec) - clickos/minios interested in pvh tim deegan (x86 and arm maintainer, has hacked on minios) michail flouris (onapp) - working on arm-pv 32 port of xen for server market hwanju kim (cambridge) - minios for pvh x86, also building netfpga device driver for xen nik sultana (cambridge) - network function virtualization ian jackson (citrix) - tools maintainer for minios. working with rump kernel stefano stabellini (citrix) - arm maintainer dave scott (citrix) - xenserver and mirage arm jon ludlam (citrix) - cubieboard interested hanger on julian chesterfield (onapp) - minios in the board euroserver project (http://www.euroserver-project.eu/) marc zyngier (arm) == Outline of discussions == - patch review of arm code (marc) - libc choices - newlib (clickos) - libm - libm choices - suspend/resume patches - mirage - pvh === Anil's Notes === MiniOS enables MMU and does 1:1 mapping. ARM guests are allowed to assume one bank of memory. We need to document this in the ABI. ARM guests should assume the presence of an FDT. How do we make MiniOS more modular? We could make start_kernel tweak. Should we move it to a separate tree? To encourage collaboration, add KVM support to Mirage?, and make it more generic. Libc choices: newlib has to go away. * Bionic from Android, too complex * libc from FreeBSD is good, but there is no easy way to build it out of the FreeBSD tree * uclibc is LGPL so it cannot be used * musl libc seems to be the best option * Could we upstream MiniOS support into musl libc or newlib? A prerequisite would be MiniOS providing a stable API. We also need a libm. OpenBSD libm has been moved out of tree to a separate project, called openlibm. _______________________________________________ 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 Jun 03 10:35:15 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 03 Jun 2014 10:35: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 1Wrm3m-0005VL-7h; Tue, 03 Jun 2014 10:35:14 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Wrm3l-0005Uk-Do; Tue, 03 Jun 2014 10:35:13 +0000 Received: from [193.109.254.147:41953] by server-4.bemta-14.messagelabs.com id 3B/76-02781-0E4AD835; Tue, 03 Jun 2014 10:35:12 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-16.tower-27.messagelabs.com!1401791711!3383002!1 X-Originating-IP: [74.125.82.51] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5588 invoked from network); 3 Jun 2014 10:35:12 -0000 Received: from mail-wg0-f51.google.com (HELO mail-wg0-f51.google.com) (74.125.82.51) by server-16.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 3 Jun 2014 10:35:12 -0000 Received: by mail-wg0-f51.google.com with SMTP id x13so6537963wgg.22 for ; Tue, 03 Jun 2014 03:35:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:reply-to:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=JhNMwg8KNU3SKalOE5EsoLhaEOHm6DhslKFNtV7Hpns=; b=qT4EqjNMLoVY70N88/LO76wJva5D59cCEPjcv+viOxcXv3mbz/i1THqxYOyCxX5PXK 8mLyDSax3O6pZX12TZe6w9XCZi53n83sHffrtxb0sMF/Meb9sxAoyHrmTdmBWjeoMMfo wTNnpBGSLYnYz5z+/qWASLilckfr4bK4R/tjg5w2Q+kbsx+nZ+eOKza5dYseiFDF6QcO AnbL1ZUCT71UExNkWvHAC7IMDenJFwk8JZgGzX+Y672xj3wGZjcjuJFgXi779I5+p1O1 wxJCig0IcgTH+Up+RsrHMsGGvLZqHPbubvftJrW0Drvv+vAHj8HpMtKN1cwvNLJrZRcB NS4Q== X-Received: by 10.194.91.144 with SMTP id ce16mr59102293wjb.18.1401791709380; Tue, 03 Jun 2014 03:35:09 -0700 (PDT) Received: from [172.16.25.10] (97e5a5cd.skybroadband.com. [151.229.165.205]) by mx.google.com with ESMTPSA id bj2sm1783291wib.3.2014.06.03.03.35.07 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 03 Jun 2014 03:35:08 -0700 (PDT) Message-ID: <538DA4DB.8050906@xen.org> Date: Tue, 03 Jun 2014 11:35:07 +0100 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: "publicity@lists.xenproject.org" , "xen-devel@lists.xen.org" , "xen-api@lists.xen.org" , "mirageos-devel@lists.xenproject.org" References: <538C505F.4050107@xen.org> In-Reply-To: <538C505F.4050107@xen.org> Subject: Re: [MirageOS-devel] Hackathon Follow-up @ Please post session notes on the list (and send me picture) X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: lars.kurth@xen.org 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 all, I started posting links to minutes on http://wiki.xen.org/wiki/Hackathon#May_2014_.5BHackathon_Minutes.5D, such that they are all in one place Lars On 02/06/2014 11:22, Lars Kurth wrote: > Hi all, > > I trust the remainder of the Hackathon went well and I hope the > evening event was fun. I have to apologize again for having to leave > on Thursday night and hope I didn't give the flu I am still battling > with to anyone. > > May I ask you to post session notes on the mailing list labelling them > [Hackathon] or add them to the wiki and post a link to the lists > labelled [Hackathon] , such that others can participate off-line. I > still have a few posts I need to make myself. They will follow shortly. > > Also, if you took photos, please send them to me. > > And of course I am looking for a volunteer to write up an event report. > > 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 Tue Jun 03 10:35:15 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 03 Jun 2014 10:35: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 1Wrm3m-0005VL-7h; Tue, 03 Jun 2014 10:35:14 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Wrm3l-0005Uk-Do; Tue, 03 Jun 2014 10:35:13 +0000 Received: from [193.109.254.147:41953] by server-4.bemta-14.messagelabs.com id 3B/76-02781-0E4AD835; Tue, 03 Jun 2014 10:35:12 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-16.tower-27.messagelabs.com!1401791711!3383002!1 X-Originating-IP: [74.125.82.51] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5588 invoked from network); 3 Jun 2014 10:35:12 -0000 Received: from mail-wg0-f51.google.com (HELO mail-wg0-f51.google.com) (74.125.82.51) by server-16.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 3 Jun 2014 10:35:12 -0000 Received: by mail-wg0-f51.google.com with SMTP id x13so6537963wgg.22 for ; Tue, 03 Jun 2014 03:35:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:reply-to:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=JhNMwg8KNU3SKalOE5EsoLhaEOHm6DhslKFNtV7Hpns=; b=qT4EqjNMLoVY70N88/LO76wJva5D59cCEPjcv+viOxcXv3mbz/i1THqxYOyCxX5PXK 8mLyDSax3O6pZX12TZe6w9XCZi53n83sHffrtxb0sMF/Meb9sxAoyHrmTdmBWjeoMMfo wTNnpBGSLYnYz5z+/qWASLilckfr4bK4R/tjg5w2Q+kbsx+nZ+eOKza5dYseiFDF6QcO AnbL1ZUCT71UExNkWvHAC7IMDenJFwk8JZgGzX+Y672xj3wGZjcjuJFgXi779I5+p1O1 wxJCig0IcgTH+Up+RsrHMsGGvLZqHPbubvftJrW0Drvv+vAHj8HpMtKN1cwvNLJrZRcB NS4Q== X-Received: by 10.194.91.144 with SMTP id ce16mr59102293wjb.18.1401791709380; Tue, 03 Jun 2014 03:35:09 -0700 (PDT) Received: from [172.16.25.10] (97e5a5cd.skybroadband.com. [151.229.165.205]) by mx.google.com with ESMTPSA id bj2sm1783291wib.3.2014.06.03.03.35.07 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 03 Jun 2014 03:35:08 -0700 (PDT) Message-ID: <538DA4DB.8050906@xen.org> Date: Tue, 03 Jun 2014 11:35:07 +0100 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: "publicity@lists.xenproject.org" , "xen-devel@lists.xen.org" , "xen-api@lists.xen.org" , "mirageos-devel@lists.xenproject.org" References: <538C505F.4050107@xen.org> In-Reply-To: <538C505F.4050107@xen.org> Subject: Re: [MirageOS-devel] Hackathon Follow-up @ Please post session notes on the list (and send me picture) X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: lars.kurth@xen.org 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 all, I started posting links to minutes on http://wiki.xen.org/wiki/Hackathon#May_2014_.5BHackathon_Minutes.5D, such that they are all in one place Lars On 02/06/2014 11:22, Lars Kurth wrote: > Hi all, > > I trust the remainder of the Hackathon went well and I hope the > evening event was fun. I have to apologize again for having to leave > on Thursday night and hope I didn't give the flu I am still battling > with to anyone. > > May I ask you to post session notes on the mailing list labelling them > [Hackathon] or add them to the wiki and post a link to the lists > labelled [Hackathon] , such that others can participate off-line. I > still have a few posts I need to make myself. They will follow shortly. > > Also, if you took photos, please send them to me. > > And of course I am looking for a volunteer to write up an event report. > > 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 Tue Jun 03 14:29:14 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 03 Jun 2014 14:29: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 1Wrpi9-0003lk-DP; Tue, 03 Jun 2014 14:29:09 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Wrpi7-0003l1-T3 for mirageos-devel@lists.xenproject.org; Tue, 03 Jun 2014 14:29:08 +0000 Received: from [85.158.139.211:55334] by server-12.bemta-5.messagelabs.com id B4/87-03824-3BBDD835; Tue, 03 Jun 2014 14:29:07 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-7.tower-206.messagelabs.com!1401805746!7878563!1 X-Originating-IP: [74.125.82.48] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_32, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3843 invoked from network); 3 Jun 2014 14:29:06 -0000 Received: from mail-wg0-f48.google.com (HELO mail-wg0-f48.google.com) (74.125.82.48) by server-7.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 3 Jun 2014 14:29:06 -0000 Received: by mail-wg0-f48.google.com with SMTP id k14so6897604wgh.7 for ; Tue, 03 Jun 2014 07:29:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:reply-to:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=KvykFIQUVwDKjVZ58bSGIwicbzdMIHbRS3pV8JFmxOU=; b=uHEtrvEVF+KOryLTacD3LzrnHvN1sPzqJ+DQb1K8DRm32vsjrYCuaiUJhytXJBJL2H 0GwA+cUelXIYmR/tlarsCrOzLlYrcHhpV0QXd+5Ss9o9T9FP/3jU71PWJGnsXXM9ssrw Q3UGEtprlfk27c6TvMwrpnJT7ZPeEg0408zLzqnaf1QBZiX+D+7kNQFbq5vqWSF3c43D hZ5Qol3yKYpHtfdpau5LsvOvALjAhlUJM6QSdyuMnpdJKaVtG2FO2CzGXzQOYUC5y7z5 Z+BkK7d7SlqF3Lbn/1bfsUtSKshjWl8a2RoPBGKfv5dhY2u2DFtO7v37/V/wPJjWN37p xrKQ== X-Received: by 10.180.78.71 with SMTP id z7mr33850985wiw.14.1401805745816; Tue, 03 Jun 2014 07:29:05 -0700 (PDT) Received: from [172.16.25.10] (97e5a5cd.skybroadband.com. [151.229.165.205]) by mx.google.com with ESMTPSA id jr1sm44375559wjc.13.2014.06.03.07.29.04 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 03 Jun 2014 07:29:04 -0700 (PDT) Message-ID: <538DDBAF.70606@xen.org> Date: Tue, 03 Jun 2014 15:29:03 +0100 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: Anil Madhavapeddy References: <53739980.5050703@eu.citrix.com> <53746EF9.3000409@eu.citrix.com> <5374818E.4020904@xen.org> <3588D698-4B41-460F-8118-039EDD356983@recoil.org> <537606C3.3000606@xen.org> In-Reply-To: <537606C3.3000606@xen.org> Cc: "xen-devel@lists.xen.org" , "mirageos-devel@lists.xenproject.org" , "xen-api@lists.xen.org" Subject: Re: [MirageOS-devel] [Need input] Proposal to change committers for the XAPI Project - implications for the whole project? X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: lars.kurth@xen.org 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 No feedback = No concerns. So this matter can be laid to rest Lars On 16/05/2014 13:38, Lars Kurth wrote: > On 15/05/2014 10:19, Anil Madhavapeddy wrote: >> On 15 May 2014, at 09:57, Lars Kurth wrote: >> >>> All the existing committers have voted in favour. So the proposal >>> carries. I will update the XAPI webpage >>> http://www.xenproject.org/developers/teams/xapi.html accordingly >>> Lars >>> >> This isn't intended to affect the voting, but I would note that it's >> slightly odd for an open-source project to switch its committers in >> such a big sweep without at least some discussion about how this >> affects the overall project direction. > Actually, thinking about it *could* affect the direction of the > project for anything that is related to global votes. And we *do* need > to have a discussion about it. And we *may* need a process change or > clarification, but I don't think so as the process was originally > designed to cover a gradual increase in the number of subprojects. > > Thanks Anil for pointing this out. I was too overloaded to really spot > this : Apologies. > > == Different Expectations when to award maintainer status == > First there is the observation in that: > * There are significant differences when it comes to when (aka under > which criteria) committer status is awarded between subprojects and > there are also difference in view within subprojects > * XAPI does not have the maintainer role as far as I understand. In > other words in XAPI maintainer=committer. Please correct me if I am > wrong. > > == Process implications == > Looking at the governance process: > http://www.xenproject.org/governance.html > > Maintainers and committers have the right to vote in some > circumstances. Now we have local (within subproject) and global votes > (affecting all projects). What the process states specifically when it > comes to voting is: > > * The role of committers in electing other committers and project > leads - this is subproject local. As such, a significant change in the > number of committers only has a local effect. > > * The role of maintainers (but not committers) is mentioned > specifically when it comes to "formal votes" such as changes to > governance (global) and other local votes. No mention of committers. > In other words, all maintainers vote in "formal votes". > > * Looking at the voting related to the project lify cycle: These are > just "formal votes" which are allowed by maintainers > > * Committers are specifically mentioned as "referees" in case there > are conflicts. There we have a hierarchy of conflict resolution and > the proposed xhange to XAPI committers should not affect > > == What is the impact of this change (IMPORTANT) == > > As such, the change proposed to XAPI committers is affecting the > voting dynamics for global votes as on the face of it it increases the > number of maintainers (=committers) from 5 to 13. Given the size of > XAPI subproject and the fact that it basically never listed its > maintainers this seems reasonable. Also in light of the number of > maintainers in the Hypervisor project, of which there are 28 if I > counted correctly. > > But it does raise the question as to whether such a significant change > to maintainers sets a bad precedence and whether we need to look at > our process > > So I would argue that, *this ptoposal has* a global impact - even > though unintended - and that for this reason we need to have a > discussion and maybe a formal vote to ratify this proposed change by > the XAPI project. > > Best 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 Tue Jun 03 14:29:14 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 03 Jun 2014 14:29: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 1Wrpi9-0003lk-DP; Tue, 03 Jun 2014 14:29:09 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Wrpi7-0003l1-T3 for mirageos-devel@lists.xenproject.org; Tue, 03 Jun 2014 14:29:08 +0000 Received: from [85.158.139.211:55334] by server-12.bemta-5.messagelabs.com id B4/87-03824-3BBDD835; Tue, 03 Jun 2014 14:29:07 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-7.tower-206.messagelabs.com!1401805746!7878563!1 X-Originating-IP: [74.125.82.48] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_32, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3843 invoked from network); 3 Jun 2014 14:29:06 -0000 Received: from mail-wg0-f48.google.com (HELO mail-wg0-f48.google.com) (74.125.82.48) by server-7.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 3 Jun 2014 14:29:06 -0000 Received: by mail-wg0-f48.google.com with SMTP id k14so6897604wgh.7 for ; Tue, 03 Jun 2014 07:29:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:reply-to:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=KvykFIQUVwDKjVZ58bSGIwicbzdMIHbRS3pV8JFmxOU=; b=uHEtrvEVF+KOryLTacD3LzrnHvN1sPzqJ+DQb1K8DRm32vsjrYCuaiUJhytXJBJL2H 0GwA+cUelXIYmR/tlarsCrOzLlYrcHhpV0QXd+5Ss9o9T9FP/3jU71PWJGnsXXM9ssrw Q3UGEtprlfk27c6TvMwrpnJT7ZPeEg0408zLzqnaf1QBZiX+D+7kNQFbq5vqWSF3c43D hZ5Qol3yKYpHtfdpau5LsvOvALjAhlUJM6QSdyuMnpdJKaVtG2FO2CzGXzQOYUC5y7z5 Z+BkK7d7SlqF3Lbn/1bfsUtSKshjWl8a2RoPBGKfv5dhY2u2DFtO7v37/V/wPJjWN37p xrKQ== X-Received: by 10.180.78.71 with SMTP id z7mr33850985wiw.14.1401805745816; Tue, 03 Jun 2014 07:29:05 -0700 (PDT) Received: from [172.16.25.10] (97e5a5cd.skybroadband.com. [151.229.165.205]) by mx.google.com with ESMTPSA id jr1sm44375559wjc.13.2014.06.03.07.29.04 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 03 Jun 2014 07:29:04 -0700 (PDT) Message-ID: <538DDBAF.70606@xen.org> Date: Tue, 03 Jun 2014 15:29:03 +0100 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: Anil Madhavapeddy References: <53739980.5050703@eu.citrix.com> <53746EF9.3000409@eu.citrix.com> <5374818E.4020904@xen.org> <3588D698-4B41-460F-8118-039EDD356983@recoil.org> <537606C3.3000606@xen.org> In-Reply-To: <537606C3.3000606@xen.org> Cc: "xen-devel@lists.xen.org" , "mirageos-devel@lists.xenproject.org" , "xen-api@lists.xen.org" Subject: Re: [MirageOS-devel] [Need input] Proposal to change committers for the XAPI Project - implications for the whole project? X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: lars.kurth@xen.org 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 No feedback = No concerns. So this matter can be laid to rest Lars On 16/05/2014 13:38, Lars Kurth wrote: > On 15/05/2014 10:19, Anil Madhavapeddy wrote: >> On 15 May 2014, at 09:57, Lars Kurth wrote: >> >>> All the existing committers have voted in favour. So the proposal >>> carries. I will update the XAPI webpage >>> http://www.xenproject.org/developers/teams/xapi.html accordingly >>> Lars >>> >> This isn't intended to affect the voting, but I would note that it's >> slightly odd for an open-source project to switch its committers in >> such a big sweep without at least some discussion about how this >> affects the overall project direction. > Actually, thinking about it *could* affect the direction of the > project for anything that is related to global votes. And we *do* need > to have a discussion about it. And we *may* need a process change or > clarification, but I don't think so as the process was originally > designed to cover a gradual increase in the number of subprojects. > > Thanks Anil for pointing this out. I was too overloaded to really spot > this : Apologies. > > == Different Expectations when to award maintainer status == > First there is the observation in that: > * There are significant differences when it comes to when (aka under > which criteria) committer status is awarded between subprojects and > there are also difference in view within subprojects > * XAPI does not have the maintainer role as far as I understand. In > other words in XAPI maintainer=committer. Please correct me if I am > wrong. > > == Process implications == > Looking at the governance process: > http://www.xenproject.org/governance.html > > Maintainers and committers have the right to vote in some > circumstances. Now we have local (within subproject) and global votes > (affecting all projects). What the process states specifically when it > comes to voting is: > > * The role of committers in electing other committers and project > leads - this is subproject local. As such, a significant change in the > number of committers only has a local effect. > > * The role of maintainers (but not committers) is mentioned > specifically when it comes to "formal votes" such as changes to > governance (global) and other local votes. No mention of committers. > In other words, all maintainers vote in "formal votes". > > * Looking at the voting related to the project lify cycle: These are > just "formal votes" which are allowed by maintainers > > * Committers are specifically mentioned as "referees" in case there > are conflicts. There we have a hierarchy of conflict resolution and > the proposed xhange to XAPI committers should not affect > > == What is the impact of this change (IMPORTANT) == > > As such, the change proposed to XAPI committers is affecting the > voting dynamics for global votes as on the face of it it increases the > number of maintainers (=committers) from 5 to 13. Given the size of > XAPI subproject and the fact that it basically never listed its > maintainers this seems reasonable. Also in light of the number of > maintainers in the Hypervisor project, of which there are 28 if I > counted correctly. > > But it does raise the question as to whether such a significant change > to maintainers sets a bad precedence and whether we need to look at > our process > > So I would argue that, *this ptoposal has* a global impact - even > though unintended - and that for this reason we need to have a > discussion and maybe a formal vote to ratify this proposed change by > the XAPI project. > > Best 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 Jun 04 12:33:58 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 04 Jun 2014 12:33: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 1WsAO9-0006as-NK; Wed, 04 Jun 2014 12:33:53 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WsAO8-0006am-8y for mirageos-devel@lists.xenproject.org; Wed, 04 Jun 2014 12:33:52 +0000 Received: from [193.109.254.147:43385] by server-12.bemta-14.messagelabs.com id 86/2E-27473-F221F835; Wed, 04 Jun 2014 12:33:51 +0000 X-Env-Sender: talex5@gmail.com X-Msg-Ref: server-2.tower-27.messagelabs.com!1401885229!9068851!1 X-Originating-IP: [209.85.214.178] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, ML_RADAR_SPEW_LINKS_23,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21471 invoked from network); 4 Jun 2014 12:33:50 -0000 Received: from mail-ob0-f178.google.com (HELO mail-ob0-f178.google.com) (209.85.214.178) by server-2.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 4 Jun 2014 12:33:50 -0000 Received: by mail-ob0-f178.google.com with SMTP id va2so7599316obc.23 for ; Wed, 04 Jun 2014 05:33:48 -0700 (PDT) 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=7ECANUI1Y2SZO/zxsVgrDVd2mOWPNo3YFpn4YMFkNyc=; b=0sM9+P0Bb7bDz/1S813bfwKp315LnPyamQHQX3D5V9w/q3sIxa5XmwvIvPO7I4uykM AFc+gC+D3Vc30CaQqLRTJTd8dPp44b1UJosJU9wx9uO45hes4GKYHgEBbY5hwLH7gat1 gVf9ZNXDxF8P65MO5x0mOTrOPwzOwSdqkZigATGIClDnAHSjMOpIpxEtGFv55o8UQtZ6 AQ7R7mL8S21mK/0SOsOZhwoyHUbjDWuFNFsdRzxiqSJnG8RIE54Zq7X3ZVHQ6xOdHeBJ cwKIkRP+c6OhLxXwdQhHEVFOBCzpvFezS8I1zTxtQCSUhhG2hJG2PMsZqeXVONjswsjO T5eQ== MIME-Version: 1.0 X-Received: by 10.182.142.194 with SMTP id ry2mr55622442obb.5.1401885228660; Wed, 04 Jun 2014 05:33:48 -0700 (PDT) Received: by 10.76.101.202 with HTTP; Wed, 4 Jun 2014 05:33:48 -0700 (PDT) In-Reply-To: References: Date: Wed, 4 Jun 2014 13:33:48 +0100 Message-ID: From: Thomas Leonard To: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Mirage on Xen/ARM status X-BeenThere: mirageos-devel@lists.xenproject.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 An update on the Mirage/ARM port: I have mirage-platform upgraded to the new Mini-OS (plus openlibm and no libc). Networking is working again on x86_64 (I can telnet to the mirage-skeleton/network service and send it a message), but not on ARM yet. This required some changes to Mini-OS to expose the grant table details and to stop Mini-OS's xenbus from stealing the event notifications. I need this clean this up. OCaml's Random currently tries to open /dev/urandom, which fails. Looks like it falls back to using gettimeofday in that case. It logs a message to the console ("Attempt to open(/dev/urandom)!"), so hopefully we'll remember to fix it eventually. Networking doesn't work on ARM as the code wants to use start_info, which doesn't exist. I might try making a fake start_info page on ARM rather than modifying everything else. My current plan is: - Upstream Karim's initial ARM support to Xen. I split the original patch into three smaller ones and submitted them, but they want it broken up further, which is fair enough. - Upstream my patches to build a libminios.a library, plus some other fixes to the build system. - Make some changes to Mini-OS to work unmodified with Mirage (specifically: expose grant table details, disable interrupt-based event handlers, and allow linking only the features we need). - Add a proper string library to mirage-platform to replace Mini-OS's limited sprintf. - Upstream my patches to mirage-platform and mirage to build using the new libminios and openlibm (these are on github in my forks). - Upstream my Mini-OS ARM patches to Xen. - Add a start_info structure on ARM, or find some other way to expose those details to Mirage. There are various other bits that would be nice to have: - Use a proper virtual memory mapping on ARM, including a stack guard page and a non-mapped page zero. I should probably find out what it does on x86 and make them consistent too. - Allow running C code in Mirage in a restricted sandbox (non-privileged mode). - Use ctypes to replace current stubs. - Replace all the unimplemented stubs (lseek, etc) to check nothing is relying on them. - Import the FreeBSD hardware float support code so we can use hardware floating point. Currently, everything is soft-float. On 16 May 2014 17:41, Thomas Leonard wrote: > Good news for Mirage on Xen/ARM: mirage-skeleton/console is now working! > > It needs tidying up, but currently to run you need: > > 1. mirage-platform/arm-hacks3: > https://github.com/talex5/mirage-platform/tree/arm-hacks3 > > This has been updated for the new Mini-OS. dietlibc is gone (we no > longer need a C library). libm is also gone, but you'll need to > replace it with something else (see below). There's a new libxencaml > with the separated-out Mini-OS OCaml bindings. > > I had to make some changes to the Mirage API, because on ARM Xen > doesn't provide start_info. Also, I switched the timer stuff to use > mini-os's block_domain call, which handles ARM correctly. > > 2. mirage-console/master (modified to avoid using start_page) > https://github.com/talex5/mirage-console/commits/master > > 3. openlibm/arm-hacks (disables all long double support, which ARM > doesn't have and OCaml doesn't need) > https://github.com/talex5/openlibm/tree/arm-hacks > > 4. Mini-OS/devel (can now be installed as a library, libminios.a - use > "make install-ocamlfind") > https://github.com/talex5/xen/tree/devel > > > You'll also need a *soft-float* ARM build machine. Hard-float would > require extra support from Mini-OS. You can cross-compile the C code > easily enough, but OCaml can't cross compile, even from armhf to armel > (the -ffpu option just gives a silly error message). I got mine with: > > debootstrap --arch armel testing /mnt > > Finally, you'll also need to modify mir-console's Makefile, because I > didn't update mirage to generate it properly. This worked for me: > > KERNEL_DIR = $(shell ocamlfind query minios-kernel) > PLATFORM_DIR = $(shell ocamlfind query mirage-xen) > > build: main.native.o > ld -d -static -nostdlib -T $(KERNEL_DIR)/link.lds \ > --start-group \ > /usr/lib/gcc/arm-linux-gnueabi/4.8/libgcc.a \ > $(PLATFORM_DIR)/libocaml.a \ > $(PLATFORM_DIR)/libxencaml.a \ > ~/lib/libopenlibm.a \ > $(KERNEL_DIR)/libminios.a -o mir-console.elf \ > _build/main.native.o \ > --end-group > objcopy -O binary mir-console.elf mir-console.xen > > The next steps are to make this all a bit easier to install and clean > up the branches so they can be merged. Also, some things are broken > (printf doesn't accept %f, for example, because we're just using > Mini-OS's version). > > > -- > 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 -- 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 Jun 04 12:33:58 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 04 Jun 2014 12:33: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 1WsAO9-0006as-NK; Wed, 04 Jun 2014 12:33:53 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WsAO8-0006am-8y for mirageos-devel@lists.xenproject.org; Wed, 04 Jun 2014 12:33:52 +0000 Received: from [193.109.254.147:43385] by server-12.bemta-14.messagelabs.com id 86/2E-27473-F221F835; Wed, 04 Jun 2014 12:33:51 +0000 X-Env-Sender: talex5@gmail.com X-Msg-Ref: server-2.tower-27.messagelabs.com!1401885229!9068851!1 X-Originating-IP: [209.85.214.178] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, ML_RADAR_SPEW_LINKS_23,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21471 invoked from network); 4 Jun 2014 12:33:50 -0000 Received: from mail-ob0-f178.google.com (HELO mail-ob0-f178.google.com) (209.85.214.178) by server-2.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 4 Jun 2014 12:33:50 -0000 Received: by mail-ob0-f178.google.com with SMTP id va2so7599316obc.23 for ; Wed, 04 Jun 2014 05:33:48 -0700 (PDT) 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=7ECANUI1Y2SZO/zxsVgrDVd2mOWPNo3YFpn4YMFkNyc=; b=0sM9+P0Bb7bDz/1S813bfwKp315LnPyamQHQX3D5V9w/q3sIxa5XmwvIvPO7I4uykM AFc+gC+D3Vc30CaQqLRTJTd8dPp44b1UJosJU9wx9uO45hes4GKYHgEBbY5hwLH7gat1 gVf9ZNXDxF8P65MO5x0mOTrOPwzOwSdqkZigATGIClDnAHSjMOpIpxEtGFv55o8UQtZ6 AQ7R7mL8S21mK/0SOsOZhwoyHUbjDWuFNFsdRzxiqSJnG8RIE54Zq7X3ZVHQ6xOdHeBJ cwKIkRP+c6OhLxXwdQhHEVFOBCzpvFezS8I1zTxtQCSUhhG2hJG2PMsZqeXVONjswsjO T5eQ== MIME-Version: 1.0 X-Received: by 10.182.142.194 with SMTP id ry2mr55622442obb.5.1401885228660; Wed, 04 Jun 2014 05:33:48 -0700 (PDT) Received: by 10.76.101.202 with HTTP; Wed, 4 Jun 2014 05:33:48 -0700 (PDT) In-Reply-To: References: Date: Wed, 4 Jun 2014 13:33:48 +0100 Message-ID: From: Thomas Leonard To: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Mirage on Xen/ARM status X-BeenThere: mirageos-devel@lists.xenproject.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 An update on the Mirage/ARM port: I have mirage-platform upgraded to the new Mini-OS (plus openlibm and no libc). Networking is working again on x86_64 (I can telnet to the mirage-skeleton/network service and send it a message), but not on ARM yet. This required some changes to Mini-OS to expose the grant table details and to stop Mini-OS's xenbus from stealing the event notifications. I need this clean this up. OCaml's Random currently tries to open /dev/urandom, which fails. Looks like it falls back to using gettimeofday in that case. It logs a message to the console ("Attempt to open(/dev/urandom)!"), so hopefully we'll remember to fix it eventually. Networking doesn't work on ARM as the code wants to use start_info, which doesn't exist. I might try making a fake start_info page on ARM rather than modifying everything else. My current plan is: - Upstream Karim's initial ARM support to Xen. I split the original patch into three smaller ones and submitted them, but they want it broken up further, which is fair enough. - Upstream my patches to build a libminios.a library, plus some other fixes to the build system. - Make some changes to Mini-OS to work unmodified with Mirage (specifically: expose grant table details, disable interrupt-based event handlers, and allow linking only the features we need). - Add a proper string library to mirage-platform to replace Mini-OS's limited sprintf. - Upstream my patches to mirage-platform and mirage to build using the new libminios and openlibm (these are on github in my forks). - Upstream my Mini-OS ARM patches to Xen. - Add a start_info structure on ARM, or find some other way to expose those details to Mirage. There are various other bits that would be nice to have: - Use a proper virtual memory mapping on ARM, including a stack guard page and a non-mapped page zero. I should probably find out what it does on x86 and make them consistent too. - Allow running C code in Mirage in a restricted sandbox (non-privileged mode). - Use ctypes to replace current stubs. - Replace all the unimplemented stubs (lseek, etc) to check nothing is relying on them. - Import the FreeBSD hardware float support code so we can use hardware floating point. Currently, everything is soft-float. On 16 May 2014 17:41, Thomas Leonard wrote: > Good news for Mirage on Xen/ARM: mirage-skeleton/console is now working! > > It needs tidying up, but currently to run you need: > > 1. mirage-platform/arm-hacks3: > https://github.com/talex5/mirage-platform/tree/arm-hacks3 > > This has been updated for the new Mini-OS. dietlibc is gone (we no > longer need a C library). libm is also gone, but you'll need to > replace it with something else (see below). There's a new libxencaml > with the separated-out Mini-OS OCaml bindings. > > I had to make some changes to the Mirage API, because on ARM Xen > doesn't provide start_info. Also, I switched the timer stuff to use > mini-os's block_domain call, which handles ARM correctly. > > 2. mirage-console/master (modified to avoid using start_page) > https://github.com/talex5/mirage-console/commits/master > > 3. openlibm/arm-hacks (disables all long double support, which ARM > doesn't have and OCaml doesn't need) > https://github.com/talex5/openlibm/tree/arm-hacks > > 4. Mini-OS/devel (can now be installed as a library, libminios.a - use > "make install-ocamlfind") > https://github.com/talex5/xen/tree/devel > > > You'll also need a *soft-float* ARM build machine. Hard-float would > require extra support from Mini-OS. You can cross-compile the C code > easily enough, but OCaml can't cross compile, even from armhf to armel > (the -ffpu option just gives a silly error message). I got mine with: > > debootstrap --arch armel testing /mnt > > Finally, you'll also need to modify mir-console's Makefile, because I > didn't update mirage to generate it properly. This worked for me: > > KERNEL_DIR = $(shell ocamlfind query minios-kernel) > PLATFORM_DIR = $(shell ocamlfind query mirage-xen) > > build: main.native.o > ld -d -static -nostdlib -T $(KERNEL_DIR)/link.lds \ > --start-group \ > /usr/lib/gcc/arm-linux-gnueabi/4.8/libgcc.a \ > $(PLATFORM_DIR)/libocaml.a \ > $(PLATFORM_DIR)/libxencaml.a \ > ~/lib/libopenlibm.a \ > $(KERNEL_DIR)/libminios.a -o mir-console.elf \ > _build/main.native.o \ > --end-group > objcopy -O binary mir-console.elf mir-console.xen > > The next steps are to make this all a bit easier to install and clean > up the branches so they can be merged. Also, some things are broken > (printf doesn't accept %f, for example, because we're just using > Mini-OS's version). > > > -- > 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 -- 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 Jun 05 11:49:17 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 05 Jun 2014 11:49: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 1WsWAS-0006sT-OQ; Thu, 05 Jun 2014 11:49:12 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WsWAR-0006sE-8C for mirageos-devel@lists.xenproject.org; Thu, 05 Jun 2014 11:49:11 +0000 Received: from [85.158.143.35:45589] by server-3.bemta-4.messagelabs.com id C8/15-13602-63950935; Thu, 05 Jun 2014 11:49:10 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-10.tower-21.messagelabs.com!1401968949!9451138!1 X-Originating-IP: [209.85.212.174] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17608 invoked from network); 5 Jun 2014 11:49:10 -0000 Received: from mail-wi0-f174.google.com (HELO mail-wi0-f174.google.com) (209.85.212.174) by server-10.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 5 Jun 2014 11:49:10 -0000 Received: by mail-wi0-f174.google.com with SMTP id r20so10334289wiv.13 for ; Thu, 05 Jun 2014 04:49:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:reply-to:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=0PIuGFAQricBo7cGiPeenBbKrqFo0HMLE4wvXKCH4oU=; b=MblUQzlHzB3nxy7fFXDgCOFlEtEYA/XjjGuv9p6d12x4TmsttRLv9MOCKyx1w0RHLe j8+G9rPXduOOWaskaEPcHcufXwSgATwUuTWXoOLAvwMeFTBlRPKbIs5hcB7M8H8WHX2p QzPT6bSysi7djpTAynIJ0R50u8Hol9DmPLQhn8ogcRB7uWwUUKDGYje0OibdZ3PPViNP rpVrPC4Z4RHkEvoN4J/4MQlTPQfYfDaUIpGvSCnjjo7NNIKIHMxp1Fb5HiX9E6xS/+2L 8wPELZjywkKSUAJfyouYPt1vWGXzPNDb0/otbNYSXLTAK1GOTqSeMdEbZ7iZ0334InKl F2mA== X-Received: by 10.180.36.35 with SMTP id n3mr15103071wij.23.1401968949639; Thu, 05 Jun 2014 04:49:09 -0700 (PDT) Received: from [172.16.25.10] (97e5a5cd.skybroadband.com. [151.229.165.205]) by mx.google.com with ESMTPSA id v15sm7759290wjq.17.2014.06.05.04.49.08 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 05 Jun 2014 04:49:08 -0700 (PDT) Message-ID: <53905933.2040000@xen.org> Date: Thu, 05 Jun 2014 12:49:07 +0100 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: "xen-devel@lists.xen.org" , "xen-api@lists.xen.org" , "mirageos-devel@lists.xenproject.org" , Russell Pavlicek References: <538CA4E3.40506@xen.org> In-Reply-To: <538CA4E3.40506@xen.org> Subject: Re: [MirageOS-devel] [vote on timing] Xen Project Developer Meeting on August 20th AM in Chicago X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: lars.kurth@xen.org 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 everyone, I have more information related to the meeting. * I have space for a maximum of 40 people * I have the room from 8:30 - 18:30 - so we can be flexible on times * I have to use the same room for a board meeting. For the board meeting, I was thinking of a 8:00 - 9:00 or 9:00 - 10:00 (TBD, but the 9:00 slot is our normal board meeting time), starting the dev meeting 30 minutes after * LinuxCon is going on in parallel and the schedule has been published at http://events.linuxfoundation.org/events/linuxcon-north-america/program/schedule yesterday * Apart from Russell and me who both have talks from 12:15 - 13:05 no-one else has really an overlap. So what I am asking is for options: please vote +1 "09:30 - 13:00" +1 "10:30 - 14:00" +1 "13:00 - 16:30" Best Regards Lars On 02/06/2014 17:22, Lars Kurth wrote: > Hi all, > > I am pleased to announce that I secured space for a 1/2 day developer > meeting the day after the Xen Project Developer Summit. As in the > past, I suggest that the meeting lasts 3.5 - 4 hours. I suggest we > start at 9:30 and run until 1pm, but could start a little bit later. > If you have any preferences, let me know. As I will need to get a > sense re numbers and order food and drinks, please reply to the thread > for now, if you are planning to attend the meeting. Once I have more > information, I will create a wiki page, and you can sign up on the > wiki page. > > We will also have an Advisory Board meeting either before or after. > > Best 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 Thu Jun 05 11:49:17 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 05 Jun 2014 11:49: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 1WsWAS-0006sT-OQ; Thu, 05 Jun 2014 11:49:12 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WsWAR-0006sE-8C for mirageos-devel@lists.xenproject.org; Thu, 05 Jun 2014 11:49:11 +0000 Received: from [85.158.143.35:45589] by server-3.bemta-4.messagelabs.com id C8/15-13602-63950935; Thu, 05 Jun 2014 11:49:10 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-10.tower-21.messagelabs.com!1401968949!9451138!1 X-Originating-IP: [209.85.212.174] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17608 invoked from network); 5 Jun 2014 11:49:10 -0000 Received: from mail-wi0-f174.google.com (HELO mail-wi0-f174.google.com) (209.85.212.174) by server-10.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 5 Jun 2014 11:49:10 -0000 Received: by mail-wi0-f174.google.com with SMTP id r20so10334289wiv.13 for ; Thu, 05 Jun 2014 04:49:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:reply-to:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=0PIuGFAQricBo7cGiPeenBbKrqFo0HMLE4wvXKCH4oU=; b=MblUQzlHzB3nxy7fFXDgCOFlEtEYA/XjjGuv9p6d12x4TmsttRLv9MOCKyx1w0RHLe j8+G9rPXduOOWaskaEPcHcufXwSgATwUuTWXoOLAvwMeFTBlRPKbIs5hcB7M8H8WHX2p QzPT6bSysi7djpTAynIJ0R50u8Hol9DmPLQhn8ogcRB7uWwUUKDGYje0OibdZ3PPViNP rpVrPC4Z4RHkEvoN4J/4MQlTPQfYfDaUIpGvSCnjjo7NNIKIHMxp1Fb5HiX9E6xS/+2L 8wPELZjywkKSUAJfyouYPt1vWGXzPNDb0/otbNYSXLTAK1GOTqSeMdEbZ7iZ0334InKl F2mA== X-Received: by 10.180.36.35 with SMTP id n3mr15103071wij.23.1401968949639; Thu, 05 Jun 2014 04:49:09 -0700 (PDT) Received: from [172.16.25.10] (97e5a5cd.skybroadband.com. [151.229.165.205]) by mx.google.com with ESMTPSA id v15sm7759290wjq.17.2014.06.05.04.49.08 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 05 Jun 2014 04:49:08 -0700 (PDT) Message-ID: <53905933.2040000@xen.org> Date: Thu, 05 Jun 2014 12:49:07 +0100 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: "xen-devel@lists.xen.org" , "xen-api@lists.xen.org" , "mirageos-devel@lists.xenproject.org" , Russell Pavlicek References: <538CA4E3.40506@xen.org> In-Reply-To: <538CA4E3.40506@xen.org> Subject: Re: [MirageOS-devel] [vote on timing] Xen Project Developer Meeting on August 20th AM in Chicago X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: lars.kurth@xen.org 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 everyone, I have more information related to the meeting. * I have space for a maximum of 40 people * I have the room from 8:30 - 18:30 - so we can be flexible on times * I have to use the same room for a board meeting. For the board meeting, I was thinking of a 8:00 - 9:00 or 9:00 - 10:00 (TBD, but the 9:00 slot is our normal board meeting time), starting the dev meeting 30 minutes after * LinuxCon is going on in parallel and the schedule has been published at http://events.linuxfoundation.org/events/linuxcon-north-america/program/schedule yesterday * Apart from Russell and me who both have talks from 12:15 - 13:05 no-one else has really an overlap. So what I am asking is for options: please vote +1 "09:30 - 13:00" +1 "10:30 - 14:00" +1 "13:00 - 16:30" Best Regards Lars On 02/06/2014 17:22, Lars Kurth wrote: > Hi all, > > I am pleased to announce that I secured space for a 1/2 day developer > meeting the day after the Xen Project Developer Summit. As in the > past, I suggest that the meeting lasts 3.5 - 4 hours. I suggest we > start at 9:30 and run until 1pm, but could start a little bit later. > If you have any preferences, let me know. As I will need to get a > sense re numbers and order food and drinks, please reply to the thread > for now, if you are planning to attend the meeting. Once I have more > information, I will create a wiki page, and you can sign up on the > wiki page. > > We will also have an Advisory Board meeting either before or after. > > Best 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 Thu Jun 05 11:53:29 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 05 Jun 2014 11:53: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 1WsWEb-0007h8-Ss; Thu, 05 Jun 2014 11:53:29 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WsWEZ-0007gQ-RD; Thu, 05 Jun 2014 11:53:28 +0000 Received: from [193.109.254.147:36600] by server-4.bemta-14.messagelabs.com id AF/D4-02781-63A50935; Thu, 05 Jun 2014 11:53:26 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-16.tower-27.messagelabs.com!1401969205!3936560!1 X-Originating-IP: [74.125.82.44] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 762 invoked from network); 5 Jun 2014 11:53:26 -0000 Received: from mail-wg0-f44.google.com (HELO mail-wg0-f44.google.com) (74.125.82.44) by server-16.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 5 Jun 2014 11:53:26 -0000 Received: by mail-wg0-f44.google.com with SMTP id a1so946639wgh.3 for ; Thu, 05 Jun 2014 04:53:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:reply-to:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=bKCejQELMHQM/ITT2ujsFBq4QxE3AWeF8u1LTWWA/vs=; b=mk128iDhKzZjtah2I2KHsrZj8/ONx5OzFGQ9tJxN7A1eD1whqEQJJB2vCyQixkRdHc hFN+dc2CokcoIR3PTycOT5hKqZTIVhJHOBLcQM9dw9JgPEm8/nRBPyLMXy1PQB5b4eaO J1jWKVybqHCEDs/UA0FxSBQ6dUgc+Wi0jpGGY2U/utC1Gd3v2doWUX1OvYQ8zEPsnvA1 QOr7GINxusftnQQWBnnz8LEaH3TbsbncBjUDgqhhfU5FvwtDFsdXPEszy/vx2HrlXN5/ t0G49NTHNglne3Q15re3y8IxfTabL/Bno6soEoeIM3XGgqDhEcgz5cIz7eF1cEod4VlK O6+A== X-Received: by 10.180.93.163 with SMTP id cv3mr15242320wib.3.1401969205651; Thu, 05 Jun 2014 04:53:25 -0700 (PDT) Received: from [172.16.25.10] (97e5a5cd.skybroadband.com. [151.229.165.205]) by mx.google.com with ESMTPSA id bl3sm2276439wib.9.2014.06.05.04.53.24 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 05 Jun 2014 04:53:25 -0700 (PDT) Message-ID: <53905A33.7000209@xen.org> Date: Thu, 05 Jun 2014 12:53:23 +0100 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: "xen-devel@lists.xen.org" , xen-users@lists.xenproject.org, "xen-api@lists.xenproject.org" , "mirageos-devel@lists.xenproject.org" References: <5385D9C6.2090105@xen.org> In-Reply-To: <5385D9C6.2090105@xen.org> Subject: Re: [MirageOS-devel] [For community review] Windows PV Drivers Incubation Sub-project Proposal X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: lars.kurth@xen.org 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 Seems nobody had any significant comments Will set up a formal vote next week Lars On 28/05/2014 13:42, Lars Kurth wrote: > Hi all, > > please find attached a link to a new subproject to proposal to host = > and develop the Windows PV drivers. The proposal is at = > http://wiki.xenproject.org/wiki/Windows_PV_Drivers_Incubation_Project_Pro= posal = > (but I also attached the text below). > > Anyone can comment on the proposal. The review period will be open = > until June 6th. I will then incorporate any comments and go for a = > formal vote. > > Best Regards > Lars > > =3D=3D Windows PV Drivers Project Proposal =3D=3D > =3D=3D=3D Roles =3D=3D=3D > * Project Lead: Paul Durrant - Paul is Windows subsystem architect for = > XenServer and has authored the majority of the driver code. > * Project Sponsor: Matt Wilson - Matt is Xen Project AB member = > representing Amazon > * Project Mentor: Lars Kurth - Lars is the Community Manager for the = > Xen Project and has agreed to act as the project=92s Mentor. > > =3D=3D=3D Background =3D=3D=3D > ParaVirtualization aware (PV) device drivers are an important part of = > HVM guests running under Xen. Citrix has provided a set of PV driver > for Windows since the inception of XenServer. These drivers have = > evolved over the years and recently the full set has been made open > source with a BSD license and are therefore available to the community = > to modify and build. > I gave a talk at the 2013 Xen Developer Summit in Edinburgh (see = > http://www.slideshare.net/xen_com_mgr/open-source-pv-drivers) to > introduce the drivers. This proposal is intended to be a logical next = > step to that initial offering to the community. > > =3D=3D=3D Relevance to Xen and its Community =3D=3D=3D > The drivers have a dependency on Xen as they are ParaVirtualization = > aware. They are not tied in any way to Citrix commercial Xen offerings; > they are designed to function on any build of Xen since 3.4. They = > encompass high performance network and storage frontends and enable > functionality such as memory ballooning, and clean shutdown or reboot = > via the xl toolstack. They are well tested and supported, since they > are crucial to Citrix products, and are of benefit to anyone wishing = > to run Windows (i386 or x86_64) as a guest under Xen. > > =3D=3D=3D Current Status =3D=3D=3D > Recent builds of the drivers are currently being tested by Citrix and = > Amazon using the Microsoft HCK and Citrix will be providing = > logo-signed builds of the drivers in future commercial Xen offerings. = > Amazon are evaluating the drivers and may ship them in future AMIs. > Citrix may also provide logo-signed drivers via Microsoft's Windows = > Update mechanism, making them widely available to anyone running > Windows under Xen (not just XenServer) without the need for them to = > build the drivers themselves. Any other organization is also free to do > the same by registering a top level PV device with the Xen community = > (see http://xenbits.xen.org/gitweb/?p=3Dxen.git;a=3Dblob;f=3Ddocs/misc/pc= i-d > evice-reservations.txt) and logo-signing their driver builds. > > =3D=3D=3D Incubation =3D=3D=3D > The aim of making the Windows PV Drivers an incubated project is to = > raise their profile to members of the Xen community other than Citrix > and Amazon and hopefully gain more developer interest and = > contribution. The driver set provide APIs to fundamental Xen = > subsystems such > as grant tables, event channels and xenstore and therefore provide a = > basis for further frontends, e.g. HID (keyboard and mouse), PV audio > and possibly framebuffer. Current maintainers of the driver = > repositories are all employed by Citrix but by becoming an incubated = > project we > hope gain maintainers from the community as we build interest. > > We hope we can work with the maintainers of the GPLPV Windows Drivers = > to standardize Windows PV drivers for the Xen project. > > =3D=3D=3D Required Infrastructure =3D=3D=3D > =3D=3D=3D=3D Repositories =3D=3D=3D=3D > As a Xen Project sub-project we would wish the driver repositories to = > be hosted on xenbits, but mirrored to GitHub to allow use of the the > GitHub workflow. It makes sense to maintain a separate repository for = > each driver as: > > Each driver is separately installable with no compile-time linkage to = > any other driver. Some headers may be imported from one > repository to another to facilitate run-time discovery of interfaces = > provided by one driver and consumed by another, but it is desirable > that this is an explicit step to move from one version of an interface = > to another. > > A continuous integration server project can be created for each = > repository such that the only a modified driver is re-built, rather than > the entire set. > > The set of drivers (and hence repositories) is currently: > * XENBUS: Bus driver binding to the top-level PCI device (and = > providing most of the interfaces to Xen) > * XENVIF: Network class driver (hosting the code necessary to drive = > the netif ring protocol) > * XENNET: Network device driver (client of the class driver, provides = > VIFs to Windows network stack) > * XENVBD: Storage class driver (hosting the code necessary to drive = > the blkif ring protocol) > * XENIFACE: Interface driver (providing user-space access to xenstore) > > =3D=3D=3D=3D Build and Test =3D=3D=3D=3D > We request build infrastructure to make new builds of driver = > repositories immediately available for use by community members. This > includes: > > A build machine (physical or virtual), possibly part of the Xen = > Project test framework, running Jenkins or some such continuous > integration server to monitor the repositories > > A license for Microsoft Visual Studio (~ $1000) > Storage, either on the build machine or elsewhere, to act as a public = > facing symbol server for the convenience of developers > > =3D=3D=3D=3D=3D Approval Status =3D=3D=3D=3D=3D > The Advisory Board agreed to fund a Visual Studio license and two = > vendors in the community offered VM's to host the build environment. > > > _______________________________________________ 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 Jun 05 11:53:29 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 05 Jun 2014 11:53: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 1WsWEb-0007h8-Ss; Thu, 05 Jun 2014 11:53:29 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WsWEZ-0007gQ-RD; Thu, 05 Jun 2014 11:53:28 +0000 Received: from [193.109.254.147:36600] by server-4.bemta-14.messagelabs.com id AF/D4-02781-63A50935; Thu, 05 Jun 2014 11:53:26 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-16.tower-27.messagelabs.com!1401969205!3936560!1 X-Originating-IP: [74.125.82.44] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 762 invoked from network); 5 Jun 2014 11:53:26 -0000 Received: from mail-wg0-f44.google.com (HELO mail-wg0-f44.google.com) (74.125.82.44) by server-16.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 5 Jun 2014 11:53:26 -0000 Received: by mail-wg0-f44.google.com with SMTP id a1so946639wgh.3 for ; Thu, 05 Jun 2014 04:53:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:reply-to:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=bKCejQELMHQM/ITT2ujsFBq4QxE3AWeF8u1LTWWA/vs=; b=mk128iDhKzZjtah2I2KHsrZj8/ONx5OzFGQ9tJxN7A1eD1whqEQJJB2vCyQixkRdHc hFN+dc2CokcoIR3PTycOT5hKqZTIVhJHOBLcQM9dw9JgPEm8/nRBPyLMXy1PQB5b4eaO J1jWKVybqHCEDs/UA0FxSBQ6dUgc+Wi0jpGGY2U/utC1Gd3v2doWUX1OvYQ8zEPsnvA1 QOr7GINxusftnQQWBnnz8LEaH3TbsbncBjUDgqhhfU5FvwtDFsdXPEszy/vx2HrlXN5/ t0G49NTHNglne3Q15re3y8IxfTabL/Bno6soEoeIM3XGgqDhEcgz5cIz7eF1cEod4VlK O6+A== X-Received: by 10.180.93.163 with SMTP id cv3mr15242320wib.3.1401969205651; Thu, 05 Jun 2014 04:53:25 -0700 (PDT) Received: from [172.16.25.10] (97e5a5cd.skybroadband.com. [151.229.165.205]) by mx.google.com with ESMTPSA id bl3sm2276439wib.9.2014.06.05.04.53.24 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 05 Jun 2014 04:53:25 -0700 (PDT) Message-ID: <53905A33.7000209@xen.org> Date: Thu, 05 Jun 2014 12:53:23 +0100 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: "xen-devel@lists.xen.org" , xen-users@lists.xenproject.org, "xen-api@lists.xenproject.org" , "mirageos-devel@lists.xenproject.org" References: <5385D9C6.2090105@xen.org> In-Reply-To: <5385D9C6.2090105@xen.org> Subject: Re: [MirageOS-devel] [For community review] Windows PV Drivers Incubation Sub-project Proposal X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: lars.kurth@xen.org 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 Seems nobody had any significant comments Will set up a formal vote next week Lars On 28/05/2014 13:42, Lars Kurth wrote: > Hi all, > > please find attached a link to a new subproject to proposal to host = > and develop the Windows PV drivers. The proposal is at = > http://wiki.xenproject.org/wiki/Windows_PV_Drivers_Incubation_Project_Pro= posal = > (but I also attached the text below). > > Anyone can comment on the proposal. The review period will be open = > until June 6th. I will then incorporate any comments and go for a = > formal vote. > > Best Regards > Lars > > =3D=3D Windows PV Drivers Project Proposal =3D=3D > =3D=3D=3D Roles =3D=3D=3D > * Project Lead: Paul Durrant - Paul is Windows subsystem architect for = > XenServer and has authored the majority of the driver code. > * Project Sponsor: Matt Wilson - Matt is Xen Project AB member = > representing Amazon > * Project Mentor: Lars Kurth - Lars is the Community Manager for the = > Xen Project and has agreed to act as the project=92s Mentor. > > =3D=3D=3D Background =3D=3D=3D > ParaVirtualization aware (PV) device drivers are an important part of = > HVM guests running under Xen. Citrix has provided a set of PV driver > for Windows since the inception of XenServer. These drivers have = > evolved over the years and recently the full set has been made open > source with a BSD license and are therefore available to the community = > to modify and build. > I gave a talk at the 2013 Xen Developer Summit in Edinburgh (see = > http://www.slideshare.net/xen_com_mgr/open-source-pv-drivers) to > introduce the drivers. This proposal is intended to be a logical next = > step to that initial offering to the community. > > =3D=3D=3D Relevance to Xen and its Community =3D=3D=3D > The drivers have a dependency on Xen as they are ParaVirtualization = > aware. They are not tied in any way to Citrix commercial Xen offerings; > they are designed to function on any build of Xen since 3.4. They = > encompass high performance network and storage frontends and enable > functionality such as memory ballooning, and clean shutdown or reboot = > via the xl toolstack. They are well tested and supported, since they > are crucial to Citrix products, and are of benefit to anyone wishing = > to run Windows (i386 or x86_64) as a guest under Xen. > > =3D=3D=3D Current Status =3D=3D=3D > Recent builds of the drivers are currently being tested by Citrix and = > Amazon using the Microsoft HCK and Citrix will be providing = > logo-signed builds of the drivers in future commercial Xen offerings. = > Amazon are evaluating the drivers and may ship them in future AMIs. > Citrix may also provide logo-signed drivers via Microsoft's Windows = > Update mechanism, making them widely available to anyone running > Windows under Xen (not just XenServer) without the need for them to = > build the drivers themselves. Any other organization is also free to do > the same by registering a top level PV device with the Xen community = > (see http://xenbits.xen.org/gitweb/?p=3Dxen.git;a=3Dblob;f=3Ddocs/misc/pc= i-d > evice-reservations.txt) and logo-signing their driver builds. > > =3D=3D=3D Incubation =3D=3D=3D > The aim of making the Windows PV Drivers an incubated project is to = > raise their profile to members of the Xen community other than Citrix > and Amazon and hopefully gain more developer interest and = > contribution. The driver set provide APIs to fundamental Xen = > subsystems such > as grant tables, event channels and xenstore and therefore provide a = > basis for further frontends, e.g. HID (keyboard and mouse), PV audio > and possibly framebuffer. Current maintainers of the driver = > repositories are all employed by Citrix but by becoming an incubated = > project we > hope gain maintainers from the community as we build interest. > > We hope we can work with the maintainers of the GPLPV Windows Drivers = > to standardize Windows PV drivers for the Xen project. > > =3D=3D=3D Required Infrastructure =3D=3D=3D > =3D=3D=3D=3D Repositories =3D=3D=3D=3D > As a Xen Project sub-project we would wish the driver repositories to = > be hosted on xenbits, but mirrored to GitHub to allow use of the the > GitHub workflow. It makes sense to maintain a separate repository for = > each driver as: > > Each driver is separately installable with no compile-time linkage to = > any other driver. Some headers may be imported from one > repository to another to facilitate run-time discovery of interfaces = > provided by one driver and consumed by another, but it is desirable > that this is an explicit step to move from one version of an interface = > to another. > > A continuous integration server project can be created for each = > repository such that the only a modified driver is re-built, rather than > the entire set. > > The set of drivers (and hence repositories) is currently: > * XENBUS: Bus driver binding to the top-level PCI device (and = > providing most of the interfaces to Xen) > * XENVIF: Network class driver (hosting the code necessary to drive = > the netif ring protocol) > * XENNET: Network device driver (client of the class driver, provides = > VIFs to Windows network stack) > * XENVBD: Storage class driver (hosting the code necessary to drive = > the blkif ring protocol) > * XENIFACE: Interface driver (providing user-space access to xenstore) > > =3D=3D=3D=3D Build and Test =3D=3D=3D=3D > We request build infrastructure to make new builds of driver = > repositories immediately available for use by community members. This > includes: > > A build machine (physical or virtual), possibly part of the Xen = > Project test framework, running Jenkins or some such continuous > integration server to monitor the repositories > > A license for Microsoft Visual Studio (~ $1000) > Storage, either on the build machine or elsewhere, to act as a public = > facing symbol server for the convenience of developers > > =3D=3D=3D=3D=3D Approval Status =3D=3D=3D=3D=3D > The Advisory Board agreed to fund a Visual Studio license and two = > vendors in the community offered VM's to host the build environment. > > > _______________________________________________ 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 Jun 05 11:54:34 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 05 Jun 2014 11:54: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 1WsWFe-0007vg-UY; Thu, 05 Jun 2014 11:54:34 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WsWFd-0007vD-Hw for mirageos-devel@lists.xenproject.org; Thu, 05 Jun 2014 11:54:33 +0000 Received: from [85.158.143.35:12387] by server-1.bemta-4.messagelabs.com id 62/CD-09853-87A50935; Thu, 05 Jun 2014 11:54:32 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-3.tower-21.messagelabs.com!1401969272!9102236!1 X-Originating-IP: [209.85.212.170] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10752 invoked from network); 5 Jun 2014 11:54:32 -0000 Received: from mail-wi0-f170.google.com (HELO mail-wi0-f170.google.com) (209.85.212.170) by server-3.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 5 Jun 2014 11:54:32 -0000 Received: by mail-wi0-f170.google.com with SMTP id bs8so9489704wib.3 for ; Thu, 05 Jun 2014 04:54:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:reply-to:user-agent:mime-version:to :subject:content-type:content-transfer-encoding; bh=qqYhfmqFmM1nDe+ihcpnMdpDnbmspoMoaZ4RjVrG4hY=; b=zPHVcYMtvF+kADeN0F0hyzOvWg8rdHHd3Whh50FH4Brt+yvwaOleCxaYgoAmBs/i08 KkbQX3Ww/217kVKDj4iFw/4DOzLYDOMvOz4CgCK3VDLm4jVpshD5GHKE75z6SGzckBH2 pydes1Kw2BFbWXOU1t0mag2Er1i2YYHe1ISjCQlT9hzX1Z30/ielQ5Ri+olstAzeaPKA 5xhTVXNE6QFHTmN990jAg+qZFF8ddUYNlRjUu8boUur7r8BeCKTZOWIB5xcnbzfHOiCg Ime9ZTxKB7ehHnCBrKAc9pm4FEHyaO4DiPR6medhz4m1Z4m9TW5AJ92Ns4cFYpRyeLyg zcZA== X-Received: by 10.180.90.51 with SMTP id bt19mr15320183wib.22.1401969272137; Thu, 05 Jun 2014 04:54:32 -0700 (PDT) Received: from [172.16.25.10] (97e5a5cd.skybroadband.com. [151.229.165.205]) by mx.google.com with ESMTPSA id ht5sm7738800wjb.49.2014.06.05.04.54.31 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 05 Jun 2014 04:54:31 -0700 (PDT) Message-ID: <53905A76.8050606@xen.org> Date: Thu, 05 Jun 2014 12:54:30 +0100 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: "xen-devel@lists.xen.org" , "xen-api@lists.xen.org" , "mirageos-devel@lists.xenproject.org" Subject: [MirageOS-devel] May Advisory Board minutes posted X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: lars.kurth@xen.org 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 http://wiki.xenproject.org/wiki/AB_Meeting/May_2014_Minutes _______________________________________________ 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 Jun 05 11:54:34 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 05 Jun 2014 11:54: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 1WsWFe-0007vg-UY; Thu, 05 Jun 2014 11:54:34 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WsWFd-0007vD-Hw for mirageos-devel@lists.xenproject.org; Thu, 05 Jun 2014 11:54:33 +0000 Received: from [85.158.143.35:12387] by server-1.bemta-4.messagelabs.com id 62/CD-09853-87A50935; Thu, 05 Jun 2014 11:54:32 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-3.tower-21.messagelabs.com!1401969272!9102236!1 X-Originating-IP: [209.85.212.170] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10752 invoked from network); 5 Jun 2014 11:54:32 -0000 Received: from mail-wi0-f170.google.com (HELO mail-wi0-f170.google.com) (209.85.212.170) by server-3.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 5 Jun 2014 11:54:32 -0000 Received: by mail-wi0-f170.google.com with SMTP id bs8so9489704wib.3 for ; Thu, 05 Jun 2014 04:54:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:reply-to:user-agent:mime-version:to :subject:content-type:content-transfer-encoding; bh=qqYhfmqFmM1nDe+ihcpnMdpDnbmspoMoaZ4RjVrG4hY=; b=zPHVcYMtvF+kADeN0F0hyzOvWg8rdHHd3Whh50FH4Brt+yvwaOleCxaYgoAmBs/i08 KkbQX3Ww/217kVKDj4iFw/4DOzLYDOMvOz4CgCK3VDLm4jVpshD5GHKE75z6SGzckBH2 pydes1Kw2BFbWXOU1t0mag2Er1i2YYHe1ISjCQlT9hzX1Z30/ielQ5Ri+olstAzeaPKA 5xhTVXNE6QFHTmN990jAg+qZFF8ddUYNlRjUu8boUur7r8BeCKTZOWIB5xcnbzfHOiCg Ime9ZTxKB7ehHnCBrKAc9pm4FEHyaO4DiPR6medhz4m1Z4m9TW5AJ92Ns4cFYpRyeLyg zcZA== X-Received: by 10.180.90.51 with SMTP id bt19mr15320183wib.22.1401969272137; Thu, 05 Jun 2014 04:54:32 -0700 (PDT) Received: from [172.16.25.10] (97e5a5cd.skybroadband.com. [151.229.165.205]) by mx.google.com with ESMTPSA id ht5sm7738800wjb.49.2014.06.05.04.54.31 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 05 Jun 2014 04:54:31 -0700 (PDT) Message-ID: <53905A76.8050606@xen.org> Date: Thu, 05 Jun 2014 12:54:30 +0100 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: "xen-devel@lists.xen.org" , "xen-api@lists.xen.org" , "mirageos-devel@lists.xenproject.org" Subject: [MirageOS-devel] May Advisory Board minutes posted X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: lars.kurth@xen.org 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 http://wiki.xenproject.org/wiki/AB_Meeting/May_2014_Minutes _______________________________________________ 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 Jun 05 14:29:45 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 05 Jun 2014 14:29: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 1WsYfj-0007eS-0A; Thu, 05 Jun 2014 14:29:39 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WsYfh-0007e5-9w for mirageos-devel@lists.xenproject.org; Thu, 05 Jun 2014 14:29:37 +0000 Received: from [193.109.254.147:53803] by server-4.bemta-14.messagelabs.com id 3E/46-02781-0DE70935; Thu, 05 Jun 2014 14:29:36 +0000 X-Env-Sender: dunlapg@gmail.com X-Msg-Ref: server-3.tower-27.messagelabs.com!1401978575!9298372!1 X-Originating-IP: [74.125.82.172] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8681 invoked from network); 5 Jun 2014 14:29:35 -0000 Received: from mail-we0-f172.google.com (HELO mail-we0-f172.google.com) (74.125.82.172) by server-3.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 5 Jun 2014 14:29:35 -0000 Received: by mail-we0-f172.google.com with SMTP id k48so1234626wev.3 for ; Thu, 05 Jun 2014 07:29:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=HeQzPwZjyh6unc45cXl9/qM/7rd4dctVeWMdlQgj3n8=; b=T1OkclypUNX937MC6nHF1C44+oA8vlmUY1B/CXX/WlInkB6DgFYM373OUrxSWr4wKj JVnpq4dl7fr+dLVCP6mCq2MLM6DtmDkyr3bPSahi2TcVZNlrgbOGwU8h/LVZBITpPD4Z d/DUV0YrJXrivpUQob/QItdg7UJfeKdzEcbM0tV5rhSdEs6XxeDjxIZ8UO4qXTcNezDQ PUP1S8LWSwfz+4388gd/zoSiNCcWIYEFKhhvEzz6OvUhzvlp9blKyYKZR1ZT8pPUlcxj qena+0hJ1DY4LEFlqUkPBJogNhceY1K8ZfLNDoozPHwiHm5oF986efecxzqCp+IGxMSM Q2Jg== MIME-Version: 1.0 X-Received: by 10.194.108.5 with SMTP id hg5mr82207027wjb.57.1401978574182; Thu, 05 Jun 2014 07:29:34 -0700 (PDT) Received: by 10.194.14.228 with HTTP; Thu, 5 Jun 2014 07:29:34 -0700 (PDT) In-Reply-To: <539096150200007800018468@mail.emea.novell.com> References: <538CA4E3.40506@xen.org> <53905933.2040000@xen.org> <539096150200007800018468@mail.emea.novell.com> Date: Thu, 5 Jun 2014 15:29:34 +0100 X-Google-Sender-Auth: Dvqwqvxr4OeKMt4oxtnkuJoLi98 Message-ID: From: George Dunlap To: Jan Beulich Cc: "xen-api@lists.xen.org" , Russell Pavlicek , "mirageos-devel@lists.xenproject.org" , "xen-devel@lists.xen.org" Subject: Re: [MirageOS-devel] [Xen-devel] [vote on timing] Xen Project Developer Meeting on August 20th AM in Chicago X-BeenThere: mirageos-devel@lists.xenproject.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 Thu, Jun 5, 2014 at 3:08 PM, Jan Beulich wrote: >>>> On 05.06.14 at 13:49, wrote: >> Hi everyone, >> >> I have more information related to the meeting. >> * I have space for a maximum of 40 people >> * I have the room from 8:30 - 18:30 - so we can be flexible on times >> * I have to use the same room for a board meeting. For the board >> meeting, I was thinking of a 8:00 - 9:00 or 9:00 - 10:00 (TBD, but the >> 9:00 slot is our normal board meeting time), starting the dev meeting 30 >> minutes after >> * LinuxCon is going on in parallel and the schedule has been published >> at >> http://events.linuxfoundation.org/events/linuxcon-north-america/program/schedu >> le >> yesterday >> * Apart from Russell and me who both have talks from 12:15 - 13:05 >> no-one else has really an overlap. >> >> So what I am asking is for options: please vote >> +1 "09:30 - 13:00" >> +1 "10:30 - 14:00" >> +1 "13:00 - 16:30" > > +1 "09:30 - 13:00" There's a talk by someone from Docker on containers and security I should really attend from 12:15-13:05 (at least, that's where it is now). +1 "09:30 - 13:00" -George _______________________________________________ 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 Jun 05 14:29:45 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 05 Jun 2014 14:29: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 1WsYfj-0007eS-0A; Thu, 05 Jun 2014 14:29:39 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WsYfh-0007e5-9w for mirageos-devel@lists.xenproject.org; Thu, 05 Jun 2014 14:29:37 +0000 Received: from [193.109.254.147:53803] by server-4.bemta-14.messagelabs.com id 3E/46-02781-0DE70935; Thu, 05 Jun 2014 14:29:36 +0000 X-Env-Sender: dunlapg@gmail.com X-Msg-Ref: server-3.tower-27.messagelabs.com!1401978575!9298372!1 X-Originating-IP: [74.125.82.172] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8681 invoked from network); 5 Jun 2014 14:29:35 -0000 Received: from mail-we0-f172.google.com (HELO mail-we0-f172.google.com) (74.125.82.172) by server-3.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 5 Jun 2014 14:29:35 -0000 Received: by mail-we0-f172.google.com with SMTP id k48so1234626wev.3 for ; Thu, 05 Jun 2014 07:29:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=HeQzPwZjyh6unc45cXl9/qM/7rd4dctVeWMdlQgj3n8=; b=T1OkclypUNX937MC6nHF1C44+oA8vlmUY1B/CXX/WlInkB6DgFYM373OUrxSWr4wKj JVnpq4dl7fr+dLVCP6mCq2MLM6DtmDkyr3bPSahi2TcVZNlrgbOGwU8h/LVZBITpPD4Z d/DUV0YrJXrivpUQob/QItdg7UJfeKdzEcbM0tV5rhSdEs6XxeDjxIZ8UO4qXTcNezDQ PUP1S8LWSwfz+4388gd/zoSiNCcWIYEFKhhvEzz6OvUhzvlp9blKyYKZR1ZT8pPUlcxj qena+0hJ1DY4LEFlqUkPBJogNhceY1K8ZfLNDoozPHwiHm5oF986efecxzqCp+IGxMSM Q2Jg== MIME-Version: 1.0 X-Received: by 10.194.108.5 with SMTP id hg5mr82207027wjb.57.1401978574182; Thu, 05 Jun 2014 07:29:34 -0700 (PDT) Received: by 10.194.14.228 with HTTP; Thu, 5 Jun 2014 07:29:34 -0700 (PDT) In-Reply-To: <539096150200007800018468@mail.emea.novell.com> References: <538CA4E3.40506@xen.org> <53905933.2040000@xen.org> <539096150200007800018468@mail.emea.novell.com> Date: Thu, 5 Jun 2014 15:29:34 +0100 X-Google-Sender-Auth: Dvqwqvxr4OeKMt4oxtnkuJoLi98 Message-ID: From: George Dunlap To: Jan Beulich Cc: "xen-api@lists.xen.org" , Russell Pavlicek , "mirageos-devel@lists.xenproject.org" , "xen-devel@lists.xen.org" Subject: Re: [MirageOS-devel] [Xen-devel] [vote on timing] Xen Project Developer Meeting on August 20th AM in Chicago X-BeenThere: mirageos-devel@lists.xenproject.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 Thu, Jun 5, 2014 at 3:08 PM, Jan Beulich wrote: >>>> On 05.06.14 at 13:49, wrote: >> Hi everyone, >> >> I have more information related to the meeting. >> * I have space for a maximum of 40 people >> * I have the room from 8:30 - 18:30 - so we can be flexible on times >> * I have to use the same room for a board meeting. For the board >> meeting, I was thinking of a 8:00 - 9:00 or 9:00 - 10:00 (TBD, but the >> 9:00 slot is our normal board meeting time), starting the dev meeting 30 >> minutes after >> * LinuxCon is going on in parallel and the schedule has been published >> at >> http://events.linuxfoundation.org/events/linuxcon-north-america/program/schedu >> le >> yesterday >> * Apart from Russell and me who both have talks from 12:15 - 13:05 >> no-one else has really an overlap. >> >> So what I am asking is for options: please vote >> +1 "09:30 - 13:00" >> +1 "10:30 - 14:00" >> +1 "13:00 - 16:30" > > +1 "09:30 - 13:00" There's a talk by someone from Docker on containers and security I should really attend from 12:15-13:05 (at least, that's where it is now). +1 "09:30 - 13:00" -George _______________________________________________ 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 Jun 05 20:29:45 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 05 Jun 2014 20:29: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 1WseI5-0001Up-Sh; Thu, 05 Jun 2014 20:29:37 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WseI5-0001Uk-1j for mirageos-devel@lists.xenproject.org; Thu, 05 Jun 2014 20:29:37 +0000 Received: from [85.158.143.35:11245] by server-2.bemta-4.messagelabs.com id 71/E7-06539-033D0935; Thu, 05 Jun 2014 20:29:36 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-15.tower-21.messagelabs.com!1402000175!9543593!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_23, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28557 invoked from network); 5 Jun 2014 20:29:35 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-15.tower-21.messagelabs.com with SMTP; 5 Jun 2014 20:29:35 -0000 Received: (qmail 3072 invoked by uid 634); 5 Jun 2014 20:29:34 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net (HELO [192.168.1.110]) (86.30.244.239) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Thu, 05 Jun 2014 21:29:32 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\)) From: Anil Madhavapeddy In-Reply-To: Date: Thu, 5 Jun 2014 21:29:31 +0100 Message-Id: <297FC9DB-3A4E-41A5-B00E-9DEF62C625E6@recoil.org> References: To: Thomas Leonard X-Mailer: Apple Mail (2.1874) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Mirage on Xen/ARM status X-BeenThere: mirageos-devel@lists.xenproject.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 Jun 2014, at 13:33, Thomas Leonard wrote: > An update on the Mirage/ARM port: > > I have mirage-platform upgraded to the new Mini-OS (plus openlibm and > no libc). Networking is working again on x86_64 (I can telnet to the > mirage-skeleton/network service and send it a message), but not on ARM > yet. Good to have x86_64 back! It's probably a good idea to CC me and Dave on the patchbombs to xen-devel, as I only sample the list these days due to mail volume. > This required some changes to Mini-OS to expose the grant table > details and to stop Mini-OS's xenbus from stealing the event > notifications. I need this clean this up. To be clear, this is networking using lwIP on ARM isnt it? For Mirage, the MiniOS Xenbus should be disabled entirely since our own OCaml Xenstore will handle everything. > OCaml's Random currently tries to open /dev/urandom, which fails. > Looks like it falls back to using gettimeofday in that case. It logs a > message to the console ("Attempt to open(/dev/urandom)!"), so > hopefully we'll remember to fix it eventually. Is this initialised forcibly anywhere, or only when someone calls a Random.self_init()? We need to deprecate this module in Mirage and ensure that we have a randomfront/back model, or risk introducing poor entropy. This hasn't mattered so far, but will be critical when we activate the OCaml TLS library that Hannes and David are working on. > Networking doesn't work on ARM as the code wants to use start_info, > which doesn't exist. I might try making a fake start_info page on ARM > rather than modifying everything else. Yep, sounds like a good plan to ease x86/ARM transition. > > > My current plan is: > > - Upstream Karim's initial ARM support to Xen. I split the original > patch into three smaller ones and submitted them, but they want it > broken up further, which is fair enough. > > - Upstream my patches to build a libminios.a library, plus some other > fixes to the build system. > > - Make some changes to Mini-OS to work unmodified with Mirage > (specifically: expose grant table details, disable interrupt-based > event handlers, and allow linking only the features we need). > > - Add a proper string library to mirage-platform to replace Mini-OS's > limited sprintf. > > - Upstream my patches to mirage-platform and mirage to build using the > new libminios and openlibm (these are on github in my forks). > > - Upstream my Mini-OS ARM patches to Xen. > > - Add a start_info structure on ARM, or find some other way to expose > those details to Mirage. > Ack! > > There are various other bits that would be nice to have: > > - Use a proper virtual memory mapping on ARM, including a stack guard > page and a non-mapped page zero. I should probably find out what it > does on x86 and make them consistent too. > > - Allow running C code in Mirage in a restricted sandbox (non-privileged mode). > > - Use ctypes to replace current stubs. > > - Replace all the unimplemented stubs (lseek, etc) to check nothing is > relying on them. > > - Import the FreeBSD hardware float support code so we can use > hardware floating point. Currently, everything is soft-float. Agreed that all these are nice-to-have but not essential to a first merge of the rest. Note that ctypes 0.3 is now out, so we have a stable baseline with stub generation. cheers, Anil > > > On 16 May 2014 17:41, Thomas Leonard wrote: >> Good news for Mirage on Xen/ARM: mirage-skeleton/console is now working! >> >> It needs tidying up, but currently to run you need: >> >> 1. mirage-platform/arm-hacks3: >> https://github.com/talex5/mirage-platform/tree/arm-hacks3 >> >> This has been updated for the new Mini-OS. dietlibc is gone (we no >> longer need a C library). libm is also gone, but you'll need to >> replace it with something else (see below). There's a new libxencaml >> with the separated-out Mini-OS OCaml bindings. >> >> I had to make some changes to the Mirage API, because on ARM Xen >> doesn't provide start_info. Also, I switched the timer stuff to use >> mini-os's block_domain call, which handles ARM correctly. >> >> 2. mirage-console/master (modified to avoid using start_page) >> https://github.com/talex5/mirage-console/commits/master >> >> 3. openlibm/arm-hacks (disables all long double support, which ARM >> doesn't have and OCaml doesn't need) >> https://github.com/talex5/openlibm/tree/arm-hacks >> >> 4. Mini-OS/devel (can now be installed as a library, libminios.a - use >> "make install-ocamlfind") >> https://github.com/talex5/xen/tree/devel >> >> >> You'll also need a *soft-float* ARM build machine. Hard-float would >> require extra support from Mini-OS. You can cross-compile the C code >> easily enough, but OCaml can't cross compile, even from armhf to armel >> (the -ffpu option just gives a silly error message). I got mine with: >> >> debootstrap --arch armel testing /mnt >> >> Finally, you'll also need to modify mir-console's Makefile, because I >> didn't update mirage to generate it properly. This worked for me: >> >> KERNEL_DIR = $(shell ocamlfind query minios-kernel) >> PLATFORM_DIR = $(shell ocamlfind query mirage-xen) >> >> build: main.native.o >> ld -d -static -nostdlib -T $(KERNEL_DIR)/link.lds \ >> --start-group \ >> /usr/lib/gcc/arm-linux-gnueabi/4.8/libgcc.a \ >> $(PLATFORM_DIR)/libocaml.a \ >> $(PLATFORM_DIR)/libxencaml.a \ >> ~/lib/libopenlibm.a \ >> $(KERNEL_DIR)/libminios.a -o mir-console.elf \ >> _build/main.native.o \ >> --end-group >> objcopy -O binary mir-console.elf mir-console.xen >> >> The next steps are to make this all a bit easier to install and clean >> up the branches so they can be merged. Also, some things are broken >> (printf doesn't accept %f, for example, because we're just using >> Mini-OS's version). >> >> >> -- >> 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 > > > > -- > 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 Thu Jun 05 20:29:45 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 05 Jun 2014 20:29: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 1WseI5-0001Up-Sh; Thu, 05 Jun 2014 20:29:37 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WseI5-0001Uk-1j for mirageos-devel@lists.xenproject.org; Thu, 05 Jun 2014 20:29:37 +0000 Received: from [85.158.143.35:11245] by server-2.bemta-4.messagelabs.com id 71/E7-06539-033D0935; Thu, 05 Jun 2014 20:29:36 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-15.tower-21.messagelabs.com!1402000175!9543593!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_23, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28557 invoked from network); 5 Jun 2014 20:29:35 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-15.tower-21.messagelabs.com with SMTP; 5 Jun 2014 20:29:35 -0000 Received: (qmail 3072 invoked by uid 634); 5 Jun 2014 20:29:34 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net (HELO [192.168.1.110]) (86.30.244.239) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Thu, 05 Jun 2014 21:29:32 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\)) From: Anil Madhavapeddy In-Reply-To: Date: Thu, 5 Jun 2014 21:29:31 +0100 Message-Id: <297FC9DB-3A4E-41A5-B00E-9DEF62C625E6@recoil.org> References: To: Thomas Leonard X-Mailer: Apple Mail (2.1874) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Mirage on Xen/ARM status X-BeenThere: mirageos-devel@lists.xenproject.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 Jun 2014, at 13:33, Thomas Leonard wrote: > An update on the Mirage/ARM port: > > I have mirage-platform upgraded to the new Mini-OS (plus openlibm and > no libc). Networking is working again on x86_64 (I can telnet to the > mirage-skeleton/network service and send it a message), but not on ARM > yet. Good to have x86_64 back! It's probably a good idea to CC me and Dave on the patchbombs to xen-devel, as I only sample the list these days due to mail volume. > This required some changes to Mini-OS to expose the grant table > details and to stop Mini-OS's xenbus from stealing the event > notifications. I need this clean this up. To be clear, this is networking using lwIP on ARM isnt it? For Mirage, the MiniOS Xenbus should be disabled entirely since our own OCaml Xenstore will handle everything. > OCaml's Random currently tries to open /dev/urandom, which fails. > Looks like it falls back to using gettimeofday in that case. It logs a > message to the console ("Attempt to open(/dev/urandom)!"), so > hopefully we'll remember to fix it eventually. Is this initialised forcibly anywhere, or only when someone calls a Random.self_init()? We need to deprecate this module in Mirage and ensure that we have a randomfront/back model, or risk introducing poor entropy. This hasn't mattered so far, but will be critical when we activate the OCaml TLS library that Hannes and David are working on. > Networking doesn't work on ARM as the code wants to use start_info, > which doesn't exist. I might try making a fake start_info page on ARM > rather than modifying everything else. Yep, sounds like a good plan to ease x86/ARM transition. > > > My current plan is: > > - Upstream Karim's initial ARM support to Xen. I split the original > patch into three smaller ones and submitted them, but they want it > broken up further, which is fair enough. > > - Upstream my patches to build a libminios.a library, plus some other > fixes to the build system. > > - Make some changes to Mini-OS to work unmodified with Mirage > (specifically: expose grant table details, disable interrupt-based > event handlers, and allow linking only the features we need). > > - Add a proper string library to mirage-platform to replace Mini-OS's > limited sprintf. > > - Upstream my patches to mirage-platform and mirage to build using the > new libminios and openlibm (these are on github in my forks). > > - Upstream my Mini-OS ARM patches to Xen. > > - Add a start_info structure on ARM, or find some other way to expose > those details to Mirage. > Ack! > > There are various other bits that would be nice to have: > > - Use a proper virtual memory mapping on ARM, including a stack guard > page and a non-mapped page zero. I should probably find out what it > does on x86 and make them consistent too. > > - Allow running C code in Mirage in a restricted sandbox (non-privileged mode). > > - Use ctypes to replace current stubs. > > - Replace all the unimplemented stubs (lseek, etc) to check nothing is > relying on them. > > - Import the FreeBSD hardware float support code so we can use > hardware floating point. Currently, everything is soft-float. Agreed that all these are nice-to-have but not essential to a first merge of the rest. Note that ctypes 0.3 is now out, so we have a stable baseline with stub generation. cheers, Anil > > > On 16 May 2014 17:41, Thomas Leonard wrote: >> Good news for Mirage on Xen/ARM: mirage-skeleton/console is now working! >> >> It needs tidying up, but currently to run you need: >> >> 1. mirage-platform/arm-hacks3: >> https://github.com/talex5/mirage-platform/tree/arm-hacks3 >> >> This has been updated for the new Mini-OS. dietlibc is gone (we no >> longer need a C library). libm is also gone, but you'll need to >> replace it with something else (see below). There's a new libxencaml >> with the separated-out Mini-OS OCaml bindings. >> >> I had to make some changes to the Mirage API, because on ARM Xen >> doesn't provide start_info. Also, I switched the timer stuff to use >> mini-os's block_domain call, which handles ARM correctly. >> >> 2. mirage-console/master (modified to avoid using start_page) >> https://github.com/talex5/mirage-console/commits/master >> >> 3. openlibm/arm-hacks (disables all long double support, which ARM >> doesn't have and OCaml doesn't need) >> https://github.com/talex5/openlibm/tree/arm-hacks >> >> 4. Mini-OS/devel (can now be installed as a library, libminios.a - use >> "make install-ocamlfind") >> https://github.com/talex5/xen/tree/devel >> >> >> You'll also need a *soft-float* ARM build machine. Hard-float would >> require extra support from Mini-OS. You can cross-compile the C code >> easily enough, but OCaml can't cross compile, even from armhf to armel >> (the -ffpu option just gives a silly error message). I got mine with: >> >> debootstrap --arch armel testing /mnt >> >> Finally, you'll also need to modify mir-console's Makefile, because I >> didn't update mirage to generate it properly. This worked for me: >> >> KERNEL_DIR = $(shell ocamlfind query minios-kernel) >> PLATFORM_DIR = $(shell ocamlfind query mirage-xen) >> >> build: main.native.o >> ld -d -static -nostdlib -T $(KERNEL_DIR)/link.lds \ >> --start-group \ >> /usr/lib/gcc/arm-linux-gnueabi/4.8/libgcc.a \ >> $(PLATFORM_DIR)/libocaml.a \ >> $(PLATFORM_DIR)/libxencaml.a \ >> ~/lib/libopenlibm.a \ >> $(KERNEL_DIR)/libminios.a -o mir-console.elf \ >> _build/main.native.o \ >> --end-group >> objcopy -O binary mir-console.elf mir-console.xen >> >> The next steps are to make this all a bit easier to install and clean >> up the branches so they can be merged. Also, some things are broken >> (printf doesn't accept %f, for example, because we're just using >> Mini-OS's version). >> >> >> -- >> 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 > > > > -- > 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 Fri Jun 06 09:49:49 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 06 Jun 2014 09:49: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 1WsqmO-00042K-CB; Fri, 06 Jun 2014 09:49:44 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WsqmN-00041l-G1 for mirageos-devel@lists.xenproject.org; Fri, 06 Jun 2014 09:49:43 +0000 Received: from [193.109.254.147:34733] by server-14.bemta-14.messagelabs.com id 76/00-08195-6BE81935; Fri, 06 Jun 2014 09:49:42 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-14.tower-27.messagelabs.com!1402048182!9554990!1 X-Originating-IP: [74.125.82.178] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5193 invoked from network); 6 Jun 2014 09:49:42 -0000 Received: from mail-we0-f178.google.com (HELO mail-we0-f178.google.com) (74.125.82.178) by server-14.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 6 Jun 2014 09:49:42 -0000 Received: by mail-we0-f178.google.com with SMTP id p10so488555wes.37 for ; Fri, 06 Jun 2014 02:49:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:reply-to:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=MpRAK4JlkahRthiOiqikRmJ5IhvdcCZMNxI1h659CQ8=; b=VnBqXgnCxr3NWhucTdAKMnOv1mL06F2snEhYtF/XXe2DT+PSYun5avLtnxW6CQjn17 cXH0i1EBxnHixRR8QQmFXKLOQukwYrfb8SBNUaY8lbthj17mTJ3GFBYvUYD4+8Uc4uzO BQ5qp5RwCzZoJedfJc5py1WBVQVxhJz0cZ/+OLp0BWHzc0dLYXBKFVXsgAaGgvlrAjXh D8iwR8TsISHoHz2+4GtY/7g1P+pNaHxqpwYl6vrfnk8f/shwweyI/fr8aQYWm60Fv1bW WOQsWdI1TtXQbCxd80luMjYRQjxdIwxuuVeCWEWrzqfdBDlhYmFY5KHP8ivlydkH34AU YGMA== X-Received: by 10.194.84.101 with SMTP id x5mr5237148wjy.52.1402048181755; Fri, 06 Jun 2014 02:49:41 -0700 (PDT) Received: from [172.16.25.10] (97e5a5cd.skybroadband.com. [151.229.165.205]) by mx.google.com with ESMTPSA id fq2sm20430788wib.2.2014.06.06.02.49.40 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 06 Jun 2014 02:49:41 -0700 (PDT) Message-ID: <53918EB3.9060506@xen.org> Date: Fri, 06 Jun 2014 10:49:39 +0100 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: Jim Fehlig References: <538CA4E3.40506@xen.org> <53905933.2040000@xen.org> <5390AEE0.2080303@suse.com> In-Reply-To: <5390AEE0.2080303@suse.com> Cc: Russell Pavlicek , "xen-api@lists.xen.org" , "mirageos-devel@lists.xenproject.org" , "xen-devel@lists.xen.org" Subject: Re: [MirageOS-devel] [Xen-devel] [vote on timing] Xen Project Developer Meeting on August 20th AM in Chicago X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: lars.kurth@xen.org 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 Seems there is an overwhelming majority for the morning so far. I will try and start as early possible and move the board meeting to the afternoon Regards Lars On 05/06/2014 18:54, Jim Fehlig wrote: > Lars Kurth wrote: >> Hi everyone, >> >> I have more information related to the meeting. >> * I have space for a maximum of 40 people >> * I have the room from 8:30 - 18:30 - so we can be flexible on times >> * I have to use the same room for a board meeting. For the board >> meeting, I was thinking of a 8:00 - 9:00 or 9:00 - 10:00 (TBD, but the >> 9:00 slot is our normal board meeting time), starting the dev meeting >> 30 minutes after >> * LinuxCon is going on in parallel and the schedule has been published >> at >> http://events.linuxfoundation.org/events/linuxcon-north-america/program/schedule >> yesterday >> * Apart from Russell and me who both have talks from 12:15 - 13:05 >> no-one else has really an overlap. >> >> So what I am asking is for options: please vote >> +1 "09:30 - 13:00" > I'm planning to attend the dev summit and would like to participate in > the dev meeting if that is possible. I'll leave on the > afternoon/evening of the 20th, so +1 to 9:30-13:00. > > Regards, > Jim > _______________________________________________ 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 Jun 06 09:49:49 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 06 Jun 2014 09:49: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 1WsqmO-00042K-CB; Fri, 06 Jun 2014 09:49:44 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WsqmN-00041l-G1 for mirageos-devel@lists.xenproject.org; Fri, 06 Jun 2014 09:49:43 +0000 Received: from [193.109.254.147:34733] by server-14.bemta-14.messagelabs.com id 76/00-08195-6BE81935; Fri, 06 Jun 2014 09:49:42 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-14.tower-27.messagelabs.com!1402048182!9554990!1 X-Originating-IP: [74.125.82.178] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5193 invoked from network); 6 Jun 2014 09:49:42 -0000 Received: from mail-we0-f178.google.com (HELO mail-we0-f178.google.com) (74.125.82.178) by server-14.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 6 Jun 2014 09:49:42 -0000 Received: by mail-we0-f178.google.com with SMTP id p10so488555wes.37 for ; Fri, 06 Jun 2014 02:49:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:reply-to:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=MpRAK4JlkahRthiOiqikRmJ5IhvdcCZMNxI1h659CQ8=; b=VnBqXgnCxr3NWhucTdAKMnOv1mL06F2snEhYtF/XXe2DT+PSYun5avLtnxW6CQjn17 cXH0i1EBxnHixRR8QQmFXKLOQukwYrfb8SBNUaY8lbthj17mTJ3GFBYvUYD4+8Uc4uzO BQ5qp5RwCzZoJedfJc5py1WBVQVxhJz0cZ/+OLp0BWHzc0dLYXBKFVXsgAaGgvlrAjXh D8iwR8TsISHoHz2+4GtY/7g1P+pNaHxqpwYl6vrfnk8f/shwweyI/fr8aQYWm60Fv1bW WOQsWdI1TtXQbCxd80luMjYRQjxdIwxuuVeCWEWrzqfdBDlhYmFY5KHP8ivlydkH34AU YGMA== X-Received: by 10.194.84.101 with SMTP id x5mr5237148wjy.52.1402048181755; Fri, 06 Jun 2014 02:49:41 -0700 (PDT) Received: from [172.16.25.10] (97e5a5cd.skybroadband.com. [151.229.165.205]) by mx.google.com with ESMTPSA id fq2sm20430788wib.2.2014.06.06.02.49.40 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 06 Jun 2014 02:49:41 -0700 (PDT) Message-ID: <53918EB3.9060506@xen.org> Date: Fri, 06 Jun 2014 10:49:39 +0100 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: Jim Fehlig References: <538CA4E3.40506@xen.org> <53905933.2040000@xen.org> <5390AEE0.2080303@suse.com> In-Reply-To: <5390AEE0.2080303@suse.com> Cc: Russell Pavlicek , "xen-api@lists.xen.org" , "mirageos-devel@lists.xenproject.org" , "xen-devel@lists.xen.org" Subject: Re: [MirageOS-devel] [Xen-devel] [vote on timing] Xen Project Developer Meeting on August 20th AM in Chicago X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: lars.kurth@xen.org 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 Seems there is an overwhelming majority for the morning so far. I will try and start as early possible and move the board meeting to the afternoon Regards Lars On 05/06/2014 18:54, Jim Fehlig wrote: > Lars Kurth wrote: >> Hi everyone, >> >> I have more information related to the meeting. >> * I have space for a maximum of 40 people >> * I have the room from 8:30 - 18:30 - so we can be flexible on times >> * I have to use the same room for a board meeting. For the board >> meeting, I was thinking of a 8:00 - 9:00 or 9:00 - 10:00 (TBD, but the >> 9:00 slot is our normal board meeting time), starting the dev meeting >> 30 minutes after >> * LinuxCon is going on in parallel and the schedule has been published >> at >> http://events.linuxfoundation.org/events/linuxcon-north-america/program/schedule >> yesterday >> * Apart from Russell and me who both have talks from 12:15 - 13:05 >> no-one else has really an overlap. >> >> So what I am asking is for options: please vote >> +1 "09:30 - 13:00" > I'm planning to attend the dev summit and would like to participate in > the dev meeting if that is possible. I'll leave on the > afternoon/evening of the 20th, so +1 to 9:30-13:00. > > Regards, > Jim > _______________________________________________ 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 Jun 06 10:00:01 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 06 Jun 2014 10:00: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 1WsqwG-0005Ei-8w; Fri, 06 Jun 2014 09:59:56 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WsqwF-0005ES-4X for mirageos-devel@lists.xenproject.org; Fri, 06 Jun 2014 09:59:55 +0000 Received: from [193.109.254.147:13183] by server-5.bemta-14.messagelabs.com id 51/68-26413-A1191935; Fri, 06 Jun 2014 09:59:54 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-7.tower-27.messagelabs.com!1402048792!9536436!1 X-Originating-IP: [66.165.176.63] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni42MyA9PiAzMDYwNDg=\n X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16713 invoked from network); 6 Jun 2014 09:59:53 -0000 Received: from smtp02.citrix.com (HELO SMTP02.CITRIX.COM) (66.165.176.63) by server-7.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 6 Jun 2014 09:59:53 -0000 X-IronPort-AV: E=Sophos;i="4.98,988,1392163200"; d="scan'208";a="139861292" Received: from accessns.citrite.net (HELO FTLPEX01CL03.citrite.net) ([10.9.154.239]) by FTLPIPO02.CITRIX.COM with ESMTP; 06 Jun 2014 09:59:52 +0000 Received: from kazak.uk.xensource.com (10.80.2.80) by FTLPEX01CL03.citrite.net (10.13.107.80) with Microsoft SMTP Server id 14.3.181.6; Fri, 6 Jun 2014 05:59:51 -0400 Message-ID: <1402048790.31120.33.camel@kazak.uk.xensource.com> From: Ian Campbell To: Date: Fri, 6 Jun 2014 10:59:50 +0100 In-Reply-To: <53905933.2040000@xen.org> References: <538CA4E3.40506@xen.org> <53905933.2040000@xen.org> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.12.2-1 MIME-Version: 1.0 X-Originating-IP: [10.80.2.80] X-DLP: MIA2 Cc: Russell Pavlicek , "xen-api@lists.xen.org" , "mirageos-devel@lists.xenproject.org" , "xen-devel@lists.xen.org" Subject: Re: [MirageOS-devel] [Xen-devel] [vote on timing] Xen Project Developer Meeting on August 20th AM in Chicago X-BeenThere: mirageos-devel@lists.xenproject.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 Thu, 2014-06-05 at 12:49 +0100, Lars Kurth wrote: > So what I am asking is for options: please vote > +1 "09:30 - 13:00" > +1 "10:30 - 14:00" > +1 "13:00 - 16:30" Unless lunch is to be provided I would prefer either 09:30-13:00 or 13:00-16:30. If lunch is provided then I don't have any particular preference, but I think you might not want the distraction of lunch during the middle proposed session (or you might want to extend it a bit to accommodate it). Ian. _______________________________________________ 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 Jun 06 10:00:01 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 06 Jun 2014 10:00: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 1WsqwG-0005Ei-8w; Fri, 06 Jun 2014 09:59:56 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WsqwF-0005ES-4X for mirageos-devel@lists.xenproject.org; Fri, 06 Jun 2014 09:59:55 +0000 Received: from [193.109.254.147:13183] by server-5.bemta-14.messagelabs.com id 51/68-26413-A1191935; Fri, 06 Jun 2014 09:59:54 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-7.tower-27.messagelabs.com!1402048792!9536436!1 X-Originating-IP: [66.165.176.63] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni42MyA9PiAzMDYwNDg=\n X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16713 invoked from network); 6 Jun 2014 09:59:53 -0000 Received: from smtp02.citrix.com (HELO SMTP02.CITRIX.COM) (66.165.176.63) by server-7.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 6 Jun 2014 09:59:53 -0000 X-IronPort-AV: E=Sophos;i="4.98,988,1392163200"; d="scan'208";a="139861292" Received: from accessns.citrite.net (HELO FTLPEX01CL03.citrite.net) ([10.9.154.239]) by FTLPIPO02.CITRIX.COM with ESMTP; 06 Jun 2014 09:59:52 +0000 Received: from kazak.uk.xensource.com (10.80.2.80) by FTLPEX01CL03.citrite.net (10.13.107.80) with Microsoft SMTP Server id 14.3.181.6; Fri, 6 Jun 2014 05:59:51 -0400 Message-ID: <1402048790.31120.33.camel@kazak.uk.xensource.com> From: Ian Campbell To: Date: Fri, 6 Jun 2014 10:59:50 +0100 In-Reply-To: <53905933.2040000@xen.org> References: <538CA4E3.40506@xen.org> <53905933.2040000@xen.org> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.12.2-1 MIME-Version: 1.0 X-Originating-IP: [10.80.2.80] X-DLP: MIA2 Cc: Russell Pavlicek , "xen-api@lists.xen.org" , "mirageos-devel@lists.xenproject.org" , "xen-devel@lists.xen.org" Subject: Re: [MirageOS-devel] [Xen-devel] [vote on timing] Xen Project Developer Meeting on August 20th AM in Chicago X-BeenThere: mirageos-devel@lists.xenproject.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 Thu, 2014-06-05 at 12:49 +0100, Lars Kurth wrote: > So what I am asking is for options: please vote > +1 "09:30 - 13:00" > +1 "10:30 - 14:00" > +1 "13:00 - 16:30" Unless lunch is to be provided I would prefer either 09:30-13:00 or 13:00-16:30. If lunch is provided then I don't have any particular preference, but I think you might not want the distraction of lunch during the middle proposed session (or you might want to extend it a bit to accommodate it). Ian. _______________________________________________ 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 Jun 06 11:31:33 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 06 Jun 2014 11:31: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 1WssMp-0001PG-S5; Fri, 06 Jun 2014 11:31:27 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WssMo-0001PB-9d for mirageos-devel@lists.xenproject.org; Fri, 06 Jun 2014 11:31:26 +0000 Received: from [85.158.137.68:13235] by server-8.bemta-3.messagelabs.com id 4E/7B-21547-D86A1935; Fri, 06 Jun 2014 11:31:25 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-9.tower-31.messagelabs.com!1402054284!4766677!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.1 required=7.0 tests=HTML_50_60,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 24587 invoked from network); 6 Jun 2014 11:31:24 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-9.tower-31.messagelabs.com with SMTP; 6 Jun 2014 11:31:24 -0000 Received: (qmail 18903 invoked by uid 634); 6 Jun 2014 11:31:23 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED,HTML_MESSAGE X-Spam-Check-By: dark.recoil.org Received: from global-1-30.nat.csx.cam.ac.uk (HELO dhcp-172-17-223-60.eduroam.lapwing.private.cam.ac.uk) (131.111.184.30) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Fri, 06 Jun 2014 12:31:22 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\)) From: Anil Madhavapeddy In-Reply-To: <2298736.WurJKiYHeE@agaric> Date: Fri, 6 Jun 2014 12:31:21 +0100 Message-Id: <1655D67C-31EC-4939-A4C3-5B9199EAFA2D@recoil.org> References: <463F65D7-9C75-458B-A046-99DBE57ACFBD@recoil.org> <2298736.WurJKiYHeE@agaric> To: Louis Gesbert X-Mailer: Apple Mail (2.1874) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: opam-devel@lists.ocaml.org, mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] [opam-devel] experimental opam bulk build logs on GitHub X-BeenThere: mirageos-devel@lists.xenproject.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="===============0226375400710097121==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============0226375400710097121== Content-Type: multipart/alternative; boundary="Apple-Mail=_4F0086F1-CF53-4AD9-967C-197D1EAD6B83" --Apple-Mail=_4F0086F1-CF53-4AD9-967C-197D1EAD6B83 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=iso-8859-1 I was discussing this very problem with Thomas in fact! Right now we = deliberately do a separate opam install for each package, and do not = cover depopts at all. The plan is to integrate the scripts into using Irmin to record the log = outputs, since git is hitting congestion collapse with >20 workers = (GitHub rejects the push due to another process having the lock). With = Irmin, we can record all the logs into a memory instance, and have one = pushing process to GitHub. When we do have Irmin support, we can calculate a static schedule of all = the packages that should be built, and just have spare CPUs pick up some = work. It would be great to build the risky packages (i.e. early up the = dependency chain) first, and then move to the leaf packages. I'm not sure if re-using packages and snapshotting is a good idea in = general, but it's very useful for common ones like ocamlfind, Lwt or = Core. Depopts are a big problem here though, particularly for Lwt... -anil On 23 May 2014, at 09:50, Louis Gesbert = wrote: > Very nice ! > =20 > I am wondering, do you 'opam install' every package individually ? We = may play some clever tricks with the solver here, like `opam upgrade = --criteria=3D-notuptodate,+new` which will attempt to install as many = packages as possible, after which we could iterate on a universe reduced = to the not-yet-installed packages. Depopts would be less predictable, = but we can't realistically test all possible combinations of those = anyway. > =20 > Would be nice to find a common place to aggregate such results. > =20 > Best, > Louis > =20 > =20 > Le mardi 20 mai 2014, 17:40:04 Anil Madhavapeddy a =E9crit : > > Hi, > >=20 > > I've written some scripts that use Docker and OPAM to run bulk = builds across the entire package repository, and the results are logged = and pushed to GitHub daily. > >=20 > > If anyone wants to improve the health of the repository, please look = at: > >=20 > > https://github.com/ocaml/opam-bulk-logs=20 > >=20 > > in the err/ directories, and submit pull requests fix the failures. > >=20 > > Source scripts are still in my personal GitHub; I'll move these to = the ocaml/ repo. > >=20 > > cheers, > > Anil > > _______________________________________________ > > opam-devel mailing list > > opam-devel@lists.ocaml.org > > http://lists.ocaml.org/listinfo/opam-devel > =20 > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --Apple-Mail=_4F0086F1-CF53-4AD9-967C-197D1EAD6B83 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=iso-8859-1 I was = discussing this very problem with Thomas in fact!  Right now we = deliberately do a separate opam install for each package, and do not = cover depopts at all.

The plan is to integrate the = scripts into using Irmin to record the log outputs, since git is hitting = congestion collapse with >20 workers (GitHub rejects the push due to = another process having the lock).  With Irmin, we can record all = the logs into a memory instance, and have one pushing process to = GitHub.

When we do have Irmin support, we can = calculate a static schedule of all the packages that should be built, = and just have spare CPUs pick up some work.  It would be great to = build the risky packages (i.e. early up the dependency chain) first, and = then move to the leaf packages.

I'm not sure if = re-using packages and snapshotting is a good idea in general, but it's = very useful for common ones like ocamlfind, Lwt or Core.  Depopts = are a big problem here though, particularly for = Lwt...

-anil

On 23 May = 2014, at 09:50, Louis Gesbert <louis.gesbert@ocamlpro.com&= gt; wrote:

Very nice !

 

I am wondering, do you 'opam install' = every package individually ? We may play some clever tricks with the = solver here, like `opam upgrade --criteria=3D-notuptodate,+new` which = will attempt to install as many packages as possible, after which we = could iterate on a universe reduced to the not-yet-installed packages. = Depopts would be less predictable, but we can't realistically test all = possible combinations of those anyway.

 

Would be = nice to find a common place to aggregate such results.

 

Best,
Louis

 

 

Le mardi 20 mai 2014, 17:40:04 Anil Madhavapeddy a = =E9crit :
> Hi,
>
> I've written some scripts = that use Docker and OPAM to run bulk builds across the entire package = repository, and the results are logged and pushed to GitHub = daily.
>
> If anyone wants to improve the = health of the repository, please look at:
>
>
> in the err/ directories, and submit = pull requests fix the failures.
>
> = Source scripts are still in my personal GitHub; I'll move these to the = ocaml/ repo.
>
> cheers,
> = Anil
> _______________________________________________
> = opam-devel mailing list

= --Apple-Mail=_4F0086F1-CF53-4AD9-967C-197D1EAD6B83-- --===============0226375400710097121== 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 --===============0226375400710097121==-- From mirageos-devel-bounces@lists.xenproject.org Fri Jun 06 11:31:33 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 06 Jun 2014 11:31: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 1WssMp-0001PG-S5; Fri, 06 Jun 2014 11:31:27 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WssMo-0001PB-9d for mirageos-devel@lists.xenproject.org; Fri, 06 Jun 2014 11:31:26 +0000 Received: from [85.158.137.68:13235] by server-8.bemta-3.messagelabs.com id 4E/7B-21547-D86A1935; Fri, 06 Jun 2014 11:31:25 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-9.tower-31.messagelabs.com!1402054284!4766677!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.1 required=7.0 tests=HTML_50_60,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 24587 invoked from network); 6 Jun 2014 11:31:24 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-9.tower-31.messagelabs.com with SMTP; 6 Jun 2014 11:31:24 -0000 Received: (qmail 18903 invoked by uid 634); 6 Jun 2014 11:31:23 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED,HTML_MESSAGE X-Spam-Check-By: dark.recoil.org Received: from global-1-30.nat.csx.cam.ac.uk (HELO dhcp-172-17-223-60.eduroam.lapwing.private.cam.ac.uk) (131.111.184.30) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Fri, 06 Jun 2014 12:31:22 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\)) From: Anil Madhavapeddy In-Reply-To: <2298736.WurJKiYHeE@agaric> Date: Fri, 6 Jun 2014 12:31:21 +0100 Message-Id: <1655D67C-31EC-4939-A4C3-5B9199EAFA2D@recoil.org> References: <463F65D7-9C75-458B-A046-99DBE57ACFBD@recoil.org> <2298736.WurJKiYHeE@agaric> To: Louis Gesbert X-Mailer: Apple Mail (2.1874) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: opam-devel@lists.ocaml.org, mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] [opam-devel] experimental opam bulk build logs on GitHub X-BeenThere: mirageos-devel@lists.xenproject.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="===============0226375400710097121==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============0226375400710097121== Content-Type: multipart/alternative; boundary="Apple-Mail=_4F0086F1-CF53-4AD9-967C-197D1EAD6B83" --Apple-Mail=_4F0086F1-CF53-4AD9-967C-197D1EAD6B83 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=iso-8859-1 I was discussing this very problem with Thomas in fact! Right now we = deliberately do a separate opam install for each package, and do not = cover depopts at all. The plan is to integrate the scripts into using Irmin to record the log = outputs, since git is hitting congestion collapse with >20 workers = (GitHub rejects the push due to another process having the lock). With = Irmin, we can record all the logs into a memory instance, and have one = pushing process to GitHub. When we do have Irmin support, we can calculate a static schedule of all = the packages that should be built, and just have spare CPUs pick up some = work. It would be great to build the risky packages (i.e. early up the = dependency chain) first, and then move to the leaf packages. I'm not sure if re-using packages and snapshotting is a good idea in = general, but it's very useful for common ones like ocamlfind, Lwt or = Core. Depopts are a big problem here though, particularly for Lwt... -anil On 23 May 2014, at 09:50, Louis Gesbert = wrote: > Very nice ! > =20 > I am wondering, do you 'opam install' every package individually ? We = may play some clever tricks with the solver here, like `opam upgrade = --criteria=3D-notuptodate,+new` which will attempt to install as many = packages as possible, after which we could iterate on a universe reduced = to the not-yet-installed packages. Depopts would be less predictable, = but we can't realistically test all possible combinations of those = anyway. > =20 > Would be nice to find a common place to aggregate such results. > =20 > Best, > Louis > =20 > =20 > Le mardi 20 mai 2014, 17:40:04 Anil Madhavapeddy a =E9crit : > > Hi, > >=20 > > I've written some scripts that use Docker and OPAM to run bulk = builds across the entire package repository, and the results are logged = and pushed to GitHub daily. > >=20 > > If anyone wants to improve the health of the repository, please look = at: > >=20 > > https://github.com/ocaml/opam-bulk-logs=20 > >=20 > > in the err/ directories, and submit pull requests fix the failures. > >=20 > > Source scripts are still in my personal GitHub; I'll move these to = the ocaml/ repo. > >=20 > > cheers, > > Anil > > _______________________________________________ > > opam-devel mailing list > > opam-devel@lists.ocaml.org > > http://lists.ocaml.org/listinfo/opam-devel > =20 > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --Apple-Mail=_4F0086F1-CF53-4AD9-967C-197D1EAD6B83 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=iso-8859-1 I was = discussing this very problem with Thomas in fact!  Right now we = deliberately do a separate opam install for each package, and do not = cover depopts at all.

The plan is to integrate the = scripts into using Irmin to record the log outputs, since git is hitting = congestion collapse with >20 workers (GitHub rejects the push due to = another process having the lock).  With Irmin, we can record all = the logs into a memory instance, and have one pushing process to = GitHub.

When we do have Irmin support, we can = calculate a static schedule of all the packages that should be built, = and just have spare CPUs pick up some work.  It would be great to = build the risky packages (i.e. early up the dependency chain) first, and = then move to the leaf packages.

I'm not sure if = re-using packages and snapshotting is a good idea in general, but it's = very useful for common ones like ocamlfind, Lwt or Core.  Depopts = are a big problem here though, particularly for = Lwt...

-anil

On 23 May = 2014, at 09:50, Louis Gesbert <louis.gesbert@ocamlpro.com&= gt; wrote:

Very nice !

 

I am wondering, do you 'opam install' = every package individually ? We may play some clever tricks with the = solver here, like `opam upgrade --criteria=3D-notuptodate,+new` which = will attempt to install as many packages as possible, after which we = could iterate on a universe reduced to the not-yet-installed packages. = Depopts would be less predictable, but we can't realistically test all = possible combinations of those anyway.

 

Would be = nice to find a common place to aggregate such results.

 

Best,
Louis

 

 

Le mardi 20 mai 2014, 17:40:04 Anil Madhavapeddy a = =E9crit :
> Hi,
>
> I've written some scripts = that use Docker and OPAM to run bulk builds across the entire package = repository, and the results are logged and pushed to GitHub = daily.
>
> If anyone wants to improve the = health of the repository, please look at:
>
>
> in the err/ directories, and submit = pull requests fix the failures.
>
> = Source scripts are still in my personal GitHub; I'll move these to the = ocaml/ repo.
>
> cheers,
> = Anil
> _______________________________________________
> = opam-devel mailing list

= --Apple-Mail=_4F0086F1-CF53-4AD9-967C-197D1EAD6B83-- --===============0226375400710097121== 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 --===============0226375400710097121==-- From mirageos-devel-bounces@lists.xenproject.org Sun Jun 08 17:56:15 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 08 Jun 2014 17:56: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 1WthKD-0005Zc-FB; Sun, 08 Jun 2014 17:56:09 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WthKC-0005ZU-9e for mirageos-devel@lists.xenproject.org; Sun, 08 Jun 2014 17:56:08 +0000 Received: from [193.109.254.147:50609] by server-5.bemta-14.messagelabs.com id 3A/B8-26413-7B3A4935; Sun, 08 Jun 2014 17:56:07 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-6.tower-27.messagelabs.com!1402250163!9860312!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 18693 invoked from network); 8 Jun 2014 17:56:03 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-6.tower-27.messagelabs.com with SMTP; 8 Jun 2014 17:56:03 -0000 Received: (qmail 32294 invoked by uid 634); 8 Jun 2014 17:56:02 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net (HELO [192.168.1.113]) (86.30.244.239) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Sun, 08 Jun 2014 18:56:02 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\)) From: Anil Madhavapeddy In-Reply-To: <4C839828-07A3-4497-9602-738CD48F34E4@gazagnaire.org> Date: Sun, 8 Jun 2014 18:56:00 +0100 Message-Id: References: <4C839828-07A3-4497-9602-738CD48F34E4@gazagnaire.org> To: Thomas Gazagnaire X-Mailer: Apple Mail (2.1874) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] irmin graphs X-BeenThere: mirageos-devel@lists.xenproject.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 graphing is really nice! Is there a small README in the examples/ directory about how to use the 'intrusion' examples btw? Would be useful for demos :-) I'm curious to see what this looks like when booting a VM with the new IrminXenstore that Dave's been working on, too. cheers, Anil On 30 May 2014, at 18:44, Thomas Gazagnaire wrote: > Hi all, > > I've just added a new option to display pretty graphs of any irmin database. It's not yet merged, but if some people wants to give a try, it's available here: https://github.com/mirage/irmin/pull/61 (or on the cleaner-graphs branch in my repo). > > To try it: > > mkdir > cd > git init > echo hello > foo && git add foo && git commit -a -m first > irmin init -d -g & > > The last command means: starts an irmin daemon reading the current Git store. The daemon runs by default on localhost:8080 (irmin init --help to change that). > > Then you can see graph.dot of you database at that url: http://localhost:8080/dump/graph.dot > > You can also see a lively updated JS interpretation of that file (using dagre-d3.js) at http://localhost:8080/dump (ie. try to run few git commands and see how the graph changes). > > If any CSS guru are reading this, and what to have a try at improving the result (which I found already quite nice), feel free to send me patches to lib/server/static/style.css > > Remark: don't try this on a normal Git repo, seems that dagre-d3.js dies when trying to parse a gigantic .dot file. > > Best, > Thomas > > > > _______________________________________________ > 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 Jun 08 17:56:15 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 08 Jun 2014 17:56: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 1WthKD-0005Zc-FB; Sun, 08 Jun 2014 17:56:09 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WthKC-0005ZU-9e for mirageos-devel@lists.xenproject.org; Sun, 08 Jun 2014 17:56:08 +0000 Received: from [193.109.254.147:50609] by server-5.bemta-14.messagelabs.com id 3A/B8-26413-7B3A4935; Sun, 08 Jun 2014 17:56:07 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-6.tower-27.messagelabs.com!1402250163!9860312!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 18693 invoked from network); 8 Jun 2014 17:56:03 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-6.tower-27.messagelabs.com with SMTP; 8 Jun 2014 17:56:03 -0000 Received: (qmail 32294 invoked by uid 634); 8 Jun 2014 17:56:02 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net (HELO [192.168.1.113]) (86.30.244.239) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Sun, 08 Jun 2014 18:56:02 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\)) From: Anil Madhavapeddy In-Reply-To: <4C839828-07A3-4497-9602-738CD48F34E4@gazagnaire.org> Date: Sun, 8 Jun 2014 18:56:00 +0100 Message-Id: References: <4C839828-07A3-4497-9602-738CD48F34E4@gazagnaire.org> To: Thomas Gazagnaire X-Mailer: Apple Mail (2.1874) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] irmin graphs X-BeenThere: mirageos-devel@lists.xenproject.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 graphing is really nice! Is there a small README in the examples/ directory about how to use the 'intrusion' examples btw? Would be useful for demos :-) I'm curious to see what this looks like when booting a VM with the new IrminXenstore that Dave's been working on, too. cheers, Anil On 30 May 2014, at 18:44, Thomas Gazagnaire wrote: > Hi all, > > I've just added a new option to display pretty graphs of any irmin database. It's not yet merged, but if some people wants to give a try, it's available here: https://github.com/mirage/irmin/pull/61 (or on the cleaner-graphs branch in my repo). > > To try it: > > mkdir > cd > git init > echo hello > foo && git add foo && git commit -a -m first > irmin init -d -g & > > The last command means: starts an irmin daemon reading the current Git store. The daemon runs by default on localhost:8080 (irmin init --help to change that). > > Then you can see graph.dot of you database at that url: http://localhost:8080/dump/graph.dot > > You can also see a lively updated JS interpretation of that file (using dagre-d3.js) at http://localhost:8080/dump (ie. try to run few git commands and see how the graph changes). > > If any CSS guru are reading this, and what to have a try at improving the result (which I found already quite nice), feel free to send me patches to lib/server/static/style.css > > Remark: don't try this on a normal Git repo, seems that dagre-d3.js dies when trying to parse a gigantic .dot file. > > Best, > Thomas > > > > _______________________________________________ > 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 Jun 08 18:13:40 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 08 Jun 2014 18:13: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 1Wthb8-0005nX-V3; Sun, 08 Jun 2014 18:13:38 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Wthb7-0005nS-4v for mirageos-devel@lists.xenproject.org; Sun, 08 Jun 2014 18:13:37 +0000 Received: from [193.109.254.147:61148] by server-5.bemta-14.messagelabs.com id 97/0F-26413-0D7A4935; Sun, 08 Jun 2014 18:13:36 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-8.tower-27.messagelabs.com!1402251215!9892580!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25161 invoked from network); 8 Jun 2014 18:13:35 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-8.tower-27.messagelabs.com with SMTP; 8 Jun 2014 18:13:35 -0000 Received: (qmail 3953 invoked by uid 634); 8 Jun 2014 18:13:35 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net (HELO [192.168.1.113]) (86.30.244.239) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Sun, 08 Jun 2014 19:13:34 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\)) From: Anil Madhavapeddy In-Reply-To: <538C9FB9.7070001@somerandomidiot.com> Date: Sun, 8 Jun 2014 19:13:33 +0100 Message-Id: <912BC56B-F927-4CDE-9C1E-D40BBD8A79CE@recoil.org> References: <537A1EAD.5090906@somerandomidiot.com> <538C9FB9.7070001@somerandomidiot.com> To: Mindy , Balraj Singh X-Mailer: Apple Mail (2.1874) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] OPW intern checking in! X-BeenThere: mirageos-devel@lists.xenproject.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 Jun 2014, at 17:00, Mindy wrote: > Hi, folks! Here's a quick summary of what I've been up to > > Late last week: dug more into observed lack of FINs from listening unikernels, found the problem, and submitted a pull request to mirage-tcpip This had Balraj and me scratching our collective heads about how it regressed, since we're *sure* it used to work (famous last words :-). Balraj, any thoughts about it after your Friday investigations? This does highlight the importance of getting a regression test infrastructure for networking in place though, since TCPIP in particular is a very interlocked protocol. Any thoughts you may have about this using scapy would be interesting... Meanwhile, I've released it as tcpip.1.1.3 into OPAM: https://github.com/ocaml/opam-repository/pull/2207 > Today: make blog post on looking into that readable by humans who wish not to be bored to death; finish unit test for upstream error reporting in a `test_net_lwt` module in lib_test; send PR for error condition unit tests to Cohttp upstream; fuzz harder! I'm still untangling Cohttp and Conduit to push releases out. My deadline is to have some of the more obvious bugfixes done before the Mirage call on Tuesday... -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 Sun Jun 08 18:13:40 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 08 Jun 2014 18:13: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 1Wthb8-0005nX-V3; Sun, 08 Jun 2014 18:13:38 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Wthb7-0005nS-4v for mirageos-devel@lists.xenproject.org; Sun, 08 Jun 2014 18:13:37 +0000 Received: from [193.109.254.147:61148] by server-5.bemta-14.messagelabs.com id 97/0F-26413-0D7A4935; Sun, 08 Jun 2014 18:13:36 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-8.tower-27.messagelabs.com!1402251215!9892580!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25161 invoked from network); 8 Jun 2014 18:13:35 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-8.tower-27.messagelabs.com with SMTP; 8 Jun 2014 18:13:35 -0000 Received: (qmail 3953 invoked by uid 634); 8 Jun 2014 18:13:35 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net (HELO [192.168.1.113]) (86.30.244.239) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Sun, 08 Jun 2014 19:13:34 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\)) From: Anil Madhavapeddy In-Reply-To: <538C9FB9.7070001@somerandomidiot.com> Date: Sun, 8 Jun 2014 19:13:33 +0100 Message-Id: <912BC56B-F927-4CDE-9C1E-D40BBD8A79CE@recoil.org> References: <537A1EAD.5090906@somerandomidiot.com> <538C9FB9.7070001@somerandomidiot.com> To: Mindy , Balraj Singh X-Mailer: Apple Mail (2.1874) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] OPW intern checking in! X-BeenThere: mirageos-devel@lists.xenproject.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 Jun 2014, at 17:00, Mindy wrote: > Hi, folks! Here's a quick summary of what I've been up to > > Late last week: dug more into observed lack of FINs from listening unikernels, found the problem, and submitted a pull request to mirage-tcpip This had Balraj and me scratching our collective heads about how it regressed, since we're *sure* it used to work (famous last words :-). Balraj, any thoughts about it after your Friday investigations? This does highlight the importance of getting a regression test infrastructure for networking in place though, since TCPIP in particular is a very interlocked protocol. Any thoughts you may have about this using scapy would be interesting... Meanwhile, I've released it as tcpip.1.1.3 into OPAM: https://github.com/ocaml/opam-repository/pull/2207 > Today: make blog post on looking into that readable by humans who wish not to be bored to death; finish unit test for upstream error reporting in a `test_net_lwt` module in lib_test; send PR for error condition unit tests to Cohttp upstream; fuzz harder! I'm still untangling Cohttp and Conduit to push releases out. My deadline is to have some of the more obvious bugfixes done before the Mirage call on Tuesday... -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 Sun Jun 08 19:00:02 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 08 Jun 2014 19:00: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 1WtiJz-0006C0-0h; Sun, 08 Jun 2014 18:59:59 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WtiJx-0006Bv-C1 for mirageos-devel@lists.xenproject.org; Sun, 08 Jun 2014 18:59:57 +0000 Received: from [85.158.143.35:62832] by server-3.bemta-4.messagelabs.com id AB/AD-13602-CA2B4935; Sun, 08 Jun 2014 18:59:56 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-11.tower-21.messagelabs.com!1402253995!9970295!1 X-Originating-IP: [209.85.212.169] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31844 invoked from network); 8 Jun 2014 18:59:55 -0000 Received: from mail-wi0-f169.google.com (HELO mail-wi0-f169.google.com) (209.85.212.169) by server-11.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 8 Jun 2014 18:59:55 -0000 Received: by mail-wi0-f169.google.com with SMTP id hi2so998097wib.4 for ; Sun, 08 Jun 2014 11:59:55 -0700 (PDT) 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=lktM2A4QNuneLaY6EwAkWMoWxUqosf1Oef38JOsxXMY=; b=0NR178w2OQK7/zAeP25XPqg/jfRRJRojrTgngUADgwmQj5VQ6TvhRkM2xFphKI/P2/ jNEbhz9PJWyvDr8Flunx5FBna1F0S5Zpk/cLF7DzRMelz+1v/1NDTP0ly/S+uZLi61Hu hju0myuE60zBqSMfsu9OBheIcMg+Hbz1UOsVBhwotCUyySQUQSTwk5PmDJUSKfH17GXm /Ea0FbxgWtqUtNPGPU2YDv3VVspMJlBOavuCNJ6Qs5rN8MJEMLqxQn0zVqKUbKldP2fA s0oXialDOKDS/6sxd4Vud0uBS6CUNhzuQXSMT3on17H/SKj4ipYBrFslz+PZfUU5P5cy 2CAg== X-Received: by 10.194.8.6 with SMTP id n6mr24964987wja.31.1402253995287; Sun, 08 Jun 2014 11:59:55 -0700 (PDT) Received: from [192.168.0.8] (cpc25-cmbg14-2-0-cust121.5-4.cable.virginm.net. [213.106.112.122]) by mx.google.com with ESMTPSA id y10sm10319158wix.24.2014.06.08.11.59.53 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 08 Jun 2014 11:59:53 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\)) From: Thomas Gazagnaire In-Reply-To: Date: Sun, 8 Jun 2014 19:59:51 +0100 Message-Id: <139DAAC0-0B28-41F7-8BB4-19BE28091D40@gazagnaire.org> References: <4C839828-07A3-4497-9602-738CD48F34E4@gazagnaire.org> To: Anil Madhavapeddy X-Mailer: Apple Mail (2.1878.2) Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] irmin graphs X-BeenThere: mirageos-devel@lists.xenproject.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 graphing is really nice! Is there a small README in the examples/ directory about how to use the 'intrusion' examples btw? Would be useful for demos :-) not yet, I'll add it shortly (I want to get the native git pull/push integrated first). to run the demo: mkdir -p /tmp/irmin/test cd /tmp/irmin/test && irmin init -d -g open your browser to http://localhost:8080/dump?depth=0 in the irmin folder, run: ./intrusion.native provision ./intrusion.native configure ./intrusion.native attack You can vary the depth parameter if you want to see more history. Not sure how this is useful in real-life, but feel to make it more shiny :-) Thomas > I'm curious to see what this looks like when booting a VM with the new IrminXenstore that Dave's been working on, too. I guess pretty messy ... > > cheers, > Anil > > On 30 May 2014, at 18:44, Thomas Gazagnaire wrote: > >> Hi all, >> >> I've just added a new option to display pretty graphs of any irmin database. It's not yet merged, but if some people wants to give a try, it's available here: https://github.com/mirage/irmin/pull/61 (or on the cleaner-graphs branch in my repo). >> >> To try it: >> >> mkdir >> cd >> git init >> echo hello > foo && git add foo && git commit -a -m first >> irmin init -d -g & >> >> The last command means: starts an irmin daemon reading the current Git store. The daemon runs by default on localhost:8080 (irmin init --help to change that). >> >> Then you can see graph.dot of you database at that url: http://localhost:8080/dump/graph.dot >> >> You can also see a lively updated JS interpretation of that file (using dagre-d3.js) at http://localhost:8080/dump (ie. try to run few git commands and see how the graph changes). >> >> If any CSS guru are reading this, and what to have a try at improving the result (which I found already quite nice), feel free to send me patches to lib/server/static/style.css >> >> Remark: don't try this on a normal Git repo, seems that dagre-d3.js dies when trying to parse a gigantic .dot file. >> >> Best, >> Thomas >> >> >> >> _______________________________________________ >> 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 Jun 08 19:00:02 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 08 Jun 2014 19:00: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 1WtiJz-0006C0-0h; Sun, 08 Jun 2014 18:59:59 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WtiJx-0006Bv-C1 for mirageos-devel@lists.xenproject.org; Sun, 08 Jun 2014 18:59:57 +0000 Received: from [85.158.143.35:62832] by server-3.bemta-4.messagelabs.com id AB/AD-13602-CA2B4935; Sun, 08 Jun 2014 18:59:56 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-11.tower-21.messagelabs.com!1402253995!9970295!1 X-Originating-IP: [209.85.212.169] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31844 invoked from network); 8 Jun 2014 18:59:55 -0000 Received: from mail-wi0-f169.google.com (HELO mail-wi0-f169.google.com) (209.85.212.169) by server-11.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 8 Jun 2014 18:59:55 -0000 Received: by mail-wi0-f169.google.com with SMTP id hi2so998097wib.4 for ; Sun, 08 Jun 2014 11:59:55 -0700 (PDT) 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=lktM2A4QNuneLaY6EwAkWMoWxUqosf1Oef38JOsxXMY=; b=0NR178w2OQK7/zAeP25XPqg/jfRRJRojrTgngUADgwmQj5VQ6TvhRkM2xFphKI/P2/ jNEbhz9PJWyvDr8Flunx5FBna1F0S5Zpk/cLF7DzRMelz+1v/1NDTP0ly/S+uZLi61Hu hju0myuE60zBqSMfsu9OBheIcMg+Hbz1UOsVBhwotCUyySQUQSTwk5PmDJUSKfH17GXm /Ea0FbxgWtqUtNPGPU2YDv3VVspMJlBOavuCNJ6Qs5rN8MJEMLqxQn0zVqKUbKldP2fA s0oXialDOKDS/6sxd4Vud0uBS6CUNhzuQXSMT3on17H/SKj4ipYBrFslz+PZfUU5P5cy 2CAg== X-Received: by 10.194.8.6 with SMTP id n6mr24964987wja.31.1402253995287; Sun, 08 Jun 2014 11:59:55 -0700 (PDT) Received: from [192.168.0.8] (cpc25-cmbg14-2-0-cust121.5-4.cable.virginm.net. [213.106.112.122]) by mx.google.com with ESMTPSA id y10sm10319158wix.24.2014.06.08.11.59.53 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 08 Jun 2014 11:59:53 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\)) From: Thomas Gazagnaire In-Reply-To: Date: Sun, 8 Jun 2014 19:59:51 +0100 Message-Id: <139DAAC0-0B28-41F7-8BB4-19BE28091D40@gazagnaire.org> References: <4C839828-07A3-4497-9602-738CD48F34E4@gazagnaire.org> To: Anil Madhavapeddy X-Mailer: Apple Mail (2.1878.2) Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] irmin graphs X-BeenThere: mirageos-devel@lists.xenproject.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 graphing is really nice! Is there a small README in the examples/ directory about how to use the 'intrusion' examples btw? Would be useful for demos :-) not yet, I'll add it shortly (I want to get the native git pull/push integrated first). to run the demo: mkdir -p /tmp/irmin/test cd /tmp/irmin/test && irmin init -d -g open your browser to http://localhost:8080/dump?depth=0 in the irmin folder, run: ./intrusion.native provision ./intrusion.native configure ./intrusion.native attack You can vary the depth parameter if you want to see more history. Not sure how this is useful in real-life, but feel to make it more shiny :-) Thomas > I'm curious to see what this looks like when booting a VM with the new IrminXenstore that Dave's been working on, too. I guess pretty messy ... > > cheers, > Anil > > On 30 May 2014, at 18:44, Thomas Gazagnaire wrote: > >> Hi all, >> >> I've just added a new option to display pretty graphs of any irmin database. It's not yet merged, but if some people wants to give a try, it's available here: https://github.com/mirage/irmin/pull/61 (or on the cleaner-graphs branch in my repo). >> >> To try it: >> >> mkdir >> cd >> git init >> echo hello > foo && git add foo && git commit -a -m first >> irmin init -d -g & >> >> The last command means: starts an irmin daemon reading the current Git store. The daemon runs by default on localhost:8080 (irmin init --help to change that). >> >> Then you can see graph.dot of you database at that url: http://localhost:8080/dump/graph.dot >> >> You can also see a lively updated JS interpretation of that file (using dagre-d3.js) at http://localhost:8080/dump (ie. try to run few git commands and see how the graph changes). >> >> If any CSS guru are reading this, and what to have a try at improving the result (which I found already quite nice), feel free to send me patches to lib/server/static/style.css >> >> Remark: don't try this on a normal Git repo, seems that dagre-d3.js dies when trying to parse a gigantic .dot file. >> >> Best, >> Thomas >> >> >> >> _______________________________________________ >> 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 Jun 09 08:01:02 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 09 Jun 2014 08: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 1WtuVk-0001aD-3X; Mon, 09 Jun 2014 08:00:56 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WtuVi-0001a8-Sy for mirageos-devel@lists.xenproject.org; Mon, 09 Jun 2014 08:00:55 +0000 Received: from [193.109.254.147:7824] by server-15.bemta-14.messagelabs.com id BF/E2-15813-6B965935; Mon, 09 Jun 2014 08:00:54 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-15.tower-27.messagelabs.com!1402300853!9958942!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.3 required=7.0 tests=MAILTO_TO_SPAM_ADDR X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2808 invoked from network); 9 Jun 2014 08:00:53 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-15.tower-27.messagelabs.com with SMTP; 9 Jun 2014 08:00:53 -0000 Received: (qmail 17440 invoked by uid 634); 9 Jun 2014 08:00:52 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net (HELO [192.168.1.113]) (86.30.244.239) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Mon, 09 Jun 2014 09:00:52 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\)) From: Anil Madhavapeddy In-Reply-To: <9E4CC3B4-B2D9-4A19-8A87-5B88106CDDEC@nottingham.ac.uk> Date: Mon, 9 Jun 2014 09:00:51 +0100 Message-Id: References: <3cdd336ae2656bf8a249f2bb3bf67ab1@cam.ac.uk> <9E4CC3B4-B2D9-4A19-8A87-5B88106CDDEC@nottingham.ac.uk> To: Richard Mortier X-Mailer: Apple Mail (2.1874) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Vagrant Cloud X-BeenThere: mirageos-devel@lists.xenproject.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 [CCing mirageos-devel] I've set up blobs.openmirage.org on Rackspace with 20GB of storage, so we can use that for big files. It would be nice to auto-rebuild these Vagrant boxes -- is there a 'make' target in that repo I can use to do so? The other thing I'll look into setting up here is a 0install target as well. Thomas(L), do you have any scaffolding for an OPAM 0install? I can use that to make a Mirage 0install publish target. cheers, Anil On 6 Jun 2014, at 11:00, Richard Mortier wrote: > ask for a quota increase? > > used to be the case that reasonable requests for <= 50% increase were fulfilled without any particular issue... > > (though of course there may be more appropriate server points or pushing it somewhere in the cloud might be appropriate...) > > On 6 Jun 2014, at 10:44, Nik Sultana wrote: > >> Hi Anil and Richard, I re-ran the workflow and packaged up the Mirage VM >> as a basebox. I created an account on Vagrant Cloud to try it out. Boxes >> can be provided in 2 ways: >> - uploading, but this requires payment >> - via an URL. >> >> I was going to try the second option, by uploading the box to my CL >> webspace, but unfortunately its size (797MB) exceeds my quote (c500MB). >> >> Is there some other filespace I could use for this? >> >> Best, >> Nik > > > -- > Cheers, > > R. > > > > _______________________________________________ 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 Jun 09 08:01:02 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 09 Jun 2014 08: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 1WtuVk-0001aD-3X; Mon, 09 Jun 2014 08:00:56 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WtuVi-0001a8-Sy for mirageos-devel@lists.xenproject.org; Mon, 09 Jun 2014 08:00:55 +0000 Received: from [193.109.254.147:7824] by server-15.bemta-14.messagelabs.com id BF/E2-15813-6B965935; Mon, 09 Jun 2014 08:00:54 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-15.tower-27.messagelabs.com!1402300853!9958942!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.3 required=7.0 tests=MAILTO_TO_SPAM_ADDR X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2808 invoked from network); 9 Jun 2014 08:00:53 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-15.tower-27.messagelabs.com with SMTP; 9 Jun 2014 08:00:53 -0000 Received: (qmail 17440 invoked by uid 634); 9 Jun 2014 08:00:52 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net (HELO [192.168.1.113]) (86.30.244.239) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Mon, 09 Jun 2014 09:00:52 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\)) From: Anil Madhavapeddy In-Reply-To: <9E4CC3B4-B2D9-4A19-8A87-5B88106CDDEC@nottingham.ac.uk> Date: Mon, 9 Jun 2014 09:00:51 +0100 Message-Id: References: <3cdd336ae2656bf8a249f2bb3bf67ab1@cam.ac.uk> <9E4CC3B4-B2D9-4A19-8A87-5B88106CDDEC@nottingham.ac.uk> To: Richard Mortier X-Mailer: Apple Mail (2.1874) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Vagrant Cloud X-BeenThere: mirageos-devel@lists.xenproject.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 [CCing mirageos-devel] I've set up blobs.openmirage.org on Rackspace with 20GB of storage, so we can use that for big files. It would be nice to auto-rebuild these Vagrant boxes -- is there a 'make' target in that repo I can use to do so? The other thing I'll look into setting up here is a 0install target as well. Thomas(L), do you have any scaffolding for an OPAM 0install? I can use that to make a Mirage 0install publish target. cheers, Anil On 6 Jun 2014, at 11:00, Richard Mortier wrote: > ask for a quota increase? > > used to be the case that reasonable requests for <= 50% increase were fulfilled without any particular issue... > > (though of course there may be more appropriate server points or pushing it somewhere in the cloud might be appropriate...) > > On 6 Jun 2014, at 10:44, Nik Sultana wrote: > >> Hi Anil and Richard, I re-ran the workflow and packaged up the Mirage VM >> as a basebox. I created an account on Vagrant Cloud to try it out. Boxes >> can be provided in 2 ways: >> - uploading, but this requires payment >> - via an URL. >> >> I was going to try the second option, by uploading the box to my CL >> webspace, but unfortunately its size (797MB) exceeds my quote (c500MB). >> >> Is there some other filespace I could use for this? >> >> Best, >> Nik > > > -- > Cheers, > > R. > > > > _______________________________________________ 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 Jun 09 08:47:34 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 09 Jun 2014 08:47: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 1WtvEo-0002PK-9m; Mon, 09 Jun 2014 08:47:30 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WtvEm-0002PB-OI for mirageos-devel@lists.xenproject.org; Mon, 09 Jun 2014 08:47:29 +0000 Received: from [85.158.143.35:8080] by server-3.bemta-4.messagelabs.com id 8B/B0-13602-0A475935; Mon, 09 Jun 2014 08:47:28 +0000 X-Env-Sender: talex5@gmail.com X-Msg-Ref: server-8.tower-21.messagelabs.com!1402303645!10081791!1 X-Originating-IP: [209.85.219.44] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, ML_RADAR_SPEW_LINKS_23, ML_RADAR_SPEW_LINKS_32, RCVD_BY_IP, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30826 invoked from network); 9 Jun 2014 08:47:27 -0000 Received: from mail-oa0-f44.google.com (HELO mail-oa0-f44.google.com) (209.85.219.44) by server-8.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 9 Jun 2014 08:47:27 -0000 Received: by mail-oa0-f44.google.com with SMTP id i7so794299oag.3 for ; Mon, 09 Jun 2014 01:47:25 -0700 (PDT) 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=XnSBqcZ/pNaRIVepBA2e1NVKK816E0SyjVOxnzlQWOs=; b=FtD79+UM3YUZImUWcIV8TIdVuqFxVqA50N2ceTXqMtgtGvGFdUuu80qujUFniMZwqA 4mNjUoHnmXaGvGpoD0HwNYCxHnBkj9vM1YK6nJpOowaBgVJX/jeFMxVNHsILp1IzkRXt Dh+EGJaSJ0aSgmttKlXX/hLaIwxfEpRb9wOpiOx8ZpnV+uCCK00FvVL/gEirM5uKH+i6 mZ+/SnBEIxhc5mPVyznsu3vPmAbAfeJFbO+zPAA46C1ulrIKchYp9sO+WhBGFeJnAyHg hPXB2pQeZgWcBOxDLijVFZ+YP0sdhjWwGMIhcsdov+qK44Lq7HQOaLLltf4tmnxvZ0EY 76TA== MIME-Version: 1.0 X-Received: by 10.182.251.170 with SMTP id zl10mr22618795obc.5.1402303645447; Mon, 09 Jun 2014 01:47:25 -0700 (PDT) Received: by 10.76.101.202 with HTTP; Mon, 9 Jun 2014 01:47:25 -0700 (PDT) In-Reply-To: References: <3cdd336ae2656bf8a249f2bb3bf67ab1@cam.ac.uk> <9E4CC3B4-B2D9-4A19-8A87-5B88106CDDEC@nottingham.ac.uk> Date: Mon, 9 Jun 2014 09:47:25 +0100 Message-ID: From: Thomas Leonard To: Anil Madhavapeddy Content-Type: multipart/mixed; boundary=001a11c2003ea7d24f04fb634255 Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Vagrant Cloud X-BeenThere: mirageos-devel@lists.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 --001a11c2003ea7d24f04fb634255 Content-Type: text/plain; charset=UTF-8 On 9 June 2014 09:00, Anil Madhavapeddy wrote: > [CCing mirageos-devel] > > I've set up blobs.openmirage.org on Rackspace with 20GB of storage, so we can use that for big files. > > It would be nice to auto-rebuild these Vagrant boxes -- is there a 'make' target in that repo I can use to do so? > > The other thing I'll look into setting up here is a 0install target as well. Thomas(L), do you have any scaffolding for an OPAM 0install? I can use that to make a Mirage 0install publish target. I'm not sure what you mean here: do you want to publish Mirage or OPAM binaries through 0install? I've attached templates for both (for test.roscidus.com - edit as appropriate). For OPAM, create a .tar.bz2 containing an executable binary called "opam" (and any license files, etc). Then create the XML with 0template[1]: $ 0template opam.xml.template version=1.1.1 arch=Linux-x86_64 Test like this: $ 0launch ./opam-1.1.1.xml usage: opam [--version] ... To publish: $ 0repo add opam-1.1.1.xml People can then get opam like this: $ 0install add opam http://test.roscidus.com/opam.xml $ opam --version 1.1.1 I didn't list any dependencies, but they can be added if needed. mir-console.xml.template is for publishing Unix binaries. You need to create a .tar.bz2 containing the binary (not the symlink!), then do: $ 0template mir-console.xml.template arch=Linux-x86_64 version=0.1 $ 0repo add mir-console-0.1.xml Then someone can run it with: $ 0launch http://test.roscidus.com/mir-console.xml hello ... For the Xen image, use "arch=Xen-x86_64" and modify the path to mir-console.xen or mir-console.xl. It's not completely clear what to do about the xl file. In the demo I gave, the xl file was in the archive and I passed it directly to "xl create". But that means trusting the package's configuration in your dom0, which isn't very sensible. We should probably write some kind of launcher so you can do something like $ 0xl add hello http://test.roscidus.com/mir-console.xml $ 0xl run hello Maybe it could prompt about disk and network requirements or take them as arguments. [1] http://0install.net/0template.html [2] http://0install.net/0repo.html -- 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 --001a11c2003ea7d24f04fb634255 Content-Type: application/octet-stream; name="mir-console.xml.template" Content-Disposition: attachment; filename="mir-console.xml.template" Content-Transfer-Encoding: base64 X-Attachment-Id: f_hw7ijmlk0 PD94bWwgdmVyc2lvbj0iMS4wIj8+CjxpbnRlcmZhY2UgeG1sbnM9Imh0dHA6Ly96ZXJvLWluc3Rh bGwuc291cmNlZm9yZ2UubmV0LzIwMDQvaW5qZWN0b3IvaW50ZXJmYWNlIj4KICA8bmFtZT5taXIt Y29uc29sZTwvbmFtZT4KICA8c3VtbWFyeT5oZWxsbyB3b3JsZCBkZW1vIGZvciBNaXJhZ2U8L3N1 bW1hcnk+CiAgPGhvbWVwYWdlPmh0dHA6Ly9vcGVubWlyYWdlLm9yZy93aWtpL2hlbGxvLXdvcmxk PC9ob21lcGFnZT4KICA8ZmVlZC1mb3IgaW50ZXJmYWNlPSJodHRwOi8vdGVzdC5yb3NjaWR1cy5j b20vbWlyLWNvbnNvbGUueG1sIi8+CgogIDxncm91cCBsaWNlbnNlPSJQdWJsaWMgRG9tYWluIj4K ICAgIDxjb21tYW5kIG5hbWU9InJ1biIgcGF0aD0ibWlyLWNvbnNvbGUiLz4KCiAgICA8aW1wbGVt ZW50YXRpb24gYXJjaD0ie2FyY2h9IiB2ZXJzaW9uPSJ7dmVyc2lvbn0iPgogICAgICA8bWFuaWZl c3QtZGlnZXN0Lz4KICAgICAgPGFyY2hpdmUgaHJlZj0ibWlyLWNvbnNvbGUte3ZlcnNpb259LnRh ci5iejIiLz4KICAgIDwvaW1wbGVtZW50YXRpb24+CiAgPC9ncm91cD4KPC9pbnRlcmZhY2U+Cg== --001a11c2003ea7d24f04fb634255 Content-Type: application/octet-stream; name="opam.xml.template" Content-Disposition: attachment; filename="opam.xml.template" Content-Transfer-Encoding: base64 X-Attachment-Id: f_hw7iweij1 PD94bWwgdmVyc2lvbj0iMS4wIj8+CjxpbnRlcmZhY2UgeG1sbnM9Imh0dHA6Ly96ZXJvLWluc3Rh bGwuc291cmNlZm9yZ2UubmV0LzIwMDQvaW5qZWN0b3IvaW50ZXJmYWNlIj4KICA8bmFtZT5PUEFN PC9uYW1lPgogIDxzdW1tYXJ5Pk9DYW1sIHBhY2thZ2UgbWFuYWdlcjwvc3VtbWFyeT4KCiAgPGRl c2NyaXB0aW9uPgogICAgT1BBTSBpcyBhbiBvcGVuLXNvdXJjZSBwYWNrYWdlIG1hbmFnZXIgZWRp dGVkIGJ5IE9DYW1sUHJvLiBJdCBzdXBwb3J0cyBtdWx0aXBsZSBzaW11bHRhbmVvdXMgY29tcGls ZXIgaW5zdGFsbGF0aW9ucywgZmxleGlibGUgcGFja2FnZSBjb25zdHJhaW50cywgYW5kIGEgR2l0 LWZyaWVuZGx5IGRldmVsb3BtZW50IHdvcmtmbG93LgogIDwvZGVzY3JpcHRpb24+CgogIDxob21l cGFnZT5odHRwOi8vb3BhbS5vY2FtbHByby5jb20vPC9ob21lcGFnZT4KCiAgPGZlZWQtZm9yIGlu dGVyZmFjZT0iaHR0cDovL3Rlc3Qucm9zY2lkdXMuY29tL29wYW0ueG1sIi8+CgogIDxncm91cCBs aWNlbnNlPSJPU0kgQXBwcm92ZWQgOjogR05VIExlc3NlciBHZW5lcmFsIFB1YmxpYyBMaWNlbnNl IChMR1BMKSI+CiAgICA8Y29tbWFuZCBuYW1lPSJydW4iIHBhdGg9Im9wYW0iLz4KCiAgICA8aW1w bGVtZW50YXRpb24gYXJjaD0ie2FyY2h9IiB2ZXJzaW9uPSJ7dmVyc2lvbn0iPgogICAgICA8bWFu aWZlc3QtZGlnZXN0Lz4KICAgICAgPGFyY2hpdmUgaHJlZj0ib3BhbS17YXJjaH0te3ZlcnNpb259 LnRneiIvPgogICAgPC9pbXBsZW1lbnRhdGlvbj4KICA8L2dyb3VwPgo8L2ludGVyZmFjZT4K --001a11c2003ea7d24f04fb634255 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 --001a11c2003ea7d24f04fb634255-- From mirageos-devel-bounces@lists.xenproject.org Mon Jun 09 08:47:34 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 09 Jun 2014 08:47: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 1WtvEo-0002PK-9m; Mon, 09 Jun 2014 08:47:30 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WtvEm-0002PB-OI for mirageos-devel@lists.xenproject.org; Mon, 09 Jun 2014 08:47:29 +0000 Received: from [85.158.143.35:8080] by server-3.bemta-4.messagelabs.com id 8B/B0-13602-0A475935; Mon, 09 Jun 2014 08:47:28 +0000 X-Env-Sender: talex5@gmail.com X-Msg-Ref: server-8.tower-21.messagelabs.com!1402303645!10081791!1 X-Originating-IP: [209.85.219.44] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, ML_RADAR_SPEW_LINKS_23, ML_RADAR_SPEW_LINKS_32, RCVD_BY_IP, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30826 invoked from network); 9 Jun 2014 08:47:27 -0000 Received: from mail-oa0-f44.google.com (HELO mail-oa0-f44.google.com) (209.85.219.44) by server-8.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 9 Jun 2014 08:47:27 -0000 Received: by mail-oa0-f44.google.com with SMTP id i7so794299oag.3 for ; Mon, 09 Jun 2014 01:47:25 -0700 (PDT) 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=XnSBqcZ/pNaRIVepBA2e1NVKK816E0SyjVOxnzlQWOs=; b=FtD79+UM3YUZImUWcIV8TIdVuqFxVqA50N2ceTXqMtgtGvGFdUuu80qujUFniMZwqA 4mNjUoHnmXaGvGpoD0HwNYCxHnBkj9vM1YK6nJpOowaBgVJX/jeFMxVNHsILp1IzkRXt Dh+EGJaSJ0aSgmttKlXX/hLaIwxfEpRb9wOpiOx8ZpnV+uCCK00FvVL/gEirM5uKH+i6 mZ+/SnBEIxhc5mPVyznsu3vPmAbAfeJFbO+zPAA46C1ulrIKchYp9sO+WhBGFeJnAyHg hPXB2pQeZgWcBOxDLijVFZ+YP0sdhjWwGMIhcsdov+qK44Lq7HQOaLLltf4tmnxvZ0EY 76TA== MIME-Version: 1.0 X-Received: by 10.182.251.170 with SMTP id zl10mr22618795obc.5.1402303645447; Mon, 09 Jun 2014 01:47:25 -0700 (PDT) Received: by 10.76.101.202 with HTTP; Mon, 9 Jun 2014 01:47:25 -0700 (PDT) In-Reply-To: References: <3cdd336ae2656bf8a249f2bb3bf67ab1@cam.ac.uk> <9E4CC3B4-B2D9-4A19-8A87-5B88106CDDEC@nottingham.ac.uk> Date: Mon, 9 Jun 2014 09:47:25 +0100 Message-ID: From: Thomas Leonard To: Anil Madhavapeddy Content-Type: multipart/mixed; boundary=001a11c2003ea7d24f04fb634255 Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Vagrant Cloud X-BeenThere: mirageos-devel@lists.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 --001a11c2003ea7d24f04fb634255 Content-Type: text/plain; charset=UTF-8 On 9 June 2014 09:00, Anil Madhavapeddy wrote: > [CCing mirageos-devel] > > I've set up blobs.openmirage.org on Rackspace with 20GB of storage, so we can use that for big files. > > It would be nice to auto-rebuild these Vagrant boxes -- is there a 'make' target in that repo I can use to do so? > > The other thing I'll look into setting up here is a 0install target as well. Thomas(L), do you have any scaffolding for an OPAM 0install? I can use that to make a Mirage 0install publish target. I'm not sure what you mean here: do you want to publish Mirage or OPAM binaries through 0install? I've attached templates for both (for test.roscidus.com - edit as appropriate). For OPAM, create a .tar.bz2 containing an executable binary called "opam" (and any license files, etc). Then create the XML with 0template[1]: $ 0template opam.xml.template version=1.1.1 arch=Linux-x86_64 Test like this: $ 0launch ./opam-1.1.1.xml usage: opam [--version] ... To publish: $ 0repo add opam-1.1.1.xml People can then get opam like this: $ 0install add opam http://test.roscidus.com/opam.xml $ opam --version 1.1.1 I didn't list any dependencies, but they can be added if needed. mir-console.xml.template is for publishing Unix binaries. You need to create a .tar.bz2 containing the binary (not the symlink!), then do: $ 0template mir-console.xml.template arch=Linux-x86_64 version=0.1 $ 0repo add mir-console-0.1.xml Then someone can run it with: $ 0launch http://test.roscidus.com/mir-console.xml hello ... For the Xen image, use "arch=Xen-x86_64" and modify the path to mir-console.xen or mir-console.xl. It's not completely clear what to do about the xl file. In the demo I gave, the xl file was in the archive and I passed it directly to "xl create". But that means trusting the package's configuration in your dom0, which isn't very sensible. We should probably write some kind of launcher so you can do something like $ 0xl add hello http://test.roscidus.com/mir-console.xml $ 0xl run hello Maybe it could prompt about disk and network requirements or take them as arguments. [1] http://0install.net/0template.html [2] http://0install.net/0repo.html -- 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 --001a11c2003ea7d24f04fb634255 Content-Type: application/octet-stream; name="mir-console.xml.template" Content-Disposition: attachment; filename="mir-console.xml.template" Content-Transfer-Encoding: base64 X-Attachment-Id: f_hw7ijmlk0 PD94bWwgdmVyc2lvbj0iMS4wIj8+CjxpbnRlcmZhY2UgeG1sbnM9Imh0dHA6Ly96ZXJvLWluc3Rh bGwuc291cmNlZm9yZ2UubmV0LzIwMDQvaW5qZWN0b3IvaW50ZXJmYWNlIj4KICA8bmFtZT5taXIt Y29uc29sZTwvbmFtZT4KICA8c3VtbWFyeT5oZWxsbyB3b3JsZCBkZW1vIGZvciBNaXJhZ2U8L3N1 bW1hcnk+CiAgPGhvbWVwYWdlPmh0dHA6Ly9vcGVubWlyYWdlLm9yZy93aWtpL2hlbGxvLXdvcmxk PC9ob21lcGFnZT4KICA8ZmVlZC1mb3IgaW50ZXJmYWNlPSJodHRwOi8vdGVzdC5yb3NjaWR1cy5j b20vbWlyLWNvbnNvbGUueG1sIi8+CgogIDxncm91cCBsaWNlbnNlPSJQdWJsaWMgRG9tYWluIj4K ICAgIDxjb21tYW5kIG5hbWU9InJ1biIgcGF0aD0ibWlyLWNvbnNvbGUiLz4KCiAgICA8aW1wbGVt ZW50YXRpb24gYXJjaD0ie2FyY2h9IiB2ZXJzaW9uPSJ7dmVyc2lvbn0iPgogICAgICA8bWFuaWZl c3QtZGlnZXN0Lz4KICAgICAgPGFyY2hpdmUgaHJlZj0ibWlyLWNvbnNvbGUte3ZlcnNpb259LnRh ci5iejIiLz4KICAgIDwvaW1wbGVtZW50YXRpb24+CiAgPC9ncm91cD4KPC9pbnRlcmZhY2U+Cg== --001a11c2003ea7d24f04fb634255 Content-Type: application/octet-stream; name="opam.xml.template" Content-Disposition: attachment; filename="opam.xml.template" Content-Transfer-Encoding: base64 X-Attachment-Id: f_hw7iweij1 PD94bWwgdmVyc2lvbj0iMS4wIj8+CjxpbnRlcmZhY2UgeG1sbnM9Imh0dHA6Ly96ZXJvLWluc3Rh bGwuc291cmNlZm9yZ2UubmV0LzIwMDQvaW5qZWN0b3IvaW50ZXJmYWNlIj4KICA8bmFtZT5PUEFN PC9uYW1lPgogIDxzdW1tYXJ5Pk9DYW1sIHBhY2thZ2UgbWFuYWdlcjwvc3VtbWFyeT4KCiAgPGRl c2NyaXB0aW9uPgogICAgT1BBTSBpcyBhbiBvcGVuLXNvdXJjZSBwYWNrYWdlIG1hbmFnZXIgZWRp dGVkIGJ5IE9DYW1sUHJvLiBJdCBzdXBwb3J0cyBtdWx0aXBsZSBzaW11bHRhbmVvdXMgY29tcGls ZXIgaW5zdGFsbGF0aW9ucywgZmxleGlibGUgcGFja2FnZSBjb25zdHJhaW50cywgYW5kIGEgR2l0 LWZyaWVuZGx5IGRldmVsb3BtZW50IHdvcmtmbG93LgogIDwvZGVzY3JpcHRpb24+CgogIDxob21l cGFnZT5odHRwOi8vb3BhbS5vY2FtbHByby5jb20vPC9ob21lcGFnZT4KCiAgPGZlZWQtZm9yIGlu dGVyZmFjZT0iaHR0cDovL3Rlc3Qucm9zY2lkdXMuY29tL29wYW0ueG1sIi8+CgogIDxncm91cCBs aWNlbnNlPSJPU0kgQXBwcm92ZWQgOjogR05VIExlc3NlciBHZW5lcmFsIFB1YmxpYyBMaWNlbnNl IChMR1BMKSI+CiAgICA8Y29tbWFuZCBuYW1lPSJydW4iIHBhdGg9Im9wYW0iLz4KCiAgICA8aW1w bGVtZW50YXRpb24gYXJjaD0ie2FyY2h9IiB2ZXJzaW9uPSJ7dmVyc2lvbn0iPgogICAgICA8bWFu aWZlc3QtZGlnZXN0Lz4KICAgICAgPGFyY2hpdmUgaHJlZj0ib3BhbS17YXJjaH0te3ZlcnNpb259 LnRneiIvPgogICAgPC9pbXBsZW1lbnRhdGlvbj4KICA8L2dyb3VwPgo8L2ludGVyZmFjZT4K --001a11c2003ea7d24f04fb634255 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 --001a11c2003ea7d24f04fb634255-- From mirageos-devel-bounces@lists.xenproject.org Mon Jun 09 09:10:21 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 09 Jun 2014 09:10: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 1Wtvau-00037Z-2w; Mon, 09 Jun 2014 09:10:20 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Wtvas-00037U-83 for mirageos-devel@lists.xenproject.org; Mon, 09 Jun 2014 09:10:18 +0000 Received: from [85.158.139.211:19561] by server-17.bemta-5.messagelabs.com id 3F/7A-09046-9F975935; Mon, 09 Jun 2014 09:10:17 +0000 X-Env-Sender: ns441@cam.ac.uk X-Msg-Ref: server-8.tower-206.messagelabs.com!1402305016!8793775!1 X-Originating-IP: [131.111.8.141] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTMxLjExMS44LjE0MSA9PiAxNTQ4NjI=\n X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11984 invoked from network); 9 Jun 2014 09:10:16 -0000 Received: from ppsw-41.csi.cam.ac.uk (HELO ppsw-41.csi.cam.ac.uk) (131.111.8.141) by server-8.tower-206.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 9 Jun 2014 09:10:16 -0000 X-Cam-AntiVirus: no malware found X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/ Received: from webmail-2a.csi.cam.ac.uk ([131.111.9.34]:47449) by ppsw-41.csi.cam.ac.uk (ppsw.cam.ac.uk [131.111.8.137]:25) with esmtp id 1Wtvaq-0000LY-Qo (Exim 4.82_3-c0e5623) (return-path ); Mon, 09 Jun 2014 10:10:16 +0100 Received: from [127.0.0.1] (helo=webmail-2.hermes.cam.ac.uk) by webmail-2a.csi.cam.ac.uk with esmtp id 1Wtvaq-000tb8-7G (Exim 4.80_167-5a66dd3) (return-path ); Mon, 09 Jun 2014 10:10:16 +0100 Received: from dhcp-172-17-152-60.eduroam.lapwing.private.cam.ac.uk ([172.17.152.60]) by webmail-2.hermes.cam.ac.uk with HTTP (HTTP/1.1 POST); Mon, 09 Jun 2014 10:10:16 +0100 MIME-Version: 1.0 X-Authenticated-User: ns441 Date: Mon, 09 Jun 2014 10:10:16 +0100 From: Nik Sultana To: Anil Madhavapeddy In-Reply-To: References: <3cdd336ae2656bf8a249f2bb3bf67ab1@cam.ac.uk> <9E4CC3B4-B2D9-4A19-8A87-5B88106CDDEC@nottingham.ac.uk> Message-ID: X-Sender: ns441@cam.ac.uk User-Agent: Roundcube Webmail/0.9.4 Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Vagrant Cloud X-BeenThere: mirageos-devel@lists.xenproject.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 On 2014-06-09 09:00, Anil Madhavapeddy wrote: > [CCing mirageos-devel] > > I've set up blobs.openmirage.org on Rackspace with 20GB of storage, so > we can use that for big files. > Awesome! > It would be nice to auto-rebuild these Vagrant boxes -- is there a > 'make' target in that repo I can use to do so? Not yet. To get going, I could write a build.sh that consisted of stringing together the building instructions. I reran the workflow at the end of last week to re-check it. Is there a way I could upload the resulting box to the blobs space, to see if it flies on Vagrant Cloud? Best, Nik > > The other thing I'll look into setting up here is a 0install target as > well. Thomas(L), do you have any scaffolding for an OPAM 0install? I > can use that to make a Mirage 0install publish target. > > cheers, > Anil > > On 6 Jun 2014, at 11:00, Richard Mortier > wrote: > >> ask for a quota increase? >> >> used to be the case that reasonable requests for <= 50% increase were >> fulfilled without any particular issue... >> >> (though of course there may be more appropriate server points or >> pushing it somewhere in the cloud might be appropriate...) >> >> On 6 Jun 2014, at 10:44, Nik Sultana wrote: >> >>> Hi Anil and Richard, I re-ran the workflow and packaged up the Mirage >>> VM >>> as a basebox. I created an account on Vagrant Cloud to try it out. >>> Boxes >>> can be provided in 2 ways: >>> - uploading, but this requires payment >>> - via an URL. >>> >>> I was going to try the second option, by uploading the box to my CL >>> webspace, but unfortunately its size (797MB) exceeds my quote >>> (c500MB). >>> >>> Is there some other filespace I could use for this? >>> >>> Best, >>> Nik >> >> >> -- >> Cheers, >> >> R. >> >> >> >> _______________________________________________ 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 Jun 09 09:10:21 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 09 Jun 2014 09:10: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 1Wtvau-00037Z-2w; Mon, 09 Jun 2014 09:10:20 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Wtvas-00037U-83 for mirageos-devel@lists.xenproject.org; Mon, 09 Jun 2014 09:10:18 +0000 Received: from [85.158.139.211:19561] by server-17.bemta-5.messagelabs.com id 3F/7A-09046-9F975935; Mon, 09 Jun 2014 09:10:17 +0000 X-Env-Sender: ns441@cam.ac.uk X-Msg-Ref: server-8.tower-206.messagelabs.com!1402305016!8793775!1 X-Originating-IP: [131.111.8.141] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTMxLjExMS44LjE0MSA9PiAxNTQ4NjI=\n X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11984 invoked from network); 9 Jun 2014 09:10:16 -0000 Received: from ppsw-41.csi.cam.ac.uk (HELO ppsw-41.csi.cam.ac.uk) (131.111.8.141) by server-8.tower-206.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 9 Jun 2014 09:10:16 -0000 X-Cam-AntiVirus: no malware found X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/ Received: from webmail-2a.csi.cam.ac.uk ([131.111.9.34]:47449) by ppsw-41.csi.cam.ac.uk (ppsw.cam.ac.uk [131.111.8.137]:25) with esmtp id 1Wtvaq-0000LY-Qo (Exim 4.82_3-c0e5623) (return-path ); Mon, 09 Jun 2014 10:10:16 +0100 Received: from [127.0.0.1] (helo=webmail-2.hermes.cam.ac.uk) by webmail-2a.csi.cam.ac.uk with esmtp id 1Wtvaq-000tb8-7G (Exim 4.80_167-5a66dd3) (return-path ); Mon, 09 Jun 2014 10:10:16 +0100 Received: from dhcp-172-17-152-60.eduroam.lapwing.private.cam.ac.uk ([172.17.152.60]) by webmail-2.hermes.cam.ac.uk with HTTP (HTTP/1.1 POST); Mon, 09 Jun 2014 10:10:16 +0100 MIME-Version: 1.0 X-Authenticated-User: ns441 Date: Mon, 09 Jun 2014 10:10:16 +0100 From: Nik Sultana To: Anil Madhavapeddy In-Reply-To: References: <3cdd336ae2656bf8a249f2bb3bf67ab1@cam.ac.uk> <9E4CC3B4-B2D9-4A19-8A87-5B88106CDDEC@nottingham.ac.uk> Message-ID: X-Sender: ns441@cam.ac.uk User-Agent: Roundcube Webmail/0.9.4 Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Vagrant Cloud X-BeenThere: mirageos-devel@lists.xenproject.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 On 2014-06-09 09:00, Anil Madhavapeddy wrote: > [CCing mirageos-devel] > > I've set up blobs.openmirage.org on Rackspace with 20GB of storage, so > we can use that for big files. > Awesome! > It would be nice to auto-rebuild these Vagrant boxes -- is there a > 'make' target in that repo I can use to do so? Not yet. To get going, I could write a build.sh that consisted of stringing together the building instructions. I reran the workflow at the end of last week to re-check it. Is there a way I could upload the resulting box to the blobs space, to see if it flies on Vagrant Cloud? Best, Nik > > The other thing I'll look into setting up here is a 0install target as > well. Thomas(L), do you have any scaffolding for an OPAM 0install? I > can use that to make a Mirage 0install publish target. > > cheers, > Anil > > On 6 Jun 2014, at 11:00, Richard Mortier > wrote: > >> ask for a quota increase? >> >> used to be the case that reasonable requests for <= 50% increase were >> fulfilled without any particular issue... >> >> (though of course there may be more appropriate server points or >> pushing it somewhere in the cloud might be appropriate...) >> >> On 6 Jun 2014, at 10:44, Nik Sultana wrote: >> >>> Hi Anil and Richard, I re-ran the workflow and packaged up the Mirage >>> VM >>> as a basebox. I created an account on Vagrant Cloud to try it out. >>> Boxes >>> can be provided in 2 ways: >>> - uploading, but this requires payment >>> - via an URL. >>> >>> I was going to try the second option, by uploading the box to my CL >>> webspace, but unfortunately its size (797MB) exceeds my quote >>> (c500MB). >>> >>> Is there some other filespace I could use for this? >>> >>> Best, >>> Nik >> >> >> -- >> Cheers, >> >> R. >> >> >> >> _______________________________________________ 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 Jun 09 11:16:47 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 09 Jun 2014 11:16: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 1WtxZD-0006nZ-NY; Mon, 09 Jun 2014 11:16:43 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WtxZC-0006nS-Dp for mirageos-devel@lists.xenproject.org; Mon, 09 Jun 2014 11:16:42 +0000 Received: from [85.158.143.35:29231] by server-2.bemta-4.messagelabs.com id 08/F4-06539-99795935; Mon, 09 Jun 2014 11:16:41 +0000 X-Env-Sender: jjl25@cam.ac.uk X-Msg-Ref: server-14.tower-21.messagelabs.com!1402312601!10130420!1 X-Originating-IP: [131.111.8.141] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTMxLjExMS44LjE0MSA9PiAxNTQ4NjI=\n X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10606 invoked from network); 9 Jun 2014 11:16:41 -0000 Received: from ppsw-41.csi.cam.ac.uk (HELO ppsw-41.csi.cam.ac.uk) (131.111.8.141) by server-14.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 9 Jun 2014 11:16:41 -0000 X-Cam-AntiVirus: no malware found X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/ Received: from [185.25.64.249] (port=10101 helo=[10.80.3.75]) by ppsw-41.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.157]:587) with esmtpsa (PLAIN:jjl25) (TLSv1:DHE-RSA-AES128-SHA:128) id 1WtxZA-0001sl-SM (Exim 4.82_3-c0e5623) for mirageos-devel@lists.xenproject.org (return-path ); Mon, 09 Jun 2014 12:16:40 +0100 Message-ID: <53959798.3020308@cam.ac.uk> Date: Mon, 09 Jun 2014 12:16:40 +0100 From: Jon Ludlam User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: mirageos-devel@lists.xenproject.org References: <3cdd336ae2656bf8a249f2bb3bf67ab1@cam.ac.uk> <9E4CC3B4-B2D9-4A19-8A87-5B88106CDDEC@nottingham.ac.uk> In-Reply-To: Subject: Re: [MirageOS-devel] Vagrant Cloud X-BeenThere: mirageos-devel@lists.xenproject.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 09/06/14 10:10, Nik Sultana wrote: > On 2014-06-09 09:00, Anil Madhavapeddy wrote: > >> It would be nice to auto-rebuild these Vagrant boxes -- is there a >> 'make' target in that repo I can use to do so? > > Not yet. To get going, I could write a build.sh that consisted of > stringing together the building instructions. I reran the workflow at > the end of last week to re-check it. Is there a way I could upload the > resulting box to the blobs space, to see if it flies on Vagrant Cloud? > For automating Vagrant box setup, packer.io is the new veewee it seems. I've used it to automate creation of XenServer vagrant boxes, and it works really really well. Jon _______________________________________________ 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 Jun 09 11:16:47 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 09 Jun 2014 11:16: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 1WtxZD-0006nZ-NY; Mon, 09 Jun 2014 11:16:43 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WtxZC-0006nS-Dp for mirageos-devel@lists.xenproject.org; Mon, 09 Jun 2014 11:16:42 +0000 Received: from [85.158.143.35:29231] by server-2.bemta-4.messagelabs.com id 08/F4-06539-99795935; Mon, 09 Jun 2014 11:16:41 +0000 X-Env-Sender: jjl25@cam.ac.uk X-Msg-Ref: server-14.tower-21.messagelabs.com!1402312601!10130420!1 X-Originating-IP: [131.111.8.141] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTMxLjExMS44LjE0MSA9PiAxNTQ4NjI=\n X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10606 invoked from network); 9 Jun 2014 11:16:41 -0000 Received: from ppsw-41.csi.cam.ac.uk (HELO ppsw-41.csi.cam.ac.uk) (131.111.8.141) by server-14.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 9 Jun 2014 11:16:41 -0000 X-Cam-AntiVirus: no malware found X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/ Received: from [185.25.64.249] (port=10101 helo=[10.80.3.75]) by ppsw-41.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.157]:587) with esmtpsa (PLAIN:jjl25) (TLSv1:DHE-RSA-AES128-SHA:128) id 1WtxZA-0001sl-SM (Exim 4.82_3-c0e5623) for mirageos-devel@lists.xenproject.org (return-path ); Mon, 09 Jun 2014 12:16:40 +0100 Message-ID: <53959798.3020308@cam.ac.uk> Date: Mon, 09 Jun 2014 12:16:40 +0100 From: Jon Ludlam User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: mirageos-devel@lists.xenproject.org References: <3cdd336ae2656bf8a249f2bb3bf67ab1@cam.ac.uk> <9E4CC3B4-B2D9-4A19-8A87-5B88106CDDEC@nottingham.ac.uk> In-Reply-To: Subject: Re: [MirageOS-devel] Vagrant Cloud X-BeenThere: mirageos-devel@lists.xenproject.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 09/06/14 10:10, Nik Sultana wrote: > On 2014-06-09 09:00, Anil Madhavapeddy wrote: > >> It would be nice to auto-rebuild these Vagrant boxes -- is there a >> 'make' target in that repo I can use to do so? > > Not yet. To get going, I could write a build.sh that consisted of > stringing together the building instructions. I reran the workflow at > the end of last week to re-check it. Is there a way I could upload the > resulting box to the blobs space, to see if it flies on Vagrant Cloud? > For automating Vagrant box setup, packer.io is the new veewee it seems. I've used it to automate creation of XenServer vagrant boxes, and it works really really well. Jon _______________________________________________ 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 Jun 09 13:10:15 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 09 Jun 2014 13:10: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 1WtzL3-0004gC-09; Mon, 09 Jun 2014 13:10:13 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WtzL1-0004fm-Ip for mirageos-devel@lists.xenproject.org; Mon, 09 Jun 2014 13:10:11 +0000 Received: from [85.158.143.35:49108] by server-3.bemta-4.messagelabs.com id 1F/14-13602-232B5935; Mon, 09 Jun 2014 13:10:10 +0000 X-Env-Sender: ns441@cam.ac.uk X-Msg-Ref: server-14.tower-21.messagelabs.com!1402319410!10163384!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.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29416 invoked from network); 9 Jun 2014 13:10:10 -0000 Received: from ppsw-51.csi.cam.ac.uk (HELO ppsw-51.csi.cam.ac.uk) (131.111.8.151) by server-14.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 9 Jun 2014 13:10:10 -0000 X-Cam-AntiVirus: no malware found X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/ Received: from webmail-2a.csi.cam.ac.uk ([131.111.9.34]:51073) by ppsw-51.csi.cam.ac.uk (ppsw.cam.ac.uk [131.111.8.139]:25) with esmtp id 1WtzL0-0006mp-Wc (Exim 4.82_3-c0e5623) (return-path ); Mon, 09 Jun 2014 14:10:10 +0100 Received: from [127.0.0.1] (helo=webmail-2.hermes.cam.ac.uk) by webmail-2a.csi.cam.ac.uk with esmtp id 1WtzL0-000uzB-0a (Exim 4.80_167-5a66dd3) (return-path ); Mon, 09 Jun 2014 14:10:10 +0100 Received: from dhcp-172-17-152-60.eduroam.lapwing.private.cam.ac.uk ([172.17.152.60]) by webmail-2.hermes.cam.ac.uk with HTTP (HTTP/1.1 POST); Mon, 09 Jun 2014 14:10:10 +0100 MIME-Version: 1.0 X-Authenticated-User: ns441 Date: Mon, 09 Jun 2014 14:10:10 +0100 From: Nik Sultana To: Jon Ludlam In-Reply-To: <53959798.3020308@cam.ac.uk> References: "\"<3cdd336ae2656bf8a249f2bb3bf67ab1@cam.ac.uk>" <9E4CC3B4-B2D9-4A19-8A87-5B88106CDDEC@nottingham.ac.uk>" <53959798.3020308@cam.ac.uk> Message-ID: <14eb11d9725d61a0daf0c079d49ca0b1@cam.ac.uk> X-Sender: ns441@cam.ac.uk User-Agent: Roundcube Webmail/0.9.4 Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Vagrant Cloud X-BeenThere: mirageos-devel@lists.xenproject.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 Thanks for the input Jon. I could try using packer's tool [1] to translate from the veewee spec. Have you come across a useful/exemplary description of a workflow that uses packer.io? Best, Nik [1] http://www.packer.io/docs/templates/veewee-to-packer.html On 2014-06-09 12:16, Jon Ludlam wrote: > On 09/06/14 10:10, Nik Sultana wrote: >> On 2014-06-09 09:00, Anil Madhavapeddy wrote: >> >>> It would be nice to auto-rebuild these Vagrant boxes -- is there a >>> 'make' target in that repo I can use to do so? >> >> Not yet. To get going, I could write a build.sh that consisted of >> stringing together the building instructions. I reran the workflow at >> the end of last week to re-check it. Is there a way I could upload the >> resulting box to the blobs space, to see if it flies on Vagrant Cloud? >> > For automating Vagrant box setup, packer.io is the new veewee it seems. > I've used it to automate creation of XenServer vagrant boxes, and it > works really really well. > > Jon > > > _______________________________________________ > 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 Jun 09 13:10:15 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 09 Jun 2014 13:10: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 1WtzL3-0004gC-09; Mon, 09 Jun 2014 13:10:13 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WtzL1-0004fm-Ip for mirageos-devel@lists.xenproject.org; Mon, 09 Jun 2014 13:10:11 +0000 Received: from [85.158.143.35:49108] by server-3.bemta-4.messagelabs.com id 1F/14-13602-232B5935; Mon, 09 Jun 2014 13:10:10 +0000 X-Env-Sender: ns441@cam.ac.uk X-Msg-Ref: server-14.tower-21.messagelabs.com!1402319410!10163384!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.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29416 invoked from network); 9 Jun 2014 13:10:10 -0000 Received: from ppsw-51.csi.cam.ac.uk (HELO ppsw-51.csi.cam.ac.uk) (131.111.8.151) by server-14.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 9 Jun 2014 13:10:10 -0000 X-Cam-AntiVirus: no malware found X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/ Received: from webmail-2a.csi.cam.ac.uk ([131.111.9.34]:51073) by ppsw-51.csi.cam.ac.uk (ppsw.cam.ac.uk [131.111.8.139]:25) with esmtp id 1WtzL0-0006mp-Wc (Exim 4.82_3-c0e5623) (return-path ); Mon, 09 Jun 2014 14:10:10 +0100 Received: from [127.0.0.1] (helo=webmail-2.hermes.cam.ac.uk) by webmail-2a.csi.cam.ac.uk with esmtp id 1WtzL0-000uzB-0a (Exim 4.80_167-5a66dd3) (return-path ); Mon, 09 Jun 2014 14:10:10 +0100 Received: from dhcp-172-17-152-60.eduroam.lapwing.private.cam.ac.uk ([172.17.152.60]) by webmail-2.hermes.cam.ac.uk with HTTP (HTTP/1.1 POST); Mon, 09 Jun 2014 14:10:10 +0100 MIME-Version: 1.0 X-Authenticated-User: ns441 Date: Mon, 09 Jun 2014 14:10:10 +0100 From: Nik Sultana To: Jon Ludlam In-Reply-To: <53959798.3020308@cam.ac.uk> References: "\"<3cdd336ae2656bf8a249f2bb3bf67ab1@cam.ac.uk>" <9E4CC3B4-B2D9-4A19-8A87-5B88106CDDEC@nottingham.ac.uk>" <53959798.3020308@cam.ac.uk> Message-ID: <14eb11d9725d61a0daf0c079d49ca0b1@cam.ac.uk> X-Sender: ns441@cam.ac.uk User-Agent: Roundcube Webmail/0.9.4 Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Vagrant Cloud X-BeenThere: mirageos-devel@lists.xenproject.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 Thanks for the input Jon. I could try using packer's tool [1] to translate from the veewee spec. Have you come across a useful/exemplary description of a workflow that uses packer.io? Best, Nik [1] http://www.packer.io/docs/templates/veewee-to-packer.html On 2014-06-09 12:16, Jon Ludlam wrote: > On 09/06/14 10:10, Nik Sultana wrote: >> On 2014-06-09 09:00, Anil Madhavapeddy wrote: >> >>> It would be nice to auto-rebuild these Vagrant boxes -- is there a >>> 'make' target in that repo I can use to do so? >> >> Not yet. To get going, I could write a build.sh that consisted of >> stringing together the building instructions. I reran the workflow at >> the end of last week to re-check it. Is there a way I could upload the >> resulting box to the blobs space, to see if it flies on Vagrant Cloud? >> > For automating Vagrant box setup, packer.io is the new veewee it seems. > I've used it to automate creation of XenServer vagrant boxes, and it > works really really well. > > Jon > > > _______________________________________________ > 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 Jun 09 13:49:03 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 09 Jun 2014 13:49: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 1Wtzwa-00061h-Rq; Mon, 09 Jun 2014 13:49:00 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WtzwY-00060G-Tz for mirageos-devel@lists.xenproject.org; Mon, 09 Jun 2014 13:48:59 +0000 Received: from [85.158.143.35:11742] by server-3.bemta-4.messagelabs.com id B7/54-13602-A4BB5935; Mon, 09 Jun 2014 13:48:58 +0000 X-Env-Sender: Dave.Scott@citrix.com X-Msg-Ref: server-14.tower-21.messagelabs.com!1402321737!10176353!1 X-Originating-IP: [185.25.65.24] X-SpamReason: No, hits=0.3 required=7.0 tests=MAILTO_TO_SPAM_ADDR X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 13791 invoked from network); 9 Jun 2014 13:48:57 -0000 Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (185.25.65.24) by server-14.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 9 Jun 2014 13:48:57 -0000 X-IronPort-AV: E=Sophos;i="4.98,1002,1392163200"; d="scan'208";a="20615301" Received: from unknown (HELO AMSPEX01CL01.citrite.net) ([10.69.60.9]) by AMSPIP01.EU.Citrix.com with ESMTP; 09 Jun 2014 13:48:57 +0000 Received: from AMSPEX01CL03.citrite.net ([169.254.8.89]) by AMSPEX01CL01.citrite.net ([169.254.6.105]) with mapi id 14.03.0181.006; Mon, 9 Jun 2014 15:48:57 +0200 From: Dave Scott To: Nik Sultana Thread-Topic: [MirageOS-devel] Vagrant Cloud Thread-Index: AQHPg7j4c8oAc19hBEGGHhOcFShOy5toXEgAgAAjUQCAAB+2AIAACtOA Date: Mon, 9 Jun 2014 13:48:56 +0000 Message-ID: <9F7DD918-C84D-4303-9F43-BD5AB897CE58@citrix.com> References: "\"<3cdd336ae2656bf8a249f2bb3bf67ab1@cam.ac.uk>" <9E4CC3B4-B2D9-4A19-8A87-5B88106CDDEC@nottingham.ac.uk>" <53959798.3020308@cam.ac.uk> <14eb11d9725d61a0daf0c079d49ca0b1@cam.ac.uk> In-Reply-To: <14eb11d9725d61a0daf0c079d49ca0b1@cam.ac.uk> Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.13.107.79] Content-ID: MIME-Version: 1.0 X-DLP: AMS1 Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Vagrant Cloud X-BeenThere: mirageos-devel@lists.xenproject.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, On 9 Jun 2014, at 14:10, Nik Sultana wrote: > Thanks for the input Jon. I could try using packer's tool [1] to translat= e from the veewee spec. Have you come across a useful/exemplary description= of a workflow that uses packer.io? > Best, > Nik > = > [1] http://www.packer.io/docs/templates/veewee-to-packer.html > = > On 2014-06-09 12:16, Jon Ludlam wrote: >> On 09/06/14 10:10, Nik Sultana wrote: >>> On 2014-06-09 09:00, Anil Madhavapeddy wrote: >>>> It would be nice to auto-rebuild these Vagrant boxes -- is there a >>>> 'make' target in that repo I can use to do so? >>> Not yet. To get going, I could write a build.sh that consisted of >>> stringing together the building instructions. I reran the workflow at >>> the end of last week to re-check it. Is there a way I could upload the >>> resulting box to the blobs space, to see if it flies on Vagrant Cloud? >> For automating Vagrant box setup, packer.io is the new veewee it seems. >> I've used it to automate creation of XenServer vagrant boxes, and it >> works really really well. If it=92s useful I have a packer conversion of mort=92s mirage-vagrant-vms = veewee spec here: https://github.com/djs55/mirage-vagrant-vms/tree/packer Cheers, Dave _______________________________________________ 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 Jun 09 13:49:03 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 09 Jun 2014 13:49: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 1Wtzwa-00061h-Rq; Mon, 09 Jun 2014 13:49:00 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WtzwY-00060G-Tz for mirageos-devel@lists.xenproject.org; Mon, 09 Jun 2014 13:48:59 +0000 Received: from [85.158.143.35:11742] by server-3.bemta-4.messagelabs.com id B7/54-13602-A4BB5935; Mon, 09 Jun 2014 13:48:58 +0000 X-Env-Sender: Dave.Scott@citrix.com X-Msg-Ref: server-14.tower-21.messagelabs.com!1402321737!10176353!1 X-Originating-IP: [185.25.65.24] X-SpamReason: No, hits=0.3 required=7.0 tests=MAILTO_TO_SPAM_ADDR X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 13791 invoked from network); 9 Jun 2014 13:48:57 -0000 Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (185.25.65.24) by server-14.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 9 Jun 2014 13:48:57 -0000 X-IronPort-AV: E=Sophos;i="4.98,1002,1392163200"; d="scan'208";a="20615301" Received: from unknown (HELO AMSPEX01CL01.citrite.net) ([10.69.60.9]) by AMSPIP01.EU.Citrix.com with ESMTP; 09 Jun 2014 13:48:57 +0000 Received: from AMSPEX01CL03.citrite.net ([169.254.8.89]) by AMSPEX01CL01.citrite.net ([169.254.6.105]) with mapi id 14.03.0181.006; Mon, 9 Jun 2014 15:48:57 +0200 From: Dave Scott To: Nik Sultana Thread-Topic: [MirageOS-devel] Vagrant Cloud Thread-Index: AQHPg7j4c8oAc19hBEGGHhOcFShOy5toXEgAgAAjUQCAAB+2AIAACtOA Date: Mon, 9 Jun 2014 13:48:56 +0000 Message-ID: <9F7DD918-C84D-4303-9F43-BD5AB897CE58@citrix.com> References: "\"<3cdd336ae2656bf8a249f2bb3bf67ab1@cam.ac.uk>" <9E4CC3B4-B2D9-4A19-8A87-5B88106CDDEC@nottingham.ac.uk>" <53959798.3020308@cam.ac.uk> <14eb11d9725d61a0daf0c079d49ca0b1@cam.ac.uk> In-Reply-To: <14eb11d9725d61a0daf0c079d49ca0b1@cam.ac.uk> Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.13.107.79] Content-ID: MIME-Version: 1.0 X-DLP: AMS1 Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Vagrant Cloud X-BeenThere: mirageos-devel@lists.xenproject.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, On 9 Jun 2014, at 14:10, Nik Sultana wrote: > Thanks for the input Jon. I could try using packer's tool [1] to translat= e from the veewee spec. Have you come across a useful/exemplary description= of a workflow that uses packer.io? > Best, > Nik > = > [1] http://www.packer.io/docs/templates/veewee-to-packer.html > = > On 2014-06-09 12:16, Jon Ludlam wrote: >> On 09/06/14 10:10, Nik Sultana wrote: >>> On 2014-06-09 09:00, Anil Madhavapeddy wrote: >>>> It would be nice to auto-rebuild these Vagrant boxes -- is there a >>>> 'make' target in that repo I can use to do so? >>> Not yet. To get going, I could write a build.sh that consisted of >>> stringing together the building instructions. I reran the workflow at >>> the end of last week to re-check it. Is there a way I could upload the >>> resulting box to the blobs space, to see if it flies on Vagrant Cloud? >> For automating Vagrant box setup, packer.io is the new veewee it seems. >> I've used it to automate creation of XenServer vagrant boxes, and it >> works really really well. If it=92s useful I have a packer conversion of mort=92s mirage-vagrant-vms = veewee spec here: https://github.com/djs55/mirage-vagrant-vms/tree/packer Cheers, Dave _______________________________________________ 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 Jun 09 14:52:34 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 09 Jun 2014 14:52: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 1Wu0w4-0000QZ-PV; Mon, 09 Jun 2014 14:52:32 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Wu0w2-0000QS-VT for mirageos-devel@lists.xenproject.org; Mon, 09 Jun 2014 14:52:31 +0000 Received: from [193.109.254.147:26865] by server-11.bemta-14.messagelabs.com id F0/0A-09902-E2AC5935; Mon, 09 Jun 2014 14:52:30 +0000 X-Env-Sender: mindy@somerandomidiot.com X-Msg-Ref: server-14.tower-27.messagelabs.com!1402325548!10059469!1 X-Originating-IP: [217.70.183.198] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25082 invoked from network); 9 Jun 2014 14:52:28 -0000 Received: from relay6-d.mail.gandi.net (HELO relay6-d.mail.gandi.net) (217.70.183.198) by server-14.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 9 Jun 2014 14:52:28 -0000 Received: from mfilter16-d.gandi.net (mfilter16-d.gandi.net [217.70.178.144]) by relay6-d.mail.gandi.net (Postfix) with ESMTP id 558E0FB89F; Mon, 9 Jun 2014 16:52:28 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at mfilter16-d.gandi.net Received: from relay6-d.mail.gandi.net ([217.70.183.198]) by mfilter16-d.gandi.net (mfilter16-d.gandi.net [10.0.15.180]) (amavisd-new, port 10024) with ESMTP id jRP3ZER4o-vB; Mon, 9 Jun 2014 16:52:26 +0200 (CEST) X-Originating-IP: 107.204.177.22 Received: from [10.0.1.140] (107-204-177-22.lightspeed.mdsnwi.sbcglobal.net [107.204.177.22]) (Authenticated sender: guybrush@somerandomidiot.com) by relay6-d.mail.gandi.net (Postfix) with ESMTPSA id 68FF5FB8AC; Mon, 9 Jun 2014 16:52:24 +0200 (CEST) Message-ID: <5395CA23.6060603@somerandomidiot.com> Date: Mon, 09 Jun 2014 09:52:19 -0500 From: Mindy User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: Anil Madhavapeddy , Balraj Singh References: <537A1EAD.5090906@somerandomidiot.com> <538C9FB9.7070001@somerandomidiot.com> <912BC56B-F927-4CDE-9C1E-D40BBD8A79CE@recoil.org> In-Reply-To: <912BC56B-F927-4CDE-9C1E-D40BBD8A79CE@recoil.org> Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] OPW intern checking in! X-BeenThere: mirageos-devel@lists.xenproject.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 On 06/08/2014 01:13 PM, Anil Madhavapeddy wrote: > On 2 Jun 2014, at 17:00, Mindy wrote: > >> Hi, folks! Here's a quick summary of what I've been up to >> >> Late last week: dug more into observed lack of FINs from listening unikernels, found the problem, and submitted a pull request to mirage-tcpip > This had Balraj and me scratching our collective heads about how it regressed, since we're *sure* it used to work It worked just fine when Mirage is the client initiating the TCP connection (different codepath for listens vs connections), so that might be it? > (famous last words :-). Balraj, any thoughts about it after your Friday investigations? > > This does highlight the importance of getting a regression test infrastructure for networking in place though, since TCPIP in particular is a very interlocked protocol. Any thoughts you may have about this using scapy would be interesting... My first thought is that I don't know how to get the workflow I've been using (start up a unikernel in Xen and throw a bunch of stuff at it from scapy) set up in Travis, but if that doesn't seem like obviously the wrong thing to do, I can look into it. I would still like to look at Quickcheck as well. > Meanwhile, I've released it as tcpip.1.1.3 into OPAM: https://github.com/ocaml/opam-repository/pull/2207 \o/ Also, an update - Last week I wrote up another Treaty of Westphalia on finding a TCP bug and made Mirage implementations of chargen, discard, and echo for use in testing the TCP stack more directly. Today, I'm planning on getting a whole bunch of data from them and (I hope) finding some interesting results. Thanks, Mindy _______________________________________________ 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 Jun 09 14:52:34 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 09 Jun 2014 14:52: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 1Wu0w4-0000QZ-PV; Mon, 09 Jun 2014 14:52:32 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Wu0w2-0000QS-VT for mirageos-devel@lists.xenproject.org; Mon, 09 Jun 2014 14:52:31 +0000 Received: from [193.109.254.147:26865] by server-11.bemta-14.messagelabs.com id F0/0A-09902-E2AC5935; Mon, 09 Jun 2014 14:52:30 +0000 X-Env-Sender: mindy@somerandomidiot.com X-Msg-Ref: server-14.tower-27.messagelabs.com!1402325548!10059469!1 X-Originating-IP: [217.70.183.198] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25082 invoked from network); 9 Jun 2014 14:52:28 -0000 Received: from relay6-d.mail.gandi.net (HELO relay6-d.mail.gandi.net) (217.70.183.198) by server-14.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 9 Jun 2014 14:52:28 -0000 Received: from mfilter16-d.gandi.net (mfilter16-d.gandi.net [217.70.178.144]) by relay6-d.mail.gandi.net (Postfix) with ESMTP id 558E0FB89F; Mon, 9 Jun 2014 16:52:28 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at mfilter16-d.gandi.net Received: from relay6-d.mail.gandi.net ([217.70.183.198]) by mfilter16-d.gandi.net (mfilter16-d.gandi.net [10.0.15.180]) (amavisd-new, port 10024) with ESMTP id jRP3ZER4o-vB; Mon, 9 Jun 2014 16:52:26 +0200 (CEST) X-Originating-IP: 107.204.177.22 Received: from [10.0.1.140] (107-204-177-22.lightspeed.mdsnwi.sbcglobal.net [107.204.177.22]) (Authenticated sender: guybrush@somerandomidiot.com) by relay6-d.mail.gandi.net (Postfix) with ESMTPSA id 68FF5FB8AC; Mon, 9 Jun 2014 16:52:24 +0200 (CEST) Message-ID: <5395CA23.6060603@somerandomidiot.com> Date: Mon, 09 Jun 2014 09:52:19 -0500 From: Mindy User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: Anil Madhavapeddy , Balraj Singh References: <537A1EAD.5090906@somerandomidiot.com> <538C9FB9.7070001@somerandomidiot.com> <912BC56B-F927-4CDE-9C1E-D40BBD8A79CE@recoil.org> In-Reply-To: <912BC56B-F927-4CDE-9C1E-D40BBD8A79CE@recoil.org> Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] OPW intern checking in! X-BeenThere: mirageos-devel@lists.xenproject.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 On 06/08/2014 01:13 PM, Anil Madhavapeddy wrote: > On 2 Jun 2014, at 17:00, Mindy wrote: > >> Hi, folks! Here's a quick summary of what I've been up to >> >> Late last week: dug more into observed lack of FINs from listening unikernels, found the problem, and submitted a pull request to mirage-tcpip > This had Balraj and me scratching our collective heads about how it regressed, since we're *sure* it used to work It worked just fine when Mirage is the client initiating the TCP connection (different codepath for listens vs connections), so that might be it? > (famous last words :-). Balraj, any thoughts about it after your Friday investigations? > > This does highlight the importance of getting a regression test infrastructure for networking in place though, since TCPIP in particular is a very interlocked protocol. Any thoughts you may have about this using scapy would be interesting... My first thought is that I don't know how to get the workflow I've been using (start up a unikernel in Xen and throw a bunch of stuff at it from scapy) set up in Travis, but if that doesn't seem like obviously the wrong thing to do, I can look into it. I would still like to look at Quickcheck as well. > Meanwhile, I've released it as tcpip.1.1.3 into OPAM: https://github.com/ocaml/opam-repository/pull/2207 \o/ Also, an update - Last week I wrote up another Treaty of Westphalia on finding a TCP bug and made Mirage implementations of chargen, discard, and echo for use in testing the TCP stack more directly. Today, I'm planning on getting a whole bunch of data from them and (I hope) finding some interesting results. Thanks, Mindy _______________________________________________ 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 Jun 10 10:27:16 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 10 Jun 2014 10:27: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 1WuJGn-0001AF-W6; Tue, 10 Jun 2014 10:27:09 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WuJGm-0001A2-Qm for mirageos-devel@lists.xenproject.org; Tue, 10 Jun 2014 10:27:09 +0000 Received: from [85.158.137.68:37827] by server-9.bemta-3.messagelabs.com id F0/1C-30063-C7DD6935; Tue, 10 Jun 2014 10:27:08 +0000 X-Env-Sender: thomas.sanders@citrix.com X-Msg-Ref: server-2.tower-31.messagelabs.com!1402396027!9129225!1 X-Originating-IP: [185.25.65.24] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22614 invoked from network); 10 Jun 2014 10:27:07 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (185.25.65.24) by server-2.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 10 Jun 2014 10:27:07 -0000 X-IronPort-AV: E=Sophos;i="4.98,1008,1392163200"; d="scan'208";a="20768631" Received: from unknown (HELO AMSPEX01CL02.citrite.net) ([10.69.60.9]) by AMSPIP01.EU.Citrix.com with ESMTP; 10 Jun 2014 10:27:08 +0000 Received: from AMSPEX01CL01.citrite.net ([169.254.6.105]) by AMSPEX01CL02.citrite.net ([10.69.46.33]) with mapi id 14.03.0181.006; Tue, 10 Jun 2014 12:27:07 +0200 From: Thomas Sanders To: Jonathan Ludlam , "xen-api@lists.xen.org" , "mirageos-devel@lists.xenproject.org" Thread-Topic: [Xen-API] Xapi project repositories Thread-Index: AQHPhJGhV8l5AmBj5Uek7i5kFUIKNZtqH+zA Date: Tue, 10 Jun 2014 10:27:07 +0000 Message-ID: <06B80725944D5847804519C301FB872729AFBF@AMSPEX01CL01.citrite.net> References: <5396D482.6000706@eu.citrix.com> In-Reply-To: <5396D482.6000706@eu.citrix.com> Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.69.129.53] MIME-Version: 1.0 X-DLP: AMS1 Cc: Lars Kurth Subject: Re: [MirageOS-devel] [Xen-API] Xapi project repositories X-BeenThere: mirageos-devel@lists.xenproject.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 10 June 2014 at 10:49 AM Jon Ludlam wrote: > I started making a list, and realised that there are a few other > inconsistencies that we ought to clean up at the same time, for example, > many repositories are marked as forks of personal repos where that > relationship ought to be reversed. [snip] > These forking relationship problems need to be fixed by the people who > own the upstream repo. I don't think it's quite as simple as clicking > the 'transfer repository' button. If anyone knows the exact procedure > for doing this, could they please reply? I'm not confident that it is possible to just designate a different fork as the "upstream" one. A while back I'm fairly sure it wasn't, though perhaps github has made changes since then. It looks as if it would be possible to transfer the repository, but this Isn't really want as we'd need to get the "upstream" one into the right state, and would have to jump through some hoops with memberships and renaming: https://help.github.com/articles/how-to-transfer-a-repository If the "upstream" owner were to delete his fork then a new fork will be chosen as the new "parent" repository, though the github documentation doesn't make it clear whether this is chosen by a github algorithm or by the user doing the deletion: https://help.github.com/articles/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility _______________________________________________ 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 Jun 10 10:27:16 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 10 Jun 2014 10:27: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 1WuJGn-0001AF-W6; Tue, 10 Jun 2014 10:27:09 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WuJGm-0001A2-Qm for mirageos-devel@lists.xenproject.org; Tue, 10 Jun 2014 10:27:09 +0000 Received: from [85.158.137.68:37827] by server-9.bemta-3.messagelabs.com id F0/1C-30063-C7DD6935; Tue, 10 Jun 2014 10:27:08 +0000 X-Env-Sender: thomas.sanders@citrix.com X-Msg-Ref: server-2.tower-31.messagelabs.com!1402396027!9129225!1 X-Originating-IP: [185.25.65.24] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22614 invoked from network); 10 Jun 2014 10:27:07 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (185.25.65.24) by server-2.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 10 Jun 2014 10:27:07 -0000 X-IronPort-AV: E=Sophos;i="4.98,1008,1392163200"; d="scan'208";a="20768631" Received: from unknown (HELO AMSPEX01CL02.citrite.net) ([10.69.60.9]) by AMSPIP01.EU.Citrix.com with ESMTP; 10 Jun 2014 10:27:08 +0000 Received: from AMSPEX01CL01.citrite.net ([169.254.6.105]) by AMSPEX01CL02.citrite.net ([10.69.46.33]) with mapi id 14.03.0181.006; Tue, 10 Jun 2014 12:27:07 +0200 From: Thomas Sanders To: Jonathan Ludlam , "xen-api@lists.xen.org" , "mirageos-devel@lists.xenproject.org" Thread-Topic: [Xen-API] Xapi project repositories Thread-Index: AQHPhJGhV8l5AmBj5Uek7i5kFUIKNZtqH+zA Date: Tue, 10 Jun 2014 10:27:07 +0000 Message-ID: <06B80725944D5847804519C301FB872729AFBF@AMSPEX01CL01.citrite.net> References: <5396D482.6000706@eu.citrix.com> In-Reply-To: <5396D482.6000706@eu.citrix.com> Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.69.129.53] MIME-Version: 1.0 X-DLP: AMS1 Cc: Lars Kurth Subject: Re: [MirageOS-devel] [Xen-API] Xapi project repositories X-BeenThere: mirageos-devel@lists.xenproject.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 10 June 2014 at 10:49 AM Jon Ludlam wrote: > I started making a list, and realised that there are a few other > inconsistencies that we ought to clean up at the same time, for example, > many repositories are marked as forks of personal repos where that > relationship ought to be reversed. [snip] > These forking relationship problems need to be fixed by the people who > own the upstream repo. I don't think it's quite as simple as clicking > the 'transfer repository' button. If anyone knows the exact procedure > for doing this, could they please reply? I'm not confident that it is possible to just designate a different fork as the "upstream" one. A while back I'm fairly sure it wasn't, though perhaps github has made changes since then. It looks as if it would be possible to transfer the repository, but this Isn't really want as we'd need to get the "upstream" one into the right state, and would have to jump through some hoops with memberships and renaming: https://help.github.com/articles/how-to-transfer-a-repository If the "upstream" owner were to delete his fork then a new fork will be chosen as the new "parent" repository, though the github documentation doesn't make it clear whether this is chosen by a github algorithm or by the user doing the deletion: https://help.github.com/articles/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility _______________________________________________ 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 Jun 10 10:28:31 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 10 Jun 2014 10:28: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 1WuJI7-0001Mm-SQ; Tue, 10 Jun 2014 10:28:31 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WuJI6-0001Ma-7o for mirageos-devel@lists.xenproject.org; Tue, 10 Jun 2014 10:28:30 +0000 Received: from [85.158.143.35:21494] by server-2.bemta-4.messagelabs.com id F7/FF-06539-DCDD6935; Tue, 10 Jun 2014 10:28:29 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-4.tower-21.messagelabs.com!1402396108!10329703!1 X-Originating-IP: [74.125.82.41] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21959 invoked from network); 10 Jun 2014 10:28:28 -0000 Received: from mail-wg0-f41.google.com (HELO mail-wg0-f41.google.com) (74.125.82.41) by server-4.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 10 Jun 2014 10:28:28 -0000 Received: by mail-wg0-f41.google.com with SMTP id a1so3651841wgh.12 for ; Tue, 10 Jun 2014 03:28:28 -0700 (PDT) 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=AgmO/GtgqAQ//toakZrz5wLX9iRr385A0Az8Xk339F0=; b=u0c7fb7LmaWZPksB6kpINvGhWD4s82K1RN+arsrELdxefZRPc/h0ubJoR/ywXnf5kU mQz5rIXFCCXmnU34O8wh0pgMxhs0z5Vgem9dInvnYUxva1oI1vFoC0o6mb1aEbVRYCuk onQJ7sIuI2hmapg6tqCACt3yqNWT2Bt5tTTSbdVBSsN957ItNU6O1AqOxEMIE8l/1Gl+ 8QEvwW02Cbj8hdo8QNHEkZu1UIGqQd3yqL5jD5ycJ3fFt89Z70yBBruTab5cYBU9eCW3 CwW2GuOSVezaj2ciMdUqF1TyJvtsnXurhKYS+6fRXW2x0qCcILqh8Q2Y8liU2FxELmdF p5Gw== X-Received: by 10.180.37.180 with SMTP id z20mr17624222wij.58.1402396108508; Tue, 10 Jun 2014 03:28:28 -0700 (PDT) Received: from [192.168.0.8] (cpc25-cmbg14-2-0-cust121.5-4.cable.virginm.net. [213.106.112.122]) by mx.google.com with ESMTPSA id s14sm1430526wij.1.2014.06.10.03.28.26 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 10 Jun 2014 03:28:27 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\)) From: Thomas Gazagnaire In-Reply-To: Date: Tue, 10 Jun 2014 11:28:25 +0100 Message-Id: References: <5396D482.6000706@eu.citrix.com> To: John Else X-Mailer: Apple Mail (2.1878.2) Cc: Lars Kurth , Jonathan Ludlam , "mirageos-devel@lists.xenproject.org" , "xen-api@lists.xen.org" Subject: Re: [MirageOS-devel] [Xen-API] Xapi project repositories X-BeenThere: mirageos-devel@lists.xenproject.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 >> These forking relationship problems need to be fixed by the people who own the upstream repo. I don't think it's quite as simple as clicking the 'transfer repository' button. If anyone knows the exact procedure for doing this, could they please reply? > > What I've done in the past is clicked 'transfer repository' to xapi-project or xenserver, then forked back to my own account. > > This seemed to work fine. I might only have done this with repos that had only a master branch, so we should make sure it works with repos with multiple branches (but I can't see why it wouldn't). Indeed, this should work fine, we did it plenty of time with mirage repos. Github also automatically sets up redirect, so everything is transparent for users. 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 Jun 10 10:28:31 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 10 Jun 2014 10:28: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 1WuJI7-0001Mm-SQ; Tue, 10 Jun 2014 10:28:31 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WuJI6-0001Ma-7o for mirageos-devel@lists.xenproject.org; Tue, 10 Jun 2014 10:28:30 +0000 Received: from [85.158.143.35:21494] by server-2.bemta-4.messagelabs.com id F7/FF-06539-DCDD6935; Tue, 10 Jun 2014 10:28:29 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-4.tower-21.messagelabs.com!1402396108!10329703!1 X-Originating-IP: [74.125.82.41] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21959 invoked from network); 10 Jun 2014 10:28:28 -0000 Received: from mail-wg0-f41.google.com (HELO mail-wg0-f41.google.com) (74.125.82.41) by server-4.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 10 Jun 2014 10:28:28 -0000 Received: by mail-wg0-f41.google.com with SMTP id a1so3651841wgh.12 for ; Tue, 10 Jun 2014 03:28:28 -0700 (PDT) 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=AgmO/GtgqAQ//toakZrz5wLX9iRr385A0Az8Xk339F0=; b=u0c7fb7LmaWZPksB6kpINvGhWD4s82K1RN+arsrELdxefZRPc/h0ubJoR/ywXnf5kU mQz5rIXFCCXmnU34O8wh0pgMxhs0z5Vgem9dInvnYUxva1oI1vFoC0o6mb1aEbVRYCuk onQJ7sIuI2hmapg6tqCACt3yqNWT2Bt5tTTSbdVBSsN957ItNU6O1AqOxEMIE8l/1Gl+ 8QEvwW02Cbj8hdo8QNHEkZu1UIGqQd3yqL5jD5ycJ3fFt89Z70yBBruTab5cYBU9eCW3 CwW2GuOSVezaj2ciMdUqF1TyJvtsnXurhKYS+6fRXW2x0qCcILqh8Q2Y8liU2FxELmdF p5Gw== X-Received: by 10.180.37.180 with SMTP id z20mr17624222wij.58.1402396108508; Tue, 10 Jun 2014 03:28:28 -0700 (PDT) Received: from [192.168.0.8] (cpc25-cmbg14-2-0-cust121.5-4.cable.virginm.net. [213.106.112.122]) by mx.google.com with ESMTPSA id s14sm1430526wij.1.2014.06.10.03.28.26 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 10 Jun 2014 03:28:27 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\)) From: Thomas Gazagnaire In-Reply-To: Date: Tue, 10 Jun 2014 11:28:25 +0100 Message-Id: References: <5396D482.6000706@eu.citrix.com> To: John Else X-Mailer: Apple Mail (2.1878.2) Cc: Lars Kurth , Jonathan Ludlam , "mirageos-devel@lists.xenproject.org" , "xen-api@lists.xen.org" Subject: Re: [MirageOS-devel] [Xen-API] Xapi project repositories X-BeenThere: mirageos-devel@lists.xenproject.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 >> These forking relationship problems need to be fixed by the people who own the upstream repo. I don't think it's quite as simple as clicking the 'transfer repository' button. If anyone knows the exact procedure for doing this, could they please reply? > > What I've done in the past is clicked 'transfer repository' to xapi-project or xenserver, then forked back to my own account. > > This seemed to work fine. I might only have done this with repos that had only a master branch, so we should make sure it works with repos with multiple branches (but I can't see why it wouldn't). Indeed, this should work fine, we did it plenty of time with mirage repos. Github also automatically sets up redirect, so everything is transparent for users. 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 Jun 10 10:58:57 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 10 Jun 2014 10:58:57 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WuJlY-00031G-96; Tue, 10 Jun 2014 10:58:56 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WuIvi-0000PM-Da for mirageos-devel@lists.xenproject.org; Tue, 10 Jun 2014 10:05:22 +0000 Received: from [85.158.137.68:21480] by server-14.bemta-3.messagelabs.com id 47/BC-30903-168D6935; Tue, 10 Jun 2014 10:05:21 +0000 X-Env-Sender: lars.kurth@citrix.com X-Msg-Ref: server-9.tower-31.messagelabs.com!1402394720!5390154!1 X-Originating-IP: [185.25.65.24] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30755 invoked from network); 10 Jun 2014 10:05:20 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (185.25.65.24) by server-9.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 10 Jun 2014 10:05:20 -0000 X-IronPort-AV: E=Sophos;i="4.98,1008,1392163200"; d="scan'208";a="20763826" Received: from unknown (HELO AMSPEX01CL02.citrite.net) ([10.69.60.9]) by AMSPIP01.EU.Citrix.com with ESMTP; 10 Jun 2014 10:05:19 +0000 Received: from AMSPEX01CL01.citrite.net ([169.254.6.105]) by AMSPEX01CL02.citrite.net ([10.69.46.33]) with mapi id 14.03.0181.006; Tue, 10 Jun 2014 12:05:19 +0200 From: Lars Kurth To: Jonathan Ludlam , "xen-api@lists.xen.org" , "mirageos-devel@lists.xenproject.org" Thread-Topic: Xapi project repositories Thread-Index: AQHPhJEwbE9WW6Sqyki8AbXoPh5dz5tqHGHA Date: Tue, 10 Jun 2014 10:05:19 +0000 Message-ID: References: <5396D482.6000706@eu.citrix.com> In-Reply-To: <5396D482.6000706@eu.citrix.com> Accept-Language: en-GB, en-US Content-Language: en-GB X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.69.46.1] MIME-Version: 1.0 X-DLP: AMS1 X-Mailman-Approved-At: Tue, 10 Jun 2014 10:58:54 +0000 Subject: Re: [MirageOS-devel] Xapi project repositories X-BeenThere: mirageos-devel@lists.xenproject.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, when you have the final list of repos for xapi and mirage. Please send it to me such that I can update the bitergia dashboard Still need to get the Mirage list, which I have been waiting for for several months. @Jon. Do you want press coverage for XAPI 2? Can talk to you on Thursdays Lars ________________________________________ From: Jonathan Ludlam Sent: 10 June 2014 10:48 To: xen-api@lists.xen.org; mirageos-devel@lists.xenproject.org Cc: Lars Kurth Subject: Xapi project repositories Hi all, In preparing for the 2.0 release, it's become increasingly obvious that we really need to tidy up the xapi-project org on github. There are many repositories that are in the org that aren't a part of the Xapi Project. I started making a list, and realised that there are a few other inconsistencies that we ought to clean up at the same time, for example, many repositories are marked as forks of personal repos where that relationship ought to be reversed. First, there are some repositories that should just be deleted: - opam A fork of github.com/ocaml/opam. I don't know why we have this, it doesn't appear to have any commits from us. - opam-repository Same as opam. - xcp-fhs This is unused by anyone, as far as I know. - xen-unstable-mirror Just a mirror of the xen project repository. - xcp-storage-managers An old fork. sm.git should be used instead. - ocaml-sha A fork of upstream, no additional changesets from us. - ocaml-tar A fork of upstream, no additional changesets from us - ocaml-vhd A fork of upstream, no additional changesets from us Secondly, I believe some of the repositories should be transferred to the 'xenserver' organisation, which I think probably needs approval, as the xenserver org is not a part of the Linux Foundation. These are: - filesystem-summarise A tool to check for filesystem changes. Useful on XenServer for detecting when changes have been made to configuration files and so on. Not useful for general installations of the xapi project. - jiralib An old python library for talking to jira. Superseded by jira-python package. - mirrortest A test repository for checking Citrix's internal mirrors of the github repositories. - PRDup 'Pull Request Duplicator', a tool for helping to backport pull requests to different branches. - pull-request-manager Uses Citrix's internal build system to test pull requests - no longer used. - xs-pull-request-build-scripts Replacement for pull-request-manager - uses Citrix's internal build system to test pull requests, this time using jenkins. - xen-api-libs-specs Spec files used for building a lot of the xapi-project components for XenServer. There is large overlap with github.com/xenserver/buildroot - these should probably merge (or become more closely related). - xen-api-backports Similar to xen-api-libs-specs, but for Citrix's internal 'old buildsystem' as opposed to Citrix's internal 'newer buildsystem'. I don't think any of these is actually contentious - they probably should never have been part of the Linux Foundation, and have been there since we only had the one place on github to put things! Third, we have some libraries that are actually mirage core libraries. These should transfer over to the mirage organisation (remaining in LF, as mirage is a Xen Project subproject like xapi): - ocaml-gnt OCaml grant table manipulation. This code originated in the mirage project and was put here when it was split out of mirage-platform (see here: https://github.com/mirage/mirage-platform/commit/f532fc79af41e0e39b624a8e63dffc900bf1b7e4). - ocaml-xenstore This is the mirage implementation of a xenstore client library. Required for running mirage kernels on xen. We use the unix-flavour of this library. It also contains a WIP new version of the guts of a xenstore daemon, which will be a mirage-style unix process _or_ unikernel (xenstore stub-domain!) that should eventually be upstreamed into xen. - ocaml-xenstore-clients Slightly oddly named library that defines the unix transport mechanisms (unix-domain sockets) for using the ocaml-xenstore library. This is the unix counterpart to the internal shared-page mechanism used by mirage unikernels. - ocaml-evtchn Similar to ocaml-gnt - split from the main mirage code at around the same time as ocaml-gnt. - ocaml-xenstore-xen Unused by xapi-project. I believe in here lives the code that turns the xenstore daemon library from ocaml-xenstore into the actual xenstored stubdomain or process. We have a few repositories that are forks of upstream repos with some of our own changes in. We should get these changes upstreamed at some point, but for now we should leave them there, but recognise that these aren't necessarily part of the official Xapi Project (excepting where they are, e.g. ocaml-xen-lowlevel-libs, which is a staging area for upstreaming back into xen.git!) - oclock - ocamltest - ocaml-xen-lowlevel-libs - python-github2 Then there are generic ocaml libraries which could be used by other ocaml programs. I think these can live on in the xapi project organisation for now, but I wouldn't class them as 'core' xapi-project repos. - cdrom - netdev - ocamldoc-json - ocaml-encodings - ocaml-crc - ocaml-fd-send-recv - ocaml-netlink - ocaml-opasswd - ocaml-pci-db - ocaml-qmp - stdext - stunnel - nbd Which leaves us with the 'core' xapi project repositories: - blktap - blktap-dkms - example-ocaml-daemon - ffs - forkexecd - libvhd - message-switch - ocaml-rrdd-plugins - opam-repo-dev - rrd-transport - rrdd-plugin-legacy - rrddump - sm - sm-cli - squeezed - tapctl - vhd-tool - vncproxy - vncterm - vxs - wsproxy - xapi-codegen - xapi-libvirt-storage - xapi-project - xcp-eliloader - xcp-guest-templates - xcp-idl - xcp-inventory - xcp-networkd - xcp-rrd - xcp-rrdd - xen-api - xen-api-client - xen-api-libs - xen-api-libs-transitional - xen-api-sdk - xenops - xenops-cli - xenopsd Of the above lists that will remain in the xapi project, these repositories have incorrect forking status (they are marked as forks of someone here at Citrix, but shouldn't be): Forked from me (jonludlam on github): xen-api-libs-transitional xen-api-client xcp-guest-templates xcp-eliloader wsproxy tapctl libvhd blktap-dkms netdev nbd cdrom Forked from Dave Scott (djs55) xcp-idl vhd-tool ffs ocaml-vhd ocaml-tar ocaml-fd-send-recv Forked from Simon Beaumont (simonjbeaumont): ocaml-pci-db Forked from Mike McClurg (mcclurmc): ocaml-opasswd These forking relationship problems need to be fixed by the people who own the upstream repo. I don't think it's quite as simple as clicking the 'transfer repository' button. If anyone knows the exact procedure for doing this, could they please reply? In summary, I believe we need to: 1) delete some repositories 2) move some repositories to xenserver 3) move some repositories to mirage-project 4) transfer ownership of some repositories (just flip around the direction of the fork). 5) document all of this on the wiki! Any comments? Jon _______________________________________________ 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 Jun 10 10:58:57 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 10 Jun 2014 10:58:57 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WuJlY-00031B-72; Tue, 10 Jun 2014 10:58:56 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WuIfm-0007Hz-QI for mirageos-devel@lists.xenproject.org; Tue, 10 Jun 2014 09:48:55 +0000 Received: from [85.158.137.68:55638] by server-8.bemta-3.messagelabs.com id 59/96-21547-584D6935; Tue, 10 Jun 2014 09:48:53 +0000 X-Env-Sender: Jonathan.Ludlam@citrix.com X-Msg-Ref: server-5.tower-31.messagelabs.com!1402393731!9140582!1 X-Originating-IP: [66.165.176.63] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni42MyA9PiAzMDYwNDg=\n X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23497 invoked from network); 10 Jun 2014 09:48:52 -0000 Received: from smtp02.citrix.com (HELO SMTP02.CITRIX.COM) (66.165.176.63) by server-5.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 10 Jun 2014 09:48:52 -0000 X-IronPort-AV: E=Sophos;i="4.98,1008,1392163200"; d="scan'208";a="141504522" Received: from accessns.citrite.net (HELO FTLPEX01CL03.citrite.net) ([10.9.154.239]) by FTLPIPO02.CITRIX.COM with ESMTP; 10 Jun 2014 09:48:50 +0000 Received: from [10.80.3.75] (10.80.3.75) by FTLPEX01CL03.citrite.net (10.13.107.80) with Microsoft SMTP Server id 14.3.181.6; Tue, 10 Jun 2014 05:48:50 -0400 Message-ID: <5396D482.6000706@eu.citrix.com> Date: Tue, 10 Jun 2014 10:48:50 +0100 From: Jon Ludlam User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: "xen-api@lists.xen.org" , "mirageos-devel@lists.xenproject.org" X-Originating-IP: [10.80.3.75] X-DLP: MIA2 X-Mailman-Approved-At: Tue, 10 Jun 2014 10:58:54 +0000 Cc: Lars Kurth Subject: [MirageOS-devel] Xapi project repositories X-BeenThere: mirageos-devel@lists.xenproject.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, In preparing for the 2.0 release, it's become increasingly obvious that we really need to tidy up the xapi-project org on github. There are many repositories that are in the org that aren't a part of the Xapi Project. I started making a list, and realised that there are a few other inconsistencies that we ought to clean up at the same time, for example, many repositories are marked as forks of personal repos where that relationship ought to be reversed. First, there are some repositories that should just be deleted: - opam A fork of github.com/ocaml/opam. I don't know why we have this, it doesn't appear to have any commits from us. - opam-repository Same as opam. - xcp-fhs This is unused by anyone, as far as I know. - xen-unstable-mirror Just a mirror of the xen project repository. - xcp-storage-managers An old fork. sm.git should be used instead. - ocaml-sha A fork of upstream, no additional changesets from us. - ocaml-tar A fork of upstream, no additional changesets from us - ocaml-vhd A fork of upstream, no additional changesets from us Secondly, I believe some of the repositories should be transferred to the 'xenserver' organisation, which I think probably needs approval, as the xenserver org is not a part of the Linux Foundation. These are: - filesystem-summarise A tool to check for filesystem changes. Useful on XenServer for detecting when changes have been made to configuration files and so on. Not useful for general installations of the xapi project. - jiralib An old python library for talking to jira. Superseded by jira-python package. - mirrortest A test repository for checking Citrix's internal mirrors of the github repositories. - PRDup 'Pull Request Duplicator', a tool for helping to backport pull requests to different branches. - pull-request-manager Uses Citrix's internal build system to test pull requests - no longer used. - xs-pull-request-build-scripts Replacement for pull-request-manager - uses Citrix's internal build system to test pull requests, this time using jenkins. - xen-api-libs-specs Spec files used for building a lot of the xapi-project components for XenServer. There is large overlap with github.com/xenserver/buildroot - these should probably merge (or become more closely related). - xen-api-backports Similar to xen-api-libs-specs, but for Citrix's internal 'old buildsystem' as opposed to Citrix's internal 'newer buildsystem'. I don't think any of these is actually contentious - they probably should never have been part of the Linux Foundation, and have been there since we only had the one place on github to put things! Third, we have some libraries that are actually mirage core libraries. These should transfer over to the mirage organisation (remaining in LF, as mirage is a Xen Project subproject like xapi): - ocaml-gnt OCaml grant table manipulation. This code originated in the mirage project and was put here when it was split out of mirage-platform (see here: https://github.com/mirage/mirage-platform/commit/f532fc79af41e0e39b624a8e63dffc900bf1b7e4). - ocaml-xenstore This is the mirage implementation of a xenstore client library. Required for running mirage kernels on xen. We use the unix-flavour of this library. It also contains a WIP new version of the guts of a xenstore daemon, which will be a mirage-style unix process _or_ unikernel (xenstore stub-domain!) that should eventually be upstreamed into xen. - ocaml-xenstore-clients Slightly oddly named library that defines the unix transport mechanisms (unix-domain sockets) for using the ocaml-xenstore library. This is the unix counterpart to the internal shared-page mechanism used by mirage unikernels. - ocaml-evtchn Similar to ocaml-gnt - split from the main mirage code at around the same time as ocaml-gnt. - ocaml-xenstore-xen Unused by xapi-project. I believe in here lives the code that turns the xenstore daemon library from ocaml-xenstore into the actual xenstored stubdomain or process. We have a few repositories that are forks of upstream repos with some of our own changes in. We should get these changes upstreamed at some point, but for now we should leave them there, but recognise that these aren't necessarily part of the official Xapi Project (excepting where they are, e.g. ocaml-xen-lowlevel-libs, which is a staging area for upstreaming back into xen.git!) - oclock - ocamltest - ocaml-xen-lowlevel-libs - python-github2 Then there are generic ocaml libraries which could be used by other ocaml programs. I think these can live on in the xapi project organisation for now, but I wouldn't class them as 'core' xapi-project repos. - cdrom - netdev - ocamldoc-json - ocaml-encodings - ocaml-crc - ocaml-fd-send-recv - ocaml-netlink - ocaml-opasswd - ocaml-pci-db - ocaml-qmp - stdext - stunnel - nbd Which leaves us with the 'core' xapi project repositories: - blktap - blktap-dkms - example-ocaml-daemon - ffs - forkexecd - libvhd - message-switch - ocaml-rrdd-plugins - opam-repo-dev - rrd-transport - rrdd-plugin-legacy - rrddump - sm - sm-cli - squeezed - tapctl - vhd-tool - vncproxy - vncterm - vxs - wsproxy - xapi-codegen - xapi-libvirt-storage - xapi-project - xcp-eliloader - xcp-guest-templates - xcp-idl - xcp-inventory - xcp-networkd - xcp-rrd - xcp-rrdd - xen-api - xen-api-client - xen-api-libs - xen-api-libs-transitional - xen-api-sdk - xenops - xenops-cli - xenopsd Of the above lists that will remain in the xapi project, these repositories have incorrect forking status (they are marked as forks of someone here at Citrix, but shouldn't be): Forked from me (jonludlam on github): xen-api-libs-transitional xen-api-client xcp-guest-templates xcp-eliloader wsproxy tapctl libvhd blktap-dkms netdev nbd cdrom Forked from Dave Scott (djs55) xcp-idl vhd-tool ffs ocaml-vhd ocaml-tar ocaml-fd-send-recv Forked from Simon Beaumont (simonjbeaumont): ocaml-pci-db Forked from Mike McClurg (mcclurmc): ocaml-opasswd These forking relationship problems need to be fixed by the people who own the upstream repo. I don't think it's quite as simple as clicking the 'transfer repository' button. If anyone knows the exact procedure for doing this, could they please reply? In summary, I believe we need to: 1) delete some repositories 2) move some repositories to xenserver 3) move some repositories to mirage-project 4) transfer ownership of some repositories (just flip around the direction of the fork). 5) document all of this on the wiki! Any comments? Jon _______________________________________________ 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 Jun 10 10:58:57 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 10 Jun 2014 10:58:57 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WuJlY-00031G-96; Tue, 10 Jun 2014 10:58:56 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WuIvi-0000PM-Da for mirageos-devel@lists.xenproject.org; Tue, 10 Jun 2014 10:05:22 +0000 Received: from [85.158.137.68:21480] by server-14.bemta-3.messagelabs.com id 47/BC-30903-168D6935; Tue, 10 Jun 2014 10:05:21 +0000 X-Env-Sender: lars.kurth@citrix.com X-Msg-Ref: server-9.tower-31.messagelabs.com!1402394720!5390154!1 X-Originating-IP: [185.25.65.24] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30755 invoked from network); 10 Jun 2014 10:05:20 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (185.25.65.24) by server-9.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 10 Jun 2014 10:05:20 -0000 X-IronPort-AV: E=Sophos;i="4.98,1008,1392163200"; d="scan'208";a="20763826" Received: from unknown (HELO AMSPEX01CL02.citrite.net) ([10.69.60.9]) by AMSPIP01.EU.Citrix.com with ESMTP; 10 Jun 2014 10:05:19 +0000 Received: from AMSPEX01CL01.citrite.net ([169.254.6.105]) by AMSPEX01CL02.citrite.net ([10.69.46.33]) with mapi id 14.03.0181.006; Tue, 10 Jun 2014 12:05:19 +0200 From: Lars Kurth To: Jonathan Ludlam , "xen-api@lists.xen.org" , "mirageos-devel@lists.xenproject.org" Thread-Topic: Xapi project repositories Thread-Index: AQHPhJEwbE9WW6Sqyki8AbXoPh5dz5tqHGHA Date: Tue, 10 Jun 2014 10:05:19 +0000 Message-ID: References: <5396D482.6000706@eu.citrix.com> In-Reply-To: <5396D482.6000706@eu.citrix.com> Accept-Language: en-GB, en-US Content-Language: en-GB X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.69.46.1] MIME-Version: 1.0 X-DLP: AMS1 X-Mailman-Approved-At: Tue, 10 Jun 2014 10:58:54 +0000 Subject: Re: [MirageOS-devel] Xapi project repositories X-BeenThere: mirageos-devel@lists.xenproject.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, when you have the final list of repos for xapi and mirage. Please send it to me such that I can update the bitergia dashboard Still need to get the Mirage list, which I have been waiting for for several months. @Jon. Do you want press coverage for XAPI 2? Can talk to you on Thursdays Lars ________________________________________ From: Jonathan Ludlam Sent: 10 June 2014 10:48 To: xen-api@lists.xen.org; mirageos-devel@lists.xenproject.org Cc: Lars Kurth Subject: Xapi project repositories Hi all, In preparing for the 2.0 release, it's become increasingly obvious that we really need to tidy up the xapi-project org on github. There are many repositories that are in the org that aren't a part of the Xapi Project. I started making a list, and realised that there are a few other inconsistencies that we ought to clean up at the same time, for example, many repositories are marked as forks of personal repos where that relationship ought to be reversed. First, there are some repositories that should just be deleted: - opam A fork of github.com/ocaml/opam. I don't know why we have this, it doesn't appear to have any commits from us. - opam-repository Same as opam. - xcp-fhs This is unused by anyone, as far as I know. - xen-unstable-mirror Just a mirror of the xen project repository. - xcp-storage-managers An old fork. sm.git should be used instead. - ocaml-sha A fork of upstream, no additional changesets from us. - ocaml-tar A fork of upstream, no additional changesets from us - ocaml-vhd A fork of upstream, no additional changesets from us Secondly, I believe some of the repositories should be transferred to the 'xenserver' organisation, which I think probably needs approval, as the xenserver org is not a part of the Linux Foundation. These are: - filesystem-summarise A tool to check for filesystem changes. Useful on XenServer for detecting when changes have been made to configuration files and so on. Not useful for general installations of the xapi project. - jiralib An old python library for talking to jira. Superseded by jira-python package. - mirrortest A test repository for checking Citrix's internal mirrors of the github repositories. - PRDup 'Pull Request Duplicator', a tool for helping to backport pull requests to different branches. - pull-request-manager Uses Citrix's internal build system to test pull requests - no longer used. - xs-pull-request-build-scripts Replacement for pull-request-manager - uses Citrix's internal build system to test pull requests, this time using jenkins. - xen-api-libs-specs Spec files used for building a lot of the xapi-project components for XenServer. There is large overlap with github.com/xenserver/buildroot - these should probably merge (or become more closely related). - xen-api-backports Similar to xen-api-libs-specs, but for Citrix's internal 'old buildsystem' as opposed to Citrix's internal 'newer buildsystem'. I don't think any of these is actually contentious - they probably should never have been part of the Linux Foundation, and have been there since we only had the one place on github to put things! Third, we have some libraries that are actually mirage core libraries. These should transfer over to the mirage organisation (remaining in LF, as mirage is a Xen Project subproject like xapi): - ocaml-gnt OCaml grant table manipulation. This code originated in the mirage project and was put here when it was split out of mirage-platform (see here: https://github.com/mirage/mirage-platform/commit/f532fc79af41e0e39b624a8e63dffc900bf1b7e4). - ocaml-xenstore This is the mirage implementation of a xenstore client library. Required for running mirage kernels on xen. We use the unix-flavour of this library. It also contains a WIP new version of the guts of a xenstore daemon, which will be a mirage-style unix process _or_ unikernel (xenstore stub-domain!) that should eventually be upstreamed into xen. - ocaml-xenstore-clients Slightly oddly named library that defines the unix transport mechanisms (unix-domain sockets) for using the ocaml-xenstore library. This is the unix counterpart to the internal shared-page mechanism used by mirage unikernels. - ocaml-evtchn Similar to ocaml-gnt - split from the main mirage code at around the same time as ocaml-gnt. - ocaml-xenstore-xen Unused by xapi-project. I believe in here lives the code that turns the xenstore daemon library from ocaml-xenstore into the actual xenstored stubdomain or process. We have a few repositories that are forks of upstream repos with some of our own changes in. We should get these changes upstreamed at some point, but for now we should leave them there, but recognise that these aren't necessarily part of the official Xapi Project (excepting where they are, e.g. ocaml-xen-lowlevel-libs, which is a staging area for upstreaming back into xen.git!) - oclock - ocamltest - ocaml-xen-lowlevel-libs - python-github2 Then there are generic ocaml libraries which could be used by other ocaml programs. I think these can live on in the xapi project organisation for now, but I wouldn't class them as 'core' xapi-project repos. - cdrom - netdev - ocamldoc-json - ocaml-encodings - ocaml-crc - ocaml-fd-send-recv - ocaml-netlink - ocaml-opasswd - ocaml-pci-db - ocaml-qmp - stdext - stunnel - nbd Which leaves us with the 'core' xapi project repositories: - blktap - blktap-dkms - example-ocaml-daemon - ffs - forkexecd - libvhd - message-switch - ocaml-rrdd-plugins - opam-repo-dev - rrd-transport - rrdd-plugin-legacy - rrddump - sm - sm-cli - squeezed - tapctl - vhd-tool - vncproxy - vncterm - vxs - wsproxy - xapi-codegen - xapi-libvirt-storage - xapi-project - xcp-eliloader - xcp-guest-templates - xcp-idl - xcp-inventory - xcp-networkd - xcp-rrd - xcp-rrdd - xen-api - xen-api-client - xen-api-libs - xen-api-libs-transitional - xen-api-sdk - xenops - xenops-cli - xenopsd Of the above lists that will remain in the xapi project, these repositories have incorrect forking status (they are marked as forks of someone here at Citrix, but shouldn't be): Forked from me (jonludlam on github): xen-api-libs-transitional xen-api-client xcp-guest-templates xcp-eliloader wsproxy tapctl libvhd blktap-dkms netdev nbd cdrom Forked from Dave Scott (djs55) xcp-idl vhd-tool ffs ocaml-vhd ocaml-tar ocaml-fd-send-recv Forked from Simon Beaumont (simonjbeaumont): ocaml-pci-db Forked from Mike McClurg (mcclurmc): ocaml-opasswd These forking relationship problems need to be fixed by the people who own the upstream repo. I don't think it's quite as simple as clicking the 'transfer repository' button. If anyone knows the exact procedure for doing this, could they please reply? In summary, I believe we need to: 1) delete some repositories 2) move some repositories to xenserver 3) move some repositories to mirage-project 4) transfer ownership of some repositories (just flip around the direction of the fork). 5) document all of this on the wiki! Any comments? Jon _______________________________________________ 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 Jun 10 10:58:57 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 10 Jun 2014 10:58:57 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WuJlY-00031L-B6; Tue, 10 Jun 2014 10:58:56 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WuJBz-0000tU-07 for mirageos-devel@lists.xenproject.org; Tue, 10 Jun 2014 10:22:11 +0000 Received: from [193.109.254.147:39107] by server-6.bemta-14.messagelabs.com id 80/F3-13066-15CD6935; Tue, 10 Jun 2014 10:22:09 +0000 X-Env-Sender: john.else@citrix.com X-Msg-Ref: server-4.tower-27.messagelabs.com!1402395729!10264971!1 X-Originating-IP: [185.25.65.24] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28321 invoked from network); 10 Jun 2014 10:22:09 -0000 Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (185.25.65.24) by server-4.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 10 Jun 2014 10:22:09 -0000 X-IronPort-AV: E=Sophos;i="4.98,1008,1392163200"; d="scan'208";a="20767570" Received: from unknown (HELO AMSPEX01CL03.citrite.net) ([10.69.60.9]) by AMSPIP01.EU.Citrix.com with ESMTP; 10 Jun 2014 10:22:09 +0000 Received: from AMSPEX01CL01.citrite.net ([169.254.6.105]) by AMSPEX01CL03.citrite.net ([169.254.8.89]) with mapi id 14.03.0181.006; Tue, 10 Jun 2014 12:22:08 +0200 From: John Else To: Jonathan Ludlam , "xen-api@lists.xen.org" , "mirageos-devel@lists.xenproject.org" Thread-Topic: [Xen-API] Xapi project repositories Thread-Index: AQHPhJGhJvFO0alLWUe9CtbtXOUU+ptqIDRA Date: Tue, 10 Jun 2014 10:22:08 +0000 Message-ID: References: <5396D482.6000706@eu.citrix.com> In-Reply-To: <5396D482.6000706@eu.citrix.com> Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.80.237.237] MIME-Version: 1.0 X-DLP: AMS1 X-Mailman-Approved-At: Tue, 10 Jun 2014 10:58:54 +0000 Cc: Lars Kurth Subject: Re: [MirageOS-devel] [Xen-API] Xapi project repositories X-BeenThere: mirageos-devel@lists.xenproject.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 10/06/2014 10:49 AM, Jon Ludlam wrote: > These forking relationship problems need to be fixed by the people who own the upstream repo. I don't think it's quite as simple as clicking the 'transfer repository' button. If anyone knows the exact procedure for doing this, could they please reply? What I've done in the past is clicked 'transfer repository' to xapi-project or xenserver, then forked back to my own account. This seemed to work fine. I might only have done this with repos that had only a master branch, so we should make sure it works with repos with multiple branches (but I can't see why it wouldn't). John _______________________________________________ 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 Jun 10 10:58:57 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 10 Jun 2014 10:58:57 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WuJlY-00031L-B6; Tue, 10 Jun 2014 10:58:56 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WuJBz-0000tU-07 for mirageos-devel@lists.xenproject.org; Tue, 10 Jun 2014 10:22:11 +0000 Received: from [193.109.254.147:39107] by server-6.bemta-14.messagelabs.com id 80/F3-13066-15CD6935; Tue, 10 Jun 2014 10:22:09 +0000 X-Env-Sender: john.else@citrix.com X-Msg-Ref: server-4.tower-27.messagelabs.com!1402395729!10264971!1 X-Originating-IP: [185.25.65.24] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28321 invoked from network); 10 Jun 2014 10:22:09 -0000 Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (185.25.65.24) by server-4.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 10 Jun 2014 10:22:09 -0000 X-IronPort-AV: E=Sophos;i="4.98,1008,1392163200"; d="scan'208";a="20767570" Received: from unknown (HELO AMSPEX01CL03.citrite.net) ([10.69.60.9]) by AMSPIP01.EU.Citrix.com with ESMTP; 10 Jun 2014 10:22:09 +0000 Received: from AMSPEX01CL01.citrite.net ([169.254.6.105]) by AMSPEX01CL03.citrite.net ([169.254.8.89]) with mapi id 14.03.0181.006; Tue, 10 Jun 2014 12:22:08 +0200 From: John Else To: Jonathan Ludlam , "xen-api@lists.xen.org" , "mirageos-devel@lists.xenproject.org" Thread-Topic: [Xen-API] Xapi project repositories Thread-Index: AQHPhJGhJvFO0alLWUe9CtbtXOUU+ptqIDRA Date: Tue, 10 Jun 2014 10:22:08 +0000 Message-ID: References: <5396D482.6000706@eu.citrix.com> In-Reply-To: <5396D482.6000706@eu.citrix.com> Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.80.237.237] MIME-Version: 1.0 X-DLP: AMS1 X-Mailman-Approved-At: Tue, 10 Jun 2014 10:58:54 +0000 Cc: Lars Kurth Subject: Re: [MirageOS-devel] [Xen-API] Xapi project repositories X-BeenThere: mirageos-devel@lists.xenproject.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 10/06/2014 10:49 AM, Jon Ludlam wrote: > These forking relationship problems need to be fixed by the people who own the upstream repo. I don't think it's quite as simple as clicking the 'transfer repository' button. If anyone knows the exact procedure for doing this, could they please reply? What I've done in the past is clicked 'transfer repository' to xapi-project or xenserver, then forked back to my own account. This seemed to work fine. I might only have done this with repos that had only a master branch, so we should make sure it works with repos with multiple branches (but I can't see why it wouldn't). John _______________________________________________ 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 Jun 10 10:58:57 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 10 Jun 2014 10:58:57 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WuJlY-00031B-72; Tue, 10 Jun 2014 10:58:56 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WuIfm-0007Hz-QI for mirageos-devel@lists.xenproject.org; Tue, 10 Jun 2014 09:48:55 +0000 Received: from [85.158.137.68:55638] by server-8.bemta-3.messagelabs.com id 59/96-21547-584D6935; Tue, 10 Jun 2014 09:48:53 +0000 X-Env-Sender: Jonathan.Ludlam@citrix.com X-Msg-Ref: server-5.tower-31.messagelabs.com!1402393731!9140582!1 X-Originating-IP: [66.165.176.63] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni42MyA9PiAzMDYwNDg=\n X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23497 invoked from network); 10 Jun 2014 09:48:52 -0000 Received: from smtp02.citrix.com (HELO SMTP02.CITRIX.COM) (66.165.176.63) by server-5.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 10 Jun 2014 09:48:52 -0000 X-IronPort-AV: E=Sophos;i="4.98,1008,1392163200"; d="scan'208";a="141504522" Received: from accessns.citrite.net (HELO FTLPEX01CL03.citrite.net) ([10.9.154.239]) by FTLPIPO02.CITRIX.COM with ESMTP; 10 Jun 2014 09:48:50 +0000 Received: from [10.80.3.75] (10.80.3.75) by FTLPEX01CL03.citrite.net (10.13.107.80) with Microsoft SMTP Server id 14.3.181.6; Tue, 10 Jun 2014 05:48:50 -0400 Message-ID: <5396D482.6000706@eu.citrix.com> Date: Tue, 10 Jun 2014 10:48:50 +0100 From: Jon Ludlam User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: "xen-api@lists.xen.org" , "mirageos-devel@lists.xenproject.org" X-Originating-IP: [10.80.3.75] X-DLP: MIA2 X-Mailman-Approved-At: Tue, 10 Jun 2014 10:58:54 +0000 Cc: Lars Kurth Subject: [MirageOS-devel] Xapi project repositories X-BeenThere: mirageos-devel@lists.xenproject.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, In preparing for the 2.0 release, it's become increasingly obvious that we really need to tidy up the xapi-project org on github. There are many repositories that are in the org that aren't a part of the Xapi Project. I started making a list, and realised that there are a few other inconsistencies that we ought to clean up at the same time, for example, many repositories are marked as forks of personal repos where that relationship ought to be reversed. First, there are some repositories that should just be deleted: - opam A fork of github.com/ocaml/opam. I don't know why we have this, it doesn't appear to have any commits from us. - opam-repository Same as opam. - xcp-fhs This is unused by anyone, as far as I know. - xen-unstable-mirror Just a mirror of the xen project repository. - xcp-storage-managers An old fork. sm.git should be used instead. - ocaml-sha A fork of upstream, no additional changesets from us. - ocaml-tar A fork of upstream, no additional changesets from us - ocaml-vhd A fork of upstream, no additional changesets from us Secondly, I believe some of the repositories should be transferred to the 'xenserver' organisation, which I think probably needs approval, as the xenserver org is not a part of the Linux Foundation. These are: - filesystem-summarise A tool to check for filesystem changes. Useful on XenServer for detecting when changes have been made to configuration files and so on. Not useful for general installations of the xapi project. - jiralib An old python library for talking to jira. Superseded by jira-python package. - mirrortest A test repository for checking Citrix's internal mirrors of the github repositories. - PRDup 'Pull Request Duplicator', a tool for helping to backport pull requests to different branches. - pull-request-manager Uses Citrix's internal build system to test pull requests - no longer used. - xs-pull-request-build-scripts Replacement for pull-request-manager - uses Citrix's internal build system to test pull requests, this time using jenkins. - xen-api-libs-specs Spec files used for building a lot of the xapi-project components for XenServer. There is large overlap with github.com/xenserver/buildroot - these should probably merge (or become more closely related). - xen-api-backports Similar to xen-api-libs-specs, but for Citrix's internal 'old buildsystem' as opposed to Citrix's internal 'newer buildsystem'. I don't think any of these is actually contentious - they probably should never have been part of the Linux Foundation, and have been there since we only had the one place on github to put things! Third, we have some libraries that are actually mirage core libraries. These should transfer over to the mirage organisation (remaining in LF, as mirage is a Xen Project subproject like xapi): - ocaml-gnt OCaml grant table manipulation. This code originated in the mirage project and was put here when it was split out of mirage-platform (see here: https://github.com/mirage/mirage-platform/commit/f532fc79af41e0e39b624a8e63dffc900bf1b7e4). - ocaml-xenstore This is the mirage implementation of a xenstore client library. Required for running mirage kernels on xen. We use the unix-flavour of this library. It also contains a WIP new version of the guts of a xenstore daemon, which will be a mirage-style unix process _or_ unikernel (xenstore stub-domain!) that should eventually be upstreamed into xen. - ocaml-xenstore-clients Slightly oddly named library that defines the unix transport mechanisms (unix-domain sockets) for using the ocaml-xenstore library. This is the unix counterpart to the internal shared-page mechanism used by mirage unikernels. - ocaml-evtchn Similar to ocaml-gnt - split from the main mirage code at around the same time as ocaml-gnt. - ocaml-xenstore-xen Unused by xapi-project. I believe in here lives the code that turns the xenstore daemon library from ocaml-xenstore into the actual xenstored stubdomain or process. We have a few repositories that are forks of upstream repos with some of our own changes in. We should get these changes upstreamed at some point, but for now we should leave them there, but recognise that these aren't necessarily part of the official Xapi Project (excepting where they are, e.g. ocaml-xen-lowlevel-libs, which is a staging area for upstreaming back into xen.git!) - oclock - ocamltest - ocaml-xen-lowlevel-libs - python-github2 Then there are generic ocaml libraries which could be used by other ocaml programs. I think these can live on in the xapi project organisation for now, but I wouldn't class them as 'core' xapi-project repos. - cdrom - netdev - ocamldoc-json - ocaml-encodings - ocaml-crc - ocaml-fd-send-recv - ocaml-netlink - ocaml-opasswd - ocaml-pci-db - ocaml-qmp - stdext - stunnel - nbd Which leaves us with the 'core' xapi project repositories: - blktap - blktap-dkms - example-ocaml-daemon - ffs - forkexecd - libvhd - message-switch - ocaml-rrdd-plugins - opam-repo-dev - rrd-transport - rrdd-plugin-legacy - rrddump - sm - sm-cli - squeezed - tapctl - vhd-tool - vncproxy - vncterm - vxs - wsproxy - xapi-codegen - xapi-libvirt-storage - xapi-project - xcp-eliloader - xcp-guest-templates - xcp-idl - xcp-inventory - xcp-networkd - xcp-rrd - xcp-rrdd - xen-api - xen-api-client - xen-api-libs - xen-api-libs-transitional - xen-api-sdk - xenops - xenops-cli - xenopsd Of the above lists that will remain in the xapi project, these repositories have incorrect forking status (they are marked as forks of someone here at Citrix, but shouldn't be): Forked from me (jonludlam on github): xen-api-libs-transitional xen-api-client xcp-guest-templates xcp-eliloader wsproxy tapctl libvhd blktap-dkms netdev nbd cdrom Forked from Dave Scott (djs55) xcp-idl vhd-tool ffs ocaml-vhd ocaml-tar ocaml-fd-send-recv Forked from Simon Beaumont (simonjbeaumont): ocaml-pci-db Forked from Mike McClurg (mcclurmc): ocaml-opasswd These forking relationship problems need to be fixed by the people who own the upstream repo. I don't think it's quite as simple as clicking the 'transfer repository' button. If anyone knows the exact procedure for doing this, could they please reply? In summary, I believe we need to: 1) delete some repositories 2) move some repositories to xenserver 3) move some repositories to mirage-project 4) transfer ownership of some repositories (just flip around the direction of the fork). 5) document all of this on the wiki! Any comments? Jon _______________________________________________ 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 Jun 10 11:29:13 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 10 Jun 2014 11:29: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 1WuKEo-0004l5-DL; Tue, 10 Jun 2014 11:29:10 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WuKEm-0004kg-Od for mirageos-devel@lists.xenproject.org; Tue, 10 Jun 2014 11:29:09 +0000 Received: from [85.158.143.35:46125] by server-1.bemta-4.messagelabs.com id FC/E7-09853-40CE6935; Tue, 10 Jun 2014 11:29:08 +0000 X-Env-Sender: balraj885@gmail.com X-Msg-Ref: server-7.tower-21.messagelabs.com!1402399746!10405690!1 X-Originating-IP: [74.125.82.179] 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.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 1583 invoked from network); 10 Jun 2014 11:29:06 -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; 10 Jun 2014 11:29:06 -0000 Received: by mail-we0-f179.google.com with SMTP id w62so2734956wes.24 for ; Tue, 10 Jun 2014 04:29:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=6Ygtg70SKhPx7m/9NFMXb5t/RBCnbc5DHDiACTW8emc=; b=nhGui2ME2C6wqzNpYiVBeP5IRQI31oy405T7PzbzInExF2dA6w1D9y4DHURda2MPiX 7U1C4Kk1xc+7GUQMx0xOODpfIrArDyEeLkjUYBODM5hOS/wyDXkF8USQI1i71r+liDXt 3SrqKuMiDNMgWzZ09585XObgkdCHPH2AxAIrEt3xL/1ACYuBkXYF3GpN8bRfm8nMasOR /xY91Px9tHlhTQypj9jX+b0DTzcVdxBrvXiLdZzLAiCS/6tYxb8K0helSiMeOx7DlcbH /3yCr4VuOAfaPTQm7izaWUomqXkHadJHQe+76vETbPlleOmRQ2anq56UclctPfbXX565 iJ5g== MIME-Version: 1.0 X-Received: by 10.194.84.101 with SMTP id x5mr40572345wjy.52.1402399744911; Tue, 10 Jun 2014 04:29:04 -0700 (PDT) Received: by 10.217.43.65 with HTTP; Tue, 10 Jun 2014 04:29:04 -0700 (PDT) In-Reply-To: <912BC56B-F927-4CDE-9C1E-D40BBD8A79CE@recoil.org> References: <537A1EAD.5090906@somerandomidiot.com> <538C9FB9.7070001@somerandomidiot.com> <912BC56B-F927-4CDE-9C1E-D40BBD8A79CE@recoil.org> Date: Tue, 10 Jun 2014 12:29:04 +0100 X-Google-Sender-Auth: oG6YqOs2C_kXRtw6VXy6AzsFQwc Message-ID: From: Balraj Singh To: Anil Madhavapeddy Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] OPW intern checking in! X-BeenThere: mirageos-devel@lists.xenproject.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="===============2187242528148141929==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============2187242528148141929== Content-Type: multipart/alternative; boundary=047d7bb04dcea0ef5c04fb79a2d0 --047d7bb04dcea0ef5c04fb79a2d0 Content-Type: text/plain; charset=UTF-8 Hi Anil, Just to confirm what I was showing you yesterday. This, along with possibly a few other defects, crept in as part of the changes that were made on Jan 23, "Simplify the listener mechanism to push it into the TCP input handler". The changes were all good improvements, and necessary, but this bug sneaked in. Mainly, as you say, this points to a lack of good regression tests and test infrastructure. I have tried to make some unit tests but for TCP there are many balls that have to be kept in the air and I could not quite do it in an automated way. The most successful of this kind of test was one in which a single VM would bring up 2 virtual interfaces and send specific patterns of data in both directions. It knew what to expect and it could, if necessary, even examine the state machines of the two TCPs. This was quite fragile - it would often stumble on something simple like bringing up two VIFs. The need of the hour for TCP really is to build a nice reliable networking regression test infrastructure. The test rig would need to be able to make different kinds of connections, be able to capture a packet trace, pull out the state of the test TCP and then make sense of it all together. Big project but could be fun. Probably also done many times before so if there is a ready made rig that we can adapt then that may be the best place to start. Balraj On Sun, Jun 8, 2014 at 7:13 PM, Anil Madhavapeddy wrote: > On 2 Jun 2014, at 17:00, Mindy wrote: > > > Hi, folks! Here's a quick summary of what I've been up to > > > > Late last week: dug more into observed lack of FINs from listening > unikernels, found the problem, and submitted a pull request to mirage-tcpip > > This had Balraj and me scratching our collective heads about how it > regressed, since we're *sure* it used to work (famous last words :-). > Balraj, any thoughts about it after your Friday investigations? > > This does highlight the importance of getting a regression test > infrastructure for networking in place though, since TCPIP in particular is > a very interlocked protocol. Any thoughts you may have about this using > scapy would be interesting... > > Meanwhile, I've released it as tcpip.1.1.3 into OPAM: > https://github.com/ocaml/opam-repository/pull/2207 > > > Today: make blog post on looking into that readable by humans who wish > not to be bored to death; finish unit test for upstream error reporting in > a `test_net_lwt` module in lib_test; send PR for error condition unit tests > to Cohttp upstream; fuzz harder! > > I'm still untangling Cohttp and Conduit to push releases out. My deadline > is to have some of the more obvious bugfixes done before the Mirage call on > Tuesday... > > -a --047d7bb04dcea0ef5c04fb79a2d0 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi Anil,

Just to confirm what I was sho= wing you yesterday. =C2=A0

This, along with possib= ly a few other defects, crept in as part of the changes that were made on J= an 23, "Simplify the listener mechanism to push it into the TCP input = handler". =C2=A0The changes were all good improvements, and necessary,= but this bug sneaked in. =C2=A0

Mainly, as you say, this points to a lack of good regre= ssion tests and test infrastructure. =C2=A0I have tried to make some unit t= ests but for TCP there are many balls that have to be kept in the air and I= could not quite do it in an automated way. =C2=A0The most successful of th= is kind of test was one in which a single VM would bring up 2 virtual inter= faces and send specific patterns of data in both directions. =C2=A0It knew = what to expect and it could, if necessary, even examine the state machines = of the two TCPs. =C2=A0This was quite fragile - it would often stumble on s= omething simple like bringing up two VIFs. =C2=A0

The need of the hour for TCP really is to build a nice = reliable networking regression test infrastructure. =C2=A0The test rig woul= d need to be able to make different kinds of connections, be able to captur= e a packet trace, pull out the state of the test TCP and then make sense of= it all together. =C2=A0Big project but could be fun. =C2=A0Probably also d= one many times before so if there is a ready made rig that we can adapt the= n that may be the best place to start.

Balraj

<= br>
On Sun, Jun 8, 2014 at 7:13 PM, Anil Madhavap= eddy <anil@recoil.org> wrote:
On 2 Jun 2014, at 17:00, Mindy <mindy@somerandomidiot.com> wro= te:

> Hi, folks! =C2=A0Here's a quick summary of w= hat I've been up to
>
> Late last week: dug more into observed lack of FINs from listening uni= kernels, found the problem, and submitted a pull request to mirage-tcpip
This had Balraj and me scratching our collective heads about how it r= egressed, since we're *sure* it used to work (famous last words :-). Ba= lraj, any thoughts about it after your Friday investigations?

This does highlight the importance of getting a regression test infrastruct= ure for networking in place though, since TCPIP in particular is a very int= erlocked protocol. =C2=A0Any thoughts you may have about this using scapy w= ould be interesting...

Meanwhile, I've released it as tcpip.1.1.3 into OPAM: https://git= hub.com/ocaml/opam-repository/pull/2207

> Today: make blog post on looking into that readable by humans who wish= not to be bored to death; finish unit test for upstream error reporting in= a `test_net_lwt` module in lib_test; send PR for error condition unit test= s to Cohttp upstream; fuzz harder!

I'm still untangling Cohttp and Conduit to push releases out. =C2= =A0My deadline is to have some of the more obvious bugfixes done before the= Mirage call on Tuesday...

-a

--047d7bb04dcea0ef5c04fb79a2d0-- --===============2187242528148141929== 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 --===============2187242528148141929==-- From mirageos-devel-bounces@lists.xenproject.org Tue Jun 10 11:29:13 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 10 Jun 2014 11:29: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 1WuKEo-0004l5-DL; Tue, 10 Jun 2014 11:29:10 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WuKEm-0004kg-Od for mirageos-devel@lists.xenproject.org; Tue, 10 Jun 2014 11:29:09 +0000 Received: from [85.158.143.35:46125] by server-1.bemta-4.messagelabs.com id FC/E7-09853-40CE6935; Tue, 10 Jun 2014 11:29:08 +0000 X-Env-Sender: balraj885@gmail.com X-Msg-Ref: server-7.tower-21.messagelabs.com!1402399746!10405690!1 X-Originating-IP: [74.125.82.179] 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.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 1583 invoked from network); 10 Jun 2014 11:29:06 -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; 10 Jun 2014 11:29:06 -0000 Received: by mail-we0-f179.google.com with SMTP id w62so2734956wes.24 for ; Tue, 10 Jun 2014 04:29:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=6Ygtg70SKhPx7m/9NFMXb5t/RBCnbc5DHDiACTW8emc=; b=nhGui2ME2C6wqzNpYiVBeP5IRQI31oy405T7PzbzInExF2dA6w1D9y4DHURda2MPiX 7U1C4Kk1xc+7GUQMx0xOODpfIrArDyEeLkjUYBODM5hOS/wyDXkF8USQI1i71r+liDXt 3SrqKuMiDNMgWzZ09585XObgkdCHPH2AxAIrEt3xL/1ACYuBkXYF3GpN8bRfm8nMasOR /xY91Px9tHlhTQypj9jX+b0DTzcVdxBrvXiLdZzLAiCS/6tYxb8K0helSiMeOx7DlcbH /3yCr4VuOAfaPTQm7izaWUomqXkHadJHQe+76vETbPlleOmRQ2anq56UclctPfbXX565 iJ5g== MIME-Version: 1.0 X-Received: by 10.194.84.101 with SMTP id x5mr40572345wjy.52.1402399744911; Tue, 10 Jun 2014 04:29:04 -0700 (PDT) Received: by 10.217.43.65 with HTTP; Tue, 10 Jun 2014 04:29:04 -0700 (PDT) In-Reply-To: <912BC56B-F927-4CDE-9C1E-D40BBD8A79CE@recoil.org> References: <537A1EAD.5090906@somerandomidiot.com> <538C9FB9.7070001@somerandomidiot.com> <912BC56B-F927-4CDE-9C1E-D40BBD8A79CE@recoil.org> Date: Tue, 10 Jun 2014 12:29:04 +0100 X-Google-Sender-Auth: oG6YqOs2C_kXRtw6VXy6AzsFQwc Message-ID: From: Balraj Singh To: Anil Madhavapeddy Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] OPW intern checking in! X-BeenThere: mirageos-devel@lists.xenproject.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="===============2187242528148141929==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============2187242528148141929== Content-Type: multipart/alternative; boundary=047d7bb04dcea0ef5c04fb79a2d0 --047d7bb04dcea0ef5c04fb79a2d0 Content-Type: text/plain; charset=UTF-8 Hi Anil, Just to confirm what I was showing you yesterday. This, along with possibly a few other defects, crept in as part of the changes that were made on Jan 23, "Simplify the listener mechanism to push it into the TCP input handler". The changes were all good improvements, and necessary, but this bug sneaked in. Mainly, as you say, this points to a lack of good regression tests and test infrastructure. I have tried to make some unit tests but for TCP there are many balls that have to be kept in the air and I could not quite do it in an automated way. The most successful of this kind of test was one in which a single VM would bring up 2 virtual interfaces and send specific patterns of data in both directions. It knew what to expect and it could, if necessary, even examine the state machines of the two TCPs. This was quite fragile - it would often stumble on something simple like bringing up two VIFs. The need of the hour for TCP really is to build a nice reliable networking regression test infrastructure. The test rig would need to be able to make different kinds of connections, be able to capture a packet trace, pull out the state of the test TCP and then make sense of it all together. Big project but could be fun. Probably also done many times before so if there is a ready made rig that we can adapt then that may be the best place to start. Balraj On Sun, Jun 8, 2014 at 7:13 PM, Anil Madhavapeddy wrote: > On 2 Jun 2014, at 17:00, Mindy wrote: > > > Hi, folks! Here's a quick summary of what I've been up to > > > > Late last week: dug more into observed lack of FINs from listening > unikernels, found the problem, and submitted a pull request to mirage-tcpip > > This had Balraj and me scratching our collective heads about how it > regressed, since we're *sure* it used to work (famous last words :-). > Balraj, any thoughts about it after your Friday investigations? > > This does highlight the importance of getting a regression test > infrastructure for networking in place though, since TCPIP in particular is > a very interlocked protocol. Any thoughts you may have about this using > scapy would be interesting... > > Meanwhile, I've released it as tcpip.1.1.3 into OPAM: > https://github.com/ocaml/opam-repository/pull/2207 > > > Today: make blog post on looking into that readable by humans who wish > not to be bored to death; finish unit test for upstream error reporting in > a `test_net_lwt` module in lib_test; send PR for error condition unit tests > to Cohttp upstream; fuzz harder! > > I'm still untangling Cohttp and Conduit to push releases out. My deadline > is to have some of the more obvious bugfixes done before the Mirage call on > Tuesday... > > -a --047d7bb04dcea0ef5c04fb79a2d0 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi Anil,

Just to confirm what I was sho= wing you yesterday. =C2=A0

This, along with possib= ly a few other defects, crept in as part of the changes that were made on J= an 23, "Simplify the listener mechanism to push it into the TCP input = handler". =C2=A0The changes were all good improvements, and necessary,= but this bug sneaked in. =C2=A0

Mainly, as you say, this points to a lack of good regre= ssion tests and test infrastructure. =C2=A0I have tried to make some unit t= ests but for TCP there are many balls that have to be kept in the air and I= could not quite do it in an automated way. =C2=A0The most successful of th= is kind of test was one in which a single VM would bring up 2 virtual inter= faces and send specific patterns of data in both directions. =C2=A0It knew = what to expect and it could, if necessary, even examine the state machines = of the two TCPs. =C2=A0This was quite fragile - it would often stumble on s= omething simple like bringing up two VIFs. =C2=A0

The need of the hour for TCP really is to build a nice = reliable networking regression test infrastructure. =C2=A0The test rig woul= d need to be able to make different kinds of connections, be able to captur= e a packet trace, pull out the state of the test TCP and then make sense of= it all together. =C2=A0Big project but could be fun. =C2=A0Probably also d= one many times before so if there is a ready made rig that we can adapt the= n that may be the best place to start.

Balraj

<= br>
On Sun, Jun 8, 2014 at 7:13 PM, Anil Madhavap= eddy <anil@recoil.org> wrote:
On 2 Jun 2014, at 17:00, Mindy <mindy@somerandomidiot.com> wro= te:

> Hi, folks! =C2=A0Here's a quick summary of w= hat I've been up to
>
> Late last week: dug more into observed lack of FINs from listening uni= kernels, found the problem, and submitted a pull request to mirage-tcpip
This had Balraj and me scratching our collective heads about how it r= egressed, since we're *sure* it used to work (famous last words :-). Ba= lraj, any thoughts about it after your Friday investigations?

This does highlight the importance of getting a regression test infrastruct= ure for networking in place though, since TCPIP in particular is a very int= erlocked protocol. =C2=A0Any thoughts you may have about this using scapy w= ould be interesting...

Meanwhile, I've released it as tcpip.1.1.3 into OPAM: https://git= hub.com/ocaml/opam-repository/pull/2207

> Today: make blog post on looking into that readable by humans who wish= not to be bored to death; finish unit test for upstream error reporting in= a `test_net_lwt` module in lib_test; send PR for error condition unit test= s to Cohttp upstream; fuzz harder!

I'm still untangling Cohttp and Conduit to push releases out. =C2= =A0My deadline is to have some of the more obvious bugfixes done before the= Mirage call on Tuesday...

-a

--047d7bb04dcea0ef5c04fb79a2d0-- --===============2187242528148141929== 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 --===============2187242528148141929==-- From mirageos-devel-bounces@lists.xenproject.org Tue Jun 10 12:04:09 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 10 Jun 2014 12:04: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 1WuKme-0006YE-L2; Tue, 10 Jun 2014 12:04:08 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WuKmc-0006XX-ED; Tue, 10 Jun 2014 12:04:06 +0000 Received: from [193.109.254.147:44600] by server-4.bemta-14.messagelabs.com id FA/64-02781-534F6935; Tue, 10 Jun 2014 12:04:05 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-6.tower-27.messagelabs.com!1402401844!10271957!1 X-Originating-IP: [74.125.82.48] X-SpamReason: No, hits=0.1 required=7.0 tests=HTML_50_60,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_32,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 13781 invoked from network); 10 Jun 2014 12:04:04 -0000 Received: from mail-wg0-f48.google.com (HELO mail-wg0-f48.google.com) (74.125.82.48) by server-6.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 10 Jun 2014 12:04:04 -0000 Received: by mail-wg0-f48.google.com with SMTP id n12so7092375wgh.7 for ; Tue, 10 Jun 2014 05:04:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:reply-to:user-agent:mime-version:to:cc :subject:content-type; bh=ZYb8JuTE/6nnS94//M8ihqB2Juo5YQU38NpNyhQ5UDE=; b=iQTWnuh9NmK0OKPdmKGMdEJtqh5vWUoi0oXxj6yNBTyHEPVjlHCrd0EPMdA0KTEvkG GGnMwHqQNwPulUZ7zIMDs3bALGRMZV8qszxg9KMgNwoMvQ/nwgps47/gCb9VLm6GsDgt qvHt4Au3HFlwks5bRJL36SpKKsFm85GJoqhn6totu0nelJ7hM7eHJDMr6rBkx0UawKb3 TJ7pkeW8nmzyyX1v6uEVO68aGIzVPnrXP/B0LmLqhB+7VMY0U370x0Ig40IIKcVmUwXM +dEFnqoSJsgOvJbiOzkWGnZFrofYB2Og2MPSLzJFMowOepDMCTPSr9gIKwev6tH+lNu2 vxeA== X-Received: by 10.194.243.104 with SMTP id wx8mr39971638wjc.32.1402401844038; Tue, 10 Jun 2014 05:04:04 -0700 (PDT) Received: from [172.16.25.10] (97e5a5cd.skybroadband.com. [151.229.165.205]) by mx.google.com with ESMTPSA id gi7sm20462737wib.1.2014.06.10.05.04.02 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 10 Jun 2014 05:04:03 -0700 (PDT) Message-ID: <5396F42E.9060901@xen.org> Date: Tue, 10 Jun 2014 13:03:58 +0100 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: "xen-devel@lists.xen.org" , "xen-api@lists.xen.org" Cc: advisory-board@lists.xenproject.org, "mirageos-devel@lists.xenproject.org" Subject: [MirageOS-devel] [Vote for approval by XAPI and Hypervisor maintainers] Windows PV Drivers Incubation Project Proposal (closing June 17th) X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: lars.kurth@xen.org List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============8626121984047938824==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org This is a multi-part message in MIME format. --===============8626121984047938824== Content-Type: multipart/alternative; boundary="------------080304090800070502020701" This is a multi-part message in MIME format. --------------080304090800070502020701 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Hi all, in accordance with http://xenproject.org/governance.html it is time to vote on http://wiki.xenproject.org/wiki/Windows_PV_Drivers_Incubation_Project_Proposal All maintainers of mature Xen Project sub-projects can vote, which includes the Hypervisor and XAPI project. The list of eligable people are * Hypervisor : see http://xenbits.xenproject.org/gitweb/?p=xen.git;a=blob;f=MAINTAINERS;hb=HEAD * XAPI : (see http://xenproject.org/developers/teams/xapi.html, XAPI PROJECT LEADS & COMMITERS and MAINTAINERS listed on https://github.com/xapi-project/xen-api) If in favour, reply "+1" to this thread If you do not care, reply "0" If you object, reply "-1" with a comment justifying the objection Best Regards Lars --------------080304090800070502020701 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Hi all,

in accordance with http://xenproject.org/governance.html it is time to vote on http://wiki.xenproject.org/wiki/Windows_PV_Drivers_Incubation_Project_Proposal

All maintainers of mature Xen Project sub-projects can vote, which includes the Hypervisor and XAPI project. The list of eligable people are
If in favour, reply "+1" to this thread
If you do not care, reply "0"
If you object, reply "-1" with a comment justifying the objection

Best Regards
Lars
--------------080304090800070502020701-- --===============8626121984047938824== 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 --===============8626121984047938824==-- From mirageos-devel-bounces@lists.xenproject.org Tue Jun 10 12:04:09 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 10 Jun 2014 12:04: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 1WuKme-0006YE-L2; Tue, 10 Jun 2014 12:04:08 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WuKmc-0006XX-ED; Tue, 10 Jun 2014 12:04:06 +0000 Received: from [193.109.254.147:44600] by server-4.bemta-14.messagelabs.com id FA/64-02781-534F6935; Tue, 10 Jun 2014 12:04:05 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-6.tower-27.messagelabs.com!1402401844!10271957!1 X-Originating-IP: [74.125.82.48] X-SpamReason: No, hits=0.1 required=7.0 tests=HTML_50_60,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_32,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 13781 invoked from network); 10 Jun 2014 12:04:04 -0000 Received: from mail-wg0-f48.google.com (HELO mail-wg0-f48.google.com) (74.125.82.48) by server-6.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 10 Jun 2014 12:04:04 -0000 Received: by mail-wg0-f48.google.com with SMTP id n12so7092375wgh.7 for ; Tue, 10 Jun 2014 05:04:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:reply-to:user-agent:mime-version:to:cc :subject:content-type; bh=ZYb8JuTE/6nnS94//M8ihqB2Juo5YQU38NpNyhQ5UDE=; b=iQTWnuh9NmK0OKPdmKGMdEJtqh5vWUoi0oXxj6yNBTyHEPVjlHCrd0EPMdA0KTEvkG GGnMwHqQNwPulUZ7zIMDs3bALGRMZV8qszxg9KMgNwoMvQ/nwgps47/gCb9VLm6GsDgt qvHt4Au3HFlwks5bRJL36SpKKsFm85GJoqhn6totu0nelJ7hM7eHJDMr6rBkx0UawKb3 TJ7pkeW8nmzyyX1v6uEVO68aGIzVPnrXP/B0LmLqhB+7VMY0U370x0Ig40IIKcVmUwXM +dEFnqoSJsgOvJbiOzkWGnZFrofYB2Og2MPSLzJFMowOepDMCTPSr9gIKwev6tH+lNu2 vxeA== X-Received: by 10.194.243.104 with SMTP id wx8mr39971638wjc.32.1402401844038; Tue, 10 Jun 2014 05:04:04 -0700 (PDT) Received: from [172.16.25.10] (97e5a5cd.skybroadband.com. [151.229.165.205]) by mx.google.com with ESMTPSA id gi7sm20462737wib.1.2014.06.10.05.04.02 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 10 Jun 2014 05:04:03 -0700 (PDT) Message-ID: <5396F42E.9060901@xen.org> Date: Tue, 10 Jun 2014 13:03:58 +0100 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: "xen-devel@lists.xen.org" , "xen-api@lists.xen.org" Cc: advisory-board@lists.xenproject.org, "mirageos-devel@lists.xenproject.org" Subject: [MirageOS-devel] [Vote for approval by XAPI and Hypervisor maintainers] Windows PV Drivers Incubation Project Proposal (closing June 17th) X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: lars.kurth@xen.org List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============8626121984047938824==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org This is a multi-part message in MIME format. --===============8626121984047938824== Content-Type: multipart/alternative; boundary="------------080304090800070502020701" This is a multi-part message in MIME format. --------------080304090800070502020701 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Hi all, in accordance with http://xenproject.org/governance.html it is time to vote on http://wiki.xenproject.org/wiki/Windows_PV_Drivers_Incubation_Project_Proposal All maintainers of mature Xen Project sub-projects can vote, which includes the Hypervisor and XAPI project. The list of eligable people are * Hypervisor : see http://xenbits.xenproject.org/gitweb/?p=xen.git;a=blob;f=MAINTAINERS;hb=HEAD * XAPI : (see http://xenproject.org/developers/teams/xapi.html, XAPI PROJECT LEADS & COMMITERS and MAINTAINERS listed on https://github.com/xapi-project/xen-api) If in favour, reply "+1" to this thread If you do not care, reply "0" If you object, reply "-1" with a comment justifying the objection Best Regards Lars --------------080304090800070502020701 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Hi all,

in accordance with http://xenproject.org/governance.html it is time to vote on http://wiki.xenproject.org/wiki/Windows_PV_Drivers_Incubation_Project_Proposal

All maintainers of mature Xen Project sub-projects can vote, which includes the Hypervisor and XAPI project. The list of eligable people are
If in favour, reply "+1" to this thread
If you do not care, reply "0"
If you object, reply "-1" with a comment justifying the objection

Best Regards
Lars
--------------080304090800070502020701-- --===============8626121984047938824== 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 --===============8626121984047938824==-- From mirageos-devel-bounces@lists.xenproject.org Tue Jun 10 12:22:48 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 10 Jun 2014 12:22: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 1WuL4h-0008Al-SV; Tue, 10 Jun 2014 12:22:47 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WuL4f-0008AN-MB for mirageos-devel@lists.xenproject.org; Tue, 10 Jun 2014 12:22:46 +0000 Received: from [85.158.139.211:59429] by server-8.bemta-5.messagelabs.com id 45/4D-11310-498F6935; Tue, 10 Jun 2014 12:22:44 +0000 X-Env-Sender: thomas.sanders@citrix.com X-Msg-Ref: server-15.tower-206.messagelabs.com!1402402963!5763005!1 X-Originating-IP: [185.25.65.24] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11703 invoked from network); 10 Jun 2014 12:22:43 -0000 Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (185.25.65.24) by server-15.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 10 Jun 2014 12:22:43 -0000 X-IronPort-AV: E=Sophos;i="4.98,1009,1392163200"; d="scan'208";a="20790194" Received: from unknown (HELO AMSPEX01CL03.citrite.net) ([10.69.60.9]) by AMSPIP01.EU.Citrix.com with ESMTP; 10 Jun 2014 12:22:43 +0000 Received: from AMSPEX01CL01.citrite.net ([169.254.6.105]) by AMSPEX01CL03.citrite.net ([169.254.8.89]) with mapi id 14.03.0181.006; Tue, 10 Jun 2014 14:22:43 +0200 From: Thomas Sanders To: 'Thomas Gazagnaire' , John Else Thread-Topic: [Xen-API] Xapi project repositories Thread-Index: AQHPhJGhV8l5AmBj5Uek7i5kFUIKNZtqAQAAgAABwYCAAD+jIA== Date: Tue, 10 Jun 2014 12:22:42 +0000 Message-ID: <06B80725944D5847804519C301FB872729D161@AMSPEX01CL01.citrite.net> References: <5396D482.6000706@eu.citrix.com> In-Reply-To: Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.69.129.53] MIME-Version: 1.0 X-DLP: AMS1 Cc: Lars Kurth , Jonathan Ludlam , "mirageos-devel@lists.xenproject.org" , "xen-api@lists.xen.org" Subject: Re: [MirageOS-devel] [Xen-API] Xapi project repositories X-BeenThere: mirageos-devel@lists.xenproject.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 Thomas Gazagnaire wrote: > >> These forking relationship problems need to be fixed by the people who > own the upstream repo. I don't think it's quite as simple as clicking the > 'transfer repository' button. If anyone knows the exact procedure for doing > this, could they please reply? > > > > What I've done in the past is clicked 'transfer repository' to xapi-project or > xenserver, then forked back to my own account. > > > > This seemed to work fine. I might only have done this with repos that had > only a master branch, so we should make sure it works with repos with > multiple branches (but I can't see why it wouldn't). > > Indeed, this should work fine, we did it plenty of time with mirage repos. > Github also automatically sets up redirect, so everything is transparent for > users. Good to know, though there would still be a certain amount of hassle involved in getting the initial parent repository into the right state, moving the xapi-project fork aside and so on. I asked Github Support for advice, and received this: > We can make a repository the root in the fork network if we receive > confirmation from the owner of the repository which is the current > root in the fork network. > If you get the owner(s) of the current fork network root repositories > to email us directly, we can make the adjustment to the fork network > as requested. This looks like the easiest approach. Thomas Sanders _______________________________________________ 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 Jun 10 12:22:48 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 10 Jun 2014 12:22: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 1WuL4h-0008Al-SV; Tue, 10 Jun 2014 12:22:47 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WuL4f-0008AN-MB for mirageos-devel@lists.xenproject.org; Tue, 10 Jun 2014 12:22:46 +0000 Received: from [85.158.139.211:59429] by server-8.bemta-5.messagelabs.com id 45/4D-11310-498F6935; Tue, 10 Jun 2014 12:22:44 +0000 X-Env-Sender: thomas.sanders@citrix.com X-Msg-Ref: server-15.tower-206.messagelabs.com!1402402963!5763005!1 X-Originating-IP: [185.25.65.24] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11703 invoked from network); 10 Jun 2014 12:22:43 -0000 Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (185.25.65.24) by server-15.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 10 Jun 2014 12:22:43 -0000 X-IronPort-AV: E=Sophos;i="4.98,1009,1392163200"; d="scan'208";a="20790194" Received: from unknown (HELO AMSPEX01CL03.citrite.net) ([10.69.60.9]) by AMSPIP01.EU.Citrix.com with ESMTP; 10 Jun 2014 12:22:43 +0000 Received: from AMSPEX01CL01.citrite.net ([169.254.6.105]) by AMSPEX01CL03.citrite.net ([169.254.8.89]) with mapi id 14.03.0181.006; Tue, 10 Jun 2014 14:22:43 +0200 From: Thomas Sanders To: 'Thomas Gazagnaire' , John Else Thread-Topic: [Xen-API] Xapi project repositories Thread-Index: AQHPhJGhV8l5AmBj5Uek7i5kFUIKNZtqAQAAgAABwYCAAD+jIA== Date: Tue, 10 Jun 2014 12:22:42 +0000 Message-ID: <06B80725944D5847804519C301FB872729D161@AMSPEX01CL01.citrite.net> References: <5396D482.6000706@eu.citrix.com> In-Reply-To: Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.69.129.53] MIME-Version: 1.0 X-DLP: AMS1 Cc: Lars Kurth , Jonathan Ludlam , "mirageos-devel@lists.xenproject.org" , "xen-api@lists.xen.org" Subject: Re: [MirageOS-devel] [Xen-API] Xapi project repositories X-BeenThere: mirageos-devel@lists.xenproject.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 Thomas Gazagnaire wrote: > >> These forking relationship problems need to be fixed by the people who > own the upstream repo. I don't think it's quite as simple as clicking the > 'transfer repository' button. If anyone knows the exact procedure for doing > this, could they please reply? > > > > What I've done in the past is clicked 'transfer repository' to xapi-project or > xenserver, then forked back to my own account. > > > > This seemed to work fine. I might only have done this with repos that had > only a master branch, so we should make sure it works with repos with > multiple branches (but I can't see why it wouldn't). > > Indeed, this should work fine, we did it plenty of time with mirage repos. > Github also automatically sets up redirect, so everything is transparent for > users. Good to know, though there would still be a certain amount of hassle involved in getting the initial parent repository into the right state, moving the xapi-project fork aside and so on. I asked Github Support for advice, and received this: > We can make a repository the root in the fork network if we receive > confirmation from the owner of the repository which is the current > root in the fork network. > If you get the owner(s) of the current fork network root repositories > to email us directly, we can make the adjustment to the fork network > as requested. This looks like the easiest approach. Thomas Sanders _______________________________________________ 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 Jun 10 12:32:02 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 10 Jun 2014 12:32: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 1WuLDa-0000SX-1N; Tue, 10 Jun 2014 12:31:58 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WuLDY-0000SF-SR; Tue, 10 Jun 2014 12:31:57 +0000 Received: from [85.158.139.211:37652] by server-14.bemta-5.messagelabs.com id 73/77-15696-CBAF6935; Tue, 10 Jun 2014 12:31:56 +0000 X-Env-Sender: thomas.sanders@citrix.com X-Msg-Ref: server-2.tower-206.messagelabs.com!1402403515!9112895!1 X-Originating-IP: [185.25.65.24] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20472 invoked from network); 10 Jun 2014 12:31:55 -0000 Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (185.25.65.24) by server-2.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 10 Jun 2014 12:31:55 -0000 X-IronPort-AV: E=Sophos;i="4.98,1009,1392163200"; d="scan'208";a="20792827" Received: from unknown (HELO AMSPEX01CL02.citrite.net) ([10.69.60.9]) by AMSPIP01.EU.Citrix.com with ESMTP; 10 Jun 2014 12:31:47 +0000 Received: from AMSPEX01CL01.citrite.net ([169.254.6.105]) by AMSPEX01CL02.citrite.net ([10.69.46.33]) with mapi id 14.03.0181.006; Tue, 10 Jun 2014 14:31:47 +0200 From: Thomas Sanders To: "'lars.kurth@xen.org'" , "xen-devel@lists.xen.org" , "xen-api@lists.xen.org" Thread-Topic: [Xen-devel] [Vote for approval by XAPI and Hypervisor maintainers] Windows PV Drivers Incubation Project Proposal (closing June 17th) Thread-Index: AQHPhKR/EFmq+27rFkC3bWalORoGk5tqRjmw Date: Tue, 10 Jun 2014 12:31:46 +0000 Message-ID: <06B80725944D5847804519C301FB872729D187@AMSPEX01CL01.citrite.net> References: <5396F42E.9060901@xen.org> In-Reply-To: <5396F42E.9060901@xen.org> Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.69.129.53] MIME-Version: 1.0 X-DLP: AMS1 Cc: "advisory-board@lists.xenproject.org" , "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] [Xen-devel] [Vote for approval by XAPI and Hypervisor maintainers] Windows PV Drivers Incubation Project Proposal (closing June 17th) X-BeenThere: mirageos-devel@lists.xenproject.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 From: xen-devel-bounces@lists.xen.org [mailto:xen-devel-bounces@lists.xen.org] On Behalf Of Lars Kurth On 10 June 2014 at 1:04 PM Lars Kurth wrote: > in accordance with http://xenproject.org/governance.html it is time to vote on http://wiki.xenproject.org/wiki/Windows_PV_Drivers_Incubation_Project_Proposal +1 _______________________________________________ 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 Jun 10 12:32:02 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 10 Jun 2014 12:32: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 1WuLDa-0000SX-1N; Tue, 10 Jun 2014 12:31:58 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WuLDY-0000SF-SR; Tue, 10 Jun 2014 12:31:57 +0000 Received: from [85.158.139.211:37652] by server-14.bemta-5.messagelabs.com id 73/77-15696-CBAF6935; Tue, 10 Jun 2014 12:31:56 +0000 X-Env-Sender: thomas.sanders@citrix.com X-Msg-Ref: server-2.tower-206.messagelabs.com!1402403515!9112895!1 X-Originating-IP: [185.25.65.24] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20472 invoked from network); 10 Jun 2014 12:31:55 -0000 Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (185.25.65.24) by server-2.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 10 Jun 2014 12:31:55 -0000 X-IronPort-AV: E=Sophos;i="4.98,1009,1392163200"; d="scan'208";a="20792827" Received: from unknown (HELO AMSPEX01CL02.citrite.net) ([10.69.60.9]) by AMSPIP01.EU.Citrix.com with ESMTP; 10 Jun 2014 12:31:47 +0000 Received: from AMSPEX01CL01.citrite.net ([169.254.6.105]) by AMSPEX01CL02.citrite.net ([10.69.46.33]) with mapi id 14.03.0181.006; Tue, 10 Jun 2014 14:31:47 +0200 From: Thomas Sanders To: "'lars.kurth@xen.org'" , "xen-devel@lists.xen.org" , "xen-api@lists.xen.org" Thread-Topic: [Xen-devel] [Vote for approval by XAPI and Hypervisor maintainers] Windows PV Drivers Incubation Project Proposal (closing June 17th) Thread-Index: AQHPhKR/EFmq+27rFkC3bWalORoGk5tqRjmw Date: Tue, 10 Jun 2014 12:31:46 +0000 Message-ID: <06B80725944D5847804519C301FB872729D187@AMSPEX01CL01.citrite.net> References: <5396F42E.9060901@xen.org> In-Reply-To: <5396F42E.9060901@xen.org> Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.69.129.53] MIME-Version: 1.0 X-DLP: AMS1 Cc: "advisory-board@lists.xenproject.org" , "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] [Xen-devel] [Vote for approval by XAPI and Hypervisor maintainers] Windows PV Drivers Incubation Project Proposal (closing June 17th) X-BeenThere: mirageos-devel@lists.xenproject.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 From: xen-devel-bounces@lists.xen.org [mailto:xen-devel-bounces@lists.xen.org] On Behalf Of Lars Kurth On 10 June 2014 at 1:04 PM Lars Kurth wrote: > in accordance with http://xenproject.org/governance.html it is time to vote on http://wiki.xenproject.org/wiki/Windows_PV_Drivers_Incubation_Project_Proposal +1 _______________________________________________ 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 Jun 10 13:59:15 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 10 Jun 2014 13:59: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 1WuMZx-0007kG-SX; Tue, 10 Jun 2014 13:59:09 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WuMZw-0007kA-KH for mirageos-devel@lists.xenproject.org; Tue, 10 Jun 2014 13:59:08 +0000 Received: from [193.109.254.147:28588] by server-2.bemta-14.messagelabs.com id DF/13-21684-B2F07935; Tue, 10 Jun 2014 13:59:07 +0000 X-Env-Sender: scott.dj@gmail.com X-Msg-Ref: server-2.tower-27.messagelabs.com!1402408745!10320712!1 X-Originating-IP: [209.85.160.47] X-SpamReason: No, hits=0.3 required=7.0 tests=HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7440 invoked from network); 10 Jun 2014 13:59:06 -0000 Received: from mail-pb0-f47.google.com (HELO mail-pb0-f47.google.com) (209.85.160.47) by server-2.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 10 Jun 2014 13:59:06 -0000 Received: by mail-pb0-f47.google.com with SMTP id un15so880296pbc.20 for ; Tue, 10 Jun 2014 06:59:04 -0700 (PDT) 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=JkfuzniuJi4klhPAQ9JBuJO7juBEBC4/De21l2lX0Zo=; b=Dj719S7t7Y+8VLqdHxxzwcJebWKKQPnztcnikXOs5UGF6KK83fcEh+oSDH+3OePN2h L4uqy9zMRDccSmVvtqVIcz9HaZiiSFc72QrtdJCSpeJwsue7QfIQiy6Xuj8Qli+ck/JZ 8jrTHRnrb4oE7W5CU5iwK5edVHEY3AAMsCBgMDs+latLgDJbzrleIcGnn7uoXUTe2QoU WRz5Ob9pmQIwNQyoqQX9kVZEv/+N1DSjd5ce5XPCYg6LYYMCgx458EZCy+djl4v5pplN stZAAgOJxa2AG/wgeh28sCpTshc0sulSSWBAJuT+ol6YEybn1vUknQs85mDUwsO686o8 E6wg== MIME-Version: 1.0 X-Received: by 10.69.26.103 with SMTP id ix7mr11845388pbd.41.1402408744912; Tue, 10 Jun 2014 06:59:04 -0700 (PDT) Received: by 10.70.11.65 with HTTP; Tue, 10 Jun 2014 06:59:04 -0700 (PDT) Date: Tue, 10 Jun 2014 14:59:04 +0100 Message-ID: From: David Scott To: "mirageos-devel@lists.xenproject.org" Subject: [MirageOS-devel] Mirage weekly call today, 4pm BST (== GMT + 1) X-BeenThere: mirageos-devel@lists.xenproject.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="===============7621958778951943349==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============7621958778951943349== Content-Type: multipart/alternative; boundary=001a1135eaac120bb604fb7bbbf1 --001a1135eaac120bb604fb7bbbf1 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi, So far on the agenda we have: =E2=80=A2 Unikernel deployment (bytemark machines) (Amir) =E2=80=A2 Lots of fist pumping because of this [1] [2] (all) * Irmin update (Thomas) [1] https://twitter.com/ID_AA_Carmack/status/476046680698003458 [2] http://www.youtube.com/watch?v=3D-FucbvoFFy0 1. Please join my meeting. https://www1.gotomeeting.com/join/591890401 Note the dial-in numbers seem to have changed. The new ones are visible if you join the meeting online. I don't have a full list to hand but I believe the US one is: +1 (213) 493-0008 If you need a local number, send me an email before the meeting. I'll try to email you a number before the meeting starts. Cheers, --=20 Dave Scott --001a1135eaac120bb604fb7bbbf1 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi,

=
So far on = the agenda we have:

=E2=80=A2 Unikerne= l deployment (bytemark machines) (Amir)

=E2=80=A2 Lots of = fist pumping because of this [1] [2] (all)

* Irmin update (Th= omas)

<= span style=3D"background-color:rgb(255,255,255)">

<= span style=3D"background-color:rgb(255,255,255)">

[1] https://twitter.c= om/ID_AA_Carmack/status/476046680698003458

[2]=C2=A0http://www.youtube.com/watch?v=3D-Fuc= bvoFFy0



1.= =C2=A0Please join my meeting.

Note the dial-in numbers seem to have changed. The new ones are vis= ible if you join the meeting online. I don't have a full list to hand b= ut I believe the US one is:


If you need a local number, send me an email before the meeting. I'll= try to email you a number before the meeting starts.

Cheers,

--
Dave Scott
--001a1135eaac120bb604fb7bbbf1-- --===============7621958778951943349== 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 --===============7621958778951943349==-- From mirageos-devel-bounces@lists.xenproject.org Tue Jun 10 13:59:15 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 10 Jun 2014 13:59: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 1WuMZx-0007kG-SX; Tue, 10 Jun 2014 13:59:09 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WuMZw-0007kA-KH for mirageos-devel@lists.xenproject.org; Tue, 10 Jun 2014 13:59:08 +0000 Received: from [193.109.254.147:28588] by server-2.bemta-14.messagelabs.com id DF/13-21684-B2F07935; Tue, 10 Jun 2014 13:59:07 +0000 X-Env-Sender: scott.dj@gmail.com X-Msg-Ref: server-2.tower-27.messagelabs.com!1402408745!10320712!1 X-Originating-IP: [209.85.160.47] X-SpamReason: No, hits=0.3 required=7.0 tests=HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7440 invoked from network); 10 Jun 2014 13:59:06 -0000 Received: from mail-pb0-f47.google.com (HELO mail-pb0-f47.google.com) (209.85.160.47) by server-2.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 10 Jun 2014 13:59:06 -0000 Received: by mail-pb0-f47.google.com with SMTP id un15so880296pbc.20 for ; Tue, 10 Jun 2014 06:59:04 -0700 (PDT) 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=JkfuzniuJi4klhPAQ9JBuJO7juBEBC4/De21l2lX0Zo=; b=Dj719S7t7Y+8VLqdHxxzwcJebWKKQPnztcnikXOs5UGF6KK83fcEh+oSDH+3OePN2h L4uqy9zMRDccSmVvtqVIcz9HaZiiSFc72QrtdJCSpeJwsue7QfIQiy6Xuj8Qli+ck/JZ 8jrTHRnrb4oE7W5CU5iwK5edVHEY3AAMsCBgMDs+latLgDJbzrleIcGnn7uoXUTe2QoU WRz5Ob9pmQIwNQyoqQX9kVZEv/+N1DSjd5ce5XPCYg6LYYMCgx458EZCy+djl4v5pplN stZAAgOJxa2AG/wgeh28sCpTshc0sulSSWBAJuT+ol6YEybn1vUknQs85mDUwsO686o8 E6wg== MIME-Version: 1.0 X-Received: by 10.69.26.103 with SMTP id ix7mr11845388pbd.41.1402408744912; Tue, 10 Jun 2014 06:59:04 -0700 (PDT) Received: by 10.70.11.65 with HTTP; Tue, 10 Jun 2014 06:59:04 -0700 (PDT) Date: Tue, 10 Jun 2014 14:59:04 +0100 Message-ID: From: David Scott To: "mirageos-devel@lists.xenproject.org" Subject: [MirageOS-devel] Mirage weekly call today, 4pm BST (== GMT + 1) X-BeenThere: mirageos-devel@lists.xenproject.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="===============7621958778951943349==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============7621958778951943349== Content-Type: multipart/alternative; boundary=001a1135eaac120bb604fb7bbbf1 --001a1135eaac120bb604fb7bbbf1 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi, So far on the agenda we have: =E2=80=A2 Unikernel deployment (bytemark machines) (Amir) =E2=80=A2 Lots of fist pumping because of this [1] [2] (all) * Irmin update (Thomas) [1] https://twitter.com/ID_AA_Carmack/status/476046680698003458 [2] http://www.youtube.com/watch?v=3D-FucbvoFFy0 1. Please join my meeting. https://www1.gotomeeting.com/join/591890401 Note the dial-in numbers seem to have changed. The new ones are visible if you join the meeting online. I don't have a full list to hand but I believe the US one is: +1 (213) 493-0008 If you need a local number, send me an email before the meeting. I'll try to email you a number before the meeting starts. Cheers, --=20 Dave Scott --001a1135eaac120bb604fb7bbbf1 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi,

=
So far on = the agenda we have:

=E2=80=A2 Unikerne= l deployment (bytemark machines) (Amir)

=E2=80=A2 Lots of = fist pumping because of this [1] [2] (all)

* Irmin update (Th= omas)

<= span style=3D"background-color:rgb(255,255,255)">

<= span style=3D"background-color:rgb(255,255,255)">

[1] https://twitter.c= om/ID_AA_Carmack/status/476046680698003458

[2]=C2=A0http://www.youtube.com/watch?v=3D-Fuc= bvoFFy0



1.= =C2=A0Please join my meeting.

Note the dial-in numbers seem to have changed. The new ones are vis= ible if you join the meeting online. I don't have a full list to hand b= ut I believe the US one is:


If you need a local number, send me an email before the meeting. I'll= try to email you a number before the meeting starts.

Cheers,

--
Dave Scott
--001a1135eaac120bb604fb7bbbf1-- --===============7621958778951943349== 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 --===============7621958778951943349==-- From mirageos-devel-bounces@lists.xenproject.org Tue Jun 10 14:01:40 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 10 Jun 2014 14: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 1WuMcO-00089J-3y; Tue, 10 Jun 2014 14:01:40 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WuMcN-000896-BK for mirageos-devel@lists.xenproject.org; Tue, 10 Jun 2014 14:01:39 +0000 Received: from [85.158.139.211:28012] by server-17.bemta-5.messagelabs.com id F2/16-09046-2CF07935; Tue, 10 Jun 2014 14:01:38 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-13.tower-206.messagelabs.com!1402408897!9170260!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests=HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 1208 invoked from network); 10 Jun 2014 14:01:37 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-13.tower-206.messagelabs.com with SMTP; 10 Jun 2014 14:01:37 -0000 Received: (qmail 13051 invoked by uid 634); 10 Jun 2014 14:01:36 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED,HTML_MESSAGE X-Spam-Check-By: dark.recoil.org Received: from volstagg-0.srg.cl.cam.ac.uk (HELO flick.office) (128.232.32.232) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Tue, 10 Jun 2014 15:01:36 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\)) From: Anil Madhavapeddy In-Reply-To: Date: Tue, 10 Jun 2014 15:01:34 +0100 Message-Id: <2BFA49C2-E2CE-40F4-A51D-C38115F1E6A6@recoil.org> References: To: David Scott X-Mailer: Apple Mail (2.1874) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Mirage weekly call today, 4pm BST (== GMT + 1) X-BeenThere: mirageos-devel@lists.xenproject.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="===============8673540655569378625==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============8673540655569378625== Content-Type: multipart/alternative; boundary="Apple-Mail=_98078048-F3B7-4F97-9BBA-EFBCFB3C92C1" --Apple-Mail=_98078048-F3B7-4F97-9BBA-EFBCFB3C92C1 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 I'll also update on the channel/conduit progress. On 10 Jun 2014, at 14:59, David Scott wrote: > Hi, >=20 > So far on the agenda we have: >=20 > =95 Unikernel deployment (bytemark machines) (Amir) > =95 Lots of fist pumping because of this [1] [2] (all) > * Irmin update (Thomas) >=20 >=20 > [1] https://twitter.com/ID_AA_Carmack/status/476046680698003458 > [2] http://www.youtube.com/watch?v=3D-FucbvoFFy0 >=20 >=20 > 1. Please join my meeting. > https://www1.gotomeeting.com/join/591890401 >=20 > Note the dial-in numbers seem to have changed. The new ones are = visible if you join the meeting online. I don't have a full list to hand = but I believe the US one is: >=20 > +1 (213) 493-0008 >=20 > If you need a local number, send me an email before the meeting. I'll = try to email you a number before the meeting starts. >=20 > Cheers, >=20 > --=20 > Dave Scott > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --Apple-Mail=_98078048-F3B7-4F97-9BBA-EFBCFB3C92C1 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=windows-1252 I'll = also update on the channel/conduit progress.
On 10 Jun = 2014, at 14:59, David Scott <scott.dj@gmail.com> = wrote:

Hi,

So far on the = agenda we have:

=95 Unikernel = deployment (bytemark machines) (Amir)
=95 Lots of fist = pumping because of this [1] [2] (all)
* Irmin update = (Thomas)

=

=
[1] https= ://twitter.com/ID_AA_Carmack/status/476046680698003458
[2] <= a href=3D"http://www.youtube.com/watch?v=3D-FucbvoFFy0" = style=3D"font-family:Menlo-Regular;font-size:11px">http://www.youtube.com/= watch?v=3D-FucbvoFFy0


1. =  Please join my meeting.

Note the dial-in numbers seem to have changed. = The new ones are visible if you join the meeting online. I don't have a = full list to hand but I believe the US one is:


If you need a local number, send = me an email before the meeting. I'll try to email you a number before = the meeting starts.

Cheers,

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

= --Apple-Mail=_98078048-F3B7-4F97-9BBA-EFBCFB3C92C1-- --===============8673540655569378625== 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 --===============8673540655569378625==-- From mirageos-devel-bounces@lists.xenproject.org Tue Jun 10 14:01:40 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 10 Jun 2014 14: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 1WuMcO-00089J-3y; Tue, 10 Jun 2014 14:01:40 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WuMcN-000896-BK for mirageos-devel@lists.xenproject.org; Tue, 10 Jun 2014 14:01:39 +0000 Received: from [85.158.139.211:28012] by server-17.bemta-5.messagelabs.com id F2/16-09046-2CF07935; Tue, 10 Jun 2014 14:01:38 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-13.tower-206.messagelabs.com!1402408897!9170260!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests=HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 1208 invoked from network); 10 Jun 2014 14:01:37 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-13.tower-206.messagelabs.com with SMTP; 10 Jun 2014 14:01:37 -0000 Received: (qmail 13051 invoked by uid 634); 10 Jun 2014 14:01:36 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED,HTML_MESSAGE X-Spam-Check-By: dark.recoil.org Received: from volstagg-0.srg.cl.cam.ac.uk (HELO flick.office) (128.232.32.232) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Tue, 10 Jun 2014 15:01:36 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\)) From: Anil Madhavapeddy In-Reply-To: Date: Tue, 10 Jun 2014 15:01:34 +0100 Message-Id: <2BFA49C2-E2CE-40F4-A51D-C38115F1E6A6@recoil.org> References: To: David Scott X-Mailer: Apple Mail (2.1874) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Mirage weekly call today, 4pm BST (== GMT + 1) X-BeenThere: mirageos-devel@lists.xenproject.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="===============8673540655569378625==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============8673540655569378625== Content-Type: multipart/alternative; boundary="Apple-Mail=_98078048-F3B7-4F97-9BBA-EFBCFB3C92C1" --Apple-Mail=_98078048-F3B7-4F97-9BBA-EFBCFB3C92C1 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 I'll also update on the channel/conduit progress. On 10 Jun 2014, at 14:59, David Scott wrote: > Hi, >=20 > So far on the agenda we have: >=20 > =95 Unikernel deployment (bytemark machines) (Amir) > =95 Lots of fist pumping because of this [1] [2] (all) > * Irmin update (Thomas) >=20 >=20 > [1] https://twitter.com/ID_AA_Carmack/status/476046680698003458 > [2] http://www.youtube.com/watch?v=3D-FucbvoFFy0 >=20 >=20 > 1. Please join my meeting. > https://www1.gotomeeting.com/join/591890401 >=20 > Note the dial-in numbers seem to have changed. The new ones are = visible if you join the meeting online. I don't have a full list to hand = but I believe the US one is: >=20 > +1 (213) 493-0008 >=20 > If you need a local number, send me an email before the meeting. I'll = try to email you a number before the meeting starts. >=20 > Cheers, >=20 > --=20 > Dave Scott > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --Apple-Mail=_98078048-F3B7-4F97-9BBA-EFBCFB3C92C1 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=windows-1252 I'll = also update on the channel/conduit progress.
On 10 Jun = 2014, at 14:59, David Scott <scott.dj@gmail.com> = wrote:

Hi,

So far on the = agenda we have:

=95 Unikernel = deployment (bytemark machines) (Amir)
=95 Lots of fist = pumping because of this [1] [2] (all)
* Irmin update = (Thomas)

=

=
[1] https= ://twitter.com/ID_AA_Carmack/status/476046680698003458
[2] <= a href=3D"http://www.youtube.com/watch?v=3D-FucbvoFFy0" = style=3D"font-family:Menlo-Regular;font-size:11px">http://www.youtube.com/= watch?v=3D-FucbvoFFy0


1. =  Please join my meeting.

Note the dial-in numbers seem to have changed. = The new ones are visible if you join the meeting online. I don't have a = full list to hand but I believe the US one is:


If you need a local number, send = me an email before the meeting. I'll try to email you a number before = the meeting starts.

Cheers,

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

= --Apple-Mail=_98078048-F3B7-4F97-9BBA-EFBCFB3C92C1-- --===============8673540655569378625== 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 --===============8673540655569378625==-- From mirageos-devel-bounces@lists.xenproject.org Tue Jun 10 22:24:10 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 10 Jun 2014 22:24: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 1WuUSb-00018W-Sw; Tue, 10 Jun 2014 22:24:05 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WuUSY-00018R-KN for mirageos-devel@lists.xenproject.org; Tue, 10 Jun 2014 22:24:04 +0000 Received: from [85.158.143.35:3756] by server-2.bemta-4.messagelabs.com id E2/E4-06539-18587935; Tue, 10 Jun 2014 22:24:01 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-6.tower-21.messagelabs.com!1402439040!10467665!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20311 invoked from network); 10 Jun 2014 22:24:00 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-6.tower-21.messagelabs.com with SMTP; 10 Jun 2014 22:24:00 -0000 Received: (qmail 16057 invoked by uid 634); 10 Jun 2014 22:24:00 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net (HELO [192.168.1.113]) (86.30.244.239) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Tue, 10 Jun 2014 23:23:56 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\)) From: Anil Madhavapeddy In-Reply-To: Date: Tue, 10 Jun 2014 23:23:55 +0100 Message-Id: References: <537A1EAD.5090906@somerandomidiot.com> <538C9FB9.7070001@somerandomidiot.com> <912BC56B-F927-4CDE-9C1E-D40BBD8A79CE@recoil.org> To: Balraj Singh X-Mailer: Apple Mail (2.1874) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] OPW intern checking in! X-BeenThere: mirageos-devel@lists.xenproject.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 10 Jun 2014, at 12:29, Balraj Singh wrote: > Hi Anil, > > Just to confirm what I was showing you yesterday. > > This, along with possibly a few other defects, crept in as part of the changes that were made on Jan 23, "Simplify the listener mechanism to push it into the TCP input handler". The changes were all good improvements, and necessary, but this bug sneaked in. Thanks for tracking these down. I believe this only affects the server side (which confirms Mindy's findings), and were due to lifting out some datastructures in the listening code, and making them available to the application directly. A short-term fix is probably around making the connection callback an option type again, but it would be better to make this more explicit to avoid the same mistake in the future. i.e., instead of type t = int option type t = [ `Connection of int | `Connection_being_established ] the latter is obviously much clearer. > > Mainly, as you say, this points to a lack of good regression tests and test infrastructure. I have tried to make some unit tests but for TCP there are many balls that have to be kept in the air and I could not quite do it in an automated way. The most successful of this kind of test was one in which a single VM would bring up 2 virtual interfaces and send specific patterns of data in both directions. It knew what to expect and it could, if necessary, even examine the state machines of the two TCPs. This was quite fragile - it would often stumble on something simple like bringing up two VIFs. The other option here is not to use Xen for testing the net stack at all, but just use Linux with two tap interfaces. That gives us the ability to use tcpdump to inspect the traces as well... > On 2 Jun 2014, at 17:00, Mindy wrote: > My first thought is that I don't know how to get the workflow I've been using (start up a unikernel in Xen and throw a bunch of stuff at it from scapy) set up in Travis, but if that doesn't seem like obviously the wrong thing to do, I can look into it. I would still like to look at Quickcheck as well. Similar to answer to Balraj above -- instead of spinning up a Xen VM, spin up a user-level stack on Linux instead (using `NET=direct mirage configure --unix` in the various skeleton examples). However, one downside to Travis is that it uses LXC (containers) for its isolation, and so doesn't support tuntap. This does leave Balraj's suggestion as the best one: create two network stacks in one Mirage program and get them talking to each other! > > Also, an update - Last week I wrote up another Treaty of Westphalia on finding a TCP bug and made Mirage implementations of chargen, discard, and echo for use in testing the TCP stack more directly. Today, I'm planning on getting a whole bunch of data from them and (I hope) finding some interesting results. The chargen/discard/echo sounds very useful indeed -- how about adding those directly into mirage/mirage-tcpip in a lib_test/ (or examples/) directory? -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 Jun 10 22:24:10 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 10 Jun 2014 22:24: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 1WuUSb-00018W-Sw; Tue, 10 Jun 2014 22:24:05 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WuUSY-00018R-KN for mirageos-devel@lists.xenproject.org; Tue, 10 Jun 2014 22:24:04 +0000 Received: from [85.158.143.35:3756] by server-2.bemta-4.messagelabs.com id E2/E4-06539-18587935; Tue, 10 Jun 2014 22:24:01 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-6.tower-21.messagelabs.com!1402439040!10467665!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20311 invoked from network); 10 Jun 2014 22:24:00 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-6.tower-21.messagelabs.com with SMTP; 10 Jun 2014 22:24:00 -0000 Received: (qmail 16057 invoked by uid 634); 10 Jun 2014 22:24:00 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net (HELO [192.168.1.113]) (86.30.244.239) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Tue, 10 Jun 2014 23:23:56 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\)) From: Anil Madhavapeddy In-Reply-To: Date: Tue, 10 Jun 2014 23:23:55 +0100 Message-Id: References: <537A1EAD.5090906@somerandomidiot.com> <538C9FB9.7070001@somerandomidiot.com> <912BC56B-F927-4CDE-9C1E-D40BBD8A79CE@recoil.org> To: Balraj Singh X-Mailer: Apple Mail (2.1874) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] OPW intern checking in! X-BeenThere: mirageos-devel@lists.xenproject.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 10 Jun 2014, at 12:29, Balraj Singh wrote: > Hi Anil, > > Just to confirm what I was showing you yesterday. > > This, along with possibly a few other defects, crept in as part of the changes that were made on Jan 23, "Simplify the listener mechanism to push it into the TCP input handler". The changes were all good improvements, and necessary, but this bug sneaked in. Thanks for tracking these down. I believe this only affects the server side (which confirms Mindy's findings), and were due to lifting out some datastructures in the listening code, and making them available to the application directly. A short-term fix is probably around making the connection callback an option type again, but it would be better to make this more explicit to avoid the same mistake in the future. i.e., instead of type t = int option type t = [ `Connection of int | `Connection_being_established ] the latter is obviously much clearer. > > Mainly, as you say, this points to a lack of good regression tests and test infrastructure. I have tried to make some unit tests but for TCP there are many balls that have to be kept in the air and I could not quite do it in an automated way. The most successful of this kind of test was one in which a single VM would bring up 2 virtual interfaces and send specific patterns of data in both directions. It knew what to expect and it could, if necessary, even examine the state machines of the two TCPs. This was quite fragile - it would often stumble on something simple like bringing up two VIFs. The other option here is not to use Xen for testing the net stack at all, but just use Linux with two tap interfaces. That gives us the ability to use tcpdump to inspect the traces as well... > On 2 Jun 2014, at 17:00, Mindy wrote: > My first thought is that I don't know how to get the workflow I've been using (start up a unikernel in Xen and throw a bunch of stuff at it from scapy) set up in Travis, but if that doesn't seem like obviously the wrong thing to do, I can look into it. I would still like to look at Quickcheck as well. Similar to answer to Balraj above -- instead of spinning up a Xen VM, spin up a user-level stack on Linux instead (using `NET=direct mirage configure --unix` in the various skeleton examples). However, one downside to Travis is that it uses LXC (containers) for its isolation, and so doesn't support tuntap. This does leave Balraj's suggestion as the best one: create two network stacks in one Mirage program and get them talking to each other! > > Also, an update - Last week I wrote up another Treaty of Westphalia on finding a TCP bug and made Mirage implementations of chargen, discard, and echo for use in testing the TCP stack more directly. Today, I'm planning on getting a whole bunch of data from them and (I hope) finding some interesting results. The chargen/discard/echo sounds very useful indeed -- how about adding those directly into mirage/mirage-tcpip in a lib_test/ (or examples/) directory? -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 Jun 11 10:29:50 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 11 Jun 2014 10:29: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 1Wufmq-0002St-IZ; Wed, 11 Jun 2014 10:29:44 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Wufmp-0002Se-65 for mirageos-devel@lists.xenproject.org; Wed, 11 Jun 2014 10:29:43 +0000 Received: from [85.158.143.35:61021] by server-2.bemta-4.messagelabs.com id 55/21-06539-69F28935; Wed, 11 Jun 2014 10:29:42 +0000 X-Env-Sender: kosmo.zb@gmail.com X-Msg-Ref: server-16.tower-21.messagelabs.com!1402482581!7213341!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.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17942 invoked from network); 11 Jun 2014 10:29:41 -0000 Received: from mail-la0-f54.google.com (HELO mail-la0-f54.google.com) (209.85.215.54) by server-16.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 11 Jun 2014 10:29:41 -0000 Received: by mail-la0-f54.google.com with SMTP id pv20so4667263lab.41 for ; Wed, 11 Jun 2014 03:29:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type:content-transfer-encoding; bh=PNPqHnlyHDrF+8s6zdePiUPmjpT4JvupMCwzofju6/Y=; b=sG6uG13SRiKUCUJKVavh2Wa3sVSWqhG+iZrr6weukFLabFAkaf3MNO8DHDwjXz1mr1 po+gcMnkep7u29vXqY0kTTBaMed2g64iWdq+hjyBQhbVFrRLPXdggHLkhRi2s49h8HCb fgNaw9390DWBbMYwZnXFUeedSv2CpE6TSb1jYb+XpN1nhff0kbRXA4OQxNjgNZHe5UwZ cYS4/a/IJ/PQcz17q/tOX9bnT5FNJ7NtWsg56ZX4f58mL3pl8IHeXdJfne/aikbvB+W1 Wg6OA9n7K1PwfwNHNmWLTjci175anWI2NXSdhfiVaK/Wc9Hs6CWUwIaqaNzD/NURChWi eHIA== MIME-Version: 1.0 X-Received: by 10.153.5.37 with SMTP id cj5mr1558283lad.48.1402482580935; Wed, 11 Jun 2014 03:29:40 -0700 (PDT) Received: by 10.112.133.226 with HTTP; Wed, 11 Jun 2014 03:29:40 -0700 (PDT) In-Reply-To: References: <537A1EAD.5090906@somerandomidiot.com> <538C9FB9.7070001@somerandomidiot.com> <912BC56B-F927-4CDE-9C1E-D40BBD8A79CE@recoil.org> Date: Wed, 11 Jun 2014 11:29:40 +0100 X-Google-Sender-Auth: el2rzUpRqtuWrmFCbxlLtk7iHws Message-ID: From: David Sheets To: Anil Madhavapeddy Cc: Balraj Singh , "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] OPW intern checking in! X-BeenThere: mirageos-devel@lists.xenproject.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 Tue, Jun 10, 2014 at 11:23 PM, Anil Madhavapeddy wrote: > On 10 Jun 2014, at 12:29, Balraj Singh wrote: > >> Hi Anil, >> >> Just to confirm what I was showing you yesterday. >> >> This, along with possibly a few other defects, crept in as part of the changes that were made on Jan 23, "Simplify the listener mechanism to push it into the TCP input handler". The changes were all good improvements, and necessary, but this bug sneaked in. > > Thanks for tracking these down. I believe this only affects the server side (which confirms Mindy's findings), and were due to lifting out some datastructures in the listening code, and making them available to the application directly. > > A short-term fix is probably around making the connection callback an option type again, but it would be better to make this more explicit to avoid the same mistake in the future. i.e., instead of > > type t = int option > type t = [ `Connection of int | `Connection_being_established ] > > the latter is obviously much clearer. > >> >> Mainly, as you say, this points to a lack of good regression tests and test infrastructure. I have tried to make some unit tests but for TCP there are many balls that have to be kept in the air and I could not quite do it in an automated way. The most successful of this kind of test was one in which a single VM would bring up 2 virtual interfaces and send specific patterns of data in both directions. It knew what to expect and it could, if necessary, even examine the state machines of the two TCPs. This was quite fragile - it would often stumble on something simple like bringing up two VIFs. > > The other option here is not to use Xen for testing the net stack at all, but just use Linux with two tap interfaces. That gives us the ability to use tcpdump to inspect the traces as well... > >> On 2 Jun 2014, at 17:00, Mindy wrote: >> My first thought is that I don't know how to get the workflow I've been using (start up a unikernel in Xen and throw a bunch of stuff at it from scapy) set up in Travis, but if that doesn't seem like obviously the wrong thing to do, I can look into it. I would still like to look at Quickcheck as well. > > Similar to answer to Balraj above -- instead of spinning up a Xen VM, spin up a user-level stack on Linux instead (using `NET=direct mirage configure --unix` in the various skeleton examples). > > However, one downside to Travis is that it uses LXC (containers) for its isolation, and so doesn't support tuntap. Last I saw, Travis uses OpenVZ which was an LXC/namespaces/cgroups precursor provided by a (very) large kernel patch. Privileged LXC containers (started by a privileged user) do support tuntap if the executor allows the dev node to be created with something like: lxc.cgroup.devices.allow = c 10:200 rwm See also . I'm not sure if this satisfies your use case but, on its face, it looks possible. ds > This does leave Balraj's suggestion as the best one: create two network stacks in one Mirage program and get them talking to each other! > >> >> Also, an update - Last week I wrote up another Treaty of Westphalia on finding a TCP bug and made Mirage implementations of chargen, discard, and echo for use in testing the TCP stack more directly. Today, I'm planning on getting a whole bunch of data from them and (I hope) finding some interesting results. > > The chargen/discard/echo sounds very useful indeed -- how about adding those directly into mirage/mirage-tcpip in a lib_test/ (or examples/) directory? > > -anil > > > _______________________________________________ > 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 Wed Jun 11 10:29:50 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 11 Jun 2014 10:29: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 1Wufmq-0002St-IZ; Wed, 11 Jun 2014 10:29:44 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Wufmp-0002Se-65 for mirageos-devel@lists.xenproject.org; Wed, 11 Jun 2014 10:29:43 +0000 Received: from [85.158.143.35:61021] by server-2.bemta-4.messagelabs.com id 55/21-06539-69F28935; Wed, 11 Jun 2014 10:29:42 +0000 X-Env-Sender: kosmo.zb@gmail.com X-Msg-Ref: server-16.tower-21.messagelabs.com!1402482581!7213341!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.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17942 invoked from network); 11 Jun 2014 10:29:41 -0000 Received: from mail-la0-f54.google.com (HELO mail-la0-f54.google.com) (209.85.215.54) by server-16.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 11 Jun 2014 10:29:41 -0000 Received: by mail-la0-f54.google.com with SMTP id pv20so4667263lab.41 for ; Wed, 11 Jun 2014 03:29:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type:content-transfer-encoding; bh=PNPqHnlyHDrF+8s6zdePiUPmjpT4JvupMCwzofju6/Y=; b=sG6uG13SRiKUCUJKVavh2Wa3sVSWqhG+iZrr6weukFLabFAkaf3MNO8DHDwjXz1mr1 po+gcMnkep7u29vXqY0kTTBaMed2g64iWdq+hjyBQhbVFrRLPXdggHLkhRi2s49h8HCb fgNaw9390DWBbMYwZnXFUeedSv2CpE6TSb1jYb+XpN1nhff0kbRXA4OQxNjgNZHe5UwZ cYS4/a/IJ/PQcz17q/tOX9bnT5FNJ7NtWsg56ZX4f58mL3pl8IHeXdJfne/aikbvB+W1 Wg6OA9n7K1PwfwNHNmWLTjci175anWI2NXSdhfiVaK/Wc9Hs6CWUwIaqaNzD/NURChWi eHIA== MIME-Version: 1.0 X-Received: by 10.153.5.37 with SMTP id cj5mr1558283lad.48.1402482580935; Wed, 11 Jun 2014 03:29:40 -0700 (PDT) Received: by 10.112.133.226 with HTTP; Wed, 11 Jun 2014 03:29:40 -0700 (PDT) In-Reply-To: References: <537A1EAD.5090906@somerandomidiot.com> <538C9FB9.7070001@somerandomidiot.com> <912BC56B-F927-4CDE-9C1E-D40BBD8A79CE@recoil.org> Date: Wed, 11 Jun 2014 11:29:40 +0100 X-Google-Sender-Auth: el2rzUpRqtuWrmFCbxlLtk7iHws Message-ID: From: David Sheets To: Anil Madhavapeddy Cc: Balraj Singh , "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] OPW intern checking in! X-BeenThere: mirageos-devel@lists.xenproject.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 Tue, Jun 10, 2014 at 11:23 PM, Anil Madhavapeddy wrote: > On 10 Jun 2014, at 12:29, Balraj Singh wrote: > >> Hi Anil, >> >> Just to confirm what I was showing you yesterday. >> >> This, along with possibly a few other defects, crept in as part of the changes that were made on Jan 23, "Simplify the listener mechanism to push it into the TCP input handler". The changes were all good improvements, and necessary, but this bug sneaked in. > > Thanks for tracking these down. I believe this only affects the server side (which confirms Mindy's findings), and were due to lifting out some datastructures in the listening code, and making them available to the application directly. > > A short-term fix is probably around making the connection callback an option type again, but it would be better to make this more explicit to avoid the same mistake in the future. i.e., instead of > > type t = int option > type t = [ `Connection of int | `Connection_being_established ] > > the latter is obviously much clearer. > >> >> Mainly, as you say, this points to a lack of good regression tests and test infrastructure. I have tried to make some unit tests but for TCP there are many balls that have to be kept in the air and I could not quite do it in an automated way. The most successful of this kind of test was one in which a single VM would bring up 2 virtual interfaces and send specific patterns of data in both directions. It knew what to expect and it could, if necessary, even examine the state machines of the two TCPs. This was quite fragile - it would often stumble on something simple like bringing up two VIFs. > > The other option here is not to use Xen for testing the net stack at all, but just use Linux with two tap interfaces. That gives us the ability to use tcpdump to inspect the traces as well... > >> On 2 Jun 2014, at 17:00, Mindy wrote: >> My first thought is that I don't know how to get the workflow I've been using (start up a unikernel in Xen and throw a bunch of stuff at it from scapy) set up in Travis, but if that doesn't seem like obviously the wrong thing to do, I can look into it. I would still like to look at Quickcheck as well. > > Similar to answer to Balraj above -- instead of spinning up a Xen VM, spin up a user-level stack on Linux instead (using `NET=direct mirage configure --unix` in the various skeleton examples). > > However, one downside to Travis is that it uses LXC (containers) for its isolation, and so doesn't support tuntap. Last I saw, Travis uses OpenVZ which was an LXC/namespaces/cgroups precursor provided by a (very) large kernel patch. Privileged LXC containers (started by a privileged user) do support tuntap if the executor allows the dev node to be created with something like: lxc.cgroup.devices.allow = c 10:200 rwm See also . I'm not sure if this satisfies your use case but, on its face, it looks possible. ds > This does leave Balraj's suggestion as the best one: create two network stacks in one Mirage program and get them talking to each other! > >> >> Also, an update - Last week I wrote up another Treaty of Westphalia on finding a TCP bug and made Mirage implementations of chargen, discard, and echo for use in testing the TCP stack more directly. Today, I'm planning on getting a whole bunch of data from them and (I hope) finding some interesting results. > > The chargen/discard/echo sounds very useful indeed -- how about adding those directly into mirage/mirage-tcpip in a lib_test/ (or examples/) directory? > > -anil > > > _______________________________________________ > 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 Wed Jun 11 15:59:04 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 11 Jun 2014 15:59: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 1WukvT-0005ou-QO; Wed, 11 Jun 2014 15:58:59 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WukvS-0005og-Lw for mirageos-devel@lists.xenproject.org; Wed, 11 Jun 2014 15:58:58 +0000 Received: from [85.158.143.35:31022] by server-1.bemta-4.messagelabs.com id A3/6E-09853-2CC78935; Wed, 11 Jun 2014 15:58:58 +0000 X-Env-Sender: mindy@somerandomidiot.com X-Msg-Ref: server-5.tower-21.messagelabs.com!1402502337!10727469!1 X-Originating-IP: [217.70.183.196] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMjE3LjcwLjE4My4xOTYgPT4gMzk1MTY=\n X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12956 invoked from network); 11 Jun 2014 15:58:57 -0000 Received: from relay4-d.mail.gandi.net (HELO relay4-d.mail.gandi.net) (217.70.183.196) by server-5.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 11 Jun 2014 15:58:57 -0000 Received: from mfilter19-d.gandi.net (mfilter19-d.gandi.net [217.70.178.147]) by relay4-d.mail.gandi.net (Postfix) with ESMTP id 11263172090; Wed, 11 Jun 2014 17:58:57 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at mfilter19-d.gandi.net Received: from relay4-d.mail.gandi.net ([217.70.183.196]) by mfilter19-d.gandi.net (mfilter19-d.gandi.net [10.0.15.180]) (amavisd-new, port 10024) with ESMTP id d1hsSptks-fe; Wed, 11 Jun 2014 17:58:55 +0200 (CEST) X-Originating-IP: 184.60.25.234 Received: from [192.168.56.15] (h184-60-25-234.mdsnwi.dsl.dynamic.tds.net [184.60.25.234]) (Authenticated sender: guybrush@somerandomidiot.com) by relay4-d.mail.gandi.net (Postfix) with ESMTPSA id C999B172080; Wed, 11 Jun 2014 17:58:53 +0200 (CEST) Message-ID: <53987CB5.7020105@somerandomidiot.com> Date: Wed, 11 Jun 2014 10:58:45 -0500 From: Mindy User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: Anil Madhavapeddy , Balraj Singh References: <537A1EAD.5090906@somerandomidiot.com> <538C9FB9.7070001@somerandomidiot.com> <912BC56B-F927-4CDE-9C1E-D40BBD8A79CE@recoil.org> In-Reply-To: Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] OPW intern checking in! X-BeenThere: mirageos-devel@lists.xenproject.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 Doubling as my update for this morning, here are some inline responses: >> Mainly, as you say, this points to a lack of good regression tests and test infrastructure. I have tried to make some unit tests but for TCP there are many balls that have to be kept in the air and I could not quite do it in an automated way. The most successful of this kind of test was one in which a single VM would bring up 2 virtual interfaces and send specific patterns of data in both directions. It knew what to expect and it could, if necessary, even examine the state machines of the two TCPs. This was quite fragile - it would often stumble on something simple like bringing up two VIFs. > The other option here is not to use Xen for testing the net stack at all, but just use Linux with two tap interfaces. That gives us the ability to use tcpdump to inspect the traces as well... > >> On 2 Jun 2014, at 17:00, Mindy wrote: >> My first thought is that I don't know how to get the workflow I've been using (start up a unikernel in Xen and throw a bunch of stuff at it from scapy) set up in Travis, but if that doesn't seem like obviously the wrong thing to do, I can look into it. I would still like to look at Quickcheck as well. > Similar to answer to Balraj above -- instead of spinning up a Xen VM, spin up a user-level stack on Linux instead (using `NET=direct mirage configure --unix` in the various skeleton examples). > > However, one downside to Travis is that it uses LXC (containers) for its isolation, and so doesn't support tuntap. > > This does leave Balraj's suggestion as the best one: create two network stacks in one Mirage program and get them talking to each other! Playing around with this uncovered a logic problem in how DHCP setup works in the context of unikernels that don't want to run listeners; I've submitted an issue (mirage/mirage-tcpip #53) with more details. >> Also, an update - Last week I wrote up another Treaty of Westphalia on finding a TCP bug and made Mirage implementations of chargen, discard, and echo for use in testing the TCP stack more directly. Today, I'm planning on getting a whole bunch of data from them and (I hope) finding some interesting results. > The chargen/discard/echo sounds very useful indeed -- how about adding those directly into mirage/mirage-tcpip in a lib_test/ (or examples/) directory? I've just submitted a PR (#52) for this. Thanks, Mindy _______________________________________________ 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 Jun 11 15:59:04 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 11 Jun 2014 15:59: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 1WukvT-0005ou-QO; Wed, 11 Jun 2014 15:58:59 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WukvS-0005og-Lw for mirageos-devel@lists.xenproject.org; Wed, 11 Jun 2014 15:58:58 +0000 Received: from [85.158.143.35:31022] by server-1.bemta-4.messagelabs.com id A3/6E-09853-2CC78935; Wed, 11 Jun 2014 15:58:58 +0000 X-Env-Sender: mindy@somerandomidiot.com X-Msg-Ref: server-5.tower-21.messagelabs.com!1402502337!10727469!1 X-Originating-IP: [217.70.183.196] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMjE3LjcwLjE4My4xOTYgPT4gMzk1MTY=\n X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12956 invoked from network); 11 Jun 2014 15:58:57 -0000 Received: from relay4-d.mail.gandi.net (HELO relay4-d.mail.gandi.net) (217.70.183.196) by server-5.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 11 Jun 2014 15:58:57 -0000 Received: from mfilter19-d.gandi.net (mfilter19-d.gandi.net [217.70.178.147]) by relay4-d.mail.gandi.net (Postfix) with ESMTP id 11263172090; Wed, 11 Jun 2014 17:58:57 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at mfilter19-d.gandi.net Received: from relay4-d.mail.gandi.net ([217.70.183.196]) by mfilter19-d.gandi.net (mfilter19-d.gandi.net [10.0.15.180]) (amavisd-new, port 10024) with ESMTP id d1hsSptks-fe; Wed, 11 Jun 2014 17:58:55 +0200 (CEST) X-Originating-IP: 184.60.25.234 Received: from [192.168.56.15] (h184-60-25-234.mdsnwi.dsl.dynamic.tds.net [184.60.25.234]) (Authenticated sender: guybrush@somerandomidiot.com) by relay4-d.mail.gandi.net (Postfix) with ESMTPSA id C999B172080; Wed, 11 Jun 2014 17:58:53 +0200 (CEST) Message-ID: <53987CB5.7020105@somerandomidiot.com> Date: Wed, 11 Jun 2014 10:58:45 -0500 From: Mindy User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: Anil Madhavapeddy , Balraj Singh References: <537A1EAD.5090906@somerandomidiot.com> <538C9FB9.7070001@somerandomidiot.com> <912BC56B-F927-4CDE-9C1E-D40BBD8A79CE@recoil.org> In-Reply-To: Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] OPW intern checking in! X-BeenThere: mirageos-devel@lists.xenproject.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 Doubling as my update for this morning, here are some inline responses: >> Mainly, as you say, this points to a lack of good regression tests and test infrastructure. I have tried to make some unit tests but for TCP there are many balls that have to be kept in the air and I could not quite do it in an automated way. The most successful of this kind of test was one in which a single VM would bring up 2 virtual interfaces and send specific patterns of data in both directions. It knew what to expect and it could, if necessary, even examine the state machines of the two TCPs. This was quite fragile - it would often stumble on something simple like bringing up two VIFs. > The other option here is not to use Xen for testing the net stack at all, but just use Linux with two tap interfaces. That gives us the ability to use tcpdump to inspect the traces as well... > >> On 2 Jun 2014, at 17:00, Mindy wrote: >> My first thought is that I don't know how to get the workflow I've been using (start up a unikernel in Xen and throw a bunch of stuff at it from scapy) set up in Travis, but if that doesn't seem like obviously the wrong thing to do, I can look into it. I would still like to look at Quickcheck as well. > Similar to answer to Balraj above -- instead of spinning up a Xen VM, spin up a user-level stack on Linux instead (using `NET=direct mirage configure --unix` in the various skeleton examples). > > However, one downside to Travis is that it uses LXC (containers) for its isolation, and so doesn't support tuntap. > > This does leave Balraj's suggestion as the best one: create two network stacks in one Mirage program and get them talking to each other! Playing around with this uncovered a logic problem in how DHCP setup works in the context of unikernels that don't want to run listeners; I've submitted an issue (mirage/mirage-tcpip #53) with more details. >> Also, an update - Last week I wrote up another Treaty of Westphalia on finding a TCP bug and made Mirage implementations of chargen, discard, and echo for use in testing the TCP stack more directly. Today, I'm planning on getting a whole bunch of data from them and (I hope) finding some interesting results. > The chargen/discard/echo sounds very useful indeed -- how about adding those directly into mirage/mirage-tcpip in a lib_test/ (or examples/) directory? I've just submitted a PR (#52) for this. Thanks, Mindy _______________________________________________ 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 Jun 11 16:11:20 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 11 Jun 2014 16:11: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 1Wul7O-0006WR-TO; Wed, 11 Jun 2014 16:11:18 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Wul7O-0006WM-4a for mirageos-devel@lists.xenproject.org; Wed, 11 Jun 2014 16:11:18 +0000 Received: from [85.158.143.35:6509] by server-1.bemta-4.messagelabs.com id 10/4F-09853-5AF78935; Wed, 11 Jun 2014 16:11:17 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-7.tower-21.messagelabs.com!1402503076!10754369!1 X-Originating-IP: [209.85.212.179] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 24279 invoked from network); 11 Jun 2014 16:11:17 -0000 Received: from mail-wi0-f179.google.com (HELO mail-wi0-f179.google.com) (209.85.212.179) by server-7.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 11 Jun 2014 16:11:17 -0000 Received: by mail-wi0-f179.google.com with SMTP id cc10so1451556wib.0 for ; Wed, 11 Jun 2014 09:11:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:reply-to:user-agent:mime-version:to :subject:content-type:content-transfer-encoding; bh=zSbYUwWKNu60kKnptnQ07IiXGPqS8Y+DHFZLgzCI23k=; b=uo0OOnvaaeK4+BfZOB5R+XNTw8M5Of9OJbK3wvsOY2PpaolofB9f3UKuKAi/puFrt0 BO+jbsP9rdMDNh1O/nBLtEttxoy3F3IKP5CtG8+y62XUVjLLUMcf1xyevewBU6otNT88 lG1A7S3XFi4N/qHtFkvhbvroU9+AiklbJT+emx9uwOf/1gPwGuFU+WtC+g+C5Ro1IlAf Tz7Njd2jbB6kwFhzSt5Xs9z0FTSCHBaRqqk4+lfUfbVBEqrWPTZOnJLQMEO6fVj7xvzQ HmQEFuxHYU6CwJKwaSKzrREEi5ThXDUfBTek1lDA8JuJtZU2rOK8nwHk+SqDZjsHSHTM wwfg== X-Received: by 10.181.13.106 with SMTP id ex10mr15820588wid.30.1402503076597; Wed, 11 Jun 2014 09:11:16 -0700 (PDT) Received: from [172.16.25.10] (97e5a5cd.skybroadband.com. [151.229.165.205]) by mx.google.com with ESMTPSA id kr6sm34910565wjb.16.2014.06.11.09.11.15 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 11 Jun 2014 09:11:15 -0700 (PDT) Message-ID: <53987F9F.6010907@xen.org> Date: Wed, 11 Jun 2014 17:11:11 +0100 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: "mirageos-devel@lists.xenproject.org" Subject: [MirageOS-devel] Mirage OS 2.0 (or next) for Xen Project Dev Summit? X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: lars.kurth@xen.org 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 all, I saw that Anil submitted a Mirage OS 2.0 talk for the Developer Summit. I was wondering what the plans for the next release were. If it is around Dev Summit time, you should probably start coordinating with me and Sarah 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 Jun 11 16:11:20 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 11 Jun 2014 16:11: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 1Wul7O-0006WR-TO; Wed, 11 Jun 2014 16:11:18 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Wul7O-0006WM-4a for mirageos-devel@lists.xenproject.org; Wed, 11 Jun 2014 16:11:18 +0000 Received: from [85.158.143.35:6509] by server-1.bemta-4.messagelabs.com id 10/4F-09853-5AF78935; Wed, 11 Jun 2014 16:11:17 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-7.tower-21.messagelabs.com!1402503076!10754369!1 X-Originating-IP: [209.85.212.179] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 24279 invoked from network); 11 Jun 2014 16:11:17 -0000 Received: from mail-wi0-f179.google.com (HELO mail-wi0-f179.google.com) (209.85.212.179) by server-7.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 11 Jun 2014 16:11:17 -0000 Received: by mail-wi0-f179.google.com with SMTP id cc10so1451556wib.0 for ; Wed, 11 Jun 2014 09:11:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:reply-to:user-agent:mime-version:to :subject:content-type:content-transfer-encoding; bh=zSbYUwWKNu60kKnptnQ07IiXGPqS8Y+DHFZLgzCI23k=; b=uo0OOnvaaeK4+BfZOB5R+XNTw8M5Of9OJbK3wvsOY2PpaolofB9f3UKuKAi/puFrt0 BO+jbsP9rdMDNh1O/nBLtEttxoy3F3IKP5CtG8+y62XUVjLLUMcf1xyevewBU6otNT88 lG1A7S3XFi4N/qHtFkvhbvroU9+AiklbJT+emx9uwOf/1gPwGuFU+WtC+g+C5Ro1IlAf Tz7Njd2jbB6kwFhzSt5Xs9z0FTSCHBaRqqk4+lfUfbVBEqrWPTZOnJLQMEO6fVj7xvzQ HmQEFuxHYU6CwJKwaSKzrREEi5ThXDUfBTek1lDA8JuJtZU2rOK8nwHk+SqDZjsHSHTM wwfg== X-Received: by 10.181.13.106 with SMTP id ex10mr15820588wid.30.1402503076597; Wed, 11 Jun 2014 09:11:16 -0700 (PDT) Received: from [172.16.25.10] (97e5a5cd.skybroadband.com. [151.229.165.205]) by mx.google.com with ESMTPSA id kr6sm34910565wjb.16.2014.06.11.09.11.15 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 11 Jun 2014 09:11:15 -0700 (PDT) Message-ID: <53987F9F.6010907@xen.org> Date: Wed, 11 Jun 2014 17:11:11 +0100 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: "mirageos-devel@lists.xenproject.org" Subject: [MirageOS-devel] Mirage OS 2.0 (or next) for Xen Project Dev Summit? X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: lars.kurth@xen.org 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 all, I saw that Anil submitted a Mirage OS 2.0 talk for the Developer Summit. I was wondering what the plans for the next release were. If it is around Dev Summit time, you should probably start coordinating with me and Sarah 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 Jun 11 16:26:17 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 11 Jun 2014 16:26: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 1WulLs-0007BE-RL; Wed, 11 Jun 2014 16:26:16 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WulLr-0007B2-T1 for mirageos-devel@lists.xenproject.org; Wed, 11 Jun 2014 16:26:15 +0000 Received: from [85.158.143.35:4213] by server-1.bemta-4.messagelabs.com id CB/F0-09853-72388935; Wed, 11 Jun 2014 16:26:15 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-8.tower-21.messagelabs.com!1402503973!10741766!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15294 invoked from network); 11 Jun 2014 16:26:13 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-8.tower-21.messagelabs.com with SMTP; 11 Jun 2014 16:26:13 -0000 Received: (qmail 11301 invoked by uid 634); 11 Jun 2014 16:26:12 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from volstagg-0.srg.cl.cam.ac.uk (HELO flick.office) (128.232.32.232) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Wed, 11 Jun 2014 17:26:12 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\)) From: Anil Madhavapeddy In-Reply-To: <53987F9F.6010907@xen.org> Date: Wed, 11 Jun 2014 17:26:10 +0100 Message-Id: <7CC65A9C-45F9-4E6C-A6D3-FD83A6C472C7@recoil.org> References: <53987F9F.6010907@xen.org> To: lars.kurth@xen.org X-Mailer: Apple Mail (2.1874) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Mirage OS 2.0 (or next) for Xen Project Dev Summit? X-BeenThere: mirageos-devel@lists.xenproject.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 11 Jun 2014, at 17:11, Lars Kurth wrote: > Hi all, > I saw that Anil submitted a Mirage OS 2.0 talk for the Developer Summit. I was wondering what the plans for the next release were. If it is around Dev Summit time, you should probably start coordinating with me and Sarah We were just chatting about this yesterday in the call! http://openmirage.org/wiki/weekly-2014-06-10 The emerging plan for the OSCON Mirage 2.0 release is to have three key features: - the Xen/ARM port (lead: Thomas Leonard) - Irmin storage integration (lead: Thomas Gazagnaire, Xenstore lead: Dave Scott) - Name resolver for distributed computation (lead: Anil Madhavapeddy) All of these look in reasonable shape to get released by mid-July, although the release announcement could probably use a week or two to let the features sit in-tree before we tell everyone about it. Anyone have anything else on the stack? There are minor things such as 'add s-expression tracing' that can be done on an ongoing basis. 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 Wed Jun 11 16:26:17 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 11 Jun 2014 16:26: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 1WulLs-0007BE-RL; Wed, 11 Jun 2014 16:26:16 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WulLr-0007B2-T1 for mirageos-devel@lists.xenproject.org; Wed, 11 Jun 2014 16:26:15 +0000 Received: from [85.158.143.35:4213] by server-1.bemta-4.messagelabs.com id CB/F0-09853-72388935; Wed, 11 Jun 2014 16:26:15 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-8.tower-21.messagelabs.com!1402503973!10741766!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15294 invoked from network); 11 Jun 2014 16:26:13 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-8.tower-21.messagelabs.com with SMTP; 11 Jun 2014 16:26:13 -0000 Received: (qmail 11301 invoked by uid 634); 11 Jun 2014 16:26:12 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from volstagg-0.srg.cl.cam.ac.uk (HELO flick.office) (128.232.32.232) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Wed, 11 Jun 2014 17:26:12 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\)) From: Anil Madhavapeddy In-Reply-To: <53987F9F.6010907@xen.org> Date: Wed, 11 Jun 2014 17:26:10 +0100 Message-Id: <7CC65A9C-45F9-4E6C-A6D3-FD83A6C472C7@recoil.org> References: <53987F9F.6010907@xen.org> To: lars.kurth@xen.org X-Mailer: Apple Mail (2.1874) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Mirage OS 2.0 (or next) for Xen Project Dev Summit? X-BeenThere: mirageos-devel@lists.xenproject.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 11 Jun 2014, at 17:11, Lars Kurth wrote: > Hi all, > I saw that Anil submitted a Mirage OS 2.0 talk for the Developer Summit. I was wondering what the plans for the next release were. If it is around Dev Summit time, you should probably start coordinating with me and Sarah We were just chatting about this yesterday in the call! http://openmirage.org/wiki/weekly-2014-06-10 The emerging plan for the OSCON Mirage 2.0 release is to have three key features: - the Xen/ARM port (lead: Thomas Leonard) - Irmin storage integration (lead: Thomas Gazagnaire, Xenstore lead: Dave Scott) - Name resolver for distributed computation (lead: Anil Madhavapeddy) All of these look in reasonable shape to get released by mid-July, although the release announcement could probably use a week or two to let the features sit in-tree before we tell everyone about it. Anyone have anything else on the stack? There are minor things such as 'add s-expression tracing' that can be done on an ongoing basis. 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 Wed Jun 11 16:27:31 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 11 Jun 2014 16:27: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 1WulN5-0007KQ-Dy; Wed, 11 Jun 2014 16:27:31 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WulN3-0007KA-Gw for mirageos-devel@lists.xenproject.org; Wed, 11 Jun 2014 16:27:29 +0000 Received: from [85.158.137.68:17170] by server-5.bemta-3.messagelabs.com id 5B/D5-18761-07388935; Wed, 11 Jun 2014 16:27:28 +0000 X-Env-Sender: talex5@gmail.com X-Msg-Ref: server-4.tower-31.messagelabs.com!1402504046!9422457!1 X-Originating-IP: [209.85.219.46] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, ML_RADAR_SPEW_LINKS_23,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 18982 invoked from network); 11 Jun 2014 16:27:27 -0000 Received: from mail-oa0-f46.google.com (HELO mail-oa0-f46.google.com) (209.85.219.46) by server-4.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 11 Jun 2014 16:27:27 -0000 Received: by mail-oa0-f46.google.com with SMTP id m1so1805158oag.19 for ; Wed, 11 Jun 2014 09:27:26 -0700 (PDT) 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=DJup5VRWgbWZA2AHzZ789ZwbVV/tr+mLNkTI8tDJrGA=; b=QW4ZTlExTFMWhp/uACIuRhbDgRp0ILv3Waql16y4WJH1XLP1714KHjEefcCRmcDyc8 wqNyeEQFqXAa6xTyl4uaQmNBbqo0bdK9KMrH2gAS092jhHJYtPW/JsPP5cw1br/6pQNn usbiy5d2mO93SBkzBZDSrOSfXu9kCWhX5FHPBt7PAwCBT1oO9o/hr8G21+ASI+d4H4Ak OMhkkIWZ21I3wXND8ptiTFqhwIkC2Fq325qiTtOR1w5pA2Yg0n2nb+6cJtxoURT0wPj5 2xsCiZYejQjPZnPG9IOyh8aVyQdXTakP2NIIHoyJ7hDDIxjpwdejMhwyASp78AuZyjg/ 7PZA== MIME-Version: 1.0 X-Received: by 10.182.251.170 with SMTP id zl10mr38520575obc.5.1402504046011; Wed, 11 Jun 2014 09:27:26 -0700 (PDT) Received: by 10.76.92.5 with HTTP; Wed, 11 Jun 2014 09:27:25 -0700 (PDT) In-Reply-To: <297FC9DB-3A4E-41A5-B00E-9DEF62C625E6@recoil.org> References: <297FC9DB-3A4E-41A5-B00E-9DEF62C625E6@recoil.org> Date: Wed, 11 Jun 2014 17:27:25 +0100 Message-ID: From: Thomas Leonard To: Anil Madhavapeddy Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Mirage on Xen/ARM status X-BeenThere: mirageos-devel@lists.xenproject.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 June 2014 21:29, Anil Madhavapeddy wrote: > On 4 Jun 2014, at 13:33, Thomas Leonard wrote: > >> An update on the Mirage/ARM port: >> >> I have mirage-platform upgraded to the new Mini-OS (plus openlibm and >> no libc). Networking is working again on x86_64 (I can telnet to the >> mirage-skeleton/network service and send it a message), but not on ARM >> yet. > > Good to have x86_64 back! It's probably a good idea to CC me and Dave > on the patchbombs to xen-devel, as I only sample the list these days > due to mail volume. > >> This required some changes to Mini-OS to expose the grant table >> details and to stop Mini-OS's xenbus from stealing the event >> notifications. I need this clean this up. > > To be clear, this is networking using lwIP on ARM isnt it? For Mirage, > the MiniOS Xenbus should be disabled entirely since our own OCaml > Xenstore will handle everything. By default, minios's event handler calls do_event on each event, and loops until they're all handled, so I had to disable that code. >> OCaml's Random currently tries to open /dev/urandom, which fails. >> Looks like it falls back to using gettimeofday in that case. It logs a >> message to the console ("Attempt to open(/dev/urandom)!"), so >> hopefully we'll remember to fix it eventually. > > Is this initialised forcibly anywhere, or only when someone calls > a Random.self_init()? We need to deprecate this module in Mirage and > ensure that we have a randomfront/back model, or risk introducing > poor entropy. This hasn't mattered so far, but will be critical when > we activate the OCaml TLS library that Hannes and David are working on. The TCP/IP stack seems to want it. >> Networking doesn't work on ARM as the code wants to use start_info, >> which doesn't exist. I might try making a fake start_info page on ARM >> rather than modifying everything else. > > Yep, sounds like a good plan to ease x86/ARM transition. Here are some instructions for testing the current version of everything (hacks and all!): To test Mirage on Xen/ARM: These instructions are for building on a soft-float ARM machine (or VM), running on the board itself. If you prefer, you can cross-compile Mini-OS and openlibm and copy the files across (the cross compiler can be hard-float or soft-float; use DESTDIR=... to stage the files): make XEN_TARGET_ARCH=arm32 CROSS_COMPILE=arm-linux-gnueabihf- However, it doesn't save much time and you still need to build the OCaml code on the machine itself. 1. Install libminios.a git clone -b arm-preview https://github.com/talex5/xen.git mini-os cd mini-os ./configure cd extras/mini-os make CONFIG_TEST=n CONFIG_XENBUS=n CONFIG_START_NETWORK=n CONFIG_BLKFRONT=n CONFIG_NETFRONT=n CONFIG_FBFRONT=n CONFIG_KBDFRONT=n CONFIG_CONSFRONT=n CONFIG_XC=n -j4 install 3. Get openlibm and install git clone https://github.com/JuliaLang/openlibm.git cd openlibm make install 4. Pin mirage-platform git clone -b arm-preview https://github.com/talex5/mirage-platform.git opam pin mirage-xen ./mirage-platform 5. Pin mirage-console git clone -b arm-preview https://github.com/talex5/mirage-console.git opam pin mirage-console-xen ./mirage-console 6. Pin mirage git clone -b arm-preview https://github.com/talex5/mirage.git opam pin mirage mirage 7. Build mirage-skeleton/console git clone git://github.com/mirage/mirage-skeleton.git cd mirage-skeleton/console opam install mirage mirage configure --xen make The next step is to get networking working on ARM. -- 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 Jun 11 16:27:31 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 11 Jun 2014 16:27: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 1WulN5-0007KQ-Dy; Wed, 11 Jun 2014 16:27:31 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WulN3-0007KA-Gw for mirageos-devel@lists.xenproject.org; Wed, 11 Jun 2014 16:27:29 +0000 Received: from [85.158.137.68:17170] by server-5.bemta-3.messagelabs.com id 5B/D5-18761-07388935; Wed, 11 Jun 2014 16:27:28 +0000 X-Env-Sender: talex5@gmail.com X-Msg-Ref: server-4.tower-31.messagelabs.com!1402504046!9422457!1 X-Originating-IP: [209.85.219.46] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, ML_RADAR_SPEW_LINKS_23,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 18982 invoked from network); 11 Jun 2014 16:27:27 -0000 Received: from mail-oa0-f46.google.com (HELO mail-oa0-f46.google.com) (209.85.219.46) by server-4.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 11 Jun 2014 16:27:27 -0000 Received: by mail-oa0-f46.google.com with SMTP id m1so1805158oag.19 for ; Wed, 11 Jun 2014 09:27:26 -0700 (PDT) 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=DJup5VRWgbWZA2AHzZ789ZwbVV/tr+mLNkTI8tDJrGA=; b=QW4ZTlExTFMWhp/uACIuRhbDgRp0ILv3Waql16y4WJH1XLP1714KHjEefcCRmcDyc8 wqNyeEQFqXAa6xTyl4uaQmNBbqo0bdK9KMrH2gAS092jhHJYtPW/JsPP5cw1br/6pQNn usbiy5d2mO93SBkzBZDSrOSfXu9kCWhX5FHPBt7PAwCBT1oO9o/hr8G21+ASI+d4H4Ak OMhkkIWZ21I3wXND8ptiTFqhwIkC2Fq325qiTtOR1w5pA2Yg0n2nb+6cJtxoURT0wPj5 2xsCiZYejQjPZnPG9IOyh8aVyQdXTakP2NIIHoyJ7hDDIxjpwdejMhwyASp78AuZyjg/ 7PZA== MIME-Version: 1.0 X-Received: by 10.182.251.170 with SMTP id zl10mr38520575obc.5.1402504046011; Wed, 11 Jun 2014 09:27:26 -0700 (PDT) Received: by 10.76.92.5 with HTTP; Wed, 11 Jun 2014 09:27:25 -0700 (PDT) In-Reply-To: <297FC9DB-3A4E-41A5-B00E-9DEF62C625E6@recoil.org> References: <297FC9DB-3A4E-41A5-B00E-9DEF62C625E6@recoil.org> Date: Wed, 11 Jun 2014 17:27:25 +0100 Message-ID: From: Thomas Leonard To: Anil Madhavapeddy Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Mirage on Xen/ARM status X-BeenThere: mirageos-devel@lists.xenproject.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 June 2014 21:29, Anil Madhavapeddy wrote: > On 4 Jun 2014, at 13:33, Thomas Leonard wrote: > >> An update on the Mirage/ARM port: >> >> I have mirage-platform upgraded to the new Mini-OS (plus openlibm and >> no libc). Networking is working again on x86_64 (I can telnet to the >> mirage-skeleton/network service and send it a message), but not on ARM >> yet. > > Good to have x86_64 back! It's probably a good idea to CC me and Dave > on the patchbombs to xen-devel, as I only sample the list these days > due to mail volume. > >> This required some changes to Mini-OS to expose the grant table >> details and to stop Mini-OS's xenbus from stealing the event >> notifications. I need this clean this up. > > To be clear, this is networking using lwIP on ARM isnt it? For Mirage, > the MiniOS Xenbus should be disabled entirely since our own OCaml > Xenstore will handle everything. By default, minios's event handler calls do_event on each event, and loops until they're all handled, so I had to disable that code. >> OCaml's Random currently tries to open /dev/urandom, which fails. >> Looks like it falls back to using gettimeofday in that case. It logs a >> message to the console ("Attempt to open(/dev/urandom)!"), so >> hopefully we'll remember to fix it eventually. > > Is this initialised forcibly anywhere, or only when someone calls > a Random.self_init()? We need to deprecate this module in Mirage and > ensure that we have a randomfront/back model, or risk introducing > poor entropy. This hasn't mattered so far, but will be critical when > we activate the OCaml TLS library that Hannes and David are working on. The TCP/IP stack seems to want it. >> Networking doesn't work on ARM as the code wants to use start_info, >> which doesn't exist. I might try making a fake start_info page on ARM >> rather than modifying everything else. > > Yep, sounds like a good plan to ease x86/ARM transition. Here are some instructions for testing the current version of everything (hacks and all!): To test Mirage on Xen/ARM: These instructions are for building on a soft-float ARM machine (or VM), running on the board itself. If you prefer, you can cross-compile Mini-OS and openlibm and copy the files across (the cross compiler can be hard-float or soft-float; use DESTDIR=... to stage the files): make XEN_TARGET_ARCH=arm32 CROSS_COMPILE=arm-linux-gnueabihf- However, it doesn't save much time and you still need to build the OCaml code on the machine itself. 1. Install libminios.a git clone -b arm-preview https://github.com/talex5/xen.git mini-os cd mini-os ./configure cd extras/mini-os make CONFIG_TEST=n CONFIG_XENBUS=n CONFIG_START_NETWORK=n CONFIG_BLKFRONT=n CONFIG_NETFRONT=n CONFIG_FBFRONT=n CONFIG_KBDFRONT=n CONFIG_CONSFRONT=n CONFIG_XC=n -j4 install 3. Get openlibm and install git clone https://github.com/JuliaLang/openlibm.git cd openlibm make install 4. Pin mirage-platform git clone -b arm-preview https://github.com/talex5/mirage-platform.git opam pin mirage-xen ./mirage-platform 5. Pin mirage-console git clone -b arm-preview https://github.com/talex5/mirage-console.git opam pin mirage-console-xen ./mirage-console 6. Pin mirage git clone -b arm-preview https://github.com/talex5/mirage.git opam pin mirage mirage 7. Build mirage-skeleton/console git clone git://github.com/mirage/mirage-skeleton.git cd mirage-skeleton/console opam install mirage mirage configure --xen make The next step is to get networking working on ARM. -- 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 Jun 11 16:30:18 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 11 Jun 2014 16:30: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 1WulPl-0008Ok-2B; Wed, 11 Jun 2014 16:30:17 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WulPj-0008OR-Ht for mirageos-devel@lists.xenproject.org; Wed, 11 Jun 2014 16:30:15 +0000 Received: from [85.158.143.35:7313] by server-1.bemta-4.messagelabs.com id A6/45-09853-61488935; Wed, 11 Jun 2014 16:30:14 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-15.tower-21.messagelabs.com!1402504213!10725554!1 X-Originating-IP: [74.125.82.46] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_23, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29577 invoked from network); 11 Jun 2014 16:30:14 -0000 Received: from mail-wg0-f46.google.com (HELO mail-wg0-f46.google.com) (74.125.82.46) by server-15.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 11 Jun 2014 16:30:14 -0000 Received: by mail-wg0-f46.google.com with SMTP id y10so5220478wgg.5 for ; Wed, 11 Jun 2014 09:30:12 -0700 (PDT) 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=Xmx3Bq8DjP/8e+73D5I5QT64qfts9IeSZ+ynWfML6OY=; b=bHKtAzZRvjZVdFIKLVb0CQ4m2kCcWni3Br3y+XNyQz3a9RiE7yq0LW68/bL1c0Ktj7 qhAPQLBMMSz90qVzkBQNnsnEmtebdy9G5ZQjTe8fjpy59eC2+pBiSELTocDsT+4HCOnq GlRFiMYg5ummS7jlFWU20xKsxAEauHEuHbzo32tkcCmU/u5VtzG7w7rU6osyCW4ejNCa y1Ghn9KsWjW61F4uQFPNKFKnOFLYaSDWowCGQOwTvCE7dwQh7PC5lBJCWaITU0/rGxft EOBnUNYkzFo1C8ZG/wXrnPkGkD1H21jROgMO+uFjqky1bNAXsTmbrOyRtpv93RKPDj4n 2TRg== X-Received: by 10.180.84.226 with SMTP id c2mr49564561wiz.50.1402504212653; Wed, 11 Jun 2014 09:30:12 -0700 (PDT) Received: from ?IPv6:2001:630:212:248:4531:d926:5b54:5768? ([2001:630:212:248:4531:d926:5b54:5768]) by mx.google.com with ESMTPSA id cy4sm28192522wib.5.2014.06.11.09.30.06 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 11 Jun 2014 09:30:06 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\)) From: Thomas Gazagnaire In-Reply-To: Date: Wed, 11 Jun 2014 17:30:05 +0100 Message-Id: References: <297FC9DB-3A4E-41A5-B00E-9DEF62C625E6@recoil.org> To: Thomas Leonard X-Mailer: Apple Mail (2.1878.2) Cc: "mirageos-devel@lists.xenproject.org" , Anil Madhavapeddy Subject: Re: [MirageOS-devel] Mirage on Xen/ARM status X-BeenThere: mirageos-devel@lists.xenproject.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 > 4. Pin mirage-platform > > git clone -b arm-preview https://github.com/talex5/mirage-platform.git > opam pin mirage-xen ./mirage-platform A quick remark, you can do directly: $ opam pin mirage-xen https://github.com/talex5/mirage-platform.git#arm-preview Thomas > > 5. Pin mirage-console > > git clone -b arm-preview https://github.com/talex5/mirage-console.git > opam pin mirage-console-xen ./mirage-console > > 6. Pin mirage > > git clone -b arm-preview https://github.com/talex5/mirage.git > opam pin mirage mirage > > 7. Build mirage-skeleton/console > > git clone git://github.com/mirage/mirage-skeleton.git > cd mirage-skeleton/console > opam install mirage > mirage configure --xen > make > > > The next step is to get networking working on ARM. > > > -- > 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 Wed Jun 11 16:30:18 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 11 Jun 2014 16:30: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 1WulPl-0008Ok-2B; Wed, 11 Jun 2014 16:30:17 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WulPj-0008OR-Ht for mirageos-devel@lists.xenproject.org; Wed, 11 Jun 2014 16:30:15 +0000 Received: from [85.158.143.35:7313] by server-1.bemta-4.messagelabs.com id A6/45-09853-61488935; Wed, 11 Jun 2014 16:30:14 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-15.tower-21.messagelabs.com!1402504213!10725554!1 X-Originating-IP: [74.125.82.46] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_23, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29577 invoked from network); 11 Jun 2014 16:30:14 -0000 Received: from mail-wg0-f46.google.com (HELO mail-wg0-f46.google.com) (74.125.82.46) by server-15.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 11 Jun 2014 16:30:14 -0000 Received: by mail-wg0-f46.google.com with SMTP id y10so5220478wgg.5 for ; Wed, 11 Jun 2014 09:30:12 -0700 (PDT) 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=Xmx3Bq8DjP/8e+73D5I5QT64qfts9IeSZ+ynWfML6OY=; b=bHKtAzZRvjZVdFIKLVb0CQ4m2kCcWni3Br3y+XNyQz3a9RiE7yq0LW68/bL1c0Ktj7 qhAPQLBMMSz90qVzkBQNnsnEmtebdy9G5ZQjTe8fjpy59eC2+pBiSELTocDsT+4HCOnq GlRFiMYg5ummS7jlFWU20xKsxAEauHEuHbzo32tkcCmU/u5VtzG7w7rU6osyCW4ejNCa y1Ghn9KsWjW61F4uQFPNKFKnOFLYaSDWowCGQOwTvCE7dwQh7PC5lBJCWaITU0/rGxft EOBnUNYkzFo1C8ZG/wXrnPkGkD1H21jROgMO+uFjqky1bNAXsTmbrOyRtpv93RKPDj4n 2TRg== X-Received: by 10.180.84.226 with SMTP id c2mr49564561wiz.50.1402504212653; Wed, 11 Jun 2014 09:30:12 -0700 (PDT) Received: from ?IPv6:2001:630:212:248:4531:d926:5b54:5768? ([2001:630:212:248:4531:d926:5b54:5768]) by mx.google.com with ESMTPSA id cy4sm28192522wib.5.2014.06.11.09.30.06 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 11 Jun 2014 09:30:06 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\)) From: Thomas Gazagnaire In-Reply-To: Date: Wed, 11 Jun 2014 17:30:05 +0100 Message-Id: References: <297FC9DB-3A4E-41A5-B00E-9DEF62C625E6@recoil.org> To: Thomas Leonard X-Mailer: Apple Mail (2.1878.2) Cc: "mirageos-devel@lists.xenproject.org" , Anil Madhavapeddy Subject: Re: [MirageOS-devel] Mirage on Xen/ARM status X-BeenThere: mirageos-devel@lists.xenproject.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 > 4. Pin mirage-platform > > git clone -b arm-preview https://github.com/talex5/mirage-platform.git > opam pin mirage-xen ./mirage-platform A quick remark, you can do directly: $ opam pin mirage-xen https://github.com/talex5/mirage-platform.git#arm-preview Thomas > > 5. Pin mirage-console > > git clone -b arm-preview https://github.com/talex5/mirage-console.git > opam pin mirage-console-xen ./mirage-console > > 6. Pin mirage > > git clone -b arm-preview https://github.com/talex5/mirage.git > opam pin mirage mirage > > 7. Build mirage-skeleton/console > > git clone git://github.com/mirage/mirage-skeleton.git > cd mirage-skeleton/console > opam install mirage > mirage configure --xen > make > > > The next step is to get networking working on ARM. > > > -- > 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 Thu Jun 12 11:00:07 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 12 Jun 2014 11:00:07 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Wv2jg-0006JV-8V; Thu, 12 Jun 2014 11:00:00 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Wv2je-0006JQ-Od for mirageos-devel@lists.xenproject.org; Thu, 12 Jun 2014 10:59:59 +0000 Received: from [193.109.254.147:33042] by server-2.bemta-14.messagelabs.com id D4/F7-21684-E2889935; Thu, 12 Jun 2014 10:59:58 +0000 X-Env-Sender: talex5@gmail.com X-Msg-Ref: server-6.tower-27.messagelabs.com!1402570796!10781400!1 X-Originating-IP: [209.85.219.51] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, ML_RADAR_SPEW_LINKS_23,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 319 invoked from network); 12 Jun 2014 10:59:57 -0000 Received: from mail-oa0-f51.google.com (HELO mail-oa0-f51.google.com) (209.85.219.51) by server-6.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 12 Jun 2014 10:59:57 -0000 Received: by mail-oa0-f51.google.com with SMTP id j17so1134237oag.38 for ; Thu, 12 Jun 2014 03:59:55 -0700 (PDT) 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=4LPkWu6hCHfq2uivOXhEkWF4s8I0BNLFdtDBgYGpk4o=; b=gouB5S47tlvjO6dVkBpE/42ddOSMEMRJW2iAC7g+DJGpvJSmM6srNgcTe4MKppVNhW ffIFDUP7P0wJ0fYWT77AhjqH6NlfFh285G3R4Gr1uOgG/c8jf20ZyyXE7WNFJGMuFBE0 KJbcEfBXDqJ90z7/jyEc42Iyo9+i4MggRx9bIoZO92bJZY9+MWIuTcv2WnOK8/AkMw5I ABatKjkwJMrU2SqIhcafsJIUipL2pCJGYWx/aqBUBfLuw2Y/1+SS8rg1pkUVpZ5aoAA4 eJQZ4gSGDILKQ9jNPSY9PknpTLEjIPD2A7SSGER4oTchrVLvZtTsNrAY6zY5teSs7bkj O6UA== MIME-Version: 1.0 X-Received: by 10.60.134.239 with SMTP id pn15mr1493977oeb.85.1402570795563; Thu, 12 Jun 2014 03:59:55 -0700 (PDT) Received: by 10.76.92.5 with HTTP; Thu, 12 Jun 2014 03:59:55 -0700 (PDT) In-Reply-To: References: <297FC9DB-3A4E-41A5-B00E-9DEF62C625E6@recoil.org> Date: Thu, 12 Jun 2014 11:59:55 +0100 Message-ID: From: Thomas Leonard To: Thomas Gazagnaire Cc: "mirageos-devel@lists.xenproject.org" , Anil Madhavapeddy Subject: Re: [MirageOS-devel] Mirage on Xen/ARM status X-BeenThere: mirageos-devel@lists.xenproject.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 11 June 2014 17:30, Thomas Gazagnaire wrote: >> 4. Pin mirage-platform >> >> git clone -b arm-preview https://github.com/talex5/mirage-platform.git >> opam pin mirage-xen ./mirage-platform > > A quick remark, you can do directly: > > $ opam pin mirage-xen https://github.com/talex5/mirage-platform.git#arm-preview That's useful. Is it documented somwhere? This just says to use a local path: https://opam.ocaml.org/doc/Advanced_Usage.html#h2-Versionpinning What happens when I want to update? Does it do a git fetch for me? -- 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 Jun 12 11:00:07 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 12 Jun 2014 11:00:07 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Wv2jg-0006JV-8V; Thu, 12 Jun 2014 11:00:00 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Wv2je-0006JQ-Od for mirageos-devel@lists.xenproject.org; Thu, 12 Jun 2014 10:59:59 +0000 Received: from [193.109.254.147:33042] by server-2.bemta-14.messagelabs.com id D4/F7-21684-E2889935; Thu, 12 Jun 2014 10:59:58 +0000 X-Env-Sender: talex5@gmail.com X-Msg-Ref: server-6.tower-27.messagelabs.com!1402570796!10781400!1 X-Originating-IP: [209.85.219.51] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, ML_RADAR_SPEW_LINKS_23,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 319 invoked from network); 12 Jun 2014 10:59:57 -0000 Received: from mail-oa0-f51.google.com (HELO mail-oa0-f51.google.com) (209.85.219.51) by server-6.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 12 Jun 2014 10:59:57 -0000 Received: by mail-oa0-f51.google.com with SMTP id j17so1134237oag.38 for ; Thu, 12 Jun 2014 03:59:55 -0700 (PDT) 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=4LPkWu6hCHfq2uivOXhEkWF4s8I0BNLFdtDBgYGpk4o=; b=gouB5S47tlvjO6dVkBpE/42ddOSMEMRJW2iAC7g+DJGpvJSmM6srNgcTe4MKppVNhW ffIFDUP7P0wJ0fYWT77AhjqH6NlfFh285G3R4Gr1uOgG/c8jf20ZyyXE7WNFJGMuFBE0 KJbcEfBXDqJ90z7/jyEc42Iyo9+i4MggRx9bIoZO92bJZY9+MWIuTcv2WnOK8/AkMw5I ABatKjkwJMrU2SqIhcafsJIUipL2pCJGYWx/aqBUBfLuw2Y/1+SS8rg1pkUVpZ5aoAA4 eJQZ4gSGDILKQ9jNPSY9PknpTLEjIPD2A7SSGER4oTchrVLvZtTsNrAY6zY5teSs7bkj O6UA== MIME-Version: 1.0 X-Received: by 10.60.134.239 with SMTP id pn15mr1493977oeb.85.1402570795563; Thu, 12 Jun 2014 03:59:55 -0700 (PDT) Received: by 10.76.92.5 with HTTP; Thu, 12 Jun 2014 03:59:55 -0700 (PDT) In-Reply-To: References: <297FC9DB-3A4E-41A5-B00E-9DEF62C625E6@recoil.org> Date: Thu, 12 Jun 2014 11:59:55 +0100 Message-ID: From: Thomas Leonard To: Thomas Gazagnaire Cc: "mirageos-devel@lists.xenproject.org" , Anil Madhavapeddy Subject: Re: [MirageOS-devel] Mirage on Xen/ARM status X-BeenThere: mirageos-devel@lists.xenproject.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 11 June 2014 17:30, Thomas Gazagnaire wrote: >> 4. Pin mirage-platform >> >> git clone -b arm-preview https://github.com/talex5/mirage-platform.git >> opam pin mirage-xen ./mirage-platform > > A quick remark, you can do directly: > > $ opam pin mirage-xen https://github.com/talex5/mirage-platform.git#arm-preview That's useful. Is it documented somwhere? This just says to use a local path: https://opam.ocaml.org/doc/Advanced_Usage.html#h2-Versionpinning What happens when I want to update? Does it do a git fetch for me? -- 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 Jun 12 11:07:03 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 12 Jun 2014 11:07: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 1Wv2qV-0006Rs-Sm; Thu, 12 Jun 2014 11:07:03 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Wv2qU-0006Ri-Jf for mirageos-devel@lists.xenproject.org; Thu, 12 Jun 2014 11:07:02 +0000 Received: from [85.158.137.68:27891] by server-9.bemta-3.messagelabs.com id 12/A9-30063-5D989935; Thu, 12 Jun 2014 11:07:01 +0000 X-Env-Sender: daniel.buenzli@erratique.ch X-Msg-Ref: server-4.tower-31.messagelabs.com!1402571220!9583108!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.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 18077 invoked from network); 12 Jun 2014 11:07:00 -0000 Received: from mail6.webfaction.com (HELO smtp.webfaction.com) (74.55.86.74) by server-4.tower-31.messagelabs.com with SMTP; 12 Jun 2014 11:07:00 -0000 Received: from [172.17.159.22] (global-1-26.nat.csx.cam.ac.uk [131.111.184.26]) by smtp.webfaction.com (Postfix) with ESMTP id 78904228715C; Thu, 12 Jun 2014 11:06:59 +0000 (UTC) Date: Thu, 12 Jun 2014 12:06:57 +0100 From: =?utf-8?Q?Daniel_B=C3=BCnzli?= To: Thomas Leonard Message-ID: <2BBD7C4273AC46E2BAD76BC4AEA76FDE@erratique.ch> In-Reply-To: References: <297FC9DB-3A4E-41A5-B00E-9DEF62C625E6@recoil.org> X-Mailer: sparrow 1.6.4 (build 1178) MIME-Version: 1.0 Content-Disposition: inline Cc: Thomas Gazagnaire , "=?utf-8?Q?mirageos-devel=40lists.xenproject.org?=" , Anil Madhavapeddy Subject: Re: [MirageOS-devel] Mirage on Xen/ARM status X-BeenThere: mirageos-devel@lists.xenproject.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 TGUgamV1ZGksIDEyIGp1aW4gMjAxNCDDoCAxMTo1OSwgVGhvbWFzIExlb25hcmQgYSDDqWNyaXQg Ogo+IFRoYXQncyB1c2VmdWwuIElzIGl0IGRvY3VtZW50ZWQgc29td2hlcmU/CgpTaG91bGQgYmUs IGluIG9wYW0gcGluIOKAlGhlbHAgdW5kZXIgdGhlIGBhZGRgIGNvbW1hbmQgKGF0IGxlYXN0IGlu IGxhdGVzdCBvcGFtIGl0IGlzKS4KICAKPiBXaGF0IGhhcHBlbnMgd2hlbiBJIHdhbnQgdG8gdXBk YXRlPyBEb2VzIGl0IGRvIGEgZ2l0IGZldGNoIGZvciBtZT8KClllcy4KCkRhbmllbAoKCgpfX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwpNaXJhZ2VPUy1kZXZl bCBtYWlsaW5nIGxpc3QKTWlyYWdlT1MtZGV2ZWxAbGlzdHMueGVucHJvamVjdC5vcmcKaHR0cDov L2xpc3RzLnhlbnByb2plY3Qub3JnL2NnaS1iaW4vbWFpbG1hbi9saXN0aW5mby9taXJhZ2Vvcy1k ZXZlbAo= From mirageos-devel-bounces@lists.xenproject.org Thu Jun 12 11:07:03 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 12 Jun 2014 11:07: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 1Wv2qV-0006Rs-Sm; Thu, 12 Jun 2014 11:07:03 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Wv2qU-0006Ri-Jf for mirageos-devel@lists.xenproject.org; Thu, 12 Jun 2014 11:07:02 +0000 Received: from [85.158.137.68:27891] by server-9.bemta-3.messagelabs.com id 12/A9-30063-5D989935; Thu, 12 Jun 2014 11:07:01 +0000 X-Env-Sender: daniel.buenzli@erratique.ch X-Msg-Ref: server-4.tower-31.messagelabs.com!1402571220!9583108!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.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 18077 invoked from network); 12 Jun 2014 11:07:00 -0000 Received: from mail6.webfaction.com (HELO smtp.webfaction.com) (74.55.86.74) by server-4.tower-31.messagelabs.com with SMTP; 12 Jun 2014 11:07:00 -0000 Received: from [172.17.159.22] (global-1-26.nat.csx.cam.ac.uk [131.111.184.26]) by smtp.webfaction.com (Postfix) with ESMTP id 78904228715C; Thu, 12 Jun 2014 11:06:59 +0000 (UTC) Date: Thu, 12 Jun 2014 12:06:57 +0100 From: =?utf-8?Q?Daniel_B=C3=BCnzli?= To: Thomas Leonard Message-ID: <2BBD7C4273AC46E2BAD76BC4AEA76FDE@erratique.ch> In-Reply-To: References: <297FC9DB-3A4E-41A5-B00E-9DEF62C625E6@recoil.org> X-Mailer: sparrow 1.6.4 (build 1178) MIME-Version: 1.0 Content-Disposition: inline Cc: Thomas Gazagnaire , "=?utf-8?Q?mirageos-devel=40lists.xenproject.org?=" , Anil Madhavapeddy Subject: Re: [MirageOS-devel] Mirage on Xen/ARM status X-BeenThere: mirageos-devel@lists.xenproject.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 TGUgamV1ZGksIDEyIGp1aW4gMjAxNCDDoCAxMTo1OSwgVGhvbWFzIExlb25hcmQgYSDDqWNyaXQg Ogo+IFRoYXQncyB1c2VmdWwuIElzIGl0IGRvY3VtZW50ZWQgc29td2hlcmU/CgpTaG91bGQgYmUs IGluIG9wYW0gcGluIOKAlGhlbHAgdW5kZXIgdGhlIGBhZGRgIGNvbW1hbmQgKGF0IGxlYXN0IGlu IGxhdGVzdCBvcGFtIGl0IGlzKS4KICAKPiBXaGF0IGhhcHBlbnMgd2hlbiBJIHdhbnQgdG8gdXBk YXRlPyBEb2VzIGl0IGRvIGEgZ2l0IGZldGNoIGZvciBtZT8KClllcy4KCkRhbmllbAoKCgpfX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwpNaXJhZ2VPUy1kZXZl bCBtYWlsaW5nIGxpc3QKTWlyYWdlT1MtZGV2ZWxAbGlzdHMueGVucHJvamVjdC5vcmcKaHR0cDov L2xpc3RzLnhlbnByb2plY3Qub3JnL2NnaS1iaW4vbWFpbG1hbi9saXN0aW5mby9taXJhZ2Vvcy1k ZXZlbAo= From mirageos-devel-bounces@lists.xenproject.org Thu Jun 12 14:46:13 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 12 Jun 2014 14:46: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 1Wv6GV-0001TN-Kv; Thu, 12 Jun 2014 14:46:07 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Wv6GU-0001TA-8g for mirageos-devel@lists.xenproject.org; Thu, 12 Jun 2014 14:46:06 +0000 Received: from [85.158.139.211:52219] by server-8.bemta-5.messagelabs.com id 9E/4B-11310-D2DB9935; Thu, 12 Jun 2014 14:46:05 +0000 X-Env-Sender: talex5@gmail.com X-Msg-Ref: server-13.tower-206.messagelabs.com!1402584363!9645768!1 X-Originating-IP: [209.85.219.50] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, ML_RADAR_SPEW_LINKS_23,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 19841 invoked from network); 12 Jun 2014 14:46:04 -0000 Received: from mail-oa0-f50.google.com (HELO mail-oa0-f50.google.com) (209.85.219.50) by server-13.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 12 Jun 2014 14:46:04 -0000 Received: by mail-oa0-f50.google.com with SMTP id n16so1439517oag.23 for ; Thu, 12 Jun 2014 07:46:02 -0700 (PDT) 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=k4sU0tMWQs8B6B+9trIglgCDA5CeDk9BQo1mSZnX/gk=; b=zB+QM7WwMcJSe7UpF9DVQ/jD9bHF+ai4Gp7fobRolvH7G9LI2l/XHTO2mqfyjIyWHa sglQzVtw8Nclpq2lpeR9x901nHPKNKWx5BbocAmrKcEJ813tk5GZNVdnfeCWM/oitW4F uCpezjqBl9AQHcIuMMASLTZrUERDdHv6yJ/GRSna0CM8HMasQDgnKM8l9vNtey+C33b7 k1VOVzxYbF+f21iXETqktgchZPSNXojSpxRM+xXmWKV/+SJrjCw/cBnQcBblD9BbkEhY XH/8BROfK4TRzRrVyr0blJXQsc/+YOsd6OrWeMZT6P7J/XEc9agiIziLMH/GKJTqXcGT UpgA== MIME-Version: 1.0 X-Received: by 10.182.97.234 with SMTP id ed10mr44261293obb.31.1402584362869; Thu, 12 Jun 2014 07:46:02 -0700 (PDT) Received: by 10.76.92.5 with HTTP; Thu, 12 Jun 2014 07:46:02 -0700 (PDT) In-Reply-To: References: <297FC9DB-3A4E-41A5-B00E-9DEF62C625E6@recoil.org> Date: Thu, 12 Jun 2014 15:46:02 +0100 Message-ID: From: Thomas Leonard To: Anil Madhavapeddy Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Mirage on Xen/ARM status X-BeenThere: mirageos-devel@lists.xenproject.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 11 June 2014 17:27, Thomas Leonard wrote: > On 5 June 2014 21:29, Anil Madhavapeddy wrote: >> On 4 Jun 2014, at 13:33, Thomas Leonard wrote: >> >>> An update on the Mirage/ARM port: >>> >>> I have mirage-platform upgraded to the new Mini-OS (plus openlibm and >>> no libc). Networking is working again on x86_64 (I can telnet to the >>> mirage-skeleton/network service and send it a message), but not on ARM >>> yet. >> >> Good to have x86_64 back! It's probably a good idea to CC me and Dave >> on the patchbombs to xen-devel, as I only sample the list these days >> due to mail volume. >> >>> This required some changes to Mini-OS to expose the grant table >>> details and to stop Mini-OS's xenbus from stealing the event >>> notifications. I need this clean this up. >> >> To be clear, this is networking using lwIP on ARM isnt it? For Mirage, >> the MiniOS Xenbus should be disabled entirely since our own OCaml >> Xenstore will handle everything. > > By default, minios's event handler calls do_event on each event, and > loops until they're all handled, so I had to disable that code. > >>> OCaml's Random currently tries to open /dev/urandom, which fails. >>> Looks like it falls back to using gettimeofday in that case. It logs a >>> message to the console ("Attempt to open(/dev/urandom)!"), so >>> hopefully we'll remember to fix it eventually. >> >> Is this initialised forcibly anywhere, or only when someone calls >> a Random.self_init()? We need to deprecate this module in Mirage and >> ensure that we have a randomfront/back model, or risk introducing >> poor entropy. This hasn't mattered so far, but will be critical when >> we activate the OCaml TLS library that Hannes and David are working on. > > The TCP/IP stack seems to want it. > >>> Networking doesn't work on ARM as the code wants to use start_info, >>> which doesn't exist. I might try making a fake start_info page on ARM >>> rather than modifying everything else. >> >> Yep, sounds like a good plan to ease x86/ARM transition. > > Here are some instructions for testing the current version of > everything (hacks and all!): > > To test Mirage on Xen/ARM: > > These instructions are for building on a soft-float ARM machine (or > VM), running on the board itself. If you prefer, you can cross-compile > Mini-OS and openlibm and copy the files across (the cross compiler > can be hard-float or soft-float; use DESTDIR=... to stage the files): > > make XEN_TARGET_ARCH=arm32 CROSS_COMPILE=arm-linux-gnueabihf- > > However, it doesn't save much time and you still need to build the > OCaml code on the machine itself. > > > 1. Install libminios.a > > git clone -b arm-preview https://github.com/talex5/xen.git mini-os > cd mini-os > ./configure > cd extras/mini-os > > make CONFIG_TEST=n CONFIG_XENBUS=n CONFIG_START_NETWORK=n > CONFIG_BLKFRONT=n CONFIG_NETFRONT=n CONFIG_FBFRONT=n CONFIG_KBDFRONT=n > CONFIG_CONSFRONT=n CONFIG_XC=n -j4 install > > 3. Get openlibm and install > > git clone https://github.com/JuliaLang/openlibm.git > cd openlibm > make install > > 4. Pin mirage-platform > > git clone -b arm-preview https://github.com/talex5/mirage-platform.git > opam pin mirage-xen ./mirage-platform > > 5. Pin mirage-console > > git clone -b arm-preview https://github.com/talex5/mirage-console.git > opam pin mirage-console-xen ./mirage-console > > 6. Pin mirage > > git clone -b arm-preview https://github.com/talex5/mirage.git > opam pin mirage mirage > > 7. Build mirage-skeleton/console > > git clone git://github.com/mirage/mirage-skeleton.git > cd mirage-skeleton/console > opam install mirage > mirage configure --xen > make > > > The next step is to get networking working on ARM. This seems to be working now (I can telnet to port 80 and send it a message), which it displays on the console. The main problem turned out to be ones_complement_checksum_bigarray, which was doing unaligned double-word (64-bit) memory access. This faults on ARM. For testing, I replaced it with the version in the unix directory. -- 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 Jun 12 14:46:13 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 12 Jun 2014 14:46: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 1Wv6GV-0001TN-Kv; Thu, 12 Jun 2014 14:46:07 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Wv6GU-0001TA-8g for mirageos-devel@lists.xenproject.org; Thu, 12 Jun 2014 14:46:06 +0000 Received: from [85.158.139.211:52219] by server-8.bemta-5.messagelabs.com id 9E/4B-11310-D2DB9935; Thu, 12 Jun 2014 14:46:05 +0000 X-Env-Sender: talex5@gmail.com X-Msg-Ref: server-13.tower-206.messagelabs.com!1402584363!9645768!1 X-Originating-IP: [209.85.219.50] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, ML_RADAR_SPEW_LINKS_23,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 19841 invoked from network); 12 Jun 2014 14:46:04 -0000 Received: from mail-oa0-f50.google.com (HELO mail-oa0-f50.google.com) (209.85.219.50) by server-13.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 12 Jun 2014 14:46:04 -0000 Received: by mail-oa0-f50.google.com with SMTP id n16so1439517oag.23 for ; Thu, 12 Jun 2014 07:46:02 -0700 (PDT) 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=k4sU0tMWQs8B6B+9trIglgCDA5CeDk9BQo1mSZnX/gk=; b=zB+QM7WwMcJSe7UpF9DVQ/jD9bHF+ai4Gp7fobRolvH7G9LI2l/XHTO2mqfyjIyWHa sglQzVtw8Nclpq2lpeR9x901nHPKNKWx5BbocAmrKcEJ813tk5GZNVdnfeCWM/oitW4F uCpezjqBl9AQHcIuMMASLTZrUERDdHv6yJ/GRSna0CM8HMasQDgnKM8l9vNtey+C33b7 k1VOVzxYbF+f21iXETqktgchZPSNXojSpxRM+xXmWKV/+SJrjCw/cBnQcBblD9BbkEhY XH/8BROfK4TRzRrVyr0blJXQsc/+YOsd6OrWeMZT6P7J/XEc9agiIziLMH/GKJTqXcGT UpgA== MIME-Version: 1.0 X-Received: by 10.182.97.234 with SMTP id ed10mr44261293obb.31.1402584362869; Thu, 12 Jun 2014 07:46:02 -0700 (PDT) Received: by 10.76.92.5 with HTTP; Thu, 12 Jun 2014 07:46:02 -0700 (PDT) In-Reply-To: References: <297FC9DB-3A4E-41A5-B00E-9DEF62C625E6@recoil.org> Date: Thu, 12 Jun 2014 15:46:02 +0100 Message-ID: From: Thomas Leonard To: Anil Madhavapeddy Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Mirage on Xen/ARM status X-BeenThere: mirageos-devel@lists.xenproject.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 11 June 2014 17:27, Thomas Leonard wrote: > On 5 June 2014 21:29, Anil Madhavapeddy wrote: >> On 4 Jun 2014, at 13:33, Thomas Leonard wrote: >> >>> An update on the Mirage/ARM port: >>> >>> I have mirage-platform upgraded to the new Mini-OS (plus openlibm and >>> no libc). Networking is working again on x86_64 (I can telnet to the >>> mirage-skeleton/network service and send it a message), but not on ARM >>> yet. >> >> Good to have x86_64 back! It's probably a good idea to CC me and Dave >> on the patchbombs to xen-devel, as I only sample the list these days >> due to mail volume. >> >>> This required some changes to Mini-OS to expose the grant table >>> details and to stop Mini-OS's xenbus from stealing the event >>> notifications. I need this clean this up. >> >> To be clear, this is networking using lwIP on ARM isnt it? For Mirage, >> the MiniOS Xenbus should be disabled entirely since our own OCaml >> Xenstore will handle everything. > > By default, minios's event handler calls do_event on each event, and > loops until they're all handled, so I had to disable that code. > >>> OCaml's Random currently tries to open /dev/urandom, which fails. >>> Looks like it falls back to using gettimeofday in that case. It logs a >>> message to the console ("Attempt to open(/dev/urandom)!"), so >>> hopefully we'll remember to fix it eventually. >> >> Is this initialised forcibly anywhere, or only when someone calls >> a Random.self_init()? We need to deprecate this module in Mirage and >> ensure that we have a randomfront/back model, or risk introducing >> poor entropy. This hasn't mattered so far, but will be critical when >> we activate the OCaml TLS library that Hannes and David are working on. > > The TCP/IP stack seems to want it. > >>> Networking doesn't work on ARM as the code wants to use start_info, >>> which doesn't exist. I might try making a fake start_info page on ARM >>> rather than modifying everything else. >> >> Yep, sounds like a good plan to ease x86/ARM transition. > > Here are some instructions for testing the current version of > everything (hacks and all!): > > To test Mirage on Xen/ARM: > > These instructions are for building on a soft-float ARM machine (or > VM), running on the board itself. If you prefer, you can cross-compile > Mini-OS and openlibm and copy the files across (the cross compiler > can be hard-float or soft-float; use DESTDIR=... to stage the files): > > make XEN_TARGET_ARCH=arm32 CROSS_COMPILE=arm-linux-gnueabihf- > > However, it doesn't save much time and you still need to build the > OCaml code on the machine itself. > > > 1. Install libminios.a > > git clone -b arm-preview https://github.com/talex5/xen.git mini-os > cd mini-os > ./configure > cd extras/mini-os > > make CONFIG_TEST=n CONFIG_XENBUS=n CONFIG_START_NETWORK=n > CONFIG_BLKFRONT=n CONFIG_NETFRONT=n CONFIG_FBFRONT=n CONFIG_KBDFRONT=n > CONFIG_CONSFRONT=n CONFIG_XC=n -j4 install > > 3. Get openlibm and install > > git clone https://github.com/JuliaLang/openlibm.git > cd openlibm > make install > > 4. Pin mirage-platform > > git clone -b arm-preview https://github.com/talex5/mirage-platform.git > opam pin mirage-xen ./mirage-platform > > 5. Pin mirage-console > > git clone -b arm-preview https://github.com/talex5/mirage-console.git > opam pin mirage-console-xen ./mirage-console > > 6. Pin mirage > > git clone -b arm-preview https://github.com/talex5/mirage.git > opam pin mirage mirage > > 7. Build mirage-skeleton/console > > git clone git://github.com/mirage/mirage-skeleton.git > cd mirage-skeleton/console > opam install mirage > mirage configure --xen > make > > > The next step is to get networking working on ARM. This seems to be working now (I can telnet to port 80 and send it a message), which it displays on the console. The main problem turned out to be ones_complement_checksum_bigarray, which was doing unaligned double-word (64-bit) memory access. This faults on ARM. For testing, I replaced it with the version in the unix directory. -- 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 Jun 12 16:55:54 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 12 Jun 2014 16:55: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 1Wv8I0-0000qA-9h; Thu, 12 Jun 2014 16:55:48 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Wv8Hy-0000pv-Jw for mirageos-devel@lists.xenproject.org; Thu, 12 Jun 2014 16:55:46 +0000 Received: from [85.158.137.68:59417] by server-17.bemta-3.messagelabs.com id 3D/C1-22741-19BD9935; Thu, 12 Jun 2014 16:55:45 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-15.tower-31.messagelabs.com!1402592144!9599231!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29576 invoked from network); 12 Jun 2014 16:55:44 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-15.tower-31.messagelabs.com with SMTP; 12 Jun 2014 16:55:44 -0000 Received: (qmail 26708 invoked by uid 634); 12 Jun 2014 16:55:44 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from global-1-27.nat.csx.cam.ac.uk (HELO dhcp-172-17-175-65.eduroam.lapwing.private.cam.ac.uk) (131.111.184.27) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Thu, 12 Jun 2014 17:55:43 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\)) From: Anil Madhavapeddy In-Reply-To: Date: Thu, 12 Jun 2014 17:55:38 +0100 Message-Id: References: <5396D482.6000706@eu.citrix.com> To: Lars Kurth X-Mailer: Apple Mail (2.1874) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: Jonathan Ludlam , "mirageos-devel@lists.xenproject.org" , "xen-api@lists.xen.org" Subject: Re: [MirageOS-devel] [Xen-API] Xapi project repositories X-BeenThere: mirageos-devel@lists.xenproject.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 Jon -- I agree with all these changes. In addition, I'm going to move the OCaml-GitHub bindings to the Mirage org as well. This way, any future 'summary-of-the-week' binaries can also benefit both Mirage and the Xapi project, and not be sitting in a personal repository. Lars: I will get you the final repo list for Bitergia just as soon as all this shuffling is done. We'll have a canonical list for the Mirage 2.0 release. best, Anil On 10 Jun 2014, at 11:05, Lars Kurth wrote: > Hi all, > > when you have the final list of repos for xapi and mirage. Please send it to me such that I can update the bitergia dashboard > > Still need to get the Mirage list, which I have been waiting for for several months. > > @Jon. Do you want press coverage for XAPI 2? > Can talk to you on Thursdays > > Lars > ________________________________________ > From: Jonathan Ludlam > Sent: 10 June 2014 10:48 > To: xen-api@lists.xen.org; mirageos-devel@lists.xenproject.org > Cc: Lars Kurth > Subject: Xapi project repositories > > Hi all, > > In preparing for the 2.0 release, it's become increasingly obvious that > we really need to tidy up the xapi-project org on github. There are many > repositories that are in the org that aren't a part of the Xapi Project. > I started making a list, and realised that there are a few other > inconsistencies that we ought to clean up at the same time, for example, > many repositories are marked as forks of personal repos where that > relationship ought to be reversed. > > > > First, there are some repositories that should just be deleted: > > - opam > A fork of github.com/ocaml/opam. I don't know why we have this, it > doesn't appear to have any commits from us. > > - opam-repository > Same as opam. > > - xcp-fhs > This is unused by anyone, as far as I know. > > - xen-unstable-mirror > Just a mirror of the xen project repository. > > - xcp-storage-managers > An old fork. sm.git should be used instead. > > - ocaml-sha > A fork of upstream, no additional changesets from us. > > - ocaml-tar > A fork of upstream, no additional changesets from us > > - ocaml-vhd > A fork of upstream, no additional changesets from us > > > > Secondly, I believe some of the repositories should be transferred to > the 'xenserver' organisation, which I think probably needs approval, as > the xenserver org is not a part of the Linux Foundation. These are: > > - filesystem-summarise > A tool to check for filesystem changes. Useful on XenServer for > detecting when changes have been made to configuration files and so on. > Not useful for general installations of the xapi project. > > - jiralib > An old python library for talking to jira. Superseded by jira-python > package. > > - mirrortest > A test repository for checking Citrix's internal mirrors of the github > repositories. > > - PRDup > 'Pull Request Duplicator', a tool for helping to backport pull requests > to different branches. > > - pull-request-manager > Uses Citrix's internal build system to test pull requests - no longer used. > > - xs-pull-request-build-scripts > Replacement for pull-request-manager - uses Citrix's internal build > system to test pull requests, this time using jenkins. > > - xen-api-libs-specs > Spec files used for building a lot of the xapi-project components for > XenServer. There is large overlap with github.com/xenserver/buildroot - > these should probably merge (or become more closely related). > > - xen-api-backports > Similar to xen-api-libs-specs, but for Citrix's internal 'old > buildsystem' as opposed to Citrix's internal 'newer buildsystem'. > > I don't think any of these is actually contentious - they probably > should never have been part of the Linux Foundation, and have been there > since we only had the one place on github to put things! > > > > Third, we have some libraries that are actually mirage core libraries. > These should transfer over to the mirage organisation (remaining in LF, > as mirage is a Xen Project subproject like xapi): > > - ocaml-gnt > OCaml grant table manipulation. This code originated in the mirage > project and was put here when it was split out of mirage-platform (see > here: > https://github.com/mirage/mirage-platform/commit/f532fc79af41e0e39b624a8e63dffc900bf1b7e4). > > - ocaml-xenstore > This is the mirage implementation of a xenstore client library. Required > for running mirage kernels on xen. We use the unix-flavour of this > library. It also contains a WIP new version of the guts of a xenstore > daemon, which will be a mirage-style unix process _or_ unikernel > (xenstore stub-domain!) that should eventually be upstreamed into xen. > > - ocaml-xenstore-clients > Slightly oddly named library that defines the unix transport mechanisms > (unix-domain sockets) for using the ocaml-xenstore library. This is the > unix counterpart to the internal shared-page mechanism used by mirage > unikernels. > > - ocaml-evtchn > Similar to ocaml-gnt - split from the main mirage code at around the > same time as ocaml-gnt. > > - ocaml-xenstore-xen > Unused by xapi-project. I believe in here lives the code that turns the > xenstore daemon library from ocaml-xenstore into the actual xenstored > stubdomain or process. > > > > We have a few repositories that are forks of upstream repos with some of > our own changes in. We should get these changes upstreamed at some > point, but for now we should leave them there, but recognise that these > aren't necessarily part of the official Xapi Project (excepting where > they are, e.g. ocaml-xen-lowlevel-libs, which is a staging area for > upstreaming back into xen.git!) > - oclock > - ocamltest > - ocaml-xen-lowlevel-libs > - python-github2 > > > > Then there are generic ocaml libraries which could be used by other > ocaml programs. I think these can live on in the xapi project > organisation for now, but I wouldn't class them as 'core' xapi-project > repos. > > - cdrom > - netdev > - ocamldoc-json > - ocaml-encodings > - ocaml-crc > - ocaml-fd-send-recv > - ocaml-netlink > - ocaml-opasswd > - ocaml-pci-db > - ocaml-qmp > - stdext > - stunnel > - nbd > > > > > Which leaves us with the 'core' xapi project repositories: > > - blktap > - blktap-dkms > - example-ocaml-daemon > - ffs > - forkexecd > - libvhd > - message-switch > - ocaml-rrdd-plugins > - opam-repo-dev > - rrd-transport > - rrdd-plugin-legacy > - rrddump > - sm > - sm-cli > - squeezed > - tapctl > - vhd-tool > - vncproxy > - vncterm > - vxs > - wsproxy > - xapi-codegen > - xapi-libvirt-storage > - xapi-project > - xcp-eliloader > - xcp-guest-templates > - xcp-idl > - xcp-inventory > - xcp-networkd > - xcp-rrd > - xcp-rrdd > - xen-api > - xen-api-client > - xen-api-libs > - xen-api-libs-transitional > - xen-api-sdk > - xenops > - xenops-cli > - xenopsd > > Of the above lists that will remain in the xapi project, these > repositories have incorrect forking status (they are marked as forks of > someone here at Citrix, but shouldn't be): > > Forked from me (jonludlam on github): > xen-api-libs-transitional > xen-api-client > xcp-guest-templates > xcp-eliloader > wsproxy > tapctl > libvhd > blktap-dkms > netdev > nbd > cdrom > > Forked from Dave Scott (djs55) > xcp-idl > vhd-tool > ffs > ocaml-vhd > ocaml-tar > ocaml-fd-send-recv > > Forked from Simon Beaumont (simonjbeaumont): > ocaml-pci-db > > Forked from Mike McClurg (mcclurmc): > ocaml-opasswd > > These forking relationship problems need to be fixed by the people who > own the upstream repo. I don't think it's quite as simple as clicking > the 'transfer repository' button. If anyone knows the exact procedure > for doing this, could they please reply? > > > In summary, I believe we need to: > 1) delete some repositories > 2) move some repositories to xenserver > 3) move some repositories to mirage-project > 4) transfer ownership of some repositories (just flip around the > direction of the fork). > 5) document all of this on the wiki! > > Any comments? > > Jon > > > > > > _______________________________________________ > Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api _______________________________________________ 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 Jun 12 16:55:54 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 12 Jun 2014 16:55: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 1Wv8I0-0000qA-9h; Thu, 12 Jun 2014 16:55:48 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Wv8Hy-0000pv-Jw for mirageos-devel@lists.xenproject.org; Thu, 12 Jun 2014 16:55:46 +0000 Received: from [85.158.137.68:59417] by server-17.bemta-3.messagelabs.com id 3D/C1-22741-19BD9935; Thu, 12 Jun 2014 16:55:45 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-15.tower-31.messagelabs.com!1402592144!9599231!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29576 invoked from network); 12 Jun 2014 16:55:44 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-15.tower-31.messagelabs.com with SMTP; 12 Jun 2014 16:55:44 -0000 Received: (qmail 26708 invoked by uid 634); 12 Jun 2014 16:55:44 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from global-1-27.nat.csx.cam.ac.uk (HELO dhcp-172-17-175-65.eduroam.lapwing.private.cam.ac.uk) (131.111.184.27) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Thu, 12 Jun 2014 17:55:43 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\)) From: Anil Madhavapeddy In-Reply-To: Date: Thu, 12 Jun 2014 17:55:38 +0100 Message-Id: References: <5396D482.6000706@eu.citrix.com> To: Lars Kurth X-Mailer: Apple Mail (2.1874) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: Jonathan Ludlam , "mirageos-devel@lists.xenproject.org" , "xen-api@lists.xen.org" Subject: Re: [MirageOS-devel] [Xen-API] Xapi project repositories X-BeenThere: mirageos-devel@lists.xenproject.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 Jon -- I agree with all these changes. In addition, I'm going to move the OCaml-GitHub bindings to the Mirage org as well. This way, any future 'summary-of-the-week' binaries can also benefit both Mirage and the Xapi project, and not be sitting in a personal repository. Lars: I will get you the final repo list for Bitergia just as soon as all this shuffling is done. We'll have a canonical list for the Mirage 2.0 release. best, Anil On 10 Jun 2014, at 11:05, Lars Kurth wrote: > Hi all, > > when you have the final list of repos for xapi and mirage. Please send it to me such that I can update the bitergia dashboard > > Still need to get the Mirage list, which I have been waiting for for several months. > > @Jon. Do you want press coverage for XAPI 2? > Can talk to you on Thursdays > > Lars > ________________________________________ > From: Jonathan Ludlam > Sent: 10 June 2014 10:48 > To: xen-api@lists.xen.org; mirageos-devel@lists.xenproject.org > Cc: Lars Kurth > Subject: Xapi project repositories > > Hi all, > > In preparing for the 2.0 release, it's become increasingly obvious that > we really need to tidy up the xapi-project org on github. There are many > repositories that are in the org that aren't a part of the Xapi Project. > I started making a list, and realised that there are a few other > inconsistencies that we ought to clean up at the same time, for example, > many repositories are marked as forks of personal repos where that > relationship ought to be reversed. > > > > First, there are some repositories that should just be deleted: > > - opam > A fork of github.com/ocaml/opam. I don't know why we have this, it > doesn't appear to have any commits from us. > > - opam-repository > Same as opam. > > - xcp-fhs > This is unused by anyone, as far as I know. > > - xen-unstable-mirror > Just a mirror of the xen project repository. > > - xcp-storage-managers > An old fork. sm.git should be used instead. > > - ocaml-sha > A fork of upstream, no additional changesets from us. > > - ocaml-tar > A fork of upstream, no additional changesets from us > > - ocaml-vhd > A fork of upstream, no additional changesets from us > > > > Secondly, I believe some of the repositories should be transferred to > the 'xenserver' organisation, which I think probably needs approval, as > the xenserver org is not a part of the Linux Foundation. These are: > > - filesystem-summarise > A tool to check for filesystem changes. Useful on XenServer for > detecting when changes have been made to configuration files and so on. > Not useful for general installations of the xapi project. > > - jiralib > An old python library for talking to jira. Superseded by jira-python > package. > > - mirrortest > A test repository for checking Citrix's internal mirrors of the github > repositories. > > - PRDup > 'Pull Request Duplicator', a tool for helping to backport pull requests > to different branches. > > - pull-request-manager > Uses Citrix's internal build system to test pull requests - no longer used. > > - xs-pull-request-build-scripts > Replacement for pull-request-manager - uses Citrix's internal build > system to test pull requests, this time using jenkins. > > - xen-api-libs-specs > Spec files used for building a lot of the xapi-project components for > XenServer. There is large overlap with github.com/xenserver/buildroot - > these should probably merge (or become more closely related). > > - xen-api-backports > Similar to xen-api-libs-specs, but for Citrix's internal 'old > buildsystem' as opposed to Citrix's internal 'newer buildsystem'. > > I don't think any of these is actually contentious - they probably > should never have been part of the Linux Foundation, and have been there > since we only had the one place on github to put things! > > > > Third, we have some libraries that are actually mirage core libraries. > These should transfer over to the mirage organisation (remaining in LF, > as mirage is a Xen Project subproject like xapi): > > - ocaml-gnt > OCaml grant table manipulation. This code originated in the mirage > project and was put here when it was split out of mirage-platform (see > here: > https://github.com/mirage/mirage-platform/commit/f532fc79af41e0e39b624a8e63dffc900bf1b7e4). > > - ocaml-xenstore > This is the mirage implementation of a xenstore client library. Required > for running mirage kernels on xen. We use the unix-flavour of this > library. It also contains a WIP new version of the guts of a xenstore > daemon, which will be a mirage-style unix process _or_ unikernel > (xenstore stub-domain!) that should eventually be upstreamed into xen. > > - ocaml-xenstore-clients > Slightly oddly named library that defines the unix transport mechanisms > (unix-domain sockets) for using the ocaml-xenstore library. This is the > unix counterpart to the internal shared-page mechanism used by mirage > unikernels. > > - ocaml-evtchn > Similar to ocaml-gnt - split from the main mirage code at around the > same time as ocaml-gnt. > > - ocaml-xenstore-xen > Unused by xapi-project. I believe in here lives the code that turns the > xenstore daemon library from ocaml-xenstore into the actual xenstored > stubdomain or process. > > > > We have a few repositories that are forks of upstream repos with some of > our own changes in. We should get these changes upstreamed at some > point, but for now we should leave them there, but recognise that these > aren't necessarily part of the official Xapi Project (excepting where > they are, e.g. ocaml-xen-lowlevel-libs, which is a staging area for > upstreaming back into xen.git!) > - oclock > - ocamltest > - ocaml-xen-lowlevel-libs > - python-github2 > > > > Then there are generic ocaml libraries which could be used by other > ocaml programs. I think these can live on in the xapi project > organisation for now, but I wouldn't class them as 'core' xapi-project > repos. > > - cdrom > - netdev > - ocamldoc-json > - ocaml-encodings > - ocaml-crc > - ocaml-fd-send-recv > - ocaml-netlink > - ocaml-opasswd > - ocaml-pci-db > - ocaml-qmp > - stdext > - stunnel > - nbd > > > > > Which leaves us with the 'core' xapi project repositories: > > - blktap > - blktap-dkms > - example-ocaml-daemon > - ffs > - forkexecd > - libvhd > - message-switch > - ocaml-rrdd-plugins > - opam-repo-dev > - rrd-transport > - rrdd-plugin-legacy > - rrddump > - sm > - sm-cli > - squeezed > - tapctl > - vhd-tool > - vncproxy > - vncterm > - vxs > - wsproxy > - xapi-codegen > - xapi-libvirt-storage > - xapi-project > - xcp-eliloader > - xcp-guest-templates > - xcp-idl > - xcp-inventory > - xcp-networkd > - xcp-rrd > - xcp-rrdd > - xen-api > - xen-api-client > - xen-api-libs > - xen-api-libs-transitional > - xen-api-sdk > - xenops > - xenops-cli > - xenopsd > > Of the above lists that will remain in the xapi project, these > repositories have incorrect forking status (they are marked as forks of > someone here at Citrix, but shouldn't be): > > Forked from me (jonludlam on github): > xen-api-libs-transitional > xen-api-client > xcp-guest-templates > xcp-eliloader > wsproxy > tapctl > libvhd > blktap-dkms > netdev > nbd > cdrom > > Forked from Dave Scott (djs55) > xcp-idl > vhd-tool > ffs > ocaml-vhd > ocaml-tar > ocaml-fd-send-recv > > Forked from Simon Beaumont (simonjbeaumont): > ocaml-pci-db > > Forked from Mike McClurg (mcclurmc): > ocaml-opasswd > > These forking relationship problems need to be fixed by the people who > own the upstream repo. I don't think it's quite as simple as clicking > the 'transfer repository' button. If anyone knows the exact procedure > for doing this, could they please reply? > > > In summary, I believe we need to: > 1) delete some repositories > 2) move some repositories to xenserver > 3) move some repositories to mirage-project > 4) transfer ownership of some repositories (just flip around the > direction of the fork). > 5) document all of this on the wiki! > > Any comments? > > Jon > > > > > > _______________________________________________ > Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api _______________________________________________ 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 Jun 12 20:38:51 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 12 Jun 2014 20:38: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 1WvBll-00037c-M5; Thu, 12 Jun 2014 20:38:45 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WvBlk-000370-4a for mirageos-devel@lists.xenproject.org; Thu, 12 Jun 2014 20:38:44 +0000 Received: from [85.158.139.211:2149] by server-3.bemta-5.messagelabs.com id 44/1E-01676-2DF0A935; Thu, 12 Jun 2014 20:38:42 +0000 X-Env-Sender: scott.dj@gmail.com X-Msg-Ref: server-13.tower-206.messagelabs.com!1402605519!9694172!1 X-Originating-IP: [209.85.160.47] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 32266 invoked from network); 12 Jun 2014 20:38:41 -0000 Received: from mail-pb0-f47.google.com (HELO mail-pb0-f47.google.com) (209.85.160.47) by server-13.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 12 Jun 2014 20:38:41 -0000 Received: by mail-pb0-f47.google.com with SMTP id un15so1383322pbc.6 for ; Thu, 12 Jun 2014 13:38:39 -0700 (PDT) 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=reUCbjGx2z9+gKVxwXSJjDR/Y0CPbp7lDA3hwjyF+Fo=; b=dwA4sZ2KD4JW2I4flNLluSkbGyPVgvOCTUVbPrQfTSLXIK6WJ2ii1Fnkq9VdUqpypC Hf96VHDBY3VYjKnTnradkxQ9SQ6XFbfSvKlv3XrSe/VOVZK6ZFbB4kMqdAr4a6FD600/ 2V2unSPxpsC3gCvrqE/JHdO2SAtKTdq41zXRNx+ywuR9+pgApbJSRgtToZMgfYsG5v2o kOigBa5X4kaV0OYafUYgkrd02D7oEew+DWSlL8qdNKhGr99NwXcXN9CQA0IQND7PHYHn fSQdQ4uTX4EF1LhV0DdofzasIl9U8kM7JrvnqFK5BHkzkugJ33g0oOYQURDXk9dqeS1T +1jQ== MIME-Version: 1.0 X-Received: by 10.68.220.103 with SMTP id pv7mr15490796pbc.17.1402605519234; Thu, 12 Jun 2014 13:38:39 -0700 (PDT) Received: by 10.70.11.65 with HTTP; Thu, 12 Jun 2014 13:38:39 -0700 (PDT) Date: Thu, 12 Jun 2014 21:38:39 +0100 Message-ID: From: David Scott To: "mirageos-devel@lists.xenproject.org" Subject: [MirageOS-devel] towards a common Mirage 'FLOW' signature X-BeenThere: mirageos-devel@lists.xenproject.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="===============2822653269403246758==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============2822653269403246758== Content-Type: multipart/alternative; boundary=e89a8ff25378bbef1f04fba98bf9 --e89a8ff25378bbef1f04fba98bf9 Content-Type: text/plain; charset=UTF-8 Hi, I'd like to create a common Mirage 'FLOW' signature to represent reading and writing along some kind of 'connection'. I think we could satisfy the signature in multiple places including at least * consoles * xen inter-domain vchan connections * plain TCP * (hopefully) TLS connections It would be nice to write clients and servers which would work over multiple FLOW implementations. For discussion I've extracted the 'FLOW' from 'TCPv4' to show you what it would look like: https://github.com/djs55/mirage/commit/87f9855f22f997264870f903c998b1d92186fdef In V2 of the API I'd like to turn the CONSOLE signature into a combination of DEVICE and FLOW. I notice the low-level network APIs (NETWORK, ETHIF, ...) are *almost* like this except they have a function like val listen: t -> udp:callback -> tcp:callback -> ... Perhaps later (V2, V3?) we could split this into something like a val read: t -> buffer (* satisfy FLOW *) val classify: buffer -> [ `UDP; `TCP ] -- is that a good idea? Thoughts welcome! Cheers, -- Dave Scott --e89a8ff25378bbef1f04fba98bf9 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi,

I'd like to create a common Mir= age 'FLOW' signature to represent reading and writing along some ki= nd of 'connection'. I think we could satisfy the signature in multi= ple places including at least

* consoles
* xen inter-domain vchan connectio= ns
* plain TCP
* (hopefully) TLS connections

It would be nice to write clients and servers which would= work over multiple FLOW implementations.

For discussion I've extracted the 'FLOW' fr= om 'TCPv4' to show you what it would look like:


In V2 of the API I'd like to turn the CONSOLE= signature into a combination of DEVICE and FLOW.

= I notice the low-level network APIs (NETWORK, ETHIF, ...) are *almost* like= this except they have a function like

val listen: t -> udp:callback -> tcp:callback -&g= t; ...=C2=A0

Perhaps later (V2, V3?) we could spli= t this into something like a=C2=A0

val read: t -&g= t; buffer (* satisfy FLOW *)
val classify: buffer -> [ `UDP; `TCP ]

-- = is that a good idea?

Thoughts welcome!
<= br>
Cheers,
--
Dave Scott
--e89a8ff25378bbef1f04fba98bf9-- --===============2822653269403246758== 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 --===============2822653269403246758==-- From mirageos-devel-bounces@lists.xenproject.org Thu Jun 12 20:38:51 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 12 Jun 2014 20:38: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 1WvBll-00037c-M5; Thu, 12 Jun 2014 20:38:45 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WvBlk-000370-4a for mirageos-devel@lists.xenproject.org; Thu, 12 Jun 2014 20:38:44 +0000 Received: from [85.158.139.211:2149] by server-3.bemta-5.messagelabs.com id 44/1E-01676-2DF0A935; Thu, 12 Jun 2014 20:38:42 +0000 X-Env-Sender: scott.dj@gmail.com X-Msg-Ref: server-13.tower-206.messagelabs.com!1402605519!9694172!1 X-Originating-IP: [209.85.160.47] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 32266 invoked from network); 12 Jun 2014 20:38:41 -0000 Received: from mail-pb0-f47.google.com (HELO mail-pb0-f47.google.com) (209.85.160.47) by server-13.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 12 Jun 2014 20:38:41 -0000 Received: by mail-pb0-f47.google.com with SMTP id un15so1383322pbc.6 for ; Thu, 12 Jun 2014 13:38:39 -0700 (PDT) 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=reUCbjGx2z9+gKVxwXSJjDR/Y0CPbp7lDA3hwjyF+Fo=; b=dwA4sZ2KD4JW2I4flNLluSkbGyPVgvOCTUVbPrQfTSLXIK6WJ2ii1Fnkq9VdUqpypC Hf96VHDBY3VYjKnTnradkxQ9SQ6XFbfSvKlv3XrSe/VOVZK6ZFbB4kMqdAr4a6FD600/ 2V2unSPxpsC3gCvrqE/JHdO2SAtKTdq41zXRNx+ywuR9+pgApbJSRgtToZMgfYsG5v2o kOigBa5X4kaV0OYafUYgkrd02D7oEew+DWSlL8qdNKhGr99NwXcXN9CQA0IQND7PHYHn fSQdQ4uTX4EF1LhV0DdofzasIl9U8kM7JrvnqFK5BHkzkugJ33g0oOYQURDXk9dqeS1T +1jQ== MIME-Version: 1.0 X-Received: by 10.68.220.103 with SMTP id pv7mr15490796pbc.17.1402605519234; Thu, 12 Jun 2014 13:38:39 -0700 (PDT) Received: by 10.70.11.65 with HTTP; Thu, 12 Jun 2014 13:38:39 -0700 (PDT) Date: Thu, 12 Jun 2014 21:38:39 +0100 Message-ID: From: David Scott To: "mirageos-devel@lists.xenproject.org" Subject: [MirageOS-devel] towards a common Mirage 'FLOW' signature X-BeenThere: mirageos-devel@lists.xenproject.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="===============2822653269403246758==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============2822653269403246758== Content-Type: multipart/alternative; boundary=e89a8ff25378bbef1f04fba98bf9 --e89a8ff25378bbef1f04fba98bf9 Content-Type: text/plain; charset=UTF-8 Hi, I'd like to create a common Mirage 'FLOW' signature to represent reading and writing along some kind of 'connection'. I think we could satisfy the signature in multiple places including at least * consoles * xen inter-domain vchan connections * plain TCP * (hopefully) TLS connections It would be nice to write clients and servers which would work over multiple FLOW implementations. For discussion I've extracted the 'FLOW' from 'TCPv4' to show you what it would look like: https://github.com/djs55/mirage/commit/87f9855f22f997264870f903c998b1d92186fdef In V2 of the API I'd like to turn the CONSOLE signature into a combination of DEVICE and FLOW. I notice the low-level network APIs (NETWORK, ETHIF, ...) are *almost* like this except they have a function like val listen: t -> udp:callback -> tcp:callback -> ... Perhaps later (V2, V3?) we could split this into something like a val read: t -> buffer (* satisfy FLOW *) val classify: buffer -> [ `UDP; `TCP ] -- is that a good idea? Thoughts welcome! Cheers, -- Dave Scott --e89a8ff25378bbef1f04fba98bf9 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi,

I'd like to create a common Mir= age 'FLOW' signature to represent reading and writing along some ki= nd of 'connection'. I think we could satisfy the signature in multi= ple places including at least

* consoles
* xen inter-domain vchan connectio= ns
* plain TCP
* (hopefully) TLS connections

It would be nice to write clients and servers which would= work over multiple FLOW implementations.

For discussion I've extracted the 'FLOW' fr= om 'TCPv4' to show you what it would look like:


In V2 of the API I'd like to turn the CONSOLE= signature into a combination of DEVICE and FLOW.

= I notice the low-level network APIs (NETWORK, ETHIF, ...) are *almost* like= this except they have a function like

val listen: t -> udp:callback -> tcp:callback -&g= t; ...=C2=A0

Perhaps later (V2, V3?) we could spli= t this into something like a=C2=A0

val read: t -&g= t; buffer (* satisfy FLOW *)
val classify: buffer -> [ `UDP; `TCP ]

-- = is that a good idea?

Thoughts welcome!
<= br>
Cheers,
--
Dave Scott
--e89a8ff25378bbef1f04fba98bf9-- --===============2822653269403246758== 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 --===============2822653269403246758==-- From mirageos-devel-bounces@lists.xenproject.org Fri Jun 13 07:33:48 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 13 Jun 2014 07:33: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 1WvLzd-000683-4f; Fri, 13 Jun 2014 07:33:45 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WvLzb-00067y-Pm for mirageos-devel@lists.xenproject.org; Fri, 13 Jun 2014 07:33:44 +0000 Received: from [85.158.143.35:23582] by server-1.bemta-4.messagelabs.com id 62/6C-09853-759AA935; Fri, 13 Jun 2014 07:33:43 +0000 X-Env-Sender: buzzheavyyear@hotmail.com X-Msg-Ref: server-15.tower-21.messagelabs.com!1402644821!11082829!1 X-Originating-IP: [157.55.2.77] X-SpamReason: No, hits=1.3 required=7.0 tests=FORGED_HOTMAIL_RCVD, HTML_20_30,HTML_MESSAGE,MAILTO_TO_SPAM_ADDR,ML_RADAR_SPEW_LINKS_1, ML_RADAR_SPEW_LINKS_12,ML_RADAR_SPEW_LINKS_14,ML_RADAR_SPEW_LINKS_2, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17375 invoked from network); 13 Jun 2014 07:33:41 -0000 Received: from dub004-omc4s2.hotmail.com (HELO DUB004-OMC4S2.hotmail.com) (157.55.2.77) by server-15.tower-21.messagelabs.com with AES128-SHA encrypted SMTP; 13 Jun 2014 07:33:41 -0000 Received: from DUB128-W2 ([157.55.2.73]) by DUB004-OMC4S2.hotmail.com with Microsoft SMTPSVC(7.5.7601.22701); Fri, 13 Jun 2014 00:33:41 -0700 X-TMN: [VzP2QBX2qumFAS8JQ4uhUZ8pAPyp2lXg] X-Originating-Email: [buzzheavyyear@hotmail.com] Message-ID: From: buzz heavyyear To: Anil Madhavapeddy , David Scott Date: Fri, 13 Jun 2014 07:33:41 +0000 Importance: Normal In-Reply-To: References: , <0846576A-E0E8-4F35-99FA-6729250975B5@recoil.org>, <5373900A.4030901@cam.ac.uk>, <9AF01405-3475-4FC7-A308-4075DE335BEF@recoil.org>, <53739693.2050308@cam.ac.uk>, <0E252CC1-CF37-4611-B633-D427E2051B7D@recoil.org>, , MIME-Version: 1.0 X-OriginalArrivalTime: 13 Jun 2014 07:33:41.0438 (UTC) FILETIME=[CC85CDE0:01CF86D9] Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Monitoring MirageOS guests on CubieBoard2 X-BeenThere: mirageos-devel@lists.xenproject.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="===============6533086079037100243==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============6533086079037100243== Content-Type: multipart/alternative; boundary="_4b81852f-5dfc-46bd-bbc2-bd1115139e9e_" --_4b81852f-5dfc-46bd-bbc2-bd1115139e9e_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Just a quick question to find out if RRD will make it into MirageOS 2.0=2C = especially for the ARM Cubieboard platform? Cheers Nick > From: anil@recoil.org > Date: Thu=2C 15 May 2014 11:21:18 +0100 > To: Dave.Scott@citrix.com > CC: mirageos-devel@lists.xenproject.org > Subject: Re: [MirageOS-devel] Monitoring MirageOS guests on CubieBoard2 >=20 > On 14 May 2014=2C at 17:41=2C Dave Scott wrote: >=20 > >=20 > > On 14 May 2014=2C at 17:21=2C Anil Madhavapeddy wrote= : > >=20 > >> On 14 May 2014=2C at 17:15=2C Jon Ludlam wrote: > >>=20 > >>> On 14/05/14 16:55=2C Anil Madhavapeddy wrote: > >>>> On 14 May 2014=2C at 16:47=2C Jon Ludlam wrote: > >>>>>> On 14/05/14 15:06=2C Anil Madhavapeddy wrote: > >>>>>>> On 14 May 2014=2C at 14:01=2C buzz heavyyear wrote: > >>>>>>>=20 > >>>>>>> Now that I'm having a lot of fun getting up to speed with ocaml= =2C xen=2C mirage=2C writing ocaml guests and getting them to run on the Cu= bieboard=2C what I really need is to see how they are performing as they ar= e running. > >>>>>>>=20 > >>>>>>> XAPI/XCP has rrd. Am I right in thinking that a good way forward = is to includegithub.com/xapi-project/xcp-rrd during the build process? > >>>>>>>=20 > >>>>>>> Perhaps there's an easier way? Any thoughts anyone? > >>>>>> RRD is definitely the right direction for dom0 to track guest acti= vity=2C but we do need to get vchan up to speed from the guest side. Dave= =2C Jon=2C what's the current state of ocaml-vchan? I'm happy to add a Coh= ttp functor for it if there's something vaguely resembling a FLOW interface= (right now=2C it's fairly low level). > >>>>> I believe the state is 'I saw it work once recently'. There's nothi= ng > >>>>> really resembling a flow interface=2C but I'm sure one could be ass= embled > >>>>> fairly easily. > >>>> Thanks=2C is there a working unit test domain anywhere? If we're go= ing to depend on vchan=2C it's time to get the low level bits well tested. = The atomic bit ops particularly worrisome=2C and we are likely to be the fi= rst ARM vchan user (so let's get the x86 bugs sorted first :-) > >>>>=20 > >>>> Anil > >>>>=20 > >>>>=20 > >>> What I was using to test was the vchan client from the xen repository= . > >>> I'll have another look at it tomorrow if you like? > >>=20 > >> Ah yes=2C I keep forgetting about those binaries from the Xen repo -- = are they installed by distros these days? (so we have a netcat-like vchan c= lient). > >=20 > > Good question. I need to take a look at vchan again=2C to see if it mak= es sense to plumb a vchan link through to guests from the dom0 toolstack fo= r off-box cloud orchestration layers to talk to their service VMs without u= sing ssh. Perhaps little Mirage HTTP <-> vchan service would work nicely. >=20 > That would certainly cure the 'RPC through xenstore' malaise that afflict= s everyone who has this problem. >=20 > More broadly=2C making vchan available with a convenient netcat-command-l= ine interface would generally make interfacing with guests much more pleasa= nt. >=20 > I notice that Arjun Guha has just started an OCaml Docker binding which w= ill give us the same benefits using LXC=2C so making these interfaces simil= ar for Xen would be very handy. > https://github.com/arjunguha/ocaml-docker >=20 > -anil > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel = --_4b81852f-5dfc-46bd-bbc2-bd1115139e9e_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Just a quick question to find ou= t if RRD will make it into MirageOS 2.0=2C especially for the ARM Cubieboar= d platform?

Cheers
Nick

>=3B From: anil@recoil.org<= br>>=3B Date: Thu=2C 15 May 2014 11:21:18 +0100
>=3B To: Dave.Scott@= citrix.com
>=3B CC: mirageos-devel@lists.xenproject.org
>=3B Subj= ect: Re: [MirageOS-devel] Monitoring MirageOS guests on CubieBoard2
>= =3B
>=3B On 14 May 2014=2C at 17:41=2C Dave Scott <=3BDave.Scott@ci= trix.com>=3B wrote:
>=3B
>=3B >=3B
>=3B >=3B On 14 M= ay 2014=2C at 17:21=2C Anil Madhavapeddy <=3Banil@recoil.org>=3B wrote:=
>=3B >=3B
>=3B >=3B>=3B On 14 May 2014=2C at 17:15=2C Jon= Ludlam <=3Bjjl25@cam.ac.uk>=3B wrote:
>=3B >=3B>=3B
>= =3B >=3B>=3B>=3B On 14/05/14 16:55=2C Anil Madhavapeddy wrote:
>= =3B >=3B>=3B>=3B>=3B On 14 May 2014=2C at 16:47=2C Jon Ludlam <= =3Bjjl25@cam.ac.uk>=3B wrote:
>=3B >=3B>=3B>=3B>=3B>=3B>= =3B On 14/05/14 15:06=2C Anil Madhavapeddy wrote:
>=3B >=3B>=3B>= =3B>=3B>=3B>=3B>=3B On 14 May 2014=2C at 14:01=2C buzz heavyyear &l= t=3Bbuzzheavyyear@hotmail.com>=3B wrote:
>=3B >=3B>=3B>=3B>= =3B>=3B>=3B>=3B
>=3B >=3B>=3B>=3B>=3B>=3B>=3B>=3B= Now that I'm having a lot of fun getting up to speed with ocaml=2C xen=2C = mirage=2C writing ocaml guests and getting them to run on the Cubieboard=2C= what I really need is to see how they are performing as they are running.<= br>>=3B >=3B>=3B>=3B>=3B>=3B>=3B>=3B
>=3B >=3B>= =3B>=3B>=3B>=3B>=3B>=3B XAPI/XCP has rrd. Am I right in thinking = that a good way forward is to includegithub.com/xapi-project/xcp-rrd during= the build process?
>=3B >=3B>=3B>=3B>=3B>=3B>=3B>=3B >=3B >=3B>=3B>=3B>=3B>=3B>=3B>=3B Perhaps there's an easi= er way? Any thoughts anyone?
>=3B >=3B>=3B>=3B>=3B>=3B>=3B= RRD is definitely the right direction for dom0 to track guest activity=2C = but we do need to get vchan up to speed from the guest side. Dave=2C Jon= =2C what's the current state of ocaml-vchan? I'm happy to add a Cohttp fun= ctor for it if there's something vaguely resembling a FLOW interface (right= now=2C it's fairly low level).
>=3B >=3B>=3B>=3B>=3B>=3B I = believe the state is 'I saw it work once recently'. There's nothing
>= =3B >=3B>=3B>=3B>=3B>=3B really resembling a flow interface=2C bu= t I'm sure one could be assembled
>=3B >=3B>=3B>=3B>=3B>=3B = fairly easily.
>=3B >=3B>=3B>=3B>=3B Thanks=2C is there a work= ing unit test domain anywhere? If we're going to depend on vchan=2C it's t= ime to get the low level bits well tested. The atomic bit ops particularly = worrisome=2C and we are likely to be the first ARM vchan user (so let's get= the x86 bugs sorted first :-)
>=3B >=3B>=3B>=3B>=3B
>= =3B >=3B>=3B>=3B>=3B Anil
>=3B >=3B>=3B>=3B>=3B
&g= t=3B >=3B>=3B>=3B>=3B
>=3B >=3B>=3B>=3B What I was usin= g to test was the vchan client from the xen repository.
>=3B >=3B>= =3B>=3B I'll have another look at it tomorrow if you like?
>=3B >= =3B>=3B
>=3B >=3B>=3B Ah yes=2C I keep forgetting about those b= inaries from the Xen repo -- are they installed by distros these days? (so = we have a netcat-like vchan client).
>=3B >=3B
>=3B >=3B Goo= d question. I need to take a look at vchan again=2C to see if it makes sens= e to plumb a vchan link through to guests from the dom0 toolstack for off-b= ox cloud orchestration layers to talk to their service VMs without using ss= h. Perhaps little Mirage HTTP <=3B->=3B vchan service would work nicely= .
>=3B
>=3B That would certainly cure the 'RPC through xenstore'= malaise that afflicts everyone who has this problem.
>=3B
>=3B = More broadly=2C making vchan available with a convenient netcat-command-lin= e interface would generally make interfacing with guests much more pleasant= .
>=3B
>=3B I notice that Arjun Guha has just started an OCaml D= ocker binding which will give us the same benefits using LXC=2C so making t= hese interfaces similar for Xen would be very handy.
>=3B https://gith= ub.com/arjunguha/ocaml-docker
>=3B
>=3B -anil
>=3B ________= _______________________________________
>=3B MirageOS-devel mailing li= st
>=3B MirageOS-devel@lists.xenproject.org
>=3B http://lists.xen= project.org/cgi-bin/mailman/listinfo/mirageos-devel
= --_4b81852f-5dfc-46bd-bbc2-bd1115139e9e_-- --===============6533086079037100243== 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 --===============6533086079037100243==-- From mirageos-devel-bounces@lists.xenproject.org Fri Jun 13 07:33:48 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 13 Jun 2014 07:33: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 1WvLzd-000683-4f; Fri, 13 Jun 2014 07:33:45 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WvLzb-00067y-Pm for mirageos-devel@lists.xenproject.org; Fri, 13 Jun 2014 07:33:44 +0000 Received: from [85.158.143.35:23582] by server-1.bemta-4.messagelabs.com id 62/6C-09853-759AA935; Fri, 13 Jun 2014 07:33:43 +0000 X-Env-Sender: buzzheavyyear@hotmail.com X-Msg-Ref: server-15.tower-21.messagelabs.com!1402644821!11082829!1 X-Originating-IP: [157.55.2.77] X-SpamReason: No, hits=1.3 required=7.0 tests=FORGED_HOTMAIL_RCVD, HTML_20_30,HTML_MESSAGE,MAILTO_TO_SPAM_ADDR,ML_RADAR_SPEW_LINKS_1, ML_RADAR_SPEW_LINKS_12,ML_RADAR_SPEW_LINKS_14,ML_RADAR_SPEW_LINKS_2, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17375 invoked from network); 13 Jun 2014 07:33:41 -0000 Received: from dub004-omc4s2.hotmail.com (HELO DUB004-OMC4S2.hotmail.com) (157.55.2.77) by server-15.tower-21.messagelabs.com with AES128-SHA encrypted SMTP; 13 Jun 2014 07:33:41 -0000 Received: from DUB128-W2 ([157.55.2.73]) by DUB004-OMC4S2.hotmail.com with Microsoft SMTPSVC(7.5.7601.22701); Fri, 13 Jun 2014 00:33:41 -0700 X-TMN: [VzP2QBX2qumFAS8JQ4uhUZ8pAPyp2lXg] X-Originating-Email: [buzzheavyyear@hotmail.com] Message-ID: From: buzz heavyyear To: Anil Madhavapeddy , David Scott Date: Fri, 13 Jun 2014 07:33:41 +0000 Importance: Normal In-Reply-To: References: , <0846576A-E0E8-4F35-99FA-6729250975B5@recoil.org>, <5373900A.4030901@cam.ac.uk>, <9AF01405-3475-4FC7-A308-4075DE335BEF@recoil.org>, <53739693.2050308@cam.ac.uk>, <0E252CC1-CF37-4611-B633-D427E2051B7D@recoil.org>, , MIME-Version: 1.0 X-OriginalArrivalTime: 13 Jun 2014 07:33:41.0438 (UTC) FILETIME=[CC85CDE0:01CF86D9] Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Monitoring MirageOS guests on CubieBoard2 X-BeenThere: mirageos-devel@lists.xenproject.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="===============6533086079037100243==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============6533086079037100243== Content-Type: multipart/alternative; boundary="_4b81852f-5dfc-46bd-bbc2-bd1115139e9e_" --_4b81852f-5dfc-46bd-bbc2-bd1115139e9e_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Just a quick question to find out if RRD will make it into MirageOS 2.0=2C = especially for the ARM Cubieboard platform? Cheers Nick > From: anil@recoil.org > Date: Thu=2C 15 May 2014 11:21:18 +0100 > To: Dave.Scott@citrix.com > CC: mirageos-devel@lists.xenproject.org > Subject: Re: [MirageOS-devel] Monitoring MirageOS guests on CubieBoard2 >=20 > On 14 May 2014=2C at 17:41=2C Dave Scott wrote: >=20 > >=20 > > On 14 May 2014=2C at 17:21=2C Anil Madhavapeddy wrote= : > >=20 > >> On 14 May 2014=2C at 17:15=2C Jon Ludlam wrote: > >>=20 > >>> On 14/05/14 16:55=2C Anil Madhavapeddy wrote: > >>>> On 14 May 2014=2C at 16:47=2C Jon Ludlam wrote: > >>>>>> On 14/05/14 15:06=2C Anil Madhavapeddy wrote: > >>>>>>> On 14 May 2014=2C at 14:01=2C buzz heavyyear wrote: > >>>>>>>=20 > >>>>>>> Now that I'm having a lot of fun getting up to speed with ocaml= =2C xen=2C mirage=2C writing ocaml guests and getting them to run on the Cu= bieboard=2C what I really need is to see how they are performing as they ar= e running. > >>>>>>>=20 > >>>>>>> XAPI/XCP has rrd. Am I right in thinking that a good way forward = is to includegithub.com/xapi-project/xcp-rrd during the build process? > >>>>>>>=20 > >>>>>>> Perhaps there's an easier way? Any thoughts anyone? > >>>>>> RRD is definitely the right direction for dom0 to track guest acti= vity=2C but we do need to get vchan up to speed from the guest side. Dave= =2C Jon=2C what's the current state of ocaml-vchan? I'm happy to add a Coh= ttp functor for it if there's something vaguely resembling a FLOW interface= (right now=2C it's fairly low level). > >>>>> I believe the state is 'I saw it work once recently'. There's nothi= ng > >>>>> really resembling a flow interface=2C but I'm sure one could be ass= embled > >>>>> fairly easily. > >>>> Thanks=2C is there a working unit test domain anywhere? If we're go= ing to depend on vchan=2C it's time to get the low level bits well tested. = The atomic bit ops particularly worrisome=2C and we are likely to be the fi= rst ARM vchan user (so let's get the x86 bugs sorted first :-) > >>>>=20 > >>>> Anil > >>>>=20 > >>>>=20 > >>> What I was using to test was the vchan client from the xen repository= . > >>> I'll have another look at it tomorrow if you like? > >>=20 > >> Ah yes=2C I keep forgetting about those binaries from the Xen repo -- = are they installed by distros these days? (so we have a netcat-like vchan c= lient). > >=20 > > Good question. I need to take a look at vchan again=2C to see if it mak= es sense to plumb a vchan link through to guests from the dom0 toolstack fo= r off-box cloud orchestration layers to talk to their service VMs without u= sing ssh. Perhaps little Mirage HTTP <-> vchan service would work nicely. >=20 > That would certainly cure the 'RPC through xenstore' malaise that afflict= s everyone who has this problem. >=20 > More broadly=2C making vchan available with a convenient netcat-command-l= ine interface would generally make interfacing with guests much more pleasa= nt. >=20 > I notice that Arjun Guha has just started an OCaml Docker binding which w= ill give us the same benefits using LXC=2C so making these interfaces simil= ar for Xen would be very handy. > https://github.com/arjunguha/ocaml-docker >=20 > -anil > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel = --_4b81852f-5dfc-46bd-bbc2-bd1115139e9e_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Just a quick question to find ou= t if RRD will make it into MirageOS 2.0=2C especially for the ARM Cubieboar= d platform?

Cheers
Nick

>=3B From: anil@recoil.org<= br>>=3B Date: Thu=2C 15 May 2014 11:21:18 +0100
>=3B To: Dave.Scott@= citrix.com
>=3B CC: mirageos-devel@lists.xenproject.org
>=3B Subj= ect: Re: [MirageOS-devel] Monitoring MirageOS guests on CubieBoard2
>= =3B
>=3B On 14 May 2014=2C at 17:41=2C Dave Scott <=3BDave.Scott@ci= trix.com>=3B wrote:
>=3B
>=3B >=3B
>=3B >=3B On 14 M= ay 2014=2C at 17:21=2C Anil Madhavapeddy <=3Banil@recoil.org>=3B wrote:=
>=3B >=3B
>=3B >=3B>=3B On 14 May 2014=2C at 17:15=2C Jon= Ludlam <=3Bjjl25@cam.ac.uk>=3B wrote:
>=3B >=3B>=3B
>= =3B >=3B>=3B>=3B On 14/05/14 16:55=2C Anil Madhavapeddy wrote:
>= =3B >=3B>=3B>=3B>=3B On 14 May 2014=2C at 16:47=2C Jon Ludlam <= =3Bjjl25@cam.ac.uk>=3B wrote:
>=3B >=3B>=3B>=3B>=3B>=3B>= =3B On 14/05/14 15:06=2C Anil Madhavapeddy wrote:
>=3B >=3B>=3B>= =3B>=3B>=3B>=3B>=3B On 14 May 2014=2C at 14:01=2C buzz heavyyear &l= t=3Bbuzzheavyyear@hotmail.com>=3B wrote:
>=3B >=3B>=3B>=3B>= =3B>=3B>=3B>=3B
>=3B >=3B>=3B>=3B>=3B>=3B>=3B>=3B= Now that I'm having a lot of fun getting up to speed with ocaml=2C xen=2C = mirage=2C writing ocaml guests and getting them to run on the Cubieboard=2C= what I really need is to see how they are performing as they are running.<= br>>=3B >=3B>=3B>=3B>=3B>=3B>=3B>=3B
>=3B >=3B>= =3B>=3B>=3B>=3B>=3B>=3B XAPI/XCP has rrd. Am I right in thinking = that a good way forward is to includegithub.com/xapi-project/xcp-rrd during= the build process?
>=3B >=3B>=3B>=3B>=3B>=3B>=3B>=3B >=3B >=3B>=3B>=3B>=3B>=3B>=3B>=3B Perhaps there's an easi= er way? Any thoughts anyone?
>=3B >=3B>=3B>=3B>=3B>=3B>=3B= RRD is definitely the right direction for dom0 to track guest activity=2C = but we do need to get vchan up to speed from the guest side. Dave=2C Jon= =2C what's the current state of ocaml-vchan? I'm happy to add a Cohttp fun= ctor for it if there's something vaguely resembling a FLOW interface (right= now=2C it's fairly low level).
>=3B >=3B>=3B>=3B>=3B>=3B I = believe the state is 'I saw it work once recently'. There's nothing
>= =3B >=3B>=3B>=3B>=3B>=3B really resembling a flow interface=2C bu= t I'm sure one could be assembled
>=3B >=3B>=3B>=3B>=3B>=3B = fairly easily.
>=3B >=3B>=3B>=3B>=3B Thanks=2C is there a work= ing unit test domain anywhere? If we're going to depend on vchan=2C it's t= ime to get the low level bits well tested. The atomic bit ops particularly = worrisome=2C and we are likely to be the first ARM vchan user (so let's get= the x86 bugs sorted first :-)
>=3B >=3B>=3B>=3B>=3B
>= =3B >=3B>=3B>=3B>=3B Anil
>=3B >=3B>=3B>=3B>=3B
&g= t=3B >=3B>=3B>=3B>=3B
>=3B >=3B>=3B>=3B What I was usin= g to test was the vchan client from the xen repository.
>=3B >=3B>= =3B>=3B I'll have another look at it tomorrow if you like?
>=3B >= =3B>=3B
>=3B >=3B>=3B Ah yes=2C I keep forgetting about those b= inaries from the Xen repo -- are they installed by distros these days? (so = we have a netcat-like vchan client).
>=3B >=3B
>=3B >=3B Goo= d question. I need to take a look at vchan again=2C to see if it makes sens= e to plumb a vchan link through to guests from the dom0 toolstack for off-b= ox cloud orchestration layers to talk to their service VMs without using ss= h. Perhaps little Mirage HTTP <=3B->=3B vchan service would work nicely= .
>=3B
>=3B That would certainly cure the 'RPC through xenstore'= malaise that afflicts everyone who has this problem.
>=3B
>=3B = More broadly=2C making vchan available with a convenient netcat-command-lin= e interface would generally make interfacing with guests much more pleasant= .
>=3B
>=3B I notice that Arjun Guha has just started an OCaml D= ocker binding which will give us the same benefits using LXC=2C so making t= hese interfaces similar for Xen would be very handy.
>=3B https://gith= ub.com/arjunguha/ocaml-docker
>=3B
>=3B -anil
>=3B ________= _______________________________________
>=3B MirageOS-devel mailing li= st
>=3B MirageOS-devel@lists.xenproject.org
>=3B http://lists.xen= project.org/cgi-bin/mailman/listinfo/mirageos-devel
= --_4b81852f-5dfc-46bd-bbc2-bd1115139e9e_-- --===============6533086079037100243== 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 --===============6533086079037100243==-- From mirageos-devel-bounces@lists.xenproject.org Fri Jun 13 09:09:51 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 13 Jun 2014 09:09: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 1WvNUZ-0007av-GJ; Fri, 13 Jun 2014 09:09:47 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WvNUX-0007aj-S6 for mirageos-devel@lists.xenproject.org; Fri, 13 Jun 2014 09:09:45 +0000 Received: from [85.158.143.35:41532] by server-3.bemta-4.messagelabs.com id 44/80-13602-9DFBA935; Fri, 13 Jun 2014 09:09:45 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-8.tower-21.messagelabs.com!1402650584!11131418!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21585 invoked from network); 13 Jun 2014 09:09:44 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-8.tower-21.messagelabs.com with SMTP; 13 Jun 2014 09:09:44 -0000 Received: (qmail 14806 invoked by uid 634); 13 Jun 2014 09:09:44 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net (HELO [192.168.1.62]) (86.30.244.239) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Fri, 13 Jun 2014 10:09:43 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\)) From: Anil Madhavapeddy In-Reply-To: Date: Fri, 13 Jun 2014 10:09:42 +0100 Message-Id: <39391660-83A7-46C0-AE53-3880A5A7A885@recoil.org> References: <297FC9DB-3A4E-41A5-B00E-9DEF62C625E6@recoil.org> To: Thomas Leonard X-Mailer: Apple Mail (2.1874) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Mirage on Xen/ARM status X-BeenThere: mirageos-devel@lists.xenproject.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 12 Jun 2014, at 15:46, Thomas Leonard wrote: >> >> The next step is to get networking working on ARM. > > This seems to be working now (I can telnet to port 80 and send it a > message), which it displays on the console. Fantastic!! > The main problem turned out to be ones_complement_checksum_bigarray, > which was doing unaligned double-word (64-bit) memory access. This > faults on ARM. For testing, I replaced it with the version in the unix > directory. Interesting -- they were meant to be exactly the same if I remember. Is there an actual code difference between the two aside from include headers? -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 Jun 13 09:09:51 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 13 Jun 2014 09:09: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 1WvNUZ-0007av-GJ; Fri, 13 Jun 2014 09:09:47 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WvNUX-0007aj-S6 for mirageos-devel@lists.xenproject.org; Fri, 13 Jun 2014 09:09:45 +0000 Received: from [85.158.143.35:41532] by server-3.bemta-4.messagelabs.com id 44/80-13602-9DFBA935; Fri, 13 Jun 2014 09:09:45 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-8.tower-21.messagelabs.com!1402650584!11131418!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21585 invoked from network); 13 Jun 2014 09:09:44 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-8.tower-21.messagelabs.com with SMTP; 13 Jun 2014 09:09:44 -0000 Received: (qmail 14806 invoked by uid 634); 13 Jun 2014 09:09:44 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net (HELO [192.168.1.62]) (86.30.244.239) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Fri, 13 Jun 2014 10:09:43 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\)) From: Anil Madhavapeddy In-Reply-To: Date: Fri, 13 Jun 2014 10:09:42 +0100 Message-Id: <39391660-83A7-46C0-AE53-3880A5A7A885@recoil.org> References: <297FC9DB-3A4E-41A5-B00E-9DEF62C625E6@recoil.org> To: Thomas Leonard X-Mailer: Apple Mail (2.1874) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Mirage on Xen/ARM status X-BeenThere: mirageos-devel@lists.xenproject.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 12 Jun 2014, at 15:46, Thomas Leonard wrote: >> >> The next step is to get networking working on ARM. > > This seems to be working now (I can telnet to port 80 and send it a > message), which it displays on the console. Fantastic!! > The main problem turned out to be ones_complement_checksum_bigarray, > which was doing unaligned double-word (64-bit) memory access. This > faults on ARM. For testing, I replaced it with the version in the unix > directory. Interesting -- they were meant to be exactly the same if I remember. Is there an actual code difference between the two aside from include headers? -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 Jun 13 09:15:51 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 13 Jun 2014 09:15: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 1WvNaR-0007nB-DW; Fri, 13 Jun 2014 09:15:51 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WvNaQ-0007n0-1m for mirageos-devel@lists.xenproject.org; Fri, 13 Jun 2014 09:15:50 +0000 Received: from [85.158.143.35:44737] by server-2.bemta-4.messagelabs.com id CF/CF-06539-541CA935; Fri, 13 Jun 2014 09:15:49 +0000 X-Env-Sender: talex5@gmail.com X-Msg-Ref: server-10.tower-21.messagelabs.com!1402650947!11138964!1 X-Originating-IP: [209.85.219.51] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, ML_RADAR_SPEW_LINKS_23,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20505 invoked from network); 13 Jun 2014 09:15:48 -0000 Received: from mail-oa0-f51.google.com (HELO mail-oa0-f51.google.com) (209.85.219.51) by server-10.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 13 Jun 2014 09:15:48 -0000 Received: by mail-oa0-f51.google.com with SMTP id j17so2524467oag.24 for ; Fri, 13 Jun 2014 02:15:47 -0700 (PDT) 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=jmLFLU0fXR93iUCzsjG8ex6U68Wk4vBTBDGkOmVSOCo=; b=HLUQMsAF0zkd2pWon4cckcjJfPCNsiXHdHuEQFjKiTS3k15T6BkLGu1UntQgqr1Y36 poMZ4WdKsO8SmdVphPC8iBjFN7WTNV/IkXxBFBx7gjIpgTzHPpSaCY7jqjO0wFY2IsNp vXJh2w5anRd+iFRsytZc5lHrHPOk1dRlDbcs/g7yKBj/9GeVH/k3kAcjGNOknqiylo3b w5glS+CHpso1tjl4rkef3pjy818W9jwSvpbXPUdnFTwiHPDC5g//9T0X0wB+ote1yfvT maQWmMgB50f4gCP0cJj0kXqLe7jc+YP6tWQDIfqNAso8SbrAoLuSyRS0ZQawjRl7AuLa Fijw== MIME-Version: 1.0 X-Received: by 10.60.103.78 with SMTP id fu14mr1352977oeb.21.1402650946890; Fri, 13 Jun 2014 02:15:46 -0700 (PDT) Received: by 10.76.92.5 with HTTP; Fri, 13 Jun 2014 02:15:46 -0700 (PDT) In-Reply-To: <39391660-83A7-46C0-AE53-3880A5A7A885@recoil.org> References: <297FC9DB-3A4E-41A5-B00E-9DEF62C625E6@recoil.org> <39391660-83A7-46C0-AE53-3880A5A7A885@recoil.org> Date: Fri, 13 Jun 2014 10:15:46 +0100 Message-ID: From: Thomas Leonard To: Anil Madhavapeddy Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Mirage on Xen/ARM status X-BeenThere: mirageos-devel@lists.xenproject.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 13 June 2014 10:09, Anil Madhavapeddy wrote: > On 12 Jun 2014, at 15:46, Thomas Leonard wrote: >>> >>> The next step is to get networking working on ARM. >> >> This seems to be working now (I can telnet to port 80 and send it a >> message), which it displays on the console. > > Fantastic!! > >> The main problem turned out to be ones_complement_checksum_bigarray, >> which was doing unaligned double-word (64-bit) memory access. This >> faults on ARM. For testing, I replaced it with the version in the unix >> directory. > > Interesting -- they were meant to be exactly the same if I remember. > Is there an actual code difference between the two aside from include > headers? They are very different. Looks like one got optimised without the other here: https://github.com/mirage/mirage-platform/commit/6fc97d77d0846bc7f17bd0702832ea1faa8a7e71 -- 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 Fri Jun 13 09:15:51 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 13 Jun 2014 09:15: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 1WvNaR-0007nB-DW; Fri, 13 Jun 2014 09:15:51 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WvNaQ-0007n0-1m for mirageos-devel@lists.xenproject.org; Fri, 13 Jun 2014 09:15:50 +0000 Received: from [85.158.143.35:44737] by server-2.bemta-4.messagelabs.com id CF/CF-06539-541CA935; Fri, 13 Jun 2014 09:15:49 +0000 X-Env-Sender: talex5@gmail.com X-Msg-Ref: server-10.tower-21.messagelabs.com!1402650947!11138964!1 X-Originating-IP: [209.85.219.51] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, ML_RADAR_SPEW_LINKS_23,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20505 invoked from network); 13 Jun 2014 09:15:48 -0000 Received: from mail-oa0-f51.google.com (HELO mail-oa0-f51.google.com) (209.85.219.51) by server-10.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 13 Jun 2014 09:15:48 -0000 Received: by mail-oa0-f51.google.com with SMTP id j17so2524467oag.24 for ; Fri, 13 Jun 2014 02:15:47 -0700 (PDT) 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=jmLFLU0fXR93iUCzsjG8ex6U68Wk4vBTBDGkOmVSOCo=; b=HLUQMsAF0zkd2pWon4cckcjJfPCNsiXHdHuEQFjKiTS3k15T6BkLGu1UntQgqr1Y36 poMZ4WdKsO8SmdVphPC8iBjFN7WTNV/IkXxBFBx7gjIpgTzHPpSaCY7jqjO0wFY2IsNp vXJh2w5anRd+iFRsytZc5lHrHPOk1dRlDbcs/g7yKBj/9GeVH/k3kAcjGNOknqiylo3b w5glS+CHpso1tjl4rkef3pjy818W9jwSvpbXPUdnFTwiHPDC5g//9T0X0wB+ote1yfvT maQWmMgB50f4gCP0cJj0kXqLe7jc+YP6tWQDIfqNAso8SbrAoLuSyRS0ZQawjRl7AuLa Fijw== MIME-Version: 1.0 X-Received: by 10.60.103.78 with SMTP id fu14mr1352977oeb.21.1402650946890; Fri, 13 Jun 2014 02:15:46 -0700 (PDT) Received: by 10.76.92.5 with HTTP; Fri, 13 Jun 2014 02:15:46 -0700 (PDT) In-Reply-To: <39391660-83A7-46C0-AE53-3880A5A7A885@recoil.org> References: <297FC9DB-3A4E-41A5-B00E-9DEF62C625E6@recoil.org> <39391660-83A7-46C0-AE53-3880A5A7A885@recoil.org> Date: Fri, 13 Jun 2014 10:15:46 +0100 Message-ID: From: Thomas Leonard To: Anil Madhavapeddy Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Mirage on Xen/ARM status X-BeenThere: mirageos-devel@lists.xenproject.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 13 June 2014 10:09, Anil Madhavapeddy wrote: > On 12 Jun 2014, at 15:46, Thomas Leonard wrote: >>> >>> The next step is to get networking working on ARM. >> >> This seems to be working now (I can telnet to port 80 and send it a >> message), which it displays on the console. > > Fantastic!! > >> The main problem turned out to be ones_complement_checksum_bigarray, >> which was doing unaligned double-word (64-bit) memory access. This >> faults on ARM. For testing, I replaced it with the version in the unix >> directory. > > Interesting -- they were meant to be exactly the same if I remember. > Is there an actual code difference between the two aside from include > headers? They are very different. Looks like one got optimised without the other here: https://github.com/mirage/mirage-platform/commit/6fc97d77d0846bc7f17bd0702832ea1faa8a7e71 -- 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 Fri Jun 13 09:20:06 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 13 Jun 2014 09:20: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 1WvNeW-0007tx-Oo; Fri, 13 Jun 2014 09:20:04 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WvNeV-0007ts-RU for mirageos-devel@lists.xenproject.org; Fri, 13 Jun 2014 09:20:03 +0000 Received: from [85.158.139.211:6720] by server-11.bemta-5.messagelabs.com id 21/51-01425-342CA935; Fri, 13 Jun 2014 09:20:03 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-13.tower-206.messagelabs.com!1402651202!9777826!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5220 invoked from network); 13 Jun 2014 09:20:02 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-13.tower-206.messagelabs.com with SMTP; 13 Jun 2014 09:20:02 -0000 Received: (qmail 15194 invoked by uid 634); 13 Jun 2014 09:20:02 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net (HELO [192.168.1.62]) (86.30.244.239) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Fri, 13 Jun 2014 10:19:58 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\)) From: Anil Madhavapeddy In-Reply-To: Date: Fri, 13 Jun 2014 10:19:56 +0100 Message-Id: References: <537A1EAD.5090906@somerandomidiot.com> <538C9FB9.7070001@somerandomidiot.com> <912BC56B-F927-4CDE-9C1E-D40BBD8A79CE@recoil.org> To: David Sheets X-Mailer: Apple Mail (2.1874) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: Balraj Singh , "mirageos-devel@lists.xenproject.org" Subject: [MirageOS-devel] Travis and tuntap (was: Re: OPW intern checking in!) X-BeenThere: mirageos-devel@lists.xenproject.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 11 Jun 2014, at 11:29, David Sheets wrote: > > Last I saw, Travis uses OpenVZ which was an LXC/namespaces/cgroups > precursor provided by a (very) large kernel patch. Privileged LXC > containers (started by a privileged user) do support tuntap if the > executor allows the dev node to be created with something like: > > lxc.cgroup.devices.allow = c 10:200 rwm > > See also . > > I'm not sure if this satisfies your use case but, on its face, it > looks possible. I raised the issue here on the Travis CI tracker: https://github.com/travis-ci/travis-ci/issues/1503 and they turned it down. It does seem reasonable to be paranoid about this, since it could expose their internal network topology more than intended if the containers can send raw network traffic out (although, hopefully their scheme also bans raw sockets). -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 Jun 13 09:20:06 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 13 Jun 2014 09:20: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 1WvNeW-0007tx-Oo; Fri, 13 Jun 2014 09:20:04 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WvNeV-0007ts-RU for mirageos-devel@lists.xenproject.org; Fri, 13 Jun 2014 09:20:03 +0000 Received: from [85.158.139.211:6720] by server-11.bemta-5.messagelabs.com id 21/51-01425-342CA935; Fri, 13 Jun 2014 09:20:03 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-13.tower-206.messagelabs.com!1402651202!9777826!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5220 invoked from network); 13 Jun 2014 09:20:02 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-13.tower-206.messagelabs.com with SMTP; 13 Jun 2014 09:20:02 -0000 Received: (qmail 15194 invoked by uid 634); 13 Jun 2014 09:20:02 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net (HELO [192.168.1.62]) (86.30.244.239) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Fri, 13 Jun 2014 10:19:58 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\)) From: Anil Madhavapeddy In-Reply-To: Date: Fri, 13 Jun 2014 10:19:56 +0100 Message-Id: References: <537A1EAD.5090906@somerandomidiot.com> <538C9FB9.7070001@somerandomidiot.com> <912BC56B-F927-4CDE-9C1E-D40BBD8A79CE@recoil.org> To: David Sheets X-Mailer: Apple Mail (2.1874) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: Balraj Singh , "mirageos-devel@lists.xenproject.org" Subject: [MirageOS-devel] Travis and tuntap (was: Re: OPW intern checking in!) X-BeenThere: mirageos-devel@lists.xenproject.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 11 Jun 2014, at 11:29, David Sheets wrote: > > Last I saw, Travis uses OpenVZ which was an LXC/namespaces/cgroups > precursor provided by a (very) large kernel patch. Privileged LXC > containers (started by a privileged user) do support tuntap if the > executor allows the dev node to be created with something like: > > lxc.cgroup.devices.allow = c 10:200 rwm > > See also . > > I'm not sure if this satisfies your use case but, on its face, it > looks possible. I raised the issue here on the Travis CI tracker: https://github.com/travis-ci/travis-ci/issues/1503 and they turned it down. It does seem reasonable to be paranoid about this, since it could expose their internal network topology more than intended if the containers can send raw network traffic out (although, hopefully their scheme also bans raw sockets). -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 Jun 13 09:21:27 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 13 Jun 2014 09:21: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 1WvNfr-0007vm-UN; Fri, 13 Jun 2014 09:21:27 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WvNfr-0007vh-3b for mirageos-devel@lists.xenproject.org; Fri, 13 Jun 2014 09:21:27 +0000 Received: from [85.158.139.211:18081] by server-4.bemta-5.messagelabs.com id 8C/D6-07250-692CA935; Fri, 13 Jun 2014 09:21:26 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-9.tower-206.messagelabs.com!1402651285!9739776!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17711 invoked from network); 13 Jun 2014 09:21:25 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-9.tower-206.messagelabs.com with SMTP; 13 Jun 2014 09:21:25 -0000 Received: (qmail 20625 invoked by uid 634); 13 Jun 2014 09:21:25 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net (HELO [192.168.1.62]) (86.30.244.239) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Fri, 13 Jun 2014 10:21:24 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\)) From: Anil Madhavapeddy In-Reply-To: Date: Fri, 13 Jun 2014 10:21:22 +0100 Message-Id: <5EC38C5B-9566-45FE-B37F-CD3FB1AC9F03@recoil.org> References: <297FC9DB-3A4E-41A5-B00E-9DEF62C625E6@recoil.org> <39391660-83A7-46C0-AE53-3880A5A7A885@recoil.org> To: Thomas Leonard X-Mailer: Apple Mail (2.1874) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Mirage on Xen/ARM status X-BeenThere: mirageos-devel@lists.xenproject.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 13 Jun 2014, at 10:15, Thomas Leonard wrote: > On 13 June 2014 10:09, Anil Madhavapeddy wrote: >> On 12 Jun 2014, at 15:46, Thomas Leonard wrote: >>>> >>>> The next step is to get networking working on ARM. >>> >>> This seems to be working now (I can telnet to port 80 and send it a >>> message), which it displays on the console. >> >> Fantastic!! >> >>> The main problem turned out to be ones_complement_checksum_bigarray, >>> which was doing unaligned double-word (64-bit) memory access. This >>> faults on ARM. For testing, I replaced it with the version in the unix >>> directory. >> >> Interesting -- they were meant to be exactly the same if I remember. >> Is there an actual code difference between the two aside from include >> headers? > > They are very different. Looks like one got optimised without the other here: > > https://github.com/mirage/mirage-platform/commit/6fc97d77d0846bc7f17bd0702832ea1faa8a7e71 > Ah yes, istr the reasoning behind this was that the Unix one would never be used in a high-performance context, so portability was more useful than performance. Still, being able to unify these is very desirable, as being able to test the stack independently of Xen (and expecting similar behavioural characteristics) is extremely important. -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 Jun 13 09:21:27 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 13 Jun 2014 09:21: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 1WvNfr-0007vm-UN; Fri, 13 Jun 2014 09:21:27 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WvNfr-0007vh-3b for mirageos-devel@lists.xenproject.org; Fri, 13 Jun 2014 09:21:27 +0000 Received: from [85.158.139.211:18081] by server-4.bemta-5.messagelabs.com id 8C/D6-07250-692CA935; Fri, 13 Jun 2014 09:21:26 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-9.tower-206.messagelabs.com!1402651285!9739776!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17711 invoked from network); 13 Jun 2014 09:21:25 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-9.tower-206.messagelabs.com with SMTP; 13 Jun 2014 09:21:25 -0000 Received: (qmail 20625 invoked by uid 634); 13 Jun 2014 09:21:25 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net (HELO [192.168.1.62]) (86.30.244.239) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Fri, 13 Jun 2014 10:21:24 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\)) From: Anil Madhavapeddy In-Reply-To: Date: Fri, 13 Jun 2014 10:21:22 +0100 Message-Id: <5EC38C5B-9566-45FE-B37F-CD3FB1AC9F03@recoil.org> References: <297FC9DB-3A4E-41A5-B00E-9DEF62C625E6@recoil.org> <39391660-83A7-46C0-AE53-3880A5A7A885@recoil.org> To: Thomas Leonard X-Mailer: Apple Mail (2.1874) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Mirage on Xen/ARM status X-BeenThere: mirageos-devel@lists.xenproject.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 13 Jun 2014, at 10:15, Thomas Leonard wrote: > On 13 June 2014 10:09, Anil Madhavapeddy wrote: >> On 12 Jun 2014, at 15:46, Thomas Leonard wrote: >>>> >>>> The next step is to get networking working on ARM. >>> >>> This seems to be working now (I can telnet to port 80 and send it a >>> message), which it displays on the console. >> >> Fantastic!! >> >>> The main problem turned out to be ones_complement_checksum_bigarray, >>> which was doing unaligned double-word (64-bit) memory access. This >>> faults on ARM. For testing, I replaced it with the version in the unix >>> directory. >> >> Interesting -- they were meant to be exactly the same if I remember. >> Is there an actual code difference between the two aside from include >> headers? > > They are very different. Looks like one got optimised without the other here: > > https://github.com/mirage/mirage-platform/commit/6fc97d77d0846bc7f17bd0702832ea1faa8a7e71 > Ah yes, istr the reasoning behind this was that the Unix one would never be used in a high-performance context, so portability was more useful than performance. Still, being able to unify these is very desirable, as being able to test the stack independently of Xen (and expecting similar behavioural characteristics) is extremely important. -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 Jun 13 09:36:56 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 13 Jun 2014 09:36: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 1WvNuo-00088v-Gj; Fri, 13 Jun 2014 09:36:54 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WvNun-00088q-3t for mirageos-devel@lists.xenproject.org; Fri, 13 Jun 2014 09:36:53 +0000 Received: from [85.158.143.35:16207] by server-3.bemta-4.messagelabs.com id 3D/47-13602-436CA935; Fri, 13 Jun 2014 09:36:52 +0000 X-Env-Sender: Dave.Scott@citrix.com X-Msg-Ref: server-6.tower-21.messagelabs.com!1402652211!11073101!1 X-Originating-IP: [185.25.65.24] X-SpamReason: No, hits=0.3 required=7.0 tests=MAILTO_TO_SPAM_ADDR X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31364 invoked from network); 13 Jun 2014 09:36:51 -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; 13 Jun 2014 09:36:51 -0000 X-IronPort-AV: E=Sophos;i="5.01,470,1400025600"; d="scan'208";a="21176549" Received: from unknown (HELO AMSPEX01CL02.citrite.net) ([10.69.60.9]) by AMSPIP01.EU.Citrix.com with ESMTP; 13 Jun 2014 09:36:51 +0000 Received: from AMSPEX01CL03.citrite.net ([169.254.8.89]) by AMSPEX01CL02.citrite.net ([10.69.46.33]) with mapi id 14.03.0181.006; Fri, 13 Jun 2014 11:36:51 +0200 From: Dave Scott To: buzz heavyyear Thread-Topic: [MirageOS-devel] Monitoring MirageOS guests on CubieBoard2 Thread-Index: AQHPb3Syz/EXZafxnE+MQGF4oUAKXps/+wMAgAAcIwCAAAIqgIAABaCAgAABpwCAAAWfgIABKCoAgC1kyICAACJoAA== Date: Fri, 13 Jun 2014 09:36:48 +0000 Message-ID: <4E8A3FB1-5F4E-4BDC-A071-8F83730AF610@citrix.com> References: , <0846576A-E0E8-4F35-99FA-6729250975B5@recoil.org>, <5373900A.4030901@cam.ac.uk>, <9AF01405-3475-4FC7-A308-4075DE335BEF@recoil.org>, <53739693.2050308@cam.ac.uk>, <0E252CC1-CF37-4611-B633-D427E2051B7D@recoil.org>, , In-Reply-To: Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.69.46.1] Content-ID: <83976D6197A01D4F8A3FE41FA493BCEF@citrix.com> MIME-Version: 1.0 X-DLP: AMS1 Cc: John Else , "mirageos-devel@lists.xenproject.org" , Anil Madhavapeddy Subject: Re: [MirageOS-devel] Monitoring MirageOS guests on CubieBoard2 X-BeenThere: mirageos-devel@lists.xenproject.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 13 Jun 2014, at 08:33, buzz heavyyear wrote: > Just a quick question to find out if RRD will make it into MirageOS 2.0, = especially for the ARM Cubieboard platform? Let=92s add =93statistics reporting=94 to our to-do list =97 we=92ve got va= rious counters all over the place and John Else (cc:d) has a draft of a sha= red-memory protocol for sharing them. Cheers, Dave > = > Cheers > Nick > = > > From: anil@recoil.org > > Date: Thu, 15 May 2014 11:21:18 +0100 > > To: Dave.Scott@citrix.com > > CC: mirageos-devel@lists.xenproject.org > > Subject: Re: [MirageOS-devel] Monitoring MirageOS guests on CubieBoard2 > > = > > On 14 May 2014, at 17:41, Dave Scott wrote: > > = > > > = > > > On 14 May 2014, at 17:21, Anil Madhavapeddy wrote: > > > = > > >> On 14 May 2014, at 17:15, Jon Ludlam wrote: > > >> = > > >>> On 14/05/14 16:55, Anil Madhavapeddy wrote: > > >>>> On 14 May 2014, at 16:47, Jon Ludlam wrote: > > >>>>>> On 14/05/14 15:06, Anil Madhavapeddy wrote: > > >>>>>>> On 14 May 2014, at 14:01, buzz heavyyear wrote: > > >>>>>>> = > > >>>>>>> Now that I'm having a lot of fun getting up to speed with ocaml= , xen, mirage, writing ocaml guests and getting them to run on the Cubieboa= rd, what I really need is to see how they are performing as they are runnin= g. > > >>>>>>> = > > >>>>>>> XAPI/XCP has rrd. Am I right in thinking that a good way forwar= d is to includegithub.com/xapi-project/xcp-rrd during the build process? > > >>>>>>> = > > >>>>>>> Perhaps there's an easier way? Any thoughts anyone? > > >>>>>> RRD is definitely the right direction for dom0 to track guest ac= tivity, but we do need to get vchan up to speed from the guest side. Dave, = Jon, what's the current state of ocaml-vchan? I'm happy to add a Cohttp fun= ctor for it if there's something vaguely resembling a FLOW interface (right= now, it's fairly low level). > > >>>>> I believe the state is 'I saw it work once recently'. There's not= hing > > >>>>> really resembling a flow interface, but I'm sure one could be ass= embled > > >>>>> fairly easily. > > >>>> Thanks, is there a working unit test domain anywhere? If we're goi= ng to depend on vchan, it's time to get the low level bits well tested. The= atomic bit ops particularly worrisome, and we are likely to be the first A= RM vchan user (so let's get the x86 bugs sorted first :-) > > >>>> = > > >>>> Anil > > >>>> = > > >>>> = > > >>> What I was using to test was the vchan client from the xen reposito= ry. > > >>> I'll have another look at it tomorrow if you like? > > >> = > > >> Ah yes, I keep forgetting about those binaries from the Xen repo -- = are they installed by distros these days? (so we have a netcat-like vchan c= lient). > > > = > > > Good question. I need to take a look at vchan again, to see if it mak= es sense to plumb a vchan link through to guests from the dom0 toolstack fo= r off-box cloud orchestration layers to talk to their service VMs without u= sing ssh. Perhaps little Mirage HTTP <-> vchan service would work nicely. > > = > > That would certainly cure the 'RPC through xenstore' malaise that affli= cts everyone who has this problem. > > = > > More broadly, making vchan available with a convenient netcat-command-l= ine interface would generally make interfacing with guests much more pleasa= nt. > > = > > I notice that Arjun Guha has just started an OCaml Docker binding which= will give us the same benefits using LXC, so making these interfaces simil= ar for Xen would be very handy. > > https://github.com/arjunguha/ocaml-docker > > = > > -anil > > _______________________________________________ > > 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 Jun 13 09:36:56 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 13 Jun 2014 09:36: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 1WvNuo-00088v-Gj; Fri, 13 Jun 2014 09:36:54 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WvNun-00088q-3t for mirageos-devel@lists.xenproject.org; Fri, 13 Jun 2014 09:36:53 +0000 Received: from [85.158.143.35:16207] by server-3.bemta-4.messagelabs.com id 3D/47-13602-436CA935; Fri, 13 Jun 2014 09:36:52 +0000 X-Env-Sender: Dave.Scott@citrix.com X-Msg-Ref: server-6.tower-21.messagelabs.com!1402652211!11073101!1 X-Originating-IP: [185.25.65.24] X-SpamReason: No, hits=0.3 required=7.0 tests=MAILTO_TO_SPAM_ADDR X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31364 invoked from network); 13 Jun 2014 09:36:51 -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; 13 Jun 2014 09:36:51 -0000 X-IronPort-AV: E=Sophos;i="5.01,470,1400025600"; d="scan'208";a="21176549" Received: from unknown (HELO AMSPEX01CL02.citrite.net) ([10.69.60.9]) by AMSPIP01.EU.Citrix.com with ESMTP; 13 Jun 2014 09:36:51 +0000 Received: from AMSPEX01CL03.citrite.net ([169.254.8.89]) by AMSPEX01CL02.citrite.net ([10.69.46.33]) with mapi id 14.03.0181.006; Fri, 13 Jun 2014 11:36:51 +0200 From: Dave Scott To: buzz heavyyear Thread-Topic: [MirageOS-devel] Monitoring MirageOS guests on CubieBoard2 Thread-Index: AQHPb3Syz/EXZafxnE+MQGF4oUAKXps/+wMAgAAcIwCAAAIqgIAABaCAgAABpwCAAAWfgIABKCoAgC1kyICAACJoAA== Date: Fri, 13 Jun 2014 09:36:48 +0000 Message-ID: <4E8A3FB1-5F4E-4BDC-A071-8F83730AF610@citrix.com> References: , <0846576A-E0E8-4F35-99FA-6729250975B5@recoil.org>, <5373900A.4030901@cam.ac.uk>, <9AF01405-3475-4FC7-A308-4075DE335BEF@recoil.org>, <53739693.2050308@cam.ac.uk>, <0E252CC1-CF37-4611-B633-D427E2051B7D@recoil.org>, , In-Reply-To: Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.69.46.1] Content-ID: <83976D6197A01D4F8A3FE41FA493BCEF@citrix.com> MIME-Version: 1.0 X-DLP: AMS1 Cc: John Else , "mirageos-devel@lists.xenproject.org" , Anil Madhavapeddy Subject: Re: [MirageOS-devel] Monitoring MirageOS guests on CubieBoard2 X-BeenThere: mirageos-devel@lists.xenproject.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 13 Jun 2014, at 08:33, buzz heavyyear wrote: > Just a quick question to find out if RRD will make it into MirageOS 2.0, = especially for the ARM Cubieboard platform? Let=92s add =93statistics reporting=94 to our to-do list =97 we=92ve got va= rious counters all over the place and John Else (cc:d) has a draft of a sha= red-memory protocol for sharing them. Cheers, Dave > = > Cheers > Nick > = > > From: anil@recoil.org > > Date: Thu, 15 May 2014 11:21:18 +0100 > > To: Dave.Scott@citrix.com > > CC: mirageos-devel@lists.xenproject.org > > Subject: Re: [MirageOS-devel] Monitoring MirageOS guests on CubieBoard2 > > = > > On 14 May 2014, at 17:41, Dave Scott wrote: > > = > > > = > > > On 14 May 2014, at 17:21, Anil Madhavapeddy wrote: > > > = > > >> On 14 May 2014, at 17:15, Jon Ludlam wrote: > > >> = > > >>> On 14/05/14 16:55, Anil Madhavapeddy wrote: > > >>>> On 14 May 2014, at 16:47, Jon Ludlam wrote: > > >>>>>> On 14/05/14 15:06, Anil Madhavapeddy wrote: > > >>>>>>> On 14 May 2014, at 14:01, buzz heavyyear wrote: > > >>>>>>> = > > >>>>>>> Now that I'm having a lot of fun getting up to speed with ocaml= , xen, mirage, writing ocaml guests and getting them to run on the Cubieboa= rd, what I really need is to see how they are performing as they are runnin= g. > > >>>>>>> = > > >>>>>>> XAPI/XCP has rrd. Am I right in thinking that a good way forwar= d is to includegithub.com/xapi-project/xcp-rrd during the build process? > > >>>>>>> = > > >>>>>>> Perhaps there's an easier way? Any thoughts anyone? > > >>>>>> RRD is definitely the right direction for dom0 to track guest ac= tivity, but we do need to get vchan up to speed from the guest side. Dave, = Jon, what's the current state of ocaml-vchan? I'm happy to add a Cohttp fun= ctor for it if there's something vaguely resembling a FLOW interface (right= now, it's fairly low level). > > >>>>> I believe the state is 'I saw it work once recently'. There's not= hing > > >>>>> really resembling a flow interface, but I'm sure one could be ass= embled > > >>>>> fairly easily. > > >>>> Thanks, is there a working unit test domain anywhere? If we're goi= ng to depend on vchan, it's time to get the low level bits well tested. The= atomic bit ops particularly worrisome, and we are likely to be the first A= RM vchan user (so let's get the x86 bugs sorted first :-) > > >>>> = > > >>>> Anil > > >>>> = > > >>>> = > > >>> What I was using to test was the vchan client from the xen reposito= ry. > > >>> I'll have another look at it tomorrow if you like? > > >> = > > >> Ah yes, I keep forgetting about those binaries from the Xen repo -- = are they installed by distros these days? (so we have a netcat-like vchan c= lient). > > > = > > > Good question. I need to take a look at vchan again, to see if it mak= es sense to plumb a vchan link through to guests from the dom0 toolstack fo= r off-box cloud orchestration layers to talk to their service VMs without u= sing ssh. Perhaps little Mirage HTTP <-> vchan service would work nicely. > > = > > That would certainly cure the 'RPC through xenstore' malaise that affli= cts everyone who has this problem. > > = > > More broadly, making vchan available with a convenient netcat-command-l= ine interface would generally make interfacing with guests much more pleasa= nt. > > = > > I notice that Arjun Guha has just started an OCaml Docker binding which= will give us the same benefits using LXC, so making these interfaces simil= ar for Xen would be very handy. > > https://github.com/arjunguha/ocaml-docker > > = > > -anil > > _______________________________________________ > > 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 Jun 13 09:42:35 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 13 Jun 2014 09:42: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 1WvO0I-0008IS-Ay; Fri, 13 Jun 2014 09:42:34 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WvO0G-0008IM-G0 for mirageos-devel@lists.xenproject.org; Fri, 13 Jun 2014 09:42:32 +0000 Received: from [85.158.143.35:44257] by server-2.bemta-4.messagelabs.com id 96/03-06539-787CA935; Fri, 13 Jun 2014 09:42:31 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-3.tower-21.messagelabs.com!1402652550!10795090!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 9330 invoked from network); 13 Jun 2014 09:42:30 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-3.tower-21.messagelabs.com with SMTP; 13 Jun 2014 09:42:30 -0000 Received: (qmail 24622 invoked by uid 634); 13 Jun 2014 09:42:30 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net (HELO [192.168.1.62]) (86.30.244.239) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Fri, 13 Jun 2014 10:42:29 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\)) From: Anil Madhavapeddy In-Reply-To: <4E8A3FB1-5F4E-4BDC-A071-8F83730AF610@citrix.com> Date: Fri, 13 Jun 2014 10:42:27 +0100 Message-Id: <25EA0DB9-6DA8-4C6F-BAD9-587D3CEC4D55@recoil.org> References: , <0846576A-E0E8-4F35-99FA-6729250975B5@recoil.org>, <5373900A.4030901@cam.ac.uk>, <9AF01405-3475-4FC7-A308-4075DE335BEF@recoil.org>, <53739693.2050308@cam.ac.uk>, <0E252CC1-CF37-4611-B633-D427E2051B7D@recoil.org>, , <4E8A3FB1-5F4E-4BDC-A071-8F83730AF610@citrix.com> To: David Scott X-Mailer: Apple Mail (2.1874) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: John Else , "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Monitoring MirageOS guests on CubieBoard2 X-BeenThere: mirageos-devel@lists.xenproject.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 13 Jun 2014, at 10:36, Dave Scott wrote: > = > On 13 Jun 2014, at 08:33, buzz heavyyear wrot= e: > = >> Just a quick question to find out if RRD will make it into MirageOS 2.0,= especially for the ARM Cubieboard platform? > = > Let=92s add =93statistics reporting=94 to our to-do list =97 we=92ve got = various counters all over the place and John Else (cc:d) has a draft of a s= hared-memory protocol for sharing them. This would be *extremely* useful to have! For the Mirage 2.0 release, I expect that ensuring that we have the right p= rimitives in place (xenstore+vchan) for an RRD library to plug into would b= e safest. The rest can follow as a normal library update. Nick: do you have any particular use-cases in mind on ARM that might guide = this integration? I'm primarily interested in RRD as a scoreboard for trac= king stats like network stack connections and load counters. As we disaggr= egate more of dom0 into unikernels, having these trace points becomes incre= asingly important. 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 Jun 13 09:42:35 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 13 Jun 2014 09:42: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 1WvO0I-0008IS-Ay; Fri, 13 Jun 2014 09:42:34 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WvO0G-0008IM-G0 for mirageos-devel@lists.xenproject.org; Fri, 13 Jun 2014 09:42:32 +0000 Received: from [85.158.143.35:44257] by server-2.bemta-4.messagelabs.com id 96/03-06539-787CA935; Fri, 13 Jun 2014 09:42:31 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-3.tower-21.messagelabs.com!1402652550!10795090!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 9330 invoked from network); 13 Jun 2014 09:42:30 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-3.tower-21.messagelabs.com with SMTP; 13 Jun 2014 09:42:30 -0000 Received: (qmail 24622 invoked by uid 634); 13 Jun 2014 09:42:30 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net (HELO [192.168.1.62]) (86.30.244.239) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Fri, 13 Jun 2014 10:42:29 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\)) From: Anil Madhavapeddy In-Reply-To: <4E8A3FB1-5F4E-4BDC-A071-8F83730AF610@citrix.com> Date: Fri, 13 Jun 2014 10:42:27 +0100 Message-Id: <25EA0DB9-6DA8-4C6F-BAD9-587D3CEC4D55@recoil.org> References: , <0846576A-E0E8-4F35-99FA-6729250975B5@recoil.org>, <5373900A.4030901@cam.ac.uk>, <9AF01405-3475-4FC7-A308-4075DE335BEF@recoil.org>, <53739693.2050308@cam.ac.uk>, <0E252CC1-CF37-4611-B633-D427E2051B7D@recoil.org>, , <4E8A3FB1-5F4E-4BDC-A071-8F83730AF610@citrix.com> To: David Scott X-Mailer: Apple Mail (2.1874) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: John Else , "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Monitoring MirageOS guests on CubieBoard2 X-BeenThere: mirageos-devel@lists.xenproject.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 13 Jun 2014, at 10:36, Dave Scott wrote: > = > On 13 Jun 2014, at 08:33, buzz heavyyear wrot= e: > = >> Just a quick question to find out if RRD will make it into MirageOS 2.0,= especially for the ARM Cubieboard platform? > = > Let=92s add =93statistics reporting=94 to our to-do list =97 we=92ve got = various counters all over the place and John Else (cc:d) has a draft of a s= hared-memory protocol for sharing them. This would be *extremely* useful to have! For the Mirage 2.0 release, I expect that ensuring that we have the right p= rimitives in place (xenstore+vchan) for an RRD library to plug into would b= e safest. The rest can follow as a normal library update. Nick: do you have any particular use-cases in mind on ARM that might guide = this integration? I'm primarily interested in RRD as a scoreboard for trac= king stats like network stack connections and load counters. As we disaggr= egate more of dom0 into unikernels, having these trace points becomes incre= asingly important. 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 Jun 13 10:26:09 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 13 Jun 2014 10:26: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 1WvOgR-0000PS-2p; Fri, 13 Jun 2014 10:26:07 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WvOgO-0000PK-Uc for mirageos-devel@lists.xenproject.org; Fri, 13 Jun 2014 10:26:05 +0000 Received: from [193.109.254.147:29268] by server-3.bemta-14.messagelabs.com id 89/4A-22179-CB1DA935; Fri, 13 Jun 2014 10:26:04 +0000 X-Env-Sender: buzzheavyyear@hotmail.com X-Msg-Ref: server-6.tower-27.messagelabs.com!1402655162!11022716!1 X-Originating-IP: [157.55.2.103] X-SpamReason: No, hits=1.5 required=7.0 tests=BODY_RANDOM_LONG, FORGED_HOTMAIL_RCVD,HTML_20_30,HTML_MESSAGE,ML_RADAR_SPEW_LINKS_12, ML_RADAR_SPEW_LINKS_14,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12023 invoked from network); 13 Jun 2014 10:26:03 -0000 Received: from dub004-omc4s28.hotmail.com (HELO DUB004-OMC4S28.hotmail.com) (157.55.2.103) by server-6.tower-27.messagelabs.com with AES128-SHA encrypted SMTP; 13 Jun 2014 10:26:03 -0000 Received: from DUB128-W82 ([157.55.2.72]) by DUB004-OMC4S28.hotmail.com with Microsoft SMTPSVC(7.5.7601.22701); Fri, 13 Jun 2014 03:26:02 -0700 X-TMN: [dng+MG3LncteHPsFId+5ey252rIdmump] X-Originating-Email: [buzzheavyyear@hotmail.com] Message-ID: From: buzz heavyyear To: Anil Madhavapeddy , David Scott Date: Fri, 13 Jun 2014 10:26:02 +0000 Importance: Normal In-Reply-To: <25EA0DB9-6DA8-4C6F-BAD9-587D3CEC4D55@recoil.org> References: , <0846576A-E0E8-4F35-99FA-6729250975B5@recoil.org>, <5373900A.4030901@cam.ac.uk>, <9AF01405-3475-4FC7-A308-4075DE335BEF@recoil.org>, <53739693.2050308@cam.ac.uk>, <0E252CC1-CF37-4611-B633-D427E2051B7D@recoil.org>, , <4E8A3FB1-5F4E-4BDC-A071-8F83730AF610@citrix.com>, <25EA0DB9-6DA8-4C6F-BAD9-587D3CEC4D55@recoil.org> MIME-Version: 1.0 X-OriginalArrivalTime: 13 Jun 2014 10:26:02.0712 (UTC) FILETIME=[E066FD80:01CF86F1] Cc: John Else , "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Monitoring MirageOS guests on CubieBoard2 X-BeenThere: mirageos-devel@lists.xenproject.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="===============2323653353777200314==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============2323653353777200314== Content-Type: multipart/alternative; boundary="_476ad63e-d7dc-4ad4-908a-68fdac619898_" --_476ad63e-d7dc-4ad4-908a-68fdac619898_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable > For the Mirage 2.0 release=2C I expect that ensuring that we have the rig= ht primitives in place (xenstore+vchan) for an RRD library to plug into wou= ld be safest. The rest can follow as a normal library update. Top dollar! > Nick: do you have any particular use-cases in mind on ARM that might guid= e this integration? I'm primarily interested in RRD as a scoreboard for tr= acking stats like network stack connections and load counters. As we disag= gregate more of dom0 into unikernels=2C having these trace points becomes i= ncreasingly important. Like you=2C I'm definitely after tracking stats=3B also concerned over poor= ly written application code which blows up and needs to be safely recovered= - intend to tack on various sensors to the cubieboard=2C monitor the proce= ss and if there is data-overload=2C safely deal with it. This really is a tremendous environment for small board solutions. Thanks t= o everyone for make this available. I'm definitely not worthy. Very best=2C Nick = --_476ad63e-d7dc-4ad4-908a-68fdac619898_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

>=3B For the Mirage 2= .0 release=2C I expect that ensuring that we have the right primitives in p= lace (xenstore+vchan) for an RRD library to plug into would be safest. The= rest can follow as a normal library update.

Top dollar!

>= =3B Nick: do you have any particular use-cases in mind on ARM that might gu= ide this integration? I'm primarily interested in RRD as a scoreboard for = tracking stats like network stack connections and load counters. As we dis= aggregate more of dom0 into unikernels=2C having these trace points becomes= increasingly important.

Like you=2C I'm definitely after tracking s= tats=3B also concerned over poorly written application code which blows up = and needs to be safely recovered - intend to tack on various sensors to the= cubieboard=2C monitor the process and if there is data-overload=2C safely = deal with it.

This really is a tremendous environment for small boar= d solutions. Thanks to everyone for make this available.

I'm definit= ely not worthy.

Very best=2C
Nick
= --_476ad63e-d7dc-4ad4-908a-68fdac619898_-- --===============2323653353777200314== 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 --===============2323653353777200314==-- From mirageos-devel-bounces@lists.xenproject.org Fri Jun 13 10:26:09 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 13 Jun 2014 10:26: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 1WvOgR-0000PS-2p; Fri, 13 Jun 2014 10:26:07 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WvOgO-0000PK-Uc for mirageos-devel@lists.xenproject.org; Fri, 13 Jun 2014 10:26:05 +0000 Received: from [193.109.254.147:29268] by server-3.bemta-14.messagelabs.com id 89/4A-22179-CB1DA935; Fri, 13 Jun 2014 10:26:04 +0000 X-Env-Sender: buzzheavyyear@hotmail.com X-Msg-Ref: server-6.tower-27.messagelabs.com!1402655162!11022716!1 X-Originating-IP: [157.55.2.103] X-SpamReason: No, hits=1.5 required=7.0 tests=BODY_RANDOM_LONG, FORGED_HOTMAIL_RCVD,HTML_20_30,HTML_MESSAGE,ML_RADAR_SPEW_LINKS_12, ML_RADAR_SPEW_LINKS_14,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12023 invoked from network); 13 Jun 2014 10:26:03 -0000 Received: from dub004-omc4s28.hotmail.com (HELO DUB004-OMC4S28.hotmail.com) (157.55.2.103) by server-6.tower-27.messagelabs.com with AES128-SHA encrypted SMTP; 13 Jun 2014 10:26:03 -0000 Received: from DUB128-W82 ([157.55.2.72]) by DUB004-OMC4S28.hotmail.com with Microsoft SMTPSVC(7.5.7601.22701); Fri, 13 Jun 2014 03:26:02 -0700 X-TMN: [dng+MG3LncteHPsFId+5ey252rIdmump] X-Originating-Email: [buzzheavyyear@hotmail.com] Message-ID: From: buzz heavyyear To: Anil Madhavapeddy , David Scott Date: Fri, 13 Jun 2014 10:26:02 +0000 Importance: Normal In-Reply-To: <25EA0DB9-6DA8-4C6F-BAD9-587D3CEC4D55@recoil.org> References: , <0846576A-E0E8-4F35-99FA-6729250975B5@recoil.org>, <5373900A.4030901@cam.ac.uk>, <9AF01405-3475-4FC7-A308-4075DE335BEF@recoil.org>, <53739693.2050308@cam.ac.uk>, <0E252CC1-CF37-4611-B633-D427E2051B7D@recoil.org>, , <4E8A3FB1-5F4E-4BDC-A071-8F83730AF610@citrix.com>, <25EA0DB9-6DA8-4C6F-BAD9-587D3CEC4D55@recoil.org> MIME-Version: 1.0 X-OriginalArrivalTime: 13 Jun 2014 10:26:02.0712 (UTC) FILETIME=[E066FD80:01CF86F1] Cc: John Else , "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Monitoring MirageOS guests on CubieBoard2 X-BeenThere: mirageos-devel@lists.xenproject.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="===============2323653353777200314==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============2323653353777200314== Content-Type: multipart/alternative; boundary="_476ad63e-d7dc-4ad4-908a-68fdac619898_" --_476ad63e-d7dc-4ad4-908a-68fdac619898_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable > For the Mirage 2.0 release=2C I expect that ensuring that we have the rig= ht primitives in place (xenstore+vchan) for an RRD library to plug into wou= ld be safest. The rest can follow as a normal library update. Top dollar! > Nick: do you have any particular use-cases in mind on ARM that might guid= e this integration? I'm primarily interested in RRD as a scoreboard for tr= acking stats like network stack connections and load counters. As we disag= gregate more of dom0 into unikernels=2C having these trace points becomes i= ncreasingly important. Like you=2C I'm definitely after tracking stats=3B also concerned over poor= ly written application code which blows up and needs to be safely recovered= - intend to tack on various sensors to the cubieboard=2C monitor the proce= ss and if there is data-overload=2C safely deal with it. This really is a tremendous environment for small board solutions. Thanks t= o everyone for make this available. I'm definitely not worthy. Very best=2C Nick = --_476ad63e-d7dc-4ad4-908a-68fdac619898_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

>=3B For the Mirage 2= .0 release=2C I expect that ensuring that we have the right primitives in p= lace (xenstore+vchan) for an RRD library to plug into would be safest. The= rest can follow as a normal library update.

Top dollar!

>= =3B Nick: do you have any particular use-cases in mind on ARM that might gu= ide this integration? I'm primarily interested in RRD as a scoreboard for = tracking stats like network stack connections and load counters. As we dis= aggregate more of dom0 into unikernels=2C having these trace points becomes= increasingly important.

Like you=2C I'm definitely after tracking s= tats=3B also concerned over poorly written application code which blows up = and needs to be safely recovered - intend to tack on various sensors to the= cubieboard=2C monitor the process and if there is data-overload=2C safely = deal with it.

This really is a tremendous environment for small boar= d solutions. Thanks to everyone for make this available.

I'm definit= ely not worthy.

Very best=2C
Nick
= --_476ad63e-d7dc-4ad4-908a-68fdac619898_-- --===============2323653353777200314== 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 --===============2323653353777200314==-- From mirageos-devel-bounces@lists.xenproject.org Fri Jun 13 10:26:33 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 13 Jun 2014 10:26: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 1WvOgr-0000R1-7R; Fri, 13 Jun 2014 10:26:33 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WvOgp-0000Qw-Ph for mirageos-devel@lists.xenproject.org; Fri, 13 Jun 2014 10:26:31 +0000 Received: from [85.158.139.211:26773] by server-2.bemta-5.messagelabs.com id 90/5B-01647-7D1DA935; Fri, 13 Jun 2014 10:26:31 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-8.tower-206.messagelabs.com!1402655189!9755471!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.1 required=7.0 tests=HTML_30_40,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 26752 invoked from network); 13 Jun 2014 10:26:30 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-8.tower-206.messagelabs.com with SMTP; 13 Jun 2014 10:26:30 -0000 Received: (qmail 21404 invoked by uid 634); 13 Jun 2014 10:26:29 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED,HTML_MESSAGE X-Spam-Check-By: dark.recoil.org Received: from cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net (HELO [192.168.1.62]) (86.30.244.239) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Fri, 13 Jun 2014 11:26:29 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\)) From: Anil Madhavapeddy In-Reply-To: Date: Fri, 13 Jun 2014 11:26:27 +0100 Message-Id: References: To: David Scott X-Mailer: Apple Mail (2.1874) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] towards a common Mirage 'FLOW' signature X-BeenThere: mirageos-devel@lists.xenproject.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="===============1227975401923027595==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============1227975401923027595== Content-Type: multipart/alternative; boundary="Apple-Mail=_38DAD928-B4A6-4788-8CF6-34374357A67A" --Apple-Mail=_38DAD928-B4A6-4788-8CF6-34374357A67A Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On 12 Jun 2014, at 21:38, David Scott wrote: > Hi, >=20 > I'd like to create a common Mirage 'FLOW' signature to represent = reading and writing along some kind of 'connection'. I think we could = satisfy the signature in multiple places including at least >=20 > * consoles > * xen inter-domain vchan connections > * plain TCP > * (hopefully) TLS connections >=20 > It would be nice to write clients and servers which would work over = multiple FLOW implementations. >=20 > For discussion I've extracted the 'FLOW' from 'TCPv4' to show you what = it would look like: >=20 > = https://github.com/djs55/mirage/commit/87f9855f22f997264870f903c998b1d9218= 6fdef >=20 > In V2 of the API I'd like to turn the CONSOLE signature into a = combination of DEVICE and FLOW. This looks good to me. The one caveat is why write cannot return an = error in the existing API. It is possible for the lower-level transport = to signal a hard error, although we rarely do so at the moment. In the = interests of future compatibility, should we make that change? > I notice the low-level network APIs (NETWORK, ETHIF, ...) are *almost* = like this except they have a function like >=20 > val listen: t -> udp:callback -> tcp:callback -> ...=20 >=20 > Perhaps later (V2, V3?) we could split this into something like a=20 >=20 > val read: t -> buffer (* satisfy FLOW *) > val classify: buffer -> [ `UDP; `TCP ] >=20 > -- is that a good idea? I don't think the listen function should be in the FLOW signature at = all, since this is part of the resolver API that establishes = connections. This is compatible with your patch, since the network APIs can "include = FLOW" and define the additional connection-specific functions without = issue. cheers, Anil= --Apple-Mail=_38DAD928-B4A6-4788-8CF6-34374357A67A Content-Transfer-Encoding: 7bit Content-Type: text/html; charset=us-ascii On 12 Jun 2014, at 21:38, David Scott <scott.dj@gmail.com> wrote:

Hi,

I'd like to create a common Mirage 'FLOW' signature to represent reading and writing along some kind of 'connection'. I think we could satisfy the signature in multiple places including at least

* consoles
* xen inter-domain vchan connections
* plain TCP
* (hopefully) TLS connections

It would be nice to write clients and servers which would work over multiple FLOW implementations.

For discussion I've extracted the 'FLOW' from 'TCPv4' to show you what it would look like:


In V2 of the API I'd like to turn the CONSOLE signature into a combination of DEVICE and FLOW.

This looks good to me.  The one caveat is why write cannot return an error in the existing API.  It is possible for the lower-level transport to signal a hard error, although we rarely do so at the moment.  In the interests of future compatibility, should we make that change?

I notice the low-level network APIs (NETWORK, ETHIF, ...) are *almost* like this except they have a function like

val listen: t -> udp:callback -> tcp:callback -> ... 

Perhaps later (V2, V3?) we could split this into something like a 

val read: t -> buffer (* satisfy FLOW *)
val classify: buffer -> [ `UDP; `TCP ]

-- is that a good idea?

I don't think the listen function should be in the FLOW signature at all, since this is part of the resolver API that establishes connections.

This is compatible with your patch, since the network APIs can "include FLOW" and define the additional connection-specific functions without issue.

cheers,
Anil
--Apple-Mail=_38DAD928-B4A6-4788-8CF6-34374357A67A-- --===============1227975401923027595== 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 --===============1227975401923027595==-- From mirageos-devel-bounces@lists.xenproject.org Fri Jun 13 10:26:33 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 13 Jun 2014 10:26: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 1WvOgr-0000R1-7R; Fri, 13 Jun 2014 10:26:33 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WvOgp-0000Qw-Ph for mirageos-devel@lists.xenproject.org; Fri, 13 Jun 2014 10:26:31 +0000 Received: from [85.158.139.211:26773] by server-2.bemta-5.messagelabs.com id 90/5B-01647-7D1DA935; Fri, 13 Jun 2014 10:26:31 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-8.tower-206.messagelabs.com!1402655189!9755471!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.1 required=7.0 tests=HTML_30_40,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 26752 invoked from network); 13 Jun 2014 10:26:30 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-8.tower-206.messagelabs.com with SMTP; 13 Jun 2014 10:26:30 -0000 Received: (qmail 21404 invoked by uid 634); 13 Jun 2014 10:26:29 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED,HTML_MESSAGE X-Spam-Check-By: dark.recoil.org Received: from cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net (HELO [192.168.1.62]) (86.30.244.239) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Fri, 13 Jun 2014 11:26:29 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\)) From: Anil Madhavapeddy In-Reply-To: Date: Fri, 13 Jun 2014 11:26:27 +0100 Message-Id: References: To: David Scott X-Mailer: Apple Mail (2.1874) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] towards a common Mirage 'FLOW' signature X-BeenThere: mirageos-devel@lists.xenproject.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="===============1227975401923027595==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============1227975401923027595== Content-Type: multipart/alternative; boundary="Apple-Mail=_38DAD928-B4A6-4788-8CF6-34374357A67A" --Apple-Mail=_38DAD928-B4A6-4788-8CF6-34374357A67A Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On 12 Jun 2014, at 21:38, David Scott wrote: > Hi, >=20 > I'd like to create a common Mirage 'FLOW' signature to represent = reading and writing along some kind of 'connection'. I think we could = satisfy the signature in multiple places including at least >=20 > * consoles > * xen inter-domain vchan connections > * plain TCP > * (hopefully) TLS connections >=20 > It would be nice to write clients and servers which would work over = multiple FLOW implementations. >=20 > For discussion I've extracted the 'FLOW' from 'TCPv4' to show you what = it would look like: >=20 > = https://github.com/djs55/mirage/commit/87f9855f22f997264870f903c998b1d9218= 6fdef >=20 > In V2 of the API I'd like to turn the CONSOLE signature into a = combination of DEVICE and FLOW. This looks good to me. The one caveat is why write cannot return an = error in the existing API. It is possible for the lower-level transport = to signal a hard error, although we rarely do so at the moment. In the = interests of future compatibility, should we make that change? > I notice the low-level network APIs (NETWORK, ETHIF, ...) are *almost* = like this except they have a function like >=20 > val listen: t -> udp:callback -> tcp:callback -> ...=20 >=20 > Perhaps later (V2, V3?) we could split this into something like a=20 >=20 > val read: t -> buffer (* satisfy FLOW *) > val classify: buffer -> [ `UDP; `TCP ] >=20 > -- is that a good idea? I don't think the listen function should be in the FLOW signature at = all, since this is part of the resolver API that establishes = connections. This is compatible with your patch, since the network APIs can "include = FLOW" and define the additional connection-specific functions without = issue. cheers, Anil= --Apple-Mail=_38DAD928-B4A6-4788-8CF6-34374357A67A Content-Transfer-Encoding: 7bit Content-Type: text/html; charset=us-ascii On 12 Jun 2014, at 21:38, David Scott <scott.dj@gmail.com> wrote:

Hi,

I'd like to create a common Mirage 'FLOW' signature to represent reading and writing along some kind of 'connection'. I think we could satisfy the signature in multiple places including at least

* consoles
* xen inter-domain vchan connections
* plain TCP
* (hopefully) TLS connections

It would be nice to write clients and servers which would work over multiple FLOW implementations.

For discussion I've extracted the 'FLOW' from 'TCPv4' to show you what it would look like:


In V2 of the API I'd like to turn the CONSOLE signature into a combination of DEVICE and FLOW.

This looks good to me.  The one caveat is why write cannot return an error in the existing API.  It is possible for the lower-level transport to signal a hard error, although we rarely do so at the moment.  In the interests of future compatibility, should we make that change?

I notice the low-level network APIs (NETWORK, ETHIF, ...) are *almost* like this except they have a function like

val listen: t -> udp:callback -> tcp:callback -> ... 

Perhaps later (V2, V3?) we could split this into something like a 

val read: t -> buffer (* satisfy FLOW *)
val classify: buffer -> [ `UDP; `TCP ]

-- is that a good idea?

I don't think the listen function should be in the FLOW signature at all, since this is part of the resolver API that establishes connections.

This is compatible with your patch, since the network APIs can "include FLOW" and define the additional connection-specific functions without issue.

cheers,
Anil
--Apple-Mail=_38DAD928-B4A6-4788-8CF6-34374357A67A-- --===============1227975401923027595== 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 --===============1227975401923027595==-- From mirageos-devel-bounces@lists.xenproject.org Fri Jun 13 10:26:56 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 13 Jun 2014 10:26: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 1WvOhE-0000Sr-AZ; Fri, 13 Jun 2014 10:26:56 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WvOhC-0000Sh-8r for mirageos-devel@lists.xenproject.org; Fri, 13 Jun 2014 10:26:54 +0000 Received: from [193.109.254.147:44632] by server-3.bemta-14.messagelabs.com id 05/7B-22179-DE1DA935; Fri, 13 Jun 2014 10:26:53 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-14.tower-27.messagelabs.com!1402655212!11038878!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.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7578 invoked from network); 13 Jun 2014 10:26:52 -0000 Received: from mail-we0-f176.google.com (HELO mail-we0-f176.google.com) (74.125.82.176) by server-14.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 13 Jun 2014 10:26:52 -0000 Received: by mail-we0-f176.google.com with SMTP id u56so2488352wes.21 for ; Fri, 13 Jun 2014 03:26:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:reply-to:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=yK8H6WMUe+Hpft1CCAIFgWPVzo5LYK5aFKAPlTd17rg=; b=cxCKCF9lzITVQ5og4FM9fgLmLYAAVpOAXadSRrDDY7IKFLAxajqrI5M2EqeYOpekOE wESEbp7o175YTpPP1+9PN1WvTmxHcBS4a93LesUsmSCrVCE47vjOh6hfTQ5kEc8oFVUE 5WIBZRYl1elhcA174lzRns7EgSH4kFUMcogo3zZidA9zbRS9reEx1A/9uME98W9S24Pe 1yolwcTRuKc6+yDAllR14nlFzZ88PjbkERvlIHip/m8gZPc1948tui92cT01pjksIqKd uFihqCkk9+GyYRCv/wjKhcMHi/mlPhbw+IjyNHzflnCnWwdnU6+9R2nDebfrUTKQeyle H2CA== X-Received: by 10.181.8.67 with SMTP id di3mr3505544wid.8.1402655212533; Fri, 13 Jun 2014 03:26:52 -0700 (PDT) Received: from [172.16.25.10] (97e5a5cd.skybroadband.com. [151.229.165.205]) by mx.google.com with ESMTPSA id r5sm5247026wjq.26.2014.06.13.03.26.50 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 13 Jun 2014 03:26:51 -0700 (PDT) Message-ID: <539AD1E9.7070606@xen.org> Date: Fri, 13 Jun 2014 11:26:49 +0100 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: Anil Madhavapeddy References: <53987F9F.6010907@xen.org> <7CC65A9C-45F9-4E6C-A6D3-FD83A6C472C7@recoil.org> In-Reply-To: <7CC65A9C-45F9-4E6C-A6D3-FD83A6C472C7@recoil.org> Cc: Sarah Conway , "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Mirage OS 2.0 (or next) for OSCON? X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: lars.kurth@xen.org 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 Anil, in that case I will pull Sarah in. And we need to get going: OSCON is only a few weeks away OSCON is a great opportunity for a release as there will be press. Who do we need to pull in for putting PR together Are there any significant new contributors that came to the project? Are there any Portland local contributors (some of the Galois folks spring to mind) Etc Regards Lars On 11/06/2014 17:26, Anil Madhavapeddy wrote: > On 11 Jun 2014, at 17:11, Lars Kurth wrote: > >> Hi all, >> I saw that Anil submitted a Mirage OS 2.0 talk for the Developer Summit. I was wondering what the plans for the next release were. If it is around Dev Summit time, you should probably start coordinating with me and Sarah > We were just chatting about this yesterday in the call! http://openmirage.org/wiki/weekly-2014-06-10 > > The emerging plan for the OSCON Mirage 2.0 release is to have three key features: > > - the Xen/ARM port (lead: Thomas Leonard) > - Irmin storage integration (lead: Thomas Gazagnaire, Xenstore lead: Dave Scott) > - Name resolver for distributed computation (lead: Anil Madhavapeddy) > > All of these look in reasonable shape to get released by mid-July, although the release announcement could probably use a week or two to let the features sit in-tree before we tell everyone about it. > > Anyone have anything else on the stack? There are minor things such as 'add s-expression tracing' that can be done on an ongoing basis. > > 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 Jun 13 10:26:56 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 13 Jun 2014 10:26: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 1WvOhE-0000Sr-AZ; Fri, 13 Jun 2014 10:26:56 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WvOhC-0000Sh-8r for mirageos-devel@lists.xenproject.org; Fri, 13 Jun 2014 10:26:54 +0000 Received: from [193.109.254.147:44632] by server-3.bemta-14.messagelabs.com id 05/7B-22179-DE1DA935; Fri, 13 Jun 2014 10:26:53 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-14.tower-27.messagelabs.com!1402655212!11038878!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.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7578 invoked from network); 13 Jun 2014 10:26:52 -0000 Received: from mail-we0-f176.google.com (HELO mail-we0-f176.google.com) (74.125.82.176) by server-14.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 13 Jun 2014 10:26:52 -0000 Received: by mail-we0-f176.google.com with SMTP id u56so2488352wes.21 for ; Fri, 13 Jun 2014 03:26:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:reply-to:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=yK8H6WMUe+Hpft1CCAIFgWPVzo5LYK5aFKAPlTd17rg=; b=cxCKCF9lzITVQ5og4FM9fgLmLYAAVpOAXadSRrDDY7IKFLAxajqrI5M2EqeYOpekOE wESEbp7o175YTpPP1+9PN1WvTmxHcBS4a93LesUsmSCrVCE47vjOh6hfTQ5kEc8oFVUE 5WIBZRYl1elhcA174lzRns7EgSH4kFUMcogo3zZidA9zbRS9reEx1A/9uME98W9S24Pe 1yolwcTRuKc6+yDAllR14nlFzZ88PjbkERvlIHip/m8gZPc1948tui92cT01pjksIqKd uFihqCkk9+GyYRCv/wjKhcMHi/mlPhbw+IjyNHzflnCnWwdnU6+9R2nDebfrUTKQeyle H2CA== X-Received: by 10.181.8.67 with SMTP id di3mr3505544wid.8.1402655212533; Fri, 13 Jun 2014 03:26:52 -0700 (PDT) Received: from [172.16.25.10] (97e5a5cd.skybroadband.com. [151.229.165.205]) by mx.google.com with ESMTPSA id r5sm5247026wjq.26.2014.06.13.03.26.50 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 13 Jun 2014 03:26:51 -0700 (PDT) Message-ID: <539AD1E9.7070606@xen.org> Date: Fri, 13 Jun 2014 11:26:49 +0100 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: Anil Madhavapeddy References: <53987F9F.6010907@xen.org> <7CC65A9C-45F9-4E6C-A6D3-FD83A6C472C7@recoil.org> In-Reply-To: <7CC65A9C-45F9-4E6C-A6D3-FD83A6C472C7@recoil.org> Cc: Sarah Conway , "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Mirage OS 2.0 (or next) for OSCON? X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: lars.kurth@xen.org 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 Anil, in that case I will pull Sarah in. And we need to get going: OSCON is only a few weeks away OSCON is a great opportunity for a release as there will be press. Who do we need to pull in for putting PR together Are there any significant new contributors that came to the project? Are there any Portland local contributors (some of the Galois folks spring to mind) Etc Regards Lars On 11/06/2014 17:26, Anil Madhavapeddy wrote: > On 11 Jun 2014, at 17:11, Lars Kurth wrote: > >> Hi all, >> I saw that Anil submitted a Mirage OS 2.0 talk for the Developer Summit. I was wondering what the plans for the next release were. If it is around Dev Summit time, you should probably start coordinating with me and Sarah > We were just chatting about this yesterday in the call! http://openmirage.org/wiki/weekly-2014-06-10 > > The emerging plan for the OSCON Mirage 2.0 release is to have three key features: > > - the Xen/ARM port (lead: Thomas Leonard) > - Irmin storage integration (lead: Thomas Gazagnaire, Xenstore lead: Dave Scott) > - Name resolver for distributed computation (lead: Anil Madhavapeddy) > > All of these look in reasonable shape to get released by mid-July, although the release announcement could probably use a week or two to let the features sit in-tree before we tell everyone about it. > > Anyone have anything else on the stack? There are minor things such as 'add s-expression tracing' that can be done on an ongoing basis. > > 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 Jun 13 10:29:45 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 13 Jun 2014 10:29: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 1WvOjw-0000WJ-JF; Fri, 13 Jun 2014 10:29:44 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WvOjv-0000WE-1x for mirageos-devel@lists.xenproject.org; Fri, 13 Jun 2014 10:29:43 +0000 Received: from [85.158.139.211:38390] by server-2.bemta-5.messagelabs.com id AA/02-01647-692DA935; Fri, 13 Jun 2014 10:29:42 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-8.tower-206.messagelabs.com!1402655381!9756298!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31489 invoked from network); 13 Jun 2014 10:29:41 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-8.tower-206.messagelabs.com with SMTP; 13 Jun 2014 10:29:41 -0000 Received: (qmail 24670 invoked by uid 634); 13 Jun 2014 10:29:41 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net (HELO [192.168.1.62]) (86.30.244.239) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Fri, 13 Jun 2014 11:29:40 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\)) From: Anil Madhavapeddy In-Reply-To: Date: Fri, 13 Jun 2014 11:29:39 +0100 Message-Id: References: , <0846576A-E0E8-4F35-99FA-6729250975B5@recoil.org>, <5373900A.4030901@cam.ac.uk>, <9AF01405-3475-4FC7-A308-4075DE335BEF@recoil.org>, <53739693.2050308@cam.ac.uk>, <0E252CC1-CF37-4611-B633-D427E2051B7D@recoil.org>, , <4E8A3FB1-5F4E-4BDC-A071-8F83730AF610@citrix.com>, <25EA0DB9-6DA8-4C6F-BAD9-587D3CEC4D55@recoil.org> To: buzz heavyyear X-Mailer: Apple Mail (2.1874) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: David Scott , John Else , "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Monitoring MirageOS guests on CubieBoard2 X-BeenThere: mirageos-devel@lists.xenproject.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 13 Jun 2014, at 11:26, buzz heavyyear wrote: > > > For the Mirage 2.0 release, I expect that ensuring that we have the right primitives in place (xenstore+vchan) for an RRD library to plug into would be safest. The rest can follow as a normal library update. > > Top dollar! > > > Nick: do you have any particular use-cases in mind on ARM that might guide this integration? I'm primarily interested in RRD as a scoreboard for tracking stats like network stack connections and load counters. As we disaggregate more of dom0 into unikernels, having these trace points becomes increasingly important. > > Like you, I'm definitely after tracking stats; also concerned over poorly written application code which blows up and needs to be safely recovered - intend to tack on various sensors to the cubieboard, monitor the process and if there is data-overload, safely deal with it. This all sounds right in scope. The medium-term goal is to sample the RRD stats into the Irmin git backend (https://github.com/mirage/irmin) that Thomas Gazagnaire is working on. This will let applications have a non-blocking stats delivery model via RRD, and still provide a persistent data structure for long-term accrual of data (e.g. via Git pushing to an aggregation server that isn't a tiny embedded device). I did ponder exposing this via SNMP, and then ran away screaming when I looked at the protocol description after some time away for it. Let's put that down as a 'future feature' :-) > This really is a tremendous environment for small board solutions. Thanks to everyone for make this available. > > I'm definitely not worthy. You most definitely are! Very much looking forward to seeing what uses you put it to. 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 Jun 13 10:29:45 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 13 Jun 2014 10:29: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 1WvOjw-0000WJ-JF; Fri, 13 Jun 2014 10:29:44 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WvOjv-0000WE-1x for mirageos-devel@lists.xenproject.org; Fri, 13 Jun 2014 10:29:43 +0000 Received: from [85.158.139.211:38390] by server-2.bemta-5.messagelabs.com id AA/02-01647-692DA935; Fri, 13 Jun 2014 10:29:42 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-8.tower-206.messagelabs.com!1402655381!9756298!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31489 invoked from network); 13 Jun 2014 10:29:41 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-8.tower-206.messagelabs.com with SMTP; 13 Jun 2014 10:29:41 -0000 Received: (qmail 24670 invoked by uid 634); 13 Jun 2014 10:29:41 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net (HELO [192.168.1.62]) (86.30.244.239) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Fri, 13 Jun 2014 11:29:40 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\)) From: Anil Madhavapeddy In-Reply-To: Date: Fri, 13 Jun 2014 11:29:39 +0100 Message-Id: References: , <0846576A-E0E8-4F35-99FA-6729250975B5@recoil.org>, <5373900A.4030901@cam.ac.uk>, <9AF01405-3475-4FC7-A308-4075DE335BEF@recoil.org>, <53739693.2050308@cam.ac.uk>, <0E252CC1-CF37-4611-B633-D427E2051B7D@recoil.org>, , <4E8A3FB1-5F4E-4BDC-A071-8F83730AF610@citrix.com>, <25EA0DB9-6DA8-4C6F-BAD9-587D3CEC4D55@recoil.org> To: buzz heavyyear X-Mailer: Apple Mail (2.1874) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: David Scott , John Else , "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Monitoring MirageOS guests on CubieBoard2 X-BeenThere: mirageos-devel@lists.xenproject.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 13 Jun 2014, at 11:26, buzz heavyyear wrote: > > > For the Mirage 2.0 release, I expect that ensuring that we have the right primitives in place (xenstore+vchan) for an RRD library to plug into would be safest. The rest can follow as a normal library update. > > Top dollar! > > > Nick: do you have any particular use-cases in mind on ARM that might guide this integration? I'm primarily interested in RRD as a scoreboard for tracking stats like network stack connections and load counters. As we disaggregate more of dom0 into unikernels, having these trace points becomes increasingly important. > > Like you, I'm definitely after tracking stats; also concerned over poorly written application code which blows up and needs to be safely recovered - intend to tack on various sensors to the cubieboard, monitor the process and if there is data-overload, safely deal with it. This all sounds right in scope. The medium-term goal is to sample the RRD stats into the Irmin git backend (https://github.com/mirage/irmin) that Thomas Gazagnaire is working on. This will let applications have a non-blocking stats delivery model via RRD, and still provide a persistent data structure for long-term accrual of data (e.g. via Git pushing to an aggregation server that isn't a tiny embedded device). I did ponder exposing this via SNMP, and then ran away screaming when I looked at the protocol description after some time away for it. Let's put that down as a 'future feature' :-) > This really is a tremendous environment for small board solutions. Thanks to everyone for make this available. > > I'm definitely not worthy. You most definitely are! Very much looking forward to seeing what uses you put it to. 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 Jun 13 11:02:24 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 13 Jun 2014 11:02: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 1WvPFV-0000eK-VF; Fri, 13 Jun 2014 11:02:21 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WvPFU-0000eF-7C for mirageos-devel@lists.xenproject.org; Fri, 13 Jun 2014 11:02:20 +0000 Received: from [193.109.254.147:61891] by server-9.bemta-14.messagelabs.com id 87/BD-03644-B3ADA935; Fri, 13 Jun 2014 11:02:19 +0000 X-Env-Sender: Dave.Scott@citrix.com X-Msg-Ref: server-4.tower-27.messagelabs.com!1402657338!11058235!1 X-Originating-IP: [185.25.65.24] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 340 invoked from network); 13 Jun 2014 11:02:18 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (185.25.65.24) by server-4.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 13 Jun 2014 11:02:18 -0000 X-IronPort-AV: E=Sophos;i="5.01,471,1400025600"; d="scan'208";a="21179454" Received: from unknown (HELO AMSPEX01CL02.citrite.net) ([10.69.60.9]) by AMSPIP01.EU.Citrix.com with ESMTP; 13 Jun 2014 11:02:18 +0000 Received: from AMSPEX01CL03.citrite.net ([169.254.8.89]) by AMSPEX01CL02.citrite.net ([10.69.46.33]) with mapi id 14.03.0181.006; Fri, 13 Jun 2014 13:02:18 +0200 From: Dave Scott To: Anil Madhavapeddy Thread-Topic: [MirageOS-devel] towards a common Mirage 'FLOW' signature Thread-Index: AQHPhn5se25anOhs8kKSi+zLRqL4cJtutVmAgAAKBQA= Date: Fri, 13 Jun 2014 11:02:16 +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: x-originating-ip: [10.69.46.1] Content-ID: <9FF03DB5FF2E9C41AC4128E6ECEA1F64@citrix.com> MIME-Version: 1.0 X-DLP: AMS1 Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] towards a common Mirage 'FLOW' signature X-BeenThere: mirageos-devel@lists.xenproject.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, On 13 Jun 2014, at 11:26, Anil Madhavapeddy wrote: > On 12 Jun 2014, at 21:38, David Scott wrote: > = >> Hi, >> = >> I'd like to create a common Mirage 'FLOW' signature to represent reading= and writing along some kind of 'connection'. I think we could satisfy the = signature in multiple places including at least >> = >> * consoles >> * xen inter-domain vchan connections >> * plain TCP >> * (hopefully) TLS connections >> = >> It would be nice to write clients and servers which would work over mult= iple FLOW implementations. >> = >> For discussion I've extracted the 'FLOW' from 'TCPv4' to show you what i= t would look like: >> = >> https://github.com/djs55/mirage/commit/87f9855f22f997264870f903c998b1d92= 186fdef >> = >> In V2 of the API I'd like to turn the CONSOLE signature into a combinati= on of DEVICE and FLOW. > = > This looks good to me. The one caveat is why write cannot return an erro= r in the existing API. It is possible for the lower-level transport to sig= nal a hard error, although we rarely do so at the moment. In the interests= of future compatibility, should we make that change? That=92s a good point =97 I can certainly imagine a hard error being report= ed (something like ECONNRESET?) How about this for a plan: 1. I=92ll make a pull request for types V1 to add a FLOW, with errors on wr= ites, which isn=92t used anywhere and so shouldn=92t break anything (unless= the name FLOW shadows some other signature) 2. I=92ll start making a list of API breaking changes we want to make for V= 2, including using FLOW everywhere (which means modifying all the write() f= unctions). Perhaps I=92ll start writing a V2 module? > = >> I notice the low-level network APIs (NETWORK, ETHIF, ...) are *almost* l= ike this except they have a function like >> = >> val listen: t -> udp:callback -> tcp:callback -> ... = >> = >> Perhaps later (V2, V3?) we could split this into something like a = >> = >> val read: t -> buffer (* satisfy FLOW *) >> val classify: buffer -> [ `UDP; `TCP ] >> = >> -- is that a good idea? > = > I don't think the listen function should be in the FLOW signature at all,= since this is part of the resolver API that establishes connections. > = > This is compatible with your patch, since the network APIs can "include F= LOW" and define the additional connection-specific functions without issue. Great. Cheers, Dave > = > cheers, > Anil > _______________________________________________ > 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 Jun 13 11:02:24 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 13 Jun 2014 11:02: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 1WvPFV-0000eK-VF; Fri, 13 Jun 2014 11:02:21 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WvPFU-0000eF-7C for mirageos-devel@lists.xenproject.org; Fri, 13 Jun 2014 11:02:20 +0000 Received: from [193.109.254.147:61891] by server-9.bemta-14.messagelabs.com id 87/BD-03644-B3ADA935; Fri, 13 Jun 2014 11:02:19 +0000 X-Env-Sender: Dave.Scott@citrix.com X-Msg-Ref: server-4.tower-27.messagelabs.com!1402657338!11058235!1 X-Originating-IP: [185.25.65.24] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 340 invoked from network); 13 Jun 2014 11:02:18 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (185.25.65.24) by server-4.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 13 Jun 2014 11:02:18 -0000 X-IronPort-AV: E=Sophos;i="5.01,471,1400025600"; d="scan'208";a="21179454" Received: from unknown (HELO AMSPEX01CL02.citrite.net) ([10.69.60.9]) by AMSPIP01.EU.Citrix.com with ESMTP; 13 Jun 2014 11:02:18 +0000 Received: from AMSPEX01CL03.citrite.net ([169.254.8.89]) by AMSPEX01CL02.citrite.net ([10.69.46.33]) with mapi id 14.03.0181.006; Fri, 13 Jun 2014 13:02:18 +0200 From: Dave Scott To: Anil Madhavapeddy Thread-Topic: [MirageOS-devel] towards a common Mirage 'FLOW' signature Thread-Index: AQHPhn5se25anOhs8kKSi+zLRqL4cJtutVmAgAAKBQA= Date: Fri, 13 Jun 2014 11:02:16 +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: x-originating-ip: [10.69.46.1] Content-ID: <9FF03DB5FF2E9C41AC4128E6ECEA1F64@citrix.com> MIME-Version: 1.0 X-DLP: AMS1 Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] towards a common Mirage 'FLOW' signature X-BeenThere: mirageos-devel@lists.xenproject.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, On 13 Jun 2014, at 11:26, Anil Madhavapeddy wrote: > On 12 Jun 2014, at 21:38, David Scott wrote: > = >> Hi, >> = >> I'd like to create a common Mirage 'FLOW' signature to represent reading= and writing along some kind of 'connection'. I think we could satisfy the = signature in multiple places including at least >> = >> * consoles >> * xen inter-domain vchan connections >> * plain TCP >> * (hopefully) TLS connections >> = >> It would be nice to write clients and servers which would work over mult= iple FLOW implementations. >> = >> For discussion I've extracted the 'FLOW' from 'TCPv4' to show you what i= t would look like: >> = >> https://github.com/djs55/mirage/commit/87f9855f22f997264870f903c998b1d92= 186fdef >> = >> In V2 of the API I'd like to turn the CONSOLE signature into a combinati= on of DEVICE and FLOW. > = > This looks good to me. The one caveat is why write cannot return an erro= r in the existing API. It is possible for the lower-level transport to sig= nal a hard error, although we rarely do so at the moment. In the interests= of future compatibility, should we make that change? That=92s a good point =97 I can certainly imagine a hard error being report= ed (something like ECONNRESET?) How about this for a plan: 1. I=92ll make a pull request for types V1 to add a FLOW, with errors on wr= ites, which isn=92t used anywhere and so shouldn=92t break anything (unless= the name FLOW shadows some other signature) 2. I=92ll start making a list of API breaking changes we want to make for V= 2, including using FLOW everywhere (which means modifying all the write() f= unctions). Perhaps I=92ll start writing a V2 module? > = >> I notice the low-level network APIs (NETWORK, ETHIF, ...) are *almost* l= ike this except they have a function like >> = >> val listen: t -> udp:callback -> tcp:callback -> ... = >> = >> Perhaps later (V2, V3?) we could split this into something like a = >> = >> val read: t -> buffer (* satisfy FLOW *) >> val classify: buffer -> [ `UDP; `TCP ] >> = >> -- is that a good idea? > = > I don't think the listen function should be in the FLOW signature at all,= since this is part of the resolver API that establishes connections. > = > This is compatible with your patch, since the network APIs can "include F= LOW" and define the additional connection-specific functions without issue. Great. Cheers, Dave > = > cheers, > Anil > _______________________________________________ > 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 Jun 13 11:06:55 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 13 Jun 2014 11:06: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 1WvPJv-0000in-NX; Fri, 13 Jun 2014 11:06:55 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WvPJu-0000id-C7 for mirageos-devel@lists.xenproject.org; Fri, 13 Jun 2014 11:06:54 +0000 Received: from [85.158.137.68:12059] by server-13.bemta-3.messagelabs.com id A9/17-18692-D4BDA935; Fri, 13 Jun 2014 11:06:53 +0000 X-Env-Sender: avsm@dark.recoil.org X-Msg-Ref: server-5.tower-31.messagelabs.com!1402657613!9905796!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17679 invoked from network); 13 Jun 2014 11:06:53 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-5.tower-31.messagelabs.com with SMTP; 13 Jun 2014 11:06:53 -0000 Received: (qmail 2772 invoked by uid 10000); 13 Jun 2014 11:06:52 -0000 Date: Fri, 13 Jun 2014 12:06:52 +0100 From: Anil Madhavapeddy To: Dave Scott Message-ID: <20140613110652.GC31126@dark.recoil.org> References: MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] towards a common Mirage 'FLOW' signature X-BeenThere: mirageos-devel@lists.xenproject.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 Fri, Jun 13, 2014 at 11:02:16AM +0000, Dave Scott wrote: > Hi, > >> https://github.com/djs55/mirage/commit/87f9855f22f997264870f903c998b1d92186fdef > >> > >> In V2 of the API I'd like to turn the CONSOLE signature into a combination of DEVICE and FLOW. > > > > This looks good to me. The one caveat is why write cannot return an > > error in the existing API. It is possible for the lower-level > > transport to signal a hard error, although we rarely do so at the > > moment. In the interests of future compatibility, should we make that > > change? > > That?s a good point ? I can certainly imagine a hard error being > reported (something like ECONNRESET?) > > How about this for a plan: > > 1. I?ll make a pull request for types V1 to add a FLOW, with errors on > writes, which isn?t used anywhere and so shouldn?t break anything > (unless the name FLOW shadows some other signature) > > 2. I?ll start making a list of API breaking changes we want to make for > V2, including using FLOW everywhere (which means modifying all the > write() functions). Perhaps I?ll start writing a V2 module? Sounds good to me -- there's no reason why we can't just work on the V2 module types in trunk. -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 Jun 13 11:06:55 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 13 Jun 2014 11:06: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 1WvPJv-0000in-NX; Fri, 13 Jun 2014 11:06:55 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WvPJu-0000id-C7 for mirageos-devel@lists.xenproject.org; Fri, 13 Jun 2014 11:06:54 +0000 Received: from [85.158.137.68:12059] by server-13.bemta-3.messagelabs.com id A9/17-18692-D4BDA935; Fri, 13 Jun 2014 11:06:53 +0000 X-Env-Sender: avsm@dark.recoil.org X-Msg-Ref: server-5.tower-31.messagelabs.com!1402657613!9905796!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17679 invoked from network); 13 Jun 2014 11:06:53 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-5.tower-31.messagelabs.com with SMTP; 13 Jun 2014 11:06:53 -0000 Received: (qmail 2772 invoked by uid 10000); 13 Jun 2014 11:06:52 -0000 Date: Fri, 13 Jun 2014 12:06:52 +0100 From: Anil Madhavapeddy To: Dave Scott Message-ID: <20140613110652.GC31126@dark.recoil.org> References: MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] towards a common Mirage 'FLOW' signature X-BeenThere: mirageos-devel@lists.xenproject.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 Fri, Jun 13, 2014 at 11:02:16AM +0000, Dave Scott wrote: > Hi, > >> https://github.com/djs55/mirage/commit/87f9855f22f997264870f903c998b1d92186fdef > >> > >> In V2 of the API I'd like to turn the CONSOLE signature into a combination of DEVICE and FLOW. > > > > This looks good to me. The one caveat is why write cannot return an > > error in the existing API. It is possible for the lower-level > > transport to signal a hard error, although we rarely do so at the > > moment. In the interests of future compatibility, should we make that > > change? > > That?s a good point ? I can certainly imagine a hard error being > reported (something like ECONNRESET?) > > How about this for a plan: > > 1. I?ll make a pull request for types V1 to add a FLOW, with errors on > writes, which isn?t used anywhere and so shouldn?t break anything > (unless the name FLOW shadows some other signature) > > 2. I?ll start making a list of API breaking changes we want to make for > V2, including using FLOW everywhere (which means modifying all the > write() functions). Perhaps I?ll start writing a V2 module? Sounds good to me -- there's no reason why we can't just work on the V2 module types in trunk. -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 Jun 13 14:10:32 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 13 Jun 2014 14:10: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 1WvSBY-00087U-9p; Fri, 13 Jun 2014 14:10:28 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WvSBW-00087K-AO for mirageos-devel@lists.xenproject.org; Fri, 13 Jun 2014 14:10:26 +0000 Received: from [85.158.137.68:7703] by server-6.bemta-3.messagelabs.com id CC/EB-00470-1560B935; Fri, 13 Jun 2014 14:10:25 +0000 X-Env-Sender: scott.dj@gmail.com X-Msg-Ref: server-13.tower-31.messagelabs.com!1402668622!9963707!1 X-Originating-IP: [209.85.192.181] X-SpamReason: No, hits=0.9 required=7.0 tests=HTML_40_50,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31012 invoked from network); 13 Jun 2014 14:10:24 -0000 Received: from mail-pd0-f181.google.com (HELO mail-pd0-f181.google.com) (209.85.192.181) by server-13.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 13 Jun 2014 14:10:24 -0000 Received: by mail-pd0-f181.google.com with SMTP id v10so1278338pde.26 for ; Fri, 13 Jun 2014 07:10:22 -0700 (PDT) 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=+m0v7Tir68cJp7ZZic06vY5E4YX2DFSU/Icrh4jD6wI=; b=bZcUlnge6C+W17shUnAwoWtpmnHOiyCAfzOyu9OqeCGUAJ/JMqLg4o8abS2NcAxT1x c6pS1wVH4rDPSZzxq87v67tjuhYh6OrZN6H/wv+fMPIqPyPbX9MxntU3gqaMOqjGs+Z6 Sh0xPBJRdvkVClXH1BFnmd+mEML85fJWOjy3jFVBT4M5tM7HRTahRIo/4Sqq5oFYos0r UmW2bui8viwoRmXzM1F90tiPYWhslysE54RxbpgNZNA/WlpEO8gxHKyZdTNyhNFYjmdi woU65h3jmGByw4ZZQL4BFjztHmJx7E47yM3cDO9kRQ8YNYdKmA84M09EqCp9QsGyKORC Fiiw== MIME-Version: 1.0 X-Received: by 10.68.130.6 with SMTP id oa6mr3684301pbb.102.1402668621983; Fri, 13 Jun 2014 07:10:21 -0700 (PDT) Received: by 10.70.11.65 with HTTP; Fri, 13 Jun 2014 07:10:21 -0700 (PDT) In-Reply-To: <20140613110652.GC31126@dark.recoil.org> References: <20140613110652.GC31126@dark.recoil.org> Date: Fri, 13 Jun 2014 15:10:21 +0100 Message-ID: From: David Scott To: Anil Madhavapeddy Cc: Dave Scott , "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] towards a common Mirage 'FLOW' signature X-BeenThere: mirageos-devel@lists.xenproject.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="===============1657854841269322031==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============1657854841269322031== Content-Type: multipart/alternative; boundary=e89a8ffbaecbf3792304fbb83c83 --e89a8ffbaecbf3792304fbb83c83 Content-Type: text/plain; charset=UTF-8 On Fri, Jun 13, 2014 at 12:06 PM, Anil Madhavapeddy wrote: > On Fri, Jun 13, 2014 at 11:02:16AM +0000, Dave Scott wrote: > > Hi, > > >> > https://github.com/djs55/mirage/commit/87f9855f22f997264870f903c998b1d92186fdef > > >> > > >> In V2 of the API I'd like to turn the CONSOLE signature into a > combination of DEVICE and FLOW. > > > > > > This looks good to me. The one caveat is why write cannot return an > > > error in the existing API. It is possible for the lower-level > > > transport to signal a hard error, although we rarely do so at the > > > moment. In the interests of future compatibility, should we make that > > > change? > > > > That?s a good point ? I can certainly imagine a hard error being > > reported (something like ECONNRESET?) > > > > How about this for a plan: > > > > 1. I?ll make a pull request for types V1 to add a FLOW, with errors on > > writes, which isn?t used anywhere and so shouldn?t break anything > > (unless the name FLOW shadows some other signature) > > > > 2. I?ll start making a list of API breaking changes we want to make for > > V2, including using FLOW everywhere (which means modifying all the > > write() functions). Perhaps I?ll start writing a V2 module? > > Sounds good to me -- there's no reason why we can't just work on the V2 > module types in trunk. > OK, I've made the following pull request which adds a FLOW signature. Note the 'write' and 'writev' now return [`Ok of unit | `Eof | `Error of error ] https://github.com/mirage/mirage/pull/248 Cheers, Dave --e89a8ffbaecbf3792304fbb83c83 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable



On Fri, Jun 13, 2014 at 12:06 PM, Anil Madhavapeddy <anil@recoil.org= > wrote:
On Fri, Jun 13, 2014 at 11:02:16AM +0000, Dave Scott wrote= :
> Hi,
> >> https://gi= thub.com/djs55/mirage/commit/87f9855f22f997264870f903c998b1d92186fdef > >>
> >> In V2 of the API I'd like to turn the CONSOLE signature i= nto a combination of DEVICE and FLOW.
> >
> > This looks good to me. =C2=A0The one caveat is why write cannot r= eturn an
> > error in the existing API. =C2=A0It is possible for the lower-lev= el
> > transport to signal a hard error, although we rarely do so at the=
> > moment. =C2=A0In the interests of future compatibility, should we= make that
> > change?
>
> That?s a good point ? I can certainly imagine a hard error being=
> reported (something like ECONNRESET?)
>
> How about this for a plan:
>
> 1. I?ll make a pull request for types V1 to add a FLOW, with err= ors on
> writes, which isn?t used anywhere and so shouldn?t break anything
> (unless the name FLOW shadows some other signature) >
> 2. I?ll start making a list of API breaking changes we want to m= ake for
> V2, including using FLOW everywhere (which means modif= ying all the
> write() functions). Perhaps I?ll start writing a V2 module?

Sounds good to me -- there's no reason why we can't just work on th= e V2
module types in trunk.

OK, I've mad= e the following pull request which adds a FLOW signature. Note the 'wri= te' and 'writev' now return=C2=A0

[`Ok of unit | `Eof | `Error of error ]


Cheers,
Dave
--e89a8ffbaecbf3792304fbb83c83-- --===============1657854841269322031== 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 --===============1657854841269322031==-- From mirageos-devel-bounces@lists.xenproject.org Fri Jun 13 14:10:32 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 13 Jun 2014 14:10: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 1WvSBY-00087U-9p; Fri, 13 Jun 2014 14:10:28 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WvSBW-00087K-AO for mirageos-devel@lists.xenproject.org; Fri, 13 Jun 2014 14:10:26 +0000 Received: from [85.158.137.68:7703] by server-6.bemta-3.messagelabs.com id CC/EB-00470-1560B935; Fri, 13 Jun 2014 14:10:25 +0000 X-Env-Sender: scott.dj@gmail.com X-Msg-Ref: server-13.tower-31.messagelabs.com!1402668622!9963707!1 X-Originating-IP: [209.85.192.181] X-SpamReason: No, hits=0.9 required=7.0 tests=HTML_40_50,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31012 invoked from network); 13 Jun 2014 14:10:24 -0000 Received: from mail-pd0-f181.google.com (HELO mail-pd0-f181.google.com) (209.85.192.181) by server-13.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 13 Jun 2014 14:10:24 -0000 Received: by mail-pd0-f181.google.com with SMTP id v10so1278338pde.26 for ; Fri, 13 Jun 2014 07:10:22 -0700 (PDT) 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=+m0v7Tir68cJp7ZZic06vY5E4YX2DFSU/Icrh4jD6wI=; b=bZcUlnge6C+W17shUnAwoWtpmnHOiyCAfzOyu9OqeCGUAJ/JMqLg4o8abS2NcAxT1x c6pS1wVH4rDPSZzxq87v67tjuhYh6OrZN6H/wv+fMPIqPyPbX9MxntU3gqaMOqjGs+Z6 Sh0xPBJRdvkVClXH1BFnmd+mEML85fJWOjy3jFVBT4M5tM7HRTahRIo/4Sqq5oFYos0r UmW2bui8viwoRmXzM1F90tiPYWhslysE54RxbpgNZNA/WlpEO8gxHKyZdTNyhNFYjmdi woU65h3jmGByw4ZZQL4BFjztHmJx7E47yM3cDO9kRQ8YNYdKmA84M09EqCp9QsGyKORC Fiiw== MIME-Version: 1.0 X-Received: by 10.68.130.6 with SMTP id oa6mr3684301pbb.102.1402668621983; Fri, 13 Jun 2014 07:10:21 -0700 (PDT) Received: by 10.70.11.65 with HTTP; Fri, 13 Jun 2014 07:10:21 -0700 (PDT) In-Reply-To: <20140613110652.GC31126@dark.recoil.org> References: <20140613110652.GC31126@dark.recoil.org> Date: Fri, 13 Jun 2014 15:10:21 +0100 Message-ID: From: David Scott To: Anil Madhavapeddy Cc: Dave Scott , "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] towards a common Mirage 'FLOW' signature X-BeenThere: mirageos-devel@lists.xenproject.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="===============1657854841269322031==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============1657854841269322031== Content-Type: multipart/alternative; boundary=e89a8ffbaecbf3792304fbb83c83 --e89a8ffbaecbf3792304fbb83c83 Content-Type: text/plain; charset=UTF-8 On Fri, Jun 13, 2014 at 12:06 PM, Anil Madhavapeddy wrote: > On Fri, Jun 13, 2014 at 11:02:16AM +0000, Dave Scott wrote: > > Hi, > > >> > https://github.com/djs55/mirage/commit/87f9855f22f997264870f903c998b1d92186fdef > > >> > > >> In V2 of the API I'd like to turn the CONSOLE signature into a > combination of DEVICE and FLOW. > > > > > > This looks good to me. The one caveat is why write cannot return an > > > error in the existing API. It is possible for the lower-level > > > transport to signal a hard error, although we rarely do so at the > > > moment. In the interests of future compatibility, should we make that > > > change? > > > > That?s a good point ? I can certainly imagine a hard error being > > reported (something like ECONNRESET?) > > > > How about this for a plan: > > > > 1. I?ll make a pull request for types V1 to add a FLOW, with errors on > > writes, which isn?t used anywhere and so shouldn?t break anything > > (unless the name FLOW shadows some other signature) > > > > 2. I?ll start making a list of API breaking changes we want to make for > > V2, including using FLOW everywhere (which means modifying all the > > write() functions). Perhaps I?ll start writing a V2 module? > > Sounds good to me -- there's no reason why we can't just work on the V2 > module types in trunk. > OK, I've made the following pull request which adds a FLOW signature. Note the 'write' and 'writev' now return [`Ok of unit | `Eof | `Error of error ] https://github.com/mirage/mirage/pull/248 Cheers, Dave --e89a8ffbaecbf3792304fbb83c83 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable



On Fri, Jun 13, 2014 at 12:06 PM, Anil Madhavapeddy <anil@recoil.org= > wrote:
On Fri, Jun 13, 2014 at 11:02:16AM +0000, Dave Scott wrote= :
> Hi,
> >> https://gi= thub.com/djs55/mirage/commit/87f9855f22f997264870f903c998b1d92186fdef > >>
> >> In V2 of the API I'd like to turn the CONSOLE signature i= nto a combination of DEVICE and FLOW.
> >
> > This looks good to me. =C2=A0The one caveat is why write cannot r= eturn an
> > error in the existing API. =C2=A0It is possible for the lower-lev= el
> > transport to signal a hard error, although we rarely do so at the=
> > moment. =C2=A0In the interests of future compatibility, should we= make that
> > change?
>
> That?s a good point ? I can certainly imagine a hard error being=
> reported (something like ECONNRESET?)
>
> How about this for a plan:
>
> 1. I?ll make a pull request for types V1 to add a FLOW, with err= ors on
> writes, which isn?t used anywhere and so shouldn?t break anything
> (unless the name FLOW shadows some other signature) >
> 2. I?ll start making a list of API breaking changes we want to m= ake for
> V2, including using FLOW everywhere (which means modif= ying all the
> write() functions). Perhaps I?ll start writing a V2 module?

Sounds good to me -- there's no reason why we can't just work on th= e V2
module types in trunk.

OK, I've mad= e the following pull request which adds a FLOW signature. Note the 'wri= te' and 'writev' now return=C2=A0

[`Ok of unit | `Eof | `Error of error ]


Cheers,
Dave
--e89a8ffbaecbf3792304fbb83c83-- --===============1657854841269322031== 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 --===============1657854841269322031==-- From mirageos-devel-bounces@lists.xenproject.org Fri Jun 13 16:53:14 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 13 Jun 2014 16: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 1WvUiz-0002yX-81; Fri, 13 Jun 2014 16:53:09 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WvUiy-0002yS-1T for mirageos-devel@lists.xenproject.org; Fri, 13 Jun 2014 16:53:08 +0000 Received: from [85.158.143.35:40667] by server-3.bemta-4.messagelabs.com id A7/A5-13602-37C2B935; Fri, 13 Jun 2014 16:53:07 +0000 X-Env-Sender: talex5@gmail.com X-Msg-Ref: server-11.tower-21.messagelabs.com!1402678385!11225778!1 X-Originating-IP: [209.85.214.181] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, ML_RADAR_SPEW_LINKS_23,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20368 invoked from network); 13 Jun 2014 16:53:06 -0000 Received: from mail-ob0-f181.google.com (HELO mail-ob0-f181.google.com) (209.85.214.181) by server-11.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 13 Jun 2014 16:53:06 -0000 Received: by mail-ob0-f181.google.com with SMTP id wp4so3114083obc.40 for ; Fri, 13 Jun 2014 09:53:04 -0700 (PDT) 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=r9XvNeGe6tFYU9JRDTm9lVjdm/mwi+kzX0kQDQA2lrI=; b=W9g26Jn/O3IR/ZfoGVt6Zv2yp26adV+/euwoLdDy6d/T355JKL4GtvubWz14ZGTtQ8 CzJnkXtXKGPcb4zFv6CrSdBtYQzKOTNi2wnPOWatqH3TWqEZaetdXkla6moiEUUwz620 WodDzJnMBPDBLHNBRu5BlB46kNnw5HGfe1wtvcHCvnxQIJdRF5o8VjnyrnZImwc55weZ qQ7gfWvwWcr9ZtVaFN+pEUERmS+yATb3uK67cOOEYqRKRDrhbyz1FNjWihey9NaSFEoy QqyLoH8K4DYfWk0N3nAha1yqR7o/65YBIHdB5fIlh1MWNlm1VfUDgx6wfTx3alOhX5h2 oCbQ== MIME-Version: 1.0 X-Received: by 10.60.145.225 with SMTP id sx1mr3934181oeb.75.1402678384762; Fri, 13 Jun 2014 09:53:04 -0700 (PDT) Received: by 10.76.92.5 with HTTP; Fri, 13 Jun 2014 09:53:04 -0700 (PDT) In-Reply-To: References: <297FC9DB-3A4E-41A5-B00E-9DEF62C625E6@recoil.org> Date: Fri, 13 Jun 2014 17:53:04 +0100 Message-ID: From: Thomas Leonard To: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Mirage on Xen/ARM status X-BeenThere: mirageos-devel@lists.xenproject.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 been going through mirage-skeleton trying all the examples on ARM (Cubietruck running Xen). Here are the results: console: works (I also patched it to try reading from the console, and that works too, after a minor patch to mirage-console; now merged) network: works block: works dns: fails to build Error: No implementations provided for the following modules: Lwt_unix referenced from /root/.opam/4.01.0/lib/dns/lwt-core.cmxa(Dns_resolver) ethifv4: seems to work (except for TCP: it shows "TCP retransmission on timer seq = 452901213" instead of connecting) io_page: works kv_ro: works (prints YES! a lot, anyway) kv_ro_crunch: works (as kv_ro) ping: works (note: reports UDP traffic as "TCP" due to a bug) stackv4: works (HTTP on 80, TCP on 8080 and UDP on 53) static_website: works, after adding re.str. Otherwise you get: Error: No implementations provided for the following modules: Re_str referenced from dispatch.cmx So, it's looking pretty good :-) A few random notes: - Lack of progress reports from mirage is a problem on x86, but it's worse on ARM because it's so much slower. - opam got very confused at one point, somehow uninstalled mirage and then wouldn't bring it back (no error shown). Here's a sample: root@softbuild:~# mirage -bash: mirage: command not found root@softbuild:~# opam reinstall mirage [ERROR] mirage is not installed. 'opam reinstall mirage' failed. root@softbuild:~# opam install mirage root@softbuild:~# mirage -bash: mirage: command not found root@softbuild:~# opam reinstall mirage [ERROR] mirage is not installed. Installing "aspcud" sorted it all out (and makes it faster!). - I was using the system ocaml, which lacked ocamlopt.opt, slowing down the builds. Using "opam sw 4.01.0" sorted that out. - mirage-console's install rule has some problems at the moment. Use "ocamlfind remove" to remove the various bits manually and try again if it happens. https://github.com/mirage/mirage-console/issues/17 - direct_stackv4_with_default_ipv4 is a bit annoying. It contains an IP address hard-coded into mirage, but it makes it difficult to see how to change it for your own network. It might be better to use direct_stackv4_with_static_ipv4 for the examples. -- 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 Fri Jun 13 16:53:14 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 13 Jun 2014 16: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 1WvUiz-0002yX-81; Fri, 13 Jun 2014 16:53:09 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WvUiy-0002yS-1T for mirageos-devel@lists.xenproject.org; Fri, 13 Jun 2014 16:53:08 +0000 Received: from [85.158.143.35:40667] by server-3.bemta-4.messagelabs.com id A7/A5-13602-37C2B935; Fri, 13 Jun 2014 16:53:07 +0000 X-Env-Sender: talex5@gmail.com X-Msg-Ref: server-11.tower-21.messagelabs.com!1402678385!11225778!1 X-Originating-IP: [209.85.214.181] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, ML_RADAR_SPEW_LINKS_23,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20368 invoked from network); 13 Jun 2014 16:53:06 -0000 Received: from mail-ob0-f181.google.com (HELO mail-ob0-f181.google.com) (209.85.214.181) by server-11.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 13 Jun 2014 16:53:06 -0000 Received: by mail-ob0-f181.google.com with SMTP id wp4so3114083obc.40 for ; Fri, 13 Jun 2014 09:53:04 -0700 (PDT) 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=r9XvNeGe6tFYU9JRDTm9lVjdm/mwi+kzX0kQDQA2lrI=; b=W9g26Jn/O3IR/ZfoGVt6Zv2yp26adV+/euwoLdDy6d/T355JKL4GtvubWz14ZGTtQ8 CzJnkXtXKGPcb4zFv6CrSdBtYQzKOTNi2wnPOWatqH3TWqEZaetdXkla6moiEUUwz620 WodDzJnMBPDBLHNBRu5BlB46kNnw5HGfe1wtvcHCvnxQIJdRF5o8VjnyrnZImwc55weZ qQ7gfWvwWcr9ZtVaFN+pEUERmS+yATb3uK67cOOEYqRKRDrhbyz1FNjWihey9NaSFEoy QqyLoH8K4DYfWk0N3nAha1yqR7o/65YBIHdB5fIlh1MWNlm1VfUDgx6wfTx3alOhX5h2 oCbQ== MIME-Version: 1.0 X-Received: by 10.60.145.225 with SMTP id sx1mr3934181oeb.75.1402678384762; Fri, 13 Jun 2014 09:53:04 -0700 (PDT) Received: by 10.76.92.5 with HTTP; Fri, 13 Jun 2014 09:53:04 -0700 (PDT) In-Reply-To: References: <297FC9DB-3A4E-41A5-B00E-9DEF62C625E6@recoil.org> Date: Fri, 13 Jun 2014 17:53:04 +0100 Message-ID: From: Thomas Leonard To: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Mirage on Xen/ARM status X-BeenThere: mirageos-devel@lists.xenproject.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 been going through mirage-skeleton trying all the examples on ARM (Cubietruck running Xen). Here are the results: console: works (I also patched it to try reading from the console, and that works too, after a minor patch to mirage-console; now merged) network: works block: works dns: fails to build Error: No implementations provided for the following modules: Lwt_unix referenced from /root/.opam/4.01.0/lib/dns/lwt-core.cmxa(Dns_resolver) ethifv4: seems to work (except for TCP: it shows "TCP retransmission on timer seq = 452901213" instead of connecting) io_page: works kv_ro: works (prints YES! a lot, anyway) kv_ro_crunch: works (as kv_ro) ping: works (note: reports UDP traffic as "TCP" due to a bug) stackv4: works (HTTP on 80, TCP on 8080 and UDP on 53) static_website: works, after adding re.str. Otherwise you get: Error: No implementations provided for the following modules: Re_str referenced from dispatch.cmx So, it's looking pretty good :-) A few random notes: - Lack of progress reports from mirage is a problem on x86, but it's worse on ARM because it's so much slower. - opam got very confused at one point, somehow uninstalled mirage and then wouldn't bring it back (no error shown). Here's a sample: root@softbuild:~# mirage -bash: mirage: command not found root@softbuild:~# opam reinstall mirage [ERROR] mirage is not installed. 'opam reinstall mirage' failed. root@softbuild:~# opam install mirage root@softbuild:~# mirage -bash: mirage: command not found root@softbuild:~# opam reinstall mirage [ERROR] mirage is not installed. Installing "aspcud" sorted it all out (and makes it faster!). - I was using the system ocaml, which lacked ocamlopt.opt, slowing down the builds. Using "opam sw 4.01.0" sorted that out. - mirage-console's install rule has some problems at the moment. Use "ocamlfind remove" to remove the various bits manually and try again if it happens. https://github.com/mirage/mirage-console/issues/17 - direct_stackv4_with_default_ipv4 is a bit annoying. It contains an IP address hard-coded into mirage, but it makes it difficult to see how to change it for your own network. It might be better to use direct_stackv4_with_static_ipv4 for the examples. -- 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 Sat Jun 14 05:56:09 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sat, 14 Jun 2014 05:56: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 1WvgwZ-0007jX-Fa; Sat, 14 Jun 2014 05:55:59 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WvgwY-0007jS-1f for mirageos-devel@lists.xenproject.org; Sat, 14 Jun 2014 05:55:58 +0000 Received: from [85.158.143.35:25453] by server-3.bemta-4.messagelabs.com id 3C/81-13602-DE3EB935; Sat, 14 Jun 2014 05:55:57 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-12.tower-21.messagelabs.com!1402725356!11320393!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.2 required=7.0 tests=MIME_QP_LONG_LINE, ML_RADAR_SPEW_LINKS_23,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 32557 invoked from network); 14 Jun 2014 05:55:56 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-12.tower-21.messagelabs.com with SMTP; 14 Jun 2014 05:55:56 -0000 Received: (qmail 24697 invoked by uid 634); 14 Jun 2014 05:55:55 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from dab-ell1-h-64-9.dab.02.net (HELO [10.3.32.190]) (82.132.239.140) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Sat, 14 Jun 2014 06:55:52 +0100 References: <297FC9DB-3A4E-41A5-B00E-9DEF62C625E6@recoil.org> Mime-Version: 1.0 (1.0) In-Reply-To: Message-Id: <12D67D67-3DAB-4033-BFC5-C7DBCBA64F34@recoil.org> X-Mailer: iPhone Mail (11D201) From: Anil Madhavapeddy Date: Sat, 14 Jun 2014 06:55:35 +0100 To: Thomas Leonard X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Mirage on Xen/ARM status X-BeenThere: mirageos-devel@lists.xenproject.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 13 Jun 2014, at 17:53, Thomas Leonard wrote: > > I've been going through mirage-skeleton trying all the examples on ARM > (Cubietruck running Xen). Here are the results: > > console: works (I also patched it to try reading from the console, and > that works too, after a minor patch to mirage-console; now merged) > > network: works > block: works > > dns: fails to build > Error: No implementations provided for the following modules: > Lwt_unix referenced from > /root/.opam/4.01.0/lib/dns/lwt-core.cmxa(Dns_resolver) This look the euphemistic "architecture independent issue". Need to see how Unix snuck into the ocaml-dns core and add a test for that. Could you create an issue on ocaml-dns for this? > > ethifv4: seems to work (except for TCP: it shows "TCP retransmission > on timer seq = 452901213" instead of connecting) Can't verify from where I am, but it may just be the stack isn't configured. > io_page: works > kv_ro: works (prints YES! a lot, anyway) > kv_ro_crunch: works (as kv_ro) > ping: works (note: reports UDP traffic as "TCP" due to a bug) > stackv4: works (HTTP on 80, TCP on 8080 and UDP on 53) > > static_website: works, after adding re.str. Otherwise you get: > Error: No implementations provided for the following modules: > Re_str referenced from dispatch.cmx Odd, this was fixed a few weeks ago. Need to look through the pull reqs in case I forgot to merge it. > > So, it's looking pretty good :-) Yes! The lack of ARM specific issues in the OCaml native code backend isn't a surprise, but still a relief. > A few random notes: > > - Lack of progress reports from mirage is a problem on x86, but it's > worse on ARM because it's so much slower. Yes, this one has a bug open on mirage/mirage. We need to tee the output from the tool really. > - opam got very confused at one point, somehow uninstalled mirage and > then wouldn't bring it back (no error shown). Here's a sample: > > root@softbuild:~# mirage > -bash: mirage: command not found > root@softbuild:~# opam reinstall mirage > [ERROR] mirage is not installed. > > 'opam reinstall mirage' failed. > root@softbuild:~# opam install mirage > root@softbuild:~# mirage > -bash: mirage: command not found > root@softbuild:~# opam reinstall mirage > [ERROR] mirage is not installed. > > Installing "aspcud" sorted it all out (and makes it faster!). Aspects is pretty much a necessity in opam 1.1.1; most packaging marks it as recommended now. Hopefully Thomas can fix the internal solver in 1.2 with some more heuristic magic :-) The recompile came from the libraries that the mirage tool needs being recompiled due to a depopt, being uninstalled during that, and then error recovery not kicking (possibly broken solver) This is much improved in opam 1.2, and using Thomas' Makefile generator instead of directly calling opam will help the user control when the package installation happens. > - I was using the system ocaml, which lacked ocamlopt.opt, slowing > down the builds. Using "opam sw 4.01.0" sorted that out. Did you install the ocaml-native-compilers package? > > - mirage-console's install rule has some problems at the moment. Use > "ocamlfind remove" to remove the various bits manually and try again > if it happens. > > https://github.com/mirage/mirage-console/issues/17 > > - direct_stackv4_with_default_ipv4 is a bit annoying. It contains an > IP address hard-coded into mirage, but it makes it difficult to see > how to change it for your own network. It might be better to use > direct_stackv4_with_static_ipv4 for the examples. Yeah, feel free to normalise any of these example and send a pull req btw. They do need a spring clean (Mort and I will look at this soon for our ECOOP tutorial at any rate) Anil > > > -- > 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 Sat Jun 14 05:56:09 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sat, 14 Jun 2014 05:56: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 1WvgwZ-0007jX-Fa; Sat, 14 Jun 2014 05:55:59 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WvgwY-0007jS-1f for mirageos-devel@lists.xenproject.org; Sat, 14 Jun 2014 05:55:58 +0000 Received: from [85.158.143.35:25453] by server-3.bemta-4.messagelabs.com id 3C/81-13602-DE3EB935; Sat, 14 Jun 2014 05:55:57 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-12.tower-21.messagelabs.com!1402725356!11320393!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.2 required=7.0 tests=MIME_QP_LONG_LINE, ML_RADAR_SPEW_LINKS_23,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 32557 invoked from network); 14 Jun 2014 05:55:56 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-12.tower-21.messagelabs.com with SMTP; 14 Jun 2014 05:55:56 -0000 Received: (qmail 24697 invoked by uid 634); 14 Jun 2014 05:55:55 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from dab-ell1-h-64-9.dab.02.net (HELO [10.3.32.190]) (82.132.239.140) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Sat, 14 Jun 2014 06:55:52 +0100 References: <297FC9DB-3A4E-41A5-B00E-9DEF62C625E6@recoil.org> Mime-Version: 1.0 (1.0) In-Reply-To: Message-Id: <12D67D67-3DAB-4033-BFC5-C7DBCBA64F34@recoil.org> X-Mailer: iPhone Mail (11D201) From: Anil Madhavapeddy Date: Sat, 14 Jun 2014 06:55:35 +0100 To: Thomas Leonard X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Mirage on Xen/ARM status X-BeenThere: mirageos-devel@lists.xenproject.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 13 Jun 2014, at 17:53, Thomas Leonard wrote: > > I've been going through mirage-skeleton trying all the examples on ARM > (Cubietruck running Xen). Here are the results: > > console: works (I also patched it to try reading from the console, and > that works too, after a minor patch to mirage-console; now merged) > > network: works > block: works > > dns: fails to build > Error: No implementations provided for the following modules: > Lwt_unix referenced from > /root/.opam/4.01.0/lib/dns/lwt-core.cmxa(Dns_resolver) This look the euphemistic "architecture independent issue". Need to see how Unix snuck into the ocaml-dns core and add a test for that. Could you create an issue on ocaml-dns for this? > > ethifv4: seems to work (except for TCP: it shows "TCP retransmission > on timer seq = 452901213" instead of connecting) Can't verify from where I am, but it may just be the stack isn't configured. > io_page: works > kv_ro: works (prints YES! a lot, anyway) > kv_ro_crunch: works (as kv_ro) > ping: works (note: reports UDP traffic as "TCP" due to a bug) > stackv4: works (HTTP on 80, TCP on 8080 and UDP on 53) > > static_website: works, after adding re.str. Otherwise you get: > Error: No implementations provided for the following modules: > Re_str referenced from dispatch.cmx Odd, this was fixed a few weeks ago. Need to look through the pull reqs in case I forgot to merge it. > > So, it's looking pretty good :-) Yes! The lack of ARM specific issues in the OCaml native code backend isn't a surprise, but still a relief. > A few random notes: > > - Lack of progress reports from mirage is a problem on x86, but it's > worse on ARM because it's so much slower. Yes, this one has a bug open on mirage/mirage. We need to tee the output from the tool really. > - opam got very confused at one point, somehow uninstalled mirage and > then wouldn't bring it back (no error shown). Here's a sample: > > root@softbuild:~# mirage > -bash: mirage: command not found > root@softbuild:~# opam reinstall mirage > [ERROR] mirage is not installed. > > 'opam reinstall mirage' failed. > root@softbuild:~# opam install mirage > root@softbuild:~# mirage > -bash: mirage: command not found > root@softbuild:~# opam reinstall mirage > [ERROR] mirage is not installed. > > Installing "aspcud" sorted it all out (and makes it faster!). Aspects is pretty much a necessity in opam 1.1.1; most packaging marks it as recommended now. Hopefully Thomas can fix the internal solver in 1.2 with some more heuristic magic :-) The recompile came from the libraries that the mirage tool needs being recompiled due to a depopt, being uninstalled during that, and then error recovery not kicking (possibly broken solver) This is much improved in opam 1.2, and using Thomas' Makefile generator instead of directly calling opam will help the user control when the package installation happens. > - I was using the system ocaml, which lacked ocamlopt.opt, slowing > down the builds. Using "opam sw 4.01.0" sorted that out. Did you install the ocaml-native-compilers package? > > - mirage-console's install rule has some problems at the moment. Use > "ocamlfind remove" to remove the various bits manually and try again > if it happens. > > https://github.com/mirage/mirage-console/issues/17 > > - direct_stackv4_with_default_ipv4 is a bit annoying. It contains an > IP address hard-coded into mirage, but it makes it difficult to see > how to change it for your own network. It might be better to use > direct_stackv4_with_static_ipv4 for the examples. Yeah, feel free to normalise any of these example and send a pull req btw. They do need a spring clean (Mort and I will look at this soon for our ECOOP tutorial at any rate) Anil > > > -- > 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 Sat Jun 14 19:10:37 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sat, 14 Jun 2014 19:10: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 1WvtLT-0003ls-Ed; Sat, 14 Jun 2014 19:10:31 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WvtLS-0003ln-7h for mirageos-devel@lists.xenproject.org; Sat, 14 Jun 2014 19:10:30 +0000 Received: from [193.109.254.147:32442] by server-14.bemta-14.messagelabs.com id A5/64-08195-52E9C935; Sat, 14 Jun 2014 19:10:29 +0000 X-Env-Sender: unitedbiscuits@gmail.com X-Msg-Ref: server-12.tower-27.messagelabs.com!1402773027!11283205!1 X-Originating-IP: [209.85.216.54] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8080 invoked from network); 14 Jun 2014 19:10:28 -0000 Received: from mail-qa0-f54.google.com (HELO mail-qa0-f54.google.com) (209.85.216.54) by server-12.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 14 Jun 2014 19:10:28 -0000 Received: by mail-qa0-f54.google.com with SMTP id v10so5451765qac.27 for ; Sat, 14 Jun 2014 12:10:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:from:date:message-id:subject:to:content-type; bh=iYhH7Hj+L3PqZZYgXNjxqFwVzljL8FdPU6xWmHNlRdM=; b=pMmACk7PP32/7PSxTowwvmlqPqLhhKxpk9FRMgOBVV57IsAcYMk9UdMJDdXS4vy2ml 6WcJMe0IPTrEEg7SnUFGnTfseUO8xw7Hb/eP/buJ+2FbcSMSyEkRhi0fbkzwElS9uhcT 7nvStbIQdABgs8BuwYRA1pn9j0KFKYl3NZg4fwzk3ql8UnK+opOqHm0h2QQO+d/4b0Tf 16QLE4RejNmwx0Rl9VgbYw+orSklmsGaLBF/Nf5zFcMtB5RxbxlluECRDn+Ro9JmZU3j y/cpM5ePH0Vk935/0x/QQ8v7FeEYGK96JReEvG0WSsJEy1hz5H49mvYu8VygcowOCIeU 0E9A== X-Received: by 10.224.161.10 with SMTP id p10mr13976740qax.12.1402773027734; Sat, 14 Jun 2014 12:10:27 -0700 (PDT) MIME-Version: 1.0 Received: by 10.140.102.245 with HTTP; Sat, 14 Jun 2014 12:10:07 -0700 (PDT) From: =?UTF-8?Q?David_Kaloper_Mer=C5=A1injak?= Date: Sat, 14 Jun 2014 20:10:07 +0100 X-Google-Sender-Auth: pxucUH-1MtvSY_moz7wv5vbUH1M Message-ID: To: mirageos-devel Subject: [MirageOS-devel] Logging, Flows and Irmin X-BeenThere: mirageos-devel@lists.xenproject.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, I'm trying to finish the tracing for the test/demo TLS server on top of Mirage and I've got two questions: To make logs meaningful, I need a way to get the address of the connected peer from a TCPV4.flow -- but all I can find is `id` to get my own address. Is this possible? Secondly; The stack uses Sexps to produce traces and they are now stored with Irmin/Git [1] (please be gentle, this is my first foray into Irmin :) ). Since we plan to spin up multiple instances of this it would be better to send Sexps to an Irmin daemon that manages the storage. Could somebody point me to a snippet of code to get started with this? Thanks, David [1] https://github.com/mirleft/tls-demo-server/blob/master/unikernel.ml#L118 _______________________________________________ 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 Jun 14 19:10:37 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sat, 14 Jun 2014 19:10: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 1WvtLT-0003ls-Ed; Sat, 14 Jun 2014 19:10:31 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WvtLS-0003ln-7h for mirageos-devel@lists.xenproject.org; Sat, 14 Jun 2014 19:10:30 +0000 Received: from [193.109.254.147:32442] by server-14.bemta-14.messagelabs.com id A5/64-08195-52E9C935; Sat, 14 Jun 2014 19:10:29 +0000 X-Env-Sender: unitedbiscuits@gmail.com X-Msg-Ref: server-12.tower-27.messagelabs.com!1402773027!11283205!1 X-Originating-IP: [209.85.216.54] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8080 invoked from network); 14 Jun 2014 19:10:28 -0000 Received: from mail-qa0-f54.google.com (HELO mail-qa0-f54.google.com) (209.85.216.54) by server-12.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 14 Jun 2014 19:10:28 -0000 Received: by mail-qa0-f54.google.com with SMTP id v10so5451765qac.27 for ; Sat, 14 Jun 2014 12:10:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:from:date:message-id:subject:to:content-type; bh=iYhH7Hj+L3PqZZYgXNjxqFwVzljL8FdPU6xWmHNlRdM=; b=pMmACk7PP32/7PSxTowwvmlqPqLhhKxpk9FRMgOBVV57IsAcYMk9UdMJDdXS4vy2ml 6WcJMe0IPTrEEg7SnUFGnTfseUO8xw7Hb/eP/buJ+2FbcSMSyEkRhi0fbkzwElS9uhcT 7nvStbIQdABgs8BuwYRA1pn9j0KFKYl3NZg4fwzk3ql8UnK+opOqHm0h2QQO+d/4b0Tf 16QLE4RejNmwx0Rl9VgbYw+orSklmsGaLBF/Nf5zFcMtB5RxbxlluECRDn+Ro9JmZU3j y/cpM5ePH0Vk935/0x/QQ8v7FeEYGK96JReEvG0WSsJEy1hz5H49mvYu8VygcowOCIeU 0E9A== X-Received: by 10.224.161.10 with SMTP id p10mr13976740qax.12.1402773027734; Sat, 14 Jun 2014 12:10:27 -0700 (PDT) MIME-Version: 1.0 Received: by 10.140.102.245 with HTTP; Sat, 14 Jun 2014 12:10:07 -0700 (PDT) From: =?UTF-8?Q?David_Kaloper_Mer=C5=A1injak?= Date: Sat, 14 Jun 2014 20:10:07 +0100 X-Google-Sender-Auth: pxucUH-1MtvSY_moz7wv5vbUH1M Message-ID: To: mirageos-devel Subject: [MirageOS-devel] Logging, Flows and Irmin X-BeenThere: mirageos-devel@lists.xenproject.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, I'm trying to finish the tracing for the test/demo TLS server on top of Mirage and I've got two questions: To make logs meaningful, I need a way to get the address of the connected peer from a TCPV4.flow -- but all I can find is `id` to get my own address. Is this possible? Secondly; The stack uses Sexps to produce traces and they are now stored with Irmin/Git [1] (please be gentle, this is my first foray into Irmin :) ). Since we plan to spin up multiple instances of this it would be better to send Sexps to an Irmin daemon that manages the storage. Could somebody point me to a snippet of code to get started with this? Thanks, David [1] https://github.com/mirleft/tls-demo-server/blob/master/unikernel.ml#L118 _______________________________________________ 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 Jun 16 09:06:08 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 16 Jun 2014 09:06: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 1WwSrS-0005Zf-4U; Mon, 16 Jun 2014 09:05:54 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WwSrQ-0005ZZ-LS for mirageos-devel@lists.xenproject.org; Mon, 16 Jun 2014 09:05:52 +0000 Received: from [85.158.143.35:2859] by server-2.bemta-4.messagelabs.com id 50/DE-06539-F63BE935; Mon, 16 Jun 2014 09:05:51 +0000 X-Env-Sender: Richard.Mortier@nottingham.ac.uk X-Msg-Ref: server-10.tower-21.messagelabs.com!1402909135!11586661!1 X-Originating-IP: [93.95.15.170] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7220 invoked from network); 16 Jun 2014 08:58:55 -0000 Received: from engine03-20433-3.icritical.com (HELO engine03-20433-3.icritical.com) (93.95.15.170) by server-10.tower-21.messagelabs.com with SMTP; 16 Jun 2014 08:58:55 -0000 Received: (qmail 23729 invoked from network); 16 Jun 2014 08:59:06 -0000 Received: from localhost (127.0.0.1) by engine03-20433-3.icritical.com with SMTP; 16 Jun 2014 08:59:06 -0000 Received: from engine03-20433-3.icritical.com ([127.0.0.1]) by localhost (engine03-20433-3.icritical.com [127.0.0.1]) (amavisd-new, port 10024) with SMTP id 23564-05 for ; Mon, 16 Jun 2014 09:58:59 +0100 (BST) Received: (qmail 22265 invoked by uid 599); 16 Jun 2014 08:56:39 -0000 Received: from unknown (HELO smtp4.nottingham.ac.uk) (128.243.220.65) by engine03-20433-3.icritical.com (qpsmtpd/0.28) with ESMTP; Mon, 16 Jun 2014 09:56:39 +0100 Received: from uiwexhub01.ad.nottingham.ac.uk ([128.243.15.133]) by smtp4.nottingham.ac.uk with esmtps (TLSv1:AES128-SHA:128) (Exim 4.77) (envelope-from ) id 1WwSiP-0003KC-BZ; Mon, 16 Jun 2014 09:56:33 +0100 From: Richard Mortier To: David Scott Date: Mon, 16 Jun 2014 09:55:11 +0100 Thread-Topic: [MirageOS-devel] towards a common Mirage 'FLOW' signature Thread-Index: Ac+JQN6CGbUjpoKnQRq5wJrv2F/NIg== Message-ID: <819892F4-DE76-4CF3-A988-85675A41E650@nottingham.ac.uk> References: In-Reply-To: Accept-Language: en-US, en-GB Content-Language: en-US X-MS-Has-Attach: yes X-MS-TNEF-Correlator: acceptlanguage: en-US, en-GB MIME-Version: 1.0 X-Virus-Scanned: by iCritical at engine03-20433-3.icritical.com Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] towards a common Mirage 'FLOW' signature X-BeenThere: mirageos-devel@lists.xenproject.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="===============0536745616405678958==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============0536745616405678958== Content-Language: en-US Content-Type: multipart/signed; boundary="Apple-Mail=_D4A5EC35-690E-4301-9318-2E6EFA7BC9BA"; protocol="application/pgp-signature"; micalg=pgp-sha512 --Apple-Mail=_D4A5EC35-690E-4301-9318-2E6EFA7BC9BA Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On 12 Jun 2014, at 21:38, David Scott wrote: > I notice the low-level network APIs (NETWORK, ETHIF, ...) are *almost* = like this except they have a function like >=20 > val listen: t -> udp:callback -> tcp:callback -> ...=20 >=20 > Perhaps later (V2, V3?) we could split this into something like a=20 >=20 > val read: t -> buffer (* satisfy FLOW *) > val classify: buffer -> [ `UDP; `TCP ] >=20 > -- is that a good idea? i generally like the idea of doing something other than an ad hoc = collection of callbacks. how would the scheme above handle recursive protocols (IP-in-IP etc)? (probably irrelevant but fwiw: i tried doing something a little like = this with the pcap code -- so there was a set of default "demux" = functions but you could override them all to construct your own protocol = demux dag.) --=20 Cheers, R. --Apple-Mail=_D4A5EC35-690E-4301-9318-2E6EFA7BC9BA Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="signature.asc" Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJTnrDvAAoJEOLF27JWwSg3IjAQALqzNEVR1D9rsN+CgyVgvj9Y DQistikYm2o9c9GqcXFOU3VXcs//2ifRQPdviUiNJzw+kqujmx1hEjEZoKs7zQZ9 pdfgK4x6wwsrOnIMZBLnnDdu5F3x7xY5J1TXVhy1N6bdI1B3wIx9/Se67XaSku7v aQKUtA8F2/F+M1SAykkBJVLXRRdKLQMiuzp6WK+Rfldl2PwY1G1RwE+8ksXxzkLt t0SOd1iTKN55Axk+UavDecwK4C2wLmDrvlIfldn15iyIXnfV88Iit4z+FcNPWiTP iU02p0S57tWy3bIkmnv2Zba/Hiu8JQoOy8NNZE8fcyl10CrFoTY6gRWjZGgJYbA+ oM5XaB0zmE6A1ZnNDZE8Vipu2IjtSyliuSIhEeI6y7aTPF+5uV93xFWNfW8E5PAd aqHLQsGZnub+OaiFBaNTUMXXIkshpuTR1RIWuw0NPUjU5nmy+C2o986dwJ+OUgCa 0q4bRCUBskNtWu16o5H7vHunT9w+BXsAT4eAEiR7/nMlDU19x+3FSXJAn4WRFSOH xKCt50vzSkzAP0K60vs1CgB1mM7P1XfeTzOqxilJ4yRvM0bec5IZKAq+lVb1Im4R o/bRBawBPhXvC9scR9PZTFF6dRP6hP71zAbbzskR4qIYNnvnAsX2ybQqJJB+xDM9 06427Hxeaj9tjH2QksgF =aPcw -----END PGP SIGNATURE----- --Apple-Mail=_D4A5EC35-690E-4301-9318-2E6EFA7BC9BA-- --===============0536745616405678958== 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 --===============0536745616405678958==-- From mirageos-devel-bounces@lists.xenproject.org Mon Jun 16 09:06:08 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 16 Jun 2014 09:06: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 1WwSrS-0005Zf-4U; Mon, 16 Jun 2014 09:05:54 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WwSrQ-0005ZZ-LS for mirageos-devel@lists.xenproject.org; Mon, 16 Jun 2014 09:05:52 +0000 Received: from [85.158.143.35:2859] by server-2.bemta-4.messagelabs.com id 50/DE-06539-F63BE935; Mon, 16 Jun 2014 09:05:51 +0000 X-Env-Sender: Richard.Mortier@nottingham.ac.uk X-Msg-Ref: server-10.tower-21.messagelabs.com!1402909135!11586661!1 X-Originating-IP: [93.95.15.170] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7220 invoked from network); 16 Jun 2014 08:58:55 -0000 Received: from engine03-20433-3.icritical.com (HELO engine03-20433-3.icritical.com) (93.95.15.170) by server-10.tower-21.messagelabs.com with SMTP; 16 Jun 2014 08:58:55 -0000 Received: (qmail 23729 invoked from network); 16 Jun 2014 08:59:06 -0000 Received: from localhost (127.0.0.1) by engine03-20433-3.icritical.com with SMTP; 16 Jun 2014 08:59:06 -0000 Received: from engine03-20433-3.icritical.com ([127.0.0.1]) by localhost (engine03-20433-3.icritical.com [127.0.0.1]) (amavisd-new, port 10024) with SMTP id 23564-05 for ; Mon, 16 Jun 2014 09:58:59 +0100 (BST) Received: (qmail 22265 invoked by uid 599); 16 Jun 2014 08:56:39 -0000 Received: from unknown (HELO smtp4.nottingham.ac.uk) (128.243.220.65) by engine03-20433-3.icritical.com (qpsmtpd/0.28) with ESMTP; Mon, 16 Jun 2014 09:56:39 +0100 Received: from uiwexhub01.ad.nottingham.ac.uk ([128.243.15.133]) by smtp4.nottingham.ac.uk with esmtps (TLSv1:AES128-SHA:128) (Exim 4.77) (envelope-from ) id 1WwSiP-0003KC-BZ; Mon, 16 Jun 2014 09:56:33 +0100 From: Richard Mortier To: David Scott Date: Mon, 16 Jun 2014 09:55:11 +0100 Thread-Topic: [MirageOS-devel] towards a common Mirage 'FLOW' signature Thread-Index: Ac+JQN6CGbUjpoKnQRq5wJrv2F/NIg== Message-ID: <819892F4-DE76-4CF3-A988-85675A41E650@nottingham.ac.uk> References: In-Reply-To: Accept-Language: en-US, en-GB Content-Language: en-US X-MS-Has-Attach: yes X-MS-TNEF-Correlator: acceptlanguage: en-US, en-GB MIME-Version: 1.0 X-Virus-Scanned: by iCritical at engine03-20433-3.icritical.com Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] towards a common Mirage 'FLOW' signature X-BeenThere: mirageos-devel@lists.xenproject.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="===============0536745616405678958==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============0536745616405678958== Content-Language: en-US Content-Type: multipart/signed; boundary="Apple-Mail=_D4A5EC35-690E-4301-9318-2E6EFA7BC9BA"; protocol="application/pgp-signature"; micalg=pgp-sha512 --Apple-Mail=_D4A5EC35-690E-4301-9318-2E6EFA7BC9BA Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On 12 Jun 2014, at 21:38, David Scott wrote: > I notice the low-level network APIs (NETWORK, ETHIF, ...) are *almost* = like this except they have a function like >=20 > val listen: t -> udp:callback -> tcp:callback -> ...=20 >=20 > Perhaps later (V2, V3?) we could split this into something like a=20 >=20 > val read: t -> buffer (* satisfy FLOW *) > val classify: buffer -> [ `UDP; `TCP ] >=20 > -- is that a good idea? i generally like the idea of doing something other than an ad hoc = collection of callbacks. how would the scheme above handle recursive protocols (IP-in-IP etc)? (probably irrelevant but fwiw: i tried doing something a little like = this with the pcap code -- so there was a set of default "demux" = functions but you could override them all to construct your own protocol = demux dag.) --=20 Cheers, R. --Apple-Mail=_D4A5EC35-690E-4301-9318-2E6EFA7BC9BA Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="signature.asc" Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJTnrDvAAoJEOLF27JWwSg3IjAQALqzNEVR1D9rsN+CgyVgvj9Y DQistikYm2o9c9GqcXFOU3VXcs//2ifRQPdviUiNJzw+kqujmx1hEjEZoKs7zQZ9 pdfgK4x6wwsrOnIMZBLnnDdu5F3x7xY5J1TXVhy1N6bdI1B3wIx9/Se67XaSku7v aQKUtA8F2/F+M1SAykkBJVLXRRdKLQMiuzp6WK+Rfldl2PwY1G1RwE+8ksXxzkLt t0SOd1iTKN55Axk+UavDecwK4C2wLmDrvlIfldn15iyIXnfV88Iit4z+FcNPWiTP iU02p0S57tWy3bIkmnv2Zba/Hiu8JQoOy8NNZE8fcyl10CrFoTY6gRWjZGgJYbA+ oM5XaB0zmE6A1ZnNDZE8Vipu2IjtSyliuSIhEeI6y7aTPF+5uV93xFWNfW8E5PAd aqHLQsGZnub+OaiFBaNTUMXXIkshpuTR1RIWuw0NPUjU5nmy+C2o986dwJ+OUgCa 0q4bRCUBskNtWu16o5H7vHunT9w+BXsAT4eAEiR7/nMlDU19x+3FSXJAn4WRFSOH xKCt50vzSkzAP0K60vs1CgB1mM7P1XfeTzOqxilJ4yRvM0bec5IZKAq+lVb1Im4R o/bRBawBPhXvC9scR9PZTFF6dRP6hP71zAbbzskR4qIYNnvnAsX2ybQqJJB+xDM9 06427Hxeaj9tjH2QksgF =aPcw -----END PGP SIGNATURE----- --Apple-Mail=_D4A5EC35-690E-4301-9318-2E6EFA7BC9BA-- --===============0536745616405678958== 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 --===============0536745616405678958==-- From mirageos-devel-bounces@lists.xenproject.org Mon Jun 16 09:23:24 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 16 Jun 2014 09:23: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 1WwT8B-00066j-WA; Mon, 16 Jun 2014 09:23:11 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WwT8B-00066c-0p for mirageos-devel@lists.xenproject.org; Mon, 16 Jun 2014 09:23:11 +0000 Received: from [193.109.254.147:5376] by server-15.bemta-14.messagelabs.com id 85/EA-15813-E77BE935; Mon, 16 Jun 2014 09:23:10 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-16.tower-27.messagelabs.com!1402910589!6066499!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 13317 invoked from network); 16 Jun 2014 09:23:09 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-16.tower-27.messagelabs.com with SMTP; 16 Jun 2014 09:23:09 -0000 Received: (qmail 24219 invoked by uid 634); 16 Jun 2014 09:23:09 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from cpc11-belf9-2-0-cust355.2-1.cable.virginm.net (HELO [10.0.1.15]) (86.24.61.100) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Mon, 16 Jun 2014 10:23:08 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\)) From: Anil Madhavapeddy In-Reply-To: <819892F4-DE76-4CF3-A988-85675A41E650@nottingham.ac.uk> Date: Mon, 16 Jun 2014 10:23:05 +0100 Message-Id: References: <819892F4-DE76-4CF3-A988-85675A41E650@nottingham.ac.uk> To: Richard Mortier X-Mailer: Apple Mail (2.1874) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] towards a common Mirage 'FLOW' signature X-BeenThere: mirageos-devel@lists.xenproject.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 Jun 2014, at 09:55, Richard Mortier wrote: > > On 12 Jun 2014, at 21:38, David Scott wrote: > >> I notice the low-level network APIs (NETWORK, ETHIF, ...) are *almost* like this except they have a function like >> >> val listen: t -> udp:callback -> tcp:callback -> ... >> >> Perhaps later (V2, V3?) we could split this into something like a >> >> val read: t -> buffer (* satisfy FLOW *) >> val classify: buffer -> [ `UDP; `TCP ] >> >> -- is that a good idea? > > i generally like the idea of doing something other than an ad hoc collection of callbacks. > > how would the scheme above handle recursive protocols (IP-in-IP etc)? You would narrow the buffer by classifying it, generating a sub-view, and making that a FLOW again. I don't think that this interface should concern itself with doing a deep packet inspection, unless I'm missing something? > (probably irrelevant but fwiw: i tried doing something a little like this with the pcap code -- so there was a set of default "demux" functions but you could override them all to construct your own protocol demux dag.) Got a pointer? Should make sure the two are compatible. -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 Jun 16 09:23:24 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 16 Jun 2014 09:23: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 1WwT8B-00066j-WA; Mon, 16 Jun 2014 09:23:11 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WwT8B-00066c-0p for mirageos-devel@lists.xenproject.org; Mon, 16 Jun 2014 09:23:11 +0000 Received: from [193.109.254.147:5376] by server-15.bemta-14.messagelabs.com id 85/EA-15813-E77BE935; Mon, 16 Jun 2014 09:23:10 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-16.tower-27.messagelabs.com!1402910589!6066499!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 13317 invoked from network); 16 Jun 2014 09:23:09 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-16.tower-27.messagelabs.com with SMTP; 16 Jun 2014 09:23:09 -0000 Received: (qmail 24219 invoked by uid 634); 16 Jun 2014 09:23:09 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from cpc11-belf9-2-0-cust355.2-1.cable.virginm.net (HELO [10.0.1.15]) (86.24.61.100) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Mon, 16 Jun 2014 10:23:08 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\)) From: Anil Madhavapeddy In-Reply-To: <819892F4-DE76-4CF3-A988-85675A41E650@nottingham.ac.uk> Date: Mon, 16 Jun 2014 10:23:05 +0100 Message-Id: References: <819892F4-DE76-4CF3-A988-85675A41E650@nottingham.ac.uk> To: Richard Mortier X-Mailer: Apple Mail (2.1874) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] towards a common Mirage 'FLOW' signature X-BeenThere: mirageos-devel@lists.xenproject.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 Jun 2014, at 09:55, Richard Mortier wrote: > > On 12 Jun 2014, at 21:38, David Scott wrote: > >> I notice the low-level network APIs (NETWORK, ETHIF, ...) are *almost* like this except they have a function like >> >> val listen: t -> udp:callback -> tcp:callback -> ... >> >> Perhaps later (V2, V3?) we could split this into something like a >> >> val read: t -> buffer (* satisfy FLOW *) >> val classify: buffer -> [ `UDP; `TCP ] >> >> -- is that a good idea? > > i generally like the idea of doing something other than an ad hoc collection of callbacks. > > how would the scheme above handle recursive protocols (IP-in-IP etc)? You would narrow the buffer by classifying it, generating a sub-view, and making that a FLOW again. I don't think that this interface should concern itself with doing a deep packet inspection, unless I'm missing something? > (probably irrelevant but fwiw: i tried doing something a little like this with the pcap code -- so there was a set of default "demux" functions but you could override them all to construct your own protocol demux dag.) Got a pointer? Should make sure the two are compatible. -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 Jun 16 09:27:53 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 16 Jun 2014 09:27: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 1WwTCc-0006LR-UK; Mon, 16 Jun 2014 09:27:46 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WwTCb-0006LH-51 for mirageos-devel@lists.xenproject.org; Mon, 16 Jun 2014 09:27:45 +0000 Received: from [193.109.254.147:49067] by server-13.bemta-14.messagelabs.com id FB/22-23211-098BE935; Mon, 16 Jun 2014 09:27:44 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-16.tower-27.messagelabs.com!1402910863!6068506!1 X-Originating-IP: [209.85.212.176] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25264 invoked from network); 16 Jun 2014 09:27:43 -0000 Received: from mail-wi0-f176.google.com (HELO mail-wi0-f176.google.com) (209.85.212.176) by server-16.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 16 Jun 2014 09:27:43 -0000 Received: by mail-wi0-f176.google.com with SMTP id n3so3670837wiv.3 for ; Mon, 16 Jun 2014 02:27:43 -0700 (PDT) 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=GyM6Dd/2dUaT47Pq7O8AJEArUs00beMlpVwZI1SaTK8=; b=GZHsV0PcqxEf6KLuXWG2kt8jksWNgBCvGGoo6UgGE35JtsD9bAHBkmoqYMjH485JEa 8tdY/w6/eQjgIPa6+/tTBWyrjdtBTYH3eijFZutlnVonrxVlspW5NewG1nr3twrtE0Wj S1O8nHMYvN0/vd05pE/F+375y9/71qfC/OgqnNUuThHeVolTxHDqRTT+wc7ZOUqkjiu6 Uz3+yxXrIw2JeKh8RDobBbA5DCahr0jLpRKfxcf7cAsJqcXlz9jlgYxxoE2XzJjEnBtU wbd3MMFlEuIVPJ5qAyh6wVS4l3a25kW0C2mwgZlDhXusuX9pu73GUyBb3IEwffrydJTr Xx7g== X-Received: by 10.194.174.168 with SMTP id bt8mr10001769wjc.72.1402910863067; Mon, 16 Jun 2014 02:27:43 -0700 (PDT) Received: from [192.168.0.8] (cpc25-cmbg14-2-0-cust121.5-4.cable.virginm.net. [213.106.112.122]) by mx.google.com with ESMTPSA id na4sm13522619wic.21.2014.06.16.02.27.40 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 16 Jun 2014 02:27:41 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\)) From: Thomas Gazagnaire In-Reply-To: Date: Mon, 16 Jun 2014 10:27:39 +0100 Message-Id: References: To: =?windows-1252?Q?David_Kaloper_Mer=9Ainjak?= X-Mailer: Apple Mail (2.1878.2) Cc: mirageos-devel Subject: Re: [MirageOS-devel] Logging, Flows and Irmin X-BeenThere: mirageos-devel@lists.xenproject.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 > Secondly; The stack uses Sexps to produce traces and they are now > stored with Irmin/Git [1] (please be gentle, this is my first foray > into Irmin :) ). Since we plan to spin up multiple instances of this > it would be better to send Sexps to an Irmin daemon that manages the > storage. Could somebody point me to a snippet of code to get started > with this? You have different ways to do this. The simplest one is to push to a remote Git repository: ``` let remote = IrminRemote.uri in Store.Sync.push t remote ``` This currently only works with the Git Unix backend, though, ie. you need to `open Irmin_unix` in your file and link with `irmin.unix`. An other way is to create a remote Irmin daemon and push to it using: ``` let module R = IrminCRUD.Make (...)(struct let uri = end) in R.create () >>= fun r -> let remote = IrminRemote.store (module R) r in Store.Sync.push t remote ``` This will work with any backends, but will be quite slow (ie. using JSON over HTTP). Hope this helps, Thomas > > Thanks, > David > > [1] https://github.com/mirleft/tls-demo-server/blob/master/unikernel.ml#L118 > > _______________________________________________ > 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 Jun 16 09:27:53 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 16 Jun 2014 09:27: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 1WwTCc-0006LR-UK; Mon, 16 Jun 2014 09:27:46 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WwTCb-0006LH-51 for mirageos-devel@lists.xenproject.org; Mon, 16 Jun 2014 09:27:45 +0000 Received: from [193.109.254.147:49067] by server-13.bemta-14.messagelabs.com id FB/22-23211-098BE935; Mon, 16 Jun 2014 09:27:44 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-16.tower-27.messagelabs.com!1402910863!6068506!1 X-Originating-IP: [209.85.212.176] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25264 invoked from network); 16 Jun 2014 09:27:43 -0000 Received: from mail-wi0-f176.google.com (HELO mail-wi0-f176.google.com) (209.85.212.176) by server-16.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 16 Jun 2014 09:27:43 -0000 Received: by mail-wi0-f176.google.com with SMTP id n3so3670837wiv.3 for ; Mon, 16 Jun 2014 02:27:43 -0700 (PDT) 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=GyM6Dd/2dUaT47Pq7O8AJEArUs00beMlpVwZI1SaTK8=; b=GZHsV0PcqxEf6KLuXWG2kt8jksWNgBCvGGoo6UgGE35JtsD9bAHBkmoqYMjH485JEa 8tdY/w6/eQjgIPa6+/tTBWyrjdtBTYH3eijFZutlnVonrxVlspW5NewG1nr3twrtE0Wj S1O8nHMYvN0/vd05pE/F+375y9/71qfC/OgqnNUuThHeVolTxHDqRTT+wc7ZOUqkjiu6 Uz3+yxXrIw2JeKh8RDobBbA5DCahr0jLpRKfxcf7cAsJqcXlz9jlgYxxoE2XzJjEnBtU wbd3MMFlEuIVPJ5qAyh6wVS4l3a25kW0C2mwgZlDhXusuX9pu73GUyBb3IEwffrydJTr Xx7g== X-Received: by 10.194.174.168 with SMTP id bt8mr10001769wjc.72.1402910863067; Mon, 16 Jun 2014 02:27:43 -0700 (PDT) Received: from [192.168.0.8] (cpc25-cmbg14-2-0-cust121.5-4.cable.virginm.net. [213.106.112.122]) by mx.google.com with ESMTPSA id na4sm13522619wic.21.2014.06.16.02.27.40 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 16 Jun 2014 02:27:41 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\)) From: Thomas Gazagnaire In-Reply-To: Date: Mon, 16 Jun 2014 10:27:39 +0100 Message-Id: References: To: =?windows-1252?Q?David_Kaloper_Mer=9Ainjak?= X-Mailer: Apple Mail (2.1878.2) Cc: mirageos-devel Subject: Re: [MirageOS-devel] Logging, Flows and Irmin X-BeenThere: mirageos-devel@lists.xenproject.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 > Secondly; The stack uses Sexps to produce traces and they are now > stored with Irmin/Git [1] (please be gentle, this is my first foray > into Irmin :) ). Since we plan to spin up multiple instances of this > it would be better to send Sexps to an Irmin daemon that manages the > storage. Could somebody point me to a snippet of code to get started > with this? You have different ways to do this. The simplest one is to push to a remote Git repository: ``` let remote = IrminRemote.uri in Store.Sync.push t remote ``` This currently only works with the Git Unix backend, though, ie. you need to `open Irmin_unix` in your file and link with `irmin.unix`. An other way is to create a remote Irmin daemon and push to it using: ``` let module R = IrminCRUD.Make (...)(struct let uri = end) in R.create () >>= fun r -> let remote = IrminRemote.store (module R) r in Store.Sync.push t remote ``` This will work with any backends, but will be quite slow (ie. using JSON over HTTP). Hope this helps, Thomas > > Thanks, > David > > [1] https://github.com/mirleft/tls-demo-server/blob/master/unikernel.ml#L118 > > _______________________________________________ > 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 Jun 16 09:33:35 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 16 Jun 2014 09:33: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 1WwTI8-0006UY-QU; Mon, 16 Jun 2014 09:33:28 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WwTI8-0006UH-5w for mirageos-devel@lists.xenproject.org; Mon, 16 Jun 2014 09:33:28 +0000 Received: from [85.158.137.68:22456] by server-2.bemta-3.messagelabs.com id 46/B7-23530-7E9BE935; Mon, 16 Jun 2014 09:33:27 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-4.tower-31.messagelabs.com!1402911206!10230185!1 X-Originating-IP: [209.85.212.182] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29086 invoked from network); 16 Jun 2014 09:33:26 -0000 Received: from mail-wi0-f182.google.com (HELO mail-wi0-f182.google.com) (209.85.212.182) by server-4.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 16 Jun 2014 09:33:26 -0000 Received: by mail-wi0-f182.google.com with SMTP id bs8so3672495wib.3 for ; Mon, 16 Jun 2014 02:33:26 -0700 (PDT) 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=vSv/jJ6VTbI7vTGFvEH2Xpx6E0K/G/X7VSC41yltZB0=; b=kQrzNVQHOhHvf6YUTsHvsATTRz8NsO9d7zGboPRjvC//LaW15wvAmvPMGqSgwcS2C0 8U0kqXtI8289z5dtnvU3FSfbXiUg/176se4TECY8KDs9fh/wlWxKsOlkIStSKDCI/qyI V8CA/MYwJE1puaNF8rJNkhrLcEBLqYOePeiR+EEOaqcVPVvDsX8et+JBvpQqlDh2sxGS 3MshZWJH5trEGN8lENaajIfHWmuKyM9dHXm131OnzLR6EbsG3YU/2CX8SvDumUh3DmRu eHM3iSK0odOizvrdlip4nIaeiNA+gkW6f1eQ/l8lI0l03VhaYO0GDsmMJuZzLeh0kzc+ 0rog== X-Received: by 10.194.90.106 with SMTP id bv10mr26081996wjb.20.1402911206387; Mon, 16 Jun 2014 02:33:26 -0700 (PDT) Received: from [192.168.0.8] (cpc25-cmbg14-2-0-cust121.5-4.cable.virginm.net. [213.106.112.122]) by mx.google.com with ESMTPSA id gi8sm13582242wib.8.2014.06.16.02.33.24 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 16 Jun 2014 02:33:25 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\)) From: Thomas Gazagnaire In-Reply-To: Date: Mon, 16 Jun 2014 10:33:23 +0100 Message-Id: <1233494D-A05A-4F52-BFE7-9773BD566372@gazagnaire.org> References: To: David Scott X-Mailer: Apple Mail (2.1878.2) Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] towards a common Mirage 'FLOW' signature X-BeenThere: mirageos-devel@lists.xenproject.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 a bit late in the discussion, but: > * consoles > * xen inter-domain vchan connections > * plain TCP > * (hopefully) TLS connections For git, we also need in/out channels over the execution of an SSH program execution (ssh git-fetch-pack ). I think your change will also allow to do that so that's good :-) 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 Jun 16 09:33:35 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 16 Jun 2014 09:33: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 1WwTI8-0006UY-QU; Mon, 16 Jun 2014 09:33:28 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WwTI8-0006UH-5w for mirageos-devel@lists.xenproject.org; Mon, 16 Jun 2014 09:33:28 +0000 Received: from [85.158.137.68:22456] by server-2.bemta-3.messagelabs.com id 46/B7-23530-7E9BE935; Mon, 16 Jun 2014 09:33:27 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-4.tower-31.messagelabs.com!1402911206!10230185!1 X-Originating-IP: [209.85.212.182] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29086 invoked from network); 16 Jun 2014 09:33:26 -0000 Received: from mail-wi0-f182.google.com (HELO mail-wi0-f182.google.com) (209.85.212.182) by server-4.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 16 Jun 2014 09:33:26 -0000 Received: by mail-wi0-f182.google.com with SMTP id bs8so3672495wib.3 for ; Mon, 16 Jun 2014 02:33:26 -0700 (PDT) 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=vSv/jJ6VTbI7vTGFvEH2Xpx6E0K/G/X7VSC41yltZB0=; b=kQrzNVQHOhHvf6YUTsHvsATTRz8NsO9d7zGboPRjvC//LaW15wvAmvPMGqSgwcS2C0 8U0kqXtI8289z5dtnvU3FSfbXiUg/176se4TECY8KDs9fh/wlWxKsOlkIStSKDCI/qyI V8CA/MYwJE1puaNF8rJNkhrLcEBLqYOePeiR+EEOaqcVPVvDsX8et+JBvpQqlDh2sxGS 3MshZWJH5trEGN8lENaajIfHWmuKyM9dHXm131OnzLR6EbsG3YU/2CX8SvDumUh3DmRu eHM3iSK0odOizvrdlip4nIaeiNA+gkW6f1eQ/l8lI0l03VhaYO0GDsmMJuZzLeh0kzc+ 0rog== X-Received: by 10.194.90.106 with SMTP id bv10mr26081996wjb.20.1402911206387; Mon, 16 Jun 2014 02:33:26 -0700 (PDT) Received: from [192.168.0.8] (cpc25-cmbg14-2-0-cust121.5-4.cable.virginm.net. [213.106.112.122]) by mx.google.com with ESMTPSA id gi8sm13582242wib.8.2014.06.16.02.33.24 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 16 Jun 2014 02:33:25 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\)) From: Thomas Gazagnaire In-Reply-To: Date: Mon, 16 Jun 2014 10:33:23 +0100 Message-Id: <1233494D-A05A-4F52-BFE7-9773BD566372@gazagnaire.org> References: To: David Scott X-Mailer: Apple Mail (2.1878.2) Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] towards a common Mirage 'FLOW' signature X-BeenThere: mirageos-devel@lists.xenproject.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 a bit late in the discussion, but: > * consoles > * xen inter-domain vchan connections > * plain TCP > * (hopefully) TLS connections For git, we also need in/out channels over the execution of an SSH program execution (ssh git-fetch-pack ). I think your change will also allow to do that so that's good :-) 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 Jun 16 09:39:40 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 16 Jun 2014 09:39: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 1WwTNy-0006eV-AP; Mon, 16 Jun 2014 09:39:30 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WwTNx-0006eQ-15 for mirageos-devel@lists.xenproject.org; Mon, 16 Jun 2014 09:39:29 +0000 Received: from [85.158.143.35:10225] by server-3.bemta-4.messagelabs.com id 1E/9E-16194-05BBE935; Mon, 16 Jun 2014 09:39:28 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-7.tower-21.messagelabs.com!1402911567!11607039!1 X-Originating-IP: [74.125.82.172] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7251 invoked from network); 16 Jun 2014 09:39:27 -0000 Received: from mail-we0-f172.google.com (HELO mail-we0-f172.google.com) (74.125.82.172) by server-7.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 16 Jun 2014 09:39:27 -0000 Received: by mail-we0-f172.google.com with SMTP id u57so5471351wes.17 for ; Mon, 16 Jun 2014 02:39:27 -0700 (PDT) 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=P1qmG+3E8yXFGRiDDbgvA7oWRFQvt4hcoelaNd2VETo=; b=nE+KRImAjjWJWlcGYpUdO2hEZmbK9oPcq2S90Srd+k34w3960IP7hkxyI4LnHDqLsS nVMsjS/cexvw+9t35M6Qy379ChGob7gzw5ozAfheEVogg40cdXECN4dGWpE/HjwWK7HU u81gz76Iba9c77NAMZrWc6oRJf9YtNyQZ5cLmsJYkOj7mHsGdaIiOLlxrCGP0N0N58n0 5T4CkfSM35bkhUivuP4/JTydx9VTHBZ3jHlmxUnstVhnQGgUX1z24jKFqwCtbW+5C88O PZsw4BPlVaOWDOBn351dnLyy9VgHeWd1EqJlF5G+5cRipHROuEfXcOMpn3PgzFX9ys19 yfoA== X-Received: by 10.194.104.129 with SMTP id ge1mr2196171wjb.94.1402911566981; Mon, 16 Jun 2014 02:39:26 -0700 (PDT) Received: from [192.168.0.8] (cpc25-cmbg14-2-0-cust121.5-4.cable.virginm.net. [213.106.112.122]) by mx.google.com with ESMTPSA id ej2sm17906762wjd.21.2014.06.16.02.39.24 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 16 Jun 2014 02:39:25 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\)) From: Thomas Gazagnaire In-Reply-To: Date: Mon, 16 Jun 2014 10:39:23 +0100 Message-Id: <55EDE239-B359-4930-9E4D-C899E8DB3E22@gazagnaire.org> References: , <0846576A-E0E8-4F35-99FA-6729250975B5@recoil.org>, <5373900A.4030901@cam.ac.uk>, <9AF01405-3475-4FC7-A308-4075DE335BEF@recoil.org>, <53739693.2050308@cam.ac.uk>, <0E252CC1-CF37-4611-B633-D427E2051B7D@recoil.org>, , <4E8A3FB1-5F4E-4BDC-A071-8F83730AF610@citrix.com>, <25EA0DB9-6DA8-4C6F-BAD9-587D3CEC4D55@recoil.org> To: Anil Madhavapeddy X-Mailer: Apple Mail (2.1878.2) Cc: David Scott , John Else , "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Monitoring MirageOS guests on CubieBoard2 X-BeenThere: mirageos-devel@lists.xenproject.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 medium-term goal is to sample the RRD stats into the Irmin git backend (https://github.com/mirage/irmin) that Thomas Gazagnaire is working on. This will let applications have a non-blocking stats delivery model via RRD, and still provide a persistent data structure for long-term accrual of data (e.g. via Git pushing to an aggregation server that isn't a tiny embedded device). I think we should be careful here. The main goal of RRD stats is to report long-running -- and possibly very intensive -- program stats with a bounded amount of memory. If you store the RRDs in irmin, you'll loose that property: your history will grow forever, possibly quite fast. I get you'll loose some performance as well as persistent arrays are less far efficient than the usual mutable arrays. So yes, that's possible to store RRDs stats in irmin, but I'm not sure that what we really want usually in this scenario. Thomas > I did ponder exposing this via SNMP, and then ran away screaming when I looked at the protocol description after some time away for it. Let's put that down as a 'future feature' :-) > >> This really is a tremendous environment for small board solutions. Thanks to everyone for make this available. >> >> I'm definitely not worthy. > > You most definitely are! Very much looking forward to seeing what uses you put it to. > > cheers, > Anil > > > _______________________________________________ > 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 Jun 16 09:39:40 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 16 Jun 2014 09:39: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 1WwTNy-0006eV-AP; Mon, 16 Jun 2014 09:39:30 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WwTNx-0006eQ-15 for mirageos-devel@lists.xenproject.org; Mon, 16 Jun 2014 09:39:29 +0000 Received: from [85.158.143.35:10225] by server-3.bemta-4.messagelabs.com id 1E/9E-16194-05BBE935; Mon, 16 Jun 2014 09:39:28 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-7.tower-21.messagelabs.com!1402911567!11607039!1 X-Originating-IP: [74.125.82.172] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7251 invoked from network); 16 Jun 2014 09:39:27 -0000 Received: from mail-we0-f172.google.com (HELO mail-we0-f172.google.com) (74.125.82.172) by server-7.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 16 Jun 2014 09:39:27 -0000 Received: by mail-we0-f172.google.com with SMTP id u57so5471351wes.17 for ; Mon, 16 Jun 2014 02:39:27 -0700 (PDT) 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=P1qmG+3E8yXFGRiDDbgvA7oWRFQvt4hcoelaNd2VETo=; b=nE+KRImAjjWJWlcGYpUdO2hEZmbK9oPcq2S90Srd+k34w3960IP7hkxyI4LnHDqLsS nVMsjS/cexvw+9t35M6Qy379ChGob7gzw5ozAfheEVogg40cdXECN4dGWpE/HjwWK7HU u81gz76Iba9c77NAMZrWc6oRJf9YtNyQZ5cLmsJYkOj7mHsGdaIiOLlxrCGP0N0N58n0 5T4CkfSM35bkhUivuP4/JTydx9VTHBZ3jHlmxUnstVhnQGgUX1z24jKFqwCtbW+5C88O PZsw4BPlVaOWDOBn351dnLyy9VgHeWd1EqJlF5G+5cRipHROuEfXcOMpn3PgzFX9ys19 yfoA== X-Received: by 10.194.104.129 with SMTP id ge1mr2196171wjb.94.1402911566981; Mon, 16 Jun 2014 02:39:26 -0700 (PDT) Received: from [192.168.0.8] (cpc25-cmbg14-2-0-cust121.5-4.cable.virginm.net. [213.106.112.122]) by mx.google.com with ESMTPSA id ej2sm17906762wjd.21.2014.06.16.02.39.24 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 16 Jun 2014 02:39:25 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\)) From: Thomas Gazagnaire In-Reply-To: Date: Mon, 16 Jun 2014 10:39:23 +0100 Message-Id: <55EDE239-B359-4930-9E4D-C899E8DB3E22@gazagnaire.org> References: , <0846576A-E0E8-4F35-99FA-6729250975B5@recoil.org>, <5373900A.4030901@cam.ac.uk>, <9AF01405-3475-4FC7-A308-4075DE335BEF@recoil.org>, <53739693.2050308@cam.ac.uk>, <0E252CC1-CF37-4611-B633-D427E2051B7D@recoil.org>, , <4E8A3FB1-5F4E-4BDC-A071-8F83730AF610@citrix.com>, <25EA0DB9-6DA8-4C6F-BAD9-587D3CEC4D55@recoil.org> To: Anil Madhavapeddy X-Mailer: Apple Mail (2.1878.2) Cc: David Scott , John Else , "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Monitoring MirageOS guests on CubieBoard2 X-BeenThere: mirageos-devel@lists.xenproject.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 medium-term goal is to sample the RRD stats into the Irmin git backend (https://github.com/mirage/irmin) that Thomas Gazagnaire is working on. This will let applications have a non-blocking stats delivery model via RRD, and still provide a persistent data structure for long-term accrual of data (e.g. via Git pushing to an aggregation server that isn't a tiny embedded device). I think we should be careful here. The main goal of RRD stats is to report long-running -- and possibly very intensive -- program stats with a bounded amount of memory. If you store the RRDs in irmin, you'll loose that property: your history will grow forever, possibly quite fast. I get you'll loose some performance as well as persistent arrays are less far efficient than the usual mutable arrays. So yes, that's possible to store RRDs stats in irmin, but I'm not sure that what we really want usually in this scenario. Thomas > I did ponder exposing this via SNMP, and then ran away screaming when I looked at the protocol description after some time away for it. Let's put that down as a 'future feature' :-) > >> This really is a tremendous environment for small board solutions. Thanks to everyone for make this available. >> >> I'm definitely not worthy. > > You most definitely are! Very much looking forward to seeing what uses you put it to. > > cheers, > Anil > > > _______________________________________________ > 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 Jun 16 09:44:02 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 16 Jun 2014 09:44: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 1WwTSF-0006iy-8G; Mon, 16 Jun 2014 09:43:55 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WwTSD-0006it-MA for mirageos-devel@lists.xenproject.org; Mon, 16 Jun 2014 09:43:53 +0000 Received: from [85.158.137.68:37343] by server-15.bemta-3.messagelabs.com id 15/F4-13757-85CBE935; Mon, 16 Jun 2014 09:43:52 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-9.tower-31.messagelabs.com!1402911832!6569682!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10418 invoked from network); 16 Jun 2014 09:43:52 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-9.tower-31.messagelabs.com with SMTP; 16 Jun 2014 09:43:52 -0000 Received: (qmail 14088 invoked by uid 634); 16 Jun 2014 09:43:51 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from cpc11-belf9-2-0-cust355.2-1.cable.virginm.net (HELO [10.0.1.15]) (86.24.61.100) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Mon, 16 Jun 2014 10:43:47 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\)) From: Anil Madhavapeddy In-Reply-To: <55EDE239-B359-4930-9E4D-C899E8DB3E22@gazagnaire.org> Date: Mon, 16 Jun 2014 10:43:45 +0100 Message-Id: References: , <0846576A-E0E8-4F35-99FA-6729250975B5@recoil.org>, <5373900A.4030901@cam.ac.uk>, <9AF01405-3475-4FC7-A308-4075DE335BEF@recoil.org>, <53739693.2050308@cam.ac.uk>, <0E252CC1-CF37-4611-B633-D427E2051B7D@recoil.org>, , <4E8A3FB1-5F4E-4BDC-A071-8F83730AF610@citrix.com>, <25EA0DB9-6DA8-4C6F-BAD9-587D3CEC4D55@recoil.org> <55EDE239-B359-4930-9E4D-C899E8DB3E22@gazagnaire.org> To: Thomas Gazagnaire X-Mailer: Apple Mail (2.1874) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: David Scott , John Else , "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Monitoring MirageOS guests on CubieBoard2 X-BeenThere: mirageos-devel@lists.xenproject.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 Jun 2014, at 10:39, Thomas Gazagnaire wrote: >> The medium-term goal is to sample the RRD stats into the Irmin git backend (https://github.com/mirage/irmin) that Thomas Gazagnaire is working on. This will let applications have a non-blocking stats delivery model via RRD, and still provide a persistent data structure for long-term accrual of data (e.g. via Git pushing to an aggregation server that isn't a tiny embedded device). > > I think we should be careful here. The main goal of RRD stats is to report long-running -- and possibly very intensive -- program stats with a bounded amount of memory. If you store the RRDs in irmin, you'll loose that property: your history will grow forever, possibly quite fast. I get you'll loose some performance as well as persistent arrays are less far efficient than the usual mutable arrays. > > So yes, that's possible to store RRDs stats in irmin, but I'm not sure that what we really want usually in this scenario. Agreed -- I was thinking about longer running analytics though. RRDs normally rotate and aggregate their statistics across a particular time period, and ensure they are fixed size. So we could either use the built-in RRD facility for this, or take advantage of Irmin to take a distributed snapshot of all the VM's RRDs via an Irmin commit (e.g. in order to figure out the total number of TCP connections across a cluster). This data would be pushed *off-cluster* into a bigger aggregation Irmin database, so provides a way out of the RRD world into doing more analytics (perhaps correlating these statistics with log files and other streaming data sources that are also being fed into Irmin) -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 Jun 16 09:44:02 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 16 Jun 2014 09:44: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 1WwTSF-0006iy-8G; Mon, 16 Jun 2014 09:43:55 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WwTSD-0006it-MA for mirageos-devel@lists.xenproject.org; Mon, 16 Jun 2014 09:43:53 +0000 Received: from [85.158.137.68:37343] by server-15.bemta-3.messagelabs.com id 15/F4-13757-85CBE935; Mon, 16 Jun 2014 09:43:52 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-9.tower-31.messagelabs.com!1402911832!6569682!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10418 invoked from network); 16 Jun 2014 09:43:52 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-9.tower-31.messagelabs.com with SMTP; 16 Jun 2014 09:43:52 -0000 Received: (qmail 14088 invoked by uid 634); 16 Jun 2014 09:43:51 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from cpc11-belf9-2-0-cust355.2-1.cable.virginm.net (HELO [10.0.1.15]) (86.24.61.100) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Mon, 16 Jun 2014 10:43:47 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\)) From: Anil Madhavapeddy In-Reply-To: <55EDE239-B359-4930-9E4D-C899E8DB3E22@gazagnaire.org> Date: Mon, 16 Jun 2014 10:43:45 +0100 Message-Id: References: , <0846576A-E0E8-4F35-99FA-6729250975B5@recoil.org>, <5373900A.4030901@cam.ac.uk>, <9AF01405-3475-4FC7-A308-4075DE335BEF@recoil.org>, <53739693.2050308@cam.ac.uk>, <0E252CC1-CF37-4611-B633-D427E2051B7D@recoil.org>, , <4E8A3FB1-5F4E-4BDC-A071-8F83730AF610@citrix.com>, <25EA0DB9-6DA8-4C6F-BAD9-587D3CEC4D55@recoil.org> <55EDE239-B359-4930-9E4D-C899E8DB3E22@gazagnaire.org> To: Thomas Gazagnaire X-Mailer: Apple Mail (2.1874) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: David Scott , John Else , "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Monitoring MirageOS guests on CubieBoard2 X-BeenThere: mirageos-devel@lists.xenproject.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 Jun 2014, at 10:39, Thomas Gazagnaire wrote: >> The medium-term goal is to sample the RRD stats into the Irmin git backend (https://github.com/mirage/irmin) that Thomas Gazagnaire is working on. This will let applications have a non-blocking stats delivery model via RRD, and still provide a persistent data structure for long-term accrual of data (e.g. via Git pushing to an aggregation server that isn't a tiny embedded device). > > I think we should be careful here. The main goal of RRD stats is to report long-running -- and possibly very intensive -- program stats with a bounded amount of memory. If you store the RRDs in irmin, you'll loose that property: your history will grow forever, possibly quite fast. I get you'll loose some performance as well as persistent arrays are less far efficient than the usual mutable arrays. > > So yes, that's possible to store RRDs stats in irmin, but I'm not sure that what we really want usually in this scenario. Agreed -- I was thinking about longer running analytics though. RRDs normally rotate and aggregate their statistics across a particular time period, and ensure they are fixed size. So we could either use the built-in RRD facility for this, or take advantage of Irmin to take a distributed snapshot of all the VM's RRDs via an Irmin commit (e.g. in order to figure out the total number of TCP connections across a cluster). This data would be pushed *off-cluster* into a bigger aggregation Irmin database, so provides a way out of the RRD world into doing more analytics (perhaps correlating these statistics with log files and other streaming data sources that are also being fed into Irmin) -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 Jun 16 09:52:54 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 16 Jun 2014 09: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 1WwTaq-0007U8-Jk; Mon, 16 Jun 2014 09:52:48 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WwTap-0007Tw-EX for mirageos-devel@lists.xenproject.org; Mon, 16 Jun 2014 09:52:47 +0000 Received: from [85.158.139.211:30516] by server-3.bemta-5.messagelabs.com id 80/4D-01676-E6EBE935; Mon, 16 Jun 2014 09:52:46 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-15.tower-206.messagelabs.com!1402912365!6798834!1 X-Originating-IP: [209.85.212.170] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10040 invoked from network); 16 Jun 2014 09:52:45 -0000 Received: from mail-wi0-f170.google.com (HELO mail-wi0-f170.google.com) (209.85.212.170) by server-15.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 16 Jun 2014 09:52:45 -0000 Received: by mail-wi0-f170.google.com with SMTP id cc10so4964214wib.5 for ; Mon, 16 Jun 2014 02:52:45 -0700 (PDT) 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=WDqEY6OrfuukrvszShTwYg9LBorAK893yKydDBhRC3Q=; b=B897PRysV2ZQ4wDLK99brttGuxkQ9zpjx3cytL1BGMJHkyuUOJPzLJog93m7Pei1Md WR2kCnLanHiwnsUFUO14/UKdvyzerlUS6DNtXZ8yW+uWXb3mI6DvYWoOWMJ3LECmY7FV x2MgXiXRUyYFKytrxY1gu60eJuBI4r8BT8g4HOHCYtCxJZSQ5Mjwiw1XCzebA9XMhHMR cyL08mkVNwzIUToPx5AbuOx6EnN2vGBWlkUxk9GNnKuMNwtLUm4atk1HUz4OuyOmSnaY mk+JcT+eZbTvUd6glxmpd/0vMS93//rPpgVyh2LYFyAZWeQVNf1JJp+0trt6VOFTo5Ui U6Kg== X-Received: by 10.194.178.99 with SMTP id cx3mr26535386wjc.54.1402912365181; Mon, 16 Jun 2014 02:52:45 -0700 (PDT) Received: from [192.168.0.8] (cpc25-cmbg14-2-0-cust121.5-4.cable.virginm.net. [213.106.112.122]) by mx.google.com with ESMTPSA id o3sm13657684wiz.24.2014.06.16.02.52.42 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 16 Jun 2014 02:52:43 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\)) From: Thomas Gazagnaire In-Reply-To: Date: Mon, 16 Jun 2014 10:52:41 +0100 Message-Id: <7292DEE0-053C-486F-9E96-BB5DF44D44BE@gazagnaire.org> References: , <0846576A-E0E8-4F35-99FA-6729250975B5@recoil.org>, <5373900A.4030901@cam.ac.uk>, <9AF01405-3475-4FC7-A308-4075DE335BEF@recoil.org>, <53739693.2050308@cam.ac.uk>, <0E252CC1-CF37-4611-B633-D427E2051B7D@recoil.org>, , <4E8A3FB1-5F4E-4BDC-A071-8F83730AF610@citrix.com>, <25EA0DB9-6DA8-4C6F-BAD9-587D3CEC4D55@recoil.org> <55EDE239-B359-4930-9E4D-C899E8DB3E22@gazagnaire.org> To: Anil Madhavapeddy X-Mailer: Apple Mail (2.1878.2) Cc: David Scott , John Else , "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Monitoring MirageOS guests on CubieBoard2 X-BeenThere: mirageos-devel@lists.xenproject.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 medium-term goal is to sample the RRD stats into the Irmin git backend (https://github.com/mirage/irmin) that Thomas Gazagnaire is working on. This will let applications have a non-blocking stats delivery model via RRD, and still provide a persistent data structure for long-term accrual of data (e.g. via Git pushing to an aggregation server that isn't a tiny embedded device). >> >> I think we should be careful here. The main goal of RRD stats is to report long-running -- and possibly very intensive -- program stats with a bounded amount of memory. If you store the RRDs in irmin, you'll loose that property: your history will grow forever, possibly quite fast. I get you'll loose some performance as well as persistent arrays are less far efficient than the usual mutable arrays. >> >> So yes, that's possible to store RRDs stats in irmin, but I'm not sure that what we really want usually in this scenario. > > Agreed -- I was thinking about longer running analytics though. RRDs normally rotate and aggregate their statistics across a particular time period, and ensure they are fixed size. > > So we could either use the built-in RRD facility for this, or take advantage of Irmin to take a distributed snapshot of all the VM's RRDs via an Irmin commit (e.g. in order to figure out the total number of TCP connections across a cluster). > > This data would be pushed *off-cluster* into a bigger aggregation Irmin database, so provides a way out of the RRD world into doing more analytics (perhaps correlating these statistics with log files and other streaming data sources that are also being fed into Irmin) Ha right I see. That's indeed a good idea. 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 Jun 16 09:52:54 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 16 Jun 2014 09: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 1WwTaq-0007U8-Jk; Mon, 16 Jun 2014 09:52:48 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WwTap-0007Tw-EX for mirageos-devel@lists.xenproject.org; Mon, 16 Jun 2014 09:52:47 +0000 Received: from [85.158.139.211:30516] by server-3.bemta-5.messagelabs.com id 80/4D-01676-E6EBE935; Mon, 16 Jun 2014 09:52:46 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-15.tower-206.messagelabs.com!1402912365!6798834!1 X-Originating-IP: [209.85.212.170] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10040 invoked from network); 16 Jun 2014 09:52:45 -0000 Received: from mail-wi0-f170.google.com (HELO mail-wi0-f170.google.com) (209.85.212.170) by server-15.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 16 Jun 2014 09:52:45 -0000 Received: by mail-wi0-f170.google.com with SMTP id cc10so4964214wib.5 for ; Mon, 16 Jun 2014 02:52:45 -0700 (PDT) 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=WDqEY6OrfuukrvszShTwYg9LBorAK893yKydDBhRC3Q=; b=B897PRysV2ZQ4wDLK99brttGuxkQ9zpjx3cytL1BGMJHkyuUOJPzLJog93m7Pei1Md WR2kCnLanHiwnsUFUO14/UKdvyzerlUS6DNtXZ8yW+uWXb3mI6DvYWoOWMJ3LECmY7FV x2MgXiXRUyYFKytrxY1gu60eJuBI4r8BT8g4HOHCYtCxJZSQ5Mjwiw1XCzebA9XMhHMR cyL08mkVNwzIUToPx5AbuOx6EnN2vGBWlkUxk9GNnKuMNwtLUm4atk1HUz4OuyOmSnaY mk+JcT+eZbTvUd6glxmpd/0vMS93//rPpgVyh2LYFyAZWeQVNf1JJp+0trt6VOFTo5Ui U6Kg== X-Received: by 10.194.178.99 with SMTP id cx3mr26535386wjc.54.1402912365181; Mon, 16 Jun 2014 02:52:45 -0700 (PDT) Received: from [192.168.0.8] (cpc25-cmbg14-2-0-cust121.5-4.cable.virginm.net. [213.106.112.122]) by mx.google.com with ESMTPSA id o3sm13657684wiz.24.2014.06.16.02.52.42 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 16 Jun 2014 02:52:43 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\)) From: Thomas Gazagnaire In-Reply-To: Date: Mon, 16 Jun 2014 10:52:41 +0100 Message-Id: <7292DEE0-053C-486F-9E96-BB5DF44D44BE@gazagnaire.org> References: , <0846576A-E0E8-4F35-99FA-6729250975B5@recoil.org>, <5373900A.4030901@cam.ac.uk>, <9AF01405-3475-4FC7-A308-4075DE335BEF@recoil.org>, <53739693.2050308@cam.ac.uk>, <0E252CC1-CF37-4611-B633-D427E2051B7D@recoil.org>, , <4E8A3FB1-5F4E-4BDC-A071-8F83730AF610@citrix.com>, <25EA0DB9-6DA8-4C6F-BAD9-587D3CEC4D55@recoil.org> <55EDE239-B359-4930-9E4D-C899E8DB3E22@gazagnaire.org> To: Anil Madhavapeddy X-Mailer: Apple Mail (2.1878.2) Cc: David Scott , John Else , "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Monitoring MirageOS guests on CubieBoard2 X-BeenThere: mirageos-devel@lists.xenproject.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 medium-term goal is to sample the RRD stats into the Irmin git backend (https://github.com/mirage/irmin) that Thomas Gazagnaire is working on. This will let applications have a non-blocking stats delivery model via RRD, and still provide a persistent data structure for long-term accrual of data (e.g. via Git pushing to an aggregation server that isn't a tiny embedded device). >> >> I think we should be careful here. The main goal of RRD stats is to report long-running -- and possibly very intensive -- program stats with a bounded amount of memory. If you store the RRDs in irmin, you'll loose that property: your history will grow forever, possibly quite fast. I get you'll loose some performance as well as persistent arrays are less far efficient than the usual mutable arrays. >> >> So yes, that's possible to store RRDs stats in irmin, but I'm not sure that what we really want usually in this scenario. > > Agreed -- I was thinking about longer running analytics though. RRDs normally rotate and aggregate their statistics across a particular time period, and ensure they are fixed size. > > So we could either use the built-in RRD facility for this, or take advantage of Irmin to take a distributed snapshot of all the VM's RRDs via an Irmin commit (e.g. in order to figure out the total number of TCP connections across a cluster). > > This data would be pushed *off-cluster* into a bigger aggregation Irmin database, so provides a way out of the RRD world into doing more analytics (perhaps correlating these statistics with log files and other streaming data sources that are also being fed into Irmin) Ha right I see. That's indeed a good idea. 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 Jun 16 10:26:23 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 16 Jun 2014 10:26: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 1WwU79-0000XH-89; Mon, 16 Jun 2014 10:26:11 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WwU77-0000XC-LB for mirageos-devel@lists.xenproject.org; Mon, 16 Jun 2014 10:26:09 +0000 Received: from [193.109.254.147:48303] by server-15.bemta-14.messagelabs.com id 2C/83-15813-046CE935; Mon, 16 Jun 2014 10:26:08 +0000 X-Env-Sender: talex5@gmail.com X-Msg-Ref: server-16.tower-27.messagelabs.com!1402914363!6087991!1 X-Originating-IP: [209.85.214.172] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, ML_RADAR_SPEW_LINKS_23,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23566 invoked from network); 16 Jun 2014 10:26:04 -0000 Received: from mail-ob0-f172.google.com (HELO mail-ob0-f172.google.com) (209.85.214.172) by server-16.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 16 Jun 2014 10:26:04 -0000 Received: by mail-ob0-f172.google.com with SMTP id uy5so5488172obc.17 for ; Mon, 16 Jun 2014 03:26:03 -0700 (PDT) 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=rRaQwZm06vFteHsJroz+o4siRN9IUeBDeO5JuNy+x4I=; b=js3iEeiFu7jK5Ey21kCpGze3SRKia/zTEEN7FFErbLoqSZCE23LC7AQX+cdKAiBh5k UHb7rHh3sI4DaZLikVbqJ6tR6OOW8ahHiBS4hAC2dw9DiGO+fFTnRnoOOj9Cx/Kvf1iU vaOyByNOu7qlfzV/1wZFg/N65/iUoKBhb8kyj7S7qXvTP1qJ3jnrWcnCQciI+TflTMDq gtsjLrs1m/k0WndZpYgoItsCzijiTDHcNxp9W6huwBuDElL3jaLGd/h6lS5bxi7i9Hma hpDNiE48JQKW7luB2ggnbMb9gxqY27hPp8oRDZWhKQ+k1yNKJxmSgl57p46h8orLZXrK hNnA== MIME-Version: 1.0 X-Received: by 10.182.200.169 with SMTP id jt9mr19422151obc.0.1402914363219; Mon, 16 Jun 2014 03:26:03 -0700 (PDT) Received: by 10.76.92.5 with HTTP; Mon, 16 Jun 2014 03:26:03 -0700 (PDT) In-Reply-To: <12D67D67-3DAB-4033-BFC5-C7DBCBA64F34@recoil.org> References: <297FC9DB-3A4E-41A5-B00E-9DEF62C625E6@recoil.org> <12D67D67-3DAB-4033-BFC5-C7DBCBA64F34@recoil.org> Date: Mon, 16 Jun 2014 11:26:03 +0100 Message-ID: From: Thomas Leonard To: Anil Madhavapeddy Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Mirage on Xen/ARM status X-BeenThere: mirageos-devel@lists.xenproject.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 14 June 2014 06:55, Anil Madhavapeddy wrote: > On 13 Jun 2014, at 17:53, Thomas Leonard wrote: >> >> I've been going through mirage-skeleton trying all the examples on ARM >> (Cubietruck running Xen). Here are the results: >> >> console: works (I also patched it to try reading from the console, and >> that works too, after a minor patch to mirage-console; now merged) >> >> network: works >> block: works >> >> dns: fails to build >> Error: No implementations provided for the following modules: >> Lwt_unix referenced from >> /root/.opam/4.01.0/lib/dns/lwt-core.cmxa(Dns_resolver) > > This look the euphemistic "architecture independent issue". Need to see how Unix snuck into the ocaml-dns core and add a test for that. Could you create an issue on ocaml-dns for this? https://github.com/mirage/ocaml-dns/issues/13 Looks like it's just some test code that needs it anyway ("resolving recoil.org"). If I remove that bit, it answers DNS queries successfully. >> ethifv4: seems to work (except for TCP: it shows "TCP retransmission >> on timer seq = 452901213" instead of connecting) > > Can't verify from where I am, but it may just be the stack isn't configured. Ah, I was just confused about what this does. I thought the IP address in the code was the one it would listen on, but it looks like it only uses it until it gets the real address by DHCP. Connecting using the DHCP-assigned address, it works. UDP seemed to be working because it logs all packets, regardless of destination address. >> io_page: works >> kv_ro: works (prints YES! a lot, anyway) >> kv_ro_crunch: works (as kv_ro) >> ping: works (note: reports UDP traffic as "TCP" due to a bug) >> stackv4: works (HTTP on 80, TCP on 8080 and UDP on 53) >> >> static_website: works, after adding re.str. Otherwise you get: >> Error: No implementations provided for the following modules: >> Re_str referenced from dispatch.cmx > > Odd, this was fixed a few weeks ago. Need to look through the pull reqs in case I forgot to merge it. Ah, you're right. I hadn't updated. >> So, it's looking pretty good :-) > > Yes! The lack of ARM specific issues in the OCaml native code backend isn't a surprise, but still a relief. > >> A few random notes: >> >> - Lack of progress reports from mirage is a problem on x86, but it's >> worse on ARM because it's so much slower. > > Yes, this one has a bug open on mirage/mirage. We need to tee the output from the tool really. [ https://github.com/mirage/mirage/issues/205 ] >> - opam got very confused at one point, somehow uninstalled mirage and >> then wouldn't bring it back (no error shown). Here's a sample: >> >> root@softbuild:~# mirage >> -bash: mirage: command not found >> root@softbuild:~# opam reinstall mirage >> [ERROR] mirage is not installed. >> >> 'opam reinstall mirage' failed. >> root@softbuild:~# opam install mirage >> root@softbuild:~# mirage >> -bash: mirage: command not found >> root@softbuild:~# opam reinstall mirage >> [ERROR] mirage is not installed. >> >> Installing "aspcud" sorted it all out (and makes it faster!). > > Aspects is pretty much a necessity in opam 1.1.1; most packaging marks it as recommended now. Hopefully Thomas can fix the internal solver in 1.2 with some more heuristic magic :-) Sounds good. The odd thing is that it didn't report any error, despite (I presume) deciding not to install the program I asked for. > The recompile came from the libraries that the mirage tool needs being recompiled due to a depopt, being uninstalled during that, and then error recovery not kicking (possibly broken solver) > > This is much improved in opam 1.2, and using Thomas' Makefile generator instead of directly calling opam will help the user control when the package installation happens. > >> - I was using the system ocaml, which lacked ocamlopt.opt, slowing >> down the builds. Using "opam sw 4.01.0" sorted that out. > > Did you install the ocaml-native-compilers package? Ah, that would explain it! >> - mirage-console's install rule has some problems at the moment. Use >> "ocamlfind remove" to remove the various bits manually and try again >> if it happens. >> >> https://github.com/mirage/mirage-console/issues/17 >> >> - direct_stackv4_with_default_ipv4 is a bit annoying. It contains an >> IP address hard-coded into mirage, but it makes it difficult to see >> how to change it for your own network. It might be better to use >> direct_stackv4_with_static_ipv4 for the examples. > > Yeah, feel free to normalise any of these example and send a pull req btw. They do need a spring clean (Mort and I will look at this soon for our ECOOP tutorial at any rate) -- 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 Jun 16 10:26:23 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 16 Jun 2014 10:26: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 1WwU79-0000XH-89; Mon, 16 Jun 2014 10:26:11 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WwU77-0000XC-LB for mirageos-devel@lists.xenproject.org; Mon, 16 Jun 2014 10:26:09 +0000 Received: from [193.109.254.147:48303] by server-15.bemta-14.messagelabs.com id 2C/83-15813-046CE935; Mon, 16 Jun 2014 10:26:08 +0000 X-Env-Sender: talex5@gmail.com X-Msg-Ref: server-16.tower-27.messagelabs.com!1402914363!6087991!1 X-Originating-IP: [209.85.214.172] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, ML_RADAR_SPEW_LINKS_23,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23566 invoked from network); 16 Jun 2014 10:26:04 -0000 Received: from mail-ob0-f172.google.com (HELO mail-ob0-f172.google.com) (209.85.214.172) by server-16.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 16 Jun 2014 10:26:04 -0000 Received: by mail-ob0-f172.google.com with SMTP id uy5so5488172obc.17 for ; Mon, 16 Jun 2014 03:26:03 -0700 (PDT) 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=rRaQwZm06vFteHsJroz+o4siRN9IUeBDeO5JuNy+x4I=; b=js3iEeiFu7jK5Ey21kCpGze3SRKia/zTEEN7FFErbLoqSZCE23LC7AQX+cdKAiBh5k UHb7rHh3sI4DaZLikVbqJ6tR6OOW8ahHiBS4hAC2dw9DiGO+fFTnRnoOOj9Cx/Kvf1iU vaOyByNOu7qlfzV/1wZFg/N65/iUoKBhb8kyj7S7qXvTP1qJ3jnrWcnCQciI+TflTMDq gtsjLrs1m/k0WndZpYgoItsCzijiTDHcNxp9W6huwBuDElL3jaLGd/h6lS5bxi7i9Hma hpDNiE48JQKW7luB2ggnbMb9gxqY27hPp8oRDZWhKQ+k1yNKJxmSgl57p46h8orLZXrK hNnA== MIME-Version: 1.0 X-Received: by 10.182.200.169 with SMTP id jt9mr19422151obc.0.1402914363219; Mon, 16 Jun 2014 03:26:03 -0700 (PDT) Received: by 10.76.92.5 with HTTP; Mon, 16 Jun 2014 03:26:03 -0700 (PDT) In-Reply-To: <12D67D67-3DAB-4033-BFC5-C7DBCBA64F34@recoil.org> References: <297FC9DB-3A4E-41A5-B00E-9DEF62C625E6@recoil.org> <12D67D67-3DAB-4033-BFC5-C7DBCBA64F34@recoil.org> Date: Mon, 16 Jun 2014 11:26:03 +0100 Message-ID: From: Thomas Leonard To: Anil Madhavapeddy Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Mirage on Xen/ARM status X-BeenThere: mirageos-devel@lists.xenproject.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 14 June 2014 06:55, Anil Madhavapeddy wrote: > On 13 Jun 2014, at 17:53, Thomas Leonard wrote: >> >> I've been going through mirage-skeleton trying all the examples on ARM >> (Cubietruck running Xen). Here are the results: >> >> console: works (I also patched it to try reading from the console, and >> that works too, after a minor patch to mirage-console; now merged) >> >> network: works >> block: works >> >> dns: fails to build >> Error: No implementations provided for the following modules: >> Lwt_unix referenced from >> /root/.opam/4.01.0/lib/dns/lwt-core.cmxa(Dns_resolver) > > This look the euphemistic "architecture independent issue". Need to see how Unix snuck into the ocaml-dns core and add a test for that. Could you create an issue on ocaml-dns for this? https://github.com/mirage/ocaml-dns/issues/13 Looks like it's just some test code that needs it anyway ("resolving recoil.org"). If I remove that bit, it answers DNS queries successfully. >> ethifv4: seems to work (except for TCP: it shows "TCP retransmission >> on timer seq = 452901213" instead of connecting) > > Can't verify from where I am, but it may just be the stack isn't configured. Ah, I was just confused about what this does. I thought the IP address in the code was the one it would listen on, but it looks like it only uses it until it gets the real address by DHCP. Connecting using the DHCP-assigned address, it works. UDP seemed to be working because it logs all packets, regardless of destination address. >> io_page: works >> kv_ro: works (prints YES! a lot, anyway) >> kv_ro_crunch: works (as kv_ro) >> ping: works (note: reports UDP traffic as "TCP" due to a bug) >> stackv4: works (HTTP on 80, TCP on 8080 and UDP on 53) >> >> static_website: works, after adding re.str. Otherwise you get: >> Error: No implementations provided for the following modules: >> Re_str referenced from dispatch.cmx > > Odd, this was fixed a few weeks ago. Need to look through the pull reqs in case I forgot to merge it. Ah, you're right. I hadn't updated. >> So, it's looking pretty good :-) > > Yes! The lack of ARM specific issues in the OCaml native code backend isn't a surprise, but still a relief. > >> A few random notes: >> >> - Lack of progress reports from mirage is a problem on x86, but it's >> worse on ARM because it's so much slower. > > Yes, this one has a bug open on mirage/mirage. We need to tee the output from the tool really. [ https://github.com/mirage/mirage/issues/205 ] >> - opam got very confused at one point, somehow uninstalled mirage and >> then wouldn't bring it back (no error shown). Here's a sample: >> >> root@softbuild:~# mirage >> -bash: mirage: command not found >> root@softbuild:~# opam reinstall mirage >> [ERROR] mirage is not installed. >> >> 'opam reinstall mirage' failed. >> root@softbuild:~# opam install mirage >> root@softbuild:~# mirage >> -bash: mirage: command not found >> root@softbuild:~# opam reinstall mirage >> [ERROR] mirage is not installed. >> >> Installing "aspcud" sorted it all out (and makes it faster!). > > Aspects is pretty much a necessity in opam 1.1.1; most packaging marks it as recommended now. Hopefully Thomas can fix the internal solver in 1.2 with some more heuristic magic :-) Sounds good. The odd thing is that it didn't report any error, despite (I presume) deciding not to install the program I asked for. > The recompile came from the libraries that the mirage tool needs being recompiled due to a depopt, being uninstalled during that, and then error recovery not kicking (possibly broken solver) > > This is much improved in opam 1.2, and using Thomas' Makefile generator instead of directly calling opam will help the user control when the package installation happens. > >> - I was using the system ocaml, which lacked ocamlopt.opt, slowing >> down the builds. Using "opam sw 4.01.0" sorted that out. > > Did you install the ocaml-native-compilers package? Ah, that would explain it! >> - mirage-console's install rule has some problems at the moment. Use >> "ocamlfind remove" to remove the various bits manually and try again >> if it happens. >> >> https://github.com/mirage/mirage-console/issues/17 >> >> - direct_stackv4_with_default_ipv4 is a bit annoying. It contains an >> IP address hard-coded into mirage, but it makes it difficult to see >> how to change it for your own network. It might be better to use >> direct_stackv4_with_static_ipv4 for the examples. > > Yeah, feel free to normalise any of these example and send a pull req btw. They do need a spring clean (Mort and I will look at this soon for our ECOOP tutorial at any rate) -- 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 Jun 16 23:33:37 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 16 Jun 2014 23:33: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 1WwgP5-0000dO-45; Mon, 16 Jun 2014 23:33:31 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WwgP3-0000dE-So for mirageos-devel@lists.xenproject.org; Mon, 16 Jun 2014 23:33:30 +0000 Received: from [85.158.143.35:63386] by server-2.bemta-4.messagelabs.com id 07/42-06539-9CE7F935; Mon, 16 Jun 2014 23:33:29 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-14.tower-21.messagelabs.com!1402961608!11796754!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 18728 invoked from network); 16 Jun 2014 23:33:28 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-14.tower-21.messagelabs.com with SMTP; 16 Jun 2014 23:33:28 -0000 Received: (qmail 17213 invoked by uid 634); 16 Jun 2014 23:33:27 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from cpc11-belf9-2-0-cust355.2-1.cable.virginm.net (HELO [10.0.1.15]) (86.24.61.100) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Tue, 17 Jun 2014 00:33:24 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\)) From: Anil Madhavapeddy In-Reply-To: Date: Tue, 17 Jun 2014 00:33:22 +0100 Message-Id: <4F3D70F5-09E4-41B6-B2B7-C5572AA67906@recoil.org> References: <297FC9DB-3A4E-41A5-B00E-9DEF62C625E6@recoil.org> <12D67D67-3DAB-4033-BFC5-C7DBCBA64F34@recoil.org> To: Thomas Leonard X-Mailer: Apple Mail (2.1874) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Mirage on Xen/ARM status X-BeenThere: mirageos-devel@lists.xenproject.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 Jun 2014, at 11:26, Thomas Leonard wrote: >>> >>> dns: fails to build >>> Error: No implementations provided for the following modules: >>> Lwt_unix referenced from >>> /root/.opam/4.01.0/lib/dns/lwt-core.cmxa(Dns_resolver) >> >> This look the euphemistic "architecture independent issue". Need to see how Unix snuck into the ocaml-dns core and add a test for that. Could you create an issue on ocaml-dns for this? > > https://github.com/mirage/ocaml-dns/issues/13 > > Looks like it's just some test code that needs it anyway ("resolving > recoil.org"). If I remove that bit, it answers DNS queries > successfully. This actually had an unrelated bug that broke it on Xen. During a refactoring, the memory allocation in Dns.Buf.t reverted to using Bigarray.create, which does not allocate page-aligned buffers. This then causes the Netfront driver on Xen to send garbage, since it can only zero-copy whole pages. I fixed it to use Io-page instead in https://github.com/mirage/ocaml-dns/pull/14 I'll release that as ocaml-dns-0.9.0 tomorrow, and update mirage-skeleton with the tweak to lift out the timer logic into the client call. -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 Jun 16 23:33:37 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 16 Jun 2014 23:33: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 1WwgP5-0000dO-45; Mon, 16 Jun 2014 23:33:31 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WwgP3-0000dE-So for mirageos-devel@lists.xenproject.org; Mon, 16 Jun 2014 23:33:30 +0000 Received: from [85.158.143.35:63386] by server-2.bemta-4.messagelabs.com id 07/42-06539-9CE7F935; Mon, 16 Jun 2014 23:33:29 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-14.tower-21.messagelabs.com!1402961608!11796754!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 18728 invoked from network); 16 Jun 2014 23:33:28 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-14.tower-21.messagelabs.com with SMTP; 16 Jun 2014 23:33:28 -0000 Received: (qmail 17213 invoked by uid 634); 16 Jun 2014 23:33:27 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from cpc11-belf9-2-0-cust355.2-1.cable.virginm.net (HELO [10.0.1.15]) (86.24.61.100) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Tue, 17 Jun 2014 00:33:24 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\)) From: Anil Madhavapeddy In-Reply-To: Date: Tue, 17 Jun 2014 00:33:22 +0100 Message-Id: <4F3D70F5-09E4-41B6-B2B7-C5572AA67906@recoil.org> References: <297FC9DB-3A4E-41A5-B00E-9DEF62C625E6@recoil.org> <12D67D67-3DAB-4033-BFC5-C7DBCBA64F34@recoil.org> To: Thomas Leonard X-Mailer: Apple Mail (2.1874) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Mirage on Xen/ARM status X-BeenThere: mirageos-devel@lists.xenproject.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 Jun 2014, at 11:26, Thomas Leonard wrote: >>> >>> dns: fails to build >>> Error: No implementations provided for the following modules: >>> Lwt_unix referenced from >>> /root/.opam/4.01.0/lib/dns/lwt-core.cmxa(Dns_resolver) >> >> This look the euphemistic "architecture independent issue". Need to see how Unix snuck into the ocaml-dns core and add a test for that. Could you create an issue on ocaml-dns for this? > > https://github.com/mirage/ocaml-dns/issues/13 > > Looks like it's just some test code that needs it anyway ("resolving > recoil.org"). If I remove that bit, it answers DNS queries > successfully. This actually had an unrelated bug that broke it on Xen. During a refactoring, the memory allocation in Dns.Buf.t reverted to using Bigarray.create, which does not allocate page-aligned buffers. This then causes the Netfront driver on Xen to send garbage, since it can only zero-copy whole pages. I fixed it to use Io-page instead in https://github.com/mirage/ocaml-dns/pull/14 I'll release that as ocaml-dns-0.9.0 tomorrow, and update mirage-skeleton with the tweak to lift out the timer logic into the client call. -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 Jun 17 09:14:16 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 17 Jun 2014 09:14: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 1WwpT1-0002mC-Ef; Tue, 17 Jun 2014 09:14:11 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WwbCS-0003Pp-4k for mirageos-devel@lists.xenproject.org; Mon, 16 Jun 2014 18:00:08 +0000 Received: from [85.158.137.68:10933] by server-7.bemta-3.messagelabs.com id 6F/70-04151-7A03F935; Mon, 16 Jun 2014 18:00:07 +0000 X-Env-Sender: sconway@linuxfoundation.org X-Msg-Ref: server-3.tower-31.messagelabs.com!1402941605!10451959!1 X-Originating-IP: [209.85.212.179] 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.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8278 invoked from network); 16 Jun 2014 18:00:05 -0000 Received: from mail-wi0-f179.google.com (HELO mail-wi0-f179.google.com) (209.85.212.179) by server-3.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 16 Jun 2014 18:00:05 -0000 Received: by mail-wi0-f179.google.com with SMTP id cc10so4522075wib.0 for ; Mon, 16 Jun 2014 11:00:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=iQIlstPV3P32z/8HkbdSZTk0KF15m+RCkKLeRfRXdq8=; b=V6fmJXyTetV/uFUqyB3cETOD39dwoKDak9hQ2Echm7PdrZILvjAbpWeNVyIJ51ZW1y jSh9RT6RRVylpPBWbZ/uTndmbGGKKHy60ADPBnLYjvWN+4T7jWGafhbbF+6L7xHc/QbF 8LVWZd5LBDDadwgBK9d/t03ZsQIkgehTUNrG4= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=iQIlstPV3P32z/8HkbdSZTk0KF15m+RCkKLeRfRXdq8=; b=kyF4jYU7ZPLnZb5CSqgAGoZMlHpbz4G02eHMZqUHpRe142qoon9cwNLA16vCwoSDRV w2b+xuuSckqfyZ9SR9zi6LGsjkZTLgkh7aJpPnob8RdVbPuPv6/ckXTnWO3CzusiIhu6 qkoNMothET5O0h8kjDrAlWm8w7aFcnWdQ/GzOleii0kKQRMCPV3hujSpfqUK90LGEwyP s1OHR7LQiAjwlKwO+f67YxGZZDRF91lfYFJEJtNh5MDGxcsyLgWKG+wHNRJ3+igNu66p qGWU7l9B2P/V89+ezP+BRswR/ww6RiHy0qhm7cIGUAYPUjHfsuFq9bZvJGstaH+SoHlB q27g== X-Gm-Message-State: ALoCoQnNeUitpS9ZjI4QOLMb/VAPJUv42YgQ33hS35M7af3xqam4c/skRczsS0XYX6rNDnShqlMf MIME-Version: 1.0 X-Received: by 10.194.186.178 with SMTP id fl18mr6454580wjc.83.1402941604440; Mon, 16 Jun 2014 11:00:04 -0700 (PDT) Received: by 10.194.198.231 with HTTP; Mon, 16 Jun 2014 11:00:04 -0700 (PDT) In-Reply-To: <539AD1E9.7070606@xen.org> References: <53987F9F.6010907@xen.org> <7CC65A9C-45F9-4E6C-A6D3-FD83A6C472C7@recoil.org> <539AD1E9.7070606@xen.org> Date: Mon, 16 Jun 2014 14:00:04 -0400 Message-ID: From: Sarah Conway To: Lars Kurth , Jennifer Cloer X-Mailman-Approved-At: Tue, 17 Jun 2014 09:14:10 +0000 Cc: "mirageos-devel@lists.xenproject.org" , Anil Madhavapeddy Subject: Re: [MirageOS-devel] Mirage OS 2.0 (or next) for OSCON? X-BeenThere: mirageos-devel@lists.xenproject.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="===============3254794774386256726==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============3254794774386256726== Content-Type: multipart/alternative; boundary=047d7bb04dd2f960d704fbf7cb69 --047d7bb04dd2f960d704fbf7cb69 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi Lars and Anil, To get things started, below are some questions that will help surface more information for a news release. I believe a phone call to discuss these makes the most sense. Should we/do we need to include anyone else (ie. lead for Xen/ARM port?)? Please provide technical explanation of new features. Why do these new features matter? Who benefits from these updates? Are any of these first, best, only features that are unique to Mirage? - the Xen/ARM port (lead: Thomas Leonard) - Irmin storage integration (lead: Thomas Gazagnaire, Xenstore lead: Dave Scott) - Name resolver for distributed computation (lead: Anil Madhavapeddy) With the 2.0 release, how does Mirage stack up against other Cloud OSes? In this blog, http://www.linux.com/news/enterprise/cloud-computing/751156-are-cloud-opera= ting-systems-the-next-big-thing- Xen wrote that a big challenge for Cloud Operating Systems is the fact that today most cloud providers do not provide support for very small, high density VM deployments. Two things need to happen to resolve this. Hypervisors need to be able to run thousands of VMs on large hosts: this is something which is being addressed for Xen by increasing the numbers of Virtual Machines that can be run on hosts (see David Vrabel=E2=80=99s talk = on Unlimited Event Channels). Cloud billing resolution would also need to adapt to allow charging for much smaller Virtual Machines that run for very short times (less RAM, less disk space, VM lifespan measured in seconds rather than hours). What progress has been made on this front? Anything noteworthy to add about the interns working on Mirage this summer? Is anyone using or prototyping any new mobile or cloud applications yet with Mirage? Any examples of Mirage supporting the kinds of network application loads that run on cloud infrastructure? Is Mirage OS still considered a Xen =E2=80=9Dincubated project=E2=80=9D or = has it graduated with this new release? Anything noteworthy to mention about new/different/number of contributors, pace of community development, etc.? What's next for Mirage, goals, etc.? Thanks, On Fri, Jun 13, 2014 at 6:26 AM, Lars Kurth wrote: > > Anil, > in that case I will pull Sarah in. And we need to get going: OSCON is only a few weeks away > OSCON is a great opportunity for a release as there will be press. Who do we need to pull in for putting PR together > Are there any significant new contributors that came to the project? > Are there any Portland local contributors (some of the Galois folks spring to mind) > Etc > Regards > Lars > > On 11/06/2014 17:26, Anil Madhavapeddy wrote: >> >> On 11 Jun 2014, at 17:11, Lars Kurth wrote: >> >>> Hi all, >>> I saw that Anil submitted a Mirage OS 2.0 talk for the Developer Summit. I was wondering what the plans for the next release were. If it is around Dev Summit time, you should probably start coordinating with me and Sarah >> >> We were just chatting about this yesterday in the call! http://openmirage.org/wiki/weekly-2014-06-10 >> >> The emerging plan for the OSCON Mirage 2.0 release is to have three key features: >> >> - the Xen/ARM port (lead: Thomas Leonard) >> - Irmin storage integration (lead: Thomas Gazagnaire, Xenstore lead: Dave Scott) >> - Name resolver for distributed computation (lead: Anil Madhavapeddy) >> >> All of these look in reasonable shape to get released by mid-July, although the release announcement could probably use a week or two to let the features sit in-tree before we tell everyone about it. >> >> Anyone have anything else on the stack? There are minor things such as 'add s-expression tracing' that can be done on an ongoing basis. >> >> cheers, >> Anil > > -- Sarah Conway PR Manager The Linux Foundation sconway@linuxfoundation.org (978) 578-5300 Cell Skype: sarah.k.conway --047d7bb04dd2f960d704fbf7cb69 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi Lars and Anil,

To get things started, below are = some questions that will help surface more information for a news release. = I believe a phone call to discuss these makes the most sense. Should we/do = we need to include anyone else (ie. lead for Xen/ARM port?)?

Please provide technical explanation of new features. Why do these new = features matter? Who benefits from these updates? Are any of these first, b= est, only features that are unique to Mirage?

- the Xen/ARM port (le= ad: Thomas Leonard)
- Irmin storage integration (lead: Thomas Gazagnaire, Xenstore lead: Dave S= cott)
- Name resolver for distributed computation (lead: Anil Madhavaped= dy)

With the 2.0 release, how does Mirage stack up against other Clo= ud OSes?

In this blog, http://www.l= inux.com/news/enterprise/cloud-computing/751156-are-cloud-operating-systems= -the-next-big-thing- Xen wrote that a big challenge for Cloud Operating= Systems is the fact that today most cloud providers do not provide support= for very small, high density VM deployments. Two things need to happen to = resolve this. Hypervisors need to be able to run thousands of VMs on large = hosts: this is something which is being addressed for Xen by increasing the= numbers of Virtual Machines that can be run on hosts (see David Vrabel=E2= =80=99s talk on Unlimited Event Channels). Cloud billing resolution would a= lso need to adapt to allow charging for much smaller Virtual Machines that = run for very short times (less RAM, less disk space, VM lifespan measured i= n seconds rather than hours). What progress has been made on this front?
Anything noteworthy to add about the interns working on Mirage this sum= mer?

Is anyone using or prototyping any new mobile or cloud applicat= ions yet with Mirage? Any examples of Mirage supporting the kinds of networ= k application loads that run on cloud infrastructure?

Is Mirage OS still considered a Xen =E2=80=9Dincubated project=E2=80=9D= or has it graduated with this new release? Anything noteworthy to mention = about new/different/number of contributors, pace of community development, = etc.?

What's next for Mirage, goals, etc.?=C2=A0

Thanks,


On Fri, Jun 13, 2014 at 6:26 AM, Lars Kurth <lars.kurth@xen.org> wrote:
>
> = Anil,
> in that case I will pull Sarah in. And we need to get going: OSCON is = only a few weeks away
> OSCON is a great opportunity for a release as= there will be press. Who do we need to pull in for putting PR together
> Are there any significant new contributors that came to the project?> Are there any Portland local contributors =C2=A0(some of the Galois = folks spring to mind)
> Etc
> Regards
> Lars
>
&= gt; On 11/06/2014 17:26, Anil Madhavapeddy wrote:
>>
>> On 11 Jun 2014, at 17:11, Lars Kurth <lars.kurth@xen.org> wrote:
>>
&= gt;>> Hi all,
>>> I saw that Anil submitted a Mirage OS 2= .0 talk for the Developer Summit. I was wondering what the plans for the ne= xt release were. If it is around Dev Summit time, you should probably start= coordinating with me and Sarah
>>
>> We were just chatting about this yesterday in the call= ! http://openmirag= e.org/wiki/weekly-2014-06-10
>>
>> The emerging plan = for the OSCON Mirage 2.0 release is to have three key features:
>>
>> - the Xen/ARM port (lead: Thomas Leonard)
>> = - Irmin storage integration (lead: Thomas Gazagnaire, Xenstore lead: Dave S= cott)
>> - Name resolver for distributed computation (lead: Anil M= adhavapeddy)
>>
>> All of these look in reasonable shape to get released = by mid-July, although the release announcement could probably use a week or= two to let the features sit in-tree before we tell everyone about it.
>>
>> Anyone have anything else on the stack? There are mino= r things such as 'add s-expression tracing' that can be done on an = ongoing basis.
>>
>> cheers,
>> Anil
>
>



--
Sarah Conway
PR Manager
The Linux Foundatio= n
sconway@linuxfoundation= .org
(978) 578-5300 =C2=A0Cell
Skype: =C2=A0sarah.k.conway
<= /div> --047d7bb04dd2f960d704fbf7cb69-- --===============3254794774386256726== 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 --===============3254794774386256726==-- From mirageos-devel-bounces@lists.xenproject.org Tue Jun 17 09:14:16 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 17 Jun 2014 09:14: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 1WwpT1-0002mC-Ef; Tue, 17 Jun 2014 09:14:11 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WwbCS-0003Pp-4k for mirageos-devel@lists.xenproject.org; Mon, 16 Jun 2014 18:00:08 +0000 Received: from [85.158.137.68:10933] by server-7.bemta-3.messagelabs.com id 6F/70-04151-7A03F935; Mon, 16 Jun 2014 18:00:07 +0000 X-Env-Sender: sconway@linuxfoundation.org X-Msg-Ref: server-3.tower-31.messagelabs.com!1402941605!10451959!1 X-Originating-IP: [209.85.212.179] 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.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8278 invoked from network); 16 Jun 2014 18:00:05 -0000 Received: from mail-wi0-f179.google.com (HELO mail-wi0-f179.google.com) (209.85.212.179) by server-3.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 16 Jun 2014 18:00:05 -0000 Received: by mail-wi0-f179.google.com with SMTP id cc10so4522075wib.0 for ; Mon, 16 Jun 2014 11:00:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=iQIlstPV3P32z/8HkbdSZTk0KF15m+RCkKLeRfRXdq8=; b=V6fmJXyTetV/uFUqyB3cETOD39dwoKDak9hQ2Echm7PdrZILvjAbpWeNVyIJ51ZW1y jSh9RT6RRVylpPBWbZ/uTndmbGGKKHy60ADPBnLYjvWN+4T7jWGafhbbF+6L7xHc/QbF 8LVWZd5LBDDadwgBK9d/t03ZsQIkgehTUNrG4= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=iQIlstPV3P32z/8HkbdSZTk0KF15m+RCkKLeRfRXdq8=; b=kyF4jYU7ZPLnZb5CSqgAGoZMlHpbz4G02eHMZqUHpRe142qoon9cwNLA16vCwoSDRV w2b+xuuSckqfyZ9SR9zi6LGsjkZTLgkh7aJpPnob8RdVbPuPv6/ckXTnWO3CzusiIhu6 qkoNMothET5O0h8kjDrAlWm8w7aFcnWdQ/GzOleii0kKQRMCPV3hujSpfqUK90LGEwyP s1OHR7LQiAjwlKwO+f67YxGZZDRF91lfYFJEJtNh5MDGxcsyLgWKG+wHNRJ3+igNu66p qGWU7l9B2P/V89+ezP+BRswR/ww6RiHy0qhm7cIGUAYPUjHfsuFq9bZvJGstaH+SoHlB q27g== X-Gm-Message-State: ALoCoQnNeUitpS9ZjI4QOLMb/VAPJUv42YgQ33hS35M7af3xqam4c/skRczsS0XYX6rNDnShqlMf MIME-Version: 1.0 X-Received: by 10.194.186.178 with SMTP id fl18mr6454580wjc.83.1402941604440; Mon, 16 Jun 2014 11:00:04 -0700 (PDT) Received: by 10.194.198.231 with HTTP; Mon, 16 Jun 2014 11:00:04 -0700 (PDT) In-Reply-To: <539AD1E9.7070606@xen.org> References: <53987F9F.6010907@xen.org> <7CC65A9C-45F9-4E6C-A6D3-FD83A6C472C7@recoil.org> <539AD1E9.7070606@xen.org> Date: Mon, 16 Jun 2014 14:00:04 -0400 Message-ID: From: Sarah Conway To: Lars Kurth , Jennifer Cloer X-Mailman-Approved-At: Tue, 17 Jun 2014 09:14:10 +0000 Cc: "mirageos-devel@lists.xenproject.org" , Anil Madhavapeddy Subject: Re: [MirageOS-devel] Mirage OS 2.0 (or next) for OSCON? X-BeenThere: mirageos-devel@lists.xenproject.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="===============3254794774386256726==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============3254794774386256726== Content-Type: multipart/alternative; boundary=047d7bb04dd2f960d704fbf7cb69 --047d7bb04dd2f960d704fbf7cb69 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi Lars and Anil, To get things started, below are some questions that will help surface more information for a news release. I believe a phone call to discuss these makes the most sense. Should we/do we need to include anyone else (ie. lead for Xen/ARM port?)? Please provide technical explanation of new features. Why do these new features matter? Who benefits from these updates? Are any of these first, best, only features that are unique to Mirage? - the Xen/ARM port (lead: Thomas Leonard) - Irmin storage integration (lead: Thomas Gazagnaire, Xenstore lead: Dave Scott) - Name resolver for distributed computation (lead: Anil Madhavapeddy) With the 2.0 release, how does Mirage stack up against other Cloud OSes? In this blog, http://www.linux.com/news/enterprise/cloud-computing/751156-are-cloud-opera= ting-systems-the-next-big-thing- Xen wrote that a big challenge for Cloud Operating Systems is the fact that today most cloud providers do not provide support for very small, high density VM deployments. Two things need to happen to resolve this. Hypervisors need to be able to run thousands of VMs on large hosts: this is something which is being addressed for Xen by increasing the numbers of Virtual Machines that can be run on hosts (see David Vrabel=E2=80=99s talk = on Unlimited Event Channels). Cloud billing resolution would also need to adapt to allow charging for much smaller Virtual Machines that run for very short times (less RAM, less disk space, VM lifespan measured in seconds rather than hours). What progress has been made on this front? Anything noteworthy to add about the interns working on Mirage this summer? Is anyone using or prototyping any new mobile or cloud applications yet with Mirage? Any examples of Mirage supporting the kinds of network application loads that run on cloud infrastructure? Is Mirage OS still considered a Xen =E2=80=9Dincubated project=E2=80=9D or = has it graduated with this new release? Anything noteworthy to mention about new/different/number of contributors, pace of community development, etc.? What's next for Mirage, goals, etc.? Thanks, On Fri, Jun 13, 2014 at 6:26 AM, Lars Kurth wrote: > > Anil, > in that case I will pull Sarah in. And we need to get going: OSCON is only a few weeks away > OSCON is a great opportunity for a release as there will be press. Who do we need to pull in for putting PR together > Are there any significant new contributors that came to the project? > Are there any Portland local contributors (some of the Galois folks spring to mind) > Etc > Regards > Lars > > On 11/06/2014 17:26, Anil Madhavapeddy wrote: >> >> On 11 Jun 2014, at 17:11, Lars Kurth wrote: >> >>> Hi all, >>> I saw that Anil submitted a Mirage OS 2.0 talk for the Developer Summit. I was wondering what the plans for the next release were. If it is around Dev Summit time, you should probably start coordinating with me and Sarah >> >> We were just chatting about this yesterday in the call! http://openmirage.org/wiki/weekly-2014-06-10 >> >> The emerging plan for the OSCON Mirage 2.0 release is to have three key features: >> >> - the Xen/ARM port (lead: Thomas Leonard) >> - Irmin storage integration (lead: Thomas Gazagnaire, Xenstore lead: Dave Scott) >> - Name resolver for distributed computation (lead: Anil Madhavapeddy) >> >> All of these look in reasonable shape to get released by mid-July, although the release announcement could probably use a week or two to let the features sit in-tree before we tell everyone about it. >> >> Anyone have anything else on the stack? There are minor things such as 'add s-expression tracing' that can be done on an ongoing basis. >> >> cheers, >> Anil > > -- Sarah Conway PR Manager The Linux Foundation sconway@linuxfoundation.org (978) 578-5300 Cell Skype: sarah.k.conway --047d7bb04dd2f960d704fbf7cb69 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi Lars and Anil,

To get things started, below are = some questions that will help surface more information for a news release. = I believe a phone call to discuss these makes the most sense. Should we/do = we need to include anyone else (ie. lead for Xen/ARM port?)?

Please provide technical explanation of new features. Why do these new = features matter? Who benefits from these updates? Are any of these first, b= est, only features that are unique to Mirage?

- the Xen/ARM port (le= ad: Thomas Leonard)
- Irmin storage integration (lead: Thomas Gazagnaire, Xenstore lead: Dave S= cott)
- Name resolver for distributed computation (lead: Anil Madhavaped= dy)

With the 2.0 release, how does Mirage stack up against other Clo= ud OSes?

In this blog, http://www.l= inux.com/news/enterprise/cloud-computing/751156-are-cloud-operating-systems= -the-next-big-thing- Xen wrote that a big challenge for Cloud Operating= Systems is the fact that today most cloud providers do not provide support= for very small, high density VM deployments. Two things need to happen to = resolve this. Hypervisors need to be able to run thousands of VMs on large = hosts: this is something which is being addressed for Xen by increasing the= numbers of Virtual Machines that can be run on hosts (see David Vrabel=E2= =80=99s talk on Unlimited Event Channels). Cloud billing resolution would a= lso need to adapt to allow charging for much smaller Virtual Machines that = run for very short times (less RAM, less disk space, VM lifespan measured i= n seconds rather than hours). What progress has been made on this front?
Anything noteworthy to add about the interns working on Mirage this sum= mer?

Is anyone using or prototyping any new mobile or cloud applicat= ions yet with Mirage? Any examples of Mirage supporting the kinds of networ= k application loads that run on cloud infrastructure?

Is Mirage OS still considered a Xen =E2=80=9Dincubated project=E2=80=9D= or has it graduated with this new release? Anything noteworthy to mention = about new/different/number of contributors, pace of community development, = etc.?

What's next for Mirage, goals, etc.?=C2=A0

Thanks,


On Fri, Jun 13, 2014 at 6:26 AM, Lars Kurth <lars.kurth@xen.org> wrote:
>
> = Anil,
> in that case I will pull Sarah in. And we need to get going: OSCON is = only a few weeks away
> OSCON is a great opportunity for a release as= there will be press. Who do we need to pull in for putting PR together
> Are there any significant new contributors that came to the project?> Are there any Portland local contributors =C2=A0(some of the Galois = folks spring to mind)
> Etc
> Regards
> Lars
>
&= gt; On 11/06/2014 17:26, Anil Madhavapeddy wrote:
>>
>> On 11 Jun 2014, at 17:11, Lars Kurth <lars.kurth@xen.org> wrote:
>>
&= gt;>> Hi all,
>>> I saw that Anil submitted a Mirage OS 2= .0 talk for the Developer Summit. I was wondering what the plans for the ne= xt release were. If it is around Dev Summit time, you should probably start= coordinating with me and Sarah
>>
>> We were just chatting about this yesterday in the call= ! http://openmirag= e.org/wiki/weekly-2014-06-10
>>
>> The emerging plan = for the OSCON Mirage 2.0 release is to have three key features:
>>
>> - the Xen/ARM port (lead: Thomas Leonard)
>> = - Irmin storage integration (lead: Thomas Gazagnaire, Xenstore lead: Dave S= cott)
>> - Name resolver for distributed computation (lead: Anil M= adhavapeddy)
>>
>> All of these look in reasonable shape to get released = by mid-July, although the release announcement could probably use a week or= two to let the features sit in-tree before we tell everyone about it.
>>
>> Anyone have anything else on the stack? There are mino= r things such as 'add s-expression tracing' that can be done on an = ongoing basis.
>>
>> cheers,
>> Anil
>
>



--
Sarah Conway
PR Manager
The Linux Foundatio= n
sconway@linuxfoundation= .org
(978) 578-5300 =C2=A0Cell
Skype: =C2=A0sarah.k.conway
<= /div> --047d7bb04dd2f960d704fbf7cb69-- --===============3254794774386256726== 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 --===============3254794774386256726==-- From mirageos-devel-bounces@lists.xenproject.org Tue Jun 17 16:23:31 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 17 Jun 2014 16:23: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 1WwwAQ-00042F-Km; Tue, 17 Jun 2014 16:23:26 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WwwAP-00041r-5C for mirageos-devel@lists.xenproject.org; Tue, 17 Jun 2014 16:23:25 +0000 Received: from [193.109.254.147:36119] by server-7.bemta-14.messagelabs.com id EE/5B-17726-C7B60A35; Tue, 17 Jun 2014 16:23:24 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-4.tower-27.messagelabs.com!1403022203!11907596!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10971 invoked from network); 17 Jun 2014 16:23:23 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-4.tower-27.messagelabs.com with SMTP; 17 Jun 2014 16:23:23 -0000 Received: (qmail 1990 invoked by uid 634); 17 Jun 2014 16:23:22 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from cpc11-belf9-2-0-cust355.2-1.cable.virginm.net (HELO [10.0.1.15]) (86.24.61.100) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Tue, 17 Jun 2014 17:23:22 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\)) From: Anil Madhavapeddy In-Reply-To: Date: Tue, 17 Jun 2014 17:23:20 +0100 Message-Id: <2E5AF614-DF84-4DBC-9EEC-C23BD7EF2144@recoil.org> References: <297FC9DB-3A4E-41A5-B00E-9DEF62C625E6@recoil.org> <12D67D67-3DAB-4033-BFC5-C7DBCBA64F34@recoil.org> To: Thomas Leonard X-Mailer: Apple Mail (2.1874) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Mirage on Xen/ARM status X-BeenThere: mirageos-devel@lists.xenproject.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 Jun 2014, at 11:26, Thomas Leonard wrote: >> >>> A few random notes: >>> >>> - Lack of progress reports from mirage is a problem on x86, but it's >>> worse on ARM because it's so much slower. >> >> Yes, this one has a bug open on mirage/mirage. We need to tee the output from the tool really. > > [ https://github.com/mirage/mirage/issues/205 ] This is addressed in the forthcoming Mirage 1.2.0 tool, with the pull req being tested in: https://github.com/mirage/mirage/pull/252 The main difference is that `mirage` no longer calls OPAM directly. It just generates a Makefile with a `make depend` target that does the honours, so it can be called explicitly. It also exports OPAMVERBOSE and OPAMYES from the Makefile, so it's easier to override it if quiet output is needed instead. I'll probably release Mirage 1.2.0 tomorrow with this change unless anyone finds an issue. I anticipate that the only fallout will be Travis scripts that need to have a "make depend" inserted 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 Jun 17 16:23:31 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 17 Jun 2014 16:23: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 1WwwAQ-00042F-Km; Tue, 17 Jun 2014 16:23:26 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WwwAP-00041r-5C for mirageos-devel@lists.xenproject.org; Tue, 17 Jun 2014 16:23:25 +0000 Received: from [193.109.254.147:36119] by server-7.bemta-14.messagelabs.com id EE/5B-17726-C7B60A35; Tue, 17 Jun 2014 16:23:24 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-4.tower-27.messagelabs.com!1403022203!11907596!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10971 invoked from network); 17 Jun 2014 16:23:23 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-4.tower-27.messagelabs.com with SMTP; 17 Jun 2014 16:23:23 -0000 Received: (qmail 1990 invoked by uid 634); 17 Jun 2014 16:23:22 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from cpc11-belf9-2-0-cust355.2-1.cable.virginm.net (HELO [10.0.1.15]) (86.24.61.100) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Tue, 17 Jun 2014 17:23:22 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\)) From: Anil Madhavapeddy In-Reply-To: Date: Tue, 17 Jun 2014 17:23:20 +0100 Message-Id: <2E5AF614-DF84-4DBC-9EEC-C23BD7EF2144@recoil.org> References: <297FC9DB-3A4E-41A5-B00E-9DEF62C625E6@recoil.org> <12D67D67-3DAB-4033-BFC5-C7DBCBA64F34@recoil.org> To: Thomas Leonard X-Mailer: Apple Mail (2.1874) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Mirage on Xen/ARM status X-BeenThere: mirageos-devel@lists.xenproject.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 Jun 2014, at 11:26, Thomas Leonard wrote: >> >>> A few random notes: >>> >>> - Lack of progress reports from mirage is a problem on x86, but it's >>> worse on ARM because it's so much slower. >> >> Yes, this one has a bug open on mirage/mirage. We need to tee the output from the tool really. > > [ https://github.com/mirage/mirage/issues/205 ] This is addressed in the forthcoming Mirage 1.2.0 tool, with the pull req being tested in: https://github.com/mirage/mirage/pull/252 The main difference is that `mirage` no longer calls OPAM directly. It just generates a Makefile with a `make depend` target that does the honours, so it can be called explicitly. It also exports OPAMVERBOSE and OPAMYES from the Makefile, so it's easier to override it if quiet output is needed instead. I'll probably release Mirage 1.2.0 tomorrow with this change unless anyone finds an issue. I anticipate that the only fallout will be Travis scripts that need to have a "make depend" inserted 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 Wed Jun 18 02:40:32 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 18 Jun 2014 02:40: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 1Wx5nX-00047H-4F; Wed, 18 Jun 2014 02:40:27 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Wx5nW-000472-2o for mirageos-devel@lists.xenproject.org; Wed, 18 Jun 2014 02:40:26 +0000 Received: from [193.109.254.147:55794] by server-10.bemta-14.messagelabs.com id 8C/87-04546-91CF0A35; Wed, 18 Jun 2014 02:40:25 +0000 X-Env-Sender: russell.pavlicek.xen@gmail.com X-Msg-Ref: server-6.tower-27.messagelabs.com!1403059224!11942823!1 X-Originating-IP: [209.85.217.171] X-SpamReason: No, hits=2.5 required=7.0 tests=RCVD_BY_IP, SUSPICIOUS_RECIPS X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5002 invoked from network); 18 Jun 2014 02:40:24 -0000 Received: from mail-lb0-f171.google.com (HELO mail-lb0-f171.google.com) (209.85.217.171) by server-6.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 18 Jun 2014 02:40:24 -0000 Received: by mail-lb0-f171.google.com with SMTP id s7so112869lbd.16 for ; Tue, 17 Jun 2014 19:40:23 -0700 (PDT) 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=g+mn+kIi5oy2PZLRqfM4u0IZNG6weruZRhqF0lIuB7I=; b=T+u+wb+dr6UaVxbnArBwvZVzcYUonW95/UbEXQPVj/PJr/FZ3xxPdOqb9S3u2P/d/R yUEWcqymDwDltoE/gyYHepLBE1U+PTDiTciPoqlObITsUNjpq+aSrSUt2gj6e44aLZLl l9TOTCCdIMzJEu7YCDpltJYy6tBU3GdjJ3H986XKkgErqavfsD9djqbWTBNm8j5DRDwo tbE8h9HQ+cDl/kHxnhfhXD5tBv35BNYrRGq5m54fJ8Gt4Mf9LrMNKa/4gJxk3nKFy8c+ Km+e87BHgjoI5U6ecsdpYQDJcK5RruRh6klVCiz2M6+6lkt9scmf/EFSf7SPLOPu33yz fPYQ== MIME-Version: 1.0 X-Received: by 10.112.150.65 with SMTP id ug1mr8619706lbb.46.1403059223649; Tue, 17 Jun 2014 19:40:23 -0700 (PDT) Received: by 10.112.29.39 with HTTP; Tue, 17 Jun 2014 19:40:23 -0700 (PDT) Date: Tue, 17 Jun 2014 22:40:23 -0400 X-Google-Sender-Auth: 5-llPh8vqpDTT14q_G4MJEy1xX8 Message-ID: From: Russ Pavlicek To: xen-devel@lists.xen.org, "xen-users@lists.xen.org" , mirageos-devel@lists.xenproject.org, xs-devel@lists.xenserver.org, xen-api@lists.xen.org Subject: [MirageOS-devel] Next Wednesday, June 25, is Xen Project Document Day X-BeenThere: mirageos-devel@lists.xenproject.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 a reminder that next Wednesday, June 25, is Xen Project Document Day. Xen Project Document Day is a day to help improve overall Xen Project documentation, particularly that of the Wiki. All the information you need to participate in Document Day is here: http://wiki.xenproject.org/wiki/Xen_Document_Days If you get a few moments in the next week, please take a look at the current TODO list to see other items which need attention: http://wiki.xenproject.org/wiki/Xen_Document_Days/TODO So 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 next 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 Wed Jun 18 02:40:32 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 18 Jun 2014 02:40: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 1Wx5nX-00047H-4F; Wed, 18 Jun 2014 02:40:27 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Wx5nW-000472-2o for mirageos-devel@lists.xenproject.org; Wed, 18 Jun 2014 02:40:26 +0000 Received: from [193.109.254.147:55794] by server-10.bemta-14.messagelabs.com id 8C/87-04546-91CF0A35; Wed, 18 Jun 2014 02:40:25 +0000 X-Env-Sender: russell.pavlicek.xen@gmail.com X-Msg-Ref: server-6.tower-27.messagelabs.com!1403059224!11942823!1 X-Originating-IP: [209.85.217.171] X-SpamReason: No, hits=2.5 required=7.0 tests=RCVD_BY_IP, SUSPICIOUS_RECIPS X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5002 invoked from network); 18 Jun 2014 02:40:24 -0000 Received: from mail-lb0-f171.google.com (HELO mail-lb0-f171.google.com) (209.85.217.171) by server-6.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 18 Jun 2014 02:40:24 -0000 Received: by mail-lb0-f171.google.com with SMTP id s7so112869lbd.16 for ; Tue, 17 Jun 2014 19:40:23 -0700 (PDT) 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=g+mn+kIi5oy2PZLRqfM4u0IZNG6weruZRhqF0lIuB7I=; b=T+u+wb+dr6UaVxbnArBwvZVzcYUonW95/UbEXQPVj/PJr/FZ3xxPdOqb9S3u2P/d/R yUEWcqymDwDltoE/gyYHepLBE1U+PTDiTciPoqlObITsUNjpq+aSrSUt2gj6e44aLZLl l9TOTCCdIMzJEu7YCDpltJYy6tBU3GdjJ3H986XKkgErqavfsD9djqbWTBNm8j5DRDwo tbE8h9HQ+cDl/kHxnhfhXD5tBv35BNYrRGq5m54fJ8Gt4Mf9LrMNKa/4gJxk3nKFy8c+ Km+e87BHgjoI5U6ecsdpYQDJcK5RruRh6klVCiz2M6+6lkt9scmf/EFSf7SPLOPu33yz fPYQ== MIME-Version: 1.0 X-Received: by 10.112.150.65 with SMTP id ug1mr8619706lbb.46.1403059223649; Tue, 17 Jun 2014 19:40:23 -0700 (PDT) Received: by 10.112.29.39 with HTTP; Tue, 17 Jun 2014 19:40:23 -0700 (PDT) Date: Tue, 17 Jun 2014 22:40:23 -0400 X-Google-Sender-Auth: 5-llPh8vqpDTT14q_G4MJEy1xX8 Message-ID: From: Russ Pavlicek To: xen-devel@lists.xen.org, "xen-users@lists.xen.org" , mirageos-devel@lists.xenproject.org, xs-devel@lists.xenserver.org, xen-api@lists.xen.org Subject: [MirageOS-devel] Next Wednesday, June 25, is Xen Project Document Day X-BeenThere: mirageos-devel@lists.xenproject.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 a reminder that next Wednesday, June 25, is Xen Project Document Day. Xen Project Document Day is a day to help improve overall Xen Project documentation, particularly that of the Wiki. All the information you need to participate in Document Day is here: http://wiki.xenproject.org/wiki/Xen_Document_Days If you get a few moments in the next week, please take a look at the current TODO list to see other items which need attention: http://wiki.xenproject.org/wiki/Xen_Document_Days/TODO So 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 next 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 Wed Jun 18 07:38:42 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 18 Jun 2014 07:38: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 1WxAS4-0007T9-Kn; Wed, 18 Jun 2014 07:38:36 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WxAS2-0007T4-Vi for mirageos-devel@lists.xenproject.org; Wed, 18 Jun 2014 07:38:35 +0000 Received: from [85.158.143.35:50330] by server-2.bemta-4.messagelabs.com id 01/B7-06539-AF141A35; Wed, 18 Jun 2014 07:38:34 +0000 X-Env-Sender: jincm12@163.com X-Msg-Ref: server-7.tower-21.messagelabs.com!1403077111!12124059!1 X-Originating-IP: [220.181.13.139] X-SpamReason: No, hits=0.4 required=7.0 tests=sa_preprocessor: QmFkIElQOiAyMjAuMTgxLjEzLjEzOSA9PiA2MDg1\n,sa_preprocessor: QmFkIElQOiAyMjAuMTgxLjEzLjEzOSA9PiA2MDg1\n,HTML_30_40,HTML_MESSAGE, MIME_BASE64_TEXT X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3353 invoked from network); 18 Jun 2014 07:38:32 -0000 Received: from m13-139.163.com (HELO m13-139.163.com) (220.181.13.139) by server-7.tower-21.messagelabs.com with SMTP; 18 Jun 2014 07:38:32 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=163.com; s=s110527; h=Date:From:Subject:MIME-Version:Message-ID; bh=8oCAE KdgGICy/qnVnkOwqlAJA7TyCfCF1pNlvDdjM7I=; b=eFOsi5btQjBD1xRejuZ3t B4L6gok+P6U3740o5NRHUPH2SDXAwEbqP0yd/5FzxqDiFA4ZDGr9hHkb5d7g0oeP VSkh/egvLpw7e8mTqwuIHvXetZsL0bcnOdWmUV62ao8ImNpmweKX9EmZzkOcH3Zg 7+dArhxlR+Z2fhLOJpYNso= Received: from jincm12$163.com ( [218.25.39.54] ) by ajax-webmail-wmsvr139 (Coremail) ; Wed, 18 Jun 2014 15:38:29 +0800 (CST) X-Originating-IP: [218.25.39.54] Date: Wed, 18 Jun 2014 15:38:29 +0800 (CST) From: jincm To: mirageos-devel@lists.xenproject.org X-Priority: 3 X-Mailer: Coremail Webmail Server Version SP_ntes V3.5 build 20140422(26738.6344) Copyright (c) 2002-2014 www.mailtech.cn 163com X-CM-CTRLDATA: ow9ZoGZvb3Rlcl9odG09ODc3Ojgx MIME-Version: 1.0 Message-ID: <1e0f9055.205e3.146ade9a86b.Coremail.jincm12@163.com> X-CM-TRANSID: i8GowECpWkD2QaFTnMwwAA--.8913W X-CM-SenderInfo: 5mlquzirs6il2tof0z/1tbitA+urFD+SDNwRwAAsb X-Coremail-Antispam: 1U5529EdanIXcx71UUUUU7vcSsGvfC2KfnxnUU== Subject: [MirageOS-devel] xen linux vm can not start X-BeenThere: mirageos-devel@lists.xenproject.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="===============4092109131835285290==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============4092109131835285290== Content-Type: multipart/alternative; boundary="----=_Part_522776_274778250.1403077109866" ------=_Part_522776_274778250.1403077109866 Content-Type: text/plain; charset=GBK Content-Transfer-Encoding: base64 aGVsbG86CiAgICB3aG8gY2FuIGhlbHAgbWU/CiAgICB3aGVuIGkgY29tcGlsZSBsaW51eCBrZXJu ZWwoeDg2ICAyLjYuMzIpIHdpdGggMS5jb25maWcgLGtlcm5lbCBjYW4gc3RhcnQgLGJ1dCB3aGVu IGkgdXNlZCAyLmNvbmZpZyBmb3IgQ09ORklHX1BBR0VfT0ZGU0VUPTB4ODAwMDAwMDAsa2VybmVs IGNhbiBub3Qgc3RhcnQ7CiAgIAoKICAgVGhlcmUgYXJlIGlzc3VlcyBsaWtlIHRoaXMgb24geGVu IDMuKiA0LiogYW5kIHhlbnNlcnZlcjYgLgoKCgogIFtyb290QGxvY2FsaG9zdCBsaW51eC0yLjYu MzIuMTUtcnBzXSMgZGlmZiAxLmNvbmZpZyAyLmNvbmZnCjRjNAo8ICMgVHVlIEp1biAxNyAyMDoz MzozNCAyMDE0Ci0tLQo+ICMgVGh1IE1heSAxNSAxNjoxMDo1OSAyMDE0CjI5OGMyOTgKPCAjIENP TkZJR19WTVNQTElUXzNHIGlzIG5vdCBzZXQKLS0tCj4gQ09ORklHX1ZNU1BMSVRfM0c9eQozMDBj MzAwCjwgQ09ORklHX1ZNU1BMSVRfMkc9eQotLS0KPiAjIENPTkZJR19WTVNQTElUXzJHIGlzIG5v dCBzZXQKMzAzYzMwMwo8IENPTkZJR19QQUdFX09GRlNFVD0weDgwMDAwMDAwCi0tLQo+IENPTkZJ R19QQUdFX09GRlNFVD0weEMwMDAwMDAwCgo= ------=_Part_522776_274778250.1403077109866 Content-Type: text/html; charset=GBK Content-Transfer-Encoding: base64 PGRpdiBzdHlsZT0ibGluZS1oZWlnaHQ6MS43O2NvbG9yOiMwMDAwMDA7Zm9udC1zaXplOjE0cHg7 Zm9udC1mYW1pbHk6QXJpYWwiPjxkaXY+aGVsbG86PGJyPiZuYnNwOyZuYnNwOyZuYnNwOyB3aG8g Y2FuIGhlbHAgbWU/PGJyPiZuYnNwOyZuYnNwOyZuYnNwOyB3aGVuIGkgY29tcGlsZSBsaW51eCBr ZXJuZWwoeDg2Jm5ic3A7IDIuNi4zMikgd2l0aCAxLmNvbmZpZyAsa2VybmVsIGNhbiBzdGFydCAs YnV0IHdoZW4gaSB1c2VkIDIuY29uZmlnIGZvciBDT05GSUdfUEFHRV9PRkZTRVQ9MHg4MDAwMDAw MCxrZXJuZWwgY2FuIG5vdCBzdGFydDs8YnI+Jm5ic3A7Jm5ic3A7Jm5ic3A7IDxicj48ZGl2IGNs YXNzPSJwMS0xMSI+Jm5ic3A7Jm5ic3A7IFRoZXJlIGFyZSBpc3N1ZXMgbGlrZSB0aGlzIG9uIHhl biAzLiogNC4qIGFuZCB4ZW5zZXJ2ZXI2IC48YnI+PC9kaXY+PGJyPjxicj4mbmJzcDsgW3Jvb3RA bG9jYWxob3N0IGxpbnV4LTIuNi4zMi4xNS1ycHNdIyBkaWZmIDEuY29uZmlnIDIuY29uZmc8YnI+ NGM0PGJyPiZsdDsgIyBUdWUgSnVuIDE3IDIwOjMzOjM0IDIwMTQ8YnI+LS0tPGJyPiZndDsgIyBU aHUgTWF5IDE1IDE2OjEwOjU5IDIwMTQ8YnI+Mjk4YzI5ODxicj4mbHQ7ICMgQ09ORklHX1ZNU1BM SVRfM0cgaXMgbm90IHNldDxicj4tLS08YnI+Jmd0OyBDT05GSUdfVk1TUExJVF8zRz15PGJyPjMw MGMzMDA8YnI+Jmx0OyBDT05GSUdfVk1TUExJVF8yRz15PGJyPi0tLTxicj4mZ3Q7ICMgQ09ORklH X1ZNU1BMSVRfMkcgaXMgbm90IHNldDxicj4zMDNjMzAzPGJyPiZsdDsgQ09ORklHX1BBR0VfT0ZG U0VUPTB4ODAwMDAwMDA8YnI+LS0tPGJyPiZndDsgQ09ORklHX1BBR0VfT0ZGU0VUPTB4QzAwMDAw MDA8YnI+PGJyPjwvZGl2PjwvZGl2Pjxicj48YnI+PHNwYW4gdGl0bGU9Im5ldGVhc2Vmb290ZXIi PjxzcGFuIGlkPSJuZXRlYXNlX21haWxfZm9vdGVyIj48L3NwYW4+PC9zcGFuPg== ------=_Part_522776_274778250.1403077109866-- --===============4092109131835285290== 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 --===============4092109131835285290==-- From mirageos-devel-bounces@lists.xenproject.org Wed Jun 18 07:38:42 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 18 Jun 2014 07:38: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 1WxAS4-0007T9-Kn; Wed, 18 Jun 2014 07:38:36 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WxAS2-0007T4-Vi for mirageos-devel@lists.xenproject.org; Wed, 18 Jun 2014 07:38:35 +0000 Received: from [85.158.143.35:50330] by server-2.bemta-4.messagelabs.com id 01/B7-06539-AF141A35; Wed, 18 Jun 2014 07:38:34 +0000 X-Env-Sender: jincm12@163.com X-Msg-Ref: server-7.tower-21.messagelabs.com!1403077111!12124059!1 X-Originating-IP: [220.181.13.139] X-SpamReason: No, hits=0.4 required=7.0 tests=sa_preprocessor: QmFkIElQOiAyMjAuMTgxLjEzLjEzOSA9PiA2MDg1\n,sa_preprocessor: QmFkIElQOiAyMjAuMTgxLjEzLjEzOSA9PiA2MDg1\n,HTML_30_40,HTML_MESSAGE, MIME_BASE64_TEXT X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3353 invoked from network); 18 Jun 2014 07:38:32 -0000 Received: from m13-139.163.com (HELO m13-139.163.com) (220.181.13.139) by server-7.tower-21.messagelabs.com with SMTP; 18 Jun 2014 07:38:32 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=163.com; s=s110527; h=Date:From:Subject:MIME-Version:Message-ID; bh=8oCAE KdgGICy/qnVnkOwqlAJA7TyCfCF1pNlvDdjM7I=; b=eFOsi5btQjBD1xRejuZ3t B4L6gok+P6U3740o5NRHUPH2SDXAwEbqP0yd/5FzxqDiFA4ZDGr9hHkb5d7g0oeP VSkh/egvLpw7e8mTqwuIHvXetZsL0bcnOdWmUV62ao8ImNpmweKX9EmZzkOcH3Zg 7+dArhxlR+Z2fhLOJpYNso= Received: from jincm12$163.com ( [218.25.39.54] ) by ajax-webmail-wmsvr139 (Coremail) ; Wed, 18 Jun 2014 15:38:29 +0800 (CST) X-Originating-IP: [218.25.39.54] Date: Wed, 18 Jun 2014 15:38:29 +0800 (CST) From: jincm To: mirageos-devel@lists.xenproject.org X-Priority: 3 X-Mailer: Coremail Webmail Server Version SP_ntes V3.5 build 20140422(26738.6344) Copyright (c) 2002-2014 www.mailtech.cn 163com X-CM-CTRLDATA: ow9ZoGZvb3Rlcl9odG09ODc3Ojgx MIME-Version: 1.0 Message-ID: <1e0f9055.205e3.146ade9a86b.Coremail.jincm12@163.com> X-CM-TRANSID: i8GowECpWkD2QaFTnMwwAA--.8913W X-CM-SenderInfo: 5mlquzirs6il2tof0z/1tbitA+urFD+SDNwRwAAsb X-Coremail-Antispam: 1U5529EdanIXcx71UUUUU7vcSsGvfC2KfnxnUU== Subject: [MirageOS-devel] xen linux vm can not start X-BeenThere: mirageos-devel@lists.xenproject.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="===============4092109131835285290==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============4092109131835285290== Content-Type: multipart/alternative; boundary="----=_Part_522776_274778250.1403077109866" ------=_Part_522776_274778250.1403077109866 Content-Type: text/plain; charset=GBK Content-Transfer-Encoding: base64 aGVsbG86CiAgICB3aG8gY2FuIGhlbHAgbWU/CiAgICB3aGVuIGkgY29tcGlsZSBsaW51eCBrZXJu ZWwoeDg2ICAyLjYuMzIpIHdpdGggMS5jb25maWcgLGtlcm5lbCBjYW4gc3RhcnQgLGJ1dCB3aGVu IGkgdXNlZCAyLmNvbmZpZyBmb3IgQ09ORklHX1BBR0VfT0ZGU0VUPTB4ODAwMDAwMDAsa2VybmVs IGNhbiBub3Qgc3RhcnQ7CiAgIAoKICAgVGhlcmUgYXJlIGlzc3VlcyBsaWtlIHRoaXMgb24geGVu IDMuKiA0LiogYW5kIHhlbnNlcnZlcjYgLgoKCgogIFtyb290QGxvY2FsaG9zdCBsaW51eC0yLjYu MzIuMTUtcnBzXSMgZGlmZiAxLmNvbmZpZyAyLmNvbmZnCjRjNAo8ICMgVHVlIEp1biAxNyAyMDoz MzozNCAyMDE0Ci0tLQo+ICMgVGh1IE1heSAxNSAxNjoxMDo1OSAyMDE0CjI5OGMyOTgKPCAjIENP TkZJR19WTVNQTElUXzNHIGlzIG5vdCBzZXQKLS0tCj4gQ09ORklHX1ZNU1BMSVRfM0c9eQozMDBj MzAwCjwgQ09ORklHX1ZNU1BMSVRfMkc9eQotLS0KPiAjIENPTkZJR19WTVNQTElUXzJHIGlzIG5v dCBzZXQKMzAzYzMwMwo8IENPTkZJR19QQUdFX09GRlNFVD0weDgwMDAwMDAwCi0tLQo+IENPTkZJ R19QQUdFX09GRlNFVD0weEMwMDAwMDAwCgo= ------=_Part_522776_274778250.1403077109866 Content-Type: text/html; charset=GBK Content-Transfer-Encoding: base64 PGRpdiBzdHlsZT0ibGluZS1oZWlnaHQ6MS43O2NvbG9yOiMwMDAwMDA7Zm9udC1zaXplOjE0cHg7 Zm9udC1mYW1pbHk6QXJpYWwiPjxkaXY+aGVsbG86PGJyPiZuYnNwOyZuYnNwOyZuYnNwOyB3aG8g Y2FuIGhlbHAgbWU/PGJyPiZuYnNwOyZuYnNwOyZuYnNwOyB3aGVuIGkgY29tcGlsZSBsaW51eCBr ZXJuZWwoeDg2Jm5ic3A7IDIuNi4zMikgd2l0aCAxLmNvbmZpZyAsa2VybmVsIGNhbiBzdGFydCAs YnV0IHdoZW4gaSB1c2VkIDIuY29uZmlnIGZvciBDT05GSUdfUEFHRV9PRkZTRVQ9MHg4MDAwMDAw MCxrZXJuZWwgY2FuIG5vdCBzdGFydDs8YnI+Jm5ic3A7Jm5ic3A7Jm5ic3A7IDxicj48ZGl2IGNs YXNzPSJwMS0xMSI+Jm5ic3A7Jm5ic3A7IFRoZXJlIGFyZSBpc3N1ZXMgbGlrZSB0aGlzIG9uIHhl biAzLiogNC4qIGFuZCB4ZW5zZXJ2ZXI2IC48YnI+PC9kaXY+PGJyPjxicj4mbmJzcDsgW3Jvb3RA bG9jYWxob3N0IGxpbnV4LTIuNi4zMi4xNS1ycHNdIyBkaWZmIDEuY29uZmlnIDIuY29uZmc8YnI+ NGM0PGJyPiZsdDsgIyBUdWUgSnVuIDE3IDIwOjMzOjM0IDIwMTQ8YnI+LS0tPGJyPiZndDsgIyBU aHUgTWF5IDE1IDE2OjEwOjU5IDIwMTQ8YnI+Mjk4YzI5ODxicj4mbHQ7ICMgQ09ORklHX1ZNU1BM SVRfM0cgaXMgbm90IHNldDxicj4tLS08YnI+Jmd0OyBDT05GSUdfVk1TUExJVF8zRz15PGJyPjMw MGMzMDA8YnI+Jmx0OyBDT05GSUdfVk1TUExJVF8yRz15PGJyPi0tLTxicj4mZ3Q7ICMgQ09ORklH X1ZNU1BMSVRfMkcgaXMgbm90IHNldDxicj4zMDNjMzAzPGJyPiZsdDsgQ09ORklHX1BBR0VfT0ZG U0VUPTB4ODAwMDAwMDA8YnI+LS0tPGJyPiZndDsgQ09ORklHX1BBR0VfT0ZGU0VUPTB4QzAwMDAw MDA8YnI+PGJyPjwvZGl2PjwvZGl2Pjxicj48YnI+PHNwYW4gdGl0bGU9Im5ldGVhc2Vmb290ZXIi PjxzcGFuIGlkPSJuZXRlYXNlX21haWxfZm9vdGVyIj48L3NwYW4+PC9zcGFuPg== ------=_Part_522776_274778250.1403077109866-- --===============4092109131835285290== 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 --===============4092109131835285290==-- From mirageos-devel-bounces@lists.xenproject.org Wed Jun 18 10:23:37 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 18 Jun 2014 10:23: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 1WxD1h-0006Tr-BB; Wed, 18 Jun 2014 10:23:33 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WxD1g-0006Tm-Pn for mirageos-devel@lists.xenproject.org; Wed, 18 Jun 2014 10:23:32 +0000 Received: from [193.109.254.147:25487] by server-11.bemta-14.messagelabs.com id 15/A1-09902-4A861A35; Wed, 18 Jun 2014 10:23:32 +0000 X-Env-Sender: hannes@mehnert.org X-Msg-Ref: server-11.tower-27.messagelabs.com!1403087011!8728836!1 X-Originating-IP: [213.73.89.200] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_23, UPPERCASE_25_50,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 14097 invoked from network); 18 Jun 2014 10:23:31 -0000 Received: from mail.mehnert.org (HELO mail.mehnert.org) (213.73.89.200) by server-11.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 18 Jun 2014 10:23:31 -0000 Received: from [128.232.110.146] (c146.al.cl.cam.ac.uk [128.232.110.146]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client CN "hannes@mehnert.org", Issuer "mehnert root CA" (verified OK)) by mail.mehnert.org (Postfix) with ESMTPS id 3361F16F7 for ; Wed, 18 Jun 2014 12:23:30 +0200 (CEST) Message-ID: <53A1685E.5010307@mehnert.org> Date: Wed, 18 Jun 2014 11:22:22 +0100 From: Hannes Mehnert User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: "mirageos-devel@lists.xenproject.org" Subject: [MirageOS-devel] mirage.github.io X-BeenThere: mirageos-devel@lists.xenproject.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 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA384 Hey, back in time https://mirage.github.io/ showed the API documentation of various mirage libraries. It seems to be broken these days. any ideas how to fix that? Thanks, Hannes -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (FreeBSD) iQIcBAEBCQAGBQJToWheAAoJELyJZYjffCju0oUP/3XGs88HJ9zuQy7pkrz7/Ooz CFGmJDFLy80nKkNcSzpgMGDAo290o+RmBtHd0/QzWsyl7rGtpPHgUkjVzKcKVh61 ACylSanXHt7IOKPoBCmXeEJC7p2Neefha5+J5yNZqFaV6Y6qWuGOef2EP2FJ/mq+ ei2CjhvYqeuGBq0XhMRrdyfDN/Tx4Ogc4p6ZjJ25WsNNcj+WPXDib4B06bDZWlEN 8BzO/Alb8zJxVwTE9yEry0v+V+CymjGCrZo2gk4S+thebgatjWYvotiC7g9q6xIe tGEqh9hM3grw1y/to6WacNPO7IyY4vb5qhT8Y/zdokAFAI1Py/wE3+eotBPplY61 LF9u3EpByqvcQXUhEM55jWf6q6JRp+oKT/iP8iuGwCLpGsdkCSHF533vu2BvzuQr Hy4B9yVhiLjCWVuxN+bl9IfkkB5fO83tP0vjjeU07pcI6khr/T4Ur7xyVJlpKxqR IcBrXMEUVwnSFXl1CSdtDr1eqPdJRl2MPgL4TPEAcy0kcfrz7AdWYdnsYmNbB6R2 GnHwlP7nTWKONely4R+lgSPofmE2elVU388W+d8dzQkJWx9aGsG/pp/y+BVapZWU AMyKCqlUS2D9vsN1mG76alZZLpSq4BB9J4/krGjVmClgvgLTGgk8hF0GdqiupXk0 yWilY3WU3LBzAneZxUme =CYab -----END PGP SIGNATURE----- _______________________________________________ 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 Jun 18 10:23:37 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 18 Jun 2014 10:23: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 1WxD1h-0006Tr-BB; Wed, 18 Jun 2014 10:23:33 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WxD1g-0006Tm-Pn for mirageos-devel@lists.xenproject.org; Wed, 18 Jun 2014 10:23:32 +0000 Received: from [193.109.254.147:25487] by server-11.bemta-14.messagelabs.com id 15/A1-09902-4A861A35; Wed, 18 Jun 2014 10:23:32 +0000 X-Env-Sender: hannes@mehnert.org X-Msg-Ref: server-11.tower-27.messagelabs.com!1403087011!8728836!1 X-Originating-IP: [213.73.89.200] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_23, UPPERCASE_25_50,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 14097 invoked from network); 18 Jun 2014 10:23:31 -0000 Received: from mail.mehnert.org (HELO mail.mehnert.org) (213.73.89.200) by server-11.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 18 Jun 2014 10:23:31 -0000 Received: from [128.232.110.146] (c146.al.cl.cam.ac.uk [128.232.110.146]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client CN "hannes@mehnert.org", Issuer "mehnert root CA" (verified OK)) by mail.mehnert.org (Postfix) with ESMTPS id 3361F16F7 for ; Wed, 18 Jun 2014 12:23:30 +0200 (CEST) Message-ID: <53A1685E.5010307@mehnert.org> Date: Wed, 18 Jun 2014 11:22:22 +0100 From: Hannes Mehnert User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: "mirageos-devel@lists.xenproject.org" Subject: [MirageOS-devel] mirage.github.io X-BeenThere: mirageos-devel@lists.xenproject.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 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA384 Hey, back in time https://mirage.github.io/ showed the API documentation of various mirage libraries. It seems to be broken these days. any ideas how to fix that? Thanks, Hannes -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (FreeBSD) iQIcBAEBCQAGBQJToWheAAoJELyJZYjffCju0oUP/3XGs88HJ9zuQy7pkrz7/Ooz CFGmJDFLy80nKkNcSzpgMGDAo290o+RmBtHd0/QzWsyl7rGtpPHgUkjVzKcKVh61 ACylSanXHt7IOKPoBCmXeEJC7p2Neefha5+J5yNZqFaV6Y6qWuGOef2EP2FJ/mq+ ei2CjhvYqeuGBq0XhMRrdyfDN/Tx4Ogc4p6ZjJ25WsNNcj+WPXDib4B06bDZWlEN 8BzO/Alb8zJxVwTE9yEry0v+V+CymjGCrZo2gk4S+thebgatjWYvotiC7g9q6xIe tGEqh9hM3grw1y/to6WacNPO7IyY4vb5qhT8Y/zdokAFAI1Py/wE3+eotBPplY61 LF9u3EpByqvcQXUhEM55jWf6q6JRp+oKT/iP8iuGwCLpGsdkCSHF533vu2BvzuQr Hy4B9yVhiLjCWVuxN+bl9IfkkB5fO83tP0vjjeU07pcI6khr/T4Ur7xyVJlpKxqR IcBrXMEUVwnSFXl1CSdtDr1eqPdJRl2MPgL4TPEAcy0kcfrz7AdWYdnsYmNbB6R2 GnHwlP7nTWKONely4R+lgSPofmE2elVU388W+d8dzQkJWx9aGsG/pp/y+BVapZWU AMyKCqlUS2D9vsN1mG76alZZLpSq4BB9J4/krGjVmClgvgLTGgk8hF0GdqiupXk0 yWilY3WU3LBzAneZxUme =CYab -----END PGP SIGNATURE----- _______________________________________________ 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 Jun 18 10:56:19 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 18 Jun 2014 10:56: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 1WxDXO-000881-8r; Wed, 18 Jun 2014 10:56:18 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WxDXN-00087w-7H for mirageos-devel@lists.xenproject.org; Wed, 18 Jun 2014 10:56:17 +0000 Received: from [85.158.137.68:63271] by server-17.bemta-3.messagelabs.com id 1B/57-22741-05071A35; Wed, 18 Jun 2014 10:56:16 +0000 X-Env-Sender: daniel.buenzli@erratique.ch X-Msg-Ref: server-8.tower-31.messagelabs.com!1403088975!10853830!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.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17354 invoked from network); 18 Jun 2014 10:56:15 -0000 Received: from mail6.webfaction.com (HELO smtp.webfaction.com) (74.55.86.74) by server-8.tower-31.messagelabs.com with SMTP; 18 Jun 2014 10:56:15 -0000 Received: from [172.17.154.228] (global-1-26.nat.csx.cam.ac.uk [131.111.184.26]) by smtp.webfaction.com (Postfix) with ESMTP id 1B3E2207CFF9; Wed, 18 Jun 2014 10:56:13 +0000 (UTC) Date: Wed, 18 Jun 2014 11:56:12 +0100 From: =?utf-8?Q?Daniel_B=C3=BCnzli?= To: Hannes Mehnert Message-ID: <7465E293D9EC41FFAAAB23E1334F2D3C@erratique.ch> In-Reply-To: <53A1685E.5010307@mehnert.org> References: <53A1685E.5010307@mehnert.org> 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] mirage.github.io X-BeenThere: mirageos-devel@lists.xenproject.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 CgpMZSBtZXJjcmVkaSwgMTgganVpbiAyMDE0IMOgIDExOjIyLCBIYW5uZXMgTWVobmVydCBhIMOp Y3JpdCA6Cgo+IGJhY2sgaW4gdGltZSBodHRwczovL21pcmFnZS5naXRodWIuaW8vIHNob3dlZCB0 aGUgQVBJIGRvY3VtZW50YXRpb24gb2YKPiB2YXJpb3VzIG1pcmFnZSBsaWJyYXJpZXMuCj4gSXQg c2VlbXMgdG8gYmUgYnJva2VuIHRoZXNlIGRheXMuIGFueSBpZGVhcyBob3cgdG8gZml4IHRoYXQ/ CgpXb3JrcyBoZXJlLCBtYXliZSBpdOKAmXMgdGhlIGphdmFzY3JpcHQgdGFraW5nIHRvbyBsb25n IHRvIGV4ZWN1dGUgPyAgCgpEYW5pZWwKCgoKX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX18KTWlyYWdlT1MtZGV2ZWwgbWFpbGluZyBsaXN0Ck1pcmFnZU9TLWRl dmVsQGxpc3RzLnhlbnByb2plY3Qub3JnCmh0dHA6Ly9saXN0cy54ZW5wcm9qZWN0Lm9yZy9jZ2kt YmluL21haWxtYW4vbGlzdGluZm8vbWlyYWdlb3MtZGV2ZWwK From mirageos-devel-bounces@lists.xenproject.org Wed Jun 18 10:56:19 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 18 Jun 2014 10:56: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 1WxDXO-000881-8r; Wed, 18 Jun 2014 10:56:18 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WxDXN-00087w-7H for mirageos-devel@lists.xenproject.org; Wed, 18 Jun 2014 10:56:17 +0000 Received: from [85.158.137.68:63271] by server-17.bemta-3.messagelabs.com id 1B/57-22741-05071A35; Wed, 18 Jun 2014 10:56:16 +0000 X-Env-Sender: daniel.buenzli@erratique.ch X-Msg-Ref: server-8.tower-31.messagelabs.com!1403088975!10853830!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.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17354 invoked from network); 18 Jun 2014 10:56:15 -0000 Received: from mail6.webfaction.com (HELO smtp.webfaction.com) (74.55.86.74) by server-8.tower-31.messagelabs.com with SMTP; 18 Jun 2014 10:56:15 -0000 Received: from [172.17.154.228] (global-1-26.nat.csx.cam.ac.uk [131.111.184.26]) by smtp.webfaction.com (Postfix) with ESMTP id 1B3E2207CFF9; Wed, 18 Jun 2014 10:56:13 +0000 (UTC) Date: Wed, 18 Jun 2014 11:56:12 +0100 From: =?utf-8?Q?Daniel_B=C3=BCnzli?= To: Hannes Mehnert Message-ID: <7465E293D9EC41FFAAAB23E1334F2D3C@erratique.ch> In-Reply-To: <53A1685E.5010307@mehnert.org> References: <53A1685E.5010307@mehnert.org> 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] mirage.github.io X-BeenThere: mirageos-devel@lists.xenproject.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 CgpMZSBtZXJjcmVkaSwgMTgganVpbiAyMDE0IMOgIDExOjIyLCBIYW5uZXMgTWVobmVydCBhIMOp Y3JpdCA6Cgo+IGJhY2sgaW4gdGltZSBodHRwczovL21pcmFnZS5naXRodWIuaW8vIHNob3dlZCB0 aGUgQVBJIGRvY3VtZW50YXRpb24gb2YKPiB2YXJpb3VzIG1pcmFnZSBsaWJyYXJpZXMuCj4gSXQg c2VlbXMgdG8gYmUgYnJva2VuIHRoZXNlIGRheXMuIGFueSBpZGVhcyBob3cgdG8gZml4IHRoYXQ/ CgpXb3JrcyBoZXJlLCBtYXliZSBpdOKAmXMgdGhlIGphdmFzY3JpcHQgdGFraW5nIHRvbyBsb25n IHRvIGV4ZWN1dGUgPyAgCgpEYW5pZWwKCgoKX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX18KTWlyYWdlT1MtZGV2ZWwgbWFpbGluZyBsaXN0Ck1pcmFnZU9TLWRl dmVsQGxpc3RzLnhlbnByb2plY3Qub3JnCmh0dHA6Ly9saXN0cy54ZW5wcm9qZWN0Lm9yZy9jZ2kt YmluL21haWxtYW4vbGlzdGluZm8vbWlyYWdlb3MtZGV2ZWwK From mirageos-devel-bounces@lists.xenproject.org Wed Jun 18 10:57:59 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 18 Jun 2014 10:57: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 1WxDZ1-00089N-Fl; Wed, 18 Jun 2014 10:57:59 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WxDZ0-00089I-En for mirageos-devel@lists.xenproject.org; Wed, 18 Jun 2014 10:57:58 +0000 Received: from [85.158.137.68:6367] by server-6.bemta-3.messagelabs.com id 99/00-00470-5B071A35; Wed, 18 Jun 2014 10:57:57 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-15.tower-31.messagelabs.com!1403089076!10712626!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_23, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29532 invoked from network); 18 Jun 2014 10:57:56 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-15.tower-31.messagelabs.com with SMTP; 18 Jun 2014 10:57:56 -0000 Received: (qmail 27060 invoked by uid 634); 18 Jun 2014 10:57:56 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from cpc11-belf9-2-0-cust355.2-1.cable.virginm.net (HELO [10.0.1.15]) (86.24.61.100) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Wed, 18 Jun 2014 11:57:56 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\)) From: Anil Madhavapeddy In-Reply-To: <53A1685E.5010307@mehnert.org> Date: Wed, 18 Jun 2014 11:57:54 +0100 Message-Id: <196EEBCD-CBA5-4ED1-A865-23116136AFA3@recoil.org> References: <53A1685E.5010307@mehnert.org> To: Hannes Mehnert X-Mailer: Apple Mail (2.1874) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] mirage.github.io X-BeenThere: mirageos-devel@lists.xenproject.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 18 Jun 2014, at 11:22, Hannes Mehnert wrote: > Hey, > > back in time https://mirage.github.io/ showed the API documentation of > various mirage libraries. > It seems to be broken these days. any ideas how to fix that? Good point -- the cron script was basically this: $ opam install opam-doc $ opam doc `opam search -s mirage` It no longer updates regularly due to the script failing. The breakage was because the "mirage" tag in the OPAM packages hasn't been maintained, and some of the packages aren't coinstallable any more (e.g. vhd-format and xen-api-client seem pinned to older cohttps). I'll fix this by creating a new 'mirage2' tag for the MirageOS 2.0 libraries that only include coinstallable packages. I'm building a snapshot of this manually first to check that it all works. -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 Jun 18 10:57:59 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 18 Jun 2014 10:57: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 1WxDZ1-00089N-Fl; Wed, 18 Jun 2014 10:57:59 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WxDZ0-00089I-En for mirageos-devel@lists.xenproject.org; Wed, 18 Jun 2014 10:57:58 +0000 Received: from [85.158.137.68:6367] by server-6.bemta-3.messagelabs.com id 99/00-00470-5B071A35; Wed, 18 Jun 2014 10:57:57 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-15.tower-31.messagelabs.com!1403089076!10712626!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_23, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29532 invoked from network); 18 Jun 2014 10:57:56 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-15.tower-31.messagelabs.com with SMTP; 18 Jun 2014 10:57:56 -0000 Received: (qmail 27060 invoked by uid 634); 18 Jun 2014 10:57:56 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from cpc11-belf9-2-0-cust355.2-1.cable.virginm.net (HELO [10.0.1.15]) (86.24.61.100) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Wed, 18 Jun 2014 11:57:56 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\)) From: Anil Madhavapeddy In-Reply-To: <53A1685E.5010307@mehnert.org> Date: Wed, 18 Jun 2014 11:57:54 +0100 Message-Id: <196EEBCD-CBA5-4ED1-A865-23116136AFA3@recoil.org> References: <53A1685E.5010307@mehnert.org> To: Hannes Mehnert X-Mailer: Apple Mail (2.1874) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] mirage.github.io X-BeenThere: mirageos-devel@lists.xenproject.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 18 Jun 2014, at 11:22, Hannes Mehnert wrote: > Hey, > > back in time https://mirage.github.io/ showed the API documentation of > various mirage libraries. > It seems to be broken these days. any ideas how to fix that? Good point -- the cron script was basically this: $ opam install opam-doc $ opam doc `opam search -s mirage` It no longer updates regularly due to the script failing. The breakage was because the "mirage" tag in the OPAM packages hasn't been maintained, and some of the packages aren't coinstallable any more (e.g. vhd-format and xen-api-client seem pinned to older cohttps). I'll fix this by creating a new 'mirage2' tag for the MirageOS 2.0 libraries that only include coinstallable packages. I'm building a snapshot of this manually first to check that it all works. -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 Jun 18 11:01:55 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 18 Jun 2014 11:01: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 1WxDcp-0008OI-Di; Wed, 18 Jun 2014 11:01:55 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WxDcp-0008OC-05 for mirageos-devel@lists.xenproject.org; Wed, 18 Jun 2014 11:01:55 +0000 Received: from [85.158.143.35:12177] by server-1.bemta-4.messagelabs.com id 9C/C3-09496-1A171A35; Wed, 18 Jun 2014 11:01:53 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-13.tower-21.messagelabs.com!1403089312!4879574!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30791 invoked from network); 18 Jun 2014 11:01:52 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-13.tower-21.messagelabs.com with SMTP; 18 Jun 2014 11:01:52 -0000 Received: (qmail 3168 invoked by uid 634); 18 Jun 2014 11:01:52 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from cpc11-belf9-2-0-cust355.2-1.cable.virginm.net (HELO [10.0.1.15]) (86.24.61.100) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Wed, 18 Jun 2014 12:01:51 +0100 From: Anil Madhavapeddy Message-Id: <13D72486-0766-49EA-AE2B-ED8ADE5CE3EF@recoil.org> Date: Wed, 18 Jun 2014 12:01:50 +0100 To: mirageos-devel@lists.xenproject.org Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\)) X-Mailer: Apple Mail (2.1874) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Subject: [MirageOS-devel] outgoing tcp connections X-BeenThere: mirageos-devel@lists.xenproject.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 Mindy submitted a fix to the 'DHCP happening too late' bug in the TCP/IP stack, which only affected unikernels that were making outgoing connections rather than listening. The fix is in https://github.com/mirage/mirage-tcpip/pull/55 In particular, it would be good to know if this fixes your TLS client problem Hannes/David, before I merge it... You can test it via this pin: opam pin tcpip git://github.com/avsm/mirage-tcpip#yomimono-dhcp-without-listen 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 Wed Jun 18 11:01:55 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 18 Jun 2014 11:01: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 1WxDcp-0008OI-Di; Wed, 18 Jun 2014 11:01:55 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WxDcp-0008OC-05 for mirageos-devel@lists.xenproject.org; Wed, 18 Jun 2014 11:01:55 +0000 Received: from [85.158.143.35:12177] by server-1.bemta-4.messagelabs.com id 9C/C3-09496-1A171A35; Wed, 18 Jun 2014 11:01:53 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-13.tower-21.messagelabs.com!1403089312!4879574!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30791 invoked from network); 18 Jun 2014 11:01:52 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-13.tower-21.messagelabs.com with SMTP; 18 Jun 2014 11:01:52 -0000 Received: (qmail 3168 invoked by uid 634); 18 Jun 2014 11:01:52 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from cpc11-belf9-2-0-cust355.2-1.cable.virginm.net (HELO [10.0.1.15]) (86.24.61.100) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Wed, 18 Jun 2014 12:01:51 +0100 From: Anil Madhavapeddy Message-Id: <13D72486-0766-49EA-AE2B-ED8ADE5CE3EF@recoil.org> Date: Wed, 18 Jun 2014 12:01:50 +0100 To: mirageos-devel@lists.xenproject.org Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\)) X-Mailer: Apple Mail (2.1874) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Subject: [MirageOS-devel] outgoing tcp connections X-BeenThere: mirageos-devel@lists.xenproject.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 Mindy submitted a fix to the 'DHCP happening too late' bug in the TCP/IP stack, which only affected unikernels that were making outgoing connections rather than listening. The fix is in https://github.com/mirage/mirage-tcpip/pull/55 In particular, it would be good to know if this fixes your TLS client problem Hannes/David, before I merge it... You can test it via this pin: opam pin tcpip git://github.com/avsm/mirage-tcpip#yomimono-dhcp-without-listen 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 Wed Jun 18 11:24:48 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 18 Jun 2014 11:24: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 1WxDyu-0001AQ-Mx; Wed, 18 Jun 2014 11:24:44 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WxDys-0001A7-Kz for mirageos-devel@lists.xenproject.org; Wed, 18 Jun 2014 11:24:42 +0000 Received: from [85.158.143.35:14261] by server-2.bemta-4.messagelabs.com id 97/CF-06539-9F671A35; Wed, 18 Jun 2014 11:24:41 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-3.tower-21.messagelabs.com!1403090680!11849025!1 X-Originating-IP: [209.85.212.172] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 13496 invoked from network); 18 Jun 2014 11:24:40 -0000 Received: from mail-wi0-f172.google.com (HELO mail-wi0-f172.google.com) (209.85.212.172) by server-3.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 18 Jun 2014 11:24:40 -0000 Received: by mail-wi0-f172.google.com with SMTP id hi2so7437206wib.5 for ; Wed, 18 Jun 2014 04:24:40 -0700 (PDT) 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=wjxN98DXYkg7vrWEObQ8deJ5lmjWhW96Z/E3OCAk8fU=; b=itKgAnhb0eNhw1+dTDFi192PfR3VPrUkK4LUtDo3vO/Gx4H1AV4A7J86ODD5cMQ81g GQDgE0n1/+g38PXp+oZqrjlb1EzBxe7SKtPQISpPFONVFdqcvBLT89PqtS7LGzox4mVp R0aAnhFvsiwUCwwi89bttQg7jQVZ/yvHhRQLUjs4EDxflPfv6CLhVkG2D/Vga7wp5JVT ZSYWD5o4lU5oN2UPvu9O0rWWRX86hnEJefWr0Ta/S3Qn8LNrFggFAKj5hNWetS0Tnw9o 4bSfypfqfMvX1Uo9hbKfJmIRfEtw1SQZZ4ZIGxtE0R7A8lassZjHvvkUukchLs6L+2VR jkQQ== X-Received: by 10.181.13.80 with SMTP id ew16mr3969372wid.51.1403090680235; Wed, 18 Jun 2014 04:24:40 -0700 (PDT) Received: from [192.168.14.16] ([62.49.66.12]) by mx.google.com with ESMTPSA id f6sm2388563wja.25.2014.06.18.04.24.38 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 18 Jun 2014 04:24:39 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\)) From: Thomas Gazagnaire In-Reply-To: <5396D482.6000706@eu.citrix.com> Date: Wed, 18 Jun 2014 12:24:37 +0100 Message-Id: References: <5396D482.6000706@eu.citrix.com> To: Jon Ludlam X-Mailer: Apple Mail (2.1878.2) Cc: Lars Kurth , "mirageos-devel@lists.xenproject.org" , "xen-api@lists.xen.org" Subject: Re: [MirageOS-devel] [Xen-API] Xapi project repositories X-BeenThere: mirageos-devel@lists.xenproject.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, > Third, we have some libraries that are actually mirage core libraries. > These should transfer over to the mirage organisation (remaining in LF, > as mirage is a Xen Project subproject like xapi): There are also a couple of libraries that I've developed while I was in Citrix (and still continue to maintain since then) which are used by xapi and which I could move to the mirage organisation as well: - https://github.com/samoht/ocaml-rpc - https://github.com/samoht/ocaml-tar (which has been forked by djs55) What do you think ? Thomas > > - ocaml-gnt > OCaml grant table manipulation. This code originated in the mirage > project and was put here when it was split out of mirage-platform (see > here: > https://github.com/mirage/mirage-platform/commit/f532fc79af41e0e39b624a8e63dffc900bf1b7e4). > > - ocaml-xenstore > This is the mirage implementation of a xenstore client library. Required > for running mirage kernels on xen. We use the unix-flavour of this > library. It also contains a WIP new version of the guts of a xenstore > daemon, which will be a mirage-style unix process _or_ unikernel > (xenstore stub-domain!) that should eventually be upstreamed into xen. > > - ocaml-xenstore-clients > Slightly oddly named library that defines the unix transport mechanisms > (unix-domain sockets) for using the ocaml-xenstore library. This is the > unix counterpart to the internal shared-page mechanism used by mirage > unikernels. > > - ocaml-evtchn > Similar to ocaml-gnt - split from the main mirage code at around the > same time as ocaml-gnt. > > - ocaml-xenstore-xen > Unused by xapi-project. I believe in here lives the code that turns the > xenstore daemon library from ocaml-xenstore into the actual xenstored > stubdomain or process. > > > > We have a few repositories that are forks of upstream repos with some of > our own changes in. We should get these changes upstreamed at some > point, but for now we should leave them there, but recognise that these > aren't necessarily part of the official Xapi Project (excepting where > they are, e.g. ocaml-xen-lowlevel-libs, which is a staging area for > upstreaming back into xen.git!) > - oclock > - ocamltest > - ocaml-xen-lowlevel-libs > - python-github2 > > > > Then there are generic ocaml libraries which could be used by other > ocaml programs. I think these can live on in the xapi project > organisation for now, but I wouldn't class them as 'core' xapi-project > repos. > > - cdrom > - netdev > - ocamldoc-json > - ocaml-encodings > - ocaml-crc > - ocaml-fd-send-recv > - ocaml-netlink > - ocaml-opasswd > - ocaml-pci-db > - ocaml-qmp > - stdext > - stunnel > - nbd > > > > > Which leaves us with the 'core' xapi project repositories: > > - blktap > - blktap-dkms > - example-ocaml-daemon > - ffs > - forkexecd > - libvhd > - message-switch > - ocaml-rrdd-plugins > - opam-repo-dev > - rrd-transport > - rrdd-plugin-legacy > - rrddump > - sm > - sm-cli > - squeezed > - tapctl > - vhd-tool > - vncproxy > - vncterm > - vxs > - wsproxy > - xapi-codegen > - xapi-libvirt-storage > - xapi-project > - xcp-eliloader > - xcp-guest-templates > - xcp-idl > - xcp-inventory > - xcp-networkd > - xcp-rrd > - xcp-rrdd > - xen-api > - xen-api-client > - xen-api-libs > - xen-api-libs-transitional > - xen-api-sdk > - xenops > - xenops-cli > - xenopsd > > Of the above lists that will remain in the xapi project, these > repositories have incorrect forking status (they are marked as forks of > someone here at Citrix, but shouldn't be): > > Forked from me (jonludlam on github): > xen-api-libs-transitional > xen-api-client > xcp-guest-templates > xcp-eliloader > wsproxy > tapctl > libvhd > blktap-dkms > netdev > nbd > cdrom > > Forked from Dave Scott (djs55) > xcp-idl > vhd-tool > ffs > ocaml-vhd > ocaml-tar > ocaml-fd-send-recv > > Forked from Simon Beaumont (simonjbeaumont): > ocaml-pci-db > > Forked from Mike McClurg (mcclurmc): > ocaml-opasswd > > These forking relationship problems need to be fixed by the people who > own the upstream repo. I don't think it's quite as simple as clicking > the 'transfer repository' button. If anyone knows the exact procedure > for doing this, could they please reply? > > > In summary, I believe we need to: > 1) delete some repositories > 2) move some repositories to xenserver > 3) move some repositories to mirage-project > 4) transfer ownership of some repositories (just flip around the > direction of the fork). > 5) document all of this on the wiki! > > Any comments? > > Jon > > > > > > _______________________________________________ > Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api _______________________________________________ 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 Jun 18 11:24:48 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 18 Jun 2014 11:24: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 1WxDyu-0001AQ-Mx; Wed, 18 Jun 2014 11:24:44 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WxDys-0001A7-Kz for mirageos-devel@lists.xenproject.org; Wed, 18 Jun 2014 11:24:42 +0000 Received: from [85.158.143.35:14261] by server-2.bemta-4.messagelabs.com id 97/CF-06539-9F671A35; Wed, 18 Jun 2014 11:24:41 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-3.tower-21.messagelabs.com!1403090680!11849025!1 X-Originating-IP: [209.85.212.172] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 13496 invoked from network); 18 Jun 2014 11:24:40 -0000 Received: from mail-wi0-f172.google.com (HELO mail-wi0-f172.google.com) (209.85.212.172) by server-3.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 18 Jun 2014 11:24:40 -0000 Received: by mail-wi0-f172.google.com with SMTP id hi2so7437206wib.5 for ; Wed, 18 Jun 2014 04:24:40 -0700 (PDT) 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=wjxN98DXYkg7vrWEObQ8deJ5lmjWhW96Z/E3OCAk8fU=; b=itKgAnhb0eNhw1+dTDFi192PfR3VPrUkK4LUtDo3vO/Gx4H1AV4A7J86ODD5cMQ81g GQDgE0n1/+g38PXp+oZqrjlb1EzBxe7SKtPQISpPFONVFdqcvBLT89PqtS7LGzox4mVp R0aAnhFvsiwUCwwi89bttQg7jQVZ/yvHhRQLUjs4EDxflPfv6CLhVkG2D/Vga7wp5JVT ZSYWD5o4lU5oN2UPvu9O0rWWRX86hnEJefWr0Ta/S3Qn8LNrFggFAKj5hNWetS0Tnw9o 4bSfypfqfMvX1Uo9hbKfJmIRfEtw1SQZZ4ZIGxtE0R7A8lassZjHvvkUukchLs6L+2VR jkQQ== X-Received: by 10.181.13.80 with SMTP id ew16mr3969372wid.51.1403090680235; Wed, 18 Jun 2014 04:24:40 -0700 (PDT) Received: from [192.168.14.16] ([62.49.66.12]) by mx.google.com with ESMTPSA id f6sm2388563wja.25.2014.06.18.04.24.38 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 18 Jun 2014 04:24:39 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\)) From: Thomas Gazagnaire In-Reply-To: <5396D482.6000706@eu.citrix.com> Date: Wed, 18 Jun 2014 12:24:37 +0100 Message-Id: References: <5396D482.6000706@eu.citrix.com> To: Jon Ludlam X-Mailer: Apple Mail (2.1878.2) Cc: Lars Kurth , "mirageos-devel@lists.xenproject.org" , "xen-api@lists.xen.org" Subject: Re: [MirageOS-devel] [Xen-API] Xapi project repositories X-BeenThere: mirageos-devel@lists.xenproject.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, > Third, we have some libraries that are actually mirage core libraries. > These should transfer over to the mirage organisation (remaining in LF, > as mirage is a Xen Project subproject like xapi): There are also a couple of libraries that I've developed while I was in Citrix (and still continue to maintain since then) which are used by xapi and which I could move to the mirage organisation as well: - https://github.com/samoht/ocaml-rpc - https://github.com/samoht/ocaml-tar (which has been forked by djs55) What do you think ? Thomas > > - ocaml-gnt > OCaml grant table manipulation. This code originated in the mirage > project and was put here when it was split out of mirage-platform (see > here: > https://github.com/mirage/mirage-platform/commit/f532fc79af41e0e39b624a8e63dffc900bf1b7e4). > > - ocaml-xenstore > This is the mirage implementation of a xenstore client library. Required > for running mirage kernels on xen. We use the unix-flavour of this > library. It also contains a WIP new version of the guts of a xenstore > daemon, which will be a mirage-style unix process _or_ unikernel > (xenstore stub-domain!) that should eventually be upstreamed into xen. > > - ocaml-xenstore-clients > Slightly oddly named library that defines the unix transport mechanisms > (unix-domain sockets) for using the ocaml-xenstore library. This is the > unix counterpart to the internal shared-page mechanism used by mirage > unikernels. > > - ocaml-evtchn > Similar to ocaml-gnt - split from the main mirage code at around the > same time as ocaml-gnt. > > - ocaml-xenstore-xen > Unused by xapi-project. I believe in here lives the code that turns the > xenstore daemon library from ocaml-xenstore into the actual xenstored > stubdomain or process. > > > > We have a few repositories that are forks of upstream repos with some of > our own changes in. We should get these changes upstreamed at some > point, but for now we should leave them there, but recognise that these > aren't necessarily part of the official Xapi Project (excepting where > they are, e.g. ocaml-xen-lowlevel-libs, which is a staging area for > upstreaming back into xen.git!) > - oclock > - ocamltest > - ocaml-xen-lowlevel-libs > - python-github2 > > > > Then there are generic ocaml libraries which could be used by other > ocaml programs. I think these can live on in the xapi project > organisation for now, but I wouldn't class them as 'core' xapi-project > repos. > > - cdrom > - netdev > - ocamldoc-json > - ocaml-encodings > - ocaml-crc > - ocaml-fd-send-recv > - ocaml-netlink > - ocaml-opasswd > - ocaml-pci-db > - ocaml-qmp > - stdext > - stunnel > - nbd > > > > > Which leaves us with the 'core' xapi project repositories: > > - blktap > - blktap-dkms > - example-ocaml-daemon > - ffs > - forkexecd > - libvhd > - message-switch > - ocaml-rrdd-plugins > - opam-repo-dev > - rrd-transport > - rrdd-plugin-legacy > - rrddump > - sm > - sm-cli > - squeezed > - tapctl > - vhd-tool > - vncproxy > - vncterm > - vxs > - wsproxy > - xapi-codegen > - xapi-libvirt-storage > - xapi-project > - xcp-eliloader > - xcp-guest-templates > - xcp-idl > - xcp-inventory > - xcp-networkd > - xcp-rrd > - xcp-rrdd > - xen-api > - xen-api-client > - xen-api-libs > - xen-api-libs-transitional > - xen-api-sdk > - xenops > - xenops-cli > - xenopsd > > Of the above lists that will remain in the xapi project, these > repositories have incorrect forking status (they are marked as forks of > someone here at Citrix, but shouldn't be): > > Forked from me (jonludlam on github): > xen-api-libs-transitional > xen-api-client > xcp-guest-templates > xcp-eliloader > wsproxy > tapctl > libvhd > blktap-dkms > netdev > nbd > cdrom > > Forked from Dave Scott (djs55) > xcp-idl > vhd-tool > ffs > ocaml-vhd > ocaml-tar > ocaml-fd-send-recv > > Forked from Simon Beaumont (simonjbeaumont): > ocaml-pci-db > > Forked from Mike McClurg (mcclurmc): > ocaml-opasswd > > These forking relationship problems need to be fixed by the people who > own the upstream repo. I don't think it's quite as simple as clicking > the 'transfer repository' button. If anyone knows the exact procedure > for doing this, could they please reply? > > > In summary, I believe we need to: > 1) delete some repositories > 2) move some repositories to xenserver > 3) move some repositories to mirage-project > 4) transfer ownership of some repositories (just flip around the > direction of the fork). > 5) document all of this on the wiki! > > Any comments? > > Jon > > > > > > _______________________________________________ > Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api _______________________________________________ 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 Jun 18 12:13:14 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 18 Jun 2014 12:13: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 1WxEjl-0004rF-C9; Wed, 18 Jun 2014 12:13:09 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WxEji-0004q5-PY; Wed, 18 Jun 2014 12:13:07 +0000 Received: from [193.109.254.147:55303] by server-4.bemta-14.messagelabs.com id CA/F3-02781-05281A35; Wed, 18 Jun 2014 12:13:04 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-7.tower-27.messagelabs.com!1403093582!12063698!1 X-Originating-IP: [74.125.82.47] X-SpamReason: No, hits=0.6 required=7.0 tests=BODY_RANDOM_LONG, HTML_50_60,HTML_MESSAGE,ML_RADAR_SPEW_LINKS_32,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5116 invoked from network); 18 Jun 2014 12:13:03 -0000 Received: from mail-wg0-f47.google.com (HELO mail-wg0-f47.google.com) (74.125.82.47) by server-7.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 18 Jun 2014 12:13:03 -0000 Received: by mail-wg0-f47.google.com with SMTP id k14so726872wgh.18 for ; Wed, 18 Jun 2014 05:13:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:reply-to:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type; bh=mo5zIcohtlUmp5As/b1cbfiM9BJfx2dEvytGqpZDnFM=; b=QGNZBBPXXDGatqZV55YvLEvdaImzNA/ViWGHCTtJfsxednSwU59rstrGmxMYaMGivr XH0IUbLv8YJbr/FCFTZk9ygHRVoNfmSYwtuH+ciAB8qf+pe6MQ9N5nYwdU5tJLWTEOqd wJ6DSG/SPU8Ywa1A4m5AkV4e2Jz0CF+0KwzvVShG5YdSXupUqD/InBmiwyWBUvJjUirV rVrZI8EuA9BEGik6P4q8alWBYiTJDL7j+ToCRA1NRyuPxFLjSkxenzrhlwAmeHD9B7BK PyjBJw7gko3aC7ThLTq3jk8/XmD47P9DaFH42jeItqdXL5mn1xZvNFo3TpI8dF4UQsYV bg4A== X-Received: by 10.194.84.101 with SMTP id x5mr46638311wjy.52.1403093582475; Wed, 18 Jun 2014 05:13:02 -0700 (PDT) Received: from [172.16.25.10] (97e5a5cd.skybroadband.com. [151.229.165.205]) by mx.google.com with ESMTPSA id kp5sm2573841wjb.30.2014.06.18.05.13.00 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 18 Jun 2014 05:13:01 -0700 (PDT) Message-ID: <53A1824C.8010008@xen.org> Date: Wed, 18 Jun 2014 13:13:00 +0100 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: "xen-devel@lists.xen.org" , "xen-api@lists.xen.org" References: <5396F42E.9060901@xen.org> In-Reply-To: <5396F42E.9060901@xen.org> Cc: advisory-board@lists.xenproject.org, Paul Durrant , "mirageos-devel@lists.xenproject.org" Subject: [MirageOS-devel] [Vote Summary] Windows PV Drivers Incubation Project Proposal Approved X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: lars.kurth@xen.org List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2208248900602130833==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org This is a multi-part message in MIME format. --===============2208248900602130833== Content-Type: multipart/alternative; boundary="------------080501040605030401010705" This is a multi-part message in MIME format. --------------080501040605030401010705 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Hi all, this proposal (http://wiki.xenproject.org/wiki/Windows_PV_Drivers_Incubation_Project_Proposal) has gone through with 5 votes in favour and no objections. There were a few minor text changes which Jon Ludlum proposed which don't block us from moving forwand and we also still have some lose ends about namespaces (e.g. exact repo name, mailing list names, etc.). I had discussed this with Paul Durrant initially and will follow up with him tomorrow. 1: We need to tie down the official name in line with trademark rules (this has come up at the board meeting) To comply with trademark rules, the official name needs to be "Xen Project ABC", e.g. "Xen Project Windows Drivers" or "Xen Project Windows PV Drivers" Personally I think shorter is better as it will sound better in press releases and other communication 2: Tie down list name, aka. ABC-devel@... I had suggested win-pv-devel@lists.xenproject.org for the mailing list (to keep it shorter than windows-pv-drivers-devel@) and Paul likes the idea On the other hand, if we go for the shorter project name maybe win-drivers-devel@... is better as more consistent 3: Tie down git repo namespace. As this proposal has been approved first, it will set the precedence for http://wiki.xenproject.org/wiki/Embedded_and_Automotive_PV_Drivers_Project_Proposal What was discussed in the thread related to automotive was: git://xenbits.xen.org/pvdrivers/* as a root for all driver repos making locating driver repos easier Slightly shorter and more consistent is git://xenbits.xen.org/drivers/*, if we went for "Xen Project Windows Drivers"as name Whatever the root is, we should probably chose git://xenbits.xen.org/pvdrivers/win/*.git or git://xenbits.xen.org/drivers/win/*.git for the 5 proposed git repos Timing of launch and creation of infrastructure still need to be worked out, once we agree on the details above. My suggestion would be to amend the proposal after I talked to Paul. We briefly discussed at the Advisory Board meeting yesterday and it would make sense to tie this into a "momentum press release" and time it with the retiring of the ARM and PVOPS subprojects on the grounds that they achieved their project goals of establishing themselves firmly as core parts of the Hypervisor and Linux. But we have to carefully message this to avoid confusion. I had discussed this with Stefano and Konrad, who agree in principle. We also need to look at other upcoming PR for Mirage OS 2.0 (mid July), XAPI 2.0 (TBD) and "load balance". Best Regards Lars On 10/06/14 13:03, Lars Kurth wrote: > Hi all, > > in accordance with http://xenproject.org/governance.html it is time to > vote on > http://wiki.xenproject.org/wiki/Windows_PV_Drivers_Incubation_Project_Proposal > > All maintainers of mature Xen Project sub-projects can vote, which > includes the Hypervisor and XAPI project. The list of eligable people are > > * Hypervisor : see > http://xenbits.xenproject.org/gitweb/?p=xen.git;a=blob;f=MAINTAINERS;hb=HEAD > * XAPI : (see http://xenproject.org/developers/teams/xapi.html, > XAPI PROJECT LEADS & COMMITERS and MAINTAINERS listed on > https://github.com/xapi-project/xen-api) > > If in favour, reply "+1" to this thread > If you do not care, reply "0" > If you object, reply "-1" with a comment justifying the objection > > Best Regards > Lars --------------080501040605030401010705 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Hi all,

this proposal (http://wiki.xenproject.org/wiki/Windows_PV_Drivers_Incubation_Project_Proposal) has gone through with 5 votes in favour and no objections.

There were a few minor text changes which Jon Ludlum proposed which don't block us from moving forwand and we also still have some lose ends about namespaces (e.g. exact repo name, mailing list names, etc.).

I had discussed this with Paul Durrant initially and will follow up with him tomorrow.

1:    We need to tie down the official name in line with trademark rules (this has come up at the board meeting)

        To comply with trademark rules, the official name needs to be "Xen Project ABC", e.g.
        "Xen Project Windows Drivers" or "Xen Project Windows PV Drivers"
        Personally I think shorter is better as it will sound better in press releases and other communication

2:    Tie down list name, aka. ABC-devel@...

        I had suggested win-pv-devel@lists.xenproject.org for the mailing list (to keep it shorter than windows-pv-drivers-devel@) and Paul likes the idea
        On the other hand, if we go for the shorter project name maybe win-drivers-devel@... is better as more consistent

3:    Tie down git repo namespace. As this proposal has been approved first, it will set the precedence for http://wiki.xenproject.org/wiki/Embedded_and_Automotive_PV_Drivers_Project_Proposal
       
        What was discussed in the thread related to automotive was: git://xenbits.xen.org/pvdrivers/* as a root for all driver repos making locating driver repos easier
        Slightly shorter and more consistent is git://xenbits.xen.org/drivers/*, if we went for "Xen Project Windows Drivers"as name
        Whatever the root is, we should probably chose git://xenbits.xen.org/pvdrivers/win/*.git  or  git://xenbits.xen.org/drivers/win/*.git for the 5 proposed git repos

Timing of launch and creation of infrastructure still need to be worked out, once we agree on the details above. My suggestion would be to amend the proposal after I talked to Paul.

We briefly discussed at the Advisory Board meeting yesterday and it would make sense to tie this into a "momentum press release" and time it with the retiring of the ARM and PVOPS subprojects on the grounds that they achieved their project goals of establishing themselves firmly as core parts of the Hypervisor and Linux. But we have to carefully message this to avoid confusion. I had discussed this with Stefano and Konrad, who agree in principle. We also need to look at other upcoming PR for Mirage OS 2.0 (mid July), XAPI 2.0 (TBD) and "load balance".

Best Regards
Lars

On 10/06/14 13:03, Lars Kurth wrote:
Hi all,

in accordance with http://xenproject.org/governance.html it is time to vote on http://wiki.xenproject.org/wiki/Windows_PV_Drivers_Incubation_Project_Proposal

All maintainers of mature Xen Project sub-projects can vote, which includes the Hypervisor and XAPI project. The list of eligable people are
If in favour, reply "+1" to this thread
If you do not care, reply "0"
If you object, reply "-1" with a comment justifying the objection

Best Regards
Lars

--------------080501040605030401010705-- --===============2208248900602130833== 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 --===============2208248900602130833==-- From mirageos-devel-bounces@lists.xenproject.org Wed Jun 18 12:13:14 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 18 Jun 2014 12:13: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 1WxEjl-0004rF-C9; Wed, 18 Jun 2014 12:13:09 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WxEji-0004q5-PY; Wed, 18 Jun 2014 12:13:07 +0000 Received: from [193.109.254.147:55303] by server-4.bemta-14.messagelabs.com id CA/F3-02781-05281A35; Wed, 18 Jun 2014 12:13:04 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-7.tower-27.messagelabs.com!1403093582!12063698!1 X-Originating-IP: [74.125.82.47] X-SpamReason: No, hits=0.6 required=7.0 tests=BODY_RANDOM_LONG, HTML_50_60,HTML_MESSAGE,ML_RADAR_SPEW_LINKS_32,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5116 invoked from network); 18 Jun 2014 12:13:03 -0000 Received: from mail-wg0-f47.google.com (HELO mail-wg0-f47.google.com) (74.125.82.47) by server-7.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 18 Jun 2014 12:13:03 -0000 Received: by mail-wg0-f47.google.com with SMTP id k14so726872wgh.18 for ; Wed, 18 Jun 2014 05:13:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:reply-to:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type; bh=mo5zIcohtlUmp5As/b1cbfiM9BJfx2dEvytGqpZDnFM=; b=QGNZBBPXXDGatqZV55YvLEvdaImzNA/ViWGHCTtJfsxednSwU59rstrGmxMYaMGivr XH0IUbLv8YJbr/FCFTZk9ygHRVoNfmSYwtuH+ciAB8qf+pe6MQ9N5nYwdU5tJLWTEOqd wJ6DSG/SPU8Ywa1A4m5AkV4e2Jz0CF+0KwzvVShG5YdSXupUqD/InBmiwyWBUvJjUirV rVrZI8EuA9BEGik6P4q8alWBYiTJDL7j+ToCRA1NRyuPxFLjSkxenzrhlwAmeHD9B7BK PyjBJw7gko3aC7ThLTq3jk8/XmD47P9DaFH42jeItqdXL5mn1xZvNFo3TpI8dF4UQsYV bg4A== X-Received: by 10.194.84.101 with SMTP id x5mr46638311wjy.52.1403093582475; Wed, 18 Jun 2014 05:13:02 -0700 (PDT) Received: from [172.16.25.10] (97e5a5cd.skybroadband.com. [151.229.165.205]) by mx.google.com with ESMTPSA id kp5sm2573841wjb.30.2014.06.18.05.13.00 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 18 Jun 2014 05:13:01 -0700 (PDT) Message-ID: <53A1824C.8010008@xen.org> Date: Wed, 18 Jun 2014 13:13:00 +0100 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: "xen-devel@lists.xen.org" , "xen-api@lists.xen.org" References: <5396F42E.9060901@xen.org> In-Reply-To: <5396F42E.9060901@xen.org> Cc: advisory-board@lists.xenproject.org, Paul Durrant , "mirageos-devel@lists.xenproject.org" Subject: [MirageOS-devel] [Vote Summary] Windows PV Drivers Incubation Project Proposal Approved X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: lars.kurth@xen.org List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2208248900602130833==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org This is a multi-part message in MIME format. --===============2208248900602130833== Content-Type: multipart/alternative; boundary="------------080501040605030401010705" This is a multi-part message in MIME format. --------------080501040605030401010705 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Hi all, this proposal (http://wiki.xenproject.org/wiki/Windows_PV_Drivers_Incubation_Project_Proposal) has gone through with 5 votes in favour and no objections. There were a few minor text changes which Jon Ludlum proposed which don't block us from moving forwand and we also still have some lose ends about namespaces (e.g. exact repo name, mailing list names, etc.). I had discussed this with Paul Durrant initially and will follow up with him tomorrow. 1: We need to tie down the official name in line with trademark rules (this has come up at the board meeting) To comply with trademark rules, the official name needs to be "Xen Project ABC", e.g. "Xen Project Windows Drivers" or "Xen Project Windows PV Drivers" Personally I think shorter is better as it will sound better in press releases and other communication 2: Tie down list name, aka. ABC-devel@... I had suggested win-pv-devel@lists.xenproject.org for the mailing list (to keep it shorter than windows-pv-drivers-devel@) and Paul likes the idea On the other hand, if we go for the shorter project name maybe win-drivers-devel@... is better as more consistent 3: Tie down git repo namespace. As this proposal has been approved first, it will set the precedence for http://wiki.xenproject.org/wiki/Embedded_and_Automotive_PV_Drivers_Project_Proposal What was discussed in the thread related to automotive was: git://xenbits.xen.org/pvdrivers/* as a root for all driver repos making locating driver repos easier Slightly shorter and more consistent is git://xenbits.xen.org/drivers/*, if we went for "Xen Project Windows Drivers"as name Whatever the root is, we should probably chose git://xenbits.xen.org/pvdrivers/win/*.git or git://xenbits.xen.org/drivers/win/*.git for the 5 proposed git repos Timing of launch and creation of infrastructure still need to be worked out, once we agree on the details above. My suggestion would be to amend the proposal after I talked to Paul. We briefly discussed at the Advisory Board meeting yesterday and it would make sense to tie this into a "momentum press release" and time it with the retiring of the ARM and PVOPS subprojects on the grounds that they achieved their project goals of establishing themselves firmly as core parts of the Hypervisor and Linux. But we have to carefully message this to avoid confusion. I had discussed this with Stefano and Konrad, who agree in principle. We also need to look at other upcoming PR for Mirage OS 2.0 (mid July), XAPI 2.0 (TBD) and "load balance". Best Regards Lars On 10/06/14 13:03, Lars Kurth wrote: > Hi all, > > in accordance with http://xenproject.org/governance.html it is time to > vote on > http://wiki.xenproject.org/wiki/Windows_PV_Drivers_Incubation_Project_Proposal > > All maintainers of mature Xen Project sub-projects can vote, which > includes the Hypervisor and XAPI project. The list of eligable people are > > * Hypervisor : see > http://xenbits.xenproject.org/gitweb/?p=xen.git;a=blob;f=MAINTAINERS;hb=HEAD > * XAPI : (see http://xenproject.org/developers/teams/xapi.html, > XAPI PROJECT LEADS & COMMITERS and MAINTAINERS listed on > https://github.com/xapi-project/xen-api) > > If in favour, reply "+1" to this thread > If you do not care, reply "0" > If you object, reply "-1" with a comment justifying the objection > > Best Regards > Lars --------------080501040605030401010705 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Hi all,

this proposal (http://wiki.xenproject.org/wiki/Windows_PV_Drivers_Incubation_Project_Proposal) has gone through with 5 votes in favour and no objections.

There were a few minor text changes which Jon Ludlum proposed which don't block us from moving forwand and we also still have some lose ends about namespaces (e.g. exact repo name, mailing list names, etc.).

I had discussed this with Paul Durrant initially and will follow up with him tomorrow.

1:    We need to tie down the official name in line with trademark rules (this has come up at the board meeting)

        To comply with trademark rules, the official name needs to be "Xen Project ABC", e.g.
        "Xen Project Windows Drivers" or "Xen Project Windows PV Drivers"
        Personally I think shorter is better as it will sound better in press releases and other communication

2:    Tie down list name, aka. ABC-devel@...

        I had suggested win-pv-devel@lists.xenproject.org for the mailing list (to keep it shorter than windows-pv-drivers-devel@) and Paul likes the idea
        On the other hand, if we go for the shorter project name maybe win-drivers-devel@... is better as more consistent

3:    Tie down git repo namespace. As this proposal has been approved first, it will set the precedence for http://wiki.xenproject.org/wiki/Embedded_and_Automotive_PV_Drivers_Project_Proposal
       
        What was discussed in the thread related to automotive was: git://xenbits.xen.org/pvdrivers/* as a root for all driver repos making locating driver repos easier
        Slightly shorter and more consistent is git://xenbits.xen.org/drivers/*, if we went for "Xen Project Windows Drivers"as name
        Whatever the root is, we should probably chose git://xenbits.xen.org/pvdrivers/win/*.git  or  git://xenbits.xen.org/drivers/win/*.git for the 5 proposed git repos

Timing of launch and creation of infrastructure still need to be worked out, once we agree on the details above. My suggestion would be to amend the proposal after I talked to Paul.

We briefly discussed at the Advisory Board meeting yesterday and it would make sense to tie this into a "momentum press release" and time it with the retiring of the ARM and PVOPS subprojects on the grounds that they achieved their project goals of establishing themselves firmly as core parts of the Hypervisor and Linux. But we have to carefully message this to avoid confusion. I had discussed this with Stefano and Konrad, who agree in principle. We also need to look at other upcoming PR for Mirage OS 2.0 (mid July), XAPI 2.0 (TBD) and "load balance".

Best Regards
Lars

On 10/06/14 13:03, Lars Kurth wrote:
Hi all,

in accordance with http://xenproject.org/governance.html it is time to vote on http://wiki.xenproject.org/wiki/Windows_PV_Drivers_Incubation_Project_Proposal

All maintainers of mature Xen Project sub-projects can vote, which includes the Hypervisor and XAPI project. The list of eligable people are
If in favour, reply "+1" to this thread
If you do not care, reply "0"
If you object, reply "-1" with a comment justifying the objection

Best Regards
Lars

--------------080501040605030401010705-- --===============2208248900602130833== 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 --===============2208248900602130833==-- From mirageos-devel-bounces@lists.xenproject.org Wed Jun 18 12:32:17 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 18 Jun 2014 12:32: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 1WxF2G-00064T-Qz; Wed, 18 Jun 2014 12:32:16 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WxF2F-00063t-N9 for mirageos-devel@lists.xenproject.org; Wed, 18 Jun 2014 12:32:15 +0000 Received: from [193.109.254.147:63055] by server-10.bemta-14.messagelabs.com id FE/31-04546-EC681A35; Wed, 18 Jun 2014 12:32:14 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-7.tower-27.messagelabs.com!1403094733!12069194!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30344 invoked from network); 18 Jun 2014 12:32:13 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-7.tower-27.messagelabs.com with SMTP; 18 Jun 2014 12:32:13 -0000 Received: (qmail 9179 invoked by uid 634); 18 Jun 2014 12:32:13 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from cpc11-belf9-2-0-cust355.2-1.cable.virginm.net (HELO [10.0.1.15]) (86.24.61.100) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Wed, 18 Jun 2014 13:32:12 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\)) From: Anil Madhavapeddy In-Reply-To: Date: Wed, 18 Jun 2014 13:32:10 +0100 Message-Id: References: <5396D482.6000706@eu.citrix.com> To: Thomas Gazagnaire X-Mailer: Apple Mail (2.1874) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: Lars Kurth , Jon Ludlam , "mirageos-devel@lists.xenproject.org" , "xen-api@lists.xen.org" Subject: Re: [MirageOS-devel] [Xen-API] Xapi project repositories X-BeenThere: mirageos-devel@lists.xenproject.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 18 Jun 2014, at 12:24, Thomas Gazagnaire wrote: > Hi, > >> Third, we have some libraries that are actually mirage core libraries. >> These should transfer over to the mirage organisation (remaining in LF, >> as mirage is a Xen Project subproject like xapi): > > There are also a couple of libraries that I've developed while I was in Citrix (and still continue to maintain since then) which are used by xapi and which I could move to the mirage organisation as well: > > - https://github.com/samoht/ocaml-rpc > - https://github.com/samoht/ocaml-tar (which has been forked by djs55) Moving both of those to Mirage makes sense to me, as they're policy-free and fairly easy to plugin. Ocaml-tar in particular seems to have done the rounds among all the organizations :-) -anil > What do you think ? > > Thomas > > >> >> - ocaml-gnt >> OCaml grant table manipulation. This code originated in the mirage >> project and was put here when it was split out of mirage-platform (see >> here: >> https://github.com/mirage/mirage-platform/commit/f532fc79af41e0e39b624a8e63dffc900bf1b7e4). >> >> - ocaml-xenstore >> This is the mirage implementation of a xenstore client library. Required >> for running mirage kernels on xen. We use the unix-flavour of this >> library. It also contains a WIP new version of the guts of a xenstore >> daemon, which will be a mirage-style unix process _or_ unikernel >> (xenstore stub-domain!) that should eventually be upstreamed into xen. >> >> - ocaml-xenstore-clients >> Slightly oddly named library that defines the unix transport mechanisms >> (unix-domain sockets) for using the ocaml-xenstore library. This is the >> unix counterpart to the internal shared-page mechanism used by mirage >> unikernels. >> >> - ocaml-evtchn >> Similar to ocaml-gnt - split from the main mirage code at around the >> same time as ocaml-gnt. >> >> - ocaml-xenstore-xen >> Unused by xapi-project. I believe in here lives the code that turns the >> xenstore daemon library from ocaml-xenstore into the actual xenstored >> stubdomain or process. >> >> >> >> We have a few repositories that are forks of upstream repos with some of >> our own changes in. We should get these changes upstreamed at some >> point, but for now we should leave them there, but recognise that these >> aren't necessarily part of the official Xapi Project (excepting where >> they are, e.g. ocaml-xen-lowlevel-libs, which is a staging area for >> upstreaming back into xen.git!) >> - oclock >> - ocamltest >> - ocaml-xen-lowlevel-libs >> - python-github2 >> >> >> >> Then there are generic ocaml libraries which could be used by other >> ocaml programs. I think these can live on in the xapi project >> organisation for now, but I wouldn't class them as 'core' xapi-project >> repos. >> >> - cdrom >> - netdev >> - ocamldoc-json >> - ocaml-encodings >> - ocaml-crc >> - ocaml-fd-send-recv >> - ocaml-netlink >> - ocaml-opasswd >> - ocaml-pci-db >> - ocaml-qmp >> - stdext >> - stunnel >> - nbd >> >> >> >> >> Which leaves us with the 'core' xapi project repositories: >> >> - blktap >> - blktap-dkms >> - example-ocaml-daemon >> - ffs >> - forkexecd >> - libvhd >> - message-switch >> - ocaml-rrdd-plugins >> - opam-repo-dev >> - rrd-transport >> - rrdd-plugin-legacy >> - rrddump >> - sm >> - sm-cli >> - squeezed >> - tapctl >> - vhd-tool >> - vncproxy >> - vncterm >> - vxs >> - wsproxy >> - xapi-codegen >> - xapi-libvirt-storage >> - xapi-project >> - xcp-eliloader >> - xcp-guest-templates >> - xcp-idl >> - xcp-inventory >> - xcp-networkd >> - xcp-rrd >> - xcp-rrdd >> - xen-api >> - xen-api-client >> - xen-api-libs >> - xen-api-libs-transitional >> - xen-api-sdk >> - xenops >> - xenops-cli >> - xenopsd >> >> Of the above lists that will remain in the xapi project, these >> repositories have incorrect forking status (they are marked as forks of >> someone here at Citrix, but shouldn't be): >> >> Forked from me (jonludlam on github): >> xen-api-libs-transitional >> xen-api-client >> xcp-guest-templates >> xcp-eliloader >> wsproxy >> tapctl >> libvhd >> blktap-dkms >> netdev >> nbd >> cdrom >> >> Forked from Dave Scott (djs55) >> xcp-idl >> vhd-tool >> ffs >> ocaml-vhd >> ocaml-tar >> ocaml-fd-send-recv >> >> Forked from Simon Beaumont (simonjbeaumont): >> ocaml-pci-db >> >> Forked from Mike McClurg (mcclurmc): >> ocaml-opasswd >> >> These forking relationship problems need to be fixed by the people who >> own the upstream repo. I don't think it's quite as simple as clicking >> the 'transfer repository' button. If anyone knows the exact procedure >> for doing this, could they please reply? >> >> >> In summary, I believe we need to: >> 1) delete some repositories >> 2) move some repositories to xenserver >> 3) move some repositories to mirage-project >> 4) transfer ownership of some repositories (just flip around the >> direction of the fork). >> 5) document all of this on the wiki! >> >> Any comments? >> >> Jon >> >> >> >> >> >> _______________________________________________ >> Xen-api mailing list >> Xen-api@lists.xen.org >> http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api > > > _______________________________________________ > Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api > _______________________________________________ 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 Jun 18 12:32:17 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 18 Jun 2014 12:32: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 1WxF2G-00064T-Qz; Wed, 18 Jun 2014 12:32:16 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WxF2F-00063t-N9 for mirageos-devel@lists.xenproject.org; Wed, 18 Jun 2014 12:32:15 +0000 Received: from [193.109.254.147:63055] by server-10.bemta-14.messagelabs.com id FE/31-04546-EC681A35; Wed, 18 Jun 2014 12:32:14 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-7.tower-27.messagelabs.com!1403094733!12069194!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30344 invoked from network); 18 Jun 2014 12:32:13 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-7.tower-27.messagelabs.com with SMTP; 18 Jun 2014 12:32:13 -0000 Received: (qmail 9179 invoked by uid 634); 18 Jun 2014 12:32:13 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from cpc11-belf9-2-0-cust355.2-1.cable.virginm.net (HELO [10.0.1.15]) (86.24.61.100) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Wed, 18 Jun 2014 13:32:12 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\)) From: Anil Madhavapeddy In-Reply-To: Date: Wed, 18 Jun 2014 13:32:10 +0100 Message-Id: References: <5396D482.6000706@eu.citrix.com> To: Thomas Gazagnaire X-Mailer: Apple Mail (2.1874) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: Lars Kurth , Jon Ludlam , "mirageos-devel@lists.xenproject.org" , "xen-api@lists.xen.org" Subject: Re: [MirageOS-devel] [Xen-API] Xapi project repositories X-BeenThere: mirageos-devel@lists.xenproject.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 18 Jun 2014, at 12:24, Thomas Gazagnaire wrote: > Hi, > >> Third, we have some libraries that are actually mirage core libraries. >> These should transfer over to the mirage organisation (remaining in LF, >> as mirage is a Xen Project subproject like xapi): > > There are also a couple of libraries that I've developed while I was in Citrix (and still continue to maintain since then) which are used by xapi and which I could move to the mirage organisation as well: > > - https://github.com/samoht/ocaml-rpc > - https://github.com/samoht/ocaml-tar (which has been forked by djs55) Moving both of those to Mirage makes sense to me, as they're policy-free and fairly easy to plugin. Ocaml-tar in particular seems to have done the rounds among all the organizations :-) -anil > What do you think ? > > Thomas > > >> >> - ocaml-gnt >> OCaml grant table manipulation. This code originated in the mirage >> project and was put here when it was split out of mirage-platform (see >> here: >> https://github.com/mirage/mirage-platform/commit/f532fc79af41e0e39b624a8e63dffc900bf1b7e4). >> >> - ocaml-xenstore >> This is the mirage implementation of a xenstore client library. Required >> for running mirage kernels on xen. We use the unix-flavour of this >> library. It also contains a WIP new version of the guts of a xenstore >> daemon, which will be a mirage-style unix process _or_ unikernel >> (xenstore stub-domain!) that should eventually be upstreamed into xen. >> >> - ocaml-xenstore-clients >> Slightly oddly named library that defines the unix transport mechanisms >> (unix-domain sockets) for using the ocaml-xenstore library. This is the >> unix counterpart to the internal shared-page mechanism used by mirage >> unikernels. >> >> - ocaml-evtchn >> Similar to ocaml-gnt - split from the main mirage code at around the >> same time as ocaml-gnt. >> >> - ocaml-xenstore-xen >> Unused by xapi-project. I believe in here lives the code that turns the >> xenstore daemon library from ocaml-xenstore into the actual xenstored >> stubdomain or process. >> >> >> >> We have a few repositories that are forks of upstream repos with some of >> our own changes in. We should get these changes upstreamed at some >> point, but for now we should leave them there, but recognise that these >> aren't necessarily part of the official Xapi Project (excepting where >> they are, e.g. ocaml-xen-lowlevel-libs, which is a staging area for >> upstreaming back into xen.git!) >> - oclock >> - ocamltest >> - ocaml-xen-lowlevel-libs >> - python-github2 >> >> >> >> Then there are generic ocaml libraries which could be used by other >> ocaml programs. I think these can live on in the xapi project >> organisation for now, but I wouldn't class them as 'core' xapi-project >> repos. >> >> - cdrom >> - netdev >> - ocamldoc-json >> - ocaml-encodings >> - ocaml-crc >> - ocaml-fd-send-recv >> - ocaml-netlink >> - ocaml-opasswd >> - ocaml-pci-db >> - ocaml-qmp >> - stdext >> - stunnel >> - nbd >> >> >> >> >> Which leaves us with the 'core' xapi project repositories: >> >> - blktap >> - blktap-dkms >> - example-ocaml-daemon >> - ffs >> - forkexecd >> - libvhd >> - message-switch >> - ocaml-rrdd-plugins >> - opam-repo-dev >> - rrd-transport >> - rrdd-plugin-legacy >> - rrddump >> - sm >> - sm-cli >> - squeezed >> - tapctl >> - vhd-tool >> - vncproxy >> - vncterm >> - vxs >> - wsproxy >> - xapi-codegen >> - xapi-libvirt-storage >> - xapi-project >> - xcp-eliloader >> - xcp-guest-templates >> - xcp-idl >> - xcp-inventory >> - xcp-networkd >> - xcp-rrd >> - xcp-rrdd >> - xen-api >> - xen-api-client >> - xen-api-libs >> - xen-api-libs-transitional >> - xen-api-sdk >> - xenops >> - xenops-cli >> - xenopsd >> >> Of the above lists that will remain in the xapi project, these >> repositories have incorrect forking status (they are marked as forks of >> someone here at Citrix, but shouldn't be): >> >> Forked from me (jonludlam on github): >> xen-api-libs-transitional >> xen-api-client >> xcp-guest-templates >> xcp-eliloader >> wsproxy >> tapctl >> libvhd >> blktap-dkms >> netdev >> nbd >> cdrom >> >> Forked from Dave Scott (djs55) >> xcp-idl >> vhd-tool >> ffs >> ocaml-vhd >> ocaml-tar >> ocaml-fd-send-recv >> >> Forked from Simon Beaumont (simonjbeaumont): >> ocaml-pci-db >> >> Forked from Mike McClurg (mcclurmc): >> ocaml-opasswd >> >> These forking relationship problems need to be fixed by the people who >> own the upstream repo. I don't think it's quite as simple as clicking >> the 'transfer repository' button. If anyone knows the exact procedure >> for doing this, could they please reply? >> >> >> In summary, I believe we need to: >> 1) delete some repositories >> 2) move some repositories to xenserver >> 3) move some repositories to mirage-project >> 4) transfer ownership of some repositories (just flip around the >> direction of the fork). >> 5) document all of this on the wiki! >> >> Any comments? >> >> Jon >> >> >> >> >> >> _______________________________________________ >> Xen-api mailing list >> Xen-api@lists.xen.org >> http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api > > > _______________________________________________ > Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api > _______________________________________________ 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 Jun 18 12:47:01 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 18 Jun 2014 12:47: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 1WxFGV-0006fa-Th; Wed, 18 Jun 2014 12:46:59 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WxFGU-0006fV-7b for mirageos-devel@lists.xenproject.org; Wed, 18 Jun 2014 12:46:58 +0000 Received: from [85.158.137.68:13271] by server-4.bemta-3.messagelabs.com id B8/20-17399-14A81A35; Wed, 18 Jun 2014 12:46:57 +0000 X-Env-Sender: hannes@mehnert.org X-Msg-Ref: server-7.tower-31.messagelabs.com!1403095616!10860996!1 X-Originating-IP: [213.73.89.200] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 9268 invoked from network); 18 Jun 2014 12:46:56 -0000 Received: from mail.mehnert.org (HELO mail.mehnert.org) (213.73.89.200) by server-7.tower-31.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 18 Jun 2014 12:46:56 -0000 Received: from [128.232.110.146] (c146.al.cl.cam.ac.uk [128.232.110.146]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client CN "hannes@mehnert.org", Issuer "mehnert root CA" (verified OK)) by mail.mehnert.org (Postfix) with ESMTPS id 5AA8C234F for ; Wed, 18 Jun 2014 14:46:55 +0200 (CEST) Message-ID: <53A189FC.7020804@mehnert.org> Date: Wed, 18 Jun 2014 13:45:48 +0100 From: Hannes Mehnert User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: mirageos-devel@lists.xenproject.org References: <13D72486-0766-49EA-AE2B-ED8ADE5CE3EF@recoil.org> In-Reply-To: <13D72486-0766-49EA-AE2B-ED8ADE5CE3EF@recoil.org> Subject: Re: [MirageOS-devel] outgoing tcp connections X-BeenThere: mirageos-devel@lists.xenproject.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 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA384 On 06/18/2014 12:01, Anil Madhavapeddy wrote: > Mindy submitted a fix to the 'DHCP happening too late' bug in the > TCP/IP stack, which only affected unikernels that were making > outgoing connections rather than listening. I saw that. Great work! And I just tested it, and it works here. Another (related) issue is when using tap and no dhcp, I've to be fast between executing the client and assigning a IP address in the hostsystem for tap0 (whenever an application is started, the host system IP gets removed) in order to reply to ARP to the mirage stack. Great work, Mindy! Hannes -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (FreeBSD) iQIcBAEBCQAGBQJToYn8AAoJELyJZYjffCjuId0P/26pIY9vKW+llXok7GKywBGj xXTFWl0lKtONx14ILNPUQEdCOCTf+EovuRrQkq2ssu0Z1W9psBADmySKYuxJVahJ QCctbCIR9ZK3DSMwbCZx4dG/xY3JJpf2mqDeLosxm4Wqs5lK/6fZIhM1X1P95tt6 SAc3eK5tZTHRyQwFgpVTiDsRDXNKFQzXaOdPdwl4UL15bYGBxBLiefajA6NNPtHX SPbMXelYp2xGjtL/i1MuX4E0FTiJ/MtmHsbHJIhvDsKCVTJe5hDNBeU8JH/QSQiJ VCJXN1efDoJvHYB1AqLq0kZEBXkoirEm+XCQKX9X2lbZuZT9xrpO6Q/1YHZVp/gW hKwHjIMlRXpQCpwHJAbTDnLqgrnazfVB3WUApd8bvM7ZQsa7Y0yCg0+PKZW/plBk TP+J5JM4HPyUMZ+rSTDwt2wBMfmLd8CdIC1G4INnBslA3WifP8dS3wgUe7YMumkg /bnspWy84KpB7lv37POhSAa4X4zDGOmnNz+42t2OsmkbBtLjvq+kk3NH42kc01cX kEg9YwKZ0FBWXlkZ2hoTAk33rPHgDHQjs8YXwMnoxMoQnL6gNKkKMpYQAjtivEpr BUGfEQ/RsUaDbQb7ur9f7nARmFhyjBEh+JngYyTFSu6L4nkbrzxubMQCKdIvt989 MmDenF7nbG5bf2Fu39jP =aOBm -----END PGP SIGNATURE----- _______________________________________________ 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 Jun 18 12:47:01 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 18 Jun 2014 12:47: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 1WxFGV-0006fa-Th; Wed, 18 Jun 2014 12:46:59 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WxFGU-0006fV-7b for mirageos-devel@lists.xenproject.org; Wed, 18 Jun 2014 12:46:58 +0000 Received: from [85.158.137.68:13271] by server-4.bemta-3.messagelabs.com id B8/20-17399-14A81A35; Wed, 18 Jun 2014 12:46:57 +0000 X-Env-Sender: hannes@mehnert.org X-Msg-Ref: server-7.tower-31.messagelabs.com!1403095616!10860996!1 X-Originating-IP: [213.73.89.200] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 9268 invoked from network); 18 Jun 2014 12:46:56 -0000 Received: from mail.mehnert.org (HELO mail.mehnert.org) (213.73.89.200) by server-7.tower-31.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 18 Jun 2014 12:46:56 -0000 Received: from [128.232.110.146] (c146.al.cl.cam.ac.uk [128.232.110.146]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client CN "hannes@mehnert.org", Issuer "mehnert root CA" (verified OK)) by mail.mehnert.org (Postfix) with ESMTPS id 5AA8C234F for ; Wed, 18 Jun 2014 14:46:55 +0200 (CEST) Message-ID: <53A189FC.7020804@mehnert.org> Date: Wed, 18 Jun 2014 13:45:48 +0100 From: Hannes Mehnert User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: mirageos-devel@lists.xenproject.org References: <13D72486-0766-49EA-AE2B-ED8ADE5CE3EF@recoil.org> In-Reply-To: <13D72486-0766-49EA-AE2B-ED8ADE5CE3EF@recoil.org> Subject: Re: [MirageOS-devel] outgoing tcp connections X-BeenThere: mirageos-devel@lists.xenproject.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 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA384 On 06/18/2014 12:01, Anil Madhavapeddy wrote: > Mindy submitted a fix to the 'DHCP happening too late' bug in the > TCP/IP stack, which only affected unikernels that were making > outgoing connections rather than listening. I saw that. Great work! And I just tested it, and it works here. Another (related) issue is when using tap and no dhcp, I've to be fast between executing the client and assigning a IP address in the hostsystem for tap0 (whenever an application is started, the host system IP gets removed) in order to reply to ARP to the mirage stack. Great work, Mindy! Hannes -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (FreeBSD) iQIcBAEBCQAGBQJToYn8AAoJELyJZYjffCjuId0P/26pIY9vKW+llXok7GKywBGj xXTFWl0lKtONx14ILNPUQEdCOCTf+EovuRrQkq2ssu0Z1W9psBADmySKYuxJVahJ QCctbCIR9ZK3DSMwbCZx4dG/xY3JJpf2mqDeLosxm4Wqs5lK/6fZIhM1X1P95tt6 SAc3eK5tZTHRyQwFgpVTiDsRDXNKFQzXaOdPdwl4UL15bYGBxBLiefajA6NNPtHX SPbMXelYp2xGjtL/i1MuX4E0FTiJ/MtmHsbHJIhvDsKCVTJe5hDNBeU8JH/QSQiJ VCJXN1efDoJvHYB1AqLq0kZEBXkoirEm+XCQKX9X2lbZuZT9xrpO6Q/1YHZVp/gW hKwHjIMlRXpQCpwHJAbTDnLqgrnazfVB3WUApd8bvM7ZQsa7Y0yCg0+PKZW/plBk TP+J5JM4HPyUMZ+rSTDwt2wBMfmLd8CdIC1G4INnBslA3WifP8dS3wgUe7YMumkg /bnspWy84KpB7lv37POhSAa4X4zDGOmnNz+42t2OsmkbBtLjvq+kk3NH42kc01cX kEg9YwKZ0FBWXlkZ2hoTAk33rPHgDHQjs8YXwMnoxMoQnL6gNKkKMpYQAjtivEpr BUGfEQ/RsUaDbQb7ur9f7nARmFhyjBEh+JngYyTFSu6L4nkbrzxubMQCKdIvt989 MmDenF7nbG5bf2Fu39jP =aOBm -----END PGP SIGNATURE----- _______________________________________________ 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 Jun 18 12:51:22 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 18 Jun 2014 12:51: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 1WxFKk-0006q1-5T; Wed, 18 Jun 2014 12:51:22 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WxFKi-0006ps-OW for mirageos-devel@lists.xenproject.org; Wed, 18 Jun 2014 12:51:20 +0000 Received: from [85.158.143.35:41187] by server-3.bemta-4.messagelabs.com id 63/6F-16194-84B81A35; Wed, 18 Jun 2014 12:51:20 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-10.tower-21.messagelabs.com!1403095879!12226077!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25302 invoked from network); 18 Jun 2014 12:51:19 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-10.tower-21.messagelabs.com with SMTP; 18 Jun 2014 12:51:19 -0000 Received: (qmail 16832 invoked by uid 634); 18 Jun 2014 12:51:19 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from cpc11-belf9-2-0-cust355.2-1.cable.virginm.net (HELO [10.0.1.15]) (86.24.61.100) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Wed, 18 Jun 2014 13:51:18 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\)) From: Anil Madhavapeddy In-Reply-To: <53A189FC.7020804@mehnert.org> Date: Wed, 18 Jun 2014 13:51:17 +0100 Message-Id: <42BBD403-02AA-4C26-AD1E-4D923622F9AF@recoil.org> References: <13D72486-0766-49EA-AE2B-ED8ADE5CE3EF@recoil.org> <53A189FC.7020804@mehnert.org> To: Hannes Mehnert X-Mailer: Apple Mail (2.1874) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] outgoing tcp connections X-BeenThere: mirageos-devel@lists.xenproject.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 18 Jun 2014, at 13:45, Hannes Mehnert wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA384 > > On 06/18/2014 12:01, Anil Madhavapeddy wrote: >> Mindy submitted a fix to the 'DHCP happening too late' bug in the >> TCP/IP stack, which only affected unikernels that were making >> outgoing connections rather than listening. > > I saw that. Great work! And I just tested it, and it works here. > > Another (related) issue is when using tap and no dhcp, I've to be fast > between executing the client and assigning a IP address in the > hostsystem for tap0 (whenever an application is started, the host > system IP gets removed) in order to reply to ARP to the mirage stack. Hrm yes, doing bridge setup is something I'm not keen on putting into our tools. Ideally, we would use persistent tunnels that could be set up by external tools and then attached to by the Unix unikernel. Does the FreeBSD tuntap support persistent tun devices? The MacOS X tuntap is the only reason we're stuck with this current painful model. However, there is a light on this horizon, as I discovered that MacOS X 10.10-beta has the vmnet framework installed by default, which finally gives us bridging support there without needing the installing of OSXtuntap. I'll write bindings when I get a chance... -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 Jun 18 12:51:22 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 18 Jun 2014 12:51: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 1WxFKk-0006q1-5T; Wed, 18 Jun 2014 12:51:22 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WxFKi-0006ps-OW for mirageos-devel@lists.xenproject.org; Wed, 18 Jun 2014 12:51:20 +0000 Received: from [85.158.143.35:41187] by server-3.bemta-4.messagelabs.com id 63/6F-16194-84B81A35; Wed, 18 Jun 2014 12:51:20 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-10.tower-21.messagelabs.com!1403095879!12226077!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25302 invoked from network); 18 Jun 2014 12:51:19 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-10.tower-21.messagelabs.com with SMTP; 18 Jun 2014 12:51:19 -0000 Received: (qmail 16832 invoked by uid 634); 18 Jun 2014 12:51:19 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from cpc11-belf9-2-0-cust355.2-1.cable.virginm.net (HELO [10.0.1.15]) (86.24.61.100) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Wed, 18 Jun 2014 13:51:18 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\)) From: Anil Madhavapeddy In-Reply-To: <53A189FC.7020804@mehnert.org> Date: Wed, 18 Jun 2014 13:51:17 +0100 Message-Id: <42BBD403-02AA-4C26-AD1E-4D923622F9AF@recoil.org> References: <13D72486-0766-49EA-AE2B-ED8ADE5CE3EF@recoil.org> <53A189FC.7020804@mehnert.org> To: Hannes Mehnert X-Mailer: Apple Mail (2.1874) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] outgoing tcp connections X-BeenThere: mirageos-devel@lists.xenproject.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 18 Jun 2014, at 13:45, Hannes Mehnert wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA384 > > On 06/18/2014 12:01, Anil Madhavapeddy wrote: >> Mindy submitted a fix to the 'DHCP happening too late' bug in the >> TCP/IP stack, which only affected unikernels that were making >> outgoing connections rather than listening. > > I saw that. Great work! And I just tested it, and it works here. > > Another (related) issue is when using tap and no dhcp, I've to be fast > between executing the client and assigning a IP address in the > hostsystem for tap0 (whenever an application is started, the host > system IP gets removed) in order to reply to ARP to the mirage stack. Hrm yes, doing bridge setup is something I'm not keen on putting into our tools. Ideally, we would use persistent tunnels that could be set up by external tools and then attached to by the Unix unikernel. Does the FreeBSD tuntap support persistent tun devices? The MacOS X tuntap is the only reason we're stuck with this current painful model. However, there is a light on this horizon, as I discovered that MacOS X 10.10-beta has the vmnet framework installed by default, which finally gives us bridging support there without needing the installing of OSXtuntap. I'll write bindings when I get a chance... -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 Jun 18 12:58:16 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 18 Jun 2014 12:58: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 1WxFRP-0007RN-S8; Wed, 18 Jun 2014 12:58:15 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WxFRO-0007R1-Mb for mirageos-devel@lists.xenproject.org; Wed, 18 Jun 2014 12:58:14 +0000 Received: from [193.109.254.147:22196] by server-1.bemta-14.messagelabs.com id 10/01-00839-6EC81A35; Wed, 18 Jun 2014 12:58:14 +0000 X-Env-Sender: hannes@mehnert.org X-Msg-Ref: server-12.tower-27.messagelabs.com!1403096292!12116923!1 X-Originating-IP: [213.73.89.200] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12891 invoked from network); 18 Jun 2014 12:58:13 -0000 Received: from mail.mehnert.org (HELO mail.mehnert.org) (213.73.89.200) by server-12.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 18 Jun 2014 12:58:13 -0000 Received: from [128.232.110.146] (c146.al.cl.cam.ac.uk [128.232.110.146]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client CN "hannes@mehnert.org", Issuer "mehnert root CA" (verified OK)) by mail.mehnert.org (Postfix) with ESMTPS id 799102742 for ; Wed, 18 Jun 2014 14:58:12 +0200 (CEST) Message-ID: <53A18CA1.3050502@mehnert.org> Date: Wed, 18 Jun 2014 13:57:05 +0100 From: Hannes Mehnert User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: mirageos-devel@lists.xenproject.org References: <13D72486-0766-49EA-AE2B-ED8ADE5CE3EF@recoil.org> <53A189FC.7020804@mehnert.org> <42BBD403-02AA-4C26-AD1E-4D923622F9AF@recoil.org> In-Reply-To: <42BBD403-02AA-4C26-AD1E-4D923622F9AF@recoil.org> Subject: Re: [MirageOS-devel] outgoing tcp connections X-BeenThere: mirageos-devel@lists.xenproject.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 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA384 On 06/18/2014 13:51, Anil Madhavapeddy wrote: > Does the FreeBSD tuntap support persistent tun devices? Oh, yes, actually it does: ifconfig tun create -> tun0 (or whichever is free) ifconfig tun0 10.0.0.1/24 sudo ./main.native ~~> voila [now after execution of main.native ended, 10.0.0.1 is no longer configured on tun0] Hannes -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (FreeBSD) iQIcBAEBCQAGBQJToYyhAAoJELyJZYjffCjunH8P/RTHSODMDIijnT+TM3kpWXdN X5hxlVuMGOzQvX0Yt9pYdLkpyv0oowjbdWwU/XVLM2J4fPVgPMdX/oT09puYh2c3 wcnIerNTw02kSjM6vugF2Z0A0Li5FS3jJKTGgeUwB/UrLjH3ZQYUeV0j+DfTybuA lN3jOwntjIP+9HN6rJxEwryikI6CBsWTkzU+956aPDs21aoSyBwgT4SK+DioVGhD GhXMX3wFbb8x+zKXFXG0zdSoBoit5YcRU18fCMmr6HvXpBPbzrYN8CGshOhOwvy4 LUIfiBoAG7MxMAK3qoV302LM0ldtSHtcMkZA4sbSHuCnwzPVajb5OKR1ohdjLJeQ 4/7+MP7ZoSb8zA1BN/r52fI6ova9Bo+ZlWKqEVwrYWiuXC+5OV+UffwQ5YkKOOhD Gys26szij8HMmFj/GdJKhPB7Ht3hxSKI64W1VMX5UmEJ8RhEw+EUEyI5C8aSQEUg 7AbXejl5R8bvE3+5VkRaL9dOKJeDR6NtMFlAMv8yHhb+DgAMxJOqovNygoPc3hqA 5i6/2KJf4ynJzbAhzLjTl4NT38GkUMaBICOhansELxvylrF/EoCRnh/5ONfjl74s 4IWwxfyh3m4j9huuQDSmMDgDWW2CqJuVTtqEhlFfZLkfntR/opf6ymc6WsVl516F 68nZxOKki1vtofCRwiGU =+H1P -----END PGP SIGNATURE----- _______________________________________________ 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 Jun 18 12:58:16 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 18 Jun 2014 12:58: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 1WxFRP-0007RN-S8; Wed, 18 Jun 2014 12:58:15 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WxFRO-0007R1-Mb for mirageos-devel@lists.xenproject.org; Wed, 18 Jun 2014 12:58:14 +0000 Received: from [193.109.254.147:22196] by server-1.bemta-14.messagelabs.com id 10/01-00839-6EC81A35; Wed, 18 Jun 2014 12:58:14 +0000 X-Env-Sender: hannes@mehnert.org X-Msg-Ref: server-12.tower-27.messagelabs.com!1403096292!12116923!1 X-Originating-IP: [213.73.89.200] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12891 invoked from network); 18 Jun 2014 12:58:13 -0000 Received: from mail.mehnert.org (HELO mail.mehnert.org) (213.73.89.200) by server-12.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 18 Jun 2014 12:58:13 -0000 Received: from [128.232.110.146] (c146.al.cl.cam.ac.uk [128.232.110.146]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client CN "hannes@mehnert.org", Issuer "mehnert root CA" (verified OK)) by mail.mehnert.org (Postfix) with ESMTPS id 799102742 for ; Wed, 18 Jun 2014 14:58:12 +0200 (CEST) Message-ID: <53A18CA1.3050502@mehnert.org> Date: Wed, 18 Jun 2014 13:57:05 +0100 From: Hannes Mehnert User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: mirageos-devel@lists.xenproject.org References: <13D72486-0766-49EA-AE2B-ED8ADE5CE3EF@recoil.org> <53A189FC.7020804@mehnert.org> <42BBD403-02AA-4C26-AD1E-4D923622F9AF@recoil.org> In-Reply-To: <42BBD403-02AA-4C26-AD1E-4D923622F9AF@recoil.org> Subject: Re: [MirageOS-devel] outgoing tcp connections X-BeenThere: mirageos-devel@lists.xenproject.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 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA384 On 06/18/2014 13:51, Anil Madhavapeddy wrote: > Does the FreeBSD tuntap support persistent tun devices? Oh, yes, actually it does: ifconfig tun create -> tun0 (or whichever is free) ifconfig tun0 10.0.0.1/24 sudo ./main.native ~~> voila [now after execution of main.native ended, 10.0.0.1 is no longer configured on tun0] Hannes -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (FreeBSD) iQIcBAEBCQAGBQJToYyhAAoJELyJZYjffCjunH8P/RTHSODMDIijnT+TM3kpWXdN X5hxlVuMGOzQvX0Yt9pYdLkpyv0oowjbdWwU/XVLM2J4fPVgPMdX/oT09puYh2c3 wcnIerNTw02kSjM6vugF2Z0A0Li5FS3jJKTGgeUwB/UrLjH3ZQYUeV0j+DfTybuA lN3jOwntjIP+9HN6rJxEwryikI6CBsWTkzU+956aPDs21aoSyBwgT4SK+DioVGhD GhXMX3wFbb8x+zKXFXG0zdSoBoit5YcRU18fCMmr6HvXpBPbzrYN8CGshOhOwvy4 LUIfiBoAG7MxMAK3qoV302LM0ldtSHtcMkZA4sbSHuCnwzPVajb5OKR1ohdjLJeQ 4/7+MP7ZoSb8zA1BN/r52fI6ova9Bo+ZlWKqEVwrYWiuXC+5OV+UffwQ5YkKOOhD Gys26szij8HMmFj/GdJKhPB7Ht3hxSKI64W1VMX5UmEJ8RhEw+EUEyI5C8aSQEUg 7AbXejl5R8bvE3+5VkRaL9dOKJeDR6NtMFlAMv8yHhb+DgAMxJOqovNygoPc3hqA 5i6/2KJf4ynJzbAhzLjTl4NT38GkUMaBICOhansELxvylrF/EoCRnh/5ONfjl74s 4IWwxfyh3m4j9huuQDSmMDgDWW2CqJuVTtqEhlFfZLkfntR/opf6ymc6WsVl516F 68nZxOKki1vtofCRwiGU =+H1P -----END PGP SIGNATURE----- _______________________________________________ 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 Jun 18 17:46:56 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 18 Jun 2014 17:46: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 1WxJwg-00033e-G9; Wed, 18 Jun 2014 17:46:50 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WxJwf-00033O-8x for mirageos-devel@lists.xenproject.org; Wed, 18 Jun 2014 17:46:49 +0000 Received: from [85.158.139.211:13884] by server-2.bemta-5.messagelabs.com id E7/45-01647-880D1A35; Wed, 18 Jun 2014 17:46:48 +0000 X-Env-Sender: scott.dj@gmail.com X-Msg-Ref: server-3.tower-206.messagelabs.com!1403113606!3122975!1 X-Originating-IP: [209.85.192.169] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25167 invoked from network); 18 Jun 2014 17:46:47 -0000 Received: from mail-pd0-f169.google.com (HELO mail-pd0-f169.google.com) (209.85.192.169) by server-3.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 18 Jun 2014 17:46:47 -0000 Received: by mail-pd0-f169.google.com with SMTP id g10so930739pdj.0 for ; Wed, 18 Jun 2014 10:46:45 -0700 (PDT) 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=rRM6Rj/V5X0SRpNNc8uQiaQZsKYIfn3Uq1yNW8kiHe4=; b=Uis8C8g0Ig+MIZWNZIYKBKk9m87N9Tv/wavi6xm3ZmS/izpfYb4ghKCyVl5mVZmi7S QlSHii6X5AaZzfCbTb1rJrFDaInS70uW0049e9l6p3tT9gAJ/O2rMZ03qJRQQHTJ9PWc PJUNxKRI7XzKBXMYswkYBVGY8gwZ3l9/Rg6oKSDMd7cYlJvRt2joGDbzE/gKVP9r+Jog ZxQyorVhKnQR5tGXhoRNUtX2YTlMUv1gV8VKn+HZD0aBeb0xWQhFPHfWOdGoWBhFpsfo Zt7bhEtWbvdV7V7Oip1bojJdLcXt0iVn7whItNq9caAHhinYWdXTehVDzLI7q6Rb43Xc /9wg== MIME-Version: 1.0 X-Received: by 10.68.189.68 with SMTP id gg4mr4440645pbc.42.1403113605574; Wed, 18 Jun 2014 10:46:45 -0700 (PDT) Received: by 10.70.11.65 with HTTP; Wed, 18 Jun 2014 10:46:45 -0700 (PDT) In-Reply-To: <1233494D-A05A-4F52-BFE7-9773BD566372@gazagnaire.org> References: <1233494D-A05A-4F52-BFE7-9773BD566372@gazagnaire.org> Date: Wed, 18 Jun 2014 18:46:45 +0100 Message-ID: From: David Scott To: Thomas Gazagnaire , Jon Ludlam Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] towards a common Mirage 'FLOW' signature X-BeenThere: mirageos-devel@lists.xenproject.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="===============6722129503585305388==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============6722129503585305388== Content-Type: multipart/alternative; boundary=e89a8ff1c4ec0a36d604fc1fd83e --e89a8ff1c4ec0a36d604fc1fd83e Content-Type: text/plain; charset=UTF-8 Quick update: mirage-types.1.1.3 has the FLOW signature (with the errors on write that Anil suggested). vchan.0.9.7 now exports FLOW rather than the old string-y extra-copying interface. Jon: to make this work with cohttp we're going to need some kind of FLOW -> cohttp adapter. More stuff to think about for v2: the 'shared-memory-ring' code exposes more detail. It's possible to 'read' data without acknowledging it, such that it'll still be there if you crash and restart. This is a bit like TCP retransmitting data you haven't ACKed. We could expose this somewhere. Also, each FLOW probably has some amount of buffering built-into it, for example vchan is limited by the size of the ring set at create time. Perhaps that could be exposed? If a particular FLOW implementation is prepared to allocate buffers it would be good to be able to control that, and apply back pressure etc. Perhaps we could draw some inspiration from somewhere-- JS core's pipes maybe? Cheers, Dave On Mon, Jun 16, 2014 at 10:33 AM, Thomas Gazagnaire wrote: > I'm a bit late in the discussion, but: > > > * consoles > > * xen inter-domain vchan connections > > * plain TCP > > * (hopefully) TLS connections > > For git, we also need in/out channels over the execution of an SSH program > execution (ssh git-fetch-pack ). I think your change will also > allow to do that so that's good :-) > > Thomas -- Dave Scott --e89a8ff1c4ec0a36d604fc1fd83e Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Quick update:

mirage-types.1.1.3 has th= e FLOW signature (with the errors on write that Anil suggested).
=
vchan.0.9.7 now exports FLOW rather than the old string-y ex= tra-copying interface. Jon: to make this work with cohttp we're going t= o need some kind of FLOW -> cohttp adapter.

More stuff to think about for v2: the 'shared-memor= y-ring' code exposes more detail. It's possible to 'read' d= ata without acknowledging it, such that it'll still be there if you cra= sh and restart. This is a bit like TCP retransmitting data you haven't = ACKed. We could expose this somewhere. Also, each FLOW probably has some am= ount of buffering built-into it, for example vchan is limited by the size o= f the ring set at create time. Perhaps that could be exposed? If a particul= ar FLOW implementation is prepared to allocate buffers it would be good to = be able to control that, and apply back pressure etc. Perhaps we could draw= some inspiration from somewhere-- JS core's pipes maybe?

Cheers,
Dave


On Mon, Jun 16, 2014 at 10:33 AM, = Thomas Gazagnaire <thomas@gazagnaire.org> wrote:
I'm a bit late in the discussion, but:

> * consoles
> * xen inter-domain vchan connections
> * plain TCP
> * (hopefully) TLS connections

For git, we also need in/out channels over the execution of an SSH pr= ogram execution (ssh <url> git-fetch-pack <args>). I think your= change will also allow to do that so that's good :-)

Thomas



--
Dave Scott
--e89a8ff1c4ec0a36d604fc1fd83e-- --===============6722129503585305388== 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 --===============6722129503585305388==-- From mirageos-devel-bounces@lists.xenproject.org Wed Jun 18 17:46:56 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 18 Jun 2014 17:46: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 1WxJwg-00033e-G9; Wed, 18 Jun 2014 17:46:50 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WxJwf-00033O-8x for mirageos-devel@lists.xenproject.org; Wed, 18 Jun 2014 17:46:49 +0000 Received: from [85.158.139.211:13884] by server-2.bemta-5.messagelabs.com id E7/45-01647-880D1A35; Wed, 18 Jun 2014 17:46:48 +0000 X-Env-Sender: scott.dj@gmail.com X-Msg-Ref: server-3.tower-206.messagelabs.com!1403113606!3122975!1 X-Originating-IP: [209.85.192.169] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25167 invoked from network); 18 Jun 2014 17:46:47 -0000 Received: from mail-pd0-f169.google.com (HELO mail-pd0-f169.google.com) (209.85.192.169) by server-3.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 18 Jun 2014 17:46:47 -0000 Received: by mail-pd0-f169.google.com with SMTP id g10so930739pdj.0 for ; Wed, 18 Jun 2014 10:46:45 -0700 (PDT) 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=rRM6Rj/V5X0SRpNNc8uQiaQZsKYIfn3Uq1yNW8kiHe4=; b=Uis8C8g0Ig+MIZWNZIYKBKk9m87N9Tv/wavi6xm3ZmS/izpfYb4ghKCyVl5mVZmi7S QlSHii6X5AaZzfCbTb1rJrFDaInS70uW0049e9l6p3tT9gAJ/O2rMZ03qJRQQHTJ9PWc PJUNxKRI7XzKBXMYswkYBVGY8gwZ3l9/Rg6oKSDMd7cYlJvRt2joGDbzE/gKVP9r+Jog ZxQyorVhKnQR5tGXhoRNUtX2YTlMUv1gV8VKn+HZD0aBeb0xWQhFPHfWOdGoWBhFpsfo Zt7bhEtWbvdV7V7Oip1bojJdLcXt0iVn7whItNq9caAHhinYWdXTehVDzLI7q6Rb43Xc /9wg== MIME-Version: 1.0 X-Received: by 10.68.189.68 with SMTP id gg4mr4440645pbc.42.1403113605574; Wed, 18 Jun 2014 10:46:45 -0700 (PDT) Received: by 10.70.11.65 with HTTP; Wed, 18 Jun 2014 10:46:45 -0700 (PDT) In-Reply-To: <1233494D-A05A-4F52-BFE7-9773BD566372@gazagnaire.org> References: <1233494D-A05A-4F52-BFE7-9773BD566372@gazagnaire.org> Date: Wed, 18 Jun 2014 18:46:45 +0100 Message-ID: From: David Scott To: Thomas Gazagnaire , Jon Ludlam Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] towards a common Mirage 'FLOW' signature X-BeenThere: mirageos-devel@lists.xenproject.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="===============6722129503585305388==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============6722129503585305388== Content-Type: multipart/alternative; boundary=e89a8ff1c4ec0a36d604fc1fd83e --e89a8ff1c4ec0a36d604fc1fd83e Content-Type: text/plain; charset=UTF-8 Quick update: mirage-types.1.1.3 has the FLOW signature (with the errors on write that Anil suggested). vchan.0.9.7 now exports FLOW rather than the old string-y extra-copying interface. Jon: to make this work with cohttp we're going to need some kind of FLOW -> cohttp adapter. More stuff to think about for v2: the 'shared-memory-ring' code exposes more detail. It's possible to 'read' data without acknowledging it, such that it'll still be there if you crash and restart. This is a bit like TCP retransmitting data you haven't ACKed. We could expose this somewhere. Also, each FLOW probably has some amount of buffering built-into it, for example vchan is limited by the size of the ring set at create time. Perhaps that could be exposed? If a particular FLOW implementation is prepared to allocate buffers it would be good to be able to control that, and apply back pressure etc. Perhaps we could draw some inspiration from somewhere-- JS core's pipes maybe? Cheers, Dave On Mon, Jun 16, 2014 at 10:33 AM, Thomas Gazagnaire wrote: > I'm a bit late in the discussion, but: > > > * consoles > > * xen inter-domain vchan connections > > * plain TCP > > * (hopefully) TLS connections > > For git, we also need in/out channels over the execution of an SSH program > execution (ssh git-fetch-pack ). I think your change will also > allow to do that so that's good :-) > > Thomas -- Dave Scott --e89a8ff1c4ec0a36d604fc1fd83e Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Quick update:

mirage-types.1.1.3 has th= e FLOW signature (with the errors on write that Anil suggested).
=
vchan.0.9.7 now exports FLOW rather than the old string-y ex= tra-copying interface. Jon: to make this work with cohttp we're going t= o need some kind of FLOW -> cohttp adapter.

More stuff to think about for v2: the 'shared-memor= y-ring' code exposes more detail. It's possible to 'read' d= ata without acknowledging it, such that it'll still be there if you cra= sh and restart. This is a bit like TCP retransmitting data you haven't = ACKed. We could expose this somewhere. Also, each FLOW probably has some am= ount of buffering built-into it, for example vchan is limited by the size o= f the ring set at create time. Perhaps that could be exposed? If a particul= ar FLOW implementation is prepared to allocate buffers it would be good to = be able to control that, and apply back pressure etc. Perhaps we could draw= some inspiration from somewhere-- JS core's pipes maybe?

Cheers,
Dave


On Mon, Jun 16, 2014 at 10:33 AM, = Thomas Gazagnaire <thomas@gazagnaire.org> wrote:
I'm a bit late in the discussion, but:

> * consoles
> * xen inter-domain vchan connections
> * plain TCP
> * (hopefully) TLS connections

For git, we also need in/out channels over the execution of an SSH pr= ogram execution (ssh <url> git-fetch-pack <args>). I think your= change will also allow to do that so that's good :-)

Thomas



--
Dave Scott
--e89a8ff1c4ec0a36d604fc1fd83e-- --===============6722129503585305388== 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 --===============6722129503585305388==-- From mirageos-devel-bounces@lists.xenproject.org Wed Jun 18 20:21:26 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 18 Jun 2014 20:21: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 1WxMME-00074o-I2; Wed, 18 Jun 2014 20:21:22 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WxMMD-00074e-VH for mirageos-devel@lists.xenproject.org; Wed, 18 Jun 2014 20:21:22 +0000 Received: from [85.158.137.68:50513] by server-1.bemta-3.messagelabs.com id 5F/EB-13056-1C4F1A35; Wed, 18 Jun 2014 20:21:21 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-15.tower-31.messagelabs.com!1403122880!10838582!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3870 invoked from network); 18 Jun 2014 20:21:20 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-15.tower-31.messagelabs.com with SMTP; 18 Jun 2014 20:21:20 -0000 Received: (qmail 28898 invoked by uid 634); 18 Jun 2014 20:21:19 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from cpc11-belf9-2-0-cust355.2-1.cable.virginm.net (HELO [10.0.1.15]) (86.24.61.100) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Wed, 18 Jun 2014 21:21:18 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\)) From: Anil Madhavapeddy In-Reply-To: Date: Wed, 18 Jun 2014 21:21:17 +0100 Message-Id: <2C06C3FC-F8F3-4FC4-A7F9-BCD1A2FADE94@recoil.org> References: <1233494D-A05A-4F52-BFE7-9773BD566372@gazagnaire.org> To: David Scott X-Mailer: Apple Mail (2.1874) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: Thomas Gazagnaire , Jon Ludlam , "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] towards a common Mirage 'FLOW' signature X-BeenThere: mirageos-devel@lists.xenproject.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 18 Jun 2014, at 18:46, David Scott wrote: > Quick update: > > mirage-types.1.1.3 has the FLOW signature (with the errors on write that Anil suggested). > > vchan.0.9.7 now exports FLOW rather than the old string-y extra-copying interface. Jon: to make this work with cohttp we're going to need some kind of FLOW -> cohttp adapter. I'm looking into that as part of my Conduit hacking (update on that as soon as it fits together again). > More stuff to think about for v2: the 'shared-memory-ring' code exposes more detail. It's possible to 'read' data without acknowledging it, such that it'll still be there if you crash and restart. This is a bit like TCP retransmitting data you haven't ACKed. We could expose this somewhere. Also, each FLOW probably has some amount of buffering built-into it, for example vchan is limited by the size of the ring set at create time. Perhaps that could be exposed? If a particular FLOW implementation is prepared to allocate buffers it would be good to be able to control that, and apply back pressure etc. Perhaps we could draw some inspiration from somewhere-- JS core's pipes maybe? Hm, the point of FLOWs is that they shouldn't have buffering, and that's in the CHANNEL type instead. Having said that, some buffering of in-flight requests is of course inescapable, and we could expose TCP buffers or the vchan ring size. What use would this information be to an application, though? If you noticed the recent DNS Io_page fix, I do like the model of allocating write-path buffers from the Flow itself. This would give a future vchan the option of allocating buffers directly into the shared ring, thus avoiding a copy. For most Flows like TCP, the memory allocator would just pass through to Io_page (but could also hook into a memory pool/logging library) -anil > > Cheers, > Dave > > > On Mon, Jun 16, 2014 at 10:33 AM, Thomas Gazagnaire wrote: > I'm a bit late in the discussion, but: > > > * consoles > > * xen inter-domain vchan connections > > * plain TCP > > * (hopefully) TLS connections > > For git, we also need in/out channels over the execution of an SSH program execution (ssh git-fetch-pack ). I think your change will also allow to do that so that's good :-) > > Thomas > > > > -- > Dave Scott > _______________________________________________ > 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 Wed Jun 18 20:21:26 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 18 Jun 2014 20:21: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 1WxMME-00074o-I2; Wed, 18 Jun 2014 20:21:22 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WxMMD-00074e-VH for mirageos-devel@lists.xenproject.org; Wed, 18 Jun 2014 20:21:22 +0000 Received: from [85.158.137.68:50513] by server-1.bemta-3.messagelabs.com id 5F/EB-13056-1C4F1A35; Wed, 18 Jun 2014 20:21:21 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-15.tower-31.messagelabs.com!1403122880!10838582!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3870 invoked from network); 18 Jun 2014 20:21:20 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-15.tower-31.messagelabs.com with SMTP; 18 Jun 2014 20:21:20 -0000 Received: (qmail 28898 invoked by uid 634); 18 Jun 2014 20:21:19 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from cpc11-belf9-2-0-cust355.2-1.cable.virginm.net (HELO [10.0.1.15]) (86.24.61.100) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Wed, 18 Jun 2014 21:21:18 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\)) From: Anil Madhavapeddy In-Reply-To: Date: Wed, 18 Jun 2014 21:21:17 +0100 Message-Id: <2C06C3FC-F8F3-4FC4-A7F9-BCD1A2FADE94@recoil.org> References: <1233494D-A05A-4F52-BFE7-9773BD566372@gazagnaire.org> To: David Scott X-Mailer: Apple Mail (2.1874) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: Thomas Gazagnaire , Jon Ludlam , "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] towards a common Mirage 'FLOW' signature X-BeenThere: mirageos-devel@lists.xenproject.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 18 Jun 2014, at 18:46, David Scott wrote: > Quick update: > > mirage-types.1.1.3 has the FLOW signature (with the errors on write that Anil suggested). > > vchan.0.9.7 now exports FLOW rather than the old string-y extra-copying interface. Jon: to make this work with cohttp we're going to need some kind of FLOW -> cohttp adapter. I'm looking into that as part of my Conduit hacking (update on that as soon as it fits together again). > More stuff to think about for v2: the 'shared-memory-ring' code exposes more detail. It's possible to 'read' data without acknowledging it, such that it'll still be there if you crash and restart. This is a bit like TCP retransmitting data you haven't ACKed. We could expose this somewhere. Also, each FLOW probably has some amount of buffering built-into it, for example vchan is limited by the size of the ring set at create time. Perhaps that could be exposed? If a particular FLOW implementation is prepared to allocate buffers it would be good to be able to control that, and apply back pressure etc. Perhaps we could draw some inspiration from somewhere-- JS core's pipes maybe? Hm, the point of FLOWs is that they shouldn't have buffering, and that's in the CHANNEL type instead. Having said that, some buffering of in-flight requests is of course inescapable, and we could expose TCP buffers or the vchan ring size. What use would this information be to an application, though? If you noticed the recent DNS Io_page fix, I do like the model of allocating write-path buffers from the Flow itself. This would give a future vchan the option of allocating buffers directly into the shared ring, thus avoiding a copy. For most Flows like TCP, the memory allocator would just pass through to Io_page (but could also hook into a memory pool/logging library) -anil > > Cheers, > Dave > > > On Mon, Jun 16, 2014 at 10:33 AM, Thomas Gazagnaire wrote: > I'm a bit late in the discussion, but: > > > * consoles > > * xen inter-domain vchan connections > > * plain TCP > > * (hopefully) TLS connections > > For git, we also need in/out channels over the execution of an SSH program execution (ssh git-fetch-pack ). I think your change will also allow to do that so that's good :-) > > Thomas > > > > -- > Dave Scott > _______________________________________________ > 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 Thu Jun 19 11:03:36 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 19 Jun 2014 11:03: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 1Wxa7u-00029C-Qw; Thu, 19 Jun 2014 11:03:30 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Wxa7t-00028y-GH for mirageos-devel@lists.xenproject.org; Thu, 19 Jun 2014 11:03:29 +0000 Received: from [85.158.139.211:30680] by server-4.bemta-5.messagelabs.com id 75/F4-07250-083C2A35; Thu, 19 Jun 2014 11:03:28 +0000 X-Env-Sender: talex5@gmail.com X-Msg-Ref: server-3.tower-206.messagelabs.com!1403175806!3261582!1 X-Originating-IP: [209.85.219.45] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, ML_RADAR_SPEW_LINKS_23,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12297 invoked from network); 19 Jun 2014 11:03:28 -0000 Received: from mail-oa0-f45.google.com (HELO mail-oa0-f45.google.com) (209.85.219.45) by server-3.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 19 Jun 2014 11:03:28 -0000 Received: by mail-oa0-f45.google.com with SMTP id o6so4763830oag.4 for ; Thu, 19 Jun 2014 04:03:26 -0700 (PDT) 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=jYYBBwjMO8xnZDBtNf/TMxPH5W8AFgbKUTDfqpJ+lEI=; b=CrnPFKCp94fCn9FlV3GctdDj7ZrzdJrORce5dITmcHqSjmOvFnoWcugHnZLhEe0VQM LqEg8ywbgFs5qJLEsYGsO1+CaDi1MXB6fzxraQo7PNwYjqg2t35SsjxVq8pza1tACo5K I5Cg0rsnE6yM5b/sN/Rv8nOMlCJF+Ump73U5z15acTiqh6UjB5pH+v9IzgHVG592pyqs aF/l4qSX0A+lAWeQ+oVOXTMJArPVq00A/6YXfAArOvwa3ufXmMFD5FFGenulEEJGrmbs qvuAnRVUYcmidva8s50fem0tpIfcSsctrwX6j2/fwR6X3oRCCEwAY5hDQaI/qZAI5Y8j JUMQ== MIME-Version: 1.0 X-Received: by 10.60.79.104 with SMTP id i8mr1901342oex.67.1403175806490; Thu, 19 Jun 2014 04:03:26 -0700 (PDT) Received: by 10.76.92.5 with HTTP; Thu, 19 Jun 2014 04:03:26 -0700 (PDT) In-Reply-To: <2E5AF614-DF84-4DBC-9EEC-C23BD7EF2144@recoil.org> References: <297FC9DB-3A4E-41A5-B00E-9DEF62C625E6@recoil.org> <12D67D67-3DAB-4033-BFC5-C7DBCBA64F34@recoil.org> <2E5AF614-DF84-4DBC-9EEC-C23BD7EF2144@recoil.org> Date: Thu, 19 Jun 2014 12:03:26 +0100 Message-ID: From: Thomas Leonard To: Anil Madhavapeddy Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Mirage on Xen/ARM status X-BeenThere: mirageos-devel@lists.xenproject.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 June 2014 17:23, Anil Madhavapeddy wrote: > On 16 Jun 2014, at 11:26, Thomas Leonard wrote: >>> >>>> A few random notes: >>>> >>>> - Lack of progress reports from mirage is a problem on x86, but it's >>>> worse on ARM because it's so much slower. >>> >>> Yes, this one has a bug open on mirage/mirage. We need to tee the output from the tool really. >> >> [ https://github.com/mirage/mirage/issues/205 ] > > This is addressed in the forthcoming Mirage 1.2.0 tool, with the pull req being tested in: > > https://github.com/mirage/mirage/pull/252 > > The main difference is that `mirage` no longer calls OPAM directly. It just generates a Makefile with a `make depend` target that does the honours, so it can be called explicitly. > > It also exports OPAMVERBOSE and OPAMYES from the Makefile, so it's easier to override it if quiet output is needed instead. > > I'll probably release Mirage 1.2.0 tomorrow with this change unless anyone finds an issue. I anticipate that the only fallout will be Travis scripts that need to have a "make depend" inserted somewhere. Thanks; that's much better! I've rebased the arm-preview branch onto this version. -- 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 Jun 19 11:03:36 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 19 Jun 2014 11:03: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 1Wxa7u-00029C-Qw; Thu, 19 Jun 2014 11:03:30 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Wxa7t-00028y-GH for mirageos-devel@lists.xenproject.org; Thu, 19 Jun 2014 11:03:29 +0000 Received: from [85.158.139.211:30680] by server-4.bemta-5.messagelabs.com id 75/F4-07250-083C2A35; Thu, 19 Jun 2014 11:03:28 +0000 X-Env-Sender: talex5@gmail.com X-Msg-Ref: server-3.tower-206.messagelabs.com!1403175806!3261582!1 X-Originating-IP: [209.85.219.45] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, ML_RADAR_SPEW_LINKS_23,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12297 invoked from network); 19 Jun 2014 11:03:28 -0000 Received: from mail-oa0-f45.google.com (HELO mail-oa0-f45.google.com) (209.85.219.45) by server-3.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 19 Jun 2014 11:03:28 -0000 Received: by mail-oa0-f45.google.com with SMTP id o6so4763830oag.4 for ; Thu, 19 Jun 2014 04:03:26 -0700 (PDT) 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=jYYBBwjMO8xnZDBtNf/TMxPH5W8AFgbKUTDfqpJ+lEI=; b=CrnPFKCp94fCn9FlV3GctdDj7ZrzdJrORce5dITmcHqSjmOvFnoWcugHnZLhEe0VQM LqEg8ywbgFs5qJLEsYGsO1+CaDi1MXB6fzxraQo7PNwYjqg2t35SsjxVq8pza1tACo5K I5Cg0rsnE6yM5b/sN/Rv8nOMlCJF+Ump73U5z15acTiqh6UjB5pH+v9IzgHVG592pyqs aF/l4qSX0A+lAWeQ+oVOXTMJArPVq00A/6YXfAArOvwa3ufXmMFD5FFGenulEEJGrmbs qvuAnRVUYcmidva8s50fem0tpIfcSsctrwX6j2/fwR6X3oRCCEwAY5hDQaI/qZAI5Y8j JUMQ== MIME-Version: 1.0 X-Received: by 10.60.79.104 with SMTP id i8mr1901342oex.67.1403175806490; Thu, 19 Jun 2014 04:03:26 -0700 (PDT) Received: by 10.76.92.5 with HTTP; Thu, 19 Jun 2014 04:03:26 -0700 (PDT) In-Reply-To: <2E5AF614-DF84-4DBC-9EEC-C23BD7EF2144@recoil.org> References: <297FC9DB-3A4E-41A5-B00E-9DEF62C625E6@recoil.org> <12D67D67-3DAB-4033-BFC5-C7DBCBA64F34@recoil.org> <2E5AF614-DF84-4DBC-9EEC-C23BD7EF2144@recoil.org> Date: Thu, 19 Jun 2014 12:03:26 +0100 Message-ID: From: Thomas Leonard To: Anil Madhavapeddy Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Mirage on Xen/ARM status X-BeenThere: mirageos-devel@lists.xenproject.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 June 2014 17:23, Anil Madhavapeddy wrote: > On 16 Jun 2014, at 11:26, Thomas Leonard wrote: >>> >>>> A few random notes: >>>> >>>> - Lack of progress reports from mirage is a problem on x86, but it's >>>> worse on ARM because it's so much slower. >>> >>> Yes, this one has a bug open on mirage/mirage. We need to tee the output from the tool really. >> >> [ https://github.com/mirage/mirage/issues/205 ] > > This is addressed in the forthcoming Mirage 1.2.0 tool, with the pull req being tested in: > > https://github.com/mirage/mirage/pull/252 > > The main difference is that `mirage` no longer calls OPAM directly. It just generates a Makefile with a `make depend` target that does the honours, so it can be called explicitly. > > It also exports OPAMVERBOSE and OPAMYES from the Makefile, so it's easier to override it if quiet output is needed instead. > > I'll probably release Mirage 1.2.0 tomorrow with this change unless anyone finds an issue. I anticipate that the only fallout will be Travis scripts that need to have a "make depend" inserted somewhere. Thanks; that's much better! I've rebased the arm-preview branch onto this version. -- 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 Jun 19 11:24:16 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 19 Jun 2014 11:24: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 1WxaRz-00048h-16; Thu, 19 Jun 2014 11:24:15 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WxaRx-00048c-Tv for mirageos-devel@lists.xenproject.org; Thu, 19 Jun 2014 11:24:14 +0000 Received: from [193.109.254.147:46362] by server-12.bemta-14.messagelabs.com id 90/21-32179-D58C2A35; Thu, 19 Jun 2014 11:24:13 +0000 X-Env-Sender: talex5@gmail.com X-Msg-Ref: server-4.tower-27.messagelabs.com!1403177051!12358097!1 X-Originating-IP: [209.85.219.45] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, ML_RADAR_SPEW_LINKS_23,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5981 invoked from network); 19 Jun 2014 11:24:12 -0000 Received: from mail-oa0-f45.google.com (HELO mail-oa0-f45.google.com) (209.85.219.45) by server-4.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 19 Jun 2014 11:24:12 -0000 Received: by mail-oa0-f45.google.com with SMTP id o6so4858866oag.32 for ; Thu, 19 Jun 2014 04:24:11 -0700 (PDT) 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=1KFp9YbC7ztfHSX0NuplFyOZfV7X6WDo3qYkx+Ugkzw=; b=WdkcWzbRYNt7Furf0Al9oEsplkkpCS9V9OPgjvG+iVt4F7eoYC021/tZjFRTMZj5Xo Z1sIcV5XT9dfyqkgLgJ7QEAUjQx8YfKPkjlS34ba+gCMTOnRzsejRDxeVbhkhyKifnBa psoK/oUNYJKRClnk0WV4/etYSr3OPCnitpufg+XmY8YWn2IbgirT4MH2yRhd4fZ2I8pD gRe+mj4qfBZh6hLqKTOz6QsJN/pg/11c7EmXpjpze5AX/mBuMz+kGkCeG2ZxzktLth7U to64Ug+g8c39Y+ia8K04gn9vRNApg/4jBvW7yKJmEyTTe/hDU6kA2fX7LlIEo9qnyc/7 yvdg== MIME-Version: 1.0 X-Received: by 10.60.79.104 with SMTP id i8mr2011530oex.67.1403177050874; Thu, 19 Jun 2014 04:24:10 -0700 (PDT) Received: by 10.76.92.5 with HTTP; Thu, 19 Jun 2014 04:24:10 -0700 (PDT) In-Reply-To: <5EC38C5B-9566-45FE-B37F-CD3FB1AC9F03@recoil.org> References: <297FC9DB-3A4E-41A5-B00E-9DEF62C625E6@recoil.org> <39391660-83A7-46C0-AE53-3880A5A7A885@recoil.org> <5EC38C5B-9566-45FE-B37F-CD3FB1AC9F03@recoil.org> Date: Thu, 19 Jun 2014 12:24:10 +0100 Message-ID: From: Thomas Leonard To: Anil Madhavapeddy Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Mirage on Xen/ARM status X-BeenThere: mirageos-devel@lists.xenproject.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 13 June 2014 10:21, Anil Madhavapeddy wrote: > On 13 Jun 2014, at 10:15, Thomas Leonard wrote: > >> On 13 June 2014 10:09, Anil Madhavapeddy wrote: >>> On 12 Jun 2014, at 15:46, Thomas Leonard wrote: >>>>> >>>>> The next step is to get networking working on ARM. >>>> >>>> This seems to be working now (I can telnet to port 80 and send it a >>>> message), which it displays on the console. >>> >>> Fantastic!! >>> >>>> The main problem turned out to be ones_complement_checksum_bigarray, >>>> which was doing unaligned double-word (64-bit) memory access. This >>>> faults on ARM. For testing, I replaced it with the version in the unix >>>> directory. >>> >>> Interesting -- they were meant to be exactly the same if I remember. >>> Is there an actual code difference between the two aside from include >>> headers? >> >> They are very different. Looks like one got optimised without the other here: >> >> https://github.com/mirage/mirage-platform/commit/6fc97d77d0846bc7f17bd0702832ea1faa8a7e71 >> > > Ah yes, istr the reasoning behind this was that the Unix one would never > be used in a high-performance context, so portability was more useful than > performance. > > Still, being able to unify these is very desirable, as being able to test > the stack independently of Xen (and expecting similar behavioural characteristics) > is extremely important. Perhaps the ones complement stuff should be moved out of mirage-platform anyway? It seems to be specific to networking, rather than to any particular platform. I see there's also a third version in the ns3 directory, which always returns zero. -- 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 Jun 19 11:24:16 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 19 Jun 2014 11:24: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 1WxaRz-00048h-16; Thu, 19 Jun 2014 11:24:15 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WxaRx-00048c-Tv for mirageos-devel@lists.xenproject.org; Thu, 19 Jun 2014 11:24:14 +0000 Received: from [193.109.254.147:46362] by server-12.bemta-14.messagelabs.com id 90/21-32179-D58C2A35; Thu, 19 Jun 2014 11:24:13 +0000 X-Env-Sender: talex5@gmail.com X-Msg-Ref: server-4.tower-27.messagelabs.com!1403177051!12358097!1 X-Originating-IP: [209.85.219.45] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, ML_RADAR_SPEW_LINKS_23,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5981 invoked from network); 19 Jun 2014 11:24:12 -0000 Received: from mail-oa0-f45.google.com (HELO mail-oa0-f45.google.com) (209.85.219.45) by server-4.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 19 Jun 2014 11:24:12 -0000 Received: by mail-oa0-f45.google.com with SMTP id o6so4858866oag.32 for ; Thu, 19 Jun 2014 04:24:11 -0700 (PDT) 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=1KFp9YbC7ztfHSX0NuplFyOZfV7X6WDo3qYkx+Ugkzw=; b=WdkcWzbRYNt7Furf0Al9oEsplkkpCS9V9OPgjvG+iVt4F7eoYC021/tZjFRTMZj5Xo Z1sIcV5XT9dfyqkgLgJ7QEAUjQx8YfKPkjlS34ba+gCMTOnRzsejRDxeVbhkhyKifnBa psoK/oUNYJKRClnk0WV4/etYSr3OPCnitpufg+XmY8YWn2IbgirT4MH2yRhd4fZ2I8pD gRe+mj4qfBZh6hLqKTOz6QsJN/pg/11c7EmXpjpze5AX/mBuMz+kGkCeG2ZxzktLth7U to64Ug+g8c39Y+ia8K04gn9vRNApg/4jBvW7yKJmEyTTe/hDU6kA2fX7LlIEo9qnyc/7 yvdg== MIME-Version: 1.0 X-Received: by 10.60.79.104 with SMTP id i8mr2011530oex.67.1403177050874; Thu, 19 Jun 2014 04:24:10 -0700 (PDT) Received: by 10.76.92.5 with HTTP; Thu, 19 Jun 2014 04:24:10 -0700 (PDT) In-Reply-To: <5EC38C5B-9566-45FE-B37F-CD3FB1AC9F03@recoil.org> References: <297FC9DB-3A4E-41A5-B00E-9DEF62C625E6@recoil.org> <39391660-83A7-46C0-AE53-3880A5A7A885@recoil.org> <5EC38C5B-9566-45FE-B37F-CD3FB1AC9F03@recoil.org> Date: Thu, 19 Jun 2014 12:24:10 +0100 Message-ID: From: Thomas Leonard To: Anil Madhavapeddy Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Mirage on Xen/ARM status X-BeenThere: mirageos-devel@lists.xenproject.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 13 June 2014 10:21, Anil Madhavapeddy wrote: > On 13 Jun 2014, at 10:15, Thomas Leonard wrote: > >> On 13 June 2014 10:09, Anil Madhavapeddy wrote: >>> On 12 Jun 2014, at 15:46, Thomas Leonard wrote: >>>>> >>>>> The next step is to get networking working on ARM. >>>> >>>> This seems to be working now (I can telnet to port 80 and send it a >>>> message), which it displays on the console. >>> >>> Fantastic!! >>> >>>> The main problem turned out to be ones_complement_checksum_bigarray, >>>> which was doing unaligned double-word (64-bit) memory access. This >>>> faults on ARM. For testing, I replaced it with the version in the unix >>>> directory. >>> >>> Interesting -- they were meant to be exactly the same if I remember. >>> Is there an actual code difference between the two aside from include >>> headers? >> >> They are very different. Looks like one got optimised without the other here: >> >> https://github.com/mirage/mirage-platform/commit/6fc97d77d0846bc7f17bd0702832ea1faa8a7e71 >> > > Ah yes, istr the reasoning behind this was that the Unix one would never > be used in a high-performance context, so portability was more useful than > performance. > > Still, being able to unify these is very desirable, as being able to test > the stack independently of Xen (and expecting similar behavioural characteristics) > is extremely important. Perhaps the ones complement stuff should be moved out of mirage-platform anyway? It seems to be specific to networking, rather than to any particular platform. I see there's also a third version in the ns3 directory, which always returns zero. -- 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 Jun 19 13:36:31 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 19 Jun 2014 13:36: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 1WxcVv-0007R3-HA; Thu, 19 Jun 2014 13:36:27 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WxcVu-0007Qp-Ab for mirageos-devel@lists.xenproject.org; Thu, 19 Jun 2014 13:36:26 +0000 Received: from [193.109.254.147:29460] by server-13.bemta-14.messagelabs.com id 5C/FD-23211-957E2A35; Thu, 19 Jun 2014 13:36:25 +0000 X-Env-Sender: Richard.Mortier@nottingham.ac.uk X-Msg-Ref: server-10.tower-27.messagelabs.com!1403184984!12383963!1 X-Originating-IP: [151.236.209.33] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 24629 invoked from network); 19 Jun 2014 13:36:24 -0000 Received: from engine01-20433-7.icritical.com (HELO engine01-20433-7.icritical.com) (151.236.209.33) by server-10.tower-27.messagelabs.com with SMTP; 19 Jun 2014 13:36:24 -0000 Received: (qmail 6173 invoked from network); 19 Jun 2014 13:36:18 -0000 Received: from localhost (127.0.0.1) by engine01-20433-7.icritical.com with SMTP; 19 Jun 2014 13:36:18 -0000 Received: from engine01-20433-7.icritical.com ([127.0.0.1]) by localhost (engine01-20433-7.icritical.com [127.0.0.1]) (amavisd-new, port 10024) with SMTP id 05714-07 for ; Thu, 19 Jun 2014 14:36:11 +0100 (BST) Received: (qmail 5926 invoked by uid 599); 19 Jun 2014 13:36:06 -0000 Received: from unknown (HELO smtp4.nottingham.ac.uk) (128.243.220.65) by engine01-20433-7.icritical.com (qpsmtpd/0.28) with ESMTP; Thu, 19 Jun 2014 14:36:06 +0100 Received: from uiwexhub02.ad.nottingham.ac.uk ([128.243.15.132]) by smtp4.nottingham.ac.uk with esmtps (TLSv1:AES128-SHA:128) (Exim 4.77) (envelope-from ) id 1WxcVd-00027z-Qz; Thu, 19 Jun 2014 14:36:09 +0100 From: Richard Mortier To: Thomas Leonard Date: Thu, 19 Jun 2014 14:36:08 +0100 Thread-Topic: [MirageOS-devel] Mirage on Xen/ARM status Thread-Index: Ac+Lw22/sWEWSXzsSg6Oba6pCKN1nw== Message-ID: <95F32191-BEBA-43A5-A204-3F9334BFD166@nottingham.ac.uk> References: <297FC9DB-3A4E-41A5-B00E-9DEF62C625E6@recoil.org> <39391660-83A7-46C0-AE53-3880A5A7A885@recoil.org> <5EC38C5B-9566-45FE-B37F-CD3FB1AC9F03@recoil.org> In-Reply-To: Accept-Language: en-US, en-GB Content-Language: en-US X-MS-Has-Attach: yes X-MS-TNEF-Correlator: acceptlanguage: en-US, en-GB MIME-Version: 1.0 X-Virus-Scanned: by iCritical at engine01-20433-7.icritical.com Cc: "mirageos-devel@lists.xenproject.org" , Anil Madhavapeddy Subject: Re: [MirageOS-devel] Mirage on Xen/ARM status X-BeenThere: mirageos-devel@lists.xenproject.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="===============3268031120986157386==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============3268031120986157386== Content-Language: en-US Content-Type: multipart/signed; boundary="Apple-Mail=_DAAC2C26-0256-4BBA-B4F1-C6F354B2F6BC"; protocol="application/pgp-signature"; micalg=pgp-sha512 --Apple-Mail=_DAAC2C26-0256-4BBA-B4F1-C6F354B2F6BC Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On 19 Jun 2014, at 12:24, Thomas Leonard wrote: > Perhaps the ones complement stuff should be moved out of > mirage-platform anyway? It seems to be specific to networking, rather > than to any particular platform. I see there's also a third version in > the ns3 directory, which always returns zero. yes; ones complement checksums are used in several IP protocols. i don't = know that they're used elsewhere (storage, etc). i guess efficient = implementations are likely to be platform specific, though perhaps one = would expect the compiler to dtrt rather than hand tweaking. --=20 Cheers, R. --Apple-Mail=_DAAC2C26-0256-4BBA-B4F1-C6F354B2F6BC Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="signature.asc" Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJToudIAAoJEOLF27JWwSg3OrQQAI7dz8EDMlYVnCPReleC0uuH fPbqi/b+se6RBILr1JhS5TV5fpuW9r4Y+/0ok+Lgf4PhuWebwUaX02wdVgwellta chva8e52v6/QPa2GBT/M9SKy7HV/Ss1C5niBb9fzpmWkfzuYbp5gNAXZNXMAPE9l t0EqHthSIeRXu+omd5x/kyKDDqd0VacvqVBGGQDbGIh27nFts2xBDXWOK3/tUZ3d jEcJm2hlpnKcWLZceETphVB4y4qapOX/BXc/opVdC4cTImyrEmYdoaNop5qLXeZa /EtoUM2xXrVydNWDstU5kaQZ04s0SBRbXbg/XtJ2KLiRdOQPkdzj2UEqrBmbHhYw Ce39bSPQiT+W6gkeQFjYgUwa32vVuqRtZVGs9oM6UEfgXP/UpRmlsAjOO3lqMYbB LbyaU9RPEfytw7xNBj1/tAzT8jrOhNBglO/64npwqb7NBjeQw7Jh5KV9pONedmSR 17MEo2fFtx7C+eJ+EYrEnuze7l16fBG+BSgjI24f82CDGsFZ9HDjsU8t7DMn5xr/ MbWNVmC7ZHUJ5iG5+smkko5w+g0+kHIitfOVByRloCqp4XOv07bqbpST4cnavUpu YTVrIU4yj5RMtsyHXZxs16/cCBp3SZecWG7L49Rw7sjNneqv3w/IJx26IpPjIH+g F2cqLWj9zQn8n22QeyYl =vl2D -----END PGP SIGNATURE----- --Apple-Mail=_DAAC2C26-0256-4BBA-B4F1-C6F354B2F6BC-- --===============3268031120986157386== 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 --===============3268031120986157386==-- From mirageos-devel-bounces@lists.xenproject.org Thu Jun 19 13:36:31 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 19 Jun 2014 13:36: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 1WxcVv-0007R3-HA; Thu, 19 Jun 2014 13:36:27 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WxcVu-0007Qp-Ab for mirageos-devel@lists.xenproject.org; Thu, 19 Jun 2014 13:36:26 +0000 Received: from [193.109.254.147:29460] by server-13.bemta-14.messagelabs.com id 5C/FD-23211-957E2A35; Thu, 19 Jun 2014 13:36:25 +0000 X-Env-Sender: Richard.Mortier@nottingham.ac.uk X-Msg-Ref: server-10.tower-27.messagelabs.com!1403184984!12383963!1 X-Originating-IP: [151.236.209.33] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 24629 invoked from network); 19 Jun 2014 13:36:24 -0000 Received: from engine01-20433-7.icritical.com (HELO engine01-20433-7.icritical.com) (151.236.209.33) by server-10.tower-27.messagelabs.com with SMTP; 19 Jun 2014 13:36:24 -0000 Received: (qmail 6173 invoked from network); 19 Jun 2014 13:36:18 -0000 Received: from localhost (127.0.0.1) by engine01-20433-7.icritical.com with SMTP; 19 Jun 2014 13:36:18 -0000 Received: from engine01-20433-7.icritical.com ([127.0.0.1]) by localhost (engine01-20433-7.icritical.com [127.0.0.1]) (amavisd-new, port 10024) with SMTP id 05714-07 for ; Thu, 19 Jun 2014 14:36:11 +0100 (BST) Received: (qmail 5926 invoked by uid 599); 19 Jun 2014 13:36:06 -0000 Received: from unknown (HELO smtp4.nottingham.ac.uk) (128.243.220.65) by engine01-20433-7.icritical.com (qpsmtpd/0.28) with ESMTP; Thu, 19 Jun 2014 14:36:06 +0100 Received: from uiwexhub02.ad.nottingham.ac.uk ([128.243.15.132]) by smtp4.nottingham.ac.uk with esmtps (TLSv1:AES128-SHA:128) (Exim 4.77) (envelope-from ) id 1WxcVd-00027z-Qz; Thu, 19 Jun 2014 14:36:09 +0100 From: Richard Mortier To: Thomas Leonard Date: Thu, 19 Jun 2014 14:36:08 +0100 Thread-Topic: [MirageOS-devel] Mirage on Xen/ARM status Thread-Index: Ac+Lw22/sWEWSXzsSg6Oba6pCKN1nw== Message-ID: <95F32191-BEBA-43A5-A204-3F9334BFD166@nottingham.ac.uk> References: <297FC9DB-3A4E-41A5-B00E-9DEF62C625E6@recoil.org> <39391660-83A7-46C0-AE53-3880A5A7A885@recoil.org> <5EC38C5B-9566-45FE-B37F-CD3FB1AC9F03@recoil.org> In-Reply-To: Accept-Language: en-US, en-GB Content-Language: en-US X-MS-Has-Attach: yes X-MS-TNEF-Correlator: acceptlanguage: en-US, en-GB MIME-Version: 1.0 X-Virus-Scanned: by iCritical at engine01-20433-7.icritical.com Cc: "mirageos-devel@lists.xenproject.org" , Anil Madhavapeddy Subject: Re: [MirageOS-devel] Mirage on Xen/ARM status X-BeenThere: mirageos-devel@lists.xenproject.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="===============3268031120986157386==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============3268031120986157386== Content-Language: en-US Content-Type: multipart/signed; boundary="Apple-Mail=_DAAC2C26-0256-4BBA-B4F1-C6F354B2F6BC"; protocol="application/pgp-signature"; micalg=pgp-sha512 --Apple-Mail=_DAAC2C26-0256-4BBA-B4F1-C6F354B2F6BC Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On 19 Jun 2014, at 12:24, Thomas Leonard wrote: > Perhaps the ones complement stuff should be moved out of > mirage-platform anyway? It seems to be specific to networking, rather > than to any particular platform. I see there's also a third version in > the ns3 directory, which always returns zero. yes; ones complement checksums are used in several IP protocols. i don't = know that they're used elsewhere (storage, etc). i guess efficient = implementations are likely to be platform specific, though perhaps one = would expect the compiler to dtrt rather than hand tweaking. --=20 Cheers, R. --Apple-Mail=_DAAC2C26-0256-4BBA-B4F1-C6F354B2F6BC Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="signature.asc" Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJToudIAAoJEOLF27JWwSg3OrQQAI7dz8EDMlYVnCPReleC0uuH fPbqi/b+se6RBILr1JhS5TV5fpuW9r4Y+/0ok+Lgf4PhuWebwUaX02wdVgwellta chva8e52v6/QPa2GBT/M9SKy7HV/Ss1C5niBb9fzpmWkfzuYbp5gNAXZNXMAPE9l t0EqHthSIeRXu+omd5x/kyKDDqd0VacvqVBGGQDbGIh27nFts2xBDXWOK3/tUZ3d jEcJm2hlpnKcWLZceETphVB4y4qapOX/BXc/opVdC4cTImyrEmYdoaNop5qLXeZa /EtoUM2xXrVydNWDstU5kaQZ04s0SBRbXbg/XtJ2KLiRdOQPkdzj2UEqrBmbHhYw Ce39bSPQiT+W6gkeQFjYgUwa32vVuqRtZVGs9oM6UEfgXP/UpRmlsAjOO3lqMYbB LbyaU9RPEfytw7xNBj1/tAzT8jrOhNBglO/64npwqb7NBjeQw7Jh5KV9pONedmSR 17MEo2fFtx7C+eJ+EYrEnuze7l16fBG+BSgjI24f82CDGsFZ9HDjsU8t7DMn5xr/ MbWNVmC7ZHUJ5iG5+smkko5w+g0+kHIitfOVByRloCqp4XOv07bqbpST4cnavUpu YTVrIU4yj5RMtsyHXZxs16/cCBp3SZecWG7L49Rw7sjNneqv3w/IJx26IpPjIH+g F2cqLWj9zQn8n22QeyYl =vl2D -----END PGP SIGNATURE----- --Apple-Mail=_DAAC2C26-0256-4BBA-B4F1-C6F354B2F6BC-- --===============3268031120986157386== 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 --===============3268031120986157386==-- From mirageos-devel-bounces@lists.xenproject.org Thu Jun 19 13:55:36 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 19 Jun 2014 13:55: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 1WxcoQ-0007gR-8N; Thu, 19 Jun 2014 13:55:34 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WxcoP-0007gK-P3 for mirageos-devel@lists.xenproject.org; Thu, 19 Jun 2014 13:55:33 +0000 Received: from [85.158.139.211:55138] by server-1.bemta-5.messagelabs.com id D3/15-30932-5DBE2A35; Thu, 19 Jun 2014 13:55:33 +0000 X-Env-Sender: Richard.Mortier@nottingham.ac.uk X-Msg-Ref: server-12.tower-206.messagelabs.com!1403186132!10885631!1 X-Originating-IP: [93.95.15.169] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 24003 invoked from network); 19 Jun 2014 13:55:32 -0000 Received: from engine01-20433-1.icritical.com (HELO engine01-20433-1.icritical.com) (93.95.15.169) by server-12.tower-206.messagelabs.com with SMTP; 19 Jun 2014 13:55:32 -0000 Received: (qmail 20862 invoked from network); 19 Jun 2014 13:55:47 -0000 Received: from localhost (127.0.0.1) by engine01-20433-1.icritical.com with SMTP; 19 Jun 2014 13:55:47 -0000 Received: from engine01-20433-1.icritical.com ([127.0.0.1]) by localhost (engine01-20433-1.icritical.com [127.0.0.1]) (amavisd-new, port 10024) with SMTP id 20481-10 for ; Thu, 19 Jun 2014 14:55:39 +0100 (BST) Received: (qmail 16420 invoked by uid 599); 19 Jun 2014 13:48:52 -0000 Received: from unknown (HELO smtp4.nottingham.ac.uk) (128.243.220.65) by engine01-20433-1.icritical.com (qpsmtpd/0.28) with ESMTP; Thu, 19 Jun 2014 14:48:52 +0100 Received: from uiwexhub02.ad.nottingham.ac.uk ([128.243.15.132]) by smtp4.nottingham.ac.uk with esmtps (TLSv1:AES128-SHA:128) (Exim 4.77) (envelope-from ) id 1Wxchf-0002oS-6z; Thu, 19 Jun 2014 14:48:35 +0100 From: Richard Mortier To: Anil Madhavapeddy Date: Thu, 19 Jun 2014 14:48:34 +0100 Thread-Topic: [MirageOS-devel] outgoing tcp connections Thread-Index: Ac+LxSoljleYtFjnTaSFsLH6AV5Q+Q== Message-ID: <5D4CD114-4F9F-4912-BE65-14F91C5322F1@nottingham.ac.uk> References: <13D72486-0766-49EA-AE2B-ED8ADE5CE3EF@recoil.org> <53A189FC.7020804@mehnert.org> <42BBD403-02AA-4C26-AD1E-4D923622F9AF@recoil.org> In-Reply-To: <42BBD403-02AA-4C26-AD1E-4D923622F9AF@recoil.org> Accept-Language: en-US, en-GB Content-Language: en-US X-MS-Has-Attach: yes X-MS-TNEF-Correlator: acceptlanguage: en-US, en-GB MIME-Version: 1.0 X-Virus-Scanned: by iCritical at engine01-20433-1.icritical.com Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] outgoing tcp connections X-BeenThere: mirageos-devel@lists.xenproject.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="===============4947526046940383793==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============4947526046940383793== Content-Language: en-US Content-Type: multipart/signed; boundary="Apple-Mail=_C72387DD-6DF4-4CB4-9FF9-DCE7971D55B7"; protocol="application/pgp-signature"; micalg=pgp-sha512 --Apple-Mail=_C72387DD-6DF4-4CB4-9FF9-DCE7971D55B7 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii On 18 Jun 2014, at 13:51, Anil Madhavapeddy wrote: >> Another (related) issue is when using tap and no dhcp, I've to be fast >> between executing the client and assigning a IP address in the >> hostsystem for tap0 (whenever an application is started, the host >> system IP gets removed) in order to reply to ARP to the mirage stack. > > Hrm yes, doing bridge setup is something I'm not keen on putting > into our tools. Ideally, we would use persistent tunnels that could > be set up by external tools and then attached to by the Unix unikernel. what was the rationale for not doing this again? > However, there is a light on this horizon, as I > discovered that MacOS X 10.10-beta has the vmnet framework installed > by default, which finally gives us bridging support there without needing > the installing of OSXtuntap. I'll write bindings when I get a chance... sweet :) -- Cheers, R. --Apple-Mail=_C72387DD-6DF4-4CB4-9FF9-DCE7971D55B7 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="signature.asc" Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJTotHQAAoJEOLF27JWwSg3k64P/R68gP6M9ccLq3ZQuoLQ8P8Y Ay3txt169aMO96SRCsl2SEQv09icNIdIS0Ho91MDdyBYVSI916dzEXA7sRFPSIwC HdxS60DwIgDXoJpt1pjMqG5Lf9bKGlnyEdr1FUjqtEVoikLL1aPECThw0rj+TTXs G2DNCZJxUh5ANGTGqV7fnUr+HgMqrHG0a9jm3thwkUhF6u4ajwhn6oRnKKSRDqmw xJKViSeQID07hXyK5FU60JUNQmlmT5CWqTUfEJ40AIDmzC+ruQ4yGcBPhyPohmD1 ksMBISqoZvdtQgSIiAYGems8C6LBNM0skmt5+lv4w/RXJwMFPoNNK0nhxmv3do91 8F4+56PzTFogVFt2drvbqLdASFgNx6aIAOheVrKTy8x/mIP+iVM30elAg1BiN6sY PaGGsRMwA6g/2n7kjcOHeHq9pJc0g8U9SRc0Ijgnm9xgL2VpI6QFEmEGxUDicoVm kjPrFB7UOqTGLZXvZ7Z67elv8wXmJGW6ddk18/mTnC3TqDbzxHSszaXJkTT12Ot2 qdVRPiwjo165kJYO3JvVV3cEqhubhJU8ANETlotdaMmCsQ215Zixi2wjVKIgfyrj 87rLzVe410OGy7LDVEyf2qshxThwLeclPicWRNsuypC/7fEfU3GXXu3CoGbmFSfQ PgqpjWDTlM7p4F7wWQiH =VnkD -----END PGP SIGNATURE----- --Apple-Mail=_C72387DD-6DF4-4CB4-9FF9-DCE7971D55B7-- --===============4947526046940383793== 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 --===============4947526046940383793==-- From mirageos-devel-bounces@lists.xenproject.org Thu Jun 19 13:55:36 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 19 Jun 2014 13:55: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 1WxcoQ-0007gR-8N; Thu, 19 Jun 2014 13:55:34 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WxcoP-0007gK-P3 for mirageos-devel@lists.xenproject.org; Thu, 19 Jun 2014 13:55:33 +0000 Received: from [85.158.139.211:55138] by server-1.bemta-5.messagelabs.com id D3/15-30932-5DBE2A35; Thu, 19 Jun 2014 13:55:33 +0000 X-Env-Sender: Richard.Mortier@nottingham.ac.uk X-Msg-Ref: server-12.tower-206.messagelabs.com!1403186132!10885631!1 X-Originating-IP: [93.95.15.169] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 24003 invoked from network); 19 Jun 2014 13:55:32 -0000 Received: from engine01-20433-1.icritical.com (HELO engine01-20433-1.icritical.com) (93.95.15.169) by server-12.tower-206.messagelabs.com with SMTP; 19 Jun 2014 13:55:32 -0000 Received: (qmail 20862 invoked from network); 19 Jun 2014 13:55:47 -0000 Received: from localhost (127.0.0.1) by engine01-20433-1.icritical.com with SMTP; 19 Jun 2014 13:55:47 -0000 Received: from engine01-20433-1.icritical.com ([127.0.0.1]) by localhost (engine01-20433-1.icritical.com [127.0.0.1]) (amavisd-new, port 10024) with SMTP id 20481-10 for ; Thu, 19 Jun 2014 14:55:39 +0100 (BST) Received: (qmail 16420 invoked by uid 599); 19 Jun 2014 13:48:52 -0000 Received: from unknown (HELO smtp4.nottingham.ac.uk) (128.243.220.65) by engine01-20433-1.icritical.com (qpsmtpd/0.28) with ESMTP; Thu, 19 Jun 2014 14:48:52 +0100 Received: from uiwexhub02.ad.nottingham.ac.uk ([128.243.15.132]) by smtp4.nottingham.ac.uk with esmtps (TLSv1:AES128-SHA:128) (Exim 4.77) (envelope-from ) id 1Wxchf-0002oS-6z; Thu, 19 Jun 2014 14:48:35 +0100 From: Richard Mortier To: Anil Madhavapeddy Date: Thu, 19 Jun 2014 14:48:34 +0100 Thread-Topic: [MirageOS-devel] outgoing tcp connections Thread-Index: Ac+LxSoljleYtFjnTaSFsLH6AV5Q+Q== Message-ID: <5D4CD114-4F9F-4912-BE65-14F91C5322F1@nottingham.ac.uk> References: <13D72486-0766-49EA-AE2B-ED8ADE5CE3EF@recoil.org> <53A189FC.7020804@mehnert.org> <42BBD403-02AA-4C26-AD1E-4D923622F9AF@recoil.org> In-Reply-To: <42BBD403-02AA-4C26-AD1E-4D923622F9AF@recoil.org> Accept-Language: en-US, en-GB Content-Language: en-US X-MS-Has-Attach: yes X-MS-TNEF-Correlator: acceptlanguage: en-US, en-GB MIME-Version: 1.0 X-Virus-Scanned: by iCritical at engine01-20433-1.icritical.com Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] outgoing tcp connections X-BeenThere: mirageos-devel@lists.xenproject.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="===============4947526046940383793==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============4947526046940383793== Content-Language: en-US Content-Type: multipart/signed; boundary="Apple-Mail=_C72387DD-6DF4-4CB4-9FF9-DCE7971D55B7"; protocol="application/pgp-signature"; micalg=pgp-sha512 --Apple-Mail=_C72387DD-6DF4-4CB4-9FF9-DCE7971D55B7 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii On 18 Jun 2014, at 13:51, Anil Madhavapeddy wrote: >> Another (related) issue is when using tap and no dhcp, I've to be fast >> between executing the client and assigning a IP address in the >> hostsystem for tap0 (whenever an application is started, the host >> system IP gets removed) in order to reply to ARP to the mirage stack. > > Hrm yes, doing bridge setup is something I'm not keen on putting > into our tools. Ideally, we would use persistent tunnels that could > be set up by external tools and then attached to by the Unix unikernel. what was the rationale for not doing this again? > However, there is a light on this horizon, as I > discovered that MacOS X 10.10-beta has the vmnet framework installed > by default, which finally gives us bridging support there without needing > the installing of OSXtuntap. I'll write bindings when I get a chance... sweet :) -- Cheers, R. --Apple-Mail=_C72387DD-6DF4-4CB4-9FF9-DCE7971D55B7 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="signature.asc" Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJTotHQAAoJEOLF27JWwSg3k64P/R68gP6M9ccLq3ZQuoLQ8P8Y Ay3txt169aMO96SRCsl2SEQv09icNIdIS0Ho91MDdyBYVSI916dzEXA7sRFPSIwC HdxS60DwIgDXoJpt1pjMqG5Lf9bKGlnyEdr1FUjqtEVoikLL1aPECThw0rj+TTXs G2DNCZJxUh5ANGTGqV7fnUr+HgMqrHG0a9jm3thwkUhF6u4ajwhn6oRnKKSRDqmw xJKViSeQID07hXyK5FU60JUNQmlmT5CWqTUfEJ40AIDmzC+ruQ4yGcBPhyPohmD1 ksMBISqoZvdtQgSIiAYGems8C6LBNM0skmt5+lv4w/RXJwMFPoNNK0nhxmv3do91 8F4+56PzTFogVFt2drvbqLdASFgNx6aIAOheVrKTy8x/mIP+iVM30elAg1BiN6sY PaGGsRMwA6g/2n7kjcOHeHq9pJc0g8U9SRc0Ijgnm9xgL2VpI6QFEmEGxUDicoVm kjPrFB7UOqTGLZXvZ7Z67elv8wXmJGW6ddk18/mTnC3TqDbzxHSszaXJkTT12Ot2 qdVRPiwjo165kJYO3JvVV3cEqhubhJU8ANETlotdaMmCsQ215Zixi2wjVKIgfyrj 87rLzVe410OGy7LDVEyf2qshxThwLeclPicWRNsuypC/7fEfU3GXXu3CoGbmFSfQ PgqpjWDTlM7p4F7wWQiH =VnkD -----END PGP SIGNATURE----- --Apple-Mail=_C72387DD-6DF4-4CB4-9FF9-DCE7971D55B7-- --===============4947526046940383793== 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 --===============4947526046940383793==-- From mirageos-devel-bounces@lists.xenproject.org Thu Jun 19 14:07:05 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 19 Jun 2014 14:07: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 1WxczX-00085l-Is; Thu, 19 Jun 2014 14:07:03 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WxczV-00085g-Id for mirageos-devel@lists.xenproject.org; Thu, 19 Jun 2014 14:07:02 +0000 Received: from [85.158.139.211:56198] by server-4.bemta-5.messagelabs.com id 1B/DD-07250-48EE2A35; Thu, 19 Jun 2014 14:07:00 +0000 X-Env-Sender: Dave.Scott@citrix.com X-Msg-Ref: server-8.tower-206.messagelabs.com!1403186820!10869753!1 X-Originating-IP: [185.25.65.24] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 18756 invoked from network); 19 Jun 2014 14:07:00 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (185.25.65.24) by server-8.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 19 Jun 2014 14:07:00 -0000 X-IronPort-AV: E=Sophos;i="5.01,507,1400025600"; d="scan'208";a="21545663" Received: from unknown (HELO AMSPEX01CL01.citrite.net) ([10.69.60.9]) by AMSPIP01.EU.Citrix.com with ESMTP; 19 Jun 2014 14:07:00 +0000 Received: from AMSPEX01CL03.citrite.net ([169.254.8.89]) by AMSPEX01CL01.citrite.net ([169.254.6.105]) with mapi id 14.03.0181.006; Thu, 19 Jun 2014 16:07:00 +0200 From: Dave Scott To: Richard Mortier Thread-Topic: [MirageOS-devel] Mirage on Xen/ARM status Thread-Index: AQHPcSW73mSdf459mkW1dyuL+7LLS5tg3qQAgAIXP4CACSpYgIABdgIAgAE0XACAAAGyAIAAAZEAgAmQTACAACTfAIAACKAA Date: Thu, 19 Jun 2014 14:06:59 +0000 Message-ID: <5C746FB4-68A6-4FF6-88BC-EAC01CA2FA7E@citrix.com> References: <297FC9DB-3A4E-41A5-B00E-9DEF62C625E6@recoil.org> <39391660-83A7-46C0-AE53-3880A5A7A885@recoil.org> <5EC38C5B-9566-45FE-B37F-CD3FB1AC9F03@recoil.org> <95F32191-BEBA-43A5-A204-3F9334BFD166@nottingham.ac.uk> In-Reply-To: <95F32191-BEBA-43A5-A204-3F9334BFD166@nottingham.ac.uk> Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.69.46.1] Content-ID: <01704DCB678BD448AB01A6BEBDD3EF36@citrix.com> MIME-Version: 1.0 X-DLP: AMS1 Cc: "mirageos-devel@lists.xenproject.org" , Anil Madhavapeddy Subject: Re: [MirageOS-devel] Mirage on Xen/ARM status X-BeenThere: mirageos-devel@lists.xenproject.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, On 19 Jun 2014, at 14:36, Richard Mortier wrote: > = > On 19 Jun 2014, at 12:24, Thomas Leonard wrote: > = >> Perhaps the ones complement stuff should be moved out of >> mirage-platform anyway? It seems to be specific to networking, rather >> than to any particular platform. I see there's also a third version in >> the ns3 directory, which always returns zero. > = > yes; ones complement checksums are used in several IP protocols. i don't = know that they're used elsewhere (storage, etc). i guess efficient implemen= tations are likely to be platform specific, though perhaps one would expect= the compiler to dtrt rather than hand tweaking. IIRC the reason the checksum code didn=92t get moved out of the platform tr= ee when the network stack itself was moved out was because we don=92t have = the right build/link magic to include C code from other libraries. I=92m not sure if ones complement checksums are used in storage. However I = believe the CRC polynomial used by iSCSI (and btrfs?) is now implemented in= Intel CPUs. Perhaps one day our OCaml CRC library will have optimised asm = code for several platforms (generated via some staged compilation from some= OCaml source I=92m sure) Cheers, Dave _______________________________________________ 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 Jun 19 14:07:05 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 19 Jun 2014 14:07: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 1WxczX-00085l-Is; Thu, 19 Jun 2014 14:07:03 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WxczV-00085g-Id for mirageos-devel@lists.xenproject.org; Thu, 19 Jun 2014 14:07:02 +0000 Received: from [85.158.139.211:56198] by server-4.bemta-5.messagelabs.com id 1B/DD-07250-48EE2A35; Thu, 19 Jun 2014 14:07:00 +0000 X-Env-Sender: Dave.Scott@citrix.com X-Msg-Ref: server-8.tower-206.messagelabs.com!1403186820!10869753!1 X-Originating-IP: [185.25.65.24] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 18756 invoked from network); 19 Jun 2014 14:07:00 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (185.25.65.24) by server-8.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 19 Jun 2014 14:07:00 -0000 X-IronPort-AV: E=Sophos;i="5.01,507,1400025600"; d="scan'208";a="21545663" Received: from unknown (HELO AMSPEX01CL01.citrite.net) ([10.69.60.9]) by AMSPIP01.EU.Citrix.com with ESMTP; 19 Jun 2014 14:07:00 +0000 Received: from AMSPEX01CL03.citrite.net ([169.254.8.89]) by AMSPEX01CL01.citrite.net ([169.254.6.105]) with mapi id 14.03.0181.006; Thu, 19 Jun 2014 16:07:00 +0200 From: Dave Scott To: Richard Mortier Thread-Topic: [MirageOS-devel] Mirage on Xen/ARM status Thread-Index: AQHPcSW73mSdf459mkW1dyuL+7LLS5tg3qQAgAIXP4CACSpYgIABdgIAgAE0XACAAAGyAIAAAZEAgAmQTACAACTfAIAACKAA Date: Thu, 19 Jun 2014 14:06:59 +0000 Message-ID: <5C746FB4-68A6-4FF6-88BC-EAC01CA2FA7E@citrix.com> References: <297FC9DB-3A4E-41A5-B00E-9DEF62C625E6@recoil.org> <39391660-83A7-46C0-AE53-3880A5A7A885@recoil.org> <5EC38C5B-9566-45FE-B37F-CD3FB1AC9F03@recoil.org> <95F32191-BEBA-43A5-A204-3F9334BFD166@nottingham.ac.uk> In-Reply-To: <95F32191-BEBA-43A5-A204-3F9334BFD166@nottingham.ac.uk> Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.69.46.1] Content-ID: <01704DCB678BD448AB01A6BEBDD3EF36@citrix.com> MIME-Version: 1.0 X-DLP: AMS1 Cc: "mirageos-devel@lists.xenproject.org" , Anil Madhavapeddy Subject: Re: [MirageOS-devel] Mirage on Xen/ARM status X-BeenThere: mirageos-devel@lists.xenproject.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, On 19 Jun 2014, at 14:36, Richard Mortier wrote: > = > On 19 Jun 2014, at 12:24, Thomas Leonard wrote: > = >> Perhaps the ones complement stuff should be moved out of >> mirage-platform anyway? It seems to be specific to networking, rather >> than to any particular platform. I see there's also a third version in >> the ns3 directory, which always returns zero. > = > yes; ones complement checksums are used in several IP protocols. i don't = know that they're used elsewhere (storage, etc). i guess efficient implemen= tations are likely to be platform specific, though perhaps one would expect= the compiler to dtrt rather than hand tweaking. IIRC the reason the checksum code didn=92t get moved out of the platform tr= ee when the network stack itself was moved out was because we don=92t have = the right build/link magic to include C code from other libraries. I=92m not sure if ones complement checksums are used in storage. However I = believe the CRC polynomial used by iSCSI (and btrfs?) is now implemented in= Intel CPUs. Perhaps one day our OCaml CRC library will have optimised asm = code for several platforms (generated via some staged compilation from some= OCaml source I=92m sure) Cheers, Dave _______________________________________________ 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 Jun 19 15:08:22 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 19 Jun 2014 15:08: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 1Wxdwo-0001KI-IC; Thu, 19 Jun 2014 15:08:18 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Wxdwn-0001KD-PR for mirageos-devel@lists.xenproject.org; Thu, 19 Jun 2014 15:08:17 +0000 Received: from [85.158.137.68:38402] by server-13.bemta-3.messagelabs.com id 79/71-18692-0ECF2A35; Thu, 19 Jun 2014 15:08:16 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-3.tower-31.messagelabs.com!1403190496!11203683!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.7 required=7.0 tests=BODY_RANDOM_LONG, MIME_QP_LONG_LINE X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 18107 invoked from network); 19 Jun 2014 15:08:16 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-3.tower-31.messagelabs.com with SMTP; 19 Jun 2014 15:08:16 -0000 Received: (qmail 11803 invoked by uid 634); 19 Jun 2014 15:08:15 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from dab-far1-h-1-2.dab.02.net (HELO [10.5.213.220]) (82.132.220.222) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Thu, 19 Jun 2014 16:08:15 +0100 References: <13D72486-0766-49EA-AE2B-ED8ADE5CE3EF@recoil.org> <53A189FC.7020804@mehnert.org> <42BBD403-02AA-4C26-AD1E-4D923622F9AF@recoil.org> <5D4CD114-4F9F-4912-BE65-14F91C5322F1@nottingham.ac.uk> Mime-Version: 1.0 (1.0) In-Reply-To: <5D4CD114-4F9F-4912-BE65-14F91C5322F1@nottingham.ac.uk> Message-Id: X-Mailer: iPhone Mail (11D201) From: Anil Madhavapeddy Date: Thu, 19 Jun 2014 16:08:08 +0100 To: Richard Mortier X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] outgoing tcp connections X-BeenThere: mirageos-devel@lists.xenproject.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 19 Jun 2014, at 14:48, Richard Mortier wrote: > > > On 18 Jun 2014, at 13:51, Anil Madhavapeddy wrote: > >>> Another (related) issue is when using tap and no dhcp, I've to be fast >>> between executing the client and assigning a IP address in the >>> hostsystem for tap0 (whenever an application is started, the host >>> system IP gets removed) in order to reply to ARP to the mirage stack. >> >> Hrm yes, doing bridge setup is something I'm not keen on putting >> into our tools. Ideally, we would use persistent tunnels that could >> be set up by external tools and then attached to by the Unix unikernel. > > what was the rationale for not doing this again? > MacOS doesn't support persistent tuns. Which is why I mentioned the next bit ... :) >> However, there is a light on this horizon, as I >> discovered that MacOS X 10.10-beta has the vmnet framework installed >> by default, which finally gives us bridging support there without needing >> the installing of OSXtuntap. I'll write bindings when I get a chance... > > _______________________________________________ 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 Jun 19 15:08:22 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 19 Jun 2014 15:08: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 1Wxdwo-0001KI-IC; Thu, 19 Jun 2014 15:08:18 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Wxdwn-0001KD-PR for mirageos-devel@lists.xenproject.org; Thu, 19 Jun 2014 15:08:17 +0000 Received: from [85.158.137.68:38402] by server-13.bemta-3.messagelabs.com id 79/71-18692-0ECF2A35; Thu, 19 Jun 2014 15:08:16 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-3.tower-31.messagelabs.com!1403190496!11203683!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.7 required=7.0 tests=BODY_RANDOM_LONG, MIME_QP_LONG_LINE X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 18107 invoked from network); 19 Jun 2014 15:08:16 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-3.tower-31.messagelabs.com with SMTP; 19 Jun 2014 15:08:16 -0000 Received: (qmail 11803 invoked by uid 634); 19 Jun 2014 15:08:15 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from dab-far1-h-1-2.dab.02.net (HELO [10.5.213.220]) (82.132.220.222) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Thu, 19 Jun 2014 16:08:15 +0100 References: <13D72486-0766-49EA-AE2B-ED8ADE5CE3EF@recoil.org> <53A189FC.7020804@mehnert.org> <42BBD403-02AA-4C26-AD1E-4D923622F9AF@recoil.org> <5D4CD114-4F9F-4912-BE65-14F91C5322F1@nottingham.ac.uk> Mime-Version: 1.0 (1.0) In-Reply-To: <5D4CD114-4F9F-4912-BE65-14F91C5322F1@nottingham.ac.uk> Message-Id: X-Mailer: iPhone Mail (11D201) From: Anil Madhavapeddy Date: Thu, 19 Jun 2014 16:08:08 +0100 To: Richard Mortier X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] outgoing tcp connections X-BeenThere: mirageos-devel@lists.xenproject.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 19 Jun 2014, at 14:48, Richard Mortier wrote: > > > On 18 Jun 2014, at 13:51, Anil Madhavapeddy wrote: > >>> Another (related) issue is when using tap and no dhcp, I've to be fast >>> between executing the client and assigning a IP address in the >>> hostsystem for tap0 (whenever an application is started, the host >>> system IP gets removed) in order to reply to ARP to the mirage stack. >> >> Hrm yes, doing bridge setup is something I'm not keen on putting >> into our tools. Ideally, we would use persistent tunnels that could >> be set up by external tools and then attached to by the Unix unikernel. > > what was the rationale for not doing this again? > MacOS doesn't support persistent tuns. Which is why I mentioned the next bit ... :) >> However, there is a light on this horizon, as I >> discovered that MacOS X 10.10-beta has the vmnet framework installed >> by default, which finally gives us bridging support there without needing >> the installing of OSXtuntap. I'll write bindings when I get a chance... > > _______________________________________________ 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 Jun 19 15:08:52 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 19 Jun 2014 15:08: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 1WxdxM-0001Mv-MZ; Thu, 19 Jun 2014 15:08:52 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WxdxL-0001Mg-O9 for mirageos-devel@lists.xenproject.org; Thu, 19 Jun 2014 15:08:51 +0000 Received: from [85.158.137.68:13444] by server-16.bemta-3.messagelabs.com id 4C/36-13481-20DF2A35; Thu, 19 Jun 2014 15:08:50 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-3.tower-31.messagelabs.com!1403190529!11203827!1 X-Originating-IP: [209.85.213.49] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21054 invoked from network); 19 Jun 2014 15:08:50 -0000 Received: from mail-yh0-f49.google.com (HELO mail-yh0-f49.google.com) (209.85.213.49) by server-3.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 19 Jun 2014 15:08:50 -0000 Received: by mail-yh0-f49.google.com with SMTP id f73so1825644yha.36 for ; Thu, 19 Jun 2014 08:08:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:reply-to:user-agent:mime-version:to :subject:content-type:content-transfer-encoding; bh=90GxrhNsyieraot7yUvUJ9p+PXjEn36xWgKjV0dTaaM=; b=pxfgS4ix+tcAJXZgNgSQNA71kTBJBTpxi0B/lrWdi8rcovbRs7bZIfoeltewM9gpcX UCydTS0CulhDBbL42aRh72XjgIgTCqcD9pjf/I5/eCp4MZ3JdcdAt6Mu9YvWC/cQuLoz KPrGyOiR/gf5HGqd2IzUSLRkTiDKVDfvhw6Dhdk3LhGz8KED/YBCADlpaeu/+KsNhwxF e0ySUUCkXzeBueaKLsi/b7uPoy0qsK04qPf5EduH4hhQCpfCQ/X02yc9TAtlbFm7s5Vn aB31CuhBhDFow+uqM/7r99ThIBIjqk76PjbiZCM5WBb7aPz64sKn3oV5FoW1NyfxzQu4 rPhQ== X-Received: by 10.236.231.36 with SMTP id k34mr2803774yhq.157.1403190528685; Thu, 19 Jun 2014 08:08:48 -0700 (PDT) Received: from [172.16.25.10] ([185.25.64.249]) by mx.google.com with ESMTPSA id k28sm9352936yhn.13.2014.06.19.08.08.45 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 19 Jun 2014 08:08:46 -0700 (PDT) Message-ID: <53A2FCFC.7050602@xen.org> Date: Thu, 19 Jun 2014 16:08:44 +0100 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: "xen-devel@lists.xen.org" , "xen-api@lists.xen.org" , "mirageos-devel@lists.xenproject.org" Subject: [MirageOS-devel] Xen Project Developer Meeting Confirmed, Aug 20, 9:30 - 13:00, Chicago - Sign up ready X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: lars.kurth@xen.org 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 all, after your feedback, we will hold the Developer Meeting from 9:30 - 13:00. To sign up on or add topics please either * modify http://wiki.xenproject.org/wiki/Developer_Meeting/Aug2014 (my preferred option) - if you don't have write access to ther wiki, fill out http://xenproject.org/component/content/article/100-misc/145-request-to-be-made-a-wiki-editor.html * reply to this thread I am currently planning for about 35 people. We will provide snacks during breaks, but no lunch. As I will have to have a Xen Project Advisory Board meeting shortly after the Developer Meeting. 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 Thu Jun 19 15:08:52 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 19 Jun 2014 15:08: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 1WxdxM-0001Mv-MZ; Thu, 19 Jun 2014 15:08:52 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WxdxL-0001Mg-O9 for mirageos-devel@lists.xenproject.org; Thu, 19 Jun 2014 15:08:51 +0000 Received: from [85.158.137.68:13444] by server-16.bemta-3.messagelabs.com id 4C/36-13481-20DF2A35; Thu, 19 Jun 2014 15:08:50 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-3.tower-31.messagelabs.com!1403190529!11203827!1 X-Originating-IP: [209.85.213.49] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21054 invoked from network); 19 Jun 2014 15:08:50 -0000 Received: from mail-yh0-f49.google.com (HELO mail-yh0-f49.google.com) (209.85.213.49) by server-3.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 19 Jun 2014 15:08:50 -0000 Received: by mail-yh0-f49.google.com with SMTP id f73so1825644yha.36 for ; Thu, 19 Jun 2014 08:08:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:reply-to:user-agent:mime-version:to :subject:content-type:content-transfer-encoding; bh=90GxrhNsyieraot7yUvUJ9p+PXjEn36xWgKjV0dTaaM=; b=pxfgS4ix+tcAJXZgNgSQNA71kTBJBTpxi0B/lrWdi8rcovbRs7bZIfoeltewM9gpcX UCydTS0CulhDBbL42aRh72XjgIgTCqcD9pjf/I5/eCp4MZ3JdcdAt6Mu9YvWC/cQuLoz KPrGyOiR/gf5HGqd2IzUSLRkTiDKVDfvhw6Dhdk3LhGz8KED/YBCADlpaeu/+KsNhwxF e0ySUUCkXzeBueaKLsi/b7uPoy0qsK04qPf5EduH4hhQCpfCQ/X02yc9TAtlbFm7s5Vn aB31CuhBhDFow+uqM/7r99ThIBIjqk76PjbiZCM5WBb7aPz64sKn3oV5FoW1NyfxzQu4 rPhQ== X-Received: by 10.236.231.36 with SMTP id k34mr2803774yhq.157.1403190528685; Thu, 19 Jun 2014 08:08:48 -0700 (PDT) Received: from [172.16.25.10] ([185.25.64.249]) by mx.google.com with ESMTPSA id k28sm9352936yhn.13.2014.06.19.08.08.45 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 19 Jun 2014 08:08:46 -0700 (PDT) Message-ID: <53A2FCFC.7050602@xen.org> Date: Thu, 19 Jun 2014 16:08:44 +0100 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: "xen-devel@lists.xen.org" , "xen-api@lists.xen.org" , "mirageos-devel@lists.xenproject.org" Subject: [MirageOS-devel] Xen Project Developer Meeting Confirmed, Aug 20, 9:30 - 13:00, Chicago - Sign up ready X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: lars.kurth@xen.org 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 all, after your feedback, we will hold the Developer Meeting from 9:30 - 13:00. To sign up on or add topics please either * modify http://wiki.xenproject.org/wiki/Developer_Meeting/Aug2014 (my preferred option) - if you don't have write access to ther wiki, fill out http://xenproject.org/component/content/article/100-misc/145-request-to-be-made-a-wiki-editor.html * reply to this thread I am currently planning for about 35 people. We will provide snacks during breaks, but no lunch. As I will have to have a Xen Project Advisory Board meeting shortly after the Developer Meeting. 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 Fri Jun 20 10:23:20 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 20 Jun 2014 10:23: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 1WxvyT-0005PV-Ac; Fri, 20 Jun 2014 10:23:13 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WxvyS-0005PQ-0a for mirageos-devel@lists.xenproject.org; Fri, 20 Jun 2014 10:23:12 +0000 Received: from [85.158.139.211:6967] by server-13.bemta-5.messagelabs.com id 7E/10-02995-F8B04A35; Fri, 20 Jun 2014 10:23:11 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-3.tower-206.messagelabs.com!1403259789!3461283!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3415 invoked from network); 20 Jun 2014 10:23:09 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-3.tower-206.messagelabs.com with SMTP; 20 Jun 2014 10:23:09 -0000 Received: (qmail 503 invoked by uid 634); 20 Jun 2014 10:23:08 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from cpc11-belf9-2-0-cust355.2-1.cable.virginm.net (HELO [10.0.1.15]) (86.24.61.100) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Fri, 20 Jun 2014 11:23:05 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\)) From: Anil Madhavapeddy In-Reply-To: <5C746FB4-68A6-4FF6-88BC-EAC01CA2FA7E@citrix.com> Date: Fri, 20 Jun 2014 11:23:04 +0100 Message-Id: References: <297FC9DB-3A4E-41A5-B00E-9DEF62C625E6@recoil.org> <39391660-83A7-46C0-AE53-3880A5A7A885@recoil.org> <5EC38C5B-9566-45FE-B37F-CD3FB1AC9F03@recoil.org> <95F32191-BEBA-43A5-A204-3F9334BFD166@nottingham.ac.uk> <5C746FB4-68A6-4FF6-88BC-EAC01CA2FA7E@citrix.com> To: David Scott X-Mailer: Apple Mail (2.1874) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Mirage on Xen/ARM status X-BeenThere: mirageos-devel@lists.xenproject.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 19 Jun 2014, at 15:06, Dave Scott wrote: > = > On 19 Jun 2014, at 14:36, Richard Mortier wrote: > = >> = >> On 19 Jun 2014, at 12:24, Thomas Leonard wrote: >> = >>> Perhaps the ones complement stuff should be moved out of >>> mirage-platform anyway? It seems to be specific to networking, rather >>> than to any particular platform. I see there's also a third version in >>> the ns3 directory, which always returns zero. >> = >> yes; ones complement checksums are used in several IP protocols. i don't= know that they're used elsewhere (storage, etc). i guess efficient impleme= ntations are likely to be platform specific, though perhaps one would expec= t the compiler to dtrt rather than hand tweaking. > = > IIRC the reason the checksum code didn=92t get moved out of the platform = tree when the network stack itself was moved out was because we don=92t hav= e the right build/link magic to include C code from other libraries. This is exactly why it's in platform (along with all the other C bindings).= Thomas, does the new installation scheme for MiniOS help with making the = MiniOS headers available for other libraries to compile against them? I'd = be very happy to move these stubs into mirage-tcpip and make them easier to= maintain. > I=92m not sure if ones complement checksums are used in storage. However = I believe the CRC polynomial used by iSCSI (and btrfs?) is now implemented = in Intel CPUs. Perhaps one day our OCaml CRC library will have optimised as= m code for several platforms (generated via some staged compilation from so= me OCaml source I=92m sure) Yes, in SSE 4.2 I believe. Completely randomly, I also noticed that the ST= TNI instructions also provide faster ways of doing substring searching that= may be useful to expose in the Re engine if the speedup justifies the comp= lexity: http://www.strchr.com/strcmp_and_strlen_using_sse_4.2 -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 Jun 20 10:23:20 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 20 Jun 2014 10:23: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 1WxvyT-0005PV-Ac; Fri, 20 Jun 2014 10:23:13 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WxvyS-0005PQ-0a for mirageos-devel@lists.xenproject.org; Fri, 20 Jun 2014 10:23:12 +0000 Received: from [85.158.139.211:6967] by server-13.bemta-5.messagelabs.com id 7E/10-02995-F8B04A35; Fri, 20 Jun 2014 10:23:11 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-3.tower-206.messagelabs.com!1403259789!3461283!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3415 invoked from network); 20 Jun 2014 10:23:09 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-3.tower-206.messagelabs.com with SMTP; 20 Jun 2014 10:23:09 -0000 Received: (qmail 503 invoked by uid 634); 20 Jun 2014 10:23:08 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from cpc11-belf9-2-0-cust355.2-1.cable.virginm.net (HELO [10.0.1.15]) (86.24.61.100) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Fri, 20 Jun 2014 11:23:05 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\)) From: Anil Madhavapeddy In-Reply-To: <5C746FB4-68A6-4FF6-88BC-EAC01CA2FA7E@citrix.com> Date: Fri, 20 Jun 2014 11:23:04 +0100 Message-Id: References: <297FC9DB-3A4E-41A5-B00E-9DEF62C625E6@recoil.org> <39391660-83A7-46C0-AE53-3880A5A7A885@recoil.org> <5EC38C5B-9566-45FE-B37F-CD3FB1AC9F03@recoil.org> <95F32191-BEBA-43A5-A204-3F9334BFD166@nottingham.ac.uk> <5C746FB4-68A6-4FF6-88BC-EAC01CA2FA7E@citrix.com> To: David Scott X-Mailer: Apple Mail (2.1874) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Mirage on Xen/ARM status X-BeenThere: mirageos-devel@lists.xenproject.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 19 Jun 2014, at 15:06, Dave Scott wrote: > = > On 19 Jun 2014, at 14:36, Richard Mortier wrote: > = >> = >> On 19 Jun 2014, at 12:24, Thomas Leonard wrote: >> = >>> Perhaps the ones complement stuff should be moved out of >>> mirage-platform anyway? It seems to be specific to networking, rather >>> than to any particular platform. I see there's also a third version in >>> the ns3 directory, which always returns zero. >> = >> yes; ones complement checksums are used in several IP protocols. i don't= know that they're used elsewhere (storage, etc). i guess efficient impleme= ntations are likely to be platform specific, though perhaps one would expec= t the compiler to dtrt rather than hand tweaking. > = > IIRC the reason the checksum code didn=92t get moved out of the platform = tree when the network stack itself was moved out was because we don=92t hav= e the right build/link magic to include C code from other libraries. This is exactly why it's in platform (along with all the other C bindings).= Thomas, does the new installation scheme for MiniOS help with making the = MiniOS headers available for other libraries to compile against them? I'd = be very happy to move these stubs into mirage-tcpip and make them easier to= maintain. > I=92m not sure if ones complement checksums are used in storage. However = I believe the CRC polynomial used by iSCSI (and btrfs?) is now implemented = in Intel CPUs. Perhaps one day our OCaml CRC library will have optimised as= m code for several platforms (generated via some staged compilation from so= me OCaml source I=92m sure) Yes, in SSE 4.2 I believe. Completely randomly, I also noticed that the ST= TNI instructions also provide faster ways of doing substring searching that= may be useful to expose in the Re engine if the speedup justifies the comp= lexity: http://www.strchr.com/strcmp_and_strlen_using_sse_4.2 -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 Jun 20 10:47:33 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 20 Jun 2014 10:47: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 1WxwLz-0005j0-3h; Fri, 20 Jun 2014 10:47:31 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WxwLy-0005is-FZ for mirageos-devel@lists.xenproject.org; Fri, 20 Jun 2014 10:47:30 +0000 Received: from [85.158.139.211:27976] by server-14.bemta-5.messagelabs.com id B1/46-27057-14114A35; Fri, 20 Jun 2014 10:47:29 +0000 X-Env-Sender: talex5@gmail.com X-Msg-Ref: server-12.tower-206.messagelabs.com!1403261247!11047520!1 X-Originating-IP: [209.85.219.41] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, ML_RADAR_SPEW_LINKS_23,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 18880 invoked from network); 20 Jun 2014 10:47:28 -0000 Received: from mail-oa0-f41.google.com (HELO mail-oa0-f41.google.com) (209.85.219.41) by server-12.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 20 Jun 2014 10:47:28 -0000 Received: by mail-oa0-f41.google.com with SMTP id l6so7215334oag.0 for ; Fri, 20 Jun 2014 03:47:27 -0700 (PDT) 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=VUV6+Fjr/E929ynM66xg4S3/KAlEYtOxKSF5Mz72HW4=; b=P7OTlc6chdHYyCZ3GR8pSIDiBfXfjoOU9f8yVoBGK02SPDcKpHlxuQV6Z6pd3rP7ay +vT3py4hB+gPQ/6h4zgt7gbAEqKlET35wLJIHwPE4c/TTdVSv2gCiGjIty0sVQH4VdEE Ojp9NFXC+iIQJh7K8uR8keQjvoHvi6ZlNpTxpLxcwZCBBx2QQjvfZaH9FY0crhEXIRlH TOJypFO6J+RYcH1dZlyF7m1ryb1YARGxrYrqYRyhuVIk8Gs/ZnsdtQDMZfmrO6EeXSKl DBRbYJv6YWLVVDp+36SV4HLmR/7p5uZMePr3acVuR7MVXq0dr5C8l0iOlDFNhTacTL6m 9qOQ== MIME-Version: 1.0 X-Received: by 10.182.251.170 with SMTP id zl10mr2373039obc.5.1403261246953; Fri, 20 Jun 2014 03:47:26 -0700 (PDT) Received: by 10.76.92.5 with HTTP; Fri, 20 Jun 2014 03:47:26 -0700 (PDT) In-Reply-To: References: <297FC9DB-3A4E-41A5-B00E-9DEF62C625E6@recoil.org> <39391660-83A7-46C0-AE53-3880A5A7A885@recoil.org> <5EC38C5B-9566-45FE-B37F-CD3FB1AC9F03@recoil.org> <95F32191-BEBA-43A5-A204-3F9334BFD166@nottingham.ac.uk> <5C746FB4-68A6-4FF6-88BC-EAC01CA2FA7E@citrix.com> Date: Fri, 20 Jun 2014 11:47:26 +0100 Message-ID: From: Thomas Leonard To: Anil Madhavapeddy Cc: David Scott , "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Mirage on Xen/ARM status X-BeenThere: mirageos-devel@lists.xenproject.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 T24gMjAgSnVuZSAyMDE0IDExOjIzLCBBbmlsIE1hZGhhdmFwZWRkeSA8YW5pbEByZWNvaWwub3Jn PiB3cm90ZToKPiBPbiAxOSBKdW4gMjAxNCwgYXQgMTU6MDYsIERhdmUgU2NvdHQgPERhdmUuU2Nv dHRAY2l0cml4LmNvbT4gd3JvdGU6Cj4+Cj4+IE9uIDE5IEp1biAyMDE0LCBhdCAxNDozNiwgUmlj aGFyZCBNb3J0aWVyIDxSaWNoYXJkLk1vcnRpZXJAbm90dGluZ2hhbS5hYy51az4gd3JvdGU6Cj4+ Cj4+Pgo+Pj4gT24gMTkgSnVuIDIwMTQsIGF0IDEyOjI0LCBUaG9tYXMgTGVvbmFyZCA8dGFsZXg1 QGdtYWlsLmNvbT4gd3JvdGU6Cj4+Pgo+Pj4+IFBlcmhhcHMgdGhlIG9uZXMgY29tcGxlbWVudCBz dHVmZiBzaG91bGQgYmUgbW92ZWQgb3V0IG9mCj4+Pj4gbWlyYWdlLXBsYXRmb3JtIGFueXdheT8g SXQgc2VlbXMgdG8gYmUgc3BlY2lmaWMgdG8gbmV0d29ya2luZywgcmF0aGVyCj4+Pj4gdGhhbiB0 byBhbnkgcGFydGljdWxhciBwbGF0Zm9ybS4gSSBzZWUgdGhlcmUncyBhbHNvIGEgdGhpcmQgdmVy c2lvbiBpbgo+Pj4+IHRoZSBuczMgZGlyZWN0b3J5LCB3aGljaCBhbHdheXMgcmV0dXJucyB6ZXJv Lgo+Pj4KPj4+IHllczsgb25lcyBjb21wbGVtZW50IGNoZWNrc3VtcyBhcmUgdXNlZCBpbiBzZXZl cmFsIElQIHByb3RvY29scy4gaSBkb24ndCBrbm93IHRoYXQgdGhleSdyZSB1c2VkIGVsc2V3aGVy ZSAoc3RvcmFnZSwgZXRjKS4gaSBndWVzcyBlZmZpY2llbnQgaW1wbGVtZW50YXRpb25zIGFyZSBs aWtlbHkgdG8gYmUgcGxhdGZvcm0gc3BlY2lmaWMsIHRob3VnaCBwZXJoYXBzIG9uZSB3b3VsZCBl eHBlY3QgdGhlIGNvbXBpbGVyIHRvIGR0cnQgcmF0aGVyIHRoYW4gaGFuZCB0d2Vha2luZy4KClll cy4KCkkgdGhpbmsgdGhlIHRlcm0gInBsYXRmb3JtIiBtaWdodCBiZSBjb25mdXNpbmcgaGVyZSwg dGhvdWdoLiBUaGUgY29kZQptaWdodCBkZXBlbmQgb24gdGhlIENQVSB0eXBlIChhcm0sIHg4Niwg ZXRjKSwgYnV0IGl0IHNob3VsZG4ndCBkZXBlbmQKb24gdGhlIE1pcmFnZSBwbGF0Zm9ybS4gSSB0 aGluayBtaXJhZ2UtcGxhdGZvcm0gaXMgZm9yIGNvZGUgdGhhdCBtdXN0CmJlIGRpZmZlcmVudCBm b3IgWGVuLCBVbml4LCBldGMsIG5vdCBmb3IgZGlmZmVyZW50IENQVSB0eXBlcy4KCj4+IElJUkMg dGhlIHJlYXNvbiB0aGUgY2hlY2tzdW0gY29kZSBkaWRu4oCZdCBnZXQgbW92ZWQgb3V0IG9mIHRo ZSBwbGF0Zm9ybSB0cmVlIHdoZW4gdGhlIG5ldHdvcmsgc3RhY2sgaXRzZWxmIHdhcyBtb3ZlZCBv dXQgd2FzIGJlY2F1c2Ugd2UgZG9u4oCZdCBoYXZlIHRoZSByaWdodCBidWlsZC9saW5rIG1hZ2lj IHRvIGluY2x1ZGUgQyBjb2RlIGZyb20gb3RoZXIgbGlicmFyaWVzLgo+Cj4gVGhpcyBpcyBleGFj dGx5IHdoeSBpdCdzIGluIHBsYXRmb3JtIChhbG9uZyB3aXRoIGFsbCB0aGUgb3RoZXIgQyBiaW5k aW5ncykuICBUaG9tYXMsIGRvZXMgdGhlIG5ldyBpbnN0YWxsYXRpb24gc2NoZW1lIGZvciBNaW5p T1MgaGVscCB3aXRoIG1ha2luZyB0aGUgTWluaU9TIGhlYWRlcnMgYXZhaWxhYmxlIGZvciBvdGhl ciBsaWJyYXJpZXMgdG8gY29tcGlsZSBhZ2FpbnN0IHRoZW0/ICBJJ2QgYmUgdmVyeSBoYXBweSB0 byBtb3ZlIHRoZXNlIHN0dWJzIGludG8gbWlyYWdlLXRjcGlwIGFuZCBtYWtlIHRoZW0gZWFzaWVy IHRvIG1haW50YWluLgoKWWVzLiBZb3UgY2FuIGp1c3QgZG8gZS5nLjoKCiQgcGtnLWNvbmZpZyAt LWNmbGFncyBsaWJtaW5pb3MKWy4uLl0gLUkvdXNyL2luY2x1ZGUvbWluaS1vcwoKL3Vzci9pbmNs dWRlL21pbmktb3MgY29udGFpbnMgYWxsIHRoZSBtaW5pLW9zIGhlYWRlcnMsIGFzIHdlbGwgYXMg YQpjb3B5IG9mIHRoZSBYZW4gcHVibGljIGhlYWRlcnMgdGhleSBkZXBlbmQgb24KKC91c3IvaW5j bHVkZS9taW5pLW9zL3hlbikuCgo+PiBJ4oCZbSBub3Qgc3VyZSBpZiBvbmVzIGNvbXBsZW1lbnQg Y2hlY2tzdW1zIGFyZSB1c2VkIGluIHN0b3JhZ2UuIEhvd2V2ZXIgSSBiZWxpZXZlIHRoZSBDUkMg cG9seW5vbWlhbCB1c2VkIGJ5IGlTQ1NJIChhbmQgYnRyZnM/KSBpcyBub3cgaW1wbGVtZW50ZWQg aW4gSW50ZWwgQ1BVcy4gUGVyaGFwcyBvbmUgZGF5IG91ciBPQ2FtbCBDUkMgbGlicmFyeSB3aWxs IGhhdmUgb3B0aW1pc2VkIGFzbSBjb2RlIGZvciBzZXZlcmFsIHBsYXRmb3JtcyAoZ2VuZXJhdGVk IHZpYSBzb21lIHN0YWdlZCBjb21waWxhdGlvbiBmcm9tIHNvbWUgT0NhbWwgc291cmNlIEnigJlt IHN1cmUpCj4KPiBZZXMsIGluIFNTRSA0LjIgSSBiZWxpZXZlLiAgQ29tcGxldGVseSByYW5kb21s eSwgSSBhbHNvIG5vdGljZWQgdGhhdCB0aGUgU1RUTkkgaW5zdHJ1Y3Rpb25zIGFsc28gcHJvdmlk ZSBmYXN0ZXIgd2F5cyBvZiBkb2luZyBzdWJzdHJpbmcgc2VhcmNoaW5nIHRoYXQgbWF5IGJlIHVz ZWZ1bCB0byBleHBvc2UgaW4gdGhlIFJlIGVuZ2luZSBpZiB0aGUgc3BlZWR1cCBqdXN0aWZpZXMg dGhlIGNvbXBsZXhpdHk6Cj4KPiBodHRwOi8vd3d3LnN0cmNoci5jb20vc3RyY21wX2FuZF9zdHJs ZW5fdXNpbmdfc3NlXzQuMgo+Cj4gLWFuaWwKPiBfX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fXwo+IE1pcmFnZU9TLWRldmVsIG1haWxpbmcgbGlzdAo+IE1pcmFn ZU9TLWRldmVsQGxpc3RzLnhlbnByb2plY3Qub3JnCj4gaHR0cDovL2xpc3RzLnhlbnByb2plY3Qu b3JnL2NnaS1iaW4vbWFpbG1hbi9saXN0aW5mby9taXJhZ2Vvcy1kZXZlbAoKCgotLSAKRHIgVGhv bWFzIExlb25hcmQgICAgICAgIGh0dHA6Ly8waW5zdGFsbC5uZXQvCkdQRzogOTI0MiA5ODA3IEM5 ODUgM0MwNyA0NEE2ICA4QjlBIEFFMDcgODI4MCA1OUE1IDNDQzEKR1BHOiBEQTk4IDI1QUUgQ0FE MCA4OTc1IDdDREEgIEJEOEUgMDcxMyAzRjk2IENBNzQgRDhCQQoKX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX18KTWlyYWdlT1MtZGV2ZWwgbWFpbGluZyBsaXN0 Ck1pcmFnZU9TLWRldmVsQGxpc3RzLnhlbnByb2plY3Qub3JnCmh0dHA6Ly9saXN0cy54ZW5wcm9q ZWN0Lm9yZy9jZ2ktYmluL21haWxtYW4vbGlzdGluZm8vbWlyYWdlb3MtZGV2ZWwK From mirageos-devel-bounces@lists.xenproject.org Fri Jun 20 10:47:33 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 20 Jun 2014 10:47: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 1WxwLz-0005j0-3h; Fri, 20 Jun 2014 10:47:31 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WxwLy-0005is-FZ for mirageos-devel@lists.xenproject.org; Fri, 20 Jun 2014 10:47:30 +0000 Received: from [85.158.139.211:27976] by server-14.bemta-5.messagelabs.com id B1/46-27057-14114A35; Fri, 20 Jun 2014 10:47:29 +0000 X-Env-Sender: talex5@gmail.com X-Msg-Ref: server-12.tower-206.messagelabs.com!1403261247!11047520!1 X-Originating-IP: [209.85.219.41] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, ML_RADAR_SPEW_LINKS_23,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 18880 invoked from network); 20 Jun 2014 10:47:28 -0000 Received: from mail-oa0-f41.google.com (HELO mail-oa0-f41.google.com) (209.85.219.41) by server-12.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 20 Jun 2014 10:47:28 -0000 Received: by mail-oa0-f41.google.com with SMTP id l6so7215334oag.0 for ; Fri, 20 Jun 2014 03:47:27 -0700 (PDT) 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=VUV6+Fjr/E929ynM66xg4S3/KAlEYtOxKSF5Mz72HW4=; b=P7OTlc6chdHYyCZ3GR8pSIDiBfXfjoOU9f8yVoBGK02SPDcKpHlxuQV6Z6pd3rP7ay +vT3py4hB+gPQ/6h4zgt7gbAEqKlET35wLJIHwPE4c/TTdVSv2gCiGjIty0sVQH4VdEE Ojp9NFXC+iIQJh7K8uR8keQjvoHvi6ZlNpTxpLxcwZCBBx2QQjvfZaH9FY0crhEXIRlH TOJypFO6J+RYcH1dZlyF7m1ryb1YARGxrYrqYRyhuVIk8Gs/ZnsdtQDMZfmrO6EeXSKl DBRbYJv6YWLVVDp+36SV4HLmR/7p5uZMePr3acVuR7MVXq0dr5C8l0iOlDFNhTacTL6m 9qOQ== MIME-Version: 1.0 X-Received: by 10.182.251.170 with SMTP id zl10mr2373039obc.5.1403261246953; Fri, 20 Jun 2014 03:47:26 -0700 (PDT) Received: by 10.76.92.5 with HTTP; Fri, 20 Jun 2014 03:47:26 -0700 (PDT) In-Reply-To: References: <297FC9DB-3A4E-41A5-B00E-9DEF62C625E6@recoil.org> <39391660-83A7-46C0-AE53-3880A5A7A885@recoil.org> <5EC38C5B-9566-45FE-B37F-CD3FB1AC9F03@recoil.org> <95F32191-BEBA-43A5-A204-3F9334BFD166@nottingham.ac.uk> <5C746FB4-68A6-4FF6-88BC-EAC01CA2FA7E@citrix.com> Date: Fri, 20 Jun 2014 11:47:26 +0100 Message-ID: From: Thomas Leonard To: Anil Madhavapeddy Cc: David Scott , "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Mirage on Xen/ARM status X-BeenThere: mirageos-devel@lists.xenproject.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 T24gMjAgSnVuZSAyMDE0IDExOjIzLCBBbmlsIE1hZGhhdmFwZWRkeSA8YW5pbEByZWNvaWwub3Jn PiB3cm90ZToKPiBPbiAxOSBKdW4gMjAxNCwgYXQgMTU6MDYsIERhdmUgU2NvdHQgPERhdmUuU2Nv dHRAY2l0cml4LmNvbT4gd3JvdGU6Cj4+Cj4+IE9uIDE5IEp1biAyMDE0LCBhdCAxNDozNiwgUmlj aGFyZCBNb3J0aWVyIDxSaWNoYXJkLk1vcnRpZXJAbm90dGluZ2hhbS5hYy51az4gd3JvdGU6Cj4+ Cj4+Pgo+Pj4gT24gMTkgSnVuIDIwMTQsIGF0IDEyOjI0LCBUaG9tYXMgTGVvbmFyZCA8dGFsZXg1 QGdtYWlsLmNvbT4gd3JvdGU6Cj4+Pgo+Pj4+IFBlcmhhcHMgdGhlIG9uZXMgY29tcGxlbWVudCBz dHVmZiBzaG91bGQgYmUgbW92ZWQgb3V0IG9mCj4+Pj4gbWlyYWdlLXBsYXRmb3JtIGFueXdheT8g SXQgc2VlbXMgdG8gYmUgc3BlY2lmaWMgdG8gbmV0d29ya2luZywgcmF0aGVyCj4+Pj4gdGhhbiB0 byBhbnkgcGFydGljdWxhciBwbGF0Zm9ybS4gSSBzZWUgdGhlcmUncyBhbHNvIGEgdGhpcmQgdmVy c2lvbiBpbgo+Pj4+IHRoZSBuczMgZGlyZWN0b3J5LCB3aGljaCBhbHdheXMgcmV0dXJucyB6ZXJv Lgo+Pj4KPj4+IHllczsgb25lcyBjb21wbGVtZW50IGNoZWNrc3VtcyBhcmUgdXNlZCBpbiBzZXZl cmFsIElQIHByb3RvY29scy4gaSBkb24ndCBrbm93IHRoYXQgdGhleSdyZSB1c2VkIGVsc2V3aGVy ZSAoc3RvcmFnZSwgZXRjKS4gaSBndWVzcyBlZmZpY2llbnQgaW1wbGVtZW50YXRpb25zIGFyZSBs aWtlbHkgdG8gYmUgcGxhdGZvcm0gc3BlY2lmaWMsIHRob3VnaCBwZXJoYXBzIG9uZSB3b3VsZCBl eHBlY3QgdGhlIGNvbXBpbGVyIHRvIGR0cnQgcmF0aGVyIHRoYW4gaGFuZCB0d2Vha2luZy4KClll cy4KCkkgdGhpbmsgdGhlIHRlcm0gInBsYXRmb3JtIiBtaWdodCBiZSBjb25mdXNpbmcgaGVyZSwg dGhvdWdoLiBUaGUgY29kZQptaWdodCBkZXBlbmQgb24gdGhlIENQVSB0eXBlIChhcm0sIHg4Niwg ZXRjKSwgYnV0IGl0IHNob3VsZG4ndCBkZXBlbmQKb24gdGhlIE1pcmFnZSBwbGF0Zm9ybS4gSSB0 aGluayBtaXJhZ2UtcGxhdGZvcm0gaXMgZm9yIGNvZGUgdGhhdCBtdXN0CmJlIGRpZmZlcmVudCBm b3IgWGVuLCBVbml4LCBldGMsIG5vdCBmb3IgZGlmZmVyZW50IENQVSB0eXBlcy4KCj4+IElJUkMg dGhlIHJlYXNvbiB0aGUgY2hlY2tzdW0gY29kZSBkaWRu4oCZdCBnZXQgbW92ZWQgb3V0IG9mIHRo ZSBwbGF0Zm9ybSB0cmVlIHdoZW4gdGhlIG5ldHdvcmsgc3RhY2sgaXRzZWxmIHdhcyBtb3ZlZCBv dXQgd2FzIGJlY2F1c2Ugd2UgZG9u4oCZdCBoYXZlIHRoZSByaWdodCBidWlsZC9saW5rIG1hZ2lj IHRvIGluY2x1ZGUgQyBjb2RlIGZyb20gb3RoZXIgbGlicmFyaWVzLgo+Cj4gVGhpcyBpcyBleGFj dGx5IHdoeSBpdCdzIGluIHBsYXRmb3JtIChhbG9uZyB3aXRoIGFsbCB0aGUgb3RoZXIgQyBiaW5k aW5ncykuICBUaG9tYXMsIGRvZXMgdGhlIG5ldyBpbnN0YWxsYXRpb24gc2NoZW1lIGZvciBNaW5p T1MgaGVscCB3aXRoIG1ha2luZyB0aGUgTWluaU9TIGhlYWRlcnMgYXZhaWxhYmxlIGZvciBvdGhl ciBsaWJyYXJpZXMgdG8gY29tcGlsZSBhZ2FpbnN0IHRoZW0/ICBJJ2QgYmUgdmVyeSBoYXBweSB0 byBtb3ZlIHRoZXNlIHN0dWJzIGludG8gbWlyYWdlLXRjcGlwIGFuZCBtYWtlIHRoZW0gZWFzaWVy IHRvIG1haW50YWluLgoKWWVzLiBZb3UgY2FuIGp1c3QgZG8gZS5nLjoKCiQgcGtnLWNvbmZpZyAt LWNmbGFncyBsaWJtaW5pb3MKWy4uLl0gLUkvdXNyL2luY2x1ZGUvbWluaS1vcwoKL3Vzci9pbmNs dWRlL21pbmktb3MgY29udGFpbnMgYWxsIHRoZSBtaW5pLW9zIGhlYWRlcnMsIGFzIHdlbGwgYXMg YQpjb3B5IG9mIHRoZSBYZW4gcHVibGljIGhlYWRlcnMgdGhleSBkZXBlbmQgb24KKC91c3IvaW5j bHVkZS9taW5pLW9zL3hlbikuCgo+PiBJ4oCZbSBub3Qgc3VyZSBpZiBvbmVzIGNvbXBsZW1lbnQg Y2hlY2tzdW1zIGFyZSB1c2VkIGluIHN0b3JhZ2UuIEhvd2V2ZXIgSSBiZWxpZXZlIHRoZSBDUkMg cG9seW5vbWlhbCB1c2VkIGJ5IGlTQ1NJIChhbmQgYnRyZnM/KSBpcyBub3cgaW1wbGVtZW50ZWQg aW4gSW50ZWwgQ1BVcy4gUGVyaGFwcyBvbmUgZGF5IG91ciBPQ2FtbCBDUkMgbGlicmFyeSB3aWxs IGhhdmUgb3B0aW1pc2VkIGFzbSBjb2RlIGZvciBzZXZlcmFsIHBsYXRmb3JtcyAoZ2VuZXJhdGVk IHZpYSBzb21lIHN0YWdlZCBjb21waWxhdGlvbiBmcm9tIHNvbWUgT0NhbWwgc291cmNlIEnigJlt IHN1cmUpCj4KPiBZZXMsIGluIFNTRSA0LjIgSSBiZWxpZXZlLiAgQ29tcGxldGVseSByYW5kb21s eSwgSSBhbHNvIG5vdGljZWQgdGhhdCB0aGUgU1RUTkkgaW5zdHJ1Y3Rpb25zIGFsc28gcHJvdmlk ZSBmYXN0ZXIgd2F5cyBvZiBkb2luZyBzdWJzdHJpbmcgc2VhcmNoaW5nIHRoYXQgbWF5IGJlIHVz ZWZ1bCB0byBleHBvc2UgaW4gdGhlIFJlIGVuZ2luZSBpZiB0aGUgc3BlZWR1cCBqdXN0aWZpZXMg dGhlIGNvbXBsZXhpdHk6Cj4KPiBodHRwOi8vd3d3LnN0cmNoci5jb20vc3RyY21wX2FuZF9zdHJs ZW5fdXNpbmdfc3NlXzQuMgo+Cj4gLWFuaWwKPiBfX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fXwo+IE1pcmFnZU9TLWRldmVsIG1haWxpbmcgbGlzdAo+IE1pcmFn ZU9TLWRldmVsQGxpc3RzLnhlbnByb2plY3Qub3JnCj4gaHR0cDovL2xpc3RzLnhlbnByb2plY3Qu b3JnL2NnaS1iaW4vbWFpbG1hbi9saXN0aW5mby9taXJhZ2Vvcy1kZXZlbAoKCgotLSAKRHIgVGhv bWFzIExlb25hcmQgICAgICAgIGh0dHA6Ly8waW5zdGFsbC5uZXQvCkdQRzogOTI0MiA5ODA3IEM5 ODUgM0MwNyA0NEE2ICA4QjlBIEFFMDcgODI4MCA1OUE1IDNDQzEKR1BHOiBEQTk4IDI1QUUgQ0FE MCA4OTc1IDdDREEgIEJEOEUgMDcxMyAzRjk2IENBNzQgRDhCQQoKX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX18KTWlyYWdlT1MtZGV2ZWwgbWFpbGluZyBsaXN0 Ck1pcmFnZU9TLWRldmVsQGxpc3RzLnhlbnByb2plY3Qub3JnCmh0dHA6Ly9saXN0cy54ZW5wcm9q ZWN0Lm9yZy9jZ2ktYmluL21haWxtYW4vbGlzdGluZm8vbWlyYWdlb3MtZGV2ZWwK From mirageos-devel-bounces@lists.xenproject.org Fri Jun 20 15:11:37 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 20 Jun 2014 15:11: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 1Wy0TV-0000LC-0v; Fri, 20 Jun 2014 15:11:33 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Wy0TU-0000L7-2g for mirageos-devel@lists.xenproject.org; Fri, 20 Jun 2014 15:11:32 +0000 Received: from [85.158.137.68:15052] by server-8.bemta-3.messagelabs.com id 2E/E4-21547-12F44A35; Fri, 20 Jun 2014 15:11:29 +0000 X-Env-Sender: psxsl6@nottingham.ac.uk X-Msg-Ref: server-16.tower-31.messagelabs.com!1403277088!11383160!1 X-Originating-IP: [93.159.202.117] X-SpamReason: No, hits=0.7 required=7.0 tests=BODY_RANDOM_LONG, MIME_QP_LONG_LINE X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29642 invoked from network); 20 Jun 2014 15:11:28 -0000 Received: from engine03-20433-11.icritical.com (HELO engine03-20433-11.icritical.com) (93.159.202.117) by server-16.tower-31.messagelabs.com with SMTP; 20 Jun 2014 15:11:28 -0000 Received: (qmail 25178 invoked from network); 20 Jun 2014 15:11:54 -0000 Received: from localhost (127.0.0.1) by engine03-20433-11.icritical.com with SMTP; 20 Jun 2014 15:11:54 -0000 Received: from engine03-20433-11.icritical.com ([127.0.0.1]) by localhost (engine03-20433-11.icritical.com [127.0.0.1]) (amavisd-new, port 10024) with SMTP id 24798-07 for ; Fri, 20 Jun 2014 16:11:47 +0100 (BST) Received: (qmail 24641 invoked by uid 599); 20 Jun 2014 15:11:11 -0000 Received: from unknown (HELO smtp4.nottingham.ac.uk) (128.243.220.65) by engine03-20433-11.icritical.com (qpsmtpd/0.28) with ESMTP; Fri, 20 Jun 2014 16:11:11 +0100 Received: from uiwexhub01.ad.nottingham.ac.uk ([128.243.15.133]) by smtp4.nottingham.ac.uk with esmtps (TLSv1:AES128-SHA:128) (Exim 4.77) (envelope-from ) id 1Wy0Sg-0006b8-7T for mirageos-devel@lists.xenproject.org; Fri, 20 Jun 2014 16:10:42 +0100 From: Steven Luland To: "mirageos-devel@lists.xenproject.org" Date: Fri, 20 Jun 2014 16:10:41 +0100 Thread-Topic: C++ library to OCaml: OCaml objects Thread-Index: Ac+MmczQv+xbd/PiTCmgGrEoBxOpzQ== Message-ID: Accept-Language: en-US, en-GB Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US, en-GB MIME-Version: 1.0 X-Virus-Scanned: by iCritical at engine03-20433-11.icritical.com Subject: [MirageOS-devel] C++ library to OCaml: OCaml objects X-BeenThere: mirageos-devel@lists.xenproject.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 am trying to use ctypes to convert a C++ library for use with OCaml. For the most part, I have had some success, but I'm struggling with using an OCaml Object as a representation for the C++ object: let value_id = object method get_command_class_id = foreign "GetCommandClassId" (void @-> returning int) end Above is the object that I would like to use. I feel that this is the easiest way to represent the ValueID in my OCaml code. Next, I wanted to set the type to work with the # notation that OCaml uses for objects. type value_id = < get_command_class_id : int > let value_id : value_id typ = ptr void With this, I am getting an error: Error: This expression has type unit ptr typ but an expression was expected of type value_id typ Type iunit ptr = (unit, [ `C ]) pointer is not compatible with type value_id = < get_command_class_id : int > Does anyone know how I can rectify this issue? My OCaml still isn't that strong, so any feedback is appreciated. Thanks, SteveThis message and any attachment are intended solely for the addressee and may contain confidential information. If you have received this message in error, please send it back to me, and immediately delete it. Please do not use, copy or disclose the information contained in this message or in any attachment. Any views or opinions expressed by the author of this email do not necessarily reflect the views of the University of Nottingham. This message has been checked for viruses but the contents of an attachment may still contain software viruses which could damage your computer system, you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation. _______________________________________________ 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 Jun 20 15:11:37 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 20 Jun 2014 15:11: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 1Wy0TV-0000LC-0v; Fri, 20 Jun 2014 15:11:33 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Wy0TU-0000L7-2g for mirageos-devel@lists.xenproject.org; Fri, 20 Jun 2014 15:11:32 +0000 Received: from [85.158.137.68:15052] by server-8.bemta-3.messagelabs.com id 2E/E4-21547-12F44A35; Fri, 20 Jun 2014 15:11:29 +0000 X-Env-Sender: psxsl6@nottingham.ac.uk X-Msg-Ref: server-16.tower-31.messagelabs.com!1403277088!11383160!1 X-Originating-IP: [93.159.202.117] X-SpamReason: No, hits=0.7 required=7.0 tests=BODY_RANDOM_LONG, MIME_QP_LONG_LINE X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29642 invoked from network); 20 Jun 2014 15:11:28 -0000 Received: from engine03-20433-11.icritical.com (HELO engine03-20433-11.icritical.com) (93.159.202.117) by server-16.tower-31.messagelabs.com with SMTP; 20 Jun 2014 15:11:28 -0000 Received: (qmail 25178 invoked from network); 20 Jun 2014 15:11:54 -0000 Received: from localhost (127.0.0.1) by engine03-20433-11.icritical.com with SMTP; 20 Jun 2014 15:11:54 -0000 Received: from engine03-20433-11.icritical.com ([127.0.0.1]) by localhost (engine03-20433-11.icritical.com [127.0.0.1]) (amavisd-new, port 10024) with SMTP id 24798-07 for ; Fri, 20 Jun 2014 16:11:47 +0100 (BST) Received: (qmail 24641 invoked by uid 599); 20 Jun 2014 15:11:11 -0000 Received: from unknown (HELO smtp4.nottingham.ac.uk) (128.243.220.65) by engine03-20433-11.icritical.com (qpsmtpd/0.28) with ESMTP; Fri, 20 Jun 2014 16:11:11 +0100 Received: from uiwexhub01.ad.nottingham.ac.uk ([128.243.15.133]) by smtp4.nottingham.ac.uk with esmtps (TLSv1:AES128-SHA:128) (Exim 4.77) (envelope-from ) id 1Wy0Sg-0006b8-7T for mirageos-devel@lists.xenproject.org; Fri, 20 Jun 2014 16:10:42 +0100 From: Steven Luland To: "mirageos-devel@lists.xenproject.org" Date: Fri, 20 Jun 2014 16:10:41 +0100 Thread-Topic: C++ library to OCaml: OCaml objects Thread-Index: Ac+MmczQv+xbd/PiTCmgGrEoBxOpzQ== Message-ID: Accept-Language: en-US, en-GB Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US, en-GB MIME-Version: 1.0 X-Virus-Scanned: by iCritical at engine03-20433-11.icritical.com Subject: [MirageOS-devel] C++ library to OCaml: OCaml objects X-BeenThere: mirageos-devel@lists.xenproject.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 am trying to use ctypes to convert a C++ library for use with OCaml. For the most part, I have had some success, but I'm struggling with using an OCaml Object as a representation for the C++ object: let value_id = object method get_command_class_id = foreign "GetCommandClassId" (void @-> returning int) end Above is the object that I would like to use. I feel that this is the easiest way to represent the ValueID in my OCaml code. Next, I wanted to set the type to work with the # notation that OCaml uses for objects. type value_id = < get_command_class_id : int > let value_id : value_id typ = ptr void With this, I am getting an error: Error: This expression has type unit ptr typ but an expression was expected of type value_id typ Type iunit ptr = (unit, [ `C ]) pointer is not compatible with type value_id = < get_command_class_id : int > Does anyone know how I can rectify this issue? My OCaml still isn't that strong, so any feedback is appreciated. Thanks, SteveThis message and any attachment are intended solely for the addressee and may contain confidential information. If you have received this message in error, please send it back to me, and immediately delete it. Please do not use, copy or disclose the information contained in this message or in any attachment. Any views or opinions expressed by the author of this email do not necessarily reflect the views of the University of Nottingham. This message has been checked for viruses but the contents of an attachment may still contain software viruses which could damage your computer system, you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation. _______________________________________________ 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 Jun 20 17:47:57 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 20 Jun 2014 17:47:57 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Wy2uk-0007OQ-8W; Fri, 20 Jun 2014 17:47:50 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Wy2uj-0007OL-Ih for mirageos-devel@lists.xenproject.org; Fri, 20 Jun 2014 17:47:49 +0000 Received: from [193.109.254.147:18597] by server-6.bemta-14.messagelabs.com id E2/C6-13066-4C374A35; Fri, 20 Jun 2014 17:47:48 +0000 X-Env-Sender: jdy22@hermes.cam.ac.uk X-Msg-Ref: server-11.tower-27.messagelabs.com!1403286468!9335278!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.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 26047 invoked from network); 20 Jun 2014 17:47:48 -0000 Received: from ppsw-50.csi.cam.ac.uk (HELO ppsw-50.csi.cam.ac.uk) (131.111.8.150) by server-11.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 20 Jun 2014 17:47:48 -0000 X-Cam-AntiVirus: no malware found X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/ Received: from mail-we0-f180.google.com ([74.125.82.180]:49631) by ppsw-50.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.158]:587) with esmtpsa (PLAIN:jdy22) (TLSv1:RC4-SHA:128) id 1Wy2uh-0007IE-sJ (Exim 4.82_3-c0e5623) for mirageos-devel@lists.xenproject.org (return-path ); Fri, 20 Jun 2014 18:47:47 +0100 Received: by mail-we0-f180.google.com with SMTP id x48so4140528wes.39 for ; Fri, 20 Jun 2014 10:47:47 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.194.86.42 with SMTP id m10mr5018457wjz.132.1403286467639; Fri, 20 Jun 2014 10:47:47 -0700 (PDT) Received: by 10.216.219.193 with HTTP; Fri, 20 Jun 2014 10:47:47 -0700 (PDT) In-Reply-To: References: Date: Fri, 20 Jun 2014 18:47:47 +0100 Message-ID: From: Jeremy Yallop To: Steven Luland Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] C++ library to OCaml: OCaml objects X-BeenThere: mirageos-devel@lists.xenproject.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 Steven, On 20 June 2014 16:10, Steven Luland wrote: > I wanted to set the type to work with the # notation that OCaml uses I find it easier to think about this kind of thing if I separate the code that binds the C++ from the code that gives it a more idiomatic OCaml interface. You then end up with four "layers" with clearly-separated responsibilities: (1) the C++ library itself (object-oriented C++) (2) the 'extern "C"' interface (function-oriented C++) (3) the ctypes bindings (function-oriented OCaml) (4) the OCaml interface (object-oriented OCaml) Here's an example to show what I mean. First, a simple C++ library with a thin 'extern "C"' interface that takes "this" arguments and forwards calls to member functions: $ cat shapes.cc #include struct Shape { virtual double area() = 0; virtual ~Shape() = 0; }; Shape::~Shape() { } struct Square : public Shape { Square(double s) : side(s) { } double area() { return side * side; } ~Square() { } private: double side; }; struct Circle : public Shape { Circle(double r) : radius(r) { } double area() { return M_PI * radius * radius; } ~Circle() { } private: double radius; }; extern "C" { Square *create_Square(double side) { return new Square(side); } void destroy_Square(Square *s) { delete s; } double Square_area(Square* s) { return s->area(); } Circle *create_Circle(double radius) { return new Circle(radius); } void destroy_Circle(Circle *c) { delete c; } double Circle_area(Circle* c) { return c->area(); } } $ g++ -shared -fPIC -ansi -pedantic -W -Wall shapes.cc -o libshapes.so You could also have a header file declaring the extern functions, but let's leave that out for the sake of simplicity, since ctypes.foreign doesn't use it. The next layer uses ctypes to bind the extern "C" functions. This is a fairly straightforward matter of translating the C declaration syntax into the corresponding calls to functions in the ctypes interface. $ cat shape_bindings.ml open Ctypes open Foreign type square type circle let square : square structure typ = structure "Square" let circle : circle structure typ = structure "Circle" let create_Square = foreign "create_Square" (double @-> returning (ptr square)) let destroy_Square = foreign "destroy_Square" (ptr square @-> returning void) let square_area = foreign "Square_area" (ptr square @-> returning double) let create_Circle = foreign "create_Circle" (double @-> returning (ptr circle)) let destroy_Circle = foreign "destroy_Circle" (ptr circle @-> returning void) let circle_area = foreign "Circle_area" (ptr circle @-> returning double); Finally, we can define OCaml classes that forward method calls to the various bound functions. There are various choices, such as how do deal with destructors, that probably need to be made on a per-binding basis. For this example, I've defined an initializer (http://caml.inria.fr/pub/docs/manual-ocaml-400/manual005.html#toc21) in each class that registers the destructor of each object with the garbage collector so that the C++ object is destroyed when the corresponding OCaml object becomes unreachable. I've also made the 'this' member, which is implicit in C++, into an explicit instance variable in the OCaml classes. $ cat shapes.ml class virtual shape = object method virtual area : float end class circle ~radius = object inherit shape val this = Shape_bindings.create_Circle radius method area = Shape_bindings.circle_area this initializer Gc.finalise Shape_bindings.destroy_Circle this end class square ~side = object inherit shape val this = Shape_bindings.create_Square side method area = Shape_bindings.square_area this initializer Gc.finalise Shape_bindings.destroy_Square this end $ ocamlfind ocamlc -linkpkg -custom -package ctypes.foreign \ shape_bindings.ml shapes.ml -cclib -L. -cclib -lshapes To see it all working we can load the library, instantiate the objects, and call methods: $ ocamlfind ocamlmktop -package ctypes.foreign shapes.cma -o shapes.top $ ./shapes.top -short-paths OCaml version 4.01.0 # open Shapes;; # let c = new circle ~radius:5.0;; val c : circle = # let s = new square ~side:10.0;; val s : square = # c#area;; - : float = 78.5398163397448315 # s#area;; - : float = 100. Hope that helps a bit! Jeremy _______________________________________________ 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 Jun 20 17:47:57 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 20 Jun 2014 17:47:57 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Wy2uk-0007OQ-8W; Fri, 20 Jun 2014 17:47:50 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Wy2uj-0007OL-Ih for mirageos-devel@lists.xenproject.org; Fri, 20 Jun 2014 17:47:49 +0000 Received: from [193.109.254.147:18597] by server-6.bemta-14.messagelabs.com id E2/C6-13066-4C374A35; Fri, 20 Jun 2014 17:47:48 +0000 X-Env-Sender: jdy22@hermes.cam.ac.uk X-Msg-Ref: server-11.tower-27.messagelabs.com!1403286468!9335278!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.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 26047 invoked from network); 20 Jun 2014 17:47:48 -0000 Received: from ppsw-50.csi.cam.ac.uk (HELO ppsw-50.csi.cam.ac.uk) (131.111.8.150) by server-11.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 20 Jun 2014 17:47:48 -0000 X-Cam-AntiVirus: no malware found X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/ Received: from mail-we0-f180.google.com ([74.125.82.180]:49631) by ppsw-50.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.158]:587) with esmtpsa (PLAIN:jdy22) (TLSv1:RC4-SHA:128) id 1Wy2uh-0007IE-sJ (Exim 4.82_3-c0e5623) for mirageos-devel@lists.xenproject.org (return-path ); Fri, 20 Jun 2014 18:47:47 +0100 Received: by mail-we0-f180.google.com with SMTP id x48so4140528wes.39 for ; Fri, 20 Jun 2014 10:47:47 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.194.86.42 with SMTP id m10mr5018457wjz.132.1403286467639; Fri, 20 Jun 2014 10:47:47 -0700 (PDT) Received: by 10.216.219.193 with HTTP; Fri, 20 Jun 2014 10:47:47 -0700 (PDT) In-Reply-To: References: Date: Fri, 20 Jun 2014 18:47:47 +0100 Message-ID: From: Jeremy Yallop To: Steven Luland Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] C++ library to OCaml: OCaml objects X-BeenThere: mirageos-devel@lists.xenproject.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 Steven, On 20 June 2014 16:10, Steven Luland wrote: > I wanted to set the type to work with the # notation that OCaml uses I find it easier to think about this kind of thing if I separate the code that binds the C++ from the code that gives it a more idiomatic OCaml interface. You then end up with four "layers" with clearly-separated responsibilities: (1) the C++ library itself (object-oriented C++) (2) the 'extern "C"' interface (function-oriented C++) (3) the ctypes bindings (function-oriented OCaml) (4) the OCaml interface (object-oriented OCaml) Here's an example to show what I mean. First, a simple C++ library with a thin 'extern "C"' interface that takes "this" arguments and forwards calls to member functions: $ cat shapes.cc #include struct Shape { virtual double area() = 0; virtual ~Shape() = 0; }; Shape::~Shape() { } struct Square : public Shape { Square(double s) : side(s) { } double area() { return side * side; } ~Square() { } private: double side; }; struct Circle : public Shape { Circle(double r) : radius(r) { } double area() { return M_PI * radius * radius; } ~Circle() { } private: double radius; }; extern "C" { Square *create_Square(double side) { return new Square(side); } void destroy_Square(Square *s) { delete s; } double Square_area(Square* s) { return s->area(); } Circle *create_Circle(double radius) { return new Circle(radius); } void destroy_Circle(Circle *c) { delete c; } double Circle_area(Circle* c) { return c->area(); } } $ g++ -shared -fPIC -ansi -pedantic -W -Wall shapes.cc -o libshapes.so You could also have a header file declaring the extern functions, but let's leave that out for the sake of simplicity, since ctypes.foreign doesn't use it. The next layer uses ctypes to bind the extern "C" functions. This is a fairly straightforward matter of translating the C declaration syntax into the corresponding calls to functions in the ctypes interface. $ cat shape_bindings.ml open Ctypes open Foreign type square type circle let square : square structure typ = structure "Square" let circle : circle structure typ = structure "Circle" let create_Square = foreign "create_Square" (double @-> returning (ptr square)) let destroy_Square = foreign "destroy_Square" (ptr square @-> returning void) let square_area = foreign "Square_area" (ptr square @-> returning double) let create_Circle = foreign "create_Circle" (double @-> returning (ptr circle)) let destroy_Circle = foreign "destroy_Circle" (ptr circle @-> returning void) let circle_area = foreign "Circle_area" (ptr circle @-> returning double); Finally, we can define OCaml classes that forward method calls to the various bound functions. There are various choices, such as how do deal with destructors, that probably need to be made on a per-binding basis. For this example, I've defined an initializer (http://caml.inria.fr/pub/docs/manual-ocaml-400/manual005.html#toc21) in each class that registers the destructor of each object with the garbage collector so that the C++ object is destroyed when the corresponding OCaml object becomes unreachable. I've also made the 'this' member, which is implicit in C++, into an explicit instance variable in the OCaml classes. $ cat shapes.ml class virtual shape = object method virtual area : float end class circle ~radius = object inherit shape val this = Shape_bindings.create_Circle radius method area = Shape_bindings.circle_area this initializer Gc.finalise Shape_bindings.destroy_Circle this end class square ~side = object inherit shape val this = Shape_bindings.create_Square side method area = Shape_bindings.square_area this initializer Gc.finalise Shape_bindings.destroy_Square this end $ ocamlfind ocamlc -linkpkg -custom -package ctypes.foreign \ shape_bindings.ml shapes.ml -cclib -L. -cclib -lshapes To see it all working we can load the library, instantiate the objects, and call methods: $ ocamlfind ocamlmktop -package ctypes.foreign shapes.cma -o shapes.top $ ./shapes.top -short-paths OCaml version 4.01.0 # open Shapes;; # let c = new circle ~radius:5.0;; val c : circle = # let s = new square ~side:10.0;; val s : square = # c#area;; - : float = 78.5398163397448315 # s#area;; - : float = 100. Hope that helps a bit! Jeremy _______________________________________________ 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 Jun 20 19:50:15 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 20 Jun 2014 19:50: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 1Wy4p9-00046C-EL; Fri, 20 Jun 2014 19:50:11 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Wy4p7-000460-RS for mirageos-devel@lists.xenproject.org; Fri, 20 Jun 2014 19:50:10 +0000 Received: from [85.158.137.68:12640] by server-12.bemta-3.messagelabs.com id 62/CE-12714-17094A35; Fri, 20 Jun 2014 19:50:09 +0000 X-Env-Sender: Richard.Mortier@nottingham.ac.uk X-Msg-Ref: server-9.tower-31.messagelabs.com!1403293808!7687129!1 X-Originating-IP: [93.159.202.53] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6219 invoked from network); 20 Jun 2014 19:50:08 -0000 Received: from engine03-20433-10.icritical.com (HELO engine03-20433-10.icritical.com) (93.159.202.53) by server-9.tower-31.messagelabs.com with SMTP; 20 Jun 2014 19:50:08 -0000 Received: (qmail 22971 invoked from network); 20 Jun 2014 19:50:03 -0000 Received: from localhost (127.0.0.1) by engine03-20433-10.icritical.com with SMTP; 20 Jun 2014 19:50:03 -0000 Received: from engine03-20433-10.icritical.com ([127.0.0.1]) by localhost (engine03-20433-10.icritical.com [127.0.0.1]) (amavisd-new, port 10024) with SMTP id 22617-07 for ; Fri, 20 Jun 2014 20:50:03 +0100 (BST) Received: (qmail 22538 invoked by uid 599); 20 Jun 2014 19:49:28 -0000 Received: from unknown (HELO smtp3.nottingham.ac.uk) (128.243.44.55) by engine03-20433-10.icritical.com (qpsmtpd/0.28) with ESMTP; Fri, 20 Jun 2014 20:49:28 +0100 Received: from uiwexhub01.ad.nottingham.ac.uk ([128.243.15.133]) by smtp3.nottingham.ac.uk with esmtps (TLSv1:AES128-SHA:128) (Exim 4.77) (envelope-from ) id 1Wy4oS-000896-IU; Fri, 20 Jun 2014 20:49:28 +0100 From: Richard Mortier To: David Scott , Anil Madhavapeddy Date: Fri, 20 Jun 2014 20:49:26 +0100 Thread-Topic: [MirageOS-devel] towards a common Mirage 'FLOW' signature Thread-Index: Ac+MwL5ncWWd56PNRL+2yDINauR03A== Message-ID: References: <1233494D-A05A-4F52-BFE7-9773BD566372@gazagnaire.org> <2C06C3FC-F8F3-4FC4-A7F9-BCD1A2FADE94@recoil.org> In-Reply-To: <2C06C3FC-F8F3-4FC4-A7F9-BCD1A2FADE94@recoil.org> Accept-Language: en-US, en-GB Content-Language: en-US X-MS-Has-Attach: yes X-MS-TNEF-Correlator: acceptlanguage: en-US, en-GB MIME-Version: 1.0 X-Virus-Scanned: by iCritical at engine03-20433-10.icritical.com Cc: Thomas Gazagnaire , Jon Ludlam , "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] towards a common Mirage 'FLOW' signature X-BeenThere: mirageos-devel@lists.xenproject.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="===============7059327769552046616==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============7059327769552046616== Content-Language: en-US Content-Type: multipart/signed; boundary="Apple-Mail=_8F023039-0154-42C1-9BA0-67F144CAF3F8"; protocol="application/pgp-signature"; micalg=pgp-sha512 --Apple-Mail=_8F023039-0154-42C1-9BA0-67F144CAF3F8 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On 18 Jun 2014, at 21:21, Anil Madhavapeddy wrote: > On 18 Jun 2014, at 18:46, David Scott wrote: >=20 >> More stuff to think about for v2: the 'shared-memory-ring' code = exposes more detail. It's possible to 'read' data without acknowledging = it, such that it'll still be there if you crash and restart. apologies for not knowing the ring api better -- do you mean it will = always be there in this case, or it will be there unless the "sender" = has overwritten it? >> This is a bit like TCP retransmitting data you haven't ACKed. We = could expose this somewhere. Also, each FLOW probably has some amount of = buffering built-into it, for example vchan is limited by the size of the = ring set at create time. Perhaps that could be exposed? If a particular = FLOW implementation is prepared to allocate buffers it would be good to = be able to control that, and apply back pressure etc. Perhaps we could = draw some inspiration from somewhere-- JS core's pipes maybe? >=20 > Hm, the point of FLOWs is that they shouldn't have buffering, and = that's in the CHANNEL type instead. Having said that, some buffering of = in-flight requests is of course inescapable, ...given that, how should a FLOW end up differing from a CHANNEL in = practice? is it simply the amount of buffering allowed, in which case = isn't this an application level decision? or is it who allocates and = manages those buffers? > and we could expose TCP buffers or the vchan ring size. What use = would this information be to an application, though? if i'm following this correctly, couldn't the application use this to do = things like customise TCP congestion control behaviour by fiddling with = the receive window?=20 --=20 Cheers, R. --Apple-Mail=_8F023039-0154-42C1-9BA0-67F144CAF3F8 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="signature.asc" Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJTpJBGAAoJEOLF27JWwSg3onwP/AsMLDqpNzTxQ/7GCqWcxboS M8f6EklHeU4PFQacLAHwirMNNO2jtqv3eRUmHWWY7ZlFPKDltdl1/vFdjuufghI7 Nr/vkbaFYt/Gh2BdYHisDByDHAxgqe3swLPm8aBkmv4wEcFWfxG6ZeJQgqybkfax QlFPhQrpbs96S/I1mjOVDfcKEAqE0f7WH28Oatwn3IARmU9arCqkqapXwgjfTp3q 0cPnXKi1vdid/adN3vxow85VT1VrtqOOHpX/JV1QsCtHTlTtqbbPuFXfguVFQKtg FB7mC4gk8Zl3Y6CcoE9fdJKICG0z26ej5GnW16RMcLN5Ma2AlFnWqYCKT5E8Lu5v hVraabfkjGumIpxwH291t0hfdPjfsAiCSr7uJoOHF7WcgirCD5JpnLN+2GNRwjF0 /Eu27EZz6YTs9TpT1hlXAT+SouKILgS/FHy6A0gP80mV6ekUUrHMjknMbyoJZDo3 TLPo3yxZQJUVQ/Tl70O80/IvK48NLhxSz4k4R8EiLXwkdCEcQso6iN69jckkwR/t 0kklx0LALFZYavCkapufTZ4IbMueJ/Y8/tc2ZNl6yrU5VOFWOb4h7ulz1f+GDAf5 7C3+6RyCJ+IU7SgE86pTjicG7XtKkuwKGiP+JDUc/CKW1mgvvUb0bJnDmWP8Hm7J XByKhiCHbqlM/UwEzyPc =B/OM -----END PGP SIGNATURE----- --Apple-Mail=_8F023039-0154-42C1-9BA0-67F144CAF3F8-- --===============7059327769552046616== 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 --===============7059327769552046616==-- From mirageos-devel-bounces@lists.xenproject.org Fri Jun 20 19:50:15 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 20 Jun 2014 19:50: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 1Wy4p9-00046C-EL; Fri, 20 Jun 2014 19:50:11 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Wy4p7-000460-RS for mirageos-devel@lists.xenproject.org; Fri, 20 Jun 2014 19:50:10 +0000 Received: from [85.158.137.68:12640] by server-12.bemta-3.messagelabs.com id 62/CE-12714-17094A35; Fri, 20 Jun 2014 19:50:09 +0000 X-Env-Sender: Richard.Mortier@nottingham.ac.uk X-Msg-Ref: server-9.tower-31.messagelabs.com!1403293808!7687129!1 X-Originating-IP: [93.159.202.53] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6219 invoked from network); 20 Jun 2014 19:50:08 -0000 Received: from engine03-20433-10.icritical.com (HELO engine03-20433-10.icritical.com) (93.159.202.53) by server-9.tower-31.messagelabs.com with SMTP; 20 Jun 2014 19:50:08 -0000 Received: (qmail 22971 invoked from network); 20 Jun 2014 19:50:03 -0000 Received: from localhost (127.0.0.1) by engine03-20433-10.icritical.com with SMTP; 20 Jun 2014 19:50:03 -0000 Received: from engine03-20433-10.icritical.com ([127.0.0.1]) by localhost (engine03-20433-10.icritical.com [127.0.0.1]) (amavisd-new, port 10024) with SMTP id 22617-07 for ; Fri, 20 Jun 2014 20:50:03 +0100 (BST) Received: (qmail 22538 invoked by uid 599); 20 Jun 2014 19:49:28 -0000 Received: from unknown (HELO smtp3.nottingham.ac.uk) (128.243.44.55) by engine03-20433-10.icritical.com (qpsmtpd/0.28) with ESMTP; Fri, 20 Jun 2014 20:49:28 +0100 Received: from uiwexhub01.ad.nottingham.ac.uk ([128.243.15.133]) by smtp3.nottingham.ac.uk with esmtps (TLSv1:AES128-SHA:128) (Exim 4.77) (envelope-from ) id 1Wy4oS-000896-IU; Fri, 20 Jun 2014 20:49:28 +0100 From: Richard Mortier To: David Scott , Anil Madhavapeddy Date: Fri, 20 Jun 2014 20:49:26 +0100 Thread-Topic: [MirageOS-devel] towards a common Mirage 'FLOW' signature Thread-Index: Ac+MwL5ncWWd56PNRL+2yDINauR03A== Message-ID: References: <1233494D-A05A-4F52-BFE7-9773BD566372@gazagnaire.org> <2C06C3FC-F8F3-4FC4-A7F9-BCD1A2FADE94@recoil.org> In-Reply-To: <2C06C3FC-F8F3-4FC4-A7F9-BCD1A2FADE94@recoil.org> Accept-Language: en-US, en-GB Content-Language: en-US X-MS-Has-Attach: yes X-MS-TNEF-Correlator: acceptlanguage: en-US, en-GB MIME-Version: 1.0 X-Virus-Scanned: by iCritical at engine03-20433-10.icritical.com Cc: Thomas Gazagnaire , Jon Ludlam , "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] towards a common Mirage 'FLOW' signature X-BeenThere: mirageos-devel@lists.xenproject.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="===============7059327769552046616==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============7059327769552046616== Content-Language: en-US Content-Type: multipart/signed; boundary="Apple-Mail=_8F023039-0154-42C1-9BA0-67F144CAF3F8"; protocol="application/pgp-signature"; micalg=pgp-sha512 --Apple-Mail=_8F023039-0154-42C1-9BA0-67F144CAF3F8 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On 18 Jun 2014, at 21:21, Anil Madhavapeddy wrote: > On 18 Jun 2014, at 18:46, David Scott wrote: >=20 >> More stuff to think about for v2: the 'shared-memory-ring' code = exposes more detail. It's possible to 'read' data without acknowledging = it, such that it'll still be there if you crash and restart. apologies for not knowing the ring api better -- do you mean it will = always be there in this case, or it will be there unless the "sender" = has overwritten it? >> This is a bit like TCP retransmitting data you haven't ACKed. We = could expose this somewhere. Also, each FLOW probably has some amount of = buffering built-into it, for example vchan is limited by the size of the = ring set at create time. Perhaps that could be exposed? If a particular = FLOW implementation is prepared to allocate buffers it would be good to = be able to control that, and apply back pressure etc. Perhaps we could = draw some inspiration from somewhere-- JS core's pipes maybe? >=20 > Hm, the point of FLOWs is that they shouldn't have buffering, and = that's in the CHANNEL type instead. Having said that, some buffering of = in-flight requests is of course inescapable, ...given that, how should a FLOW end up differing from a CHANNEL in = practice? is it simply the amount of buffering allowed, in which case = isn't this an application level decision? or is it who allocates and = manages those buffers? > and we could expose TCP buffers or the vchan ring size. What use = would this information be to an application, though? if i'm following this correctly, couldn't the application use this to do = things like customise TCP congestion control behaviour by fiddling with = the receive window?=20 --=20 Cheers, R. --Apple-Mail=_8F023039-0154-42C1-9BA0-67F144CAF3F8 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="signature.asc" Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJTpJBGAAoJEOLF27JWwSg3onwP/AsMLDqpNzTxQ/7GCqWcxboS M8f6EklHeU4PFQacLAHwirMNNO2jtqv3eRUmHWWY7ZlFPKDltdl1/vFdjuufghI7 Nr/vkbaFYt/Gh2BdYHisDByDHAxgqe3swLPm8aBkmv4wEcFWfxG6ZeJQgqybkfax QlFPhQrpbs96S/I1mjOVDfcKEAqE0f7WH28Oatwn3IARmU9arCqkqapXwgjfTp3q 0cPnXKi1vdid/adN3vxow85VT1VrtqOOHpX/JV1QsCtHTlTtqbbPuFXfguVFQKtg FB7mC4gk8Zl3Y6CcoE9fdJKICG0z26ej5GnW16RMcLN5Ma2AlFnWqYCKT5E8Lu5v hVraabfkjGumIpxwH291t0hfdPjfsAiCSr7uJoOHF7WcgirCD5JpnLN+2GNRwjF0 /Eu27EZz6YTs9TpT1hlXAT+SouKILgS/FHy6A0gP80mV6ekUUrHMjknMbyoJZDo3 TLPo3yxZQJUVQ/Tl70O80/IvK48NLhxSz4k4R8EiLXwkdCEcQso6iN69jckkwR/t 0kklx0LALFZYavCkapufTZ4IbMueJ/Y8/tc2ZNl6yrU5VOFWOb4h7ulz1f+GDAf5 7C3+6RyCJ+IU7SgE86pTjicG7XtKkuwKGiP+JDUc/CKW1mgvvUb0bJnDmWP8Hm7J XByKhiCHbqlM/UwEzyPc =B/OM -----END PGP SIGNATURE----- --Apple-Mail=_8F023039-0154-42C1-9BA0-67F144CAF3F8-- --===============7059327769552046616== 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 --===============7059327769552046616==-- From mirageos-devel-bounces@lists.xenproject.org Fri Jun 20 20:19:38 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 20 Jun 2014 20:19: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 1Wy5Hd-0004sH-0n; Fri, 20 Jun 2014 20:19:37 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Wy5Hb-0004sC-7M for mirageos-devel@lists.xenproject.org; Fri, 20 Jun 2014 20:19:35 +0000 Received: from [193.109.254.147:37531] by server-4.bemta-14.messagelabs.com id 05/40-02781-65794A35; Fri, 20 Jun 2014 20:19:34 +0000 X-Env-Sender: Richard.Mortier@nottingham.ac.uk X-Msg-Ref: server-11.tower-27.messagelabs.com!1403295573!9352572!1 X-Originating-IP: [93.159.202.53] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16284 invoked from network); 20 Jun 2014 20:19:33 -0000 Received: from engine03-20433-10.icritical.com (HELO engine03-20433-10.icritical.com) (93.159.202.53) by server-11.tower-27.messagelabs.com with SMTP; 20 Jun 2014 20:19:33 -0000 Received: (qmail 3554 invoked from network); 20 Jun 2014 20:19:25 -0000 Received: from localhost (127.0.0.1) by engine03-20433-10.icritical.com with SMTP; 20 Jun 2014 20:19:25 -0000 Received: from engine03-20433-10.icritical.com ([127.0.0.1]) by localhost (engine03-20433-10.icritical.com [127.0.0.1]) (amavisd-new, port 10024) with SMTP id 02858-05 for ; Fri, 20 Jun 2014 21:19:18 +0100 (BST) Received: (qmail 3532 invoked by uid 599); 20 Jun 2014 20:19:18 -0000 Received: from unknown (HELO smtp3.nottingham.ac.uk) (128.243.44.55) by engine03-20433-10.icritical.com (qpsmtpd/0.28) with ESMTP; Fri, 20 Jun 2014 21:19:18 +0100 Received: from uiwexhub02.ad.nottingham.ac.uk ([128.243.15.132]) by smtp3.nottingham.ac.uk with esmtps (TLSv1:AES128-SHA:128) (Exim 4.77) (envelope-from ) id 1Wy5HP-00009y-Cv; Fri, 20 Jun 2014 21:19:23 +0100 From: Richard Mortier To: Anil Madhavapeddy Date: Fri, 20 Jun 2014 21:19:21 +0100 Thread-Topic: [MirageOS-devel] towards a common Mirage 'FLOW' signature Thread-Index: Ac+MxOxqPVieKH9GSmSN2hEYgMH2hw== Message-ID: <73296C04-0B84-4CEF-9764-EC4F8A8E8E96@nottingham.ac.uk> References: <819892F4-DE76-4CF3-A988-85675A41E650@nottingham.ac.uk> In-Reply-To: Accept-Language: en-US, en-GB Content-Language: en-US X-MS-Has-Attach: yes X-MS-TNEF-Correlator: acceptlanguage: en-US, en-GB MIME-Version: 1.0 X-Virus-Scanned: by iCritical at engine03-20433-10.icritical.com Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] towards a common Mirage 'FLOW' signature X-BeenThere: mirageos-devel@lists.xenproject.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="===============7764640195132293135==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============7764640195132293135== Content-Language: en-US Content-Type: multipart/signed; boundary="Apple-Mail=_A05FF50B-2032-44D0-94A7-700E196E3DB4"; protocol="application/pgp-signature"; micalg=pgp-sha512 --Apple-Mail=_A05FF50B-2032-44D0-94A7-700E196E3DB4 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On 16 Jun 2014, at 10:23, Anil Madhavapeddy wrote: > On 16 Jun 2014, at 09:55, Richard Mortier = wrote: >=20 >> i generally like the idea of doing something other than an ad hoc = collection of callbacks. >>=20 >> how would the scheme above handle recursive protocols (IP-in-IP etc)? >=20 > You would narrow the buffer by classifying it, generating a sub-view, = and making that a FLOW again. I don't think that this interface should = concern itself with doing a deep packet inspection, unless I'm missing = something? i guess what i mean is i'm (still, after years) not clear on the = relationship between a FLOW and the demultiplexing of protocols. or does = every layer of the stack effectively allow a FLOW to be read from so = that at the lowest layer every read might return a new ethernet frame, = at a layer above that you might get an IP packet per read, at the layer = above that you might get a chunk of data off a TCP connection bearing no = relationship to the underlying TCP segmentation? or you'd get a TCP = segment every time? >> (probably irrelevant but fwiw: i tried doing something a little like = this with the pcap code -- so there was a set of default "demux" = functions but you could override them all to construct your own protocol = demux dag.) >=20 > Got a pointer? Should make sure the two are compatible. it's still half assed but fwiw: https://github.com/mor1/ocaml-pcap --=20 Cheers, R. --Apple-Mail=_A05FF50B-2032-44D0-94A7-700E196E3DB4 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="signature.asc" Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJTpJdKAAoJEOLF27JWwSg3xvIP/jt/ZyXRIsXWCGlJQbSuHD8R yvuztQ5UStpgC9/UkYG1amUeign42/CmQF4+XMJnckSyzBJ7Xfxy6dIxkGo/jZ/n iljdjoduPEofgZrny98fq2uBbB/t3O+MIgfZVRBNi8LRBCb0EeKEF3xAk2yviH9q rYwpk4wzrsWm9kVm8H/R0z7eONqM/XwH0AY2Qgbanl5ud0zQXDgwokGoEMEnnHTx G9+FjNgfgoabI1v08qASWUfCKpr9ExSscKuUPH98u/4/FWWrtP9+sKlE0tbowUEI xpiApdoAe1VwBfHVqVAdngbnbkjHquhrgitINgXZ1iguAMy3ARUNdUJkW1oaD/V0 KOaLUA02qpkXSjyW9i9cN9q2xy+HcNUbPDrHqpaQVUbcKDujzg17I42LSsk65vi4 4hOcbTOLgaOtzFGdEbITQExKdkCL1cKV6T7x5SW8MGpCsfDrJClNyluF1liZRqEb KkF2dB47XmHs/TpTh8ddakE7oBrcQF8RRaLeZCIe3q1AuvrcVpqMlvY7wazSPVX1 ZZRwOlNlRzOK0BOazfyZFAlSaE7nWWDXIRigCQI7jev5kccs0W4d4iIYkHcT7H0m n1DV7OVB4gyNGCZWKcNQV5SDYuptTqxo4aB1ddIk0lrYIdV8EgVFsqwu2CdFf7tw bCCfRJs7xhNTF6BmmHtn =+U+P -----END PGP SIGNATURE----- --Apple-Mail=_A05FF50B-2032-44D0-94A7-700E196E3DB4-- --===============7764640195132293135== 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 --===============7764640195132293135==-- From mirageos-devel-bounces@lists.xenproject.org Fri Jun 20 20:19:38 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 20 Jun 2014 20:19: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 1Wy5Hd-0004sH-0n; Fri, 20 Jun 2014 20:19:37 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Wy5Hb-0004sC-7M for mirageos-devel@lists.xenproject.org; Fri, 20 Jun 2014 20:19:35 +0000 Received: from [193.109.254.147:37531] by server-4.bemta-14.messagelabs.com id 05/40-02781-65794A35; Fri, 20 Jun 2014 20:19:34 +0000 X-Env-Sender: Richard.Mortier@nottingham.ac.uk X-Msg-Ref: server-11.tower-27.messagelabs.com!1403295573!9352572!1 X-Originating-IP: [93.159.202.53] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16284 invoked from network); 20 Jun 2014 20:19:33 -0000 Received: from engine03-20433-10.icritical.com (HELO engine03-20433-10.icritical.com) (93.159.202.53) by server-11.tower-27.messagelabs.com with SMTP; 20 Jun 2014 20:19:33 -0000 Received: (qmail 3554 invoked from network); 20 Jun 2014 20:19:25 -0000 Received: from localhost (127.0.0.1) by engine03-20433-10.icritical.com with SMTP; 20 Jun 2014 20:19:25 -0000 Received: from engine03-20433-10.icritical.com ([127.0.0.1]) by localhost (engine03-20433-10.icritical.com [127.0.0.1]) (amavisd-new, port 10024) with SMTP id 02858-05 for ; Fri, 20 Jun 2014 21:19:18 +0100 (BST) Received: (qmail 3532 invoked by uid 599); 20 Jun 2014 20:19:18 -0000 Received: from unknown (HELO smtp3.nottingham.ac.uk) (128.243.44.55) by engine03-20433-10.icritical.com (qpsmtpd/0.28) with ESMTP; Fri, 20 Jun 2014 21:19:18 +0100 Received: from uiwexhub02.ad.nottingham.ac.uk ([128.243.15.132]) by smtp3.nottingham.ac.uk with esmtps (TLSv1:AES128-SHA:128) (Exim 4.77) (envelope-from ) id 1Wy5HP-00009y-Cv; Fri, 20 Jun 2014 21:19:23 +0100 From: Richard Mortier To: Anil Madhavapeddy Date: Fri, 20 Jun 2014 21:19:21 +0100 Thread-Topic: [MirageOS-devel] towards a common Mirage 'FLOW' signature Thread-Index: Ac+MxOxqPVieKH9GSmSN2hEYgMH2hw== Message-ID: <73296C04-0B84-4CEF-9764-EC4F8A8E8E96@nottingham.ac.uk> References: <819892F4-DE76-4CF3-A988-85675A41E650@nottingham.ac.uk> In-Reply-To: Accept-Language: en-US, en-GB Content-Language: en-US X-MS-Has-Attach: yes X-MS-TNEF-Correlator: acceptlanguage: en-US, en-GB MIME-Version: 1.0 X-Virus-Scanned: by iCritical at engine03-20433-10.icritical.com Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] towards a common Mirage 'FLOW' signature X-BeenThere: mirageos-devel@lists.xenproject.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="===============7764640195132293135==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============7764640195132293135== Content-Language: en-US Content-Type: multipart/signed; boundary="Apple-Mail=_A05FF50B-2032-44D0-94A7-700E196E3DB4"; protocol="application/pgp-signature"; micalg=pgp-sha512 --Apple-Mail=_A05FF50B-2032-44D0-94A7-700E196E3DB4 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On 16 Jun 2014, at 10:23, Anil Madhavapeddy wrote: > On 16 Jun 2014, at 09:55, Richard Mortier = wrote: >=20 >> i generally like the idea of doing something other than an ad hoc = collection of callbacks. >>=20 >> how would the scheme above handle recursive protocols (IP-in-IP etc)? >=20 > You would narrow the buffer by classifying it, generating a sub-view, = and making that a FLOW again. I don't think that this interface should = concern itself with doing a deep packet inspection, unless I'm missing = something? i guess what i mean is i'm (still, after years) not clear on the = relationship between a FLOW and the demultiplexing of protocols. or does = every layer of the stack effectively allow a FLOW to be read from so = that at the lowest layer every read might return a new ethernet frame, = at a layer above that you might get an IP packet per read, at the layer = above that you might get a chunk of data off a TCP connection bearing no = relationship to the underlying TCP segmentation? or you'd get a TCP = segment every time? >> (probably irrelevant but fwiw: i tried doing something a little like = this with the pcap code -- so there was a set of default "demux" = functions but you could override them all to construct your own protocol = demux dag.) >=20 > Got a pointer? Should make sure the two are compatible. it's still half assed but fwiw: https://github.com/mor1/ocaml-pcap --=20 Cheers, R. --Apple-Mail=_A05FF50B-2032-44D0-94A7-700E196E3DB4 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="signature.asc" Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJTpJdKAAoJEOLF27JWwSg3xvIP/jt/ZyXRIsXWCGlJQbSuHD8R yvuztQ5UStpgC9/UkYG1amUeign42/CmQF4+XMJnckSyzBJ7Xfxy6dIxkGo/jZ/n iljdjoduPEofgZrny98fq2uBbB/t3O+MIgfZVRBNi8LRBCb0EeKEF3xAk2yviH9q rYwpk4wzrsWm9kVm8H/R0z7eONqM/XwH0AY2Qgbanl5ud0zQXDgwokGoEMEnnHTx G9+FjNgfgoabI1v08qASWUfCKpr9ExSscKuUPH98u/4/FWWrtP9+sKlE0tbowUEI xpiApdoAe1VwBfHVqVAdngbnbkjHquhrgitINgXZ1iguAMy3ARUNdUJkW1oaD/V0 KOaLUA02qpkXSjyW9i9cN9q2xy+HcNUbPDrHqpaQVUbcKDujzg17I42LSsk65vi4 4hOcbTOLgaOtzFGdEbITQExKdkCL1cKV6T7x5SW8MGpCsfDrJClNyluF1liZRqEb KkF2dB47XmHs/TpTh8ddakE7oBrcQF8RRaLeZCIe3q1AuvrcVpqMlvY7wazSPVX1 ZZRwOlNlRzOK0BOazfyZFAlSaE7nWWDXIRigCQI7jev5kccs0W4d4iIYkHcT7H0m n1DV7OVB4gyNGCZWKcNQV5SDYuptTqxo4aB1ddIk0lrYIdV8EgVFsqwu2CdFf7tw bCCfRJs7xhNTF6BmmHtn =+U+P -----END PGP SIGNATURE----- --Apple-Mail=_A05FF50B-2032-44D0-94A7-700E196E3DB4-- --===============7764640195132293135== 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 --===============7764640195132293135==-- From mirageos-devel-bounces@lists.xenproject.org Fri Jun 20 20:19:41 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 20 Jun 2014 20:19: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 1Wy5Hh-0004sl-3Q; Fri, 20 Jun 2014 20:19:41 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Wy5Hf-0004sb-Kd for mirageos-devel@lists.xenproject.org; Fri, 20 Jun 2014 20:19:39 +0000 Received: from [193.109.254.147:43241] by server-6.bemta-14.messagelabs.com id FB/30-13066-A5794A35; Fri, 20 Jun 2014 20:19:38 +0000 X-Env-Sender: Dave.Scott@citrix.com X-Msg-Ref: server-6.tower-27.messagelabs.com!1403295577!12675374!1 X-Originating-IP: [185.25.65.24] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 938 invoked from network); 20 Jun 2014 20:19:37 -0000 Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (185.25.65.24) by server-6.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 20 Jun 2014 20:19:37 -0000 X-IronPort-AV: E=Sophos;i="5.01,516,1400025600"; d="scan'208";a="21726218" Received: from unknown (HELO AMSPEX01CL02.citrite.net) ([10.69.60.9]) by AMSPIP01.EU.Citrix.com with ESMTP; 20 Jun 2014 20:19:37 +0000 Received: from AMSPEX01CL03.citrite.net ([169.254.8.89]) by AMSPEX01CL02.citrite.net ([10.69.46.33]) with mapi id 14.03.0181.006; Fri, 20 Jun 2014 22:19:37 +0200 From: Dave Scott To: Richard Mortier Thread-Topic: [MirageOS-devel] towards a common Mirage 'FLOW' signature Thread-Index: AQHPhn5se25anOhs8kKSi+zLRqL4cJtzXYSAgAOugoCAACstgIADG8QAgAAIawA= Date: Fri, 20 Jun 2014 20:19:35 +0000 Message-ID: References: <1233494D-A05A-4F52-BFE7-9773BD566372@gazagnaire.org> <2C06C3FC-F8F3-4FC4-A7F9-BCD1A2FADE94@recoil.org> In-Reply-To: Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.13.112.14] Content-ID: <05BFE7C1CABB6849B3853521AD15D169@citrix.com> MIME-Version: 1.0 X-DLP: AMS1 Cc: Jonathan Ludlam , Thomas Gazagnaire , "mirageos-devel@lists.xenproject.org" , Anil Madhavapeddy Subject: Re: [MirageOS-devel] towards a common Mirage 'FLOW' signature X-BeenThere: mirageos-devel@lists.xenproject.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 20 Jun 2014, at 20:49, Richard Mortier wrote: > = > On 18 Jun 2014, at 21:21, Anil Madhavapeddy wrote: > = >> On 18 Jun 2014, at 18:46, David Scott wrote: >> = >>> More stuff to think about for v2: the 'shared-memory-ring' code exposes= more detail. It's possible to 'read' data without acknowledging it, such t= hat it'll still be there if you crash and restart. > = > apologies for not knowing the ring api better -- do you mean it will alwa= ys be there in this case, or it will be there unless the "sender" has overw= ritten it? The data has been =91produced=92 (and a producer pointer has been increment= ed) but won=92t be overwritten by the sender until the receiver =91consumes= =92 it (by advancing a consumer pointer). I=92m exploiting this in xenstore= to make sure I never lose data=97 I only advance the consumer pointer when= I=92ve written the data to somewhere persistent. Separately I=92ve seen problems where block writes from VMs have been sent = over NFS/TCP and then the buffers freed, before the TCP ACKs have been rece= ived. Seeing that made me whether ACKing data would be a good thing to expo= se in every FLOW. >>> This is a bit like TCP retransmitting data you haven't ACKed. We could = expose this somewhere. Also, each FLOW probably has some amount of bufferin= g built-into it, for example vchan is limited by the size of the ring set a= t create time. Perhaps that could be exposed? If a particular FLOW implemen= tation is prepared to allocate buffers it would be good to be able to contr= ol that, and apply back pressure etc. Perhaps we could draw some inspiratio= n from somewhere-- JS core's pipes maybe? >> = >> Hm, the point of FLOWs is that they shouldn't have buffering, and that's= in the CHANNEL type instead. Having said that, some buffering of in-fligh= t requests is of course inescapable, > = > ...given that, how should a FLOW end up differing from a CHANNEL in pract= ice? is it simply the amount of buffering allowed, in which case isn't this= an application level decision? or is it who allocates and manages those b= uffers? I think it would help (me anyway) if we could clearly differentiate FLOW an= d CHANNEL. > = >> and we could expose TCP buffers or the vchan ring size. What use would = this information be to an application, though? > = > if i'm following this correctly, couldn't the application use this to do = things like customise TCP congestion control behaviour by fiddling with the= receive window? = Maybe we should start by cataloging our current buffer management and see i= f we can see any nice patterns? We have a nice set of protocols now. Cheers, Dave _______________________________________________ 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 Jun 20 20:19:41 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 20 Jun 2014 20:19: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 1Wy5Hh-0004sl-3Q; Fri, 20 Jun 2014 20:19:41 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Wy5Hf-0004sb-Kd for mirageos-devel@lists.xenproject.org; Fri, 20 Jun 2014 20:19:39 +0000 Received: from [193.109.254.147:43241] by server-6.bemta-14.messagelabs.com id FB/30-13066-A5794A35; Fri, 20 Jun 2014 20:19:38 +0000 X-Env-Sender: Dave.Scott@citrix.com X-Msg-Ref: server-6.tower-27.messagelabs.com!1403295577!12675374!1 X-Originating-IP: [185.25.65.24] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 938 invoked from network); 20 Jun 2014 20:19:37 -0000 Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (185.25.65.24) by server-6.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 20 Jun 2014 20:19:37 -0000 X-IronPort-AV: E=Sophos;i="5.01,516,1400025600"; d="scan'208";a="21726218" Received: from unknown (HELO AMSPEX01CL02.citrite.net) ([10.69.60.9]) by AMSPIP01.EU.Citrix.com with ESMTP; 20 Jun 2014 20:19:37 +0000 Received: from AMSPEX01CL03.citrite.net ([169.254.8.89]) by AMSPEX01CL02.citrite.net ([10.69.46.33]) with mapi id 14.03.0181.006; Fri, 20 Jun 2014 22:19:37 +0200 From: Dave Scott To: Richard Mortier Thread-Topic: [MirageOS-devel] towards a common Mirage 'FLOW' signature Thread-Index: AQHPhn5se25anOhs8kKSi+zLRqL4cJtzXYSAgAOugoCAACstgIADG8QAgAAIawA= Date: Fri, 20 Jun 2014 20:19:35 +0000 Message-ID: References: <1233494D-A05A-4F52-BFE7-9773BD566372@gazagnaire.org> <2C06C3FC-F8F3-4FC4-A7F9-BCD1A2FADE94@recoil.org> In-Reply-To: Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.13.112.14] Content-ID: <05BFE7C1CABB6849B3853521AD15D169@citrix.com> MIME-Version: 1.0 X-DLP: AMS1 Cc: Jonathan Ludlam , Thomas Gazagnaire , "mirageos-devel@lists.xenproject.org" , Anil Madhavapeddy Subject: Re: [MirageOS-devel] towards a common Mirage 'FLOW' signature X-BeenThere: mirageos-devel@lists.xenproject.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 20 Jun 2014, at 20:49, Richard Mortier wrote: > = > On 18 Jun 2014, at 21:21, Anil Madhavapeddy wrote: > = >> On 18 Jun 2014, at 18:46, David Scott wrote: >> = >>> More stuff to think about for v2: the 'shared-memory-ring' code exposes= more detail. It's possible to 'read' data without acknowledging it, such t= hat it'll still be there if you crash and restart. > = > apologies for not knowing the ring api better -- do you mean it will alwa= ys be there in this case, or it will be there unless the "sender" has overw= ritten it? The data has been =91produced=92 (and a producer pointer has been increment= ed) but won=92t be overwritten by the sender until the receiver =91consumes= =92 it (by advancing a consumer pointer). I=92m exploiting this in xenstore= to make sure I never lose data=97 I only advance the consumer pointer when= I=92ve written the data to somewhere persistent. Separately I=92ve seen problems where block writes from VMs have been sent = over NFS/TCP and then the buffers freed, before the TCP ACKs have been rece= ived. Seeing that made me whether ACKing data would be a good thing to expo= se in every FLOW. >>> This is a bit like TCP retransmitting data you haven't ACKed. We could = expose this somewhere. Also, each FLOW probably has some amount of bufferin= g built-into it, for example vchan is limited by the size of the ring set a= t create time. Perhaps that could be exposed? If a particular FLOW implemen= tation is prepared to allocate buffers it would be good to be able to contr= ol that, and apply back pressure etc. Perhaps we could draw some inspiratio= n from somewhere-- JS core's pipes maybe? >> = >> Hm, the point of FLOWs is that they shouldn't have buffering, and that's= in the CHANNEL type instead. Having said that, some buffering of in-fligh= t requests is of course inescapable, > = > ...given that, how should a FLOW end up differing from a CHANNEL in pract= ice? is it simply the amount of buffering allowed, in which case isn't this= an application level decision? or is it who allocates and manages those b= uffers? I think it would help (me anyway) if we could clearly differentiate FLOW an= d CHANNEL. > = >> and we could expose TCP buffers or the vchan ring size. What use would = this information be to an application, though? > = > if i'm following this correctly, couldn't the application use this to do = things like customise TCP congestion control behaviour by fiddling with the= receive window? = Maybe we should start by cataloging our current buffer management and see i= f we can see any nice patterns? We have a nice set of protocols now. Cheers, Dave _______________________________________________ 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 Jun 20 20:37:10 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 20 Jun 2014 20:37: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 1Wy5Ya-00058A-7x; Fri, 20 Jun 2014 20:37:08 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Wy5YT-000585-KD for mirageos-devel@lists.xenproject.org; Fri, 20 Jun 2014 20:37:07 +0000 Received: from [85.158.143.35:35428] by server-3.bemta-4.messagelabs.com id 87/1C-16194-C6B94A35; Fri, 20 Jun 2014 20:37:00 +0000 X-Env-Sender: Richard.Mortier@nottingham.ac.uk X-Msg-Ref: server-12.tower-21.messagelabs.com!1403296620!12790465!1 X-Originating-IP: [195.62.217.150] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTk1LjYyLjIxNy4xNTAgPT4gNzU3Mg==\n X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27836 invoked from network); 20 Jun 2014 20:37:00 -0000 Received: from engine06-20433-6.icritical.com (HELO engine06-20433-6.icritical.com) (195.62.217.150) by server-12.tower-21.messagelabs.com with SMTP; 20 Jun 2014 20:37:00 -0000 Received: (qmail 17388 invoked from network); 20 Jun 2014 20:36:54 -0000 Received: from localhost (127.0.0.1) by engine06-20433-6.icritical.com with SMTP; 20 Jun 2014 20:36:54 -0000 Received: from engine06-20433-6.icritical.com ([127.0.0.1]) by localhost (engine06-20433-6.icritical.com [127.0.0.1]) (amavisd-new, port 10024) with SMTP id 16190-06 for ; Fri, 20 Jun 2014 21:36:46 +0100 (BST) Received: (qmail 17330 invoked by uid 599); 20 Jun 2014 20:36:46 -0000 Received: from unknown (HELO smtp4.nottingham.ac.uk) (128.243.220.65) by engine06-20433-6.icritical.com (qpsmtpd/0.28) with ESMTP; Fri, 20 Jun 2014 21:36:46 +0100 Received: from uiwexhub01.ad.nottingham.ac.uk ([128.243.15.133]) by smtp4.nottingham.ac.uk with esmtps (TLSv1:AES128-SHA:128) (Exim 4.77) (envelope-from ) id 1Wy5YA-00007H-O8; Fri, 20 Jun 2014 21:36:42 +0100 From: Richard Mortier To: Dave Scott Date: Fri, 20 Jun 2014 21:36:41 +0100 Thread-Topic: [MirageOS-devel] towards a common Mirage 'FLOW' signature Thread-Index: Ac+Mx1f1N0Edhb+hR7ySnr/xw3wFXQ== Message-ID: <129A6757-8F0A-4650-9667-B97A1946D6C8@nottingham.ac.uk> References: <1233494D-A05A-4F52-BFE7-9773BD566372@gazagnaire.org> <2C06C3FC-F8F3-4FC4-A7F9-BCD1A2FADE94@recoil.org> In-Reply-To: Accept-Language: en-US, en-GB Content-Language: en-US X-MS-Has-Attach: yes X-MS-TNEF-Correlator: acceptlanguage: en-US, en-GB MIME-Version: 1.0 X-Virus-Scanned: by iCritical at engine06-20433-6.icritical.com Cc: Jonathan Ludlam , Thomas Gazagnaire , "mirageos-devel@lists.xenproject.org" , Anil Madhavapeddy Subject: Re: [MirageOS-devel] towards a common Mirage 'FLOW' signature X-BeenThere: mirageos-devel@lists.xenproject.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="===============8795960147661283003==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============8795960147661283003== Content-Language: en-US Content-Type: multipart/signed; boundary="Apple-Mail=_E7AAA8BA-5F30-42C5-9A0C-4E9ED20D6D9C"; protocol="application/pgp-signature"; micalg=pgp-sha512 --Apple-Mail=_E7AAA8BA-5F30-42C5-9A0C-4E9ED20D6D9C Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 On 20 Jun 2014, at 21:19, Dave Scott wrote: > On 20 Jun 2014, at 20:49, Richard Mortier = wrote: >=20 >> On 18 Jun 2014, at 21:21, Anil Madhavapeddy wrote: >>=20 >>> On 18 Jun 2014, at 18:46, David Scott wrote: >>>=20 >>>> More stuff to think about for v2: the 'shared-memory-ring' code = exposes more detail. It's possible to 'read' data without acknowledging = it, such that it'll still be there if you crash and restart. >>=20 >> apologies for not knowing the ring api better -- do you mean it will = always be there in this case, or it will be there unless the "sender" = has overwritten it? >=20 > The data has been =91produced=92 (and a producer pointer has been = incremented) but won=92t be overwritten by the sender until the receiver = =91consumes=92 it (by advancing a consumer pointer). I=92m exploiting = this in xenstore to make sure I never lose data=97 I only advance the = consumer pointer when I=92ve written the data to somewhere persistent. >=20 > Separately I=92ve seen problems where block writes from VMs have been = sent over NFS/TCP and then the buffers freed, before the TCP ACKs have = been received. Seeing that made me whether ACKing data would be a good = thing to expose in every FLOW. wonder how this would work with the fable magic -- could you end up with = a bad receiver causing sender to block? (though i guess this is solved = by having a clear idea of whether something is an external receiver or = just another module of your server that may have been moved between = physical hosts.) >>> Hm, the point of FLOWs is that they shouldn't have buffering, and = that's in the CHANNEL type instead. Having said that, some buffering of = in-flight requests is of course inescapable, >>=20 >> ...given that, how should a FLOW end up differing from a CHANNEL in = practice? is it simply the amount of buffering allowed, in which case = isn't this an application level decision? or is it who allocates and = manages those buffers? >=20 > I think it would help (me anyway) if we could clearly differentiate = FLOW and CHANNEL. sure; what i meant was, if a FLOW has to have some buffering in anyway, = but it's the presence of buffering that distinguishes CHANNEL from FLOW, = then what's the difference? >>> and we could expose TCP buffers or the vchan ring size. What use = would this information be to an application, though? >>=20 >> if i'm following this correctly, couldn't the application use this to = do things like customise TCP congestion control behaviour by fiddling = with the receive window?=20 >=20 > Maybe we should start by cataloging our current buffer management and = see if we can see any nice patterns? We have a nice set of protocols = now. sounds like a good idea (though how many of them have been stressed = enough to be reasonably sure they're good implementations?) --=20 Cheers, R. --Apple-Mail=_E7AAA8BA-5F30-42C5-9A0C-4E9ED20D6D9C Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="signature.asc" Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJTpJtZAAoJEOLF27JWwSg32rIP/35BMF+nCC6XE0qhc3AfCBud ZmYmi9FKH3y6C4zktHmtGSZGzqBUzB+lB27s19HQRygMaop2v6rbIU/CF0csYGbn 7JPtVFN6NjTsZVnjj1XHWVNrvST4WVZzoTiwruSJBH4ScbmnSAKPLcVPJqnFC0ip pD+kZJRve8++bz7MZ/PIl10FB/7KrqzMQ5l2lwuN9YqkUhL7oUbqReQAZEf0FQRP 4RLtP9JPcnkFPaL+NS5OFPfs1YFM80FGqa0aslF/U/5hw3aAkL2sfT3IUVeyXevP bRg1zHni3j8EOwF5S8KcCMHebXu3ANEoAXFvv85vL0IBkHbIX3VQFbeNcuaP8z11 YhJn9jloL8i26NK0IDin/ZwSaWCKIjGgu2+modRxy+mQoNCW6qcoOs6P+Nr6xKnP mf2WYz4UNo59FZBch31jqwSH261QT6oKPXMLKIWD2OHpDSAZK3cwy/gTMOBtnOW+ xoGnxjtiCGSYc0cIcDiubkN3LQRhLAA/wZMe5y2nAEPXbInoT2nLXoBJCM2TjXFA Xl0fhfXtFtF/bDczI8Y7ZVFKd9/LvL6IadcsuAAXUb0HLdijOADv6bmgGG/6GJqG vofb3cXmULcFMriymcGSeSF9Dg+uyUiff9x03PJhMnRmDCQcKsXLWw2UN69vJ1Vi uCUrpIHiM+QTB3zWsJ8+ =kicC -----END PGP SIGNATURE----- --Apple-Mail=_E7AAA8BA-5F30-42C5-9A0C-4E9ED20D6D9C-- --===============8795960147661283003== 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 --===============8795960147661283003==-- From mirageos-devel-bounces@lists.xenproject.org Fri Jun 20 20:37:10 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 20 Jun 2014 20:37: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 1Wy5Ya-00058A-7x; Fri, 20 Jun 2014 20:37:08 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Wy5YT-000585-KD for mirageos-devel@lists.xenproject.org; Fri, 20 Jun 2014 20:37:07 +0000 Received: from [85.158.143.35:35428] by server-3.bemta-4.messagelabs.com id 87/1C-16194-C6B94A35; Fri, 20 Jun 2014 20:37:00 +0000 X-Env-Sender: Richard.Mortier@nottingham.ac.uk X-Msg-Ref: server-12.tower-21.messagelabs.com!1403296620!12790465!1 X-Originating-IP: [195.62.217.150] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTk1LjYyLjIxNy4xNTAgPT4gNzU3Mg==\n X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27836 invoked from network); 20 Jun 2014 20:37:00 -0000 Received: from engine06-20433-6.icritical.com (HELO engine06-20433-6.icritical.com) (195.62.217.150) by server-12.tower-21.messagelabs.com with SMTP; 20 Jun 2014 20:37:00 -0000 Received: (qmail 17388 invoked from network); 20 Jun 2014 20:36:54 -0000 Received: from localhost (127.0.0.1) by engine06-20433-6.icritical.com with SMTP; 20 Jun 2014 20:36:54 -0000 Received: from engine06-20433-6.icritical.com ([127.0.0.1]) by localhost (engine06-20433-6.icritical.com [127.0.0.1]) (amavisd-new, port 10024) with SMTP id 16190-06 for ; Fri, 20 Jun 2014 21:36:46 +0100 (BST) Received: (qmail 17330 invoked by uid 599); 20 Jun 2014 20:36:46 -0000 Received: from unknown (HELO smtp4.nottingham.ac.uk) (128.243.220.65) by engine06-20433-6.icritical.com (qpsmtpd/0.28) with ESMTP; Fri, 20 Jun 2014 21:36:46 +0100 Received: from uiwexhub01.ad.nottingham.ac.uk ([128.243.15.133]) by smtp4.nottingham.ac.uk with esmtps (TLSv1:AES128-SHA:128) (Exim 4.77) (envelope-from ) id 1Wy5YA-00007H-O8; Fri, 20 Jun 2014 21:36:42 +0100 From: Richard Mortier To: Dave Scott Date: Fri, 20 Jun 2014 21:36:41 +0100 Thread-Topic: [MirageOS-devel] towards a common Mirage 'FLOW' signature Thread-Index: Ac+Mx1f1N0Edhb+hR7ySnr/xw3wFXQ== Message-ID: <129A6757-8F0A-4650-9667-B97A1946D6C8@nottingham.ac.uk> References: <1233494D-A05A-4F52-BFE7-9773BD566372@gazagnaire.org> <2C06C3FC-F8F3-4FC4-A7F9-BCD1A2FADE94@recoil.org> In-Reply-To: Accept-Language: en-US, en-GB Content-Language: en-US X-MS-Has-Attach: yes X-MS-TNEF-Correlator: acceptlanguage: en-US, en-GB MIME-Version: 1.0 X-Virus-Scanned: by iCritical at engine06-20433-6.icritical.com Cc: Jonathan Ludlam , Thomas Gazagnaire , "mirageos-devel@lists.xenproject.org" , Anil Madhavapeddy Subject: Re: [MirageOS-devel] towards a common Mirage 'FLOW' signature X-BeenThere: mirageos-devel@lists.xenproject.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="===============8795960147661283003==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============8795960147661283003== Content-Language: en-US Content-Type: multipart/signed; boundary="Apple-Mail=_E7AAA8BA-5F30-42C5-9A0C-4E9ED20D6D9C"; protocol="application/pgp-signature"; micalg=pgp-sha512 --Apple-Mail=_E7AAA8BA-5F30-42C5-9A0C-4E9ED20D6D9C Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 On 20 Jun 2014, at 21:19, Dave Scott wrote: > On 20 Jun 2014, at 20:49, Richard Mortier = wrote: >=20 >> On 18 Jun 2014, at 21:21, Anil Madhavapeddy wrote: >>=20 >>> On 18 Jun 2014, at 18:46, David Scott wrote: >>>=20 >>>> More stuff to think about for v2: the 'shared-memory-ring' code = exposes more detail. It's possible to 'read' data without acknowledging = it, such that it'll still be there if you crash and restart. >>=20 >> apologies for not knowing the ring api better -- do you mean it will = always be there in this case, or it will be there unless the "sender" = has overwritten it? >=20 > The data has been =91produced=92 (and a producer pointer has been = incremented) but won=92t be overwritten by the sender until the receiver = =91consumes=92 it (by advancing a consumer pointer). I=92m exploiting = this in xenstore to make sure I never lose data=97 I only advance the = consumer pointer when I=92ve written the data to somewhere persistent. >=20 > Separately I=92ve seen problems where block writes from VMs have been = sent over NFS/TCP and then the buffers freed, before the TCP ACKs have = been received. Seeing that made me whether ACKing data would be a good = thing to expose in every FLOW. wonder how this would work with the fable magic -- could you end up with = a bad receiver causing sender to block? (though i guess this is solved = by having a clear idea of whether something is an external receiver or = just another module of your server that may have been moved between = physical hosts.) >>> Hm, the point of FLOWs is that they shouldn't have buffering, and = that's in the CHANNEL type instead. Having said that, some buffering of = in-flight requests is of course inescapable, >>=20 >> ...given that, how should a FLOW end up differing from a CHANNEL in = practice? is it simply the amount of buffering allowed, in which case = isn't this an application level decision? or is it who allocates and = manages those buffers? >=20 > I think it would help (me anyway) if we could clearly differentiate = FLOW and CHANNEL. sure; what i meant was, if a FLOW has to have some buffering in anyway, = but it's the presence of buffering that distinguishes CHANNEL from FLOW, = then what's the difference? >>> and we could expose TCP buffers or the vchan ring size. What use = would this information be to an application, though? >>=20 >> if i'm following this correctly, couldn't the application use this to = do things like customise TCP congestion control behaviour by fiddling = with the receive window?=20 >=20 > Maybe we should start by cataloging our current buffer management and = see if we can see any nice patterns? We have a nice set of protocols = now. sounds like a good idea (though how many of them have been stressed = enough to be reasonably sure they're good implementations?) --=20 Cheers, R. --Apple-Mail=_E7AAA8BA-5F30-42C5-9A0C-4E9ED20D6D9C Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="signature.asc" Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJTpJtZAAoJEOLF27JWwSg32rIP/35BMF+nCC6XE0qhc3AfCBud ZmYmi9FKH3y6C4zktHmtGSZGzqBUzB+lB27s19HQRygMaop2v6rbIU/CF0csYGbn 7JPtVFN6NjTsZVnjj1XHWVNrvST4WVZzoTiwruSJBH4ScbmnSAKPLcVPJqnFC0ip pD+kZJRve8++bz7MZ/PIl10FB/7KrqzMQ5l2lwuN9YqkUhL7oUbqReQAZEf0FQRP 4RLtP9JPcnkFPaL+NS5OFPfs1YFM80FGqa0aslF/U/5hw3aAkL2sfT3IUVeyXevP bRg1zHni3j8EOwF5S8KcCMHebXu3ANEoAXFvv85vL0IBkHbIX3VQFbeNcuaP8z11 YhJn9jloL8i26NK0IDin/ZwSaWCKIjGgu2+modRxy+mQoNCW6qcoOs6P+Nr6xKnP mf2WYz4UNo59FZBch31jqwSH261QT6oKPXMLKIWD2OHpDSAZK3cwy/gTMOBtnOW+ xoGnxjtiCGSYc0cIcDiubkN3LQRhLAA/wZMe5y2nAEPXbInoT2nLXoBJCM2TjXFA Xl0fhfXtFtF/bDczI8Y7ZVFKd9/LvL6IadcsuAAXUb0HLdijOADv6bmgGG/6GJqG vofb3cXmULcFMriymcGSeSF9Dg+uyUiff9x03PJhMnRmDCQcKsXLWw2UN69vJ1Vi uCUrpIHiM+QTB3zWsJ8+ =kicC -----END PGP SIGNATURE----- --Apple-Mail=_E7AAA8BA-5F30-42C5-9A0C-4E9ED20D6D9C-- --===============8795960147661283003== 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 --===============8795960147661283003==-- From mirageos-devel-bounces@lists.xenproject.org Fri Jun 20 22:43:38 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 20 Jun 2014 22:43: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 1Wy7Wv-0001F3-8O; Fri, 20 Jun 2014 22:43:33 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Wy7Wt-0001Ey-Ch for mirageos-devel@lists.xenproject.org; Fri, 20 Jun 2014 22:43:31 +0000 Received: from [85.158.139.211:38226] by server-15.bemta-5.messagelabs.com id 72/1B-19516-219B4A35; Fri, 20 Jun 2014 22:43:30 +0000 X-Env-Sender: yallop@gmail.com X-Msg-Ref: server-9.tower-206.messagelabs.com!1403304210!11155971!1 X-Originating-IP: [209.85.212.169] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4982 invoked from network); 20 Jun 2014 22:43:30 -0000 Received: from mail-wi0-f169.google.com (HELO mail-wi0-f169.google.com) (209.85.212.169) by server-9.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 20 Jun 2014 22:43:30 -0000 Received: by mail-wi0-f169.google.com with SMTP id hi2so1697418wib.0 for ; Fri, 20 Jun 2014 15:43:29 -0700 (PDT) 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=++NwY+OH0mj8tfVSp8OHfaO1nfVyeNropwAz4Z2YTCA=; b=Afsjrb38RNXykZQlOal2OHgmsimOmwV2FcYCY0G/LYNVyMkBlOZs5GCZEbrENMEeQo DMwuqiZ/phUOqwTxWB59rB9ew4c+9sYMl7y+EzUqoPofQ6N8zMJtsU5cDmJo0nsS5Ar2 pjK8PlcFDWcYRh5K0jfoE/V2vDrm0/WAUrZ6ktVS0qD1v1RZPzs3d6pAFPJMRgE9QATi HRkKic29jux8K/GOQUWpJQmUsGQdo5o3d6NHhdTenEhvUFeeikO403tysYQwbU3u/BIY SJ1HKZlxdKy9wpQQapdq0mQUiuL7ym4NLLp0E5eaF8g3oyZkdYhAo3oz4EogjJTcLy5A 0ELA== MIME-Version: 1.0 X-Received: by 10.194.94.226 with SMTP id df2mr6824367wjb.113.1403304209825; Fri, 20 Jun 2014 15:43:29 -0700 (PDT) Received: by 10.216.219.193 with HTTP; Fri, 20 Jun 2014 15:43:29 -0700 (PDT) Date: Fri, 20 Jun 2014 23:43:29 +0100 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] OCaml compiler hacking next Wednesday (25th June) X-BeenThere: mirageos-devel@lists.xenproject.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's time for another OCaml compiler hacking session! We'll be meeting in the computer lab next Wednesday evening (25th June). The details are on the blog: http://ocamllabs.github.io/compiler-hacking/2014/06/20/sixth-compiler-hacking-session.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 Fri Jun 20 22:43:38 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 20 Jun 2014 22:43: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 1Wy7Wv-0001F3-8O; Fri, 20 Jun 2014 22:43:33 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Wy7Wt-0001Ey-Ch for mirageos-devel@lists.xenproject.org; Fri, 20 Jun 2014 22:43:31 +0000 Received: from [85.158.139.211:38226] by server-15.bemta-5.messagelabs.com id 72/1B-19516-219B4A35; Fri, 20 Jun 2014 22:43:30 +0000 X-Env-Sender: yallop@gmail.com X-Msg-Ref: server-9.tower-206.messagelabs.com!1403304210!11155971!1 X-Originating-IP: [209.85.212.169] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4982 invoked from network); 20 Jun 2014 22:43:30 -0000 Received: from mail-wi0-f169.google.com (HELO mail-wi0-f169.google.com) (209.85.212.169) by server-9.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 20 Jun 2014 22:43:30 -0000 Received: by mail-wi0-f169.google.com with SMTP id hi2so1697418wib.0 for ; Fri, 20 Jun 2014 15:43:29 -0700 (PDT) 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=++NwY+OH0mj8tfVSp8OHfaO1nfVyeNropwAz4Z2YTCA=; b=Afsjrb38RNXykZQlOal2OHgmsimOmwV2FcYCY0G/LYNVyMkBlOZs5GCZEbrENMEeQo DMwuqiZ/phUOqwTxWB59rB9ew4c+9sYMl7y+EzUqoPofQ6N8zMJtsU5cDmJo0nsS5Ar2 pjK8PlcFDWcYRh5K0jfoE/V2vDrm0/WAUrZ6ktVS0qD1v1RZPzs3d6pAFPJMRgE9QATi HRkKic29jux8K/GOQUWpJQmUsGQdo5o3d6NHhdTenEhvUFeeikO403tysYQwbU3u/BIY SJ1HKZlxdKy9wpQQapdq0mQUiuL7ym4NLLp0E5eaF8g3oyZkdYhAo3oz4EogjJTcLy5A 0ELA== MIME-Version: 1.0 X-Received: by 10.194.94.226 with SMTP id df2mr6824367wjb.113.1403304209825; Fri, 20 Jun 2014 15:43:29 -0700 (PDT) Received: by 10.216.219.193 with HTTP; Fri, 20 Jun 2014 15:43:29 -0700 (PDT) Date: Fri, 20 Jun 2014 23:43:29 +0100 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] OCaml compiler hacking next Wednesday (25th June) X-BeenThere: mirageos-devel@lists.xenproject.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's time for another OCaml compiler hacking session! We'll be meeting in the computer lab next Wednesday evening (25th June). The details are on the blog: http://ocamllabs.github.io/compiler-hacking/2014/06/20/sixth-compiler-hacking-session.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 Fri Jun 20 22:53:56 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 20 Jun 2014 22:53: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 1Wy7gx-0001ew-8C; Fri, 20 Jun 2014 22:53:55 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Wy7gw-0001er-MB for mirageos-devel@lists.xenproject.org; Fri, 20 Jun 2014 22:53:54 +0000 Received: from [85.158.139.211:14328] by server-2.bemta-5.messagelabs.com id 4C/EC-01647-28BB4A35; Fri, 20 Jun 2014 22:53:54 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-13.tower-206.messagelabs.com!1403304833!11187466!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16927 invoked from network); 20 Jun 2014 22:53:53 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-13.tower-206.messagelabs.com with SMTP; 20 Jun 2014 22:53:53 -0000 Received: (qmail 12503 invoked by uid 634); 20 Jun 2014 22:53:52 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from cpc11-belf9-2-0-cust355.2-1.cable.virginm.net (HELO [10.0.1.15]) (86.24.61.100) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Fri, 20 Jun 2014 23:53:44 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\)) From: Anil Madhavapeddy In-Reply-To: Date: Fri, 20 Jun 2014 23:53:43 +0100 Message-Id: References: <1233494D-A05A-4F52-BFE7-9773BD566372@gazagnaire.org> <2C06C3FC-F8F3-4FC4-A7F9-BCD1A2FADE94@recoil.org> To: David Scott X-Mailer: Apple Mail (2.1874) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: Thomas Gazagnaire , Jonathan Ludlam , "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] towards a common Mirage 'FLOW' signature X-BeenThere: mirageos-devel@lists.xenproject.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 20 Jun 2014, at 21:19, Dave Scott wrote: >>> >>> and we could expose TCP buffers or the vchan ring size. What use would this information be to an application, though? >> >> if i'm following this correctly, couldn't the application use this to do things like customise TCP congestion control behaviour by fiddling with the receive window? > > Maybe we should start by cataloging our current buffer management and see if we can see any nice patterns? We have a nice set of protocols now. The buffers all take different forms though -- unless the application specifically knows that it's a TCP flow, it can't take any sensible action based on predicted congestion behaviour. And this would be entirely wrong behaviour if the buffer size it gets back is actually a (lossless) vchan ring buffer size instead. So my point is that rather than exposing the buffer size as an integer, it would be worth figuring out some use cases for when applications would need to know the buffer size (as opposed to, for example, having a high level "sendfile"-style API that provides more declarative knowledge to the lower levels of the communications stack). -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 Jun 20 22:53:56 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 20 Jun 2014 22:53: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 1Wy7gx-0001ew-8C; Fri, 20 Jun 2014 22:53:55 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Wy7gw-0001er-MB for mirageos-devel@lists.xenproject.org; Fri, 20 Jun 2014 22:53:54 +0000 Received: from [85.158.139.211:14328] by server-2.bemta-5.messagelabs.com id 4C/EC-01647-28BB4A35; Fri, 20 Jun 2014 22:53:54 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-13.tower-206.messagelabs.com!1403304833!11187466!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16927 invoked from network); 20 Jun 2014 22:53:53 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-13.tower-206.messagelabs.com with SMTP; 20 Jun 2014 22:53:53 -0000 Received: (qmail 12503 invoked by uid 634); 20 Jun 2014 22:53:52 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from cpc11-belf9-2-0-cust355.2-1.cable.virginm.net (HELO [10.0.1.15]) (86.24.61.100) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Fri, 20 Jun 2014 23:53:44 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\)) From: Anil Madhavapeddy In-Reply-To: Date: Fri, 20 Jun 2014 23:53:43 +0100 Message-Id: References: <1233494D-A05A-4F52-BFE7-9773BD566372@gazagnaire.org> <2C06C3FC-F8F3-4FC4-A7F9-BCD1A2FADE94@recoil.org> To: David Scott X-Mailer: Apple Mail (2.1874) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: Thomas Gazagnaire , Jonathan Ludlam , "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] towards a common Mirage 'FLOW' signature X-BeenThere: mirageos-devel@lists.xenproject.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 20 Jun 2014, at 21:19, Dave Scott wrote: >>> >>> and we could expose TCP buffers or the vchan ring size. What use would this information be to an application, though? >> >> if i'm following this correctly, couldn't the application use this to do things like customise TCP congestion control behaviour by fiddling with the receive window? > > Maybe we should start by cataloging our current buffer management and see if we can see any nice patterns? We have a nice set of protocols now. The buffers all take different forms though -- unless the application specifically knows that it's a TCP flow, it can't take any sensible action based on predicted congestion behaviour. And this would be entirely wrong behaviour if the buffer size it gets back is actually a (lossless) vchan ring buffer size instead. So my point is that rather than exposing the buffer size as an integer, it would be worth figuring out some use cases for when applications would need to know the buffer size (as opposed to, for example, having a high level "sendfile"-style API that provides more declarative knowledge to the lower levels of the communications stack). -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 Sat Jun 21 07:58:59 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sat, 21 Jun 2014 07:58: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 1WyGCL-000894-IG; Sat, 21 Jun 2014 07:58:53 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WyGCK-00088z-Dr for mirageos-devel@lists.xenproject.org; Sat, 21 Jun 2014 07:58:52 +0000 Received: from [85.158.143.35:10194] by server-3.bemta-4.messagelabs.com id 68/36-16194-B3B35A35; Sat, 21 Jun 2014 07:58:51 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-9.tower-21.messagelabs.com!1403337526!12868703!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_8, spamassassin: , surbl: (ASYNC_NO) c3VyYmxfcmVjaGVja19kZWxheTogMzI3Njc1OSAo YWJhbmRvbmVkOiB0aGVpbnZpc2libGV0aGlu\nZ3MuYmxvZ3Nwb3QuaW4p\n X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15329 invoked from network); 21 Jun 2014 07:58:46 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-9.tower-21.messagelabs.com with SMTP; 21 Jun 2014 07:58:46 -0000 Received: (qmail 18766 invoked by uid 634); 21 Jun 2014 07:58:46 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from cpc11-belf9-2-0-cust355.2-1.cable.virginm.net (HELO [10.0.1.15]) (86.24.61.100) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Sat, 21 Jun 2014 08:58:46 +0100 From: Anil Madhavapeddy Message-Id: <6A38AB63-7876-4CDA-BDE3-87987E926F35@recoil.org> Date: Sat, 21 Jun 2014 08:58:44 +0100 To: mirageos-devel@lists.xenproject.org Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\)) X-Mailer: Apple Mail (2.1874) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Subject: [MirageOS-devel] vchan/xenstore in Qubes r3 X-BeenThere: mirageos-devel@lists.xenproject.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 A very interesting article from Joanna on the new r3 alpha of QubesOS. http://theinvisiblethings.blogspot.in/2013/06/qubes-os-r3-alpha-preview-odyssey-hal.html - Qubes uses upstream Xen vchan now, which means that we "should" interoperate with the ocaml-vchan library. - They've replaced Xenstore with a simpler transport that removes permissions and uses vchan under the hood. This is also something that should be easier to do with Dave's oxenstore+irmin, since many of the components such as xenstore_transport are functorized, and of Irmin can serialize to several formats including Git, for reconciliation with external databases. - Qubes looks like an excellent candidate for a 'unikernel' desktop OS! I'm going to try it when I hunt down a PC laptop, but if anyone else gets a chance I'd be interested in hearing about it. -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 Sat Jun 21 07:58:59 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sat, 21 Jun 2014 07:58: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 1WyGCL-000894-IG; Sat, 21 Jun 2014 07:58:53 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WyGCK-00088z-Dr for mirageos-devel@lists.xenproject.org; Sat, 21 Jun 2014 07:58:52 +0000 Received: from [85.158.143.35:10194] by server-3.bemta-4.messagelabs.com id 68/36-16194-B3B35A35; Sat, 21 Jun 2014 07:58:51 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-9.tower-21.messagelabs.com!1403337526!12868703!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_8, spamassassin: , surbl: (ASYNC_NO) c3VyYmxfcmVjaGVja19kZWxheTogMzI3Njc1OSAo YWJhbmRvbmVkOiB0aGVpbnZpc2libGV0aGlu\nZ3MuYmxvZ3Nwb3QuaW4p\n X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15329 invoked from network); 21 Jun 2014 07:58:46 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-9.tower-21.messagelabs.com with SMTP; 21 Jun 2014 07:58:46 -0000 Received: (qmail 18766 invoked by uid 634); 21 Jun 2014 07:58:46 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from cpc11-belf9-2-0-cust355.2-1.cable.virginm.net (HELO [10.0.1.15]) (86.24.61.100) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Sat, 21 Jun 2014 08:58:46 +0100 From: Anil Madhavapeddy Message-Id: <6A38AB63-7876-4CDA-BDE3-87987E926F35@recoil.org> Date: Sat, 21 Jun 2014 08:58:44 +0100 To: mirageos-devel@lists.xenproject.org Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\)) X-Mailer: Apple Mail (2.1874) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Subject: [MirageOS-devel] vchan/xenstore in Qubes r3 X-BeenThere: mirageos-devel@lists.xenproject.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 A very interesting article from Joanna on the new r3 alpha of QubesOS. http://theinvisiblethings.blogspot.in/2013/06/qubes-os-r3-alpha-preview-odyssey-hal.html - Qubes uses upstream Xen vchan now, which means that we "should" interoperate with the ocaml-vchan library. - They've replaced Xenstore with a simpler transport that removes permissions and uses vchan under the hood. This is also something that should be easier to do with Dave's oxenstore+irmin, since many of the components such as xenstore_transport are functorized, and of Irmin can serialize to several formats including Git, for reconciliation with external databases. - Qubes looks like an excellent candidate for a 'unikernel' desktop OS! I'm going to try it when I hunt down a PC laptop, but if anyone else gets a chance I'd be interested in hearing about it. -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 Sat Jun 21 08:26:22 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sat, 21 Jun 2014 08:26: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 1WyGcv-0000PN-9k; Sat, 21 Jun 2014 08:26:21 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WyGcu-0000PI-55 for mirageos-devel@lists.xenproject.org; Sat, 21 Jun 2014 08:26:20 +0000 Received: from [85.158.139.211:46954] by server-2.bemta-5.messagelabs.com id B2/DF-01647-BA145A35; Sat, 21 Jun 2014 08:26:19 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-2.tower-206.messagelabs.com!1403339178!11192468!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16396 invoked from network); 21 Jun 2014 08:26:18 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-2.tower-206.messagelabs.com with SMTP; 21 Jun 2014 08:26:18 -0000 Received: (qmail 22360 invoked by uid 634); 21 Jun 2014 08:26:18 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from cpc11-belf9-2-0-cust355.2-1.cable.virginm.net (HELO [10.0.1.15]) (86.24.61.100) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Sat, 21 Jun 2014 09:26:14 +0100 From: Anil Madhavapeddy Date: Sat, 21 Jun 2014 09:26:12 +0100 Message-Id: <693C6F9A-EF9D-47BB-83FD-7EA201484778@recoil.org> To: mirageos-devel@lists.xenproject.org Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\)) X-Mailer: Apple Mail (2.1874) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Subject: [MirageOS-devel] dns fuzzing tool X-BeenThere: mirageos-devel@lists.xenproject.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 Another potential useful fuzzing tool to drop into the mix is this DNS one: https://github.com/crondaemon/dines (I've been tidying up the DNS parsing code but have deliberately left some inexhaustive pattern matches that were there alone, since i'd rather parse them rather than dynamically fail. If they're hard to add support for, we can add a catch-all failure). -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 Sat Jun 21 08:26:22 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sat, 21 Jun 2014 08:26: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 1WyGcv-0000PN-9k; Sat, 21 Jun 2014 08:26:21 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WyGcu-0000PI-55 for mirageos-devel@lists.xenproject.org; Sat, 21 Jun 2014 08:26:20 +0000 Received: from [85.158.139.211:46954] by server-2.bemta-5.messagelabs.com id B2/DF-01647-BA145A35; Sat, 21 Jun 2014 08:26:19 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-2.tower-206.messagelabs.com!1403339178!11192468!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16396 invoked from network); 21 Jun 2014 08:26:18 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-2.tower-206.messagelabs.com with SMTP; 21 Jun 2014 08:26:18 -0000 Received: (qmail 22360 invoked by uid 634); 21 Jun 2014 08:26:18 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from cpc11-belf9-2-0-cust355.2-1.cable.virginm.net (HELO [10.0.1.15]) (86.24.61.100) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Sat, 21 Jun 2014 09:26:14 +0100 From: Anil Madhavapeddy Date: Sat, 21 Jun 2014 09:26:12 +0100 Message-Id: <693C6F9A-EF9D-47BB-83FD-7EA201484778@recoil.org> To: mirageos-devel@lists.xenproject.org Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\)) X-Mailer: Apple Mail (2.1874) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Subject: [MirageOS-devel] dns fuzzing tool X-BeenThere: mirageos-devel@lists.xenproject.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 Another potential useful fuzzing tool to drop into the mix is this DNS one: https://github.com/crondaemon/dines (I've been tidying up the DNS parsing code but have deliberately left some inexhaustive pattern matches that were there alone, since i'd rather parse them rather than dynamically fail. If they're hard to add support for, we can add a catch-all failure). -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 Sat Jun 21 09:02:32 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sat, 21 Jun 2014 09:02: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 1WyHBs-0000tr-Oy; Sat, 21 Jun 2014 09:02:28 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WyHBr-0000tm-HP for mirageos-devel@lists.xenproject.org; Sat, 21 Jun 2014 09:02:27 +0000 Received: from [85.158.139.211:10333] by server-2.bemta-5.messagelabs.com id 6B/10-01647-22A45A35; Sat, 21 Jun 2014 09:02:26 +0000 X-Env-Sender: talex5@gmail.com X-Msg-Ref: server-4.tower-206.messagelabs.com!1403341344!11220778!1 X-Originating-IP: [209.85.219.48] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, ML_RADAR_SPEW_LINKS_23, ML_RADAR_SPEW_LINKS_8, RCVD_BY_IP, spamassassin: , surbl: (ASYNC_NO) c3VyYmxfcmVjaGVja19kZWxheTogMCAoYWJhbmRvbmVkOiB0aGVpbnZ pc2libGV0aGluZ3MuYmxv\nZ3Nwb3QuaW4p\n X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20525 invoked from network); 21 Jun 2014 09:02:25 -0000 Received: from mail-oa0-f48.google.com (HELO mail-oa0-f48.google.com) (209.85.219.48) by server-4.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 21 Jun 2014 09:02:25 -0000 Received: by mail-oa0-f48.google.com with SMTP id m1so8315327oag.35 for ; Sat, 21 Jun 2014 02:02:24 -0700 (PDT) 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=0WOiaEc8eBBaIryGozFcS5LGwi0yaF7XANVMkITMsl8=; b=Z4pFiIf7wXNl4YVYy0dkX3P+yjUrMrKYaE/X4dB8zPGguWNMYcNKyT+A9hYKl7Jm2v zLX6QIVQxVtWWZ0F1/Pp3VvJVKxTBGos0UnsdVa8WWduUdd4ey6WM5TbT7xQOR/+puYp 7yCytpWvzMu7EwPbqAVp6QtJKtFCedv9wvj24r41XyfsVa+xXwY5w5K53ooeNXSWoTX1 JHU4zClgAz9YMr/tUz6ot6OVMbqm6+ZMKVeAvvJwcfGM7JTpzPoSnUZNViAM0ZqjwU1L KI2GV3vkvix6Ykh2K9okaPAI9Vh1t+jvUgXDCo3KZ0pykUVA2kf2cgXPyVnae6s3msq5 MdZQ== MIME-Version: 1.0 X-Received: by 10.60.145.225 with SMTP id sx1mr684714oeb.75.1403341344115; Sat, 21 Jun 2014 02:02:24 -0700 (PDT) Received: by 10.76.92.5 with HTTP; Sat, 21 Jun 2014 02:02:24 -0700 (PDT) In-Reply-To: <6A38AB63-7876-4CDA-BDE3-87987E926F35@recoil.org> References: <6A38AB63-7876-4CDA-BDE3-87987E926F35@recoil.org> Date: Sat, 21 Jun 2014 10:02:24 +0100 Message-ID: From: Thomas Leonard To: Anil Madhavapeddy Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] vchan/xenstore in Qubes r3 X-BeenThere: mirageos-devel@lists.xenproject.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 21 June 2014 08:58, Anil Madhavapeddy wrote: > A very interesting article from Joanna on the new r3 alpha of QubesOS. > > http://theinvisiblethings.blogspot.in/2013/06/qubes-os-r3-alpha-preview-odyssey-hal.html > > - Qubes uses upstream Xen vchan now, which means that we "should" interoperate with the ocaml-vchan library. > > - They've replaced Xenstore with a simpler transport that removes permissions and uses vchan under the hood. This is also something that should be easier to do with Dave's oxenstore+irmin, since many of the components such as xenstore_transport are functorized, and of Irmin can serialize to several formats including Git, for reconciliation with external databases. > > - Qubes looks like an excellent candidate for a 'unikernel' desktop OS! I'm going to try it when I hunt down a PC laptop, but if anyone else gets a chance I'd be interested in hearing about it. I haven't tried the new alpha, but I tried the previous version of Qubes on my new laptop when it first arrived (actually, being able to try Qubes was one of the reasons I wanted a laptop with Intel graphics). It's clever, but it seemed rather slow and quite buggy. Even the installer failed and needed some manual work before I could boot the new system. I had hoped to use it as an easy way to run applications on multiple OSs together on a single display, but it turned out they only really support Fedora for now. One interesting thing for Mirage: they have a separate domain (NetVM) for network drivers, and another for the firewall (FirewallVM): http://wiki.qubes-os.org/trac/wiki/QubesFirewall FirewallVM is a complete Linux system and requires several hundred MB, as shown in this screenshot: http://wiki.qubes-os.org/trac/attachment/wiki/QubesScreenshots/r2b2-software-update.png [ aside: I don't know under what UI theory it's considered a good idea to fade out the bars on bar graphs, but anyway ] I imagine a Mirage unikernel would be a perfect replacement for their FirewallVM. In the end, I only tried it for a few hours before wiping it and installing Arch instead. Some other problems were that there is no tiling window manager available, and you can't run VirtualBox on Xen. Qubes doesn't offer graphics acceleration for guests (due to the focus on security), which would probably mess up gotomeeting. -- 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 Sat Jun 21 09:02:32 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sat, 21 Jun 2014 09:02: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 1WyHBs-0000tr-Oy; Sat, 21 Jun 2014 09:02:28 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WyHBr-0000tm-HP for mirageos-devel@lists.xenproject.org; Sat, 21 Jun 2014 09:02:27 +0000 Received: from [85.158.139.211:10333] by server-2.bemta-5.messagelabs.com id 6B/10-01647-22A45A35; Sat, 21 Jun 2014 09:02:26 +0000 X-Env-Sender: talex5@gmail.com X-Msg-Ref: server-4.tower-206.messagelabs.com!1403341344!11220778!1 X-Originating-IP: [209.85.219.48] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, ML_RADAR_SPEW_LINKS_23, ML_RADAR_SPEW_LINKS_8, RCVD_BY_IP, spamassassin: , surbl: (ASYNC_NO) c3VyYmxfcmVjaGVja19kZWxheTogMCAoYWJhbmRvbmVkOiB0aGVpbnZ pc2libGV0aGluZ3MuYmxv\nZ3Nwb3QuaW4p\n X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20525 invoked from network); 21 Jun 2014 09:02:25 -0000 Received: from mail-oa0-f48.google.com (HELO mail-oa0-f48.google.com) (209.85.219.48) by server-4.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 21 Jun 2014 09:02:25 -0000 Received: by mail-oa0-f48.google.com with SMTP id m1so8315327oag.35 for ; Sat, 21 Jun 2014 02:02:24 -0700 (PDT) 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=0WOiaEc8eBBaIryGozFcS5LGwi0yaF7XANVMkITMsl8=; b=Z4pFiIf7wXNl4YVYy0dkX3P+yjUrMrKYaE/X4dB8zPGguWNMYcNKyT+A9hYKl7Jm2v zLX6QIVQxVtWWZ0F1/Pp3VvJVKxTBGos0UnsdVa8WWduUdd4ey6WM5TbT7xQOR/+puYp 7yCytpWvzMu7EwPbqAVp6QtJKtFCedv9wvj24r41XyfsVa+xXwY5w5K53ooeNXSWoTX1 JHU4zClgAz9YMr/tUz6ot6OVMbqm6+ZMKVeAvvJwcfGM7JTpzPoSnUZNViAM0ZqjwU1L KI2GV3vkvix6Ykh2K9okaPAI9Vh1t+jvUgXDCo3KZ0pykUVA2kf2cgXPyVnae6s3msq5 MdZQ== MIME-Version: 1.0 X-Received: by 10.60.145.225 with SMTP id sx1mr684714oeb.75.1403341344115; Sat, 21 Jun 2014 02:02:24 -0700 (PDT) Received: by 10.76.92.5 with HTTP; Sat, 21 Jun 2014 02:02:24 -0700 (PDT) In-Reply-To: <6A38AB63-7876-4CDA-BDE3-87987E926F35@recoil.org> References: <6A38AB63-7876-4CDA-BDE3-87987E926F35@recoil.org> Date: Sat, 21 Jun 2014 10:02:24 +0100 Message-ID: From: Thomas Leonard To: Anil Madhavapeddy Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] vchan/xenstore in Qubes r3 X-BeenThere: mirageos-devel@lists.xenproject.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 21 June 2014 08:58, Anil Madhavapeddy wrote: > A very interesting article from Joanna on the new r3 alpha of QubesOS. > > http://theinvisiblethings.blogspot.in/2013/06/qubes-os-r3-alpha-preview-odyssey-hal.html > > - Qubes uses upstream Xen vchan now, which means that we "should" interoperate with the ocaml-vchan library. > > - They've replaced Xenstore with a simpler transport that removes permissions and uses vchan under the hood. This is also something that should be easier to do with Dave's oxenstore+irmin, since many of the components such as xenstore_transport are functorized, and of Irmin can serialize to several formats including Git, for reconciliation with external databases. > > - Qubes looks like an excellent candidate for a 'unikernel' desktop OS! I'm going to try it when I hunt down a PC laptop, but if anyone else gets a chance I'd be interested in hearing about it. I haven't tried the new alpha, but I tried the previous version of Qubes on my new laptop when it first arrived (actually, being able to try Qubes was one of the reasons I wanted a laptop with Intel graphics). It's clever, but it seemed rather slow and quite buggy. Even the installer failed and needed some manual work before I could boot the new system. I had hoped to use it as an easy way to run applications on multiple OSs together on a single display, but it turned out they only really support Fedora for now. One interesting thing for Mirage: they have a separate domain (NetVM) for network drivers, and another for the firewall (FirewallVM): http://wiki.qubes-os.org/trac/wiki/QubesFirewall FirewallVM is a complete Linux system and requires several hundred MB, as shown in this screenshot: http://wiki.qubes-os.org/trac/attachment/wiki/QubesScreenshots/r2b2-software-update.png [ aside: I don't know under what UI theory it's considered a good idea to fade out the bars on bar graphs, but anyway ] I imagine a Mirage unikernel would be a perfect replacement for their FirewallVM. In the end, I only tried it for a few hours before wiping it and installing Arch instead. Some other problems were that there is no tiling window manager available, and you can't run VirtualBox on Xen. Qubes doesn't offer graphics acceleration for guests (due to the focus on security), which would probably mess up gotomeeting. -- 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 Sat Jun 21 10:36:53 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sat, 21 Jun 2014 10:36: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 1WyIfB-000294-AV; Sat, 21 Jun 2014 10:36:49 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WyIfA-00028z-M0 for mirageos-devel@lists.xenproject.org; Sat, 21 Jun 2014 10:36:48 +0000 Received: from [193.109.254.147:35895] by server-8.bemta-14.messagelabs.com id BF/F6-01877-F3065A35; Sat, 21 Jun 2014 10:36:47 +0000 X-Env-Sender: scott.dj@gmail.com X-Msg-Ref: server-10.tower-27.messagelabs.com!1403347004!12760059!1 X-Originating-IP: [209.85.192.181] X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_10_20,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 9674 invoked from network); 21 Jun 2014 10:36:46 -0000 Received: from mail-pd0-f181.google.com (HELO mail-pd0-f181.google.com) (209.85.192.181) by server-10.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 21 Jun 2014 10:36:46 -0000 Received: by mail-pd0-f181.google.com with SMTP id v10so3816572pde.26 for ; Sat, 21 Jun 2014 03:36:44 -0700 (PDT) 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=qC3AbuES0gMKFPIK58JOxUH3jIsS9qzaFOj1rSqEQGU=; b=nvtmxfqRE+YO6d4ErtrYF8higCGREKQvd3h1DqJbuIhps+vVXYmcWNf/tcOD37mG1Z HnEgpc1e3yj4ONQUR/ZIoRrHJsWbgURLjrGaetclP8rTMmBItk8sqpSNvaNE1YMbsBe0 /Zs1ExSq7Vahc4XpxzlRqp/X7Y2DMX75SynmHsbxs1coVZ96PPNC7wO0FugzkwF6IGzM TyhIdx2DjR78MBUb4I4l1oEpk3Rxj/aiVNXgf/iuY8DPmBBoI3x4ct84abKquzByecD4 G1qe0bnGve522FRKeeZHmMoPeBD5Wwbzm8DRmd137djs3JO8vkhyiDrhQZyTe/lcVdMs cwbA== MIME-Version: 1.0 X-Received: by 10.68.245.162 with SMTP id xp2mr12197617pbc.69.1403347004600; Sat, 21 Jun 2014 03:36:44 -0700 (PDT) Received: by 10.70.11.65 with HTTP; Sat, 21 Jun 2014 03:36:44 -0700 (PDT) In-Reply-To: References: <1233494D-A05A-4F52-BFE7-9773BD566372@gazagnaire.org> <2C06C3FC-F8F3-4FC4-A7F9-BCD1A2FADE94@recoil.org> Date: Sat, 21 Jun 2014 11:36:44 +0100 Message-ID: From: David Scott To: Anil Madhavapeddy Cc: David Scott , Thomas Gazagnaire , Jonathan Ludlam , "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] towards a common Mirage 'FLOW' signature X-BeenThere: mirageos-devel@lists.xenproject.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="===============7166304763981884046==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============7166304763981884046== Content-Type: multipart/alternative; boundary=047d7b1637edb4b8fe04fc562f58 --047d7b1637edb4b8fe04fc562f58 Content-Type: text/plain; charset=UTF-8 Hi, On Fri, Jun 20, 2014 at 11:53 PM, Anil Madhavapeddy wrote: > On 20 Jun 2014, at 21:19, Dave Scott wrote: > > >>> > >>> and we could expose TCP buffers or the vchan ring size. What use > would this information be to an application, though? > >> > >> if i'm following this correctly, couldn't the application use this to > do things like customise TCP congestion control behaviour by fiddling with > the receive window? > > > > Maybe we should start by cataloging our current buffer management and > see if we can see any nice patterns? We have a nice set of protocols now. > > The buffers all take different forms though -- unless the application > specifically knows that it's a TCP flow, it can't take any sensible action > based on predicted congestion behaviour. And this would be entirely wrong > behaviour if the buffer size it gets back is actually a (lossless) vchan > ring buffer size instead. > > So my point is that rather than exposing the buffer size as an integer, it > would be worth figuring out some use cases for when applications would need > to know the buffer size (as opposed to, for example, having a high level > "sendfile"-style API that provides more declarative knowledge to the lower > levels of the communications stack). > I think I'm confused about 2 separate questions :-) I wonder whether we should extend flow to have all 4 of {read,write}{,_ack} so that we can control when data is acked/consumed. The TCP implementation would then only call the _ack function when it had received confirmation the data had been processed. If the TCP implementation needed to resend (possibly after a crash) it could call 'read' again and get back the same data it had before. So the result of 'read' would be an int64 stream offset * Cstruct.t, and 'read_ack' would mark an int64 offset as being consumed. This is what I'm doing in xenstore and shared-memory-ring: I don't know if anyone else wants this kind of behaviour. In the case where a VM sends a block write, which is then sent over NFS/TCP it would allow us to call write_ack on the flow to the guest when the TCP acks are received. Separately, in the case of vchan the buffer size is set at ring setup time. If you connected a vhan ring to a TCP transmitter then the TCP transmitter, presumably with it's higher latency link, would try to keep its link full by buffering more. If the vchan ring size is smaller then the TCP window size (likely), TCP would have to copy into temporary buffers. If we knew we were going to need more buffered data then we could make the vchan ring larger and avoid the copying? Perhaps that wouldn't work due to alignment requirements. Anyway, this is more of a 'flow setup' issue than a during-the-flow issue. Perhaps a CHANNEL would be where we could close and re-open flows in order to adjust their parameters. Cheers, Dave --047d7b1637edb4b8fe04fc562f58 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi,

On Fri, Jun 20, 2014 at 11:53 PM, Anil Madhavapeddy &l= t;anil@recoil.org&= gt; wrote:
On 20 Jun 2014, at 21:19, Da= ve Scott <Dave.Scott@citrix.com= > wrote:

>>>
>>> and we could expose TCP buffers or the v= chan ring size. =C2=A0What use would this information be to an application,= though?
>>
>> if i'm following this correctly, couldn't the application = use this to do things like customise TCP congestion control behaviour by fi= ddling with the receive window?
>
> Maybe we should start by cataloging our current buffer management and = see if we can see any nice patterns? We have a nice set of protocols now.
The buffers all take different forms though -- unless the application= specifically knows that it's a TCP flow, it can't take any sensibl= e action based on predicted congestion behaviour. =C2=A0And this would be e= ntirely wrong behaviour if the buffer size it gets back is actually a (loss= less) vchan ring buffer size instead.

So my point is that rather than exposing the buffer size as an integer, it = would be worth figuring out some use cases for when applications would need= to know the buffer size (as opposed to, for example, having a high level &= quot;sendfile"-style API that provides more declarative knowledge to t= he lower levels of the communications stack).

I think I'm confused about 2 separate = questions :-)

I wonder whether we should extend fl= ow to have all 4 of {read,write}{,_ack} =C2=A0so that we can control when d= ata is acked/consumed. The TCP implementation would then only call the _ack= function when it had received confirmation the data had been processed. If= the TCP implementation needed to resend (possibly after a crash) it could = call 'read' again and get back the same data it had before. So the = result of 'read' would be an int64 stream offset * Cstruct.t, and &= #39;read_ack' would mark an int64 offset as being consumed. This is wha= t I'm doing in xenstore and shared-memory-ring: I don't know if any= one else wants this kind of behaviour. In the case where a VM sends a block= write, which is then sent over NFS/TCP it would allow us to call write_ack= on the flow to the guest when the TCP acks are received.

Separately, in the case of vchan the buffer size is set= at ring setup time. If you connected a vhan ring to a TCP transmitter then= the TCP transmitter, presumably with it's higher latency link, would t= ry to keep its link full by buffering more. If the vchan ring size is small= er then the TCP window size (likely), TCP would have to copy into temporary= buffers. If we knew we were going to need more buffered data then we could= make the vchan ring larger and avoid the copying? Perhaps that wouldn'= t work due to alignment requirements. Anyway, this is more of a 'flow s= etup' issue than a during-the-flow issue. Perhaps a CHANNEL would be wh= ere we could close and re-open flows in order to adjust their parameters.

Cheers,
Dave
--047d7b1637edb4b8fe04fc562f58-- --===============7166304763981884046== 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 --===============7166304763981884046==-- From mirageos-devel-bounces@lists.xenproject.org Sat Jun 21 10:36:53 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sat, 21 Jun 2014 10:36: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 1WyIfB-000294-AV; Sat, 21 Jun 2014 10:36:49 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WyIfA-00028z-M0 for mirageos-devel@lists.xenproject.org; Sat, 21 Jun 2014 10:36:48 +0000 Received: from [193.109.254.147:35895] by server-8.bemta-14.messagelabs.com id BF/F6-01877-F3065A35; Sat, 21 Jun 2014 10:36:47 +0000 X-Env-Sender: scott.dj@gmail.com X-Msg-Ref: server-10.tower-27.messagelabs.com!1403347004!12760059!1 X-Originating-IP: [209.85.192.181] X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_10_20,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 9674 invoked from network); 21 Jun 2014 10:36:46 -0000 Received: from mail-pd0-f181.google.com (HELO mail-pd0-f181.google.com) (209.85.192.181) by server-10.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 21 Jun 2014 10:36:46 -0000 Received: by mail-pd0-f181.google.com with SMTP id v10so3816572pde.26 for ; Sat, 21 Jun 2014 03:36:44 -0700 (PDT) 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=qC3AbuES0gMKFPIK58JOxUH3jIsS9qzaFOj1rSqEQGU=; b=nvtmxfqRE+YO6d4ErtrYF8higCGREKQvd3h1DqJbuIhps+vVXYmcWNf/tcOD37mG1Z HnEgpc1e3yj4ONQUR/ZIoRrHJsWbgURLjrGaetclP8rTMmBItk8sqpSNvaNE1YMbsBe0 /Zs1ExSq7Vahc4XpxzlRqp/X7Y2DMX75SynmHsbxs1coVZ96PPNC7wO0FugzkwF6IGzM TyhIdx2DjR78MBUb4I4l1oEpk3Rxj/aiVNXgf/iuY8DPmBBoI3x4ct84abKquzByecD4 G1qe0bnGve522FRKeeZHmMoPeBD5Wwbzm8DRmd137djs3JO8vkhyiDrhQZyTe/lcVdMs cwbA== MIME-Version: 1.0 X-Received: by 10.68.245.162 with SMTP id xp2mr12197617pbc.69.1403347004600; Sat, 21 Jun 2014 03:36:44 -0700 (PDT) Received: by 10.70.11.65 with HTTP; Sat, 21 Jun 2014 03:36:44 -0700 (PDT) In-Reply-To: References: <1233494D-A05A-4F52-BFE7-9773BD566372@gazagnaire.org> <2C06C3FC-F8F3-4FC4-A7F9-BCD1A2FADE94@recoil.org> Date: Sat, 21 Jun 2014 11:36:44 +0100 Message-ID: From: David Scott To: Anil Madhavapeddy Cc: David Scott , Thomas Gazagnaire , Jonathan Ludlam , "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] towards a common Mirage 'FLOW' signature X-BeenThere: mirageos-devel@lists.xenproject.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="===============7166304763981884046==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============7166304763981884046== Content-Type: multipart/alternative; boundary=047d7b1637edb4b8fe04fc562f58 --047d7b1637edb4b8fe04fc562f58 Content-Type: text/plain; charset=UTF-8 Hi, On Fri, Jun 20, 2014 at 11:53 PM, Anil Madhavapeddy wrote: > On 20 Jun 2014, at 21:19, Dave Scott wrote: > > >>> > >>> and we could expose TCP buffers or the vchan ring size. What use > would this information be to an application, though? > >> > >> if i'm following this correctly, couldn't the application use this to > do things like customise TCP congestion control behaviour by fiddling with > the receive window? > > > > Maybe we should start by cataloging our current buffer management and > see if we can see any nice patterns? We have a nice set of protocols now. > > The buffers all take different forms though -- unless the application > specifically knows that it's a TCP flow, it can't take any sensible action > based on predicted congestion behaviour. And this would be entirely wrong > behaviour if the buffer size it gets back is actually a (lossless) vchan > ring buffer size instead. > > So my point is that rather than exposing the buffer size as an integer, it > would be worth figuring out some use cases for when applications would need > to know the buffer size (as opposed to, for example, having a high level > "sendfile"-style API that provides more declarative knowledge to the lower > levels of the communications stack). > I think I'm confused about 2 separate questions :-) I wonder whether we should extend flow to have all 4 of {read,write}{,_ack} so that we can control when data is acked/consumed. The TCP implementation would then only call the _ack function when it had received confirmation the data had been processed. If the TCP implementation needed to resend (possibly after a crash) it could call 'read' again and get back the same data it had before. So the result of 'read' would be an int64 stream offset * Cstruct.t, and 'read_ack' would mark an int64 offset as being consumed. This is what I'm doing in xenstore and shared-memory-ring: I don't know if anyone else wants this kind of behaviour. In the case where a VM sends a block write, which is then sent over NFS/TCP it would allow us to call write_ack on the flow to the guest when the TCP acks are received. Separately, in the case of vchan the buffer size is set at ring setup time. If you connected a vhan ring to a TCP transmitter then the TCP transmitter, presumably with it's higher latency link, would try to keep its link full by buffering more. If the vchan ring size is smaller then the TCP window size (likely), TCP would have to copy into temporary buffers. If we knew we were going to need more buffered data then we could make the vchan ring larger and avoid the copying? Perhaps that wouldn't work due to alignment requirements. Anyway, this is more of a 'flow setup' issue than a during-the-flow issue. Perhaps a CHANNEL would be where we could close and re-open flows in order to adjust their parameters. Cheers, Dave --047d7b1637edb4b8fe04fc562f58 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi,

On Fri, Jun 20, 2014 at 11:53 PM, Anil Madhavapeddy &l= t;anil@recoil.org&= gt; wrote:
On 20 Jun 2014, at 21:19, Da= ve Scott <Dave.Scott@citrix.com= > wrote:

>>>
>>> and we could expose TCP buffers or the v= chan ring size. =C2=A0What use would this information be to an application,= though?
>>
>> if i'm following this correctly, couldn't the application = use this to do things like customise TCP congestion control behaviour by fi= ddling with the receive window?
>
> Maybe we should start by cataloging our current buffer management and = see if we can see any nice patterns? We have a nice set of protocols now.
The buffers all take different forms though -- unless the application= specifically knows that it's a TCP flow, it can't take any sensibl= e action based on predicted congestion behaviour. =C2=A0And this would be e= ntirely wrong behaviour if the buffer size it gets back is actually a (loss= less) vchan ring buffer size instead.

So my point is that rather than exposing the buffer size as an integer, it = would be worth figuring out some use cases for when applications would need= to know the buffer size (as opposed to, for example, having a high level &= quot;sendfile"-style API that provides more declarative knowledge to t= he lower levels of the communications stack).

I think I'm confused about 2 separate = questions :-)

I wonder whether we should extend fl= ow to have all 4 of {read,write}{,_ack} =C2=A0so that we can control when d= ata is acked/consumed. The TCP implementation would then only call the _ack= function when it had received confirmation the data had been processed. If= the TCP implementation needed to resend (possibly after a crash) it could = call 'read' again and get back the same data it had before. So the = result of 'read' would be an int64 stream offset * Cstruct.t, and &= #39;read_ack' would mark an int64 offset as being consumed. This is wha= t I'm doing in xenstore and shared-memory-ring: I don't know if any= one else wants this kind of behaviour. In the case where a VM sends a block= write, which is then sent over NFS/TCP it would allow us to call write_ack= on the flow to the guest when the TCP acks are received.

Separately, in the case of vchan the buffer size is set= at ring setup time. If you connected a vhan ring to a TCP transmitter then= the TCP transmitter, presumably with it's higher latency link, would t= ry to keep its link full by buffering more. If the vchan ring size is small= er then the TCP window size (likely), TCP would have to copy into temporary= buffers. If we knew we were going to need more buffered data then we could= make the vchan ring larger and avoid the copying? Perhaps that wouldn'= t work due to alignment requirements. Anyway, this is more of a 'flow s= etup' issue than a during-the-flow issue. Perhaps a CHANNEL would be wh= ere we could close and re-open flows in order to adjust their parameters.

Cheers,
Dave
--047d7b1637edb4b8fe04fc562f58-- --===============7166304763981884046== 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 --===============7166304763981884046==-- From mirageos-devel-bounces@lists.xenproject.org Sat Jun 21 10:46:05 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sat, 21 Jun 2014 10:46: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 1WyIo9-0002HV-7j; Sat, 21 Jun 2014 10:46:05 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WyIo7-0002HQ-UB for mirageos-devel@lists.xenproject.org; Sat, 21 Jun 2014 10:46:04 +0000 Received: from [85.158.137.68:17018] by server-3.bemta-3.messagelabs.com id DB/AF-12895-B6265A35; Sat, 21 Jun 2014 10:46:03 +0000 X-Env-Sender: scott.dj@gmail.com X-Msg-Ref: server-4.tower-31.messagelabs.com!1403347560!11437770!1 X-Originating-IP: [209.85.192.173] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14, ML_RADAR_SPEW_LINKS_8, RCVD_BY_IP, spamassassin: , surbl: (ASYNC_NO) c3VyYmxfcmVjaGVja19kZWxheTogMCAoYWJhbmRvbmVkOiB0aGVpbnZ pc2libGV0aGluZ3MuYmxv\nZ3Nwb3QuaW4p\n X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8200 invoked from network); 21 Jun 2014 10:46:01 -0000 Received: from mail-pd0-f173.google.com (HELO mail-pd0-f173.google.com) (209.85.192.173) by server-4.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 21 Jun 2014 10:46:01 -0000 Received: by mail-pd0-f173.google.com with SMTP id r10so3856427pdi.32 for ; Sat, 21 Jun 2014 03:45:59 -0700 (PDT) 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=CobqYP1LIosdN/VRvzWB1Js9esiaCurpWcKC7LyPE98=; b=ZFG65JDRvLLo6I01VB4NmaE7c48cif4c+rbgTkJq/+JkpsaAgSewFeO5FNc077Llvh ZLthF9LckMVPd2tcAvjZdeRwRsis0Ogfh5L5fpe7yPNWrSW+8DAG8u3ic5+LQ2ZkJQqo msA80cpCA87eHmdkuzZLo1OVz2SSi/TozG8rlkjeLteBmuiBB4YYIqV61M5t8ad3kYui 2ThX9ydPONsYyHMpbpDnvt52ua17Iho6lcTY02866bj6GLOFbvl9dclhhbE8foFN2Pvc wXswM91GQjklVr/7GeXxYnfKLQAnWtbaCd2aZTei89tFSpnm5jie4wzX/yZpXnoY7QpO V/Pg== MIME-Version: 1.0 X-Received: by 10.66.246.138 with SMTP id xw10mr11990122pac.142.1403347559780; Sat, 21 Jun 2014 03:45:59 -0700 (PDT) Received: by 10.70.11.65 with HTTP; Sat, 21 Jun 2014 03:45:59 -0700 (PDT) In-Reply-To: <6A38AB63-7876-4CDA-BDE3-87987E926F35@recoil.org> References: <6A38AB63-7876-4CDA-BDE3-87987E926F35@recoil.org> Date: Sat, 21 Jun 2014 11:45:59 +0100 Message-ID: From: David Scott To: Anil Madhavapeddy Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] vchan/xenstore in Qubes r3 X-BeenThere: mirageos-devel@lists.xenproject.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="===============0366970918264427871==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============0366970918264427871== Content-Type: multipart/alternative; boundary=047d7b15fc91cc187e04fc565019 --047d7b15fc91cc187e04fc565019 Content-Type: text/plain; charset=UTF-8 Hi, On Sat, Jun 21, 2014 at 8:58 AM, Anil Madhavapeddy wrote: > A very interesting article from Joanna on the new r3 alpha of QubesOS. > > > http://theinvisiblethings.blogspot.in/2013/06/qubes-os-r3-alpha-preview-odyssey-hal.html Is the URL wrong is is this 12 months old (as of today)? It's all good stuff, but I wonder whether they've done lots more good stuff in the intervening period! - Qubes uses upstream Xen vchan now, which means that we "should" > interoperate with the ocaml-vchan library. > > - They've replaced Xenstore with a simpler transport that removes > permissions and uses vchan under the hood. This is also something that > should be easier to do with Dave's oxenstore+irmin, since many of the > components such as xenstore_transport are functorized, and of Irmin can > serialize to several formats including Git, for reconciliation with > external databases. > I like the idea of running separate xenstore databases per VM, since there's no need for guest VMs to be able to see any of each other's stuff. The only tricky bit is any shared backends would have to talk to multiple xenstores, and a lot of code has the assumption of a single xenstore built-in. Cheers, Dave > - Qubes looks like an excellent candidate for a 'unikernel' desktop OS! > I'm going to try it when I hunt down a PC laptop, but if anyone else gets > a chance I'd be interested in hearing about it. > > -anil > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > -- Dave Scott --047d7b15fc91cc187e04fc565019 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi,

On Sat, Jun 21, 2014 at 8:58 AM, Anil Madhavapeddy <anil@recoil.org> wrote:
A very interesting article from Joanna on th= e new r3 alpha of QubesOS.

http://theinvisiblethings.blogs= pot.in/2013/06/qubes-os-r3-alpha-preview-odyssey-hal.html

Is the URL wrong is is this 12 months old (as of today)= ?

It's all good stuff, but I wonder whether th= ey've done lots more good stuff in the intervening period!

- Qubes uses upstream Xen vchan no= w, which means that we "should" interoperate with the ocaml-vchan= library.

- They've replaced Xenstore with a simpler transport that removes permi= ssions and uses vchan under the hood. =C2=A0This is also something that sho= uld be easier to do with Dave's oxenstore+irmin, since many of the comp= onents such as xenstore_transport are functorized, and of Irmin can seriali= ze to several formats including Git, for reconciliation with external datab= ases.

I like the idea of running separate xensto= re databases per VM, since there's no need for guest VMs to be able to = see any of each other's stuff. The only tricky bit is any shared backen= ds would have to talk to multiple xenstores, and a lot of code has the assu= mption of a single xenstore built-in.
=C2=A0
Cheers,
Dave


- Qubes looks like an excellent candidate for a 'unikernel' desktop= OS! =C2=A0I'm going to try it when I hunt down a PC laptop, but if any= one else gets a chance I'd be interested in hearing about it.

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



--
Dave Scott
--047d7b15fc91cc187e04fc565019-- --===============0366970918264427871== 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 --===============0366970918264427871==-- From mirageos-devel-bounces@lists.xenproject.org Sat Jun 21 10:46:05 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sat, 21 Jun 2014 10:46: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 1WyIo9-0002HV-7j; Sat, 21 Jun 2014 10:46:05 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WyIo7-0002HQ-UB for mirageos-devel@lists.xenproject.org; Sat, 21 Jun 2014 10:46:04 +0000 Received: from [85.158.137.68:17018] by server-3.bemta-3.messagelabs.com id DB/AF-12895-B6265A35; Sat, 21 Jun 2014 10:46:03 +0000 X-Env-Sender: scott.dj@gmail.com X-Msg-Ref: server-4.tower-31.messagelabs.com!1403347560!11437770!1 X-Originating-IP: [209.85.192.173] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14, ML_RADAR_SPEW_LINKS_8, RCVD_BY_IP, spamassassin: , surbl: (ASYNC_NO) c3VyYmxfcmVjaGVja19kZWxheTogMCAoYWJhbmRvbmVkOiB0aGVpbnZ pc2libGV0aGluZ3MuYmxv\nZ3Nwb3QuaW4p\n X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8200 invoked from network); 21 Jun 2014 10:46:01 -0000 Received: from mail-pd0-f173.google.com (HELO mail-pd0-f173.google.com) (209.85.192.173) by server-4.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 21 Jun 2014 10:46:01 -0000 Received: by mail-pd0-f173.google.com with SMTP id r10so3856427pdi.32 for ; Sat, 21 Jun 2014 03:45:59 -0700 (PDT) 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=CobqYP1LIosdN/VRvzWB1Js9esiaCurpWcKC7LyPE98=; b=ZFG65JDRvLLo6I01VB4NmaE7c48cif4c+rbgTkJq/+JkpsaAgSewFeO5FNc077Llvh ZLthF9LckMVPd2tcAvjZdeRwRsis0Ogfh5L5fpe7yPNWrSW+8DAG8u3ic5+LQ2ZkJQqo msA80cpCA87eHmdkuzZLo1OVz2SSi/TozG8rlkjeLteBmuiBB4YYIqV61M5t8ad3kYui 2ThX9ydPONsYyHMpbpDnvt52ua17Iho6lcTY02866bj6GLOFbvl9dclhhbE8foFN2Pvc wXswM91GQjklVr/7GeXxYnfKLQAnWtbaCd2aZTei89tFSpnm5jie4wzX/yZpXnoY7QpO V/Pg== MIME-Version: 1.0 X-Received: by 10.66.246.138 with SMTP id xw10mr11990122pac.142.1403347559780; Sat, 21 Jun 2014 03:45:59 -0700 (PDT) Received: by 10.70.11.65 with HTTP; Sat, 21 Jun 2014 03:45:59 -0700 (PDT) In-Reply-To: <6A38AB63-7876-4CDA-BDE3-87987E926F35@recoil.org> References: <6A38AB63-7876-4CDA-BDE3-87987E926F35@recoil.org> Date: Sat, 21 Jun 2014 11:45:59 +0100 Message-ID: From: David Scott To: Anil Madhavapeddy Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] vchan/xenstore in Qubes r3 X-BeenThere: mirageos-devel@lists.xenproject.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="===============0366970918264427871==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============0366970918264427871== Content-Type: multipart/alternative; boundary=047d7b15fc91cc187e04fc565019 --047d7b15fc91cc187e04fc565019 Content-Type: text/plain; charset=UTF-8 Hi, On Sat, Jun 21, 2014 at 8:58 AM, Anil Madhavapeddy wrote: > A very interesting article from Joanna on the new r3 alpha of QubesOS. > > > http://theinvisiblethings.blogspot.in/2013/06/qubes-os-r3-alpha-preview-odyssey-hal.html Is the URL wrong is is this 12 months old (as of today)? It's all good stuff, but I wonder whether they've done lots more good stuff in the intervening period! - Qubes uses upstream Xen vchan now, which means that we "should" > interoperate with the ocaml-vchan library. > > - They've replaced Xenstore with a simpler transport that removes > permissions and uses vchan under the hood. This is also something that > should be easier to do with Dave's oxenstore+irmin, since many of the > components such as xenstore_transport are functorized, and of Irmin can > serialize to several formats including Git, for reconciliation with > external databases. > I like the idea of running separate xenstore databases per VM, since there's no need for guest VMs to be able to see any of each other's stuff. The only tricky bit is any shared backends would have to talk to multiple xenstores, and a lot of code has the assumption of a single xenstore built-in. Cheers, Dave > - Qubes looks like an excellent candidate for a 'unikernel' desktop OS! > I'm going to try it when I hunt down a PC laptop, but if anyone else gets > a chance I'd be interested in hearing about it. > > -anil > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > -- Dave Scott --047d7b15fc91cc187e04fc565019 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi,

On Sat, Jun 21, 2014 at 8:58 AM, Anil Madhavapeddy <anil@recoil.org> wrote:
A very interesting article from Joanna on th= e new r3 alpha of QubesOS.

http://theinvisiblethings.blogs= pot.in/2013/06/qubes-os-r3-alpha-preview-odyssey-hal.html

Is the URL wrong is is this 12 months old (as of today)= ?

It's all good stuff, but I wonder whether th= ey've done lots more good stuff in the intervening period!

- Qubes uses upstream Xen vchan no= w, which means that we "should" interoperate with the ocaml-vchan= library.

- They've replaced Xenstore with a simpler transport that removes permi= ssions and uses vchan under the hood. =C2=A0This is also something that sho= uld be easier to do with Dave's oxenstore+irmin, since many of the comp= onents such as xenstore_transport are functorized, and of Irmin can seriali= ze to several formats including Git, for reconciliation with external datab= ases.

I like the idea of running separate xensto= re databases per VM, since there's no need for guest VMs to be able to = see any of each other's stuff. The only tricky bit is any shared backen= ds would have to talk to multiple xenstores, and a lot of code has the assu= mption of a single xenstore built-in.
=C2=A0
Cheers,
Dave


- Qubes looks like an excellent candidate for a 'unikernel' desktop= OS! =C2=A0I'm going to try it when I hunt down a PC laptop, but if any= one else gets a chance I'd be interested in hearing about it.

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



--
Dave Scott
--047d7b15fc91cc187e04fc565019-- --===============0366970918264427871== 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 --===============0366970918264427871==-- From mirageos-devel-bounces@lists.xenproject.org Sat Jun 21 14:54:19 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sat, 21 Jun 2014 14:54: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 1WyMgH-0007SR-KT; Sat, 21 Jun 2014 14:54:13 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WyMgG-0007SI-Ct for mirageos-devel@lists.xenproject.org; Sat, 21 Jun 2014 14:54:12 +0000 Received: from [85.158.143.35:32245] by server-2.bemta-4.messagelabs.com id 66/02-06539-39C95A35; Sat, 21 Jun 2014 14:54:11 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-16.tower-21.messagelabs.com!1403362440!9446127!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_8, spamassassin: , async_handler: YXN5bmNfZGVsYXk6IDcwNjQ5MzQgKHRpbWVvdXQp\n X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4876 invoked from network); 21 Jun 2014 14:54:00 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-16.tower-21.messagelabs.com with SMTP; 21 Jun 2014 14:54:00 -0000 Received: (qmail 27894 invoked by uid 634); 21 Jun 2014 14:54:00 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from Unknown (HELO [10.32.5.100]) (37.205.63.157) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Sat, 21 Jun 2014 15:53:59 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\)) From: Anil Madhavapeddy In-Reply-To: Date: Sat, 21 Jun 2014 15:53:52 +0100 Message-Id: <69BCED97-B3DF-41E3-9A26-398FA49322B8@recoil.org> References: <6A38AB63-7876-4CDA-BDE3-87987E926F35@recoil.org> To: Thomas Leonard X-Mailer: Apple Mail (2.1874) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] vchan/xenstore in Qubes r3 X-BeenThere: mirageos-devel@lists.xenproject.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 21 Jun 2014, at 10:02, Thomas Leonard wrote: > On 21 June 2014 08:58, Anil Madhavapeddy wrote: >> A very interesting article from Joanna on the new r3 alpha of QubesOS. >> >> http://theinvisiblethings.blogspot.in/2013/06/qubes-os-r3-alpha-preview-odyssey-hal.html >> >> - Qubes uses upstream Xen vchan now, which means that we "should" interoperate with the ocaml-vchan library. >> >> - They've replaced Xenstore with a simpler transport that removes permissions and uses vchan under the hood. This is also something that should be easier to do with Dave's oxenstore+irmin, since many of the components such as xenstore_transport are functorized, and of Irmin can serialize to several formats including Git, for reconciliation with external databases. >> >> - Qubes looks like an excellent candidate for a 'unikernel' desktop OS! I'm going to try it when I hunt down a PC laptop, but if anyone else gets a chance I'd be interested in hearing about it. > > I haven't tried the new alpha, but I tried the previous version of > Qubes on my new laptop when it first arrived (actually, being able to > try Qubes was one of the reasons I wanted a laptop with Intel > graphics). Woops, this was indeed a year-old blog post as Dave points out. It's still being very actively developed though: http://www.qubes-os.org/trac/timeline > > One interesting thing for Mirage: they have a separate domain (NetVM) > for network drivers, and another for the firewall (FirewallVM): > > http://wiki.qubes-os.org/trac/wiki/QubesFirewall > > FirewallVM is a complete Linux system and requires several hundred MB, > as shown in this screenshot: > > http://wiki.qubes-os.org/trac/attachment/wiki/QubesScreenshots/r2b2-software-update.png That is an interesting application indeed! The other thing that would be useful is a key management VM (which could expose an ssh-agent-like socket proxy via vchan into another domain, to protect against kernel exploits revealing). > > In the end, I only tried it for a few hours before wiping it and > installing Arch instead. Some other problems were that there is no > tiling window manager available, and you can't run VirtualBox on Xen. > Qubes doesn't offer graphics acceleration for guests (due to the focus > on security), which would probably mess up gotomeeting. Out of curiosity, are you running Xen on your laptop at the moment (and if so, which distribution do you use?). I haven't set it up for a while, but everyone I talk to seems to have issues with power management, although pv_ops does allegedly support passing this through from dom0->Xen without issue. -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 Sat Jun 21 14:54:19 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sat, 21 Jun 2014 14:54: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 1WyMgH-0007SR-KT; Sat, 21 Jun 2014 14:54:13 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WyMgG-0007SI-Ct for mirageos-devel@lists.xenproject.org; Sat, 21 Jun 2014 14:54:12 +0000 Received: from [85.158.143.35:32245] by server-2.bemta-4.messagelabs.com id 66/02-06539-39C95A35; Sat, 21 Jun 2014 14:54:11 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-16.tower-21.messagelabs.com!1403362440!9446127!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_8, spamassassin: , async_handler: YXN5bmNfZGVsYXk6IDcwNjQ5MzQgKHRpbWVvdXQp\n X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4876 invoked from network); 21 Jun 2014 14:54:00 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-16.tower-21.messagelabs.com with SMTP; 21 Jun 2014 14:54:00 -0000 Received: (qmail 27894 invoked by uid 634); 21 Jun 2014 14:54:00 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from Unknown (HELO [10.32.5.100]) (37.205.63.157) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Sat, 21 Jun 2014 15:53:59 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\)) From: Anil Madhavapeddy In-Reply-To: Date: Sat, 21 Jun 2014 15:53:52 +0100 Message-Id: <69BCED97-B3DF-41E3-9A26-398FA49322B8@recoil.org> References: <6A38AB63-7876-4CDA-BDE3-87987E926F35@recoil.org> To: Thomas Leonard X-Mailer: Apple Mail (2.1874) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] vchan/xenstore in Qubes r3 X-BeenThere: mirageos-devel@lists.xenproject.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 21 Jun 2014, at 10:02, Thomas Leonard wrote: > On 21 June 2014 08:58, Anil Madhavapeddy wrote: >> A very interesting article from Joanna on the new r3 alpha of QubesOS. >> >> http://theinvisiblethings.blogspot.in/2013/06/qubes-os-r3-alpha-preview-odyssey-hal.html >> >> - Qubes uses upstream Xen vchan now, which means that we "should" interoperate with the ocaml-vchan library. >> >> - They've replaced Xenstore with a simpler transport that removes permissions and uses vchan under the hood. This is also something that should be easier to do with Dave's oxenstore+irmin, since many of the components such as xenstore_transport are functorized, and of Irmin can serialize to several formats including Git, for reconciliation with external databases. >> >> - Qubes looks like an excellent candidate for a 'unikernel' desktop OS! I'm going to try it when I hunt down a PC laptop, but if anyone else gets a chance I'd be interested in hearing about it. > > I haven't tried the new alpha, but I tried the previous version of > Qubes on my new laptop when it first arrived (actually, being able to > try Qubes was one of the reasons I wanted a laptop with Intel > graphics). Woops, this was indeed a year-old blog post as Dave points out. It's still being very actively developed though: http://www.qubes-os.org/trac/timeline > > One interesting thing for Mirage: they have a separate domain (NetVM) > for network drivers, and another for the firewall (FirewallVM): > > http://wiki.qubes-os.org/trac/wiki/QubesFirewall > > FirewallVM is a complete Linux system and requires several hundred MB, > as shown in this screenshot: > > http://wiki.qubes-os.org/trac/attachment/wiki/QubesScreenshots/r2b2-software-update.png That is an interesting application indeed! The other thing that would be useful is a key management VM (which could expose an ssh-agent-like socket proxy via vchan into another domain, to protect against kernel exploits revealing). > > In the end, I only tried it for a few hours before wiping it and > installing Arch instead. Some other problems were that there is no > tiling window manager available, and you can't run VirtualBox on Xen. > Qubes doesn't offer graphics acceleration for guests (due to the focus > on security), which would probably mess up gotomeeting. Out of curiosity, are you running Xen on your laptop at the moment (and if so, which distribution do you use?). I haven't set it up for a while, but everyone I talk to seems to have issues with power management, although pv_ops does allegedly support passing this through from dom0->Xen without issue. -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 Sat Jun 21 14:56:45 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sat, 21 Jun 2014 14:56: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 1WyMii-0007Z4-Ug; Sat, 21 Jun 2014 14:56:44 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WyMih-0007Yy-Lk for mirageos-devel@lists.xenproject.org; Sat, 21 Jun 2014 14:56:43 +0000 Received: from [85.158.143.35:49598] by server-2.bemta-4.messagelabs.com id B6/A2-06539-A2D95A35; Sat, 21 Jun 2014 14:56:42 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-4.tower-21.messagelabs.com!1403362602!12846792!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11339 invoked from network); 21 Jun 2014 14:56:42 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-4.tower-21.messagelabs.com with SMTP; 21 Jun 2014 14:56:42 -0000 Received: (qmail 27288 invoked by uid 634); 21 Jun 2014 14:56:42 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from Unknown (HELO [10.32.5.100]) (37.205.63.157) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Sat, 21 Jun 2014 15:56:42 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\)) From: Anil Madhavapeddy In-Reply-To: Date: Sat, 21 Jun 2014 15:56:38 +0100 Message-Id: References: <6A38AB63-7876-4CDA-BDE3-87987E926F35@recoil.org> To: David Scott X-Mailer: Apple Mail (2.1874) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] vchan/xenstore in Qubes r3 X-BeenThere: mirageos-devel@lists.xenproject.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 21 Jun 2014, at 11:45, David Scott wrote: > > I like the idea of running separate xenstore databases per VM, since there's no need for guest VMs to be able to see any of each other's stuff. The only tricky bit is any shared backends would have to talk to multiple xenstores, and a lot of code has the assumption of a single xenstore built-in. I guess this comes down the semantics of a distributed Xenstore and how to weakening the consistency exposed to VMs under the guise of transactions. Not using a big Xenstore and shifting to a process-per-VM is also the model that Bromium's vSentry adopts for their microvirtualization, if I remember Ian's XenSummit talk right. -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 Sat Jun 21 14:56:45 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sat, 21 Jun 2014 14:56: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 1WyMii-0007Z4-Ug; Sat, 21 Jun 2014 14:56:44 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WyMih-0007Yy-Lk for mirageos-devel@lists.xenproject.org; Sat, 21 Jun 2014 14:56:43 +0000 Received: from [85.158.143.35:49598] by server-2.bemta-4.messagelabs.com id B6/A2-06539-A2D95A35; Sat, 21 Jun 2014 14:56:42 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-4.tower-21.messagelabs.com!1403362602!12846792!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11339 invoked from network); 21 Jun 2014 14:56:42 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-4.tower-21.messagelabs.com with SMTP; 21 Jun 2014 14:56:42 -0000 Received: (qmail 27288 invoked by uid 634); 21 Jun 2014 14:56:42 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from Unknown (HELO [10.32.5.100]) (37.205.63.157) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Sat, 21 Jun 2014 15:56:42 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\)) From: Anil Madhavapeddy In-Reply-To: Date: Sat, 21 Jun 2014 15:56:38 +0100 Message-Id: References: <6A38AB63-7876-4CDA-BDE3-87987E926F35@recoil.org> To: David Scott X-Mailer: Apple Mail (2.1874) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] vchan/xenstore in Qubes r3 X-BeenThere: mirageos-devel@lists.xenproject.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 21 Jun 2014, at 11:45, David Scott wrote: > > I like the idea of running separate xenstore databases per VM, since there's no need for guest VMs to be able to see any of each other's stuff. The only tricky bit is any shared backends would have to talk to multiple xenstores, and a lot of code has the assumption of a single xenstore built-in. I guess this comes down the semantics of a distributed Xenstore and how to weakening the consistency exposed to VMs under the guise of transactions. Not using a big Xenstore and shifting to a process-per-VM is also the model that Bromium's vSentry adopts for their microvirtualization, if I remember Ian's XenSummit talk right. -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 Sat Jun 21 15:02:48 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sat, 21 Jun 2014 15:02: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 1WyMoa-00080U-A1; Sat, 21 Jun 2014 15:02:48 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WyMoZ-00080N-7L for mirageos-devel@lists.xenproject.org; Sat, 21 Jun 2014 15:02:47 +0000 Received: from [85.158.139.211:19237] by server-15.bemta-5.messagelabs.com id 0E/76-19516-69E95A35; Sat, 21 Jun 2014 15:02:46 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-11.tower-206.messagelabs.com!1403362965!7096178!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 13513 invoked from network); 21 Jun 2014 15:02:45 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-11.tower-206.messagelabs.com with SMTP; 21 Jun 2014 15:02:45 -0000 Received: (qmail 20137 invoked by uid 634); 21 Jun 2014 15:02:45 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from Unknown (HELO [10.32.5.100]) (37.205.63.157) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Sat, 21 Jun 2014 16:02:44 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\)) From: Anil Madhavapeddy In-Reply-To: Date: Sat, 21 Jun 2014 16:02:43 +0100 Message-Id: <62442984-A2CE-4E9E-BA14-BBFE10698B8F@recoil.org> References: <1233494D-A05A-4F52-BFE7-9773BD566372@gazagnaire.org> <2C06C3FC-F8F3-4FC4-A7F9-BCD1A2FADE94@recoil.org> To: David Scott X-Mailer: Apple Mail (2.1874) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: David Scott , Thomas Gazagnaire , Jonathan Ludlam , "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] towards a common Mirage 'FLOW' signature X-BeenThere: mirageos-devel@lists.xenproject.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 21 Jun 2014, at 11:36, David Scott wrote: > > I wonder whether we should extend flow to have all 4 of {read,write}{,_ack} so that we can control when data is acked/consumed. The TCP implementation would then only call the _ack function when it had received confirmation the data had been processed. If the TCP implementation needed to resend (possibly after a crash) it could call 'read' again and get back the same data it had before. So the result of 'read' would be an int64 stream offset * Cstruct.t, and 'read_ack' would mark an int64 offset as being consumed. This is what I'm doing in xenstore and shared-memory-ring: I don't know if anyone else wants this kind of behaviour. In the case where a VM sends a block write, which is then sent over NFS/TCP it would allow us to call write_ack on the flow to the guest when the TCP acks are received. Yes, this definitely makes sense. It's very nice to have a clean async notification API for writes, as this could (for example) also eventually bind to storage APIs like libaio for the Unix backend. However, how would NFS/TCP work with FLOW for this? That would require a scatter/gather API (much like the RING requests/responses), whereas FLOW works with streams. Oh, unless you are referring to a FLOW of a single file over NFS/TCP, rather than the underlying XDR RPCs from NFS. (Perhaps we should shift to calling it Flow in e-mail instead of FLOW to AVOID SHOUTING) > Separately, in the case of vchan the buffer size is set at ring setup time. If you connected a vhan ring to a TCP transmitter then the TCP transmitter, presumably with it's higher latency link, would try to keep its link full by buffering more. If the vchan ring size is smaller then the TCP window size (likely), TCP would have to copy into temporary buffers. If we knew we were going to need more buffered data then we could make the vchan ring larger and avoid the copying? Perhaps that wouldn't work due to alignment requirements. Anyway, this is more of a 'flow setup' issue than a during-the-flow issue. Perhaps a CHANNEL would be where we could close and re-open flows in order to adjust their parameters. This is definitely a path-MTU style problem, but the real question is why you would be running TCP directly over vchan, which is a lossless medium. The only use would be for congestion control, and we could consider just cherry picking some of that logic straight out of the TCP stack rather than suffering the overhead of marshalling into the TCP wire format just to go over shared memory. -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 Sat Jun 21 15:02:48 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sat, 21 Jun 2014 15:02: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 1WyMoa-00080U-A1; Sat, 21 Jun 2014 15:02:48 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WyMoZ-00080N-7L for mirageos-devel@lists.xenproject.org; Sat, 21 Jun 2014 15:02:47 +0000 Received: from [85.158.139.211:19237] by server-15.bemta-5.messagelabs.com id 0E/76-19516-69E95A35; Sat, 21 Jun 2014 15:02:46 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-11.tower-206.messagelabs.com!1403362965!7096178!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 13513 invoked from network); 21 Jun 2014 15:02:45 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-11.tower-206.messagelabs.com with SMTP; 21 Jun 2014 15:02:45 -0000 Received: (qmail 20137 invoked by uid 634); 21 Jun 2014 15:02:45 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from Unknown (HELO [10.32.5.100]) (37.205.63.157) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Sat, 21 Jun 2014 16:02:44 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\)) From: Anil Madhavapeddy In-Reply-To: Date: Sat, 21 Jun 2014 16:02:43 +0100 Message-Id: <62442984-A2CE-4E9E-BA14-BBFE10698B8F@recoil.org> References: <1233494D-A05A-4F52-BFE7-9773BD566372@gazagnaire.org> <2C06C3FC-F8F3-4FC4-A7F9-BCD1A2FADE94@recoil.org> To: David Scott X-Mailer: Apple Mail (2.1874) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: David Scott , Thomas Gazagnaire , Jonathan Ludlam , "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] towards a common Mirage 'FLOW' signature X-BeenThere: mirageos-devel@lists.xenproject.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 21 Jun 2014, at 11:36, David Scott wrote: > > I wonder whether we should extend flow to have all 4 of {read,write}{,_ack} so that we can control when data is acked/consumed. The TCP implementation would then only call the _ack function when it had received confirmation the data had been processed. If the TCP implementation needed to resend (possibly after a crash) it could call 'read' again and get back the same data it had before. So the result of 'read' would be an int64 stream offset * Cstruct.t, and 'read_ack' would mark an int64 offset as being consumed. This is what I'm doing in xenstore and shared-memory-ring: I don't know if anyone else wants this kind of behaviour. In the case where a VM sends a block write, which is then sent over NFS/TCP it would allow us to call write_ack on the flow to the guest when the TCP acks are received. Yes, this definitely makes sense. It's very nice to have a clean async notification API for writes, as this could (for example) also eventually bind to storage APIs like libaio for the Unix backend. However, how would NFS/TCP work with FLOW for this? That would require a scatter/gather API (much like the RING requests/responses), whereas FLOW works with streams. Oh, unless you are referring to a FLOW of a single file over NFS/TCP, rather than the underlying XDR RPCs from NFS. (Perhaps we should shift to calling it Flow in e-mail instead of FLOW to AVOID SHOUTING) > Separately, in the case of vchan the buffer size is set at ring setup time. If you connected a vhan ring to a TCP transmitter then the TCP transmitter, presumably with it's higher latency link, would try to keep its link full by buffering more. If the vchan ring size is smaller then the TCP window size (likely), TCP would have to copy into temporary buffers. If we knew we were going to need more buffered data then we could make the vchan ring larger and avoid the copying? Perhaps that wouldn't work due to alignment requirements. Anyway, this is more of a 'flow setup' issue than a during-the-flow issue. Perhaps a CHANNEL would be where we could close and re-open flows in order to adjust their parameters. This is definitely a path-MTU style problem, but the real question is why you would be running TCP directly over vchan, which is a lossless medium. The only use would be for congestion control, and we could consider just cherry picking some of that logic straight out of the TCP stack rather than suffering the overhead of marshalling into the TCP wire format just to go over shared memory. -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 Sat Jun 21 15:07:06 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sat, 21 Jun 2014 15:07: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 1WyMsi-00083V-Pg; Sat, 21 Jun 2014 15:07:04 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WyMsh-00083Q-6y for mirageos-devel@lists.xenproject.org; Sat, 21 Jun 2014 15:07:03 +0000 Received: from [85.158.139.211:48190] by server-14.bemta-5.messagelabs.com id 1A/FF-27057-69F95A35; Sat, 21 Jun 2014 15:07:02 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-15.tower-206.messagelabs.com!1403363221!7874104!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21377 invoked from network); 21 Jun 2014 15:07:02 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-15.tower-206.messagelabs.com with SMTP; 21 Jun 2014 15:07:02 -0000 Received: (qmail 24013 invoked by uid 634); 21 Jun 2014 15:07:01 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from Unknown (HELO [10.32.5.100]) (37.205.63.157) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Sat, 21 Jun 2014 16:07:01 +0100 From: Anil Madhavapeddy Message-Id: <3406CA70-0595-4575-9CCE-85925217C11B@recoil.org> Date: Sat, 21 Jun 2014 16:07:00 +0100 To: mirageos-devel@lists.xenproject.org Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\)) X-Mailer: Apple Mail (2.1874) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Subject: [MirageOS-devel] Using Clock directly from the mirage tool X-BeenThere: mirageos-devel@lists.xenproject.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 Hannes, David, You mentioned a problem with the Mirage frontend not exposing a generator for Clock directly to unikernels. ThomasG thought that it should be an easy fix, but I can't find a bug open for this. Is it still an issue? I'd like to release Mirage 1.2.0 (with the `make depend` fix) soon, and we could add this into the CLI at the same time. 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 Sat Jun 21 15:07:06 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sat, 21 Jun 2014 15:07: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 1WyMsi-00083V-Pg; Sat, 21 Jun 2014 15:07:04 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WyMsh-00083Q-6y for mirageos-devel@lists.xenproject.org; Sat, 21 Jun 2014 15:07:03 +0000 Received: from [85.158.139.211:48190] by server-14.bemta-5.messagelabs.com id 1A/FF-27057-69F95A35; Sat, 21 Jun 2014 15:07:02 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-15.tower-206.messagelabs.com!1403363221!7874104!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21377 invoked from network); 21 Jun 2014 15:07:02 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-15.tower-206.messagelabs.com with SMTP; 21 Jun 2014 15:07:02 -0000 Received: (qmail 24013 invoked by uid 634); 21 Jun 2014 15:07:01 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from Unknown (HELO [10.32.5.100]) (37.205.63.157) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Sat, 21 Jun 2014 16:07:01 +0100 From: Anil Madhavapeddy Message-Id: <3406CA70-0595-4575-9CCE-85925217C11B@recoil.org> Date: Sat, 21 Jun 2014 16:07:00 +0100 To: mirageos-devel@lists.xenproject.org Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\)) X-Mailer: Apple Mail (2.1874) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Subject: [MirageOS-devel] Using Clock directly from the mirage tool X-BeenThere: mirageos-devel@lists.xenproject.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 Hannes, David, You mentioned a problem with the Mirage frontend not exposing a generator for Clock directly to unikernels. ThomasG thought that it should be an easy fix, but I can't find a bug open for this. Is it still an issue? I'd like to release Mirage 1.2.0 (with the `make depend` fix) soon, and we could add this into the CLI at the same time. 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 Sat Jun 21 16:07:56 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sat, 21 Jun 2014 16:07: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 1WyNpZ-00012V-I7; Sat, 21 Jun 2014 16:07:53 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WyNpY-00012Q-Tv for mirageos-devel@lists.xenproject.org; Sat, 21 Jun 2014 16:07:53 +0000 Received: from [85.158.143.35:40653] by server-3.bemta-4.messagelabs.com id C2/13-16194-8DDA5A35; Sat, 21 Jun 2014 16:07:52 +0000 X-Env-Sender: hannes@mehnert.org X-Msg-Ref: server-11.tower-21.messagelabs.com!1403366871!12860767!1 X-Originating-IP: [213.73.89.200] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27532 invoked from network); 21 Jun 2014 16:07:51 -0000 Received: from mail.mehnert.org (HELO mail.mehnert.org) (213.73.89.200) by server-11.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 21 Jun 2014 16:07:51 -0000 Received: from [128.232.110.146] (c146.al.cl.cam.ac.uk [128.232.110.146]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client CN "hannes@mehnert.org", Issuer "mehnert root CA" (verified OK)) by mail.mehnert.org (Postfix) with ESMTPS id 064CB3D55 for ; Sat, 21 Jun 2014 18:07:49 +0200 (CEST) Message-ID: <53A5AD92.3040404@mehnert.org> Date: Sat, 21 Jun 2014 17:06:42 +0100 From: Hannes Mehnert User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: mirageos-devel@lists.xenproject.org References: <3406CA70-0595-4575-9CCE-85925217C11B@recoil.org> In-Reply-To: <3406CA70-0595-4575-9CCE-85925217C11B@recoil.org> Subject: Re: [MirageOS-devel] Using Clock directly from the mirage tool X-BeenThere: mirageos-devel@lists.xenproject.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 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA384 On 06/21/2014 16:07, Anil Madhavapeddy wrote: > You mentioned a problem with the Mirage frontend not exposing a > generator for Clock directly to unikernels. ThomasG thought that > it should be an easy fix, but I can't find a bug open for this. Is > it still an issue? It is. Our current workaround is to require mirage-clock-unix: https://github.com/mirleft/ocaml-tls/commit/4e54d3122c882552198c0eacfbb7af9d67888d32 (and our X509 module requires a CLOCK): https://github.com/mirleft/ocaml-tls/commit/8a71e7fca4e022edaeb79076972ce7818ed30ac9 Cheers, Hannes -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (FreeBSD) iQIcBAEBCQAGBQJTpa2SAAoJELyJZYjffCjuZosP/iyDmr+opg2fEt0/6INyCSx+ MIUeWSDcWb8QgoEwxrFmwu14m11LAuUEQnAQrtCyLfwtZXNzdyXaGag1royKzljI IOz2UeFMikt4MGKVEmjWWrNTjD9I8eQpaNP11e8slIbRl0r4Fqz66y+Nmov1GgPh KLTquxTiOVaNuWxbVU9CT/U8L9L4wTTeQ4iZAknQAy39nxA+6ys8a+Y4J+7NOdCh Zt+RZmbYJ+PvX9H3CV5NwuW1NaW7/MfmEB+6iUwifS/Pkrw9TFsyHiGqnLnza8Ag CgJCy3iWko5guTY70xecAtjjCmyXud27FYklGa815S8DGxZtWz+dqKGIigLgi21z BLFttj6RLrgR7GK8Of5bYdpA+zylw/68QyOlgftYGLSHqavOJtSMpWznj7c72bpH kenLKBCs2qvX/wpVyjf+IifwuVY3SHDTyxuCRVO7U9kb1EzMvDWXNJqWHNWPfLUD GzBlsHqeHiLD6VP72Mo30QE3bg65uWguUu8Eg50Bn+QOUp1AQzXw5WMa5boXy1Eo lJt21pMQY0tt6KT7jYBMWBmNKVIiZSVnFof7lbEzOIMYST5+fJFy5a9+S6dzOC+R wQmcqOIlD1UDvaPlIVNGpW81ENxbLPskL0UrkU0Uy9+onZsXeZQC2zLA6/476e7A DkIDNiX17m2CaF/2JXzB =rTHy -----END PGP SIGNATURE----- _______________________________________________ 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 Jun 21 16:07:56 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sat, 21 Jun 2014 16:07: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 1WyNpZ-00012V-I7; Sat, 21 Jun 2014 16:07:53 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WyNpY-00012Q-Tv for mirageos-devel@lists.xenproject.org; Sat, 21 Jun 2014 16:07:53 +0000 Received: from [85.158.143.35:40653] by server-3.bemta-4.messagelabs.com id C2/13-16194-8DDA5A35; Sat, 21 Jun 2014 16:07:52 +0000 X-Env-Sender: hannes@mehnert.org X-Msg-Ref: server-11.tower-21.messagelabs.com!1403366871!12860767!1 X-Originating-IP: [213.73.89.200] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27532 invoked from network); 21 Jun 2014 16:07:51 -0000 Received: from mail.mehnert.org (HELO mail.mehnert.org) (213.73.89.200) by server-11.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 21 Jun 2014 16:07:51 -0000 Received: from [128.232.110.146] (c146.al.cl.cam.ac.uk [128.232.110.146]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client CN "hannes@mehnert.org", Issuer "mehnert root CA" (verified OK)) by mail.mehnert.org (Postfix) with ESMTPS id 064CB3D55 for ; Sat, 21 Jun 2014 18:07:49 +0200 (CEST) Message-ID: <53A5AD92.3040404@mehnert.org> Date: Sat, 21 Jun 2014 17:06:42 +0100 From: Hannes Mehnert User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: mirageos-devel@lists.xenproject.org References: <3406CA70-0595-4575-9CCE-85925217C11B@recoil.org> In-Reply-To: <3406CA70-0595-4575-9CCE-85925217C11B@recoil.org> Subject: Re: [MirageOS-devel] Using Clock directly from the mirage tool X-BeenThere: mirageos-devel@lists.xenproject.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 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA384 On 06/21/2014 16:07, Anil Madhavapeddy wrote: > You mentioned a problem with the Mirage frontend not exposing a > generator for Clock directly to unikernels. ThomasG thought that > it should be an easy fix, but I can't find a bug open for this. Is > it still an issue? It is. Our current workaround is to require mirage-clock-unix: https://github.com/mirleft/ocaml-tls/commit/4e54d3122c882552198c0eacfbb7af9d67888d32 (and our X509 module requires a CLOCK): https://github.com/mirleft/ocaml-tls/commit/8a71e7fca4e022edaeb79076972ce7818ed30ac9 Cheers, Hannes -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (FreeBSD) iQIcBAEBCQAGBQJTpa2SAAoJELyJZYjffCjuZosP/iyDmr+opg2fEt0/6INyCSx+ MIUeWSDcWb8QgoEwxrFmwu14m11LAuUEQnAQrtCyLfwtZXNzdyXaGag1royKzljI IOz2UeFMikt4MGKVEmjWWrNTjD9I8eQpaNP11e8slIbRl0r4Fqz66y+Nmov1GgPh KLTquxTiOVaNuWxbVU9CT/U8L9L4wTTeQ4iZAknQAy39nxA+6ys8a+Y4J+7NOdCh Zt+RZmbYJ+PvX9H3CV5NwuW1NaW7/MfmEB+6iUwifS/Pkrw9TFsyHiGqnLnza8Ag CgJCy3iWko5guTY70xecAtjjCmyXud27FYklGa815S8DGxZtWz+dqKGIigLgi21z BLFttj6RLrgR7GK8Of5bYdpA+zylw/68QyOlgftYGLSHqavOJtSMpWznj7c72bpH kenLKBCs2qvX/wpVyjf+IifwuVY3SHDTyxuCRVO7U9kb1EzMvDWXNJqWHNWPfLUD GzBlsHqeHiLD6VP72Mo30QE3bg65uWguUu8Eg50Bn+QOUp1AQzXw5WMa5boXy1Eo lJt21pMQY0tt6KT7jYBMWBmNKVIiZSVnFof7lbEzOIMYST5+fJFy5a9+S6dzOC+R wQmcqOIlD1UDvaPlIVNGpW81ENxbLPskL0UrkU0Uy9+onZsXeZQC2zLA6/476e7A DkIDNiX17m2CaF/2JXzB =rTHy -----END PGP SIGNATURE----- _______________________________________________ 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 Jun 21 22:18:11 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sat, 21 Jun 2014 22:18: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 1WyTbp-0006Cw-8i; Sat, 21 Jun 2014 22:18:05 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WyTbn-0006Cr-4q for mirageos-devel@lists.xenproject.org; Sat, 21 Jun 2014 22:18:03 +0000 Received: from [85.158.139.211:2525] by server-12.bemta-5.messagelabs.com id 98/F0-27841-A9406A35; Sat, 21 Jun 2014 22:18:02 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-12.tower-206.messagelabs.com!1403389081!11240277!1 X-Originating-IP: [209.85.212.176] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4739 invoked from network); 21 Jun 2014 22:18:01 -0000 Received: from mail-wi0-f176.google.com (HELO mail-wi0-f176.google.com) (209.85.212.176) by server-12.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 21 Jun 2014 22:18:01 -0000 Received: by mail-wi0-f176.google.com with SMTP id n3so2338866wiv.9 for ; Sat, 21 Jun 2014 15:18:01 -0700 (PDT) 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=0hht//K+GqginMuEeUKW1pc2Q+mr9G2jyuYNk4yrghQ=; b=YQ8ZmJ1+w333US9DVqEIXR0tGyzWF4d5geSG1YvFsoQay+kKoNGoRYju3hcMnqjkyM 2Ibz9amlCweW5LhXQHhKgjMThzP3eAEL3LJQkdKTzZeZqOYBeqtNnpqYgLztiWegQzzS dOgC1zM5uxGMJJY2CjEBuqCUjAkiyDTEBLzor+2ldJnrdPeyrthGcCbU4OXCQAoKW1FG 70YKfk/BtpimnFt+lcar5fi/C4gM5+uxtTKaOh0Tvv9ZYiSrPV+TSSZjn6uhnx5EdtJ6 cL9r+8V4SL+aVsFRaJBssY33DanbpZ/V+WYepmhLp94n/VJ4STJNVBRLgStxJVWOgDEx XGNA== X-Received: by 10.180.97.195 with SMTP id ec3mr14201580wib.13.1403389081127; Sat, 21 Jun 2014 15:18:01 -0700 (PDT) Received: from [192.168.0.8] (cpc25-cmbg14-2-0-cust121.5-4.cable.virginm.net. [213.106.112.122]) by mx.google.com with ESMTPSA id s3sm24980091wje.36.2014.06.21.15.17.59 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 21 Jun 2014 15:18:00 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\)) From: Thomas Gazagnaire In-Reply-To: <53A5AD92.3040404@mehnert.org> Date: Sat, 21 Jun 2014 23:17:56 +0100 Message-Id: References: <3406CA70-0595-4575-9CCE-85925217C11B@recoil.org> <53A5AD92.3040404@mehnert.org> To: Hannes Mehnert X-Mailer: Apple Mail (2.1878.2) Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Using Clock directly from the mirage tool X-BeenThere: mirageos-devel@lists.xenproject.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 Done in https://github.com/mirage/mirage/pull/255 Note, the PR contains slightly more changes that really needed, but I think I didn't break any user code. In doubt, the only relevant commit is https://github.com/samoht/mirage/commit/68958f760f35e6dd259eddfcc803395041a72891 Thomas On 21 Jun 2014, at 17:06, Hannes Mehnert wrote: > Signed PGP part > On 06/21/2014 16:07, Anil Madhavapeddy wrote: > > You mentioned a problem with the Mirage frontend not exposing a > > generator for Clock directly to unikernels. ThomasG thought that > > it should be an easy fix, but I can't find a bug open for this. Is > > it still an issue? > > It is. Our current workaround is to require mirage-clock-unix: > https://github.com/mirleft/ocaml-tls/commit/4e54d3122c882552198c0eacfbb7af9d67888d32 > > (and our X509 module requires a CLOCK): > https://github.com/mirleft/ocaml-tls/commit/8a71e7fca4e022edaeb79076972ce7818ed30ac9 > > Cheers, > > Hannes > > > _______________________________________________ > 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 Jun 21 22:18:11 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sat, 21 Jun 2014 22:18: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 1WyTbp-0006Cw-8i; Sat, 21 Jun 2014 22:18:05 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WyTbn-0006Cr-4q for mirageos-devel@lists.xenproject.org; Sat, 21 Jun 2014 22:18:03 +0000 Received: from [85.158.139.211:2525] by server-12.bemta-5.messagelabs.com id 98/F0-27841-A9406A35; Sat, 21 Jun 2014 22:18:02 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-12.tower-206.messagelabs.com!1403389081!11240277!1 X-Originating-IP: [209.85.212.176] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4739 invoked from network); 21 Jun 2014 22:18:01 -0000 Received: from mail-wi0-f176.google.com (HELO mail-wi0-f176.google.com) (209.85.212.176) by server-12.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 21 Jun 2014 22:18:01 -0000 Received: by mail-wi0-f176.google.com with SMTP id n3so2338866wiv.9 for ; Sat, 21 Jun 2014 15:18:01 -0700 (PDT) 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=0hht//K+GqginMuEeUKW1pc2Q+mr9G2jyuYNk4yrghQ=; b=YQ8ZmJ1+w333US9DVqEIXR0tGyzWF4d5geSG1YvFsoQay+kKoNGoRYju3hcMnqjkyM 2Ibz9amlCweW5LhXQHhKgjMThzP3eAEL3LJQkdKTzZeZqOYBeqtNnpqYgLztiWegQzzS dOgC1zM5uxGMJJY2CjEBuqCUjAkiyDTEBLzor+2ldJnrdPeyrthGcCbU4OXCQAoKW1FG 70YKfk/BtpimnFt+lcar5fi/C4gM5+uxtTKaOh0Tvv9ZYiSrPV+TSSZjn6uhnx5EdtJ6 cL9r+8V4SL+aVsFRaJBssY33DanbpZ/V+WYepmhLp94n/VJ4STJNVBRLgStxJVWOgDEx XGNA== X-Received: by 10.180.97.195 with SMTP id ec3mr14201580wib.13.1403389081127; Sat, 21 Jun 2014 15:18:01 -0700 (PDT) Received: from [192.168.0.8] (cpc25-cmbg14-2-0-cust121.5-4.cable.virginm.net. [213.106.112.122]) by mx.google.com with ESMTPSA id s3sm24980091wje.36.2014.06.21.15.17.59 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 21 Jun 2014 15:18:00 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\)) From: Thomas Gazagnaire In-Reply-To: <53A5AD92.3040404@mehnert.org> Date: Sat, 21 Jun 2014 23:17:56 +0100 Message-Id: References: <3406CA70-0595-4575-9CCE-85925217C11B@recoil.org> <53A5AD92.3040404@mehnert.org> To: Hannes Mehnert X-Mailer: Apple Mail (2.1878.2) Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Using Clock directly from the mirage tool X-BeenThere: mirageos-devel@lists.xenproject.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 Done in https://github.com/mirage/mirage/pull/255 Note, the PR contains slightly more changes that really needed, but I think I didn't break any user code. In doubt, the only relevant commit is https://github.com/samoht/mirage/commit/68958f760f35e6dd259eddfcc803395041a72891 Thomas On 21 Jun 2014, at 17:06, Hannes Mehnert wrote: > Signed PGP part > On 06/21/2014 16:07, Anil Madhavapeddy wrote: > > You mentioned a problem with the Mirage frontend not exposing a > > generator for Clock directly to unikernels. ThomasG thought that > > it should be an easy fix, but I can't find a bug open for this. Is > > it still an issue? > > It is. Our current workaround is to require mirage-clock-unix: > https://github.com/mirleft/ocaml-tls/commit/4e54d3122c882552198c0eacfbb7af9d67888d32 > > (and our X509 module requires a CLOCK): > https://github.com/mirleft/ocaml-tls/commit/8a71e7fca4e022edaeb79076972ce7818ed30ac9 > > Cheers, > > Hannes > > > _______________________________________________ > 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 Jun 22 10:44:44 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 22 Jun 2014 10:44: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 1WyfGI-0003rl-D1; Sun, 22 Jun 2014 10:44:38 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WyfGH-0003rg-6o for mirageos-devel@lists.xenproject.org; Sun, 22 Jun 2014 10:44:37 +0000 Received: from [85.158.137.68:5508] by server-2.bemta-3.messagelabs.com id 45/BA-13558-493B6A35; Sun, 22 Jun 2014 10:44:36 +0000 X-Env-Sender: talex5@gmail.com X-Msg-Ref: server-2.tower-31.messagelabs.com!1403433863!11571860!1 X-Originating-IP: [209.85.219.54] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, ML_RADAR_SPEW_LINKS_23, ML_RADAR_SPEW_LINKS_8, RCVD_BY_IP, spamassassin: , async_handler: YXN5bmNfZGVsYXk6IDcwNTM3NTggKHRpbWVvdXQp\n X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15423 invoked from network); 22 Jun 2014 10:44:24 -0000 Received: from mail-oa0-f54.google.com (HELO mail-oa0-f54.google.com) (209.85.219.54) by server-2.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 22 Jun 2014 10:44:24 -0000 Received: by mail-oa0-f54.google.com with SMTP id eb12so9086282oac.13 for ; Sun, 22 Jun 2014 03:44:23 -0700 (PDT) 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=3xDhdzSny8C6linhWOXohQ3GR7xlpP304sdC1JO0KO4=; b=y3VPUhve3hvLiPWpLRsOUSNr/zq3xdbi8fGa6tXWWDwCu51LgimoMvhfV9dur6DfRU vnfrKB9RCvJKFxUv0kKyx+u7+Bz12uYOzDjhr9Er8h7jTVmkcJ8Ju2qy2QMQe08pKRff MszDj3es3wY2VlPWgn3Q0vM5tWaZHplEemJWzrRIN/oKeT2Z+Vc4uaGqjwCIwMOOItXQ 5NEl7mZJ6gl82uYcIqckvT4g1BeOdWf+kVcgSPfZW6PI1l++ilkJYdqk0sY1eU6pCK8f 2Dt14YjzYr0k5LZv7zty/RijNVUxwWJ/bPL7cqTMF1AUmdYngl76CSRKfetUzKXUCN31 ISYA== MIME-Version: 1.0 X-Received: by 10.182.81.99 with SMTP id z3mr823428obx.79.1403433863238; Sun, 22 Jun 2014 03:44:23 -0700 (PDT) Received: by 10.76.92.5 with HTTP; Sun, 22 Jun 2014 03:44:23 -0700 (PDT) In-Reply-To: <69BCED97-B3DF-41E3-9A26-398FA49322B8@recoil.org> References: <6A38AB63-7876-4CDA-BDE3-87987E926F35@recoil.org> <69BCED97-B3DF-41E3-9A26-398FA49322B8@recoil.org> Date: Sun, 22 Jun 2014 11:44:23 +0100 Message-ID: From: Thomas Leonard To: Anil Madhavapeddy Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] vchan/xenstore in Qubes r3 X-BeenThere: mirageos-devel@lists.xenproject.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 21 June 2014 15:53, Anil Madhavapeddy wrote: > On 21 Jun 2014, at 10:02, Thomas Leonard wrote: > >> On 21 June 2014 08:58, Anil Madhavapeddy wrote: >>> A very interesting article from Joanna on the new r3 alpha of QubesOS. >>> >>> http://theinvisiblethings.blogspot.in/2013/06/qubes-os-r3-alpha-preview-odyssey-hal.html >>> >>> - Qubes uses upstream Xen vchan now, which means that we "should" interoperate with the ocaml-vchan library. >>> >>> - They've replaced Xenstore with a simpler transport that removes permissions and uses vchan under the hood. This is also something that should be easier to do with Dave's oxenstore+irmin, since many of the components such as xenstore_transport are functorized, and of Irmin can serialize to several formats including Git, for reconciliation with external databases. >>> >>> - Qubes looks like an excellent candidate for a 'unikernel' desktop OS! I'm going to try it when I hunt down a PC laptop, but if anyone else gets a chance I'd be interested in hearing about it. >> >> I haven't tried the new alpha, but I tried the previous version of >> Qubes on my new laptop when it first arrived (actually, being able to >> try Qubes was one of the reasons I wanted a laptop with Intel >> graphics). > > Woops, this was indeed a year-old blog post as Dave points out. It's > still being very actively developed though: > > http://www.qubes-os.org/trac/timeline > >> >> One interesting thing for Mirage: they have a separate domain (NetVM) >> for network drivers, and another for the firewall (FirewallVM): >> >> http://wiki.qubes-os.org/trac/wiki/QubesFirewall >> >> FirewallVM is a complete Linux system and requires several hundred MB, >> as shown in this screenshot: >> >> http://wiki.qubes-os.org/trac/attachment/wiki/QubesScreenshots/r2b2-software-update.png > > That is an interesting application indeed! The other thing that would > be useful is a key management VM (which could expose an ssh-agent-like > socket proxy via vchan into another domain, to protect against kernel > exploits revealing). > >> >> In the end, I only tried it for a few hours before wiping it and >> installing Arch instead. Some other problems were that there is no >> tiling window manager available, and you can't run VirtualBox on Xen. >> Qubes doesn't offer graphics acceleration for guests (due to the focus >> on security), which would probably mess up gotomeeting. > > Out of curiosity, are you running Xen on your laptop at the moment > (and if so, which distribution do you use?). I haven't set it up for > a while, but everyone I talk to seems to have issues with power > management, although pv_ops does allegedly support passing this through > from dom0->Xen without issue. On the laptop I don't run Xen directly. For testing, I run it under Virtual Box (Mirage works fine that way, but I can't run HVM guests). I still have power issues though! If I suspend the host, then the Xen VM dies for some reason and needs to be rebooted. I am tempted to run Xen directly on the laptop, but I suspect it wouldn't be as slick for graphical guests (pointer and clipboard integration, graphics acceleration, etc). I tried running Windows under KVM with virt-manager and it wasn't very usable. I imagine Xen would be the same. -- 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 Sun Jun 22 10:44:44 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 22 Jun 2014 10:44: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 1WyfGI-0003rl-D1; Sun, 22 Jun 2014 10:44:38 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WyfGH-0003rg-6o for mirageos-devel@lists.xenproject.org; Sun, 22 Jun 2014 10:44:37 +0000 Received: from [85.158.137.68:5508] by server-2.bemta-3.messagelabs.com id 45/BA-13558-493B6A35; Sun, 22 Jun 2014 10:44:36 +0000 X-Env-Sender: talex5@gmail.com X-Msg-Ref: server-2.tower-31.messagelabs.com!1403433863!11571860!1 X-Originating-IP: [209.85.219.54] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, ML_RADAR_SPEW_LINKS_23, ML_RADAR_SPEW_LINKS_8, RCVD_BY_IP, spamassassin: , async_handler: YXN5bmNfZGVsYXk6IDcwNTM3NTggKHRpbWVvdXQp\n X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15423 invoked from network); 22 Jun 2014 10:44:24 -0000 Received: from mail-oa0-f54.google.com (HELO mail-oa0-f54.google.com) (209.85.219.54) by server-2.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 22 Jun 2014 10:44:24 -0000 Received: by mail-oa0-f54.google.com with SMTP id eb12so9086282oac.13 for ; Sun, 22 Jun 2014 03:44:23 -0700 (PDT) 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=3xDhdzSny8C6linhWOXohQ3GR7xlpP304sdC1JO0KO4=; b=y3VPUhve3hvLiPWpLRsOUSNr/zq3xdbi8fGa6tXWWDwCu51LgimoMvhfV9dur6DfRU vnfrKB9RCvJKFxUv0kKyx+u7+Bz12uYOzDjhr9Er8h7jTVmkcJ8Ju2qy2QMQe08pKRff MszDj3es3wY2VlPWgn3Q0vM5tWaZHplEemJWzrRIN/oKeT2Z+Vc4uaGqjwCIwMOOItXQ 5NEl7mZJ6gl82uYcIqckvT4g1BeOdWf+kVcgSPfZW6PI1l++ilkJYdqk0sY1eU6pCK8f 2Dt14YjzYr0k5LZv7zty/RijNVUxwWJ/bPL7cqTMF1AUmdYngl76CSRKfetUzKXUCN31 ISYA== MIME-Version: 1.0 X-Received: by 10.182.81.99 with SMTP id z3mr823428obx.79.1403433863238; Sun, 22 Jun 2014 03:44:23 -0700 (PDT) Received: by 10.76.92.5 with HTTP; Sun, 22 Jun 2014 03:44:23 -0700 (PDT) In-Reply-To: <69BCED97-B3DF-41E3-9A26-398FA49322B8@recoil.org> References: <6A38AB63-7876-4CDA-BDE3-87987E926F35@recoil.org> <69BCED97-B3DF-41E3-9A26-398FA49322B8@recoil.org> Date: Sun, 22 Jun 2014 11:44:23 +0100 Message-ID: From: Thomas Leonard To: Anil Madhavapeddy Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] vchan/xenstore in Qubes r3 X-BeenThere: mirageos-devel@lists.xenproject.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 21 June 2014 15:53, Anil Madhavapeddy wrote: > On 21 Jun 2014, at 10:02, Thomas Leonard wrote: > >> On 21 June 2014 08:58, Anil Madhavapeddy wrote: >>> A very interesting article from Joanna on the new r3 alpha of QubesOS. >>> >>> http://theinvisiblethings.blogspot.in/2013/06/qubes-os-r3-alpha-preview-odyssey-hal.html >>> >>> - Qubes uses upstream Xen vchan now, which means that we "should" interoperate with the ocaml-vchan library. >>> >>> - They've replaced Xenstore with a simpler transport that removes permissions and uses vchan under the hood. This is also something that should be easier to do with Dave's oxenstore+irmin, since many of the components such as xenstore_transport are functorized, and of Irmin can serialize to several formats including Git, for reconciliation with external databases. >>> >>> - Qubes looks like an excellent candidate for a 'unikernel' desktop OS! I'm going to try it when I hunt down a PC laptop, but if anyone else gets a chance I'd be interested in hearing about it. >> >> I haven't tried the new alpha, but I tried the previous version of >> Qubes on my new laptop when it first arrived (actually, being able to >> try Qubes was one of the reasons I wanted a laptop with Intel >> graphics). > > Woops, this was indeed a year-old blog post as Dave points out. It's > still being very actively developed though: > > http://www.qubes-os.org/trac/timeline > >> >> One interesting thing for Mirage: they have a separate domain (NetVM) >> for network drivers, and another for the firewall (FirewallVM): >> >> http://wiki.qubes-os.org/trac/wiki/QubesFirewall >> >> FirewallVM is a complete Linux system and requires several hundred MB, >> as shown in this screenshot: >> >> http://wiki.qubes-os.org/trac/attachment/wiki/QubesScreenshots/r2b2-software-update.png > > That is an interesting application indeed! The other thing that would > be useful is a key management VM (which could expose an ssh-agent-like > socket proxy via vchan into another domain, to protect against kernel > exploits revealing). > >> >> In the end, I only tried it for a few hours before wiping it and >> installing Arch instead. Some other problems were that there is no >> tiling window manager available, and you can't run VirtualBox on Xen. >> Qubes doesn't offer graphics acceleration for guests (due to the focus >> on security), which would probably mess up gotomeeting. > > Out of curiosity, are you running Xen on your laptop at the moment > (and if so, which distribution do you use?). I haven't set it up for > a while, but everyone I talk to seems to have issues with power > management, although pv_ops does allegedly support passing this through > from dom0->Xen without issue. On the laptop I don't run Xen directly. For testing, I run it under Virtual Box (Mirage works fine that way, but I can't run HVM guests). I still have power issues though! If I suspend the host, then the Xen VM dies for some reason and needs to be rebooted. I am tempted to run Xen directly on the laptop, but I suspect it wouldn't be as slick for graphical guests (pointer and clipboard integration, graphics acceleration, etc). I tried running Windows under KVM with virt-manager and it wasn't very usable. I imagine Xen would be the same. -- 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 Sun Jun 22 11:00:51 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 22 Jun 2014 11:00: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 1WyfVx-0003we-Lh; Sun, 22 Jun 2014 11:00:49 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WyfVw-0003wZ-0z for mirageos-devel@lists.xenproject.org; Sun, 22 Jun 2014 11:00:48 +0000 Received: from [193.109.254.147:19089] by server-13.bemta-14.messagelabs.com id A2/A9-23211-E57B6A35; Sun, 22 Jun 2014 11:00:46 +0000 X-Env-Sender: Dave.Scott@citrix.com X-Msg-Ref: server-9.tower-27.messagelabs.com!1403434845!12845225!1 X-Originating-IP: [185.25.65.24] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_8, spamassassin: , surbl: (ASYNC_NO) c3VyYmxfcmVjaGVja19kZWxheTogMCAoYWJhbmRv bmVkOiB0aGVpbnZpc2libGV0aGluZ3MuYmxv\nZ3Nwb3QuaW4p\n X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20800 invoked from network); 22 Jun 2014 11:00:45 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (185.25.65.24) by server-9.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 22 Jun 2014 11:00:45 -0000 X-IronPort-AV: E=Sophos;i="5.01,523,1400025600"; d="scan'208";a="21850874" Received: from unknown (HELO AMSPEX01CL02.citrite.net) ([10.69.60.9]) by AMSPIP01.EU.Citrix.com with ESMTP; 22 Jun 2014 11:00:44 +0000 Received: from AMSPEX01CL03.citrite.net ([169.254.8.89]) by AMSPEX01CL02.citrite.net ([10.69.46.33]) with mapi id 14.03.0181.006; Sun, 22 Jun 2014 13:00:44 +0200 From: Dave Scott To: Thomas Leonard Thread-Topic: [MirageOS-devel] vchan/xenstore in Qubes r3 Thread-Index: AQHPjSaxc0muaRmEm0y9tL34lhIS7Zt7IzQAgABiMwCAAUyggIAABIuA Date: Sun, 22 Jun 2014 11:00:42 +0000 Message-ID: References: <6A38AB63-7876-4CDA-BDE3-87987E926F35@recoil.org> <69BCED97-B3DF-41E3-9A26-398FA49322B8@recoil.org> In-Reply-To: Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.13.112.14] Content-ID: <310779E6E3F7294F85CCEF69CE67F619@citrix.com> MIME-Version: 1.0 X-DLP: AMS1 Cc: "mirageos-devel@lists.xenproject.org" , Anil Madhavapeddy Subject: Re: [MirageOS-devel] vchan/xenstore in Qubes r3 X-BeenThere: mirageos-devel@lists.xenproject.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 22 Jun 2014, at 11:44, Thomas Leonard wrote: > On 21 June 2014 15:53, Anil Madhavapeddy wrote: >> On 21 Jun 2014, at 10:02, Thomas Leonard wrote: >> = >>> On 21 June 2014 08:58, Anil Madhavapeddy wrote: >>>> A very interesting article from Joanna on the new r3 alpha of QubesOS. >>>> = >>>> http://theinvisiblethings.blogspot.in/2013/06/qubes-os-r3-alpha-previe= w-odyssey-hal.html >>>> = >>>> - Qubes uses upstream Xen vchan now, which means that we "should" inte= roperate with the ocaml-vchan library. >>>> = >>>> - They've replaced Xenstore with a simpler transport that removes perm= issions and uses vchan under the hood. This is also something that should = be easier to do with Dave's oxenstore+irmin, since many of the components s= uch as xenstore_transport are functorized, and of Irmin can serialize to se= veral formats including Git, for reconciliation with external databases. >>>> = >>>> - Qubes looks like an excellent candidate for a 'unikernel' desktop OS= ! I'm going to try it when I hunt down a PC laptop, but if anyone else get= s a chance I'd be interested in hearing about it. >>> = >>> I haven't tried the new alpha, but I tried the previous version of >>> Qubes on my new laptop when it first arrived (actually, being able to >>> try Qubes was one of the reasons I wanted a laptop with Intel >>> graphics). >> = >> Woops, this was indeed a year-old blog post as Dave points out. It's >> still being very actively developed though: >> = >> http://www.qubes-os.org/trac/timeline >> = >>> = >>> One interesting thing for Mirage: they have a separate domain (NetVM) >>> for network drivers, and another for the firewall (FirewallVM): >>> = >>> http://wiki.qubes-os.org/trac/wiki/QubesFirewall >>> = >>> FirewallVM is a complete Linux system and requires several hundred MB, >>> as shown in this screenshot: >>> = >>> http://wiki.qubes-os.org/trac/attachment/wiki/QubesScreenshots/r2b2-sof= tware-update.png >> = >> That is an interesting application indeed! The other thing that would >> be useful is a key management VM (which could expose an ssh-agent-like >> socket proxy via vchan into another domain, to protect against kernel >> exploits revealing). >> = >>> = >>> In the end, I only tried it for a few hours before wiping it and >>> installing Arch instead. Some other problems were that there is no >>> tiling window manager available, and you can't run VirtualBox on Xen. >>> Qubes doesn't offer graphics acceleration for guests (due to the focus >>> on security), which would probably mess up gotomeeting. >> = >> Out of curiosity, are you running Xen on your laptop at the moment >> (and if so, which distribution do you use?). I haven't set it up for >> a while, but everyone I talk to seems to have issues with power >> management, although pv_ops does allegedly support passing this through >> from dom0->Xen without issue. > = > On the laptop I don't run Xen directly. For testing, I run it under > Virtual Box (Mirage works fine that way, but I can't run HVM guests). > = > I still have power issues though! If I suspend the host, then the Xen > VM dies for some reason and needs to be rebooted. > = > I am tempted to run Xen directly on the laptop, but I suspect it > wouldn't be as slick for graphical guests (pointer and clipboard > integration, graphics acceleration, etc). I tried running Windows > under KVM with virt-manager and it wasn't very usable. I imagine Xen > would be the same. For Linux guests I=92ve heard good things about SPICE with KVM, including s= upport for resolution changing and multiple monitors. The SPICE code is mai= nly in Linux and in qemu, so Xen systems should be able to use it too (alth= ough I hear this might need some fixes only present in Xen 4.5) For Windows guests I use RDP quite a lot, although I bet it=92s not smoothl= y integrated into virt-manager. I=92ve not tried it, but you could try windows SPICE drivers: http://www.spice-space.org/download.html Cheers, Dave _______________________________________________ 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 Jun 22 11:00:51 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 22 Jun 2014 11:00: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 1WyfVx-0003we-Lh; Sun, 22 Jun 2014 11:00:49 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WyfVw-0003wZ-0z for mirageos-devel@lists.xenproject.org; Sun, 22 Jun 2014 11:00:48 +0000 Received: from [193.109.254.147:19089] by server-13.bemta-14.messagelabs.com id A2/A9-23211-E57B6A35; Sun, 22 Jun 2014 11:00:46 +0000 X-Env-Sender: Dave.Scott@citrix.com X-Msg-Ref: server-9.tower-27.messagelabs.com!1403434845!12845225!1 X-Originating-IP: [185.25.65.24] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_8, spamassassin: , surbl: (ASYNC_NO) c3VyYmxfcmVjaGVja19kZWxheTogMCAoYWJhbmRv bmVkOiB0aGVpbnZpc2libGV0aGluZ3MuYmxv\nZ3Nwb3QuaW4p\n X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20800 invoked from network); 22 Jun 2014 11:00:45 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (185.25.65.24) by server-9.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 22 Jun 2014 11:00:45 -0000 X-IronPort-AV: E=Sophos;i="5.01,523,1400025600"; d="scan'208";a="21850874" Received: from unknown (HELO AMSPEX01CL02.citrite.net) ([10.69.60.9]) by AMSPIP01.EU.Citrix.com with ESMTP; 22 Jun 2014 11:00:44 +0000 Received: from AMSPEX01CL03.citrite.net ([169.254.8.89]) by AMSPEX01CL02.citrite.net ([10.69.46.33]) with mapi id 14.03.0181.006; Sun, 22 Jun 2014 13:00:44 +0200 From: Dave Scott To: Thomas Leonard Thread-Topic: [MirageOS-devel] vchan/xenstore in Qubes r3 Thread-Index: AQHPjSaxc0muaRmEm0y9tL34lhIS7Zt7IzQAgABiMwCAAUyggIAABIuA Date: Sun, 22 Jun 2014 11:00:42 +0000 Message-ID: References: <6A38AB63-7876-4CDA-BDE3-87987E926F35@recoil.org> <69BCED97-B3DF-41E3-9A26-398FA49322B8@recoil.org> In-Reply-To: Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.13.112.14] Content-ID: <310779E6E3F7294F85CCEF69CE67F619@citrix.com> MIME-Version: 1.0 X-DLP: AMS1 Cc: "mirageos-devel@lists.xenproject.org" , Anil Madhavapeddy Subject: Re: [MirageOS-devel] vchan/xenstore in Qubes r3 X-BeenThere: mirageos-devel@lists.xenproject.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 22 Jun 2014, at 11:44, Thomas Leonard wrote: > On 21 June 2014 15:53, Anil Madhavapeddy wrote: >> On 21 Jun 2014, at 10:02, Thomas Leonard wrote: >> = >>> On 21 June 2014 08:58, Anil Madhavapeddy wrote: >>>> A very interesting article from Joanna on the new r3 alpha of QubesOS. >>>> = >>>> http://theinvisiblethings.blogspot.in/2013/06/qubes-os-r3-alpha-previe= w-odyssey-hal.html >>>> = >>>> - Qubes uses upstream Xen vchan now, which means that we "should" inte= roperate with the ocaml-vchan library. >>>> = >>>> - They've replaced Xenstore with a simpler transport that removes perm= issions and uses vchan under the hood. This is also something that should = be easier to do with Dave's oxenstore+irmin, since many of the components s= uch as xenstore_transport are functorized, and of Irmin can serialize to se= veral formats including Git, for reconciliation with external databases. >>>> = >>>> - Qubes looks like an excellent candidate for a 'unikernel' desktop OS= ! I'm going to try it when I hunt down a PC laptop, but if anyone else get= s a chance I'd be interested in hearing about it. >>> = >>> I haven't tried the new alpha, but I tried the previous version of >>> Qubes on my new laptop when it first arrived (actually, being able to >>> try Qubes was one of the reasons I wanted a laptop with Intel >>> graphics). >> = >> Woops, this was indeed a year-old blog post as Dave points out. It's >> still being very actively developed though: >> = >> http://www.qubes-os.org/trac/timeline >> = >>> = >>> One interesting thing for Mirage: they have a separate domain (NetVM) >>> for network drivers, and another for the firewall (FirewallVM): >>> = >>> http://wiki.qubes-os.org/trac/wiki/QubesFirewall >>> = >>> FirewallVM is a complete Linux system and requires several hundred MB, >>> as shown in this screenshot: >>> = >>> http://wiki.qubes-os.org/trac/attachment/wiki/QubesScreenshots/r2b2-sof= tware-update.png >> = >> That is an interesting application indeed! The other thing that would >> be useful is a key management VM (which could expose an ssh-agent-like >> socket proxy via vchan into another domain, to protect against kernel >> exploits revealing). >> = >>> = >>> In the end, I only tried it for a few hours before wiping it and >>> installing Arch instead. Some other problems were that there is no >>> tiling window manager available, and you can't run VirtualBox on Xen. >>> Qubes doesn't offer graphics acceleration for guests (due to the focus >>> on security), which would probably mess up gotomeeting. >> = >> Out of curiosity, are you running Xen on your laptop at the moment >> (and if so, which distribution do you use?). I haven't set it up for >> a while, but everyone I talk to seems to have issues with power >> management, although pv_ops does allegedly support passing this through >> from dom0->Xen without issue. > = > On the laptop I don't run Xen directly. For testing, I run it under > Virtual Box (Mirage works fine that way, but I can't run HVM guests). > = > I still have power issues though! If I suspend the host, then the Xen > VM dies for some reason and needs to be rebooted. > = > I am tempted to run Xen directly on the laptop, but I suspect it > wouldn't be as slick for graphical guests (pointer and clipboard > integration, graphics acceleration, etc). I tried running Windows > under KVM with virt-manager and it wasn't very usable. I imagine Xen > would be the same. For Linux guests I=92ve heard good things about SPICE with KVM, including s= upport for resolution changing and multiple monitors. The SPICE code is mai= nly in Linux and in qemu, so Xen systems should be able to use it too (alth= ough I hear this might need some fixes only present in Xen 4.5) For Windows guests I use RDP quite a lot, although I bet it=92s not smoothl= y integrated into virt-manager. I=92ve not tried it, but you could try windows SPICE drivers: http://www.spice-space.org/download.html Cheers, Dave _______________________________________________ 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 Jun 22 12:21:40 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 22 Jun 2014 12:21: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 1Wygm7-0004UD-Ne; Sun, 22 Jun 2014 12:21:35 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Wygm6-0004U8-5Q for mirageos-devel@lists.xenproject.org; Sun, 22 Jun 2014 12:21:34 +0000 Received: from [193.109.254.147:54442] by server-10.bemta-14.messagelabs.com id 0A/93-04546-D4AC6A35; Sun, 22 Jun 2014 12:21:33 +0000 X-Env-Sender: talex5@gmail.com X-Msg-Ref: server-5.tower-27.messagelabs.com!1403439690!8228690!1 X-Originating-IP: [209.85.214.169] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, ML_RADAR_SPEW_LINKS_23, ML_RADAR_SPEW_LINKS_8, RCVD_BY_IP, spamassassin: , surbl: (ASYNC_NO) c3VyYmxfcmVjaGVja19kZWxheTogMCAoYWJhbmRvbmVkOiB0aGVpbnZ pc2libGV0aGluZ3MuYmxv\nZ3Nwb3QuaW4p\n X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2602 invoked from network); 22 Jun 2014 12:21:31 -0000 Received: from mail-ob0-f169.google.com (HELO mail-ob0-f169.google.com) (209.85.214.169) by server-5.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 22 Jun 2014 12:21:31 -0000 Received: by mail-ob0-f169.google.com with SMTP id wp18so2947033obc.14 for ; Sun, 22 Jun 2014 05:21:30 -0700 (PDT) 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=KPzddGkBrNj4LqAFBa781gVrXYlSGXmgpVahWMmzsFQ=; b=LWsDudve5jLJ7CvAFfkEt3DhWDYuB6KA3I57FM9pWliD2FALlEUI6L5VEH1pRTWYQo 0zqnw0gtp/a24bPly3mRbIOCQoQBY+koOo45uztCv+sBqdSpYWg2n52g7t8S3e9Z9zBv KE539JaovsgEi89pACPN/b6zGBnXYUfKZP0my8YYoBb5HzMnjBjeCzzDN9lcQ6t/Xy9F /j9itJ/zNS7dhT4rnoNHT47ZNaVKQKPERrbRwx6kUy8mtwy1NckajjH8qnG2iZE33F/j 2FSCmS0PkLvXdl6ZRVA4S7x9f4OGvCvg0zPbZCth2l9BBpIW4X82vPZhYrR7RPCA08JU Ti8Q== MIME-Version: 1.0 X-Received: by 10.182.200.169 with SMTP id jt9mr15710991obc.0.1403439690103; Sun, 22 Jun 2014 05:21:30 -0700 (PDT) Received: by 10.76.92.5 with HTTP; Sun, 22 Jun 2014 05:21:30 -0700 (PDT) In-Reply-To: References: <6A38AB63-7876-4CDA-BDE3-87987E926F35@recoil.org> <69BCED97-B3DF-41E3-9A26-398FA49322B8@recoil.org> Date: Sun, 22 Jun 2014 13:21:30 +0100 Message-ID: From: Thomas Leonard To: Dave Scott Cc: "mirageos-devel@lists.xenproject.org" , Anil Madhavapeddy Subject: Re: [MirageOS-devel] vchan/xenstore in Qubes r3 X-BeenThere: mirageos-devel@lists.xenproject.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 T24gMjIgSnVuZSAyMDE0IDEyOjAwLCBEYXZlIFNjb3R0IDxEYXZlLlNjb3R0QGNpdHJpeC5jb20+ IHdyb3RlOgo+Cj4gT24gMjIgSnVuIDIwMTQsIGF0IDExOjQ0LCBUaG9tYXMgTGVvbmFyZCA8dGFs ZXg1QGdtYWlsLmNvbT4gd3JvdGU6Cj4KPj4gT24gMjEgSnVuZSAyMDE0IDE1OjUzLCBBbmlsIE1h ZGhhdmFwZWRkeSA8YW5pbEByZWNvaWwub3JnPiB3cm90ZToKPj4+IE9uIDIxIEp1biAyMDE0LCBh dCAxMDowMiwgVGhvbWFzIExlb25hcmQgPHRhbGV4NUBnbWFpbC5jb20+IHdyb3RlOgo+Pj4KPj4+ PiBPbiAyMSBKdW5lIDIwMTQgMDg6NTgsIEFuaWwgTWFkaGF2YXBlZGR5IDxhbmlsQHJlY29pbC5v cmc+IHdyb3RlOgo+Pj4+PiBBIHZlcnkgaW50ZXJlc3RpbmcgYXJ0aWNsZSBmcm9tIEpvYW5uYSBv biB0aGUgbmV3IHIzIGFscGhhIG9mIFF1YmVzT1MuCj4+Pj4+Cj4+Pj4+IGh0dHA6Ly90aGVpbnZp c2libGV0aGluZ3MuYmxvZ3Nwb3QuaW4vMjAxMy8wNi9xdWJlcy1vcy1yMy1hbHBoYS1wcmV2aWV3 LW9keXNzZXktaGFsLmh0bWwKPj4+Pj4KPj4+Pj4gLSBRdWJlcyB1c2VzIHVwc3RyZWFtIFhlbiB2 Y2hhbiBub3csIHdoaWNoIG1lYW5zIHRoYXQgd2UgInNob3VsZCIgaW50ZXJvcGVyYXRlIHdpdGgg dGhlIG9jYW1sLXZjaGFuIGxpYnJhcnkuCj4+Pj4+Cj4+Pj4+IC0gVGhleSd2ZSByZXBsYWNlZCBY ZW5zdG9yZSB3aXRoIGEgc2ltcGxlciB0cmFuc3BvcnQgdGhhdCByZW1vdmVzIHBlcm1pc3Npb25z IGFuZCB1c2VzIHZjaGFuIHVuZGVyIHRoZSBob29kLiAgVGhpcyBpcyBhbHNvIHNvbWV0aGluZyB0 aGF0IHNob3VsZCBiZSBlYXNpZXIgdG8gZG8gd2l0aCBEYXZlJ3Mgb3hlbnN0b3JlK2lybWluLCBz aW5jZSBtYW55IG9mIHRoZSBjb21wb25lbnRzIHN1Y2ggYXMgeGVuc3RvcmVfdHJhbnNwb3J0IGFy ZSBmdW5jdG9yaXplZCwgYW5kIG9mIElybWluIGNhbiBzZXJpYWxpemUgdG8gc2V2ZXJhbCBmb3Jt YXRzIGluY2x1ZGluZyBHaXQsIGZvciByZWNvbmNpbGlhdGlvbiB3aXRoIGV4dGVybmFsIGRhdGFi YXNlcy4KPj4+Pj4KPj4+Pj4gLSBRdWJlcyBsb29rcyBsaWtlIGFuIGV4Y2VsbGVudCBjYW5kaWRh dGUgZm9yIGEgJ3VuaWtlcm5lbCcgZGVza3RvcCBPUyEgIEknbSBnb2luZyB0byB0cnkgaXQgd2hl biBJIGh1bnQgZG93biBhIFBDIGxhcHRvcCwgYnV0IGlmIGFueW9uZSBlbHNlIGdldHMgYSBjaGFu Y2UgSSdkIGJlIGludGVyZXN0ZWQgaW4gaGVhcmluZyBhYm91dCBpdC4KPj4+Pgo+Pj4+IEkgaGF2 ZW4ndCB0cmllZCB0aGUgbmV3IGFscGhhLCBidXQgSSB0cmllZCB0aGUgcHJldmlvdXMgdmVyc2lv biBvZgo+Pj4+IFF1YmVzIG9uIG15IG5ldyBsYXB0b3Agd2hlbiBpdCBmaXJzdCBhcnJpdmVkIChh Y3R1YWxseSwgYmVpbmcgYWJsZSB0bwo+Pj4+IHRyeSBRdWJlcyB3YXMgb25lIG9mIHRoZSByZWFz b25zIEkgd2FudGVkIGEgbGFwdG9wIHdpdGggSW50ZWwKPj4+PiBncmFwaGljcykuCj4+Pgo+Pj4g V29vcHMsIHRoaXMgd2FzIGluZGVlZCBhIHllYXItb2xkIGJsb2cgcG9zdCBhcyBEYXZlIHBvaW50 cyBvdXQuICBJdCdzCj4+PiBzdGlsbCBiZWluZyB2ZXJ5IGFjdGl2ZWx5IGRldmVsb3BlZCB0aG91 Z2g6Cj4+Pgo+Pj4gaHR0cDovL3d3dy5xdWJlcy1vcy5vcmcvdHJhYy90aW1lbGluZQo+Pj4KPj4+ Pgo+Pj4+IE9uZSBpbnRlcmVzdGluZyB0aGluZyBmb3IgTWlyYWdlOiB0aGV5IGhhdmUgYSBzZXBh cmF0ZSBkb21haW4gKE5ldFZNKQo+Pj4+IGZvciBuZXR3b3JrIGRyaXZlcnMsIGFuZCBhbm90aGVy IGZvciB0aGUgZmlyZXdhbGwgKEZpcmV3YWxsVk0pOgo+Pj4+Cj4+Pj4gaHR0cDovL3dpa2kucXVi ZXMtb3Mub3JnL3RyYWMvd2lraS9RdWJlc0ZpcmV3YWxsCj4+Pj4KPj4+PiBGaXJld2FsbFZNIGlz IGEgY29tcGxldGUgTGludXggc3lzdGVtIGFuZCByZXF1aXJlcyBzZXZlcmFsIGh1bmRyZWQgTUIs Cj4+Pj4gYXMgc2hvd24gaW4gdGhpcyBzY3JlZW5zaG90Ogo+Pj4+Cj4+Pj4gaHR0cDovL3dpa2ku cXViZXMtb3Mub3JnL3RyYWMvYXR0YWNobWVudC93aWtpL1F1YmVzU2NyZWVuc2hvdHMvcjJiMi1z b2Z0d2FyZS11cGRhdGUucG5nCj4+Pgo+Pj4gVGhhdCBpcyBhbiBpbnRlcmVzdGluZyBhcHBsaWNh dGlvbiBpbmRlZWQhICBUaGUgb3RoZXIgdGhpbmcgdGhhdCB3b3VsZAo+Pj4gYmUgdXNlZnVsIGlz IGEga2V5IG1hbmFnZW1lbnQgVk0gKHdoaWNoIGNvdWxkIGV4cG9zZSBhbiBzc2gtYWdlbnQtbGlr ZQo+Pj4gc29ja2V0IHByb3h5IHZpYSB2Y2hhbiBpbnRvIGFub3RoZXIgZG9tYWluLCB0byBwcm90 ZWN0IGFnYWluc3Qga2VybmVsCj4+PiBleHBsb2l0cyByZXZlYWxpbmcpLgo+Pj4KPj4+Pgo+Pj4+ IEluIHRoZSBlbmQsIEkgb25seSB0cmllZCBpdCBmb3IgYSBmZXcgaG91cnMgYmVmb3JlIHdpcGlu ZyBpdCBhbmQKPj4+PiBpbnN0YWxsaW5nIEFyY2ggaW5zdGVhZC4gU29tZSBvdGhlciBwcm9ibGVt cyB3ZXJlIHRoYXQgdGhlcmUgaXMgbm8KPj4+PiB0aWxpbmcgd2luZG93IG1hbmFnZXIgYXZhaWxh YmxlLCBhbmQgeW91IGNhbid0IHJ1biBWaXJ0dWFsQm94IG9uIFhlbi4KPj4+PiBRdWJlcyBkb2Vz bid0IG9mZmVyIGdyYXBoaWNzIGFjY2VsZXJhdGlvbiBmb3IgZ3Vlc3RzIChkdWUgdG8gdGhlIGZv Y3VzCj4+Pj4gb24gc2VjdXJpdHkpLCB3aGljaCB3b3VsZCBwcm9iYWJseSBtZXNzIHVwIGdvdG9t ZWV0aW5nLgo+Pj4KPj4+IE91dCBvZiBjdXJpb3NpdHksIGFyZSB5b3UgcnVubmluZyBYZW4gb24g eW91ciBsYXB0b3AgYXQgdGhlIG1vbWVudAo+Pj4gKGFuZCBpZiBzbywgd2hpY2ggZGlzdHJpYnV0 aW9uIGRvIHlvdSB1c2U/KS4gIEkgaGF2ZW4ndCBzZXQgaXQgdXAgZm9yCj4+PiBhIHdoaWxlLCBi dXQgZXZlcnlvbmUgSSB0YWxrIHRvIHNlZW1zIHRvIGhhdmUgaXNzdWVzIHdpdGggcG93ZXIKPj4+ IG1hbmFnZW1lbnQsIGFsdGhvdWdoIHB2X29wcyBkb2VzIGFsbGVnZWRseSBzdXBwb3J0IHBhc3Np bmcgdGhpcyB0aHJvdWdoCj4+PiBmcm9tIGRvbTAtPlhlbiB3aXRob3V0IGlzc3VlLgo+Pgo+PiBP biB0aGUgbGFwdG9wIEkgZG9uJ3QgcnVuIFhlbiBkaXJlY3RseS4gRm9yIHRlc3RpbmcsIEkgcnVu IGl0IHVuZGVyCj4+IFZpcnR1YWwgQm94IChNaXJhZ2Ugd29ya3MgZmluZSB0aGF0IHdheSwgYnV0 IEkgY2FuJ3QgcnVuIEhWTSBndWVzdHMpLgo+Pgo+PiBJIHN0aWxsIGhhdmUgcG93ZXIgaXNzdWVz IHRob3VnaCEgSWYgSSBzdXNwZW5kIHRoZSBob3N0LCB0aGVuIHRoZSBYZW4KPj4gVk0gZGllcyBm b3Igc29tZSByZWFzb24gYW5kIG5lZWRzIHRvIGJlIHJlYm9vdGVkLgo+Pgo+PiBJIGFtIHRlbXB0 ZWQgdG8gcnVuIFhlbiBkaXJlY3RseSBvbiB0aGUgbGFwdG9wLCBidXQgSSBzdXNwZWN0IGl0Cj4+ IHdvdWxkbid0IGJlIGFzIHNsaWNrIGZvciBncmFwaGljYWwgZ3Vlc3RzIChwb2ludGVyIGFuZCBj bGlwYm9hcmQKPj4gaW50ZWdyYXRpb24sIGdyYXBoaWNzIGFjY2VsZXJhdGlvbiwgZXRjKS4gSSB0 cmllZCBydW5uaW5nIFdpbmRvd3MKPj4gdW5kZXIgS1ZNIHdpdGggdmlydC1tYW5hZ2VyIGFuZCBp dCB3YXNuJ3QgdmVyeSB1c2FibGUuIEkgaW1hZ2luZSBYZW4KPj4gd291bGQgYmUgdGhlIHNhbWUu Cj4KPiBGb3IgTGludXggZ3Vlc3RzIEnigJl2ZSBoZWFyZCBnb29kIHRoaW5ncyBhYm91dCBTUElD RSB3aXRoIEtWTSwgaW5jbHVkaW5nIHN1cHBvcnQgZm9yIHJlc29sdXRpb24gY2hhbmdpbmcgYW5k IG11bHRpcGxlIG1vbml0b3JzLiBUaGUgU1BJQ0UgY29kZSBpcyBtYWlubHkgaW4gTGludXggYW5k IGluIHFlbXUsIHNvIFhlbiBzeXN0ZW1zIHNob3VsZCBiZSBhYmxlIHRvIHVzZSBpdCB0b28gKGFs dGhvdWdoIEkgaGVhciB0aGlzIG1pZ2h0IG5lZWQgc29tZSBmaXhlcyBvbmx5IHByZXNlbnQgaW4g WGVuIDQuNSkKPgo+IEZvciBXaW5kb3dzIGd1ZXN0cyBJIHVzZSBSRFAgcXVpdGUgYSBsb3QsIGFs dGhvdWdoIEkgYmV0IGl04oCZcyBub3Qgc21vb3RobHkgaW50ZWdyYXRlZCBpbnRvIHZpcnQtbWFu YWdlci4KPgo+IEnigJl2ZSBub3QgdHJpZWQgaXQsIGJ1dCB5b3UgY291bGQgdHJ5IHdpbmRvd3Mg U1BJQ0UgZHJpdmVyczoKPgo+IGh0dHA6Ly93d3cuc3BpY2Utc3BhY2Uub3JnL2Rvd25sb2FkLmh0 bWwKCkkgdGhpbmsgSSB3YXMgdXNpbmcgU1BJQ0Ugd2l0aCBLVk0sIGJ1dCBpdCBkaWRuJ3Qgc2Vl bSBhcyBzbW9vdGggYXMKd2l0aCBWaXJ0dWFsIEJveC4KCkkganVzdCB0cmllZCBpbnN0YWxsaW5n IFhlbiBmcm9tIEFyY2gsIGJ1dCB0aGVuIG15IGxhcHRvcCB3b3VsZG4ndApib290LiBJIGNvdWxk bid0IHVzZSB0aGUgbGFwdG9wIGtleWJvYXJkLCBhbmQgdGhlIGV4dGVybmFsIGtleWJvYXJkCmRp ZG4ndCB3b3JrIHdoZW4gY29ubmVjdGVkIHRocm91Z2ggYW4gZXh0ZXJuYWwgaHViLiBBZnRlciBj b25uZWN0aW5nCml0IGRpcmVjdGx5IEkgY291bGQgdHlwZSwgYnV0IFggd291bGRuJ3Qgc3RhcnQu IEkgc3VzcGVjdCB0aGlzIGlzIHRoZQpmYXVsdCBvZiB0aGUgQXJjaCBYZW4gcGFja2FnZSwgYXMg UXViZXMgZGlkIHdvcmsgb24gdGhlIHNhbWUgbWFjaGluZSwKYnV0IEkgdGhpbmsgSSdsbCBzdGlj ayB0byBWQiBmb3Igbm93Li4uCgoKLS0gCkRyIFRob21hcyBMZW9uYXJkICAgICAgICBodHRwOi8v MGluc3RhbGwubmV0LwpHUEc6IDkyNDIgOTgwNyBDOTg1IDNDMDcgNDRBNiAgOEI5QSBBRTA3IDgy ODAgNTlBNSAzQ0MxCkdQRzogREE5OCAyNUFFIENBRDAgODk3NSA3Q0RBICBCRDhFIDA3MTMgM0Y5 NiBDQTc0IEQ4QkEKCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fCk1pcmFnZU9TLWRldmVsIG1haWxpbmcgbGlzdApNaXJhZ2VPUy1kZXZlbEBsaXN0cy54ZW5w cm9qZWN0Lm9yZwpodHRwOi8vbGlzdHMueGVucHJvamVjdC5vcmcvY2dpLWJpbi9tYWlsbWFuL2xp c3RpbmZvL21pcmFnZW9zLWRldmVsCg== From mirageos-devel-bounces@lists.xenproject.org Sun Jun 22 12:21:40 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 22 Jun 2014 12:21: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 1Wygm7-0004UD-Ne; Sun, 22 Jun 2014 12:21:35 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Wygm6-0004U8-5Q for mirageos-devel@lists.xenproject.org; Sun, 22 Jun 2014 12:21:34 +0000 Received: from [193.109.254.147:54442] by server-10.bemta-14.messagelabs.com id 0A/93-04546-D4AC6A35; Sun, 22 Jun 2014 12:21:33 +0000 X-Env-Sender: talex5@gmail.com X-Msg-Ref: server-5.tower-27.messagelabs.com!1403439690!8228690!1 X-Originating-IP: [209.85.214.169] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, ML_RADAR_SPEW_LINKS_23, ML_RADAR_SPEW_LINKS_8, RCVD_BY_IP, spamassassin: , surbl: (ASYNC_NO) c3VyYmxfcmVjaGVja19kZWxheTogMCAoYWJhbmRvbmVkOiB0aGVpbnZ pc2libGV0aGluZ3MuYmxv\nZ3Nwb3QuaW4p\n X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2602 invoked from network); 22 Jun 2014 12:21:31 -0000 Received: from mail-ob0-f169.google.com (HELO mail-ob0-f169.google.com) (209.85.214.169) by server-5.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 22 Jun 2014 12:21:31 -0000 Received: by mail-ob0-f169.google.com with SMTP id wp18so2947033obc.14 for ; Sun, 22 Jun 2014 05:21:30 -0700 (PDT) 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=KPzddGkBrNj4LqAFBa781gVrXYlSGXmgpVahWMmzsFQ=; b=LWsDudve5jLJ7CvAFfkEt3DhWDYuB6KA3I57FM9pWliD2FALlEUI6L5VEH1pRTWYQo 0zqnw0gtp/a24bPly3mRbIOCQoQBY+koOo45uztCv+sBqdSpYWg2n52g7t8S3e9Z9zBv KE539JaovsgEi89pACPN/b6zGBnXYUfKZP0my8YYoBb5HzMnjBjeCzzDN9lcQ6t/Xy9F /j9itJ/zNS7dhT4rnoNHT47ZNaVKQKPERrbRwx6kUy8mtwy1NckajjH8qnG2iZE33F/j 2FSCmS0PkLvXdl6ZRVA4S7x9f4OGvCvg0zPbZCth2l9BBpIW4X82vPZhYrR7RPCA08JU Ti8Q== MIME-Version: 1.0 X-Received: by 10.182.200.169 with SMTP id jt9mr15710991obc.0.1403439690103; Sun, 22 Jun 2014 05:21:30 -0700 (PDT) Received: by 10.76.92.5 with HTTP; Sun, 22 Jun 2014 05:21:30 -0700 (PDT) In-Reply-To: References: <6A38AB63-7876-4CDA-BDE3-87987E926F35@recoil.org> <69BCED97-B3DF-41E3-9A26-398FA49322B8@recoil.org> Date: Sun, 22 Jun 2014 13:21:30 +0100 Message-ID: From: Thomas Leonard To: Dave Scott Cc: "mirageos-devel@lists.xenproject.org" , Anil Madhavapeddy Subject: Re: [MirageOS-devel] vchan/xenstore in Qubes r3 X-BeenThere: mirageos-devel@lists.xenproject.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 T24gMjIgSnVuZSAyMDE0IDEyOjAwLCBEYXZlIFNjb3R0IDxEYXZlLlNjb3R0QGNpdHJpeC5jb20+ IHdyb3RlOgo+Cj4gT24gMjIgSnVuIDIwMTQsIGF0IDExOjQ0LCBUaG9tYXMgTGVvbmFyZCA8dGFs ZXg1QGdtYWlsLmNvbT4gd3JvdGU6Cj4KPj4gT24gMjEgSnVuZSAyMDE0IDE1OjUzLCBBbmlsIE1h ZGhhdmFwZWRkeSA8YW5pbEByZWNvaWwub3JnPiB3cm90ZToKPj4+IE9uIDIxIEp1biAyMDE0LCBh dCAxMDowMiwgVGhvbWFzIExlb25hcmQgPHRhbGV4NUBnbWFpbC5jb20+IHdyb3RlOgo+Pj4KPj4+ PiBPbiAyMSBKdW5lIDIwMTQgMDg6NTgsIEFuaWwgTWFkaGF2YXBlZGR5IDxhbmlsQHJlY29pbC5v cmc+IHdyb3RlOgo+Pj4+PiBBIHZlcnkgaW50ZXJlc3RpbmcgYXJ0aWNsZSBmcm9tIEpvYW5uYSBv biB0aGUgbmV3IHIzIGFscGhhIG9mIFF1YmVzT1MuCj4+Pj4+Cj4+Pj4+IGh0dHA6Ly90aGVpbnZp c2libGV0aGluZ3MuYmxvZ3Nwb3QuaW4vMjAxMy8wNi9xdWJlcy1vcy1yMy1hbHBoYS1wcmV2aWV3 LW9keXNzZXktaGFsLmh0bWwKPj4+Pj4KPj4+Pj4gLSBRdWJlcyB1c2VzIHVwc3RyZWFtIFhlbiB2 Y2hhbiBub3csIHdoaWNoIG1lYW5zIHRoYXQgd2UgInNob3VsZCIgaW50ZXJvcGVyYXRlIHdpdGgg dGhlIG9jYW1sLXZjaGFuIGxpYnJhcnkuCj4+Pj4+Cj4+Pj4+IC0gVGhleSd2ZSByZXBsYWNlZCBY ZW5zdG9yZSB3aXRoIGEgc2ltcGxlciB0cmFuc3BvcnQgdGhhdCByZW1vdmVzIHBlcm1pc3Npb25z IGFuZCB1c2VzIHZjaGFuIHVuZGVyIHRoZSBob29kLiAgVGhpcyBpcyBhbHNvIHNvbWV0aGluZyB0 aGF0IHNob3VsZCBiZSBlYXNpZXIgdG8gZG8gd2l0aCBEYXZlJ3Mgb3hlbnN0b3JlK2lybWluLCBz aW5jZSBtYW55IG9mIHRoZSBjb21wb25lbnRzIHN1Y2ggYXMgeGVuc3RvcmVfdHJhbnNwb3J0IGFy ZSBmdW5jdG9yaXplZCwgYW5kIG9mIElybWluIGNhbiBzZXJpYWxpemUgdG8gc2V2ZXJhbCBmb3Jt YXRzIGluY2x1ZGluZyBHaXQsIGZvciByZWNvbmNpbGlhdGlvbiB3aXRoIGV4dGVybmFsIGRhdGFi YXNlcy4KPj4+Pj4KPj4+Pj4gLSBRdWJlcyBsb29rcyBsaWtlIGFuIGV4Y2VsbGVudCBjYW5kaWRh dGUgZm9yIGEgJ3VuaWtlcm5lbCcgZGVza3RvcCBPUyEgIEknbSBnb2luZyB0byB0cnkgaXQgd2hl biBJIGh1bnQgZG93biBhIFBDIGxhcHRvcCwgYnV0IGlmIGFueW9uZSBlbHNlIGdldHMgYSBjaGFu Y2UgSSdkIGJlIGludGVyZXN0ZWQgaW4gaGVhcmluZyBhYm91dCBpdC4KPj4+Pgo+Pj4+IEkgaGF2 ZW4ndCB0cmllZCB0aGUgbmV3IGFscGhhLCBidXQgSSB0cmllZCB0aGUgcHJldmlvdXMgdmVyc2lv biBvZgo+Pj4+IFF1YmVzIG9uIG15IG5ldyBsYXB0b3Agd2hlbiBpdCBmaXJzdCBhcnJpdmVkIChh Y3R1YWxseSwgYmVpbmcgYWJsZSB0bwo+Pj4+IHRyeSBRdWJlcyB3YXMgb25lIG9mIHRoZSByZWFz b25zIEkgd2FudGVkIGEgbGFwdG9wIHdpdGggSW50ZWwKPj4+PiBncmFwaGljcykuCj4+Pgo+Pj4g V29vcHMsIHRoaXMgd2FzIGluZGVlZCBhIHllYXItb2xkIGJsb2cgcG9zdCBhcyBEYXZlIHBvaW50 cyBvdXQuICBJdCdzCj4+PiBzdGlsbCBiZWluZyB2ZXJ5IGFjdGl2ZWx5IGRldmVsb3BlZCB0aG91 Z2g6Cj4+Pgo+Pj4gaHR0cDovL3d3dy5xdWJlcy1vcy5vcmcvdHJhYy90aW1lbGluZQo+Pj4KPj4+ Pgo+Pj4+IE9uZSBpbnRlcmVzdGluZyB0aGluZyBmb3IgTWlyYWdlOiB0aGV5IGhhdmUgYSBzZXBh cmF0ZSBkb21haW4gKE5ldFZNKQo+Pj4+IGZvciBuZXR3b3JrIGRyaXZlcnMsIGFuZCBhbm90aGVy IGZvciB0aGUgZmlyZXdhbGwgKEZpcmV3YWxsVk0pOgo+Pj4+Cj4+Pj4gaHR0cDovL3dpa2kucXVi ZXMtb3Mub3JnL3RyYWMvd2lraS9RdWJlc0ZpcmV3YWxsCj4+Pj4KPj4+PiBGaXJld2FsbFZNIGlz IGEgY29tcGxldGUgTGludXggc3lzdGVtIGFuZCByZXF1aXJlcyBzZXZlcmFsIGh1bmRyZWQgTUIs Cj4+Pj4gYXMgc2hvd24gaW4gdGhpcyBzY3JlZW5zaG90Ogo+Pj4+Cj4+Pj4gaHR0cDovL3dpa2ku cXViZXMtb3Mub3JnL3RyYWMvYXR0YWNobWVudC93aWtpL1F1YmVzU2NyZWVuc2hvdHMvcjJiMi1z b2Z0d2FyZS11cGRhdGUucG5nCj4+Pgo+Pj4gVGhhdCBpcyBhbiBpbnRlcmVzdGluZyBhcHBsaWNh dGlvbiBpbmRlZWQhICBUaGUgb3RoZXIgdGhpbmcgdGhhdCB3b3VsZAo+Pj4gYmUgdXNlZnVsIGlz IGEga2V5IG1hbmFnZW1lbnQgVk0gKHdoaWNoIGNvdWxkIGV4cG9zZSBhbiBzc2gtYWdlbnQtbGlr ZQo+Pj4gc29ja2V0IHByb3h5IHZpYSB2Y2hhbiBpbnRvIGFub3RoZXIgZG9tYWluLCB0byBwcm90 ZWN0IGFnYWluc3Qga2VybmVsCj4+PiBleHBsb2l0cyByZXZlYWxpbmcpLgo+Pj4KPj4+Pgo+Pj4+ IEluIHRoZSBlbmQsIEkgb25seSB0cmllZCBpdCBmb3IgYSBmZXcgaG91cnMgYmVmb3JlIHdpcGlu ZyBpdCBhbmQKPj4+PiBpbnN0YWxsaW5nIEFyY2ggaW5zdGVhZC4gU29tZSBvdGhlciBwcm9ibGVt cyB3ZXJlIHRoYXQgdGhlcmUgaXMgbm8KPj4+PiB0aWxpbmcgd2luZG93IG1hbmFnZXIgYXZhaWxh YmxlLCBhbmQgeW91IGNhbid0IHJ1biBWaXJ0dWFsQm94IG9uIFhlbi4KPj4+PiBRdWJlcyBkb2Vz bid0IG9mZmVyIGdyYXBoaWNzIGFjY2VsZXJhdGlvbiBmb3IgZ3Vlc3RzIChkdWUgdG8gdGhlIGZv Y3VzCj4+Pj4gb24gc2VjdXJpdHkpLCB3aGljaCB3b3VsZCBwcm9iYWJseSBtZXNzIHVwIGdvdG9t ZWV0aW5nLgo+Pj4KPj4+IE91dCBvZiBjdXJpb3NpdHksIGFyZSB5b3UgcnVubmluZyBYZW4gb24g eW91ciBsYXB0b3AgYXQgdGhlIG1vbWVudAo+Pj4gKGFuZCBpZiBzbywgd2hpY2ggZGlzdHJpYnV0 aW9uIGRvIHlvdSB1c2U/KS4gIEkgaGF2ZW4ndCBzZXQgaXQgdXAgZm9yCj4+PiBhIHdoaWxlLCBi dXQgZXZlcnlvbmUgSSB0YWxrIHRvIHNlZW1zIHRvIGhhdmUgaXNzdWVzIHdpdGggcG93ZXIKPj4+ IG1hbmFnZW1lbnQsIGFsdGhvdWdoIHB2X29wcyBkb2VzIGFsbGVnZWRseSBzdXBwb3J0IHBhc3Np bmcgdGhpcyB0aHJvdWdoCj4+PiBmcm9tIGRvbTAtPlhlbiB3aXRob3V0IGlzc3VlLgo+Pgo+PiBP biB0aGUgbGFwdG9wIEkgZG9uJ3QgcnVuIFhlbiBkaXJlY3RseS4gRm9yIHRlc3RpbmcsIEkgcnVu IGl0IHVuZGVyCj4+IFZpcnR1YWwgQm94IChNaXJhZ2Ugd29ya3MgZmluZSB0aGF0IHdheSwgYnV0 IEkgY2FuJ3QgcnVuIEhWTSBndWVzdHMpLgo+Pgo+PiBJIHN0aWxsIGhhdmUgcG93ZXIgaXNzdWVz IHRob3VnaCEgSWYgSSBzdXNwZW5kIHRoZSBob3N0LCB0aGVuIHRoZSBYZW4KPj4gVk0gZGllcyBm b3Igc29tZSByZWFzb24gYW5kIG5lZWRzIHRvIGJlIHJlYm9vdGVkLgo+Pgo+PiBJIGFtIHRlbXB0 ZWQgdG8gcnVuIFhlbiBkaXJlY3RseSBvbiB0aGUgbGFwdG9wLCBidXQgSSBzdXNwZWN0IGl0Cj4+ IHdvdWxkbid0IGJlIGFzIHNsaWNrIGZvciBncmFwaGljYWwgZ3Vlc3RzIChwb2ludGVyIGFuZCBj bGlwYm9hcmQKPj4gaW50ZWdyYXRpb24sIGdyYXBoaWNzIGFjY2VsZXJhdGlvbiwgZXRjKS4gSSB0 cmllZCBydW5uaW5nIFdpbmRvd3MKPj4gdW5kZXIgS1ZNIHdpdGggdmlydC1tYW5hZ2VyIGFuZCBp dCB3YXNuJ3QgdmVyeSB1c2FibGUuIEkgaW1hZ2luZSBYZW4KPj4gd291bGQgYmUgdGhlIHNhbWUu Cj4KPiBGb3IgTGludXggZ3Vlc3RzIEnigJl2ZSBoZWFyZCBnb29kIHRoaW5ncyBhYm91dCBTUElD RSB3aXRoIEtWTSwgaW5jbHVkaW5nIHN1cHBvcnQgZm9yIHJlc29sdXRpb24gY2hhbmdpbmcgYW5k IG11bHRpcGxlIG1vbml0b3JzLiBUaGUgU1BJQ0UgY29kZSBpcyBtYWlubHkgaW4gTGludXggYW5k IGluIHFlbXUsIHNvIFhlbiBzeXN0ZW1zIHNob3VsZCBiZSBhYmxlIHRvIHVzZSBpdCB0b28gKGFs dGhvdWdoIEkgaGVhciB0aGlzIG1pZ2h0IG5lZWQgc29tZSBmaXhlcyBvbmx5IHByZXNlbnQgaW4g WGVuIDQuNSkKPgo+IEZvciBXaW5kb3dzIGd1ZXN0cyBJIHVzZSBSRFAgcXVpdGUgYSBsb3QsIGFs dGhvdWdoIEkgYmV0IGl04oCZcyBub3Qgc21vb3RobHkgaW50ZWdyYXRlZCBpbnRvIHZpcnQtbWFu YWdlci4KPgo+IEnigJl2ZSBub3QgdHJpZWQgaXQsIGJ1dCB5b3UgY291bGQgdHJ5IHdpbmRvd3Mg U1BJQ0UgZHJpdmVyczoKPgo+IGh0dHA6Ly93d3cuc3BpY2Utc3BhY2Uub3JnL2Rvd25sb2FkLmh0 bWwKCkkgdGhpbmsgSSB3YXMgdXNpbmcgU1BJQ0Ugd2l0aCBLVk0sIGJ1dCBpdCBkaWRuJ3Qgc2Vl bSBhcyBzbW9vdGggYXMKd2l0aCBWaXJ0dWFsIEJveC4KCkkganVzdCB0cmllZCBpbnN0YWxsaW5n IFhlbiBmcm9tIEFyY2gsIGJ1dCB0aGVuIG15IGxhcHRvcCB3b3VsZG4ndApib290LiBJIGNvdWxk bid0IHVzZSB0aGUgbGFwdG9wIGtleWJvYXJkLCBhbmQgdGhlIGV4dGVybmFsIGtleWJvYXJkCmRp ZG4ndCB3b3JrIHdoZW4gY29ubmVjdGVkIHRocm91Z2ggYW4gZXh0ZXJuYWwgaHViLiBBZnRlciBj b25uZWN0aW5nCml0IGRpcmVjdGx5IEkgY291bGQgdHlwZSwgYnV0IFggd291bGRuJ3Qgc3RhcnQu IEkgc3VzcGVjdCB0aGlzIGlzIHRoZQpmYXVsdCBvZiB0aGUgQXJjaCBYZW4gcGFja2FnZSwgYXMg UXViZXMgZGlkIHdvcmsgb24gdGhlIHNhbWUgbWFjaGluZSwKYnV0IEkgdGhpbmsgSSdsbCBzdGlj ayB0byBWQiBmb3Igbm93Li4uCgoKLS0gCkRyIFRob21hcyBMZW9uYXJkICAgICAgICBodHRwOi8v MGluc3RhbGwubmV0LwpHUEc6IDkyNDIgOTgwNyBDOTg1IDNDMDcgNDRBNiAgOEI5QSBBRTA3IDgy ODAgNTlBNSAzQ0MxCkdQRzogREE5OCAyNUFFIENBRDAgODk3NSA3Q0RBICBCRDhFIDA3MTMgM0Y5 NiBDQTc0IEQ4QkEKCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fCk1pcmFnZU9TLWRldmVsIG1haWxpbmcgbGlzdApNaXJhZ2VPUy1kZXZlbEBsaXN0cy54ZW5w cm9qZWN0Lm9yZwpodHRwOi8vbGlzdHMueGVucHJvamVjdC5vcmcvY2dpLWJpbi9tYWlsbWFuL2xp c3RpbmZvL21pcmFnZW9zLWRldmVsCg== From mirageos-devel-bounces@lists.xenproject.org Sun Jun 22 16:39:47 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 22 Jun 2014 16:39: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 1Wyknw-0006LC-KA; Sun, 22 Jun 2014 16:39:44 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Wyknw-0006L7-53 for mirageos-devel@lists.xenproject.org; Sun, 22 Jun 2014 16:39:44 +0000 Received: from [85.158.137.68:56386] by server-2.bemta-3.messagelabs.com id A1/64-13558-FC607A35; Sun, 22 Jun 2014 16:39:43 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-9.tower-31.messagelabs.com!1403455182!7878029!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 13432 invoked from network); 22 Jun 2014 16:39:42 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-9.tower-31.messagelabs.com with SMTP; 22 Jun 2014 16:39:42 -0000 Received: (qmail 30569 invoked by uid 634); 22 Jun 2014 16:39:42 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net (HELO [192.168.1.94]) (86.30.244.239) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Sun, 22 Jun 2014 17:39:41 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\)) From: Anil Madhavapeddy In-Reply-To: Date: Sun, 22 Jun 2014 17:39:39 +0100 Message-Id: <2A0B705D-8D2E-4874-A0F0-8D88342B7797@recoil.org> References: <6A38AB63-7876-4CDA-BDE3-87987E926F35@recoil.org> <69BCED97-B3DF-41E3-9A26-398FA49322B8@recoil.org> To: Thomas Leonard X-Mailer: Apple Mail (2.1874) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: David Scott , "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] vchan/xenstore in Qubes r3 X-BeenThere: mirageos-devel@lists.xenproject.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 22 Jun 2014, at 13:21, Thomas Leonard wrote: > > I just tried installing Xen from Arch, but then my laptop wouldn't > boot. I couldn't use the laptop keyboard, and the external keyboard > didn't work when connected through an external hub. After connecting > it directly I could type, but X wouldn't start. I suspect this is the > fault of the Arch Xen package, as Qubes did work on the same machine, > but I think I'll stick to VB for now... > Yowch, that's pretty broken. Which version of Xen/dom0 does Arch have packaged up? -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 Jun 22 16:39:47 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 22 Jun 2014 16:39: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 1Wyknw-0006LC-KA; Sun, 22 Jun 2014 16:39:44 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Wyknw-0006L7-53 for mirageos-devel@lists.xenproject.org; Sun, 22 Jun 2014 16:39:44 +0000 Received: from [85.158.137.68:56386] by server-2.bemta-3.messagelabs.com id A1/64-13558-FC607A35; Sun, 22 Jun 2014 16:39:43 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-9.tower-31.messagelabs.com!1403455182!7878029!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 13432 invoked from network); 22 Jun 2014 16:39:42 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-9.tower-31.messagelabs.com with SMTP; 22 Jun 2014 16:39:42 -0000 Received: (qmail 30569 invoked by uid 634); 22 Jun 2014 16:39:42 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net (HELO [192.168.1.94]) (86.30.244.239) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Sun, 22 Jun 2014 17:39:41 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\)) From: Anil Madhavapeddy In-Reply-To: Date: Sun, 22 Jun 2014 17:39:39 +0100 Message-Id: <2A0B705D-8D2E-4874-A0F0-8D88342B7797@recoil.org> References: <6A38AB63-7876-4CDA-BDE3-87987E926F35@recoil.org> <69BCED97-B3DF-41E3-9A26-398FA49322B8@recoil.org> To: Thomas Leonard X-Mailer: Apple Mail (2.1874) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: David Scott , "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] vchan/xenstore in Qubes r3 X-BeenThere: mirageos-devel@lists.xenproject.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 22 Jun 2014, at 13:21, Thomas Leonard wrote: > > I just tried installing Xen from Arch, but then my laptop wouldn't > boot. I couldn't use the laptop keyboard, and the external keyboard > didn't work when connected through an external hub. After connecting > it directly I could type, but X wouldn't start. I suspect this is the > fault of the Arch Xen package, as Qubes did work on the same machine, > but I think I'll stick to VB for now... > Yowch, that's pretty broken. Which version of Xen/dom0 does Arch have packaged up? -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 Jun 22 16:53:17 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 22 Jun 2014 16:53: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 1Wyl11-0006Na-M0; Sun, 22 Jun 2014 16:53:15 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Wyl10-0006NV-Pv for mirageos-devel@lists.xenproject.org; Sun, 22 Jun 2014 16:53:14 +0000 Received: from [85.158.143.35:14616] by server-1.bemta-4.messagelabs.com id 80/C3-09496-AF907A35; Sun, 22 Jun 2014 16:53:14 +0000 X-Env-Sender: Richard.Mortier@nottingham.ac.uk X-Msg-Ref: server-16.tower-21.messagelabs.com!1403455993!9560471!1 X-Originating-IP: [93.95.15.171] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogOTMuOTUuMTUuMTcxID0+IDQyMTM=\n X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20510 invoked from network); 22 Jun 2014 16:53:13 -0000 Received: from engine05-20433-5.icritical.com (HELO engine05-20433-5.icritical.com) (93.95.15.171) by server-16.tower-21.messagelabs.com with SMTP; 22 Jun 2014 16:53:13 -0000 Received: (qmail 32619 invoked from network); 22 Jun 2014 16:53:11 -0000 Received: from localhost (127.0.0.1) by engine05-20433-5.icritical.com with SMTP; 22 Jun 2014 16:53:11 -0000 Received: from engine05-20433-5.icritical.com ([127.0.0.1]) by localhost (engine05-20433-5.icritical.com [127.0.0.1]) (amavisd-new, port 10024) with SMTP id 31555-09 for ; Sun, 22 Jun 2014 17:53:03 +0100 (BST) Received: (qmail 32584 invoked by uid 599); 22 Jun 2014 16:53:01 -0000 Received: from unknown (HELO smtp4.nottingham.ac.uk) (128.243.220.65) by engine05-20433-5.icritical.com (qpsmtpd/0.28) with ESMTP; Sun, 22 Jun 2014 17:53:01 +0100 Received: from uiwexhub02.ad.nottingham.ac.uk ([128.243.15.132]) by smtp4.nottingham.ac.uk with esmtps (TLSv1:AES128-SHA:128) (Exim 4.77) (envelope-from ) id 1Wyl0m-0004Yr-FL; Sun, 22 Jun 2014 17:53:00 +0100 From: Richard Mortier To: Thomas Leonard Date: Sun, 22 Jun 2014 17:52:57 +0100 Thread-Topic: [MirageOS-devel] vchan/xenstore in Qubes r3 Thread-Index: Ac+OOmvqglZERTerTiCPh8IRdb3H6Q== Message-ID: <4EF23D52-605E-418A-95BC-E7C407041FF5@nottingham.ac.uk> References: <6A38AB63-7876-4CDA-BDE3-87987E926F35@recoil.org> <69BCED97-B3DF-41E3-9A26-398FA49322B8@recoil.org> In-Reply-To: Accept-Language: en-US, en-GB Content-Language: en-US X-MS-Has-Attach: yes X-MS-TNEF-Correlator: acceptlanguage: en-US, en-GB MIME-Version: 1.0 X-Virus-Scanned: by iCritical at engine05-20433-5.icritical.com Cc: Dave Scott , "mirageos-devel@lists.xenproject.org" , Anil Madhavapeddy Subject: Re: [MirageOS-devel] vchan/xenstore in Qubes r3 X-BeenThere: mirageos-devel@lists.xenproject.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="===============6563001116829724856==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============6563001116829724856== Content-Language: en-US Content-Type: multipart/signed; boundary="Apple-Mail=_D72CA674-3626-42CA-B01B-2D2F6C017601"; protocol="application/pgp-signature"; micalg=pgp-sha512 --Apple-Mail=_D72CA674-3626-42CA-B01B-2D2F6C017601 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 On 22 Jun 2014, at 13:21, Thomas Leonard wrote: > On 22 June 2014 12:00, Dave Scott wrote: >>=20 >> On 22 Jun 2014, at 11:44, Thomas Leonard wrote: >>=20 >>> I am tempted to run Xen directly on the laptop, but I suspect it >>> wouldn't be as slick for graphical guests (pointer and clipboard >>> integration, graphics acceleration, etc). I tried running Windows >>> under KVM with virt-manager and it wasn't very usable. I imagine Xen >>> would be the same. >>=20 >> For Linux guests I=92ve heard good things about SPICE with KVM, = including support for resolution changing and multiple monitors. The = SPICE code is mainly in Linux and in qemu, so Xen systems should be able = to use it too (although I hear this might need some fixes only present = in Xen 4.5) >>=20 >> For Windows guests I use RDP quite a lot, although I bet it=92s not = smoothly integrated into virt-manager. >>=20 >> I=92ve not tried it, but you could try windows SPICE drivers: >>=20 >> http://www.spice-space.org/download.html >=20 > I think I was using SPICE with KVM, but it didn't seem as smooth as > with Virtual Box. >=20 > I just tried installing Xen from Arch, but then my laptop wouldn't > boot. I couldn't use the laptop keyboard, and the external keyboard > didn't work when connected through an external hub. After connecting > it directly I could type, but X wouldn't start. I suspect this is the > fault of the Arch Xen package, as Qubes did work on the same machine, > but I think I'll stick to VB for now... as an aside, i wonder whether there's any collective documentation of = recommended laptop-based xen/mirage development setups? i use linux dom0 = on xen on virtualbox on osx myself but the several other options = discussed in this thread so far might be useful to capture... --=20 Cheers, R. --Apple-Mail=_D72CA674-3626-42CA-B01B-2D2F6C017601 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="signature.asc" Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJTpwnpAAoJEOLF27JWwSg3eu8P/3WmOmCWL4ZT2GY+zcsjilVj 766mLunqrG1NVHGJ2rVgCJNfBbi6OAI353AUkyuxRhBNcm9lPWBcb8/HvaHxILpl u8g38WWKUDBNcjmNVMdIHcrE7bQBvqNzYosN2s74eESpdZGkoh8vJ4HfT31tx67R kTegFZawph3944eYcp/7dGLCyML/VBG3zytTdcQ5mF3FKQllPcMmzWekss+WXgwm TneDPw1YJ7YBaxby5dZx9y4wQgElx3D/RV4uTBA6rnAS+zyX+Q7NNxefsAGQyvVI 8x4jnL7j32i3+VoshWxDDrmk2crE5Wpklkzj33CMBfRxd6j6A0kxoHAl7eLWtDbd 5mZ/RZb7eQoCoTluNhMZ7AxFzJ2IXH6d0x/Qb6mCK/e5TbsdFWwW8uJH4f2dx53K re+ZvJN1w1EzAnlxc5PwHcu+Sgjw3sdXMQAdGh0KJJzjwREII+eLG7EeB+cJEJ4E vNb1wmnIgsnJaqrIdK/w5Hq29kytvEFIdGFMGLZELcHTkptns25c6wTy6oXfBc/T VkIw/gASLpr8NhLSbdh1HyM8LP3KQMTxP5w8bXGHNQDFSTk3GhINqCuKhdIKnu1m V23720Hlvja3AEgQiUK0XAOXSpT3LU1VEQJUqlJ1KugsKd2cGkLp+QbmKgIPT6Ko z7d2qSM4oGrwUqDzlKnl =vZqq -----END PGP SIGNATURE----- --Apple-Mail=_D72CA674-3626-42CA-B01B-2D2F6C017601-- --===============6563001116829724856== 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 --===============6563001116829724856==-- From mirageos-devel-bounces@lists.xenproject.org Sun Jun 22 16:53:17 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 22 Jun 2014 16:53: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 1Wyl11-0006Na-M0; Sun, 22 Jun 2014 16:53:15 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Wyl10-0006NV-Pv for mirageos-devel@lists.xenproject.org; Sun, 22 Jun 2014 16:53:14 +0000 Received: from [85.158.143.35:14616] by server-1.bemta-4.messagelabs.com id 80/C3-09496-AF907A35; Sun, 22 Jun 2014 16:53:14 +0000 X-Env-Sender: Richard.Mortier@nottingham.ac.uk X-Msg-Ref: server-16.tower-21.messagelabs.com!1403455993!9560471!1 X-Originating-IP: [93.95.15.171] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogOTMuOTUuMTUuMTcxID0+IDQyMTM=\n X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20510 invoked from network); 22 Jun 2014 16:53:13 -0000 Received: from engine05-20433-5.icritical.com (HELO engine05-20433-5.icritical.com) (93.95.15.171) by server-16.tower-21.messagelabs.com with SMTP; 22 Jun 2014 16:53:13 -0000 Received: (qmail 32619 invoked from network); 22 Jun 2014 16:53:11 -0000 Received: from localhost (127.0.0.1) by engine05-20433-5.icritical.com with SMTP; 22 Jun 2014 16:53:11 -0000 Received: from engine05-20433-5.icritical.com ([127.0.0.1]) by localhost (engine05-20433-5.icritical.com [127.0.0.1]) (amavisd-new, port 10024) with SMTP id 31555-09 for ; Sun, 22 Jun 2014 17:53:03 +0100 (BST) Received: (qmail 32584 invoked by uid 599); 22 Jun 2014 16:53:01 -0000 Received: from unknown (HELO smtp4.nottingham.ac.uk) (128.243.220.65) by engine05-20433-5.icritical.com (qpsmtpd/0.28) with ESMTP; Sun, 22 Jun 2014 17:53:01 +0100 Received: from uiwexhub02.ad.nottingham.ac.uk ([128.243.15.132]) by smtp4.nottingham.ac.uk with esmtps (TLSv1:AES128-SHA:128) (Exim 4.77) (envelope-from ) id 1Wyl0m-0004Yr-FL; Sun, 22 Jun 2014 17:53:00 +0100 From: Richard Mortier To: Thomas Leonard Date: Sun, 22 Jun 2014 17:52:57 +0100 Thread-Topic: [MirageOS-devel] vchan/xenstore in Qubes r3 Thread-Index: Ac+OOmvqglZERTerTiCPh8IRdb3H6Q== Message-ID: <4EF23D52-605E-418A-95BC-E7C407041FF5@nottingham.ac.uk> References: <6A38AB63-7876-4CDA-BDE3-87987E926F35@recoil.org> <69BCED97-B3DF-41E3-9A26-398FA49322B8@recoil.org> In-Reply-To: Accept-Language: en-US, en-GB Content-Language: en-US X-MS-Has-Attach: yes X-MS-TNEF-Correlator: acceptlanguage: en-US, en-GB MIME-Version: 1.0 X-Virus-Scanned: by iCritical at engine05-20433-5.icritical.com Cc: Dave Scott , "mirageos-devel@lists.xenproject.org" , Anil Madhavapeddy Subject: Re: [MirageOS-devel] vchan/xenstore in Qubes r3 X-BeenThere: mirageos-devel@lists.xenproject.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="===============6563001116829724856==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============6563001116829724856== Content-Language: en-US Content-Type: multipart/signed; boundary="Apple-Mail=_D72CA674-3626-42CA-B01B-2D2F6C017601"; protocol="application/pgp-signature"; micalg=pgp-sha512 --Apple-Mail=_D72CA674-3626-42CA-B01B-2D2F6C017601 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 On 22 Jun 2014, at 13:21, Thomas Leonard wrote: > On 22 June 2014 12:00, Dave Scott wrote: >>=20 >> On 22 Jun 2014, at 11:44, Thomas Leonard wrote: >>=20 >>> I am tempted to run Xen directly on the laptop, but I suspect it >>> wouldn't be as slick for graphical guests (pointer and clipboard >>> integration, graphics acceleration, etc). I tried running Windows >>> under KVM with virt-manager and it wasn't very usable. I imagine Xen >>> would be the same. >>=20 >> For Linux guests I=92ve heard good things about SPICE with KVM, = including support for resolution changing and multiple monitors. The = SPICE code is mainly in Linux and in qemu, so Xen systems should be able = to use it too (although I hear this might need some fixes only present = in Xen 4.5) >>=20 >> For Windows guests I use RDP quite a lot, although I bet it=92s not = smoothly integrated into virt-manager. >>=20 >> I=92ve not tried it, but you could try windows SPICE drivers: >>=20 >> http://www.spice-space.org/download.html >=20 > I think I was using SPICE with KVM, but it didn't seem as smooth as > with Virtual Box. >=20 > I just tried installing Xen from Arch, but then my laptop wouldn't > boot. I couldn't use the laptop keyboard, and the external keyboard > didn't work when connected through an external hub. After connecting > it directly I could type, but X wouldn't start. I suspect this is the > fault of the Arch Xen package, as Qubes did work on the same machine, > but I think I'll stick to VB for now... as an aside, i wonder whether there's any collective documentation of = recommended laptop-based xen/mirage development setups? i use linux dom0 = on xen on virtualbox on osx myself but the several other options = discussed in this thread so far might be useful to capture... --=20 Cheers, R. --Apple-Mail=_D72CA674-3626-42CA-B01B-2D2F6C017601 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="signature.asc" Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJTpwnpAAoJEOLF27JWwSg3eu8P/3WmOmCWL4ZT2GY+zcsjilVj 766mLunqrG1NVHGJ2rVgCJNfBbi6OAI353AUkyuxRhBNcm9lPWBcb8/HvaHxILpl u8g38WWKUDBNcjmNVMdIHcrE7bQBvqNzYosN2s74eESpdZGkoh8vJ4HfT31tx67R kTegFZawph3944eYcp/7dGLCyML/VBG3zytTdcQ5mF3FKQllPcMmzWekss+WXgwm TneDPw1YJ7YBaxby5dZx9y4wQgElx3D/RV4uTBA6rnAS+zyX+Q7NNxefsAGQyvVI 8x4jnL7j32i3+VoshWxDDrmk2crE5Wpklkzj33CMBfRxd6j6A0kxoHAl7eLWtDbd 5mZ/RZb7eQoCoTluNhMZ7AxFzJ2IXH6d0x/Qb6mCK/e5TbsdFWwW8uJH4f2dx53K re+ZvJN1w1EzAnlxc5PwHcu+Sgjw3sdXMQAdGh0KJJzjwREII+eLG7EeB+cJEJ4E vNb1wmnIgsnJaqrIdK/w5Hq29kytvEFIdGFMGLZELcHTkptns25c6wTy6oXfBc/T VkIw/gASLpr8NhLSbdh1HyM8LP3KQMTxP5w8bXGHNQDFSTk3GhINqCuKhdIKnu1m V23720Hlvja3AEgQiUK0XAOXSpT3LU1VEQJUqlJ1KugsKd2cGkLp+QbmKgIPT6Ko z7d2qSM4oGrwUqDzlKnl =vZqq -----END PGP SIGNATURE----- --Apple-Mail=_D72CA674-3626-42CA-B01B-2D2F6C017601-- --===============6563001116829724856== 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 --===============6563001116829724856==-- From mirageos-devel-bounces@lists.xenproject.org Sun Jun 22 16:53:41 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 22 Jun 2014 16:53: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 1Wyl1R-0006Oj-Pb; Sun, 22 Jun 2014 16:53:41 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Wyl1R-0006Od-4z for mirageos-devel@lists.xenproject.org; Sun, 22 Jun 2014 16:53:41 +0000 Received: from [193.109.254.147:23392] by server-10.bemta-14.messagelabs.com id E4/74-04546-41A07A35; Sun, 22 Jun 2014 16:53:40 +0000 X-Env-Sender: Richard.Mortier@nottingham.ac.uk X-Msg-Ref: server-12.tower-27.messagelabs.com!1403456019!12896689!1 X-Originating-IP: [93.159.202.117] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10023 invoked from network); 22 Jun 2014 16:53:39 -0000 Received: from engine03-20433-11.icritical.com (HELO engine03-20433-11.icritical.com) (93.159.202.117) by server-12.tower-27.messagelabs.com with SMTP; 22 Jun 2014 16:53:39 -0000 Received: (qmail 29545 invoked from network); 22 Jun 2014 16:53:40 -0000 Received: from localhost (127.0.0.1) by engine03-20433-11.icritical.com with SMTP; 22 Jun 2014 16:53:40 -0000 Received: from engine03-20433-11.icritical.com ([127.0.0.1]) by localhost (engine03-20433-11.icritical.com [127.0.0.1]) (amavisd-new, port 10024) with SMTP id 28549-06 for ; Sun, 22 Jun 2014 17:53:33 +0100 (BST) Received: (qmail 29530 invoked by uid 599); 22 Jun 2014 16:53:33 -0000 Received: from unknown (HELO smtp3.nottingham.ac.uk) (128.243.44.55) by engine03-20433-11.icritical.com (qpsmtpd/0.28) with ESMTP; Sun, 22 Jun 2014 17:53:33 +0100 Received: from uiwexhub01.ad.nottingham.ac.uk ([128.243.15.133]) by smtp3.nottingham.ac.uk with esmtps (TLSv1:AES128-SHA:128) (Exim 4.77) (envelope-from ) id 1Wyl1F-0005kB-NM; Sun, 22 Jun 2014 17:53:29 +0100 From: Richard Mortier To: Anil Madhavapeddy Date: Sun, 22 Jun 2014 17:53:28 +0100 Thread-Topic: [MirageOS-devel] vchan/xenstore in Qubes r3 Thread-Index: Ac+OOn5C5rpXS1j/QFWNJMSwuElAhg== Message-ID: References: <6A38AB63-7876-4CDA-BDE3-87987E926F35@recoil.org> In-Reply-To: Accept-Language: en-US, en-GB Content-Language: en-US X-MS-Has-Attach: yes X-MS-TNEF-Correlator: acceptlanguage: en-US, en-GB MIME-Version: 1.0 X-Virus-Scanned: by iCritical at engine03-20433-11.icritical.com Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] vchan/xenstore in Qubes r3 X-BeenThere: mirageos-devel@lists.xenproject.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="===============5909698833368823611==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============5909698833368823611== Content-Language: en-US Content-Type: multipart/signed; boundary="Apple-Mail=_0CFA6F88-3FAC-4610-B546-A5259E14605D"; protocol="application/pgp-signature"; micalg=pgp-sha512 --Apple-Mail=_0CFA6F88-3FAC-4610-B546-A5259E14605D Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On 21 Jun 2014, at 15:56, Anil Madhavapeddy wrote: > Not using a big Xenstore and shifting to a process-per-VM is also the = model that Bromium's vSentry adopts for their microvirtualization, if I = remember Ian's XenSummit talk right. fwiw, my understanding of his seminar at notts was that it's = approximately a vm per process but not quite as clear cut as that. = (really a vm per "task" which is defined based on a relatively small set = of simple policies for the enterprise context but may include multiple = processes.) --=20 Cheers, R. --Apple-Mail=_0CFA6F88-3FAC-4610-B546-A5259E14605D Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="signature.asc" Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJTpwoIAAoJEOLF27JWwSg35HgQALrNXd8QpqjlF/fqkm9GCJhQ +FAzIvkjxHudpEx5ObBj9m6UNYar9YBv/gNTJGTvAUcV5abu+hRVRMjyDmGzOoxi HKb9Xzxb/laJBeJXW812QdZffFwCi/81wlUuco2Ji5Ryd95i4CVqWtWE12NnT9oD +g+8K79z506uaOPYR8SUcwBkLi1lp6gfAHCqRO7cXVi1kaHEPbwSQ05REQF15I17 f3goimEQHsSL/73jLd7gkHySBlxhlmqncZUVrgFCiQ1A14Oxh175Yw2Cn0zSwqL2 qCai04mWUGzlQdgeGVJHINSRRVYqHr3GC985Wym8RADvWErm38OFWwZIGMw7k1+t e5M8wH3M1KGiXIEuVzaxfc1gznlgHVvjilriK3exppMSn9vzmwcnuytp2VNAzKOL +awX+Dl746vs99VeOJJh/U+qJ/ydOCSUHTF7JNrCVjvMhRyxm1mEk9LsP3enSruV 8GwYeNx6K7jH72JjxdB0CAwt+TQm6p7sn4gcFccMkA4fJoSkKetunYnLhcTvSzs5 DeOlNc8D0yMMJ9eEnMVBuBnElmiupEs8FgMnO8Dq0CtFG1LZFpcQklgXbqgUdQRc C8glJxWp5yR6qLwIkEdNafjoA+R/oXXMizqpzahuucFPG9y2sDmBdAgDNw4UYEyE QFR+O1HgzzrKluesw2hq =mFDI -----END PGP SIGNATURE----- --Apple-Mail=_0CFA6F88-3FAC-4610-B546-A5259E14605D-- --===============5909698833368823611== 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 --===============5909698833368823611==-- From mirageos-devel-bounces@lists.xenproject.org Sun Jun 22 16:53:41 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 22 Jun 2014 16:53: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 1Wyl1R-0006Oj-Pb; Sun, 22 Jun 2014 16:53:41 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Wyl1R-0006Od-4z for mirageos-devel@lists.xenproject.org; Sun, 22 Jun 2014 16:53:41 +0000 Received: from [193.109.254.147:23392] by server-10.bemta-14.messagelabs.com id E4/74-04546-41A07A35; Sun, 22 Jun 2014 16:53:40 +0000 X-Env-Sender: Richard.Mortier@nottingham.ac.uk X-Msg-Ref: server-12.tower-27.messagelabs.com!1403456019!12896689!1 X-Originating-IP: [93.159.202.117] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10023 invoked from network); 22 Jun 2014 16:53:39 -0000 Received: from engine03-20433-11.icritical.com (HELO engine03-20433-11.icritical.com) (93.159.202.117) by server-12.tower-27.messagelabs.com with SMTP; 22 Jun 2014 16:53:39 -0000 Received: (qmail 29545 invoked from network); 22 Jun 2014 16:53:40 -0000 Received: from localhost (127.0.0.1) by engine03-20433-11.icritical.com with SMTP; 22 Jun 2014 16:53:40 -0000 Received: from engine03-20433-11.icritical.com ([127.0.0.1]) by localhost (engine03-20433-11.icritical.com [127.0.0.1]) (amavisd-new, port 10024) with SMTP id 28549-06 for ; Sun, 22 Jun 2014 17:53:33 +0100 (BST) Received: (qmail 29530 invoked by uid 599); 22 Jun 2014 16:53:33 -0000 Received: from unknown (HELO smtp3.nottingham.ac.uk) (128.243.44.55) by engine03-20433-11.icritical.com (qpsmtpd/0.28) with ESMTP; Sun, 22 Jun 2014 17:53:33 +0100 Received: from uiwexhub01.ad.nottingham.ac.uk ([128.243.15.133]) by smtp3.nottingham.ac.uk with esmtps (TLSv1:AES128-SHA:128) (Exim 4.77) (envelope-from ) id 1Wyl1F-0005kB-NM; Sun, 22 Jun 2014 17:53:29 +0100 From: Richard Mortier To: Anil Madhavapeddy Date: Sun, 22 Jun 2014 17:53:28 +0100 Thread-Topic: [MirageOS-devel] vchan/xenstore in Qubes r3 Thread-Index: Ac+OOn5C5rpXS1j/QFWNJMSwuElAhg== Message-ID: References: <6A38AB63-7876-4CDA-BDE3-87987E926F35@recoil.org> In-Reply-To: Accept-Language: en-US, en-GB Content-Language: en-US X-MS-Has-Attach: yes X-MS-TNEF-Correlator: acceptlanguage: en-US, en-GB MIME-Version: 1.0 X-Virus-Scanned: by iCritical at engine03-20433-11.icritical.com Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] vchan/xenstore in Qubes r3 X-BeenThere: mirageos-devel@lists.xenproject.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="===============5909698833368823611==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============5909698833368823611== Content-Language: en-US Content-Type: multipart/signed; boundary="Apple-Mail=_0CFA6F88-3FAC-4610-B546-A5259E14605D"; protocol="application/pgp-signature"; micalg=pgp-sha512 --Apple-Mail=_0CFA6F88-3FAC-4610-B546-A5259E14605D Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On 21 Jun 2014, at 15:56, Anil Madhavapeddy wrote: > Not using a big Xenstore and shifting to a process-per-VM is also the = model that Bromium's vSentry adopts for their microvirtualization, if I = remember Ian's XenSummit talk right. fwiw, my understanding of his seminar at notts was that it's = approximately a vm per process but not quite as clear cut as that. = (really a vm per "task" which is defined based on a relatively small set = of simple policies for the enterprise context but may include multiple = processes.) --=20 Cheers, R. --Apple-Mail=_0CFA6F88-3FAC-4610-B546-A5259E14605D Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="signature.asc" Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJTpwoIAAoJEOLF27JWwSg35HgQALrNXd8QpqjlF/fqkm9GCJhQ +FAzIvkjxHudpEx5ObBj9m6UNYar9YBv/gNTJGTvAUcV5abu+hRVRMjyDmGzOoxi HKb9Xzxb/laJBeJXW812QdZffFwCi/81wlUuco2Ji5Ryd95i4CVqWtWE12NnT9oD +g+8K79z506uaOPYR8SUcwBkLi1lp6gfAHCqRO7cXVi1kaHEPbwSQ05REQF15I17 f3goimEQHsSL/73jLd7gkHySBlxhlmqncZUVrgFCiQ1A14Oxh175Yw2Cn0zSwqL2 qCai04mWUGzlQdgeGVJHINSRRVYqHr3GC985Wym8RADvWErm38OFWwZIGMw7k1+t e5M8wH3M1KGiXIEuVzaxfc1gznlgHVvjilriK3exppMSn9vzmwcnuytp2VNAzKOL +awX+Dl746vs99VeOJJh/U+qJ/ydOCSUHTF7JNrCVjvMhRyxm1mEk9LsP3enSruV 8GwYeNx6K7jH72JjxdB0CAwt+TQm6p7sn4gcFccMkA4fJoSkKetunYnLhcTvSzs5 DeOlNc8D0yMMJ9eEnMVBuBnElmiupEs8FgMnO8Dq0CtFG1LZFpcQklgXbqgUdQRc C8glJxWp5yR6qLwIkEdNafjoA+R/oXXMizqpzahuucFPG9y2sDmBdAgDNw4UYEyE QFR+O1HgzzrKluesw2hq =mFDI -----END PGP SIGNATURE----- --Apple-Mail=_0CFA6F88-3FAC-4610-B546-A5259E14605D-- --===============5909698833368823611== 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 --===============5909698833368823611==-- From mirageos-devel-bounces@lists.xenproject.org Mon Jun 23 08:02:24 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 23 Jun 2014 08:02: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 1WyzCl-0001TQ-I8; Mon, 23 Jun 2014 08:02:19 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WyzCk-0001TI-F8 for mirageos-devel@lists.xenproject.org; Mon, 23 Jun 2014 08:02:18 +0000 Received: from [85.158.139.211:57246] by server-1.bemta-5.messagelabs.com id 37/FC-30932-90FD7A35; Mon, 23 Jun 2014 08:02:17 +0000 X-Env-Sender: talex5@gmail.com X-Msg-Ref: server-14.tower-206.messagelabs.com!1403510535!5978855!1 X-Originating-IP: [209.85.214.182] X-SpamReason: No, hits=0.8 required=7.0 tests=BODY_RANDOM_LONG, ML_RADAR_SPEW_LINKS_14, ML_RADAR_SPEW_LINKS_23, RCVD_BY_IP, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25207 invoked from network); 23 Jun 2014 08:02:17 -0000 Received: from mail-ob0-f182.google.com (HELO mail-ob0-f182.google.com) (209.85.214.182) by server-14.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 23 Jun 2014 08:02:17 -0000 Received: by mail-ob0-f182.google.com with SMTP id nu7so3570354obb.13 for ; Mon, 23 Jun 2014 01:02:15 -0700 (PDT) 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=HpenI2HbU6UHEQDW74eEIGSsCR7yWpchWFwf4BphfMM=; b=bQn40KWL++nAlArDoqeK76lQ5mdb19CqY62T77RmjojJF90h5mE1peSVXo3d8vNQ4x 6AhPR80Gp+A36/oZkd7jPp3wwr8uT5DZy2r265oN0KoDU3ntCS/xvTcfEIHfnUiedRFB a65ZTfDDuuDUZx3zgJ0Q9Sk+VlTNw5WsOFiiBCbCIp/vJLj2mmwyMzhtMFO0GGNy8u6z yO8bSjipPs/MfpMWbiwD6j7T4/axwqVuRZU2/3hTNlYE4LihtZcXi063/POqp/YhkcRQ SkP6EF1rQMqGKohL8QObLjTqftqB/1OZfaJsHlcfZbskgAaXFqz8n1gXKqSeNoLTJqC0 RVtw== MIME-Version: 1.0 X-Received: by 10.60.134.239 with SMTP id pn15mr463257oeb.85.1403510535247; Mon, 23 Jun 2014 01:02:15 -0700 (PDT) Received: by 10.76.92.5 with HTTP; Mon, 23 Jun 2014 01:02:15 -0700 (PDT) In-Reply-To: References: Date: Mon, 23 Jun 2014 09:02:15 +0100 Message-ID: From: Thomas Leonard To: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Mirage on Xen/ARM status X-BeenThere: mirageos-devel@lists.xenproject.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 June 2014 13:33, Thomas Leonard wrote: > An update on the Mirage/ARM port: [...] > My current plan is: > > - Upstream Karim's initial ARM support to Xen. I split the original > patch into three smaller ones and submitted them, but they want it > broken up further, which is fair enough. We're going through many of rounds of review with these patches (no major problems - mainly style issues). I'm going to split them up further to make them easier to review. > - Upstream my patches to build a libminios.a library, plus some other > fixes to the build system. The fixes to the build system have been accepted, but the library patches are waiting for the ARM patches to go in first (otherwise we'll get conflicts). > - Make some changes to Mini-OS to work unmodified with Mirage > (specifically: expose grant table details, disable interrupt-based > event handlers, and allow linking only the features we need). These are also waiting on the previous patches (and need tidying up). We'll need to make our own release of Mini-OS at some point for Mirage 2.0, and almost certainly before these patches are accepted upstream. The later we do it, the closer it will be to what eventually ends up upstream in Xen. The sooner, the more time we have for testing against it. Does some time this week sound reasonable? > - Add a proper string library to mirage-platform to replace Mini-OS's > limited sprintf. I'll probably add the FreeBSD one here. > - Upstream my patches to mirage-platform and mirage to build using the > new libminios and openlibm (these are on github in my forks). How do we want to do this? Can we just tell everyone to upgrade mirage and mirage-platform together, and get Mini-OS and openlibm at the same time, or should we add backwards-compatibility hacks so e.g. mirage can configure for either the old or new version of mirage-platform? > - Upstream my Mini-OS ARM patches to Xen. I squashed these into Karim's ARM patches to simplify the review (no point reviewing code that's about to be replaced). > - Add a start_info structure on ARM, or find some other way to expose > those details to Mirage. This is done, and simplified things greatly. No changes are now needed in mirage-console, etc for ARM. We also need to sort out the ones complement stuff for networking on ARM, but that can come after the upgrade to the new Mini-OS (which is the big change; once we have that, ARM support comes almost for free). -- 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 Jun 23 08:02:24 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 23 Jun 2014 08:02: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 1WyzCl-0001TQ-I8; Mon, 23 Jun 2014 08:02:19 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WyzCk-0001TI-F8 for mirageos-devel@lists.xenproject.org; Mon, 23 Jun 2014 08:02:18 +0000 Received: from [85.158.139.211:57246] by server-1.bemta-5.messagelabs.com id 37/FC-30932-90FD7A35; Mon, 23 Jun 2014 08:02:17 +0000 X-Env-Sender: talex5@gmail.com X-Msg-Ref: server-14.tower-206.messagelabs.com!1403510535!5978855!1 X-Originating-IP: [209.85.214.182] X-SpamReason: No, hits=0.8 required=7.0 tests=BODY_RANDOM_LONG, ML_RADAR_SPEW_LINKS_14, ML_RADAR_SPEW_LINKS_23, RCVD_BY_IP, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25207 invoked from network); 23 Jun 2014 08:02:17 -0000 Received: from mail-ob0-f182.google.com (HELO mail-ob0-f182.google.com) (209.85.214.182) by server-14.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 23 Jun 2014 08:02:17 -0000 Received: by mail-ob0-f182.google.com with SMTP id nu7so3570354obb.13 for ; Mon, 23 Jun 2014 01:02:15 -0700 (PDT) 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=HpenI2HbU6UHEQDW74eEIGSsCR7yWpchWFwf4BphfMM=; b=bQn40KWL++nAlArDoqeK76lQ5mdb19CqY62T77RmjojJF90h5mE1peSVXo3d8vNQ4x 6AhPR80Gp+A36/oZkd7jPp3wwr8uT5DZy2r265oN0KoDU3ntCS/xvTcfEIHfnUiedRFB a65ZTfDDuuDUZx3zgJ0Q9Sk+VlTNw5WsOFiiBCbCIp/vJLj2mmwyMzhtMFO0GGNy8u6z yO8bSjipPs/MfpMWbiwD6j7T4/axwqVuRZU2/3hTNlYE4LihtZcXi063/POqp/YhkcRQ SkP6EF1rQMqGKohL8QObLjTqftqB/1OZfaJsHlcfZbskgAaXFqz8n1gXKqSeNoLTJqC0 RVtw== MIME-Version: 1.0 X-Received: by 10.60.134.239 with SMTP id pn15mr463257oeb.85.1403510535247; Mon, 23 Jun 2014 01:02:15 -0700 (PDT) Received: by 10.76.92.5 with HTTP; Mon, 23 Jun 2014 01:02:15 -0700 (PDT) In-Reply-To: References: Date: Mon, 23 Jun 2014 09:02:15 +0100 Message-ID: From: Thomas Leonard To: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Mirage on Xen/ARM status X-BeenThere: mirageos-devel@lists.xenproject.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 June 2014 13:33, Thomas Leonard wrote: > An update on the Mirage/ARM port: [...] > My current plan is: > > - Upstream Karim's initial ARM support to Xen. I split the original > patch into three smaller ones and submitted them, but they want it > broken up further, which is fair enough. We're going through many of rounds of review with these patches (no major problems - mainly style issues). I'm going to split them up further to make them easier to review. > - Upstream my patches to build a libminios.a library, plus some other > fixes to the build system. The fixes to the build system have been accepted, but the library patches are waiting for the ARM patches to go in first (otherwise we'll get conflicts). > - Make some changes to Mini-OS to work unmodified with Mirage > (specifically: expose grant table details, disable interrupt-based > event handlers, and allow linking only the features we need). These are also waiting on the previous patches (and need tidying up). We'll need to make our own release of Mini-OS at some point for Mirage 2.0, and almost certainly before these patches are accepted upstream. The later we do it, the closer it will be to what eventually ends up upstream in Xen. The sooner, the more time we have for testing against it. Does some time this week sound reasonable? > - Add a proper string library to mirage-platform to replace Mini-OS's > limited sprintf. I'll probably add the FreeBSD one here. > - Upstream my patches to mirage-platform and mirage to build using the > new libminios and openlibm (these are on github in my forks). How do we want to do this? Can we just tell everyone to upgrade mirage and mirage-platform together, and get Mini-OS and openlibm at the same time, or should we add backwards-compatibility hacks so e.g. mirage can configure for either the old or new version of mirage-platform? > - Upstream my Mini-OS ARM patches to Xen. I squashed these into Karim's ARM patches to simplify the review (no point reviewing code that's about to be replaced). > - Add a start_info structure on ARM, or find some other way to expose > those details to Mirage. This is done, and simplified things greatly. No changes are now needed in mirage-console, etc for ARM. We also need to sort out the ones complement stuff for networking on ARM, but that can come after the upgrade to the new Mini-OS (which is the big change; once we have that, ARM support comes almost for free). -- 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 Jun 23 11:09:00 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 23 Jun 2014 11:09:00 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Wz27K-00077B-W3; Mon, 23 Jun 2014 11:08:54 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Wz27J-000771-Qq for mirageos-devel@lists.xenproject.org; Mon, 23 Jun 2014 11:08:54 +0000 Received: from [193.109.254.147:19329] by server-14.bemta-14.messagelabs.com id 92/B2-08195-5CA08A35; Mon, 23 Jun 2014 11:08:53 +0000 X-Env-Sender: amc79@cam.ac.uk X-Msg-Ref: server-2.tower-27.messagelabs.com!1403521732!13022970!1 X-Originating-IP: [131.111.8.141] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTMxLjExMS44LjE0MSA9PiAxNTQ4NjI=\n X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27899 invoked from network); 23 Jun 2014 11:08:52 -0000 Received: from ppsw-41.csi.cam.ac.uk (HELO ppsw-41.csi.cam.ac.uk) (131.111.8.141) by server-2.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 23 Jun 2014 11:08:52 -0000 X-Cam-AntiVirus: no malware found X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/ Received: from dhcp-172-17-137-13.eduroam.lapwing.private.cam.ac.uk ([172.17.137.13]:50993) by ppsw-41.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.157]:587) with esmtpsa (PLAIN:amc79) (TLSv1:AES128-SHA:128) id 1Wz27H-0005CD-Sh (Exim 4.82_3-c0e5623) for mirageos-devel@lists.xenproject.org (return-path ); Mon, 23 Jun 2014 12:08:51 +0100 From: Amir Chaudhry Message-Id: <2CC8D976-EEC1-485F-AF7B-95D556BB515C@cam.ac.uk> Date: Mon, 23 Jun 2014 12:09:10 +0100 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 weekly call, Tuesday 23rd at 4.30pm BST (== GMT + 1) X-BeenThere: mirageos-devel@lists.xenproject.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 Dear all, The Mirage call will take place tomorrow at 4pm BST (== GMT + 1). If you have points you'd like to discuss, please add them to the agenda at https://github.com/mirage/mirage-www/wiki/Call-Agenda - I'll structure them shortly before the call. 1. Please join my meeting. https://www1.gotomeeting.com/join/591890401 Note the dial-in numbers seem to have changed. The new ones are visible if you join the meeting online. I don't have a full list to hand but I believe the US one is: +1 (213) 493-0008 Thanks, 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 Mon Jun 23 11:09:00 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 23 Jun 2014 11:09:00 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Wz27K-00077B-W3; Mon, 23 Jun 2014 11:08:54 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Wz27J-000771-Qq for mirageos-devel@lists.xenproject.org; Mon, 23 Jun 2014 11:08:54 +0000 Received: from [193.109.254.147:19329] by server-14.bemta-14.messagelabs.com id 92/B2-08195-5CA08A35; Mon, 23 Jun 2014 11:08:53 +0000 X-Env-Sender: amc79@cam.ac.uk X-Msg-Ref: server-2.tower-27.messagelabs.com!1403521732!13022970!1 X-Originating-IP: [131.111.8.141] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTMxLjExMS44LjE0MSA9PiAxNTQ4NjI=\n X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27899 invoked from network); 23 Jun 2014 11:08:52 -0000 Received: from ppsw-41.csi.cam.ac.uk (HELO ppsw-41.csi.cam.ac.uk) (131.111.8.141) by server-2.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 23 Jun 2014 11:08:52 -0000 X-Cam-AntiVirus: no malware found X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/ Received: from dhcp-172-17-137-13.eduroam.lapwing.private.cam.ac.uk ([172.17.137.13]:50993) by ppsw-41.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.157]:587) with esmtpsa (PLAIN:amc79) (TLSv1:AES128-SHA:128) id 1Wz27H-0005CD-Sh (Exim 4.82_3-c0e5623) for mirageos-devel@lists.xenproject.org (return-path ); Mon, 23 Jun 2014 12:08:51 +0100 From: Amir Chaudhry Message-Id: <2CC8D976-EEC1-485F-AF7B-95D556BB515C@cam.ac.uk> Date: Mon, 23 Jun 2014 12:09:10 +0100 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 weekly call, Tuesday 23rd at 4.30pm BST (== GMT + 1) X-BeenThere: mirageos-devel@lists.xenproject.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 Dear all, The Mirage call will take place tomorrow at 4pm BST (== GMT + 1). If you have points you'd like to discuss, please add them to the agenda at https://github.com/mirage/mirage-www/wiki/Call-Agenda - I'll structure them shortly before the call. 1. Please join my meeting. https://www1.gotomeeting.com/join/591890401 Note the dial-in numbers seem to have changed. The new ones are visible if you join the meeting online. I don't have a full list to hand but I believe the US one is: +1 (213) 493-0008 Thanks, 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 Mon Jun 23 22:04:23 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 23 Jun 2014 22:04: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 1WzCLY-0007e7-I7; Mon, 23 Jun 2014 22:04:16 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WzCLW-0007e2-Th for mirageos-devel@lists.xenproject.org; Mon, 23 Jun 2014 22:04:15 +0000 Received: from [85.158.139.211:19229] by server-10.bemta-5.messagelabs.com id 98/BD-01434-E54A8A35; Mon, 23 Jun 2014 22:04:14 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-13.tower-206.messagelabs.com!1403561053!11580942!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 649 invoked from network); 23 Jun 2014 22:04:13 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-13.tower-206.messagelabs.com with SMTP; 23 Jun 2014 22:04:13 -0000 Received: (qmail 6382 invoked by uid 634); 23 Jun 2014 22:04:12 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net (HELO [192.168.1.94]) (86.30.244.239) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Mon, 23 Jun 2014 23:04:11 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\)) From: Anil Madhavapeddy In-Reply-To: Date: Mon, 23 Jun 2014 23:04:10 +0100 Message-Id: References: To: Thomas Leonard X-Mailer: Apple Mail (2.1874) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Mirage on Xen/ARM status X-BeenThere: mirageos-devel@lists.xenproject.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 23 Jun 2014, at 09:02, Thomas Leonard wrote: > On 4 June 2014 13:33, Thomas Leonard wrote: >> An update on the Mirage/ARM port: > [...] >> My current plan is: >> >> - Upstream Karim's initial ARM support to Xen. I split the original >> patch into three smaller ones and submitted them, but they want it >> broken up further, which is fair enough. > > We're going through many of rounds of review with these patches (no > major problems - mainly style issues). I'm going to split them up > further to make them easier to review. Thanks for going through the upstreaming so patiently; it's very good to know that we're reducing our custom-fork technical debt. >> - Upstream my patches to build a libminios.a library, plus some other >> fixes to the build system. > > The fixes to the build system have been accepted, but the library > patches are waiting for the ARM patches to go in first (otherwise > we'll get conflicts). >> - Make some changes to Mini-OS to work unmodified with Mirage >> (specifically: expose grant table details, disable interrupt-based >> event handlers, and allow linking only the features we need). > > These are also waiting on the previous patches (and need tidying up). > > We'll need to make our own release of Mini-OS at some point for Mirage > 2.0, and almost certainly before these patches are accepted upstream. > > The later we do it, the closer it will be to what eventually ends up > upstream in Xen. The sooner, the more time we have for testing against > it. Does some time this week sound reasonable? Some time this week sounds great. Since we now know with reasonable certainty that the libminios.a will exist upstream, running with our forked version is fine for a while (and possibly forever, if minor local patches are needed, or we want to do something like tidy up the console logging in such a way that upstream doesn't like it). > >> - Add a proper string library to mirage-platform to replace Mini-OS's >> limited sprintf. > > I'll probably add the FreeBSD one here. Ack. > >> - Upstream my patches to mirage-platform and mirage to build using the >> new libminios and openlibm (these are on github in my forks). > > How do we want to do this? Can we just tell everyone to upgrade mirage > and mirage-platform together, and get Mini-OS and openlibm at the same > time, or should we add backwards-compatibility hacks so e.g. mirage > can configure for either the old or new version of mirage-platform? Mirage 1.2.0 will be the last of the 1.x series (except any minor bugfix releases), and out this week. After that, we can merge the 2.0 branch into trunk, which can include the Makefile changes needed for the new MiniOS (as well as V2 mirage-types). There's no need for backwards compatibility hacks between Mirage 1.x and 2.x. The one hitch is that it's not possible to specify a version constraint on the command line (e.g. so that `opam install mirage-xen {<2.0}` will work), so releasing a new mirage-platform will result in older setups breaking if they upgrade. I'm not sure there's much we can do about that beyond instruct users of old Mirage to pin packages, or pick a new name such as mirage-platform-xen. Both are confusing :( > >> - Upstream my Mini-OS ARM patches to Xen. > > I squashed these into Karim's ARM patches to simplify the review (no > point reviewing code that's about to be replaced). > >> - Add a start_info structure on ARM, or find some other way to expose >> those details to Mirage. > > This is done, and simplified things greatly. No changes are now needed > in mirage-console, etc for ARM. > > We also need to sort out the ones complement stuff for networking on > ARM, but that can come after the upgrade to the new Mini-OS (which is > the big change; once we have that, ARM support comes almost for free). Agreed! -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 Jun 23 22:04:23 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 23 Jun 2014 22:04: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 1WzCLY-0007e7-I7; Mon, 23 Jun 2014 22:04:16 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WzCLW-0007e2-Th for mirageos-devel@lists.xenproject.org; Mon, 23 Jun 2014 22:04:15 +0000 Received: from [85.158.139.211:19229] by server-10.bemta-5.messagelabs.com id 98/BD-01434-E54A8A35; Mon, 23 Jun 2014 22:04:14 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-13.tower-206.messagelabs.com!1403561053!11580942!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 649 invoked from network); 23 Jun 2014 22:04:13 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-13.tower-206.messagelabs.com with SMTP; 23 Jun 2014 22:04:13 -0000 Received: (qmail 6382 invoked by uid 634); 23 Jun 2014 22:04:12 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net (HELO [192.168.1.94]) (86.30.244.239) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Mon, 23 Jun 2014 23:04:11 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\)) From: Anil Madhavapeddy In-Reply-To: Date: Mon, 23 Jun 2014 23:04:10 +0100 Message-Id: References: To: Thomas Leonard X-Mailer: Apple Mail (2.1874) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Mirage on Xen/ARM status X-BeenThere: mirageos-devel@lists.xenproject.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 23 Jun 2014, at 09:02, Thomas Leonard wrote: > On 4 June 2014 13:33, Thomas Leonard wrote: >> An update on the Mirage/ARM port: > [...] >> My current plan is: >> >> - Upstream Karim's initial ARM support to Xen. I split the original >> patch into three smaller ones and submitted them, but they want it >> broken up further, which is fair enough. > > We're going through many of rounds of review with these patches (no > major problems - mainly style issues). I'm going to split them up > further to make them easier to review. Thanks for going through the upstreaming so patiently; it's very good to know that we're reducing our custom-fork technical debt. >> - Upstream my patches to build a libminios.a library, plus some other >> fixes to the build system. > > The fixes to the build system have been accepted, but the library > patches are waiting for the ARM patches to go in first (otherwise > we'll get conflicts). >> - Make some changes to Mini-OS to work unmodified with Mirage >> (specifically: expose grant table details, disable interrupt-based >> event handlers, and allow linking only the features we need). > > These are also waiting on the previous patches (and need tidying up). > > We'll need to make our own release of Mini-OS at some point for Mirage > 2.0, and almost certainly before these patches are accepted upstream. > > The later we do it, the closer it will be to what eventually ends up > upstream in Xen. The sooner, the more time we have for testing against > it. Does some time this week sound reasonable? Some time this week sounds great. Since we now know with reasonable certainty that the libminios.a will exist upstream, running with our forked version is fine for a while (and possibly forever, if minor local patches are needed, or we want to do something like tidy up the console logging in such a way that upstream doesn't like it). > >> - Add a proper string library to mirage-platform to replace Mini-OS's >> limited sprintf. > > I'll probably add the FreeBSD one here. Ack. > >> - Upstream my patches to mirage-platform and mirage to build using the >> new libminios and openlibm (these are on github in my forks). > > How do we want to do this? Can we just tell everyone to upgrade mirage > and mirage-platform together, and get Mini-OS and openlibm at the same > time, or should we add backwards-compatibility hacks so e.g. mirage > can configure for either the old or new version of mirage-platform? Mirage 1.2.0 will be the last of the 1.x series (except any minor bugfix releases), and out this week. After that, we can merge the 2.0 branch into trunk, which can include the Makefile changes needed for the new MiniOS (as well as V2 mirage-types). There's no need for backwards compatibility hacks between Mirage 1.x and 2.x. The one hitch is that it's not possible to specify a version constraint on the command line (e.g. so that `opam install mirage-xen {<2.0}` will work), so releasing a new mirage-platform will result in older setups breaking if they upgrade. I'm not sure there's much we can do about that beyond instruct users of old Mirage to pin packages, or pick a new name such as mirage-platform-xen. Both are confusing :( > >> - Upstream my Mini-OS ARM patches to Xen. > > I squashed these into Karim's ARM patches to simplify the review (no > point reviewing code that's about to be replaced). > >> - Add a start_info structure on ARM, or find some other way to expose >> those details to Mirage. > > This is done, and simplified things greatly. No changes are now needed > in mirage-console, etc for ARM. > > We also need to sort out the ones complement stuff for networking on > ARM, but that can come after the upgrade to the new Mini-OS (which is > the big change; once we have that, ARM support comes almost for free). Agreed! -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 Jun 23 23:09:51 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 23 Jun 2014 23:09: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 1WzDMy-00089F-FE; Mon, 23 Jun 2014 23:09:48 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WzDMy-00089A-4k for mirageos-devel@lists.xenproject.org; Mon, 23 Jun 2014 23:09:48 +0000 Received: from [85.158.137.68:32222] by server-1.bemta-3.messagelabs.com id 6A/BB-13056-BB3B8A35; Mon, 23 Jun 2014 23:09:47 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-6.tower-31.messagelabs.com!1403564986!7450889!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3252 invoked from network); 23 Jun 2014 23:09:46 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-6.tower-31.messagelabs.com with SMTP; 23 Jun 2014 23:09:46 -0000 Received: (qmail 24997 invoked by uid 634); 23 Jun 2014 23:09:45 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net (HELO [192.168.1.94]) (86.30.244.239) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Tue, 24 Jun 2014 00:09:45 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\)) From: Anil Madhavapeddy In-Reply-To: Date: Tue, 24 Jun 2014 00:09:44 +0100 Message-Id: References: <3406CA70-0595-4575-9CCE-85925217C11B@recoil.org> <53A5AD92.3040404@mehnert.org> To: Thomas Gazagnaire X-Mailer: Apple Mail (2.1874) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Using Clock directly from the mirage tool X-BeenThere: mirageos-devel@lists.xenproject.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 merged into mirage-trunk now, and will be in 1.2.0. Hannes, David, do you want to make ocaml-tls depend on mirage-trunk for now, so you can undo the CLOCK hacks and ensure the support is enough for what you need? -anil On 21 Jun 2014, at 23:17, Thomas Gazagnaire wrote: > Done in https://github.com/mirage/mirage/pull/255 > > Note, the PR contains slightly more changes that really needed, but I think I didn't break any user code. In doubt, the only relevant commit is https://github.com/samoht/mirage/commit/68958f760f35e6dd259eddfcc803395041a72891 > > Thomas > > > On 21 Jun 2014, at 17:06, Hannes Mehnert wrote: > >> Signed PGP part >> On 06/21/2014 16:07, Anil Madhavapeddy wrote: >>> You mentioned a problem with the Mirage frontend not exposing a >>> generator for Clock directly to unikernels. ThomasG thought that >>> it should be an easy fix, but I can't find a bug open for this. Is >>> it still an issue? >> >> It is. Our current workaround is to require mirage-clock-unix: >> https://github.com/mirleft/ocaml-tls/commit/4e54d3122c882552198c0eacfbb7af9d67888d32 >> >> (and our X509 module requires a CLOCK): >> https://github.com/mirleft/ocaml-tls/commit/8a71e7fca4e022edaeb79076972ce7818ed30ac9 >> >> Cheers, >> >> Hannes >> >> >> _______________________________________________ >> 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 Mon Jun 23 23:09:51 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 23 Jun 2014 23:09: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 1WzDMy-00089F-FE; Mon, 23 Jun 2014 23:09:48 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WzDMy-00089A-4k for mirageos-devel@lists.xenproject.org; Mon, 23 Jun 2014 23:09:48 +0000 Received: from [85.158.137.68:32222] by server-1.bemta-3.messagelabs.com id 6A/BB-13056-BB3B8A35; Mon, 23 Jun 2014 23:09:47 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-6.tower-31.messagelabs.com!1403564986!7450889!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3252 invoked from network); 23 Jun 2014 23:09:46 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-6.tower-31.messagelabs.com with SMTP; 23 Jun 2014 23:09:46 -0000 Received: (qmail 24997 invoked by uid 634); 23 Jun 2014 23:09:45 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net (HELO [192.168.1.94]) (86.30.244.239) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Tue, 24 Jun 2014 00:09:45 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\)) From: Anil Madhavapeddy In-Reply-To: Date: Tue, 24 Jun 2014 00:09:44 +0100 Message-Id: References: <3406CA70-0595-4575-9CCE-85925217C11B@recoil.org> <53A5AD92.3040404@mehnert.org> To: Thomas Gazagnaire X-Mailer: Apple Mail (2.1874) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Using Clock directly from the mirage tool X-BeenThere: mirageos-devel@lists.xenproject.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 merged into mirage-trunk now, and will be in 1.2.0. Hannes, David, do you want to make ocaml-tls depend on mirage-trunk for now, so you can undo the CLOCK hacks and ensure the support is enough for what you need? -anil On 21 Jun 2014, at 23:17, Thomas Gazagnaire wrote: > Done in https://github.com/mirage/mirage/pull/255 > > Note, the PR contains slightly more changes that really needed, but I think I didn't break any user code. In doubt, the only relevant commit is https://github.com/samoht/mirage/commit/68958f760f35e6dd259eddfcc803395041a72891 > > Thomas > > > On 21 Jun 2014, at 17:06, Hannes Mehnert wrote: > >> Signed PGP part >> On 06/21/2014 16:07, Anil Madhavapeddy wrote: >>> You mentioned a problem with the Mirage frontend not exposing a >>> generator for Clock directly to unikernels. ThomasG thought that >>> it should be an easy fix, but I can't find a bug open for this. Is >>> it still an issue? >> >> It is. Our current workaround is to require mirage-clock-unix: >> https://github.com/mirleft/ocaml-tls/commit/4e54d3122c882552198c0eacfbb7af9d67888d32 >> >> (and our X509 module requires a CLOCK): >> https://github.com/mirleft/ocaml-tls/commit/8a71e7fca4e022edaeb79076972ce7818ed30ac9 >> >> Cheers, >> >> Hannes >> >> >> _______________________________________________ >> 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 Jun 24 13:21:30 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 24 Jun 2014 13:21: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 1WzQf5-0002QG-Dy; Tue, 24 Jun 2014 13:21:23 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WzQf4-0002QA-OG for mirageos-devel@lists.xenproject.org; Tue, 24 Jun 2014 13:21:22 +0000 Received: from [85.158.137.68:49705] by server-15.bemta-3.messagelabs.com id DF/B4-26980-25B79A35; Tue, 24 Jun 2014 13:21:22 +0000 X-Env-Sender: yallop@gmail.com X-Msg-Ref: server-9.tower-31.messagelabs.com!1403616081!8318463!1 X-Originating-IP: [209.85.212.182] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30599 invoked from network); 24 Jun 2014 13:21:21 -0000 Received: from mail-wi0-f182.google.com (HELO mail-wi0-f182.google.com) (209.85.212.182) by server-9.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 24 Jun 2014 13:21:21 -0000 Received: by mail-wi0-f182.google.com with SMTP id bs8so589977wib.15 for ; Tue, 24 Jun 2014 06:21:20 -0700 (PDT) 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=4TOL7jX/i2iXB6qXwLDnzMd/SqDVXLvkwUAKb2dGBas=; b=DxH/KgIlDEIH8NEj4FnboYYH3cvqs8VnK8jxl/zP2kLKwn30AmbdWHxI56wfB4RUwC 2P8S3ycH2rij18dvfhgpjgCH3YCGd8zZLYwST6VcpNseTgS/BAxty2pt+LQ2i+kUslBe Ni7z2Ho6MmG0xRM0Pn8jCfDxjjuTX0M8Dthq7e4bpn7pj4sqI5pwZXQKsA09uT9P3isC klgngDweZUa/H61zEIc9Nv2YNCCV8jvU8o+e/QTWDdtYAbPWkYh5ELBr/LlxWl3GpOFz Hca4isd9cjqK5kcn5zQiS3HAE4BOOK34mXvj+kmv2i5dzZSypDhbgPMS4zDapgwazlqM iMDw== MIME-Version: 1.0 X-Received: by 10.180.103.228 with SMTP id fz4mr34078141wib.4.1403616078821; Tue, 24 Jun 2014 06:21:18 -0700 (PDT) Received: by 10.216.219.193 with HTTP; Tue, 24 Jun 2014 06:21:18 -0700 (PDT) In-Reply-To: References: Date: Tue, 24 Jun 2014 14:21:18 +0100 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" , netos@cl.cam.ac.uk Subject: Re: [MirageOS-devel] OCaml compiler hacking next Wednesday (25th June) X-BeenThere: mirageos-devel@lists.xenproject.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 Update: Stephen Dolan will be starting off tomorrow's compiler hacking session with a demo of multicore OCaml! If you're planning to come along but haven't yet signed up it'd be helpful if you could add your name to the Doodle poll: http://doodle.com/2ps9gunbkiy3tp6i On 20 June 2014 23:43, Jeremy Yallop wrote: > It's time for another OCaml compiler hacking session! We'll be > meeting in the computer lab next Wednesday evening (25th June). The > details are on the blog: > > http://ocamllabs.github.io/compiler-hacking/2014/06/20/sixth-compiler-hacking-session.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 Tue Jun 24 13:21:30 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 24 Jun 2014 13:21: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 1WzQf5-0002QG-Dy; Tue, 24 Jun 2014 13:21:23 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WzQf4-0002QA-OG for mirageos-devel@lists.xenproject.org; Tue, 24 Jun 2014 13:21:22 +0000 Received: from [85.158.137.68:49705] by server-15.bemta-3.messagelabs.com id DF/B4-26980-25B79A35; Tue, 24 Jun 2014 13:21:22 +0000 X-Env-Sender: yallop@gmail.com X-Msg-Ref: server-9.tower-31.messagelabs.com!1403616081!8318463!1 X-Originating-IP: [209.85.212.182] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30599 invoked from network); 24 Jun 2014 13:21:21 -0000 Received: from mail-wi0-f182.google.com (HELO mail-wi0-f182.google.com) (209.85.212.182) by server-9.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 24 Jun 2014 13:21:21 -0000 Received: by mail-wi0-f182.google.com with SMTP id bs8so589977wib.15 for ; Tue, 24 Jun 2014 06:21:20 -0700 (PDT) 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=4TOL7jX/i2iXB6qXwLDnzMd/SqDVXLvkwUAKb2dGBas=; b=DxH/KgIlDEIH8NEj4FnboYYH3cvqs8VnK8jxl/zP2kLKwn30AmbdWHxI56wfB4RUwC 2P8S3ycH2rij18dvfhgpjgCH3YCGd8zZLYwST6VcpNseTgS/BAxty2pt+LQ2i+kUslBe Ni7z2Ho6MmG0xRM0Pn8jCfDxjjuTX0M8Dthq7e4bpn7pj4sqI5pwZXQKsA09uT9P3isC klgngDweZUa/H61zEIc9Nv2YNCCV8jvU8o+e/QTWDdtYAbPWkYh5ELBr/LlxWl3GpOFz Hca4isd9cjqK5kcn5zQiS3HAE4BOOK34mXvj+kmv2i5dzZSypDhbgPMS4zDapgwazlqM iMDw== MIME-Version: 1.0 X-Received: by 10.180.103.228 with SMTP id fz4mr34078141wib.4.1403616078821; Tue, 24 Jun 2014 06:21:18 -0700 (PDT) Received: by 10.216.219.193 with HTTP; Tue, 24 Jun 2014 06:21:18 -0700 (PDT) In-Reply-To: References: Date: Tue, 24 Jun 2014 14:21:18 +0100 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" , netos@cl.cam.ac.uk Subject: Re: [MirageOS-devel] OCaml compiler hacking next Wednesday (25th June) X-BeenThere: mirageos-devel@lists.xenproject.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 Update: Stephen Dolan will be starting off tomorrow's compiler hacking session with a demo of multicore OCaml! If you're planning to come along but haven't yet signed up it'd be helpful if you could add your name to the Doodle poll: http://doodle.com/2ps9gunbkiy3tp6i On 20 June 2014 23:43, Jeremy Yallop wrote: > It's time for another OCaml compiler hacking session! We'll be > meeting in the computer lab next Wednesday evening (25th June). The > details are on the blog: > > http://ocamllabs.github.io/compiler-hacking/2014/06/20/sixth-compiler-hacking-session.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 Tue Jun 24 14:06:16 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 24 Jun 2014 14:06: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 1WzRMV-0004V5-D9; Tue, 24 Jun 2014 14:06:15 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WzRMT-0004Ut-CI for mirageos-devel@lists.xenproject.org; Tue, 24 Jun 2014 14:06:13 +0000 Received: from [85.158.139.211:47254] by server-3.bemta-5.messagelabs.com id C9/EE-01676-4D589A35; Tue, 24 Jun 2014 14:06:12 +0000 X-Env-Sender: scott.dj@gmail.com X-Msg-Ref: server-15.tower-206.messagelabs.com!1403618770!8377357!1 X-Originating-IP: [209.85.160.52] X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_40_50,HTML_MESSAGE, MAILTO_TO_SPAM_ADDR,ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 14170 invoked from network); 24 Jun 2014 14:06:11 -0000 Received: from mail-pb0-f52.google.com (HELO mail-pb0-f52.google.com) (209.85.160.52) by server-15.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 24 Jun 2014 14:06:11 -0000 Received: by mail-pb0-f52.google.com with SMTP id rq2so296651pbb.11 for ; Tue, 24 Jun 2014 07:06:09 -0700 (PDT) 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=ASv4Kmoo2hrl9TadVN1ij+nKvKRB2KO9zKuvs5iooUI=; b=KxKhMv5XYFD2e0xUIyIQYiKCRWswtAKnHiPrdqSKIy8JuBbaZRtI0GVwyzbF5MikJM IwSYQ8Sw9OX3C+9c/C88X/eRtherrxAxrIax4X4VgKzJ79dxCJlZy753hg4rK64m80zQ TSQBZwQPR6qDhfrZPWccPEZrL0XXCZpU17ddmgL2qseBGQb0ZQnINW15tZxpZeRFTW21 rW/4MYNH/VQwZ+kgsj8Zf0+HNAA0Ig6yhSysso8zAizyAB67ANLrNK92X2KG60RsYrbn qMlG9euVLr1wQyqy9pI67Q3lr/eZCAfgydL51YD8yNhcqhoAMTvNP1sWEb6sOZTg41Sz 7haA== MIME-Version: 1.0 X-Received: by 10.68.130.6 with SMTP id oa6mr1853663pbb.102.1403618769728; Tue, 24 Jun 2014 07:06:09 -0700 (PDT) Received: by 10.70.11.65 with HTTP; Tue, 24 Jun 2014 07:06:09 -0700 (PDT) In-Reply-To: <2CC8D976-EEC1-485F-AF7B-95D556BB515C@cam.ac.uk> References: <2CC8D976-EEC1-485F-AF7B-95D556BB515C@cam.ac.uk> Date: Tue, 24 Jun 2014 15:06:09 +0100 Message-ID: From: David Scott To: Amir Chaudhry Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Mirage weekly call, Tuesday 23rd at 4.30pm BST (== GMT + 1) X-BeenThere: mirageos-devel@lists.xenproject.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="===============7144676732755216890==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============7144676732755216890== Content-Type: multipart/alternative; boundary=e89a8ffbaecb2b7c3d04fc95766a --e89a8ffbaecb2b7c3d04fc95766a Content-Type: text/plain; charset=UTF-8 I assume the meeting is at 4pm, as in the email body (and not at 4.30pm as in the subject) Shout if I'm wrong! On Mon, Jun 23, 2014 at 12:09 PM, Amir Chaudhry wrote: > Dear all, > > The Mirage call will take place tomorrow at 4pm BST (== GMT + 1). If you > have points you'd like to discuss, please add them to the agenda at > https://github.com/mirage/mirage-www/wiki/Call-Agenda - I'll structure > them shortly before the call. > > 1. Please join my meeting. > https://www1.gotomeeting.com/join/591890401 > > Note the dial-in numbers seem to have changed. The new ones are visible if > you join the meeting online. I don't have a full list to hand but I believe > the US one is: > > +1 (213) 493-0008 > > > Thanks, > Amir > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > -- Dave Scott --e89a8ffbaecb2b7c3d04fc95766a Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
I assume the meeting is at 4pm, as in the email body (and = not at 4.30pm as in the subject)

Shout if I'm wrong!=


O= n Mon, Jun 23, 2014 at 12:09 PM, Amir Chaudhry <amc79@cam.ac.uk> wrote:
Dear all,

The Mirage call will take place tomorrow at 4pm BST (=3D=3D GMT + 1). =C2= =A0If you have points you'd like to discuss, please add them to the age= nda at https://github.com/mirage/mirage-www/wiki/Call-Agenda -= I'll structure them shortly before the call.

1. =C2=A0Please join my meeting.
h= ttps://www1.gotomeeting.com/join/591890401

Note the dial-in numbers seem to have changed. The new ones are visible if = you join the meeting online. I don't have a full list to hand but I bel= ieve the US one is:

+1 (213)= 493-0008


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



--
Dave Scott
--e89a8ffbaecb2b7c3d04fc95766a-- --===============7144676732755216890== 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 --===============7144676732755216890==-- From mirageos-devel-bounces@lists.xenproject.org Tue Jun 24 14:06:16 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 24 Jun 2014 14:06: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 1WzRMV-0004V5-D9; Tue, 24 Jun 2014 14:06:15 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WzRMT-0004Ut-CI for mirageos-devel@lists.xenproject.org; Tue, 24 Jun 2014 14:06:13 +0000 Received: from [85.158.139.211:47254] by server-3.bemta-5.messagelabs.com id C9/EE-01676-4D589A35; Tue, 24 Jun 2014 14:06:12 +0000 X-Env-Sender: scott.dj@gmail.com X-Msg-Ref: server-15.tower-206.messagelabs.com!1403618770!8377357!1 X-Originating-IP: [209.85.160.52] X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_40_50,HTML_MESSAGE, MAILTO_TO_SPAM_ADDR,ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 14170 invoked from network); 24 Jun 2014 14:06:11 -0000 Received: from mail-pb0-f52.google.com (HELO mail-pb0-f52.google.com) (209.85.160.52) by server-15.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 24 Jun 2014 14:06:11 -0000 Received: by mail-pb0-f52.google.com with SMTP id rq2so296651pbb.11 for ; Tue, 24 Jun 2014 07:06:09 -0700 (PDT) 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=ASv4Kmoo2hrl9TadVN1ij+nKvKRB2KO9zKuvs5iooUI=; b=KxKhMv5XYFD2e0xUIyIQYiKCRWswtAKnHiPrdqSKIy8JuBbaZRtI0GVwyzbF5MikJM IwSYQ8Sw9OX3C+9c/C88X/eRtherrxAxrIax4X4VgKzJ79dxCJlZy753hg4rK64m80zQ TSQBZwQPR6qDhfrZPWccPEZrL0XXCZpU17ddmgL2qseBGQb0ZQnINW15tZxpZeRFTW21 rW/4MYNH/VQwZ+kgsj8Zf0+HNAA0Ig6yhSysso8zAizyAB67ANLrNK92X2KG60RsYrbn qMlG9euVLr1wQyqy9pI67Q3lr/eZCAfgydL51YD8yNhcqhoAMTvNP1sWEb6sOZTg41Sz 7haA== MIME-Version: 1.0 X-Received: by 10.68.130.6 with SMTP id oa6mr1853663pbb.102.1403618769728; Tue, 24 Jun 2014 07:06:09 -0700 (PDT) Received: by 10.70.11.65 with HTTP; Tue, 24 Jun 2014 07:06:09 -0700 (PDT) In-Reply-To: <2CC8D976-EEC1-485F-AF7B-95D556BB515C@cam.ac.uk> References: <2CC8D976-EEC1-485F-AF7B-95D556BB515C@cam.ac.uk> Date: Tue, 24 Jun 2014 15:06:09 +0100 Message-ID: From: David Scott To: Amir Chaudhry Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Mirage weekly call, Tuesday 23rd at 4.30pm BST (== GMT + 1) X-BeenThere: mirageos-devel@lists.xenproject.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="===============7144676732755216890==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============7144676732755216890== Content-Type: multipart/alternative; boundary=e89a8ffbaecb2b7c3d04fc95766a --e89a8ffbaecb2b7c3d04fc95766a Content-Type: text/plain; charset=UTF-8 I assume the meeting is at 4pm, as in the email body (and not at 4.30pm as in the subject) Shout if I'm wrong! On Mon, Jun 23, 2014 at 12:09 PM, Amir Chaudhry wrote: > Dear all, > > The Mirage call will take place tomorrow at 4pm BST (== GMT + 1). If you > have points you'd like to discuss, please add them to the agenda at > https://github.com/mirage/mirage-www/wiki/Call-Agenda - I'll structure > them shortly before the call. > > 1. Please join my meeting. > https://www1.gotomeeting.com/join/591890401 > > Note the dial-in numbers seem to have changed. The new ones are visible if > you join the meeting online. I don't have a full list to hand but I believe > the US one is: > > +1 (213) 493-0008 > > > Thanks, > Amir > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > -- Dave Scott --e89a8ffbaecb2b7c3d04fc95766a Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
I assume the meeting is at 4pm, as in the email body (and = not at 4.30pm as in the subject)

Shout if I'm wrong!=


O= n Mon, Jun 23, 2014 at 12:09 PM, Amir Chaudhry <amc79@cam.ac.uk> wrote:
Dear all,

The Mirage call will take place tomorrow at 4pm BST (=3D=3D GMT + 1). =C2= =A0If you have points you'd like to discuss, please add them to the age= nda at https://github.com/mirage/mirage-www/wiki/Call-Agenda -= I'll structure them shortly before the call.

1. =C2=A0Please join my meeting.
h= ttps://www1.gotomeeting.com/join/591890401

Note the dial-in numbers seem to have changed. The new ones are visible if = you join the meeting online. I don't have a full list to hand but I bel= ieve the US one is:

+1 (213)= 493-0008


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



--
Dave Scott
--e89a8ffbaecb2b7c3d04fc95766a-- --===============7144676732755216890== 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 --===============7144676732755216890==-- From mirageos-devel-bounces@lists.xenproject.org Tue Jun 24 14:23:35 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 24 Jun 2014 14:23: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 1WzRdD-0004vK-G0; Tue, 24 Jun 2014 14:23:31 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WzRdC-0004vF-Bp for mirageos-devel@lists.xenproject.org; Tue, 24 Jun 2014 14:23:30 +0000 Received: from [193.109.254.147:5924] by server-15.bemta-14.messagelabs.com id 16/B4-15813-1E989A35; Tue, 24 Jun 2014 14:23:29 +0000 X-Env-Sender: mindy@somerandomidiot.com X-Msg-Ref: server-13.tower-27.messagelabs.com!1403619808!13371005!1 X-Originating-IP: [217.70.183.198] X-SpamReason: No, hits=0.6 required=7.0 tests=HTML_60_70,HTML_MESSAGE, MAILTO_TO_SPAM_ADDR X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 1255 invoked from network); 24 Jun 2014 14:23:28 -0000 Received: from relay6-d.mail.gandi.net (HELO relay6-d.mail.gandi.net) (217.70.183.198) by server-13.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 24 Jun 2014 14:23:28 -0000 Received: from mfilter23-d.gandi.net (mfilter23-d.gandi.net [217.70.178.151]) by relay6-d.mail.gandi.net (Postfix) with ESMTP id 3E00CFB8E1 for ; Tue, 24 Jun 2014 16:23:28 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at mfilter23-d.gandi.net Received: from relay6-d.mail.gandi.net ([217.70.183.198]) by mfilter23-d.gandi.net (mfilter23-d.gandi.net [10.0.15.180]) (amavisd-new, port 10024) with ESMTP id LlUzz3Wt+WEs for ; Tue, 24 Jun 2014 16:23:26 +0200 (CEST) X-Originating-IP: 67.23.193.215 Received: from [10.1.8.26] (unknown [67.23.193.215]) (Authenticated sender: guybrush@somerandomidiot.com) by relay6-d.mail.gandi.net (Postfix) with ESMTPSA id 26B05FB89F for ; Tue, 24 Jun 2014 16:23:24 +0200 (CEST) Message-ID: <53A989D7.6020008@somerandomidiot.com> Date: Tue, 24 Jun 2014 09:23:19 -0500 From: Mindy User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: mirageos-devel@lists.xenproject.org References: <2CC8D976-EEC1-485F-AF7B-95D556BB515C@cam.ac.uk> In-Reply-To: Subject: Re: [MirageOS-devel] Mirage weekly call, Tuesday 23rd at 4.30pm BST (== GMT + 1) X-BeenThere: mirageos-devel@lists.xenproject.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="===============8917772892576038715==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org This is a multi-part message in MIME format. --===============8917772892576038715== Content-Type: multipart/alternative; boundary="------------030907080007080508030909" This is a multi-part message in MIME format. --------------030907080007080508030909 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit I won't be able to make it this week, unfortunately. :( -Mindy On 06/24/2014 09:06 AM, David Scott wrote: > I assume the meeting is at 4pm, as in the email body (and not at > 4.30pm as in the subject) > > Shout if I'm wrong! > > > On Mon, Jun 23, 2014 at 12:09 PM, Amir Chaudhry > wrote: > > Dear all, > > The Mirage call will take place tomorrow at 4pm BST (== GMT + 1). > If you have points you'd like to discuss, please add them to the > agenda at https://github.com/mirage/mirage-www/wiki/Call-Agenda - > I'll structure them shortly before the call. > > 1. Please join my meeting. > https://www1.gotomeeting.com/join/591890401 > > Note the dial-in numbers seem to have changed. The new ones are > visible if you join the meeting online. I don't have a full list > to hand but I believe the US one is: > > +1 (213) 493-0008 > > > Thanks, > Amir > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > > > > > -- > Dave Scott > > > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --------------030907080007080508030909 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit I won't be able to make it this week, unfortunately. :(

-Mindy
On 06/24/2014 09:06 AM, David Scott wrote:
I assume the meeting is at 4pm, as in the email body (and not at 4.30pm as in the subject)

Shout if I'm wrong!


On Mon, Jun 23, 2014 at 12:09 PM, Amir Chaudhry <amc79@cam.ac.uk> wrote:
Dear all,

The Mirage call will take place tomorrow at 4pm BST (== GMT + 1).  If you have points you'd like to discuss, please add them to the agenda at https://github.com/mirage/mirage-www/wiki/Call-Agenda - I'll structure them shortly before the call.

1.  Please join my meeting.
https://www1.gotomeeting.com/join/591890401

Note the dial-in numbers seem to have changed. The new ones are visible if you join the meeting online. I don't have a full list to hand but I believe the US one is:

+1 (213) 493-0008


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



--
Dave Scott 


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

--------------030907080007080508030909-- --===============8917772892576038715== 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 --===============8917772892576038715==-- From mirageos-devel-bounces@lists.xenproject.org Tue Jun 24 14:23:35 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 24 Jun 2014 14:23: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 1WzRdD-0004vK-G0; Tue, 24 Jun 2014 14:23:31 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WzRdC-0004vF-Bp for mirageos-devel@lists.xenproject.org; Tue, 24 Jun 2014 14:23:30 +0000 Received: from [193.109.254.147:5924] by server-15.bemta-14.messagelabs.com id 16/B4-15813-1E989A35; Tue, 24 Jun 2014 14:23:29 +0000 X-Env-Sender: mindy@somerandomidiot.com X-Msg-Ref: server-13.tower-27.messagelabs.com!1403619808!13371005!1 X-Originating-IP: [217.70.183.198] X-SpamReason: No, hits=0.6 required=7.0 tests=HTML_60_70,HTML_MESSAGE, MAILTO_TO_SPAM_ADDR X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 1255 invoked from network); 24 Jun 2014 14:23:28 -0000 Received: from relay6-d.mail.gandi.net (HELO relay6-d.mail.gandi.net) (217.70.183.198) by server-13.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 24 Jun 2014 14:23:28 -0000 Received: from mfilter23-d.gandi.net (mfilter23-d.gandi.net [217.70.178.151]) by relay6-d.mail.gandi.net (Postfix) with ESMTP id 3E00CFB8E1 for ; Tue, 24 Jun 2014 16:23:28 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at mfilter23-d.gandi.net Received: from relay6-d.mail.gandi.net ([217.70.183.198]) by mfilter23-d.gandi.net (mfilter23-d.gandi.net [10.0.15.180]) (amavisd-new, port 10024) with ESMTP id LlUzz3Wt+WEs for ; Tue, 24 Jun 2014 16:23:26 +0200 (CEST) X-Originating-IP: 67.23.193.215 Received: from [10.1.8.26] (unknown [67.23.193.215]) (Authenticated sender: guybrush@somerandomidiot.com) by relay6-d.mail.gandi.net (Postfix) with ESMTPSA id 26B05FB89F for ; Tue, 24 Jun 2014 16:23:24 +0200 (CEST) Message-ID: <53A989D7.6020008@somerandomidiot.com> Date: Tue, 24 Jun 2014 09:23:19 -0500 From: Mindy User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: mirageos-devel@lists.xenproject.org References: <2CC8D976-EEC1-485F-AF7B-95D556BB515C@cam.ac.uk> In-Reply-To: Subject: Re: [MirageOS-devel] Mirage weekly call, Tuesday 23rd at 4.30pm BST (== GMT + 1) X-BeenThere: mirageos-devel@lists.xenproject.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="===============8917772892576038715==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org This is a multi-part message in MIME format. --===============8917772892576038715== Content-Type: multipart/alternative; boundary="------------030907080007080508030909" This is a multi-part message in MIME format. --------------030907080007080508030909 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit I won't be able to make it this week, unfortunately. :( -Mindy On 06/24/2014 09:06 AM, David Scott wrote: > I assume the meeting is at 4pm, as in the email body (and not at > 4.30pm as in the subject) > > Shout if I'm wrong! > > > On Mon, Jun 23, 2014 at 12:09 PM, Amir Chaudhry > wrote: > > Dear all, > > The Mirage call will take place tomorrow at 4pm BST (== GMT + 1). > If you have points you'd like to discuss, please add them to the > agenda at https://github.com/mirage/mirage-www/wiki/Call-Agenda - > I'll structure them shortly before the call. > > 1. Please join my meeting. > https://www1.gotomeeting.com/join/591890401 > > Note the dial-in numbers seem to have changed. The new ones are > visible if you join the meeting online. I don't have a full list > to hand but I believe the US one is: > > +1 (213) 493-0008 > > > Thanks, > Amir > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > > > > > -- > Dave Scott > > > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --------------030907080007080508030909 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit I won't be able to make it this week, unfortunately. :(

-Mindy
On 06/24/2014 09:06 AM, David Scott wrote:
I assume the meeting is at 4pm, as in the email body (and not at 4.30pm as in the subject)

Shout if I'm wrong!


On Mon, Jun 23, 2014 at 12:09 PM, Amir Chaudhry <amc79@cam.ac.uk> wrote:
Dear all,

The Mirage call will take place tomorrow at 4pm BST (== GMT + 1).  If you have points you'd like to discuss, please add them to the agenda at https://github.com/mirage/mirage-www/wiki/Call-Agenda - I'll structure them shortly before the call.

1.  Please join my meeting.
https://www1.gotomeeting.com/join/591890401

Note the dial-in numbers seem to have changed. The new ones are visible if you join the meeting online. I don't have a full list to hand but I believe the US one is:

+1 (213) 493-0008


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



--
Dave Scott 


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

--------------030907080007080508030909-- --===============8917772892576038715== 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 --===============8917772892576038715==-- From mirageos-devel-bounces@lists.xenproject.org Tue Jun 24 14:34:56 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 24 Jun 2014 14:34: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 1WzRoF-0005D6-4E; Tue, 24 Jun 2014 14:34:55 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WzRoD-0005D0-Dy for mirageos-devel@lists.xenproject.org; Tue, 24 Jun 2014 14:34:53 +0000 Received: from [85.158.137.68:36148] by server-16.bemta-3.messagelabs.com id 15/5C-28986-C8C89A35; Tue, 24 Jun 2014 14:34:52 +0000 X-Env-Sender: amc79@cam.ac.uk X-Msg-Ref: server-7.tower-31.messagelabs.com!1403620491!12064863!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.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 24967 invoked from network); 24 Jun 2014 14:34:51 -0000 Received: from ppsw-52.csi.cam.ac.uk (HELO ppsw-52.csi.cam.ac.uk) (131.111.8.152) by server-7.tower-31.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 24 Jun 2014 14:34:51 -0000 X-Cam-AntiVirus: no malware found X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/ Received: from dhcp-172-17-159-208.eduroam.lapwing.private.cam.ac.uk ([172.17.159.208]:52971) 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 1WzRoB-0004ec-E4 (Exim 4.82_3-c0e5623) for mirageos-devel@lists.xenproject.org (return-path ); Tue, 24 Jun 2014 15:34:51 +0100 Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) From: Amir Chaudhry In-Reply-To: <53A989D7.6020008@somerandomidiot.com> Date: Tue, 24 Jun 2014 15:34:53 +0100 Message-Id: <85CB0755-0669-4038-AC0A-1544E49C5A79@cam.ac.uk> References: <2CC8D976-EEC1-485F-AF7B-95D556BB515C@cam.ac.uk> <53A989D7.6020008@somerandomidiot.com> To: "mirageos-devel@lists.xenproject.org" X-Mailer: Apple Mail (2.1510) Subject: Re: [MirageOS-devel] Mirage weekly call, Tuesday 23rd at 4pm BST (== GMT + 1) X-BeenThere: mirageos-devel@lists.xenproject.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, the call is at 4pm this week. Apologies for the error! Sorry we'll miss you this week, Mindy. Amir On 24 Jun 2014, at 15:23, Mindy wrote: > I won't be able to make it this week, unfortunately. :( > > -Mindy > On 06/24/2014 09:06 AM, David Scott wrote: >> I assume the meeting is at 4pm, as in the email body (and not at 4.30pm as in the subject) >> >> Shout if I'm wrong! >> >> >> On Mon, Jun 23, 2014 at 12:09 PM, Amir Chaudhry wrote: >> Dear all, >> >> The Mirage call will take place tomorrow at 4pm BST (== GMT + 1). If you have points you'd like to discuss, please add them to the agenda at https://github.com/mirage/mirage-www/wiki/Call-Agenda - I'll structure them shortly before the call. >> >> 1. Please join my meeting. >> https://www1.gotomeeting.com/join/591890401 >> >> Note the dial-in numbers seem to have changed. The new ones are visible if you join the meeting online. I don't have a full list to hand but I believe the US one is: >> >> +1 (213) 493-0008 >> >> >> Thanks, >> Amir >> _______________________________________________ >> MirageOS-devel mailing list >> MirageOS-devel@lists.xenproject.org >> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel >> >> >> >> -- >> Dave Scott >> >> >> _______________________________________________ >> 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 Jun 24 14:34:56 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 24 Jun 2014 14:34: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 1WzRoF-0005D6-4E; Tue, 24 Jun 2014 14:34:55 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WzRoD-0005D0-Dy for mirageos-devel@lists.xenproject.org; Tue, 24 Jun 2014 14:34:53 +0000 Received: from [85.158.137.68:36148] by server-16.bemta-3.messagelabs.com id 15/5C-28986-C8C89A35; Tue, 24 Jun 2014 14:34:52 +0000 X-Env-Sender: amc79@cam.ac.uk X-Msg-Ref: server-7.tower-31.messagelabs.com!1403620491!12064863!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.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 24967 invoked from network); 24 Jun 2014 14:34:51 -0000 Received: from ppsw-52.csi.cam.ac.uk (HELO ppsw-52.csi.cam.ac.uk) (131.111.8.152) by server-7.tower-31.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 24 Jun 2014 14:34:51 -0000 X-Cam-AntiVirus: no malware found X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/ Received: from dhcp-172-17-159-208.eduroam.lapwing.private.cam.ac.uk ([172.17.159.208]:52971) 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 1WzRoB-0004ec-E4 (Exim 4.82_3-c0e5623) for mirageos-devel@lists.xenproject.org (return-path ); Tue, 24 Jun 2014 15:34:51 +0100 Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) From: Amir Chaudhry In-Reply-To: <53A989D7.6020008@somerandomidiot.com> Date: Tue, 24 Jun 2014 15:34:53 +0100 Message-Id: <85CB0755-0669-4038-AC0A-1544E49C5A79@cam.ac.uk> References: <2CC8D976-EEC1-485F-AF7B-95D556BB515C@cam.ac.uk> <53A989D7.6020008@somerandomidiot.com> To: "mirageos-devel@lists.xenproject.org" X-Mailer: Apple Mail (2.1510) Subject: Re: [MirageOS-devel] Mirage weekly call, Tuesday 23rd at 4pm BST (== GMT + 1) X-BeenThere: mirageos-devel@lists.xenproject.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, the call is at 4pm this week. Apologies for the error! Sorry we'll miss you this week, Mindy. Amir On 24 Jun 2014, at 15:23, Mindy wrote: > I won't be able to make it this week, unfortunately. :( > > -Mindy > On 06/24/2014 09:06 AM, David Scott wrote: >> I assume the meeting is at 4pm, as in the email body (and not at 4.30pm as in the subject) >> >> Shout if I'm wrong! >> >> >> On Mon, Jun 23, 2014 at 12:09 PM, Amir Chaudhry wrote: >> Dear all, >> >> The Mirage call will take place tomorrow at 4pm BST (== GMT + 1). If you have points you'd like to discuss, please add them to the agenda at https://github.com/mirage/mirage-www/wiki/Call-Agenda - I'll structure them shortly before the call. >> >> 1. Please join my meeting. >> https://www1.gotomeeting.com/join/591890401 >> >> Note the dial-in numbers seem to have changed. The new ones are visible if you join the meeting online. I don't have a full list to hand but I believe the US one is: >> >> +1 (213) 493-0008 >> >> >> Thanks, >> Amir >> _______________________________________________ >> MirageOS-devel mailing list >> MirageOS-devel@lists.xenproject.org >> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel >> >> >> >> -- >> Dave Scott >> >> >> _______________________________________________ >> 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 Jun 24 15:00:51 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 24 Jun 2014 15:00: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 1WzSDJ-0005yr-KU; Tue, 24 Jun 2014 15:00:49 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WzSDH-0005ye-Hx for mirageos-devel@lists.xenproject.org; Tue, 24 Jun 2014 15:00:47 +0000 Received: from [85.158.143.35:54703] by server-2.bemta-4.messagelabs.com id 31/32-06539-E9299A35; Tue, 24 Jun 2014 15:00:46 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-13.tower-21.messagelabs.com!1403622045!6217638!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16032 invoked from network); 24 Jun 2014 15:00:45 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-13.tower-21.messagelabs.com with SMTP; 24 Jun 2014 15:00:45 -0000 Received: (qmail 22507 invoked by uid 634); 24 Jun 2014 15:00:45 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from volstagg-0.srg.cl.cam.ac.uk (HELO flick.office) (128.232.32.232) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Tue, 24 Jun 2014 16:00:44 +0100 From: Anil Madhavapeddy Message-Id: <310551E9-D116-4544-A705-2C9844F101A5@recoil.org> Date: Tue, 24 Jun 2014 16:00:43 +0100 To: mirageos-devel@lists.xenproject.org Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\)) X-Mailer: Apple Mail (2.1874) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Subject: [MirageOS-devel] Snapshot of all mirageos repos X-BeenThere: mirageos-devel@lists.xenproject.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 to Balraj for assembling this. Are we missing any? Please reply to this thread with corrections and we can assemble: Core OS / Build Framework ------------------------- mirage/mirage - Command-line frontend mirage/mirage-platform - Core framework and runtime mirage/mirage-clock - clock for Unix and Xen mirage/mirage-types - type signatures for all Mirage modules ocaml/opam - package manager library ocaml/opamfu - functions over package sets samoht/ocaml-tools - tools to manage project configuration Persistence ----------- mirage/irmin - Distributed database with Git-like properties samoht/ocaml-git - OCaml low level git bindings mirage/ocaml-lazy-trie - Lazy trie data structure samoht/ocaml-bloom-filter - Bloom filters in OCaml mirage/orm - ORM-style relational mapper samoht/mqueue - Distributed, persistent queues Filesystems and Block Storage ------------- mirage/mirage-block-volume - Implementation of Linux LVM in OCaml mirage/mirage-block-unix - Unix mmap-based block driver for Mirage mirage/ocaml-fat - FAT format file system mirage/xen-disk - Example userspace blkback in mirage/ocaml-crunch - Convert a filesystem into a static Oaml module mirage/mirage-fs-unix - Unix filesystem passthrough dsheets/profuse - FUSE protocol implementation Network Stack ------------- mirage/mirage-tcpip - OCaml TCP/IP stack mirage/mirage-net-xen - Xen Netfront ethernet device driver mirage/mirage-net-unix - Ethernet interface using tuntap mirage/ocaml-tuntap - bindings to UNIX tuntap mirage/ocaml-ipaddr - IPv4 and IPv6 parsing and manipulation mirage/ocaml-conduit - Establish connections via multiple mechanisms mirage/ocaml-dns - DNS protocol Security -------- mirleft/ocaml-asn1-combinators - parse ASN.1 formats mirleft/ocaml-x509 - X509 (RFC5280) certificate handling mirleft/ocaml-nocrypto - libc-free crypto implementations mirleft/ocaml-tls - TLS 1.x implementation in pure OCaml dsheets/ocaml-sodium - bindings to NaCL crypto dsheets/ocaml-dnscurve - implementation of DNSCurve protocol Foreign Language Interface -------------------------- mirage/ocaml-cstruct - Map OCaml arrays to C-like structs samoht/mstruct - mutable cstruct interface ocamllabs/ocaml-ctypes - Xen support ----------- mirage/shared-memory-ring - Xen style shared memory ring mirage/io-page - IO memory page library mirage/ocaml-xenstore - Client, server and Xenstore protocol djs55/ocaml-xenstore-clients - mirage/mirage-block-xen - Xen blkfront driver for Mirage mirage/ocaml-vchan - Inter-VM shared memory communication HTTP Utilities ------------- mirage/ocaml-cohttp - Light weight HTTP server mirage/cowabloga - Zurb Foundation templates for blog/wiki mirage/ocaml-uri - URI and URL handling mirage/mirage-http - Mirage HTTP client and server mirage/ocaml-cow - Caml on the Web ocaml/omd - Markdown implementation in OCaml Misc Utilities -------------- mirage/mirage-console - Portable application console mirage/ocaml-pcap - Capture and analyse pcap files avsm/ocaml-github - GitHub API bindings mirage/dyntype - Dynamic types for OCaml Reference Applications ---------------------- mirage/mirage-www - complete openmirage.org site and server mirage/mirage-decks - Presentations written using Mirage about Mirage mirage/mirage-skeleton - Build skeleton, tests and examples Docker and Vagrant ------------------ mirage/mirage-vagrant-vms - Build Vagrant images _______________________________________________ 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 Jun 24 15:00:51 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 24 Jun 2014 15:00: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 1WzSDJ-0005yr-KU; Tue, 24 Jun 2014 15:00:49 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WzSDH-0005ye-Hx for mirageos-devel@lists.xenproject.org; Tue, 24 Jun 2014 15:00:47 +0000 Received: from [85.158.143.35:54703] by server-2.bemta-4.messagelabs.com id 31/32-06539-E9299A35; Tue, 24 Jun 2014 15:00:46 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-13.tower-21.messagelabs.com!1403622045!6217638!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16032 invoked from network); 24 Jun 2014 15:00:45 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-13.tower-21.messagelabs.com with SMTP; 24 Jun 2014 15:00:45 -0000 Received: (qmail 22507 invoked by uid 634); 24 Jun 2014 15:00:45 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from volstagg-0.srg.cl.cam.ac.uk (HELO flick.office) (128.232.32.232) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Tue, 24 Jun 2014 16:00:44 +0100 From: Anil Madhavapeddy Message-Id: <310551E9-D116-4544-A705-2C9844F101A5@recoil.org> Date: Tue, 24 Jun 2014 16:00:43 +0100 To: mirageos-devel@lists.xenproject.org Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\)) X-Mailer: Apple Mail (2.1874) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Subject: [MirageOS-devel] Snapshot of all mirageos repos X-BeenThere: mirageos-devel@lists.xenproject.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 to Balraj for assembling this. Are we missing any? Please reply to this thread with corrections and we can assemble: Core OS / Build Framework ------------------------- mirage/mirage - Command-line frontend mirage/mirage-platform - Core framework and runtime mirage/mirage-clock - clock for Unix and Xen mirage/mirage-types - type signatures for all Mirage modules ocaml/opam - package manager library ocaml/opamfu - functions over package sets samoht/ocaml-tools - tools to manage project configuration Persistence ----------- mirage/irmin - Distributed database with Git-like properties samoht/ocaml-git - OCaml low level git bindings mirage/ocaml-lazy-trie - Lazy trie data structure samoht/ocaml-bloom-filter - Bloom filters in OCaml mirage/orm - ORM-style relational mapper samoht/mqueue - Distributed, persistent queues Filesystems and Block Storage ------------- mirage/mirage-block-volume - Implementation of Linux LVM in OCaml mirage/mirage-block-unix - Unix mmap-based block driver for Mirage mirage/ocaml-fat - FAT format file system mirage/xen-disk - Example userspace blkback in mirage/ocaml-crunch - Convert a filesystem into a static Oaml module mirage/mirage-fs-unix - Unix filesystem passthrough dsheets/profuse - FUSE protocol implementation Network Stack ------------- mirage/mirage-tcpip - OCaml TCP/IP stack mirage/mirage-net-xen - Xen Netfront ethernet device driver mirage/mirage-net-unix - Ethernet interface using tuntap mirage/ocaml-tuntap - bindings to UNIX tuntap mirage/ocaml-ipaddr - IPv4 and IPv6 parsing and manipulation mirage/ocaml-conduit - Establish connections via multiple mechanisms mirage/ocaml-dns - DNS protocol Security -------- mirleft/ocaml-asn1-combinators - parse ASN.1 formats mirleft/ocaml-x509 - X509 (RFC5280) certificate handling mirleft/ocaml-nocrypto - libc-free crypto implementations mirleft/ocaml-tls - TLS 1.x implementation in pure OCaml dsheets/ocaml-sodium - bindings to NaCL crypto dsheets/ocaml-dnscurve - implementation of DNSCurve protocol Foreign Language Interface -------------------------- mirage/ocaml-cstruct - Map OCaml arrays to C-like structs samoht/mstruct - mutable cstruct interface ocamllabs/ocaml-ctypes - Xen support ----------- mirage/shared-memory-ring - Xen style shared memory ring mirage/io-page - IO memory page library mirage/ocaml-xenstore - Client, server and Xenstore protocol djs55/ocaml-xenstore-clients - mirage/mirage-block-xen - Xen blkfront driver for Mirage mirage/ocaml-vchan - Inter-VM shared memory communication HTTP Utilities ------------- mirage/ocaml-cohttp - Light weight HTTP server mirage/cowabloga - Zurb Foundation templates for blog/wiki mirage/ocaml-uri - URI and URL handling mirage/mirage-http - Mirage HTTP client and server mirage/ocaml-cow - Caml on the Web ocaml/omd - Markdown implementation in OCaml Misc Utilities -------------- mirage/mirage-console - Portable application console mirage/ocaml-pcap - Capture and analyse pcap files avsm/ocaml-github - GitHub API bindings mirage/dyntype - Dynamic types for OCaml Reference Applications ---------------------- mirage/mirage-www - complete openmirage.org site and server mirage/mirage-decks - Presentations written using Mirage about Mirage mirage/mirage-skeleton - Build skeleton, tests and examples Docker and Vagrant ------------------ mirage/mirage-vagrant-vms - Build Vagrant images _______________________________________________ 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 Jun 24 15:22:30 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 24 Jun 2014 15:22: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 1WzSYG-0006Ht-Eb; Tue, 24 Jun 2014 15:22:28 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WzSYE-0006He-Mn for mirageos-devel@lists.xenproject.org; Tue, 24 Jun 2014 15:22:26 +0000 Received: from [85.158.137.68:55802] by server-17.bemta-3.messagelabs.com id C3/89-05521-1B799A35; Tue, 24 Jun 2014 15:22:25 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-7.tower-31.messagelabs.com!1403623345!12076774!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.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6727 invoked from network); 24 Jun 2014 15:22:25 -0000 Received: from mail-wi0-f175.google.com (HELO mail-wi0-f175.google.com) (209.85.212.175) by server-7.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 24 Jun 2014 15:22:25 -0000 Received: by mail-wi0-f175.google.com with SMTP id r20so6238384wiv.2 for ; Tue, 24 Jun 2014 08:22:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:reply-to:user-agent:mime-version:to :subject:content-type:content-transfer-encoding; bh=p1ds8umxby+knLZUCtLFjcJWiXOFxLdNCBPjcvB/9rQ=; b=rBPDNBXOoPu1ZbA0AutIjGsgsxFPevYQuzfEED6S5b/IyfEr3GNqI4IxtTgD3zuL8x f17XTVDkPD2qaM/H/OwKhIy+SypA9xdBUx+4TFISKV0jQRDmRdexazvjukEM8s5g5GL7 9MnzbV+F6s1FAevPLporhs4Exxdyi/R1GbNYUKfFmhyv/xZfCxLT/9Ol+uPq93oF1vc9 avofXPhmh8tHiaBtiBkVn1dl1tlWUrfTGz/TGJcuAM+3cdPo7GkD2dhvd9MDgRHgPJpX c1KjmevDZGvdlBP8ptCFpkH3/GF5cUa0CySHQm5tcub8lABLsb0uboLzl8LB6MBh3dMm IPcw== X-Received: by 10.194.77.103 with SMTP id r7mr2119284wjw.67.1403623341786; Tue, 24 Jun 2014 08:22:21 -0700 (PDT) Received: from [172.16.25.10] (97e5a5cd.skybroadband.com. [151.229.165.205]) by mx.google.com with ESMTPSA id cx5sm1204188wjb.8.2014.06.24.08.22.20 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 24 Jun 2014 08:22:20 -0700 (PDT) Message-ID: <53A997AB.6080305@xen.org> Date: Tue, 24 Jun 2014 16:22:19 +0100 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: "xen-devel@lists.xen.org" , "xen-api@lists.xen.org" , "mirageos-devel@lists.xenproject.org" Subject: [MirageOS-devel] June Advisory Board Minutes published X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: lars.kurth@xen.org 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 http://wiki.xenproject.org/wiki/AB_Meeting/June_2014_Minutes# _______________________________________________ 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 Jun 24 15:22:30 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 24 Jun 2014 15:22: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 1WzSYG-0006Ht-Eb; Tue, 24 Jun 2014 15:22:28 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WzSYE-0006He-Mn for mirageos-devel@lists.xenproject.org; Tue, 24 Jun 2014 15:22:26 +0000 Received: from [85.158.137.68:55802] by server-17.bemta-3.messagelabs.com id C3/89-05521-1B799A35; Tue, 24 Jun 2014 15:22:25 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-7.tower-31.messagelabs.com!1403623345!12076774!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.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6727 invoked from network); 24 Jun 2014 15:22:25 -0000 Received: from mail-wi0-f175.google.com (HELO mail-wi0-f175.google.com) (209.85.212.175) by server-7.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 24 Jun 2014 15:22:25 -0000 Received: by mail-wi0-f175.google.com with SMTP id r20so6238384wiv.2 for ; Tue, 24 Jun 2014 08:22:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:reply-to:user-agent:mime-version:to :subject:content-type:content-transfer-encoding; bh=p1ds8umxby+knLZUCtLFjcJWiXOFxLdNCBPjcvB/9rQ=; b=rBPDNBXOoPu1ZbA0AutIjGsgsxFPevYQuzfEED6S5b/IyfEr3GNqI4IxtTgD3zuL8x f17XTVDkPD2qaM/H/OwKhIy+SypA9xdBUx+4TFISKV0jQRDmRdexazvjukEM8s5g5GL7 9MnzbV+F6s1FAevPLporhs4Exxdyi/R1GbNYUKfFmhyv/xZfCxLT/9Ol+uPq93oF1vc9 avofXPhmh8tHiaBtiBkVn1dl1tlWUrfTGz/TGJcuAM+3cdPo7GkD2dhvd9MDgRHgPJpX c1KjmevDZGvdlBP8ptCFpkH3/GF5cUa0CySHQm5tcub8lABLsb0uboLzl8LB6MBh3dMm IPcw== X-Received: by 10.194.77.103 with SMTP id r7mr2119284wjw.67.1403623341786; Tue, 24 Jun 2014 08:22:21 -0700 (PDT) Received: from [172.16.25.10] (97e5a5cd.skybroadband.com. [151.229.165.205]) by mx.google.com with ESMTPSA id cx5sm1204188wjb.8.2014.06.24.08.22.20 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 24 Jun 2014 08:22:20 -0700 (PDT) Message-ID: <53A997AB.6080305@xen.org> Date: Tue, 24 Jun 2014 16:22:19 +0100 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: "xen-devel@lists.xen.org" , "xen-api@lists.xen.org" , "mirageos-devel@lists.xenproject.org" Subject: [MirageOS-devel] June Advisory Board Minutes published X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: lars.kurth@xen.org 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 http://wiki.xenproject.org/wiki/AB_Meeting/June_2014_Minutes# _______________________________________________ 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 Jun 24 15:26:26 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 24 Jun 2014 15:26: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 1WzSc4-0006UT-E3; Tue, 24 Jun 2014 15:26:24 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WzSc2-0006UO-TX for mirageos-devel@lists.xenproject.org; Tue, 24 Jun 2014 15:26:23 +0000 Received: from [85.158.139.211:39130] by server-17.bemta-5.messagelabs.com id 9B/8C-08711-E9899A35; Tue, 24 Jun 2014 15:26:22 +0000 X-Env-Sender: Richard.Mortier@nottingham.ac.uk X-Msg-Ref: server-11.tower-206.messagelabs.com!1403623581!7611596!1 X-Originating-IP: [93.95.15.169] X-SpamReason: No, hits=0.3 required=7.0 tests=MAILTO_TO_SPAM_ADDR X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16804 invoked from network); 24 Jun 2014 15:26:21 -0000 Received: from engine01-20433-1.icritical.com (HELO engine01-20433-1.icritical.com) (93.95.15.169) by server-11.tower-206.messagelabs.com with SMTP; 24 Jun 2014 15:26:21 -0000 Received: (qmail 8604 invoked from network); 24 Jun 2014 15:26:16 -0000 Received: from localhost (127.0.0.1) by engine01-20433-1.icritical.com with SMTP; 24 Jun 2014 15:26:16 -0000 Received: from engine01-20433-1.icritical.com ([127.0.0.1]) by localhost (engine01-20433-1.icritical.com [127.0.0.1]) (amavisd-new, port 10024) with SMTP id 08295-07 for ; Tue, 24 Jun 2014 16:26:09 +0100 (BST) Received: (qmail 5275 invoked by uid 599); 24 Jun 2014 15:20:04 -0000 Received: from unknown (HELO smtp3.nottingham.ac.uk) (128.243.44.55) by engine01-20433-1.icritical.com (qpsmtpd/0.28) with ESMTP; Tue, 24 Jun 2014 16:20:04 +0100 Received: from uiwexhub01.ad.nottingham.ac.uk ([128.243.15.133]) by smtp3.nottingham.ac.uk with esmtps (TLSv1:AES128-SHA:128) (Exim 4.77) (envelope-from ) id 1WzSUd-0007iI-HJ for mirageos-devel@lists.xenproject.org; Tue, 24 Jun 2014 16:18:43 +0100 From: Richard Mortier To: Amir Chaudhry Date: Tue, 24 Jun 2014 16:18:39 +0100 Thread-Topic: [MirageOS-devel] Mirage weekly call, Tuesday 23rd at 4pm BST (== GMT + 1) Thread-Index: Ac+Pv5WmrF0HYq0CTmGg6FaZYAycSQ== Message-ID: <0A9B174C-858D-4EEE-A05D-D174CFF7888E@nottingham.ac.uk> References: <2CC8D976-EEC1-485F-AF7B-95D556BB515C@cam.ac.uk> <53A989D7.6020008@somerandomidiot.com> <85CB0755-0669-4038-AC0A-1544E49C5A79@cam.ac.uk> In-Reply-To: <85CB0755-0669-4038-AC0A-1544E49C5A79@cam.ac.uk> Accept-Language: en-US, en-GB Content-Language: en-US X-MS-Has-Attach: yes X-MS-TNEF-Correlator: acceptlanguage: en-US, en-GB MIME-Version: 1.0 X-Virus-Scanned: by iCritical at engine01-20433-1.icritical.com Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Mirage weekly call, Tuesday 23rd at 4pm BST (== GMT + 1) X-BeenThere: mirageos-devel@lists.xenproject.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="===============7123537148545227120==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============7123537148545227120== Content-Language: en-US Content-Type: multipart/signed; boundary="Apple-Mail=_AFC65A11-8C76-4E46-951A-52F495D348CD"; protocol="application/pgp-signature"; micalg=pgp-sha512 --Apple-Mail=_AFC65A11-8C76-4E46-951A-52F495D348CD Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii also unable - had hoped to but had to come home early due to poorly = child... On 24 Jun 2014, at 15:34, Amir Chaudhry wrote: > Yes, the call is at 4pm this week. Apologies for the error! >=20 > Sorry we'll miss you this week, Mindy. >=20 > Amir >=20 > On 24 Jun 2014, at 15:23, Mindy wrote: >=20 >> I won't be able to make it this week, unfortunately. :( >>=20 >> -Mindy >> On 06/24/2014 09:06 AM, David Scott wrote: >>> I assume the meeting is at 4pm, as in the email body (and not at = 4.30pm as in the subject) >>>=20 >>> Shout if I'm wrong! >>>=20 >>>=20 >>> On Mon, Jun 23, 2014 at 12:09 PM, Amir Chaudhry = wrote: >>> Dear all, >>>=20 >>> The Mirage call will take place tomorrow at 4pm BST (=3D=3D GMT + = 1). If you have points you'd like to discuss, please add them to the = agenda at https://github.com/mirage/mirage-www/wiki/Call-Agenda - I'll = structure them shortly before the call. >>>=20 >>> 1. Please join my meeting. >>> https://www1.gotomeeting.com/join/591890401 >>>=20 >>> Note the dial-in numbers seem to have changed. The new ones are = visible if you join the meeting online. I don't have a full list to hand = but I believe the US one is: >>>=20 >>> +1 (213) 493-0008 >>>=20 >>>=20 >>> Thanks, >>> Amir >>> _______________________________________________ >>> MirageOS-devel mailing list >>> MirageOS-devel@lists.xenproject.org >>> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel >>>=20 >>>=20 >>>=20 >>> --=20 >>> Dave Scott >>>=20 >>>=20 >>> _______________________________________________ >>> MirageOS-devel mailing list >>>=20 >>> MirageOS-devel@lists.xenproject.org >>> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel >>=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 Cheers, R. --Apple-Mail=_AFC65A11-8C76-4E46-951A-52F495D348CD Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="signature.asc" Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJTqZbQAAoJEOLF27JWwSg3k4oQAJovzbwgX6sgwMDXhqoxE7N8 RQWAByyT1sysSy9IxOK/LDR915wvOzhaB3G8cyUD4D8Z1al+29DDUE4R+Yj3zWuE f+OIt31V4FY0cYD7tLGQsqNbJsvbn8XUgSbN1yxmX82CYpLXGs6AB372LLDxCCzC IDPIKOsIGm1q84CgxQr1UnHthFwR9s80sl9qFlyy4NDEIc+zT2KFGRFOoa79JKA4 S490mTDkJ7pxSLnp6I1mKpbF2az2Ba+GORvCIVdZ5Ngrog4+CUXw0Pk/tP/ZhUHr Mwc5Y0Euc9DNyKHeSUOvm78lE832NI3FTJc2SNEsizzltLsccWUtXj9l2p8lyWrU LFrMRB5BIR/6JhrNctaZSeM0y8rr7vDHgEZ0YV/+QjJjVbah4adltCJsN7LrLraZ Q9Uykdxm7IlSv0kOTSlcS2LhlSC+QNUWsO3N66mftmyNo12Pbo0YUEVrK2HEPs8n 7e/Fol4Kd7MiIU+AZJWVoOKV2xGjdbixmaK2WdDeexQc7FrGnOKcDJSPbyfIDtQk XZ85a7asxx9lfQeE9cVdfzm2j2Uq2SwuRH1e/3iVLn0RpxQnSOIw3yx5dlD+hRUa h70npia3REYJG+2oMxtk79GpgqdOyy6cpsxOzBzEXrM94Er5BU+sjy/LCsOuJl2r NyV0BbBWJVKJ13PwEosI =6oau -----END PGP SIGNATURE----- --Apple-Mail=_AFC65A11-8C76-4E46-951A-52F495D348CD-- --===============7123537148545227120== 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 --===============7123537148545227120==-- From mirageos-devel-bounces@lists.xenproject.org Tue Jun 24 15:26:26 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 24 Jun 2014 15:26: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 1WzSc4-0006UT-E3; Tue, 24 Jun 2014 15:26:24 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WzSc2-0006UO-TX for mirageos-devel@lists.xenproject.org; Tue, 24 Jun 2014 15:26:23 +0000 Received: from [85.158.139.211:39130] by server-17.bemta-5.messagelabs.com id 9B/8C-08711-E9899A35; Tue, 24 Jun 2014 15:26:22 +0000 X-Env-Sender: Richard.Mortier@nottingham.ac.uk X-Msg-Ref: server-11.tower-206.messagelabs.com!1403623581!7611596!1 X-Originating-IP: [93.95.15.169] X-SpamReason: No, hits=0.3 required=7.0 tests=MAILTO_TO_SPAM_ADDR X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16804 invoked from network); 24 Jun 2014 15:26:21 -0000 Received: from engine01-20433-1.icritical.com (HELO engine01-20433-1.icritical.com) (93.95.15.169) by server-11.tower-206.messagelabs.com with SMTP; 24 Jun 2014 15:26:21 -0000 Received: (qmail 8604 invoked from network); 24 Jun 2014 15:26:16 -0000 Received: from localhost (127.0.0.1) by engine01-20433-1.icritical.com with SMTP; 24 Jun 2014 15:26:16 -0000 Received: from engine01-20433-1.icritical.com ([127.0.0.1]) by localhost (engine01-20433-1.icritical.com [127.0.0.1]) (amavisd-new, port 10024) with SMTP id 08295-07 for ; Tue, 24 Jun 2014 16:26:09 +0100 (BST) Received: (qmail 5275 invoked by uid 599); 24 Jun 2014 15:20:04 -0000 Received: from unknown (HELO smtp3.nottingham.ac.uk) (128.243.44.55) by engine01-20433-1.icritical.com (qpsmtpd/0.28) with ESMTP; Tue, 24 Jun 2014 16:20:04 +0100 Received: from uiwexhub01.ad.nottingham.ac.uk ([128.243.15.133]) by smtp3.nottingham.ac.uk with esmtps (TLSv1:AES128-SHA:128) (Exim 4.77) (envelope-from ) id 1WzSUd-0007iI-HJ for mirageos-devel@lists.xenproject.org; Tue, 24 Jun 2014 16:18:43 +0100 From: Richard Mortier To: Amir Chaudhry Date: Tue, 24 Jun 2014 16:18:39 +0100 Thread-Topic: [MirageOS-devel] Mirage weekly call, Tuesday 23rd at 4pm BST (== GMT + 1) Thread-Index: Ac+Pv5WmrF0HYq0CTmGg6FaZYAycSQ== Message-ID: <0A9B174C-858D-4EEE-A05D-D174CFF7888E@nottingham.ac.uk> References: <2CC8D976-EEC1-485F-AF7B-95D556BB515C@cam.ac.uk> <53A989D7.6020008@somerandomidiot.com> <85CB0755-0669-4038-AC0A-1544E49C5A79@cam.ac.uk> In-Reply-To: <85CB0755-0669-4038-AC0A-1544E49C5A79@cam.ac.uk> Accept-Language: en-US, en-GB Content-Language: en-US X-MS-Has-Attach: yes X-MS-TNEF-Correlator: acceptlanguage: en-US, en-GB MIME-Version: 1.0 X-Virus-Scanned: by iCritical at engine01-20433-1.icritical.com Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Mirage weekly call, Tuesday 23rd at 4pm BST (== GMT + 1) X-BeenThere: mirageos-devel@lists.xenproject.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="===============7123537148545227120==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============7123537148545227120== Content-Language: en-US Content-Type: multipart/signed; boundary="Apple-Mail=_AFC65A11-8C76-4E46-951A-52F495D348CD"; protocol="application/pgp-signature"; micalg=pgp-sha512 --Apple-Mail=_AFC65A11-8C76-4E46-951A-52F495D348CD Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii also unable - had hoped to but had to come home early due to poorly = child... On 24 Jun 2014, at 15:34, Amir Chaudhry wrote: > Yes, the call is at 4pm this week. Apologies for the error! >=20 > Sorry we'll miss you this week, Mindy. >=20 > Amir >=20 > On 24 Jun 2014, at 15:23, Mindy wrote: >=20 >> I won't be able to make it this week, unfortunately. :( >>=20 >> -Mindy >> On 06/24/2014 09:06 AM, David Scott wrote: >>> I assume the meeting is at 4pm, as in the email body (and not at = 4.30pm as in the subject) >>>=20 >>> Shout if I'm wrong! >>>=20 >>>=20 >>> On Mon, Jun 23, 2014 at 12:09 PM, Amir Chaudhry = wrote: >>> Dear all, >>>=20 >>> The Mirage call will take place tomorrow at 4pm BST (=3D=3D GMT + = 1). If you have points you'd like to discuss, please add them to the = agenda at https://github.com/mirage/mirage-www/wiki/Call-Agenda - I'll = structure them shortly before the call. >>>=20 >>> 1. Please join my meeting. >>> https://www1.gotomeeting.com/join/591890401 >>>=20 >>> Note the dial-in numbers seem to have changed. The new ones are = visible if you join the meeting online. I don't have a full list to hand = but I believe the US one is: >>>=20 >>> +1 (213) 493-0008 >>>=20 >>>=20 >>> Thanks, >>> Amir >>> _______________________________________________ >>> MirageOS-devel mailing list >>> MirageOS-devel@lists.xenproject.org >>> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel >>>=20 >>>=20 >>>=20 >>> --=20 >>> Dave Scott >>>=20 >>>=20 >>> _______________________________________________ >>> MirageOS-devel mailing list >>>=20 >>> MirageOS-devel@lists.xenproject.org >>> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel >>=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 Cheers, R. --Apple-Mail=_AFC65A11-8C76-4E46-951A-52F495D348CD Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="signature.asc" Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJTqZbQAAoJEOLF27JWwSg3k4oQAJovzbwgX6sgwMDXhqoxE7N8 RQWAByyT1sysSy9IxOK/LDR915wvOzhaB3G8cyUD4D8Z1al+29DDUE4R+Yj3zWuE f+OIt31V4FY0cYD7tLGQsqNbJsvbn8XUgSbN1yxmX82CYpLXGs6AB372LLDxCCzC IDPIKOsIGm1q84CgxQr1UnHthFwR9s80sl9qFlyy4NDEIc+zT2KFGRFOoa79JKA4 S490mTDkJ7pxSLnp6I1mKpbF2az2Ba+GORvCIVdZ5Ngrog4+CUXw0Pk/tP/ZhUHr Mwc5Y0Euc9DNyKHeSUOvm78lE832NI3FTJc2SNEsizzltLsccWUtXj9l2p8lyWrU LFrMRB5BIR/6JhrNctaZSeM0y8rr7vDHgEZ0YV/+QjJjVbah4adltCJsN7LrLraZ Q9Uykdxm7IlSv0kOTSlcS2LhlSC+QNUWsO3N66mftmyNo12Pbo0YUEVrK2HEPs8n 7e/Fol4Kd7MiIU+AZJWVoOKV2xGjdbixmaK2WdDeexQc7FrGnOKcDJSPbyfIDtQk XZ85a7asxx9lfQeE9cVdfzm2j2Uq2SwuRH1e/3iVLn0RpxQnSOIw3yx5dlD+hRUa h70npia3REYJG+2oMxtk79GpgqdOyy6cpsxOzBzEXrM94Er5BU+sjy/LCsOuJl2r NyV0BbBWJVKJ13PwEosI =6oau -----END PGP SIGNATURE----- --Apple-Mail=_AFC65A11-8C76-4E46-951A-52F495D348CD-- --===============7123537148545227120== 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 --===============7123537148545227120==-- From mirageos-devel-bounces@lists.xenproject.org Tue Jun 24 16:44:22 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 24 Jun 2014 16:44: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 1WzTpP-0008JU-Cn; Tue, 24 Jun 2014 16:44:15 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WzTpN-0008JP-Rh for mirageos-devel@lists.xenproject.org; Tue, 24 Jun 2014 16:44:14 +0000 Received: from [193.109.254.147:27633] by server-14.bemta-14.messagelabs.com id 63/98-08195-DDAA9A35; Tue, 24 Jun 2014 16:44:13 +0000 X-Env-Sender: hannes@mehnert.org X-Msg-Ref: server-7.tower-27.messagelabs.com!1403628252!13371010!1 X-Originating-IP: [213.73.89.200] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21403 invoked from network); 24 Jun 2014 16:44:12 -0000 Received: from mail.mehnert.org (HELO mail.mehnert.org) (213.73.89.200) by server-7.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 24 Jun 2014 16:44:12 -0000 Received: from [128.232.110.146] (c146.al.cl.cam.ac.uk [128.232.110.146]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client CN "hannes@mehnert.org", Issuer "mehnert root CA" (verified OK)) by mail.mehnert.org (Postfix) with ESMTPS id 691B62D7F for ; Tue, 24 Jun 2014 18:44:11 +0200 (CEST) Message-ID: <53A9AA91.7030706@mehnert.org> Date: Tue, 24 Jun 2014 17:42:57 +0100 From: Hannes Mehnert User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: mirageos-devel@lists.xenproject.org References: <310551E9-D116-4544-A705-2C9844F101A5@recoil.org> In-Reply-To: <310551E9-D116-4544-A705-2C9844F101A5@recoil.org> Subject: Re: [MirageOS-devel] Snapshot of all mirageos repos X-BeenThere: mirageos-devel@lists.xenproject.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 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA384 On 06/24/2014 16:00, Anil Madhavapeddy wrote: > Thanks to Balraj for assembling this. Are we missing any? Please > reply to this thread with corrections and we can assemble: > > > Core OS / Build Framework ------------------------- mirage/mirage > - Command-line frontend mirage/mirage-platform - Core framework > and runtime mirage/mirage-clock - clock for Unix and Xen > mirage/mirage-types - type signatures for all Mirage > modules - From mirage-types README: This repository is now obsolete as of Mirage 1.1.x. The latest interfaces are now tracked directly in https://github.com/mirage/mirage, in the types/ subdirectory I believe that can be removed then to avoid further confusion. Hannes -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (FreeBSD) iQIcBAEBCQAGBQJTqaqRAAoJELyJZYjffCjuMFgP/AnszkXJRRRB7HcspqZen11n bhMWEYrXn5GSSpUqoxUA69NEpDSmqbziwbLviZ7if1kx5PR4pl2x/BviV3IOa+NU 58lqqGOvrsRptQKEdMPaYnCrtw3GTqmAVWDsU4Rs4O+wAK79JEsstM6Jw8DbtIA/ 75MzdAO4vlZonFrPv8cn/VfvNfniO+g98EUTZ81szohuW7zr9M4Ris5Z3V8OW4+z JRrUe9BXBkWq+4mJHd+mTjILBztEHgFSQeF/GRdgmOQRCL0BjGGZJrpzHMWB8LcA rWRHABL1wF+4DyUvUZJiBXiE4jgp2pOA52jOvSnDTIL9FLgAcxdb+iEYw/9JStne Dfjk0hGKzZgTFH4jaTB0Cr/HRWBKV0wv4M9Dk8hjOVgzAN32Qqq+bvFHuqGgH9rw 8OrF9WFzaYiOh5rBW2doB50Xw8OrHDbDNogd14AqTlQFyHHDI1w11d9IJUApkBWA hkkAL6V0oZUDOS8y7neavgSn7SGpo9A1sk6t/gZDnY8Rgpc1D5WxbHU5g38bE85K z/rXVZD6JY5nwG5dUqWd4ghNUXmC9fn1FTfZfzWl/NEJurzeHWIo3N3Khj22hCeF t3fkagAI1y3Qab09LIGry7lG+pM+ILTn8gklrNIO8ePGWaMx67y3qy2rTk+AbML0 lLEDP61rN0BKj9X19GQZ =mDlq -----END PGP SIGNATURE----- _______________________________________________ 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 Jun 24 16:44:22 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 24 Jun 2014 16:44: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 1WzTpP-0008JU-Cn; Tue, 24 Jun 2014 16:44:15 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WzTpN-0008JP-Rh for mirageos-devel@lists.xenproject.org; Tue, 24 Jun 2014 16:44:14 +0000 Received: from [193.109.254.147:27633] by server-14.bemta-14.messagelabs.com id 63/98-08195-DDAA9A35; Tue, 24 Jun 2014 16:44:13 +0000 X-Env-Sender: hannes@mehnert.org X-Msg-Ref: server-7.tower-27.messagelabs.com!1403628252!13371010!1 X-Originating-IP: [213.73.89.200] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21403 invoked from network); 24 Jun 2014 16:44:12 -0000 Received: from mail.mehnert.org (HELO mail.mehnert.org) (213.73.89.200) by server-7.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 24 Jun 2014 16:44:12 -0000 Received: from [128.232.110.146] (c146.al.cl.cam.ac.uk [128.232.110.146]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client CN "hannes@mehnert.org", Issuer "mehnert root CA" (verified OK)) by mail.mehnert.org (Postfix) with ESMTPS id 691B62D7F for ; Tue, 24 Jun 2014 18:44:11 +0200 (CEST) Message-ID: <53A9AA91.7030706@mehnert.org> Date: Tue, 24 Jun 2014 17:42:57 +0100 From: Hannes Mehnert User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: mirageos-devel@lists.xenproject.org References: <310551E9-D116-4544-A705-2C9844F101A5@recoil.org> In-Reply-To: <310551E9-D116-4544-A705-2C9844F101A5@recoil.org> Subject: Re: [MirageOS-devel] Snapshot of all mirageos repos X-BeenThere: mirageos-devel@lists.xenproject.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 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA384 On 06/24/2014 16:00, Anil Madhavapeddy wrote: > Thanks to Balraj for assembling this. Are we missing any? Please > reply to this thread with corrections and we can assemble: > > > Core OS / Build Framework ------------------------- mirage/mirage > - Command-line frontend mirage/mirage-platform - Core framework > and runtime mirage/mirage-clock - clock for Unix and Xen > mirage/mirage-types - type signatures for all Mirage > modules - From mirage-types README: This repository is now obsolete as of Mirage 1.1.x. The latest interfaces are now tracked directly in https://github.com/mirage/mirage, in the types/ subdirectory I believe that can be removed then to avoid further confusion. Hannes -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (FreeBSD) iQIcBAEBCQAGBQJTqaqRAAoJELyJZYjffCjuMFgP/AnszkXJRRRB7HcspqZen11n bhMWEYrXn5GSSpUqoxUA69NEpDSmqbziwbLviZ7if1kx5PR4pl2x/BviV3IOa+NU 58lqqGOvrsRptQKEdMPaYnCrtw3GTqmAVWDsU4Rs4O+wAK79JEsstM6Jw8DbtIA/ 75MzdAO4vlZonFrPv8cn/VfvNfniO+g98EUTZ81szohuW7zr9M4Ris5Z3V8OW4+z JRrUe9BXBkWq+4mJHd+mTjILBztEHgFSQeF/GRdgmOQRCL0BjGGZJrpzHMWB8LcA rWRHABL1wF+4DyUvUZJiBXiE4jgp2pOA52jOvSnDTIL9FLgAcxdb+iEYw/9JStne Dfjk0hGKzZgTFH4jaTB0Cr/HRWBKV0wv4M9Dk8hjOVgzAN32Qqq+bvFHuqGgH9rw 8OrF9WFzaYiOh5rBW2doB50Xw8OrHDbDNogd14AqTlQFyHHDI1w11d9IJUApkBWA hkkAL6V0oZUDOS8y7neavgSn7SGpo9A1sk6t/gZDnY8Rgpc1D5WxbHU5g38bE85K z/rXVZD6JY5nwG5dUqWd4ghNUXmC9fn1FTfZfzWl/NEJurzeHWIo3N3Khj22hCeF t3fkagAI1y3Qab09LIGry7lG+pM+ILTn8gklrNIO8ePGWaMx67y3qy2rTk+AbML0 lLEDP61rN0BKj9X19GQZ =mDlq -----END PGP SIGNATURE----- _______________________________________________ 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 Jun 24 17:13:02 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 24 Jun 2014 17:13: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 1WzUHE-00005p-KI; Tue, 24 Jun 2014 17:13:00 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WzUHD-00005k-Hg for mirageos-devel@lists.xenproject.org; Tue, 24 Jun 2014 17:12:59 +0000 Received: from [85.158.143.35:23036] by server-2.bemta-4.messagelabs.com id B1/A4-06539-A91B9A35; Tue, 24 Jun 2014 17:12:58 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-2.tower-21.messagelabs.com!1403629977!5510775!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27970 invoked from network); 24 Jun 2014 17:12:58 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-2.tower-21.messagelabs.com with SMTP; 24 Jun 2014 17:12:58 -0000 Received: (qmail 23162 invoked by uid 634); 24 Jun 2014 17:12:57 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from volstagg-0.srg.cl.cam.ac.uk (HELO flick.office) (128.232.32.232) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Tue, 24 Jun 2014 18:12:53 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\)) From: Anil Madhavapeddy In-Reply-To: <53A9AA91.7030706@mehnert.org> Date: Tue, 24 Jun 2014 18:12:53 +0100 Message-Id: References: <310551E9-D116-4544-A705-2C9844F101A5@recoil.org> <53A9AA91.7030706@mehnert.org> To: Hannes Mehnert X-Mailer: Apple Mail (2.1874) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Snapshot of all mirageos repos X-BeenThere: mirageos-devel@lists.xenproject.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 Jun 2014, at 17:42, Hannes Mehnert wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA384 > > On 06/24/2014 16:00, Anil Madhavapeddy wrote: >> Thanks to Balraj for assembling this. Are we missing any? Please >> reply to this thread with corrections and we can assemble: >> >> >> Core OS / Build Framework ------------------------- mirage/mirage >> - Command-line frontend mirage/mirage-platform - Core framework >> and runtime mirage/mirage-clock - clock for Unix and Xen >> mirage/mirage-types - type signatures for all Mirage >> modules > > - From mirage-types README: > This repository is now obsolete as of Mirage 1.1.x. The latest > interfaces are now tracked directly in > https://github.com/mirage/mirage, in the types/ subdirectory > I believe that can be removed then to avoid further confusion. Good point -- the *opam* package is called mirage-types, but it all comes out of the mirage/mirage repository. Thanks! -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 Jun 24 17:13:02 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 24 Jun 2014 17:13: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 1WzUHE-00005p-KI; Tue, 24 Jun 2014 17:13:00 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WzUHD-00005k-Hg for mirageos-devel@lists.xenproject.org; Tue, 24 Jun 2014 17:12:59 +0000 Received: from [85.158.143.35:23036] by server-2.bemta-4.messagelabs.com id B1/A4-06539-A91B9A35; Tue, 24 Jun 2014 17:12:58 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-2.tower-21.messagelabs.com!1403629977!5510775!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27970 invoked from network); 24 Jun 2014 17:12:58 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-2.tower-21.messagelabs.com with SMTP; 24 Jun 2014 17:12:58 -0000 Received: (qmail 23162 invoked by uid 634); 24 Jun 2014 17:12:57 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from volstagg-0.srg.cl.cam.ac.uk (HELO flick.office) (128.232.32.232) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Tue, 24 Jun 2014 18:12:53 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\)) From: Anil Madhavapeddy In-Reply-To: <53A9AA91.7030706@mehnert.org> Date: Tue, 24 Jun 2014 18:12:53 +0100 Message-Id: References: <310551E9-D116-4544-A705-2C9844F101A5@recoil.org> <53A9AA91.7030706@mehnert.org> To: Hannes Mehnert X-Mailer: Apple Mail (2.1874) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Snapshot of all mirageos repos X-BeenThere: mirageos-devel@lists.xenproject.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 Jun 2014, at 17:42, Hannes Mehnert wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA384 > > On 06/24/2014 16:00, Anil Madhavapeddy wrote: >> Thanks to Balraj for assembling this. Are we missing any? Please >> reply to this thread with corrections and we can assemble: >> >> >> Core OS / Build Framework ------------------------- mirage/mirage >> - Command-line frontend mirage/mirage-platform - Core framework >> and runtime mirage/mirage-clock - clock for Unix and Xen >> mirage/mirage-types - type signatures for all Mirage >> modules > > - From mirage-types README: > This repository is now obsolete as of Mirage 1.1.x. The latest > interfaces are now tracked directly in > https://github.com/mirage/mirage, in the types/ subdirectory > I believe that can be removed then to avoid further confusion. Good point -- the *opam* package is called mirage-types, but it all comes out of the mirage/mirage repository. Thanks! -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 Jun 25 02:54:09 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 25 Jun 2014 02:54: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 1WzdLY-0004z8-CQ; Wed, 25 Jun 2014 02:54:04 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WzdLV-0004yh-8s for mirageos-devel@lists.xenproject.org; Wed, 25 Jun 2014 02:54:01 +0000 Received: from [85.158.137.68:34137] by server-10.bemta-3.messagelabs.com id 9C/AB-09305-8C93AA35; Wed, 25 Jun 2014 02:54:00 +0000 X-Env-Sender: russell.pavlicek.xen@gmail.com X-Msg-Ref: server-3.tower-31.messagelabs.com!1403664839!12212079!1 X-Originating-IP: [209.85.215.43] X-SpamReason: No, hits=2.5 required=7.0 tests=RCVD_BY_IP, SUSPICIOUS_RECIPS X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 26824 invoked from network); 25 Jun 2014 02:53:59 -0000 Received: from mail-la0-f43.google.com (HELO mail-la0-f43.google.com) (209.85.215.43) by server-3.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 25 Jun 2014 02:53:59 -0000 Received: by mail-la0-f43.google.com with SMTP id e16so283106lan.2 for ; Tue, 24 Jun 2014 19:53:59 -0700 (PDT) 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=9f0FY1eQc3vRTZWIExhL8wFAViyy9IFlE0Js7uhujCM=; b=rgzZihNcSt0+7bq3Fo6ltR/lOv1r61+ciosQIliFaBD6egOHdO4GM1WwrCGM3nnD7f Vynv41iJNs2WlPKMLS9EHmXBhuZNzM5RpC1YsZYRvFixGZudFjWJeYVvweR44ppKrPUo /5D2+YTA0oeDoiwT7s/aK6DMbIM3YKPlBwiqBG2TWdKK7kjcHhrN2mbDjhRScJ+2+itm H5TQTT6hFNXi7bEcOmnA95ToIjKuq0Tm1amqJtE68UuqKGjnYy9xO3lxC/t1WN/APo66 AFD68qSxN3z9ySlhEz/+6Ucn93KkPAnLPNtkGOGv7FDAq7H96pgekluEGOzPT8K7QumH 19QQ== MIME-Version: 1.0 X-Received: by 10.152.205.11 with SMTP id lc11mr3525866lac.46.1403664838907; Tue, 24 Jun 2014 19:53:58 -0700 (PDT) Received: by 10.112.22.39 with HTTP; Tue, 24 Jun 2014 19:53:58 -0700 (PDT) Date: Tue, 24 Jun 2014 22:53:58 -0400 X-Google-Sender-Auth: AdpQpmzaSrvto8cl7QWkWekkeM0 Message-ID: From: Russ Pavlicek To: xen-devel@lists.xen.org, "xen-users@lists.xen.org" , xen-api@lists.xen.org, xs-devel@lists.xenserver.org, mirageos-devel@lists.xenproject.org Subject: [MirageOS-devel] Today, June 25, is Xen Project Document Day X-BeenThere: mirageos-devel@lists.xenproject.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 Welcome to the June 2014 Xen Project Document Day! We have a number of things to do spelled out in the TODO list: http://wiki.xenproject.org/wiki/Xen_Document_Days/TODO But if you know of things needing attention which aren't already on the list, feel free to address them instead. This is your chance to make a difference any way you can. If you haven't participated in Document Days before, it really is easy to do. The information you need can be found here: http://wiki.xenproject.org/wiki/Xen_Document_Days And we finally have some swag available, so we can single out people who do a great job with a small thank you gift of a Xen Project T-shirt! So please think about how you can join in the action. 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 in #xendocs in Freenode IRC as we work on the docs! _______________________________________________ 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 Jun 25 02:54:09 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 25 Jun 2014 02:54: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 1WzdLY-0004z8-CQ; Wed, 25 Jun 2014 02:54:04 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WzdLV-0004yh-8s for mirageos-devel@lists.xenproject.org; Wed, 25 Jun 2014 02:54:01 +0000 Received: from [85.158.137.68:34137] by server-10.bemta-3.messagelabs.com id 9C/AB-09305-8C93AA35; Wed, 25 Jun 2014 02:54:00 +0000 X-Env-Sender: russell.pavlicek.xen@gmail.com X-Msg-Ref: server-3.tower-31.messagelabs.com!1403664839!12212079!1 X-Originating-IP: [209.85.215.43] X-SpamReason: No, hits=2.5 required=7.0 tests=RCVD_BY_IP, SUSPICIOUS_RECIPS X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 26824 invoked from network); 25 Jun 2014 02:53:59 -0000 Received: from mail-la0-f43.google.com (HELO mail-la0-f43.google.com) (209.85.215.43) by server-3.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 25 Jun 2014 02:53:59 -0000 Received: by mail-la0-f43.google.com with SMTP id e16so283106lan.2 for ; Tue, 24 Jun 2014 19:53:59 -0700 (PDT) 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=9f0FY1eQc3vRTZWIExhL8wFAViyy9IFlE0Js7uhujCM=; b=rgzZihNcSt0+7bq3Fo6ltR/lOv1r61+ciosQIliFaBD6egOHdO4GM1WwrCGM3nnD7f Vynv41iJNs2WlPKMLS9EHmXBhuZNzM5RpC1YsZYRvFixGZudFjWJeYVvweR44ppKrPUo /5D2+YTA0oeDoiwT7s/aK6DMbIM3YKPlBwiqBG2TWdKK7kjcHhrN2mbDjhRScJ+2+itm H5TQTT6hFNXi7bEcOmnA95ToIjKuq0Tm1amqJtE68UuqKGjnYy9xO3lxC/t1WN/APo66 AFD68qSxN3z9ySlhEz/+6Ucn93KkPAnLPNtkGOGv7FDAq7H96pgekluEGOzPT8K7QumH 19QQ== MIME-Version: 1.0 X-Received: by 10.152.205.11 with SMTP id lc11mr3525866lac.46.1403664838907; Tue, 24 Jun 2014 19:53:58 -0700 (PDT) Received: by 10.112.22.39 with HTTP; Tue, 24 Jun 2014 19:53:58 -0700 (PDT) Date: Tue, 24 Jun 2014 22:53:58 -0400 X-Google-Sender-Auth: AdpQpmzaSrvto8cl7QWkWekkeM0 Message-ID: From: Russ Pavlicek To: xen-devel@lists.xen.org, "xen-users@lists.xen.org" , xen-api@lists.xen.org, xs-devel@lists.xenserver.org, mirageos-devel@lists.xenproject.org Subject: [MirageOS-devel] Today, June 25, is Xen Project Document Day X-BeenThere: mirageos-devel@lists.xenproject.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 Welcome to the June 2014 Xen Project Document Day! We have a number of things to do spelled out in the TODO list: http://wiki.xenproject.org/wiki/Xen_Document_Days/TODO But if you know of things needing attention which aren't already on the list, feel free to address them instead. This is your chance to make a difference any way you can. If you haven't participated in Document Days before, it really is easy to do. The information you need can be found here: http://wiki.xenproject.org/wiki/Xen_Document_Days And we finally have some swag available, so we can single out people who do a great job with a small thank you gift of a Xen Project T-shirt! So please think about how you can join in the action. 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 in #xendocs in Freenode IRC as we work on the docs! _______________________________________________ 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 Jun 25 14:08:33 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 25 Jun 2014 14:08: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 1WznsD-0006ET-1z; Wed, 25 Jun 2014 14:08:29 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WznsB-0006EA-CS for mirageos-devel@lists.xenproject.org; Wed, 25 Jun 2014 14:08:27 +0000 Received: from [85.158.143.35:21429] by server-2.bemta-4.messagelabs.com id 87/A6-06539-AD7DAA35; Wed, 25 Jun 2014 14:08:26 +0000 X-Env-Sender: Richard.Mortier@nottingham.ac.uk X-Msg-Ref: server-12.tower-21.messagelabs.com!1403705305!13774549!1 X-Originating-IP: [93.159.202.117] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30523 invoked from network); 25 Jun 2014 14:08:25 -0000 Received: from engine03-20433-11.icritical.com (HELO engine03-20433-11.icritical.com) (93.159.202.117) by server-12.tower-21.messagelabs.com with SMTP; 25 Jun 2014 14:08:25 -0000 Received: (qmail 18171 invoked from network); 25 Jun 2014 14:08:33 -0000 Received: from localhost (127.0.0.1) by engine03-20433-11.icritical.com with SMTP; 25 Jun 2014 14:08:33 -0000 Received: from engine03-20433-11.icritical.com ([127.0.0.1]) by localhost (engine03-20433-11.icritical.com [127.0.0.1]) (amavisd-new, port 10024) with SMTP id 17478-08 for ; Wed, 25 Jun 2014 15:08:25 +0100 (BST) Received: (qmail 17640 invoked by uid 599); 25 Jun 2014 14:07:46 -0000 Received: from unknown (HELO smtp4.nottingham.ac.uk) (128.243.220.65) by engine03-20433-11.icritical.com (qpsmtpd/0.28) with ESMTP; Wed, 25 Jun 2014 15:07:46 +0100 Received: from uiwexhub01.ad.nottingham.ac.uk ([128.243.15.133]) by smtp4.nottingham.ac.uk with esmtps (TLSv1:AES128-SHA:128) (Exim 4.77) (envelope-from ) id 1WznrH-0001vw-IX; Wed, 25 Jun 2014 15:07:31 +0100 From: Richard Mortier To: Anil Madhavapeddy Date: Wed, 25 Jun 2014 15:07:30 +0100 Thread-Topic: [MirageOS-devel] towards a common Mirage 'FLOW' signature Thread-Index: Ac+Qfs2lU34LKp6RQeS19m1HpmZHIg== Message-ID: References: <1233494D-A05A-4F52-BFE7-9773BD566372@gazagnaire.org> <2C06C3FC-F8F3-4FC4-A7F9-BCD1A2FADE94@recoil.org> <62442984-A2CE-4E9E-BA14-BBFE10698B8F@recoil.org> In-Reply-To: <62442984-A2CE-4E9E-BA14-BBFE10698B8F@recoil.org> Accept-Language: en-US, en-GB Content-Language: en-US X-MS-Has-Attach: yes X-MS-TNEF-Correlator: acceptlanguage: en-US, en-GB MIME-Version: 1.0 X-Virus-Scanned: by iCritical at engine03-20433-11.icritical.com Cc: "mirageos-devel@lists.xenproject.org" , David Scott , Thomas Gazagnaire , Jonathan Ludlam Subject: Re: [MirageOS-devel] towards a common Mirage 'FLOW' signature X-BeenThere: mirageos-devel@lists.xenproject.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="===============3249317176227058288==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============3249317176227058288== Content-Language: en-US Content-Type: multipart/signed; boundary="Apple-Mail=_6BB28816-EE93-4369-BEC1-8CFC2BD117D3"; protocol="application/pgp-signature"; micalg=pgp-sha512 --Apple-Mail=_6BB28816-EE93-4369-BEC1-8CFC2BD117D3 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On 21 Jun 2014, at 16:02, Anil Madhavapeddy wrote: > On 21 Jun 2014, at 11:36, David Scott wrote: >>=20 >> I wonder whether we should extend flow to have all 4 of = {read,write}{,_ack} so that we can control when data is acked/consumed. = The TCP implementation would then only call the _ack function when it = had received confirmation the data had been processed. If the TCP = implementation needed to resend (possibly after a crash) it could call = 'read' again and get back the same data it had before. So the result of = 'read' would be an int64 stream offset * Cstruct.t, and 'read_ack' would = mark an int64 offset as being consumed. This is what I'm doing in = xenstore and shared-memory-ring: I don't know if anyone else wants this = kind of behaviour. In the case where a VM sends a block write, which is = then sent over NFS/TCP it would allow us to call write_ack on the flow = to the guest when the TCP acks are received. >=20 > Yes, this definitely makes sense. It's very nice to have a clean = async notification API for writes, as this could (for example) also = eventually bind to storage APIs like libaio for the Unix backend.=20 agree. also, in passing, wouldn't this also make it a (the first?) e2e TCP = implementation in that acks are sent after data is delivered to the = *application* rather than just received by the receiving stack... :) > However, how would NFS/TCP work with FLOW for this? That would = require a scatter/gather API (much like the RING requests/responses), = whereas FLOW works with streams. Oh, unless you are referring to a FLOW = of a single file over NFS/TCP, rather than the underlying XDR RPCs from = NFS. not sure i understand. isn't this something that the nfs/tcp = implementation handles when it passes things down? > (Perhaps we should shift to calling it Flow in e-mail instead of FLOW = to AVOID SHOUTING) PLUS ONE. >> Separately, in the case of vchan the buffer size is set at ring setup = time. If you connected a vhan ring to a TCP transmitter then the TCP = transmitter, presumably with it's higher latency link, would try to keep = its link full by buffering more. If the vchan ring size is smaller then = the TCP window size (likely), TCP would have to copy into temporary = buffers. If we knew we were going to need more buffered data then we = could make the vchan ring larger and avoid the copying? Perhaps that = wouldn't work due to alignment requirements. Anyway, this is more of a = 'flow setup' issue than a during-the-flow issue. Perhaps a CHANNEL would = be where we could close and re-open flows in order to adjust their = parameters. >=20 > This is definitely a path-MTU style problem, but the real question is = why you would be running TCP directly over vchan, which is a lossless = medium. The only use would be for congestion control, and we could = consider just cherry picking some of that logic straight out of the TCP = stack rather than suffering the overhead of marshalling into the TCP = wire format just to go over shared memory. agree; but the comment about CHANNEL makes sense to me (a Channel is an = abstraction over a set of Flows), is that right? --=20 Cheers, R. --Apple-Mail=_6BB28816-EE93-4369-BEC1-8CFC2BD117D3 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="signature.asc" Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJTqteiAAoJEOLF27JWwSg319QP/22E8zwRYk2NJFCe7JPTNat2 EnmRcRtr+Uhf2gt1Dn30zYgm4OMCs/TZmcn4Pxq3OybCzBW7dd3lGVoFSMV+1sPH DR+m37d7NXSRgX+0gGek/5pUZtftib/35EWsAyTmlqUsZNcSIBCTUei1TnnOpk1Z Xdhtsqdb01xgVl/OxVhxc/IOJ3zzgNeIO/jePyveI5DWSWQWz9bXiG/3jPmy2eOx ncoXN/ze5K6QnZAiQ9D4odWgZKzrZ5m+WOqrCUVnXwpQoo+tBjOOqPL95LmvwRu6 qLxA06VgvtMZy/H907fOwbh6FWlo/U+9oAtgzMBDu81FWE8jkf//fErEbnK+wo3o THhQmg4wtA7G/Sf1ef0zk+vOGyURwq9oH/wnoKh1cEYzRB6npehMYPCCrlI4iH+6 zHrDYN5LBtdX31AdXWja1WIvpWiyCpeXHDGpYUmRKAAuFQkgyNmIRw4Tu+1O/ige aQ2QE6URQja9kRWiHsX+0wOz7/XXKpJziqwSsMrI4ibYoWDesASXrzQHyKtwH0/d 4xAQwgQLyC5c5cLcOtryPQ9+AknEx2nllFY/Pa0P9OzCyNIxwUNvYaiC64j/ab54 Ih6oD5hfXD3gceEHgdsum45LDuUZdACZtVA22gwitrA12PEnfuh62Z+No0wN8VKq 6/utu8jl1guaTgSz0zwr =sSHF -----END PGP SIGNATURE----- --Apple-Mail=_6BB28816-EE93-4369-BEC1-8CFC2BD117D3-- --===============3249317176227058288== 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 --===============3249317176227058288==-- From mirageos-devel-bounces@lists.xenproject.org Wed Jun 25 14:08:33 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 25 Jun 2014 14:08: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 1WznsD-0006ET-1z; Wed, 25 Jun 2014 14:08:29 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WznsB-0006EA-CS for mirageos-devel@lists.xenproject.org; Wed, 25 Jun 2014 14:08:27 +0000 Received: from [85.158.143.35:21429] by server-2.bemta-4.messagelabs.com id 87/A6-06539-AD7DAA35; Wed, 25 Jun 2014 14:08:26 +0000 X-Env-Sender: Richard.Mortier@nottingham.ac.uk X-Msg-Ref: server-12.tower-21.messagelabs.com!1403705305!13774549!1 X-Originating-IP: [93.159.202.117] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30523 invoked from network); 25 Jun 2014 14:08:25 -0000 Received: from engine03-20433-11.icritical.com (HELO engine03-20433-11.icritical.com) (93.159.202.117) by server-12.tower-21.messagelabs.com with SMTP; 25 Jun 2014 14:08:25 -0000 Received: (qmail 18171 invoked from network); 25 Jun 2014 14:08:33 -0000 Received: from localhost (127.0.0.1) by engine03-20433-11.icritical.com with SMTP; 25 Jun 2014 14:08:33 -0000 Received: from engine03-20433-11.icritical.com ([127.0.0.1]) by localhost (engine03-20433-11.icritical.com [127.0.0.1]) (amavisd-new, port 10024) with SMTP id 17478-08 for ; Wed, 25 Jun 2014 15:08:25 +0100 (BST) Received: (qmail 17640 invoked by uid 599); 25 Jun 2014 14:07:46 -0000 Received: from unknown (HELO smtp4.nottingham.ac.uk) (128.243.220.65) by engine03-20433-11.icritical.com (qpsmtpd/0.28) with ESMTP; Wed, 25 Jun 2014 15:07:46 +0100 Received: from uiwexhub01.ad.nottingham.ac.uk ([128.243.15.133]) by smtp4.nottingham.ac.uk with esmtps (TLSv1:AES128-SHA:128) (Exim 4.77) (envelope-from ) id 1WznrH-0001vw-IX; Wed, 25 Jun 2014 15:07:31 +0100 From: Richard Mortier To: Anil Madhavapeddy Date: Wed, 25 Jun 2014 15:07:30 +0100 Thread-Topic: [MirageOS-devel] towards a common Mirage 'FLOW' signature Thread-Index: Ac+Qfs2lU34LKp6RQeS19m1HpmZHIg== Message-ID: References: <1233494D-A05A-4F52-BFE7-9773BD566372@gazagnaire.org> <2C06C3FC-F8F3-4FC4-A7F9-BCD1A2FADE94@recoil.org> <62442984-A2CE-4E9E-BA14-BBFE10698B8F@recoil.org> In-Reply-To: <62442984-A2CE-4E9E-BA14-BBFE10698B8F@recoil.org> Accept-Language: en-US, en-GB Content-Language: en-US X-MS-Has-Attach: yes X-MS-TNEF-Correlator: acceptlanguage: en-US, en-GB MIME-Version: 1.0 X-Virus-Scanned: by iCritical at engine03-20433-11.icritical.com Cc: "mirageos-devel@lists.xenproject.org" , David Scott , Thomas Gazagnaire , Jonathan Ludlam Subject: Re: [MirageOS-devel] towards a common Mirage 'FLOW' signature X-BeenThere: mirageos-devel@lists.xenproject.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="===============3249317176227058288==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============3249317176227058288== Content-Language: en-US Content-Type: multipart/signed; boundary="Apple-Mail=_6BB28816-EE93-4369-BEC1-8CFC2BD117D3"; protocol="application/pgp-signature"; micalg=pgp-sha512 --Apple-Mail=_6BB28816-EE93-4369-BEC1-8CFC2BD117D3 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On 21 Jun 2014, at 16:02, Anil Madhavapeddy wrote: > On 21 Jun 2014, at 11:36, David Scott wrote: >>=20 >> I wonder whether we should extend flow to have all 4 of = {read,write}{,_ack} so that we can control when data is acked/consumed. = The TCP implementation would then only call the _ack function when it = had received confirmation the data had been processed. If the TCP = implementation needed to resend (possibly after a crash) it could call = 'read' again and get back the same data it had before. So the result of = 'read' would be an int64 stream offset * Cstruct.t, and 'read_ack' would = mark an int64 offset as being consumed. This is what I'm doing in = xenstore and shared-memory-ring: I don't know if anyone else wants this = kind of behaviour. In the case where a VM sends a block write, which is = then sent over NFS/TCP it would allow us to call write_ack on the flow = to the guest when the TCP acks are received. >=20 > Yes, this definitely makes sense. It's very nice to have a clean = async notification API for writes, as this could (for example) also = eventually bind to storage APIs like libaio for the Unix backend.=20 agree. also, in passing, wouldn't this also make it a (the first?) e2e TCP = implementation in that acks are sent after data is delivered to the = *application* rather than just received by the receiving stack... :) > However, how would NFS/TCP work with FLOW for this? That would = require a scatter/gather API (much like the RING requests/responses), = whereas FLOW works with streams. Oh, unless you are referring to a FLOW = of a single file over NFS/TCP, rather than the underlying XDR RPCs from = NFS. not sure i understand. isn't this something that the nfs/tcp = implementation handles when it passes things down? > (Perhaps we should shift to calling it Flow in e-mail instead of FLOW = to AVOID SHOUTING) PLUS ONE. >> Separately, in the case of vchan the buffer size is set at ring setup = time. If you connected a vhan ring to a TCP transmitter then the TCP = transmitter, presumably with it's higher latency link, would try to keep = its link full by buffering more. If the vchan ring size is smaller then = the TCP window size (likely), TCP would have to copy into temporary = buffers. If we knew we were going to need more buffered data then we = could make the vchan ring larger and avoid the copying? Perhaps that = wouldn't work due to alignment requirements. Anyway, this is more of a = 'flow setup' issue than a during-the-flow issue. Perhaps a CHANNEL would = be where we could close and re-open flows in order to adjust their = parameters. >=20 > This is definitely a path-MTU style problem, but the real question is = why you would be running TCP directly over vchan, which is a lossless = medium. The only use would be for congestion control, and we could = consider just cherry picking some of that logic straight out of the TCP = stack rather than suffering the overhead of marshalling into the TCP = wire format just to go over shared memory. agree; but the comment about CHANNEL makes sense to me (a Channel is an = abstraction over a set of Flows), is that right? --=20 Cheers, R. --Apple-Mail=_6BB28816-EE93-4369-BEC1-8CFC2BD117D3 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="signature.asc" Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJTqteiAAoJEOLF27JWwSg319QP/22E8zwRYk2NJFCe7JPTNat2 EnmRcRtr+Uhf2gt1Dn30zYgm4OMCs/TZmcn4Pxq3OybCzBW7dd3lGVoFSMV+1sPH DR+m37d7NXSRgX+0gGek/5pUZtftib/35EWsAyTmlqUsZNcSIBCTUei1TnnOpk1Z Xdhtsqdb01xgVl/OxVhxc/IOJ3zzgNeIO/jePyveI5DWSWQWz9bXiG/3jPmy2eOx ncoXN/ze5K6QnZAiQ9D4odWgZKzrZ5m+WOqrCUVnXwpQoo+tBjOOqPL95LmvwRu6 qLxA06VgvtMZy/H907fOwbh6FWlo/U+9oAtgzMBDu81FWE8jkf//fErEbnK+wo3o THhQmg4wtA7G/Sf1ef0zk+vOGyURwq9oH/wnoKh1cEYzRB6npehMYPCCrlI4iH+6 zHrDYN5LBtdX31AdXWja1WIvpWiyCpeXHDGpYUmRKAAuFQkgyNmIRw4Tu+1O/ige aQ2QE6URQja9kRWiHsX+0wOz7/XXKpJziqwSsMrI4ibYoWDesASXrzQHyKtwH0/d 4xAQwgQLyC5c5cLcOtryPQ9+AknEx2nllFY/Pa0P9OzCyNIxwUNvYaiC64j/ab54 Ih6oD5hfXD3gceEHgdsum45LDuUZdACZtVA22gwitrA12PEnfuh62Z+No0wN8VKq 6/utu8jl1guaTgSz0zwr =sSHF -----END PGP SIGNATURE----- --Apple-Mail=_6BB28816-EE93-4369-BEC1-8CFC2BD117D3-- --===============3249317176227058288== 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 --===============3249317176227058288==-- From mirageos-devel-bounces@lists.xenproject.org Wed Jun 25 14:55:38 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 25 Jun 2014 14:55: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 1Wzobp-0008Up-C0; Wed, 25 Jun 2014 14:55:37 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Wzobn-0008UX-Jd for mirageos-devel@lists.xenproject.org; Wed, 25 Jun 2014 14:55:35 +0000 Received: from [85.158.137.68:28732] by server-17.bemta-3.messagelabs.com id 5A/1B-05521-6E2EAA35; Wed, 25 Jun 2014 14:55:34 +0000 X-Env-Sender: talex5@gmail.com X-Msg-Ref: server-9.tower-31.messagelabs.com!1403708132!8583087!1 X-Originating-IP: [209.85.219.42] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, ML_RADAR_SPEW_LINKS_23,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2255 invoked from network); 25 Jun 2014 14:55:34 -0000 Received: from mail-oa0-f42.google.com (HELO mail-oa0-f42.google.com) (209.85.219.42) by server-9.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 25 Jun 2014 14:55:34 -0000 Received: by mail-oa0-f42.google.com with SMTP id eb12so2252242oac.29 for ; Wed, 25 Jun 2014 07:55:32 -0700 (PDT) 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=mW5DGFF119/KpCWKAZO50hdS4VUGHrBlgtyc82G/U1k=; b=SdiyxpZBIOqD325kB/Vd5gpyl002cJadsueTw4pudnn8rqWkn1/n9ZcWrWMzz7NZ/m Dc2NY2ILapBkR7bc5U9c6qSuuv664bTFypwxBI697j4UvBPz1KKjffHSpyXKyX/AEaPa 5LbsKz5pYyuG/h20vxqBi9LFW2sVgRKeJkbV5XHALF4V2KK3Xyw3ycDspfGIBzlqSz9U BArLRXmyPCF4hvN7+T5l7JtaY79f/gZh77KVS0YnCCvipLMOCJds0YG23jdIAWwspOoO SN83max4weFdpGnnorvws+ZN+oOU37fXRNbis/4OGiVLgQA6UFnfmDFPkWpJuIpHFBKD Cx+Q== MIME-Version: 1.0 X-Received: by 10.182.138.65 with SMTP id qo1mr8735756obb.9.1403708132395; Wed, 25 Jun 2014 07:55:32 -0700 (PDT) Received: by 10.76.92.5 with HTTP; Wed, 25 Jun 2014 07:55:32 -0700 (PDT) Date: Wed, 25 Jun 2014 15:55:32 +0100 Message-ID: From: Thomas Leonard To: "mirageos-devel@lists.xenproject.org" Subject: [MirageOS-devel] libminios and stub_hypervisor_suspend X-BeenThere: mirageos-devel@lists.xenproject.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 started tidying up my arm-preview branch of mirage-platform. The only obvious thing missing in the new version is stub_hypervisor_suspend, which tries to call the missing arch_rebuild_p2m. Is this a Mirage-only thing? Apart from that, stub_gnttab_init and stub_gnttab_fini both now do nothing, as Mini-OS deals with mapping the grant tables. I've left them in for now - hopefully they're not needed at other times. The new-minios branch has the changes so far to upgrade to using the new libminios (without ARM support): https://github.com/talex5/mirage-platform/commits/new-minios Github won't display the diff because it's too big: 779 files changed, 1395 insertions(+), 59697 deletions(-) However, if you ignore deletions and renaming there aren't many changes. The ARM changes build on this in the arm-preview branch. Both branches need more cleanups - this is just a preview. -- 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 Jun 25 14:55:38 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 25 Jun 2014 14:55: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 1Wzobp-0008Up-C0; Wed, 25 Jun 2014 14:55:37 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Wzobn-0008UX-Jd for mirageos-devel@lists.xenproject.org; Wed, 25 Jun 2014 14:55:35 +0000 Received: from [85.158.137.68:28732] by server-17.bemta-3.messagelabs.com id 5A/1B-05521-6E2EAA35; Wed, 25 Jun 2014 14:55:34 +0000 X-Env-Sender: talex5@gmail.com X-Msg-Ref: server-9.tower-31.messagelabs.com!1403708132!8583087!1 X-Originating-IP: [209.85.219.42] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, ML_RADAR_SPEW_LINKS_23,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2255 invoked from network); 25 Jun 2014 14:55:34 -0000 Received: from mail-oa0-f42.google.com (HELO mail-oa0-f42.google.com) (209.85.219.42) by server-9.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 25 Jun 2014 14:55:34 -0000 Received: by mail-oa0-f42.google.com with SMTP id eb12so2252242oac.29 for ; Wed, 25 Jun 2014 07:55:32 -0700 (PDT) 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=mW5DGFF119/KpCWKAZO50hdS4VUGHrBlgtyc82G/U1k=; b=SdiyxpZBIOqD325kB/Vd5gpyl002cJadsueTw4pudnn8rqWkn1/n9ZcWrWMzz7NZ/m Dc2NY2ILapBkR7bc5U9c6qSuuv664bTFypwxBI697j4UvBPz1KKjffHSpyXKyX/AEaPa 5LbsKz5pYyuG/h20vxqBi9LFW2sVgRKeJkbV5XHALF4V2KK3Xyw3ycDspfGIBzlqSz9U BArLRXmyPCF4hvN7+T5l7JtaY79f/gZh77KVS0YnCCvipLMOCJds0YG23jdIAWwspOoO SN83max4weFdpGnnorvws+ZN+oOU37fXRNbis/4OGiVLgQA6UFnfmDFPkWpJuIpHFBKD Cx+Q== MIME-Version: 1.0 X-Received: by 10.182.138.65 with SMTP id qo1mr8735756obb.9.1403708132395; Wed, 25 Jun 2014 07:55:32 -0700 (PDT) Received: by 10.76.92.5 with HTTP; Wed, 25 Jun 2014 07:55:32 -0700 (PDT) Date: Wed, 25 Jun 2014 15:55:32 +0100 Message-ID: From: Thomas Leonard To: "mirageos-devel@lists.xenproject.org" Subject: [MirageOS-devel] libminios and stub_hypervisor_suspend X-BeenThere: mirageos-devel@lists.xenproject.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 started tidying up my arm-preview branch of mirage-platform. The only obvious thing missing in the new version is stub_hypervisor_suspend, which tries to call the missing arch_rebuild_p2m. Is this a Mirage-only thing? Apart from that, stub_gnttab_init and stub_gnttab_fini both now do nothing, as Mini-OS deals with mapping the grant tables. I've left them in for now - hopefully they're not needed at other times. The new-minios branch has the changes so far to upgrade to using the new libminios (without ARM support): https://github.com/talex5/mirage-platform/commits/new-minios Github won't display the diff because it's too big: 779 files changed, 1395 insertions(+), 59697 deletions(-) However, if you ignore deletions and renaming there aren't many changes. The ARM changes build on this in the arm-preview branch. Both branches need more cleanups - this is just a preview. -- 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 Jun 25 22:44:05 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 25 Jun 2014 22:44: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 1Wzvv6-00039r-4K; Wed, 25 Jun 2014 22:44:00 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Wzvv5-00039g-5P for mirageos-devel@lists.xenproject.org; Wed, 25 Jun 2014 22:43:59 +0000 Received: from [85.158.137.68:37371] by server-8.bemta-3.messagelabs.com id 7D/C8-05923-EA05BA35; Wed, 25 Jun 2014 22:43:58 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-14.tower-31.messagelabs.com!1403736237!9931679!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.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 1493 invoked from network); 25 Jun 2014 22:43:57 -0000 Received: from mail-wg0-f42.google.com (HELO mail-wg0-f42.google.com) (74.125.82.42) by server-14.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 25 Jun 2014 22:43:57 -0000 Received: by mail-wg0-f42.google.com with SMTP id z12so2731181wgg.13 for ; Wed, 25 Jun 2014 15:43:57 -0700 (PDT) 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=bcR7b5m4ch5Y1GuRga6YQnRx///pP9lzvibueqBI1Ks=; b=t3K08D3VoLHjHcV1XO+hvuLM8SZL3Bvg5k61ozBHW5BaTNYNV20npjtCiPCNlOaEkD eBKcN+dZLMRyZRTcu318iNKx9zCu+4CJA60rFj2l7/dfgWQfU+NDW5U9uKk9bwPgZmDy kPad8KzrOb0/Gc3dJtymOaIUOzcVrNC8mHKoiI8Uw8TlbERInEdAeEcB1JR3/vPJnsgR O3qxSgnWFEZNaZeinvjfqHW7UOukSAJY+LkSEwmw5l+Z48hZm2qdOQPKfXVr0evW97B2 00PaQi6uWSffzTYjaPXLVXJMt2cC0iydRqu6jOounZGEFgNmIDwOMPiccv1/eiUnyqCG yqnA== X-Received: by 10.180.198.226 with SMTP id jf2mr13502938wic.35.1403736236948; Wed, 25 Jun 2014 15:43:56 -0700 (PDT) Received: from [192.168.0.8] (cpc25-cmbg14-2-0-cust121.5-4.cable.virginm.net. [213.106.112.122]) by mx.google.com with ESMTPSA id wk8sm10259979wjb.22.2014.06.25.15.43.55 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 25 Jun 2014 15:43:56 -0700 (PDT) From: Thomas Gazagnaire Message-Id: Date: Wed, 25 Jun 2014 23:43:50 +0100 To: mirageos-devel Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\)) X-Mailer: Apple Mail (2.1878.2) Subject: [MirageOS-devel] release 0.8.3 of irmin X-BeenThere: mirageos-devel@lists.xenproject.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, I've just released in opam a new point release of Irmin (0.8.3), which was used by Dave Scott to produce an awesome video of a Xen VM booting using an Irmin-backed version of Xenstore: https://www.youtube.com/watch?v=DSzvFwIVm5s The full list of changes: * Views now keep track of their parent commits - this makes View.merge_path looks like a merge between branches. All the view operations are squashed into a unique commit. * Add View.rebase_path (same behaviour as the previous View.merge_path) * Better graphs, where we only show the commit history (the full graph is still available using `--full` on the command-lineor or `?full=1` on the web interface) * By default, do not call `dot` when dumping a graph on the command-line. `dot` does not like big graphs, but that's still useful to have the `.dot` file to analyze it. The only missing feature before the 1.0 release is the implementation of a simple GC to collect old/unreachable objects in the store. Don't expect something too clever here, but this is needed to deploy Irmin on real systems with limited resources. 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 Wed Jun 25 22:44:05 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 25 Jun 2014 22:44: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 1Wzvv6-00039r-4K; Wed, 25 Jun 2014 22:44:00 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Wzvv5-00039g-5P for mirageos-devel@lists.xenproject.org; Wed, 25 Jun 2014 22:43:59 +0000 Received: from [85.158.137.68:37371] by server-8.bemta-3.messagelabs.com id 7D/C8-05923-EA05BA35; Wed, 25 Jun 2014 22:43:58 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-14.tower-31.messagelabs.com!1403736237!9931679!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.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 1493 invoked from network); 25 Jun 2014 22:43:57 -0000 Received: from mail-wg0-f42.google.com (HELO mail-wg0-f42.google.com) (74.125.82.42) by server-14.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 25 Jun 2014 22:43:57 -0000 Received: by mail-wg0-f42.google.com with SMTP id z12so2731181wgg.13 for ; Wed, 25 Jun 2014 15:43:57 -0700 (PDT) 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=bcR7b5m4ch5Y1GuRga6YQnRx///pP9lzvibueqBI1Ks=; b=t3K08D3VoLHjHcV1XO+hvuLM8SZL3Bvg5k61ozBHW5BaTNYNV20npjtCiPCNlOaEkD eBKcN+dZLMRyZRTcu318iNKx9zCu+4CJA60rFj2l7/dfgWQfU+NDW5U9uKk9bwPgZmDy kPad8KzrOb0/Gc3dJtymOaIUOzcVrNC8mHKoiI8Uw8TlbERInEdAeEcB1JR3/vPJnsgR O3qxSgnWFEZNaZeinvjfqHW7UOukSAJY+LkSEwmw5l+Z48hZm2qdOQPKfXVr0evW97B2 00PaQi6uWSffzTYjaPXLVXJMt2cC0iydRqu6jOounZGEFgNmIDwOMPiccv1/eiUnyqCG yqnA== X-Received: by 10.180.198.226 with SMTP id jf2mr13502938wic.35.1403736236948; Wed, 25 Jun 2014 15:43:56 -0700 (PDT) Received: from [192.168.0.8] (cpc25-cmbg14-2-0-cust121.5-4.cable.virginm.net. [213.106.112.122]) by mx.google.com with ESMTPSA id wk8sm10259979wjb.22.2014.06.25.15.43.55 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 25 Jun 2014 15:43:56 -0700 (PDT) From: Thomas Gazagnaire Message-Id: Date: Wed, 25 Jun 2014 23:43:50 +0100 To: mirageos-devel Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\)) X-Mailer: Apple Mail (2.1878.2) Subject: [MirageOS-devel] release 0.8.3 of irmin X-BeenThere: mirageos-devel@lists.xenproject.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, I've just released in opam a new point release of Irmin (0.8.3), which was used by Dave Scott to produce an awesome video of a Xen VM booting using an Irmin-backed version of Xenstore: https://www.youtube.com/watch?v=DSzvFwIVm5s The full list of changes: * Views now keep track of their parent commits - this makes View.merge_path looks like a merge between branches. All the view operations are squashed into a unique commit. * Add View.rebase_path (same behaviour as the previous View.merge_path) * Better graphs, where we only show the commit history (the full graph is still available using `--full` on the command-lineor or `?full=1` on the web interface) * By default, do not call `dot` when dumping a graph on the command-line. `dot` does not like big graphs, but that's still useful to have the `.dot` file to analyze it. The only missing feature before the 1.0 release is the implementation of a simple GC to collect old/unreachable objects in the store. Don't expect something too clever here, but this is needed to deploy Irmin on real systems with limited resources. 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 Thu Jun 26 13:01:44 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 26 Jun 2014 13:01: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 1X09J6-0006Yb-FW; Thu, 26 Jun 2014 13:01:40 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1X09J5-0006YR-50 for mirageos-devel@lists.xenproject.org; Thu, 26 Jun 2014 13:01:39 +0000 Received: from [193.109.254.147:3133] by server-13.bemta-14.messagelabs.com id 0C/98-23211-2B91CA35; Thu, 26 Jun 2014 13:01:38 +0000 X-Env-Sender: talex5@gmail.com X-Msg-Ref: server-12.tower-27.messagelabs.com!1403787696!13894812!1 X-Originating-IP: [209.85.214.170] X-SpamReason: No, hits=0.8 required=7.0 tests=BODY_RANDOM_LONG, ML_RADAR_SPEW_LINKS_14, ML_RADAR_SPEW_LINKS_23, RCVD_BY_IP, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 19501 invoked from network); 26 Jun 2014 13:01:37 -0000 Received: from mail-ob0-f170.google.com (HELO mail-ob0-f170.google.com) (209.85.214.170) by server-12.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 26 Jun 2014 13:01:37 -0000 Received: by mail-ob0-f170.google.com with SMTP id uz6so3839862obc.29 for ; Thu, 26 Jun 2014 06:01:36 -0700 (PDT) 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=4BJ6DjOY8216pxp3gn7zA0PxUPAykZRE9r9eVGu9AVU=; b=0vztERHbBpDyeKgM3w4vnEZc1gXujbbR+Gr7LM2BM68CMM0wG0MYYyfsq7U70LWQRw axln04hvGtidKbR6xjxuEMUEkGpnHe+WZ1GU3i90tNUhQ5ffNVq9CNicFZ76YLUvR/oI 6KRZzNUMF3kqHgrOrHUPPwzT65AfhLGUugK9RX3tSpF9HQvvcjABt0r3IkLRQ4DPSrpR iuLz97AVahUmXq+LS3OSIK2QdbUOjBQLTg/Adh0C9wX+JeHXbzoh80/3DWPcos8EtJMQ h0c5dxbF81uqJcK0PCKQTq4PnXbqyeT8wXanEQ7fP3J1e8q9ESi8tdvcdOhcQch+mK65 geTg== MIME-Version: 1.0 X-Received: by 10.182.200.169 with SMTP id jt9mr15592842obc.0.1403787695911; Thu, 26 Jun 2014 06:01:35 -0700 (PDT) Received: by 10.76.92.5 with HTTP; Thu, 26 Jun 2014 06:01:35 -0700 (PDT) In-Reply-To: <310551E9-D116-4544-A705-2C9844F101A5@recoil.org> References: <310551E9-D116-4544-A705-2C9844F101A5@recoil.org> Date: Thu, 26 Jun 2014 14:01:35 +0100 Message-ID: From: Thomas Leonard To: Anil Madhavapeddy Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Snapshot of all mirageos repos X-BeenThere: mirageos-devel@lists.xenproject.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 June 2014 16:00, Anil Madhavapeddy wrote: > Thanks to Balraj for assembling this. Are we missing any? Please reply to this thread with corrections and we can assemble: > > > Core OS / Build Framework > ------------------------- > mirage/mirage - Command-line frontend > mirage/mirage-platform - Core framework and runtime > mirage/mirage-clock - clock for Unix and Xen > mirage/mirage-types - type signatures for all Mirage modules > ocaml/opam - package manager library > ocaml/opamfu - functions over package sets > samoht/ocaml-tools - tools to manage project configuration > > Persistence > ----------- > > mirage/irmin - Distributed database with Git-like properties > samoht/ocaml-git - OCaml low level git bindings > mirage/ocaml-lazy-trie - Lazy trie data structure > samoht/ocaml-bloom-filter - Bloom filters in OCaml > mirage/orm - ORM-style relational mapper > samoht/mqueue - Distributed, persistent queues > > > Filesystems and Block Storage > ------------- > mirage/mirage-block-volume - Implementation of Linux LVM in OCaml > mirage/mirage-block-unix - Unix mmap-based block driver for Mirage > mirage/ocaml-fat - FAT format file system > mirage/xen-disk - Example userspace blkback in > mirage/ocaml-crunch - Convert a filesystem into a static Oaml module > mirage/mirage-fs-unix - Unix filesystem passthrough > dsheets/profuse - FUSE protocol implementation > > Network Stack > ------------- > mirage/mirage-tcpip - OCaml TCP/IP stack > mirage/mirage-net-xen - Xen Netfront ethernet device driver > mirage/mirage-net-unix - Ethernet interface using tuntap > mirage/ocaml-tuntap - bindings to UNIX tuntap > mirage/ocaml-ipaddr - IPv4 and IPv6 parsing and manipulation > mirage/ocaml-conduit - Establish connections via multiple mechanisms > mirage/ocaml-dns - DNS protocol > > Security > -------- > > mirleft/ocaml-asn1-combinators - parse ASN.1 formats > mirleft/ocaml-x509 - X509 (RFC5280) certificate handling > mirleft/ocaml-nocrypto - libc-free crypto implementations > mirleft/ocaml-tls - TLS 1.x implementation in pure OCaml > dsheets/ocaml-sodium - bindings to NaCL crypto > dsheets/ocaml-dnscurve - implementation of DNSCurve protocol > > Foreign Language Interface > -------------------------- > > mirage/ocaml-cstruct - Map OCaml arrays to C-like structs > samoht/mstruct - mutable cstruct interface > ocamllabs/ocaml-ctypes - > > Xen support > ----------- > > mirage/shared-memory-ring - Xen style shared memory ring > mirage/io-page - IO memory page library > mirage/ocaml-xenstore - Client, server and Xenstore protocol > djs55/ocaml-xenstore-clients - > mirage/mirage-block-xen - Xen blkfront driver for Mirage > mirage/ocaml-vchan - Inter-VM shared memory communication > > HTTP Utilities > ------------- > mirage/ocaml-cohttp - Light weight HTTP server > mirage/cowabloga - Zurb Foundation templates for blog/wiki > mirage/ocaml-uri - URI and URL handling > mirage/mirage-http - Mirage HTTP client and server > mirage/ocaml-cow - Caml on the Web > ocaml/omd - Markdown implementation in OCaml > > Misc Utilities > -------------- > mirage/mirage-console - Portable application console > mirage/ocaml-pcap - Capture and analyse pcap files > avsm/ocaml-github - GitHub API bindings > mirage/dyntype - Dynamic types for OCaml > > > Reference Applications > ---------------------- > mirage/mirage-www - complete openmirage.org site and server > mirage/mirage-decks - Presentations written using Mirage about Mirage > mirage/mirage-skeleton - Build skeleton, tests and examples > > Docker and Vagrant > ------------------ > > mirage/mirage-vagrant-vms - Build Vagrant images You mentioned adding 0install in the telco. The repository is here: https://github.com/0install/0install It can be used to distribute Mirage Unix binaries directly, as for any other program. For Xen images, I set the arch to e.g. "Xen-x86_64" when publishing and use --os=Xen to download Xen images rather than regular binaries. What's the approved way to run an untrusted image on Xen? Obviously, you don't want to trust the Xen config file it comes with... -- 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 Jun 26 13:01:44 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 26 Jun 2014 13:01: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 1X09J6-0006Yb-FW; Thu, 26 Jun 2014 13:01:40 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1X09J5-0006YR-50 for mirageos-devel@lists.xenproject.org; Thu, 26 Jun 2014 13:01:39 +0000 Received: from [193.109.254.147:3133] by server-13.bemta-14.messagelabs.com id 0C/98-23211-2B91CA35; Thu, 26 Jun 2014 13:01:38 +0000 X-Env-Sender: talex5@gmail.com X-Msg-Ref: server-12.tower-27.messagelabs.com!1403787696!13894812!1 X-Originating-IP: [209.85.214.170] X-SpamReason: No, hits=0.8 required=7.0 tests=BODY_RANDOM_LONG, ML_RADAR_SPEW_LINKS_14, ML_RADAR_SPEW_LINKS_23, RCVD_BY_IP, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 19501 invoked from network); 26 Jun 2014 13:01:37 -0000 Received: from mail-ob0-f170.google.com (HELO mail-ob0-f170.google.com) (209.85.214.170) by server-12.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 26 Jun 2014 13:01:37 -0000 Received: by mail-ob0-f170.google.com with SMTP id uz6so3839862obc.29 for ; Thu, 26 Jun 2014 06:01:36 -0700 (PDT) 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=4BJ6DjOY8216pxp3gn7zA0PxUPAykZRE9r9eVGu9AVU=; b=0vztERHbBpDyeKgM3w4vnEZc1gXujbbR+Gr7LM2BM68CMM0wG0MYYyfsq7U70LWQRw axln04hvGtidKbR6xjxuEMUEkGpnHe+WZ1GU3i90tNUhQ5ffNVq9CNicFZ76YLUvR/oI 6KRZzNUMF3kqHgrOrHUPPwzT65AfhLGUugK9RX3tSpF9HQvvcjABt0r3IkLRQ4DPSrpR iuLz97AVahUmXq+LS3OSIK2QdbUOjBQLTg/Adh0C9wX+JeHXbzoh80/3DWPcos8EtJMQ h0c5dxbF81uqJcK0PCKQTq4PnXbqyeT8wXanEQ7fP3J1e8q9ESi8tdvcdOhcQch+mK65 geTg== MIME-Version: 1.0 X-Received: by 10.182.200.169 with SMTP id jt9mr15592842obc.0.1403787695911; Thu, 26 Jun 2014 06:01:35 -0700 (PDT) Received: by 10.76.92.5 with HTTP; Thu, 26 Jun 2014 06:01:35 -0700 (PDT) In-Reply-To: <310551E9-D116-4544-A705-2C9844F101A5@recoil.org> References: <310551E9-D116-4544-A705-2C9844F101A5@recoil.org> Date: Thu, 26 Jun 2014 14:01:35 +0100 Message-ID: From: Thomas Leonard To: Anil Madhavapeddy Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Snapshot of all mirageos repos X-BeenThere: mirageos-devel@lists.xenproject.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 June 2014 16:00, Anil Madhavapeddy wrote: > Thanks to Balraj for assembling this. Are we missing any? Please reply to this thread with corrections and we can assemble: > > > Core OS / Build Framework > ------------------------- > mirage/mirage - Command-line frontend > mirage/mirage-platform - Core framework and runtime > mirage/mirage-clock - clock for Unix and Xen > mirage/mirage-types - type signatures for all Mirage modules > ocaml/opam - package manager library > ocaml/opamfu - functions over package sets > samoht/ocaml-tools - tools to manage project configuration > > Persistence > ----------- > > mirage/irmin - Distributed database with Git-like properties > samoht/ocaml-git - OCaml low level git bindings > mirage/ocaml-lazy-trie - Lazy trie data structure > samoht/ocaml-bloom-filter - Bloom filters in OCaml > mirage/orm - ORM-style relational mapper > samoht/mqueue - Distributed, persistent queues > > > Filesystems and Block Storage > ------------- > mirage/mirage-block-volume - Implementation of Linux LVM in OCaml > mirage/mirage-block-unix - Unix mmap-based block driver for Mirage > mirage/ocaml-fat - FAT format file system > mirage/xen-disk - Example userspace blkback in > mirage/ocaml-crunch - Convert a filesystem into a static Oaml module > mirage/mirage-fs-unix - Unix filesystem passthrough > dsheets/profuse - FUSE protocol implementation > > Network Stack > ------------- > mirage/mirage-tcpip - OCaml TCP/IP stack > mirage/mirage-net-xen - Xen Netfront ethernet device driver > mirage/mirage-net-unix - Ethernet interface using tuntap > mirage/ocaml-tuntap - bindings to UNIX tuntap > mirage/ocaml-ipaddr - IPv4 and IPv6 parsing and manipulation > mirage/ocaml-conduit - Establish connections via multiple mechanisms > mirage/ocaml-dns - DNS protocol > > Security > -------- > > mirleft/ocaml-asn1-combinators - parse ASN.1 formats > mirleft/ocaml-x509 - X509 (RFC5280) certificate handling > mirleft/ocaml-nocrypto - libc-free crypto implementations > mirleft/ocaml-tls - TLS 1.x implementation in pure OCaml > dsheets/ocaml-sodium - bindings to NaCL crypto > dsheets/ocaml-dnscurve - implementation of DNSCurve protocol > > Foreign Language Interface > -------------------------- > > mirage/ocaml-cstruct - Map OCaml arrays to C-like structs > samoht/mstruct - mutable cstruct interface > ocamllabs/ocaml-ctypes - > > Xen support > ----------- > > mirage/shared-memory-ring - Xen style shared memory ring > mirage/io-page - IO memory page library > mirage/ocaml-xenstore - Client, server and Xenstore protocol > djs55/ocaml-xenstore-clients - > mirage/mirage-block-xen - Xen blkfront driver for Mirage > mirage/ocaml-vchan - Inter-VM shared memory communication > > HTTP Utilities > ------------- > mirage/ocaml-cohttp - Light weight HTTP server > mirage/cowabloga - Zurb Foundation templates for blog/wiki > mirage/ocaml-uri - URI and URL handling > mirage/mirage-http - Mirage HTTP client and server > mirage/ocaml-cow - Caml on the Web > ocaml/omd - Markdown implementation in OCaml > > Misc Utilities > -------------- > mirage/mirage-console - Portable application console > mirage/ocaml-pcap - Capture and analyse pcap files > avsm/ocaml-github - GitHub API bindings > mirage/dyntype - Dynamic types for OCaml > > > Reference Applications > ---------------------- > mirage/mirage-www - complete openmirage.org site and server > mirage/mirage-decks - Presentations written using Mirage about Mirage > mirage/mirage-skeleton - Build skeleton, tests and examples > > Docker and Vagrant > ------------------ > > mirage/mirage-vagrant-vms - Build Vagrant images You mentioned adding 0install in the telco. The repository is here: https://github.com/0install/0install It can be used to distribute Mirage Unix binaries directly, as for any other program. For Xen images, I set the arch to e.g. "Xen-x86_64" when publishing and use --os=Xen to download Xen images rather than regular binaries. What's the approved way to run an untrusted image on Xen? Obviously, you don't want to trust the Xen config file it comes with... -- 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 Fri Jun 27 13:58:44 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 27 Jun 2014 13:58: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 1X0Wfm-00064V-5R; Fri, 27 Jun 2014 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 1X0Wfk-000639-VS for mirageos-devel@lists.xenproject.org; Fri, 27 Jun 2014 13:58:37 +0000 Received: from [85.158.143.35:16778] by server-1.bemta-4.messagelabs.com id 53/22-09496-C887DA35; Fri, 27 Jun 2014 13:58:36 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-10.tower-21.messagelabs.com!1403877514!14354230!1 X-Originating-IP: [74.125.82.182] X-SpamReason: No, hits=0.6 required=7.0 tests=BODY_RANDOM_LONG, HTML_50_60,HTML_MESSAGE,ML_RADAR_SPEW_LINKS_32,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 1230 invoked from network); 27 Jun 2014 13:58:34 -0000 Received: from mail-we0-f182.google.com (HELO mail-we0-f182.google.com) (74.125.82.182) by server-10.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 27 Jun 2014 13:58:34 -0000 Received: by mail-we0-f182.google.com with SMTP id q59so5294333wes.27 for ; Fri, 27 Jun 2014 06:58:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:reply-to:user-agent:mime-version:to :subject:references:in-reply-to:content-type; bh=eRGwsHgYLI8rcO4JagRdP2Zo7hFDhy4afafzmo+NpD0=; b=ayUbx7uA5tHXt6gyLpctkPL0CoSEhrRDOR1zPEkjShD6ePeAjFoDHjgxiJjuZnEhVE wZRftcDqt5VdxltwHWm65Vm5l+SR16dPrm1CIgXHGpRVexD6Hq8zi3XhGPBGnxsCSWIP Sxg19VfaRGHRmGCxWJZLf3/wSF9P0CbstgLUGsZXHaZ3fmiay4+Wfp/DS59rdbbfw175 sz1aLbbfpgT5iYswRuRAx0/OvI3zRcS7veiEaRsS9I4gE5RDa8BjzW3T3IBQg3VXwVma 7cmfjBUa8yHn+WgsEkcsQLPIf3oaA9QIJcHt3kYUSwY2p2zhy0X35ygFuoAsguekr/u4 MN+g== X-Received: by 10.194.200.67 with SMTP id jq3mr3426388wjc.114.1403877514576; Fri, 27 Jun 2014 06:58:34 -0700 (PDT) Received: from [172.16.25.10] (97e5a5cd.skybroadband.com. [151.229.165.205]) by mx.google.com with ESMTPSA id ev9sm36802748wic.24.2014.06.27.06.58.33 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 27 Jun 2014 06:58:33 -0700 (PDT) Message-ID: <53AD7888.8030100@xen.org> Date: Fri, 27 Jun 2014 14:58:32 +0100 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: "xen-api@lists.xen.org" , "mirageos-devel@lists.xenproject.org" References: <53AD77DA.9040408@xen.org> In-Reply-To: <53AD77DA.9040408@xen.org> X-Forwarded-Message-Id: <53AD77DA.9040408@xen.org> Subject: [MirageOS-devel] Fwd: Archiving PVOPS and Xen on ARM as stand-alone subprojects X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: lars.kurth@xen.org List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============4206601849432166815==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org This is a multi-part message in MIME format. --===============4206601849432166815== Content-Type: multipart/alternative; boundary="------------080001060604040201000108" This is a multi-part message in MIME format. --------------080001060604040201000108 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Forgot to add these two lists Lars -------- Original Message -------- Subject: Archiving PVOPS and Xen on ARM as stand-alone subprojects Date: Fri, 27 Jun 2014 14:55:38 +0100 From: Lars Kurth Reply-To: lars.kurth@xen.org To: xen-devel@lists.xen.org , Stefano Stabellini , Konrad Rzeszutek Wilk Hi all, I was wondering how the community feels if we retired * http://xenproject.org/developers/teams/pvops.html * http://xenproject.org/developers/teams/arm-hypervisor.html as stand-alone subprojects of the Xen Projects in line withttp://xenproject.org/governance.html (see http://xenproject.org/governance.html - Archivation Review). I had already discussed with Stefano and Konrad and they believe this is a good idea. I have also raised the at the last Advisory Board meeting and the feedback was that this is a good idea, if we craft the messaging around this correctly as to not to cause confusion. Why Archive these subprojects? * The goal of both subprojects was to establish Xen support in Linux and ARM support in the Hypervisor in the upstream projects * This clearly has been achieved, so it is not necessary any more to keep these around as separate subprojects * Xen support is firmly established as part of Linux kernel releases * ARM support is firmly established as part of the Hypervisor What does it NOT mean? * Development of Xen in Linux would not stop - we merely treat it as part of upstream development (which is what we have de-facto today) * Development of Xen on ARM would not stop - we merely treat it as part of upstream development (which again is the de-facto status today) * We already retired separate mailing lists and PR tends to be handled as part of the upstream development. The main impact is that two xenproject.org pages would either disappear, become smaller or become merged with (or subpages) of http://xenproject.org/developers/teams/hypervisor.html What are the next step? * Consultation (this mail) * Make an archivation proposal * Formal vote * Craft a positive messaging as part of a momentum press release : the message would be that we are making progress, that our governance model works and we can tie it up with the creation of say the PV driver project. In other words, the project is evolving and addressing issues. Any views? Best Regards Lars --------------080001060604040201000108 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit
Forgot to add these two lists
Lars

-------- Original Message --------
Subject: Archiving PVOPS and Xen on ARM as stand-alone subprojects
Date: Fri, 27 Jun 2014 14:55:38 +0100
From: Lars Kurth <lars.kurth@xen.org>
Reply-To: lars.kurth@xen.org
To: xen-devel@lists.xen.org <xen-devel@lists.xen.org>, Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>, Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>


Hi all,
I was wondering how the community feels if we retired
as stand-alone subprojects of the Xen Projects in line withttp://xenproject.org/governance.html (see http://xenproject.org/governance.html - Archivation Review). I had already discussed with Stefano and Konrad and they believe this is a good idea. I have also raised the at the last Advisory Board meeting and the feedback was that this is a good idea, if we craft the messaging around this correctly as to not to cause confusion.

Why Archive these subprojects?
* The goal of both subprojects was to establish Xen support in Linux and ARM support in the Hypervisor in the upstream projects
* This clearly has been achieved, so it is not necessary any more to keep these around as separate subprojects
* Xen support is firmly established as part of Linux kernel releases
* ARM support is firmly established as part of the Hypervisor

What does it NOT mean?
* Development of Xen in Linux would not stop - we merely treat it as part of upstream development (which is what we have de-facto today)
* Development of Xen on ARM would not stop - we merely treat it as part of upstream development (which again is the de-facto status today)
* We already retired separate mailing lists and PR tends to be handled as part of the upstream development. The main impact is that two xenproject.org pages would either disappear, become smaller or become merged with (or subpages) of http://xenproject.org/developers/teams/hypervisor.html

What are the next step?
* Consultation (this mail)
* Make an archivation proposal
* Formal vote
* Craft a positive messaging as part of a momentum press release : the message would be that we are making progress, that our governance model works and we can tie it up with the creation of say the PV driver project. In other words, the project is evolving and addressing issues.

Any views?

Best Regards
Lars



--------------080001060604040201000108-- --===============4206601849432166815== 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 --===============4206601849432166815==-- From mirageos-devel-bounces@lists.xenproject.org Fri Jun 27 13:58:44 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 27 Jun 2014 13:58: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 1X0Wfm-00064V-5R; Fri, 27 Jun 2014 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 1X0Wfk-000639-VS for mirageos-devel@lists.xenproject.org; Fri, 27 Jun 2014 13:58:37 +0000 Received: from [85.158.143.35:16778] by server-1.bemta-4.messagelabs.com id 53/22-09496-C887DA35; Fri, 27 Jun 2014 13:58:36 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-10.tower-21.messagelabs.com!1403877514!14354230!1 X-Originating-IP: [74.125.82.182] X-SpamReason: No, hits=0.6 required=7.0 tests=BODY_RANDOM_LONG, HTML_50_60,HTML_MESSAGE,ML_RADAR_SPEW_LINKS_32,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 1230 invoked from network); 27 Jun 2014 13:58:34 -0000 Received: from mail-we0-f182.google.com (HELO mail-we0-f182.google.com) (74.125.82.182) by server-10.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 27 Jun 2014 13:58:34 -0000 Received: by mail-we0-f182.google.com with SMTP id q59so5294333wes.27 for ; Fri, 27 Jun 2014 06:58:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:reply-to:user-agent:mime-version:to :subject:references:in-reply-to:content-type; bh=eRGwsHgYLI8rcO4JagRdP2Zo7hFDhy4afafzmo+NpD0=; b=ayUbx7uA5tHXt6gyLpctkPL0CoSEhrRDOR1zPEkjShD6ePeAjFoDHjgxiJjuZnEhVE wZRftcDqt5VdxltwHWm65Vm5l+SR16dPrm1CIgXHGpRVexD6Hq8zi3XhGPBGnxsCSWIP Sxg19VfaRGHRmGCxWJZLf3/wSF9P0CbstgLUGsZXHaZ3fmiay4+Wfp/DS59rdbbfw175 sz1aLbbfpgT5iYswRuRAx0/OvI3zRcS7veiEaRsS9I4gE5RDa8BjzW3T3IBQg3VXwVma 7cmfjBUa8yHn+WgsEkcsQLPIf3oaA9QIJcHt3kYUSwY2p2zhy0X35ygFuoAsguekr/u4 MN+g== X-Received: by 10.194.200.67 with SMTP id jq3mr3426388wjc.114.1403877514576; Fri, 27 Jun 2014 06:58:34 -0700 (PDT) Received: from [172.16.25.10] (97e5a5cd.skybroadband.com. [151.229.165.205]) by mx.google.com with ESMTPSA id ev9sm36802748wic.24.2014.06.27.06.58.33 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 27 Jun 2014 06:58:33 -0700 (PDT) Message-ID: <53AD7888.8030100@xen.org> Date: Fri, 27 Jun 2014 14:58:32 +0100 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: "xen-api@lists.xen.org" , "mirageos-devel@lists.xenproject.org" References: <53AD77DA.9040408@xen.org> In-Reply-To: <53AD77DA.9040408@xen.org> X-Forwarded-Message-Id: <53AD77DA.9040408@xen.org> Subject: [MirageOS-devel] Fwd: Archiving PVOPS and Xen on ARM as stand-alone subprojects X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: lars.kurth@xen.org List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============4206601849432166815==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org This is a multi-part message in MIME format. --===============4206601849432166815== Content-Type: multipart/alternative; boundary="------------080001060604040201000108" This is a multi-part message in MIME format. --------------080001060604040201000108 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Forgot to add these two lists Lars -------- Original Message -------- Subject: Archiving PVOPS and Xen on ARM as stand-alone subprojects Date: Fri, 27 Jun 2014 14:55:38 +0100 From: Lars Kurth Reply-To: lars.kurth@xen.org To: xen-devel@lists.xen.org , Stefano Stabellini , Konrad Rzeszutek Wilk Hi all, I was wondering how the community feels if we retired * http://xenproject.org/developers/teams/pvops.html * http://xenproject.org/developers/teams/arm-hypervisor.html as stand-alone subprojects of the Xen Projects in line withttp://xenproject.org/governance.html (see http://xenproject.org/governance.html - Archivation Review). I had already discussed with Stefano and Konrad and they believe this is a good idea. I have also raised the at the last Advisory Board meeting and the feedback was that this is a good idea, if we craft the messaging around this correctly as to not to cause confusion. Why Archive these subprojects? * The goal of both subprojects was to establish Xen support in Linux and ARM support in the Hypervisor in the upstream projects * This clearly has been achieved, so it is not necessary any more to keep these around as separate subprojects * Xen support is firmly established as part of Linux kernel releases * ARM support is firmly established as part of the Hypervisor What does it NOT mean? * Development of Xen in Linux would not stop - we merely treat it as part of upstream development (which is what we have de-facto today) * Development of Xen on ARM would not stop - we merely treat it as part of upstream development (which again is the de-facto status today) * We already retired separate mailing lists and PR tends to be handled as part of the upstream development. The main impact is that two xenproject.org pages would either disappear, become smaller or become merged with (or subpages) of http://xenproject.org/developers/teams/hypervisor.html What are the next step? * Consultation (this mail) * Make an archivation proposal * Formal vote * Craft a positive messaging as part of a momentum press release : the message would be that we are making progress, that our governance model works and we can tie it up with the creation of say the PV driver project. In other words, the project is evolving and addressing issues. Any views? Best Regards Lars --------------080001060604040201000108 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit
Forgot to add these two lists
Lars

-------- Original Message --------
Subject: Archiving PVOPS and Xen on ARM as stand-alone subprojects
Date: Fri, 27 Jun 2014 14:55:38 +0100
From: Lars Kurth <lars.kurth@xen.org>
Reply-To: lars.kurth@xen.org
To: xen-devel@lists.xen.org <xen-devel@lists.xen.org>, Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>, Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>


Hi all,
I was wondering how the community feels if we retired
as stand-alone subprojects of the Xen Projects in line withttp://xenproject.org/governance.html (see http://xenproject.org/governance.html - Archivation Review). I had already discussed with Stefano and Konrad and they believe this is a good idea. I have also raised the at the last Advisory Board meeting and the feedback was that this is a good idea, if we craft the messaging around this correctly as to not to cause confusion.

Why Archive these subprojects?
* The goal of both subprojects was to establish Xen support in Linux and ARM support in the Hypervisor in the upstream projects
* This clearly has been achieved, so it is not necessary any more to keep these around as separate subprojects
* Xen support is firmly established as part of Linux kernel releases
* ARM support is firmly established as part of the Hypervisor

What does it NOT mean?
* Development of Xen in Linux would not stop - we merely treat it as part of upstream development (which is what we have de-facto today)
* Development of Xen on ARM would not stop - we merely treat it as part of upstream development (which again is the de-facto status today)
* We already retired separate mailing lists and PR tends to be handled as part of the upstream development. The main impact is that two xenproject.org pages would either disappear, become smaller or become merged with (or subpages) of http://xenproject.org/developers/teams/hypervisor.html

What are the next step?
* Consultation (this mail)
* Make an archivation proposal
* Formal vote
* Craft a positive messaging as part of a momentum press release : the message would be that we are making progress, that our governance model works and we can tie it up with the creation of say the PV driver project. In other words, the project is evolving and addressing issues.

Any views?

Best Regards
Lars



--------------080001060604040201000108-- --===============4206601849432166815== 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 --===============4206601849432166815==-- From mirageos-devel-bounces@lists.xenproject.org Fri Jun 27 13:59:45 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 27 Jun 2014 13:59: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 1X0Wgr-0006WW-Nm; Fri, 27 Jun 2014 13:59:45 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1X0WMl-00049l-J5 for mirageos-devel@lists.xenproject.org; Fri, 27 Jun 2014 13:38:59 +0000 Received: from [193.109.254.147:35831] by server-16.bemta-14.messagelabs.com id 53/13-16986-2F37DA35; Fri, 27 Jun 2014 13:38:58 +0000 X-Env-Sender: kosmo.zb@gmail.com X-Msg-Ref: server-6.tower-27.messagelabs.com!1403876337!14122378!1 X-Originating-IP: [209.85.215.49] X-SpamReason: No, hits=0.8 required=7.0 tests=BODY_RANDOM_LONG, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 9201 invoked from network); 27 Jun 2014 13:38:58 -0000 Received: from mail-la0-f49.google.com (HELO mail-la0-f49.google.com) (209.85.215.49) by server-6.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 27 Jun 2014 13:38:58 -0000 Received: by mail-la0-f49.google.com with SMTP id gf5so2926509lab.22 for ; Fri, 27 Jun 2014 06:38:57 -0700 (PDT) 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=Im+KM370PxJDfjby8svFrGfKKr2CcA9UcrCdXJFCcBM=; b=JwzSgJwG4ewGkxY6Y7k2L/Y6BcE5F8/0nSTXvg4oe/MRo48TNRY0ARybWZ2qve+tvZ Gb8G41RGBuSAORedeVnO8xrJ0ghQ5A4m02nJZL1EW65ew/ej8o1wESIQaGzKj2AE46aG tl+O/RKsWgCUsedIqz1bBP6mkCs2uIZvE5ADPtzvgluachXBgvhwgfltccruuRJVpXtA cFDu+T0mEOPTxlEMucC493secQwFN48JZFXhV+tLzeugiE9DrtgyLxampF44EFEOeMtD x/+8zEDMlHrmnQZwrqE4diKSHjXLjd3nJN5BV5u7wd7wIiXvB06vnHVCxfdYsCqP8lp7 hl3w== MIME-Version: 1.0 X-Received: by 10.112.180.70 with SMTP id dm6mr6727471lbc.32.1403876336962; Fri, 27 Jun 2014 06:38:56 -0700 (PDT) Received: by 10.112.133.226 with HTTP; Fri, 27 Jun 2014 06:38:56 -0700 (PDT) In-Reply-To: <310551E9-D116-4544-A705-2C9844F101A5@recoil.org> References: <310551E9-D116-4544-A705-2C9844F101A5@recoil.org> Date: Fri, 27 Jun 2014 14:38:56 +0100 Message-ID: From: David Sheets To: Anil Madhavapeddy X-Mailman-Approved-At: Fri, 27 Jun 2014 13:59:44 +0000 Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Snapshot of all mirageos repos X-BeenThere: mirageos-devel@lists.xenproject.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 Tue, Jun 24, 2014 at 4:00 PM, Anil Madhavapeddy wrote: > Thanks to Balraj for assembling this. Are we missing any? Please reply to this thread with corrections and we can assemble: profuse depends on ocaml-unix-errno, ocaml-unix-dirent, ocaml-unix-sys-stat, ocaml-unix-unistd, and ocaml-unix-fcntl for host-specific libc macro codecs. They will soon undergo fairly major refactoring to make them cleaner and more Mirage-friendly. Neither they nor profuse has been released but will likely be cut later this summer. I don't know if you count these libraries as Mirage libraries but they do offer a way to achieve compatibility with UNIX-like systems that expect client and server to share a common set of CPP macro definitions. Do as you will. David > Core OS / Build Framework > ------------------------- > mirage/mirage - Command-line frontend > mirage/mirage-platform - Core framework and runtime > mirage/mirage-clock - clock for Unix and Xen > mirage/mirage-types - type signatures for all Mirage modules > ocaml/opam - package manager library > ocaml/opamfu - functions over package sets > samoht/ocaml-tools - tools to manage project configuration > > Persistence > ----------- > > mirage/irmin - Distributed database with Git-like properties > samoht/ocaml-git - OCaml low level git bindings > mirage/ocaml-lazy-trie - Lazy trie data structure > samoht/ocaml-bloom-filter - Bloom filters in OCaml > mirage/orm - ORM-style relational mapper > samoht/mqueue - Distributed, persistent queues > > > Filesystems and Block Storage > ------------- > mirage/mirage-block-volume - Implementation of Linux LVM in OCaml > mirage/mirage-block-unix - Unix mmap-based block driver for Mirage > mirage/ocaml-fat - FAT format file system > mirage/xen-disk - Example userspace blkback in > mirage/ocaml-crunch - Convert a filesystem into a static Oaml module > mirage/mirage-fs-unix - Unix filesystem passthrough > dsheets/profuse - FUSE protocol implementation > > Network Stack > ------------- > mirage/mirage-tcpip - OCaml TCP/IP stack > mirage/mirage-net-xen - Xen Netfront ethernet device driver > mirage/mirage-net-unix - Ethernet interface using tuntap > mirage/ocaml-tuntap - bindings to UNIX tuntap > mirage/ocaml-ipaddr - IPv4 and IPv6 parsing and manipulation > mirage/ocaml-conduit - Establish connections via multiple mechanisms > mirage/ocaml-dns - DNS protocol > > Security > -------- > > mirleft/ocaml-asn1-combinators - parse ASN.1 formats > mirleft/ocaml-x509 - X509 (RFC5280) certificate handling > mirleft/ocaml-nocrypto - libc-free crypto implementations > mirleft/ocaml-tls - TLS 1.x implementation in pure OCaml > dsheets/ocaml-sodium - bindings to NaCL crypto > dsheets/ocaml-dnscurve - implementation of DNSCurve protocol > > Foreign Language Interface > -------------------------- > > mirage/ocaml-cstruct - Map OCaml arrays to C-like structs > samoht/mstruct - mutable cstruct interface > ocamllabs/ocaml-ctypes - > > Xen support > ----------- > > mirage/shared-memory-ring - Xen style shared memory ring > mirage/io-page - IO memory page library > mirage/ocaml-xenstore - Client, server and Xenstore protocol > djs55/ocaml-xenstore-clients - > mirage/mirage-block-xen - Xen blkfront driver for Mirage > mirage/ocaml-vchan - Inter-VM shared memory communication > > HTTP Utilities > ------------- > mirage/ocaml-cohttp - Light weight HTTP server > mirage/cowabloga - Zurb Foundation templates for blog/wiki > mirage/ocaml-uri - URI and URL handling > mirage/mirage-http - Mirage HTTP client and server > mirage/ocaml-cow - Caml on the Web > ocaml/omd - Markdown implementation in OCaml > > Misc Utilities > -------------- > mirage/mirage-console - Portable application console > mirage/ocaml-pcap - Capture and analyse pcap files > avsm/ocaml-github - GitHub API bindings > mirage/dyntype - Dynamic types for OCaml > > > Reference Applications > ---------------------- > mirage/mirage-www - complete openmirage.org site and server > mirage/mirage-decks - Presentations written using Mirage about Mirage > mirage/mirage-skeleton - Build skeleton, tests and examples > > Docker and Vagrant > ------------------ > > mirage/mirage-vagrant-vms - Build Vagrant images > > > > > _______________________________________________ > 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 Jun 27 13:59:45 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 27 Jun 2014 13:59: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 1X0Wgr-0006WW-Nm; Fri, 27 Jun 2014 13:59:45 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1X0WMl-00049l-J5 for mirageos-devel@lists.xenproject.org; Fri, 27 Jun 2014 13:38:59 +0000 Received: from [193.109.254.147:35831] by server-16.bemta-14.messagelabs.com id 53/13-16986-2F37DA35; Fri, 27 Jun 2014 13:38:58 +0000 X-Env-Sender: kosmo.zb@gmail.com X-Msg-Ref: server-6.tower-27.messagelabs.com!1403876337!14122378!1 X-Originating-IP: [209.85.215.49] X-SpamReason: No, hits=0.8 required=7.0 tests=BODY_RANDOM_LONG, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 9201 invoked from network); 27 Jun 2014 13:38:58 -0000 Received: from mail-la0-f49.google.com (HELO mail-la0-f49.google.com) (209.85.215.49) by server-6.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 27 Jun 2014 13:38:58 -0000 Received: by mail-la0-f49.google.com with SMTP id gf5so2926509lab.22 for ; Fri, 27 Jun 2014 06:38:57 -0700 (PDT) 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=Im+KM370PxJDfjby8svFrGfKKr2CcA9UcrCdXJFCcBM=; b=JwzSgJwG4ewGkxY6Y7k2L/Y6BcE5F8/0nSTXvg4oe/MRo48TNRY0ARybWZ2qve+tvZ Gb8G41RGBuSAORedeVnO8xrJ0ghQ5A4m02nJZL1EW65ew/ej8o1wESIQaGzKj2AE46aG tl+O/RKsWgCUsedIqz1bBP6mkCs2uIZvE5ADPtzvgluachXBgvhwgfltccruuRJVpXtA cFDu+T0mEOPTxlEMucC493secQwFN48JZFXhV+tLzeugiE9DrtgyLxampF44EFEOeMtD x/+8zEDMlHrmnQZwrqE4diKSHjXLjd3nJN5BV5u7wd7wIiXvB06vnHVCxfdYsCqP8lp7 hl3w== MIME-Version: 1.0 X-Received: by 10.112.180.70 with SMTP id dm6mr6727471lbc.32.1403876336962; Fri, 27 Jun 2014 06:38:56 -0700 (PDT) Received: by 10.112.133.226 with HTTP; Fri, 27 Jun 2014 06:38:56 -0700 (PDT) In-Reply-To: <310551E9-D116-4544-A705-2C9844F101A5@recoil.org> References: <310551E9-D116-4544-A705-2C9844F101A5@recoil.org> Date: Fri, 27 Jun 2014 14:38:56 +0100 Message-ID: From: David Sheets To: Anil Madhavapeddy X-Mailman-Approved-At: Fri, 27 Jun 2014 13:59:44 +0000 Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Snapshot of all mirageos repos X-BeenThere: mirageos-devel@lists.xenproject.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 Tue, Jun 24, 2014 at 4:00 PM, Anil Madhavapeddy wrote: > Thanks to Balraj for assembling this. Are we missing any? Please reply to this thread with corrections and we can assemble: profuse depends on ocaml-unix-errno, ocaml-unix-dirent, ocaml-unix-sys-stat, ocaml-unix-unistd, and ocaml-unix-fcntl for host-specific libc macro codecs. They will soon undergo fairly major refactoring to make them cleaner and more Mirage-friendly. Neither they nor profuse has been released but will likely be cut later this summer. I don't know if you count these libraries as Mirage libraries but they do offer a way to achieve compatibility with UNIX-like systems that expect client and server to share a common set of CPP macro definitions. Do as you will. David > Core OS / Build Framework > ------------------------- > mirage/mirage - Command-line frontend > mirage/mirage-platform - Core framework and runtime > mirage/mirage-clock - clock for Unix and Xen > mirage/mirage-types - type signatures for all Mirage modules > ocaml/opam - package manager library > ocaml/opamfu - functions over package sets > samoht/ocaml-tools - tools to manage project configuration > > Persistence > ----------- > > mirage/irmin - Distributed database with Git-like properties > samoht/ocaml-git - OCaml low level git bindings > mirage/ocaml-lazy-trie - Lazy trie data structure > samoht/ocaml-bloom-filter - Bloom filters in OCaml > mirage/orm - ORM-style relational mapper > samoht/mqueue - Distributed, persistent queues > > > Filesystems and Block Storage > ------------- > mirage/mirage-block-volume - Implementation of Linux LVM in OCaml > mirage/mirage-block-unix - Unix mmap-based block driver for Mirage > mirage/ocaml-fat - FAT format file system > mirage/xen-disk - Example userspace blkback in > mirage/ocaml-crunch - Convert a filesystem into a static Oaml module > mirage/mirage-fs-unix - Unix filesystem passthrough > dsheets/profuse - FUSE protocol implementation > > Network Stack > ------------- > mirage/mirage-tcpip - OCaml TCP/IP stack > mirage/mirage-net-xen - Xen Netfront ethernet device driver > mirage/mirage-net-unix - Ethernet interface using tuntap > mirage/ocaml-tuntap - bindings to UNIX tuntap > mirage/ocaml-ipaddr - IPv4 and IPv6 parsing and manipulation > mirage/ocaml-conduit - Establish connections via multiple mechanisms > mirage/ocaml-dns - DNS protocol > > Security > -------- > > mirleft/ocaml-asn1-combinators - parse ASN.1 formats > mirleft/ocaml-x509 - X509 (RFC5280) certificate handling > mirleft/ocaml-nocrypto - libc-free crypto implementations > mirleft/ocaml-tls - TLS 1.x implementation in pure OCaml > dsheets/ocaml-sodium - bindings to NaCL crypto > dsheets/ocaml-dnscurve - implementation of DNSCurve protocol > > Foreign Language Interface > -------------------------- > > mirage/ocaml-cstruct - Map OCaml arrays to C-like structs > samoht/mstruct - mutable cstruct interface > ocamllabs/ocaml-ctypes - > > Xen support > ----------- > > mirage/shared-memory-ring - Xen style shared memory ring > mirage/io-page - IO memory page library > mirage/ocaml-xenstore - Client, server and Xenstore protocol > djs55/ocaml-xenstore-clients - > mirage/mirage-block-xen - Xen blkfront driver for Mirage > mirage/ocaml-vchan - Inter-VM shared memory communication > > HTTP Utilities > ------------- > mirage/ocaml-cohttp - Light weight HTTP server > mirage/cowabloga - Zurb Foundation templates for blog/wiki > mirage/ocaml-uri - URI and URL handling > mirage/mirage-http - Mirage HTTP client and server > mirage/ocaml-cow - Caml on the Web > ocaml/omd - Markdown implementation in OCaml > > Misc Utilities > -------------- > mirage/mirage-console - Portable application console > mirage/ocaml-pcap - Capture and analyse pcap files > avsm/ocaml-github - GitHub API bindings > mirage/dyntype - Dynamic types for OCaml > > > Reference Applications > ---------------------- > mirage/mirage-www - complete openmirage.org site and server > mirage/mirage-decks - Presentations written using Mirage about Mirage > mirage/mirage-skeleton - Build skeleton, tests and examples > > Docker and Vagrant > ------------------ > > mirage/mirage-vagrant-vms - Build Vagrant images > > > > > _______________________________________________ > 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 Jun 30 08:29:58 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 30 Jun 2014 08:29: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 1X1WyG-0001oe-Nj; Mon, 30 Jun 2014 08:29:52 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1X1WyF-0001oT-Mr for mirageos-devel@lists.xenproject.org; Mon, 30 Jun 2014 08:29:51 +0000 Received: from [85.158.137.68:59469] by server-3.bemta-3.messagelabs.com id 9E/63-12895-EFF11B35; Mon, 30 Jun 2014 08:29:50 +0000 X-Env-Sender: mmatalka@gmail.com X-Msg-Ref: server-6.tower-31.messagelabs.com!1404116990!8592526!1 X-Originating-IP: [74.125.82.51] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16651 invoked from network); 30 Jun 2014 08:29:50 -0000 Received: from mail-wg0-f51.google.com (HELO mail-wg0-f51.google.com) (74.125.82.51) by server-6.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 30 Jun 2014 08:29:50 -0000 Received: by mail-wg0-f51.google.com with SMTP id x12so7603451wgg.22 for ; Mon, 30 Jun 2014 01:29:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:subject:date:message-id:user-agent:mime-version :content-type; bh=CjVl77qcS9ejX7tErCzbmbsw+yVaoEqm6ZxJ/jbxaeY=; b=OT2pTyFnD78/LVzENcE0A8+DRfwDxLg9JehVewh7nAiW2Zinia32xH+YcjgAsnN3kC EWH8TcC8bFs6n0bks6UqNxpOT8pJVwJcSsgqmzGGys/su5hosEGmQhbZ8YZVgI6jjclV exVhdMkinM9gtnTM2Y9BE4gy3dqC/orFmkwi00Hh8uiBeym2n3NE7nO+wduce4xXVtzG 5AwL/9s2xUUyrMW1ELfhU1gAPd9lAc4gaMJ08N9GLMl6PCGnY2gkXqiCon8ELzLzoyhG uO+VMtBoczTSjttmMA8bii8+5xC4RUhEprk7wccWHzVeIwH4LWu0652aPkf4XPiObH4Q cK0A== X-Received: by 10.180.89.69 with SMTP id bm5mr27918204wib.41.1404116989669; Mon, 30 Jun 2014 01:29:49 -0700 (PDT) Received: from localhost ([2a01:7e00::f03c:91ff:fe70:2696]) by mx.google.com with ESMTPSA id w5sm28836459wif.3.2014.06.30.01.29.48 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 30 Jun 2014 01:29:49 -0700 (PDT) From: Malcolm Matalka To: mirageos-devel@lists.xenproject.org Date: Mon, 30 Jun 2014 08:29:48 +0000 Message-ID: <87fvimpzpf.fsf@gmail.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) MIME-Version: 1.0 Subject: [MirageOS-devel] Whole Program Optimization in 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've seen it mentioned a few times that Mirage does WPO. Is there documentation on what exactly this means? I am under the impression that the ocaml compiler does not do whole program optimization. Thanks, /M _______________________________________________ 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 Jun 30 08:29:58 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 30 Jun 2014 08:29: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 1X1WyG-0001oe-Nj; Mon, 30 Jun 2014 08:29:52 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1X1WyF-0001oT-Mr for mirageos-devel@lists.xenproject.org; Mon, 30 Jun 2014 08:29:51 +0000 Received: from [85.158.137.68:59469] by server-3.bemta-3.messagelabs.com id 9E/63-12895-EFF11B35; Mon, 30 Jun 2014 08:29:50 +0000 X-Env-Sender: mmatalka@gmail.com X-Msg-Ref: server-6.tower-31.messagelabs.com!1404116990!8592526!1 X-Originating-IP: [74.125.82.51] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16651 invoked from network); 30 Jun 2014 08:29:50 -0000 Received: from mail-wg0-f51.google.com (HELO mail-wg0-f51.google.com) (74.125.82.51) by server-6.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 30 Jun 2014 08:29:50 -0000 Received: by mail-wg0-f51.google.com with SMTP id x12so7603451wgg.22 for ; Mon, 30 Jun 2014 01:29:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:subject:date:message-id:user-agent:mime-version :content-type; bh=CjVl77qcS9ejX7tErCzbmbsw+yVaoEqm6ZxJ/jbxaeY=; b=OT2pTyFnD78/LVzENcE0A8+DRfwDxLg9JehVewh7nAiW2Zinia32xH+YcjgAsnN3kC EWH8TcC8bFs6n0bks6UqNxpOT8pJVwJcSsgqmzGGys/su5hosEGmQhbZ8YZVgI6jjclV exVhdMkinM9gtnTM2Y9BE4gy3dqC/orFmkwi00Hh8uiBeym2n3NE7nO+wduce4xXVtzG 5AwL/9s2xUUyrMW1ELfhU1gAPd9lAc4gaMJ08N9GLMl6PCGnY2gkXqiCon8ELzLzoyhG uO+VMtBoczTSjttmMA8bii8+5xC4RUhEprk7wccWHzVeIwH4LWu0652aPkf4XPiObH4Q cK0A== X-Received: by 10.180.89.69 with SMTP id bm5mr27918204wib.41.1404116989669; Mon, 30 Jun 2014 01:29:49 -0700 (PDT) Received: from localhost ([2a01:7e00::f03c:91ff:fe70:2696]) by mx.google.com with ESMTPSA id w5sm28836459wif.3.2014.06.30.01.29.48 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 30 Jun 2014 01:29:49 -0700 (PDT) From: Malcolm Matalka To: mirageos-devel@lists.xenproject.org Date: Mon, 30 Jun 2014 08:29:48 +0000 Message-ID: <87fvimpzpf.fsf@gmail.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) MIME-Version: 1.0 Subject: [MirageOS-devel] Whole Program Optimization in 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've seen it mentioned a few times that Mirage does WPO. Is there documentation on what exactly this means? I am under the impression that the ocaml compiler does not do whole program optimization. Thanks, /M _______________________________________________ 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 Jun 30 13:53:41 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 30 Jun 2014 13:53: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 1X1c1Y-0000QQ-KK; Mon, 30 Jun 2014 13:53:36 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1X1c1X-0000QL-Bi for mirageos-devel@lists.xenproject.org; Mon, 30 Jun 2014 13:53:35 +0000 Received: from [85.158.139.211:25590] by server-9.bemta-5.messagelabs.com id 80/3C-14363-EDB61B35; Mon, 30 Jun 2014 13:53:34 +0000 X-Env-Sender: goswin-v-b@web.de X-Msg-Ref: server-10.tower-206.messagelabs.com!1404136414!7469545!1 X-Originating-IP: [212.227.17.12] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: QmFkIElQOiAyMTIuMjI3LjE3LjEyID0+IDEzODM5\n,sa_preprocessor: QmFkIElQOiAyMTIuMjI3LjE3LjEyID0+IDEzODM5\n X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27731 invoked from network); 30 Jun 2014 13:53:34 -0000 Received: from mout.web.de (HELO mout.web.de) (212.227.17.12) by server-10.tower-206.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 30 Jun 2014 13:53:34 -0000 Received: from frosties.localnet ([78.43.112.61]) by smtp.web.de (mrweb101) with ESMTPSA (Nemesis) id 0MYNrh-1X5eLk3AQL-00V91q for ; Mon, 30 Jun 2014 15:53:33 +0200 Received: from mrvn by frosties.localnet with local (Exim 4.82) (envelope-from ) id 1X1c1U-00062c-QK for mirageos-devel@lists.xenproject.org; Mon, 30 Jun 2014 15:53:32 +0200 Date: Mon, 30 Jun 2014 15:53:32 +0200 From: Goswin von Brederlow To: mirageos-devel@lists.xenproject.org Message-ID: <20140630135332.GA23123@frosties> References: <87fvimpzpf.fsf@gmail.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <87fvimpzpf.fsf@gmail.com> User-Agent: Mutt/1.5.23 (2014-03-12) X-Provags-ID: V03:K0:JYkdm++EH5YYQ18Dh/GsrJqpNZLH0bD1pI9BROKS1zKgxd8pCdV aSTBkfd9tsC1Wffp/zyl08vO0Djh/Y5yG78yV1JC+2vUr/a+HcmGTI/pGPph2bH0rATqKd7 52RafztZ7yxnAw4oYuJo5x+uMb1+ZaAU4wGMsXKFNI40OQnb8Ihpw4xzIruFI8iQX9BgxY6 D2P3zgI9fDm8jTXBE8I/g== Subject: Re: [MirageOS-devel] Whole Program Optimization in 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 Mon, Jun 30, 2014 at 08:29:48AM +0000, Malcolm Matalka wrote: > I've seen it mentioned a few times that Mirage does WPO. Is there > documentation on what exactly this means? I am under the impression > that the ocaml compiler does not do whole program optimization. > > Thanks, > /M The ocaml compiler does at least cross module inlining. So it does more than just optimizing each compilation unit on its own. That mostly means that unlike in C/C++ trivial functions in modules (e.g. let length t = t.length) are not slow because they will get inlined where used. MfG Goswin _______________________________________________ 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 Jun 30 13:53:41 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 30 Jun 2014 13:53: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 1X1c1Y-0000QQ-KK; Mon, 30 Jun 2014 13:53:36 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1X1c1X-0000QL-Bi for mirageos-devel@lists.xenproject.org; Mon, 30 Jun 2014 13:53:35 +0000 Received: from [85.158.139.211:25590] by server-9.bemta-5.messagelabs.com id 80/3C-14363-EDB61B35; Mon, 30 Jun 2014 13:53:34 +0000 X-Env-Sender: goswin-v-b@web.de X-Msg-Ref: server-10.tower-206.messagelabs.com!1404136414!7469545!1 X-Originating-IP: [212.227.17.12] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: QmFkIElQOiAyMTIuMjI3LjE3LjEyID0+IDEzODM5\n,sa_preprocessor: QmFkIElQOiAyMTIuMjI3LjE3LjEyID0+IDEzODM5\n X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27731 invoked from network); 30 Jun 2014 13:53:34 -0000 Received: from mout.web.de (HELO mout.web.de) (212.227.17.12) by server-10.tower-206.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 30 Jun 2014 13:53:34 -0000 Received: from frosties.localnet ([78.43.112.61]) by smtp.web.de (mrweb101) with ESMTPSA (Nemesis) id 0MYNrh-1X5eLk3AQL-00V91q for ; Mon, 30 Jun 2014 15:53:33 +0200 Received: from mrvn by frosties.localnet with local (Exim 4.82) (envelope-from ) id 1X1c1U-00062c-QK for mirageos-devel@lists.xenproject.org; Mon, 30 Jun 2014 15:53:32 +0200 Date: Mon, 30 Jun 2014 15:53:32 +0200 From: Goswin von Brederlow To: mirageos-devel@lists.xenproject.org Message-ID: <20140630135332.GA23123@frosties> References: <87fvimpzpf.fsf@gmail.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <87fvimpzpf.fsf@gmail.com> User-Agent: Mutt/1.5.23 (2014-03-12) X-Provags-ID: V03:K0:JYkdm++EH5YYQ18Dh/GsrJqpNZLH0bD1pI9BROKS1zKgxd8pCdV aSTBkfd9tsC1Wffp/zyl08vO0Djh/Y5yG78yV1JC+2vUr/a+HcmGTI/pGPph2bH0rATqKd7 52RafztZ7yxnAw4oYuJo5x+uMb1+ZaAU4wGMsXKFNI40OQnb8Ihpw4xzIruFI8iQX9BgxY6 D2P3zgI9fDm8jTXBE8I/g== Subject: Re: [MirageOS-devel] Whole Program Optimization in 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 Mon, Jun 30, 2014 at 08:29:48AM +0000, Malcolm Matalka wrote: > I've seen it mentioned a few times that Mirage does WPO. Is there > documentation on what exactly this means? I am under the impression > that the ocaml compiler does not do whole program optimization. > > Thanks, > /M The ocaml compiler does at least cross module inlining. So it does more than just optimizing each compilation unit on its own. That mostly means that unlike in C/C++ trivial functions in modules (e.g. let length t = t.length) are not slow because they will get inlined where used. MfG Goswin _______________________________________________ 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 Jun 30 14:21:25 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 30 Jun 2014 14:21: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 1X1cSR-0001uy-LB; Mon, 30 Jun 2014 14:21:23 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1X1cSP-0001ut-23 for mirageos-devel@lists.xenproject.org; Mon, 30 Jun 2014 14:21:22 +0000 Received: from [193.109.254.147:6732] by server-16.bemta-14.messagelabs.com id 51/56-16986-E5271B35; Mon, 30 Jun 2014 14:21:18 +0000 X-Env-Sender: talex5@gmail.com X-Msg-Ref: server-10.tower-27.messagelabs.com!1404138076!14585069!1 X-Originating-IP: [209.85.214.171] X-SpamReason: No, hits=0.8 required=7.0 tests=BODY_RANDOM_LONG, ML_RADAR_SPEW_LINKS_14, ML_RADAR_SPEW_LINKS_23, RCVD_BY_IP, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22373 invoked from network); 30 Jun 2014 14:21:17 -0000 Received: from mail-ob0-f171.google.com (HELO mail-ob0-f171.google.com) (209.85.214.171) by server-10.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 30 Jun 2014 14:21:17 -0000 Received: by mail-ob0-f171.google.com with SMTP id nu7so8932703obb.30 for ; Mon, 30 Jun 2014 07:21:15 -0700 (PDT) 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=YdYxSIhwc9VJkI4FYi2V9ds3uZdmaW4hXjpXctgZn/o=; b=VMVxoejkZ+tpybdVrbMwhKt8as6DaFD9ZvfKN1ETSS3T5V+iXojjc8F5eTlODApNWd fxRi9ofitoXgG/WG5dTheOp/GcXEbIFGqT9RVKudOyO24vrH7XF3+zLz4htsTUhhkFwa 1veDGm3LBx5ToGZRmEitcySH8fAdWWKPCQ6xEWWEt/WR4T6hxsuTcM1PUFemK7fblHgQ +IYpSIvJLTUsMq2MAnlCcWLgeGXdhm6SB6cZJkjTV8YBelplguQi1+rMdd62qz9xCaKk XTxvoePzC5eV1r0TZaBo+dAM36QPM25nGC/BSj0Col2TW37/TWG7YNTphvWLJJdelmGP YkHA== MIME-Version: 1.0 X-Received: by 10.60.39.166 with SMTP id q6mr43292138oek.20.1404138075882; Mon, 30 Jun 2014 07:21:15 -0700 (PDT) Received: by 10.76.92.5 with HTTP; Mon, 30 Jun 2014 07:21:15 -0700 (PDT) In-Reply-To: References: Date: Mon, 30 Jun 2014 15:21:15 +0100 Message-ID: From: Thomas Leonard To: Anil Madhavapeddy Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Mirage on Xen/ARM status X-BeenThere: mirageos-devel@lists.xenproject.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 23 June 2014 23:04, Anil Madhavapeddy wrote: > On 23 Jun 2014, at 09:02, Thomas Leonard wrote: > >> On 4 June 2014 13:33, Thomas Leonard wrote: >>> An update on the Mirage/ARM port: >> [...] >>> My current plan is: >>> >>> - Upstream Karim's initial ARM support to Xen. I split the original >>> patch into three smaller ones and submitted them, but they want it >>> broken up further, which is fair enough. >> >> We're going through many of rounds of review with these patches (no >> major problems - mainly style issues). I'm going to split them up >> further to make them easier to review. > > Thanks for going through the upstreaming so patiently; it's very good > to know that we're reducing our custom-fork technical debt. Yeah, I've had 18 patches accepted so far, but we still haven't got to the ones that actually add ARM support, and those are the big ones! >>> - Upstream my patches to build a libminios.a library, plus some other >>> fixes to the build system. >> >> The fixes to the build system have been accepted, but the library >> patches are waiting for the ARM patches to go in first (otherwise >> we'll get conflicts). > >>> - Make some changes to Mini-OS to work unmodified with Mirage >>> (specifically: expose grant table details, disable interrupt-based >>> event handlers, and allow linking only the features we need). >> >> These are also waiting on the previous patches (and need tidying up). >> >> We'll need to make our own release of Mini-OS at some point for Mirage >> 2.0, and almost certainly before these patches are accepted upstream. >> >> The later we do it, the closer it will be to what eventually ends up >> upstream in Xen. The sooner, the more time we have for testing against >> it. Does some time this week sound reasonable? > > Some time this week sounds great. Since we now know with reasonable > certainty that the libminios.a will exist upstream, running with our > forked version is fine for a while (and possibly forever, if minor local > patches are needed, or we want to do something like tidy up the console > logging in such a way that upstream doesn't like it). I got a bit distracted rewriting the boot code to work on Xen/unstable. It uses a different memory layout to 4.4, so we need to detect where we are and program the MMU to fix everything up. It seems to be working now, though. >>> - Add a proper string library to mirage-platform to replace Mini-OS's >>> limited sprintf. >> >> I'll probably add the FreeBSD one here. > > Ack. On further investigation, this looks like a lot of work! sprintf uses vfprintf, which pulls in file stream handling, locales, wchar support, etc (musl looks similar). I'm currently hacking this all this in to see how it fits (planning to go back and do it properly once I understand exactly what's needed), but I'm wondering whether we could get away with just adding float support to Mini-OS's existing printf functions? Once OCaml 4.02 comes out, I guess that's all we'll need anyway. >>> - Upstream my patches to mirage-platform and mirage to build using the >>> new libminios and openlibm (these are on github in my forks). >> >> How do we want to do this? Can we just tell everyone to upgrade mirage >> and mirage-platform together, and get Mini-OS and openlibm at the same >> time, or should we add backwards-compatibility hacks so e.g. mirage >> can configure for either the old or new version of mirage-platform? > > Mirage 1.2.0 will be the last of the 1.x series (except any minor bugfix > releases), and out this week. > > After that, we can merge the 2.0 branch into trunk, which can include the > Makefile changes needed for the new MiniOS (as well as V2 mirage-types). > > There's no need for backwards compatibility hacks between Mirage 1.x and > 2.x. The one hitch is that it's not possible to specify a version > constraint on the command line (e.g. so that `opam install mirage-xen {<2.0}` > will work), so releasing a new mirage-platform will result in older > setups breaking if they upgrade. I'm not sure there's much we can do > about that beyond instruct users of old Mirage to pin packages, or > pick a new name such as mirage-platform-xen. Both are confusing :( > >> >>> - Upstream my Mini-OS ARM patches to Xen. >> >> I squashed these into Karim's ARM patches to simplify the review (no >> point reviewing code that's about to be replaced). >> >>> - Add a start_info structure on ARM, or find some other way to expose >>> those details to Mirage. >> >> This is done, and simplified things greatly. No changes are now needed >> in mirage-console, etc for ARM. >> >> We also need to sort out the ones complement stuff for networking on >> ARM, but that can come after the upgrade to the new Mini-OS (which is >> the big change; once we have that, ARM support comes almost for free). > > Agreed! BTW, did anyone manage to test my current preview branches (i.e. mirage-platform + libminios)? -- 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 Jun 30 14:21:25 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 30 Jun 2014 14:21: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 1X1cSR-0001uy-LB; Mon, 30 Jun 2014 14:21:23 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1X1cSP-0001ut-23 for mirageos-devel@lists.xenproject.org; Mon, 30 Jun 2014 14:21:22 +0000 Received: from [193.109.254.147:6732] by server-16.bemta-14.messagelabs.com id 51/56-16986-E5271B35; Mon, 30 Jun 2014 14:21:18 +0000 X-Env-Sender: talex5@gmail.com X-Msg-Ref: server-10.tower-27.messagelabs.com!1404138076!14585069!1 X-Originating-IP: [209.85.214.171] X-SpamReason: No, hits=0.8 required=7.0 tests=BODY_RANDOM_LONG, ML_RADAR_SPEW_LINKS_14, ML_RADAR_SPEW_LINKS_23, RCVD_BY_IP, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22373 invoked from network); 30 Jun 2014 14:21:17 -0000 Received: from mail-ob0-f171.google.com (HELO mail-ob0-f171.google.com) (209.85.214.171) by server-10.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 30 Jun 2014 14:21:17 -0000 Received: by mail-ob0-f171.google.com with SMTP id nu7so8932703obb.30 for ; Mon, 30 Jun 2014 07:21:15 -0700 (PDT) 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=YdYxSIhwc9VJkI4FYi2V9ds3uZdmaW4hXjpXctgZn/o=; b=VMVxoejkZ+tpybdVrbMwhKt8as6DaFD9ZvfKN1ETSS3T5V+iXojjc8F5eTlODApNWd fxRi9ofitoXgG/WG5dTheOp/GcXEbIFGqT9RVKudOyO24vrH7XF3+zLz4htsTUhhkFwa 1veDGm3LBx5ToGZRmEitcySH8fAdWWKPCQ6xEWWEt/WR4T6hxsuTcM1PUFemK7fblHgQ +IYpSIvJLTUsMq2MAnlCcWLgeGXdhm6SB6cZJkjTV8YBelplguQi1+rMdd62qz9xCaKk XTxvoePzC5eV1r0TZaBo+dAM36QPM25nGC/BSj0Col2TW37/TWG7YNTphvWLJJdelmGP YkHA== MIME-Version: 1.0 X-Received: by 10.60.39.166 with SMTP id q6mr43292138oek.20.1404138075882; Mon, 30 Jun 2014 07:21:15 -0700 (PDT) Received: by 10.76.92.5 with HTTP; Mon, 30 Jun 2014 07:21:15 -0700 (PDT) In-Reply-To: References: Date: Mon, 30 Jun 2014 15:21:15 +0100 Message-ID: From: Thomas Leonard To: Anil Madhavapeddy Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Mirage on Xen/ARM status X-BeenThere: mirageos-devel@lists.xenproject.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 23 June 2014 23:04, Anil Madhavapeddy wrote: > On 23 Jun 2014, at 09:02, Thomas Leonard wrote: > >> On 4 June 2014 13:33, Thomas Leonard wrote: >>> An update on the Mirage/ARM port: >> [...] >>> My current plan is: >>> >>> - Upstream Karim's initial ARM support to Xen. I split the original >>> patch into three smaller ones and submitted them, but they want it >>> broken up further, which is fair enough. >> >> We're going through many of rounds of review with these patches (no >> major problems - mainly style issues). I'm going to split them up >> further to make them easier to review. > > Thanks for going through the upstreaming so patiently; it's very good > to know that we're reducing our custom-fork technical debt. Yeah, I've had 18 patches accepted so far, but we still haven't got to the ones that actually add ARM support, and those are the big ones! >>> - Upstream my patches to build a libminios.a library, plus some other >>> fixes to the build system. >> >> The fixes to the build system have been accepted, but the library >> patches are waiting for the ARM patches to go in first (otherwise >> we'll get conflicts). > >>> - Make some changes to Mini-OS to work unmodified with Mirage >>> (specifically: expose grant table details, disable interrupt-based >>> event handlers, and allow linking only the features we need). >> >> These are also waiting on the previous patches (and need tidying up). >> >> We'll need to make our own release of Mini-OS at some point for Mirage >> 2.0, and almost certainly before these patches are accepted upstream. >> >> The later we do it, the closer it will be to what eventually ends up >> upstream in Xen. The sooner, the more time we have for testing against >> it. Does some time this week sound reasonable? > > Some time this week sounds great. Since we now know with reasonable > certainty that the libminios.a will exist upstream, running with our > forked version is fine for a while (and possibly forever, if minor local > patches are needed, or we want to do something like tidy up the console > logging in such a way that upstream doesn't like it). I got a bit distracted rewriting the boot code to work on Xen/unstable. It uses a different memory layout to 4.4, so we need to detect where we are and program the MMU to fix everything up. It seems to be working now, though. >>> - Add a proper string library to mirage-platform to replace Mini-OS's >>> limited sprintf. >> >> I'll probably add the FreeBSD one here. > > Ack. On further investigation, this looks like a lot of work! sprintf uses vfprintf, which pulls in file stream handling, locales, wchar support, etc (musl looks similar). I'm currently hacking this all this in to see how it fits (planning to go back and do it properly once I understand exactly what's needed), but I'm wondering whether we could get away with just adding float support to Mini-OS's existing printf functions? Once OCaml 4.02 comes out, I guess that's all we'll need anyway. >>> - Upstream my patches to mirage-platform and mirage to build using the >>> new libminios and openlibm (these are on github in my forks). >> >> How do we want to do this? Can we just tell everyone to upgrade mirage >> and mirage-platform together, and get Mini-OS and openlibm at the same >> time, or should we add backwards-compatibility hacks so e.g. mirage >> can configure for either the old or new version of mirage-platform? > > Mirage 1.2.0 will be the last of the 1.x series (except any minor bugfix > releases), and out this week. > > After that, we can merge the 2.0 branch into trunk, which can include the > Makefile changes needed for the new MiniOS (as well as V2 mirage-types). > > There's no need for backwards compatibility hacks between Mirage 1.x and > 2.x. The one hitch is that it's not possible to specify a version > constraint on the command line (e.g. so that `opam install mirage-xen {<2.0}` > will work), so releasing a new mirage-platform will result in older > setups breaking if they upgrade. I'm not sure there's much we can do > about that beyond instruct users of old Mirage to pin packages, or > pick a new name such as mirage-platform-xen. Both are confusing :( > >> >>> - Upstream my Mini-OS ARM patches to Xen. >> >> I squashed these into Karim's ARM patches to simplify the review (no >> point reviewing code that's about to be replaced). >> >>> - Add a start_info structure on ARM, or find some other way to expose >>> those details to Mirage. >> >> This is done, and simplified things greatly. No changes are now needed >> in mirage-console, etc for ARM. >> >> We also need to sort out the ones complement stuff for networking on >> ARM, but that can come after the upgrade to the new Mini-OS (which is >> the big change; once we have that, ARM support comes almost for free). > > Agreed! BTW, did anyone manage to test my current preview branches (i.e. mirage-platform + libminios)? -- 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 Jun 30 17:32:33 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 30 Jun 2014 17:32: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 1X1fRM-0000OU-GS; Mon, 30 Jun 2014 17:32:28 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1X1fRL-0000OH-R9 for mirageos-devel@lists.xenproject.org; Mon, 30 Jun 2014 17:32:27 +0000 Received: from [85.158.139.211:8294] by server-7.bemta-5.messagelabs.com id 77/E3-03657-B2F91B35; Mon, 30 Jun 2014 17:32:27 +0000 X-Env-Sender: mmatalka@gmail.com X-Msg-Ref: server-2.tower-206.messagelabs.com!1404149546!12809427!1 X-Originating-IP: [74.125.82.49] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30478 invoked from network); 30 Jun 2014 17:32:26 -0000 Received: from mail-wg0-f49.google.com (HELO mail-wg0-f49.google.com) (74.125.82.49) by server-2.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 30 Jun 2014 17:32:26 -0000 Received: by mail-wg0-f49.google.com with SMTP id y10so8665515wgg.32 for ; Mon, 30 Jun 2014 10:32:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:subject:date:message-id:user-agent:mime-version :content-type; bh=3D61x4VQAvVXDJkKVJptdZKboiDjd1PDAoQSJSN9V48=; b=cWkE3Be0H2rG2w8qQ3pPLTqrefCGoV1f99hNcPtz1Ln0RPg8NnPSavhJD17Ym1c0mn IY/xHOc+xdCvvapzPK1eipd13RCR3SnYbnk8LSpLZ4cvOpUZKYSmkHphkfWnMRcItrSb UDIIJ2LYeQABf7diD6OqW7KNGbqZSsizAhg87jas/PcjNElo2df3ptNa/hzYwSsxHNow sTY9pEfgwHEDh8C0dFusnoG/Cv6v5GkunBzkgk97tmsWRMVQb+KCYJchh86ZoYFWGXhd wy6q+Tzu0NCpSJpTmGkORBCCv7Vl88nFKsKV/HvVihtX7clMmR1p6PcX5Vu3GgMcnWPF 65ZQ== X-Received: by 10.180.84.168 with SMTP id a8mr30752616wiz.36.1404149546384; Mon, 30 Jun 2014 10:32:26 -0700 (PDT) Received: from localhost ([2a01:7e00::f03c:91ff:fe70:2696]) by mx.google.com with ESMTPSA id ub8sm33638143wib.0.2014.06.30.10.32.25 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 30 Jun 2014 10:32:25 -0700 (PDT) From: Malcolm Matalka To: mirageos-devel@lists.xenproject.org Date: Mon, 30 Jun 2014 17:32:24 +0000 Message-ID: <87zjgumhg7.fsf@gmail.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) MIME-Version: 1.0 Subject: [MirageOS-devel] Small typo in hello-world doc X-BeenThere: mirageos-devel@lists.xenproject.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 Hey, just noticed what I believe to me a tiny typo in the hello-world doc. http://openmirage.org/wiki/hello-world Search for: env FS=fat mirage configure I believe there is a missing new line between 'fat' and 'mirage'. _______________________________________________ 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 Jun 30 17:32:33 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 30 Jun 2014 17:32: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 1X1fRM-0000OU-GS; Mon, 30 Jun 2014 17:32:28 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1X1fRL-0000OH-R9 for mirageos-devel@lists.xenproject.org; Mon, 30 Jun 2014 17:32:27 +0000 Received: from [85.158.139.211:8294] by server-7.bemta-5.messagelabs.com id 77/E3-03657-B2F91B35; Mon, 30 Jun 2014 17:32:27 +0000 X-Env-Sender: mmatalka@gmail.com X-Msg-Ref: server-2.tower-206.messagelabs.com!1404149546!12809427!1 X-Originating-IP: [74.125.82.49] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30478 invoked from network); 30 Jun 2014 17:32:26 -0000 Received: from mail-wg0-f49.google.com (HELO mail-wg0-f49.google.com) (74.125.82.49) by server-2.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 30 Jun 2014 17:32:26 -0000 Received: by mail-wg0-f49.google.com with SMTP id y10so8665515wgg.32 for ; Mon, 30 Jun 2014 10:32:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:subject:date:message-id:user-agent:mime-version :content-type; bh=3D61x4VQAvVXDJkKVJptdZKboiDjd1PDAoQSJSN9V48=; b=cWkE3Be0H2rG2w8qQ3pPLTqrefCGoV1f99hNcPtz1Ln0RPg8NnPSavhJD17Ym1c0mn IY/xHOc+xdCvvapzPK1eipd13RCR3SnYbnk8LSpLZ4cvOpUZKYSmkHphkfWnMRcItrSb UDIIJ2LYeQABf7diD6OqW7KNGbqZSsizAhg87jas/PcjNElo2df3ptNa/hzYwSsxHNow sTY9pEfgwHEDh8C0dFusnoG/Cv6v5GkunBzkgk97tmsWRMVQb+KCYJchh86ZoYFWGXhd wy6q+Tzu0NCpSJpTmGkORBCCv7Vl88nFKsKV/HvVihtX7clMmR1p6PcX5Vu3GgMcnWPF 65ZQ== X-Received: by 10.180.84.168 with SMTP id a8mr30752616wiz.36.1404149546384; Mon, 30 Jun 2014 10:32:26 -0700 (PDT) Received: from localhost ([2a01:7e00::f03c:91ff:fe70:2696]) by mx.google.com with ESMTPSA id ub8sm33638143wib.0.2014.06.30.10.32.25 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 30 Jun 2014 10:32:25 -0700 (PDT) From: Malcolm Matalka To: mirageos-devel@lists.xenproject.org Date: Mon, 30 Jun 2014 17:32:24 +0000 Message-ID: <87zjgumhg7.fsf@gmail.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) MIME-Version: 1.0 Subject: [MirageOS-devel] Small typo in hello-world doc X-BeenThere: mirageos-devel@lists.xenproject.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 Hey, just noticed what I believe to me a tiny typo in the hello-world doc. http://openmirage.org/wiki/hello-world Search for: env FS=fat mirage configure I believe there is a missing new line between 'fat' and 'mirage'. _______________________________________________ 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 Jun 30 18:55:51 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 30 Jun 2014 18:55: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 1X1gjw-0006ya-Lj; Mon, 30 Jun 2014 18:55:44 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1X1gjv-0006yV-5y for mirageos-devel@lists.xenproject.org; Mon, 30 Jun 2014 18:55:43 +0000 Received: from [85.158.143.35:5997] by server-3.bemta-4.messagelabs.com id 1D/3E-16194-EA2B1B35; Mon, 30 Jun 2014 18:55:42 +0000 X-Env-Sender: jyotsna.prakash@gmail.com X-Msg-Ref: server-4.tower-21.messagelabs.com!1404154540!14839771!1 X-Originating-IP: [209.85.219.45] X-SpamReason: No, hits=0.9 required=7.0 tests=HTML_40_50,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10261 invoked from network); 30 Jun 2014 18:55:41 -0000 Received: from mail-oa0-f45.google.com (HELO mail-oa0-f45.google.com) (209.85.219.45) by server-4.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 30 Jun 2014 18:55:41 -0000 Received: by mail-oa0-f45.google.com with SMTP id o6so9274075oag.4 for ; Mon, 30 Jun 2014 11:55:39 -0700 (PDT) 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=XDxkx3jke33RzjtQyacPrK5N+o8EJB3hn8z/lYSjuzA=; b=K7g2Uf/Ookv+rIlhevStdnP8tAjwCF26eN1RbtQLFiUien3rfo6W55RCaE2dla1I7D 5HkJqafXS5a4T0rcKg47SdHaFFVVAdQgeiUDXpxw5MVAoTkCKKNMg2vuvAz5UpWn3Wm1 qWu2IhdaZvIW6QkwvBjPgsMrYCilND0nK1gCmFm7gyzeu7rClNfQuCvWEv+Ate1sZOdh 96J0mJu+2wcjxV3kPQndlEmR2iqVHfKk6PoDksdfpoTUMcq633uaHdjVswvh+RvzquXj dIsx7daDmf4aApOOD5awp4WE/qCGoLO9rQaHKDsyllDP3q63TVyqI8nT2QqFeU0FNm/O xHNg== MIME-Version: 1.0 X-Received: by 10.60.116.166 with SMTP id jx6mr20416117oeb.6.1404154539630; Mon, 30 Jun 2014 11:55:39 -0700 (PDT) Received: by 10.202.215.193 with HTTP; Mon, 30 Jun 2014 11:55:39 -0700 (PDT) In-Reply-To: <87zjgumhg7.fsf@gmail.com> References: <87zjgumhg7.fsf@gmail.com> Date: Mon, 30 Jun 2014 11:55:39 -0700 Message-ID: From: Jyotsna Prakash To: Malcolm Matalka Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Small typo in hello-world doc X-BeenThere: mirageos-devel@lists.xenproject.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="===============3021382459882589796==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============3021382459882589796== Content-Type: multipart/alternative; boundary=089e0129534e8b6ab604fd123450 --089e0129534e8b6ab604fd123450 Content-Type: text/plain; charset=UTF-8 Hi Malcolm, According to the manpage for env this syntax should be correct. It seems env only sets the environment variable temporarily--so mirage configure will not have FS set and will default to crunch in the newline case. However I believe that you can do $ export FS=fat $ mirage configure to get the same results. - Jyotsna On Mon, Jun 30, 2014 at 10:32 AM, Malcolm Matalka wrote: > Hey, just noticed what I believe to me a tiny typo in the hello-world > doc. > > http://openmirage.org/wiki/hello-world > > Search for: > > env FS=fat mirage configure > > I believe there is a missing new line between 'fat' and 'mirage'. > > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > --089e0129534e8b6ab604fd123450 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi Malcolm,

According to the manpage for env this s= yntax should be correct. It seems env only sets the environment variable te= mporarily--so mirage configure will not have FS set and will default to cru= nch in the newline case.

However I believe that you can do

$ export FS=3Dfat
$ mirage = configure

to get the same results.
- Jyotsna


On Mon, Jun 30, 2014 at= 10:32 AM, Malcolm Matalka <mmatalka@gmail.com> wrote:
Hey, just noticed what I believe to me a tin= y typo in the hello-world
doc.

http:/= /openmirage.org/wiki/hello-world

Search for:

env FS=3Dfat mirage configure

I believe there is a missing new line between 'fat' and 'mirage= '.

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

--089e0129534e8b6ab604fd123450-- --===============3021382459882589796== 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 --===============3021382459882589796==-- From mirageos-devel-bounces@lists.xenproject.org Mon Jun 30 18:55:51 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 30 Jun 2014 18:55: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 1X1gjw-0006ya-Lj; Mon, 30 Jun 2014 18:55:44 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1X1gjv-0006yV-5y for mirageos-devel@lists.xenproject.org; Mon, 30 Jun 2014 18:55:43 +0000 Received: from [85.158.143.35:5997] by server-3.bemta-4.messagelabs.com id 1D/3E-16194-EA2B1B35; Mon, 30 Jun 2014 18:55:42 +0000 X-Env-Sender: jyotsna.prakash@gmail.com X-Msg-Ref: server-4.tower-21.messagelabs.com!1404154540!14839771!1 X-Originating-IP: [209.85.219.45] X-SpamReason: No, hits=0.9 required=7.0 tests=HTML_40_50,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10261 invoked from network); 30 Jun 2014 18:55:41 -0000 Received: from mail-oa0-f45.google.com (HELO mail-oa0-f45.google.com) (209.85.219.45) by server-4.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 30 Jun 2014 18:55:41 -0000 Received: by mail-oa0-f45.google.com with SMTP id o6so9274075oag.4 for ; Mon, 30 Jun 2014 11:55:39 -0700 (PDT) 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=XDxkx3jke33RzjtQyacPrK5N+o8EJB3hn8z/lYSjuzA=; b=K7g2Uf/Ookv+rIlhevStdnP8tAjwCF26eN1RbtQLFiUien3rfo6W55RCaE2dla1I7D 5HkJqafXS5a4T0rcKg47SdHaFFVVAdQgeiUDXpxw5MVAoTkCKKNMg2vuvAz5UpWn3Wm1 qWu2IhdaZvIW6QkwvBjPgsMrYCilND0nK1gCmFm7gyzeu7rClNfQuCvWEv+Ate1sZOdh 96J0mJu+2wcjxV3kPQndlEmR2iqVHfKk6PoDksdfpoTUMcq633uaHdjVswvh+RvzquXj dIsx7daDmf4aApOOD5awp4WE/qCGoLO9rQaHKDsyllDP3q63TVyqI8nT2QqFeU0FNm/O xHNg== MIME-Version: 1.0 X-Received: by 10.60.116.166 with SMTP id jx6mr20416117oeb.6.1404154539630; Mon, 30 Jun 2014 11:55:39 -0700 (PDT) Received: by 10.202.215.193 with HTTP; Mon, 30 Jun 2014 11:55:39 -0700 (PDT) In-Reply-To: <87zjgumhg7.fsf@gmail.com> References: <87zjgumhg7.fsf@gmail.com> Date: Mon, 30 Jun 2014 11:55:39 -0700 Message-ID: From: Jyotsna Prakash To: Malcolm Matalka Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Small typo in hello-world doc X-BeenThere: mirageos-devel@lists.xenproject.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="===============3021382459882589796==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============3021382459882589796== Content-Type: multipart/alternative; boundary=089e0129534e8b6ab604fd123450 --089e0129534e8b6ab604fd123450 Content-Type: text/plain; charset=UTF-8 Hi Malcolm, According to the manpage for env this syntax should be correct. It seems env only sets the environment variable temporarily--so mirage configure will not have FS set and will default to crunch in the newline case. However I believe that you can do $ export FS=fat $ mirage configure to get the same results. - Jyotsna On Mon, Jun 30, 2014 at 10:32 AM, Malcolm Matalka wrote: > Hey, just noticed what I believe to me a tiny typo in the hello-world > doc. > > http://openmirage.org/wiki/hello-world > > Search for: > > env FS=fat mirage configure > > I believe there is a missing new line between 'fat' and 'mirage'. > > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > --089e0129534e8b6ab604fd123450 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi Malcolm,

According to the manpage for env this s= yntax should be correct. It seems env only sets the environment variable te= mporarily--so mirage configure will not have FS set and will default to cru= nch in the newline case.

However I believe that you can do

$ export FS=3Dfat
$ mirage = configure

to get the same results.
- Jyotsna


On Mon, Jun 30, 2014 at= 10:32 AM, Malcolm Matalka <mmatalka@gmail.com> wrote:
Hey, just noticed what I believe to me a tin= y typo in the hello-world
doc.

http:/= /openmirage.org/wiki/hello-world

Search for:

env FS=3Dfat mirage configure

I believe there is a missing new line between 'fat' and 'mirage= '.

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

--089e0129534e8b6ab604fd123450-- --===============3021382459882589796== 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 --===============3021382459882589796==-- From mirageos-devel-bounces@lists.xenproject.org Mon Jun 30 19:04:33 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 30 Jun 2014 19:04: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 1X1gsT-0007I3-Ci; Mon, 30 Jun 2014 19:04:33 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1X1gsS-0007Hy-6v for mirageos-devel@lists.xenproject.org; Mon, 30 Jun 2014 19:04:32 +0000 Received: from [193.109.254.147:61607] by server-8.bemta-14.messagelabs.com id 25/CB-01877-FB4B1B35; Mon, 30 Jun 2014 19:04:31 +0000 X-Env-Sender: mmatalka@gmail.com X-Msg-Ref: server-6.tower-27.messagelabs.com!1404155070!14610533!1 X-Originating-IP: [74.125.82.180] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31844 invoked from network); 30 Jun 2014 19:04:30 -0000 Received: from mail-we0-f180.google.com (HELO mail-we0-f180.google.com) (74.125.82.180) by server-6.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 30 Jun 2014 19:04:30 -0000 Received: by mail-we0-f180.google.com with SMTP id x48so8518563wes.39 for ; Mon, 30 Jun 2014 12:04:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:subject:references:date:in-reply-to:message-id :user-agent:mime-version:content-type; bh=tsmvTdmNZ1FLMQMjLLLgpLa023SFahP64X4aRc7X5Eg=; b=QchfMbaEJHLgI1QoOKFj5lJYi0cguqu6QT0WaCbzb+vY92+HLQMYD152pKDi9cLZUb 7d4g7WNwwzu1ikFHwR+nx5+3WyLS9CBCYZVk4AxmzwLauLt3FT68g31QDBMcGlM6Uoiq bTNdel7LGNWm0HXu+VJvqfV+z0tEkYCgyJNCBzOXDmNh7rxgz0DEIZlWPBnaj2+SmFOs rmBl9gBxxy3xcPEGPrMq04t/VvwKBCqrDo4m1KOwcbwqtshQUi9Sf8cHbROJBFEhyJAF 6GJiTopmGEazM8g8u2hI9aiilzwz7yAhWJ1Mqs4CFvviTuZN88zuCwcsrxLsczJwuy3X UdZw== X-Received: by 10.194.89.168 with SMTP id bp8mr47229952wjb.73.1404155070307; Mon, 30 Jun 2014 12:04:30 -0700 (PDT) Received: from localhost ([2a01:7e00::f03c:91ff:fe70:2696]) by mx.google.com with ESMTPSA id bq7sm34379015wib.7.2014.06.30.12.04.29 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 30 Jun 2014 12:04:29 -0700 (PDT) From: Malcolm Matalka To: Jyotsna Prakash References: <87zjgumhg7.fsf@gmail.com> Date: Mon, 30 Jun 2014 19:04:28 +0000 In-Reply-To: (Jyotsna Prakash's message of "Mon, 30 Jun 2014 11:55:39 -0700") Message-ID: <87k37ymd6r.fsf@gmail.com> 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] Small typo in hello-world doc X-BeenThere: mirageos-devel@lists.xenproject.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 Whoops, brain fart. You're completely right. My brain was just working the wrong way today. Ignore me! Jyotsna Prakash writes: > Hi Malcolm, > > According to the manpage for env this syntax should be correct. It seems > env only sets the environment variable temporarily--so mirage configure > will not have FS set and will default to crunch in the newline case. > > However I believe that you can do > > $ export FS=fat > $ mirage configure > > to get the same results. > - Jyotsna > > > On Mon, Jun 30, 2014 at 10:32 AM, Malcolm Matalka > wrote: > >> Hey, just noticed what I believe to me a tiny typo in the hello-world >> doc. >> >> http://openmirage.org/wiki/hello-world >> >> Search for: >> >> env FS=fat mirage configure >> >> I believe there is a missing new line between 'fat' and 'mirage'. >> >> _______________________________________________ >> 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 Jun 30 19:04:33 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 30 Jun 2014 19:04: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 1X1gsT-0007I3-Ci; Mon, 30 Jun 2014 19:04:33 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1X1gsS-0007Hy-6v for mirageos-devel@lists.xenproject.org; Mon, 30 Jun 2014 19:04:32 +0000 Received: from [193.109.254.147:61607] by server-8.bemta-14.messagelabs.com id 25/CB-01877-FB4B1B35; Mon, 30 Jun 2014 19:04:31 +0000 X-Env-Sender: mmatalka@gmail.com X-Msg-Ref: server-6.tower-27.messagelabs.com!1404155070!14610533!1 X-Originating-IP: [74.125.82.180] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31844 invoked from network); 30 Jun 2014 19:04:30 -0000 Received: from mail-we0-f180.google.com (HELO mail-we0-f180.google.com) (74.125.82.180) by server-6.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 30 Jun 2014 19:04:30 -0000 Received: by mail-we0-f180.google.com with SMTP id x48so8518563wes.39 for ; Mon, 30 Jun 2014 12:04:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:subject:references:date:in-reply-to:message-id :user-agent:mime-version:content-type; bh=tsmvTdmNZ1FLMQMjLLLgpLa023SFahP64X4aRc7X5Eg=; b=QchfMbaEJHLgI1QoOKFj5lJYi0cguqu6QT0WaCbzb+vY92+HLQMYD152pKDi9cLZUb 7d4g7WNwwzu1ikFHwR+nx5+3WyLS9CBCYZVk4AxmzwLauLt3FT68g31QDBMcGlM6Uoiq bTNdel7LGNWm0HXu+VJvqfV+z0tEkYCgyJNCBzOXDmNh7rxgz0DEIZlWPBnaj2+SmFOs rmBl9gBxxy3xcPEGPrMq04t/VvwKBCqrDo4m1KOwcbwqtshQUi9Sf8cHbROJBFEhyJAF 6GJiTopmGEazM8g8u2hI9aiilzwz7yAhWJ1Mqs4CFvviTuZN88zuCwcsrxLsczJwuy3X UdZw== X-Received: by 10.194.89.168 with SMTP id bp8mr47229952wjb.73.1404155070307; Mon, 30 Jun 2014 12:04:30 -0700 (PDT) Received: from localhost ([2a01:7e00::f03c:91ff:fe70:2696]) by mx.google.com with ESMTPSA id bq7sm34379015wib.7.2014.06.30.12.04.29 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 30 Jun 2014 12:04:29 -0700 (PDT) From: Malcolm Matalka To: Jyotsna Prakash References: <87zjgumhg7.fsf@gmail.com> Date: Mon, 30 Jun 2014 19:04:28 +0000 In-Reply-To: (Jyotsna Prakash's message of "Mon, 30 Jun 2014 11:55:39 -0700") Message-ID: <87k37ymd6r.fsf@gmail.com> 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] Small typo in hello-world doc X-BeenThere: mirageos-devel@lists.xenproject.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 Whoops, brain fart. You're completely right. My brain was just working the wrong way today. Ignore me! Jyotsna Prakash writes: > Hi Malcolm, > > According to the manpage for env this syntax should be correct. It seems > env only sets the environment variable temporarily--so mirage configure > will not have FS set and will default to crunch in the newline case. > > However I believe that you can do > > $ export FS=fat > $ mirage configure > > to get the same results. > - Jyotsna > > > On Mon, Jun 30, 2014 at 10:32 AM, Malcolm Matalka > wrote: > >> Hey, just noticed what I believe to me a tiny typo in the hello-world >> doc. >> >> http://openmirage.org/wiki/hello-world >> >> Search for: >> >> env FS=fat mirage configure >> >> I believe there is a missing new line between 'fat' and 'mirage'. >> >> _______________________________________________ >> 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