From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id A05A927587C for ; Mon, 19 May 2025 12:30:45 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=170.10.129.124 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1747657850; cv=none; b=AK2UWlavpd5YpCYFYMon+5sktwpXfctsJQYuskB1+6yVzFsGRZvriXCrgAFu4pvGGqErSwj2AOH/mC6G2ep7s76JIPXdSS/Bkrdkp9iK/oYi8L57BD+jzbaSl38EWcRJ9oxXGCdWo+WbAZrV2hceBNnvni3md9eymax3uQDXkFE= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1747657850; c=relaxed/simple; bh=cjmIuppiw3ZfVZeRQUzXzpW2c0/PI1s4TY/CoiOGaSc=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: In-Reply-To:Content-Type:Content-Disposition; b=IhrIVJDbBXaVl/O1hjdoDqJBxZQhlyTdfvEOSiAOwxlQA4FMYhGfVEsda7iBVJ4pxNhCUjo3jUSj/Qk4W0gWY/Nvcp5rnBll6ofgtIPwWZHJqx9uyOkh4rUXOIOr3enDwLCTh99L9a3Ma8sQGn2o+UuH48omucA9QoAHelfL5UU= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=redhat.com; spf=pass smtp.mailfrom=redhat.com; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b=I+BGMWQU; arc=none smtp.client-ip=170.10.129.124 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=redhat.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=redhat.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b="I+BGMWQU" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1747657844; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=mMzdHr/O71dzg2i0/IqeRVkSu7FOn4cczFEMrikDdIs=; b=I+BGMWQUOTiFIvbd07m78UWcD73n99I8fb3d3JSVqz15uZWaE2NGXzaF7CUXdFdicBt7u4 vYum830Hj6mzm2io0CbU0+KwcDzt9ru0lCjx8ZxScialbfCee4HtScofsGym804t7Y+Xl8 UsVyraCQjB4o48CrHXKM1zm4mU0zl5k= Received: from mail-wr1-f72.google.com (mail-wr1-f72.google.com [209.85.221.72]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-9-5tav1_8-OySsAVLMaFCkaQ-1; Mon, 19 May 2025 08:30:41 -0400 X-MC-Unique: 5tav1_8-OySsAVLMaFCkaQ-1 X-Mimecast-MFC-AGG-ID: 5tav1_8-OySsAVLMaFCkaQ_1747657840 Received: by mail-wr1-f72.google.com with SMTP id ffacd0b85a97d-3a360d01518so2396315f8f.2 for ; Mon, 19 May 2025 05:30:40 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1747657840; x=1748262640; h=in-reply-to:content-transfer-encoding:content-disposition :mime-version:references:message-id:subject:cc:to:from:date :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=mMzdHr/O71dzg2i0/IqeRVkSu7FOn4cczFEMrikDdIs=; b=TKByhbcbiN6B8rnSuJhN7/q4KelcWnPAnGMCFfa6LD9u9wrbbCPcZVQvt3LhyRSkPu CW4IHBBrSlPFcfQUInMk6oSFoKCf2sg7485aq0MLleyHTCm7UrX6PXAehubtpj5hNWKc W6PyzAahXzHhfrqDQLf3u9EqvTuXEp3Hh7HIOMd9OAqZfW7w2IbdhNpXo2mqMr5x+jlZ kaMe8Q/8/5IFcLUmI8E/opfwaBuzYCzGJeEmAYu6nXJdkzsy2ccjZ2XggIhbf4T8rLFR jTwcFOG/xYmJvou9QI28mO+2Td3Hmx5BUAz5/ISGAWJMpZKPXGY/HRDm3aViZfM6r7Xk Eldg== X-Gm-Message-State: AOJu0Yz6kS5e99S1f8L283JNJuhwg6XpLJkSg1bc6JcIKJ5HTKCO2sk4 cIY9hk3vHP2hGyMCbd10ZrVuZqPKHxojN9RhnnH+E6e8/LgfIj7liqRPWtCgWCoaoswW8l7G/Xp fyqbdELomr+RTu9Rlwn0AUbhhrasxQgUIylYh7Fd565yQzFqkRjoVDEzIjo+YtnZOScew X-Gm-Gg: ASbGncuKqBaeoLXCaqBhVK/vc/a99uPQbnSjpZH80+/u9JNtB6KPjd3otGGG2N5DiyI OrbQfAcA6yb1O6EQasGa3LxBTJTZTrRdArXmKbCGfwDIAVszOLJ+6DUmGgIkppSzglACjaqszOR i3skAbe3ia/lHXPttAEjYYZvXKiLzCOLpGsI86wmBWjWLLKL/6XUa4VuW2yYFyUixe8rPpZiwTm VvG/N4iqrAfdhRfgsisWAhikrgYpLLWzLWYy3Tww4o8WV2i0BCW37irzaI7AP0TuStb1EoAtKUd 2+86SQ== X-Received: by 2002:adf:f30f:0:b0:3a3:60f0:e2eb with SMTP id ffacd0b85a97d-3a360f0e520mr8699396f8f.33.1747657839986; Mon, 19 May 2025 05:30:39 -0700 (PDT) X-Google-Smtp-Source: AGHT+IFnor2EOpFboeqwlA8m+khJQ/6TlnD4f82+4QfCj9mUYV/zj5uEb4JZVo+3adLk8MZfoqSzsw== X-Received: by 2002:adf:f30f:0:b0:3a3:60f0:e2eb with SMTP id ffacd0b85a97d-3a360f0e520mr8699358f8f.33.1747657839472; Mon, 19 May 2025 05:30:39 -0700 (PDT) Received: from redhat.com ([2a0d:6fc0:1517:1000:ea83:8e5f:3302:3575]) by smtp.gmail.com with ESMTPSA id ffacd0b85a97d-3a35ca5a5b4sm12521119f8f.21.2025.05.19.05.30.37 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 19 May 2025 05:30:38 -0700 (PDT) Date: Mon, 19 May 2025 08:30:36 -0400 From: "Michael S. Tsirkin" To: Manos Pitsidianakis Cc: virtio-comment@lists.linux.dev, VirtIO Dev List , Bill Mills , David Hildenbrand , Stefan Hajnoczi , Stefano Garzarella , Dmitry Osipenko , Sergio Lopez , Cornelia Huck , Alex =?iso-8859-1?Q?Benn=E9e?= Subject: Re: Central repo for VirtIO conformance tests? Message-ID: <20250519082712-mutt-send-email-mst@kernel.org> References: <87semtpjrt.fsf@draig.linaro.org> <20250519034810-mutt-send-email-mst@kernel.org> <20250519041030-mutt-send-email-mst@kernel.org> Precedence: bulk X-Mailing-List: virtio-comment@lists.linux.dev List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 In-Reply-To: X-Mimecast-Spam-Score: 0 X-Mimecast-MFC-PROC-ID: mkPMlj_bXIGbUFAVJqu8LFkFtO9E3v5HGYvDSd36yo4_1747657840 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit On Mon, May 19, 2025 at 11:18:36AM +0300, Manos Pitsidianakis wrote: > On Mon, May 19, 2025 at 11:15 AM Michael S. Tsirkin wrote: > > > > On Mon, May 19, 2025 at 11:03:43AM +0300, Manos Pitsidianakis wrote: > > > Hello Michael, thanks for the reply, > > > > > > On Mon, May 19, 2025 at 10:54 AM Michael S. Tsirkin wrote: > > > > > > > > On Mon, May 19, 2025 at 10:43:33AM +0300, Manos Pitsidianakis wrote: > > > > > Pinging this thread to ask the OASIS people: Would it be possible to > > > > > host a software project (this testsuite) under OASIS but with a > > > > > lighter contribution process? We expect everyone to be contributing to > > > > > them, from open source/proprietary hypervisor developers, to kernel/OS > > > > > developers, hobbyists and professionals alike. So I think a low > > > > > barrier of entry would be reasonable here. > > > > > > > > Take a look here pls: > > > > https://www.oasis-open.org/open-repositories/#licensingRules > > > > > > > > > > > > > > > > > Seeing as a test suite is essentially tied to the published VIRTIO > > > > > spec itself it also makes it a good fit semantically. Having a suite > > > > > with multiple VIRTIO implementations including slim images with Linux > > > > > would also give a wider frame of reference for downstream consumers of > > > > > the spec. Currently, the Linux kernel is the de facto (because it's > > > > > also open source) VIRTIO implementation on the frontend side and > > > > > oftentimes we end up looking at what Linux does to implement backends. > > > > > > > > > > We'd like to potentially: > > > > > > > > > > - Expand the array of rootfs images with more Linux userspace tests > > > > > for more devices > > > > > - Expand the array of rootfs images with other open source OSes as > > > > > they gain VIRTIO functionalities > > > > > - Implement missing VIRTIO spec features in our unikernel test and > > > > > also exercise realistic but basic VIRTIO command use scenarios for > > > > > more devices > > > > > - (This is on my personal wishlist) write a VIRTIO fuzzer framework, > > > > > similar in spirit to Google's syzkaller project (unsupervised > > > > > coverage-guided kernel fuzzer) > > > > > - As a stretch goal, provide a reference test runner framework to run > > > > > the images with QEMU and rust-vmm vhost-user backends for people to > > > > > adapt to their setups. > > > > > > > > > > PS: The git repositories Alex linked are temporarily inaccessible due > > > > > to internal unrelated issues, and will be public again. > > > > > > > > > > > > At the moment, from the above link, and if you want it tied to OASIS > > > > open repositories, it has to be one of: > > > > > > > > BSD-3-Clause License (which shall apply if the TC makes no license selection in its approval action); Apache License v 2.0; CC-BY 2.0; CC-BY 4.0; Eclipse Public License v 1.0. > > > > > > OK that's doable and completely reasonable. > > > > > > > I am not a lawyer, but can full OS images we licensed under one of > > > > these? If not, you are better off creating the repository itself outside > > > > the confines of OASIS. > > > > > > We'd be hosting essentially build recipes for the images, for tests > > > where we use other people's code. The build recipes would have the > > > same license. > > > > > > If I understand the CLA requirement correctly, even if the > > > contribution is merged by a maintainer who has signed the CLA, the > > > original contributor who has no write access to the repository, has to > > > sign the CLA as well? > > > > > > I think is would be the OASIS equivalent of the Linux DCO: > > Each person making a repo contribution must be bound to the terms of the > > CLA, by obtaining their signature (which may be an equivalent electronic > > assent) > > So just a Signed-off-by? That massively simplifies things! Well we need to make sure people read CLA and know what it implies. Which unfortunately I can not tell you what it is since CLA at OASIS site is down: https://www.oasis-open.org/resources/open-repositories/cla/individual-cla I will reach out to OASIS to figure it out. > > If you like I can reach out to OASIS to confirm. > > Yes, that'd be very helpful, thank you. > > > -- > Manos Pitsidianakis > Emulation and Virtualization Engineer at Linaro Ltd