From: Ankit Agrawal <ankita@nvidia.com>
To: Jason Gunthorpe <jgg@nvidia.com>,
Alex Williamson <alex.williamson@redhat.com>
Cc: "maz@kernel.org" <maz@kernel.org>,
"oliver.upton@linux.dev" <oliver.upton@linux.dev>,
"james.morse@arm.com" <james.morse@arm.com>,
"suzuki.poulose@arm.com" <suzuki.poulose@arm.com>,
"yuzenghui@huawei.com" <yuzenghui@huawei.com>,
"reinette.chatre@intel.com" <reinette.chatre@intel.com>,
"surenb@google.com" <surenb@google.com>,
"stefanha@redhat.com" <stefanha@redhat.com>,
"brauner@kernel.org" <brauner@kernel.org>,
"catalin.marinas@arm.com" <catalin.marinas@arm.com>,
"will@kernel.org" <will@kernel.org>,
"mark.rutland@arm.com" <mark.rutland@arm.com>,
"kevin.tian@intel.com" <kevin.tian@intel.com>,
"yi.l.liu@intel.com" <yi.l.liu@intel.com>,
"ardb@kernel.org" <ardb@kernel.org>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"andreyknvl@gmail.com" <andreyknvl@gmail.com>,
"wangjinchao@xfusion.com" <wangjinchao@xfusion.com>,
"gshan@redhat.com" <gshan@redhat.com>,
"ricarkol@google.com" <ricarkol@google.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"lpieralisi@kernel.org" <lpieralisi@kernel.org>,
"rananta@google.com" <rananta@google.com>,
"ryan.roberts@arm.com" <ryan.roberts@arm.com>,
Aniket Agashe <aniketa@nvidia.com>, Neo Jia <cjia@nvidia.com>,
Kirti Wankhede <kwankhede@nvidia.com>,
"Tarun Gupta (SW-GPU)" <targupta@nvidia.com>,
Vikram Sethi <vsethi@nvidia.com>,
Andy Currid <acurrid@nvidia.com>,
Alistair Popple <apopple@nvidia.com>,
John Hubbard <jhubbard@nvidia.com>,
Dan Williams <danw@nvidia.com>,
"kvmarm@lists.linux.dev" <kvmarm@lists.linux.dev>,
Matt Ochs <mochs@nvidia.com>, Zhi Wang <zhiw@nvidia.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v6 4/4] vfio: convey kvm that the vfio-pci device is wc safe
Date: Fri, 9 Feb 2024 14:02:26 +0000 [thread overview]
Message-ID: <MW4PR12MB7213C81E5CD611CF3AFCB0A9B04B2@MW4PR12MB7213.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20240208175437.GN10476@nvidia.com>
> The comment above this is justifying the flags as equivalent to those
> set by the remap_pfn_range() path. That's no longer the case and the
> additional flag needs to be described there.
Ack.
>> the comment where the bit is defined and we could use a name like
>> VM_ALLOW_ANY_UNCACHED or VM_IO_ANY. Thanks,
>
> I'd pick VM_ALLOW_ANY_UNCACHED of those two
If there is consensus on this name, I'll make the change
s/VM_VFIO_ALLOW_WC/VM_ALLOW_ANY_UNCACHED.
WARNING: multiple messages have this Message-ID (diff)
From: Ankit Agrawal <ankita@nvidia.com>
To: Jason Gunthorpe <jgg@nvidia.com>,
Alex Williamson <alex.williamson@redhat.com>
Cc: "maz@kernel.org" <maz@kernel.org>,
"oliver.upton@linux.dev" <oliver.upton@linux.dev>,
"james.morse@arm.com" <james.morse@arm.com>,
"suzuki.poulose@arm.com" <suzuki.poulose@arm.com>,
"yuzenghui@huawei.com" <yuzenghui@huawei.com>,
"reinette.chatre@intel.com" <reinette.chatre@intel.com>,
"surenb@google.com" <surenb@google.com>,
"stefanha@redhat.com" <stefanha@redhat.com>,
"brauner@kernel.org" <brauner@kernel.org>,
"catalin.marinas@arm.com" <catalin.marinas@arm.com>,
"will@kernel.org" <will@kernel.org>,
"mark.rutland@arm.com" <mark.rutland@arm.com>,
"kevin.tian@intel.com" <kevin.tian@intel.com>,
"yi.l.liu@intel.com" <yi.l.liu@intel.com>,
"ardb@kernel.org" <ardb@kernel.org>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"andreyknvl@gmail.com" <andreyknvl@gmail.com>,
"wangjinchao@xfusion.com" <wangjinchao@xfusion.com>,
"gshan@redhat.com" <gshan@redhat.com>,
"ricarkol@google.com" <ricarkol@google.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"lpieralisi@kernel.org" <lpieralisi@kernel.org>,
"rananta@google.com" <rananta@google.com>,
"ryan.roberts@arm.com" <ryan.roberts@arm.com>,
Aniket Agashe <aniketa@nvidia.com>, Neo Jia <cjia@nvidia.com>,
Kirti Wankhede <kwankhede@nvidia.com>,
"Tarun Gupta (SW-GPU)" <targupta@nvidia.com>,
Vikram Sethi <vsethi@nvidia.com>,
Andy Currid <acurrid@nvidia.com>,
Alistair Popple <apopple@nvidia.com>,
John Hubbard <jhubbard@nvidia.com>,
Dan Williams <danw@nvidia.com>,
"kvmarm@lists.linux.dev" <kvmarm@lists.linux.dev>,
Matt Ochs <mochs@nvidia.com>, Zhi Wang <zhiw@nvidia.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v6 4/4] vfio: convey kvm that the vfio-pci device is wc safe
Date: Fri, 9 Feb 2024 14:02:26 +0000 [thread overview]
Message-ID: <MW4PR12MB7213C81E5CD611CF3AFCB0A9B04B2@MW4PR12MB7213.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20240208175437.GN10476@nvidia.com>
> The comment above this is justifying the flags as equivalent to those
> set by the remap_pfn_range() path. That's no longer the case and the
> additional flag needs to be described there.
Ack.
>> the comment where the bit is defined and we could use a name like
>> VM_ALLOW_ANY_UNCACHED or VM_IO_ANY. Thanks,
>
> I'd pick VM_ALLOW_ANY_UNCACHED of those two
If there is consensus on this name, I'll make the change
s/VM_VFIO_ALLOW_WC/VM_ALLOW_ANY_UNCACHED.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2024-02-09 14:02 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-07 20:46 [PATCH v6 0/4] kvm: arm64: allow the VM to select DEVICE_* and NORMAL_NC for IO memory ankita
2024-02-07 20:46 ` ankita
2024-02-07 20:46 ` [PATCH v6 1/4] kvm: arm64: introduce new flag for non-cacheable " ankita
2024-02-07 20:46 ` ankita
2024-02-08 13:00 ` Catalin Marinas
2024-02-08 13:00 ` Catalin Marinas
2024-02-08 13:24 ` Oliver Upton
2024-02-08 13:24 ` Oliver Upton
2024-02-09 14:10 ` Ankit Agrawal
2024-02-09 14:10 ` Ankit Agrawal
2024-02-08 13:19 ` Will Deacon
2024-02-08 13:19 ` Will Deacon
2024-02-09 14:12 ` Ankit Agrawal
2024-02-09 14:12 ` Ankit Agrawal
2024-02-07 20:46 ` [PATCH v6 2/4] mm: introduce new flag to indicate wc safe ankita
2024-02-07 20:46 ` ankita
2024-02-08 13:03 ` Catalin Marinas
2024-02-08 13:03 ` Catalin Marinas
2024-02-08 14:34 ` Jason Gunthorpe
2024-02-08 14:34 ` Jason Gunthorpe
2024-02-07 20:46 ` [PATCH v6 3/4] kvm: arm64: set io memory s2 pte as normalnc for vfio pci device ankita
2024-02-07 20:46 ` ankita
2024-02-08 13:26 ` Oliver Upton
2024-02-08 13:26 ` Oliver Upton
2024-02-08 14:51 ` Catalin Marinas
2024-02-08 14:51 ` Catalin Marinas
2024-02-09 14:05 ` Ankit Agrawal
2024-02-09 14:05 ` Ankit Agrawal
2024-02-07 20:46 ` [PATCH v6 4/4] vfio: convey kvm that the vfio-pci device is wc safe ankita
2024-02-07 20:46 ` ankita
2024-02-08 14:53 ` Catalin Marinas
2024-02-08 14:53 ` Catalin Marinas
2024-02-08 17:30 ` Alex Williamson
2024-02-08 17:30 ` Alex Williamson
2024-02-08 17:54 ` Jason Gunthorpe
2024-02-08 17:54 ` Jason Gunthorpe
2024-02-09 14:02 ` Ankit Agrawal [this message]
2024-02-09 14:02 ` 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=MW4PR12MB7213C81E5CD611CF3AFCB0A9B04B2@MW4PR12MB7213.namprd12.prod.outlook.com \
--to=ankita@nvidia.com \
--cc=acurrid@nvidia.com \
--cc=akpm@linux-foundation.org \
--cc=alex.williamson@redhat.com \
--cc=andreyknvl@gmail.com \
--cc=aniketa@nvidia.com \
--cc=apopple@nvidia.com \
--cc=ardb@kernel.org \
--cc=brauner@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=cjia@nvidia.com \
--cc=danw@nvidia.com \
--cc=gshan@redhat.com \
--cc=james.morse@arm.com \
--cc=jgg@nvidia.com \
--cc=jhubbard@nvidia.com \
--cc=kevin.tian@intel.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.linux.dev \
--cc=kwankhede@nvidia.com \
--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=oliver.upton@linux.dev \
--cc=rananta@google.com \
--cc=reinette.chatre@intel.com \
--cc=ricarkol@google.com \
--cc=ryan.roberts@arm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.