Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 9 Jul 2014 10:10:33 -0600
From:      Warner Losh <imp@bsdimp.com>
To:        Bruce Evans <brde@optusnet.com.au>
Cc:        arch@freebsd.org, Don Lewis <truckman@freebsd.org>, adrian@freebsd.org
Subject:   Re: [patch] axe RF_TIMESHARE?
Message-ID:  <2174B753-A1C9-4F8A-8E25-28612030AF78@bsdimp.com>
In-Reply-To: <20140709200848.Q1201@besplex.bde.org>
References:  <201407082254.s68MsaPS028312@gw.catspoiler.org> <20140709200848.Q1201@besplex.bde.org>

next in thread | previous in thread | raw e-mail | index | archive | help

--Apple-Mail=_114355A0-E7DD-464D-A856-EE61F48CEC28
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252


On Jul 9, 2014, at 4:08 AM, Bruce Evans <brde@optusnet.com.au> wrote:
> RF_TIMESHARE doesn't simplify this significantly.  Ownership of the
> interrupt should be claimed somewhere so that the interrupt resource
> is available at first open time.  That can probably be done using
> a super-device or some hack to own the interrupt by the first device
> that can share it.  Then you don't need a flag for it.  It seems too
> hard (bloated) to generalize RF_TIMESHARE so that all of the OUT2
> complications can be handled at the new-bus level.

I think that, while interesting, none of this has a bearing on =
RF_TIMESHARE.

For shared interrupts, we=92ve used RF_SHARED for a long time. I don=92t =
think anybody ever actually implemented RF_TIMESHARE apart from an =
aborted attempt by the ppcbus code which later wound up abandoning that =
effort (I think before it even made it into the tree).

It was an interesting concept, but we never used it and I think we can =
light a bonfire under it. There are other ways to share resources that =
have been used instead...

Warner


--Apple-Mail=_114355A0-E7DD-464D-A856-EE61F48CEC28
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCgAGBQJTvWl5AAoJEGwc0Sh9sBEAHKgP/jHjvXmVcwX1QP56QNjf5kf1
95Bf8jMeI4KHkeZmrotKsl4YLfeCEpn74wEDnnXi5V22xFrZYsEh9xxOWIjNKjbq
Og+hNhTjgFGzkE6U5oB6mLPMxzIgBWD28vxUVhu+1AU3PLXxmnXDeXf3r+dMrOgX
jbu09r+40AKdTGIESzyPv2AAM56Hi4xIyUofIfacG4VbHHXioMsYssxdNqTqM+rf
lHr511IypQcadjE3o1lFZvRtYg1T33AppRQolvv2loylm2XTbJsvHg/ibPi3k0sm
tp/cn15Ye1r/uhOFf3gdJwVPBx2Bbr2RrbImmyxBRNspgJ31uXAy5iq1yzmJG1Au
XKgBe70WIFNKGcYiSKQHC+GmwERChlsmTiA7MefaN0RyBFtsirrS2I5cNfUCJbQw
MPe9XIaayqQ9gv7rjpWjeNpB3OBXAdWZD32vF1TAS18/DKFEm2h1g9ch1CjCWTm+
tniq2L75H9Xtzm8TbrdpNYu8aicOaQ/gQno54uU9Fx+eN9owDG3ZvdenBDcBos6b
LY6kVx+El2SwpAxDfQV7m8kEAZPknugEydDqI4kEJPU7G+fMVCTUS8Q739+SJfuR
PWma2EunIAbTfcUqfuF0RWUNBKGa1XEYTpAQFhQSlXyUkMt8c9BUvp8XN6PFdJ/L
DcW5PymqsHdfDIk00YeA
=L2ml
-----END PGP SIGNATURE-----

--Apple-Mail=_114355A0-E7DD-464D-A856-EE61F48CEC28--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2174B753-A1C9-4F8A-8E25-28612030AF78>