On Thu, Oct 15, 2020 at 2:39 PM Felipe Franciosi wrote:
> > On Oct 13, 2020, at 10:30 AM, Stefan Hajnoczi wrote:>
> > >
> > On Fri, Oct 02, 2020 at 10:14:23AM +, Felipe Franciosi wrote:
> >>> On Sep 30, 2020, at 3:24 PM, Stefan Hajnoczi wrote:
> >>> On Tue, Sep 29, 2020 at 09:21:54AM -0700,
Hi,
> On Oct 13, 2020, at 10:30 AM, Stefan Hajnoczi wrote:
>
> On Fri, Oct 02, 2020 at 10:14:23AM +, Felipe Franciosi wrote:
>>
>>
>>> On Sep 30, 2020, at 3:24 PM, Stefan Hajnoczi wrote:
>>>
>>> On Tue, Sep 29, 2020 at 09:21:54AM -0700, John G Johnson wrote:
> On Sep 29, 2020, at 3:3
On Wed, Sep 30, 2020 at 03:24:08PM +0100, Stefan Hajnoczi wrote:
> On Tue, Sep 29, 2020 at 09:21:54AM -0700, John G Johnson wrote:
> > > On Sep 29, 2020, at 3:37 AM, Stefan Hajnoczi wrote:
> > >
> > > On Mon, Sep 28, 2020 at 09:58:37AM +, Thanos Makatos wrote:
> > >>> It should be accompanied
On Fri, Oct 02, 2020 at 10:14:23AM +, Felipe Franciosi wrote:
>
>
> > On Sep 30, 2020, at 3:24 PM, Stefan Hajnoczi wrote:
> >
> > On Tue, Sep 29, 2020 at 09:21:54AM -0700, John G Johnson wrote:
> >>> On Sep 29, 2020, at 3:37 AM, Stefan Hajnoczi wrote:
> >>>
> >>> On Mon, Sep 28, 2020 at 0
> On Sep 30, 2020, at 3:24 PM, Stefan Hajnoczi wrote:
>
> On Tue, Sep 29, 2020 at 09:21:54AM -0700, John G Johnson wrote:
>>> On Sep 29, 2020, at 3:37 AM, Stefan Hajnoczi wrote:
>>>
>>> On Mon, Sep 28, 2020 at 09:58:37AM +, Thanos Makatos wrote:
> It should be accompanied by a test i
On Tue, Sep 29, 2020 at 09:21:54AM -0700, John G Johnson wrote:
> > On Sep 29, 2020, at 3:37 AM, Stefan Hajnoczi wrote:
> >
> > On Mon, Sep 28, 2020 at 09:58:37AM +, Thanos Makatos wrote:
> >>> It should be accompanied by a test in tests/. PCI-level testing APIS for
> >>> BARs, configuration
> On Sep 29, 2020, at 3:37 AM, Stefan Hajnoczi wrote:
>
> On Mon, Sep 28, 2020 at 09:58:37AM +, Thanos Makatos wrote:
>>> It should be accompanied by a test in tests/. PCI-level testing APIS for
>>> BARs, configuration space, interrupts, etc are available in
>>> tests/qtest/libqos/pci.h. T
On Tue, Sep 15, 2020 at 07:29:17AM -0700, Thanos Makatos wrote:
> This patch introduces the vfio-user protocol specification (formerly
> known as VFIO-over-socket), which is designed to allow devices to be
> emulated outside QEMU, in a separate process. vfio-user reuses the
> existing VFIO defines,
On Mon, Sep 28, 2020 at 09:58:37AM +, Thanos Makatos wrote:
> > It should be accompanied by a test in tests/. PCI-level testing APIS for
> > BARs, configuration space, interrupts, etc are available in
> > tests/qtest/libqos/pci.h. The test case needs to include a vfio-user
> > device backend in
@gmail.com;
> ism...@linux.com; xiuchun...@intel.com; John G Johnson
>
> Subject: Re: [PATCH v4] introduce vfio-user protocol specification
>
> On Tue, Sep 15, 2020 at 07:29:17AM -0700, Thanos Makatos wrote:
> > This patch introduces the vfio-user protocol specification (formerl
On Thu, Sep 24, 2020 at 09:21:32AM +0100, Stefan Hajnoczi wrote:
> On Tue, Sep 15, 2020 at 07:29:17AM -0700, Thanos Makatos wrote:
> > This patch introduces the vfio-user protocol specification (formerly
> > known as VFIO-over-socket), which is designed to allow devices to be
> > emulated outside Q
On Tue, Sep 15, 2020 at 07:29:17AM -0700, Thanos Makatos wrote:
> This patch introduces the vfio-user protocol specification (formerly
> known as VFIO-over-socket), which is designed to allow devices to be
> emulated outside QEMU, in a separate process. vfio-user reuses the
> existing VFIO defines,
This patch introduces the vfio-user protocol specification (formerly
known as VFIO-over-socket), which is designed to allow devices to be
emulated outside QEMU, in a separate process. vfio-user reuses the
existing VFIO defines, structs and concepts.
It has been earlier discussed as an RFC in:
"RFC
13 matches
Mail list logo
