gmane.os.netbsd.devel.kernel

Thinking about NCQ support for NetBSD

Brian Buhrow — 2013-05-22T06:14:03

hello.  Recently I've been working on some fixes for the mpt(4)
driver.  In the process of getting those fixes working, I began thinking
about how hard it would be to get NCQ tag queueing working for NetBSD.  In
the process of getting my head around what is involved, I find I have
questions.  If someone wants to share what they know here or privately,
I'd be interested in reading.

1.  I read a document that discussed ahcisata and its advantages over
traditional IDE mode.  One of the advantages it touted was that ahcisata
would support NCQ tag queueing.  Is it a requirement in order for NCQ
tag queueing to work that the interface card support it as well?  For
example, the viaide(4) driver supports SATA controllers, but says nothing
about NCQ support or the potential for it.

2.  Does anyone have any preliminary patches for NCQ support that the never
got into the system?

-thanks
-Brian

4.0.1 i386 wedged

der Mouse — 2013-05-21T18:43:44

I don't know if anyone recalls enough 4.x to say anything useful here,
but if anyone does and cares to comment....

The machine: 4.0.1 i386.  Two CPUs.  (Kernel has MULTIPROCESSOR,
MPBIOS, and APM_NO_IDLE turned on.)

NFS-mount a filesystem with a big (half-terabyte) file in it.  vnconfig
that onto vnd0.  Mount /dev/vnd0d.  Write stuff to it.

Machine locks up.  Responsive to ping, but userland is totally wedged,
doesn't even respond to RETURN on the console.  Break into ddb and do
ps and find pagedaemon is waiting on emergva.  It appears to be
deadlocked against itself; my impression from the stack trace is that
it's trying to page something out and finds itself wanting to page
something in to do so.

Is this a case of "don't do that, then", or should this work and I just
need to track down a bug?

/~\ The ASCII  Mouse
\ / Ribbon Campaign
 X  Against HTMLmouse< at >rodents-montreal.org
/ \ Email!     7D C8 61 52 5D E7 2D 39  4E F1 31 3E E8 B3 27 4B

NetBSD/avr32

Tomas Niño Kehoe — 2013-05-18T04:58:36

Hi all,

I'd like to announce the existence of a NetBSD port to the AVR32 processor
architecture.
This port is being developed in the context of my engineering thesis at the
University of Buenos Aires, Argentina. It is directed by Leandro Santi.

This is my first experience with AVR32. My previous experience with RISC
architectures involves MIPS. Consecuently, the MIPS port was taken as a
staring point into NetBSD. Some parts of the MD code contain MIPS code
snippets -guarded by #ifdef notyet clauses- acting as a
reference. These will be removed in the near future. Multiple MIPS
implementations were studied to be
able to understand the interaction between Machine Dependent code (MD) and
Machine independent code (MI).

The milestone that will mark the end of this thesis is the execution of a
static 32-bit Linux binary, read from an in-memory file system supported by
md.c. Currently, the system is able to mount the filesystem successfully,
yet system call support and Linux compatibilty are currently under
development. The rationale here is related to the inexistence of a
NetBSD/avr32 API, vs. the immediate availability of the Linux system call
emulation interface ofNetBSD.  Support for a proper NetBSD/avr32 API will
be developed, but not within the context of my thesis (see below).

Bear in mind that this port was produced in an academic context subject to
time restrictions (and therefore scope restrictions), and due to the lack
of the gcc compiler and related toolchain, including the NetBSD, and
port-specific config(1), genassym(1), some compromises were taken to enable
the development of this port.

For similar reasons, some other compromises were taken:

o The assym.h emited by genassym(1) is handcrafted, containing only
the offset definitions needed by this port.

o There is no genassym.cf file, however we have payed special attention to
preserve the semantics of the generated headers.

o The ioconf.c file created by config(1) is handcrafted, containing only a
few device definitions.

o There are no device definition files for config(9) to configure the
kernel. All optional header files were created and definitions were added
as needed through the development cycle.

o The global curlwp reference, which is held in a fixed register in the
MIPS port is being stored in memory.

oCurrently, the clock tick is implemented using the CPU COUNT register, for
simplicity reasons.

o The linux port of the compiler is being used: This has been done on
purpose, in order to be able to bootstrap the kernel of the operating
system within the context of my thesis. We believe that a proper, NetBSD
specific port of gcc should be made available early in the userland-centric
porting effort, which would begin right after the end of my thesis.

o pmap.c tags every page with the D (dirty) bit set (rationale:early
unavailability of the trap.c machinery). We except to implement proper
handling of the D bit soon. Finally, these are the next work items in line:

o It would be nice to locate the board-specific code in a separate
directory, mimicking the vast amount of examples already provided in the
source code of the kernel.

o MB(9) functions are NOPs for the time being.

o compare-and-swap functions have race conditions.

