Displaying 7 results from an estimated 7 matches for "bouce".
Did you mean:
bounce
2006 Mar 05
1
[patch] Effect.Move and a little experiment
i everybody! first at all, sorry about my poor english...
i''m working in a little experiment about boucing objects using
Effect.Move implementation and a couple Effect.Transitions''
but... i was stuck in the way how Effect.Move works. I need to move a
object in two dimensions: X and Y, but in different times....
Effect.Parallel not work for me, because meanwhile the object
2009 Jul 23
7
Ubuntu crashes when gaming
Hello,
I am a french Ubuntu user since a few weeks. So, please excuse my English and my Technical knowledge.
I've got a problem when I play games with wine : my computer crashes and reboots.
I tried two games : wow and oblivion.
Here is my config :
ubuntu 9.04 ? Jaunty Jackalope ? 64 bits + Ext 4
Graphic card GeForce GTX 260 PLUS - 896 Mo DDR3
INTEL Core 2 Quad Q9400 - 2.66 GHz
3 x
2002 Oct 22
0
Samba users on Windows 2000 server
Hello,
We have used successfully Samba suite for 5 years and it's a real
pleasure to work with these safe and powerful products. ;-) Thank's to
samba team.
We have a Solaris Server with Samba 2.2.3a and a list of about 20
running volumes. Each person has a private connection with our data
sphere via Samba (directly with PC, NFS with UNIX and Samba + DAVE with
Mac). We have also a W2K
2018 Aug 07
2
[RFC 0/4] Virtio uses DMA API for all devices
...t does. It's the guest itself that initiates it. That's my
point, it's not a factor of the hypervisor, which is unchanged in that
area.
It's the guest itself, that makes the decision early on, to stash it's
memory away in a secure place, and thus needs to establish some kind of
bouce buffering via a few left over "insecure" pages.
It's all done by the guest: initiated by the guest and controlled by
the guest.
That's why I don't see why this specifically needs to involve the
hypervisor side, and thus a VIRTIO feature bit.
Note that I can make it so that...
2018 Aug 07
2
[RFC 0/4] Virtio uses DMA API for all devices
...t does. It's the guest itself that initiates it. That's my
point, it's not a factor of the hypervisor, which is unchanged in that
area.
It's the guest itself, that makes the decision early on, to stash it's
memory away in a secure place, and thus needs to establish some kind of
bouce buffering via a few left over "insecure" pages.
It's all done by the guest: initiated by the guest and controlled by
the guest.
That's why I don't see why this specifically needs to involve the
hypervisor side, and thus a VIRTIO feature bit.
Note that I can make it so that...
2018 Aug 06
2
[RFC 0/4] Virtio uses DMA API for all devices
On Mon, 2018-08-06 at 02:42 -0700, Christoph Hellwig wrote:
> On Mon, Aug 06, 2018 at 07:16:47AM +1000, Benjamin Herrenschmidt wrote:
> > Who would set this bit ? qemu ? Under what circumstances ?
>
> I don't really care who sets what. The implementation might not even
> involved qemu.
>
> It is your job to write a coherent interface specification that does
> not
2018 Aug 06
2
[RFC 0/4] Virtio uses DMA API for all devices
On Mon, 2018-08-06 at 02:42 -0700, Christoph Hellwig wrote:
> On Mon, Aug 06, 2018 at 07:16:47AM +1000, Benjamin Herrenschmidt wrote:
> > Who would set this bit ? qemu ? Under what circumstances ?
>
> I don't really care who sets what. The implementation might not even
> involved qemu.
>
> It is your job to write a coherent interface specification that does
> not