From: Philippe Gerum <rpm@xenomai.org>
To: Jan Kiszka <jan.kiszka@siemens.com>, Pintu Kumar <pintu.ping@gmail.com>
Cc: "Xenomai@xenomai.org" <xenomai@xenomai.org>
Subject: Re: [Xenomai] Kernel oops during rtnet loopback usage on x86_64 (e1000e)
Date: Wed, 27 Jun 2018 20:04:37 +0200 [thread overview]
Message-ID: <913ebdb1-f356-4171-a765-1ce7a0222bd5@xenomai.org> (raw)
In-Reply-To: <b15f32c2-9bbc-c2f6-e65d-7331c0bc790a@siemens.com>
On 06/27/2018 06:17 PM, Jan Kiszka wrote:
> On 2018-06-27 16:12, Pintu Kumar wrote:
>>> With nosmap, that particular issue should no longer occur (at least as
>>> long as we can ask the kernel for this relaxation), so I suspect the
>>> other effect you see now is something else.
>>
>> Just for the information, that issue occurred even on Beagle bone, and
>> there is no smap on arm.
>> However, it works on virtual box. how ?
>
> Does it work when you go back to Xenomai 3.0.6? Then it would be a
> regression of the copy-to/from-userspace improvements done after that
> release, you could start bisecting which commit introduced it.
>
> But I'm not sure right now if there isn't something similar to smap
> (then just without a knob to turn it off) in the ARM architecture as well...
>
AFAIR, use of protection domains is built in depending on a selection by
the CPU support code.
--
Philippe.
next prev parent reply other threads:[~2018-06-27 18:04 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-25 8:39 [Xenomai] Kernel oops during rtnet loopback usage on x86_64 (e1000e) Pintu Kumar
2018-04-25 10:05 ` Jan Kiszka
2018-04-25 11:36 ` Pintu Kumar
2018-04-26 16:23 ` Jan Kiszka
2018-06-19 13:48 ` Pintu Kumar
2018-06-20 7:54 ` Pintu Kumar
2018-06-21 11:20 ` Pintu Kumar
2018-06-21 11:55 ` Jan Kiszka
2018-06-21 12:27 ` [Xenomai] Kernel panic during kernel bootup on arm64 qemu (e1000e) gengdongjiu
2018-06-21 13:47 ` Greg Gallagher
2018-06-21 13:56 ` [Xenomai] Kernel panic during kernel bootup on arm64 qemu gengdongjiu
[not found] ` <5b2baebc.1c69fb81.af598.ef46SMTPIN_ADDED_BROKEN@mx.google.com>
2018-06-21 14:04 ` Greg Gallagher
2018-06-21 14:14 ` gengdongjiu
2018-06-21 13:41 ` [Xenomai] Kernel oops during rtnet loopback usage on x86_64 (e1000e) Jan Kiszka
2018-06-21 14:57 ` Jan Kiszka
2018-06-25 12:56 ` Pintu Kumar
2018-06-26 11:08 ` Pintu Kumar
2018-06-27 10:20 ` Jan Kiszka
2018-06-27 10:56 ` Pintu Kumar
2018-06-27 11:14 ` Jan Kiszka
2018-06-27 14:12 ` Pintu Kumar
2018-06-27 16:17 ` Jan Kiszka
2018-06-27 17:13 ` Pintu Kumar
2018-06-27 17:17 ` Greg Gallagher
2018-06-27 17:29 ` Pintu Kumar
2018-06-27 18:10 ` Philippe Gerum
2018-06-28 10:40 ` Pintu Kumar
2018-06-28 13:07 ` Philippe Gerum
2018-06-27 18:04 ` Philippe Gerum [this message]
2018-11-04 16:17 ` Philippe Gerum
2018-11-06 18:57 ` Jan Kiszka
2018-11-07 10:04 ` Philippe Gerum
2018-11-07 10:19 ` Jan Kiszka
2018-11-07 10:31 ` Philippe Gerum
2018-11-07 11:19 ` Jan Kiszka
2018-11-07 11:29 ` Philippe Gerum
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=913ebdb1-f356-4171-a765-1ce7a0222bd5@xenomai.org \
--to=rpm@xenomai.org \
--cc=jan.kiszka@siemens.com \
--cc=pintu.ping@gmail.com \
--cc=xenomai@xenomai.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 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.