From: catalin.marinas@arm.com (Catalin Marinas)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH RFC 1/6] [HACK!] arm64/xen: create links to arch/arm include files and Xen code
Date: Fri, 31 May 2013 11:36:17 +0100 [thread overview]
Message-ID: <20130531103617.GA18045@localhost.cambridge.arm.com> (raw)
In-Reply-To: <1369930713-6063-1-git-send-email-stefano.stabellini@eu.citrix.com>
On Thu, May 30, 2013 at 05:18:28PM +0100, Stefano Stabellini wrote:
> Most of Xen support for ARM is common between ARMv7 and ARMv8.
> Create links to the code under arch/arm (bleah).
>
> Other, probably better alternatives:
>
> - move the code to a different location, maybe the header files to
> include/xen/arm and the code to drivers/xen/arm (still pretty ugly)?
>
> - create a copy of the code to arch/arm64 (even worse);
KVM handles this in the Makefile by referencing back to arch/arm or even
the generic kvm directory. I think that's the 'cleanest' ;)
--
Catalin
WARNING: multiple messages have this Message-ID (diff)
From: Catalin Marinas <catalin.marinas@arm.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: "linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Will Deacon <Will.Deacon@arm.com>,
"Ian.Campbell@citrix.com" <Ian.Campbell@citrix.com>,
"konrad.wilk@oracle.com" <konrad.wilk@oracle.com>
Subject: Re: [PATCH RFC 1/6] [HACK!] arm64/xen: create links to arch/arm include files and Xen code
Date: Fri, 31 May 2013 11:36:17 +0100 [thread overview]
Message-ID: <20130531103617.GA18045@localhost.cambridge.arm.com> (raw)
In-Reply-To: <1369930713-6063-1-git-send-email-stefano.stabellini@eu.citrix.com>
On Thu, May 30, 2013 at 05:18:28PM +0100, Stefano Stabellini wrote:
> Most of Xen support for ARM is common between ARMv7 and ARMv8.
> Create links to the code under arch/arm (bleah).
>
> Other, probably better alternatives:
>
> - move the code to a different location, maybe the header files to
> include/xen/arm and the code to drivers/xen/arm (still pretty ugly)?
>
> - create a copy of the code to arch/arm64 (even worse);
KVM handles this in the Makefile by referencing back to arch/arm or even
the generic kvm directory. I think that's the 'cleanest' ;)
--
Catalin
next prev parent reply other threads:[~2013-05-31 10:36 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-30 16:18 [PATCH RFC 0/6] Introduce Xen support to ARM64 Stefano Stabellini
2013-05-30 16:18 ` Stefano Stabellini
2013-05-30 16:18 ` Stefano Stabellini
2013-05-30 16:18 ` [PATCH RFC 1/6] [HACK!] arm64/xen: create links to arch/arm include files and Xen code Stefano Stabellini
2013-05-30 16:18 ` Stefano Stabellini
2013-05-30 16:18 ` Stefano Stabellini
2013-05-31 10:36 ` Catalin Marinas [this message]
2013-05-31 10:36 ` Catalin Marinas
2013-05-31 12:02 ` Stefano Stabellini
2013-05-31 12:02 ` Stefano Stabellini
2013-05-31 13:10 ` Catalin Marinas
2013-05-31 13:10 ` Catalin Marinas
2013-05-31 13:10 ` Catalin Marinas
2013-05-31 15:20 ` Stefano Stabellini
2013-05-31 15:20 ` Stefano Stabellini
2013-05-30 16:18 ` [PATCH RFC 2/6] arm64/xen: arm/xen header changes to compile on arm64 Stefano Stabellini
2013-05-30 16:18 ` Stefano Stabellini
2013-05-30 16:18 ` Stefano Stabellini
2013-05-31 10:43 ` Catalin Marinas
2013-05-31 10:43 ` Catalin Marinas
2013-05-31 10:43 ` Catalin Marinas
2013-05-31 13:25 ` Stefano Stabellini
2013-05-31 13:25 ` Stefano Stabellini
2013-05-30 16:18 ` [PATCH RFC 3/6] arm64/xen: use XEN_IO_PROTO_ABI_ARM on ARM64 Stefano Stabellini
2013-05-30 16:18 ` Stefano Stabellini
2013-05-30 16:18 ` Stefano Stabellini
2013-05-30 16:18 ` [PATCH RFC 4/6] arm64/xen: introduce asm/hypervisor.h and sys_bitops.h Stefano Stabellini
2013-05-30 16:18 ` Stefano Stabellini
2013-05-30 16:18 ` Stefano Stabellini
2013-05-30 16:18 ` [PATCH RFC 5/6] arm64/xen: implement xen_remap on arm64 Stefano Stabellini
2013-05-30 16:18 ` Stefano Stabellini
2013-05-30 16:18 ` Stefano Stabellini
2013-05-31 10:59 ` Catalin Marinas
2013-05-31 10:59 ` Catalin Marinas
2013-05-31 10:59 ` Catalin Marinas
2013-05-31 13:21 ` Stefano Stabellini
2013-05-31 13:21 ` Stefano Stabellini
2013-05-31 14:16 ` Catalin Marinas
2013-05-31 14:16 ` Catalin Marinas
2013-05-31 14:50 ` Stefano Stabellini
2013-05-31 14:50 ` Stefano Stabellini
2013-05-31 15:23 ` Stefano Stabellini
2013-05-31 15:23 ` Stefano Stabellini
2013-05-31 15:56 ` Catalin Marinas
2013-05-31 15:56 ` Catalin Marinas
2013-05-31 15:56 ` Catalin Marinas
2013-05-30 16:18 ` [PATCH RFC 6/6] arm64/xen: introduce CONFIG_XEN and hypercall.S on ARM64 Stefano Stabellini
2013-05-30 16:18 ` Stefano Stabellini
2013-05-30 16:18 ` Stefano Stabellini
2013-05-31 11:02 ` Catalin Marinas
2013-05-31 11:02 ` Catalin Marinas
2013-05-31 11:02 ` Catalin Marinas
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=20130531103617.GA18045@localhost.cambridge.arm.com \
--to=catalin.marinas@arm.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 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.