From: Paolo Bonzini <pbonzini@redhat.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Alexander Graf <agraf@suse.de>,
kvm@vger.kernel.org, Peter Maydell <peter.maydell@linaro.org>,
Jan Kiszka <jan.kiszka@siemens.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
David Gibson <dwg@au1.ibm.com>
Subject: Re: Interrupt controller updates
Date: Thu, 22 Nov 2012 11:25:44 +0100 [thread overview]
Message-ID: <50ADFDA8.9010003@redhat.com> (raw)
In-Reply-To: <1353460020.17856.25.camel@pasglop>
Il 21/11/2012 02:07, Benjamin Herrenschmidt ha scritto:
> David (CC) want to make some progress with our in-kernel PIC. From
> memory, one of the outcomes of the BOF was that we need to move the
> existing "enable in-kernel PIC" from generic KVM init to machine init in
> order to be able to add an argument indicating the "model" use by the
> arch/platform since some like ours support several different models and
> since that all needs to be selected before the VCPUs are created.
>
> Again, from memory, you were volunteered to do the initial x86 change so
> we could piggy back on it :-) Or do I remember wrong ?
Please suggest an API, then we can work out the x86 changes. I can
volunteer myself, but I wasn't in the BOF so I need something more concrete.
Paolo
WARNING: multiple messages have this Message-ID (diff)
From: Paolo Bonzini <pbonzini@redhat.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Alexander Graf <agraf@suse.de>,
kvm@vger.kernel.org, Peter Maydell <peter.maydell@linaro.org>,
Jan Kiszka <jan.kiszka@siemens.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
David Gibson <dwg@au1.ibm.com>
Subject: Re: [Qemu-devel] Interrupt controller updates
Date: Thu, 22 Nov 2012 11:25:44 +0100 [thread overview]
Message-ID: <50ADFDA8.9010003@redhat.com> (raw)
In-Reply-To: <1353460020.17856.25.camel@pasglop>
Il 21/11/2012 02:07, Benjamin Herrenschmidt ha scritto:
> David (CC) want to make some progress with our in-kernel PIC. From
> memory, one of the outcomes of the BOF was that we need to move the
> existing "enable in-kernel PIC" from generic KVM init to machine init in
> order to be able to add an argument indicating the "model" use by the
> arch/platform since some like ours support several different models and
> since that all needs to be selected before the VCPUs are created.
>
> Again, from memory, you were volunteered to do the initial x86 change so
> we could piggy back on it :-) Or do I remember wrong ?
Please suggest an API, then we can work out the x86 changes. I can
volunteer myself, but I wasn't in the BOF so I need something more concrete.
Paolo
next prev parent reply other threads:[~2012-11-22 10:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-21 1:07 Interrupt controller updates Benjamin Herrenschmidt
2012-11-21 1:07 ` [Qemu-devel] " Benjamin Herrenschmidt
2012-11-21 8:30 ` Jan Kiszka
2012-11-21 8:30 ` [Qemu-devel] " Jan Kiszka
2012-11-22 10:25 ` Paolo Bonzini [this message]
2012-11-22 10:25 ` Paolo Bonzini
2012-11-22 21:00 ` Benjamin Herrenschmidt
2012-11-22 21:00 ` [Qemu-devel] " Benjamin Herrenschmidt
2012-11-22 21:14 ` Peter Maydell
2012-11-22 21:14 ` [Qemu-devel] " Peter Maydell
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=50ADFDA8.9010003@redhat.com \
--to=pbonzini@redhat.com \
--cc=agraf@suse.de \
--cc=benh@kernel.crashing.org \
--cc=dwg@au1.ibm.com \
--cc=jan.kiszka@siemens.com \
--cc=kvm@vger.kernel.org \
--cc=peter.maydell@linaro.org \
--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.