From: Cornelia Huck <cohuck@redhat.com>
To: Halil Pasic <pasic@linux.vnet.ibm.com>
Cc: Shalini Chellathurai Saroja <shalini@linux.vnet.ibm.com>,
qemu-devel@nongnu.org,
Christian Borntraeger <borntraeger@de.ibm.com>,
qemu-s390x@nongnu.org,
Boris Fiuczynski <fiuczy@linux.vnet.ibm.com>,
Dong Jia Shi <bjsdjshi@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] [RFC PATCH 1/1] s390x/css: unresrict cssids
Date: Thu, 23 Nov 2017 17:59:15 +0100 [thread overview]
Message-ID: <20171123175915.14ec1639.cohuck@redhat.com> (raw)
In-Reply-To: <35aee93c-70e0-d9dd-b8e1-598c4e4c6a1c@linux.vnet.ibm.com>
On Thu, 23 Nov 2017 17:09:16 +0100
Halil Pasic <pasic@linux.vnet.ibm.com> wrote:
[I need time to process your other remarks.]
> On 11/22/2017 01:13 PM, Cornelia Huck wrote:
> >> Also I can't find anything about vfio-ccw in the upstream users
> >> manual for 2.10.91.
> >
> > We have an "upstream users manual"?
> >
> This is what I mean:
> https://qemu.weilnetz.de/doc/qemu-doc.html
This is really hit-and-miss. Some things are documented in there, some
are not. I usually consider the output of the binary the canonical list
of supported devices (in combination with the x- notation.)
>
> >> So I would argue using vfio-ccw is using an
> >> undocumented feature: if undocumented features changing in a non
> >> compatible way hits you, it's partly your own fault.
> >
> > If it's an x- interface, it is preliminary. If not, we should avoid
> > breaking it.
> >
>
> I don't see this documented in the users manual? Shouldn't the users
> know what is preliminary?
>
> Where is this documented?
It is long standing practice, but I cannot point to documentation
(maybe someone else can?)
next prev parent reply other threads:[~2017-11-23 16:59 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-21 11:18 [Qemu-devel] [RFC PATCH 1/1] s390x/css: unresrict cssids Halil Pasic
2017-11-21 13:44 ` Cornelia Huck
2017-11-21 14:27 ` Christian Borntraeger
2017-11-21 14:45 ` Christian Borntraeger
2017-11-21 16:06 ` Cornelia Huck
2017-11-21 18:10 ` Christian Borntraeger
2017-11-22 12:18 ` Cornelia Huck
2017-11-21 15:47 ` Halil Pasic
2017-11-21 16:20 ` Cornelia Huck
2017-11-21 17:05 ` Halil Pasic
2017-11-22 12:13 ` Cornelia Huck
2017-11-22 14:45 ` Boris Fiuczynski
2017-11-22 16:25 ` Cornelia Huck
2017-11-23 13:33 ` Halil Pasic
2017-11-24 12:46 ` Cornelia Huck
2017-11-24 13:01 ` Christian Borntraeger
2017-11-24 13:27 ` Cornelia Huck
2017-11-24 14:58 ` Christian Borntraeger
2017-11-24 15:30 ` Halil Pasic
2017-11-24 16:15 ` Cornelia Huck
2017-11-24 16:39 ` Halil Pasic
2017-11-27 2:20 ` Dong Jia Shi
2017-11-27 12:58 ` Cornelia Huck
2017-11-28 2:10 ` Dong Jia Shi
2017-11-27 12:56 ` Cornelia Huck
2017-11-27 13:11 ` Halil Pasic
2017-11-27 13:19 ` Cornelia Huck
2017-11-27 14:03 ` Christian Borntraeger
2017-11-27 14:38 ` Halil Pasic
2017-11-27 14:13 ` Halil Pasic
2017-11-27 15:09 ` Boris Fiuczynski
2017-11-27 16:56 ` Cornelia Huck
2017-11-27 17:34 ` Halil Pasic
2017-11-28 2:08 ` Dong Jia Shi
2017-11-28 8:53 ` Boris Fiuczynski
2017-11-28 10:22 ` Cornelia Huck
2017-11-28 11:49 ` Boris Fiuczynski
2017-11-28 12:14 ` Cornelia Huck
2017-11-28 12:24 ` Christian Borntraeger
2017-11-28 13:17 ` Halil Pasic
2017-11-28 13:25 ` Christian Borntraeger
2017-11-28 14:01 ` Cornelia Huck
2017-11-28 14:17 ` Christian Borntraeger
2017-11-28 14:45 ` Cornelia Huck
2017-11-29 18:51 ` Christian Borntraeger
2017-11-30 9:50 ` Cornelia Huck
2017-11-30 12:09 ` Christian Borntraeger
2017-11-28 14:11 ` Halil Pasic
2017-11-23 16:09 ` Halil Pasic
2017-11-23 16:59 ` Cornelia Huck [this message]
2017-11-22 11:25 ` Shalini Chellathurai Saroja
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=20171123175915.14ec1639.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=bjsdjshi@linux.vnet.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=fiuczy@linux.vnet.ibm.com \
--cc=pasic@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=shalini@linux.vnet.ibm.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).