From: Paolo Bonzini <pbonzini@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: Anthony Liguori <anthony@codemonkey.ws>,
qemu-devel <qemu-devel@nongnu.org>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
Markus Armbruster <armbru@redhat.com>
Subject: Re: [Qemu-devel] KVM call agenda for Tuesday 24
Date: Tue, 24 Jan 2012 15:53:28 +0100 [thread overview]
Message-ID: <4F1EC5E8.9050600@redhat.com> (raw)
In-Reply-To: <4F1EC099.9080705@redhat.com>
On 01/24/2012 03:30 PM, Kevin Wolf wrote:
>>> >> * qtest/libos: Python or C?
>> >
>> > Both.
> More importantly: When?:-)
>
> Are there still any problems that must be fixed before it can be merged?
There was no discussion on my alternative proposal on IRQ interception.
Which might mean it's all fine and it will just replace Anthony's
qtest_interrupt_controller, but I'm not that optimist. :) Certainly
Anthony's approach to IRQ interception had some objections from Peter
(which I second).
Also, Anthony's sleep(1) hack _can_ be eliminated, I didn't have it in
my Python version.
In that series I also had vm_clock management, but it can go in afterwards.
Similarly, PyUnit integration can be committed separately. Knowing that
the answer is "both" is fine.
URLs:
http://thread.gmane.org/gmane.comp.emulators.qemu/132558 (IRQ/timer)
http://thread.gmane.org/gmane.comp.emulators.qemu/132512 (Python)
Paolo
WARNING: multiple messages have this Message-ID (diff)
From: Paolo Bonzini <pbonzini@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: Markus Armbruster <armbru@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: [Qemu-devel] KVM call agenda for Tuesday 24
Date: Tue, 24 Jan 2012 15:53:28 +0100 [thread overview]
Message-ID: <4F1EC5E8.9050600@redhat.com> (raw)
In-Reply-To: <4F1EC099.9080705@redhat.com>
On 01/24/2012 03:30 PM, Kevin Wolf wrote:
>>> >> * qtest/libos: Python or C?
>> >
>> > Both.
> More importantly: When?:-)
>
> Are there still any problems that must be fixed before it can be merged?
There was no discussion on my alternative proposal on IRQ interception.
Which might mean it's all fine and it will just replace Anthony's
qtest_interrupt_controller, but I'm not that optimist. :) Certainly
Anthony's approach to IRQ interception had some objections from Peter
(which I second).
Also, Anthony's sleep(1) hack _can_ be eliminated, I didn't have it in
my Python version.
In that series I also had vm_clock management, but it can go in afterwards.
Similarly, PyUnit integration can be committed separately. Knowing that
the answer is "both" is fine.
URLs:
http://thread.gmane.org/gmane.comp.emulators.qemu/132558 (IRQ/timer)
http://thread.gmane.org/gmane.comp.emulators.qemu/132512 (Python)
Paolo
next prev parent reply other threads:[~2012-01-24 14:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-23 17:38 KVM call agenda for Tuesday 24 Markus Armbruster
2012-01-23 17:38 ` [Qemu-devel] " Markus Armbruster
2012-01-24 13:57 ` Anthony Liguori
2012-01-24 13:57 ` Anthony Liguori
2012-01-24 14:03 ` Paolo Bonzini
2012-01-24 14:08 ` Anthony Liguori
2012-01-24 14:08 ` Anthony Liguori
2012-01-24 14:30 ` Kevin Wolf
2012-01-24 14:53 ` Paolo Bonzini [this message]
2012-01-24 14:53 ` Paolo Bonzini
2012-01-24 14:32 ` Markus Armbruster
2012-01-24 14:32 ` Markus Armbruster
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F1EC5E8.9050600@redhat.com \
--to=pbonzini@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=armbru@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.