From: Alec Ari <neotheuser@gmail.com>
To: Scott Wood <swood@redhat.com>, linux-rt-users@vger.kernel.org
Subject: Re: EFI_STUB doesn't work if PREEMPT_RT
Date: Wed, 12 Jun 2019 12:01:46 -0500 [thread overview]
Message-ID: <CAM5Ud7MTfpyv4ajVkuoe+_pjvq0t1ZWAGUUukrDK+xf5Rx0qiQ@mail.gmail.com> (raw)
In-Reply-To: <CAM5Ud7O2OtDLdJPArAAfw7A1xBm89dBSXk64vYsb-KY9N5RXUw@mail.gmail.com>
EFI Stub is working now, thanks again. Latency isn't affected by EFI
on this particular board (ASUS TUF B450M-Plus Gaming) with Ryzen 2200G
and BIOS version 1003 (dated 2019/04/30 -- Latest as of this writing.)
Alec
On Mon, Jun 10, 2019 at 9:47 PM Alec Ari <neotheuser@gmail.com> wrote:
>
> Hi,
>
> Thank you, Scott! That explains everything, appreciate it! I wanted to
> do latency testing with PREEMPT_RT under EFI and couldn't figure out
> what I was doing wrong.
>
> Alec
next prev parent reply other threads:[~2019-06-12 17:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-10 20:46 EFI_STUB doesn't work if PREEMPT_RT Alec Ari
2019-06-10 20:52 ` Alec Ari
2019-06-10 21:02 ` Alec Ari
2019-06-10 23:37 ` Scott Wood
2019-06-11 2:47 ` Alec Ari
2019-06-12 17:01 ` Alec Ari [this message]
2019-06-14 19:36 ` Sebastian Andrzej Siewior
2019-06-14 23:19 ` Alec Ari
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=CAM5Ud7MTfpyv4ajVkuoe+_pjvq0t1ZWAGUUukrDK+xf5Rx0qiQ@mail.gmail.com \
--to=neotheuser@gmail.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=swood@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).