Re: [PATCH 0/4] New UART drivers for PL011 and Mini UART

A gentle reminder. On Wed, Sep 6, 2023 at 8:31 AM Utkarsh Verma wrote: > A gentle reminder. > > Regards, > Utkarsh > > On Thu, Aug 31, 2023 at 10:02 AM Utkarsh Verma > wrote: > >> A gentle reminder for this patch. Please have a look at this and let me >>

Re: [PATCH 0/4] New UART drivers for PL011 and Mini UART

A gentle reminder. Regards, Utkarsh On Thu, Aug 31, 2023 at 10:02 AM Utkarsh Verma wrote: > A gentle reminder for this patch. Please have a look at this and let me > know what changes are required. Once this is merged, I have a few more > patches building upon this. > > Reg

Re: [PATCH 0/4] New UART drivers for PL011 and Mini UART

A gentle reminder for this patch. Please have a look at this and let me know what changes are required. Once this is merged, I have a few more patches building upon this. Regards, Utkarsh On Wed, Aug 30, 2023 at 9:47 AM Utkarsh Verma wrote: > This patch series adds two drivers, PL011 and M

[PATCH 4/4] bsps: Update BSPs to use the new PL011 driver

This commit updates the existing BSPs to use the new PL011 driver. --- bsps/aarch64/a53/console/console.c| 15 +- bsps/aarch64/a72/console/console.c| 15 +- bsps/aarch64/raspberrypi/console/console.c| 29 --- bsps/arm/raspberrypi/console/

[PATCH 1/4] bsps/shared: Add new PL011 driver with IRQ support

X-License-Identifier: BSD-2-Clause */ -/** - * @file - * - * @ingroup RTEMSBSPsARMShared - * - * @brief ARM PL011 Support Package - */ - /* - * Copyright (C) 2013, 2014 embedded brains GmbH & Co. KG + * Copyright (C) 2023 Utkarsh Verma + * * * Redistribution and use in source and binar

[PATCH 3/4] spec: Add Mini UART and PL011 drivers to build spec

This commit updates the build spec to include the new UART drivers for PL011 and Mini UART. --- spec/build/bsps/aarch64/raspberrypi/bspraspberrypi4.yml | 1 - spec/build/bsps/obj.yml | 7 --- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/spec/bu

[PATCH 0/4] New UART drivers for PL011 and Mini UART

a/rtems/tree/uart-drivers Utkarsh Verma (4): bsps/shared: Add new PL011 driver with IRQ support bsps/shared: Add new Mini UART driver spec: Add Mini UART and PL011 drivers to build spec bsps: Update BSPs to use the new PL011 driver bsps/aarch64/a53/console/console.c| 15 +-

[PATCH 2/4] bsps/shared: Add new Mini UART driver

mode 100644 index 00..7fce5d0d97 --- /dev/null +++ b/bsps/include/dev/serial/mini-uart.h @@ -0,0 +1,54 @@ +/* SPDX-License-Identifier: BSD-2-Clause */ + +/* + * Copyright (C) 2023 Utkarsh Verma + * + * + * Redistribution and use in source and binary forms, with or without + * modification

[PATCH 4/4] spec: Add Mini UART and PL011 drivers to build spec

This commit updates the build spec to include the new UART drivers for PL011 and Mini UART. --- spec/build/bsps/aarch64/raspberrypi/bspraspberrypi4.yml | 1 - spec/build/bsps/obj.yml | 7 --- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/spec/bu

[PATCH 3/4] bsps: Update BSPs to use the new PL011 driver

This commit updates the existing BSPs to use the new PL011 driver. --- bsps/aarch64/a53/console/console.c| 14 +- bsps/aarch64/a72/console/console.c| 14 +- bsps/aarch64/raspberrypi/console/console.c| 14 +- bsps/arm/raspberrypi/console/console-c

[PATCH 2/4] bsps/shared: Add new Mini UART driver

mode 100644 index 00..7fce5d0d97 --- /dev/null +++ b/bsps/include/dev/serial/mini-uart.h @@ -0,0 +1,54 @@ +/* SPDX-License-Identifier: BSD-2-Clause */ + +/* + * Copyright (C) 2023 Utkarsh Verma + * + * + * Redistribution and use in source and binary forms, with or without + * modification

[PATCH 1/4] bsps/shared: Add new PL011 driver with IRQ support

X-License-Identifier: BSD-2-Clause */ -/** - * @file - * - * @ingroup RTEMSBSPsARMShared - * - * @brief ARM PL011 Support Package - */ - /* - * Copyright (C) 2013, 2014 embedded brains GmbH & Co. KG + * Copyright (C) 2023 Utkarsh Verma + * * * Redistribution and use in source and binar

[PATCH 0/4] New UART drivers for PL011 and Mini UART

a/rtems/tree/uart-drivers Utkarsh Verma (4): bsps/shared: Add new PL011 driver with IRQ support bsps/shared: Add new Mini UART driver bsps: Update BSPs to use the new PL011 driver spec: Add Mini UART and PL011 drivers to build spec bsps/aarch64/a53/console/console.c| 14 +-

Re: [PATCH 0/2 v3] Refactor the aarch64/raspberryp4b BSP

A gentle reminder for this patch. On Thu, Aug 10, 2023 at 11:45 AM Utkarsh Verma wrote: > A gentle reminder for this. Please let me know which changes are required > so that I can send the next set of patches as well. > > On Wed, Aug 9, 2023 at 9:20 AM Utkarsh Verma > wrote: &

Re: [PATCH 0/2 v3] Refactor the aarch64/raspberryp4b BSP

A gentle reminder for this. Please let me know which changes are required so that I can send the next set of patches as well. On Wed, Aug 9, 2023 at 9:20 AM Utkarsh Verma wrote: > Changes can also be seen on my fork: > https://github.com/UtkarshVerma/rtems/tree/refactor > > On Wed,

Re: [PATCH 0/2 v3] Refactor the aarch64/raspberryp4b BSP

Changes can also be seen on my fork: https://github.com/UtkarshVerma/rtems/tree/refactor On Wed, Aug 9, 2023 at 9:18 AM Utkarsh Verma wrote: > This patch series refactors the BSP and build spec for Raspberry Pi 4B > with the following goals in mind: > > - IWYU(include what you u

[PATCH 2/2] build: Modularize the aarch64/raspberrypi spec

rmv8-a -description: | - ABI flags + - Copyright (C) 2022 Mohd Noor Aman + - Copyright (C) 2023 Utkarsh Verma + +type: build enabled-by: true -links: [] + +build-type: option name: ABI_FLAGS -type: build +description: ABI flags + +actions: + - get-string: null + - split: null + - env-append: null + +d

[PATCH 1/2] bsps/aarch64/raspberrypi: Refactor the BSP

*/ /* * Copyright (C) 2022 Mohd Noor Aman + * Copyright (C) 2023 Utkarsh Verma * * * Redistribution and use in source and binary forms, with or without @@ -34,36 +35,32 @@ * POSSIBILITY OF SUCH DAMAGE. */ -#include - -#include -#include #include +#include +#include -#include

