search for: shareable

...the outer > > > coherent stuff. > > > > Does outer coherent imply inner coherent? > > > > > the *mb() primitives cover both. > > I do not think so, but lets add Will, he dreams this stuff. Right, and I don't sleep well these days. Anyway, the outer-shareable domain (osh) is a superset of the inner-shareable domain (ish). The inner-shareable domain contains the CPUs and any peripherals that you and I would call "cache coherent". The outer-shareable domain extends this to cover a strange set of "less cache coherent" devices, which we...

...the outer > > > coherent stuff. > > > > Does outer coherent imply inner coherent? > > > > > the *mb() primitives cover both. > > I do not think so, but lets add Will, he dreams this stuff. Right, and I don't sleep well these days. Anyway, the outer-shareable domain (osh) is a superset of the inner-shareable domain (ish). The inner-shareable domain contains the CPUs and any peripherals that you and I would call "cache coherent". The outer-shareable domain extends this to cover a strange set of "less cache coherent" devices, which we...

We wan't to setup two Oracle instance and make RAC work on them. Both VM are setup based on libvirt + KVM, we use a lvm lun which formated in qcow2 format and set the shareable properties in the disk driver like this: <disk type='block' device='disk'> <driver name='qemu' type='qcow2' cache='none'/> <source dev='/dev/81035c32-d2e4-4aaf-82fa-3e76ae587586/ca18f6a5-7c98-46ea-b562-9424e68a52f3'/&gt...

Commit aa9e0057b19e29f76c9a81f9aebeeb1cb5bf1fdb made the libvirt backend use <shareable/> for the disk of the appliance, since at that time all the instances were using the disk directly. OTOH, commit 3ad44c866042919374e2d840502e53da2ed8aef0 switched to overlays for read-only disks, including the appliance, so effectively protecting the appliance. Because of this, the libvirt back...

We currently setup page table walks etc as outer-shareable. Given we don''t really make the distinction between inner- and outer-shareable yet err on theside of safety. Signed-off-by: Ian Campbell <ian.campbell@citrix.com> Cc: Stefano Stabellini <Stefano.Stabellini@eu.citrix.com> Cc: Tim Deegan <tim@xen.org> --- xen/include/asm-...

...the IDE bus. > > On Fri, Aug 2, 2013 at 1:58 PM, Timon Wang <timonwst@gmail.com> wrote: >> We wan't to setup two Oracle instance and make RAC work on them. >> Both VM are setup based on libvirt + KVM, we use a lvm lun which >> formated in qcow2 format and set the shareable properties in the disk >> driver like this: >> >> <disk type='block' device='disk'> >> <driver name='qemu' type='qcow2' cache='none'/> >> <source dev='/dev/81035c32-d2e4-4aaf-82fa-3e76ae587586/c...

Hello Kindred R Spirits... I'm trying to get a file (csv) from Dropbox using their shareable link concept. They issue a short URL that goes to a web page where you see a button that says "Download File". They don't really give you the URL of the file itself, just this page. Is there a way to coax R into getting such a file? I don't even really want the file pe...

On Thu, Dec 17, 2015 at 03:02:12PM +0100, Peter Zijlstra wrote: > On Thu, Dec 17, 2015 at 03:26:29PM +0200, Michael S. Tsirkin wrote: > > > Note that virtio_mb() is weirdly inconsistent with virtio_[rw]mb() in > > > that they use dma_* ops for weak_barriers, while virtio_mb() uses > > > smp_mb(). > > > > It's a hack really. I think I'll clean it

On Thu, Dec 17, 2015 at 03:02:12PM +0100, Peter Zijlstra wrote: > On Thu, Dec 17, 2015 at 03:26:29PM +0200, Michael S. Tsirkin wrote: > > > Note that virtio_mb() is weirdly inconsistent with virtio_[rw]mb() in > > > that they use dma_* ops for weak_barriers, while virtio_mb() uses > > > smp_mb(). > > > > It's a hack really. I think I'll clean it

...benchmark the difference as measureable in the past. The generic implementation for the smp_ barriers does the same thing when CONFIG_SMP is defined. The only spot where there should be an appreciable difference between the two is on ARM where we define the dma_ barriers as being in the outer shareable domain, and for the smp_ barriers they are inner shareable domain. > Additionally, isn't this relying on undocumented behaviour? > The documentation says: > "These are for use with consistent memory" > and virtio does not bother to request consistent memory > allocat...

...benchmark the difference as measureable in the past. The generic implementation for the smp_ barriers does the same thing when CONFIG_SMP is defined. The only spot where there should be an appreciable difference between the two is on ARM where we define the dma_ barriers as being in the outer shareable domain, and for the smp_ barriers they are inner shareable domain. > Additionally, isn't this relying on undocumented behaviour? > The documentation says: > "These are for use with consistent memory" > and virtio does not bother to request consistent memory > allocat...

Hi I just wondered if there was a reason why Rails controller specs are not shareable? eg describe "All XHR POSTs to /gap/calculate_quote", :shared => true do controller_name :gap # ... end describe "XHR POST /gap/calculate_quote with valid details" do it_should_behave_like "All XHR POSTs to /gap/calculate_quote" # ... end bl...

...s, but still can't get through. On Fri, Aug 2, 2013 at 1:58 PM, Timon Wang <timonwst@gmail.com> wrote: > We wan't to setup two Oracle instance and make RAC work on them. > Both VM are setup based on libvirt + KVM, we use a lvm lun which > formated in qcow2 format and set the shareable properties in the disk > driver like this: > > <disk type='block' device='disk'> > <driver name='qemu' type='qcow2' cache='none'/> > <source dev='/dev/81035c32-d2e4-4aaf-82fa-3e76ae587586/ca18f6a5-7c98-46ea-b5...

...gt; >> On Fri, Aug 2, 2013 at 1:58 PM, Timon Wang <timonwst@gmail.com> wrote: >>> We wan't to setup two Oracle instance and make RAC work on them. >>> Both VM are setup based on libvirt + KVM, we use a lvm lun which >>> formated in qcow2 format and set the shareable properties in the disk >>> driver like this: >>> >>> <disk type='block' device='disk'> >>> <driver name='qemu' type='qcow2' cache='none'/> >>> <source dev='/dev/81035c32-d2e4-4aaf...

...o the client passes the dma-buf to the guest proxy, the guest proxy imports it to look up the resource-id, passes the resource-id to the host proxy, the host proxy looks up the drm buffer and exports it as dma-buf, then passes it to the server. Done, without any extra data copies. > Creation of shareable buffer by guest > ------------------------------------------------- > > 1. Client requests virtio driver to create a buffer suitable for sharing > with host (DRM_VIRTGPU_RESOURCE_CREATE) client or guest proxy? > 4. QEMU maps that buffer to the guest's address space > (KVM_S...

...o the client passes the dma-buf to the guest proxy, the guest proxy imports it to look up the resource-id, passes the resource-id to the host proxy, the host proxy looks up the drm buffer and exports it as dma-buf, then passes it to the server. Done, without any extra data copies. > Creation of shareable buffer by guest > ------------------------------------------------- > > 1. Client requests virtio driver to create a buffer suitable for sharing > with host (DRM_VIRTGPU_RESOURCE_CREATE) client or guest proxy? > 4. QEMU maps that buffer to the guest's address space > (KVM_S...

...ux/5/html-single/Virtualization/index.html#proc-Virtualization-Adding_storage_devices_to_guests-Adding_physical_block_devices_to_virtualized_guests First I check that the module acpiphp is present on the guest. It is. On the host I write: virsh attach-disk test1 /dev/sdb1 sda --driver tap --mode shareable - test1 is my guest domain - /dev/sdb1 is the name of the unformatted partition on the host - sda is what it is supposed to be called on the guest (the name is unused on the guest) - the example in RHEL Virtualization guide says "--mode readonly". This does not sound right for a hard dis...

...ELinux - solved, DAC - not (yet). >> > > I played with it earlier, but I'm not sure which settings we use when. > This is just a "possible workaround", even though it might look like > it's doing something else.  Anyway, If I'm not mistaken, adding a > <shareable/> into the <disk> element should stop all relabeling. > Correct me if I'm wrong and post your findings, I'll try how relabel > works for DAC with upstream in the meantime. <shareable/> didn't work for me.  This is what I currently have:     # virsh dumpxml test   ...

...activity on that bug so far. This is the results when attaching virtio-scsi disks in a loop. Sdf is attached but sdg fails. virsh attach-disk --domain UEM004n1 --source /dev/GuestVols/UEM004-5 --target sdf --cache none --type disk --config --wwn 1fc7058865439717 --serial c7d11fc7058865439717 --shareable Disk attached successfully Vol UEM004-6 created virsh attach-disk --domain UEM004n1 --source /dev/GuestVols/UEM004-6 --target sdg --cache none --type disk --config --wwn 4d3ddb9d15b05e7e --serial 62fd4d3ddb9d15b05e7e --shareable error: Failed to attach disk error: internal error Unable to determi...

...define PAGE_SZ 4096 /* PAGE_SIZE @ */ + +ENTRY(cpu_flush_tlb_all) + dsb + mov ip, #0 +#ifndef SMP + mcr p15, 0, ip, c8, c6, 0 @ invalidate Entire I TLB + mcr p15, 0, ip, c8, c5, 0 @ invalidate Entire D TLB +#else + mcr p15, 0, ip, c8, c3, 0 +#endif + mcr p15, 0, ip, c7, c5, 6 @ flush BTAC/BTB (shareable) + dsb + isb + mov pc, lr + +ENTRY(cpu_flush_tlb_entry) + dsb +#ifndef SMP + mcr p15, 0, r0, c8, c6, 1 @ TLB invalidate D MVA + mcr p15, 0, r0, c8, c5, 1 @ TLB invalidate I MVA +#else + mcr p15, 0, r0, c8, c3, 1 @ TLB invalidate U MVA (shareable) +#endif + mov ip, #0 + mcr p15, 0, ip, c7, c5, 6...