search for: msg42783

...ISON)) > > + __virtio_clear_bit(vdev, VIRTIO_BALLOON_F_REPORTING); > > > > __virtio_clear_bit(vdev, VIRTIO_F_IOMMU_PLATFORM); > > return 0; > > > > Did you see my feedback on v1? > > https://www.spinics.net/lists/linux-virtualization/msg42783.html > > In case of want_init_on_free(), we don't really need VIRTIO_BALLOON_F_PAGE_POISON. I believe we do. We had discussions earlier in which Michael had mentioned that the guest should not assume implementation details of the host/hypervisor. The PAGE_POISON feature is being used to...

...ISON)) > > + __virtio_clear_bit(vdev, VIRTIO_BALLOON_F_REPORTING); > > > > __virtio_clear_bit(vdev, VIRTIO_F_IOMMU_PLATFORM); > > return 0; > > > > Did you see my feedback on v1? > > https://www.spinics.net/lists/linux-virtualization/msg42783.html > > In case of want_init_on_free(), we don't really need VIRTIO_BALLOON_F_PAGE_POISON. I believe we do. We had discussions earlier in which Michael had mentioned that the guest should not assume implementation details of the host/hypervisor. The PAGE_POISON feature is being used to...

From: Alexander Duyck <alexander.h.duyck at linux.intel.com> We should disable free page reporting if page poisoning is enabled in the kernel but we cannot report it via the balloon interface. This way we can avoid the possibility of corrupting guest memory. Normally the page poison reporting feature should always be present when free page reporting is enabled on the hypervisor, however

From: Alexander Duyck <alexander.h.duyck at linux.intel.com> We should disable free page reporting if page poisoning is enabled in the kernel but we cannot report it via the balloon interface. This way we can avoid the possibility of corrupting guest memory. Normally the page poison reporting feature should always be present when free page reporting is enabled on the hypervisor, however

...else if (!virtio_has_feature(vdev, VIRTIO_BALLOON_F_PAGE_POISON)) > + __virtio_clear_bit(vdev, VIRTIO_BALLOON_F_REPORTING); > > __virtio_clear_bit(vdev, VIRTIO_F_IOMMU_PLATFORM); > return 0; > Did you see my feedback on v1? https://www.spinics.net/lists/linux-virtualization/msg42783.html In case of want_init_on_free(), we don't really need VIRTIO_BALLOON_F_PAGE_POISON. -- Thanks, David / dhildenb

...__virtio_clear_bit(vdev, VIRTIO_BALLOON_F_REPORTING); >>> >>> __virtio_clear_bit(vdev, VIRTIO_F_IOMMU_PLATFORM); >>> return 0; >>> >> >> Did you see my feedback on v1? >> >> https://www.spinics.net/lists/linux-virtualization/msg42783.html >> >> In case of want_init_on_free(), we don't really need VIRTIO_BALLOON_F_PAGE_POISON. > > I believe we do. We had discussions earlier in which Michael had > mentioned that the guest should not assume implementation details of > the host/hypervisor. We can simpl...

...ON_F_REPORTING); > >>> > >>> __virtio_clear_bit(vdev, VIRTIO_F_IOMMU_PLATFORM); > >>> return 0; > >>> > >> > >> Did you see my feedback on v1? > >> > >> https://www.spinics.net/lists/linux-virtualization/msg42783.html > >> > >> In case of want_init_on_free(), we don't really need VIRTIO_BALLOON_F_PAGE_POISON. > > > > I believe we do. We had discussions earlier in which Michael had > > mentioned that the guest should not assume implementation details of > > the h...