> > 3) Muser.ko pins the pages (in get_dma_map(), called from below)
> > (https://urldefense.proofpoint.com/v2/url?u=https-
> 3A__github.com_nutanix_muser_blob_master_kmod_muser.c-
> 23L711=DwICAg=s883GpUCOChKOHiocYtGcg=XTpYsh5Ps2zJvtw6ogtt
>
* John G Johnson (john.g.john...@oracle.com) wrote:
> DMA
>
> This is one place where I might diverge from VFIO. It uses an
> ioctl to tell the kernel driver what areas of guest memory the device
> can address. The driver then pins that memory so it can be programmed
> into a HW IOMMU.
> On Jan 3, 2020, at 7:59 AM, Stefan Hajnoczi wrote:
>
> On Thu, Jan 02, 2020 at 11:03:22AM +, Felipe Franciosi wrote:
>>> On Jan 2, 2020, at 10:42 AM, Stefan Hajnoczi wrote:
>>> On Fri, Dec 20, 2019 at 10:22:37AM +, Daniel P. Berrangé wrote:
On Fri, Dec 20, 2019 at 09:47:12AM
On Thu, Jan 02, 2020 at 10:55:46PM +0400, Marc-André Lureau wrote:
> On Thu, Jan 2, 2020 at 3:03 PM Felipe Franciosi wrote:
> > I even recall highlighting that vhost-user could be moved underneath
> > that later, greatly simplifying lots of other Qemu code.
>
> That would eventually be an
On Thu, Jan 02, 2020 at 11:03:22AM +, Felipe Franciosi wrote:
> > On Jan 2, 2020, at 10:42 AM, Stefan Hajnoczi wrote:
> > On Fri, Dec 20, 2019 at 10:22:37AM +, Daniel P. Berrangé wrote:
> >> On Fri, Dec 20, 2019 at 09:47:12AM +, Stefan Hajnoczi wrote:
> >>> On Thu, Dec 19, 2019 at
On Thu, Jan 02, 2020 at 08:01:36AM -0800, Elena Ufimtseva wrote:
> On Tue, Dec 17, 2019 at 04:33:16PM +, Stefan Hajnoczi wrote:
> > On Mon, Dec 16, 2019 at 07:57:32PM +, Felipe Franciosi wrote:
> > > > On 16 Dec 2019, at 20:47, Elena Ufimtseva
> > > > wrote:
> > > > On Fri, Dec 13, 2019
Hi
On Thu, Jan 2, 2020 at 3:03 PM Felipe Franciosi wrote:
> The reason I dislike yet another offloading protocol (ie. there is
> vhost, there is vfio, and then there would be qdev-over-socket) is
> that we keep reinventing the wheel. I very much prefer picking
> something solid (eg. VFIO) and
On Tue, Dec 17, 2019 at 04:33:16PM +, Stefan Hajnoczi wrote:
> On Mon, Dec 16, 2019 at 07:57:32PM +, Felipe Franciosi wrote:
> > > On 16 Dec 2019, at 20:47, Elena Ufimtseva
> > > wrote:
> > > On Fri, Dec 13, 2019 at 10:41:16AM +, Stefan Hajnoczi wrote:
> > >> Is there a
> On Jan 2, 2020, at 10:42 AM, Stefan Hajnoczi wrote:
>
> On Fri, Dec 20, 2019 at 10:22:37AM +, Daniel P. Berrangé wrote:
>> On Fri, Dec 20, 2019 at 09:47:12AM +, Stefan Hajnoczi wrote:
>>> On Thu, Dec 19, 2019 at 12:55:04PM +, Daniel P. Berrangé wrote:
On Thu, Dec 19, 2019 at
On Fri, Dec 20, 2019 at 10:22:37AM +, Daniel P. Berrangé wrote:
> On Fri, Dec 20, 2019 at 09:47:12AM +, Stefan Hajnoczi wrote:
> > On Thu, Dec 19, 2019 at 12:55:04PM +, Daniel P. Berrangé wrote:
> > > On Thu, Dec 19, 2019 at 12:33:15PM +, Felipe Franciosi wrote:
> > > > > On Dec
On Fri, Dec 20, 2019 at 09:15:40AM -0800, John G Johnson wrote:
> > On Dec 19, 2019, at 5:36 AM, Stefan Hajnoczi wrote:
> > On Wed, Dec 18, 2019 at 01:00:55AM +0100, Paolo Bonzini wrote:
> >> On 17/12/19 23:57, Felipe Franciosi wrote:
> We don’t pin guest memory; we pass the QEMU file descriptors
On Fri, Dec 20, 2019 at 09:15:40AM -0800, John G Johnson wrote:
> > On Dec 19, 2019, at 5:36 AM, Stefan Hajnoczi wrote:
> > On Wed, Dec 18, 2019 at 01:00:55AM +0100, Paolo Bonzini wrote:
> >> On 17/12/19 23:57, Felipe Franciosi wrote:
> We don’t pin guest memory; we pass the QEMU file descriptors
> On Dec 19, 2019, at 5:36 AM, Stefan Hajnoczi wrote:
>
> On Wed, Dec 18, 2019 at 01:00:55AM +0100, Paolo Bonzini wrote:
>> On 17/12/19 23:57, Felipe Franciosi wrote:
>>> Doing it in userspace was the flow we proposed back in last year's KVM
>>> Forum (Edinburgh), but it got turned down.
>>
Heya,
> On Dec 20, 2019, at 3:25 PM, Alex Williamson
> wrote:
>
> On Fri, 20 Dec 2019 14:14:33 +
> Felipe Franciosi wrote:
>
>>> On Dec 20, 2019, at 9:50 AM, Paolo Bonzini wrote:
>>>
>>> On 20/12/19 10:47, Stefan Hajnoczi wrote:
> If it doesn't create too large of a burden to
On Fri, 20 Dec 2019 14:14:33 +
Felipe Franciosi wrote:
> > On Dec 20, 2019, at 9:50 AM, Paolo Bonzini wrote:
> >
> > On 20/12/19 10:47, Stefan Hajnoczi wrote:
> >>> If it doesn't create too large of a burden to support both, then I think
> >>> it is very desirable. IIUC, this is saying a
> On Dec 20, 2019, at 9:50 AM, Paolo Bonzini wrote:
>
> On 20/12/19 10:47, Stefan Hajnoczi wrote:
>>> If it doesn't create too large of a burden to support both, then I think
>>> it is very desirable. IIUC, this is saying a kernel based solution as the
>>> optimized/optimal solution, and
On Fri, Dec 20, 2019 at 09:47:12AM +, Stefan Hajnoczi wrote:
> On Thu, Dec 19, 2019 at 12:55:04PM +, Daniel P. Berrangé wrote:
> > On Thu, Dec 19, 2019 at 12:33:15PM +, Felipe Franciosi wrote:
> > > > On Dec 19, 2019, at 11:55 AM, Stefan Hajnoczi
> > > > wrote:
> > > > On Tue, Dec
On 20/12/19 10:47, Stefan Hajnoczi wrote:
>> If it doesn't create too large of a burden to support both, then I think
>> it is very desirable. IIUC, this is saying a kernel based solution as the
>> optimized/optimal solution, and userspace UNIX socket based option as the
>> generic "works
On Thu, Dec 19, 2019 at 12:55:04PM +, Daniel P. Berrangé wrote:
> On Thu, Dec 19, 2019 at 12:33:15PM +, Felipe Franciosi wrote:
> > > On Dec 19, 2019, at 11:55 AM, Stefan Hajnoczi wrote:
> > > On Tue, Dec 17, 2019 at 10:57:17PM +, Felipe Franciosi wrote:
> > >>> On Dec 17, 2019, at
On Thu, Dec 19, 2019 at 12:50:21PM +, Daniel P. Berrangé wrote:
> On Tue, Dec 17, 2019 at 10:57:17PM +, Felipe Franciosi wrote:
> >
> >
> > > On Dec 17, 2019, at 5:33 PM, Stefan Hajnoczi wrote:
> > >
> > > On Mon, Dec 16, 2019 at 07:57:32PM +, Felipe Franciosi wrote:
> > >>> On 16
On 12/19/2019 7:33 AM, Felipe Franciosi wrote:
Hello,
(I've added Jim and Ben from the SPDK team to the thread.)
On Dec 19, 2019, at 11:55 AM, Stefan Hajnoczi wrote:
On Tue, Dec 17, 2019 at 10:57:17PM +, Felipe Franciosi wrote:
On Dec 17, 2019, at 5:33 PM, Stefan Hajnoczi wrote:
On
On Wed, Dec 18, 2019 at 01:00:55AM +0100, Paolo Bonzini wrote:
> On 17/12/19 23:57, Felipe Franciosi wrote:
> > Doing it in userspace was the flow we proposed back in last year's KVM
> > Forum (Edinburgh), but it got turned down.
>
> I think the time since then has shown that essentially the cat
On Thu, Dec 19, 2019 at 12:33:15PM +, Felipe Franciosi wrote:
> Hello,
>
> (I've added Jim and Ben from the SPDK team to the thread.)
>
> > On Dec 19, 2019, at 11:55 AM, Stefan Hajnoczi wrote:
> >
> > On Tue, Dec 17, 2019 at 10:57:17PM +, Felipe Franciosi wrote:
> >>> On Dec 17, 2019,
Hello,
(I've added Jim and Ben from the SPDK team to the thread.)
> On Dec 19, 2019, at 11:55 AM, Stefan Hajnoczi wrote:
>
> On Tue, Dec 17, 2019 at 10:57:17PM +, Felipe Franciosi wrote:
>>> On Dec 17, 2019, at 5:33 PM, Stefan Hajnoczi wrote:
>>> On Mon, Dec 16, 2019 at 07:57:32PM +,
On Tue, Dec 17, 2019 at 10:57:17PM +, Felipe Franciosi wrote:
>
>
> > On Dec 17, 2019, at 5:33 PM, Stefan Hajnoczi wrote:
> >
> > On Mon, Dec 16, 2019 at 07:57:32PM +, Felipe Franciosi wrote:
> >>> On 16 Dec 2019, at 20:47, Elena Ufimtseva
> >>> wrote:
> >>> On Fri, Dec 13, 2019 at
On Tue, Dec 17, 2019 at 10:57:17PM +, Felipe Franciosi wrote:
> > On Dec 17, 2019, at 5:33 PM, Stefan Hajnoczi wrote:
> > On Mon, Dec 16, 2019 at 07:57:32PM +, Felipe Franciosi wrote:
> >>> On 16 Dec 2019, at 20:47, Elena Ufimtseva
> >>> wrote:
> >>> On Fri, Dec 13, 2019 at 10:41:16AM
On 17/12/19 23:57, Felipe Franciosi wrote:
> Doing it in userspace was the flow we proposed back in last year's KVM
> Forum (Edinburgh), but it got turned down.
I think the time since then has shown that essentially the cat is out of
the bag. I didn't really like the idea of devices outside
> On Dec 17, 2019, at 5:33 PM, Stefan Hajnoczi wrote:
>
> On Mon, Dec 16, 2019 at 07:57:32PM +, Felipe Franciosi wrote:
>>> On 16 Dec 2019, at 20:47, Elena Ufimtseva
>>> wrote:
>>> On Fri, Dec 13, 2019 at 10:41:16AM +, Stefan Hajnoczi wrote:
Is there a work-in-progress muser
On Mon, Dec 16, 2019 at 07:57:32PM +, Felipe Franciosi wrote:
> > On 16 Dec 2019, at 20:47, Elena Ufimtseva
> > wrote:
> > On Fri, Dec 13, 2019 at 10:41:16AM +, Stefan Hajnoczi wrote:
> >> Is there a work-in-progress muser patch series you can post to start the
> >> discussion early?
Heya,
> On 16 Dec 2019, at 20:47, Elena Ufimtseva wrote:
>
> On Fri, Dec 13, 2019 at 10:41:16AM +, Stefan Hajnoczi wrote:
>>> On Mon, Dec 09, 2019 at 10:47:17PM -0800, Elena Ufimtseva wrote:
>>> At this moment we are working on the first stage of the project with help of
>>> the Nutanix
On Fri, Dec 13, 2019 at 10:41:16AM +, Stefan Hajnoczi wrote:
> On Mon, Dec 09, 2019 at 10:47:17PM -0800, Elena Ufimtseva wrote:
> > At this moment we are working on the first stage of the project with help of
> > the Nutanix developers.
> > The questions we have gathered so far will be
On Mon, Dec 09, 2019 at 10:47:17PM -0800, Elena Ufimtseva wrote:
> At this moment we are working on the first stage of the project with help of
> the Nutanix developers.
> The questions we have gathered so far will be addressed with muser
> and Qemu developers after we finish the first stage and
Hi
We would like to give a short update to the community about the multi-process
project.
Firstly, we appreciate the feedback and all productive discussions we had
at KVM 2019 forum.
As an outcome of the conference, we have switched gears and are investigating
the ways of using the muser
On Thu, Oct 24, 2019 at 05:08:41AM -0400, Jagannathan Raman wrote:
> Started with the presentation in October 2017 made by Marc-Andre (Red Hat)
> and Konrad Wilk (Oracle) [1], and continued by Jag's BoF at KVM Forum 2018,
> the multi-process project is now a prototype and presented in this
Patchew URL: https://patchew.org/QEMU/cover.1571905346.git.jag.ra...@oracle.com/
Hi,
This series seems to have some coding style problems. See output below for
more information:
Subject: [RFC v4 PATCH 00/49] Initial support of multi-process qemu
Type: series
Message-id: cover.1571905346
Patchew URL: https://patchew.org/QEMU/cover.1571905346.git.jag.ra...@oracle.com/
Hi,
This series failed the docker-mingw@fedora build test. Please find the testing
commands and
their output below. If you have Docker installed, you can probably reproduce it
locally.
=== TEST SCRIPT BEGIN ===
Patchew URL: https://patchew.org/QEMU/cover.1571905346.git.jag.ra...@oracle.com/
Hi,
This series failed the docker-quick@centos7 build test. Please find the testing
commands and
their output below. If you have Docker installed, you can probably reproduce it
locally.
=== TEST SCRIPT BEGIN ===
Started with the presentation in October 2017 made by Marc-Andre (Red Hat)
and Konrad Wilk (Oracle) [1], and continued by Jag's BoF at KVM Forum 2018,
the multi-process project is now a prototype and presented in this patchset.
John & Elena will present the status of this project in KVM Forum
38 matches
Mail list logo
