On Thu, Jul 21, 2011 at 4:49 PM, Anthony Liguori wrote:
[cut]
> And it's really not that much nicer than the C version. The problem with
> C++ is that even though the type system is much, much nicer, it still
> doesn't have introspection or decorators. These two things would be the
> killer feat
On Mon, Sep 6, 2010 at 12:25 PM, Alexander Graf wrote:
> On 06.09.2010, at 12:04, Stefan Hajnoczi wrote:
>> +
>> +const char *bytes_to_str(uint64_t size)
>> +{
>> + static char buffer[64];
>> +
>> + if (size < (1ULL << 10)) {
>> + snprintf(buffer, sizeof(buffer), "%" PRIu64 " byte(s)"
On Tue, Dec 29, 2009 at 2:21 PM, Jamie Lokier wrote:
> Avi Kivity wrote:
>> Guests use this number as a hint for alignment and I/O request sizes.
>
> It's not just a hint. It is also the "radius of corruption on failed
> write" - important for journalling filesystems and databases.
>
>> Given
>>
Andreas Färber ha scritto:
> Am 25.08.2007 um 09:37 schrieb Andreas F=E4rber:
>
>> One of the recent patches (dynticks) has broken compilation on Mac
>> OS X v10.4. Should this work on OS X or should this have been
>> limited to Linux?
>
> Getting no answer on this I have prepared a quickfix which
Il Wed, Aug 22, 2007 at 08:02:07AM +0300, Avi Kivity ha scritto:
> Luca Tettamanti wrote:
>
> > Actually I'm having troubles with cyclesoak (probably it's calibration),
> > numbers are not very stable across multiple runs...
> >
>
> I've had good
Avi Kivity ha scritto:
> Luca Tettamanti wrote:
>> At 1000Hz:
>>
>> QEMU
>> hpet5.5%
>> dynticks 11.7%
>>
>> KVM
>> hpet3.4%
>> dynticks7.3%
>>
>> No surprises here, you can see the additi
Il Sun, Aug 19, 2007 at 10:31:26PM +0300, Avi Kivity ha scritto:
> Luca wrote:
> > On 8/19/07, Luca Tettamanti <[EMAIL PROTECTED]> wrote:
> >
> >> +static uint64_t qemu_next_deadline(void) {
> >> +uint64_t nearest_delta_us = ULLONG_MAX;
> >>
se the dyn-tick minimum res will be 1msec. I believe it should
> work ok since this is the case without any dyn-tick.
Actually minimum resolution depends on host HZ setting, but - yes -
essentially you have the same behaviour of the "unix" timer, plus the
overhead of reprogramming the t
Allow user to override the list of available alarm timers and their
priority. The format of the options is -clock clk1,clk2,...
Signed-off-by: Luca Tettamanti <[EMAIL PROTECTED]>
---
vl.c | 72 +++
1 file changed, 72 inse
AIL PROTECTED]>
Signed-off-by: Luca Tettamanti <[EMAIL PROTECTED]>
---
configure |5 ++
vl.c | 149 +++---
2 files changed, 148 insertions(+), 6 deletions(-)
Inde
ed in the
same way as the RTC timer.
Signed-off-by: Luca Tettamanti <[EMAIL PROTECTED]>
---
vl.c | 57 -
1 file changed, 56 insertions(+), 1 deletion(-)
Index
Hello,
in reply to this mail I will send a serie of 4 patches that cleans up and
expands the alarm timer handling in QEMU. Patches have been rebased on QEMU
CVS.
Patch 1 is mostly a cleanup of the existing code; instead of having multiple
#ifdefs to handle different timers scattered all over the c
Make the alarm code modular, removing #ifdef from the generic code and
abstract a common interface for all the timer. The result is functionally
equivalent to the old code.
Signed-off-by: Luca Tettamanti <[EMAIL PROTECTED]>
---
vl.c
AIL PROTECTED]>
Signed-off-by: Luca Tettamanti <[EMAIL PROTECTED]>
---
qemu/configure |5 ++
qemu/vl.c | 149 --
2 files changed, 148 insertions(+), 6 deletions(-)
diff --git a/qemu/configure b/qemu/configure
index 365b7fb..38373db 10075
Make the alarm code modular, removing #ifdef from the generic code and
abstract a common interface for all the timer. The result is functionally
equivalent to the old code.
Signed-off-by: Luca Tettamanti <[EMAIL PROTECTED]>
---
qemu/vl.c
ed in the
same way as the RTC timer.
Signed-off-by: Luca Tettamanti <[EMAIL PROTECTED]>
---
qemu/vl.c | 57 ++-
1 files changed, 56 insertions(+), 1 deletions(-)
diff --git a/qemu/vl.c b/qemu/vl.c
index f0b4896..0373beb 100644
--- a/qemu/vl.c
Hello,
in reply to this mail I will send a serie of 4 patches that cleans up and
expands
the alarm timer handling in QEMU. Patches apply to current kvm-userspace tree,
but I think I can rebase it to QEMU svn if desired.
Patch 1 is mostly a cleanup of the existing code; instead of having multiple
Allow user to override the list of available alarm timers and their
priority. The format of the options is -clock clk1,clk2,...
Signed-off-by: Luca Tettamanti <[EMAIL PROTECTED]>
---
qemu/vl.c | 90 --
1 files changed, 72 insertions(
Il Mon, Aug 13, 2007 at 05:42:55PM +0300, Dan Kenigsberg ha scritto:
> "Dynamic ticks" in Qemu: have a SIGALRM generated only when it is
> needed, instead of every 1 millisecond. This patch requires that the
> host supports high resolution timers, since it arms a POSIX timer to the
> nearest Qemu
ed in the same way as the
RTC timer.
HPET must be explicitly enabled with -use-hpet.
Signed-off-by: Luca Tettamanti <[EMAIL PROTECTED]>
---
qemu/vl.c | 62 +-
1 files changed, 60 insertions(+), 2 deletions(-)
diff --git a/qemu/vl.c b/qemu
Hello,
I'm testing the new Fedora7 under KVM. As you may know Fedora has
migrated to the new libata drivers.
ata_piix is unhappy with the PIIX IDE controller provided by QEmu/KVM:
libata version 2.20 loaded.
ata_piix :00:01.1: version 2.10ac1
PCI: Setting latency timer of device :00:01.1
21 matches
Mail list logo
