All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julien Grall <julien.grall@linaro.org>
To: Ian Campbell <ian.campbell@citrix.com>, xen-devel@lists.xen.org
Cc: tim@xen.org, stefano.stabellini@eu.citrix.com
Subject: Re: [PATCH 2/3] xen: arm: correctly handle continuations for 64-bit guests
Date: Wed, 25 Mar 2015 22:39:25 +0000	[thread overview]
Message-ID: <5513391D.9040002@linaro.org> (raw)
In-Reply-To: <1427297660-26447-2-git-send-email-ian.campbell@citrix.com>

Hi Ian,

On 25/03/2015 15:34, Ian Campbell wrote:
> The 64-bit ABI is different to 32-bit:
>
>   - uses x16 as the op register rather than r12.
>   - arguments in x0..x5 and not r0..r5. Using rN here potentially
>     truncates.
>   - return value goes in x0, not r0.
>
> Hypercalls can only be made directly from kernel space, so checking
> the domain's size is sufficient.
>
> The update of regs->pc is duplicated in both halves because the 32-bit
> case is going to need fixing to handle Thumb mode (next patch).
>
> Spotted due to spurious -EFAULT when destroying a domain, due to the
> hypercall's pointer argument being truncated. I'm unclear why I am
> only seeing this now.

Good catch!

x16 would still contain the valid operation, because we are (most of the 
time?) continuing on the same hypercall.

So the only issue would be argument truncation. I guess that we don't 
have big value (i.e > 32 bits) to store.

> Signed-off-by: Ian Campbell <ian.campbell@citrix.com>
> ---
> I imagine this needs backporting everywhere...

Agree for Xen 4.4 and Xen 4.5.

Reviewed-by: Julien Grall <julien.grall@linaro.org>

Regards,

-- 
Julien Grall

  parent reply	other threads:[~2015-03-25 22:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-25 15:34 [PATCH 2/3] xen: arm: correctly handle continuations for 64-bit guests Ian Campbell
2015-03-25 15:41 ` Andrew Cooper
2015-03-25 15:50   ` Ian Campbell
2015-03-25 22:39 ` Julien Grall [this message]
2015-03-26 10:04   ` Ian Campbell

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=5513391D.9040002@linaro.org \
    --to=julien.grall@linaro.org \
    --cc=ian.campbell@citrix.com \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=tim@xen.org \
    --cc=xen-devel@lists.xen.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.