Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The LLVM Linux Project #219

Closed
tpimh opened this issue Oct 15, 2018 · 5 comments
Closed

The LLVM Linux Project #219

tpimh opened this issue Oct 15, 2018 · 5 comments
Labels
question Question asked by issue author.

Comments

@tpimh
Copy link

tpimh commented Oct 15, 2018

Since the LLVM Linux Project is deprecated, maybe we can get some exposure on @lll-project or llvm.linuxfoundation.org? Since @ClangBuiltLinux is a spiritual successor of that project with similar goals and active community, we can ask for a link from their pages.

@tpimh tpimh added the question Question asked by issue author. label Oct 15, 2018
@nickdesaulniers
Copy link
Member

We'd need a site to link to first. We could put up a gh-pages branch here.

@dileks
Copy link
Collaborator

dileks commented Oct 16, 2018

A new project name is desired - probably "ClangBuiltLinux". Personally, I name my linux-kernels with the suffix "cbl" like in my latest version "4.19.0-rc6-1-amd64-cbl".

@nickdesaulniers
Copy link
Member

Also, we're going to pay someone to do some vector art for the project soon. That way we can have a logo for a site, die cut stickers, and t shirts for our 🔥 contributors.

@tpimh
Copy link
Author

tpimh commented Oct 30, 2018

Possibly we can just create a ClangBuiltLinux.github.io repo and use a simple clean template from what GitHub Pages provides.

@nickdesaulniers
Copy link
Member

@behanw had sent me this note:

Hey. So Linux Foundation just forwarded the llvm.linuxfoundation.org URL to https://clangbuiltlinux.github.io/ , which is fine by me.

Again, I’m happy for you to use the “llvmlinux” name if you want to.

Closing this issue for now, as we have the links from Linux Foundation. But happy to reopen the discussion if folks feel passionately about this.

nathanchance pushed a commit that referenced this issue Oct 18, 2019
Workaround for Cavium/Marvell ThunderX2 erratum #219.

* errata/tx2-219:
  arm64: Allow CAVIUM_TX2_ERRATUM_219 to be selected
  arm64: Avoid Cavium TX2 erratum 219 when switching TTBR
  arm64: Enable workaround for Cavium TX2 erratum 219 when running SMT
  arm64: KVM: Trap VM ops when ARM64_WORKAROUND_CAVIUM_TX2_219_TVM is set
nathanchance pushed a commit that referenced this issue Oct 18, 2019
…git/arm64/linux

Pull arm64 fixes from Will Deacon:
 "The main thing here is a long-awaited workaround for a CPU erratum on
  ThunderX2 which we have developed in conjunction with engineers from
  Cavium/Marvell.

  At the moment, the workaround is unconditionally enabled for affected
  CPUs at runtime but we may add a command-line option to disable it in
  future if performance numbers show up indicating a significant cost
  for real workloads.

  Summary:

   - Work around Cavium/Marvell ThunderX2 erratum #219

   - Fix regression in mlock() ABI caused by sign-extension of TTBR1 addresses

   - More fixes to the spurious kernel fault detection logic

   - Fix pathological preemption race when enabling some CPU features at boot

   - Drop broken kcore macros in favour of generic implementations

   - Fix userspace view of ID_AA64ZFR0_EL1 when SVE is disabled

   - Avoid NULL dereference on allocation failure during hibernation"

* tag 'arm64-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux:
  arm64: tags: Preserve tags for addresses translated via TTBR1
  arm64: mm: fix inverted PAR_EL1.F check
  arm64: sysreg: fix incorrect definition of SYS_PAR_EL1_F
  arm64: entry.S: Do not preempt from IRQ before all cpufeatures are enabled
  arm64: hibernate: check pgd table allocation
  arm64: cpufeature: Treat ID_AA64ZFR0_EL1 as RAZ when SVE is not enabled
  arm64: Fix kcore macros after 52-bit virtual addressing fallout
  arm64: Allow CAVIUM_TX2_ERRATUM_219 to be selected
  arm64: Avoid Cavium TX2 erratum 219 when switching TTBR
  arm64: Enable workaround for Cavium TX2 erratum 219 when running SMT
  arm64: KVM: Trap VM ops when ARM64_WORKAROUND_CAVIUM_TX2_219_TVM is set
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Question asked by issue author.
Projects
None yet
Development

No branches or pull requests

3 participants