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]

Date: Mon, 26 Feb 2024 23:45:30 +0000
From: Oliver Upton <oliver.upton@...ux.dev>
To: wangjinchao@...sion.com,
	shahuang@...hat.com,
	catalin.marinas@....com,
	ryan.roberts@....com,
	stefanha@...hat.com,
	yi.l.liu@...el.com,
	david@...hat.com,
	Jason Gunthorpe <jgg@...pe.ca>,
	lpieralisi@...nel.org,
	gshan@...hat.com,
	brauner@...nel.org,
	rananta@...gle.com,
	alex.williamson@...hat.com,
	suzuki.poulose@....com,
	kevin.tian@...el.com,
	surenb@...gle.com,
	ricarkol@...gle.com,
	linus.walleij@...aro.org,
	james.morse@....com,
	ankita@...dia.com,
	ardb@...nel.org,
	will@...nel.org,
	akpm@...ux-foundation.org,
	maz@...nel.org,
	bhe@...hat.com,
	reinette.chatre@...el.com,
	yuzenghui@...wei.com,
	andreyknvl@...il.com,
	linux-mm@...ck.org,
	mark.rutland@....com
Cc: Oliver Upton <oliver.upton@...ux.dev>,
	danw@...dia.com,
	acurrid@...dia.com,
	apopple@...dia.com,
	mochs@...dia.com,
	linux-kernel@...r.kernel.org,
	aniketa@...dia.com,
	cjia@...dia.com,
	kvm@...r.kernel.org,
	jhubbard@...dia.com,
	kvmarm@...ts.linux.dev,
	zhiw@...dia.com,
	kwankhede@...dia.com,
	vsethi@...dia.com,
	linux-arm-kernel@...ts.infradead.org,
	targupta@...dia.com
Subject: Re: [PATCH v9 0/4] KVM: arm64: Allow the VM to select DEVICE_* and NORMAL_NC for IO memory

On Sat, 24 Feb 2024 20:35:42 +0530, ankita@...dia.com wrote:
> From: Ankit Agrawal <ankita@...dia.com>
> 
> 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!

[1/4] KVM: arm64: Introduce new flag for non-cacheable IO memory
      https://git.kernel.org/kvmarm/kvmarm/c/c034ec84e879
[2/4] mm: Introduce new flag to indicate wc safe
      https://git.kernel.org/kvmarm/kvmarm/c/5c656fcdd6c6
[3/4] KVM: arm64: Set io memory s2 pte as normalnc for vfio pci device
      https://git.kernel.org/kvmarm/kvmarm/c/8c47ce3e1d2c
[4/4] vfio: Convey kvm that the vfio-pci device is wc safe
      https://git.kernel.org/kvmarm/kvmarm/c/a39d3a966a09

--
Best,
Oliver