All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc Zyngier <maz@kernel.org>
To: Ankit Agrawal <ankita@nvidia.com>
Cc: David Hildenbrand <david@redhat.com>,
	Jason Gunthorpe <jgg@nvidia.com>,
	"alex.williamson@redhat.com" <alex.williamson@redhat.com>,
	"naoya.horiguchi@nec.com" <naoya.horiguchi@nec.com>,
	"oliver.upton@linux.dev" <oliver.upton@linux.dev>,
	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>,
	"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>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: [PATCH v3 0/6] Expose GPU memory as coherently CPU accessible
Date: Wed, 12 Apr 2023 10:48:54 +0100	[thread overview]
Message-ID: <86wn2hl9bt.wl-maz@kernel.org> (raw)
In-Reply-To: <BY5PR12MB3763086D7CD36B7B158FC426B09B9@BY5PR12MB3763.namprd12.prod.outlook.com>

On Wed, 12 Apr 2023 09:43:56 +0100,
Ankit Agrawal <ankita@nvidia.com> wrote:
> 
> Thanks David, response inline.
> 
> [...]
> 
> > I briefly skimmed over the series, the patch subject prefixes are a bit
> > misleading IMHO and could be improved:
> 
> Understood. Will fix that in the next iteration.
> 
> 
> >> Ankit Agrawal (6):
> >>    kvm: determine memory type from VMA
> 
> > this is arch64 specific kvm (kvm/aarch64: ?)
> Right. I'll change the prefix to kvm/aarch64

Please look at the git log: the idiomatic prefix is
"KVM: arm64: Something starting with a capital letter"

AArch64 is almost never used anywhere in the arm64 tree.

	M.

-- 
Without deviation from the norm, progress is not possible.

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

WARNING: multiple messages have this Message-ID (diff)
From: Marc Zyngier <maz@kernel.org>
To: Ankit Agrawal <ankita@nvidia.com>
Cc: David Hildenbrand <david@redhat.com>,
	Jason Gunthorpe <jgg@nvidia.com>,
	"alex.williamson@redhat.com" <alex.williamson@redhat.com>,
	"naoya.horiguchi@nec.com" <naoya.horiguchi@nec.com>,
	"oliver.upton@linux.dev" <oliver.upton@linux.dev>,
	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>,
	"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>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: [PATCH v3 0/6] Expose GPU memory as coherently CPU accessible
Date: Wed, 12 Apr 2023 10:48:54 +0100	[thread overview]
Message-ID: <86wn2hl9bt.wl-maz@kernel.org> (raw)
In-Reply-To: <BY5PR12MB3763086D7CD36B7B158FC426B09B9@BY5PR12MB3763.namprd12.prod.outlook.com>

On Wed, 12 Apr 2023 09:43:56 +0100,
Ankit Agrawal <ankita@nvidia.com> wrote:
> 
> Thanks David, response inline.
> 
> [...]
> 
> > I briefly skimmed over the series, the patch subject prefixes are a bit
> > misleading IMHO and could be improved:
> 
> Understood. Will fix that in the next iteration.
> 
> 
> >> Ankit Agrawal (6):
> >>    kvm: determine memory type from VMA
> 
> > this is arch64 specific kvm (kvm/aarch64: ?)
> Right. I'll change the prefix to kvm/aarch64

Please look at the git log: the idiomatic prefix is
"KVM: arm64: Something starting with a capital letter"

AArch64 is almost never used anywhere in the arm64 tree.

	M.

-- 
Without deviation from the norm, progress is not possible.

  reply	other threads:[~2023-04-12  9:49 UTC|newest]

Thread overview: 60+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-05 18:01 [PATCH v3 0/6] Expose GPU memory as coherently CPU accessible ankita
2023-04-05 18:01 ` ankita
2023-04-05 18:01 ` [PATCH v3 1/6] kvm: determine memory type from VMA ankita
2023-04-05 18:01   ` ankita
2023-04-12 12:43   ` Marc Zyngier
2023-04-12 12:43     ` Marc Zyngier
2023-04-12 13:01     ` Jason Gunthorpe
2023-04-12 13:01       ` Jason Gunthorpe
2023-05-31 11:35       ` Catalin Marinas
2023-05-31 11:35         ` Catalin Marinas
2023-06-14 12:44         ` Jason Gunthorpe
2023-06-14 12:44           ` Jason Gunthorpe
2023-07-14  8:10         ` Benjamin Herrenschmidt
2023-07-14  8:10           ` Benjamin Herrenschmidt
2023-07-16 15:09           ` Catalin Marinas
2023-07-16 15:09             ` Catalin Marinas
2023-07-16 22:30             ` Jason Gunthorpe
2023-07-16 22:30               ` Jason Gunthorpe
2023-07-17 18:35               ` Alex Williamson
2023-07-17 18:35                 ` Alex Williamson
2023-07-25  6:18                 ` Benjamin Herrenschmidt
2023-04-05 18:01 ` [PATCH v3 2/6] vfio/nvgpu: expose GPU device memory as BAR1 ankita
2023-04-05 18:01   ` ankita
2023-04-05 21:07   ` kernel test robot
2023-04-05 21:07     ` kernel test robot
2023-04-05 18:01 ` [PATCH v3 3/6] mm: handle poisoning of pfn without struct pages ankita
2023-04-05 18:01   ` ankita
2023-04-05 21:07   ` kernel test robot
2023-04-05 21:07     ` kernel test robot
2023-05-09  9:51   ` HORIGUCHI NAOYA(堀口　直也)
2023-05-15 11:18     ` Ankit Agrawal
2023-05-15 11:18       ` Ankit Agrawal
2023-05-23  5:43       ` HORIGUCHI NAOYA(堀口　直也)
2023-05-23  5:43         ` HORIGUCHI NAOYA(堀口　直也)
2023-04-05 18:01 ` [PATCH v3 4/6] mm: Add poison error check in fixup_user_fault() for mapped PFN ankita
2023-04-05 18:01   ` ankita
2023-04-05 18:01 ` [PATCH v3 5/6] mm: Change ghes code to allow poison of non-struct PFN ankita
2023-04-05 18:01   ` ankita
2023-04-05 18:01 ` [PATCH v3 6/6] vfio/nvgpu: register device memory for poison handling ankita
2023-04-05 18:01   ` ankita
2023-04-05 20:24   ` Zhi Wang
2023-04-05 20:24     ` Zhi Wang
2023-04-05 21:50   ` kernel test robot
2023-04-05 21:50     ` kernel test robot
2023-05-24  9:53   ` Dan Carpenter
2023-05-24  9:53     ` Dan Carpenter
2023-04-06 12:07 ` [PATCH v3 0/6] Expose GPU memory as coherently CPU accessible David Hildenbrand
2023-04-06 12:07   ` David Hildenbrand
2023-04-12  8:43   ` Ankit Agrawal
2023-04-12  8:43     ` Ankit Agrawal
2023-04-12  9:48     ` Marc Zyngier [this message]
2023-04-12  9:48       ` Marc Zyngier
2023-04-12 12:28 ` Marc Zyngier
2023-04-12 12:28   ` Marc Zyngier
2023-04-12 12:53   ` Jason Gunthorpe
2023-04-12 12:53     ` Jason Gunthorpe
2023-04-13  9:52     ` Marc Zyngier
2023-04-13  9:52       ` Marc Zyngier
2023-04-13 13:19       ` Jason Gunthorpe
2023-04-13 13:19         ` Jason Gunthorpe

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=86wn2hl9bt.wl-maz@kernel.org \
    --to=maz@kernel.org \
    --cc=acurrid@nvidia.com \
    --cc=alex.williamson@redhat.com \
    --cc=aniketa@nvidia.com \
    --cc=ankita@nvidia.com \
    --cc=apopple@nvidia.com \
    --cc=cjia@nvidia.com \
    --cc=danw@nvidia.com \
    --cc=david@redhat.com \
    --cc=jgg@nvidia.com \
    --cc=jhubbard@nvidia.com \
    --cc=kvm@vger.kernel.org \
    --cc=kwankhede@nvidia.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=naoya.horiguchi@nec.com \
    --cc=oliver.upton@linux.dev \
    --cc=targupta@nvidia.com \
    --cc=vsethi@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.