{"push_id":1419056796,"size":7,"distinct_size":4,"ref":"refs/heads/nvdimm","head":"6705b8e18b158da9917f6c881f5735c5313e5d9f","before":"b704079aea340ab22e276c8f15a1660337f5d1a9","commits":[{"sha":"085692c8bb9154f6f5e66b2e3fa150daef03fa19","author":{"name":"Michal Privoznik","email":"ff52d8b477e4489d0b3b856d550bc61214c6ad4b@redhat.com"},"message":"qemu: Update cgroup on RNG hotplug\n\nIf users try to hotplug RNG device with a backend different to\n/dev/random or /dev/urandom the whole operation fails as qemu is\nunable to access the device. The problem is we don't update\ndevice CGroups during the operation.\n\nSigned-off-by: Michal Privoznik <mprivozn@redhat.com>","distinct":false,"url":"https://api.github.com/repos/zippy2/libvirt/commits/085692c8bb9154f6f5e66b2e3fa150daef03fa19"},{"sha":"5d9c2c708111835ee8e625a9c8a98353687c3fa5","author":{"name":"Michal Privoznik","email":"ff52d8b477e4489d0b3b856d550bc61214c6ad4b@redhat.com"},"message":"qemu: Update cgroup on chardev hotplug\n\nJust like in the previous commit, we are not updating CGroups on\nchardev hot(un-)plug and thus leaving qemu unable to access any\nnon-default device users are trying to hotplug.\n\nSigned-off-by: Michal Privoznik <mprivozn@redhat.com>","distinct":false,"url":"https://api.github.com/repos/zippy2/libvirt/commits/5d9c2c708111835ee8e625a9c8a98353687c3fa5"},{"sha":"0f366efce0e4d518cfd87a341c428a851d39bbf0","author":{"name":"Michal Privoznik","email":"ff52d8b477e4489d0b3b856d550bc61214c6ad4b@redhat.com"},"message":"Introduce NVDIMM memory model\n\nNVDIMM is new type of memory introduced in qemu. The idea is that\nwe have a DIMM module that keeps the data persistent across\ndomain reboots.\nAt the domain XML level, we already have some representation of\n'dimm' modules. Long story short, we have <memory/> element that\nlives under <devices/>. Now, the element even has @model\nattribute which we can use to introduce new memory type:\n\n    <memory model='nvdimm'>\n      <source>\n        <path>/tmp/nvdimm</path>\n      </source>\n      <target>\n        <size unit='KiB'>523264</size>\n        <node>0</node>\n      </target>\n    </memory>\n\nSo far, this is just a XML parser/formatter extension. QEMU\ndriver implementation is in the next commit.\n\nFor more info on NVDIMM visit the following web page:\n\n    http://pmem.io/\n\nSigned-off-by: Michal Privoznik <mprivozn@redhat.com>","distinct":false,"url":"https://api.github.com/repos/zippy2/libvirt/commits/0f366efce0e4d518cfd87a341c428a851d39bbf0"},{"sha":"2b527d5f7a26c3b106580d38465f10fbabe76410","author":{"name":"Michal Privoznik","email":"ff52d8b477e4489d0b3b856d550bc61214c6ad4b@redhat.com"},"message":"qemu: Introduce QEMU_CAPS_DEVICE_NVDIMM\n\nIntroduce a qemu capability for -device nvdimm.\n\nSigned-off-by: Michal Privoznik <mprivozn@redhat.com>","distinct":true,"url":"https://api.github.com/repos/zippy2/libvirt/commits/2b527d5f7a26c3b106580d38465f10fbabe76410"},{"sha":"5f2f3f90dfc746b21c11e6fa393be1cb046933eb","author":{"name":"Michal Privoznik","email":"ff52d8b477e4489d0b3b856d550bc61214c6ad4b@redhat.com"},"message":"qemu: Implement NVDIMM\n\nSo, majority of the code is just ready as-is. Well, with one\nslight change: differentiate between dimm and nvdimm in places\nlike device alias generation, generating the command line and so\non.\n\nSpeaking of the command line, we also need to append 'nvdimm=on'\nto the '-machine' argument so that the nvdimm feature is\nadvertised in the ACPI tables properly.\n\nSigned-off-by: Michal Privoznik <mprivozn@redhat.com>","distinct":true,"url":"https://api.github.com/repos/zippy2/libvirt/commits/5f2f3f90dfc746b21c11e6fa393be1cb046933eb"},{"sha":"d92bc6547974e451e658639b8865963add44d1e7","author":{"name":"Michal Privoznik","email":"ff52d8b477e4489d0b3b856d550bc61214c6ad4b@redhat.com"},"message":"conf: Introduce memAccess to <memory/>\n\nNow that NVDIMM has found its way into libvirt, users might want\nto fine tune some settings for each module separately. One such\nsetting is 'share=on|off' for the memory-backend-file object.\nThis setting - just like its name suggest already - enables\nsharing the nvdimm module with other applications. Under the hood\nit controls whether qemu mmaps() the file as MAP_PRIVATE or\nMAP_SHARED.\n\nYet again, we have such config knob in domain XML, but it's just\nan attribute to numa <cell/>. This does not give fine enough\ntuning on per-memdevice basis so we need to have the attribute\nfor each device too.\n\nSigned-off-by: Michal Privoznik <mprivozn@redhat.com>","distinct":true,"url":"https://api.github.com/repos/zippy2/libvirt/commits/d92bc6547974e451e658639b8865963add44d1e7"},{"sha":"6705b8e18b158da9917f6c881f5735c5313e5d9f","author":{"name":"Michal Privoznik","email":"ff52d8b477e4489d0b3b856d550bc61214c6ad4b@redhat.com"},"message":"qemu: Implement memAccess for <memory/> banks\n\nSigned-off-by: Michal Privoznik <mprivozn@redhat.com>","distinct":true,"url":"https://api.github.com/repos/zippy2/libvirt/commits/6705b8e18b158da9917f6c881f5735c5313e5d9f"}]}
{"actor":{"display_login":"zippy2"}}