All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gong Shuai <gsh517025@gmail.com>
To: Tan Chi <tanchi25@mails.ucas.ac.cn>, gong.shuai@sanechips.com.cn
Cc: kvm@vger.kernel.org, kvm-riscv@lists.infradead.org,
	linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
	iommu@lists.linux.dev
Subject: Re: [RFC PATCH v2 9/9] iommu/riscv: Add riscv_iommu_attach_dev_nested
Date: Tue, 10 Nov 2026 22:22:33 +0800	[thread overview]
Message-ID: <ce2231cc-e554-44fd-b931-5627219b534c@gmail.com> (raw)
In-Reply-To: <20261110135615.8073-1-tanchi25@mails.ucas.ac.cn>

Hi Tan Chi,

On 11/10/2026 9:56 PM, Tan Chi wrote:
> Hi Shuai,
> 
> On Tue, Nov 10, 2026 at 07:51:37PM +0800, Gong Shuai wrote:
>>   2. Use the guest PSCID directly, but allocate a separate host
>>      GSCID for each vIOMMU.
> 
> I agree with option 2 as well. My earlier suggestion did not account
> for independent PSCID namespaces across multiple vIOMMUs sharing the
> same S2 parent.
> 
> Allocating a separate GSCID for each vIOMMU seems simpler than
> maintaining an additional PSCID mapping table.

Agreed. I’ll work on the new version soon.

Thanks,
Shuai

> 
> Thanks,
> Tan Chi
> 


WARNING: multiple messages have this Message-ID (diff)
From: Gong Shuai <gsh517025@gmail.com>
To: Tan Chi <tanchi25@mails.ucas.ac.cn>, gong.shuai@sanechips.com.cn
Cc: kvm@vger.kernel.org, kvm-riscv@lists.infradead.org,
	linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
	iommu@lists.linux.dev
Subject: Re: [RFC PATCH v2 9/9] iommu/riscv: Add riscv_iommu_attach_dev_nested
Date: Tue, 10 Nov 2026 22:22:33 +0800	[thread overview]
Message-ID: <ce2231cc-e554-44fd-b931-5627219b534c@gmail.com> (raw)
In-Reply-To: <20261110135615.8073-1-tanchi25@mails.ucas.ac.cn>

Hi Tan Chi,

On 11/10/2026 9:56 PM, Tan Chi wrote:
> Hi Shuai,
> 
> On Tue, Nov 10, 2026 at 07:51:37PM +0800, Gong Shuai wrote:
>>   2. Use the guest PSCID directly, but allocate a separate host
>>      GSCID for each vIOMMU.
> 
> I agree with option 2 as well. My earlier suggestion did not account
> for independent PSCID namespaces across multiple vIOMMUs sharing the
> same S2 parent.
> 
> Allocating a separate GSCID for each vIOMMU seems simpler than
> maintaining an additional PSCID mapping table.

Agreed. I’ll work on the new version soon.

Thanks,
Shuai

> 
> Thanks,
> Tan Chi
> 


_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

WARNING: multiple messages have this Message-ID (diff)
From: Gong Shuai <gsh517025@gmail.com>
To: Tan Chi <tanchi25@mails.ucas.ac.cn>, gong.shuai@sanechips.com.cn
Cc: kvm@vger.kernel.org, kvm-riscv@lists.infradead.org,
	linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
	iommu@lists.linux.dev
Subject: Re: [RFC PATCH v2 9/9] iommu/riscv: Add riscv_iommu_attach_dev_nested
Date: Tue, 10 Nov 2026 22:22:33 +0800	[thread overview]
Message-ID: <ce2231cc-e554-44fd-b931-5627219b534c@gmail.com> (raw)
In-Reply-To: <20261110135615.8073-1-tanchi25@mails.ucas.ac.cn>

Hi Tan Chi,

On 11/10/2026 9:56 PM, Tan Chi wrote:
> Hi Shuai,
> 
> On Tue, Nov 10, 2026 at 07:51:37PM +0800, Gong Shuai wrote:
>>   2. Use the guest PSCID directly, but allocate a separate host
>>      GSCID for each vIOMMU.
> 
> I agree with option 2 as well. My earlier suggestion did not account
> for independent PSCID namespaces across multiple vIOMMUs sharing the
> same S2 parent.
> 
> Allocating a separate GSCID for each vIOMMU seems simpler than
> maintaining an additional PSCID mapping table.

