All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cao jin <caoj.fnst@cn.fujitsu.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Alex Williamson <alex.williamson@redhat.com>,
	<linux-kernel@vger.kernel.org>, <kvm@vger.kernel.org>,
	<qemu-devel@nongnu.org>, <izumi.taku@jp.fujitsu.com>
Subject: Re: [PATCH v6] vfio error recovery: kernel support
Date: Thu, 6 Apr 2017 16:49:35 +0800	[thread overview]
Message-ID: <58E6011F.6030002@cn.fujitsu.com> (raw)
In-Reply-To: <20170406005028-mutt-send-email-mst@kernel.org>



On 04/06/2017 05:56 AM, Michael S. Tsirkin wrote:
> On Wed, Apr 05, 2017 at 04:54:33PM +0800, Cao jin wrote:
>> Apparently, I don't have experience to induce non-fatal error, device
>> error is more of a chance related with the environment(temperature,
>> humidity, etc) as I understand.
> 
> I'm not sure how to interpret this statement. I think what Alex is
> saying is simply that patches should include some justification. They
> make changes but what are they improving?
> For example:
> 
> 	I tested device ABC in conditions DEF. Without a patch VM
> 	stops. With the patches applied VM recovers and proceeds to
> 	use the device normally.
> 
> is one reasonable justification imho.
> 

Got it. But unfortunately, until now, I haven't seen a VM stop caused by
a real device non-fatal error during device assignment(Only saw real
fatal errors after start VM).
On one side, AER error could occur theoretically; on the other side,
seldom people have seen a VM stop caused by AER. Now I am asked that do
I have a real evidence or scenario to prove that this patchset is really
useful? I don't, and we all know it is hard to trigger a real hardware
error, so, seems I am pushed into the corner.  I guess these questions
also apply for AER driver's author, if the scenario is easy to
reproduce, there is no need to write aer_inject to fake errors.

-- 
Sincerely,
Cao jin

WARNING: multiple messages have this Message-ID (diff)
From: Cao jin <caoj.fnst@cn.fujitsu.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Alex Williamson <alex.williamson@redhat.com>,
	linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
	qemu-devel@nongnu.org, izumi.taku@jp.fujitsu.com
Subject: Re: [Qemu-devel] [PATCH v6] vfio error recovery: kernel support
Date: Thu, 6 Apr 2017 16:49:35 +0800	[thread overview]
Message-ID: <58E6011F.6030002@cn.fujitsu.com> (raw)
In-Reply-To: <20170406005028-mutt-send-email-mst@kernel.org>



On 04/06/2017 05:56 AM, Michael S. Tsirkin wrote:
> On Wed, Apr 05, 2017 at 04:54:33PM +0800, Cao jin wrote:
>> Apparently, I don't have experience to induce non-fatal error, device
>> error is more of a chance related with the environment(temperature,
>> humidity, etc) as I understand.
> 
> I'm not sure how to interpret this statement. I think what Alex is
> saying is simply that patches should include some justification. They
> make changes but what are they improving?
> For example:
> 
> 	I tested device ABC in conditions DEF. Without a patch VM
> 	stops. With the patches applied VM recovers and proceeds to
> 	use the device normally.
> 
> is one reasonable justification imho.
> 

Got it. But unfortunately, until now, I haven't seen a VM stop caused by
a real device non-fatal error during device assignment(Only saw real
fatal errors after start VM).
On one side, AER error could occur theoretically; on the other side,
seldom people have seen a VM stop caused by AER. Now I am asked that do
I have a real evidence or scenario to prove that this patchset is really
useful? I don't, and we all know it is hard to trigger a real hardware
error, so, seems I am pushed into the corner.  I guess these questions
also apply for AER driver's author, if the scenario is easy to
reproduce, there is no need to write aer_inject to fake errors.

-- 
Sincerely,
Cao jin

  reply	other threads:[~2017-04-06  8:49 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-23  9:07 [PATCH v6] vfio error recovery: kernel support Cao jin
2017-03-23  9:07 ` [Qemu-devel] " Cao jin
2017-03-24 22:12 ` Alex Williamson
2017-03-24 22:12   ` [Qemu-devel] " Alex Williamson
2017-03-28 13:47   ` Cao jin
2017-03-28 13:47     ` [Qemu-devel] " Cao jin
2017-03-28 16:12     ` Alex Williamson
2017-03-28 16:12       ` [Qemu-devel] " Alex Williamson
2017-03-29  0:01       ` Michael S. Tsirkin
2017-03-29  0:01         ` [Qemu-devel] " Michael S. Tsirkin
2017-03-29  2:55         ` Alex Williamson
2017-03-29  2:55           ` [Qemu-devel] " Alex Williamson
2017-03-30 18:00           ` Michael S. Tsirkin
2017-03-30 18:00             ` [Qemu-devel] " Michael S. Tsirkin
2017-03-30 18:16             ` Alex Williamson
2017-03-30 18:16               ` [Qemu-devel] " Alex Williamson
2017-04-05  8:54               ` Cao jin
2017-04-05  8:54                 ` [Qemu-devel] " Cao jin
2017-04-05 19:38                 ` Alex Williamson
2017-04-05 19:38                   ` [Qemu-devel] " Alex Williamson
2017-04-05 21:50                   ` Michael S. Tsirkin
2017-04-05 21:50                     ` [Qemu-devel] " Michael S. Tsirkin
2017-04-05 22:19                     ` Alex Williamson
2017-04-05 22:19                       ` [Qemu-devel] " Alex Williamson
2017-04-05 22:36                       ` Michael S. Tsirkin
2017-04-05 22:36                         ` [Qemu-devel] " Michael S. Tsirkin
2017-04-05 22:56                         ` Alex Williamson
2017-04-05 22:56                           ` [Qemu-devel] " Alex Williamson
2017-04-06  8:53                         ` Cao jin
2017-04-06  8:53                           ` [Qemu-devel] " Cao jin
2017-04-06 15:35                           ` Alex Williamson
2017-04-06 15:35                             ` [Qemu-devel] " Alex Williamson
2017-04-06  8:49                   ` Cao jin
2017-04-06  8:49                     ` [Qemu-devel] " Cao jin
2017-04-05 21:56                 ` Michael S. Tsirkin
2017-04-05 21:56                   ` [Qemu-devel] " Michael S. Tsirkin
2017-04-06  8:49                   ` Cao jin [this message]
2017-04-06  8:49                     ` Cao jin
2017-04-06 15:31                     ` Alex Williamson
2017-04-06 15:31                       ` [Qemu-devel] " Alex Williamson

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=58E6011F.6030002@cn.fujitsu.com \
    --to=caoj.fnst@cn.fujitsu.com \
    --cc=alex.williamson@redhat.com \
    --cc=izumi.taku@jp.fujitsu.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.