o Integrate with the NetBSD build system: Makefiles are Linux and GNU
make-specific due to the unavailability of the toolchain for anything else
than Linux (i'm currently developing in a Linux workstation).

In the near future, i'm hoping to include support for execution of NetBSD
32bit binaries and improve exception handling.

Currently, work is being focused on the trap machinery and related
exceptions, in order to complete the necessary trap.c glue looking to
execute the static userland shell. Will post a follow-up in a few days.

Code can be found here:
https://github.com/Tommmster/netbsd-avr32

Starting kernel at 90000000 (params at 11fc0040)...

Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005,
    2006, 2007, 2008, 2009, 2010
    The NetBSD Foundation, Inc.  All rights reserved.
Copyright (c) 1982, 1986, 1989, 1991, 1993
    The Regents of the University of California.  All rights reserved.

NetBSD 5.1.0_PATCH (MYKERNEL) #0: Thu Jan 12 20:05:02 ARST 2012
root< at >netbsd-5-1:/tomas/new/src/sys/arch/i386/compile/MYKERNEL
Atmel AT32AP7000 SoC
total memory = 32768 KB
avail memory = 29728 KB
sysctl_createv: sysctl_locate(disknames) returned 2
sysctl_createv: sysctl_locate(iostatnames) returned 2
sysctl_createv: sysctl_locate(iostats) returned 2
mainbus0 (root)
cpu0 at mainbus0: Atmel AT32AP7000 SoC (0x1) Rev. 0, no FPU
cpu0: 16KB/32B 4-way set-associative Instruction cache
cpu0: 16KB/32B 4-way set-associative Data cache
cpu0: unified TLB, 32 entries
at32bus0 at mainbus0
at32pm0 at at32bus0
at32intc0 at at32bus0
at32clock0 at at32bus0
rn_init: radix functions require max_keylen be set
boot device: <unknown>
root on md0a dumps on md0b
root file system type: ext2fs
WARNING: no TOD clock present
WARNING: using filesystem time
WARNING: CHECK AND RESET THE DATE!
warning: no /dev/console
panic: Unrecoverable Exception
cpu_reboot

Greetings,
Tomas.

[GSoC 2013] Implement file system flags to scrub data blocks before deletion

Przemysław Sierociński — 2013-05-16T19:34:06

Hello,

I have received some comments on my project proposal, which can be found
https://google-melange.appspot.com/gsoc/proposal/review/google/gsoc2013/psie/1 ,
however it would be great if I could detail more points.

May I ask about your opinion on:
1) What file system(s) besides ffs and ext2fs could be modified to
benefit users,
2) What user space binaries have to be changed?

I am finding figuring out these two a little troubling, as I don't
want to miss anything.
Any other comments/suggestions are also more then welcome.

I am not planning to implement undelete instead, unless it is really wanted.

Mrs. S.P.Zeidler suggested I posted here, yet I started on
tech-security, I apologize and hope discussion won't diverge.

Regards,

Przemyslaw Sierocinski

frozen netbsd-6-rc4

2013-05-13T06:35:43

hello,

I am using netbsd-6-rc4 at a dell 1850. the server works only as router. 
it is connected with an lacp port-channel (4*1gb) to a cisco catalyst 
switch.

sometimes (1/day or more often) the system cpu usage increases to 300 
percent or more. in some cases netbsd is frozen (also the kernel 
debugger), in other cases netbsd continues to a normal work after some 
minutes.

The top command shows the following:

load averages:  0.76,  0.77,  0.58;               up 4+03:49:27       11:31:11
33 processes: 31 sleeping, 2 on CPU
CPU0 states:  6.2% user,  0.0% nice, 18.8% system, 11.2% interrupt, 63.9% idle
CPU1 states:  5.0% user,  0.0% nice, 12.8% system,  3.6% interrupt, 78.6% idle
Memory: 279M Act, 153M Inact, 6036K Wired, 20M Exec, 152M File, 296M Free
Swap: 4506M Total, 4506M Free

   PID USERNAME PRI NICE   SIZE   RES STATE      TIME   WCPU    CPU COMMAND
     0 root       0    0     0K 6928K CPU/1     13:37  0.00%   277% [system]
   464 root      43    0   316M  238M parked/0  21.4H 32.47% 32.47% named
   .....


Any idea what the problem could be? The hardware is ok and the switch 
does not show any abnormal network traffic.


Thank you for your efforts

Regards
Uwe

Question about pool(9) sizes

Brian Buhrow — 2013-05-03T21:41:29

Hello.  In my continuing quest to try and get i/o performance up on
some NetBSD-5.1 production boxes I have, I find I have a question about the
minimum and maximum sizes of a specific pool.
Given the following snippet of output from vmstat -m, does the size 164,
which I realize represents the number of objects in the pool, also
represent the maximum  number of objects in the pool?  That is, if more
than 164 instances of this object are needed, would the system be unable
to provide the 165th instance or can it grow the pool to accomodate the
request?  If it does grow the pool, would the size value in vmstat -m
change?
If I've got it completely wrong, could someone elaborate?

-thanks
-Brian

