Home
last modified time | relevance | path

Searched refs:pmem (Results 1 – 23 of 23) sorted by relevance

/openbmc/qemu/hw/virtio/
H A Dvirtio-pmem.c32 VirtIOPMEM *pmem; member
62 virtqueue_push(req_data->pmem->rq_vq, &req_data->elem, len); in done_cb()
63 virtio_notify((VirtIODevice *)req_data->pmem, req_data->pmem->rq_vq); in done_cb()
71 VirtIOPMEM *pmem = VIRTIO_PMEM(vdev); in virtio_pmem_flush() local
72 HostMemoryBackend *backend = MEMORY_BACKEND(pmem->memdev); in virtio_pmem_flush()
88 req_data->pmem = pmem; in virtio_pmem_flush()
95 VirtIOPMEM *pmem = VIRTIO_PMEM(vdev); in virtio_pmem_get_config() local
98 virtio_stq_p(vdev, &pmemcfg->start, pmem->start); in virtio_pmem_get_config()
99 virtio_stq_p(vdev, &pmemcfg->size, memory_region_size(&pmem->memdev->mr)); in virtio_pmem_get_config()
111 VirtIOPMEM *pmem = VIRTIO_PMEM(dev); in virtio_pmem_realize() local
[all …]
H A Dvirtio-pmem-pci.c45 VirtIOPMEM *pmem = &pci_pmem->vdev; in virtio_pmem_pci_get_memory_region() local
46 VirtIOPMEMClass *vpc = VIRTIO_PMEM_GET_CLASS(pmem); in virtio_pmem_pci_get_memory_region()
48 return vpc->get_memory_region(pmem, errp); in virtio_pmem_pci_get_memory_region()
55 VirtIOPMEM *pmem = &pci_pmem->vdev; in virtio_pmem_pci_get_plugged_size() local
56 VirtIOPMEMClass *vpc = VIRTIO_PMEM_GET_CLASS(pmem); in virtio_pmem_pci_get_plugged_size()
57 MemoryRegion *mr = vpc->get_memory_region(pmem, errp); in virtio_pmem_pci_get_plugged_size()
68 VirtIOPMEM *pmem = &pci_pmem->vdev; in virtio_pmem_pci_fill_device_info() local
69 VirtIOPMEMClass *vpc = VIRTIO_PMEM_GET_CLASS(pmem); in virtio_pmem_pci_fill_device_info()
77 vpc->fill_device_info(pmem, vi); in virtio_pmem_pci_fill_device_info()
H A Dmeson.build57 specific_virtio_ss.add(when: 'CONFIG_VIRTIO_PMEM', if_true: files('virtio-pmem.c'))
84 virtio_pci_ss.add(when: 'CONFIG_VIRTIO_PMEM', if_true: files('virtio-pmem-pci.c'))
H A Dtrace-events152 # virtio-pmem.c
/openbmc/qemu/docs/system/devices/
H A Dvirtio-pmem.rst3 virtio pmem
6 This document explains the setup and usage of the virtio pmem device.
7 The virtio pmem device is a paravirtualized persistent memory device
13 Virtio pmem allows to bypass the guest page cache and directly use
17 How does virtio-pmem compare to the nvdimm emulation?
22 specification. The virtio pmem device provides guest write persistence
25 virtio pmem usage
28 A virtio pmem device backed by a memory-backend-file can be created on
32 -device virtio-pmem-pci,memdev=mem1,id=nv1
39 - "device virtio-pmem-pci,id=nvdimm1,memdev=mem1" creates a virtio pmem
[all …]
/openbmc/qemu/include/hw/virtio/
H A Dvirtio-pmem.h42 void (*fill_device_info)(const VirtIOPMEM *pmem, VirtioPMEMDeviceInfo *vi);
43 MemoryRegion *(*get_memory_region)(VirtIOPMEM *pmem, Error **errp);
/openbmc/u-boot/post/drivers/
H A Dmemory.c201 static int memory_post_dataline(unsigned long long * pmem) in memory_post_dataline() argument
210 move64(&(pattern[i]), pmem++); in memory_post_dataline()
215 move64(&otherpattern, pmem--); in memory_post_dataline()
216 move64(pmem, &temp64); in memory_post_dataline()
231 pmem, pathi, patlo, hi, lo); in memory_post_dataline()
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-extended/pmdk/
H A Dpmdk_2.1.1.bb3 HOMEPAGE = "http://pmem.io"
14 SRC_URI = "git://github.com/pmem/pmdk.git;branch=master;protocol=https"
/openbmc/qemu/docs/
H A Dnvdimm.txt176 both 'pmem' and 'share' flags are set to 'on' on the backend.
178 If these conditions are not satisfied i.e. if either 'pmem' or 'share'
245 the 'pmem' option of memory-backend-file to 'on'. When 'pmem' is 'on' and QEMU
249 If 'pmem' is 'on' while there is no libpmem support, qemu will exit and report
254 -object memory-backend-file,id=nv_mem,mem-path=/XXX/yyy,size=4G,pmem=on
263 http://pmem.io/pmdk/
265 http://pmem.io/ndctl/ndctl-create-namespace.html
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-core/ndctl/ndctl/
H A D0001-include-libgen.h-for-basename.patch12 Upstream-Status: Submitted [https://github.com/pmem/ndctl/pull/263]
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-core/ndctl/
H A Dndctl_v79.bb14 SRC_URI = "git://github.com/pmem/ndctl.git;branch=main;protocol=https \
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-benchmark/fio/
H A Dfio_3.39.bb14 DEPENDS += "${@bb.utils.contains('MACHINE_FEATURES', 'pmem', 'pmdk', '', d)}"
/openbmc/qemu/docs/system/
H A Ddevice-emulation.rst97 devices/virtio-pmem.rst
/openbmc/u-boot/drivers/ram/
H A Dstm32_sdram.c33 u32 pmem; /* Common memory space timing register */ member
/openbmc/qemu/docs/about/
H A Ddeprecated.rst379 Using non-persistent backing file with pmem=on (since 6.1)
383 device. However enabling ``memory-backend-file.pmem`` option, when backing file
389 - modify VM configuration to set ``pmem=off`` to continue using fake NVDIMM
391 - move backing file to NVDIMM storage and keep ``pmem=on``
/openbmc/qemu/docs/specs/
H A Dacpi_nvdimm.rst44 http://pmem.io/documents/NVDIMM_DSM_Interface_Example.pdf
/openbmc/openbmc/poky/meta/recipes-devtools/qemu/
H A Dqemu.inc217 PACKAGECONFIG[pmem] = "--enable-libpmem,--disable-libpmem,pmdk"
/openbmc/qemu/qapi/
H A Dmachine.json1419 # @virtio-pmem: since 4.1
1430 'data': [ 'dimm', 'nvdimm', 'virtio-pmem', 'virtio-mem', 'sgx-epc',
1497 'virtio-pmem': 'VirtioPMEMDeviceInfoWrapper',
H A Dqom.json717 # @pmem: specifies whether the backing file specified by @mem-path is
747 '*pmem': { 'type': 'bool', 'if': 'CONFIG_LIBPMEM' },
/openbmc/openbmc/poky/documentation/migration-guides/
H A Drelease-notes-4.0.rst253 - qemu: Add knob for enabling PMDK pmem support
/openbmc/qemu/
H A Dqemu-options.hx5624 The ``pmem`` option specifies whether the backing file specified
5627 NVDIMM). If ``pmem`` is set to 'on', QEMU will take necessary
/openbmc/
Dopengrok1.0.log[all...]
Dopengrok2.0.log[all...]