search for: afaiu

...rgument and take actions depending it, this may answer Halil's >> concern. >> >> Regards, >> Pierre >> > > hum, in between I found another way which seems to me much better: > > We already have the force_dma_unencrypted() function available which > AFAIU is what we want for encrypted memory protection and is already > used by power and x86 SEV/SME in a way that seems AFAIU compatible > with our problem. > > Even DMA and IOMMU are different things, I think they should be used > together in our case. > > What do you think? &gt...

...rgument and take actions depending it, this may answer Halil's >> concern. >> >> Regards, >> Pierre >> > > hum, in between I found another way which seems to me much better: > > We already have the force_dma_unencrypted() function available which > AFAIU is what we want for encrypted memory protection and is already > used by power and x86 SEV/SME in a way that seems AFAIU compatible > with our problem. > > Even DMA and IOMMU are different things, I think they should be used > together in our case. > > What do you think? &gt...

...//llvm.org/docs/GettingStarted.html currently mentions Python 2.5 as a minimum required version. I'd like to use argparse <https://docs.python.org/dev/library/argparse.html> in a script and be able to test this script. This requires Python 2.7. This version has been around since 2010, and afaiu, is available on all modern platforms. Is there any reason not to change minimum required version of Python to 2.7? -- Regards, Alexander Kornienko -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20140626/d22...

On 2020-06-11 05:10, Jason Wang wrote: > > On 2020/6/10 ??9:11, Pierre Morel wrote: >> Protected Virtualisation protects the memory of the guest and >> do not allow a the host to access all of its memory. >> >> Let's refuse a VIRTIO device which does not use IOMMU >> protected access. >> >> Signed-off-by: Pierre Morel <pmorel at

On 2020-06-11 05:10, Jason Wang wrote: > > On 2020/6/10 ??9:11, Pierre Morel wrote: >> Protected Virtualisation protects the memory of the guest and >> do not allow a the host to access all of its memory. >> >> Let's refuse a VIRTIO device which does not use IOMMU >> protected access. >> >> Signed-off-by: Pierre Morel <pmorel at

...40, Vince Hsu wrote: > >>This patch adds some checks in the suspend/resume functions to distinguish > >>the dGPU and mobile GPU and exports some variables/functions so that the > >>nouveau platform device can reuse them. > >> > >Hi Vince, > > > >Afaiu one needs to export a symbol as it's used by another module or > >subsystem. With the follow up two patches you are not doing either one, > >so I'd assume that you can just omit the EXPORT_* changes. > The nouveau platform device driver is built as another module - > nouve...

