unsubscribe

unsubscribe

[marduk]

unsubscribe kernelnewbies

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20110106/4fcfedd9/attachment.html 

unsubscribe

[GMAIL]

unsubscribe

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20130911/dc13c3c6/attachment.html 

unsubscribe

[GMAIL]

unsubscribe

 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20130915/385e6398/attachment.html 

unsubscribe

[Daniel Kranich]

unsubscribe

[고영준]

unsubscribe
 
?????ohojang?? ???
????? ??????
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20161005/31223606/attachment.html 

unsubscribe

[조동석]

An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20161205/bb7ead76/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 13402 bytes
Desc: not available
Url : http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20161205/bb7ead76/attachment-0001.gif 

unsubscribe

[조동석]

An HTML attachment was scrubbed...
URL: <http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20180128/2b24fa0e/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 13402 bytes
Desc: not available
URL: <http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20180128/2b24fa0e/attachment.gif>

CONFIG_XXX vs CONFIG_HAVE_XXX ?

[Alexandre Ferrieux]

Hi,

What is the rationale behind having, for some feature XXX, both configuration
macros CONFIG_XXX and CONFIG_HAVE_XXX ?

For example, I'd love to use ftrace's new life-saving feature "funcgraph-retval"
(which instantly shows the root cause of an error returned from a fully graphed
function). Unfortunately, on all recent Debians the config says:

  CONFIG_HAVE_FUNCTION_GRAPH_RETVAL=y
  # CONFIG_FUNCTION_GRAPH_RETVAL is not set

As a result, the feature is not available. Okay, I'll just enable and recompile.
However, I'm wondering why in the first place such a situation is possible: what
is the intention there ? Either we want the feature, or we don't (e.g. because
it may incur some CPU or memory overhead), but why sit halfway in between ?

Thanks in advance,

-Alex

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

संदर्भ: CONFIG_XXX vs CONFIG_HAVE_XXX ?

[Siddh Raman Pant]

Sun, 18 May 2025 23:15:13 +0530 को alexandre.ferrieux@gmail.com ने लिखा :
> What is the rationale behind having, for some feature XXX, both configuration
> macros CONFIG_XXX and CONFIG_HAVE_XXX ?


CONFIG_HAVE_XXX -> XXX is supported.
CONFIG_XXX -> Enable XXX.


XXX may not be available on an arch, for eg.


Thanks,
Siddh


[Sorry for duplicate, pressed reply instead of reply all :P]



_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

unsubscribe

[Mrunal Gawade]