[PATCH 0/2 v3] Refactor the aarch64/raspberryp4b BSP

highly appreciated. Regards, Utkarsh Utkarsh Verma (2): bsps/aarch64/raspberrypi: Refactor the BSP build: Modularize the aarch64/raspberrypi spec bsps/aarch64/raspberrypi/console/console.c| 39 +- bsps/aarch64/raspberrypi/include/bsp.h| 37 +- .../aarch64/raspberrypi/include/bsp

Re: [PATCH 1/3] gitignore: Ignore clangd and clang-format files

You're correct. I'll remove this commit. Regards, Utkarsh On Tue, Aug 8, 2023 at 11:39 AM Chris Johns wrote: > On 8/8/2023 4:07 pm, Chris Johns wrote: > > On 8/8/2023 1:05 pm, Utkarsh Verma wrote: > >> --- > >> .gitignore | 4 > >> 1 file c

Re: [PATCH 0/3] Refactor the aarch64/raspberryp4b BSP

Changes are also on my GitHub fork: https://github.com/UtkarshVerma/rtems/tree/refactor. Regards, Utkarsh On Tue, Aug 8, 2023 at 8:35 AM Utkarsh Verma wrote: > This patch series refactors the BSP and build spec for Raspberry Pi 4B > with the following goals in mind: > > - IWYU(incl

[PATCH 3/3] build: Modularize the aarch64/raspberrypi spec

rmv8-a -description: | - ABI flags + - Copyright (C) 2022 Mohd Noor Aman + - Copyright (C) 2023 Utkarsh Verma + +type: build enabled-by: true -links: [] + +build-type: option name: ABI_FLAGS -type: build +description: ABI flags + +actions: + - get-string: null + - split: null + - env-append: null + +d

[PATCH 2/3] bsps/aarch64/raspberrypi: Refactor the BSP

*/ /* * Copyright (C) 2022 Mohd Noor Aman + * Copyright (C) 2023 Utkarsh Verma * * * Redistribution and use in source and binary forms, with or without @@ -34,36 +35,32 @@ * POSSIBILITY OF SUCH DAMAGE. */ -#include - -#include -#include #include +#include +#include -#include

[PATCH 1/3] gitignore: Ignore clangd and clang-format files

