From owner-freebsd-arch@freebsd.org  Wed Feb 24 10:28:05 2016
Return-Path: <owner-freebsd-arch@freebsd.org>
Delivered-To: freebsd-arch@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id B0D80AB29DC
 for <freebsd-arch@mailman.ysv.freebsd.org>;
 Wed, 24 Feb 2016 10:28:05 +0000 (UTC)
 (envelope-from kostikbel@gmail.com)
Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1])
 (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 31A4B8BB
 for <freebsd-arch@freebsd.org>; Wed, 24 Feb 2016 10:28:05 +0000 (UTC)
 (envelope-from kostikbel@gmail.com)
Received: from tom.home (kostik@localhost [127.0.0.1])
 by kib.kiev.ua (8.15.2/8.15.2) with ESMTPS id u1OARtOJ005229
 (version=TLSv1 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO);
 Wed, 24 Feb 2016 12:27:55 +0200 (EET)
 (envelope-from kostikbel@gmail.com)
DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua u1OARtOJ005229
Received: (from kostik@localhost)
 by tom.home (8.15.2/8.15.2/Submit) id u1OARsv5005216;
 Wed, 24 Feb 2016 12:27:54 +0200 (EET)
 (envelope-from kostikbel@gmail.com)
X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com
 using -f
Date: Wed, 24 Feb 2016 12:27:54 +0200
From: Konstantin Belousov <kostikbel@gmail.com>
To: Justin Hibbits <jrh29@alumni.cwru.edu>
Cc: "freebsd-arch@freebsd.org" <freebsd-arch@freebsd.org>
Subject: Re: RF_CACHEABLE flag
Message-ID: <20160224102754.GK91220@kib.kiev.ua>
References: <CAHSQbTA5A3uSDT143e3yWmfzWZyOCDJ4GSo6JO2NiLc_VAKoYg@mail.gmail.com>
 <20160222121836.GH91220@kib.kiev.ua>
 <CAHSQbTDZVpNU0WsXSHM8yuDqn_5vmy9Ox0fnLZLb2NJfoC7Exg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAHSQbTDZVpNU0WsXSHM8yuDqn_5vmy9Ox0fnLZLb2NJfoC7Exg@mail.gmail.com>
User-Agent: Mutt/1.5.24 (2015-08-30)
X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00,
 DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no
 autolearn_force=no version=3.4.1
X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on tom.home
X-BeenThere: freebsd-arch@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Discussion related to FreeBSD architecture <freebsd-arch.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-arch>,
 <mailto:freebsd-arch-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-arch/>
List-Post: <mailto:freebsd-arch@freebsd.org>
List-Help: <mailto:freebsd-arch-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
 <mailto:freebsd-arch-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Feb 2016 10:28:05 -0000

On Tue, Feb 23, 2016 at 02:19:57PM -0600, Justin Hibbits wrote:
> This really isn't much different from bus_space_map() conceptually.
> The work involved is pretty much the same, and if this route is deemed
> the Wrong Way(TM), I'll go that route.
> 
> Grepping through sys/, only x86 currently implements
> pmap_change_attr(), and arm has the declaration but no definition that
> I could see.  Writing it wouldn't be difficult of course, there's just
> not much compelling case for it right now.  But, yes, either of these
> alternatives are acceptable, and I had explored it.  Seeing John
> Baldwin's comment on the phab review, it looks like he wants to go a
> different (parallel) direction.

If this was not clear from my reply, I did not objected against RF_CACHEABLE,
but was more to highlight weird needs of seemingly simple architecture,
which are close to RF_CACHEABLE stuff.  And, I think that architectures
that care about caching modes, should do provide real pmap_change_attr()
implementation.  This might be important e.g. if drm is brought up on
these platforms.