From: Arun Sharma <arun.sharma@intel.com>
To: Philippe Berthault <Philippe.Berthault@Bull.net>
Cc: xen-devel@lists.sourceforge.net, aliguori@us.ibm.com
Subject: Re: A reorganization of Xen sources is necessary before integrating Xen into Linux.
Date: Wed, 23 Feb 2005 15:33:54 -0800 [thread overview]
Message-ID: <421D12E2.7040407@intel.com> (raw)
In-Reply-To: <mailman.1109002520.32751@unix-os.sc.intel.com>
On 2/21/2005 8:14 AM, Philippe Berthault wrote:
> I have searched assembly code in Xen sources (xen-unstable)
> and I'm very surprised because the assembly code isn't located
> in 'arch' directories.
>
> [..]
> - tools/ioemu/iodev
Yes, that one is my fault. The main issue is that we don't have a common place to put arch specific definitions accessible from user space. This came up in the other thread related to rmb/wmb as well.
If we agree that: <asm/xc.h> or <bits/xc.h> is the right thing to do, I'll be happy to submit patches.
-Arun
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
next parent reply other threads:[~2005-02-23 23:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1109002520.32751@unix-os.sc.intel.com>
2005-02-23 23:33 ` Arun Sharma [this message]
2005-02-21 16:14 A reorganization of Xen sources is necessary before integrating Xen into Linux Philippe Berthault
2005-02-21 16:57 ` 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=421D12E2.7040407@intel.com \
--to=arun.sharma@intel.com \
--cc=Philippe.Berthault@Bull.net \
--cc=aliguori@us.ibm.com \
--cc=xen-devel@lists.sourceforge.net \
/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.