From: "Srivatsa S. Bhat (VMware)"
I have decided to change employers and I'm not sure if I'll be able to
spend as much time on the paravirt-ops subsystem going forward. So, I
would like to remove myself from the maintainer role for paravirt-ops.
Remove Srivatsa from the maintai
From: "Srivatsa S. Bhat (VMware)"
I have decided to change employers, so I would like to remove myself
from the maintainer role for VMware-supported subsystems.
Remove Srivatsa from the maintainers entry for VMware virtual PTP
clock driver (ptp_vmw) and add Ajay Kaher as an additiona
From: "Srivatsa S. Bhat (VMware)"
I have decided to change employers, so I would like to remove myself
from the maintainer role for VMware-supported subsystems.
Remove Srivatsa from the maintainers entry for VMware hypervisor
interface and add Ajay Kaher as a co-maintainer. Also, upda
Hi,
On 1/27/23 4:37 PM, Srivatsa S. Bhat wrote:
> From: "Srivatsa S. Bhat (VMware)"
>
> The comment that says mwait_play_dead() returns only on failure is a
> bit misleading because mwait_play_dead() could actually return for
> valid reasons (such as mwait not being
map).
>
> As the first parameter of the old callbacks isn't used, drop it from
> the replacement one.
>
> Signed-off-by: Juergen Gross
> Reviewed-by: Boris Ostrovsky
Reviewed-by: Srivatsa S. Bhat (VMware)
Regards,
Srivatsa
VMware Photon OS
> ---
> V2:
> - expand com
From: "Srivatsa S. Bhat (VMware)"
The comment that says mwait_play_dead() returns only on failure is a
bit misleading because mwait_play_dead() could actually return for
valid reasons (such as mwait not being supported by the platform) that
do not indicate a failure of the CPU offline
Hi Igor and Sean,
On 1/20/23 10:35 AM, Sean Christopherson wrote:
> On Fri, Jan 20, 2023, Igor Mammedov wrote:
>> On Fri, 20 Jan 2023 05:55:11 -0800
>> "Srivatsa S. Bhat" wrote:
>>
>>> Hi Igor and Thomas,
>>>
>>> Thank you for your
Hi Igor and Thomas,
Thank you for your review!
On 1/19/23 1:12 PM, Thomas Gleixner wrote:
> On Mon, Jan 16 2023 at 15:55, Igor Mammedov wrote:
>> "Srivatsa S. Bhat" wrote:
>>> Fix this by preventing the use of mwait idle state in the vCPU offline
>>> play
On 1/15/23 10:43 PM, Juergen Gross wrote:
> On 16.01.23 05:27, Srivatsa S. Bhat wrote:
>>
>> Hi Juergen,
>>
>> On 1/12/23 7:21 AM, Juergen Gross wrote:
>>> The two paravirt callbacks .mmu.activate_mm and .mmu.dup_mmap are
>>> sharing the same im
From: "Srivatsa S. Bhat (VMware)"
Under hypervisors that support mwait passthrough, a vCPU in mwait
CPU-idle state remains in guest context (instead of yielding to the
hypervisor via VMEXIT), which helps speed up wakeups from idle.
However, this runs into problems with CPU hotplu
Hi Juergen,
On 1/12/23 7:21 AM, Juergen Gross wrote:
> The two paravirt callbacks .mmu.activate_mm and .mmu.dup_mmap are
> sharing the same implementations in all cases: for Xen PV guests they
> are pinning the PGD of the new mm_struct, and for all other cases
> they are a NOP.
>
I was
pted(), _paravirt_nop() and
paravirt_ret0(). Maybe that's worth calling out in the commit message?
Reviewed-by: Srivatsa S. Bhat (VMware)
Regards,
Srivatsa
VMware Photon OS
> ---
> arch/x86/include/asm/paravirt.h | 12 ++
> arch/x86/include/asm/qspinlock_paravirt.h | 46 +
On 9/23/22 3:45 AM, Borislav Petkov wrote:
> + kvm ML and leaving the whole mail quoted in for them.
>
> On Fri, Sep 23, 2022 at 09:05:26AM +0200, Peter Zijlstra wrote:
>> On Thu, Jul 21, 2022 at 01:44:33PM -0700, Srivatsa S. Bhat wrote:
>>> From: Srivatsa S. Bhat (VMwa
Hi Boris, Thomas, Peter,
On 7/21/22 1:44 PM, Srivatsa S. Bhat wrote:
> From: Srivatsa S. Bhat (VMware)
>
> VMware ESXi allows enabling a passthru mwait CPU-idle state in the
> guest using the following VMX option:
>
> monitor_control.mwait_in_guest = "TRUE"
&g
gt;
> Fixes: 63338a38db95 ("jailhouse: Provide detection for non-x86 systems")
> Signed-off-by: Liang He
> Co-developed-by: Kelin Wang
> Signed-off-by: Kelin Wang
Reviewed-by: Srivatsa S. Bhat (VMware)
> ---
>
> v2: use proper return type not the 'np' pointer
>
>
[ Adding author and reviewers of commit 63338a38db95 ]
On 9/14/22 7:23 PM, Liang He wrote:
> In jailhouse_paravirt(), we should hold the reference returned from
> of_find_compatible_node() which has increased the refcount and then
> call of_node_put() with it when done.
>
> Fixes: 63338a38db95
From: Srivatsa S. Bhat (VMware)
VMware ESXi allows enabling a passthru mwait CPU-idle state in the
guest using the following VMX option:
monitor_control.mwait_in_guest = "TRUE"
This lets a vCPU in mwait to remain in guest context (instead of
yielding to the hypervisor via a VMEX
arning: objtool: xen_safe_halt+0xa: call to
> HYPERVISOR_sched_op.constprop.0() leaves .noinstr.text section
>
> Signed-off-by: Peter Zijlstra (Intel)
Reviewed-by: Srivatsa S. Bhat (VMware)
Regards,
Srivatsa
VMware Photon OS
> ---
> arch/x86/include/asm/paravirt.h |6
y 31 bits is not an issue in this case.
>
> Signed-off-by: Shreenidhi Shedi
> ---
Looks good to me.
Reviewed-by: Srivatsa S. Bhat (VMware)
> arch/x86/kernel/cpu/vmware.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/arch/x86/kernel/cpu/v
On 5/28/22 6:52 AM, Peter Zijlstra wrote:
> On Fri, May 27, 2022 at 11:27:37PM +0530, Shreenidhi Shedi wrote:
>> From: Shreenidhi Shedi
>>
>> Shifting signed 32-bit value by 31 bits is implementation-defined
>> behaviour. Using unsigned is better option for this.
>
> The kernel builds with
On 5/20/22 7:09 AM, Shreenidhi Shedi wrote:
> From: Shreenidhi Shedi
>
> From: Shreenidhi Shedi
>
> Shifting signed 32-bit value by 31 bits is implementation-defined
> behaviour. Using unsigned is better option for this.
>
> Fixes: 4cca6ea04d31 ("x86/apic: Allow x2apic without IR on VMware
Hi Shreenidhi,
Thank you for the patch!
On 5/20/22 2:26 AM, Borislav Petkov wrote:
> On Fri, May 20, 2022 at 12:58:57PM +0530, Shreenidhi Shedi wrote:
>> Shifting signed 32-bit value by 31 bits is implementation-defined
>> behaviour. Using unsigned is better option for this.
>>
Can you also add
On 5/17/22 1:54 AM, Will Deacon wrote:
> On Fri, May 13, 2022 at 04:32:53PM -0700, Srivatsa S. Bhat wrote:
>> On 5/13/22 10:46 AM, Elliot Berman wrote:
>>> From: Prakruthi Deepak Heragu
>>>
[...]
>>> static int stolen_time_cpu_down_prepare(uns
ork+0x10/0x20
>
> As a fix, introduce rcu lock to update stolen time structure.
>
> Suggested-by: Will Deacon
> Signed-off-by: Prakruthi Deepak Heragu
> Signed-off-by: Elliot Berman
> ---
Looks good to me, but one quick question though (see below).
Reviewed-by: Srivatsa S.
[+virtualization list, which I forgot to CC when posting v5]
Hi Thomas, other x86 maintainers,
On 2/25/22 2:23 PM, Srivatsa S. Bhat wrote:
> This series updates a few maintainer entries for VMware-maintained
> subsystems and cleans up references to VMware's private mailing lists
>
On Mon, Nov 15, 2021 at 08:33:40PM -0800, Joe Perches wrote:
> On Mon, 2021-11-15 at 14:39 -0800, Srivatsa S. Bhat wrote:
> > On Fri, Nov 12, 2021 at 12:16:53PM -0500, Sasha Levin wrote:
> > > Maybe we should just remove MAINTAINERS from stable trees to make it
> > >
On Fri, Nov 12, 2021 at 12:16:53PM -0500, Sasha Levin wrote:
> On Thu, Nov 11, 2021 at 11:40:02AM -0800, Srivatsa S. Bhat wrote:
> > On Thu, Nov 11, 2021 at 07:45:02PM +0100, Greg KH wrote:
> > > On Thu, Nov 11, 2021 at 07:39:16AM -0800, Srivatsa S. Bhat wrote:
> > > &
[ Resending since my previous reply didn't reach the mailing lists. ]
On 11/11/21 5:55 AM, Jakub Kicinski wrote:
> On Wed, 10 Nov 2021 21:19:53 -0800 Joe Perches wrote:
>> On Wed, 2021-11-10 at 17:39 -0800, Jakub Kicinski wrote:
>>> On Wed, 10 Nov 2021 12:09:06 -0800 Sriv
On Fri, Nov 12, 2021 at 07:55:14AM +0100, Greg KH wrote:
> On Thu, Nov 11, 2021 at 11:40:02AM -0800, Srivatsa S. Bhat wrote:
> > On Thu, Nov 11, 2021 at 07:45:02PM +0100, Greg KH wrote:
> > > On Thu, Nov 11, 2021 at 07:39:16AM -0800, Srivatsa S. Bhat wrote:
> > > >
On Thu, Nov 11, 2021 at 07:45:02PM +0100, Greg KH wrote:
> On Thu, Nov 11, 2021 at 07:39:16AM -0800, Srivatsa S. Bhat wrote:
> > On Thu, Nov 11, 2021 at 07:50:39AM +0100, Greg KH wrote:
> > > On Wed, Nov 10, 2021 at 12:08:16PM -0800, Srivatsa S. Bhat wrote:
> > > >
On Thu, Nov 11, 2021 at 07:50:39AM +0100, Greg KH wrote:
> On Wed, Nov 10, 2021 at 12:08:16PM -0800, Srivatsa S. Bhat wrote:
> > From: Srivatsa S. Bhat (VMware)
> >
> > Deep has decided to transfer maintainership of the VMware hypervisor
> > interface to Srivatsa, a
From: Srivatsa S. Bhat (VMware)
VMware mailing lists in the MAINTAINERS file are private lists meant
for VMware-internal review/notification for patches to the respective
subsystems. Anyone can post to these addresses, but there is no public
read access like open mailing lists, which makes them
From: Srivatsa S. Bhat (VMware)
Zack Rusin will be taking over the maintainership of the VMware
vmmouse driver. Update the MAINTAINERS file to reflect this change.
Signed-off-by: Srivatsa S. Bhat (VMware)
Acked-by: Zack Rusin
Cc: linux-graphics-maintai...@vmware.com
Cc: pv-driv...@vmware.com
From: Srivatsa S. Bhat (VMware)
Deep has decided to transfer maintainership of the VMware hypervisor
interface to Srivatsa, and the joint-maintainership of paravirt ops in
the Linux kernel to Srivatsa and Alexey. Update the MAINTAINERS file
to reflect this change.
Signed-off-by: Srivatsa S
ver
- Use R: to denote email-aliases for VMware reviewers
Regards,
Srivatsa
---
Srivatsa S. Bhat (VMware) (3):
MAINTAINERS: Update maintainers for paravirt ops and VMware hypervisor
interface
MAINTAINERS: Add Zack as maintainer of vmmouse driver
MAINTAINERS: Mark VMware mailing l
On Wed, Nov 10, 2021 at 05:40:09PM +, Nadav Amit wrote:
>
>
> > On Nov 10, 2021, at 9:20 AM, Srivatsa S. Bhat
> > wrote:
> >
> > On Tue, Nov 09, 2021 at 01:57:31PM -0800, Joe Perches wrote:
> >> On Tue, 2021-11-09 at 00:58 +, Nadav Amit wrote:
On Tue, Nov 09, 2021 at 01:57:31PM -0800, Joe Perches wrote:
> On Tue, 2021-11-09 at 00:58 +, Nadav Amit wrote:
> > > On Nov 8, 2021, at 4:37 PM, Joe Perches wrote:
> > > On Mon, 2021-11-08 at 16:22 -0800, Srivatsa S. Bhat wrote:
> > >
> > > So it
+Greg, Thomas
Hi Joe,
On 11/8/21 3:37 PM, Joe Perches wrote:
> On Mon, 2021-11-08 at 12:30 -0800, Srivatsa S. Bhat wrote:
>> From: Srivatsa S. Bhat (VMware)
>>
>> VMware mailing lists in the MAINTAINERS file are private lists meant
>> for VMware-internal revi
From: Srivatsa S. Bhat (VMware)
VMware mailing lists in the MAINTAINERS file are private lists meant
for VMware-internal review/notification for patches to the respective
subsystems. So, in an earlier discussion [1][2], it was recommended to
mark them as such. Update all the remaining VMware
From: Srivatsa S. Bhat (VMware)
Deep has decided to transfer maintainership of the VMware hypervisor
interface to Srivatsa, and the joint-maintainership of paravirt ops in
the Linux kernel to Srivatsa and Alexey. Update the MAINTAINERS file
to reflect this change.
Signed-off-by: Srivatsa S
Hi Thomas,
On 11/4/21 1:11 PM, Thomas Gleixner wrote:
> Srivatsa,
>
> On Thu, Nov 04 2021 at 12:09, Srivatsa S. Bhat wrote:
>> On a related note, I'll be stepping in soon to assist (in place of
>> Deep) as a co-maintainer of the PARAVIRT_OPS interface. I had the same
>
Hi Juergen, Thomas,
On 11/4/21 2:18 AM, Thomas Gleixner wrote:
> On Thu, Nov 04 2021 at 10:17, Thomas Gleixner wrote:
>
> CC+ x86, peterz
>
>> Juergen,
>>
>> On Thu, Nov 04 2021 at 06:53, Juergen Gross wrote:
>>
>>> A recent patch modifying the core paravirt-ops functionality is
>>>
konrad.w...@oracle.com
Cc: Jeremy Fitzhardinge jer...@goop.org
Cc: Thomas Gleixner t...@linutronix.de
Cc: Ingo Molnar mi...@redhat.com
Cc: H. Peter Anvin h...@zytor.com
Cc: x...@kernel.org
Cc: xen-de...@lists.xensource.com
Cc: virtualization@lists.linux-foundation.org
Signed-off-by: Srivatsa S. Bhat
konrad.w...@oracle.com
Cc: Jeremy Fitzhardinge jer...@goop.org
Cc: Thomas Gleixner t...@linutronix.de
Cc: Ingo Molnar mi...@redhat.com
Cc: H. Peter Anvin h...@zytor.com
Cc: x...@kernel.org
Cc: xen-de...@lists.xensource.com
Cc: virtualization@lists.linux-foundation.org
Signed-off-by: Srivatsa S. Bhat
konrad.w...@oracle.com
Cc: Jeremy Fitzhardinge jer...@goop.org
Cc: Thomas Gleixner t...@linutronix.de
Cc: Ingo Molnar mi...@redhat.com
Cc: H. Peter Anvin h...@zytor.com
Cc: x...@kernel.org
Cc: xen-de...@lists.xensource.com
Cc: virtualization@lists.linux-foundation.org
Signed-off-by: Srivatsa S. Bhat
On 06/05/2012 10:19 PM, Konrad Rzeszutek Wilk wrote:
On Sat, Jun 02, 2012 at 11:36:00PM +0530, Srivatsa S. Bhat wrote:
On 06/01/2012 09:06 PM, Jan Beulich wrote:
On 01.06.12 at 17:13, Srivatsa S. Bhat
srivatsa.b...@linux.vnet.ibm.com
wrote:
On 06/01/2012 06:29 PM, Jan Beulich wrote
On 06/05/2012 11:10 PM, Thomas Gleixner wrote:
On Sat, 2 Jun 2012, Srivatsa S. Bhat wrote:
Ok.. So, I would love to hear a confirmation about whether this patch (which
removes cpu_bringup() in xen_play_dead()) will break things or it is good as
is.
If its not correct, then we can probably
On 06/01/2012 09:06 PM, Jan Beulich wrote:
On 01.06.12 at 17:13, Srivatsa S. Bhat srivatsa.b...@linux.vnet.ibm.com
wrote:
On 06/01/2012 06:29 PM, Jan Beulich wrote:
On 01.06.12 at 11:11, Srivatsa S. Bhat
srivatsa.b...@linux.vnet.ibm.com
wrote:
xen_play_dead calls cpu_bringup() which
...@goop.org
Cc: Thomas Gleixner t...@linutronix.de
Cc: Ingo Molnar mi...@redhat.com
Cc: H. Peter Anvin h...@zytor.com
Cc: x...@kernel.org
Cc: xen-de...@lists.xensource.com
Cc: virtualization@lists.linux-foundation.org
Signed-off-by: Srivatsa S. Bhat srivatsa.b...@linux.vnet.ibm.com
---
arch/x86/xen/smp.c
...@lists.xensource.com
Cc: virtualization@lists.linux-foundation.org
Cc: linux-ker...@vger.kernel.org
Signed-off-by: Srivatsa S. Bhat srivatsa.b...@linux.vnet.ibm.com
---
arch/x86/xen/smp.c | 21 -
1 files changed, 4 insertions(+), 17 deletions(-)
diff --git a/arch/x86/xen/smp.c b
Cc: linux-m...@linux-mips.org
Cc: linuxppc-...@lists.ozlabs.org
Cc: linux...@vger.kernel.org
Cc: xen-de...@lists.xensource.com
Cc: virtualization@lists.linux-foundation.org
Signed-off-by: Srivatsa S. Bhat srivatsa.b...@linux.vnet.ibm.com
---
arch/ia64/include/asm/cpu.h |2 --
arch/ia64/kernel
On 06/01/2012 06:29 PM, Jan Beulich wrote:
On 01.06.12 at 11:11, Srivatsa S. Bhat srivatsa.b...@linux.vnet.ibm.com
wrote:
xen_play_dead calls cpu_bringup() which looks weird, because xen_play_dead()
is invoked in the cpu down path, whereas cpu_bringup() (as the name
suggests) is useful
There is an extra and unnecessary call to smp_processor_id()
in cpu_bringup(). Remove it.
Signed-off-by: Srivatsa S. Bhat srivatsa.b...@linux.vnet.ibm.com
---
arch/x86/xen/smp.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/arch/x86/xen/smp.c b/arch/x86/xen/smp.c
53 matches
Mail list logo
