search for: marchand

Displaying 20 results from an estimated 49 matches for "marchand".

2014 Jun 18
6
[Qemu-devel] Why I advise against using ivshmem
On Tue, Jun 17, 2014 at 11:44:11AM +0200, Paolo Bonzini wrote: > Il 17/06/2014 11:03, David Marchand ha scritto: > >>Unless someone steps up and maintains ivshmem, I think it should be > >>deprecated and dropped from QEMU. > > > >Then I can maintain ivshmem for QEMU. > >If this is ok, I will send a patch for MAINTAINERS file. > > Typically, adding yoursel...
2014 Jun 18
6
[Qemu-devel] Why I advise against using ivshmem
On Tue, Jun 17, 2014 at 11:44:11AM +0200, Paolo Bonzini wrote: > Il 17/06/2014 11:03, David Marchand ha scritto: > >>Unless someone steps up and maintains ivshmem, I think it should be > >>deprecated and dropped from QEMU. > > > >Then I can maintain ivshmem for QEMU. > >If this is ok, I will send a patch for MAINTAINERS file. > > Typically, adding yoursel...
2014 Jun 17
4
[Qemu-devel] Why I advise against using ivshmem
...guest. Actually, you can avoid this memory copy using frameworks like DPDK. > Unless someone steps up and maintains ivshmem, I think it should be > deprecated and dropped from QEMU. Then I can maintain ivshmem for QEMU. If this is ok, I will send a patch for MAINTAINERS file. -- David Marchand
2014 Jun 17
4
[Qemu-devel] Why I advise against using ivshmem
...guest. Actually, you can avoid this memory copy using frameworks like DPDK. > Unless someone steps up and maintains ivshmem, I think it should be > deprecated and dropped from QEMU. Then I can maintain ivshmem for QEMU. If this is ok, I will send a patch for MAINTAINERS file. -- David Marchand
2014 Jun 18
1
[Qemu-devel] Why I advise against using ivshmem
...w it. > > Please also see the bug fixes in the following unapplied patch: > "[PATCH] ivshmem: fix potential OOB r/w access (#2)" by Sebastian Krahmer > https://lists.gnu.org/archive/html/qemu-devel/2014-04/msg03538.html Thanks for the pointer. I'll check it. -- David Marchand
2014 Jun 18
1
[Qemu-devel] Why I advise against using ivshmem
...w it. > > Please also see the bug fixes in the following unapplied patch: > "[PATCH] ivshmem: fix potential OOB r/w access (#2)" by Sebastian Krahmer > https://lists.gnu.org/archive/html/qemu-devel/2014-04/msg03538.html Thanks for the pointer. I'll check it. -- David Marchand
2016 Jan 14
1
[PATCH] virtio_pci: fix use after free on release
...ove code. In virtio_pci_remove(), vp_dev is still used after being freed in unregister_virtio_device() (in virtio_pci_release_dev() more precisely). To fix, keep a reference until cleanup is done. Fixes: 63bd62a08ca4 ("virtio_pci: defer kfree until release callback") Reported-by: Jerome Marchand <jmarchan at redhat.com> Cc: stable at vger.kernel.org Cc: Sasha Levin <sasha.levin at oracle.com> Signed-off-by: Michael S. Tsirkin <mst at redhat.com> --- drivers/virtio/virtio_pci_common.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/drivers/virtio/virtio_pci_common.c...
2016 Jan 14
1
[PATCH] virtio_pci: fix use after free on release
...ove code. In virtio_pci_remove(), vp_dev is still used after being freed in unregister_virtio_device() (in virtio_pci_release_dev() more precisely). To fix, keep a reference until cleanup is done. Fixes: 63bd62a08ca4 ("virtio_pci: defer kfree until release callback") Reported-by: Jerome Marchand <jmarchan at redhat.com> Cc: stable at vger.kernel.org Cc: Sasha Levin <sasha.levin at oracle.com> Signed-off-by: Michael S. Tsirkin <mst at redhat.com> --- drivers/virtio/virtio_pci_common.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/drivers/virtio/virtio_pci_common.c...
2014 Jun 21
0
[Qemu-devel] Why I advise against using ivshmem
On Wed, Jun 18, 2014 at 10:57 PM, David Marchand <david.marchand at 6wind.com> wrote: > On 06/18/2014 12:48 PM, Stefan Hajnoczi wrote: >> >> One more thing to add to the list: >> >> static void ivshmem_read(void *opaque, const uint8_t * buf, int flags) >> >> The "flags" argument should be &qu...
2003 May 02
1
Problem with smbclient to Windows 2003 Server.
Hello! I?m writing to you all on behalf of my working party, a group of students at Chalmers Lindholmen University. We have been working on a problem for 6 weeks but we have come to a dead stop. If you could help us in any way we would remember it with gratitude and make sure it?s not forgotten! We are wondering if someone can assist us with a dilemma we have regarding Samba 3.0 alpha23 on
2004 May 04
1
nnet function
...gine that it is a single column transformation of the two matrices of weighs (input to hidden Ninputs+1 x Nodes) and hidden to output (Nodes+1 x Noutputs). Thanks ---------------------------------------------- Dr. Laurentiu Adi Tarca Post Doc. in Bioinformatics Forest Biology Research Center C-E-Marchand Bld, 3113 Laval University Quebec, (Qc) G1K-7P4 Tel: 656-2131 ext. 4509 e-mail: ltarca at rsvs.ulaval.ca
2014 Jun 17
0
[Qemu-devel] Why I advise against using ivshmem
Il 17/06/2014 11:03, David Marchand ha scritto: >> Unless someone steps up and maintains ivshmem, I think it should be >> deprecated and dropped from QEMU. > > Then I can maintain ivshmem for QEMU. > If this is ok, I will send a patch for MAINTAINERS file. Typically, adding yourself to maintainers is done only a...
2014 Jun 18
0
[Qemu-devel] Why I advise against using ivshmem
On Tue, Jun 17, 2014 at 11:03:32AM +0200, David Marchand wrote: > On 06/17/2014 04:54 AM, Stefan Hajnoczi wrote: > >ivshmem has a performance disadvantage for guest-to-host > >communication. Since the shared memory is exposed as PCI BARs, the > >guest has to memcpy into the shared memory. > > > >vhost-user can access gue...
2014 Jun 18
0
[Qemu-devel] Why I advise against using ivshmem
Il 18/06/2014 16:57, David Marchand ha scritto: > Hello Stefan, > > On 06/18/2014 12:48 PM, Stefan Hajnoczi wrote: >> One more thing to add to the list: >> >> static void ivshmem_read(void *opaque, const uint8_t * buf, int flags) >> >> The "flags" argument should be "size"....
2014 Jun 18
0
[Qemu-devel] Why I advise against using ivshmem
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Am 18.06.2014 12:48, schrieb Stefan Hajnoczi: > On Tue, Jun 17, 2014 at 11:44:11AM +0200, Paolo Bonzini wrote: >> Il 17/06/2014 11:03, David Marchand ha scritto: >>>> Unless someone steps up and maintains ivshmem, I think it >>>> should be deprecated and dropped from QEMU. >>> >>> Then I can maintain ivshmem for QEMU. If this is ok, I will >>> send a patch for MAINTAINERS file. >> >&g...
2004 Jul 06
1
aide pour une affiner une AFD.
madame, monsieur, help me please, Je debute avec R. J'ai r??alis?? une analyse factorielle discriminante avec R. J'obtient les resultat graphiques et les tables assici??es ?? l'analyse. Cependant je souhaiterais savoir si les distances separant les groupes (decades) sont statistiquement significatives. pour cela il me faut utiliser la distance de mahalanobis et la statistique de
2014 Apr 16
1
Connecting 2 asterisks, one with PJSIP and other SIP returning 401
It's my first post here, so I'll cut to the chase I have 2 Asterisk servers and want to connect them using sip on one and pjsip on the other one. One is running at home and another at a VPS. The first one will be the client (with dynamic ip) and the 2nd the server. The client uses sip and the server pjsip. This is the client's sip.conf [general] context = default allowguest = no
2014 Jun 13
3
[Qemu-devel] Why I advise against using ivshmem
Il 13/06/2014 15:41, Vincent JARDIN ha scritto: >> Fine, however Red Hat would also need a way to test ivshmem code, with >> proper quality assurance (that also benefits upstream, of course). With >> ivshmem this is not possible without the out-of-tree packages. > > You did not reply to my question: how to get the list of things that > are/will be disabled by Redhat? I
2014 Jun 13
3
[Qemu-devel] Why I advise against using ivshmem
Il 13/06/2014 15:41, Vincent JARDIN ha scritto: >> Fine, however Red Hat would also need a way to test ivshmem code, with >> proper quality assurance (that also benefits upstream, of course). With >> ivshmem this is not possible without the out-of-tree packages. > > You did not reply to my question: how to get the list of things that > are/will be disabled by Redhat? I
2016 Jan 14
0
Possible memory corruption in virtio-pci driver.
On Thu, Jan 14, 2016 at 02:25:50PM +0100, Jerome Marchand wrote: > Hi Michael, > > KASan detected a use-after-free error in virtio-pci remove code. In > virtio_pci_remove(), vp_dev is still used after being freed in > unregister_virtio_device() (in virtio_pci_release_dev() more > precisely). I don't know the proper way to fix this....