Jens Axboe wrote:
On Tue, Aug 01 2006, Jamie Lokier wrote:
Should we change to only reiserfs and expect fsync() to commit data
reliably only with that fs? I realise this is a lot of difficult
questions, that apply to more than just Qemu...
Yes, reiser is the only one that works reliably
Thomas Steffen wrote:
On 8/7/06, R. Armiento [EMAIL PROTECTED] wrote:
And some IDE disks do not let you switch off write-caching. So as far
as I know, you need SCSI for transactional guarantees.
I don't think the fact that there are some buggy drives/firmwares out
there should be taken
R. Armiento wrote:
Couldn't there be situations where someone depends on mwait waking up
without there being an event that wakes hlt? Or are we sure qemu's hlt
will happen to wake up anyway?
Joachim Henke wrote:
Currently the Linux kernel simply uses monitor/mwait as a faster 'hlt
Hi,
Joachim Henke wrote:
Please use the updated patch attached below.
Great work! The patch fixes the kernel panic for me. Thank you.
However, as you probably know, despite not declaring MONITOR in qemu,
kqemu sees MONITOR on the host processor and Linux CPU usage will still
be 100%, even
Hi,
Again, thank you for helping out with updated patches, it is much
appreciated.
Joachim Henke wrote:
R. Armiento wrote:
So even with your patch applied one should use the 'idle=halt'
kernel parameter when booting Linux with -kernel-kqemu on newer
processors. [...]
To lower the cpu usage
R. Armiento wrote:
The error looks very similar to the one reported here:
http://www.mail-archive.com/qemu-devel@nongnu.org/msg03964.html
But I believe that reported issue should not appear in recent qemu,
since SSE3 is now emulated (right?). (At least the patch in the end of
that thread
