search for: unaddressable

...ily describe the exact semantic of an instruction. For instance, on x86 it is probably right to assume most instruction do not touch the high bits, but on AArch64 this is the opposite. That's not necessary. In the x86-64 case, if EAX had an extra reg unit that it would share with RAX (for the unaddressable part extending from bit 16 upwards), then none of AL=, AH=, or AX= would invalidate the rest of EAX and RAX, while EAX= would, since it would store into the "hidden" reg unit. The fact that RAX ends up with 0s in the high part would not be exploited by any target-independent code. T...

On 9/28/2016 2:59 PM, Quentin Colombet wrote: > The cases where that it could make sense to use unaddressable register units are: > > 2. If we want to track precise liveness for physical registers > > #2 is not a problem IMO since most of our work with liveness happens on unallocated code. This is what I'm working on (RDF). I generate a data-flow graph for physical registers, and I need t...

On 9/28/2016 1:20 PM, Quentin Colombet wrote: > >> On Sep 28, 2016, at 10:52 AM, Krzysztof Parzyszek via llvm-dev <llvm-dev at lists.llvm.org> wrote: >> >> On X86, the registers AX, EAX and RAX all share the exact same register units. In terms of units, there is no difference between these registers. This makes register units insufficient to track liveness, since live AX

On X86, the registers AX, EAX and RAX all share the exact same register units. In terms of units, there is no difference between these registers. This makes register units insufficient to track liveness, since live AX does not imply live EAX. Would it make sense to have register units (and lane masks) for the parts of registers that are not individually addressable? -Krzysztof -- Qualcomm

Hi, We all know most people are reporting that Amazon hasn't been helpful at all. A few people say they've received answers, but most are getting smoke screen PR BS. You can vote this up on Slashdot, send the message: SIP Attacks From Amazon EC2 Going Unaddressed: http://bit.ly/bOkNNx Send this message out to Amazon, I am positive that once it reaches the right person, they will do the

Hi! I'm working on ASan option that uses llvm.lifetime intrinsics to detect use-after-scope bugs. In short, the idea is to insert calls into ASan runtime that would mark the memory as "addressable" or "unaddressable". I see the following problem with the following "trivial" basic block: for.body.lr.ph.i: ; preds = %for.body.i310 call void @llvm.lifetime.start(i64 24, i8* %174) call void @llvm.lifetime.start(i64 4, i8* %175) call void @llvm.lifetime.start(i6...

...es (unneeded in math, but perhaps needed in some code): Fs * Ss / Fe >= ( Fo / Cs ) + 2 Note the ">=". In fact ">" is the common case and "=" would be a rare case (yet, desirable). The uncommon case would be "<", resulting in unallocatable (unaddressable) sectors (which is the issue we are discussing). > The free amount of sectors must be the total amount minus the FAT's and > the Reserved Sectors. We'll assume the Root Directory takes no space, Again, inaccurate. First, the ">=" I mentioned before; so the &q...

...on STAGING + select DEVICE_PRIVATE select HMM_MIRROR select MMU_NOTIFIER default n diff --git a/mm/Kconfig b/mm/Kconfig index c1acc34c1c358c..7ca36bf5f5058e 100644 --- a/mm/Kconfig +++ b/mm/Kconfig @@ -805,15 +805,10 @@ config HMM_MIRROR depends on MMU config DEVICE_PRIVATE - bool "Unaddressable device memory (GPU memory, ...)" + bool depends on ZONE_DEVICE select DEV_PAGEMAP_OPS - help - Allows creation of struct pages to represent unaddressable device - memory; i.e., memory that is only accessible from the device (or - group of devices). You likely also want to select HM...

...on STAGING + select DEVICE_PRIVATE select HMM_MIRROR select MMU_NOTIFIER default n diff --git a/mm/Kconfig b/mm/Kconfig index c1acc34c1c358c..7ca36bf5f5058e 100644 --- a/mm/Kconfig +++ b/mm/Kconfig @@ -805,15 +805,10 @@ config HMM_MIRROR depends on MMU config DEVICE_PRIVATE - bool "Unaddressable device memory (GPU memory, ...)" + bool depends on ZONE_DEVICE select DEV_PAGEMAP_OPS - help - Allows creation of struct pages to represent unaddressable device - memory; i.e., memory that is only accessible from the device (or - group of devices). You likely also want to select HM...

http://developer.kde.org/~sewardj/ Valgrind is a GPL'd tool to help you find memory-management problems in your programs. When a program is run under Valgrind's supervision, all reads and writes of memory are checked, and calls to malloc/new/free/delete are intercepted. As a result, Valgrind can detect problems such as: * Use of uninitialised memory * Reading/writing memory after

