From: Jan Kiszka <jan.kiszka@web.de>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Peter Maydell <peter.maydell@linaro.org>,
David Gibson <dwg@au1.ibm.com>, Alexander Graf <agraf@suse.de>,
kvm@vger.kernel.org,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Interrupt controller updates
Date: Wed, 21 Nov 2012 09:30:42 +0100 [thread overview]
Message-ID: <50AC9132.6050806@web.de> (raw)
In-Reply-To: <1353460020.17856.25.camel@pasglop>
[-- Attachment #1: Type: text/plain, Size: 827 bytes --]
On 2012-11-21 02:07, Benjamin Herrenschmidt wrote:
> Hi Jan !
>
> 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 ?
I guess I wasn't in the room at that time ;).
I don't have much bandwidth the very next weeks to work on this, so I
guess it's better you come up with a patch proposal.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 259 bytes --]
next prev parent reply other threads:[~2012-11-21 8:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-21 1:07 [Qemu-devel] Interrupt controller updates Benjamin Herrenschmidt
2012-11-21 8:30 ` Jan Kiszka [this message]
2012-11-22 10:25 ` Paolo Bonzini
2012-11-22 21:00 ` Benjamin Herrenschmidt
2012-11-22 21:14 ` 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=50AC9132.6050806@web.de \
--to=jan.kiszka@web.de \
--cc=agraf@suse.de \
--cc=benh@kernel.crashing.org \
--cc=dwg@au1.ibm.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 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).