<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">I forget when that was setup, but here is a copy of the schema from the <a href="http://lnt.llvm.org" class="">lnt.llvm.org</a> server:<div class=""><br class=""></div><div class="">```</div><div class=""><div class="">format_version: '2'</div><div class="">name: link</div><div class="">run_fields:</div><div class=""> - name: llvm_project_revision</div><div class=""> order: true</div><div class="">machine_fields:</div><div class=""> - name: hardware</div><div class=""> - name: os</div><div class="">metrics:</div><div class=""> - name: branch-misses</div><div class=""> bigger_is_better: false</div><div class=""> type: Real</div><div class=""> - name: stalled-cycles-frontend</div><div class=""> bigger_is_better: false</div><div class=""> type: Real</div><div class=""> - name: branches</div><div class=""> bigger_is_better: false</div><div class=""> type: Real</div><div class=""> - name: context-switches</div><div class=""> bigger_is_better: false</div><div class=""> type: Real</div><div class=""> - name: cpu-migrations</div><div class=""> bigger_is_better: false</div><div class=""> type: Real</div><div class=""> - name: cycles</div><div class=""> bigger_is_better: false</div><div class=""> type: Real</div><div class=""> - name: instructions</div><div class=""> bigger_is_better: false</div><div class=""> type: Real</div><div class=""> - name: seconds-elapsed</div><div class=""> bigger_is_better: false</div><div class=""> type: Real</div><div class=""> - name: page-faults</div><div class=""> bigger_is_better: false</div><div class=""> type: Real</div><div class=""> - name: task-clock</div><div class=""> bigger_is_better: false</div><div class=""> type: Real</div><div class="">```</div><div><br class=""><blockquote type="cite" class=""><div class="">On Jan 19, 2021, at 1:49 PM, Jez via llvm-dev <<a href="mailto:llvm-dev@lists.llvm.org" class="">llvm-dev@lists.llvm.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">Hi,<div class=""><br class=""></div><div class="">I understand that the `link` test suite schema at <a href="https://lnt.llvm.org/" class="">https://lnt.llvm.org/</a> is being used to record profiling results for LLD for ELF. I would like to do the same with LLD's Mach-O implementation by running the profiling jobs on an internal server & submitting the results to the public LNT instance. A few questions:</div><div class=""><br class=""></div><div class="">1. I don't see the `link` schema under `schemas/` in the `lnt` repo. Where can I find it?</div><div class=""><br class=""></div><div class="">2. Should I reuse the schema or create a new one? I expect that we can stick to the same set of perf data fields, so reusing should be fine as long as we create one more column to indicate whether we're running the ELF or Mach-O suite.</div><div class=""><br class=""></div><div class="">3. I would also like to reuse the lld/utils/benchmark.py script. Currently, it invokes the LLD for ELF process via a hard-coded name, so I would like to make that configurable via a CLI flag. But that would involve updating the current job on the `as-worker` machines to specify the ELF back-end. Who owns those machines and would be able to do this update? (That said, it's hardly a blocker, since I can still have the script default the ELF backend for now.)</div><div class=""><br class=""></div><div class="">Thanks,</div><div class=""><div class=""><div dir="ltr" data-smartmail="gmail_signature" class="">Jez</div></div></div></div>
_______________________________________________<br class="">LLVM Developers mailing list<br class=""><a href="mailto:llvm-dev@lists.llvm.org" class="">llvm-dev@lists.llvm.org</a><br class="">https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev<br class=""></div></blockquote></div><br class=""></div></body></html>