Linux Perf Users
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Mingming Cao" <mmc@linux.ibm.com>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: [PATCH net-next v8 01/15] ibmveth: Add MQ RX hypercall wrappers and call definitions
Date: Tue, 10 Nov 2026 23:57:45 +0000	[thread overview]
Message-ID: <sashiko-outbox-207971@kernel.org> (raw)
In-Reply-To: <20261109235556.60604-2-mmc@linux.ibm.com>

> Single-queue ibmveth only needs h_register_logical_lan() plus legacy
> buffer add/free calls. MQ RX uses per-queue handles, so the driver must
> also be able to register/deregister subordinate queues and post
> buffers against a specific queue handle.
> 
> Add the PHYP call IDs for:
> 
>   H_REG_LOGICAL_LAN_QUEUE (0x49C)
>   H_ADD_LOGICAL_LAN_BUFFERS_QUEUE (0x4A0)
>   H_FREE_LOGICAL_LAN_QUEUE (0x4A8)
> 
> as defined in PAPR 11.20.00. The gaps at 0x498 (reserved) and 0x4A4
> (reserved for H_FREE_LOGICAL_LAN_BUFFER_QUEUE) are intentional; this
> series tears queues down with H_FREE_LOGICAL_LAN_QUEUE and does not add
> the buffer-queue free hcall.
> [ ... ]
> yet. Legacy firmware keeps H_REGISTER_LOGICAL_LAN and the existing
> buffer hcalls. The new wrappers are used only when a later commit sets
> multi_queue from H_ILLAN_ATTRIBUTES.
> 
> Signed-off-by: Mingming Cao <mmc@linux.ibm.com>

Sashiko has reviewed this patch and found no issues.

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261109235556.60604-1-mmc@linux.ibm.com?part=1


      reply	other threads:[~2026-11-10 23:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20261109235556.60604-1-mmc@linux.ibm.com>
2026-11-09 23:55 ` [PATCH net-next v8 01/15] ibmveth: Add MQ RX hypercall wrappers and call definitions Mingming Cao
2026-11-10 23:57   ` sashiko-bot [this message]

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=sashiko-outbox-207971@kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mmc@linux.ibm.com \
    --cc=sashiko-reviews@lists.linux.dev \
    /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