From: Maxim Kokryashkin via Tarantool-patches <tarantool-patches@dev.tarantool.org> To: Sergey Kaplun <skaplun@tarantool.org> Cc: tarantool-patches@dev.tarantool.org Subject: Re: [Tarantool-patches] [PATCH luajit] Fix maxslots when recording BC_TSETM. Date: Mon, 28 Aug 2023 18:16:45 +0300 [thread overview] Message-ID: <pmcm76ldqquf24b6d6vyhhdb6vh6dkmjt3sv35ewzqeczb62bt@prkq4r7g5f2g> (raw) In-Reply-To: <ZOy29MqHwznZRoiS@root> Hi, Sergey! Thanks for the fixes! LGTM, except for a few more comments below. On Mon, Aug 28, 2023 at 06:02:12PM +0300, Sergey Kaplun wrote: > Hi, Maxim! > Thanks for the review! > I've updated the patch considering your comments and force-pushed the > branch. > > On 28.08.23, Maxim Kokryashkin wrote: > > Hi, Sergey! > > Thanks for the patch! > > Please consider my comments below. > > > > On Fri, Aug 25, 2023 at 06:00:24PM +0300, Sergey Kaplun wrote: > > > From: Mike Pall <mike> > > > > > > Analyzed by Sergey Kaplun. > > > > > > (cherry-picked from commit 0cc5fdfbc0810073485150eb184dc358dab507d9) > > > > > > Recording of the `BC_TSETM` bytecode may keep too optimistic JIT > > > maxslot. In that case, the slot above the top of the Lua stack may be > > Typo: s/too optimistic JIT maxslot./the JIT maxslot too optimistic./ > > Fixed. > > > > considered used. When any VM event handler is called before the > > > recording of the next instruction, this leads to an assertion failure in > > > `rec_check_slots()`. > > > > > > This patch sets the `ra` as a maxslot, as far as the `ra` - 1 contains a > > > table, which is always the highest slot after this bytecode. Also, it > > > adds an assertion that we check slots below the top of the Lua stack. > > > > > > Sergey Kaplun: > > > * added the description and the test for the problem > > > > > > Part of tarantool/tarantool#8825 > > > --- > > <snipped> > > > > + > > > +local TEST_VALUE = '5' > > > +local TEST_IDX = 5 > > > + > > > +local function slot5() > > > + return nil, nil, nil, nil, TEST_VALUE > > > +end > > Why the fifth slot? Drop a comment. > > Fixed. See the iterative patch below. > > > > + > > > +local storage > > > +local function test_tsetm(...) > > > + -- Usage of `TSETM` bytecode. > > > + storage = {slot5()} > > > + -- Use this function again to trick use-def analysis and avoid > > > + -- cleaning JIT slots, so the last JIT slot contains > > > + -- `TEST_VALUE`. > > > + return slot5(...) > > > +end > > > + > > > +-- Wrapper to avoid the recording of just the inner `slot5()` > > > +-- function. > > > +local function wrap() > > > + test_tsetm() > > > +end > > > + > > > +jit.opt.start('hotloop=1') > > > +-- We need to call the VM event handler after each recorded bytecode > > > +-- instruction to pollute the Lua stack and the issue > > > +-- becomes observable. > > Typo: s/and the issue becomes/and make the issue/ > > Fixed. > > See the iterative patch below: > > =================================================================== > diff --git a/test/tarantool-tests/lj-1025-tsetm-maxslot.test.lua b/test/tarantool-tests/lj-1025-tsetm-maxslot.test.lua > index 7ae0a99d..74625a79 100644 > --- a/test/tarantool-tests/lj-1025-tsetm-maxslot.test.lua > +++ b/test/tarantool-tests/lj-1025-tsetm-maxslot.test.lua > @@ -15,6 +15,8 @@ local jit_dump = require('jit.dump') > local TEST_VALUE = '5' > local TEST_IDX = 5 > > +-- XXX: Use big enough slot numbewr to be overwritten by VM event Typo: s/Use/Use a/ Typo: s/numbewr/number/ Typo: s/by VM/by the VM/ > +-- handler function. Please also add that this is an empirical number. > local function slot5() > return nil, nil, nil, nil, TEST_VALUE > end > @@ -36,9 +38,9 @@ local function wrap() > end > > jit.opt.start('hotloop=1') > --- We need to call the VM event handler after each recorded bytecode > --- instruction to pollute the Lua stack and the issue > --- becomes observable. > +-- We need to call the VM event handler after each recorded > +-- bytecode instruction to pollute the Lua stack and make the > +-- issue observable. > jit_dump.start('b', '/dev/null') > > -- Compile and execute the trace with `TSETM`. > =================================================================== > > > > +jit_dump.start('b', '/dev/null') > > > + > > <snipped> > > > > -- > > > 2.41.0 > > > > > -- > Best regards, > Sergey Kaplun
next prev parent reply other threads:[~2023-08-28 15:16 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-08-25 15:00 Sergey Kaplun via Tarantool-patches 2023-08-28 12:58 ` Sergey Bronnikov via Tarantool-patches 2023-08-28 14:04 ` Sergey Kaplun via Tarantool-patches 2023-08-28 15:00 ` Maxim Kokryashkin via Tarantool-patches 2023-08-28 15:02 ` Sergey Kaplun via Tarantool-patches 2023-08-28 15:16 ` Maxim Kokryashkin via Tarantool-patches [this message] 2023-08-28 15:19 ` Sergey Kaplun via Tarantool-patches 2023-09-01 15:45 ` Igor Munkin via Tarantool-patches
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=pmcm76ldqquf24b6d6vyhhdb6vh6dkmjt3sv35ewzqeczb62bt@prkq4r7g5f2g \ --to=tarantool-patches@dev.tarantool.org \ --cc=m.kokryashkin@tarantool.org \ --cc=skaplun@tarantool.org \ --subject='Re: [Tarantool-patches] [PATCH luajit] Fix maxslots when recording BC_TSETM.' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox