On Tue 02 Jun 2015 12:56:10 PM CEST, Kevin Wolf wrote:
>> > It seems that getpagesize() is usually used in qemu.
>>
>> The getpagesize() manual page actually recommends using sysconf() for
>> portability reasons. But other than that I don't have a problem with
>> getpagesize() if it's the preferr
Am 02.06.2015 um 12:50 hat Alberto Garcia geschrieben:
> On Tue 02 Jun 2015 12:05:59 PM CEST, Kevin Wolf wrote:
>
> >> +#include
> >> #include "block/block_int.h"
> >> #include "qemu-common.h"
> >> +#include "qemu/osdep.h"
> >> #include "qcow2.h"
> >> #include "trace.h"
> >
> > This breaks t
On Tue 02 Jun 2015 12:05:59 PM CEST, Kevin Wolf wrote:
>> +#include
>> #include "block/block_int.h"
>> #include "qemu-common.h"
>> +#include "qemu/osdep.h"
>> #include "qcow2.h"
>> #include "trace.h"
>
> This breaks the mingw build:
>
> /mnt/qemu/block/qcow2-cache.c:25:22: fatal error: sys/m
Am 29.05.2015 um 11:24 hat Alberto Garcia geschrieben:
> After having emptied the cache, the data in the cache tables is no
> longer useful, so we can tell the kernel that we are done with it. In
> Linux this frees the resources associated with it.
>
> The effect of this can be seen in the HMP com
After having emptied the cache, the data in the cache tables is no
longer useful, so we can tell the kernel that we are done with it. In
Linux this frees the resources associated with it.
The effect of this can be seen in the HMP commit operation: it moves
data from the top to the base image (and
After having emptied the cache, the data in the cache tables is no
longer useful, so we can tell the kernel that we are done with it. In
Linux this frees the resources associated with it.
The effect of this can be seen in the HMP commit operation: it moves
data from the top to the base image (and
After having emptied the cache, the data in the cache tables is no
longer useful, so we can tell the kernel that we are done with it. In
Linux this frees the resources associated with it.
The effect of this can be seen in the HMP commit operation: it moves
data from the top to the base image (and
On 26.05.2015 17:51, Alberto Garcia wrote:
On Tue 26 May 2015 05:39:12 PM CEST, Max Reitz wrote:
After having emptied the cache, the data in the cache tables is no
longer useful, so we can tell the kernel that we are done with it. In
Linux this frees the resources associated with it.
Looks go
On Tue 26 May 2015 05:39:12 PM CEST, Max Reitz wrote:
>> After having emptied the cache, the data in the cache tables is no
>> longer useful, so we can tell the kernel that we are done with it. In
>> Linux this frees the resources associated with it.
> Looks good, but by applying the same logic,
On 18.05.2015 18:48, Alberto Garcia wrote:
After having emptied the cache, the data in the cache tables is no
longer useful, so we can tell the kernel that we are done with it. In
Linux this frees the resources associated with it.
The effect of this can be seen in the block-commit operation: it
After having emptied the cache, the data in the cache tables is no
longer useful, so we can tell the kernel that we are done with it. In
Linux this frees the resources associated with it.
The effect of this can be seen in the block-commit operation: it moves
data from the top to the base image (an
11 matches
Mail list logo
