From: Sairaj Kodilkar <sarunkod@amd.com>
To: Jason Gunthorpe <jgg@nvidia.com>
Cc: Vasant Hegde <vasant.hegde@amd.com>, <iommu@lists.linux.dev>,
<linux-kernel@vger.kernel.org>, <joro@8bytes.org>,
<suravee.suthikulpanit@amd.com>, <ashish.kalra@amd.com>,
<robin.murphy@arm.com>, <will@kernel.org>
Subject: Re: [PATCH 1/2] amd/iommu: Preserve domain ids inside the kdump kernel
Date: Fri, 21 Nov 2025 10:51:55 +0530 [thread overview]
Message-ID: <66a032df-d54f-471a-8219-5f41c2298b5f@amd.com> (raw)
In-Reply-To: <20251120125634.GA153257@nvidia.com>
On 11/20/2025 6:26 PM, Jason Gunthorpe wrote:
> On Thu, Nov 20, 2025 at 10:32:32AM +0530, Sairaj Kodilkar wrote:
>
>> No, its not atomic context. My intension was to ensure that the
>> memory allocation succeeds. But I am not sure if it's the most
>> appropriate choice for this scenario
> This is early boot, it won't fail either way. Use GFP_KERNEL because
> it is clearer
Sure, Thanks for suggestion
-Sairaj
next prev parent reply other threads:[~2025-11-21 5:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-14 10:44 [PATCH 0/2] " Sairaj Kodilkar
2025-11-14 10:44 ` [PATCH 1/2] " Sairaj Kodilkar
2025-11-17 5:21 ` Ankit Soni
2025-11-19 10:50 ` Vasant Hegde
2025-11-19 13:43 ` Jason Gunthorpe
2025-11-20 5:02 ` Sairaj Kodilkar
2025-11-20 12:56 ` Jason Gunthorpe
2025-11-21 5:21 ` Sairaj Kodilkar [this message]
2025-11-20 6:22 ` Vasant Hegde
2025-11-20 6:56 ` Vasant Hegde
2025-11-14 10:44 ` [PATCH 2/2] amd/iommu: Make protection domain ID functions non-static Sairaj Kodilkar
2025-11-19 10:47 ` Vasant Hegde
2025-11-19 13:47 ` 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=66a032df-d54f-471a-8219-5f41c2298b5f@amd.com \
--to=sarunkod@amd.com \
--cc=ashish.kalra@amd.com \
--cc=iommu@lists.linux.dev \
--cc=jgg@nvidia.com \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robin.murphy@arm.com \
--cc=suravee.suthikulpanit@amd.com \
--cc=vasant.hegde@amd.com \
--cc=will@kernel.org \
/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
all inboxes | Powered by JetHome®