Re: [PATCH v2] news/2023-q3.mdwn: new file.
Applied, thanks! jbra...@dismail.de, le dim. 14 janv. 2024 20:15:58 -0500, a ecrit: > New qoth file. Rust port, SMP work, 64-bit port, mmap work, etc. > > I added some comments mention that Damien's SMP work is based on > Almudena previous work. Thanks for than Almudena! > --- > news/2023-q3.mdwn | 193 ++ > 1 file changed, 193 insertions(+) > create mode 100644 news/2023-q3.mdwn > > diff --git a/news/2023-q3.mdwn b/news/2023-q3.mdwn > new file mode 100644 > index ..8050ce98 > --- /dev/null > +++ b/news/2023-q3.mdwn > @@ -0,0 +1,193 @@ > +[[!meta copyright="Copyright © 2013 Free Software Foundation, Inc."]] > + > +[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable > +id="license" text="Permission is granted to copy, distribute and/or modify > this > +document under the terms of the GNU Free Documentation License, Version 1.2 > or > +any later version published by the Free Software Foundation; with no > Invariant > +Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the > license > +is included in the section entitled [[GNU Free Documentation > +License|/fdl]]."]]"""]] > + > +[[!meta date="2024-01-01 22:22 UTC"]] > + > +Hello! Welcome to a new qoth. This qoth covers new and interesting GNU/Hurd > +developments in Q3 of 2023! > +[[!if test="included()" then="""[[!toggle id=full_news > +text="Details."]][[!toggleable id=full_news text="[[!paste > id=full_news]]"]]""" > +else=" > +[[!paste id=full_news]]"]] > + > +[[!cut id="full_news" text=""" > + > +Joan Lledo modified the PCI arbiter to prevent mapping I/O region > +files. He previously sent some patches to implement mapping region > +and ROM files using `mmap()`. However, a `BAR` region can represent > +either memory or I/O space, and only memory should be allowed to be > +mapped. Since I/O `BARs` only contain I/O addresses, he went ahead > +and [[prevented the mapping of I/O region > +files|https://lists.gnu.org/archive/html/bug-hurd/2023-07/msg00041.html]]. > The > +next step is to make IO spaces available for users through the > +pci-arbiter. He plans to add a new RPC that checks for permission and > +calls `i386_io_perm_create()`. Then it returns the resulting port. > + > +Our Google summer of code student Vedant Tewari decided to port rust, > +and the rust porting effort is making good progress. [[The build > +process is a bit > +wonky|https://lists.gnu.org/archive/html/bug-hurd/2023-08/msg00091.html]], > +and we are using an older rust version. Check out [[the rust pull > +request|https://github.com/rust-lang/rust/pull/115230]] that adds Hurd > +support! > + > +[[Samuel|samuelthibault]] worked on setting up > +[[PAE|https://en.wikipedia.org/wiki/Physical_Address_Extension]], > +which will eventually let us use more than 4GB of RAM on a 32-bit > +Hurd! It is also useful for the X86_64 architecture. He also the > +[[jemalloc|https://lists.debian.org/debian-hurd/2023/08/msg0.html]] > +build. > + > +Samuel was incredibly productive this quarter making the `X86_64` bit > +port more stable. He fixed the 64-bit Hurd [[ > +PIE|https://lists.gnu.org/archive/html/bug-hurd/2023-08/msg00040.html]] > +build, and he got [[git > +working|https://lists.gnu.org/archive/html/bug-hurd/2023-08/msg00059.html]] > +on the 64-bit port! Though a few of the [[git > +tests|https://lists.gnu.org/archive/html/bug-hurd/2023-08/msg00069.html]] > +are failing on both `X86_64` and the 32 bit port. He fixed the [[glibc > +build|https://lists.gnu.org/archive/html/bug-hurd/2023-08/msg00064.html]], > +which involved fixing `pmap_remove` and `pmap_protect`. He discovered > +that [[core dumping is currently causing > +problems|https://lists.gnu.org/archive/html/bug-hurd/2023-08/msg00068.html]] > +on the 64-bit port, and he temporarily encourages people to disable > +core dumping. Samuel fixed some [[networking > +issues|https://lists.gnu.org/archive/html/bug-hurd/2023-08/msg00027.html]] > +and a [[dpkg > +issue|https://lists.gnu.org/archive/html/bug-hurd/2023-08/msg00058.html]] > +for the 64-bit port. It was hard to discover what the problem was, > +because the debugging tools have not been ported to the 64-bit port. > +He used some locking to fix some bugs, and he encourages other > +developers to help him fix the debugging tools for X86-64. It seems > +that most developers are currently running the 64-bit Hurd in a > +virtual machine and not in real hardware. > + > +Luca Dariz got a patch series merged > +[[for|https://lists.gnu.org/archive/html/bug-hurd/2023-08/msg0.html]] > +[[the|https://lists.gnu.org/archive/html/bug-hurd/2023-08/msg1.html]] > +[[64|https://lists.gnu.org/archive/html/bug-hurd/2023-08/msg2.html]] > +[[bit|https://lists.gnu.org/archive/html/bug-hurd/2023-08/msg3.html]] > +[[port|https://lists.gnu.org/archive/html/bug-hurd/2023-08/msg4.html]]. > + > +Sergey implemented > +[[MAP_EXCL|https://lists.gnu.org/archive/html/bug-hurd/2023-0
[PATCH v2] news/2023-q3.mdwn: new file.
New qoth file. Rust port, SMP work, 64-bit port, mmap work, etc. I added some comments mention that Damien's SMP work is based on Almudena previous work. Thanks for than Almudena! --- news/2023-q3.mdwn | 193 ++ 1 file changed, 193 insertions(+) create mode 100644 news/2023-q3.mdwn diff --git a/news/2023-q3.mdwn b/news/2023-q3.mdwn new file mode 100644 index ..8050ce98 --- /dev/null +++ b/news/2023-q3.mdwn @@ -0,0 +1,193 @@ +[[!meta copyright="Copyright © 2013 Free Software Foundation, Inc."]] + +[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable +id="license" text="Permission is granted to copy, distribute and/or modify this +document under the terms of the GNU Free Documentation License, Version 1.2 or +any later version published by the Free Software Foundation; with no Invariant +Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license +is included in the section entitled [[GNU Free Documentation +License|/fdl]]."]]"""]] + +[[!meta date="2024-01-01 22:22 UTC"]] + +Hello! Welcome to a new qoth. This qoth covers new and interesting GNU/Hurd +developments in Q3 of 2023! +[[!if test="included()" then="""[[!toggle id=full_news +text="Details."]][[!toggleable id=full_news text="[[!paste id=full_news]]"]]""" +else=" +[[!paste id=full_news]]"]] + +[[!cut id="full_news" text=""" + +Joan Lledo modified the PCI arbiter to prevent mapping I/O region +files. He previously sent some patches to implement mapping region +and ROM files using `mmap()`. However, a `BAR` region can represent +either memory or I/O space, and only memory should be allowed to be +mapped. Since I/O `BARs` only contain I/O addresses, he went ahead +and [[prevented the mapping of I/O region +files|https://lists.gnu.org/archive/html/bug-hurd/2023-07/msg00041.html]]. The +next step is to make IO spaces available for users through the +pci-arbiter. He plans to add a new RPC that checks for permission and +calls `i386_io_perm_create()`. Then it returns the resulting port. + +Our Google summer of code student Vedant Tewari decided to port rust, +and the rust porting effort is making good progress. [[The build +process is a bit +wonky|https://lists.gnu.org/archive/html/bug-hurd/2023-08/msg00091.html]], +and we are using an older rust version. Check out [[the rust pull +request|https://github.com/rust-lang/rust/pull/115230]] that adds Hurd +support! + +[[Samuel|samuelthibault]] worked on setting up +[[PAE|https://en.wikipedia.org/wiki/Physical_Address_Extension]], +which will eventually let us use more than 4GB of RAM on a 32-bit +Hurd! It is also useful for the X86_64 architecture. He also the +[[jemalloc|https://lists.debian.org/debian-hurd/2023/08/msg0.html]] +build. + +Samuel was incredibly productive this quarter making the `X86_64` bit +port more stable. He fixed the 64-bit Hurd [[ +PIE|https://lists.gnu.org/archive/html/bug-hurd/2023-08/msg00040.html]] +build, and he got [[git +working|https://lists.gnu.org/archive/html/bug-hurd/2023-08/msg00059.html]] +on the 64-bit port! Though a few of the [[git +tests|https://lists.gnu.org/archive/html/bug-hurd/2023-08/msg00069.html]] +are failing on both `X86_64` and the 32 bit port. He fixed the [[glibc +build|https://lists.gnu.org/archive/html/bug-hurd/2023-08/msg00064.html]], +which involved fixing `pmap_remove` and `pmap_protect`. He discovered +that [[core dumping is currently causing +problems|https://lists.gnu.org/archive/html/bug-hurd/2023-08/msg00068.html]] +on the 64-bit port, and he temporarily encourages people to disable +core dumping. Samuel fixed some [[networking +issues|https://lists.gnu.org/archive/html/bug-hurd/2023-08/msg00027.html]] +and a [[dpkg +issue|https://lists.gnu.org/archive/html/bug-hurd/2023-08/msg00058.html]] +for the 64-bit port. It was hard to discover what the problem was, +because the debugging tools have not been ported to the 64-bit port. +He used some locking to fix some bugs, and he encourages other +developers to help him fix the debugging tools for X86-64. It seems +that most developers are currently running the 64-bit Hurd in a +virtual machine and not in real hardware. + +Luca Dariz got a patch series merged +[[for|https://lists.gnu.org/archive/html/bug-hurd/2023-08/msg0.html]] +[[the|https://lists.gnu.org/archive/html/bug-hurd/2023-08/msg1.html]] +[[64|https://lists.gnu.org/archive/html/bug-hurd/2023-08/msg2.html]] +[[bit|https://lists.gnu.org/archive/html/bug-hurd/2023-08/msg3.html]] +[[port|https://lists.gnu.org/archive/html/bug-hurd/2023-08/msg4.html]]. + +Sergey implemented +[[MAP_EXCL|https://lists.gnu.org/archive/html/bug-hurd/2023-07/msg00010.html]] +and provided `MAP_FIXED_NOREPLACE` and `MAP_TRYFIXED` as aliases of +`(MAP_FIXED|MAP_EXCL)` as well other `mmap` work. He explains: + +> `MAP_FIXED` is defined to silently replace any existing mappings at +> the address range being mapped over. However, this is dangerous a
