From: John Kacur <jkacur@redhat.com>
To: Punit Agrawal <punit1.agrawal@toshiba.co.jp>
Cc: binh1.tranhai@toshiba.co.jp,
Daniel Sangorrin <daniel.sangorrin@toshiba.co.jp>,
dwagner@suse.de, linux-rt-users@vger.kernel.org
Subject: Re: Some issues running rteval on arm64, arm and i386
Date: Fri, 22 Jan 2021 18:27:00 -0500 (EST) [thread overview]
Message-ID: <f4fac09b-dd20-3949-87e1-6855b0cec521@redhat.com> (raw)
In-Reply-To: <877doa1uwx.fsf@kokedama.swc.toshiba.co.jp>
On Mon, 18 Jan 2021, Punit Agrawal wrote:
> Hi John,
>
> We ran into a few issues when trying to run rteval on arm64, arm and
> i386.
>
> A few of the assumptions in rteval don't hold true on these systems.
>
> 1. On arm64, there is no 'model name' in /proc/cpuinfo. See attached
> sample output from qemu arm64. I verified the same behaviour on
> an arm64 board we have as well.
>
> 2. Also, the build target for the kernel on arm64 is "Image" of
> "bzImage". Rather than use different targets per-architecture it
> maybe better to drop it all together. Do you see any downsides?
>
> The attached patches[1][2] gets things moving with regards to Issues 1
> and 2 locally but I am not sure that's the best solution - especially
> for "cpuinfo".
>
> 3. Both arm and i386 do not provide "numa" nodes in sysfs. This
> causes rteval to complain "No valid nodes found in
> /sys/devices/system/node"
>
> Is this requirement planned to be relaxed - it'll be really
> useful to be able to use rteval on these architectures.
>
> Thanks,
> Punit
>
>
In the past we targetted x86_64 only with rteval, but I definitely am
interested in patches that would make it work on other architectures where
the rt-kernel runs.
Could you resend the patches inline in separate mails, as you would when
sending patches for the linux kernel? The reason for this is it makes it
easier to comment on the code.
Thanks
John
next prev parent reply other threads:[~2021-01-22 23:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-18 9:00 Some issues running rteval on arm64, arm and i386 Punit Agrawal
2021-01-22 6:26 ` Ahmed S. Darwish
2021-01-22 23:31 ` John Kacur
2021-01-26 1:40 ` Punit Agrawal
2021-01-22 23:27 ` John Kacur [this message]
2021-01-26 1:04 ` Punit Agrawal
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=f4fac09b-dd20-3949-87e1-6855b0cec521@redhat.com \
--to=jkacur@redhat.com \
--cc=binh1.tranhai@toshiba.co.jp \
--cc=daniel.sangorrin@toshiba.co.jp \
--cc=dwagner@suse.de \
--cc=linux-rt-users@vger.kernel.org \
--cc=punit1.agrawal@toshiba.co.jp \
/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.