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
