From: "Dan Magenheimer (sent by Nabble.com)" <lists@nabble.com>
To: xen-devel@lists.xensource.com
Subject: Re: Fix blatant non-archdep'isms... need help with build env change?
Date: Tue, 13 Sep 2005 06:18:52 -0700 (PDT) [thread overview]
Message-ID: <849242.post@talk.nabble.com> (raw)
In-Reply-To: <20050913002325.GS7901@shell0.pdx.osdl.net>
[-- Attachment #1.1: Type: text/plain, Size: 614 bytes --]
>>
> wondered about that. Does that mean you have implementation of this,
>or it it unnecessary on ia64?
I don't think its necessary but I need to define the synch_xxx
functions to xxx.
>> - hypervisor.h: about half of this header is
>There's already arch specific files (for hypercall), I wonder if they
>could be reused?
There probably will be more, though I suppose it would be
possible to put all such arch-dep'isms into a single file.
Dan
--
Sent from the Xen - Dev forum at Nabble.com:
http://www.nabble.com/Fix-blatant-non-archdep%27isms...-need-help-with-build-env-change--t302207.html#a849242
[-- Attachment #1.2: Type: text/html, Size: 795 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2005-09-13 13:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-12 23:25 Fix blatant non-archdep'isms... need help with build env change? Magenheimer, Dan (HP Labs Fort Collins)
2005-09-13 0:23 ` Chris Wright
2005-09-13 13:18 ` Dan Magenheimer (sent by Nabble.com) [this message]
2005-09-13 10:32 ` Keir Fraser
2005-09-13 13:16 ` Dan Magenheimer (sent by Nabble.com)
-- strict thread matches above, loose matches on Subject: below --
2005-09-13 22:22 Magenheimer, Dan (HP Labs Fort Collins)
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=849242.post@talk.nabble.com \
--to=lists@nabble.com \
--cc=dan.magenheimer@hp.com \
--cc=xen-devel@lists.xensource.com \
/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.