All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Cao jin <caoj.fnst@cn.fujitsu.com>
Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
	qemu-devel@nongnu.org, izumi.taku@jp.fujitsu.com,
	alex.williamson@redhat.com
Subject: Re: [PATCH v2] vfio/pci: Support error recovery
Date: Thu, 12 Jan 2017 18:24:19 +0200	[thread overview]
Message-ID: <20170112182135-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <58759015.5060909@cn.fujitsu.com>

On Wed, Jan 11, 2017 at 09:53:25AM +0800, Cao jin wrote:
> 
> 
> On 01/10/2017 11:11 PM, Michael S. Tsirkin wrote:
> > On Tue, Jan 10, 2017 at 07:46:17PM +0800, Cao jin wrote:
> >>
> >>
> >> On 01/10/2017 07:04 AM, Michael S. Tsirkin wrote:
> >>> On Sat, Dec 31, 2016 at 05:15:36PM +0800, Cao jin wrote:
> >>>> Support serious device error recovery
> >>>
> >>> serious?
> >>>
> >>
> >> Sorry for my poor vocabulary if it confuses people. I wanted to express
> >> the meaning that: vfio-pci actually cannot do a real recovery for device
> >> even if it provides the callbacks, it relies on the user to do a
> >> effective(or word "serious"?) recovery.
> >>
> >> Welcome the amendment on the commit log.
> > 
> > It's up to Alex, maybe he's able to figure it all out from
> > code, but the rest of us could benefit from a description
> > of what the patch does from userspace point of view.
> > 
> > Also, is it a pre-requisite of the userspace patches you posted?
> > 
> 
> Yes, it is.

Looks like it's time for another design document :)

WARNING: multiple messages have this Message-ID (diff)
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Cao jin <caoj.fnst@cn.fujitsu.com>
Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
	qemu-devel@nongnu.org, izumi.taku@jp.fujitsu.com,
	alex.williamson@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2] vfio/pci: Support error recovery
Date: Thu, 12 Jan 2017 18:24:19 +0200	[thread overview]
Message-ID: <20170112182135-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <58759015.5060909@cn.fujitsu.com>

On Wed, Jan 11, 2017 at 09:53:25AM +0800, Cao jin wrote:
> 
> 
> On 01/10/2017 11:11 PM, Michael S. Tsirkin wrote:
> > On Tue, Jan 10, 2017 at 07:46:17PM +0800, Cao jin wrote:
> >>
> >>
> >> On 01/10/2017 07:04 AM, Michael S. Tsirkin wrote:
> >>> On Sat, Dec 31, 2016 at 05:15:36PM +0800, Cao jin wrote:
> >>>> Support serious device error recovery
> >>>
> >>> serious?
> >>>
> >>
> >> Sorry for my poor vocabulary if it confuses people. I wanted to express
> >> the meaning that: vfio-pci actually cannot do a real recovery for device
> >> even if it provides the callbacks, it relies on the user to do a
> >> effective(or word "serious"?) recovery.
> >>
> >> Welcome the amendment on the commit log.
> > 
> > It's up to Alex, maybe he's able to figure it all out from
> > code, but the rest of us could benefit from a description
> > of what the patch does from userspace point of view.
> > 
> > Also, is it a pre-requisite of the userspace patches you posted?
> > 
> 
> Yes, it is.

Looks like it's time for another design document :)

  reply	other threads:[~2017-01-12 16:24 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-31  9:15 [PATCH v2] vfio/pci: Support error recovery Cao jin
2016-12-31  9:15 ` [Qemu-devel] " Cao jin
2017-01-09 23:04 ` Michael S. Tsirkin
2017-01-09 23:04   ` [Qemu-devel] " Michael S. Tsirkin
2017-01-10 11:46   ` Cao jin
2017-01-10 11:46     ` [Qemu-devel] " Cao jin
2017-01-10 15:11     ` Michael S. Tsirkin
2017-01-10 15:11       ` [Qemu-devel] " Michael S. Tsirkin
2017-01-11  1:53       ` Cao jin
2017-01-11  1:53         ` [Qemu-devel] " Cao jin
2017-01-12 16:24         ` Michael S. Tsirkin [this message]
2017-01-12 16:24           ` Michael S. Tsirkin
2017-01-18 21:32       ` Alex Williamson
2017-01-18 21:32         ` [Qemu-devel] " Alex Williamson
2017-01-18 21:32         ` Alex Williamson
2017-01-19  3:04         ` Cao jin
2017-01-19  3:04           ` [Qemu-devel] " Cao jin
2017-01-19  3:04           ` Cao jin
2017-01-19 19:26           ` Alex Williamson
2017-01-19 19:26             ` [Qemu-devel] " Alex Williamson
2017-01-18  5:33 ` Cao jin
2017-01-18  5:33   ` [Qemu-devel] " Cao jin
2017-01-18  5:33   ` Cao jin

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=20170112182135-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=alex.williamson@redhat.com \
    --cc=caoj.fnst@cn.fujitsu.com \
    --cc=izumi.taku@jp.fujitsu.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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.