[#80531] Re: [ruby-cvs:65407] normal:r58236 (trunk): thread.c: comments on M:N threading [ci skip] — Eric Wong <normalperson@...>

SASADA Koichi <ko1@ruby-lang.org> wrote:

24 messages 2017/04/02
[#80532] Re: [ruby-cvs:65407] normal:r58236 (trunk): thread.c: comments on M:N threading [ci skip] — SASADA Koichi <ko1@...> 2017/04/02

On 2017/04/02 11:35, Eric Wong wrote:

[#80540] Re: [ruby-cvs:65407] normal:r58236 (trunk): thread.c: comments on M:N threading [ci skip] — Eric Wong <normalperson@...> 2017/04/03

SASADA Koichi <ko1@atdot.net> wrote:

[#81027] Re: [ruby-cvs:65407] normal:r58236 (trunk): thread.c: comments on M:N threading [ci skip] — Eric Wong <normalperson@...> 2017/05/08

Eric Wong <normalperson@yhbt.net> wrote:

[#81028] Re: [ruby-cvs:65407] normal:r58236 (trunk): thread.c: comments on M:N threading [ci skip] — SASADA Koichi <ko1@...> 2017/05/08

On 2017/05/08 9:33, Eric Wong wrote:

[#81029] Re: [ruby-cvs:65407] normal:r58236 (trunk): thread.c: comments on M:N threading [ci skip] — SASADA Koichi <ko1@...> 2017/05/08

On 2017/05/08 10:53, SASADA Koichi wrote:

[#81031] Re: [ruby-cvs:65407] normal:r58236 (trunk): thread.c: comments on M:N threading [ci skip] — Eric Wong <normalperson@...> 2017/05/08

SASADA Koichi <ko1@atdot.net> wrote:

[#81033] Re: [ruby-cvs:65407] normal:r58236 (trunk): thread.c: comments on M:N threading [ci skip] — SASADA Koichi <ko1@...> 2017/05/08

On 2017/05/08 12:01, Eric Wong wrote:

[#81035] Re: [ruby-cvs:65407] normal:r58236 (trunk): thread.c: comments on M:N threading [ci skip] — Eric Wong <normalperson@...> 2017/05/08

SASADA Koichi <ko1@atdot.net> wrote:

[#81042] Re: [ruby-cvs:65407] normal:r58236 (trunk): thread.c: comments on M:N threading [ci skip] — SASADA Koichi <ko1@...> 2017/05/09

On 2017/05/08 15:36, Eric Wong wrote:

[#81044] Re: [ruby-cvs:65407] normal:r58236 (trunk): thread.c: comments on M:N threading [ci skip] — Eric Wong <normalperson@...> 2017/05/09

SASADA Koichi <ko1@atdot.net> wrote:

[#81045] Re: [ruby-cvs:65407] normal:r58236 (trunk): thread.c: comments on M:N threading [ci skip] — SASADA Koichi <ko1@...> 2017/05/09

On 2017/05/09 12:38, Eric Wong wrote:

[#81047] Re: [ruby-cvs:65407] normal:r58236 (trunk): thread.c: comments on M:N threading [ci skip] — Eric Wong <normalperson@...> 2017/05/09

SASADA Koichi <ko1@atdot.net> wrote:

[ruby-core:80575] [Ruby trunk Feature#13133] TracePoint: Add event type for constant access

From: ko1@...
Date: 2017-04-05 07:10:39 UTC
List: ruby-core #80575
Issue #13133 has been updated by ko1 (Koichi Sasada).


> Enforcing package boundaries is a problem we've been discussing a lot lately at Shopify.

I understand the issue. But your patch and your design needs more consideration.

* Your patch provide a hook only on const cache miss, but the name `constant_access` I assume it hooks all of constant accesses.
* Your patch inserts the hook only in insns.def, but C level constant access is available.
* Not only constant access, constant setting or reopen class/modules are also needed to analyze (and introduce restriction if needed into ) program behavior.



----------------------------------------
Feature #13133: TracePoint: Add event type for constant access
https://bugs.ruby-lang.org/issues/13133#change-64077

* Author: burke (Burke Libbey)
* Status: Assigned
* Priority: Normal
* Assignee: ko1 (Koichi Sasada)
* Target version: 
----------------------------------------
Hi there,

I've attached a patch to add a new `:constant_access` TracePoint event.

One feature and/or bug, depending on your perspective: since this event fires from `setinlinecache`, the event is only triggered:

- **after nested constant resolution**: for `A::B`, only one event is triggered (because `getinlinecache/getconstant/getconstant/`**`setinlinecache`**);
- **on cache miss**: it cannot be used for things like counting iterations, which limits possible uses, but reduces overhead (because `getinlinecache` jumps over `setinlinecache` on a hit).

The use-case I have in mind here is to enable building runtime package/component boundary enforcement systems. For this case, both of the above properties are ideal.

Enforcing package boundaries is a problem we've been discussing a lot lately at Shopify.

If you want a more concrete usage example for this patch, I have some [proof-of-concept code](https://github.com/burke/packages) posted that makes use of it to construct a fairly minimal package system. [`Packages::CONSTANT_ACCESS_TRACEPOINT`](https://github.com/burke/packages/blob/master/lib/packages.rb) is the particularly relevant bit.


---Files--------------------------------
0001-add-a-tracepoint-for-constant-access.patch (3.38 KB)


-- 
https://bugs.ruby-lang.org/

Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>

In This Thread

Prev Next