[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20201126162338.GV4327@casper.infradead.org>
Date: Thu, 26 Nov 2020 16:23:38 +0000
From: Matthew Wilcox <willy@...radead.org>
To: Marc Zyngier <maz@...nel.org>
Cc: David Brazdil <dbrazdil@...gle.com>, kvmarm@...ts.cs.columbia.edu,
Jonathan Corbet <corbet@....net>,
Catalin Marinas <catalin.marinas@....com>,
Will Deacon <will@...nel.org>,
James Morse <james.morse@....com>,
Julien Thierry <julien.thierry.kdev@...il.com>,
Suzuki K Poulose <suzuki.poulose@....com>,
Dennis Zhou <dennis@...nel.org>, Tejun Heo <tj@...nel.org>,
Christoph Lameter <cl@...ux.com>,
Mark Rutland <mark.rutland@....com>,
Lorenzo Pieralisi <lorenzo.pieralisi@....com>,
Sudeep Holla <sudeep.holla@....com>, linux-doc@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
kernel-team@...roid.com
Subject: Re: [PATCH v3 00/23] Opt-in always-on nVHE hypervisor
On Thu, Nov 26, 2020 at 04:19:55PM +0000, Marc Zyngier wrote:
> On 2020-11-26 15:57, Matthew Wilcox wrote:
> > On Thu, Nov 26, 2020 at 03:53:58PM +0000, David Brazdil wrote:
> > > The hypervisor starts trapping host SMCs and intercepting host's PSCI
> > > CPU_ON/SUSPEND calls. It replaces the host's entry point with its own,
> > > initializes the EL2 state of the new CPU and installs the nVHE hyp
> > > vector
> > > before ERETing to the host's entry point.
> >
> > I hate CPU people. This is complete gibberish to anyone who doesn't
> > already have their head deep in ... whatever you're talking about.
>
> What I hate the most is people having a go at other people because they
> don't understand what is being discussed. Who is at fault there?
The person who wrote an explanation that doesn't actually explain
anything? If you're sending mail to a bunch of mailing lists which
aren't already familiar with what you're trying to do, the onus is on
you to do more explanation.
Powered by blists - more mailing lists