search for: localmem

...ageFiles; /* Created by VMX using VMCI page files */ + struct vmci_queue *produceQ; + struct vmci_queue *consumeQ; + struct vmci_queue_header savedProduceQ; + struct vmci_queue_header savedConsumeQ; + VMCIEventReleaseCB wakeupCB; + void *clientData; + void *localMem; /* Kernel memory for local queue pair */ +}; + +struct qp_guest_endpoint { + struct qp_entry qp; + uint64_t numPPNs; + void *produceQ; + void *consumeQ; + struct PPNSet ppnSet; +}; + +struct qp_list { + struct list_head head; + struct semaphore mutex; +};...

...ageFiles; /* Created by VMX using VMCI page files */ + struct vmci_queue *produceQ; + struct vmci_queue *consumeQ; + struct vmci_queue_header savedProduceQ; + struct vmci_queue_header savedConsumeQ; + VMCIEventReleaseCB wakeupCB; + void *clientData; + void *localMem; /* Kernel memory for local queue pair */ +}; + +struct qp_guest_endpoint { + struct qp_entry qp; + uint64_t numPPNs; + void *produceQ; + void *consumeQ; + struct PPNSet ppnSet; +}; + +struct qp_list { + struct list_head head; + struct semaphore mutex; +};...

Hello, I'm trying to define in my new back end, in MyBackendInstrInfo.td file, a vector load instruction that takes an immediate address operand. (I got inspired from Mips' MSA SIMD extensions.) Could you please tell me what's the right way to do it? Here, the load class has $addrsrc which is a relative address with base a certain register and offset: class

...name == "rv730") { > + mDeviceFlag = OCL_DEVICE_RV730; > + } else { > + mDeviceFlag = OCL_DEVICE_RV770; > + } > +} > + > +AMDIL7XXDevice::~AMDIL7XXDevice() > +{ > +} > + > +void AMDIL7XXDevice::setCaps() > +{ > + mSWBits.set(AMDILDeviceInfo::LocalMem); > +} > + > +size_t AMDIL7XXDevice::getMaxLDSSize() const > +{ > + if (usesHardware(AMDILDeviceInfo::LocalMem)) { > + return MAX_LDS_SIZE_700; > + } > + return 0; > +} > + > +size_t AMDIL7XXDevice::getWavefrontSize() const > +{ > + return AMDILDevice::...

Second revision of the VMware VMCI RFC patchset. It incorperates fixes for all the feedback about the comment blocks and style and now passes checkpatch with 0 errors and 0 warnings. Thanks to all who have reviewed the code thus far. * * * In an effort to improve the out-of-the-box experience with Linux kernels for VMware users, VMware is working on readying the Virtual Machine Communication

Second revision of the VMware VMCI RFC patchset. It incorperates fixes for all the feedback about the comment blocks and style and now passes checkpatch with 0 errors and 0 warnings. Thanks to all who have reviewed the code thus far. * * * In an effort to improve the out-of-the-box experience with Linux kernels for VMware users, VMware is working on readying the Virtual Machine Communication

In an effort to improve the out-of-the-box experience with Linux kernels for VMware users, VMware is working on readying the Virtual Machine Communication Interface (vmw_vmci) and VMCI Sockets (vmw_vsock) kernel modules for inclusion in the Linux kernel. The purpose of this post is to acquire feedback on the vmw_vmci kernel module. The vmw_vsock kernel module will be presented in a later post.

In an effort to improve the out-of-the-box experience with Linux kernels for VMware users, VMware is working on readying the Virtual Machine Communication Interface (vmw_vmci) and VMCI Sockets (vmw_vsock) kernel modules for inclusion in the Linux kernel. The purpose of this post is to acquire feedback on the vmw_vmci kernel module. The vmw_vsock kernel module will be presented in a later post.

In an effort to improve the out-of-the-box experience with Linux kernels for VMware users, VMware is working on readying the Virtual Machine Communication Interface (vmw_vmci) and VMCI Sockets (vmw_vsock) kernel modules for inclusion in the Linux kernel. The purpose of this post is to acquire feedback on the vmw_vmci kernel module. The vmw_vsock kernel module will be presented in a later post.

In an effort to improve the out-of-the-box experience with Linux kernels for VMware users, VMware is working on readying the Virtual Machine Communication Interface (vmw_vmci) and VMCI Sockets (vmw_vsock) kernel modules for inclusion in the Linux kernel. The purpose of this post is to acquire feedback on the vmw_vmci kernel module. The vmw_vsock kernel module will be presented in a later post.