Stefan Hajnoczi writes:
> On Fri, Nov 28, 2014 at 02:41:54PM +0100, Markus Armbruster wrote:
>> Stefan Hajnoczi writes:
>>
>> > On Wed, Nov 26, 2014 at 03:01:02PM +0100, Paolo Bonzini wrote:
>> >> Use the external qemu-timer API instead.
>> >>
>> >> Cc: kw...@redhat.com
>> >> Cc: stefa...@redh
On Fri, Nov 28, 2014 at 02:41:54PM +0100, Markus Armbruster wrote:
> Stefan Hajnoczi writes:
>
> > On Wed, Nov 26, 2014 at 03:01:02PM +0100, Paolo Bonzini wrote:
> >> Use the external qemu-timer API instead.
> >>
> >> Cc: kw...@redhat.com
> >> Cc: stefa...@redhat.com
> >> Signed-off-by: Paolo Bo
Stefan Hajnoczi writes:
> On Wed, Nov 26, 2014 at 03:01:02PM +0100, Paolo Bonzini wrote:
>> Use the external qemu-timer API instead.
>>
>> Cc: kw...@redhat.com
>> Cc: stefa...@redhat.com
>> Signed-off-by: Paolo Bonzini
>> ---
>> block/accounting.c | 6 --
>> block/raw-posix.c | 8
On Wed, Nov 26, 2014 at 03:01:02PM +0100, Paolo Bonzini wrote:
> Use the external qemu-timer API instead.
>
> Cc: kw...@redhat.com
> Cc: stefa...@redhat.com
> Signed-off-by: Paolo Bonzini
> ---
> block/accounting.c | 6 --
> block/raw-posix.c | 8
> 2 files changed, 8 insertions(+)
On 27/11/2014 18:45, Markus Armbruster wrote:
>> >
>> > Because no one else calls it directly, it is an internal function. I
>> > want to keep it confined to qemu-timer.c (and possibly cpus.c in the
>> > icount implementation, but maybe not even that is necessary).
> That's a perfectly sensible
Paolo Bonzini writes:
> On 27/11/2014 10:19, Markus Armbruster wrote:
>> Paolo Bonzini writes:
>>
>>> Use the external qemu-timer API instead.
>>
>> Ignorant question: why?
>
> Because no one else calls it directly, it is an internal function. I
> want to keep it confined to qemu-timer.c (and
On 27/11/2014 17:44, Stefan Hajnoczi wrote:
> On Thu, Nov 27, 2014 at 10:19:45AM +0100, Markus Armbruster wrote:
>> Paolo Bonzini writes:
>>
>>> Use the external qemu-timer API instead.
>>
>> Ignorant question: why?
>
> Patch seems fine but I concur with Markus. Let's add the rationale to
> th
On Thu, Nov 27, 2014 at 10:19:45AM +0100, Markus Armbruster wrote:
> Paolo Bonzini writes:
>
> > Use the external qemu-timer API instead.
>
> Ignorant question: why?
Patch seems fine but I concur with Markus. Let's add the rationale to
the commit description.
pgpj67g1P8W4L.pgp
Description: P
On 27/11/2014 10:19, Markus Armbruster wrote:
> Paolo Bonzini writes:
>
>> Use the external qemu-timer API instead.
>
> Ignorant question: why?
Because no one else calls it directly, it is an internal function. I
want to keep it confined to qemu-timer.c (and possibly cpus.c in the
icount imp
Paolo Bonzini writes:
> Use the external qemu-timer API instead.
Ignorant question: why?
Use the external qemu-timer API instead.
Cc: kw...@redhat.com
Cc: stefa...@redhat.com
Signed-off-by: Paolo Bonzini
---
block/accounting.c | 6 --
block/raw-posix.c | 8
2 files changed, 8 insertions(+), 6 deletions(-)
diff --git a/block/accounting.c b/block/accounting.c
index edbb
11 matches
Mail list logo