Re: VirtIO MMIO for amd64

2023-12-19 Thread Emile 'iMil' Heitor
On 12/20/23 06:55, Emile 'iMil' Heitor wrote: Well that's the thing, I can't find where does MMIO attaches on FreeBSD, they have a very simple way of creating the resources: After a bit of digging, their virtio_mmio device attaches to "nexus0", which if I understand correctly, is our

Re: VirtIO MMIO for amd64

2023-12-19 Thread Emile 'iMil' Heitor
On 12/19/23 13:11, Taylor R Campbell wrote: to queue a task and then run it. Normally softint_schedule is called from a hard interrupt handler. Here, you need something in the host to get hard interrupts. For example, on ACPI systems there are ACPI interrupt resources that can be used with

Re: _KERNEL_OPT and 0x6e074def

2023-12-19 Thread Jason Thorpe
> On Dec 19, 2023, at 10:33 AM, Jason Thorpe wrote: > > >> On Dec 19, 2023, at 10:01 AM, Edgar Fuß wrote: >> >> 0x6e074def > > the-ripe-vessel:thorpej 99$ grep UNDEFINED * > mkheaders.c:#define UNDEFINED ('n' << 24 | 0 << 20 | 't' << 12 | 0xdefU) > mkheaders.c:/* Value for defined

Re: _KERNEL_OPT and 0x6e074def

2023-12-19 Thread Jason Thorpe
> On Dec 19, 2023, at 10:01 AM, Edgar Fuß wrote: > > 0x6e074def the-ripe-vessel:thorpej 99$ grep UNDEFINED * mkheaders.c:#define UNDEFINED ('n' << 24 | 0 << 20 | 't' << 12 | 0xdefU) mkheaders.c:/* Value for defined options with value UNDEFINED */ mkheaders.c: return (unsigned int)(h !=

Re: _KERNEL_OPT and 0x6e074def

2023-12-19 Thread Paul Goyette
On Tue, 19 Dec 2023, Edgar Fu? wrote: What's the point of #include'ing opt_foobar.h only if _KERNEL_OPT is defined and what's magic about 0x6e074def? The opt_* files only exist when building a kernel. They do not exist when building loadable modules. In the module case, any options needed

_KERNEL_OPT and 0x6e074def

2023-12-19 Thread Edgar Fuß
What's the point of #include'ing opt_foobar.h only if _KERNEL_OPT is defined and what's magic about 0x6e074def?

Re: Change max ttys from 8 to 12?

2023-12-19 Thread Michael van Elst
u...@stderr.spb.ru (Valery Ushakov) writes: >Switching from a fixed size array to a dynamic one is probably not too >much work either. But then, overall, I think that trying to make the >kernel substitute for screen, tmux (in base), etc is kinda dead end, >so I'd rather we don't encourage it.

Re: Change max ttys from 8 to 12?

2023-12-19 Thread Valery Ushakov
On Tue, Dec 19, 2023 at 11:10:52 +0100, Dan-Simon Myrland wrote: > 2) Make a custom kernel with the option WSDISPLAY_DEFAULTSCREENS=12 Why? WSDISPLAY_DEFAULTSCREENS is the number of screens pre-created by the kernel, but you can always create as many as you need (subject to

Re: VirtIO MMIO for amd64

2023-12-19 Thread Taylor R Campbell
> Date: Tue, 19 Dec 2023 08:55:32 +0100 > From: Emile 'iMil' Heitor > > Maybe related: the interrupt handler function I wrote uses > softint_establish() as there's no "real" hardware behind this > block device, is this the correct way to deal with it? You need to use softint_schedule in order

Re: Change max ttys from 8 to 12?

2023-12-19 Thread Martin Husemann
On Tue, Dec 19, 2023 at 11:10:52AM +0100, Dan-Simon Myrland wrote: > This might be bikeshedding, but would it make sense to change the > maximum allowed ttys, on commodity architectures like i386/amd64 at > least, to 12? I guess most people just don't use Ctrl-Alt-Fn a lot (but instead run X with

Change max ttys from 8 to 12?

2023-12-19 Thread Dan-Simon Myrland
This might be bikeshedding, but would it make sense to change the maximum allowed ttys, on commodity architectures like i386/amd64 at least, to 12? In order to use all 12 function keys to switch between 12 ttys on my laptop I need to do the following steps: 1) Add new ttys to /etc/ttys 2) Make