From: Tim Deegan <tim@xen.org>
To: Dan Magenheimer <dan.magenheimer@oracle.com>
Cc: "Keir (Xen.org)" <keir@xen.org>, xen-devel@lists.xen.org
Subject: Re: 32bit xen and "claim"
Date: Fri, 2 Nov 2012 09:30:55 +0000 [thread overview]
Message-ID: <20121102093055.GA77212@ocelot.phlegethon.org> (raw)
In-Reply-To: <e47d14a7-65e2-4e0e-aec9-3cc4379aa272@default>
At 13:57 -0700 on 01 Nov (1351778261), Dan Magenheimer wrote:
> > From: Tim Deegan [mailto:tim@xen.org]
> > Subject: Re: [Xen-devel] 32bit xen and "claim"
> >
> > At 13:34 -0700 on 01 Nov (1351776880), Dan Magenheimer wrote:
> > > With the plan to obsolete the x86 32-bit hypervisor at 4.3,
> > > when prototyping the "claim" hypercall/subop, can I assume
> > > that the CONFIG_X86 code in the hypervisor and, specifically
> > > any separation of the concepts of xen_heap from dom_heap,
> > > can be ignored?
> > >
> > > Or will the ARM version of the hypervisor be requiring
> > > a similar separation of xen_heap vs dom_heap?
> >
> > Yes, 32-bit ARM has this separation.
>
> Hmmm... looking at page_alloc.c... does ARM overload CONFIG_X86
> to mean CONFIG-32-bitness then?
No. CONFIG_X86 doesn't mean 32-bit, even on x86; it means i386/amd64 as
distinct from MIPS/ARM/PPC.
Tim.
next prev parent reply other threads:[~2012-11-02 9:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-01 20:34 32bit xen and "claim" Dan Magenheimer
2012-11-01 20:41 ` Jan Beulich
2012-11-01 20:55 ` Dan Magenheimer
2012-11-02 8:41 ` Jan Beulich
2012-11-05 19:16 ` Dan Magenheimer
2012-11-05 19:50 ` Keir Fraser
2012-11-06 9:44 ` Jan Beulich
2012-11-06 20:40 ` Dan Magenheimer
2012-11-07 8:25 ` Jan Beulich
2012-11-01 20:46 ` Tim Deegan
2012-11-01 20:57 ` Dan Magenheimer
2012-11-02 9:30 ` Tim Deegan [this message]
2012-11-05 19:00 ` Dan Magenheimer
2012-11-05 19:06 ` Tim Deegan
2012-11-05 19:51 ` Keir Fraser
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=20121102093055.GA77212@ocelot.phlegethon.org \
--to=tim@xen.org \
--cc=dan.magenheimer@oracle.com \
--cc=keir@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 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).