Eric McCorkle | 14 Sep 15:40 2014
Picon

Resuming old EFI project

Hello everyone,

About two years ago, I was working on a project to try and finish the 
EFI support for AMD64.  Unfortunately, I had to abandon the project due 
to family illness and a job search.  At this point, I'm in a position to 
pick that project back up as a side project (I also have better hardware 
now ;)

It seems everything in sys/boot/amd64/efi is pretty much unchanged.  One 
thing that's changed things quite a bit, though, is the switch to clang.

When I was working on it before, there was a custom linker script that 
got used to produce loader as a PE binary (EFI uses the PE format and 
win32 ABI).  However, that script seemed to produce bad offsets when 
using clang.

On the other hand, clang can cross-compile to the win32 ABI (by giving 
it -target x86_64-unknown-win32).  This does have some additional 
advantages; win32 has slightly different conventions, and I remember 
reading about an issue someone was having because of a stack alignment 
issue when they were using a linker script solution.  So the thing to do 
might be to cross-compile loader and its dependencies (stand, ficl, if I 
recall).  The issue here is that you'd potentially be producing two sets 
of libraries: one with the standard ABI and one with the win32 ABI. 
Worth noting: there's supposedly a way to get clang to produce "object" 
files that are actually LLVM bitcode; that could potentially avoid 
generating two sets of object files.

I welcome any suggestions or comments.
_______________________________________________
(Continue reading)

Wojciech Puchar | 11 Sep 18:58 2014
Picon

openssl with aes-in or padlock

how to check if openssl is actually using these instructions?

on machine with padlock:

#openssl speed -evp aes-256-cbc
Doing aes-256-cbc for 3s on 16 size blocks: 732600 aes-256-cbc's in 2.91s
Doing aes-256-cbc for 3s on 64 size blocks: 199833 aes-256-cbc's in 2.92s
Doing aes-256-cbc for 3s on 256 size blocks: 50469 aes-256-cbc's in 2.91s
Doing aes-256-cbc for 3s on 1024 size blocks: 25060 aes-256-cbc's in 2.92s
Doing aes-256-cbc for 3s on 8192 size blocks: 3145 aes-256-cbc's in 2.93s
OpenSSL 1.0.1e-freebsd 11 Feb 2013
built on: date not available
options:bn(64,32) rc4(8x,mmx) des(ptr,risc1,16,long) aes(partial) idea(int) 
blowfish(idx)
compiler: cc
The 'numbers' are in 1000s of bytes per second processed.
type             16 bytes     64 bytes    256 bytes   1024 bytes   8192 bytes
aes-256-cbc       4033.24k     4377.09k     4445.61k     8782.52k     8794.06k

#openssl engine
(dynamic) Dynamic engine loading support

in the same time dd from geli encrypted ramdisk to /dev/null is 66MB/s

how to enable padlock or aes-in in openssl?

_______________________________________________
freebsd-hackers <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscribe <at> freebsd.org"
(Continue reading)

Wojciech Puchar | 11 Sep 09:18 2014
Picon

openssl with aes-in or padlock

how to check if openssl is actually using these instructions?

on machine with padlock:

#openssl speed -evp aes-256-cbc
Doing aes-256-cbc for 3s on 16 size blocks: 732600 aes-256-cbc's in 2.91s
Doing aes-256-cbc for 3s on 64 size blocks: 199833 aes-256-cbc's in 2.92s
Doing aes-256-cbc for 3s on 256 size blocks: 50469 aes-256-cbc's in 2.91s
Doing aes-256-cbc for 3s on 1024 size blocks: 25060 aes-256-cbc's in 2.92s
Doing aes-256-cbc for 3s on 8192 size blocks: 3145 aes-256-cbc's in 2.93s
OpenSSL 1.0.1e-freebsd 11 Feb 2013
built on: date not available
options:bn(64,32) rc4(8x,mmx) des(ptr,risc1,16,long) aes(partial) 
idea(int) blowfish(idx)
compiler: cc
The 'numbers' are in 1000s of bytes per second processed.
type             16 bytes     64 bytes    256 bytes   1024 bytes   8192 
bytes
aes-256-cbc       4033.24k     4377.09k     4445.61k     8782.52k     8794.06k

#openssl engine
(dynamic) Dynamic engine loading support

in the same time dd from geli encrypted ramdisk to /dev/null is 66MB/s

how to enable padlock or aes-in in openssl?

_______________________________________________
freebsd-hackers <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
(Continue reading)

Philippe Jalaber | 10 Sep 09:46 2014
Picon

subr_witness.c "rm_spinlock" and "smp rendezvous" wrong declaration order

Hello there,

I have been playing with SMP and witness and looking at subr_witness.c. I
suspect there is a bug in the declaration order of locks "rm_spinlock" and
"smp rendezvous". It leads witness to fire a wrong LOR in SMP.

Details: _rm_wlock in kern/kern_rmlock.c calls smp_rendezvous_cpus who
locks smp_ipi_mtx then calls smp_rendezvous_action who calls rm_cleanIPI
who locks rm_spinlock.

So "smp_rendezvous" should be declared before "rm_spinlock" in
subr_witness.c

Thanks for reading me,
Philippe
_______________________________________________
freebsd-hackers <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscribe <at> freebsd.org"

Maxim V FIlimonov | 6 Sep 21:57 2014

What to do if USB stack seems dead

Lately, I've been heavily experimenting with different USB devices (for 
instance, USB to TTL one, but that's another story), and at a moment I 
encountered that the system doesn't react on new USB devices connected. The 
connected devices work fine, though. The question is: what can I do in such a 
case if I don't want to reboot my box? 
--

-- 
wbr, Maxim Filimonov
che <at> bein.link
_______________________________________________
freebsd-hackers <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscribe <at> freebsd.org"

Pokala, Ravi | 6 Sep 21:06 2014

Re: freebsd-hackers Digest, Vol 594, Issue 5

>Date: Fri, 5 Sep 2014 11:18:50 -0400
>From: John Baldwin <jhb <at> freebsd.org>
>To: "Sinha, Prokash" <psinha <at> panasas.com>
>Cc: "freebsd-hackers <at> freebsd.org" <freebsd-hackers <at> freebsd.org>
>Subject: Re: PXE boot
>Message-ID: <201409051118.50416.jhb <at> freebsd.org>
>Content-Type: Text/Plain;  charset="iso-8859-2"
>
>On Thursday, September 04, 2014 5:23:19 pm Sinha, Prokash wrote:
>>On 9/4/14 2:22 PM, "Sinha, Prokash" <psinha <at> panasas.com> wrote:
>>>Yeah, something going on that I don't understand. I defined that macro,
>>>and for quick verify -
>>>make -v
>>>Warning: Object directory not changed from original
>>>/.automount/nfs.paneast.panasas.com/root/home/psinha/psinha-bug-pa/src/f
>>>re
>>>e
>>>bsd-c/sys/boot/i386/pxeldr
>>>cc -O2 -fno-strict-aliasing -pipe  -ffreestanding
>>>-mpreferred-stack-boundary=2  -mno-mmx -mno-3dnow -mno-sse -mno-sse2
>>>-mno-sse3 -m32 -march=i386 -DALWAYS_SERIAL  -c pxeldr.S
>>>cc -O2 -fno-strict-aliasing -pipe  -ffreestanding
>>>-mpreferred-stack-boundary=2  -mno-mmx -mno-3dnow -mno-sse -mno-sse2
>>>-mno-sse3 -m32 -march=i386 -DALWAYS_SERIAL   -nostdlib -m elf_i386_fbsd
>>>-N
>>>-e start -Ttext 0x7c00 -Wl,-S,--oformat,binary -o pxeldr pxeldr.o
>>>make: don't know how to make pxeboot.8. Stop
>>>
>>>==> The variable is defined and the correct flag is included in the cc
>>>...
(Continue reading)

Lionel Cons | 5 Sep 16:25 2014
Picon

Tool to access ZFS/NFSv4 alternate data streams on FreeBSD?

Is there any tool which can be used to access ZFS and NFSv4 alternate
data streams on FreeBSD?

Lionel
_______________________________________________
freebsd-hackers <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscribe <at> freebsd.org"

Eitan Adler | 5 Sep 15:40 2014
Picon

Re: patchchecker for FreeBSD ?

+theraven <at>  who might be able to give a better answer
+hackers <at>  since this relates to a technical issue

On 5 September 2014 03:53, Kashyap Desai <kashyap.desai <at> avagotech.com> wrote:
> Hi Eitan Adler,
>
> I was searching for patchchecker tool on FreeBSD same as Linux and found
> below link.
>
> https://wiki.freebsd.org/GoogleCodeIn/2012Tasks#Patch_style_checker
>
> Is there any tool available to check any coding standard issue in FreeBSD ?

