♟ br

use sleep(9) instead of thread_suspend_one

coresight_allocate() and coresight_release() calls added

another attempt to handle failure case correctly

wrap lines that are longer than 79 characters

fix style issues (wrap long lines)

fix memory leak on failure

fix destroying device on failure
destroy mtx lock

correctly deregister osd thread on failure

deregister osd thread on failure

Use thread_suspend_one() instead of thread_suspend_switch()

Include sys/x86/include/specialreg.h

destroy the character device first, and then osd_thread_deregister()

Use bool literals
Move pmc_vm_initialize() just after pmc_md_initialize()

/dev/pmc* devices permissions changed to read-only

deregister thread OSD
use read-only permissions for /dev/pmc*

X1000 is a single-core IoT cpu released 3 years ago. X1000/E even newer. They are so nice, I bought 20 of them (only 5 USD each).
Since X1000 uses parts from jz4780, may be it is better to rename jz4780 to X1000 and remove SMP support.

o Add pmap lock around pmap_fault_fixup() to ensure other thread will not

Support RISC-V implementations that do not manage the A and D bits

Revert r339421 due to unintended files included to commit.

Support RISC-V implementations that do not manage the A and D bits

Remove unneeded parenthesis in pmap_fault_fixup()
Set PTE_X for a new entry in pmap_enter_quick_locked()

Invalidate TLB on a local hart.

Check if PTE is valid before setting A or D bits

Don't set PTE_A bit on a regular kernel mapping too

Don't set PTE_D bit even on kernel mappings of regular VM objects ahead of time
Don't call to vm_fault on PTE_A, PTE_D (2nd scheme) faults. Use pmap_fault_fixup() instead

Initialize interrupt priority to 0 on all sources.

Add support for the UART device found in lowRISC system-on-a-chip.

Fix issues pointed by markj

In D17424#371884, @jhb wrote:

Hmm, I think for this we want to actually wait to set PTE_A and PTE_D for user mappings until we get a fault? Presumably we'd want to check in the page fault handler if f the PTE was already valid before calling vm_fault and if it was set PTE_A (and PTE_D for a write) and then retry?

Setting PTE_A/PTE_D ahead of time for the kernel mappings to avoid the extra faults is certainly sensible (and the manual suggests it IIRC), but if we set them always for user mappings than the VM won't get the right feedback about which pages are accessed vs dirty.

Don't set A and D bits ahead of time of User mappings. Set them on fault

Fix build with GCC 8.1.

Enable VIMAGE support for RISC-V.

Use elf_relocaddr() to find the address for R_RISCV_RELATIVE

Don't mark module data as static on RISC-V.

Permit supervisor to access user VA space for certain functions only.

Fix bug: compare uaddr to VM_MAXUSER_ADDRESS, not to a tmp value

Enable 'C'-compressed ISA extension.

Add support for 'C'-compressed ISA extension to DTrace FBT provider.

Fix an integer overflow while setting the kernel address (MODINFO_ADDR).

Query MVPConf0.PVPE for number of CPUs.

Avoid repeated address calculation for malta_ap_boot.

Rewrite RISC-V disassembler:

Add RISC-V instructions encoding.

Implement uma_small_alloc(), uma_small_free().

Add a comment on why we pause the thread

I tested this on RISC-V. It boots multiuser fine.

Increase timeout for timedmutex_test:mutex2, timedmutex_test:mutex3

Return ENAMETOOLONG if the latest copied character

MAXLOGNAME changed to 33 in r243023.

Replace __riscv__ with __riscv.

Increase timeout for nop_test:stripesize.

br (Ruslan Bukin)
User

Projects

User Details

Recent Activity
View All

Thu, Jan 31

Thu, Jan 24

Wed, Jan 23

Tue, Jan 22

Mon, Jan 21

Jan 14 2019

Dec 28 2018

Dec 27 2018

Dec 21 2018

Dec 16 2018

Dec 6 2018

Nov 12 2018

Oct 26 2018

Oct 18 2018

Oct 17 2018

Oct 16 2018

Oct 15 2018

Oct 12 2018

Oct 9 2018

Oct 8 2018

Oct 4 2018

Oct 1 2018

Sep 18 2018

Sep 12 2018

Sep 7 2018

Sep 5 2018

Sep 3 2018

Aug 31 2018

Aug 14 2018

Aug 13 2018

Aug 10 2018

Aug 9 2018

Aug 8 2018

Aug 6 2018

Aug 3 2018

Aug 2 2018

br (Ruslan Bukin)User