With the traditional qemu tree fixed to not use PROT_WRITE anymore in the mmap() call for this region, and with the upstream qemu tree not being capable of handling passthrough, yet, there''s no need to treat Dom specially here anymore. This continues to leave unaddressed the case where PV guests map the MSI-X table page(s) before setting up the first MSI-X interrupt (see the original c/s

Relatedly, Phabricator doesn't stop you continuing a comment chain for reasons I have yet to follow, which Github sometimes does. Some others: 1) I believe Github also doesn't have an easy way to respond to multiple comments simultaneously, if you are not in "review" mode, (which is always the case if you are replying to out-of-line comments). 2) Typically in our Phabricator,

...t; I don't think your pigeonhole is from git master. Thanks. That was it... Now onto 2.3 -git, there is a repeatable crash occurring in lmtp. In fact it looks like there could be more than one problem, because even invoking lmtp (with gdb) and no arguments results in a gdb error about an unaddressable byte. However when lmtp is used normally within dovecot it crashes out on a few but not all mails. The full gdb output looks like this: Oct 20 12:59:21 thunderstorm.reub.net dovecot: master: Dovecot v2.3.devel (c398eca6b) starting up for imap, lmtp, sieve Oct 20 12:59:30 thunderstorm.reub.net...

This past weekend, but holiday was ruined due to a log device "replacement" gone awry. I posted all about it here: http://jmlittle.blogspot.com/2008/05/problem-with-slogs-how-i-lost.html In a nutshell, an resilver of a single log device with itself, due to the fact one can''t remove a log device from a pool once defined, cause ZFS to fully resilver but then attach the log

...y Samsonov <samsonov at google.com>wrote: > Hi! > > I'm working on ASan option that uses llvm.lifetime intrinsics to detect > use-after-scope bugs. In short, the idea is to > insert calls into ASan runtime that would mark the memory as "addressable" > or "unaddressable". > I see the following problem with the following "trivial" basic block: > > for.body.lr.ph.i: ; preds = %for.body.i310 > call void @llvm.lifetime.start(i64 24, i8* %174) > call void @llvm.lifetime.start(i64 4, i8* %175) > call...

...R) */ #if IS_ENABLED(CONFIG_DEVICE_PRIVATE) || IS_ENABLED(CONFIG_DEVICE_PUBLIC) -struct hmm_devmem; - -/* - * struct hmm_devmem_ops - callback for ZONE_DEVICE memory events - * - * @free: call when refcount on page reach 1 and thus is no longer use - * @fault: call when there is a page fault to unaddressable memory - * - * Both callback happens from page_free() and page_fault() callback of struct - * dev_pagemap respectively. See include/linux/memremap.h for more details on - * those. - * - * The hmm_devmem_ops callback are just here to provide a coherent and - * uniq API to device driver and device dr...

On 19 August 2016 at 19:35, Justin Bogner <mail at justinbogner.com> wrote: > I think you misunderstood what I meant here. Whether "moving to git" > will affect my workflow depends very much on "how we're moving to > git". That's exactly what I understood. :) > For example, if we do a monorepo, I may now need to lay code out > differently on my

...hole is from git master. > > Thanks.? That was it... > > Now onto 2.3 -git, there is a repeatable crash occurring in lmtp. In > fact it looks like there could be more than one problem, because even > invoking lmtp (with gdb) and no arguments results in a gdb error about > an unaddressable byte. > > However when lmtp is used normally within dovecot it crashes out on a > few but not all mails. I see what that smtp-submit problem is already. Will push fix later today. We're not sure that epoll_pwait() issue is an actual problem or valgrind being confused. Regards, St...

On Wed, 8 Jan 2020 at 01:48, Eric Christopher via llvm-dev <llvm-dev at lists.llvm.org> wrote: > I am in favor of having a flang front end in tree. I have concerns about the design of flang versus other front ends, the lack of llvm based library use, and a number of other things that I tried to enumerate in previous emails. I don't know if anything has changed and the responses I got

...ReservedSecCnt) Denominator = (SecPerClus * BytesPerSect) + (FatElementSize * NumFATs) Then +1 is added to the FAT Size for rounding. ----------------------------------------------------------------------- However, as Ady demonstrated, this computation doesn't actually work because it leaves unaddressable sectors. So let us instead try to follow Ady's post, to derive a proper algorithm. First, let me quote the relevant part: On 2016.02.25 20:49, Ady via Syslinux wrote: > _ Bytes per Sector: 512 > _ FAT Entries per Sector: 128 > _ Reserved Sectors: 32 > _ Volume's Total Sector...