On Thursday 06 September 2007, Lapo Luchini wrote:
> I noticed that cow adds space also if the written data is the same as
> the one it was there already.
> Is there a reason why checking it would be bad/difficult/slow/other?
> Simply no one had the will to code the check?
Simply that your operati
Anthony Liguori wrote:
> I like this idea but I have some suggestions about the general approach.
> I think instead of defining another machine type, it would be better to
> just have a command line option like -cpuid that took a comma separate
> string of features with "all" meaning all features t
I noticed that cow adds space also if the written data is the same as
the one it was there already.
Is there a reason why checking it would be bad/difficult/slow/other?
Simply no one had the will to code the check?
I ask because for shrinking drives I usually create big zero-filled
files... and th
Hi,
earlier this week I needed to use gdb with QEMU to debug some software
of mine that runs in a 64-bit code segment. But gdb only gave me
nonsense data because QEMU sent it a normal i386 register dump.
The following patch fixes cpu_gdb_read_registers() so that it works
for 64-bit code segments.
