From owner-soc-status@freebsd.org Mon May 28 02:10:30 2018 Return-Path: Delivered-To: soc-status@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A3A28EF41DC for ; Mon, 28 May 2018 02:10:30 +0000 (UTC) (envelope-from aniket.ezio41@gmail.com) Received: from mail-wm0-f49.google.com (mail-wm0-f49.google.com [74.125.82.49]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1C17176D6E; Mon, 28 May 2018 02:10:29 +0000 (UTC) (envelope-from aniket.ezio41@gmail.com) Received: by mail-wm0-f49.google.com with SMTP id m129-v6so27939672wmb.3; Sun, 27 May 2018 19:10:29 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=aqpO4/9K72dcN6UwLws8cu0IGOIt10Oyuko2g6QVbo4=; b=HPG8yH7JG2gcMgemdfogN7yiRO06KlyfZrkC7hyCRMyZB8nK/QEDKoDN48NMYOolKe hGgwljm+NOeSDjB0t+CYfAnVQhPHbPIEygbA8vIW1ZtCvR3RwzZaGv/MJkRM046CcP66 E8QCIL3ZpLgpQxh6BZGKTMqM+ddTPNjl/0jmeTSNqr6XWFGf3U4vzlXF7Fe4fKO/ZNHC y5bNE8EvkGNoWCVzrcz0cxa4l6yMsW+hI13R36ojj+PgLtypfv+5W9XuYQ31DHjelUnG /L6bTSbSx/lHlg9FpF9PFJHaGgIE/Mv0FA9XnNx70IebVeioeMyTpEGm3q6M4z6sOg5i u5Mg== X-Gm-Message-State: ALKqPwe6pwwB5yhlsyCmlEnPJeG5w88mjSc8403P76PuQ9qOgUTpZpry ANPoIfXnzf5zfw5pCA3nVi35fMNB X-Google-Smtp-Source: AB8JxZrvOPy2JpG6eFZzHjMzKlrWjQVH6/jZCPGkmebhKNysFn+UFHPHfCkvfH2wPxVePXYMrWveMQ== X-Received: by 2002:a50:c119:: with SMTP id l25-v6mr13113194edf.188.1527473422666; Sun, 27 May 2018 19:10:22 -0700 (PDT) Received: from mail-wm0-f53.google.com (mail-wm0-f53.google.com. [74.125.82.53]) by smtp.gmail.com with ESMTPSA id j22-v6sm15711635edq.92.2018.05.27.19.10.22 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 27 May 2018 19:10:22 -0700 (PDT) Received: by mail-wm0-f53.google.com with SMTP id o78-v6so28069512wmg.0; Sun, 27 May 2018 19:10:22 -0700 (PDT) X-Received: by 2002:a1c:5403:: with SMTP id i3-v6mr7048693wmb.37.1527473422026; Sun, 27 May 2018 19:10:22 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:adf:adcf:0:0:0:0:0 with HTTP; Sun, 27 May 2018 19:10:21 -0700 (PDT) From: Aniket Pandey Date: Mon, 28 May 2018 07:40:21 +0530 X-Gmail-Original-Message-ID: Message-ID: Subject: [GSoC-18] Regression Test-Suite for Audit Framework [Week-2] To: soc-status@freebsd.org Cc: asomers@freebsd.org, robert.watson@cl.cam.ac.uk, gavin@freebsd.org, George Neville-Neil Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: soc-status@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Summer of Code Status Reports and Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 May 2018 02:10:30 -0000 Hello all, At the end of the week 2, as promised, I was able to finish off the tests for network APIs and complete the remaining test cases for audit classes concerned with File I/O and device management. I also studied about "Inter Process Communication" within an Operating System and how best to audit the syscalls present within IPC audit class. So a total of 115 atf-c(3) test-cases spanning over 6 audit classes {fm, cl, nt, io, ex, ip} were developed during this week. Milestones and issues encountered ~~~~~~~~~~~~~~~~~~~~~~~~~~~ 1) Fixing the panic mentioned in the previous mail, brought up another consistent and reproducible kernel panic. This time, whenever auditd(8) was already running and the system-wide audit mask was set as "pc" (process control), trying to list the contents of a directory using "exa-0.8.0" caused another panic. The stack trace showed the involvement of an audit lookup function. ( https://pastebin.com/b68k27iw ) 2) On trying to audit execve(2) system call, we noticed that even on the successful invocation of execve, audit record showed "return,failure : Unknown error" which was quite unexpected. On further analysis, we concluded that since execve(2) overlays the calling process on successful execution, the audit(4) doesn't get any return status so it essentially prints out the exception case in the errno lookup here: https://github.com/freebsd/freebsd/blob/master/sys/security/audit/bsm_errno.c#L728 3) While writing tests for network socket system calls, I had to overcome a unique challenge. Since Kyua executes every test-case as a separate process and that it's not possible to share the state between the test cases, I had to somehow integrate both client and server APIs within a single test case body. Now the options I could think of were to either fork the client out of the main process after listen(2) has been called, or simply use different threads for both. However, Alan suggested a much better approach, simply make the server non-blocking and create the client socket right before connect(2) is called. With the server waiting for connection by the time client calls a connect(2), we would be able to get the successful connection within the same program in a single thread. [ Note: Even though this method is successful in FreeBSD, it sometimes returns EWOULDBLOCK in Linux ] Although I could get a successful connection using this approach, I still had to audit recv(2), recvfrom(2) which are blocking, after they successfully receive data from their counterparts, i.e send(2) and sendto(2). But since I was calling the recv(2) from the server which was already non-blocking, I couldn't get a successful audit of these functions. On further research, I came across some threads on reddit which mentioned doing synchronous I/O multiplexing on the client socket using select(2) to ensure that the socket is ready for reading, i.e recv(2), recvfrom(2) can successfully exit. This allowed me to audit all possible scenarios of network socket system calls! Here is the test-case which checks the audit of recvfrom(2): https://github.com/aniketp/AuditTestSuite/blob/master/src/network.c#L877 4) Post that, I've added about 51 test cases for system calls concerned with manipulating message queues, shared memory segments and semaphore sets as a part of IPC audit class. I would keep adding the tests and hopefully, finish off "ip" audit events within a couple of days. 5) I've also created a differential revision on shifting "struct auditpipe_ioctl_preselect" from to since its members, i.e "au_mask_t" and "au_id_t" are defined within the later header file. It is currently under review. Status ~~~~~~ So far, I've been able to create 421 test-cases spanning over 11 test programs for 107 system calls of {"fc", "fr", "fw", "fd", "fa", "fm", "cl", "io", "ex", "nt", "ip"} audit classes in 8449 SLOC. The tests are passing apart from a few expected failures from syscalls which are supposed to be audited but are not. The test result can be seen here > https://pastebin.com/eMPUNfrX I'll hopefully be able to finish off my proposed work (explicit system call testing) within a week and then I can work on testing some other important aspects of the audit system as a stretch goal. Bugs Reported (this week) ~~~~~~~~~~~ 1) https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228444 [Kernel panic due to "exa"] 2) https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228470 [ location of struct] Differential Revisions ~~~~~~~~~~~~~~~~ 1) https://reviews.freebsd.org/D15561 Thank you, With Best Regards, Aniket Pandey P.S: The discussion regarding the project takes place on #audit-testing channel on efnet. If anybody is interested in the discussions and would like to suggest some improvements in the current approach, please feel free to join the channel! From owner-soc-status@freebsd.org Mon May 28 05:53:52 2018 Return-Path: Delivered-To: soc-status@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BCB54EFA5AB for ; Mon, 28 May 2018 05:53:52 +0000 (UTC) (envelope-from pratiy0100@gmail.com) Received: from mail-wm0-f48.google.com (mail-wm0-f48.google.com [74.125.82.48]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4BB177D8B7; Mon, 28 May 2018 05:53:52 +0000 (UTC) (envelope-from pratiy0100@gmail.com) Received: by mail-wm0-f48.google.com with SMTP id a67-v6so28791547wmf.3; Sun, 27 May 2018 22:53:52 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=nlGjp9+dc30uuoO5wnuadk6MtOEtPDEFbsHGPz3Esc4=; b=aaq+bPL4sbXOjB4X7T+CagtZYBTDYQfWOzBSVwX5Z5vGinPDq3zgxYXunm3BPy6g0Z qOCtbHpm4BQlmJ/aiGrcPBLviLwzORID51euWBRY8KYE3W8cIt+iPPvbNoAeF3e4okOR GI7U4Bt1gnly9v6o/fCQWtSAMXO+wvLVip4hrW6Mc9s4SVA/IH1qbScnX6PPx8EWayW4 RNzCcmz5w+HrXMDdvWuiDO/encTglQ/b5Zarv7IkQ/6VjsFWaf+RK8VLFkxWTg03VIYR 99SUfS1oe/PcC+W1KbMGb7UimdqlDZ4oWFK56OgSlhnUatv9qkCeRDVGF7ou10m9oIIm dKcA== X-Gm-Message-State: ALKqPwdpWhBzG9+mHbK40bzuDZ+oyleXAgYOfoKVVXqid/Eyuj5RrX+L pXkfYMGoZuHO3s7glYFCt75tJt1E X-Google-Smtp-Source: ADUXVKJujyiSLR7Cyc4CkMw56F94Ie9m/1APAYOvfVjR5CxumzeS6+I6JwWONQ8vKeFjH1t7rGDsFw== X-Received: by 2002:a50:cd03:: with SMTP id z3-v6mr5445713edi.118.1527486824875; Sun, 27 May 2018 22:53:44 -0700 (PDT) Received: from mail-wm0-f45.google.com (mail-wm0-f45.google.com. [74.125.82.45]) by smtp.gmail.com with ESMTPSA id h39-v6sm191758edb.65.2018.05.27.22.53.44 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 27 May 2018 22:53:44 -0700 (PDT) Received: by mail-wm0-f45.google.com with SMTP id x2-v6so21427224wmh.5; Sun, 27 May 2018 22:53:44 -0700 (PDT) X-Received: by 2002:a50:ad69:: with SMTP id z38-v6mr13516013edc.306.1527486824000; Sun, 27 May 2018 22:53:44 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a50:aa21:0:0:0:0:0 with HTTP; Sun, 27 May 2018 22:53:03 -0700 (PDT) From: Pratyush Yadav Date: Mon, 28 May 2018 11:23:03 +0530 X-Gmail-Original-Message-ID: Message-ID: Subject: [Week 2] Import the Xen grant-table bus_dma(9) handlers from OpenBSD To: soc-status@freebsd.org Cc: Edward Napierala , Akshay Jaggi Content-Type: text/plain; charset="UTF-8" X-BeenThere: soc-status@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Summer of Code Status Reports and Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 May 2018 05:53:52 -0000 Hi, I spent this week on writing rough initial implementations of the Xen-specific grant table handlers imported from OpenBSD. I spent a lot of time understanding the differences in OpenBSD and FreeBSD's grant-table interface. They turn out to be more different than I anticipated. After that we encountered some design decisions. Since the bus_dma(9) interface in FreeBSD is quite different from the OpenBSD counterpart, some design choices had to be made. I am still in talks with my mentors about it. I also produced rough implementations of the grant table handlers. These are not yet complete. There are a lot of rough edges to polish. Check out the implementations in my GitHub fork [0]. Unrelated to the project, I submitted a diff to remove some leftover function prototypes from the grant table header file gnttab.h [1]. I maintain a blog on Blogger where I publish my progress every few days. Check it out if you want more details on what I'm doing [2]. Regards, Pratyush Yadav [0] https://github.com/prati0100/freebsd/tree/projects/xen_bus_dma [1] https://reviews.freebsd.org/D15553 [2] http://pratyushgsoc.blogspot.in/2018/05/import-xen-grant-table-busdma9-handlers.html From owner-soc-status@freebsd.org Mon May 28 14:44:29 2018 Return-Path: Delivered-To: soc-status@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B080AEFB491 for ; Mon, 28 May 2018 14:44:29 +0000 (UTC) (envelope-from lakhanshiva@gmail.com) Received: from mail-ot0-x243.google.com (mail-ot0-x243.google.com [IPv6:2607:f8b0:4003:c0f::243]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4736372420; Mon, 28 May 2018 14:44:29 +0000 (UTC) (envelope-from lakhanshiva@gmail.com) Received: by mail-ot0-x243.google.com with SMTP id l22-v6so13708662otj.0; Mon, 28 May 2018 07:44:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to:cc; bh=d7z9fB9LYbtIeIAufwKYoYKlyjz3WySxBtvlEwI2kV8=; b=TeCCwK1SitleAEjrAkKl4ETkUUgLMwBQxDQj60/NiiIn6U6GnnOYaDtqeTuSqlUD2+ aXMvNI4p5DhDNCjHqNpq12FK2sl7djHA1u9Bbk6dSRMnkbWbyJUt4efnPcjsVmQ0Ckzq kVI+dCe8beCFmsIKknMrV+WxuY72dDHi09TrfVo2UMVfARgpKpCZpRO89tOtBlIDRSu7 V6Z9PEq15AjxoZqJUlZTvXBL0sivcoS83HerfbN7/G+pRcGbGrJrsAp7S8vd32sZFW9o uK1RNRnDib4nvYQF8wMyA1kQp3Utg5zBKXRo81hYZ6xitprKOdePf96Ax9u6xm6GolYn Nwmw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=d7z9fB9LYbtIeIAufwKYoYKlyjz3WySxBtvlEwI2kV8=; b=nslMmr2Sy/XR/nvqEA8dEyp1Ph2jAejV/5QmLf3QlX8lmuJ8+y3m3abTuEFAkh3fQ6 fI0cDUJoSWYGvI9RBAgp+enDhdwe4yufhQ/dTz3bOEy5ycQdnruc+2CePvAcQKN6A+ae zxwX2ojYbHj44x9Y3CoWOQaGba0aGCFzboQVvA19nEIgqVUhivxFDhzi1f97BYXILZ+Z VAragC3ScQqdYoc+spQQ122AQyjKj6xRf5Mk9cl6gD0YMrSQxzNuYxbkfcbwxMUcoeS4 THZnl41p2QsxgPxvj6Bly+ad0RLPzbtmC3dCOqY02Pn4XfOf+2Bca1GoGKlqEYn5UNxj k/eQ== X-Gm-Message-State: ALKqPwcCg+ejq8sTJh6q8sKisoq6j2iW3jFUzW1puW0qB9zWA8A/IE6B 6yKhPNYmS3n9tOPIbyoQF7ptZuG9g7v2/Bqri7AIMpHd X-Google-Smtp-Source: ADUXVKL17SKTehP/ZVt8C/s8Vqc8fU90ISNFz+uoDf7wM8RTRBooarXCU+vEdZKDFpVGpjv2pbdL6Mczgr6kh2tBMW8= X-Received: by 2002:a9d:9d3:: with SMTP id 19-v6mr1500707otz.324.1527518667939; Mon, 28 May 2018 07:44:27 -0700 (PDT) MIME-Version: 1.0 From: Lakhan Shiva Date: Mon, 28 May 2018 20:14:16 +0530 Message-ID: Subject: [GSOC-18] Convert all PCI drivers to be table driven and mark them with PNP_INFO - Week 2 To: soc-status@freebsd.org Cc: Gavin Atkinson Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: soc-status@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Summer of Code Status Reports and Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 May 2018 14:44:29 -0000 Hi All, Please find my Project homepage here. [1] This week I have worked on more drivers. I got time to convert ath, aacraid, ahci, an, bwn, bwi, ale. I have touched a couple of harder drivers. [2] I have added the Plug and Play information for them and found them to be used by devmatch to match them with modules automatically. There were some kernel build issues, especially for drivers which had more than one table. I have solved the issues by adding multiple PNP info tags with unique names. There is one problem though. Currently in MODULE_PNP_INFO description string, we only support upto 32 bit variables. We need to be able to support upto 64 bit variables. (uint64_t type). I will discuss with my mentor regarding this. In a couple of drivers I have added tables and modified the probe function. At the same time, I am also learning the internals of the kernel, this will help our goal ultimately - Automatic module loading. [3] Thank you, Lakhan [1] https://wiki.freebsd.org/SummerOfCode2018Projects/ConvertPCIdriverAttachmentsToTables [2] https://github.com/bsdimp/freebsd/pull/3/files [3] http://bsdimp.blogspot.in/2016/01/details-on-coming-automatic-module.html From owner-soc-status@freebsd.org Mon May 28 17:41:37 2018 Return-Path: Delivered-To: soc-status@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C75F7F737F0 for ; Mon, 28 May 2018 17:41:37 +0000 (UTC) (envelope-from uddka@student.kit.edu) Received: from scc-mailout-kit-02.scc.kit.edu (scc-mailout-kit-02.scc.kit.edu [IPv6:2a00:1398:9:f712::810d:e752]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 6436A7901A; Mon, 28 May 2018 17:41:37 +0000 (UTC) (envelope-from uddka@student.kit.edu) Received: from tr-v1239-fse.scc.kit.edu ([2a00:1398:e:28::2] helo=server-01.fs-etec.kit.edu) by scc-mailout-kit-02.scc.kit.edu with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (envelope-from ) id 1fNM9F-0006ab-HM; Mon, 28 May 2018 19:41:35 +0200 Received: from Chris-TP (unknown [IPv6:2a00:1398:5:ee00:60d7:1374:864:93ee]) by server-01.fs-etec.kit.edu (Postfix) with ESMTPSA id 24908188EE0; Mon, 28 May 2018 19:41:33 +0200 (CEST) Date: Mon, 28 May 2018 19:40:54 +0200 From: Christian =?ISO-8859-1?Q?Kr=E4mer?= To: soc-status@freebsd.org Cc: Chuck Tuffli , Luiz Otavio O Souza Subject: User space interface for GPIO interrupts / Status Report Week 2 Message-Id: <20180528194054.b44df7621d933376ee686dde@student.kit.edu> X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.32; amd64-portbld-freebsd11.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: soc-status@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Summer of Code Status Reports and Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 May 2018 17:41:37 -0000 Dear all, since my last status report I implemented dynamic reconfiguration of the monitored pin and also started to write user space tools [1] to communicate with the gpiointr device driver [2]. Furthermore the gpiointr driver was moved away from simplebus, so that one instance of the gpiointr driver is now attached to each gpio controller. As a result no modified DTB file is needed any more and all GPIO pins can be configured in a consistent way like gpio(3) and gpioc. The configuration of, for example, pin 5 on gpiobus0 looks like this: $ gpiointr_config -f /dev/gpiointr0 5 Monitoring of the pin is still done by a read() syscall that will block until an interrupt on the pin is triggered. During this week I am going to implement locking mechanisms in order to avoid race conditions and start to move forward to dynamic resource management to be able to register interrupts for multiple pins on a specific gpiobus. Additionally the trigger type will become runtime configurable. Thanks, Chris [1] [2] From owner-soc-status@freebsd.org Mon May 28 20:28:05 2018 Return-Path: Delivered-To: soc-status@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 61466F94B3C for ; Mon, 28 May 2018 20:28:05 +0000 (UTC) (envelope-from duostefano93@gmail.com) Received: from mail-io0-x232.google.com (mail-io0-x232.google.com [IPv6:2607:f8b0:4001:c06::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id EE1FC83458 for ; Mon, 28 May 2018 20:28:04 +0000 (UTC) (envelope-from duostefano93@gmail.com) Received: by mail-io0-x232.google.com with SMTP id g1-v6so15219234iob.2 for ; Mon, 28 May 2018 13:28:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=Qkhgsn8kEOmD7iO66c5WiQn/gYq71TllSujC91Jmq68=; b=CTAs1BnG1JUzan4BbE3LWe9XueCxPSchxyOOdUTZPx/y+EBQ2DDL9Ry+VmslqyytZG lYPzWCF0OelQIOTuqYBk1JU7TWmDX1zO0K/DUWxLzW6Pw2qLlcN5T948YN/X3GquziPz aba2mUDoEurTC7eWMQaXFL+m+YeItLPapLSComybYVSO+NIj85ZNRRwekmbIWv7rUVXv Yed7zwKq1rgOSw4FcLjVS40ZakgtYMP+JESdOqZFM71RYvDYuxvUKRcZ9bQYi/1v6jgd tAtk8+MRDbnAvbojXTMrSFz5kRuk4wqr2h9ibUxkQ0NO4McaUC+5FyUAscRfrg1jyKVy wp7Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=Qkhgsn8kEOmD7iO66c5WiQn/gYq71TllSujC91Jmq68=; b=E3DkFsOjOA1cgiCIFLNVcOR0Mvs3sSY38WuMnBNA4d3eMzaxmfhHD3lM2FDKSI65R0 Z7m8uaIKeNsXDo66xjeGeh2COb5yfVYovMW4wDpZzKcF3LD8/K1jLt+km1BEcs4ZHoOa pOmrkMtDNB8DMgB96PMJXSnBNtEwNDwMfjvEG3a0oTQFyam+/N4aOQLPa+G2ce+Kljwp +hwnPHkjArLB+PNHf0inGU8shtkYEk5uFFKv4bVuU+9AGCvbFauNgKcUf/KfVKf12SBk 7CWMMWVQVfGWnEifan1Ziu7X6oot5jd+AM8FSL/W+T9oBaMblLMGAj3wMRhDS/FBkpFG C8kw== X-Gm-Message-State: ALKqPwdz4Mo3jaD8G6FxUaz6Am58pDnA1tesUlSbTNLlfmLNZL4LKwtq aOzXjO+x7Y8OGBfuvA/OJ3J92wOViT3JrMl2KMTw9jA9 X-Google-Smtp-Source: ADUXVKIZNeEV+F70rX+A5zsQajRDyA+mWRsK967i1REmHQ3EnLE9XhfhNk6bmjHVLQIJkXLGh5ZszBG6kqrwpMR2DAw= X-Received: by 2002:a6b:db15:: with SMTP id t21-v6mr11529521ioc.224.1527539284142; Mon, 28 May 2018 13:28:04 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a02:c44:0:0:0:0:0 with HTTP; Mon, 28 May 2018 13:28:03 -0700 (PDT) From: Stefano Duo Date: Mon, 28 May 2018 22:28:03 +0200 Message-ID: Subject: Extension to the netmap framework - Week 2 To: soc-status@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: soc-status@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Summer of Code Status Reports and Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 May 2018 20:28:05 -0000 Hi, during the second week i extended the vale_vlan kernel module. VLAN configuration can now be created (modified and read) through system calls on the device "/dev/vale_vlan". First a VLAN configuration must be selected though an ioctl(), which expects a "struct vlanreq_header". Then commands are issued to the configuration through a write(), which expects an array "struct vlan_conf_entry". An array of commands is considered atomic, therefore if one of them fails, the status of the configuration is rolled back. Finally the current configuration can be read though a read(), passing an array of "struct port". The data structures used by the interface between user and kernel space are defined in "net/vale_vlan_user.h". Project wiki: https://wiki.freebsd.org/SummerOfCode2018Projects/ExtensionsToNetmap SVN repository: https://svnweb.freebsd.org/socsvn/soc2018/sduo/ Stefano. From owner-soc-status@freebsd.org Wed May 30 12:00:06 2018 Return-Path: Delivered-To: soc-status@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4FCB1EF39BE for ; Wed, 30 May 2018 12:00:06 +0000 (UTC) (envelope-from mateus@mateus.tech) Received: from NAM02-SN1-obe.outbound.protection.outlook.com (mail-sn1nam02on0112.outbound.protection.outlook.com [104.47.36.112]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "mail.protection.outlook.com", Issuer "Microsoft IT TLS CA 4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6AE5A7EF1E for ; Wed, 30 May 2018 12:00:05 +0000 (UTC) (envelope-from mateus@mateus.tech) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mateusrodrigueslive.onmicrosoft.com; s=selector1-mateus-tech; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=MLN+Upt8pdL2bTvNhUr+W7DjRqAlNI8juUqRsYVaRTM=; b=LZXCATSmtnXexkSV6XJqWemnZcl/tQU1oGEQNZQq/kx8OqRERQhwaijXp06CNabd2H85NXKdan6FkwUr2OpwrjM4luPCxHeCB4PQkPK1MjwW6Ws3pJ7Qgb+WBHMYDw9gDtcYY+YCvZvuCkF/RpF+BrsmQMPOWw2REjW6ryqxbOY= Received: from FR1P152MB1126.LAMP152.PROD.OUTLOOK.COM (10.171.43.11) by FR1P152MB0019.LAMP152.PROD.OUTLOOK.COM (10.167.135.145) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.820.11; Wed, 30 May 2018 11:59:59 +0000 Received: from FR1P152MB1126.LAMP152.PROD.OUTLOOK.COM ([fe80::e50f:ee4e:bc5c:153f]) by FR1P152MB1126.LAMP152.PROD.OUTLOOK.COM ([fe80::e50f:ee4e:bc5c:153f%3]) with mapi id 15.20.0797.017; Wed, 30 May 2018 11:59:59 +0000 From: Mateus Rodrigues de Morais To: "soc-status@freebsd.org" Subject: [Week 2] Porting Microsoft's CoreCLR, CoreFX, and PowerShell to FreeBSD Thread-Topic: [Week 2] Porting Microsoft's CoreCLR, CoreFX, and PowerShell to FreeBSD Thread-Index: AQHT+A2xoRXSFayIbEeRfFw9/9wwjQ== Date: Wed, 30 May 2018 11:59:59 +0000 Message-ID: <53b447f3-9a16-345a-bedc-2dac4e9489af@mateus.tech> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ms-exchange-imapappendstamp: FR1P152MB1126.LAMP152.PROD.OUTLOOK.COM (15.20.0797.000) x-originating-ip: [177.20.152.120] x-ms-publictraffictype: Email x-microsoft-exchange-diagnostics: 1; FR1P152MB0019; 7:Hz09xkTVc0HD8NJUxTMKicKz+civNBRjNIlSPeJ/I9o9gpPlZcgEDl+85Mo5OxTPRk7gE8OQZ1JRaHpC8Q89E6cIJlKkhYKA5/tc59ORAfR9VeZHukmSD3oN3lK33uGjOF4semnicCPS15nazziqrXlCeiaBPKUUAH5rnV6353Mn49jYAG5Wf3H+t/ySH0j8Gi006FHyCOaf2F8RhqY1tQe/pDw2lVxPWfwB1XZ6eFf30pB3aJtMZB2h82E8n0bG x-ms-exchange-antispam-srfa-diagnostics: SOS; x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(7021125)(5600026)(4534165)(7022125)(4603075)(7168020)(4627221)(201702281549075)(7048125)(7024125)(7027125)(7028125)(7023125)(2017052603328)(7153060)(7193020); SRVR:FR1P152MB0019; x-ms-traffictypediagnostic: FR1P152MB0019: authentication-results: spf=none (sender IP is ) smtp.mailfrom=mateus@mateus.tech; x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:; x-ms-exchange-senderadcheck: 1 x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040522)(2401047)(8121501046)(5005006)(93006095)(93001095)(10201501046)(3231254)(2017060905117)(944501410)(52105095)(3002001)(149027)(150027)(6041310)(20161123560045)(20161123564045)(20161123562045)(20161123558120)(2016111802025)(6043046)(6072148)(201708071742011)(7699016); SRVR:FR1P152MB0019; BCL:0; PCL:0; RULEID:; SRVR:FR1P152MB0019; x-forefront-prvs: 0688BF9B46 x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(39380400002)(39830400003)(396003)(366004)(346002)(376002)(47530400004)(199004)(53754006)(189003)(14454004)(52230400001)(59450400001)(5660300001)(2906002)(2616005)(486006)(3280700002)(476003)(105586002)(3660700001)(31686004)(106356001)(3846002)(99286004)(6916009)(26005)(2900100001)(5640700003)(102836004)(68736007)(6116002)(186003)(36756003)(6436002)(6486002)(316002)(97736004)(8936002)(86362001)(31696002)(2501003)(5250100002)(55236004)(6512007)(8676002)(25786009)(6506007)(66066001)(81156014)(305945005)(7736002)(81166006)(478600001)(53936002)(45080400002)(2351001); DIR:OUT; SFP:1102; SCL:1; SRVR:FR1P152MB0019; H:FR1P152MB1126.LAMP152.PROD.OUTLOOK.COM; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1; received-spf: None (protection.outlook.com: mateus.tech does not designate permitted sender hosts) x-microsoft-antispam-message-info: HjWckd4NBqwJ4eYe48p6/57cnqces0L7ge2BhtxnTp+jOenRSzvdaU3UdxGBiffynwtaZ+GeqpnVlV5stCJ4mcZ+Xe9ViSc4CW8xQhtgcgBVZrIW5rjOeQkQBUvPf+BykqBZkoTw97v0AlPRmgQTdOn7uFa6Nks96t3YxXCyuhI55AydfvoAxWVAVDydBd84 spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM Content-Type: text/plain; charset="iso-8859-1" Content-ID: Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-MS-Office365-Filtering-Correlation-Id: 90afeb33-dc5d-4251-c567-08d5c624de56 X-OriginatorOrg: mateus.tech X-MS-Exchange-CrossTenant-Network-Message-Id: 90afeb33-dc5d-4251-c567-08d5c624de56 X-MS-Exchange-CrossTenant-originalarrivaltime: 30 May 2018 11:59:59.1956 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 3cb2d6d7-8d6e-44b8-954d-3085729d2030 X-MS-Exchange-Transport-CrossTenantHeadersStamped: FR1P152MB0019 X-BeenThere: soc-status@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Summer of Code Status Reports and Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 May 2018 12:00:06 -0000 Hello all, During this second week of work, with help from the .NET community, I=20 managed to get the CoreFX native components to build on FreeBSD, which=20 brings the effort a step closer to a complete FreeBSD support. Also, while in touch with the Microsoft people, we gathered a list of=20 items that should be completed in order to make the product ready for=20 production. This checklist will be helpful when I start polishing the=20 rough edges to finally port the software to FreeBSD. Right now, I'm still working on building a functional .NET runtime/SDK=20 on FreeBSD. It involves many different components that are all available=20 open-source -- including CoreCLR and CoreFX which are already building=20 on the platform. Best, --=20 Mateus From owner-soc-status@freebsd.org Sat Jun 2 00:18:37 2018 Return-Path: Delivered-To: soc-status@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 41F35F722FA for ; Sat, 2 Jun 2018 00:18:37 +0000 (UTC) (envelope-from shubhgupta2104@gmail.com) Received: from mail-oi0-x231.google.com (mail-oi0-x231.google.com [IPv6:2607:f8b0:4003:c06::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id CDF307EACA for ; Sat, 2 Jun 2018 00:18:36 +0000 (UTC) (envelope-from shubhgupta2104@gmail.com) Received: by mail-oi0-x231.google.com with SMTP id 14-v6so15914279oie.3 for ; Fri, 01 Jun 2018 17:18:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=wpsHY+T2880NRvVZY/rGo40Z+dKuJ65qHbOvHn/ToJc=; b=IwoxBq0xzTvfyjRsOd+4Yv4bV91a3HvxDbJEvpmttfcEXf5kTGh6BgOg0sljBDKbPf zvkrYrUkdE6Ss0LCL8otXscEHjdJJJKXFDbBkgB4/barmD9dAvVtM75DaGcPwkFdpy3E GqLD3U3fP+htplIGs1IygZSQf/tSd0p1J45bZUJR4nvzWJyh+Wp8InUoubUr0QJksMC1 J9EODvZpqgKKe4y3xG2fHfCgOtxigiCyL5MC/nkNOlVIgqYa5597JHPpgbXBjqDC8Bgu v/oHWOsVkUzh8mtiyLjM9MjOKzsDb4kIG3Lq7wRirS1/5MbZX7HSDkJE63bKP8FpNbt7 IEKQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=wpsHY+T2880NRvVZY/rGo40Z+dKuJ65qHbOvHn/ToJc=; b=Wq+b9y/K8pn7yl7H9YBfFv0IXXgvZlC05mqtyQVRNVpZk++QGS5Gg1Q+BWZk1WMW1H LXmox4ZK89C6C3pQD93f//jlTti9zLGKtQ8+0XSfzLnsKjvk2ffgwt/JzxS84muVyKK3 NtjcEnLif/wYMnIH8AudrIkpS0DQiN/5alRen5M1Cewfbbf4kKlR2Q9RsjryJznddEj+ 0lgGfITKIfxfV3zc+AiYG2HEfZ0N4ABq67MHpHYl3GGVSv+xi8qzMiEiD+QygtJvpB9u hfCUXcrXcY2GRtTeTbtJ/R7MYzZPmMppfvdftYX+U5Z6pnhrkRRGQVq0q3JiTo1hPun7 Fnag== X-Gm-Message-State: APt69E05vP4BCaObydT/tZcLwUkm1Ipd2fVRCB8o0jAmopDvfDxuiYqa hGUtEaCey/HYBaJyXMRQdv3oTlhKEhKeDSKIKpw= X-Google-Smtp-Source: ADUXVKIakgf5daOuApViYA4aznyGdyYKzWQA7DXUnRIvXlSd6abd6w68s537I/uFCo4rdiyq2Uc/0MnepEmv4FtwCAo= X-Received: by 2002:aca:674b:: with SMTP id b11-v6mr7718362oiy.249.1527898716016; Fri, 01 Jun 2018 17:18:36 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:ac9:424b:0:0:0:0:0 with HTTP; Fri, 1 Jun 2018 17:18:35 -0700 (PDT) From: Shubh Gupta Date: Sat, 2 Jun 2018 00:18:35 +0000 Message-ID: Subject: Weekly Report To: soc-status@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: soc-status@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Summer of Code Status Reports and Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Jun 2018 00:18:37 -0000 I have been working on integrating libpreopen and capsh, and providing capsh the functionality to preopen all the files given in the argument(tries to preopen the argument even though it may not be a file) such that those files can be traversed and read after we have entered into the capability mode. All this time, I was trying to figure out how could capsh leverage libpreopen. 1. I included libpreopen.h in capsh/src/platform/FreeBSD.hh 2. I made the po_map in FreeBSD.cc when arguments were being parsed and preopened all the arguments into file descriptors and made a po_map_entry corresponding to each of the files. 3. Initially, I was trying to open the directory in which the argument file was present so that the openat wrapper call for open could be used. But, i observed directories like ".." could not be preopened because of the capability mode. hence i had to make some changes in the open wrapper function and hence the preopening of the file was made possible. 4. The shared memory map which was packing the po_map into the shared memory was not able to unwrap from the shared memory, where I figured out that the close-on-exec flag had to be passed for this to be made possible. The result is, that I am able to leverage the functionality of cat, in the oblivious sandbox, wherein it gets just the resources it requires, which was the goal of my first evaluation. The results can be seen in the latest commits on my repositories which are mentioned in my wiki. I have deleted the lame commits that I had made earlier and made the latest commit as the final working one, encompassing all the good work in just one commit. Now, I am beginning to work on the stretch goal for my first evaluation, i.e making it possible for telnet to run. The plan that I will follow for telnet will be: 1. Just like files, make it possible for the sockets to be pre-opened as descriptors. 2. Figure out what extra resources telnet might need to leverage the functionality of an Oblivious Sandbox, which would be provided before entering into the capability mode. 3. Implement the third entry in po_map_entry which specifies that the preopened descriptor is a file or a socket. From owner-soc-status@freebsd.org Sat Jun 2 13:18:17 2018 Return-Path: Delivered-To: soc-status@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 92A82FDCBD2 for ; Sat, 2 Jun 2018 13:18:17 +0000 (UTC) (envelope-from sudh.cse@gmail.com) Received: from mail-io0-x241.google.com (mail-io0-x241.google.com [IPv6:2607:f8b0:4001:c06::241]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 252588115D for ; Sat, 2 Jun 2018 13:18:17 +0000 (UTC) (envelope-from sudh.cse@gmail.com) Received: by mail-io0-x241.google.com with SMTP id a10-v6so32865041ioc.9 for ; Sat, 02 Jun 2018 06:18:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=BpcDr/S3ubY/ajRAAQNacjnOrju+NpreY//ruKPTyKo=; b=apXbNauKsP1RRXywiIteJOzZFWH2/EpHG7ipBnkAFQU39qyVkXHTpVyImPC8WmveHr uDRLK5Q8tSSOFAdK8m0Qt/ke9UM4LH/64nAtgkGGbApQDDSY/KRdGrRbYo1DTqMKB5C0 ioku7kEH0Xiqr/GNpn/BQ8qHzvx6rDZJ37dmvqkcbikfqtibk0j2cI/H4vKC2U2ob1NI LhXQBZu2UfaSsuPPmkU/2J37DOmdSpZxah+lRIDFYh6z1JELBfPC1IrR1YhLnQxKNKnH cGU3yYDxX7vd7/3x5GUbSAK3xqF6TMQVd+k3UdpGmS8fu67qA9s9vcvL1teDdP4LKhm9 XvEQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=BpcDr/S3ubY/ajRAAQNacjnOrju+NpreY//ruKPTyKo=; b=a9/xFsXSHUzIPegz6k6QGaXaD6jLos0wM6pvpjIAb+aWzVsG3aPSmObtG3IZoW7hfX eBW70yYk2KbvBe+ZdeOO83FJHCOGYlN7j4mweUJcZaxiuJeOfRaM80EDES90WRBVsH0e zxfz+uIOP7jpwmSnyRFVHPVr/s92jIJWutGQOnd01rh5pBdl2yHYQsRtDyGfvX9pMRn1 LpDM8MAUCyoI2Y9T4VsxCykJgedXxrQsXBsYXLIq6xIf1qQ66isatu8EeQMUaWTj6u7z X0Jz2Cv13cBDHBnJHTY/iQEZtKTKzXpvkdOJn/e1kVoqVEhbpKK2034X5nD4qJ4fN7M8 jH9w== X-Gm-Message-State: APt69E2MUjpGRJ9lRXWAj/oNF+7FLq7FPEHmjctPVjQJoDxoKD694G3H GHp9UPYxxQCNgIJ3Rl5DhrpaXgxn52Sz41SDqMf7hA== X-Google-Smtp-Source: ADUXVKJ8819f5pfcEBr4RAD4IkEXYknwcGucgJbhe5/tgqDuwuCE3vSVKamPXaYNcvkga6diTL9iN9dRXYYC4CJjE7g= X-Received: by 2002:a6b:6208:: with SMTP id f8-v6mr2273846iog.11.1527945496312; Sat, 02 Jun 2018 06:18:16 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a02:1802:0:0:0:0:0 with HTTP; Sat, 2 Jun 2018 06:18:15 -0700 (PDT) From: Sudhanshu Saurav Date: Sat, 2 Jun 2018 18:48:15 +0530 Message-ID: Subject: Regarding Progress of my Gsoc 2018 project To: soc-status@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: soc-status@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Summer of Code Status Reports and Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Jun 2018 13:18:17 -0000 Hello Everyone! This is Sudhanshu (capreyon) working on FreeBSD project Verification of bhyve Instruction emulation. You can see the progress of my project on *https://github.com/Capreyon/Test-harness-for-bhyve-instruction * Initially I had spent a lot of time in reading the documentation of Intel XED, Actually, I thought that I have to convert all the bhyve instructions by using functions and libraries present in Intel XED and then compare it but I am very thankful to my mentor he guided me very well and clear my doubts regarding this. In my repository, I modify the Revision 240941 to Revision 254964 till now and on the way of writing the stubs, drivers, and tests for these Instructions and also verified it using Intel XED. I am facing a problem currently the first one is, Running the bhyve Instructions in userspace. If there is any manual present on how to run bhyve Instructions in Userspace/Userland please provide me for this I am thankful to you. Thanks, Sudhanshu [image: Mailtrack] Sender notified by Mailtrack 06/02/18, 6:22:47 PM