From: Daniel Henrique Barboza <dbarboza@ventanamicro.com>
To: Gerd Hoffmann <kraxel@redhat.com>, Frank Chang <frank.chang@sifive.com>
Cc: qemu-devel@nongnu.org, qemu-riscv@nongnu.org,
alistair.francis@wdc.com, bmeng@tinylab.org, liwei1518@gmail.com,
zhiwei_liu@linux.alibaba.com, palmer@rivosinc.com,
ajones@ventanamicro.com
Subject: Re: [RFC PATCH 0/1] pci: allocate a PCI ID for RISC-V IOMMU
Date: Wed, 8 May 2024 08:19:37 -0300 [thread overview]
Message-ID: <2819c24b-c3ae-41ad-af8a-f06cceca3a1c@ventanamicro.com> (raw)
In-Reply-To: <d4wsa62chc4dgxeakmsimk6tsvxhflgbofgbugpfjyyo5xx2oh@urgime5r4wqs>
On 5/7/24 12:53, Gerd Hoffmann wrote:
> On Tue, May 07, 2024 at 11:37:05PM GMT, Frank Chang wrote:
>> Hi Daniel,
>>
>> Daniel Henrique Barboza <dbarboza@ventanamicro.com> 於 2024年5月3日 週五 下午8:43寫道：
>>>
>>> Hi,
>>>
>>> In this RFC I want to check with Gerd and others if it's ok to add a PCI
>>> id for the RISC-V IOMMU device. It's currently under review in [1]. The
>>
>> Is the link [1] missing?
>
> Yes ;)
>
> Also: A bit more background on the iommu would be great, for example a
> pointer to the specification.
Fair enough. I'll add a pointer to the latest version of the spec:
https://github.com/riscv-non-isa/riscv-iommu/releases/tag/v1.0.0
Thanks,
Daniel
>
> take care,
> Gerd
>
next prev parent reply other threads:[~2024-05-08 11:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-03 12:42 [RFC PATCH 0/1] pci: allocate a PCI ID for RISC-V IOMMU Daniel Henrique Barboza
2024-05-03 12:42 ` [RFC PATCH 1/1] pci-ids.rst: add Red Hat pci-id for generic IOMMU device Daniel Henrique Barboza
2024-05-07 15:35 ` Frank Chang
2024-05-07 15:37 ` [RFC PATCH 0/1] pci: allocate a PCI ID for RISC-V IOMMU Frank Chang
2024-05-07 15:53 ` Gerd Hoffmann
2024-05-08 11:19 ` Daniel Henrique Barboza [this message]
2024-05-08 11:17 ` Daniel Henrique Barboza
2024-05-07 15:44 ` Peter Maydell
2024-05-08 12:41 ` Daniel Henrique Barboza
2024-05-10 10:47 ` Frank Chang
2024-05-20 17:40 ` Daniel Henrique Barboza
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=2819c24b-c3ae-41ad-af8a-f06cceca3a1c@ventanamicro.com \
--to=dbarboza@ventanamicro.com \
--cc=ajones@ventanamicro.com \
--cc=alistair.francis@wdc.com \
--cc=bmeng@tinylab.org \
--cc=frank.chang@sifive.com \
--cc=kraxel@redhat.com \
--cc=liwei1518@gmail.com \
--cc=palmer@rivosinc.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-riscv@nongnu.org \
--cc=zhiwei_liu@linux.alibaba.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).