From: Avi Kivity <avi@redhat.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: KVM list <kvm@vger.kernel.org>
Subject: Re: Reconciling qemu-kvm and qemu's PIT
Date: Wed, 29 Feb 2012 16:42:22 +0200 [thread overview]
Message-ID: <4F4E394E.40805@redhat.com> (raw)
In-Reply-To: <4F4E352A.4090109@siemens.com>
On 02/29/2012 04:24 PM, Jan Kiszka wrote:
> On 2012-02-29 14:45, Avi Kivity wrote:
> > On 02/29/2012 12:14 PM, Jan Kiszka wrote:
> >> On 2012-02-29 10:29, Avi Kivity wrote:
> >>> On 02/28/2012 11:47 PM, Jan Kiszka wrote:
> >>>>>
> >>>>> Looks like isa-pit has zero gpio pins, so it fails when crashing. I
> >>>>> must have mismerged it, but where is the gpio pin count set?
> >>>>
> >>>> In pit_initfn. Does -no-kvm-irqchip work fine? It's a bit tricky to
> >>>> discuss this without seeing your code.
> >>>>
> >>>
> >>> pushed it into qemu-kvm.git usptream-merge
> >>>
> >>
> >> As I assumed: You try to initialize the kvm-pit like the userspace pit,
> >> that cannot work. Don't run the qdev_connect_gpio_out in pit_init, just
> >> like my kvm-pit patches does in their kvm_pit_init.
> >>
> >
> > The merge is now in 'next', hopefully not too many regressions.
>
> Hope we can quickly finish the switch to the new kvm-pit.
>
> When do you plan to push or rebase uq/master? Then I could check/refresh
> my kvm-pit series on top of it.
Real soon... I hoped to do it after the upstream merge, but it doesn't
pass autotest due to a screendump regression.
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2012-02-29 14:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-28 14:32 Reconciling qemu-kvm and qemu's PIT Avi Kivity
2012-02-28 14:40 ` Jan Kiszka
2012-02-28 14:42 ` Avi Kivity
2012-02-28 19:50 ` Avi Kivity
2012-02-28 21:47 ` Jan Kiszka
2012-02-29 9:29 ` Avi Kivity
2012-02-29 10:14 ` Jan Kiszka
2012-02-29 13:45 ` Avi Kivity
2012-02-29 14:24 ` Jan Kiszka
2012-02-29 14:42 ` Avi Kivity [this message]
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=4F4E394E.40805@redhat.com \
--to=avi@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=kvm@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).