--- .gitignore | 4 1 file changed, 4 insertions(+) diff --git a/.gitignore b/.gitignore index 8b28b186e1..d0144f6737 100644 --- a/.gitignore +++ b/.gitignore @@ -12,3 +12,7 @@ Makefile.in /testsuites/build/build /testsuites/build/wscript .waf* +.clangd +.clang-format +compile_commands.js

[PATCH 0/3] Refactor the aarch64/raspberryp4b BSP

highly appreciated. Regards, Utkarsh Utkarsh Verma (3): gitignore: Ignore clangd and clang-format files bsps/aarch64/raspberrypi: Refactor the BSP build: Modularize the aarch64/raspberrypi spec .gitignore| 4 + bsps/aarch64/raspberrypi/console/console.c

Re: [PATCH 1/2] bsps/aarch64/raspberrypi: Refactor code base

Hi Kinsey, Thanks for the suggestions. I'll break it up into several commits as you suggested. Shall I break it down as follows? - Build spec changes - Formatting changes - Macro renamings Regards, Utkarsh On Mon, Aug 7, 2023 at 8:49 PM Kinsey Moore wrote: > I would say that the cont

Re: [PATCH 0/2] Refactor aarch64/raspberrypi4b BSP

Forgot to add that these changes are there on my GitHub fork on the " rpi4b-refactor <https://github.com/UtkarshVerma/rtems/tree/rpi4b-refactor>" branch. Please have a look at it and let me know what could be improved. On Mon, Aug 7, 2023 at 10:19 AM Utkarsh Verma wrote: > T

[PATCH 2/2] bsps/aarch64/raspberrypi: Refactor code base

From: Utkarsh Verma Refactor the code base for better organization to facilitate future patches. --- .gitignore| 4 + bsps/aarch64/raspberrypi/console/console.c| 41 +- bsps/aarch64/raspberrypi/include/bsp.h| 33 +- .../aarch64/raspberrypi

[PATCH 1/2] bsps/aarch64/raspberrypi: Refactor code base

From: Utkarsh Verma Refactor the code base for better organization to facilitate future patches. --- .gitignore| 4 + bsps/aarch64/raspberrypi/console/console.c| 42 +- bsps/aarch64/raspberrypi/include/bsp.h| 33 +- .../aarch64/raspberrypi

[PATCH 0/2] Refactor aarch64/raspberrypi4b BSP

This patch refactors the Raspberry Pi 4B BSP with the following changes: - Build spec organization - IWYU(include what you use) includes - Self contained sources and headers - More specific MMU mapping - A basic API to allow extending this BSP to other variants of the RPi family Utkarsh Verma

Need community suggestions for a new generic GPIO API

Dear all, While working on the Raspberry Pi 4 BSP, I realized that the GPIO API could be improved. It seems that last year, a GSoC student worked on introducing a new GPIO API, called GPIO2 to RTEMS. However, it did not get merged. Discussing this topic with my mentor and on RTEMS Discord revealed

[PATCH 1/1] user/bsp/raspberrypi4: Fix incorrect config.txt typo

This commit removes spaces in config.txt which made it invalid. --- user/bsps/aarch64/raspberrypi4.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/user/bsps/aarch64/raspberrypi4.rst b/user/bsps/aarch64/raspberrypi4.rst index efb09b6..ad817aa 100644 --- a/user/bsps/aarch64/

[PATCH 0/1] Fix Raspberry Pi 4B's UART setup's config.txt

This is a simple patch fixing a typo made in the config.txt Utkarsh Verma (1): user/bsp/raspberrypi4: Fix incorrect config.txt typo user/bsps/aarch64/raspberrypi4.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) -- 2.41.0 ___ devel

[PATCH 0/1] Fix config.txt for Raspberry Pi 4B's UART setup

The config.txt included in the docs is invalid as it includes spaces in the parameter assignment. This patch fixes that typo by removing the spaces. Utkarsh Verma (1): user/bsps/raspberrypi4: Fix config.txt for UART setup user/bsps/aarch64/raspberrypi4.rst | 2 +- 1 file changed, 1 insertion

[PATCH 1/1] eng: Fix builds for newer Sphinx versions (>=7)

The current Sphinx theme depends on the `style` parameter which got deprecated in v5.1 and finally got removed in v7. Now, the `styles` key should be preferred which is a list of stylesheets. This commit implements this change. --- common/sphinx_rtd_theme_rtems/layout.html | 2 ++ 1 file changed,

[PATCH 0/1] eng: Fix builds for newer Sphinx versions (>=7)