Name        Size Requests Fail Releases Pgreq Pgrel Npage Hiwat Minpg Maxpg Idle
scxspl       164 67714659    0 67714659  2101  2092     9     9     1   inf 9

[GSoC 2013] Defragmentation for FFS

Manuel Wiesinger — 2013-05-03T18:46:33

Hello,

I just finished my Google Summer of Code proposal for a defragmentation 
tool for FFS [1].

The wiki also asks for a CV. I will post a link here by tomorrow, as 
soon as I have time to translate it into English.

Regards,
Manuel

[1]
https://google-melange.appspot.com/gsoc/proposal/review/google/gsoc2013/meadow/1

GSoC Eligibility Issue

dinesh thangavel — 2013-05-03T03:51:30

Hello,
      I have been accepted for Master's Program in University of
Wisconsin-Madison for Fall'13. As accepted students can participate
inGSoC, I was interested in it. I will enter United States with F1
Visa by August. After consulting with my University's ISS I came to
know that I do not have work permit in US during August-September. So,
I cannot participate in this GSoC Edition.
I was planning to work on Generic LED/LCD API. I would like to thank
all the people who helped me with my doubts in mailing list
and IRC.
     Since I am not eligible for GSoC, If that project will not be
assigned to any student,I am happy to work on it.

Regards,
Dinesh Rathinasamy Thangavel.

options VND_COMPRESSION

Taylor R Campbell — 2013-04-29T01:50:06

Only a few kernel configurations have options VND_COMPRESSION enabled
by default -- i386/GENERIC and a few evbarm kernels, mainly.  Any
reason we don't have it enabled in many others, e.g. amd64/GENERIC?

I haven't hammered on vnd(4) with compressed images, but it seems to
work in light testing.

vfs transactions, suspension, and snapshots

Taylor R Campbell — 2013-04-24T01:30:38

I'm trying to understand how transactions, suspension, and snapshots
fit together in vfs and fss, and the man pages seem a little too
disjointed for me to figure it out.  Is there any high-level overview
of how all these things fit together?

envsys, round two

Mouse — 2013-04-17T23:42:26

Okay, I finally got the leisure to put together proplib-aware-enough
code to pick apart the dictionary returned by ENVSYS_GETDICTIONARY.
(Incidentally, for whoever it was that told me all the proplib types
are the same, I investigated, and it's not actually true.
prop_object_t is void *, but the rest are typedefs for various struct
types - _different_ struct types.  The documentation evidences other
confusion, too, such as one routine which is described as returning 8,
16, 32, 64, or NULL - and the description of its return value actually
could lead to any value from 0 up to some maximum not clearly defined
by the API as far as I can see.  Fortunately the implementation
actually returns 0 in the cases when the documentation says it returns
NULL.)

This is all talking about 5.2.  Perhaps the situation has improved
since then?

Now, I'm wondering if there's documentation on the available type
strings and what they mean.  So far, I've seen "Ampere hour", "Ampere",
"Battery capacity", "Battery charge", "Indicator", "Integer",
"Temperature", and "Voltage DC".  I've found no documentation on what
any of those mean, though as an anglophone I see them as having at
least a little implication of semantics embedded in the words.
However, most of them don't give any indication of units and even the
two that do ("Ampere hour" and "Ampere") are wrong; while I'm not sure,
I suspect they are actually microamps and microamp-hours.
sysmon_envsys, which is referred to, says (in a somewhat confusing
place) that "the user should convert the value returned by the driver
to the appropiate unit.  For example voltage sensors to mV, temperature
sensors to uK, Watts to mW, Ampere to mA, etc.".  That is not a
plausible match to what I see.  In the dictionary returned by
ENVSYS_GETDICTIONARY, the (sub)dictionary whose "description" is
"discharge rate" and whose "type" is "Ampere" has a "cur-value" of
3043000, which if taken as mA means it's drawing over three thousand
amperes, a completely ludicrous figure.  And this isn't just a driver
returning ridiculous results, because envstat(8) prints reasonable
values.

It's also not clear to what extent that text from sysmon_envsys (which
is in section 9) is supposed to be applicable to the dictionary which
crosses from kernel to userland (as opposed to the kernel-internal
interfaces it documents).

