From: Paolo Bonzini <pbonzini@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>,
Chen Fan <chen.fan.fnst@cn.fujitsu.com>
Cc: izumi.taku@jp.fujitsu.com, alex.williamson@redhat.com,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v5 0/7] pass aer error to guest for vfio device
Date: Thu, 19 Mar 2015 22:44:10 +0100 [thread overview]
Message-ID: <550B432A.2030905@redhat.com> (raw)
In-Reply-To: <20150316055709-mutt-send-email-mst@redhat.com>
On 16/03/2015 05:57, Michael S. Tsirkin wrote:
> > 1. add 'x-aer' for user to off aer capability.
>
> User-exposed properties should not start with x- - by convention
> that's for internal properties.
Wrong, x- is for properties that we don't guarantee to remain there in
the future. It looks indeed like the property should be called simply
'aer', but not for the reason you mentioned.
Paolo
prev parent reply other threads:[~2015-03-19 21:44 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-12 10:23 [Qemu-devel] [PATCH v5 0/7] pass aer error to guest for vfio device Chen Fan
2015-03-12 10:23 ` [Qemu-devel] [PATCH v5 1/7] vfio: add pcie extanded capability support Chen Fan
2015-03-12 10:23 ` [Qemu-devel] [PATCH v5 2/7] aer: impove pcie_aer_init to support vfio device Chen Fan
2015-03-13 22:25 ` Alex Williamson
2015-03-16 2:30 ` Chen Fan
2015-03-12 10:23 ` [Qemu-devel] [PATCH v5 3/7] vfio: add aer support for " Chen Fan
2015-03-13 22:28 ` Alex Williamson
2015-03-12 10:23 ` [Qemu-devel] [PATCH v5 4/7] pcie_aer: expose pcie_aer_msg() interface Chen Fan
2015-03-13 22:30 ` Alex Williamson
2015-03-18 13:29 ` Michael S. Tsirkin
2015-03-19 1:33 ` Chen Fan
2015-03-12 10:23 ` [Qemu-devel] [PATCH v5 5/7] vfio-pci: pass the aer error to guest Chen Fan
2015-03-13 22:34 ` Alex Williamson
2015-03-16 3:05 ` Chen Fan
2015-03-16 3:52 ` Alex Williamson
2015-03-16 7:35 ` Chen Fan
2015-03-16 14:09 ` Alex Williamson
2015-03-25 1:33 ` Chen Fan
2015-03-25 2:31 ` Alex Williamson
2015-03-25 1:53 ` Chen Fan
2015-03-25 2:41 ` Alex Williamson
2015-03-25 3:07 ` Chen Fan
2015-04-01 4:12 ` Chen Fan
2015-04-01 15:46 ` Alex Williamson
2015-04-08 8:59 ` Chen Fan
2015-04-08 15:36 ` Alex Williamson
2015-04-15 10:30 ` Chen Fan
2015-04-15 14:18 ` Alex Williamson
2015-03-12 10:23 ` [Qemu-devel] [PATCH v5 6/7] vfio: add 'x-aer' property to expose aercap Chen Fan
2015-03-18 13:23 ` Michael S. Tsirkin
2015-03-18 14:09 ` Alex Williamson
2015-03-12 10:23 ` [Qemu-devel] [PATCH v5 7/7] pc: add PC_I440FX_COMPAT to disable aercap for vifo device Chen Fan
2015-03-13 22:38 ` Alex Williamson
2015-03-16 2:48 ` Chen Fan
2015-03-16 2:49 ` Chen Fan
2015-03-18 13:23 ` Michael S. Tsirkin
2015-03-18 14:02 ` Alex Williamson
2015-03-18 14:05 ` Michael S. Tsirkin
2015-03-18 14:15 ` Alex Williamson
2015-03-18 14:36 ` Michael S. Tsirkin
2015-03-18 14:50 ` Alex Williamson
2015-03-18 15:02 ` Michael S. Tsirkin
2015-03-18 15:45 ` Alex Williamson
2015-03-18 16:44 ` Michael S. Tsirkin
2015-03-18 17:11 ` Alex Williamson
2015-03-18 17:45 ` Michael S. Tsirkin
2015-03-18 18:08 ` Alex Williamson
2015-03-18 18:56 ` Michael S. Tsirkin
2015-03-18 19:05 ` Alex Williamson
2015-03-19 21:26 ` Paolo Bonzini
2015-03-16 2:52 ` [Qemu-devel] [PATCH v5 0/7] pass aer error to guest for vfio device Chen Fan
2015-03-16 4:57 ` Michael S. Tsirkin
2015-03-19 21:44 ` Paolo Bonzini [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=550B432A.2030905@redhat.com \
--to=pbonzini@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=chen.fan.fnst@cn.fujitsu.com \
--cc=izumi.taku@jp.fujitsu.com \
--cc=mst@redhat.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).