search for: baken

...onvenient" for sales people) FWIW the context were large "old-school" corps (like Novell or Oracle) taking over free software companies. > that is simple not true - if it would be true linux distributions would Define "true Linux distribution". > not include half baken and aplha quality sofwtare again and again in > stable releases because "the market out there" That's everywhere in the commercial world the problem with "delivery vs quality/known problems" and someone's decision to ship or not to ship - based in whatever feels app...

On Don, 2015-03-26 at 17:01 +0200, Andreas Kasenides wrote: > On 26/03/15 13:05, Bernd Petrovitsch wrote: > > On Mon, 2015-03-23 at 16:08 +0200, Andreas Kasenides wrote: > >> I am usually emotionally (at least) against of open-source projects > >> loosing their independence to large corporations. Possibly due to bad > > OX-AG is a "large corporation"?

...like. Free software/OSS just happens that *at > least* half of it should come from the "working level" and that is - at > least - much more - ahemm - "inconvenient" for sales people) that is simple not true - if it would be true linux distributions would not include half baken and aplha quality sofwtare again and again in stable releases because "the market out there" the *possible* long-term benefits are more time to invest because a fixed income -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: applica...

...018 at 02:16:44PM -0700, Siwei Liu wrote: > Good to see this discussion going. I share the same feeling that the > decision of plugging the primary (passthrough) should only be made > until guest driver acknowledges DRIVER_OK and _F_STANDBY. > Architecturally this intelligence should be baken to QEMU itself > rather than moving up to management stack, such as libvirt. > > A few questions in line below. > > On Tue, Jun 5, 2018 at 5:33 AM, Michael S. Tsirkin <mst at redhat.com> wrote: > > I don't think this is sufficient. > > > > If both primar...

...ike Novell or Oracle) > taking over free software companies. > >> that is simple not true - if it would be true linux distributions would > > Define "true Linux distribution". who the fuck was talking abiut "true Linux distribution"? >> not include half baken and aplha quality sofwtare again and again in >> stable releases because "the market out there" > > That's everywhere in the commercial world the problem with "delivery vs > quality/known problems" and someone's decision to ship or not to ship - > based...

Here, this has cc the maintainers of AF_XDP. For on the same page, I summarize it. We discusses this question last at [1]. We planned to pass one device to xsk. Then xsk can use the DMA API on this device. The device can be one hw device(such as PCI, mmio) or virtio device. If it is one hw device, no problem. If it is one virtio device, then we expect that DMA API on that will return direct dma

Good to see this discussion going. I share the same feeling that the decision of plugging the primary (passthrough) should only be made until guest driver acknowledges DRIVER_OK and _F_STANDBY. Architecturally this intelligence should be baken to QEMU itself rather than moving up to management stack, such as libvirt. A few questions in line below. On Tue, Jun 5, 2018 at 5:33 AM, Michael S. Tsirkin <mst at redhat.com> wrote: > I don't think this is sufficient. > > If both primary and standby devices are present, a leg...

...M -0700, Siwei Liu wrote: >> Good to see this discussion going. I share the same feeling that the >> decision of plugging the primary (passthrough) should only be made >> until guest driver acknowledges DRIVER_OK and _F_STANDBY. >> Architecturally this intelligence should be baken to QEMU itself >> rather than moving up to management stack, such as libvirt. >> >> A few questions in line below. >> >> On Tue, Jun 5, 2018 at 5:33 AM, Michael S. Tsirkin <mst at redhat.com> wrote: >> > I don't think this is sufficient. >> &gt...

Hello guys... I compiled inside of "mock" libdrm 2.67 mesa 11.2.1 ati 7.6.1 mockbuild says: libdrm x86_64 2.4.67-1.20160218gitadd8936.el7.centos local-drivers - OK mesa-libGL-devel x86_64 11.1.2-1.20160210.el7.centos local-mesa - OK installed packaged: xorg-x11-drv-ati.x86_64 7.6.1-1.el7.centos @local-drivers OK libdrm.x86_64 2.4.67-1.20160218gitadd8936.el7.centos OK

I don't think this is sufficient. If both primary and standby devices are present, a legacy guest without support for the feature might see two devices with same mac and get confused. I think that we should only make primary visible after guest acked the backup feature bit. And on reset or when backup is cleared in some other way, unplug the primary. Something like the below will do the

I don't think this is sufficient. If both primary and standby devices are present, a legacy guest without support for the feature might see two devices with same mac and get confused. I think that we should only make primary visible after guest acked the backup feature bit. And on reset or when backup is cleared in some other way, unplug the primary. Something like the below will do the