From: Jeff Johnson <jeff.johnson@oss.qualcomm.com>
To: Zhang Zekun <zhangzekun11@huawei.com>,
xuwei5@hisilicon.com, lihuisong@huawei.com,
Jonathan.Cameron@huawei.com
Cc: linux-kernel@vger.kernel.org, liuyongqiang13@huawei.com
Subject: Re: [PATCH 2/2] soc: hisilicon: kunpeng_hbmcache: Add support for online and offline the hbm cache
Date: Mon, 9 Dec 2024 16:01:24 -0800 [thread overview]
Message-ID: <79f0dbc0-b0b7-448d-a4fb-9e3eceb89801@oss.qualcomm.com> (raw)
In-Reply-To: <20241206112812.32618-3-zhangzekun11@huawei.com>
On 12/6/24 03:28, Zhang Zekun wrote:
> Add a driver for High Bandwidth Memory (HBM) cache, which provides user
> space interfaces to power on/off the HBM cache. Use HBM as a cache can
> take advantage of the high bandwidth of HBM in normal memory access, and
> OS does not need to aware of the existence of HBM cache. For workloads
> which does not require a high memory access bandwidth, power off the HBM
> cache device can help save energy.
>
> Signed-off-by: Zhang Zekun <zhangzekun11@huawei.com>
...
> +module_exit(hbm_cache_module_exit);
> +MODULE_LICENSE("GPL");
Unlike the 1/2 patch, this one CAN be built as a module, so please add the
missing MODULE_DESCRIPTION() macro to avoid the warning with make W=1.
/jeff
next prev parent reply other threads:[~2024-12-10 0:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-06 11:28 [PATCH 0/2] soc: hisilicon: Add power control support for kunpeng HBM Zhang Zekun
2024-12-06 11:28 ` [PATCH 1/2] soc: hisilicon: kunpeng_hbmdev: Add support for controling the power of hbm memory Zhang Zekun
2024-12-07 16:50 ` Alex Elder
2024-12-09 23:56 ` Jeff Johnson
2024-12-06 11:28 ` [PATCH 2/2] soc: hisilicon: kunpeng_hbmcache: Add support for online and offline the hbm cache Zhang Zekun
2024-12-06 21:02 ` kernel test robot
2024-12-07 16:50 ` Alex Elder
2024-12-10 0:01 ` Jeff Johnson [this message]
2024-12-07 16:50 ` [PATCH 0/2] soc: hisilicon: Add power control support for kunpeng HBM Alex Elder
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=79f0dbc0-b0b7-448d-a4fb-9e3eceb89801@oss.qualcomm.com \
--to=jeff.johnson@oss.qualcomm.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=lihuisong@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=liuyongqiang13@huawei.com \
--cc=xuwei5@hisilicon.com \
--cc=zhangzekun11@huawei.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
all inboxes | Powered by JetHome®