...ed to the pod, needed by libvirtd and other services. One of the capabilities libvirtd requires for successful startup inside a pod is SYS_RESOURCE. This capability is used to adjust RLIMIT_MEMLOCK ulimit value depending on devices attached to the managed guest, both on startup and during hotplug. AFAIU the need to lock the memory is to avoid pages being pushed out from RAM into swap. In KubeVirt world, several libvirtd assumptions do not apply: 1. In Kubernetes environments, swap is usually disabled. (e.g. kubeadm official deployment tool won't even initialize a cluster until you disable it...

...that faithfully describes the JITted code into memory along with the JITted code itself and point the debugger to it. Let's assume that the bridge with the debugger is taken care of (e.g. http://llvm.org/docs/DebuggingJITedCode.html) - my concern in this question is solely with the LLVM side. AFAIU, LLVM currently includes very partial support for emitting DWARF info with JIT, in the JITDwarfEmitter class. What it has is just a way to emit stack frame information (symbols and DWARF CFA), to allow meaningful core dumps from JITted code, with stack information. This is useful, but obviously ver...

...irmware (few allocs, each bellow 100k). DomU kernel cmdline: console=hvc0 iommu=soft earlyprintk=xen There is two cases (I think): 1. With IOMMU 2. Without IOMMU I''ve tried only the second one. Is there any known solution for this problem? Some ideas: 1. With IOMMU pass iommu=pv to Xen. AFAIU domU will not need iommu=soft parameter then, right? Will it work then with fragmented memory? 2. Force somehow on xen/libxl to allocate memory (for domU) in chunks of, say 4MB, to not fragment it so badly. Is it doable? In tmem documentation is also described some workaround for this: reserve so...

...le to define an instruction as always having a certain register as operand in XXXInstrInfo.td? I know I can do it defining a single-register register class, but I need that register also to be on a broader class for other operations (and it is not possible for a reg to be in several classes AFAIU). Thanks! Carlos

...ractor::ExtractCodeRegion(const std::vector<llvm::BasicBlock*, std::allocator<llvm::BasicBlock*> >&): Assertion `BlocksToExtract.count(*PI) && "No blocks in this region may have entries from outside the region" " except for the first block!"' failed. AFAIU, this assertion is not related to ordering of analysis passes. Analyzing incoming bb vector for ExtractCodeRegion() may help you understand why you're triggering this assertion. May the vector is stale ? - Devang

On Mon, 15 Jun 2020 11:01:55 +0800 Jason Wang <jasowang at redhat.com> wrote: > > hum, in between I found another way which seems to me much better: > > > > We already have the force_dma_unencrypted() function available which > > AFAIU is what we want for encrypted memory protection and is already > > used by power and x86 SEV/SME in a way that seems AFAIU compatible > > with our problem. > > > > Even DMA and IOMMU are different things, I think they should be used > > together in our case. > &g...

Dear list! I am interested in learning about MLE and I wonder whether it is possible to use the examples for maximum likelihood estimation given in 8.7 in MASSv3 with R? AFAIU R does not have a direct replacement for S-PLUS's ms() which the examples use for the fitting, but optim() may be of help for me. However, I am not sure how I can convert the use of ms() using optim()--is there an explanation how to do this somewhere? Thanks. Best wishes, Sven C. Koehler =...

...omfortably "reset" R's library such that it only contains only the base packages again? In other words, how can I uninstall all contributed packages that I installed? Is there some sort of index that's keeping track of what has been installed? If so, a pointer would be great. AFAIU, if you don't create such an "index file" yourself and loose track of what you installed, probably the best way to "reset" R is to actually re-install it. That's exactly what I'm trying to avoid. I would like something like path.lib <- "path/to/R/lib&quot...

...posed to be a FXO card, but there are 2 rj-11 plug on the card. One is labelled "phone" and the other "pstn". When i plug the "pstn" on the wall and the "phone" on my analog phone, everything (incoming and outgoing calls) works like before (without asterisk). AFAIU, i should have an FXS card in my box to be able to use my analog phone, so why does it work this way ? Second question, what is the cheapest card to use one analog phone only (TDM400 is too expensive). I read there's a S100U which seems to be a single FXS card, but I can't find a webshop s...

Dear list, I have a small feature request regarding the implementation of 'file.path()': It'd be great if 'file.path()' would allow to specify an input *vector* instead of solely rely on a specification via the three dot argument. AFAIU, currently it's only possible to "manually" specify each path component via the three dot argument: > file.path(letters[1], letters[2], letters[3]) [1] "a/b/c" Providing a vector object will result in the same vector being returned, instead of a slash separated scalar...

...el Core i7 > gcc/g++ compiler available > TARGET: 32-bit mips-typed linux > gnu gcc/g++ for 32-bit mips-typed linux available > ------ * What do you specify as -target? (eg. clag -c -target i686-pc-mingw32) * Which toolchain have you installed and what is the prefix of it? AFAIU, GNU binutils for the target would be essential. (eg. /usr/bin/i686-pc-mingw32-ld) > As Clang's option is "-c" in use, my programs are compiled and linked under a host machine's environment (in my case, 32-bit Fedora 16 is a host OS with Intel Core i7). > > In order to c...

...orted both by the win-builder and the rhub services: * R 3.3.2: https://win-builder.r-project.org/xj8fwadE4K31/00check.log * R devel: https://win-builder.r-project.org/xj8fwadE4K31/00check.log * R 3.2.5: https://builder.r-hub.io/status/R.devices_2.14.0-9000.tar.gz-a252b2d919124c63bc976d78befce161 AFAIU, this is due to the HTTPS webserver not having SSL3 disabled, e.g. http://unix.stackexchange.com/questions/192944/how-to-fix-curl-sslv3-alert-handshake-failure. Is this something that should be fixed in R CMD check --as-cran itself? The only workaround I can see as a package maintainer is to drop...

...d. > > + \field{max_virtqueue_pairs} is valid only if VIRTIO_NET_F_MQ is > > + set and can be read by the driver. > > + > > > I don't get the point that adding "can be read by the driver". Looks > like it's hard for hypervisor to detect this? AFAIU, if the device sets VIRTIO_NET_F_MQ, the device also sets the value of 'max_virtqueue_pairs' even before driver negotiated VIRTIO_NET_F_MQ. If so, the driver can read the value of 'max_virtqueue_pairs' during negotiation and potentially this value can even affect negotiation decisio...

...d. > > + \field{max_virtqueue_pairs} is valid only if VIRTIO_NET_F_MQ is > > + set and can be read by the driver. > > + > > > I don't get the point that adding "can be read by the driver". Looks > like it's hard for hypervisor to detect this? AFAIU, if the device sets VIRTIO_NET_F_MQ, the device also sets the value of 'max_virtqueue_pairs' even before driver negotiated VIRTIO_NET_F_MQ. If so, the driver can read the value of 'max_virtqueue_pairs' during negotiation and potentially this value can even affect negotiation decisio...