Make a couple minor wording improvements and split an overly-long paragrph to make it more readable. --- multiple-monitors.rst | 34 ++++++++++++++++++---------------- 1 file changed, 18 insertions(+), 16 deletions(-) diff --git a/multiple-monitors.rst b/multiple-monitors.rst index 18ffe0c..5289f42 100644 --- a/multiple-monitors.rst +++ b/multiple-monitors.rst @@ -120,9 +120,9 @@ will have a single DisplayChannel which manages up to 4 displays on the same channel. A Windows guest will have multiple Display channels, one for each device and each managing a single display. -Implementation -++++++++++++++ -Since so many different components are involved, the implementation can vary +Implementation Notes +++++++++++++++++++++ +Since many different components are involved, the implementation can vary significantly between different guest operating systems or even between different versions of the components. Several of these differences have already been discussed above, but there are others to be aware of as well. @@ -132,19 +132,21 @@ Server When the server receives a new monitors config message from the client, the server checks whether the qxl device implementation provides a monitors config callback function. If it does, that callback is executed. If that callback is -not provided, the monitors config is instead send via a char device to the -spice vdagent running within the guest. These different approaches will be -discussed in more detail below. As the guest display configuration changes, the -QXL device will be updated and the server will send new monitors config -messages to the client. Note that guests can change display configurations in -different manners and the change is not necessarily done atomically. So when a -client requests a display configuration change, the change may happen in -several steps (e.g. enable an additional display and then move that display to -the proper location and then resize that display to the appropriate -resolution). These different steps may each result in a monitors config message -being sent from the server to the client. So you cannot rely on a single -monitors config request from a client generating a single monitors config reply -from the server. +not provided, the monitors config message is instead sent via a char device to +the spice vdagent running within the guest. These different approaches will be +discussed in more detail below. + +Whenever the guest display configuration changes, the QXL device will be +updated and the server will send new monitors config messages to the client to +notify the client of the changes. Note that different guests may change the +display configuration in different ways and the change is not necessarily done +atomically. In other words, when a client requests a display configuration +change, the change may happen in several steps (e.g. enable an additional +display and then move that display to the proper location and then resize that +display to the appropriate resolution). These different steps may each result +in a monitors config message being sent from the server to the client. Because +of this, there is no guarantee of a one-to-one relationship between a monitors +config request from a client and a monitors config reply from the server. Guest ----- -- 2.9.3 _______________________________________________ Spice-devel mailing list Spice-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/spice-devel