public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Xu Lu <luxu.kernel@bytedance.com>
To: tjeznach@rivosinc.com, joro@8bytes.org, will@kernel.org,
	robin.murphy@arm.com, paul.walmsley@sifive.com
Cc: palmer@dabbelt.com, aou@eecs.berkeley.edu,
	apatel@ventanamicro.com, sunilvl@ventanamicro.com,
	iommu@lists.linux.dev, linux-riscv@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux@rivosinc.com,
	baolu.lu@linux.intel.com, lihangjing@bytedance.com,
	xieyongji@bytedance.com, Xu Lu <luxu.kernel@bytedance.com>
Subject: [PATCH 0/1] iommu/riscv: Support sharing irq lines between iommu queues
Date: Mon,  1 Jul 2024 15:29:07 +0800	[thread overview]
Message-ID: <20240701072908.25503-1-luxu.kernel@bytedance.com> (raw)

This is an additional patch for Tomasz Jeznach's riscv iommu driver
patch series[1].

It seems that when the number of wired irq lines is less than the number
of iommu queues, iommu platform driver does not assign virtual irqs for
iommu queues whose id exceeds the total number of irq lines.

If it is a problem worth fixing, please feel free to merge this patch
into existing commits. And please ignore this patch if we don't think
it is a problem.

[1] link: https://lore.kernel.org/all/cover.1718388908.git.tjeznach@rivosinc.com/

Xu Lu (1):
  iommu/riscv: Support sharing irq lines between iommu queues

 drivers/iommu/riscv/iommu-platform.c | 4 ++++
 1 file changed, 4 insertions(+)

-- 
2.20.1


             reply	other threads:[~2024-07-01  7:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-01  7:29 Xu Lu [this message]
2024-07-01  7:29 ` [PATCH 1/1] iommu/riscv: Support sharing irq lines between iommu queues Xu Lu
2024-07-01  8:47   ` Tomasz Jeznach
2024-07-01  9:10     ` [External] " Xu Lu
2024-07-01  9:14       ` Xu Lu
2024-07-01  9:25         ` Tomasz Jeznach

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=20240701072908.25503-1-luxu.kernel@bytedance.com \
    --to=luxu.kernel@bytedance.com \
    --cc=aou@eecs.berkeley.edu \
    --cc=apatel@ventanamicro.com \
    --cc=baolu.lu@linux.intel.com \
    --cc=iommu@lists.linux.dev \
    --cc=joro@8bytes.org \
    --cc=lihangjing@bytedance.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=linux@rivosinc.com \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.com \
    --cc=robin.murphy@arm.com \
    --cc=sunilvl@ventanamicro.com \
    --cc=tjeznach@rivosinc.com \
    --cc=will@kernel.org \
    --cc=xieyongji@bytedance.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