Displaying 12 results from an estimated 12 matches for "muthuswami".
Did you mean:
muthuswamy
2019 Jun 13
2
[PATCH net-next] vsock: correct removal of socket from the list
The current vsock code for removal of socket from the list is both
subject to race and inefficient. It takes the lock, checks whether
the socket is in the list, drops the lock and if the socket was on the
list, deletes it from the list. This is subject to race because as soon
as the lock is dropped once it is checked for presence, that condition
cannot be relied upon for any decision. It is also
2019 Jun 13
2
[PATCH net-next] vsock: correct removal of socket from the list
The current vsock code for removal of socket from the list is both
subject to race and inefficient. It takes the lock, checks whether
the socket is in the list, drops the lock and if the socket was on the
list, deletes it from the list. This is subject to race because as soon
as the lock is dropped once it is checked for presence, that condition
cannot be relied upon for any decision. It is also
2019 Jun 13
0
[PATCH net-next] vsock: correct removal of socket from the list
On Thu, Jun 13, 2019 at 03:52:27AM +0000, Sunil Muthuswamy wrote:
> The current vsock code for removal of socket from the list is both
> subject to race and inefficient. It takes the lock, checks whether
> the socket is in the list, drops the lock and if the socket was on the
> list, deletes it from the list. This is subject to race because as soon
> as the lock is dropped once it
2019 Jun 15
0
[PATCH net-next] vsock: correct removal of socket from the list
From: Sunil Muthuswamy <sunilmut at microsoft.com>
Date: Thu, 13 Jun 2019 03:52:27 +0000
> The current vsock code for removal of socket from the list is both
> subject to race and inefficient. It takes the lock, checks whether
> the socket is in the list, drops the lock and if the socket was on the
> list, deletes it from the list. This is subject to race because as soon
> as
2020 Sep 15
0
[PATCH RFC v1 08/18] x86/hyperv: handling hypercall page setup for root
Wei Liu <wei.liu at kernel.org> writes:
> When Linux is running as the root partition, the hypercall page will
> have already been setup by Hyper-V. Copy the content over to the
> allocated page.
And we can't setup a new hypercall page by writing something different
to HV_X64_MSR_HYPERCALL, right?
>
> The suspend, resume and cleanup paths remain untouched because they
2020 Sep 15
0
[PATCH RFC v1 10/18] x86/hyperv: implement and use hv_smp_prepare_cpus
Wei Liu <wei.liu at kernel.org> writes:
> Microsoft Hypervisor requires the root partition to make a few
> hypercalls to setup application processors before they can be used.
>
> Signed-off-by: Lillian Grassin-Drake <ligrassi at microsoft.com>
> Signed-off-by: Sunil Muthuswamy <sunilmut at microsoft.com>
> Co-Developed-by: Lillian Grassin-Drake <ligrassi at
2020 Sep 15
0
[PATCH RFC v1 13/18] asm-generic/hyperv: introduce hv_device_id and auxiliary structures
Wei Liu <wei.liu at kernel.org> writes:
> We will need to identify the device we want Microsoft Hypervisor to
> manipulate. Introduce the data structures for that purpose.
>
> They will be used in a later patch.
>
> Signed-off-by: Sunil Muthuswamy <sunilmut at microsoft.com>
> Co-Developed-by: Sunil Muthuswamy <sunilmut at microsoft.com>
> Signed-off-by:
2020 Sep 15
0
[PATCH RFC v1 08/18] x86/hyperv: handling hypercall page setup for root
Wei Liu <wei.liu at kernel.org> writes:
> On Tue, Sep 15, 2020 at 12:32:29PM +0200, Vitaly Kuznetsov wrote:
>> Wei Liu <wei.liu at kernel.org> writes:
>>
>> > When Linux is running as the root partition, the hypercall page will
>> > have already been setup by Hyper-V. Copy the content over to the
>> > allocated page.
>>
>> And we
2020 Sep 15
0
[PATCH RFC v1 08/18] x86/hyperv: handling hypercall page setup for root
Wei Liu <wei.liu at kernel.org> writes:
> On Tue, Sep 15, 2020 at 01:02:08PM +0200, Vitaly Kuznetsov wrote:
>> Wei Liu <wei.liu at kernel.org> writes:
>>
>> > On Tue, Sep 15, 2020 at 12:32:29PM +0200, Vitaly Kuznetsov wrote:
>> >> Wei Liu <wei.liu at kernel.org> writes:
>> >>
>> >> > When Linux is running as the
2020 Sep 15
0
[PATCH RFC v1 09/18] x86/hyperv: provide a bunch of helper functions
Wei Liu <wei.liu at kernel.org> writes:
> They are used to deposit pages into Microsoft Hypervisor and bring up
> logical and virtual processors.
>
> Signed-off-by: Lillian Grassin-Drake <ligrassi at microsoft.com>
> Signed-off-by: Sunil Muthuswamy <sunilmut at microsoft.com>
> Signed-off-by: Nuno Das Neves <nudasnev at microsoft.com>
>
2020 Sep 16
1
[EXTERNAL] Re: [PATCH RFC v1 08/18] x86/hyperv: handling hypercall page setup for root
>
> On Tue, Sep 15, 2020 at 12:32:29PM +0200, Vitaly Kuznetsov wrote:
> > Wei Liu <wei.liu at kernel.org> writes:
> >
> > > When Linux is running as the root partition, the hypercall page will
> > > have already been setup by Hyper-V. Copy the content over to the
> > > allocated page.
> >
> > And we can't setup a new hypercall
2020 Sep 15
0
[PATCH RFC v1 07/18] x86/hyperv: extract partition ID from Microsoft Hypervisor if necessary
Wei Liu <wei.liu at kernel.org> writes:
> We will need the partition ID for executing some hypercalls later.
>
> Signed-off-by: Lillian Grassin-Drake <ligrassi at microsoft.com>
> Co-Developed-by: Sunil Muthuswamy <sunilmut at microsoft.com>
> Signed-off-by: Wei Liu <wei.liu at kernel.org>
> ---
> arch/x86/hyperv/hv_init.c | 26