I don't think there is any standard tool we use, but there have been
multiple projects to come up with one.

--

-- 
Eitan Adler
Source, Ports, Doc committer
Bugmeister, Ports Security teams
_______________________________________________
freebsd-hackers <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscribe <at> freebsd.org"

Pieter de Goeje | 5 Sep 02:29 2014
Picon

mmap MAP_NOSYNC regression in 10.x

After upgrading my month old 10-stable installation today (to r271093) , 
I've noticed a that the kernel no longer honors the MAP_NOSYNC flag. 
Attached is a demonstration program that highlights the issue (also 
available here: http://pastebin.com/y0kvdn0r ).

The program creates and mmap()s a 200MiB file and repeatedly writes 
zeros to it. The expected behavior is that under normal circumstances 
(no memory pressure), the dirtied pages are not flushed to disk. 
Observed is however that every ~30 seconds the syncer kicks in and 
basically halts the program while it does its job. The program prints a 
line everytime the throughput drops below 500MBps, well below memory 
bandwidth.

mmap() is called like this:

   void *p = mmap(NULL, len, PROT_READ | PROT_WRITE,
      MAP_SHARED | MAP_NOSYNC | MAP_ALIGNED_SUPER, fd, 0);

Sample output:

write...
zeroing: 209.6 MB
  ...write: 5.839s
mmap...
  ...mmap: 0.000s
20.1s: memset #259: 34.7MBps - stalled
55.7s: memset #810: 34.7MBps - stalled
91.3s: memset #1359: 34.6MBps - stalled
100.0s: memset #1522: 3938.5MBps
overall bandwidth: 3190.6MBps
(Continue reading)

Sinha, Prokash | 4 Sep 23:23 2014

Re: PXE boot


On 9/4/14 2:22 PM, "Sinha, Prokash" <psinha <at> panasas.com> wrote:

>Yeah, something going on that I don't understand. I defined that macro,
>and for quick verify -
>make -v 
>Warning: Object directory not changed from original
>/.automount/nfs.paneast.panasas.com/root/home/psinha/psinha-bug-pa/src/fre
>e
>bsd-c/sys/boot/i386/pxeldr
>cc -O2 -fno-strict-aliasing -pipe  -ffreestanding
>-mpreferred-stack-boundary=2  -mno-mmx -mno-3dnow -mno-sse -mno-sse2
>-mno-sse3 -m32 -march=i386 -DALWAYS_SERIAL  -c pxeldr.S
>cc -O2 -fno-strict-aliasing -pipe  -ffreestanding
>-mpreferred-stack-boundary=2  -mno-mmx -mno-3dnow -mno-sse -mno-sse2
>-mno-sse3 -m32 -march=i386 -DALWAYS_SERIAL   -nostdlib -m elf_i386_fbsd -N
>-e start -Ttext 0x7c00 -Wl,-S,--oformat,binary -o pxeldr pxeldr.o
>make: don't know how to make pxeboot.8. Stop
>
>==> The variable is defined and the correct flag is included in the cc ...
>
>
>But I still don't get the messages from pxe_enable or pxe_init...
>
>Need to sit back and look further...
>
>John, much appreciated for the help...
>
>If anything else you can think of, please drop couple lines for me to
>investigate...
(Continue reading)

Steven Stewart-Gallus | 4 Sep 21:53 2014
Picon

Re: Can anyone help clarify details about the FreeBSD system call interface?

> I don't have any particular objection to such a thing existing, but
> I wonder whether the developer time to create it could be better
> used on other things.  I guess it comes down to what value it is
> seen as providing.

I'm not suggesting anybody else create this stuff. I plan to work on
patches for some of this stuff myself.

Eg)

.\" Copyright (c) 2014
.\"	The Regents of the University of California.  All rights reserved.
.\"
.\" Redistribution and use in source and binary forms, with or without
.\" modification, are permitted provided that the following conditions
.\" are met:
.\" 1. Redistributions of source code must retain the above copyright
.\"    notice, this list of conditions and the following disclaimer.
.\" 2. Redistributions in binary form must reproduce the above copyright
.\"    notice, this list of conditions and the following disclaimer in the
.\"    documentation and/or other materials provided with the distribution.
.\" 4. Neither the name of the University nor the names of its contributors
.\"    may be used to endorse or promote products derived from this software
.\"    without specific prior written permission.
.\"
.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
(Continue reading)


Gmane