[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20231005115630.GL682044@nvidia.com>
Date: Thu, 5 Oct 2023 08:56:30 -0300
From: Jason Gunthorpe <jgg@...dia.com>
To: Lorenzo Pieralisi <lpieralisi@...nel.org>
Cc: Catalin Marinas <catalin.marinas@....com>, ankita@...dia.com,
maz@...nel.org, oliver.upton@...ux.dev, will@...nel.org,
aniketa@...dia.com, cjia@...dia.com, kwankhede@...dia.com,
targupta@...dia.com, vsethi@...dia.com, acurrid@...dia.com,
apopple@...dia.com, jhubbard@...dia.com, danw@...dia.com,
linux-arm-kernel@...ts.infradead.org, kvmarm@...ts.linux.dev,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v1 2/2] KVM: arm64: allow the VM to select DEVICE_* and
NORMAL_NC for IO memory
On Thu, Oct 05, 2023 at 11:56:55AM +0200, Lorenzo Pieralisi wrote:
> On Tue, Sep 26, 2023 at 02:52:13PM +0100, Catalin Marinas wrote:
>
> [...]
>
> > Anyway, the text looks fine to me. Thanks for putting it together
> > Lorenzo.
>
> Thanks !
>
> > One thing not mentioned here is that pci-vfio still maps such memory as
> > Device-nGnRnE in user space and relaxing this potentially creates an
> > alias. But such alias is only relevant of both the VMM and the VM try to
> > access the same device which I doubt is a realistic scenario.
>
> A revised log, FWIW:
What is the plan here, do you want Ankit to resend the series with
this text?
There were no comments on patch 1/2?
Thanks,
Jason
Powered by blists - more mailing lists