From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: julien.grall@citrix.com, tim@xen.org,
Ian Campbell <ian.campbell@citrix.com>,
xen-devel@lists.xen.org
Subject: Re: [PATCH] xen: arm: document which hypercalls (and subops) are supported on ARM
Date: Tue, 23 Jul 2013 12:09:22 -0400 [thread overview]
Message-ID: <20130723160922.GB5397@phenom.dumpdata.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1307231633390.4893@kaball.uk.xensource.com>
On Tue, Jul 23, 2013 at 04:34:18PM +0100, Stefano Stabellini wrote:
> On Tue, 23 Jul 2013, Ian Campbell wrote:
> > On Tue, 2013-07-23 at 12:33 +0100, Stefano Stabellini wrote:
> >
> > > You are missing all the common tmem ops.
> >
> > tmem_ops are not hooked up in arm_hypercall_table, so they are currently
> > not supported. We should add them here when we add the necessary
> > support. ISTR stubbing out some functions which are used by tmem
> > (steal_page and donate_page perhaps?) so it's not just a case or wiring
> > it up either.
>
> Right.. I was confused by the fact that we do compile tmem_op in Linux,
> even though XEN_TMEM is actually not available on ARM or ARM64
It is an attractive option of using TMEM on those platforms - but I hadn't had
a chance yet to get my Chromebook setup to work with Xen :-(
(It also did not help that I stepped on it and crushed the LCD).
next prev parent reply other threads:[~2013-07-23 16:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-22 18:17 [PATCH] xen: arm: document which hypercalls (and subops) are supported on ARM Ian Campbell
2013-07-23 11:33 ` Stefano Stabellini
2013-07-23 14:14 ` Ian Campbell
2013-07-23 15:34 ` Stefano Stabellini
2013-07-23 16:09 ` Konrad Rzeszutek Wilk [this message]
2013-07-23 16:59 ` Ian Campbell
2013-07-29 14:56 ` Ian Campbell
2013-07-29 18:09 ` Konrad Rzeszutek Wilk
2013-07-30 9:08 ` Ian Campbell
2013-08-08 10:59 ` Ian Campbell
2013-08-08 14:05 ` Tim Deegan
2013-08-08 15:25 ` 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=20130723160922.GB5397@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=ian.campbell@citrix.com \
--cc=julien.grall@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.