Received: by 2002:a25:8b91:0:0:0:0:0 with SMTP id j17csp17234047ybl; Thu, 2 Jan 2020 01:14:30 -0800 (PST) X-Google-Smtp-Source: APXvYqxF4b7gVk/TF8omueTrlsIfPg7jap0zB6UYtc9/pNI8kugLpf1lZiU63DBimxJQQz5cOIHn X-Received: by 2002:a05:6830:1bf2:: with SMTP id k18mr88656214otb.36.1577956470186; Thu, 02 Jan 2020 01:14:30 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1577956470; cv=none; d=google.com; s=arc-20160816; b=B7rC1WTkfEBplIm0GSzfuUW7sfKeflsKxTJUzqNSklSE31ptICONuAhXzIDFLc4X48 rcHq6NQ97MYEFLoW8WhWqybTTrzoGRLOMRrOWGhosCx0FbK4JNG819+YU9XMnAO/TKNI 0MZKaxTce+1RIdiaKeVMlfNlctDMNJK2uNoFgN2bw0W/ip4LyaStd4km6bgOQiAxiCbh LUTXv4CSzz9oegKc3VPlZhLazyVnZjYbwBQndrebQOOqz+R+iI9vYFiYJxVe4ViPBMqr FbgkVJxawQEgJSTlLHxsVSqZSyh53jw2BWV7ZwsoxxoMxsWVWYlcdsibVnUkmtfE8t9f 0pEA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-language :content-transfer-encoding:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject; bh=rBMw402AoOSpPJUfzAwgpvmIhXE3jsKODsiDXDx/nzM=; b=tuB+yO/oWlnQp8NmOUV9JjQEGjF8RN2h6wRdFHeGqQd9xStLA63k9SOlnd+P3FURWr kjWAMM+O4hwOY5Ts7vzSqqeoc9QA1Jazg2TYZ+CeOcb9YvReeRN1CCl3wV9AyxrayYbQ xgzEvWlVJ/gpdCDuORis5bsYA8xsaFLtvWi3uLEAW1Ib0NOay5OWY2+9YD4bXVTI0lVX VAvlLYkWWFRtAi2bnx6gjrHuM05qcqMhUtPyRNxwPIBGuD5WLJwriYUg93vL2JXhqyD4 fvQNmR7DdGeAwVdfYBcZpfv3iHsauRhTbNhgkrNy63U1bCW6eR0S4zVBx3A/ZY7CSqh3 uYeA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id n203si25327625oia.112.2020.01.02.01.14.16; Thu, 02 Jan 2020 01:14:30 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727891AbgABJNc (ORCPT + 99 others); Thu, 2 Jan 2020 04:13:32 -0500 Received: from mga07.intel.com ([134.134.136.100]:44707 "EHLO mga07.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727801AbgABJNc (ORCPT ); Thu, 2 Jan 2020 04:13:32 -0500 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga008.jf.intel.com ([10.7.209.65]) by orsmga105.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 02 Jan 2020 01:13:30 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.69,386,1571727600"; d="scan'208";a="214099642" Received: from liujing-mobl1.ccr.corp.intel.com (HELO [10.238.130.173]) ([10.238.130.173]) by orsmga008.jf.intel.com with ESMTP; 02 Jan 2020 01:13:28 -0800 Subject: Re: [virtio-dev] Re: [PATCH v1 2/2] virtio-mmio: add features for virtio-mmio specification version 3 To: Jason Wang , Zha Bin , linux-kernel@vger.kernel.org Cc: mst@redhat.com, slp@redhat.com, virtio-dev@lists.oasis-open.org, gerry@linux.alibaba.com, jing2.liu@intel.com, chao.p.peng@intel.com References: <85eeab19-1f53-6c45-95a2-44c1cfd39184@redhat.com> <28da67db-73ab-f772-fb00-5a471b746fc5@linux.intel.com> <683cac51-853d-c8c8-24c6-b01886978ca4@redhat.com> From: "Liu, Jing2" Message-ID: <42346d41-b758-967a-30b7-95aa0d383beb@linux.intel.com> Date: Thu, 2 Jan 2020 17:13:28 +0800 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.3.1 MIME-Version: 1.0 In-Reply-To: <683cac51-853d-c8c8-24c6-b01886978ca4@redhat.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org [...] >>> >>>> + >>>> +/* RO: MSI feature enabled mask */ >>>> +#define VIRTIO_MMIO_MSI_ENABLE_MASK    0x8000 >>>> +/* RO: Maximum queue size available */ >>>> +#define VIRTIO_MMIO_MSI_STATUS_QMASK    0x07ff >>>> +/* Reserved */ >>>> +#define VIRTIO_MMIO_MSI_STATUS_RESERVED    0x7800 >>>> + >>>> +#define VIRTIO_MMIO_MSI_CMD_UPDATE    0x1 >>> >>> >>> I believe we need a command to read the number of vectors supported >>> by the device, or 2048 is assumed to be a fixed size here? >> >> For not bringing much complexity, we proposed vector per queue and >> fixed relationship between events and vectors. > > > It's a about the number of MSIs not the mapping between queues to > MSIs.And it looks to me it won't bring obvious complexity, just need a > register to read the #MSIs. Device implementation may stick to a fixed > size. Based on that assumption, the device supports #MSIs = #queues + #config. Then driver need not read the register. We're trying to make such kind of agreement on spec level. > > Having few pages for a device that only have one queue is kind of a > waste. Could I ask what's the meaning of few pages here? BTW, we didn't define MSIx-like tables for virtio-mmio. Thanks, Jing > > Thanks > > >> >> >> So the number of vectors supported by device is equal to the total >> number of vqs and config. >> >> We will try to explicitly highlight this point in spec for later >> version. >> >> >> Thanks! >> >> Jing >> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org >>> For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org >>> >> >