From: Keir Fraser <keir@xensource.com>
To: Dietmar Hahn <dietmar.hahn@fujitsu-siemens.com>,
Grzegorz Milos <gm281@cam.ac.uk>
Cc: xen-devel@lists.xensource.com, Keir Fraser <keir@xensource.com>,
Xen-ia64-devel <xen-ia64-devel@lists.xensource.com>
Subject: Re: [RFC][PATCH]mini-os: big-endian mini-os on ia64
Date: Wed, 21 Feb 2007 13:51:39 +0000 [thread overview]
Message-ID: <C201FEEB.9D89%keir@xensource.com> (raw)
In-Reply-To: <200702211404.49908.dietmar.hahn@fujitsu-siemens.com>
On 21/2/07 13:04, "Dietmar Hahn" <dietmar.hahn@fujitsu-siemens.com> wrote:
> I think the SWAP()'s are not that much. Maybe I can reduce this by moving some
> into the ia64-hypercall interface. What remain are the accesses to the ring
> buffers (not that simple in netfront because of the xen-macros).
> Perhaps some other guys contribute their opinion.
I would actually argue that they're scattered all over the place and it will
be hard to be sure that we have all the SWAPs we need and only the SWAPs we
need. Particularly to continue ensuring that given that most development
will be with minios having same endianness as Xen.
In short: it's ugly and unless someone really cares it will rot.
-- Keir
next prev parent reply other threads:[~2007-02-21 13:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-20 14:00 [RFC][PATCH]mini-os: big-endian mini-os on ia64 Dietmar Hahn
2007-02-20 14:36 ` Keir Fraser
2007-02-20 14:51 ` [Xen-devel] " Dietmar Hahn
2007-02-20 19:03 ` Grzegorz Milos
2007-02-21 13:04 ` [Xen-devel] " Dietmar Hahn
2007-02-21 13:51 ` Keir Fraser [this message]
2007-02-27 9:55 ` Dietmar Hahn
2007-02-27 10:51 ` Keir Fraser
2007-02-27 12:07 ` Mark Williamson
2007-02-28 8:21 ` [Xen-devel] " Dietmar Hahn
2007-02-28 8:42 ` Keir Fraser
2007-02-28 10:14 ` [Xen-devel] " Dietmar Hahn
2007-02-28 8:25 ` Dietmar Hahn
2007-02-28 8:37 ` Keir Fraser
2007-02-28 9:05 ` Dietmar Hahn
2007-03-01 22:08 ` Grzegorz Milos
2007-03-15 10:55 ` Dietmar Hahn
2007-03-15 11:01 ` Dietmar Hahn
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=C201FEEB.9D89%keir@xensource.com \
--to=keir@xensource.com \
--cc=dietmar.hahn@fujitsu-siemens.com \
--cc=gm281@cam.ac.uk \
--cc=xen-devel@lists.xensource.com \
--cc=xen-ia64-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.