From mboxrd@z Thu Jan 1 00:00:00 1970 From: nicolas.pitre@linaro.org (Nicolas Pitre) Date: Fri, 9 Mar 2012 11:20:20 -0500 (EST) Subject: [PATCH-WIP 01/13] xen/arm: use r12 to pass the hypercall number to the hypervisor In-Reply-To: References: <1330019314-20865-1-git-send-email-stefano.stabellini@eu.citrix.com> <1330360043.8557.302.camel@zakaz.uk.xensource.com> <20120227180355.GB2023@linaro.org> <1330371219.10008.34.camel@dagon.hellion.org.uk> <20120228102040.GB2063@linaro.org> <1330426133.31269.70.camel@zakaz.uk.xensource.com> <20120229093436.GA2077@linaro.org> <1330509362.4270.20.camel@zakaz.uk.xensource.com> <20120229125826.GC2077@linaro.org> <4F5882BF.1030104@arm.com> <4F58FEC0.8080706@arm.com> Message-ID: To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Fri, 9 Mar 2012, Dave Martin wrote: > Register variables feel like a red herring though. We're only using > those because we can't do the needful thing and actually desscribe > these constraints in the asm constraints (which would seem to be the > right place). We specifically don't care where those values are > except at the boundaries of the asm block itself. Absolutely. > Is there a reason why ARM gcc doesn't provide the ability to specify > such exact-register constraints, or is this more for historical > reasons? It is possible? I don't know how much things have changed since I last looked at the gcc code, but implementing this seemed to be pretty trivial at the time. The problem would be to determine a good letter scheme to map to actual registers. Nicolas