From: Christoffer Dall <christoffer.dall@linaro.org>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Patch Tracking <patches@linaro.org>,
QEMU Developers <qemu-devel@nongnu.org>,
"kvmarm@lists.cs.columbia.edu" <kvmarm@lists.cs.columbia.edu>
Subject: Re: [Qemu-devel] [PATCH v4 0/4] Create ARM KVM VGIC with device control API
Date: Sun, 2 Feb 2014 13:42:07 -0800 [thread overview]
Message-ID: <20140202214207.GA30235@cbox> (raw)
In-Reply-To: <CAFEAcA8VLfQ2E5pj4WQ0dv-3apr9ji_5rNKbOn8R9Y_d8pFHyA@mail.gmail.com>
On Fri, Jan 31, 2014 at 02:21:42PM +0000, Peter Maydell wrote:
> On 29 January 2014 13:21, Peter Maydell <peter.maydell@linaro.org> wrote:
> > On 28 January 2014 20:28, Christoffer Dall <christoffer.dall@linaro.org> wrote:
> >> This patch series adds generic support for issuing device control
> >> related ioctls and supports creating the ARM KVM-accelerated VGIC using
> >> the device control API while maintaining backwards compatibility for
> >> older kernels.
> >>
> >> Changelogs in the individual patches.
> >
> > Thanks, applied to target-arm.next. Git complains about trailing
> > whitespace in the kernel header patch; dunno if you care about
> > fixing that kind of thing in the kernel upstream.
>
> I slightly belatedly discovered that these patches break
> the build on aarch64 hosts, because your new kernel defines
> only exist in the arm KVM headers and not the arm64 ones:
>
> /home/petmay01/linaro/qemu-from-laptop/qemu/hw/intc/arm_gic_kvm.c: In
> function 'kvm_arm_gic_realize':
> /home/petmay01/linaro/qemu-from-laptop/qemu/hw/intc/arm_gic_kvm.c:141:29:
> error: 'KVM_DEV_ARM_VGIC_GRP_ADDR' undeclared (first use in this
> function)
> /home/petmay01/linaro/qemu-from-laptop/qemu/hw/intc/arm_gic_kvm.c:141:29:
> note: each undeclared identifier is reported only once for each
> function it appears in
>
> I've dropped the patches from target-arm.next. The
> simplest fix is probably to get the arm64 headers to
> also support this API and then resubmit.
>
Yikes! Yeah, it also breaks the build of arm64 kernels with KVM enabled,
better get this fix upstream fast. Thanks for spotting it!
-Christoffer
prev parent reply other threads:[~2014-02-02 21:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-28 20:28 [Qemu-devel] [PATCH v4 0/4] Create ARM KVM VGIC with device control API Christoffer Dall
2014-01-28 20:28 ` [Qemu-devel] [PATCH v4 1/4] linux-headers: Update from Linus' master ba635f8 Christoffer Dall
2014-01-28 20:28 ` [Qemu-devel] [PATCH v4 2/4] kvm: Introduce kvm_arch_irqchip_create Christoffer Dall
2014-01-28 20:28 ` [Qemu-devel] [PATCH v4 3/4] kvm: Common device control API functions Christoffer Dall
2014-01-28 20:28 ` [Qemu-devel] [PATCH v4 4/4] arm: vgic device control api support Christoffer Dall
2014-01-29 13:21 ` [Qemu-devel] [PATCH v4 0/4] Create ARM KVM VGIC with device control API Peter Maydell
2014-01-29 15:43 ` Christoffer Dall
2014-01-31 14:21 ` Peter Maydell
2014-02-02 21:42 ` Christoffer Dall [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=20140202214207.GA30235@cbox \
--to=christoffer.dall@linaro.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=patches@linaro.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.