From: Jens Freimann <jfrei@linux.vnet.ibm.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Thomas Huth <thuth@linux.vnet.ibm.com>,
kvm-devel <kvm@vger.kernel.org>, Alexander Graf <agraf@suse.de>,
QEMU Developers <qemu-devel@nongnu.org>,
Christian Borntraeger <borntraeger@de.ibm.com>,
Cornelia Huck <cornelia.huck@de.ibm.com>,
Andreas Faerber <afaerber@suse.de>,
Christoffer Dall <christoffer.dall@linaro.org>
Subject: Re: [Qemu-devel] [PATCH 1/2] linux-headers: update for s390 floating interrupt controller
Date: Fri, 6 Sep 2013 14:41:04 +0200 [thread overview]
Message-ID: <20130906124104.GB5819@linux.vnet.ibm.com> (raw)
In-Reply-To: <CAFEAcA-N6ytXgtdSupptO=Tb5di4F8OBZug4YD+y7ADZwMaSeQ@mail.gmail.com>
On Fri, Sep 06, 2013 at 01:32:52PM +0100, Peter Maydell wrote:
> On 6 September 2013 13:19, Jens Freimann <jfrei@linux.vnet.ibm.com> wrote:
> > @@ -839,6 +903,7 @@ struct kvm_device_attr {
> > #define KVM_DEV_TYPE_FSL_MPIC_20 1
> > #define KVM_DEV_TYPE_FSL_MPIC_42 2
> > #define KVM_DEV_TYPE_XICS 3
> > +#define KVM_DEV_TYPE_FLIC 4
>
> Christoffer's patchset switching the ARM VGIC to this
> list also uses 4 as its enumeration value:
>
> https://lists.cs.columbia.edu/pipermail/kvmarm/2013-August/006822.html
>
> That patchset isn't in yet, but maybe you should use
> 5 to avoid conflicts?
sure, will do
regards
Jens
>
> thanks
> -- PMM
>
next prev parent reply other threads:[~2013-09-09 7:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-06 12:19 [Qemu-devel] [PATCH 0/2] s390x/kvm: implement floating interrupt controller Jens Freimann
2013-09-06 12:19 ` [Qemu-devel] [PATCH 1/2] linux-headers: update for s390 " Jens Freimann
2013-09-06 12:23 ` Peter Maydell
2013-09-06 12:34 ` Jens Freimann
2013-09-06 12:32 ` Peter Maydell
2013-09-06 12:41 ` Jens Freimann [this message]
2013-09-06 13:18 ` Christian Borntraeger
2013-09-06 12:19 ` [Qemu-devel] [PATCH 2/2] s390x/kvm: implement floating-interrupt controller device Jens Freimann
2013-09-06 13:24 ` Christian Borntraeger
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=20130906124104.GB5819@linux.vnet.ibm.com \
--to=jfrei@linux.vnet.ibm.com \
--cc=afaerber@suse.de \
--cc=agraf@suse.de \
--cc=borntraeger@de.ibm.com \
--cc=christoffer.dall@linaro.org \
--cc=cornelia.huck@de.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@linux.vnet.ibm.com \
/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).