The current Sphinx theme depends on the `style` parameter which got deprecated in v5.1 and finally got removed in v7. Now, the `styles` key should be preferred which is a list of stylesheets. This commit implements this change. Utkarsh Verma (1): eng: Fix builds for newer Sphinx versions (>

Re: [PATCH 0/1] Improve coherence of user/start docs

Hi, This is just a gentle reminder for this patch. Please let me know if I could improve anything. Regards, Utkarsh On Wed, Mar 29, 2023 at 6:08 AM Utkarsh Verma wrote: > This patch improves consistency of the documentation in the user/start > section. In app.rst, absolute path ha

GSoC Proposal Draft - Improve Raspberry Pi 4 BSP

I have drafted my GSoC proposal and uploaded it to Google Docs. You can leave suggestions as comments in the document. https://docs.google.com/document/d/1dL5zl_iSYeyx6ZoOpKjy-CkLh_OvgGDJvblrPH5q6rg/edit?usp=sharing I apologize for not giving you much time for this review. Regards, Utkarsh

[PATCH 1/1] bsp-howto: Fix grammar and improve coherence.

--- user/start/app.rst | 2 +- user/start/bsp-build.rst | 17 + 2 files changed, 6 insertions(+), 13 deletions(-) diff --git a/user/start/app.rst b/user/start/app.rst index ce9a44d..0599305 100644 --- a/user/start/app.rst +++ b/user/start/app.rst @@ -209,7 +209,7 @@ Run the

[PATCH 0/1] Improve coherence of user/start docs

directory as it is unnecessary. Apart from that, minor grammatical fixes have been made. Utkarsh Verma (1): bsp-howto: Fix grammar and improve coherence. user/start/app.rst | 2 +- user/start/bsp-build.rst | 17 + 2 files changed, 6 insertions(+), 13 deletions(-) -- 2.40.0

Improve docs for quickstart guide

Dear all, I have made a small patch to improve the documentation of the quickstart guide. Please have a look and let me know what you think. P.S.: This is my first patch so feel free to let me know if I made any mistakes. Regards, Utkarsh From 1377d30f47b22133f8514d2525d6390573e181ca Mon Sep 17

GSoC Contributor Introduction

asks I could contribute, and so on. Regards, Utkarsh Verma https://utkarshverma.me RTEMS Testing - Run, 6.0.not_released Command Line: /home/subaru/gsoc/rtems/rtems/6/bin//rtems-run --rtems-bsp=erc32-sis build/sparc-rtems6-erc32/hello.exe Host: Linux metia 6.2.7-arch1-1 #1 SMP PREEMPT_DYNAMIC Sat,

Re: GSoC Project - Beagle BSP Projects

task. > > Best, > Nils > > On Tue, 23 Mar 2021 at 17:00, Christian MAUDERER < > christian.maude...@embedded-brains.de> wrote: > >> Hello Gedare, >> >> Am 23.03.21 um 16:48 schrieb Gedare Bloom: >> > CC: Nils, Utkarsh >> > >> >

Re: GSoC project: Memory protection (Ticket no: 2904)

On Tue, Mar 23, 2021 at 5:49 PM Rajiv Vaidyanathan < rajiv.vaidyanath...@gmail.com> wrote: > Dear Utkarsh, > > Thank you for providing these links. I would like to know if these pending > tasks are long enough to take it up as a GSoC project. > > Resolving the issues r

Re: GSoC project: Memory protection (Ticket no: 2904)

topic > has been pursued a few times in GSoC. It would be great if someone can let > me know the current status of this project and guide me about what are the > contributions that can be done this year. > > > Yes, this is a frequently attempted project that slowly makes progress >

Re: Memory Protection related project for GSOC

On Sun, Feb 21, 2021 at 12:00 AM Gedare Bloom wrote: > Hi Sanskar, > > We had a student (Utkarsh) work on this project last year. I have CC'd > him here, and he may be able to suggest some ideas/updates. > > On Sat, Feb 20, 2021 at 7:17 AM Sanskar Khandelwal > wrot

Re: Report on failing tests with thread stack protection and their resolution.

On Tue, Jan 26, 2021 at 9:33 PM Gedare Bloom wrote: > > > On Tue, Jan 26, 2021 at 8:24 AM Sebastian Huber < > sebastian.hu...@embedded-brains.de> wrote: > >> On 23/01/2021 07:27, Utkarsh Rai wrote: >> >> > The issue that remains is of User extensi

Re: Report on failing tests with thread stack protection and their resolution.

On Sat, Jan 23, 2021 at 9:29 PM Joel Sherrill wrote: > > > On Sat, Jan 23, 2021, 12:28 AM Utkarsh Rai > wrote: > >> >> >> On Mon, Dec 7, 2020 at 8:00 AM Utkarsh Rai >> wrote: >> >>> >>> >>> On Thu, Dec 3, 2020 at 10:22 P

Re: Report on failing tests with thread stack protection and their resolution.

On Mon, Dec 7, 2020 at 8:00 AM Utkarsh Rai wrote: > > > On Thu, Dec 3, 2020 at 10:22 PM Gedare Bloom wrote: > >> >> >> On Wed, Dec 2, 2020 at 5:53 PM Utkarsh Rai >> wrote: >> >>> Hello, >>> As discussed in this >>> <h

Re: Report on failing tests with thread stack protection and their resolution.

On Thu, Dec 17, 2020 at 8:23 PM Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > Hello, > > On 03/12/2020 01:53, Utkarsh Rai wrote: > > +rtems_status_code _Memory_protection_Disable( void ) > > +{ > > + uint32_t access_flags; > >

Re: Report on failing tests with thread stack protection and their resolution.

On Thu, Dec 3, 2020 at 10:22 PM Gedare Bloom wrote: > > > On Wed, Dec 2, 2020 at 5:53 PM Utkarsh Rai > wrote: > >> Hello, >> As discussed in this >> <https://lists.rtems.org/pipermail/devel/2020-November/063341.html> thread, >> I have compiled a

Report on failing tests with thread stack protection and their resolution.

Hello, As discussed in this thread, I have compiled a list of the tests that deal with inter stack communication and fail with the thread stack protection option. Most of these tests pass when, as Sebastian suggested and had provid

Re: [PATCH v4 0/1] Test for clock_nanosleep() with CLOCK_MONOTONIC option

Hello, Is there any update on this patch? On Wed, Oct 28, 2020 at 7:04 PM Utkarsh Rai wrote: > Ping. > > On Wed, Oct 21, 2020 at 8:58 AM Utkarsh Rai > wrote: > >> This patch has the tests for clock_nanosleep with the CLOCK_MONOTONIC >> option. >> The psxtests

Re: Fatal exceptions on context-switching for more than two isolated threads

On Thu, Nov 19, 2020 at 11:39 PM Gedare Bloom wrote: > Hi Utkarsh, > > On Thu, Nov 19, 2020 at 4:59 AM Sebastian Huber > wrote: > > > > On 19/11/2020 11:47, Utkarsh Rai wrote: > > > > > There are a couple of other areas in RTEMS in which the stack of

Re: Fatal exceptions on context-switching for more than two isolated threads

On Thu, Nov 5, 2020 at 11:45 AM Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > On 04/11/2020 19:38, Gedare Bloom wrote: > > >> Based on the above suggestions I tried to move the > User_extensions_Iterator storage to the TCB by adding a new field to the > structure, but that did n

Re: [PATCH v4 0/1] Test for clock_nanosleep() with CLOCK_MONOTONIC option

On Thu, Nov 5, 2020 at 12:13 AM Gedare Bloom wrote: > i need to find time to look at this, and try it out. > > Does this compile? e.g., I don't see a definition of OPERATION_COUNT > Yes, the OPERATION_COUNT is defined in "timesys.h". > > On Wed, Oct 28, 202

Re: Fatal exceptions on context-switching for more than two isolated threads

On Fri, Oct 23, 2020 at 10:28 PM Utkarsh Rai wrote: > > > On Fri, Oct 23, 2020 at 9:57 PM Gedare Bloom wrote: > >> On Fri, Oct 23, 2020 at 9:37 AM Utkarsh Rai >> wrote: >> > >> > >> > >> > On Thu, Oct 22, 2020 at 11:23 PM Se

Re: [PATCH v4 0/1] Test for clock_nanosleep() with CLOCK_MONOTONIC option

Ping. On Wed, Oct 21, 2020 at 8:58 AM Utkarsh Rai wrote: > This patch has the tests for clock_nanosleep with the CLOCK_MONOTONIC > option. > The psxtests/psxclocknanosleep01/.. tests for valid timeout values as well > as > for the effect on timeout delay when REALTIME clock

Re: Fatal exceptions on context-switching for more than two isolated threads

On Fri, Oct 23, 2020 at 9:57 PM Gedare Bloom wrote: > On Fri, Oct 23, 2020 at 9:37 AM Utkarsh Rai > wrote: > > > > > > > > On Thu, Oct 22, 2020 at 11:23 PM Sebastian Huber < > sebastian.hu...@embedded-brains.de> wrote: > >> > >> On 22/

Re: Fatal exceptions on context-switching for more than two isolated threads

On Thu, Oct 22, 2020 at 11:23 PM Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > On 22/10/2020 02:40, Utkarsh Rai wrote: > > > Hello, this thread has gone a bit cold over the last few weeks, due to > > my engagement in the university tests. I have provid

Re: Fatal exceptions on context-switching for more than two isolated threads

been set to NO-ACCESS during the context switch. Is there any work-around to this? On Tue, Sep 22, 2020 at 8:28 PM Utkarsh Rai wrote: > > > > On Mon, Sep 21, 2020 at 10:29 PM Gedare Bloom wrote: > >> On Sat, Sep 19, 2020 at 5:41 AM Utkarsh Rai >> wrote: >>

[PATCH v4 0/1] Test for clock_nanosleep() with CLOCK_MONOTONIC option

(yielding and blocking). Utkarsh Rai (1): Test for clock_nanosleep() with CLOCK_MONOTONIC option .../psxtests/psxclocknanosleep01.yml | 19 +++ spec/build/testsuites/psxtmtests/grp.yml | 4 + .../psxtmtests/psxtmclocknanosleep04.yml | 19 +++ .../psxtmtests

[PATCH v4 1/1] Test for clock_nanosleep() with CLOCK_MONOTONIC option

-SA-4.0 OR BSD-2-Clause +build-type: test-program +cflags: [] +copyrights: +- Copyright (C) 2020 Utkarsh Rai(utkarsh.ra...@gmail.com) +cppflags: [] +cxxflags: [] +enabled-by: true +features: c cprogram +includes: [] +ldflags: [] +links: [] +source: +- testsuites/psxtests/psxclocknanosleep01/init.c

Error while using the trace linker

Hello, I am following the tracing example as mentioned in the docs <https://docs.rtems.org/branches/master/user/tracing/examples.html> for sparc/erc32 BSP. When I run the "rtems-tld" command, I get the following error - "error: /home/utkarsh/sandbox/bsps/sparc: Invalid RTEM

Re: [PATCH v4] Test for clock_nanosleep() with CLOCK_MONOTONIC option

On Mon, Sep 28, 2020 at 9:58 PM Gedare Bloom wrote: > Hi Utkarsh, > > I was starting to review this, but then I got a little bit confused by > what you have done. > > I think you may have gone down the wrong path to do this work. It > looks like you copied from libtests/ttes

Re: [PATCH v4] Test for clock_nanosleep() with CLOCK_MONOTONIC option

Hello, Can someone please review this. I would like to work on the suggested changes over the weekend. On Mon, Sep 21, 2020 at 8:45 PM Utkarsh Rai wrote: > From: Utkarsh > > Closes #3890 > > Signed-off-by: Utkarsh Rai > --- > spec/build/testsuites/psxtests

Re: Fatal exceptions on context-switching for more than two isolated threads

On Mon, Sep 21, 2020 at 10:29 PM Gedare Bloom wrote: > On Sat, Sep 19, 2020 at 5:41 AM Utkarsh Rai > wrote: > > > > Hello, > > When I isolate more than two threads in RTEMS (the implementation can be > found here), I get fatal exceptions while context-switching. On st

[PATCH v4] Test for clock_nanosleep() with CLOCK_MONOTONIC option

From: Utkarsh Closes #3890 Signed-off-by: Utkarsh Rai --- spec/build/testsuites/psxtests/grp.yml| 2 + .../psxtests/psxclocknanosleep01.yml | 20 +++ .../psxtests/psxclocknanosleep01/init.c | 94 ++ .../psxclocknanosleep01.doc | 13

Fatal exceptions on context-switching for more than two isolated threads

Hello, When I isolate more than two threads in RTEMS (the implementation can be found here ), I get fatal exceptions while context-switching. On stepping into the code, the problem seems to be with the _User_extensions_T

Re: devel Digest, Vol 106, Issue 81

On Mon, Sep 14, 2020 at 5:30 PM wrote: > Send devel mailing list submissions to > devel@rtems.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.rtems.org/mailman/listinfo/devel > or, via email, send a message with subject or body 'help' to >

Re: How to use _Thread_Get() function properly?

Thanks, I'll check it out. On Mon, Aug 31, 2020 at 11:35 PM Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > On 31/08/2020 19:52, Utkarsh Rai wrote: > > > Hello, > > I have been trying to get the pointer to the control block of a thread > > u

How to use _Thread_Get() function properly?

Hello, I have been trying to get the pointer to the control block of a thread using the _Thread_Get() function for stack sharing using a shared-memory object, the implementation can be seen here . The problem is when

Re: GSoC 2020 - Final project report

n, Aug 30, 2020 at 4:55 AM Utkarsh Rai > wrote: > > > > I have updated my post with the help of all of your suggestions. As > @Niteesh G. S. said, sorry to disturb you on a weekend but please take a > look. > > > > On Sat, Aug 29, 2020 at 6:03 PM Utkarsh Rai > wrote

Re: GSoC 2020 - Final project report

I have updated my post with the help of all of your suggestions. As @Niteesh G. S. said, sorry to disturb you on a weekend but please take a look. On Sat, Aug 29, 2020 at 6:03 PM Utkarsh Rai wrote: > > > On Sat, Aug 29, 2020 at 3:59 PM Hesham Almatary < > hesham.almat...@cl.c

Re: GSoC 2020 - Final project report

On Sat, Aug 29, 2020 at 3:59 PM Hesham Almatary < hesham.almat...@cl.cam.ac.uk> wrote: > Hello Utkarsh, > > Thanks for the blog post. Are there any instructions on how can > someone (maybe a future GSoC student or someone else interested) get > your code tested (with tes

Re: GSoC 2020 - Final project report

On Sat, Aug 29, 2020 at 4:18 AM Gedare Bloom wrote: > Similarly, I would like to have a consolidated set of links to "your > code" instead of having them woven in with the narrative and links to > blogs etc. > > Ok, I will do that. > On Thu, Aug 27, 2020 at

GSoC 2020 - Final project report

Hello, I have prepared a tentative final report for my project. You can view it here . Note there are few changes to be made in the report based on my progress this week as I am working on static initialization of PMP and

Re: mmap shared stack design was: [PATCH v4 1/3] Strict thread-stack isolation

On Mon, Aug 24, 2020 at 9:34 PM Gedare Bloom wrote: > On Sat, Aug 22, 2020 at 11:27 PM Utkarsh Rai > wrote: > > > > > > > > On Sat, Aug 22, 2020 at 11:32 PM Gedare Bloom wrote: > >> > >> I have some comments below. I'm not that happy with th

Re: [PATCH v4 1/3] Strict thread-stack isolation

o also comment on stylistic problems, and when some decisions you > make while coding end up not being correct or aren't easily understood > during code review then you might have to spend more time recoding. It > can be hard to find the balance between design and code reviews, > > On Sat

[PATCH v4 1/3] Strict thread-stack isolation

/ + +/* + * Copyright (C) 2020 Utkarsh Rai + * + * Redistribution and use in source and binary forms, with or without + * modification, are permitted provided that the following conditions + * are met: + * 1. Redistributions of source code must retain the above copyright + *notice, this list o

[PATCH v4 2/3] High level configuration option for thread stack protection

-4.0 OR BSD-2-Clause +actions: +- get-boolean: null +- env-enable: null +- define-condition: null +build-type: option +copyrights: +- Copyright (C) 2020 Utkarsh Rai (utkarsh.ra...@gmail.com) +default: false +default-by-variant: [] +description: | + Enable the thread stack protection support +enabled

[PATCH v4 3/3] Thread stack sharing

For the design details of the stack sharing mechanism please refer to the following post - https://gsoc2020memoryprotection.blogspot.com/2020/08/high-level-design-and-implementation-of.html --- cpukit/posix/src/mmap.c | 39 - cpukit/posix/src/shmopen.c

Re: Context switching through an ISR in RTEMS

On Mon, Aug 17, 2020 at 10:12 PM Gedare Bloom wrote: > On Mon, Aug 17, 2020 at 10:30 AM Utkarsh Rai > wrote: > > > > > > > > On Mon, Aug 17, 2020 at 9:24 PM Gedare Bloom wrote: > >> > >> On Mon, Aug 17, 2020 at 5:53 AM Utkarsh Rai > wrote:

Re: Context switching through an ISR in RTEMS

On Mon, Aug 17, 2020 at 9:24 PM Gedare Bloom wrote: > On Mon, Aug 17, 2020 at 5:53 AM Utkarsh Rai > wrote: > > > > > > > > On Mon, Aug 17, 2020 at 11:32 AM Sebastian Huber < > sebastian.hu...@embedded-brains.de> wrote: > >

Re: Context switching through an ISR in RTEMS

On Mon, Aug 17, 2020 at 11:32 AM Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > On 16/08/2020 18:09, Utkarsh Rai wrote: > > > > > > > On Sun, Aug 16, 2020 at 9:18 PM Gedare Bloom > <mailto:ged...@rtems.org>> wrote: > > >

Re: Context switching through an ISR in RTEMS

On Sun, Aug 16, 2020 at 9:18 PM Gedare Bloom wrote: > On Sat, Aug 15, 2020 at 9:03 PM Utkarsh Rai > wrote: > > > > > > > > On Sun, Aug 16, 2020 at 6:12 AM Utkarsh Rai > wrote: > >> > >> > >> > >> On Sat, Aug 15, 2020 at 7:2

Re: Context switching through an ISR in RTEMS

On Sun, Aug 16, 2020 at 6:12 AM Utkarsh Rai wrote: > > > On Sat, Aug 15, 2020 at 7:26 PM Gedare Bloom wrote: > >> On Sat, Aug 15, 2020 at 6:26 AM Utkarsh Rai >> wrote: >> > >> > >> > On Thu, Aug 13, 2020 at 5:10 AM Utkarsh Rai >> wrote

Re: Context switching through an ISR in RTEMS

On Sat, Aug 15, 2020 at 7:26 PM Gedare Bloom wrote: > On Sat, Aug 15, 2020 at 6:26 AM Utkarsh Rai > wrote: > > > > > > On Thu, Aug 13, 2020 at 5:10 AM Utkarsh Rai > wrote: > >> > >> Thanks, I'll check them out. > >> > >> On T

Re: Context switching through an ISR in RTEMS

On Thu, Aug 13, 2020 at 5:10 AM Utkarsh Rai wrote: > Thanks, I'll check them out. > > On Thu, Aug 13, 2020 at 12:56 AM Gedare Bloom wrote: > >> On Wed, Aug 12, 2020 at 11:33 AM Utkarsh Rai >> wrote: >> > >> > Hello, >> > I have been te

Re: [PATCH] Strict thread-stack isolation and thread-stack sharing.

On Sat, Aug 15, 2020 at 12:39 AM Gedare Bloom wrote: > On Fri, Aug 14, 2020 at 9:25 AM Utkarsh Rai > wrote: > > > > Sorry for the late reply, I somehow missed the mail notification! > > > > On Thu, Aug 13, 2020 at 9:35 PM Gedare Bloom wrote: > >> >

Re: [PATCH] Strict thread-stack isolation and thread-stack sharing.

Sorry for the late reply, I somehow missed the mail notification! On Thu, Aug 13, 2020 at 9:35 PM Gedare Bloom wrote: > On Thu, Aug 13, 2020 at 9:06 AM Utkarsh Rai > wrote: > > > > -This patch provides thread-stack isolation and thread-stack sharing > > mech

[PATCH] Strict thread-stack isolation and thread-stack sharing.

evel memory protection + * + */ + +/* + * Copyright (C) 2020 Utkarsh Rai + * + * Redistribution and use in source and binary forms, with or without + * modification, are permitted provided that the following conditions + * are met: + * 1. Redistributions of source code must retain the above copyrig

Strict thread stack isolation and sharing

Following is the complete set of changes for thread stack isolation and sharing. Configuration for thread stack isolation. > The configuration for thread stack isolation is based upon the new build system. > The RTEMS_THREAD_STACK_PROTECTION option needs to be specified and set to 'True' for en

Re: Context switching through an ISR in RTEMS

Thanks, I'll check them out. On Thu, Aug 13, 2020 at 12:56 AM Gedare Bloom wrote: > On Wed, Aug 12, 2020 at 11:33 AM Utkarsh Rai > wrote: > > > > Hello, > > I have been testing my code for thread stack isolation against various > tests( Some written by me, and

Re: [PATCH v2] Test for clock_nanosleep with CLOCK_MONOTONIC option.

t;>> On Tue, Apr 14, 2020 at 10:56 PM Sebastian Huber >>> wrote: >>> > >>> > Hello Utkarsh Rai, >>> > >>> > do we really need a new test program for this test case? I would prefer >>> > add it to an existing test program o

Context switching through an ISR in RTEMS

Hello, I have been testing my code for thread stack isolation against various tests( Some written by me, and remaining already present). One of the limitations that I have found is that I encounter fatal errors whenever a context switch takes place through an ISR. Can you please explain how the con

Re: Configuration option for thread-stack protection.

On Thu, Aug 6, 2020 at 8:34 PM Gedare Bloom wrote: > On Thu, Aug 6, 2020 at 6:21 AM Sebastian Huber > wrote: > > > > On 06/08/2020 14:12, Utkarsh Rai wrote: > > > > > Hello, > > > The thread-stack protection needs to be configured by the user. Two

Configuration option for thread-stack protection.

Hello, The thread-stack protection needs to be configured by the user. Two of the options that need configuring during build time are - > Enabling thread stack protection ( THREAD_STACK_PROTECTION )- This is a high-level option similar to RTEMS_SMP, RTEMS_POSIX_API etc. > Size of the MMU pages - T

Re: Error while building realview_pbx_a9 BSP with the new build system

n Mon, Aug 3, 2020 at 10:47 PM Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > On 03/08/2020 18:32, Gedare Bloom wrote: > > > On Mon, Aug 3, 2020 at 10:27 AM Sebastian Huber > > wrote: > >> On 03/08/2020 18:25, Gedare Bloom wrote: > >> &g

Re: Error while building realview_pbx_a9 BSP with the new build system

On Mon, Aug 3, 2020 at 9:56 PM Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > On 03/08/2020 18:17, Utkarsh Rai wrote: > > > When I use the above branch I get the following error on './waf > > install ' - > > > > Build failed >

  1   2   3   >