[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAKdAkRSSYTWWoTdcw+dsgNDNd1QrngQZRd_3x4UT03sFYs3O8g@mail.gmail.com>
Date: Tue, 1 Dec 2015 15:52:37 -0800
From: Dmitry Torokhov <dmitry.torokhov@...il.com>
To: Sinclair Yeh <syeh@...are.com>
Cc: X86 ML <x86@...nel.org>,
"pv-drivers@...are.com" <pv-drivers@...are.com>,
"linux-graphics-maintainer@...are.com"
<linux-graphics-maintainer@...are.com>,
virtualization@...ts.linux-foundation.org,
lkml <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 4/6] Input: Remove vmmouse port reservation
On Tue, Dec 1, 2015 at 3:04 PM, Sinclair Yeh <syeh@...are.com> wrote:
> Hi,
>
> On Tue, Dec 01, 2015 at 02:30:05PM -0800, Dmitry Torokhov wrote:
>> Hi Sinclair,
>>
>> On Tue, Dec 1, 2015 at 2:18 PM, Sinclair Yeh <syeh@...are.com> wrote:
>> > Port reservation is not required.
>>
>> You need to expand on why we do not need to reserve port.
>
> Thomas gave me this input earlier, too, so I added the one liner.
>
> There was a long discussion on accessing the port a few years ago:
> https://lkml.org/lkml/2008/9/24/512
>
>>
>> > Furthermore, this port is shared
>> > by other VMware services for host-side communication.
>>
>> What services would that be? Do they reserve the port?
>
> This port is used by quite a few guest-to-host communication capabilities,
> e.g. getting configuration, logging, etc. Currently multiple kernel
> modules, and one or more priviledged guest user mode app, e.g.
> open-vmware-tools, use this port without reservation.
Ah, I forgot that vmmouse does not have a dedicated port...
>
> After some internal discussions, it was determined that no reservation
> is required when accessing the port in this manner.
>
> Do you want me to put the above in the commit message?
Not about the bit about "internal discussions", but the rest - yes please.
--
Dmitry
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists