qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PATCH v5 07/13] vfio/ccw: vfio based subchannel passth


From: Dong Jia Shi
Subject: Re: [Qemu-devel] [PATCH v5 07/13] vfio/ccw: vfio based subchannel passthrough driver
Date: Wed, 26 Apr 2017 16:49:20 +0800
User-agent: Mutt/1.5.24 (2015-08-30)

* Dong Jia Shi <address@hidden> [2017-04-25 13:15:19 +0800]:

> * Alex Williamson <address@hidden> [2017-04-24 16:56:28 -0600]:
> 
> [...]
> > > > diff --git a/hw/vfio/ccw.c b/hw/vfio/ccw.c
> > > > new file mode 100644
> > > > index 0000000..c491bee
> > > > --- /dev/null
> > > > +++ b/hw/vfio/ccw.c
> > > > @@ -0,0 +1,207 @@
> > > > +/*
> > > > + * vfio based subchannel assignment support
> > > > + *
> > > > + * Copyright 2017 IBM Corp.
> > > > + * Author(s): Dong Jia Shi <address@hidden>
> > > > + *            Xiao Feng Ren <address@hidden>
> > > > + *            Pierre Morel <address@hidden>
> > > > + *
> > > > + * This work is licensed under the terms of the GNU GPL, version 2 
> > > > or(at
> > > > + * your option) any version. See the COPYING file in the top-level
> > > > + * directory.
> > > > + */
> > > > +
> > > > +#include <linux/vfio.h>
> > > > +#include <sys/ioctl.h>
> > > > +
> > > > +#include "qemu/osdep.h"
> > > > +#include "qapi/error.h"
> > > > +#include "hw/sysbus.h"
> > > > +#include "hw/vfio/vfio.h"
> > > > +#include "hw/vfio/vfio-common.h"
> > > > +#include "hw/s390x/s390-ccw.h"
> > > > +#include "hw/s390x/ccw-device.h"
> > > > +
> > > > +#define TYPE_VFIO_CCW "vfio-ccw"
> > > > +typedef struct VFIOCCWDevice {
> > > > +    S390CCWDevice cdev;
> > > > +    VFIODevice vdev;
> > > > +} VFIOCCWDevice;
> > > > +
> > > > +static void vfio_ccw_compute_needs_reset(VFIODevice *vdev)
> > > > +{
> > > > +    vdev->needs_reset = false;
> > > > +}
> > > > +
> > > > +/*
> > > > + * We don't need vfio_hot_reset_multi and vfio_eoi operationis for
> > 
> > One more:
> > 
> > s/operationis/operations/
> > 
> Ok.
> 

Hi Conny,

I have pulled your cohuck-qemu/s390-next branch, and prepared a new
patch set with all of these problems fixed directly on the coressponding
commits on it. Fine to send out the new version as that?

Or I should rebase them against the latest master branch?

Thanks.

[...]

-- 
Dong Jia Shi




reply via email to

[Prev in Thread] Current Thread [Next in Thread]