From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: virtio-comment-return-1371-cohuck=redhat.com@lists.oasis-open.org Sender: List-Post: List-Help: List-Unsubscribe: List-Subscribe: Received: from lists.oasis-open.org (oasis-open.org [10.110.1.242]) by lists.oasis-open.org (Postfix) with ESMTP id 4EC00985B4C for ; Mon, 27 Jul 2020 13:20:17 +0000 (UTC) Date: Mon, 27 Jul 2020 09:20:09 -0400 From: "Michael S. Tsirkin" Message-ID: <20200727091802-mutt-send-email-mst@kernel.org> References: MIME-Version: 1.0 In-Reply-To: Subject: [virtio-comment] Re: [RFC] ivshmem v2: Shared memory device specification Content-Type: text/plain; charset=us-ascii Content-Disposition: inline To: Jan Kiszka Cc: "virtio-comment@lists.oasis-open.org" , Jailhouse , qemu-devel , Alex =?iso-8859-1?Q?Benn=E9e?= , liang yan List-ID: On Mon, May 25, 2020 at 09:58:28AM +0200, Jan Kiszka wrote: > #### Vendor Specific Capability (ID 09h) > > This capability must always be present. > > | Offset | Register | Content | > |-------:|:--------------------|:-----------------------------------------------| > | 00h | ID | 09h | > | 01h | Next Capability | Pointer to next capability or 00h | > | 02h | Length | 20h if Base Address is present, 18h otherwise | > | 03h | Privileged Control | Bit 0 (read/write): one-shot interrupt mode | > | | | Bits 1-7: Reserved (0 on read, writes ignored) | > | 04h | State Table Size | 32-bit size of read-only State Table | > | 08h | R/W Section Size | 64-bit size of common read/write section | > | 10h | Output Section Size | 64-bit size of output sections | > | 18h | Base Address | optional: 64-bit base address of shared memory | > > All registers are read-only. Writes are ignored, except to bit 0 of > the Privileged Control register. Is there value in making this follow the virtio vendor-specific capability format? That will cost several extra bytes - do you envision having many of these in the config space? Also, do we want to define an extended capability format in case this is a pci extended capability? -- MST This publicly archived list offers a means to provide input to the OASIS Virtual I/O Device (VIRTIO) TC. In order to verify user consent to the Feedback License terms and to minimize spam in the list archive, subscription is required before posting. Subscribe: virtio-comment-subscribe@lists.oasis-open.org Unsubscribe: virtio-comment-unsubscribe@lists.oasis-open.org List help: virtio-comment-help@lists.oasis-open.org List archive: https://lists.oasis-open.org/archives/virtio-comment/ Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lists Committee: https://www.oasis-open.org/committees/virtio/ Join OASIS: https://www.oasis-open.org/join/