From: Jan Kiszka <jan.kiszka@siemens.com>
To: Pintu Agarwal <pintu.ping@gmail.com>
Cc: "孙世龙 sunshilong" <sunshilong369@gmail.com>,
"Pintu Kumar" <pintu@codeaurora.org>,
xenomai <xenomai@xenomai.org>
Subject: Re: [PATCH] kernel:cobalt:heap: replace kzalloc with kvzalloc
Date: Thu, 13 Aug 2020 12:31:06 +0200 [thread overview]
Message-ID: <45246226-b3ca-a00a-5729-9a28e558dda5@siemens.com> (raw)
In-Reply-To: <CAOuPNLixxP7+RkW716PZ97mq1dNNdzsMMdX_LAZ4+_DYkmREUw@mail.gmail.com>
On 13.08.20 04:26, Pintu Agarwal wrote:
> On Wed, 12 Aug 2020 at 21:22, Jan Kiszka <jan.kiszka@siemens.com> wrote:
>>
>> On 11.08.20 13:44, Pintu Agarwal wrote:
>>> Oh sorry about this.
>>> I can send a new patch set with kvmalloc that can work on all kernel versions.
>>>
>>
>> Yes, please do so to avoid that things become to messy when trying to
>> create that manually.
>>
>
> Thank you so much for your confirmation.
> Yes I am preparing a patch-set v2 and will send it soon.
> But is there a way to use both kvzalloc and kvmalloc depending on
> kernel version ?
> I see that checking using below is also not valid any more in higher
> kernel version:
> #if LINUX_VERSION_CODE >= KERNEL_VERSION(4, 9, 0)
>
This pattern still works, also in 5.x.
> Also I see in some versions directly kmalloc is used (not kzalloc).
> Moreover, kvmalloc also may not be available in 3.x kernel version as well.
> So wondering if kvmalloc would be fine or not ?
>
> Is covering 4.x kernel version should be enough ?
>
Yes, 4.4 is our lower boundary for Xenomai 3.1.
Jan
--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2020-08-13 10:31 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-31 18:04 [PATCH] kernel:cobalt:heap: replace kzalloc with kvzalloc Pintu Kumar
2020-08-07 4:56 ` pintu
2020-08-10 7:09 ` pintu
2020-08-10 8:41 ` Philippe Gerum
2020-08-11 7:11 ` Jan Kiszka
2020-08-11 8:10 ` Jan Kiszka
2020-08-11 8:48 ` 孙世龙 sunshilong
2020-08-11 8:51 ` Jan Kiszka
2020-08-11 9:17 ` 孙世龙 sunshilong
[not found] ` <CAOuPNLhPejZsUwCrjOWm=kT_JLJipcV7WXt6TgiAA6UDXpOmvg@mail.gmail.com>
2020-08-12 15:51 ` Jan Kiszka
[not found] ` <CAOuPNLixxP7+RkW716PZ97mq1dNNdzsMMdX_LAZ4+_DYkmREUw@mail.gmail.com>
2020-08-13 10:31 ` Jan Kiszka [this message]
[not found] ` <CAOuPNLjozRbNL_S8d8qNR9feSjcbiT+vbhLVM4K+AMAhrJy=TQ@mail.gmail.com>
2020-08-14 0:52 ` 孙世龙 sunshilong
2020-08-14 7:06 ` Jan Kiszka
[not found] ` <CAOuPNLjMBjWEQ7KiZd=d6ySMJ=zz_OMWZZ6A2VoHRgcEvp=MnA@mail.gmail.com>
2020-08-14 9:54 ` 孙世龙 sunshilong
2020-08-14 10:08 ` Jan Kiszka
2020-08-15 10:29 ` [PATCH v2] kernel:cobalt:heap: replace kzalloc with vmalloc Pintu Kumar
2020-08-18 5:44 ` Jan Kiszka
2020-08-18 5:51 ` Jan Kiszka
2020-08-18 7:40 ` 孙世龙 sunshilong
2020-08-18 17:56 ` [PATCH v3] kernel:cobalt:heap: replace kzalloc with vzalloc Pintu Kumar
2020-08-19 6:31 ` Jan Kiszka
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=45246226-b3ca-a00a-5729-9a28e558dda5@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=pintu.ping@gmail.com \
--cc=pintu@codeaurora.org \
--cc=sunshilong369@gmail.com \
--cc=xenomai@xenomai.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 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.