aboutsummaryrefslogtreecommitdiffstats
path: root/xen/arch/x86/hvm/rtc.c
diff options
context:
space:
mode:
authorOlaf Hering <olaf@aepfle.de>2012-03-01 15:58:02 +0000
committerOlaf Hering <olaf@aepfle.de>2012-03-01 15:58:02 +0000
commit2131e4744b591ef304e4ee2dd0d3c6891ad659b9 (patch)
tree4db2c4cda6a571bbd6e34a1b8f71c1d4b0180e99 /xen/arch/x86/hvm/rtc.c
parent546ba55410f7c772799b5f89c7027d8393b25b23 (diff)
downloadxen-2131e4744b591ef304e4ee2dd0d3c6891ad659b9.tar.gz
xen-2131e4744b591ef304e4ee2dd0d3c6891ad659b9.tar.bz2
xen-2131e4744b591ef304e4ee2dd0d3c6891ad659b9.zip
xenpaging: remove obsolete XENMEM_paging_op_resume
With changeset 24364:0964341efd65 an event channel based notification of new responses in the ringbuffer is implemented. This makes the memevent interface obsolete. Currently a call to p2m_mem_paging_resume() is triggered twice by xenpaging, once per memevent and once per even channel. In practice this double call does not lead to issues because p2m_mem_paging_resume() processes only available events. xenpaging used the event channel notification since the beginning, but it was a no-op until changeset mentioned above. This change removes the unneeded XENMEM_paging_op_resume functionality. Pagers are notified via an event channel of new requests, and now they are required to notify the hypervisor about their responses also with an event channel. Signed-off-by: Olaf Hering <olaf@aepfle.de> Acked-by: Tim Deegan <tim@xen.org> Acked-by: Ian Jackson <ian.jackson@eu.citrix.com> Committed-by: Ian Jackson <ian.jackson@eu.citrix.com>
Diffstat (limited to 'xen/arch/x86/hvm/rtc.c')
0 files changed, 0 insertions, 0 deletions