From: Ian Campbell <Ian.Campbell@citrix.com>
To: Anil Madhavapeddy <anil@recoil.org>
Cc: Thomas Leonard <talex5@gmail.com>,
Dave.Scott@eu.citrix.com, stefano.stabellini@eu.citrix.com,
Julien Grall <julien.grall@linaro.org>,
samuel.thibault@ens-lyon.org, xen-devel@lists.xenproject.org
Subject: Re: [PATCH ARM v8 2/4] mini-os: arm: interrupt controller
Date: Tue, 21 Oct 2014 20:18:45 +0100 [thread overview]
Message-ID: <1413919125.20604.40.camel@citrix.com> (raw)
In-Reply-To: <13402DD8-D998-4D36-8FA2-C5D262E4900B@recoil.org>
On Tue, 2014-10-21 at 19:14 +0100, Anil Madhavapeddy wrote:
> On 21 Oct 2014, at 17:03, Julien Grall <julien.grall@linaro.org> wrote:
> >
> >>> In this case, it would make mini-os working directly on Xen 4.4.
> >
> >> and how long should mini-os carry this hack for then?
> >
> > The current issue could be considered as an hardware bug (even though
> > it's an emulation). Time to time guest has to deal with hardware bug. As
> > long as it's very simple to fix it and doesn't impact performance, I
> > guess it's better to have it forever.
> > In this case, interrupts will be configured only once during mini-os
> > initialization.
> >
> > If nobody care about running mini-os on current version of current Xen
> > 4.4.x, then fine.
Anybody who cares should fix the bug in Xen. It would have taken less
typing than this thread.
> Isn't this what XEN_INTERFACE_VERSION checks are for? It's certainly
> convenient to have MiniOS support the last stable version of the Xen
> ABI unless it's a huge diff, and this should just be a localised #ifdef.
This isn't an ABI issue, it's a violation of a hardware spec which we
are supposed to be emulating.
In any case XEN_INTERFACE_VERSION is for API compatiblity (for users of
the Xen headers), not ABI compatibility.
Ian.
next prev parent reply other threads:[~2014-10-21 19:18 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-03 9:20 [PATCH ARM v8 0/4] mini-os: initial ARM support Thomas Leonard
2014-10-03 9:20 ` [PATCH ARM v8 1/4] mini-os: arm: time Thomas Leonard
2014-10-21 10:50 ` Ian Campbell
2014-10-21 14:07 ` [PATCH incomplete] xen: arm: wallclock support (incomplete, needs work/refactoring) Ian Campbell
2014-10-26 9:51 ` [PATCH ARM v8 1/4] mini-os: arm: time Thomas Leonard
2014-10-27 10:34 ` Ian Campbell
2014-11-13 16:29 ` Thomas Leonard
2014-11-14 10:29 ` Ian Campbell
2014-11-19 20:57 ` Konrad Rzeszutek Wilk
2015-01-08 15:52 ` Ian Campbell
2015-01-08 15:58 ` Thomas Leonard
2015-01-08 16:04 ` Ian Campbell
2014-10-03 9:20 ` [PATCH ARM v8 2/4] mini-os: arm: interrupt controller Thomas Leonard
2014-10-21 11:00 ` Ian Campbell
2014-10-21 14:26 ` Julien Grall
2014-10-21 15:16 ` Ian Campbell
2014-10-21 15:22 ` Julien Grall
2014-10-21 15:35 ` Ian Campbell
2014-10-21 16:03 ` Julien Grall
2014-10-21 18:14 ` Anil Madhavapeddy
2014-10-21 19:18 ` Ian Campbell [this message]
2014-10-21 21:54 ` Samuel Thibault
2014-10-22 9:03 ` Ian Campbell
2014-10-22 13:06 ` Julien Grall
2014-10-22 13:14 ` Samuel Thibault
2014-10-28 15:15 ` Thomas Leonard
2014-10-28 15:25 ` Julien Grall
2014-10-28 15:43 ` Thomas Leonard
2014-10-28 15:51 ` Julien Grall
2014-11-14 10:22 ` Thomas Leonard
2014-11-14 11:33 ` Julien Grall
2014-11-14 11:42 ` Ian Campbell
2014-11-14 11:48 ` Julien Grall
2014-11-14 12:01 ` Ian Campbell
2014-10-03 9:20 ` [PATCH ARM v8 3/4] mini-os: arm: build system Thomas Leonard
2014-10-21 11:44 ` Ian Campbell
2014-10-21 21:50 ` Samuel Thibault
2014-10-22 9:01 ` Ian Campbell
2014-10-22 9:59 ` Samuel Thibault
2014-10-26 9:46 ` Thomas Leonard
2014-10-26 9:55 ` Samuel Thibault
2014-10-26 10:25 ` Thomas Leonard
2014-11-17 11:42 ` Thomas Leonard
2014-11-17 11:45 ` Ian Campbell
2014-11-17 11:47 ` Andrew Cooper
2014-11-17 11:47 ` Samuel Thibault
2014-10-03 9:20 ` [PATCH ARM v8 4/4] mini-os: arm: show registers, stack and exception vector on fault Thomas Leonard
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=1413919125.20604.40.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=Dave.Scott@eu.citrix.com \
--cc=anil@recoil.org \
--cc=julien.grall@linaro.org \
--cc=samuel.thibault@ens-lyon.org \
--cc=stefano.stabellini@eu.citrix.com \
--cc=talex5@gmail.com \
--cc=xen-devel@lists.xenproject.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.