[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170112182135-mutt-send-email-mst@kernel.org>
Date: Thu, 12 Jan 2017 18:24:19 +0200
From: "Michael S. Tsirkin" <mst@...hat.com>
To: Cao jin <caoj.fnst@...fujitsu.com>
Cc: linux-kernel@...r.kernel.org, kvm@...r.kernel.org,
qemu-devel@...gnu.org, izumi.taku@...fujitsu.com,
alex.williamson@...hat.com
Subject: Re: [PATCH v2] vfio/pci: Support error recovery
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 :)
Powered by blists - more mailing lists