From: Douglas Freimuth <freimuth@linux.ibm.com>
To: Christian Borntraeger <borntraeger@linux.ibm.com>,
imbrenda@linux.ibm.com, frankja@linux.ibm.com, david@kernel.org,
hca@linux.ibm.com, gor@linux.ibm.com, agordeev@linux.ibm.com,
svens@linux.ibm.com, kvm@vger.kernel.org,
linux-s390@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: mjrosato@linux.ibm.com
Subject: Re: [PATCH v2 1/3] KVM: s390: Add map/unmap ioctl and clean mappings post-guest
Date: Fri, 27 Mar 2026 11:22:03 -0400 [thread overview]
Message-ID: <fd8f5702-8118-4db5-b3be-d68a79fef0de@linux.ibm.com> (raw)
In-Reply-To: <1948daf3-9e5e-471b-94fc-c0aed00b4c09@linux.ibm.com>
On 3/26/26 7:46 AM, Christian Borntraeger wrote:
> Am 26.03.26 um 02:42 schrieb Douglas Freimuth:
>> +static int kvm_s390_adapter_map(struct kvm *kvm, unsigned int id,
>> __u64 addr)
>> +{
>> + struct s390_io_adapter *adapter = get_io_adapter(kvm, id);
>> + struct s390_map_info *map;
>> + unsigned long flags;
>> + int ret;
>> +
>> + if (!adapter || !addr)
>> + return -EINVAL;
>> +
>> + map = kzalloc_obj(*map, GFP_KERNEL);
>
> GFP_KERNEL_ACCOUNT certainly makes sense. Depending on other feedback
> can be
> added when applying.
>
>
I will make that change.
next prev parent reply other threads:[~2026-03-27 15:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-26 1:42 [PATCH v2 0/3] KVM: s390: Introducing kvm_arch_set_irq_inatomic Fast Inject Douglas Freimuth
2026-03-26 1:42 ` [PATCH v2 1/3] KVM: s390: Add map/unmap ioctl and clean mappings post-guest Douglas Freimuth
2026-03-26 11:46 ` Christian Borntraeger
2026-03-27 15:22 ` Douglas Freimuth [this message]
2026-03-26 15:56 ` Janosch Frank
2026-03-27 15:31 ` Douglas Freimuth
2026-03-27 15:24 ` Matthew Rosato
2026-03-26 1:42 ` [PATCH v2 2/3] KVM: s390: Enable adapter_indicators_set to use mapped pages Douglas Freimuth
2026-03-27 15:25 ` Matthew Rosato
2026-03-26 1:42 ` [PATCH v2 3/3] KVM: s390: Introducing kvm_arch_set_irq_inatomic fast inject Douglas Freimuth
2026-03-27 15:59 ` Matthew Rosato
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=fd8f5702-8118-4db5-b3be-d68a79fef0de@linux.ibm.com \
--to=freimuth@linux.ibm.com \
--cc=agordeev@linux.ibm.com \
--cc=borntraeger@linux.ibm.com \
--cc=david@kernel.org \
--cc=frankja@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=imbrenda@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=mjrosato@linux.ibm.com \
--cc=svens@linux.ibm.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
Powered by JetHome