search for: dataref

...ing an inner loop inside a parallel loop. > > > > I suggest that we only add the 'llvm.loop.parallel' metadata and not llvm.mem.parallem. Ok. A solution similar to Pekka's, using fewer annotations as you suggested, is to reference in 'llvm.loop.parallel' all the datarefs to which the parallel access semantics applies. When the list of datarefs in 'llvm.loop.parallel' differs from the datarefs in the loop, the annotation is deemed invalid. Sebastian -- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation

...parallel loop. >>> >> >> I suggest that we only add the 'llvm.loop.parallel' metadata and not llvm.mem.parallem. > > > Ok. A solution similar to Pekka's, using fewer annotations as you suggested, is > to reference in 'llvm.loop.parallel' all the datarefs to which the parallel > access semantics applies. When the list of datarefs in 'llvm.loop.parallel' > differs from the datarefs in the loop, the annotation is deemed invalid. That sounds elegant and seems to solve the correctness problems. Cheers, Tobias

On Feb 7, 2013, at 10:55 AM, Pekka Jääskeläinen <pekka.jaaskelainen at tut.fi> wrote: > Hi Nadav, > > On 02/07/2013 07:46 PM, Nadav Rotem wrote: >> Pekka suggested that we add two kind of metadata: llvm.loop.parallel >> (attached to each loop latch) and llvm.mem.parallel (attached to each memory >> instruction!). I think that the motivation for the first

...; + (offset, aml[offset])); > + offset += 1; > + pkglenbytes = aml_pkglen_bytes(offset) > + offset += pkglenbytes; > + return offset; > + > +# Given name offset, find its NameString offset > +def aml_name_string(offset): > + #0x08 NameOp NameString DataRef > + if (aml[offset] != 0x08): > + die( "Name offset 0x%x: expected 0x08 actual 0x%x" % > + (offset, aml[offset])); > + offset += 1 > + # Block Name Modifier. Skip it. > + if (aml[offset] == 0x5c or aml[offset] == 0x5e): > + offset...

Patrick, there following patches fix xenpaging for me. Granttable handling is incomplete. If a page is gone, a GNTST_eagain should be returned to the caller to inidcate the hypercall has to be retried after a while, until the page is available again. Please review. Olaf _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com

Unlike full virtualization in which the virtual machine provides the same platform interface as running natively on the hardware, paravirtualization requires modification to the guest operating system to work with the platform interface provided by the hypervisor. Xen was designed with performance in mind. Calls to the hypervisor are minimized, batched if necessary, and non-critical codepaths

Unlike full virtualization in which the virtual machine provides the same platform interface as running natively on the hardware, paravirtualization requires modification to the guest operating system to work with the platform interface provided by the hypervisor. Xen was designed with performance in mind. Calls to the hypervisor are minimized, batched if necessary, and non-critical codepaths

Unlike full virtualization in which the virtual machine provides the same platform interface as running natively on the hardware, paravirtualization requires modification to the guest operating system to work with the platform interface provided by the hypervisor. Xen was designed with performance in mind. Calls to the hypervisor are minimized, batched if necessary, and non-critical codepaths