From: Oliver Upton <oliver.upton@linux.dev>
To: wangjinchao@xfusion.com, shahuang@redhat.com,
catalin.marinas@arm.com, ryan.roberts@arm.com,
stefanha@redhat.com, yi.l.liu@intel.com, david@redhat.com,
Jason Gunthorpe <jgg@ziepe.ca>,
lpieralisi@kernel.org, gshan@redhat.com, brauner@kernel.org,
rananta@google.com, alex.williamson@redhat.com,
suzuki.poulose@arm.com, kevin.tian@intel.com, surenb@google.com,
ricarkol@google.com, linus.walleij@linaro.org,
james.morse@arm.com, ankita@nvidia.com, ardb@kernel.org,
will@kernel.org, akpm@linux-foundation.org, maz@kernel.org,
bhe@redhat.com, reinette.chatre@intel.com, yuzenghui@huawei.com,
andreyknvl@gmail.com, linux-mm@kvack.org, mark.rutland@arm.com
Cc: Oliver Upton <oliver.upton@linux.dev>,
danw@nvidia.com, acurrid@nvidia.com, apopple@nvidia.com,
mochs@nvidia.com, linux-kernel@vger.kernel.org,
aniketa@nvidia.com, cjia@nvidia.com, kvm@vger.kernel.org,
jhubbard@nvidia.com, kvmarm@lists.linux.dev, zhiw@nvidia.com,
kwankhede@nvidia.com, vsethi@nvidia.com,
linux-arm-kernel@lists.infradead.org, targupta@nvidia.com
Subject: Re: [PATCH v9 0/4] KVM: arm64: Allow the VM to select DEVICE_* and NORMAL_NC for IO memory
Date: Mon, 26 Feb 2024 23:45:30 +0000 [thread overview]
Message-ID: <170899100569.1405597.5047894183843333522.b4-ty@linux.dev> (raw)
In-Reply-To: <20240224150546.368-1-ankita@nvidia.com>
On Sat, 24 Feb 2024 20:35:42 +0530, ankita@nvidia.com wrote:
> From: Ankit Agrawal <ankita@nvidia.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
next prev parent reply other threads:[~2024-02-26 23:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-24 15:05 ankita
2024-02-24 15:05 ` [PATCH v9 1/4] KVM: arm64: Introduce new flag for non-cacheable " ankita
2024-02-24 15:05 ` [PATCH v9 2/4] mm: Introduce new flag to indicate wc safe ankita
2024-02-24 15:05 ` [PATCH v9 3/4] KVM: arm64: Set io memory s2 pte as normalnc for vfio pci device ankita
2024-02-24 15:05 ` [PATCH v9 4/4] vfio: Convey kvm that the vfio-pci device is wc safe ankita
2024-02-26 23:45 ` Oliver Upton [this message]
2024-02-27 8:45 ` [PATCH v9 0/4] KVM: arm64: Allow the VM to select DEVICE_* and NORMAL_NC for IO memory Ankit Agrawal
2024-02-27 8:49 ` Oliver Upton
2024-02-27 9:42 ` Ankit Agrawal
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=170899100569.1405597.5047894183843333522.b4-ty@linux.dev \
--to=oliver.upton@linux.dev \
--cc=acurrid@nvidia.com \
--cc=akpm@linux-foundation.org \
--cc=alex.williamson@redhat.com \
--cc=andreyknvl@gmail.com \
--cc=aniketa@nvidia.com \
--cc=ankita@nvidia.com \
--cc=apopple@nvidia.com \
--cc=ardb@kernel.org \
--cc=bhe@redhat.com \
--cc=brauner@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=cjia@nvidia.com \
--cc=danw@nvidia.com \
--cc=david@redhat.com \
--cc=gshan@redhat.com \
--cc=james.morse@arm.com \
--cc=jgg@ziepe.ca \
--cc=jhubbard@nvidia.com \
--cc=kevin.tian@intel.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.linux.dev \
--cc=kwankhede@nvidia.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lpieralisi@kernel.org \
--cc=mark.rutland@arm.com \
--cc=maz@kernel.org \
--cc=mochs@nvidia.com \
--cc=rananta@google.com \
--cc=reinette.chatre@intel.com \
--cc=ricarkol@google.com \
--cc=ryan.roberts@arm.com \
--cc=shahuang@redhat.com \
--cc=stefanha@redhat.com \
--cc=surenb@google.com \
--cc=suzuki.poulose@arm.com \
--cc=targupta@nvidia.com \
--cc=vsethi@nvidia.com \
--cc=wangjinchao@xfusion.com \
--cc=will@kernel.org \
--cc=yi.l.liu@intel.com \
--cc=yuzenghui@huawei.com \
--cc=zhiw@nvidia.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox