qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Pierre Morel <pmorel@linux.ibm.com>
To: Halil Pasic <pasic@linux.ibm.com>,
	Christian Borntraeger <borntraeger@de.ibm.com>
Cc: thuth@redhat.com, frankja@linux.ibm.com, kvm@vger.kernel.org,
	david@redhat.com, cohuck@redhat.com,
	richard.henderson@linaro.org, drjones@redhat.com,
	qemu-devel@nongnu.org, qemu-s390x@nongnu.org,
	Michael S Tsirkin <mst@redhat.com>,
	imbrenda@linux.ibm.com
Subject: Re: [PATCH 0/2] s390x: ccw: A simple test device for virtio CCW
Date: Wed, 1 Sep 2021 15:59:19 +0200	[thread overview]
Message-ID: <9bcd5bc3-06b9-f5f5-d6c5-949e70a71ffa@linux.ibm.com> (raw)
In-Reply-To: <20210830224204.49a7965a.pasic@linux.ibm.com>



On 8/30/21 10:42 PM, Halil Pasic wrote:
> On Mon, 30 Aug 2021 11:51:51 +0200
> Christian Borntraeger <borntraeger@de.ibm.com> wrote:
> 
>> On 27.08.21 12:50, Pierre Morel wrote:
>>> Hello All,
>>>
>>>
>>> This series presents a VIRTIO test device which receives data on its
>>> input channel and sends back a simple checksum for the data it received
>>> on its output channel.
>>>    
>>> The goal is to allow a simple VIRTIO device driver to check the VIRTIO
>>> initialization and various data transfer.
> 
> Can you please elaborate a little on the objectives.

Yes I will, but I must think a lot more about it, I think doing the 
specifications you speak about later in this response is the right way 
to do it.


> 
>>>
>>> For this I introduced a new device ID for the device and having no
>>> Linux driver but a kvm-unit-test driver, I have the following
>>> questions:
>>
>> I think we should reserve an ID in the official virtio spec then for such a device?
>> Maybe also add mst for such things.
> 
> I agree having ID reserved is a good idea. But then if we are going to
> introduce an official test device, I believe we should write a
> specification for it as well. Yes having the guarantee that test devices
> and real devices won't mix is a value in itself, but if we had a
> standardized test device, whoever does work with it would not have to
> ask themselves is this test device compatible with this test device
> driver.

Yes right.

> 
>>    
>>
>>> Is there another way to advertise new VIRTIO IDs but Linux?
>>> If this QEMU test meet interest, should I write a Linux test program?
>>>
> 
> You may not simply claim and advertise a VIRTIO ID. The virtio ids
> are allocated by the virtio standardisation body, and the list of the
> IDs reserved in the v1.1-cs01 incarnation of the spec can be found here:
> https://docs.oasis-open.org/virtio/virtio/v1.1/cs01/virtio-v1.1-cs01.html#x1-1930005
> 
> For how to contribute to the virtio specification please take look at
> this:
> https://github.com/oasis-tcs/virtio-admin/blob/master/README.md

Thanks, I will go this way.


Thanks for these constructive answers,

Regards,
Pierre



-- 
Pierre Morel
IBM Lab Boeblingen


      reply	other threads:[~2021-09-01 14:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-27 10:50 [PATCH 0/2] s390x: ccw: A simple test device for virtio CCW Pierre Morel
2021-08-27 10:50 ` [PATCH 1/2] virtio: Linux: Update of virtio_ids Pierre Morel
2021-08-27 10:50 ` [PATCH 2/2] s390x: ccw: A simple test device for virtio CCW Pierre Morel
2021-08-30  9:51 ` [PATCH 0/2] " Christian Borntraeger
2021-08-30 12:05   ` Pierre Morel
2021-08-30 20:42   ` Halil Pasic
2021-09-01 13:59     ` Pierre Morel [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=9bcd5bc3-06b9-f5f5-d6c5-949e70a71ffa@linux.ibm.com \
    --to=pmorel@linux.ibm.com \
    --cc=borntraeger@de.ibm.com \
    --cc=cohuck@redhat.com \
    --cc=david@redhat.com \
    --cc=drjones@redhat.com \
    --cc=frankja@linux.ibm.com \
    --cc=imbrenda@linux.ibm.com \
    --cc=kvm@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=pasic@linux.ibm.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-s390x@nongnu.org \
    --cc=richard.henderson@linaro.org \
    --cc=thuth@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).