All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc Zyngier <maz@kernel.org>
To: Ganapatrao Kulkarni <gankulkarni@os.amperecomputing.com>
Cc: Oliver Upton <oliver.upton@linux.dev>,
	kvmarm@lists.linux.dev, kvm@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, darren@os.amperecomputing.com,
	d.scott.phillips@amperecomputing.com,
	James Morse <james.morse@arm.com>,
	Suzuki K Poulose <suzuki.poulose@arm.com>,
	Zenghui Yu <yuzenghui@huawei.com>
Subject: Re: [RFC PATCH] kvm: nv: Optimize the unmapping of shadow S2-MMU tables.
Date: Wed, 06 Mar 2024 13:33:34 +0000	[thread overview]
Message-ID: <86plw71o41.wl-maz@kernel.org> (raw)
In-Reply-To: <8e2ee8dd-4412-4133-8b08-75d64ab79649@os.amperecomputing.com>

On Wed, 06 Mar 2024 05:31:09 +0000,
Ganapatrao Kulkarni <gankulkarni@os.amperecomputing.com> wrote:
> 
> 
> 
> On 05-03-2024 02:16 pm, Oliver Upton wrote:
> > -cc old kvmarm list
> > +cc new kvmarm list, reviewers
> > 
> > Please run scripts/get_maintainer.pl next time around so we get the
> > right people looking at a patch.
> > 
> 
> Of course I know this script -:)
> I didn't cc since I felt to avoid unnecessary overloading someone's
> inbox. I don't think anyone(even ARM) is interested in this feature
> other than Marc and me/Ampere. Otherwise this would have merged
> upstream by now.

You're wrong on a lot of this. There is quite a significant interest,
actually. But in the fine corporate tradition, not even my employer
can be bothered to actively contribute. These people are waiting for
things to land. I'm happy to make them wait even longer (I'm paying
for my own HW, so I don't owe anyone anything).

The architecture also wasn't in a good enough state for the support to
be merged until very recently, and it still is broken in a lot of
respects.

> BTW, NV feature development started way back in 2016/17.

And? Cc'ing individuals and lists is basic courtesy, I'm afraid.
Please don't leave people in the dark.

Thanks,

	M.

-- 
Without deviation from the norm, progress is not possible.

WARNING: multiple messages have this Message-ID (diff)
From: Marc Zyngier <maz@kernel.org>
To: Ganapatrao Kulkarni <gankulkarni@os.amperecomputing.com>
Cc: Oliver Upton <oliver.upton@linux.dev>,
	kvmarm@lists.linux.dev, kvm@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, darren@os.amperecomputing.com,
	d.scott.phillips@amperecomputing.com,
	James Morse <james.morse@arm.com>,
	Suzuki K Poulose <suzuki.poulose@arm.com>,
	Zenghui Yu <yuzenghui@huawei.com>
Subject: Re: [RFC PATCH] kvm: nv: Optimize the unmapping of shadow S2-MMU tables.
Date: Wed, 06 Mar 2024 13:33:34 +0000	[thread overview]
Message-ID: <86plw71o41.wl-maz@kernel.org> (raw)
In-Reply-To: <8e2ee8dd-4412-4133-8b08-75d64ab79649@os.amperecomputing.com>

On Wed, 06 Mar 2024 05:31:09 +0000,
Ganapatrao Kulkarni <gankulkarni@os.amperecomputing.com> wrote:
> 
> 
> 
> On 05-03-2024 02:16 pm, Oliver Upton wrote:
> > -cc old kvmarm list
> > +cc new kvmarm list, reviewers
> > 
> > Please run scripts/get_maintainer.pl next time around so we get the
> > right people looking at a patch.
> > 
> 
> Of course I know this script -:)
> I didn't cc since I felt to avoid unnecessary overloading someone's
> inbox. I don't think anyone(even ARM) is interested in this feature
> other than Marc and me/Ampere. Otherwise this would have merged
> upstream by now.

You're wrong on a lot of this. There is quite a significant interest,
actually. But in the fine corporate tradition, not even my employer
can be bothered to actively contribute. These people are waiting for
things to land. I'm happy to make them wait even longer (I'm paying
for my own HW, so I don't owe anyone anything).

The architecture also wasn't in a good enough state for the support to
be merged until very recently, and it still is broken in a lot of
respects.

> BTW, NV feature development started way back in 2016/17.

And? Cc'ing individuals and lists is basic courtesy, I'm afraid.
Please don't leave people in the dark.

Thanks,

	M.

-- 
Without deviation from the norm, progress is not possible.

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2024-03-06 13:33 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-05  5:46 [RFC PATCH] kvm: nv: Optimize the unmapping of shadow S2-MMU tables Ganapatrao Kulkarni
2024-03-05  5:46 ` Ganapatrao Kulkarni
2024-03-05  8:46 ` Oliver Upton
2024-03-05  8:46   ` Oliver Upton
2024-03-06  5:31   ` Ganapatrao Kulkarni
2024-03-06  5:31     ` Ganapatrao Kulkarni
2024-03-06  8:39     ` Oliver Upton
2024-03-06  8:39       ` Oliver Upton
2024-03-06 13:33     ` Marc Zyngier [this message]
2024-03-06 13:33       ` Marc Zyngier
2024-03-06 14:57       ` Ganapatrao Kulkarni
2024-03-06 14:57         ` Ganapatrao Kulkarni
2024-03-05 11:08 ` Marc Zyngier
2024-03-05 11:08   ` Marc Zyngier
2024-03-05 11:13 ` Marc Zyngier
2024-03-05 11:13   ` Marc Zyngier
2024-03-05 13:29   ` Ganapatrao Kulkarni
2024-03-05 13:29     ` Ganapatrao Kulkarni
2024-03-05 15:03     ` Marc Zyngier
2024-03-05 15:03       ` Marc Zyngier
2024-03-05 18:33       ` Ganapatrao Kulkarni
2024-03-05 18:33         ` Ganapatrao Kulkarni
2024-03-06 10:23         ` Marc Zyngier
2024-03-06 10:23           ` Marc Zyngier
2024-03-26 11:33       ` Ganapatrao Kulkarni
2024-03-26 11:33         ` Ganapatrao Kulkarni
2024-03-27 12:12         ` Marc Zyngier
2024-03-27 12:12           ` Marc Zyngier

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=86plw71o41.wl-maz@kernel.org \
    --to=maz@kernel.org \
    --cc=d.scott.phillips@amperecomputing.com \
    --cc=darren@os.amperecomputing.com \
    --cc=gankulkarni@os.amperecomputing.com \
    --cc=james.morse@arm.com \
    --cc=kvm@vger.kernel.org \
    --cc=kvmarm@lists.linux.dev \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oliver.upton@linux.dev \
    --cc=suzuki.poulose@arm.com \
    --cc=yuzenghui@huawei.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.