[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PATCH v17 6/6] virtio-balloon: VIRTIO_BALLOON_F_FREE_P

From: Wei Wang
Subject: Re: [Qemu-devel] [PATCH v17 6/6] virtio-balloon: VIRTIO_BALLOON_F_FREE_PAGE_VQ
Date: Tue, 14 Nov 2017 20:02:03 +0800
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0

On 11/14/2017 01:32 AM, Michael S. Tsirkin wrote:
- guest2host_cmd: written by the guest to ACK to the host about the
commands that have been received. The host will clear the corresponding
bits on the host2guest_cmd register. The guest also uses this register
to send commands to the host (e.g. when finish free page reporting).
I am not sure what is the role of guest2host_cmd. Reporting of
the correct cmd id seems sufficient indication that guest
received the start command. Not getting any more seems sufficient
to detect stop.

I think the issue is when the host is waiting for the guest to report pages, it does not know whether the guest is going to report more or the report is done already. That's why we need a way to let the guest tell the host "the report is done, don't wait for more", then the host continues to the next step - sending the non-free pages to the destination. The following method is a conclusion of other comments, with some new thought. Please have a check if it is good.

Two new configuration registers in total:
- cmd_reg: the command register, combined from the previous host2guest and guest2host. I think we can use the same register for host requesting and guest ACKing, since the guest writing will trap to QEMU, that is, all the writes to the register are performed in QEMU, and we can keep things work in a correct way there.
- cmd_id_reg: the sequence id of the free page report command.

-- free page report:
- host requests the guest to start reporting by "cmd_reg | REPORT_START"; - guest ACKs to the host about receiving the start reporting request by "cmd_reg | REPORT_START", host will clear the flag bit once receiving the ACK.
    - host requests the guest to stop reporting by "cmd_reg | REPORT_STOP";
- guest ACKs to the host about receiving the stop reporting request by "cmd_reg | REPORT_STOP", host will clear the flag once receiving the ACK. - guest tells the host about the start of the reporting by writing "cmd id" into an outbuf, which is added to the free page vq. - guest tells the host about the end of the reporting by writing "0" into an outbuf, which is added to the free page vq. (we reserve "id=0" as the stop sign)

-- ballooning:
- host requests the guest to start ballooning by "cmd_reg | BALLOONING"; - guest ACKs to the host about receiving the request by "cmd_reg | BALLOONING", host will clear the flag once receiving the ACK.

Some more explanations:
-- Why not let the host request the guest to start the free page reporting simply by writing a new cmd id to the cmd_id_reg? The configuration interrupt is shared among all the features - ballooning, free page reporting, and future feature extensions which need host-to-guest requests. Some features may need to add other feature specific configuration registers, like free page reporting need the cmd_id_reg, which is not used by ballooning. The rule here is that the feature specific registers are read only when that feature is requested via the cmd_reg. For example, the cmd_id_reg is read only when "cmd_reg | REPORT_START" is true. Otherwise, when the driver receives a configuration interrupt, it has to read both cmd_reg and cmd_id registers to know what are requested by the host - think about the case that ballooning requests are sent frequently while free page reporting isn't requested, the guest has to read the cmd_id register every time a ballooning request is sent by the host, which is not necessary. If future new features follow this style, there will be more unnecessary VMexits to read the unused feature specific registers. So I think it is good to have a central control of the feature request via only one cmd register - reading that one is enough to know what is requested by the host.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]