From: owl129 <owl129@126.com>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>, qemu-devel@nongnu.org
Subject: Re:Re: [PATCH] This patch implements several Octeon +/II instructions.
Date: Mon, 12 Feb 2024 18:57:03 +0800 (CST) [thread overview]
Message-ID: <233bef0a.937.18d9cf6996a.Coremail.owl129@126.com> (raw)
In-Reply-To: <a616c83d-068e-46a0-80b7-878425005317@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 972 bytes --]
Hi > How can we test it? Is there any distribution producing kernel for
> Octeon+/2? Per https://github.com/MarvellEmbeddedProcessors/marvell-dpdk
> I understand there could be Linux and FreeBSD, is that correct?Actually I don't know how to fully test each intruction.
To the best of my knowledge, the Octeon Instruction is optimized for networking security/application processor.
And the latest reference manual is not public available. (https://dokumen.tips/documents/cavium-networks-octeon-plus-cn50xx-hardware-2008-cavium-networks-octeon-plus.html?page=1 )
I find the Instruction specification from Marvell's toolchain and Vargrind's vex ir translation (https://sourceware.org/git/?p=valgrind.git;a=blob;f=VEX/priv/guest_mips_toIR.c;h=1285edad0b83b0f0a6b21fc63d2235d50f94d204;hb=HEAD#l2909)
I have successfully emulated an ELF binary compiled for Cavium (Marvell) on x86 architecture.
Can you help or give me some suggestions about testing?
Best
owl129
[-- Attachment #2: Type: text/html, Size: 2193 bytes --]
prev parent reply other threads:[~2024-02-12 10:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-19 4:56 [PATCH] This patch implements several Octeon +/II instructions owl129
2024-02-12 8:56 ` Philippe Mathieu-Daudé
2024-02-12 10:57 ` owl129 [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=233bef0a.937.18d9cf6996a.Coremail.owl129@126.com \
--to=owl129@126.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
/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).