From: Cornelia Huck <cohuck@redhat.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>
Cc: Halil Pasic <pasic@linux.vnet.ibm.com>,
Dong Jia Shi <bjsdjshi@linux.vnet.ibm.com>,
Pierre Morel <pmorel@linux.vnet.ibm.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 1/2] s390x/ccs: add ccw-tester emulated device
Date: Mon, 18 Sep 2017 10:42:29 +0200 [thread overview]
Message-ID: <20170918104229.4eadb172.cohuck@redhat.com> (raw)
In-Reply-To: <5626693c-d7be-7c21-37e3-27625e9fbf2b@de.ibm.com>
On Mon, 18 Sep 2017 10:30:32 +0200
Christian Borntraeger <borntraeger@de.ibm.com> wrote:
> On 09/15/2017 09:27 AM, Cornelia Huck wrote:
> > On Thu, 14 Sep 2017 18:50:29 +0200
> > Halil Pasic <pasic@linux.vnet.ibm.com> wrote:
> >
> >> On 09/14/2017 04:26 PM, Cornelia Huck wrote:
> >>> On Wed, 13 Sep 2017 15:27:51 +0200
> >>> Halil Pasic <pasic@linux.vnet.ibm.com> wrote:
> >
> >>>> +static Property ccw_tester_properties[] = {
> >>>> + DEFINE_PROP_UINT16("cu_type", CcwTesterDevice, cu_type,
> >>>> + 0x3831),
> >>>
> >>> 0x4711 would be nice :)
> >>
> >> I don't understand the joke/pun/whatever if there is one,
> >> but I'm fine with changing this too.
> >
> > https://en.wikipedia.org/wiki/4711
> >
> > That's my default if I need a four-digit number :)
> >
> >>
> >>>
> >>> If we want to follow up on that testdev idea (and I think we should),
> >>> it might make sense to have a proper type reserve to prevent accidental
> >>> clashes.
> >>
> >> I agree. Although I would still keep the cu_type configurable,
> >> because it might make sense to test a particular 'real' driver
> >> (and not a test driver like here). I haven't really thought
> >> this through, but it was an idea I had while agonizing over
> >> not having a proper type reserved.
> >>
> >> I suppose you did something like that for virtio, or? I'm in dark
> >> when it comes to the question what process do we/I have to go to
> >> get a type,for example 0x4711, reserved.
> >
> > 4711 is more a joke :) It might be worth trying the same channels as
> > for virtio-ccw.
> >
> > Christian should know more about that.
>
> Getting a new number was very easy (because it is attached to a machine type
> number). I I remember correctly, only numerical values are uses, so maybe
> we can use ffff as there will never be such a real value?
>
Yes, that sounds like the easiest way to do that.
next prev parent reply other threads:[~2017-09-18 8:42 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-13 13:27 [Qemu-devel] [PATCH 0/2] tests for CCW IDA Halil Pasic
2017-09-13 13:27 ` [Qemu-devel] [PATCH 1/2] s390x/ccs: add ccw-tester emulated device Halil Pasic
2017-09-14 14:26 ` Cornelia Huck
2017-09-14 16:50 ` Halil Pasic
2017-09-15 7:27 ` Cornelia Huck
2017-09-15 17:01 ` Cornelia Huck
2017-09-19 14:20 ` Pierre Morel
2017-09-25 15:06 ` Halil Pasic
2017-09-25 15:39 ` Cornelia Huck
2017-09-18 8:30 ` Christian Borntraeger
2017-09-18 8:42 ` Cornelia Huck [this message]
2017-10-19 16:39 ` Halil Pasic
2017-10-20 13:00 ` Cornelia Huck
2017-10-20 14:33 ` Halil Pasic
2017-10-20 15:46 ` Cornelia Huck
2017-09-19 14:26 ` Pierre Morel
2017-09-13 13:27 ` [Qemu-devel] [PATCH 2/2 NOT QEMU] a tester device for ccw I/O Halil Pasic
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=20170918104229.4eadb172.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=bjsdjshi@linux.vnet.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=pasic@linux.vnet.ibm.com \
--cc=pmorel@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
/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).