2022-02-19
00:30boardwalk has quit [Quit: The Lounge - https://thelounge.chat]
01:06yuyichao_ has quit [Ping timeout: 480 seconds]
02:00DragoonAethis has quit [Quit: hej-hej!]
02:00DragoonAethis has joined #asahi-dev
02:20Emantor has quit [Quit: ZNC - http://znc.in]
02:20Emantor has joined #asahi-dev
03:16yuyichao has joined #asahi-dev
03:26PhilippvK has joined #asahi-dev
03:29phiologe has quit [Ping timeout: 480 seconds]
03:48kov has quit [Quit: Coyote finally caught me]
03:51kov has joined #asahi-dev
04:12axboe_ has quit [Quit: leaving]
06:43sirn- has joined #asahi-dev
06:49sirn has quit [Ping timeout: 480 seconds]
06:49sirn has joined #asahi-dev
06:56sirn- has quit [Ping timeout: 480 seconds]
07:08rkjnsnmarcan, yeah, 300-600 IOPS isn't great, but it's a lot better than 46 for cases where one wants to ensure internal consistency but doesn't care about losing a second or two of writes. It's almost certainly the mode I'll end up using for fsync if we provide it as an option.
07:27willemml has joined #asahi-dev
07:40marcanrkjnsn: that's partially a filesystem thing; according to axboe linux doesn't really do barriers these days
07:41rkjnsnRight. I mean if there was an option to translate fsyncs into drive barriers instead of full flushes.
07:41marcanthe barrier flush thing in macos is probably just something it constructs on top of the cow/journal of the filesystems
07:42marcanand it's still slow because it still has to flush once in a while, but can probably enforce barrier semantics across multiple writes through the metadata without flushing every time
07:42Glanzmannmarcan: I don't know if that is relevant, but if you repeat the random test with the files in place I get 70k IOPS: https://pbot.rmdir.de/NAZqGckf6JqZoyrwOvlMnQ
07:45marcannot sure what test sven was doing but I'm pretty sure you aren't flushing each write that way if you're getting that performance
07:46rkjnsnWithout some way to pass the barrier on to the ANS, how would it enforce ordering to persistent storage without requiring individual flushes?
07:52rkjnsnMaybe it's worth seeing if there's a similar speedup for F_BARRIERFSYNC vs F_BARRIERFSYNC on an HFS+ partition, which presumably can't be doing any CoW shenanigans try to enforce ordering with fewer flushes.
08:23marcanam I forgetting anything other than what was already in spmi/work and jannau's spi fixes?
08:24Glanzmannhttps://git.kernel.dk/cgit/linux-block/commit/?h=m1-test&id=e493225b2692e663729a79754065c3fcbe2d3243
08:24Glanzmannmarcan: https://git.kernel.dk/cgit/linux-block/commit/?h=m1-test&id=e226b395bc2d49a6a1411765875e0864c9a0e0da
08:27j`eythe 'defer nvme flush' commit has the interval defaulting to 1s, there was talk of that actually defaulting to 0s (aka always flush)
08:27jannaunot sure if you count the two top commints in https://github.com/jannau/linux/commits/bits/010-devicetree under the spi fixes
08:27willemml has quit [Quit: willemml]
08:30rkjnsn(I also think abxoe mentioned that flushing by default would be needed for it to be accepted upstream.)
08:32marcanI think I'm going to make the default deferring flushes *this time* just so people test that codepath
08:33marcanif you're concerned about consistency/safety you probably shouldn't be running this kernel anyway for a myriad of other reasons :-)
08:37j`eymarcan: theres also https://git.kernel.dk/cgit/linux-block/commit/?h=m1-test&id=6b70875739979358439ec81f8736cba9e24b0575 for nvme, I think sven has informally acked that
08:54Glanzmannjannau: So I did not saw these patches, but maybe I was not looking right: https://tg.st/u/9ce9060dea91951a330feeeda3ad636bc88c642c.patch https://tg.st/u/256f5efbf23ff68c489dad92f99d1cecfb021729.patch https://tg.st/u/8737955a0263d09ffa8550658dfcac1df3d0665c.patch
09:05jannaumarcan: https://lore.kernel.org/all/e6b80669-20f3-06e7-9ed5-8951a9c6db6f@kernel.dk/ is not yet in next and prevents un-ackable irqs on macbook pro 14/16 where tps6598x fails to probe for all ports except magsafe
09:17psykose has quit [Remote host closed the connection]
09:18psykose has joined #asahi-dev
09:20j`eymarcan: https://github.com/AsahiLinux/linux/commit/9acbb166b4985ddc54786a1ecd2923abda05f177#diff-c97feab6d65c3eb9cf18d7cd08e205d8ff6022dff5fd02e570a55d0b05b7c950R89
09:50marcansound/soc/apple/mca.c:917:45: warning: format ‘%d’ expects argument of type ‘int’, but argument 4 has type ‘long int’ [-Wformat=]
09:50marcansound/soc/apple/mca.c:951:47: warning: too many arguments for format [-Wformat-extra-args]
09:50marcansound/soc/apple/mca.c:951:47: warning: format ‘%d’ expects argument of type ‘int’, but argument 4 has type ‘struct device_node *’ [-Wformat=]
11:16Glanzmannmarcan: Yes, it did, but I started testing kernel options from the bottom up, now top down.
11:17marcanbut that sounds like SND_SOC_APPLE_MCA needs a dep on ARCH_APPLE too to prevent that broken dep chain
11:17marcanGlanzmann: it's the only thing in the message that doesn't have a [y] next to it and isn't COMPILE_TEST
11:17mpsI have few aarch64 machines (some are powerfull) and I always build on them everything for aarch64
11:23Glanzmannpovik: I think it is unrelaed, maybe I had it just on in my usually broken config without any reason whatsoever.
11:35kettenismarcan: I just created an "asahi" u-boot branch with all the diffs that we still need on top of u-boot master
12:02povikyou can try playback with couple of different samplerates, then post a tested-by here: https://lore.kernel.org/linux-clk/20220208183411.61090-1-povik+lin@cutebit.org
13:35___nick___ has joined #asahi-dev
13:37___nick___ has quit []
13:39___nick___ has joined #asahi-dev
13:40___nick___ has quit []
13:42___nick___ has joined #asahi-dev
14:35joerg has joined #asahi-dev
14:35joerg is now known as Guest293
14:36Guest293 has quit []
14:41joerg1 has joined #asahi-dev
14:43joerg1 has quit []
14:55ah-[m]povik: oh does https://github.com/povik/linux/commit/babbcf6fe43a957fa373094241d764a9aeec41ad mean you got something working on t6000?
14:58povikbut the other day Dcow[m] suggested cs42l92 as possibly similar to cs42l83: https://statics.cirrus.com/pubs/proDatasheet/CS42L92_F2.pdf
15:02svenlooks like i just can't reproduce those missed nvme interrupts anymore (without the additional lock around command submission) no matter what i try :/
15:13jeffmiwj`ey: I'm with an old macOS 11.5.2 and neither rtc nor shutdown work with latest asahi branch, currently updating my system to latest macOS 12 to re-test
15:14j`eyjeffmiw: shutdown worked for me in the end, also 11.x. make sure you had all the SPMI/MFD/NVMEM options
15:18axboe has joined #asahi-dev
15:21jeffmiwI had all the SPMI/MFD/NVMEM options, I saw some errors on the spmi nodes in the dt, which model are you testing on ? I'm on mba
15:23jeffmiwok so probably something else wrong in my setup then. I dig into it if I still see the issue after updating. For testing power off I tried halt or shutdown, how do you so it ?
15:38axboe has quit [Quit: leaving]
15:40axboe has joined #asahi-dev
16:02grgy has quit [Quit: ZNC 1.8.2 - https://znc.in]
16:03grgy has joined #asahi-dev
16:18kettenishmm, did I misunderstand that the CLUSTER_PSTATE register contains the actual power state of the cluster as well as the desired state?
18:52willemml has joined #asahi-dev
19:22willemml has quit [Quit: willemml]
19:59bps has quit [Ping timeout: 480 seconds]
20:01willemml has joined #asahi-dev
20:03willemml has quit []
20:07bps has joined #asahi-dev
20:10boardwalk has joined #asahi-dev
20:18Hiroshi has joined #asahi-dev
20:19Hiroshi is now known as Guest306
20:19axboe has quit [Quit: leaving]
20:20Guest306 has quit []
20:21axboe has joined #asahi-dev
20:54axboe has quit [Quit: reboot]
20:56axboe has joined #asahi-dev
21:07___nick___ has quit [Ping timeout: 480 seconds]
21:17bps has quit [Ping timeout: 480 seconds]
23:25Gaspare has joined #asahi-dev
23:40willemml has joined #asahi-dev
23:41willemml has quit []