similar to: Refining which symbols are preemptable with lto

RFC: (Thin)LTO with Linker Scripts At the last US LLVM Developers' Meeting, we presented [1] a proposal for linker script support in (Thin)LTO. In this RFC, I would like to describe the proposal in more detail and invite the community's feedback, so we can build consensus on the upstream implementation. The end goal of this effort is to extend the benefits of (Thin)LTO, including

I recently sent off a fix for lazy vmalloc faults which can happen under = paravirt when lazy mode is enabled. Unfortunately, I jumped the gun a = bit on fixing this. I neglected to notice that since the new call to = flush the MMU update queue is called from the page fault handler, it can = be pre-empted. Both VMI and Xen use per-cpu variables to track lazy = mode state, as all previous

I recently sent off a fix for lazy vmalloc faults which can happen under = paravirt when lazy mode is enabled. Unfortunately, I jumped the gun a = bit on fixing this. I neglected to notice that since the new call to = flush the MMU update queue is called from the page fault handler, it can = be pre-empted. Both VMI and Xen use per-cpu variables to track lazy = mode state, as all previous

Hi, when creating a bigger (> 50 GB) HVM guest with maxmem > memory we get softlockups from time to time. kernel: [ 802.084335] BUG: soft lockup - CPU#1 stuck for 22s! [xend:31351] I tracked this down to the call of xc_domain_set_pod_target() and further p2m_pod_set_mem_target(). Unfortunately I can this check only with xen-4.2.2 as I don''t have a machine with enough memory for

> On Feb 25, 2016, at 11:41 AM, James Y Knight via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > While we're talking about this, I'd just mention again that the same issue arises for *normal* functions too, when linked into a shared library: > int foo() { return 1; } > int bar() { return foo(); } > > Now, compare: > clang -fPIC -O1 -S -o - test.c

Hello Tobias, Thanks very much for the RFC, I think that this will be useful in persuading embedded developers to use LTO in their projects. I think the overall approach for communication between the linker and code generator sounds reasonable. I've got some questions/comments based on some experience with Arm's proprietary linker, which supports LTO but has a different linker script

Someone recently posted on the x2go list that he had a problem with jerky videos playing remotely on Ubuntu, but solved it by installing a low latency kernel that was available as an alternative. That made me curious as to whether CentOS has an equivalent - or a way to build something similar. -- Les Mikesell lesmikesell at gmail.com

While we're talking about this, I'd just mention again that the same issue arises for *normal* functions too, when linked into a shared library: int foo() { return 1; } int bar() { return foo(); } Now, compare: clang -fPIC -O1 -S -o - test.c gcc -fPIC -O1 -S -o - test.c GCC will refuse to inline foo into bar, or use any information about foo in compiling bar, because foo is

Ok here is a real geek question, I building my own linux kernel for my asterisk system and came across the kernel setting for the timer frequency. I have one of 3 hardcode choices 100Hz, 250 Hz and 1000Hz. From what I understand the default Freq was changed from 100Hz in kernel 2.4 to 1000Hz (1KHz) in kernel 2.6. Timing is a BIG issue in asterisk with all the TDM and zap channel stuff.

Hi, This patch series is an update of my previous paravirt_ops patches. They are loosely based on Ingo's original paravirt_ops implementation for KVM. Some of the changes since the last series include: 1) Switch to using CPUID 0x40000000 instead of using MSR writes to discover shared memory area 2) Attempt to deal with SMP guests 3) Support for generic CR read caching 4) Support for

Hi, This patch series is an update of my previous paravirt_ops patches. They are loosely based on Ingo's original paravirt_ops implementation for KVM. Some of the changes since the last series include: 1) Switch to using CPUID 0x40000000 instead of using MSR writes to discover shared memory area 2) Attempt to deal with SMP guests 3) Support for generic CR read caching 4) Support for

Hi, Keir, The following patches refines Xen support for CPU Xsave/Xrestore support. There are four patches included. Patch 1/4: Cleaning up existing Xsave code in Xen. Replace xfeature_low and xfeature_high with a u64 variable xfeature_mask. In structure hvm_vcpu, rename xfeature_mask to xcr0 Provide EDX:EAX with all bits set to 1 for XSAVE and XRSTOR as spec recommends

On Mon, Sep 8, 2008 at 2:45 PM, Scott Graham <scott.llvm at h4ck3r.net> wrote: > LLVMTypeRef a = LLVMPointerType(LLVMOpaqueType(), 0); > LLVMTypeHandleRef ha = LLVMCreateTypeHandle(a); > LLVMTypeRef atypes[1] = { LLVMResolveTypeHandle(ha) }; > LLVMRefineType(LLVMResolveTypeHandle(ha), LLVMStructType(atypes, 1, 0)); > > Can anyone explain what I'm doing wrong

Hi, I've been using rsync (V 3.09) in non-daemon mode for a while to backup and/or sync various linux machines (sometimes to & from windows shares). I would like to reduce the stuff in my log files to the minimum (as I see it) and cannot find the appropriate parameters to rsync. I can obviously turn all logging off, but would like to see just the names (with path is ok, but not

Hi I'm using the llvm-c wrapper, and trying to build some recursive types (using released 2.3). I get an assert on trying to create a second opaque pointer type after refining a first. The first time through creating an opaque pointer type, a new type is created and returned from PointerType::get, but the second time, ValueType (the opaque type) is found in the PointerTypes map, which seems

Hi, I am currently using the following script to shape traffic on my linux box. I am getting ready to move the script to my linux firewall box so it shapes traffic for my home lan. I am looking to refine my rules a bit so to make bandwidth sharing a bit more efficient. Specifically I am looking to give out bound email more priority so that when a large email is sent, I want it to borrow all

Helo, I have problem with Digium TE110P connected to CISCO 3640 (port on NM-HDV-2E1-60) wth PRI E1 link. I use CISCO now for testing but when I tried with real PBX problem was exactly same. I have this messages in Asterisk conole and log sometimes: NOTICE[1115] chan_zap.c: PRI got event: HDLC Abort (6) on Primary D-channel of span 1 Usually 2-5 such messages in series, can be repeated after 10

Hi, I got a forced update when pulling today. If I merge master to a local branch, I get a bunch of add/add conflicts. This same commit exists under several hashes: https://github.com/llvm-project/llvm-project-20170507/commit/687841777ef505 https://github.com/llvm-project/llvm-project-20170507/commit/74725885552 Did someone push -f to the monorepo after doing branch surgery? Maybe there was a

While playing with sanitizer in a downstream project, I found out this. /Users/davide/work/llvm-monorepo/llvm-project-20170507/llvm/tools/llvm-mc-assemble-fuzzer/llvm-mc-assemble-fuzzer.cpp:207:32: error: reference to type 'std::unique_ptr<MCCodeEmitter>' could not bind to an lvalue of type 'llvm::MCCodeEmitter *' UseDwarfDirectory, IP, CE, MAB, ShowInst));

Hi all, This is something that came up in the "RFC: Add guard intrinsics to LLVM" thread; and while I'm not exactly blocked on this, figuring out a path forward here will be helpful in deciding if we can use the available_externally linkage type to expression certain semantic properties guard intrinsics will have. Let's start with an example that shows that we have a problem