From owner-freebsd-arm@FreeBSD.ORG  Mon Jan 19 17:15:53 2015
Return-Path: <owner-freebsd-arm@FreeBSD.ORG>
Delivered-To: freebsd-arm@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 429DAB6C
 for <freebsd-arm@freebsd.org>; Mon, 19 Jan 2015 17:15:53 +0000 (UTC)
Received: from mail-qg0-x22c.google.com (mail-qg0-x22c.google.com
 [IPv6:2607:f8b0:400d:c04::22c])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id 0CBCDB27
 for <freebsd-arm@freebsd.org>; Mon, 19 Jan 2015 17:15:52 +0000 (UTC)
Received: by mail-qg0-f44.google.com with SMTP id l89so17136772qgf.3
 for <freebsd-arm@freebsd.org>; Mon, 19 Jan 2015 09:15:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:in-reply-to:references:date:message-id:subject:from:to
 :content-type; bh=sJTmaIoYxqQ+G2ML0VV2IE7ZERGWUGCcmvcLiavVqVs=;
 b=wbL4cej7K0+w1wGKT2OR3V5TWgdLGYfI4FC8lb8LrFEaOct9dX7ClZHvHD1y1eNguP
 n1rRsuL8a5TZjxywNKV64ty6jUgHBlFEu7yEFqd26VNx8xgvw2DwoYTOmPuJWuXRu482
 dFVsQCtjL1gWEEJyTbT4QDPaRcj4HytDFEL3oafuPKv/8eAankR9BU2nWG2uPHfzYvgY
 izryYpKq2OdZ10vYr2MEsMQf5Xrd4h+JRjL423aW653jin/THL2tJTUNMhjx9spSvwQp
 UPMo1zSzXjiavU0I+i+XhSwwR4AJhgaGJNdA2i9jNLeFS+LhLdMt08ZZbTqnKOdJgQeH
 T2Aw==
MIME-Version: 1.0
X-Received: by 10.229.248.69 with SMTP id mf5mr49593585qcb.29.1421687749585;
 Mon, 19 Jan 2015 09:15:49 -0800 (PST)
Received: by 10.140.82.180 with HTTP; Mon, 19 Jan 2015 09:15:49 -0800 (PST)
In-Reply-To: <54BC49CB.4020504@freebsd.org>
References: <CAFHCsPX5kG_v-F-cjpyMQsT_b386eok=mqWW0+EUb_4-_1Otnw@mail.gmail.com>
 <54B7EB67.6010702@freebsd.org> <20150118203021.3ecac737@bender.lan>
 <54BC49CB.4020504@freebsd.org>
Date: Mon, 19 Jan 2015 18:15:49 +0100
Message-ID: <CAFHCsPWyEAGnSErw_24FEENw_Luce-puRFekGe74=PvvofYXfQ@mail.gmail.com>
Subject: Re: interrupt framework
From: Svatopluk Kraus <onwahe@gmail.com>
To: freebsd-arm@freebsd.org
Content-Type: text/plain; charset=UTF-8
X-BeenThere: freebsd-arm@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: "Porting FreeBSD to ARM processors." <freebsd-arm.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-arm>,
 <mailto:freebsd-arm-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-arm/>
List-Post: <mailto:freebsd-arm@freebsd.org>
List-Help: <mailto:freebsd-arm-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arm>,
 <mailto:freebsd-arm-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Jan 2015 17:15:53 -0000

Considering that our work could be the framework and even for more
archs, I like to ask what should be optimalized?

(1) The framework is based on an interrupt source structure. Should it
be transparent for controllers with a set of interface functions or
should it be public for them?

(2) We are using KOBJ methods as controller's interface now. However,
there is a table of functions used in i386 arch.

(3) Could be the new INTR_SOLO method how to handle an interrupt
useful for other archs? If so, it will be nice to try to import it
somehow to MI interrupt event in kern_intr.c. For example, there is a
timer interrupt in i386 arch which is handled without MI interrupt
framework to be really fast.

Svata