xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Ian Campbell <ian.campbell@citrix.com>
To: Vijay Kilari <vijay.kilari@gmail.com>
Cc: Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
	Prasun Kapoor <Prasun.Kapoor@caviumnetworks.com>,
	Vijaya Kumar K <vijaya.kumar@caviumnetworks.com>,
	Julien Grall <julien.grall@linaro.org>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
	Stefano Stabellini <stefano.stabellini@citrix.com>
Subject: Re: [PATCH] xen/arm: Restricted access to IFSR32_EL2 and FPEXC32_EL2
Date: Wed, 17 Sep 2014 18:00:18 +0100	[thread overview]
Message-ID: <1410973218.23505.51.camel@citrix.com> (raw)
In-Reply-To: <CALicx6vEv5tke=oJGT6WERQv2ay2t5D_PzM-=91c6+1PjZbDmw@mail.gmail.com>

On Wed, 2014-09-17 at 14:29 +0530, Vijay Kilari wrote:
> So questions are :
> 1) Is this the hypercall where domain type is set?.

For domU, yes.

> If so, can we return error for this hypercall if domU type is not supported by Xen?

I think that would indeed be the right thing to do.

In addition we need to modifiy arch_get_xen_caps to only include
xen-X.Y-armv7l in the result if the hardware does in fact support domU
as 32-bit. The toolstack will consult this when trying to figure out if
a domain can be built (I think the end result is that
XEN_DOMCTL_set_address_size should never fail because it should never be
called if it could fail, but add the check anyway)

> 2) Can xl tool allow to load domU that platform supports?. May be it require
>     hardware info here which may not be right way to do.

Not sure what you are asking here. If you try and build a 32-bit domain
on a 64-bit-only platform then the above changes will cause it to fail,
which is the right thing to happen. Does that answer your question?

Ian.

      reply	other threads:[~2014-09-17 17:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-27 10:37 [PATCH] xen/arm: Restricted access to IFSR32_EL2 and FPEXC32_EL2 vijay.kilari
2014-05-27 11:21 ` Julien Grall
2014-09-17  8:59   ` Vijay Kilari
2014-09-17 17:00     ` Ian Campbell [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=1410973218.23505.51.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=Prasun.Kapoor@caviumnetworks.com \
    --cc=julien.grall@linaro.org \
    --cc=stefano.stabellini@citrix.com \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=vijay.kilari@gmail.com \
    --cc=vijaya.kumar@caviumnetworks.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).