From: Eric Biggers <ebiggers@kernel.org>
To: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
Cc: Theodore Tso <tytso@mit.edu>,
Nathaniel Roach <nroach44@nroach44.id.au>,
Andreas Larsson <andreas@gaisler.com>,
"David S. Miller" <davem@davemloft.net>,
sparclinux@vger.kernel.org, linux-crypto@vger.kernel.org
Subject: Re: Does the SPARC optimized crypto and CRC code actually work?
Date: Sun, 22 Mar 2026 07:59:42 -0700 [thread overview]
Message-ID: <20260322145942.GC2183@quark> (raw)
In-Reply-To: <079d287944ffe94903286ea73fc1df167206321a.camel@physik.fu-berlin.de>
On Tue, Mar 17, 2026 at 03:14:50PM +0100, John Paul Adrian Glaubitz wrote:
> Hi Ted,
>
> On Tue, 2026-03-17 at 10:06 -0400, Theodore Tso wrote:
> > How hard would it be to add support for the Sparc crypto accleration
> > opcodes to QEMU? Is that something that could be, say, an GSOC or
> > Outreachy project?
>
> Good idea. I'll ask someone who has been mentoring QEMU enhancements in the past.
>
> Adrian
FYI, I filed https://github.com/sparclinux/issues/issues/77
- Eric
next prev parent reply other threads:[~2026-03-22 14:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-16 20:42 Does the SPARC optimized crypto and CRC code actually work? Eric Biggers
2026-03-17 2:48 ` Nathaniel Roach
2026-03-17 3:45 ` Eric Biggers
2026-03-17 7:16 ` John Paul Adrian Glaubitz
2026-03-17 14:06 ` Theodore Tso
2026-03-17 14:14 ` John Paul Adrian Glaubitz
2026-03-22 14:59 ` Eric Biggers [this message]
2026-03-23 5:58 ` John Paul Adrian Glaubitz
2026-03-23 10:36 ` Nathaniel Roach
2026-03-23 18:20 ` Eric Biggers
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=20260322145942.GC2183@quark \
--to=ebiggers@kernel.org \
--cc=andreas@gaisler.com \
--cc=davem@davemloft.net \
--cc=glaubitz@physik.fu-berlin.de \
--cc=linux-crypto@vger.kernel.org \
--cc=nroach44@nroach44.id.au \
--cc=sparclinux@vger.kernel.org \
--cc=tytso@mit.edu \
/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.