[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID:
<SA1PR12MB7199C7BD48EB39F536DD34DBB0A62@SA1PR12MB7199.namprd12.prod.outlook.com>
Date: Wed, 26 Mar 2025 08:31:32 +0000
From: Ankit Agrawal <ankita@...dia.com>
To: Catalin Marinas <catalin.marinas@....com>, Jason Gunthorpe
<jgg@...dia.com>
CC: Oliver Upton <oliver.upton@...ux.dev>, Marc Zyngier <maz@...nel.org>,
"joey.gouly@....com" <joey.gouly@....com>, "suzuki.poulose@....com"
<suzuki.poulose@....com>, "yuzenghui@...wei.com" <yuzenghui@...wei.com>,
"will@...nel.org" <will@...nel.org>, "ryan.roberts@....com"
<ryan.roberts@....com>, "shahuang@...hat.com" <shahuang@...hat.com>,
"lpieralisi@...nel.org" <lpieralisi@...nel.org>, "david@...hat.com"
<david@...hat.com>, Aniket Agashe <aniketa@...dia.com>, Neo Jia
<cjia@...dia.com>, Kirti Wankhede <kwankhede@...dia.com>, "Tarun Gupta
(SW-GPU)" <targupta@...dia.com>, Vikram Sethi <vsethi@...dia.com>, Andy
Currid <acurrid@...dia.com>, Alistair Popple <apopple@...dia.com>, John
Hubbard <jhubbard@...dia.com>, Dan Williams <danw@...dia.com>, Zhi Wang
<zhiw@...dia.com>, Matt Ochs <mochs@...dia.com>, Uday Dhoke
<udhoke@...dia.com>, Dheeraj Nigam <dnigam@...dia.com>, Krishnakant Jaju
<kjaju@...dia.com>, "alex.williamson@...hat.com"
<alex.williamson@...hat.com>, "sebastianene@...gle.com"
<sebastianene@...gle.com>, "coltonlewis@...gle.com" <coltonlewis@...gle.com>,
"kevin.tian@...el.com" <kevin.tian@...el.com>, "yi.l.liu@...el.com"
<yi.l.liu@...el.com>, "ardb@...nel.org" <ardb@...nel.org>,
"akpm@...ux-foundation.org" <akpm@...ux-foundation.org>, "gshan@...hat.com"
<gshan@...hat.com>, "linux-mm@...ck.org" <linux-mm@...ck.org>,
"ddutile@...hat.com" <ddutile@...hat.com>, "tabba@...gle.com"
<tabba@...gle.com>, "qperret@...gle.com" <qperret@...gle.com>,
"seanjc@...gle.com" <seanjc@...gle.com>, "kvmarm@...ts.linux.dev"
<kvmarm@...ts.linux.dev>, "linux-kernel@...r.kernel.org"
<linux-kernel@...r.kernel.org>, "linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH v3 1/1] KVM: arm64: Allow cacheable stage 2 mapping using
VMA flags
> On Wed, Mar 19, 2025 at 04:22:46PM -0300, Jason Gunthorpe wrote:
> > On Wed, Mar 19, 2025 at 06:11:02PM +0000, Catalin Marinas wrote:
> > > On Wed, Mar 19, 2025 at 02:04:29PM -0300, Jason Gunthorpe wrote:
> > > > On Wed, Mar 19, 2025 at 12:01:29AM -0700, Oliver Upton wrote:
> > > > > You have a very good point that KVM is broken for cacheable PFNMAP'd
> > > > > crap since we demote to something non-cacheable, and maybe that
> > > > > deserves fixing first. Hopefully nobody notices that we've taken away
> > > > > the toys...
> > > >
> > > > Fixing it is either faulting all access attempts or mapping it
> > > > cachable to the S2 (as this series is trying to do)..
> > >
> > > As I replied earlier, it might be worth doing both - fault on !FWB
> > > hardware (or rather reject the memslot creation), cacheable S2
> > > otherwise.
> >
> > I have no objection, Ankit are you able to make a failure patch?
>
> I'd wait until the KVM maintainers have their say.
>
Maz, Oliver any thoughts on this? Can we conclude to create this failure
patch in memslot creation?
> --
> Catalin
Powered by blists - more mailing lists