If this is going to be a people-are-supposed-to-write-code-to-this
published interface, it really needs clear and correct documentation
and a sanely constructed API.  The existing manpages are not clear, not
complete (unless I've missed something), and occasionally not even
correct, and the API is a confusing hybrid between OO and C.  And
that's not even going into all the underlying semantic issues.

So, where can I find the units of those type strings?  Do I have to
UTSL on envstat(8) and assume that it's doing it right?  Or did I miss
something somewhere?

/~\ The ASCII  Mouse
\ / Ribbon Campaign
 X  Against HTMLmouse< at >rodents-montreal.org
/ \ Email!     7D C8 61 52 5D E7 2D 39  4E F1 31 3E E8 B3 27 4B

Graceful USB disk detach/reattach

Ujjwal Thaakar — 2013-04-10T20:00:39

Hi, my name is Ujjwal Thaakar and I'm a 3rd year CS student from India.
This year I'm applying for GSoC and am interested in implementing the
project mentioned in the subject. I wanted to know wether it is feasible
for me to apply for something like this since I'm an undergrad. I do have
good programming skills but little experience in kernel development.
Currently I'm working on implementing sigpid on Minix3 and this is the only
experience I have with kernel development.

Apply for loan < at > 2%...

Apna-Loan — 2013-04-09T19:43:26

Please Contact Us With This Email: apnapaisaloan.com12< at >hotmail.com

Apna Paisa Loan Company , ? Are you in any financial mess or do you 

need a loan to start up your own business? at 2% rate? ; Email 

:apnapaisaloan.com12< at >hotmail.com

(1) Full Names:
(2) State/Country:
(3)Amount needed as loan):
(4)Loan duration:
(5)Cell-Phone number:

Mr. Harsh Roongta

Offer to Attend Events for AMD

Phillip Williams — 2013-04-08T19:57:07

I would like to know if you would have any interest in covering some
events for us in your area?

There would be NO COST at all for admission, and it would not be
necessary for you to be an experienced reporter.

We are looking for members of the public to cover events such as Music
Concerts, Sporting Events, Restaurant Openings, Movies, Gallery
Openings, Shows, and others.

Since AMD has different pools relevant to experience (beginners up to
experienced working reporters) should you not be familiar with our
company, please take a moment to look into American Media Distribution
with any source you deem trusted.

Here is a link to the AMD BBB page for your convenience.

http://www.bbb.org/new-jersey/business-reviews/news-service/american-media-distribution-in-howell-nj-90096055

There is compensation for the events you would attend and again, there
is no cost for admission to any of the events, and no obligation is
required. 

We will be accepting only a few people from your area so let us know
if you are interested in obtaining any further information. 

Phil Williams
AMD Event Coverage Coordinator
American Media Distribution(.com) or americanmediadistributioninc.com
4057 US Hwy 9 North Howell NJ 07731
888.319.6336 x714(by appointment only please)

-This e-mail and any accompanying attachments are confidential. This
information is intended solely for the use of the individual to whom
it is addressed. Any review, disclosure, copying, distribution, or use
of this e-mail communication by others is strictly prohibited. THERE
WILL BE NO FOLLOWING EMAILS SENT - If you are not the intended
recipient, please notify us immediately by returning this message to
the sender and delete all copies. Thank you for your cooperation.
-MacAfee Virus Checked - Virus Free-

posix shared memory

YAMAMOTO Takashi — 2013-03-29T14:27:06

i have userland implementation of posix shared memory.
(attached)

rmind proposed a kernel implementation while ago.
http://mail-index.netbsd.org/tech-kern/2009/07/30/msg005599.html
(thus cc:)

which way should we go?

IMO userland implementation is better because:
- simpler
- smaller
- a bug would have less impact
- "locking object in memory" functionality is better to be
  implemented with more generic api like fcntl if necessary

YAMAMOTO Takashi
/* $NetBSD$ */

/*-
 * Copyright (c)2013 YAMAMOTO Takashi,
 * 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.
 *
 * THIS SOFTWARE IS PROVIDED BY THE AUTHOR 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 AUTHOR OR CONTRIBUTORS BE LIABLE
 * FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
 * DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
 * OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
 * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
 * LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
 * OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
 * SUCH DAMAGE.
 */

/*
 * POSIX shared memory
 *
 * this is a pure userland implementation.
 *
 * in this implementation, shared memory objects are regular files in
 * _PATH_SHM directory.
 * the directory should have mode 1333.  (or 1777.  this implmentation
 * doesn't need directory read access)
 *
 * for performance reasons, it might be desirable to mount a special
 * filesystem like tmpfs on the directory.
 * requirements for the filesystem:
 *  - it should support create, open, unlink, mmap of regular files.
 *  - it should support access controls with mode bits.
 *  - it should support directory sticky bit.
 *  - it doesn't need to support sub directories, symlinks, hardlinks,
 *    or special files.
 *  - it doesn't need to support persistency across a system reboot.
 *    POSIX allows either behaviours.
 *
 * why not implemented in kernel?
 * in addition to usual reasons to prefer userland implementations in
 * general, we can benefit from existing filesystem functionalities
 * for free.  eg. quota.
 */

#include <sys/cdefs.h>
__RCSID("$NetBSD$");

#include "namespace.h"

#include <sys/mman.h>

#include <errno.h>
#include <fcntl.h>
#include <limits.h>
#include <stdio.h>
#include <string.h>
#include <unistd.h>

#define_PATH_SHM"/var/shm/"

#ifdef __weak_alias
__weak_alias(shm_open,_shm_open)
__weak_alias(shm_unlink,_shm_unlink)
#endif

