RFR (S): JEP-142: Reduce Cache Contention on Specified Fields

Doug Lea dl at cs.oswego.edu
Tue Dec 11 04:46:47 PST 2012


On 12/10/12 18:52, John Rose wrote:
>
> On Dec 5, 2012, at 3:16 AM, Doug Lea wrote:
>
>> This would be a less
>> controversial idea if it were not for all the cases that arise
>> in practice where other factors make it impossible for the
>> actual users of the functionality to control JVM startup
>> settings. Which ends up making this proposed rule overly
>> hostile in its practical effect.
>
> Note that Unsafe.defineClass allows you to load classes anywhere, including on
> the boot class path.  So if you want to load privileged code from an
> unprivileged context, and you are willing and able to use Unsafe, that is an
> option.  Is there some reason this fails to be useful?  Maybe some residual
> security check that still executes?

It's just another gratuitous pain-point. But having already
established that low-level Java concurrency hackers are
masochists, there's no point in saying "ouch".
So please proceed.

-Doug





More information about the hotspot-dev mailing list