linux-kernel - Re: [PATCH v9 0/4] KVM: arm64: Allow the VM to select DEVICE_* and NORMAL

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <Zd2iCg5A0Zg_EyCm@linux.dev>
Date: Tue, 27 Feb 2024 08:49:14 +0000
From: Oliver Upton <oliver.upton@...ux.dev>
To: Ankit Agrawal <ankita@...dia.com>
Cc: "wangjinchao@...sion.com" <wangjinchao@...sion.com>,
	"shahuang@...hat.com" <shahuang@...hat.com>,
	"catalin.marinas@....com" <catalin.marinas@....com>,
	"ryan.roberts@....com" <ryan.roberts@....com>,
	"stefanha@...hat.com" <stefanha@...hat.com>,
	"yi.l.liu@...el.com" <yi.l.liu@...el.com>,
	"david@...hat.com" <david@...hat.com>,
	Jason Gunthorpe <jgg@...pe.ca>,
	"lpieralisi@...nel.org" <lpieralisi@...nel.org>,
	"gshan@...hat.com" <gshan@...hat.com>,
	"brauner@...nel.org" <brauner@...nel.org>,
	"rananta@...gle.com" <rananta@...gle.com>,
	"alex.williamson@...hat.com" <alex.williamson@...hat.com>,
	"suzuki.poulose@....com" <suzuki.poulose@....com>,
	"kevin.tian@...el.com" <kevin.tian@...el.com>,
	"surenb@...gle.com" <surenb@...gle.com>,
	"ricarkol@...gle.com" <ricarkol@...gle.com>,
	"linus.walleij@...aro.org" <linus.walleij@...aro.org>,
	"james.morse@....com" <james.morse@....com>,
	"ardb@...nel.org" <ardb@...nel.org>,
	"will@...nel.org" <will@...nel.org>,
	"akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
	"maz@...nel.org" <maz@...nel.org>,
	"bhe@...hat.com" <bhe@...hat.com>,
	"reinette.chatre@...el.com" <reinette.chatre@...el.com>,
	"yuzenghui@...wei.com" <yuzenghui@...wei.com>,
	"andreyknvl@...il.com" <andreyknvl@...il.com>,
	"linux-mm@...ck.org" <linux-mm@...ck.org>,
	"mark.rutland@....com" <mark.rutland@....com>,
	Dan Williams <danw@...dia.com>, Andy Currid <acurrid@...dia.com>,
	Alistair Popple <apopple@...dia.com>, Matt Ochs <mochs@...dia.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Aniket Agashe <aniketa@...dia.com>, Neo Jia <cjia@...dia.com>,
	"kvm@...r.kernel.org" <kvm@...r.kernel.org>,
	John Hubbard <jhubbard@...dia.com>,
	"kvmarm@...ts.linux.dev" <kvmarm@...ts.linux.dev>,
	Zhi Wang <zhiw@...dia.com>, Kirti Wankhede <kwankhede@...dia.com>,
	Vikram Sethi <vsethi@...dia.com>,
	"linux-arm-kernel@...ts.infradead.org" <linux-arm-kernel@...ts.infradead.org>,
	"Tarun Gupta (SW-GPU)" <targupta@...dia.com>
Subject: Re: [PATCH v9 0/4] KVM: arm64: Allow the VM to select DEVICE_* and
 NORMAL_NC for IO memory

On Tue, Feb 27, 2024 at 08:45:38AM +0000, Ankit Agrawal wrote:
> >>
> >> Currently, KVM for ARM64 maps at stage 2 memory that is considered device
> >> with DEVICE_nGnRE memory attributes; this setting overrides (per
> >> ARM architecture [1]) any device MMIO mapping present at stage 1,
> >> resulting in a set-up whereby a guest operating system cannot
> >> determine device MMIO mapping memory attributes on its own but
> >> it is always overridden by the KVM stage 2 default.
> >>
> >> [...]
> >
> > High time to get this cooking in -next. Looks like there aren't any
> > conflicts w/ VFIO, but if that changes I've pushed a topic branch to:
> >
> >  https://git.kernel.org/pub/scm/linux/kernel/git/oupton/linux.git/log/?h=kvm-arm64/vfio-normal-nc
> >
> > Applied to kvmarm/next, thanks!
> 
> Thanks Oliver for your efforts. Pardon my naivety, but what would the
> sequence of steps that this series go through next before landing in an
> rc branch? Also, what is the earliest branch this is supposed to land
> assuming all goes well?

We should see this showing up in linux-next imminently. Assuming there
are no issues there, your changes will be sent out as part of the kvmarm
pull request for 6.9.

At least in kvmarm, /next is used for patches that'll land in the next
merge window and /fixes is for bugfixes that need to go in the current
release cycle.

-- 
Thanks,
Oliver