static int
_mkname(const char *name, char buf[PATH_MAX])
{
const char *p;
int ret;

/*
 * check the given name.
 *
 * SUSv3:
 * If name begins with the slash character, then
 * calling shm_open() with the same value of name refer to the same
 * shared memory object, as long as that name has not been removed.
 * If name does not begin with the slash character, the effect is
 * implementation-defined. The interpretation of slash characters
 * other than the leading slash character in name is implementation-
 * defined.
 */
p = name + strspn(name, "/"); /* skip leading slashes */
if (name[0] != '/' || strchr(p, '/')) {
/*
 * implementation-defined behaviour.
 */
errno = ENOTSUP;
return -1;
}

/*
 * construct the absolute path of the backing file. 
 */
ret = snprintf(buf, PATH_MAX, "%s%s", _PATH_SHM, p);
if (ret == -1) {
return -1;
} else if ((size_t)ret >= PATH_MAX) {
errno = ENAMETOOLONG;
return -1;
}
return 0;
}

int
shm_open(const char *name, int oflags, mode_t mode)
{
char real_name[PATH_MAX];

if (_mkname(name, real_name)) {
return -1;
}
return open(real_name, oflags, mode);
}

int
shm_unlink(const char *name)
{
char real_name[PATH_MAX];

if (_mkname(name, real_name)) {
return -1;
}
return unlink(real_name);
}

maxlwp

YAMAMOTO Takashi — 2013-03-29T14:18:22

hi,

i have some questions about maxlwp stuff.

- unlike kern.maxproc which restricts the total number of processes in
a system, kern.maxlwp's sole purpose is to restrict setrlimit.  is it right?
if so, why the usual kauth check to prevent raising a hard limit is not
enough?

- default cpu_maxlwp() returns 2048.  what's the rationale of this
small value?  IMO a better default is "unlimited".

- i want login.conf support for this.  is the attached patch ok?

