Re: [Qemu-devel] DMA in Windows 2000/XP/2003

2005-08-24 Thread Jan Marten Simons
Víctor Córcoles López wrote: Hello developers. My English is not good. I see that DMA in Hard Disks in guest OS Windows 2000/XP/2003 is not avalaible, it run in PIO mode. How can activate UDMA mode for hard disk ? I don't think you'd get any advantage of activating DMA inside the qemu

Re: [Qemu-devel] [PATCH] const / static (against current CVS)

2005-08-24 Thread Doctor Bill
My own experience is the effect of these types of optimizations is usually negligible, although it is still the first thing I do when optimizing a program. The main improvement I find is reducing the time required to initialize variables and improved code readability. If you know values are

Re: [Qemu-devel] [PATCH] const / static (against current CVS)

2005-08-24 Thread Paul Brook
Probably more important is to make sure none constant data structures are done on the stack. There is no good reason why any code page should be read-write. Huh? this is nonsense. You have three segements in an application (ignoring dynamic heap allocated memory): The RO segment that

Re: [Qemu-devel] DMA in Windows 2000/XP/2003

2005-08-24 Thread André Braga
Fortunately, it does make a difference. PIO is polling-base, whereas DMA is, lacking a better term (excuse my English), transaction-based. Since no CPU arbitration is needed, quite a few optimizations can be done because of this, like real, large block transfers. And if you happen to search the

Re: [Qemu-devel] [PATCH] const / static (against current CVS)

2005-08-24 Thread Paul Brook
On Wednesday 24 August 2005 15:38, Andreas Mohr wrote: Hi, On Wed, Aug 24, 2005 at 02:41:44PM +0100, Paul Brook wrote: Probably more important is to make sure none constant data structures are done on the stack. There is no good reason why any code page should be read-write. Huh?

Re: [Qemu-devel] [PATCH] const / static (against current CVS)

2005-08-24 Thread Doctor Bill
On Wed, Aug 24, 2005 at 02:41:44PM +0100, Paul Brook wrote: Probably more important is to make sure none constant data structures are done on the stack. There is no good reason why any code page should be read-write. Huh? this is nonsense. I stand corrected, I ment to say on the

[Qemu-devel] Read/Write to shares on Windows (XP Pro) host from Windows (2000 Adv) guest.

2005-08-24 Thread Francois Rioux
Hi, What I'm trying to achieve is to write a file from a guest OS to a host. In this case both are Windows OS. I use the user network command line options since I looking for a no install on host, portablesolution. I've tried various build in solutions: -tftp (read-only), and -smb (not

Re: [Qemu-devel] Read/Write to shares on Windows (XP Pro) host from Windows (2000 Adv) guest.

2005-08-24 Thread John R. Hogerhuis
On Wed, 2005-08-24 at 19:23 -0700, Francois Rioux wrote: I don't understand why this doesn't work. Is it Windows preventing the write is the exchange this a limitation in QEMU or in SLiRP? As I understand it SLiRP translates some tcp headers and acts as a firewall preventing incoming calls