On 9/4/2012 2:14 AM, AN wrote:
> FreeBSD FBSD10 10.0-CURRENT FreeBSD 10.0-CURRENT #18 r240078: Mon Sep 3
> 17:41:46 EDT 2012 root@FBSD10:/usr/obj/usr/src/sys/MYKERNEL amd64
>
> # cat /etc/make.conf
> OVERRIDE_LINUX_BASE_PORT=f10
> QT4_OPTIONS= QGTKSTYLE
>
> # added by use.perl 2012-04-04 01
FreeBSD FBSD10 10.0-CURRENT FreeBSD 10.0-CURRENT #18 r240078: Mon Sep 3
17:41:46 EDT 2012 root@FBSD10:/usr/obj/usr/src/sys/MYKERNEL amd64
# cat /etc/make.conf
OVERRIDE_LINUX_BASE_PORT=f10
QT4_OPTIONS= QGTKSTYLE
# added by use.perl 2012-04-04 01:11:13
PERL_VERSION=5.14.2
MALLOC_PRODUCTION=
On Mon, Sep 03, 2012 at 02:04:21PM +0200, Fabien Thomas wrote:
> Hi,
>
> Find a patch that add Intel Ivy Bridge support to hwpmc(9).
> The patch also support offcore RSP token for Sandy Bridge.
> Note: No uncore support.
>
> Tested on:
> Intel(R) Xeon(R) CPU E3-1265L V2 @ 2.50GHz (2494.35-
On 01-09-2012 21:40, Matthew Seaman wrote:
> On 01/09/2012 18:43, Tijl Coosemans wrote:
>> In this scenario the ports tree needs to keep support for older releases,
>> but that's a consequence of the fact that there's only one ports tree for
>> all releases. Somewhere in between the ports and the v
TB --- 2012-09-03 18:01:51 - tinderbox 2.9 running on freebsd-current.sentex.ca
TB --- 2012-09-03 18:01:51 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE
FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012
d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64
TB --- 2012-
On Mon, Sep 03, 2012 at 12:35:08PM +0200, Svatopluk Kraus wrote:
> Hi,
>
> I found out that while the running excecutables and a dynamic linker
> are protected against writing (ETXTBSY), the loaded shared libraries
> are not protected. The libraries are mapped by mmap() in dynamic
> linker (rtld
Hi,
Find a patch that add Intel Ivy Bridge support to hwpmc(9).
The patch also support offcore RSP token for Sandy Bridge.
Note: No uncore support.
Tested on:
Intel(R) Xeon(R) CPU E3-1265L V2 @ 2.50GHz (2494.35-MHz K8-class CPU)
Origin = "GenuineIntel" Id = 0x306a9 Family = 6 Model =
on 03/09/2012 13:35 Svatopluk Kraus said the following:
> After some investigation, it looks that VV_TEXT once set on a vnode
> remains set until last reference on the vnode is left.
There was an idea to turn VV_TEXT flag into a v_text counter.
Maybe something like that would be useful indeed?
--
Hi,
I found out that while the running excecutables and a dynamic linker
are protected against writing (ETXTBSY), the loaded shared libraries
are not protected. The libraries are mapped by mmap() in dynamic
linker (rtld) and there is no way how to set VV_TEXT flag on the
libraries vnodes in mmap
