From: Ethan Chen via <qemu-devel@nongnu.org>
To: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Cc: Peter Xu <peterx@redhat.com>, David Hildenbrand <david@redhat.com>
Subject: Re: [PATCH 0/6] Support RISC-V IOPMP
Date: Thu, 26 Oct 2023 20:02:18 +0800 [thread overview]
Message-ID: <ZTpVSvySyMfZSyg5@ethan84-VirtualBox> (raw)
In-Reply-To: <20231025051430.493079-1-ethan84@andestech.com>
I found that after add size information it is still not enough for IOPMP to
reject partially hit error. Access is separated in flatview_read_continue and
lost the start address information. I will fix it in next version.
Address start, address end will be added to MemTxAttr, translate_size will
beremoved and translate_attr which is have full MemTxAttr information will be
added in next version patch.
WARNING: multiple messages have this Message-ID (diff)
From: Ethan Chen <ethan84@andestech.com>
To: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Cc: Peter Xu <peterx@redhat.com>, David Hildenbrand <david@redhat.com>
Subject: Re: [PATCH 0/6] Support RISC-V IOPMP
Date: Thu, 26 Oct 2023 20:02:18 +0800 [thread overview]
Message-ID: <ZTpVSvySyMfZSyg5@ethan84-VirtualBox> (raw)
Message-ID: <20231026120218.Jk_CbuCloy4oovKMW-CWHRm8yLCCG_TLrQgktFQYFhc@z> (raw)
In-Reply-To: <20231025051430.493079-1-ethan84@andestech.com>
I found that after add size information it is still not enough for IOPMP to
reject partially hit error. Access is separated in flatview_read_continue and
lost the start address information. I will fix it in next version.
Address start, address end will be added to MemTxAttr, translate_size will
beremoved and translate_attr which is have full MemTxAttr information will be
added in next version patch.
next prev parent reply other threads:[~2023-10-26 12:04 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-25 5:14 [PATCH 0/6] Support RISC-V IOPMP Ethan Chen via
2023-10-25 5:14 ` Ethan Chen
2023-10-25 5:14 ` [PATCH 1/6] exec/memory: Introduce the translate_size function within the IOMMU class Ethan Chen via
2023-10-25 5:14 ` Ethan Chen
2023-10-25 14:56 ` David Hildenbrand
2023-10-26 7:14 ` Ethan Chen via
2023-10-26 7:14 ` Ethan Chen
2023-10-26 7:26 ` David Hildenbrand
2023-10-25 5:14 ` [PATCH 2/6] system/physmem: IOMMU: Invoke the translate_size function if it is implemented Ethan Chen via
2023-10-25 5:14 ` Ethan Chen
2023-10-25 15:14 ` Peter Xu
2023-10-26 6:48 ` Ethan Chen via
2023-10-26 6:48 ` Ethan Chen
2023-10-26 14:20 ` Peter Xu
2023-10-27 3:28 ` Ethan Chen via
2023-10-27 3:28 ` Ethan Chen
2023-10-27 16:02 ` Peter Xu
2023-10-27 16:13 ` Peter Xu
2023-10-30 6:00 ` Ethan Chen via
2023-10-30 6:00 ` Ethan Chen
2023-10-30 15:02 ` Peter Xu
2023-10-31 8:52 ` Ethan Chen via
2023-10-31 8:52 ` Ethan Chen
2023-10-25 5:14 ` [PATCH 3/6] exec/memattrs: Add iopmp source id to MemTxAttrs Ethan Chen via
2023-10-25 5:14 ` Ethan Chen
2023-10-25 5:14 ` [PATCH 4/6] Add RISC-V IOPMP support Ethan Chen via
2023-10-25 5:14 ` Ethan Chen
2023-10-25 5:14 ` [PATCH 5/6] hw/dma: Add Andes ATCDMAC300 support Ethan Chen via
2023-10-25 5:14 ` Ethan Chen
2023-10-25 5:14 ` [PATCH 6/6] hw/riscv/virt: Add IOPMP support Ethan Chen via
2023-10-25 5:14 ` Ethan Chen
2023-10-26 12:02 ` Ethan Chen via [this message]
2023-10-26 12:02 ` [PATCH 0/6] Support RISC-V IOPMP Ethan Chen
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=ZTpVSvySyMfZSyg5@ethan84-VirtualBox \
--to=qemu-devel@nongnu.org \
--cc=david@redhat.com \
--cc=ethan84@andestech.com \
--cc=peterx@redhat.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 NNTP newsgroup(s).