From: ian.campbell@citrix.com (Ian Campbell)
To: linux-arm-kernel@lists.infradead.org
Subject: [Xen-devel] [PATCH v4 2/7] xen/arm: introduce HYPERVISOR_platform_op on arm and arm64
Date: Mon, 16 Nov 2015 09:42:57 +0000 [thread overview]
Message-ID: <1447666977.15629.9.camel@citrix.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1511131757360.2653@kaball.uk.xensource.com>
On Fri, 2015-11-13 at 18:10 +0000, Stefano Stabellini wrote:
>
> I agree with your point (I thought about it myself) but the current
> assembly scheme for hypercalls doesn't work well with that. I would have
> to introduce, and maintain going forward, two special hypercall
> implementations in assembly, one for arm and another for arm64, just to
> set interface_version. I don't think it is worth it; I prefer to have to
> maintain the explicit interface_version setting at the call sites (that
> today is just one).
You could give the bare assembly stub a different name (append _core or
_raw or something) and make HYPERVISOR_platform_op a C wrapper for it which
DTRT.
Ian.
WARNING: multiple messages have this Message-ID (diff)
From: Ian Campbell <ian.campbell@citrix.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
Julien Grall <julien.grall@citrix.com>
Cc: <xen-devel@lists.xensource.com>, <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [Xen-devel] [PATCH v4 2/7] xen/arm: introduce HYPERVISOR_platform_op on arm and arm64
Date: Mon, 16 Nov 2015 09:42:57 +0000 [thread overview]
Message-ID: <1447666977.15629.9.camel@citrix.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1511131757360.2653@kaball.uk.xensource.com>
On Fri, 2015-11-13 at 18:10 +0000, Stefano Stabellini wrote:
>
> I agree with your point (I thought about it myself) but the current
> assembly scheme for hypercalls doesn't work well with that. I would have
> to introduce, and maintain going forward, two special hypercall
> implementations in assembly, one for arm and another for arm64, just to
> set interface_version. I don't think it is worth it; I prefer to have to
> maintain the explicit interface_version setting at the call sites (that
> today is just one).
You could give the bare assembly stub a different name (append _core or
_raw or something) and make HYPERVISOR_platform_op a C wrapper for it which
DTRT.
Ian.
WARNING: multiple messages have this Message-ID (diff)
From: Ian Campbell <ian.campbell@citrix.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
Julien Grall <julien.grall@citrix.com>
Cc: xen-devel@lists.xensource.com, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [Xen-devel] [PATCH v4 2/7] xen/arm: introduce HYPERVISOR_platform_op on arm and arm64
Date: Mon, 16 Nov 2015 09:42:57 +0000 [thread overview]
Message-ID: <1447666977.15629.9.camel@citrix.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1511131757360.2653@kaball.uk.xensource.com>
On Fri, 2015-11-13 at 18:10 +0000, Stefano Stabellini wrote:
>
> I agree with your point (I thought about it myself) but the current
> assembly scheme for hypercalls doesn't work well with that. I would have
> to introduce, and maintain going forward, two special hypercall
> implementations in assembly, one for arm and another for arm64, just to
> set interface_version. I don't think it is worth it; I prefer to have to
> maintain the explicit interface_version setting at the call sites (that
> today is just one).
You could give the bare assembly stub a different name (append _core or
_raw or something) and make HYPERVISOR_platform_op a C wrapper for it which
DTRT.
Ian.
next prev parent reply other threads:[~2015-11-16 9:42 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-12 17:29 [PATCH v4 0/7] Xen wallclock on arm and arm64 Stefano Stabellini
2015-11-12 17:29 ` Stefano Stabellini
2015-11-12 17:29 ` Stefano Stabellini
2015-11-12 17:30 ` [PATCH v4 1/7] xen: rename dom0_op to platform_op Stefano Stabellini
2015-11-12 17:30 ` Stefano Stabellini
2015-11-12 17:30 ` Stefano Stabellini
2015-11-12 17:30 ` [PATCH v4 2/7] xen/arm: introduce HYPERVISOR_platform_op on arm and arm64 Stefano Stabellini
2015-11-12 17:30 ` Stefano Stabellini
2015-11-12 17:30 ` Stefano Stabellini
2015-11-13 13:40 ` [Xen-devel] " Julien Grall
2015-11-13 13:40 ` Julien Grall
2015-11-13 13:40 ` Julien Grall
2015-11-13 18:10 ` Stefano Stabellini
2015-11-13 18:10 ` Stefano Stabellini
2015-11-13 18:10 ` Stefano Stabellini
2015-11-13 18:31 ` Julien Grall
2015-11-13 18:31 ` Julien Grall
2015-11-13 18:31 ` Julien Grall
2015-11-16 9:42 ` Ian Campbell [this message]
2015-11-16 9:42 ` Ian Campbell
2015-11-16 9:42 ` Ian Campbell
2015-11-20 11:58 ` Stefano Stabellini
2015-11-20 11:58 ` Stefano Stabellini
2015-11-20 11:58 ` Stefano Stabellini
2015-11-20 12:18 ` Ian Campbell
2015-11-20 12:18 ` Ian Campbell
2015-11-20 12:18 ` Ian Campbell
2015-11-12 17:30 ` [PATCH v4 3/7] xen: introduce XENPF_settime64 Stefano Stabellini
2015-11-12 17:30 ` Stefano Stabellini
2015-11-12 17:30 ` Stefano Stabellini
2015-11-12 17:30 ` [PATCH v4 4/7] arm: extend pvclock_wall_clock with sec_hi Stefano Stabellini
2015-11-12 17:30 ` Stefano Stabellini
2015-11-12 17:30 ` Stefano Stabellini
2015-11-13 13:43 ` [Xen-devel] " Julien Grall
2015-11-13 13:43 ` Julien Grall
2015-11-13 13:43 ` Julien Grall
2015-11-12 17:30 ` [PATCH v4 5/7] xen/arm: introduce xen_read_wallclock Stefano Stabellini
2015-11-12 17:30 ` Stefano Stabellini
2015-11-12 17:30 ` Stefano Stabellini
2015-11-12 19:12 ` Arnd Bergmann
2015-11-12 19:12 ` Arnd Bergmann
2015-11-12 17:30 ` [PATCH v4 6/7] xen/arm: set the system time in Xen via the XENPF_settime64 hypercall Stefano Stabellini
2015-11-12 17:30 ` Stefano Stabellini
2015-11-12 17:30 ` Stefano Stabellini
2015-11-13 13:56 ` [Xen-devel] " Julien Grall
2015-11-13 13:56 ` Julien Grall
2015-11-13 13:56 ` Julien Grall
2015-11-12 17:30 ` [PATCH v4 7/7] xen/x86: support XENPF_settime64 Stefano Stabellini
2015-11-12 17:30 ` Stefano Stabellini
2015-11-12 17:30 ` Stefano Stabellini
2015-11-12 19:14 ` Arnd Bergmann
2015-11-12 19:14 ` Arnd Bergmann
2015-11-13 10:42 ` [Xen-devel] " David Vrabel
2015-11-13 10:42 ` David Vrabel
2015-11-13 10:42 ` David Vrabel
2015-11-13 10:45 ` Stefano Stabellini
2015-11-13 10:45 ` Stefano Stabellini
2015-11-13 10:45 ` Stefano Stabellini
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=1447666977.15629.9.camel@citrix.com \
--to=ian.campbell@citrix.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.