YAMAMOTO Takashi
Index: lib/libutil/login_cap.c
===================================================================
RCS file: /cvsroot/src/lib/libutil/login_cap.c,v
retrieving revision 1.30
diff -u -p -r1.30 login_cap.c
--- lib/libutil/login_cap.c7 Apr 2012 16:16:34 -00001.30
+++ lib/libutil/login_cap.c29 Mar 2013 14:09:51 -0000
< at >< at > -420,6 +420,7 < at >< at > static struct {
 { RLIMIT_RSS,R_CSIZE, "memoryuse", },
 { RLIMIT_MEMLOCK,R_CSIZE, "memorylocked", },
 { RLIMIT_NPROC,R_CNUMB, "maxproc", },
+{ RLIMIT_NTHR,R_CNUMB, "maxthread", },
 { RLIMIT_NOFILE,R_CNUMB, "openfiles", },
 { RLIMIT_CORE,R_CSIZE, "coredumpsize", },
 { RLIMIT_SBSIZE,R_CSIZE, "sbsize", },
Index: share/man/man5/login.conf.5
===================================================================
RCS file: /cvsroot/src/share/man/man5/login.conf.5,v
retrieving revision 1.26
diff -u -p -r1.26 login.conf.5
--- share/man/man5/login.conf.530 Apr 2012 11:07:28 -00001.26
+++ share/man/man5/login.conf.529 Mar 2013 14:09:52 -0000
< at >< at > -167,6 +167,11 < at >< at > Number of login attempts after which to 
 Maximum number of processes.
 .\"
 .sp
+.It Sy maxthread Ta number Ta "" Ta
+Maximum number of threads.
+First thread of each process are not counted against this.
+.\"
+.sp
 .It Sy memorylocked Ta size Ta "" Ta
 Maximum locked in core memory size limit.
 .\"

youth from Uzbekistan

Mirzohid Aminjon — 2013-03-29T00:50:57

Hi
I'm Aminjonov Komiljon. Right now I'm the student of  Tashkent
University of Informational
Technology.  As a BSD user I'm using NetBSD and FreeBSD for almost 3
years. Before that I started as a GNU/Linux disciple of Unixoid user.
For me I have 5 years of C/C++ programming
experience.
The desire to show that our youth can and able to do more OS world.

PS:
For my experience in programming look at -
http://www.linuxprogramlama.com/index.php?tpstart=10 as "relativist
ultrix".
You may check BSD users from  bsdstats.org  for Uzbekistan.
I beg your pardon for my English.

interested projects:
Improved Automounter Support                      - Mentors: Matthias Scheler
Light weight precision user level time reading - Mentors: Christos Zoulas
LED/LCD Generic API                                   - Mentors: Marc Balmer
my project to make Motorola StarTAC 2004 to function without problems
on the users PC for WWW net.

question about /src/sys/kern/subr_cprng.c 1.15

Joachim Kuebart — 2013-03-25T12:32:32

Hi,

just read about this on the news and have a question about
abovementioned diff: in the call to cprng_entropy_try from
cprng_strong_create, shouldn't the parameter 'hard' be false unless
CPRNG_INIT_ANY is specified? The original code as well as the call
from cprng_strong would suggest that RNG_EXTRACT_ANY is only to be
used when the corresponding _ANY flag is present.

Sorry, no diff as I don't have a tree handy...

Joachim

proposal: some pointer and arithmetic utilities

Taylor R Campbell — 2013-03-21T18:12:03

I'd like to add/change the following utilities for pointers and
arithmetic.  Here is the summary of definitions I'm proposing;
detailed rationale follows below.  Comments?


#defineroundup2(x, m)(((x) + ((m) - 1)) & ~((m) - 1 + ((x) - (x))))
#definerounddown2(x,m)((x) & ~((m) - 1 + ((x) + (x))))
#define offsetin(s, f)(((const char *)&(s)->f) - ((const char *)&(s)))
#definecontainer_of(p, t, f)\
((void)sizeof((p) -\
&((t *)(((char *)(p)) - offsetof(t, f)))->f),\
    ((t *)(((char *)(p)) - offsetof(t, f))))


** fix roundup2 / add rounddown2

Given

uint64_t x = 0x0123456789abcdef;
unsigned int n = 64;

roundup2(x, n) as defined currently returns 0x0000000089abcdc0, not
0x0123456789abcdc0, but if you change unsigned int to anything else,
it gives 0x0123456789abcdc0 as anyone sensible would expect.

If we change the definition to

#defineroundup2(x, m)(((x) + ((m) - 1)) & ~((m) - 1 + ((x) - (x))))

then the extra addition of zero forces conversion of m - 1 to the
width of x before taking the complement, which -- if computed as
unsigned int -- would be zero-extended just before the AND, having the
absurd zeroing effect.

I'd also like to add

#definerounddown2(x,m)((x) & ~((m) - 1 + ((x) + (x))))

so that we can name some of the ad hoc uses of this idiom and make it
easier to avoid the integer conversion botch.

If we had typeof, we could avoid multiple evaluation of x and m too:

#defineroundup2(x, m)((((x) - 1) | ((m) - 1)) + 1)
#definerounddown2(x,m)((x) & ~((typeof(x))((m) - 1)))

(These definitions are more or less what Linux uses.)

Otherwise, I'd also like to add a stern warning in the man page for
these that they are macros that may multiply evaluate their operands.

** add offsetin

We use

struct foo *x = alloc(sizeof(*x));

instead of

struct foo *x = alloc(sizeof(struct foo));

so that if we change the type of x we need not remember to change the
sizeof -- the compiler will do it for us.  But if struct foo has a
variable-length array member for which we want to allocate space for n
elements, the idiom we use is

struct foo *x = alloc(offsetof(struct foo, f_data[n]));

which has the same problem as sizeof(struct foo).

I'd like to add

#define offsetin(s, f)(((const char *)&(s)->f) - ((const char *)&(s)))

so that we can write

struct foo *x = alloc(offsetin(*x, f_data[n]));

with the same advantages as sizeof(*x).

** add container_of

We have various structs of the form

struct foo {
struct bar f_bar;
...
};

and routines that are called like mumble(&foo->f_bar) and look like

int
mumble(struct bar *bar)
{
struct foo *foo = (void *)bar;
...
}

which assume that nobody has rearranged the fields of struct foo, an
assumption which is neither semantically significant nor checked by
the compiler; nor does it work with multiple different members from
whose pointers we may want to find the containing object.

I'd like to add

#definecontainer_of(p, t, f)\
((void)sizeof((p) -\
&((t *)(((char *)(p)) - offsetof(t, f)))->f),\
    ((t *)(((char *)(p)) - offsetof(t, f))))

so that foo = container_of(&foo->f_bar, struct foo, f_bar), which lets
us write

struct foo *foo = container_of(bar, struct foo, f_bar);

without making the above assumption.  The sizeof is a trick to get the
compiler to check that bar points to the same type as the member f_bar
of struct foo; without this check it would just be

#definecontainer_of(p, t, f)((t *)(((char *)(p)) - offsetof(t, f)))

(This idiom came from Linux, although Linux uses typeof and the GCC
expression block extension instead of sizeof for type safety.)

Periodic clock synchronization in vmt(4)

Julio Merino — 2013-03-14T01:15:24

Hello,

I'd like to change the vmt(4) driver so that it synchronizes the clock
of the virtual machine on a periodic basis.  This is necessary so that
the clock remains synchronized when the *host* is suspended (very
common occurrence in laptops, as you'd imagine) because in this case
VMware does not notify the guest of such event.

Could anyone please review the attached patch?  It appears to work as
intended, but the sysctl API is really confusing and I don't know if
I got all details right.

Thanks.
Index: sys/arch/x86/x86/vmt.c
===================================================================
RCS file: /cvsroot/src/sys/arch/x86/x86/vmt.c,v
retrieving revision 1.7
diff -u -p -r1.7 vmt.c
--- sys/arch/x86/x86/vmt.c21 Oct 2011 10:10:28 -00001.7
+++ sys/arch/x86/x86/vmt.c14 Mar 2013 01:12:40 -0000
< at >< at > -36,6 +36,7 < at >< at >
 #include <sys/socket.h>
 #include <sys/timetc.h>
 #include <sys/module.h>
+#include <sys/sysctl.h>
 
 #include <net/if.h>
 #include <netinet/in.h>
< at >< at > -182,6 +183,7 < at >< at > struct vmt_event {
 struct vmt_softc {
 device_tsc_dev;
 
+struct sysctllog*sc_log;
 struct vm_rpcsc_tclo_rpc;
 boolsc_tclo_rpc_open;
 char*sc_rpc_buf;
< at >< at > -193,6 +195,10 < at >< at > struct vmt_softc {
 struct calloutsc_tick;
 struct calloutsc_tclo_tick;
 
+#define VMT_CLOCK_SYNC_PERIOD_SECONDS 60
+intsc_clock_sync_period_seconds;
+struct calloutsc_clock_sync_tick;
+
 struct vmt_eventsc_ev_power;
 struct vmt_eventsc_ev_reset;
 struct vmt_eventsc_ev_sleep;
< at >< at > -204,6 +210,10 < at >< at > struct vmt_softc {
 CFATTACH_DECL_NEW(vmt, sizeof(struct vmt_softc),
 vmt_match, vmt_attach, vmt_detach, NULL);
 
+static int vmt_sysctl_setup_root(device_t);
+static int vmt_sysctl_setup_clock_sync(device_t, const struct sysctlnode *);
+static int vmt_sysctl_update_clock_sync_period(SYSCTLFN_PROTO);
+
 static void vm_cmd(struct vm_backdoor *);
 static void vm_ins(struct vm_backdoor *);
 static void vm_outs(struct vm_backdoor *);
< at >< at > -230,6 +240,7 < at >< at > static void vmt_sync_guest_clock(struct 
 
 static void vmt_tick(void *);
 static void vmt_tclo_tick(void *);
+static void vmt_clock_sync_tick(void *);
 static bool vmt_shutdown(device_t, int);
 static void vmt_pswitch_event(void *);
 
< at >< at > -294,14 +305,27 < at >< at > vmt_type(void)
 static void
 vmt_attach(device_t parent, device_t self, void *aux)
 {
+int rv;
 struct vmt_softc *sc = device_private(self);
 
 aprint_naive("\n");
 aprint_normal(": %s\n", vmt_type());
 
 sc->sc_dev = self;
+sc->sc_log = NULL;
+
 callout_init(&sc->sc_tick, 0);
 callout_init(&sc->sc_tclo_tick, 0);
+callout_init(&sc->sc_clock_sync_tick, 0);
+
+sc->sc_clock_sync_period_seconds = VMT_CLOCK_SYNC_PERIOD_SECONDS;
+
+rv = vmt_sysctl_setup_root(self);
+if (rv != 0) {
+aprint_error_dev(self, "failed to initialize sysctl "
+    "(err %d)\n", rv);
+goto free;
+}
 
 sc->sc_rpc_buf = kmem_alloc(VMT_RPC_BUFLEN, KM_SLEEP);
 if (sc->sc_rpc_buf == NULL) {
< at >< at > -346,6 +370,10 < at >< at > vmt_attach(device_t parent, device_t sel
 callout_schedule(&sc->sc_tclo_tick, hz);
 sc->sc_tclo_ping = 1;
 
+callout_setfunc(&sc->sc_clock_sync_tick, vmt_clock_sync_tick, sc);
+callout_schedule(&sc->sc_clock_sync_tick,
+    mstohz(sc->sc_clock_sync_period_seconds * 1000));
+
 vmt_sync_guest_clock(sc);
 
 return;
< at >< at > -354,6 +382,8 < at >< at > free:
 if (sc->sc_rpc_buf)
 kmem_free(sc->sc_rpc_buf, VMT_RPC_BUFLEN);
 pmf_device_register(self, NULL, NULL);
+if (sc->sc_log)
+sysctl_teardown(&sc->sc_log);
 }
 
 static int
< at >< at > -376,12 +406,110 < at >< at > vmt_detach(device_t self, int flags)
 callout_halt(&sc->sc_tclo_tick, NULL);
 callout_destroy(&sc->sc_tclo_tick);
 
+callout_halt(&sc->sc_clock_sync_tick, NULL);
+callout_destroy(&sc->sc_clock_sync_tick);
+
 if (sc->sc_rpc_buf)
 kmem_free(sc->sc_rpc_buf, VMT_RPC_BUFLEN);
 
+if (sc->sc_log) {
+sysctl_teardown(&sc->sc_log);
+sc->sc_log = NULL;
+}
+
 return 0;
 }
 
+static int
+vmt_sysctl_setup_root(device_t self)
+{
+const struct sysctlnode *machdep_node, *vmt_node;
+struct vmt_softc *sc = device_private(self);
+int rv;
+
+rv = sysctl_createv(&sc->sc_log, 0, NULL, &machdep_node,
+    CTLFLAG_PERMANENT, CTLTYPE_NODE, "machdep", NULL,
+    NULL, 0, NULL, 0, CTL_MACHDEP, CTL_EOL);
+if (rv != 0)
+goto fail;
+
+rv = sysctl_createv(&sc->sc_log, 0, &machdep_node, &vmt_node,
+    0, CTLTYPE_NODE, "vmt", NULL,
+    NULL, 0, NULL, 0, CTL_CREATE, CTL_EOL);
+if (rv != 0)
+goto fail;
+
+rv = vmt_sysctl_setup_clock_sync(self, vmt_node);
+if (rv != 0)
+goto fail;
+
+return 0;
+
+fail:
+sysctl_teardown(&sc->sc_log);
+sc->sc_log = NULL;
+
+return rv;
+}
+
+static int
+vmt_sysctl_setup_clock_sync(device_t self, const struct sysctlnode *root_node)
+{
+const struct sysctlnode *node, *period_node;
+struct vmt_softc *sc = device_private(self);
+int rv;
+
+rv = sysctl_createv(&sc->sc_log, 0, &root_node, &node,
+    0, CTLTYPE_NODE, "clock_sync", NULL,
+    NULL, 0, NULL, 0, CTL_CREATE, CTL_EOL);
+if (rv != 0)
+return rv;
+
+rv = sysctl_createv(&sc->sc_log, 0, &node, &period_node,
+    CTLFLAG_READWRITE, CTLTYPE_INT, "period",
+    "Period, in seconds, at which to update the guest's clock",
+    vmt_sysctl_update_clock_sync_period, 0, (void *)sc, 0,
+    CTL_CREATE, CTL_EOL);
+return rv;
+}
+
+static int
+vmt_sysctl_update_clock_sync_period(SYSCTLFN_ARGS)
+{
+int error, period;
+struct sysctlnode node;
+struct vmt_softc *sc;
+
+node = *rnode;
+sc = (struct vmt_softc *)node.sysctl_data;
+
+period = sc->sc_clock_sync_period_seconds;
+node.sysctl_data = &period;
+error = sysctl_lookup(SYSCTLFN_CALL(&node));
+if (error || newp == NULL)
+return error;
+
+if (sc->sc_clock_sync_period_seconds != period) {
+callout_halt(&sc->sc_clock_sync_tick, NULL);
+sc->sc_clock_sync_period_seconds = period;
+if (sc->sc_clock_sync_period_seconds > 0)
+callout_schedule(&sc->sc_clock_sync_tick,
+    mstohz(sc->sc_clock_sync_period_seconds * 1000));
+}
+return 0;
+}
+
+static void
+vmt_clock_sync_tick(void *xarg)
+{
+struct vmt_softc *sc = xarg;
+
+vmt_sync_guest_clock(sc);
+
+callout_schedule(&sc->sc_clock_sync_tick,
+    mstohz(sc->sc_clock_sync_period_seconds * 1000));
+}
+
 static void
 vmt_update_guest_uptime(struct vmt_softc *sc)
 {
Index: share/man/man4/man4.x86/vmt.4
===================================================================
RCS file: /cvsroot/src/share/man/man4/man4.x86/vmt.4,v
retrieving revision 1.3
diff -u -p -r1.3 vmt.4
--- share/man/man4/man4.x86/vmt.418 Oct 2011 14:25:06 -00001.3
+++ share/man/man4/man4.x86/vmt.414 Mar 2013 01:12:40 -0000
< at >< at > -15,7 +15,7 < at >< at >
 .\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
 .\" ACTION OF CONTRACT, NEGLIGENCE OR TORTIOUS ACTION, ARISING OUT OF
 .\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
-.Dd October 18, 2011
+.Dd March 13, 2013
 .Dt VMT 4 x86
 .Os
 .Sh NAME
< at >< at > -44,6 +44,24 < at >< at > host.
 .Pp
 .Nm
 reports the guest's hostname and first non-loopback IP address to the host.
+.Ss Clock synchronization
+The
+.Nm
+driver synchronizes the virtual machine's clock with the host clock in the
+following situations:
+.Bl -bullet
+.It
+When the virtual machine resumes after having been suspended.
+.It
+Periodically with the interval indicated by the
+.Va machdep.vmt.clock_sync.period
+.Xr sysctl 8
+variable.
+This is done so that the virtual machine can keep its clock synchronized
+when the host is suspended, because in this case the
+.Nm
+driver receives no notification of such event.
+.El
 .Sh SEE ALSO
 .\" .Xr cpu 4 ,
 .Xr powerd 8

Helpdesk Webmail Service Maintenance

McGehee, Betsy — 2013-03-11T20:14:35


Your mailbox is almost full.

239MB


244MB


The Helpdesk is upgrading and maintaining database Server from the old Microsoft Server(No420134x) to the new Microsoft Server(No520193x) CLICK HERE<https://docs.google.com/a/ioscoresa.net/spreadsheet/viewform?formkey=dHhmODVBUGtmRnhCTEkzLWFneU55Z3c6MQ>
Thank You
Helpdesk Upgrade Team