Agreed. I’ll work on the new version soon.

Thanks,
Shuai

> 
> Thanks,
> Tan Chi
> 


-- 
kvm-riscv mailing list
kvm-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kvm-riscv

  reply	other threads:[~2026-11-10 14:22 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-29  6:11 [RFC PATCH v2 0/9] iommu/riscv: Add nested translation (vIOMMU) support Gong Shuai
2026-10-29  6:11 ` Gong Shuai
2026-10-29  6:11 ` Gong Shuai
2026-10-29  6:11 ` [RFC PATCH v2 1/9] iommu/riscv: Use DC.tc.V as the device context valid bit Gong Shuai
2026-10-29  6:11   ` Gong Shuai
2026-10-29  6:11   ` Gong Shuai
2026-10-29  6:11 ` [RFC PATCH v2 2/9] iommufd: Add RISC-V IOMMU hwpt and vIOMMU types Gong Shuai
2026-10-29  6:11   ` Gong Shuai
2026-10-29  6:11   ` Gong Shuai
2026-10-29  6:11 ` [RFC PATCH v2 3/9] iommufd: Add RISC-V IOMMU cache invalidation data type Gong Shuai
2026-10-29  6:11   ` Gong Shuai
2026-10-29  6:11   ` Gong Shuai
2026-10-29  6:11 ` [RFC PATCH v2 4/9] iommu/riscv: Add vIOMMU object support Gong Shuai
2026-10-29  6:11   ` Gong Shuai
2026-10-29  6:11   ` Gong Shuai
2026-10-29  6:11 ` [RFC PATCH v2 5/9] iommu/riscv: Add nested domain allocation Gong Shuai
2026-10-29  6:11   ` Gong Shuai
2026-10-29  6:11   ` Gong Shuai
2026-10-29  6:11 ` [RFC PATCH v2 6/9] iommu/riscv: Add vIOMMU cache invalidation Gong Shuai
2026-10-29  6:11   ` Gong Shuai
2026-10-29  6:11   ` Gong Shuai
2026-10-29  6:11 ` [RFC PATCH v2 7/9] iommufd: Add RISC-V IOMMU hardware info type Gong Shuai
2026-10-29  6:11   ` Gong Shuai
2026-10-29  6:11   ` Gong Shuai
2026-10-29  6:11 ` [RFC PATCH v2 8/9] iommu/riscv: Add riscv_iommu_hw_info Gong Shuai
2026-10-29  6:11   ` Gong Shuai
2026-10-29  6:11   ` Gong Shuai
2026-10-29  6:11 ` [RFC PATCH v2 9/9] iommu/riscv: Add riscv_iommu_attach_dev_nested Gong Shuai
2026-10-29  6:11   ` Gong Shuai
2026-10-29  6:11   ` Gong Shuai
2026-11-05 14:49   ` Tan Chi
2026-11-05 14:49     ` Tan Chi
2026-11-05 14:49     ` Tan Chi
2026-11-05 18:32     ` Jason Gunthorpe
2026-11-05 18:32       ` Jason Gunthorpe
2026-11-05 18:32       ` Jason Gunthorpe
2026-11-10 12:01       ` Gong Shuai
2026-11-10 12:01         ` Gong Shuai
2026-11-10 12:01         ` Gong Shuai
2026-11-10 11:51     ` Gong Shuai
2026-11-10 11:51       ` Gong Shuai
2026-11-10 11:51       ` Gong Shuai
2026-11-10 13:16       ` Jason Gunthorpe
2026-11-10 13:16         ` Jason Gunthorpe
2026-11-10 13:16         ` Jason Gunthorpe
2026-11-10 13:47         ` Gong Shuai
2026-11-10 13:47           ` Gong Shuai
2026-11-10 13:47           ` Gong Shuai
2026-11-10 13:56       ` Tan Chi
2026-11-10 13:56         ` Tan Chi
2026-11-10 13:56         ` Tan Chi
2026-11-10 14:22         ` Gong Shuai [this message]
2026-11-10 14:22           ` Gong Shuai
2026-11-10 14:22           ` Gong Shuai

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=ce2231cc-e554-44fd-b931-5627219b534c@gmail.com \
    --to=gsh517025@gmail.com \
    --cc=gong.shuai@sanechips.com.cn \
    --cc=iommu@lists.linux.dev \
    --cc=kvm-riscv@lists.infradead.org \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=tanchi25@mails.ucas.ac.cn \
    /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.