From: pbonzini@redhat.com (Paolo Bonzini)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] KVM: arm/arm64: Move shared files to virt/kvm/arm
Date: Thu, 4 May 2017 15:07:03 +0200 [thread overview]
Message-ID: <dad57222-b97f-59f1-68cd-5ddfed69b078@redhat.com> (raw)
In-Reply-To: <20170504123311.25252-1-cdall@linaro.org>
On 04/05/2017 14:33, Christoffer Dall wrote:
> For some time now we have been having a lot of shared functionality
> between the arm and arm64 KVM support in arch/arm, which not only
> required a horrible inter-arch reference from the Makefile in
> arch/arm64/kvm, but also created confusion for newcomers to the code
> base, as was recently seen on the mailing list.
>
> Further, it causes confusion for things like cscope, which needs special
> attention to index specific shared files for arm64 from the arm tree.
>
> Move the shared files into virt/kvm/arm and move the trace points along
> with it. When moving the tracepoints we have to modify the way the vgic
> creates definitions of the trace points, so we take the chance to
> include the VGIC tracepoints in its very own special vgic trace.h file.
>
> Signed-off-by: Christoffer Dall <cdall@linaro.org>
> ---
> Hi Marc,
>
> What do you think of this? If you like it, I think we should include it
> for this merge window.
Certainly no objection from me, in fact this should not be a problem
even after -rc1.
Paolo
prev parent reply other threads:[~2017-05-04 13:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-04 12:33 [PATCH] KVM: arm/arm64: Move shared files to virt/kvm/arm Christoffer Dall
2017-05-04 12:45 ` Marc Zyngier
2017-05-04 13:05 ` Andrew Jones
2017-05-04 13:07 ` Paolo Bonzini [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=dad57222-b97f-59f1-68cd-5ddfed69b078@redhat.com \
--to=pbonzini@redhat.com \
--cc=linux-arm-kernel@lists.infradead.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