On Thu, 2015-12-03 at 15:22 +1100, David Gibson wrote:
> On Wed, Dec 02, 2015 at 01:09:34PM -0700, Alex Williamson wrote:
> > On Tue, 2015-12-01 at 13:23 +1100, David Gibson wrote:
> > > On Mon, Nov 23, 2015 at 02:58:11PM -0700, Alex Williamson wrote:
> > > > On Thu, 2015-11-19 at 15:29 +1100, Davi
On Wed, Dec 02, 2015 at 01:09:34PM -0700, Alex Williamson wrote:
> On Tue, 2015-12-01 at 13:23 +1100, David Gibson wrote:
> > On Mon, Nov 23, 2015 at 02:58:11PM -0700, Alex Williamson wrote:
> > > On Thu, 2015-11-19 at 15:29 +1100, David Gibson wrote:
> > > > At present the code handling IBM's Enha
On Tue, 2015-12-01 at 13:23 +1100, David Gibson wrote:
> On Mon, Nov 23, 2015 at 02:58:11PM -0700, Alex Williamson wrote:
> > On Thu, 2015-11-19 at 15:29 +1100, David Gibson wrote:
> > > At present the code handling IBM's Enhanced Error Handling (EEH) interface
> > > on VFIO devices operates by byp
On Mon, Nov 23, 2015 at 02:58:11PM -0700, Alex Williamson wrote:
> On Thu, 2015-11-19 at 15:29 +1100, David Gibson wrote:
> > At present the code handling IBM's Enhanced Error Handling (EEH) interface
> > on VFIO devices operates by bypassing the usual VFIO logic with
> > vfio_container_ioctl(). T
On Thu, 2015-11-19 at 15:29 +1100, David Gibson wrote:
> At present the code handling IBM's Enhanced Error Handling (EEH) interface
> on VFIO devices operates by bypassing the usual VFIO logic with
> vfio_container_ioctl(). That's a poorly designed interface with unclear
> semantics about exactly
At present the code handling IBM's Enhanced Error Handling (EEH) interface
on VFIO devices operates by bypassing the usual VFIO logic with
vfio_container_ioctl(). That's a poorly designed interface with unclear
semantics about exactly what can be operated on.
In particular it operates on a single
