pment forward.
I do really think that Brennan's work should be the "true" solution to
PCI devices.
--
Yang Chung Fan (楊宗凡) (ヤン ゾン ファン)
/ 16GB
- Custom compiled kernel:
- Linux rtlab-linux 5.4.39-rt23+ #1 SMP PREEMPT_RT Mon May 11
22:10:55 JST 2020 x86_64 x86_64 x86_64 GNU/Linux
- Custom compiled Qemu:
- QEMU emulator version 4.2.0 (v4.2.0-dirty)
BR,
--
Yang Chung Fan (楊宗凡) (ヤン ゾン ファン)
In addition, may I have your processor model please.
The Intel processors feature set varys quite a lot.
Maybe some feature settings are considered improper for your
processor, causing a GP.
BR,
--
Yang Chung Fan (楊宗凡) (ヤン ゾン ファン)
u[0] and gcc[1] shipped with Debian Bullseye (testing).
These shouldn't be an issue.
I have seen aliked looping problem during porting, mainly due to
improperly setup GPT causing GP or page table causing PF.
I suppose you didn't modify the code, therefore it seems strange to me.
BR,
--
Yang Chung Fan (楊宗凡) (ヤン ゾン ファン)
erred fix would simply to make CONFIG_LIB_SYSCALL
> dependent on !CONFIG_BUILD_FLAT in the Kconfig file.
>
>
--
Yang Chung Fan (楊宗凡) (ヤン ゾン ファン)
Member of Softlab, Tsukuba University , Japan
Email: sonic.tw...@gmail.com
Hi,
Did anyone also noticed that when building with CONFIG_LIB_SYSCALL=y,
the linker is unhappy about the duplicated task_spawn() symbols?
One of them is in sched/ and other one is in libs/libc.
--
Yang
2020年5月18日(月) 14:47 Brennan Ashton :
>
> On Sun, May 17, 2020, 10:36 PM Takashi Yamamoto
> wrote:
>
> > hi,
> >
> > this is just a curious question.
> > why do we use the name "intel64" for qemu things?
> > i thought it was from qemu, but qemu seems to use x86_64 or amd64.
> > i think "amd64" is m
register profile as again
sigdeliver.
The original RIP saved in TCB is overwritten and destroyed.
Currently, by removing any possibility voluntary schedule point in the
critical section, this problem no longer exists.
--
Yang Chung Fan (楊宗凡) (ヤン ゾン ファン)
Member of Softlab, Tsukuba University , Ja
tched in task might send a second signal to the task A.
In such case, the saved instruction pointer value in the TCB might get
overwritten, causing a consecutive incorrect execution path when
returning tho the previous signal.
Am I correct or did I missed something here?
--
Yang Chung Fan (楊宗凡) (
oader after these are properly done.
Yang
--
Yang Chung Fan (楊宗凡) (ヤン ゾン ファン)
Member of Softlab, Tsukuba University , Japan
Email: sonic.tw...@gmail.com
existing Linux
real-time solutions while not losing the compatibility with Linux.
--
Yang Chung Fan (楊宗凡) (ヤン ゾン ファン)
Member of Softlab, Tsukuba University , Japan
Email: sonic.tw...@gmail.com
11 matches
Mail list logo