search for: write_config

Hi, Got everything setup nicely with backgroundrb for the development environment and running tests with rspec. However, I have to keep editing the backgroundrb.yml file, to switch between development and testing environment. How can I declare a development, testing and production environment in backgroundrb.yml? Thanks in advance Rai

From: anand jain <anand.jain@oracle.com> Anand Jain (1): [RFC] Add btrfs autosnap feature Makefile | 6 +- autosnap.c | 1553 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ autosnap.h | 81 +++ btrfs-list.c | 140 +++++- btrfs.c | 46 ++- btrfs_cmds.c | 186 +++++++- btrfs_cmds.h | 3 +- scrub.c | 1 + 8 files changed, 1982 insertions(+), 34

...se; > + vhost_mdev_features_changed_t features_changed; > +}; Consider we want to implement a network device, who is going to implement the device configuration space? I believe it's not good to invent another set of API for doing this. So I believe we want something like read_config/write_config here. Then I came up an idea: 1) introduce a new mdev bus transport, and a new mdev driver virtio_mdev 2) vDPA (either software or hardware) can register as a device of virtio mdev device 3) then we can use kernel virtio driver to drive vDPA device and utilize kernel networking/storage stack 4)...

...se; > + vhost_mdev_features_changed_t features_changed; > +}; Consider we want to implement a network device, who is going to implement the device configuration space? I believe it's not good to invent another set of API for doing this. So I believe we want something like read_config/write_config here. Then I came up an idea: 1) introduce a new mdev bus transport, and a new mdev driver virtio_mdev 2) vDPA (either software or hardware) can register as a device of virtio mdev device 3) then we can use kernel virtio driver to drive vDPA device and utilize kernel networking/storage stack 4)...

...hanged_t features_changed; > > +}; > > > Consider we want to implement a network device, who is going to implement > the device configuration space? I believe it's not good to invent another > set of API for doing this. So I believe we want something like > read_config/write_config here. > > Then I came up an idea: > > 1) introduce a new mdev bus transport, and a new mdev driver virtio_mdev > 2) vDPA (either software or hardware) can register as a device of virtio > mdev device > 3) then we can use kernel virtio driver to drive vDPA device and utilize &...

...itialize event channels and io rings xen: Introduce the Xen mapcache piix3: introduce register_set_irq and register_map_irq piix_pci: introduce a write_config notifier vl.c: Introduce getter for shutdown_requested and reset_requested. xen: destroy the VM when shutdown is requested Makefile.target | 31 ++ arch_...

The OpRegion shouldn''t be mapped 1:1 because the address in the host can''t be used in the guest directly. This patch traps read and write access to the opregion of the Intel GPU config space (offset 0xfc). To work correctly this patch needs a change in hvmloader. HVMloader will allocate 2 pages for the OpRegion and write this address on the config space of the Intel GPU. Qemu