On Nov 30, 2007, at 3:12 PM, Carlo Marcelo Arenas Belon wrote:
right my bad, missed that on my copy of ATA-4 while looking for a
match to
your description of the mis-implementation, but why are you
asserting one
also for the reset?
My fault. I tried to make code common too quickly!
If I
Trivial patch adding CPU listing and the ability to do per-subtype
CVR/PVR/PRR values. The existing semantics aren't changed, as only
the SH7751R values are stubbed in for the moment, but the kernel is at
least able to get the cache probing correct.
This also makes it trivial to abstract subtype
This adds trivial support for the R2D-PLUS FPGA, mostly just for the
versioning information that the kernel uses for IRL mappings, in addition
to handling the heartbeat and poweroff writes.
Signed-off-by: Paul Mundt [EMAIL PROTECTED]
---
hw/r2d.c | 96
These patches allow to open file using O_DIRECT and bypass the host I/O cache.
The v2 is a new version including comments from Anthony Liguori (directio
has been renamed cache), from Balazs Attila-Mihaly (for Win32 support,
not tested) and Samuel Thibault (for the generic function
Le lundi 03 décembre 2007 à 11:23 +0100, Fabrice Bellard a écrit :
Laurent Vivier wrote:
This patch enhances the -drive ,cache=off mode with IDE drive emulation
by removing the buffer used in the IDE emulation.
---
block.c | 10 +++
block.h |2
block_int.h |1
Laurent Vivier wrote:
This patch enhances the -drive ,cache=off mode with IDE drive emulation
by removing the buffer used in the IDE emulation.
---
block.c | 10 +++
block.h |2
block_int.h |1
cpu-all.h |1
exec.c | 19 ++
hw/ide.c| 176
This patch enhances the -drive ,cache=off mode with IDE drive emulation
by removing the buffer used in the IDE emulation.
---
block.c | 10 +++
block.h |2
block_int.h |1
cpu-all.h |1
exec.c | 19 ++
hw/ide.c| 176
This patch adds a new parameter to -drive
Using cache=off with -drive will open the disk image file using
O_DIRECT.
By default, cache is set to on to keep original behavior of qemu.
example:
-drive file=my_disk.qcow2,cache=off
---
block-raw.c| 12
block.c|2 +-
Hi,
On Mon, 3 Dec 2007, Fabrice Bellard wrote:
Laurent Vivier wrote:
This patch enhances the -drive ,cache=off mode with IDE drive emulation
by removing the buffer used in the IDE emulation.
---
block.c | 10 +++
block.h |2 block_int.h |1 cpu-all.h |1
Am 03.12.2007 um 11:30 schrieb Laurent Vivier:
But if you think I should remove the buffered case, I can.
In doubt, less code is always better. For the unlikely case you broke
something badly, there's always the option to take back the patch.
BTW, do you think I should enable cache=off
Hi,
I don't know whether this is an easy one or not and if it will apply
to all archs, but I'd like to see an option in the monitor to
change/override the value given for -boot.
This way, for instance if you install a VM from a CDROM using -boot
d, you would be able to restart it on the
On Mon, Dec 03, 2007 at 01:34:16PM +, Gildas wrote:
Hi,
I don't know whether this is an easy one or not and if it will apply
to all archs, but I'd like to see an option in the monitor to
change/override the value given for -boot.
This way, for instance if you install a VM from a CDROM
Laurent Vivier wrote:
Le lundi 03 décembre 2007 à 11:23 +0100, Fabrice Bellard a écrit :
Laurent Vivier wrote:
This patch enhances the -drive ,cache=off mode with IDE drive emulation
by removing the buffer used in the IDE emulation.
---
block.c | 10 +++
block.h |2
On Monday 03 December 2007, Markus Hitter wrote:
Am 03.12.2007 um 11:30 schrieb Laurent Vivier:
But if you think I should remove the buffered case, I can.
In doubt, less code is always better. For the unlikely case you broke
something badly, there's always the option to take back the patch.
On Mon, Dec 03, 2007 at 01:34:16PM +, Gildas wrote:
Hi,
I don't know whether this is an easy one or not and if it will apply
to all archs, but I'd like to see an option in the monitor to
change/override the value given for -boot.
This way, for instance if you install a VM from a CDROM
CVSROOT:/sources/qemu
Module name:qemu
Changes by: Thiemo Seufer ths 07/12/03 17:05:38
Modified files:
. : monitor.c
Log message:
The profiler need qemu-timer.h
CVSWeb URLs:
Anthony Liguori, le Mon 03 Dec 2007 09:54:47 -0600, a écrit :
Have you done any performance testing? Buffered IO should absolutely
beat direct IO simply because buffered IO allows writes to complete
before they actually hit disk.
Since qemu can use the aio interface, that shouldn't matter.
On 12/3/07, Robert Reif [EMAIL PROTECTED] wrote:
This patch sets the maximum number of CPUs and memory to what is
supported by the actual hardware.
While it's not historically accurate to emulate a Sparcstation 5 with
16 CPUs and 2 gigabytes of memory, it doesn't break anything to have
this
On Monday 03 December 2007, Samuel Thibault wrote:
Anthony Liguori, le Mon 03 Dec 2007 09:54:47 -0600, a écrit :
Have you done any performance testing? Buffered IO should absolutely
beat direct IO simply because buffered IO allows writes to complete
before they actually hit disk.
Since
Paul Brook wrote:
On Monday 03 December 2007, Samuel Thibault wrote:
Anthony Liguori, le Mon 03 Dec 2007 09:54:47 -0600, a écrit :
Have you done any performance testing? Buffered IO should absolutely
beat direct IO simply because buffered IO allows writes to complete
before they
Samuel Thibault wrote:
Anthony Liguori, le Mon 03 Dec 2007 09:54:47 -0600, a écrit :
Have you done any performance testing? Buffered IO should absolutely
beat direct IO simply because buffered IO allows writes to complete
before they actually hit disk.
Since qemu can use the aio
Jamie Lokier wrote:
Paul Brook wrote:
On Monday 03 December 2007, Samuel Thibault wrote:
Anthony Liguori, le Mon 03 Dec 2007 09:54:47 -0600, a écrit :
Have you done any performance testing? Buffered IO should absolutely
beat direct IO simply because buffered IO allows writes
Anthony Liguori wrote:
With the IDE emulation, when the emulated disk write cache flag is
on it may be reasonable to report a write as completed when the AIO is
dispatched, without waiting for the AIO to complete.
An IDE flush cache command would wait for all outstanding write AIOs
to
Le lundi 03 décembre 2007 à 09:54 -0600, Anthony Liguori a écrit :
Laurent Vivier wrote:
Le lundi 03 décembre 2007 à 11:23 +0100, Fabrice Bellard a écrit :
Laurent Vivier wrote:
This patch enhances the -drive ,cache=off mode with IDE drive emulation
by removing the buffer used
2007/12/3, Dan Kenigsberg [EMAIL PROTECTED]:
On Mon, Dec 03, 2007 at 01:34:16PM +, Gildas wrote:
Hi,
I don't know whether this is an easy one or not and if it will apply
to all archs, but I'd like to see an option in the monitor to
change/override the value given for -boot.
This
Le lundi 03 décembre 2007 à 12:06 -0600, Anthony Liguori a écrit :
Samuel Thibault wrote:
Anthony Liguori, le Mon 03 Dec 2007 09:54:47 -0600, a écrit :
Have you done any performance testing? Buffered IO should absolutely
beat direct IO simply because buffered IO allows writes to
Yes, librt is providing posix-aio, and librt coming with GNU libc uses
threads.
But if I remember correctly librt coming with RHEL uses a mix of threads
and linux kernel AIO (you can have a look to the .srpm of libc).
BTW, if everyone thinks it could be a good idea I can port block-raw.c
to
Paul Brook, le Mon 03 Dec 2007 15:39:48 +, a écrit :
I think host caching is still useful enough to be enabled by default, and
provides a significant performance increase in several cases.
- The guest typically has a relatively small quantity of RAM, compared to a
modern machine.
2007/12/3, Daniel P. Berrange [EMAIL PROTECTED]:
On Mon, Dec 03, 2007 at 01:34:16PM +, Gildas wrote:
Hi,
I don't know whether this is an easy one or not and if it will apply
to all archs, but I'd like to see an option in the monitor to
change/override the value given for -boot.
Well, let's separate a few things. QEMU uses posix-aio which uses
threads and normal read/write operations. It also limits the number of
threads that aio uses to 1 which effectively makes everything
synchronous anyway.
This is a bug. Allegedly this is to workaround an old broken glibc, so
Hi,
BTW, if everyone thinks it could be a good idea I can port block-raw.c
to use linux kernel AIO (without removing POSIX AIO support, of course)
IMHO it would be a much better idea to kill the aio interface altogether
and instead make the block drivers reentrant. Then you can use
CVSROOT:/sources/qemu
Module name:qemu
Changes by: Andrzej Zaborowski balrog 07/12/04 00:11:33
Modified files:
hw : sd.c
Log message:
Don't claim SD card supports voltages linux claims are below defined
voltage range.
CVSWeb URLs:
Blue Swirl wrote:
On 12/3/07, Robert Reif [EMAIL PROTECTED] wrote:
This patch sets the maximum number of CPUs and memory to what is
supported by the actual hardware.
While it's not historically accurate to emulate a Sparcstation 5 with
16 CPUs and 2 gigabytes of memory, it doesn't
Log message:
Always create an SD bdrv, so that PXA and OMAP boards can boot with
no card inserted again. Eventually SD, CDROM and floppy should all
be registered conditionally depending on machine.
This seems the wrong way to solve this problem. The SD emulation should be
On 04/12/2007, Paul Brook [EMAIL PROTECTED] wrote:
On Tuesday 04 December 2007, andrzej zaborowski wrote:
On 04/12/2007, Paul Brook [EMAIL PROTECTED] wrote:
Log message:
Always create an SD bdrv, so that PXA and OMAP boards can boot
with no card inserted again. Eventually SD,
On Tuesday 04 December 2007, andrzej zaborowski wrote:
On 04/12/2007, Paul Brook [EMAIL PROTECTED] wrote:
Log message:
Always create an SD bdrv, so that PXA and OMAP boards can boot
with no card inserted again. Eventually SD, CDROM and floppy should
all be registered
On 04/12/2007, Paul Brook [EMAIL PROTECTED] wrote:
Log message:
Always create an SD bdrv, so that PXA and OMAP boards can boot with
no card inserted again. Eventually SD, CDROM and floppy should all
be registered conditionally depending on machine.
This seems the wrong
Hi,
the -drive patch changed the name strings to for block devices to
driven, which carries about as much information as a serial
number. With the previous naming the devices were easier to
distinguish in the output of info block so I would like to change
the naming and propose interfaceindex
any comments on the current status of moving beyond dependency on GCC 3.3.6?
no need to go into details of 'why' on my behalf, so spare yourself the time
on that... :-)
thanks
39 matches
Mail list logo