From: Johannes Berg <johannes@sipsolutions.net>
To: Simo Sorce <simo@redhat.com>,
Anton Ivanov <anton.ivanov@kot-begemot.co.uk>,
linux-um@lists.infradead.org
Cc: linux-crypto@vger.kernel.org, "Stephan Müller" <smueller@chronox.de>
Subject: Re: jitterentropy vs. simulation
Date: Fri, 01 Dec 2023 21:04:30 +0100 [thread overview]
Message-ID: <640c12810b336aa99584697e21215f3cacb13c79.camel@sipsolutions.net> (raw)
In-Reply-To: <e1b3ccb744d67e6214cf206ba8480cb3e35694cf.camel@redhat.com>
On Fri, 2023-12-01 at 14:25 -0500, Simo Sorce wrote:
>
> Doesn't this imply the simulation is not complete
Kind of?
> and you need to add
> clock jitter for the simulation to be more useful?
>
No, it's more _intentionally_ incomplete. This works fine in normal
ARCH=um, but with time-travel variants we have more of a discrete event-
based simulation, to integrates well with other things (e.g. SystemC or
similar based device simulations). So this is quite intentional, and
yes, it breaks in a few spots such as this one.
johannes
next prev parent reply other threads:[~2023-12-01 20:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-01 10:21 jitterentropy vs. simulation Johannes Berg
[not found] ` <7db861e3-60e4-0ed4-9b28-25a89069a9db@kot-begemot.co.uk>
2023-12-01 18:35 ` Johannes Berg
2023-12-01 19:25 ` Simo Sorce
2023-12-01 20:04 ` Johannes Berg [this message]
2023-12-04 8:52 ` Stephan Mueller
2023-12-04 10:24 ` Johannes Berg
2023-12-04 10:35 ` Stephan Mueller
2023-12-04 12:06 ` Benjamin Beichler
2023-12-04 12:50 ` Anton Ivanov
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=640c12810b336aa99584697e21215f3cacb13c79.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=anton.ivanov@kot-begemot.co.uk \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-um@lists.infradead.org \
--cc=simo@redhat.com \
--cc=smueller@chronox.de \
/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