[-- Attachment #1.1: Type: text/plain, Size: 725 bytes --]

On Sun, May 18, 2025 at 8:25 PM Siddh Raman Pant <sanganaka@siddh.me> wrote:

> Sun, 18 May 2025 23:15:13 +0530 को alexandre.ferrieux@gmail.com ने लिखा :
> > What is the rationale behind having, for some feature XXX, both
> configuration
> > macros CONFIG_XXX and CONFIG_HAVE_XXX ?
>
>
> CONFIG_HAVE_XXX -> XXX is supported.
> CONFIG_XXX -> Enable XXX.
>
>
> XXX may not be available on an arch, for eg.
>
>
> Thanks,
> Siddh
>
>
> [Sorry for duplicate, pressed reply instead of reply all :P]
>
>
>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies@kernelnewbies.org
> https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>

[-- Attachment #1.2: Type: text/html, Size: 1360 bytes --]

[-- Attachment #2: Type: text/plain, Size: 170 bytes --]

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

unsubscribe

[Mrunal Gawade]

[-- Attachment #1.1: Type: text/plain, Size: 725 bytes --]

On Sun, May 18, 2025 at 8:25 PM Siddh Raman Pant <sanganaka@siddh.me> wrote:

> Sun, 18 May 2025 23:15:13 +0530 को alexandre.ferrieux@gmail.com ने लिखा :
> > What is the rationale behind having, for some feature XXX, both
> configuration
> > macros CONFIG_XXX and CONFIG_HAVE_XXX ?
>
>
> CONFIG_HAVE_XXX -> XXX is supported.
> CONFIG_XXX -> Enable XXX.
>
>
> XXX may not be available on an arch, for eg.
>
>
> Thanks,
> Siddh
>
>
> [Sorry for duplicate, pressed reply instead of reply all :P]
>
>
>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies@kernelnewbies.org
> https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>

[-- Attachment #1.2: Type: text/html, Size: 1360 bytes --]

[-- Attachment #2: Type: text/plain, Size: 170 bytes --]

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

Re: CONFIG_XXX vs CONFIG_HAVE_XXX ?

[Alexandre Ferrieux]

On 18/05/2025 20:22, Siddh Raman Pant wrote:
> Sun, 18 May 2025 23:15:13 +0530  alexandre.ferrieux@gmail.com :
>> What is the rationale behind having, for some feature XXX, both configuration
>> macros CONFIG_XXX and CONFIG_HAVE_XXX ?
> 
> 
> CONFIG_HAVE_XXX -> XXX is supported.
> CONFIG_XXX -> Enable XXX.
> 
> 
> XXX may not be available on an arch, for eg.

Ah yes, so the *_HAVE_* series are automatically-detected compatibility hints,
rather than actual human-selectable configuration decisions. Makes sense, thanks!

-Alex

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

unsubscribe

[Mrunal Gawade]

[-- Attachment #1.1: Type: text/plain, Size: 2779 bytes --]

On Mon, May 19, 2025 at 9:27 PM Vikram R <vikram@karlexai.com> wrote:

> ASIOS – Envisioned to Host and Sustain Cognition & Synthetic Intelligence
> The world’s first AI-native operating system.
>
> ASIOS is a new class of OS built on Ubuntu 24.04 LTS, designed from
> first principles for AI workloads. We’re creating the foundational
> infrastructure layer to support ever-more sophisticated
> intelligence—from today’s deep-learning models to tomorrow’s advanced
> cognitive and quantum-ready AI.
>
> Building on our May 3 thread, we’ve landed a resilient config-overlay
> and build script for ASIOS on both x86_64 and aarch64. Key artifacts:
>
> asios-config-overlay.sh: idempotent Kconfig overlay that tolerates
> missing symbols
> build-asios-kernel.sh: automated clone to config to compile workflow
> test-asios-config.sh: verifies .config flags post build
> Initial perf on Ubuntu 24.04 HWE 6.11:
> x86_64: mbw=7.3 GB/s, hackbench=53 ms, fio=1.6 GB/s
> arm64: mbw=27.4 GB/s, hackbench=4.8 ms, fio=3.2 GB/s
>
> GitHub (scripts and tests): https://github.com/asi-os/asios-core/
> Discord: https://discord.gg/rWuU7cWU4E
>
> Areas for review and test:
> 1. Overlay logic: skipping versus failing on absent Kconfig symbols
> 2. Build-matrix logic: host-only versus cross-build
> 3. Test completeness: missing flags
> 4. Scripting style and robustness
>
> Any pointers or suggestions are highly appreciated before we push to a
> formal RFC series.
>
> —
> Vikram R
> Founder & CEO, KarLex AI, Inc.
> https://asios.ai
>
>
> On Sat, May 3, 2025 at 12:22 PM Vikram R <vikram@karlexai.com> wrote:
> >
> > ASIOS is a new AI‑native OS (Ubuntu 24.04 LTS base) bringing
> > deterministic scheduling, NUMA‑GPU optimizations, zero‑copy I/O, and
> > eBPF telemetry into the Linux kernel.
> >
> > Key directions—
> > — Deterministic CPU scheduling for reproducible AI runs
> > — NUMA‑aware memory placement tuned for GPU DMA
> > — Zero‑copy GPU I/O via GPUDirect RDMA/Storage
> > — eBPF‑based telemetry hooks
> >
> > **Call for contributors:** scheduler/MM, GPU/accelerator integration,
> > eBPF instrumentation.
> >
> > Project links—
> > GitHub: <https://github.com/asi-os>
> > Discord: <https://discord.gg/rWuU7cWU4E>
> > Roadmap: <
> https://github.com/asi-os/asios-docs/blob/main/docs/ARCHITECTURE.md>
> >
> > Please reply on‑list with questions or join us on Discord to dive into
> > the design.
> >
> > Vikram Karlex R
> > KarLex AI, Inc. | <https://asios.ai> | <https://karlex.ai>
>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies@kernelnewbies.org
> https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>

[-- Attachment #1.2: Type: text/html, Size: 4216 bytes --]

[-- Attachment #2: Type: text/plain, Size: 170 bytes --]

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies