at amd64, if a tag has created maps it will fail with EBUSY on HEAD
(this may not be in 7.x yet). If a map is destroyed that has bounce buffers
in use it will fail with EBUSY as well.
--
John Baldwin
___
freebsd-hackers@freebsd.org mailing list
http
had measured it previously and HPET is newer and less proven.
--
John Baldwin
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
(
http://wiki.freebsd.org/NvidiaFeatureRequests
or a back post in this ML) - the improved mmap system call.
you might check with jhb (john Baldwin) as I think (from his
p4 work) that he may be doing something in this area in p4.
After some promptings from Robert and his needs for Xorg
. I would not
change the value of NULL that userland sees though as I think that may be too
risky.
--
John Baldwin
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail
to protect the sysctl tree, but only pick up
the lock when we traverse parts of the sysctl tree that has
dynamically created entries.
I don't think further work is needed here for the tree, notice that in-kernel
sysctls are already concurrent and use a read lock on the tree.
--
John Baldwin
really expect a symlink to be longer
than 2^31 on a 64-bit machine?
--
John Baldwin
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr
On Monday 11 May 2009 2:33:09 pm Kostik Belousov wrote:
On Mon, May 11, 2009 at 02:05:07PM -0400, John Baldwin wrote:
On Friday 28 September 2007 10:39:56 pm Ighighi wrote:
^
Yes, I had this stuck in the back of my head from when it first appeared.
The POXIX
On Monday 11 May 2009 2:58:14 pm Kostik Belousov wrote:
On Mon, May 11, 2009 at 02:46:14PM -0400, John Baldwin wrote:
On Monday 11 May 2009 2:33:09 pm Kostik Belousov wrote:
On Mon, May 11, 2009 at 02:05:07PM -0400, John Baldwin wrote:
On Friday 28 September 2007 10:39:56 pm Ighighi
.
On Mon, May 11, 2009 at 12:24 PM, John Baldwin j...@freebsd.org wrote:
On Friday 08 May 2009 5:41:17 pm Ed Schouten wrote:
A solution would be to solve it as follows:
- Use a semaphore, initialized to some insane high value to put an upper
limit on the amount of concurrent sysctl
(..., VM_FAULT_DIRTY) though if that would have the same effect.
--
John Baldwin
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
On Thursday 14 May 2009 5:34:26 pm Ed Schouten wrote:
* John Baldwin j...@freebsd.org wrote:
Well, in theory a bunch of small requests to SYSCTL_PROC() nodes that
used
sysctl_wire_old() (or whatever it is called) could cause the amount of
user
memory wired for sysctls to grow unbounded
a rather bogus PVM I think).
--
John Baldwin
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
, *lock1, and *lock2.
--
John Baldwin
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
On Thursday 04 June 2009 9:02:32 am Menshikov Konstantin wrote:
John Baldwin wrote:
On Thursday 04 June 2009 5:24:07 am Menshikov Konstantin wrote:
Hi.
My system FreeBSD 7.1 RELEASE periodically freeze.
I`m compiling kernel with WITNESS and get backtrace.
#0 doadump
= {li_lock = 0x80a12db8, li_file = 0x807c22f5
/usr/src/sys/kern/kern_sig.c, li_line = 2291,
li_flags = 65536}
Ok, can you 'p *lock1-li_lock'?
--
John Baldwin
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman
' in
DDB for similar info as well.
--
John Baldwin
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
On Tuesday 16 June 2009 1:52:23 pm Mel Flynn wrote:
Hi John,
On Tuesday 16 June 2009 04:19:57 John Baldwin wrote:
On Monday 15 June 2009 5:53:05 pm Mel Flynn wrote:
PIDTID COMM TDNAME KSTACK
4283 100215 kdeinit4 -mi_switch
On Tuesday 16 June 2009 7:01:45 pm Mel Flynn wrote:
On Tuesday 16 June 2009 11:02:42 John Baldwin wrote:
On Tuesday 16 June 2009 1:52:23 pm Mel Flynn wrote:
Hi John,
On Tuesday 16 June 2009 04:19:57 John Baldwin wrote:
On Monday 15 June 2009 5:53:05 pm Mel Flynn wrote:
PID
On Wednesday 17 June 2009 3:52:54 pm Mel Flynn wrote:
On Wednesday 17 June 2009 04:15:26 John Baldwin wrote:
On Tuesday 16 June 2009 7:01:45 pm Mel Flynn wrote:
On Tuesday 16 June 2009 11:02:42 John Baldwin wrote:
On Tuesday 16 June 2009 1:52:23 pm Mel Flynn wrote:
Hi John
On Wednesday 17 June 2009 6:11:42 pm Mel Flynn wrote:
On Wednesday 17 June 2009 13:17:37 John Baldwin wrote:
On Wednesday 17 June 2009 3:52:54 pm Mel Flynn wrote:
On Wednesday 17 June 2009 04:15:26 John Baldwin wrote:
On Tuesday 16 June 2009 7:01:45 pm Mel Flynn wrote:
On Tuesday 16
On Wednesday 17 June 2009 6:11:42 pm Mel Flynn wrote:
On Wednesday 17 June 2009 13:17:37 John Baldwin wrote:
These are the key frames. It looks like uipc_peeraddr() tries to lock two
unp locks w/o any protection from the global unp linkage lock. I've
changed it to use the same locking
= ENOSYS;
break;
}
--
John Baldwin
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
in turn could lead to a variety of odd behaviors
and potentially (although not necessarily) deadlock.
FWIW, we do not actually sort the callouts in this manner, so all callouts
will be blocked until Giant is acquired.
--
John Baldwin
___
freebsd-hackers
||
+ if ((ssize_t) uap-len = 0 ||
((flags MAP_ANON) uap-fd != -1))
return (EINVAL);
--
John Baldwin
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail
device a subtractive bridge that will
forward requests for ISA ranges and your devices all use ISA ranges?
--
John Baldwin
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail
On Monday 13 July 2009 2:49:24 pm Robert N. M. Watson wrote:
On 13 Jul 2009, at 19:17, John Baldwin wrote:
Callouts are marked as MPSAFE or non-MPSAFE when registered. If
non-MPSAFE,
we will acquire Giant automatically for the callout, but I believe
we'll also
try and sort non
On Monday 13 July 2009 3:33:51 pm Tijl Coosemans wrote:
On Monday 13 July 2009 20:28:08 John Baldwin wrote:
On Sunday 05 July 2009 3:32:25 am Alexander Best wrote:
so mmap differs from the POSIX recommendation right. the malloc.conf
option seems more like a workaround/hack. imo it's
On Tuesday 14 July 2009 3:08:40 am Norbert Koch wrote:
John Baldwin schrieb:
On Monday 13 July 2009 10:05:15 am Norbert Koch wrote:
Hello.
I just started to write a device
driver for a multi-function pci card.
This card replaces a number of
independant isa hardware devices
of that to your children).
For the interrupt resource you can just return your own resource pointer
directly in your bus_alloc_resource() routine.
--
John Baldwin
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo
hostb0 and allocate a
resource from its parent as a quick hack. The PCI bus should pass the requst
up to acpi0. That is, do:
BUS_ALLOC_RESOURCE(device_get_parent(device_get_parent(dev)), dev, ...);
instead of
bus_alloc_resource(dev, ...);
--
John Baldwin
.
--
John Baldwin
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
mydriver_ACPI (HOW?)
3. attach mydriver to hostb0 and do my work
Did you try
doing 'bus_alloc_resource(device_get_parent(device_get_parent(dev))' in your
driver that is a child of hostb0?
--
John Baldwin
___
freebsd-hackers@freebsd.org mailing list
http
On Thursday 23 July 2009 10:25:40 am Doug Ambrisko wrote:
John Baldwin writes:
| On Thursday 23 July 2009 2:08:35 am Andre Albsmeier wrote:
| On Wed, 22-Jul-2009 at 09:48:56 -0700, Doug Ambrisko wrote:
| Andre Albsmeier writes:
| | On Sat, 18-Jul-2009 at 10:25:06 +0100, Rui Paulo wrote
address, the length, RF_ACTIVE);
--
John Baldwin
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
suppose you are incurring a user -
kernel - user transition for each I/O access.
--
John Baldwin
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers
an environment as
userland, and it can be quite saner and easier to debug if you export certain
bits of the kernel to userland to accelerate portions of your application
than moving the application into the kernel in my experience.
--
John Baldwin
___
freebsd
, not of kernel processes. However,
fd_[cjr]dir need to be valid to perform any namei() lookup even if one is
simply going to do a vn_open() on the resulting vnode (which is more
approprate for kernel code to do, if it is to open a file at all).
--
John Baldwin
partitions,
etc.
--
John Baldwin
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
are for.
So, valid arguments against change should be:
1. users will be surprised if ps starts displaying more stuff no matter if
that stuff is correct and less stuff (current state) is incorrect
2. your personal preference is that current defaults are lovely
POLA
--
John Baldwin
to note is that ktrace only logs voluntary context switches (i.e.
call to tsleep or waiting on a condition variable). It specifically does not
log preemptions or blocking on a mutex, so in theory if your machine was
livelocked temporarily that might explain this.
--
John Baldwin
the lower 3 bits of a BAR are various flags.
bit 0 indicates if a BAR is for I/O (1) or memory (0) hence why you read back
0x3f8 | 0x1.
--
John Baldwin
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
/i386/boot2/sio.S work? If it does, I can develop code to read
and set it to the current port instead of hard-coding it.
Yes, I would try that. You can also just do 'BOOT_COMCONSOLE_PORT=0xe800' to
see if that will work as a test w/o having to modify any of the boot2 code
directly.
--
John Baldwin
= total_missed_rx + adapter-stats.crcerrs +
adapter-stats.rlec;
It also increments if_ierrors in ixgbe_rxeof(). The driver should only do one
or the other, but probably not both.
--
John Baldwin
___
freebsd-hackers@freebsd.org mailing list
On Monday 31 August 2009 3:15:53 pm Andrew Brampton wrote:
2009/8/31 John Baldwin j...@freebsd.org:
It should be total and it sounds like a bug in the device driver. It
looks
like ixgbe_update_stats_counters() overwrites the accumulated value of
if_ierrors:
/* Rx Errors
.
You can use the gdb scripts at http://www.FreeBSD.org/~jhb/gdb/ in kgdb to
figure some of that stuff out (source gdb6 from within gdb. I usually start
with 'ps').
--
John Baldwin
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org
with the idle threads looking too long (esp. at
the start and end of graphs).
--
John Baldwin
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers
On Friday 11 September 2009 11:35:14 am Julian Elischer wrote:
John Baldwin wrote:
A more recently schedgraph.py might also
fix the bugs you were seeing with the idle threads looking too long (esp.
at
the start and end of graphs).
not unless something has been fixed in the last
On Friday 11 September 2009 1:35:00 pm Linda Messerschmidt wrote:
On Fri, Sep 11, 2009 at 11:02 AM, John Baldwin j...@freebsd.org wrote:
Try turning off KTR_LOCK for spin mutexes (just force LO_QUIET on in
mtx_init() if MTX_SPIN is set)
I have *no* idea what you just said. :)
Which
have used svk for this at ${JOB} and it works well for managing the mirror.
--
John Baldwin
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr
of many things added that work well on newer processors
is going to be very painful on a 386 (probably on a 486 as well). 4.x runs
fine on a 386 and should support all the hardware you can stick into a
machine with an 80386 CPU.
--
John Baldwin
On Wednesday 23 September 2009 11:54:34 am Julian H. Stacey wrote:
Rui Paulo wrote:
On 22 Sep 2009, at 19:03, Nate Eldredge wrote:
On Tue, 22 Sep 2009, John Baldwin wrote:
My comment is to just use 4.x (seriously). A true 386 is going to
be quite
slow and the overhead
On Wednesday 23 September 2009 1:21:59 pm Julian Elischer wrote:
John Baldwin wrote:
On Wednesday 23 September 2009 11:54:34 am Julian H. Stacey wrote:
Rui Paulo wrote:
On 22 Sep 2009, at 19:03, Nate Eldredge wrote:
On Tue, 22 Sep 2009, John Baldwin wrote:
My comment is to just use
really
want is just a barrier to tell GCC to not reorder things. If I read a value
in the program before acquiring a lock it is in theory fine to keep that
cached across the barrier. However, there isn't a way to do this sort of
thing with GCC currently.
--
John Baldwin
On Tuesday 29 September 2009 3:15:40 pm Attilio Rao wrote:
2009/9/29 John Baldwin j...@freebsd.org:
On Tuesday 29 September 2009 11:39:37 am Attilio Rao wrote:
2009/9/25 Fabio Checconi fa...@freebsd.org:
Hi all,
looking at sys/sx.h I have some troubles understanding this comment
On Tuesday 29 September 2009 4:26:56 pm Marius Nünnerich wrote:
On Tue, Sep 29, 2009 at 21:15, Attilio Rao atti...@freebsd.org wrote:
2009/9/29 John Baldwin j...@freebsd.org:
On Tuesday 29 September 2009 11:39:37 am Attilio Rao wrote:
2009/9/25 Fabio Checconi fa...@freebsd.org:
Hi all
);
y = p-gen;
} while (x != y x != 0);
--
John Baldwin
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
On Tuesday 29 September 2009 5:39:43 pm Attilio Rao wrote:
2009/9/29 John Baldwin j...@freebsd.org:
On Tuesday 29 September 2009 4:42:13 pm Attilio Rao wrote:
2009/9/29 Max Laier m...@love2party.net:
On Tuesday 29 September 2009 17:39:37 Attilio Rao wrote:
2009/9/25 Fabio Checconi fa
Attilio Rao wrote:
2009/9/29 John Baldwin j...@freebsd.org:
On Tuesday 29 September 2009 4:42:13 pm Attilio Rao wrote:
2009/9/29 Max Laier m...@love2party.net:
On Tuesday 29 September 2009 17:39:37 Attilio Rao wrote:
2009/9/25 Fabio Checconi fa...@freebsd.org:
Hi all,
looking at sys/sx.h I
in favor of this. I assume you have tested it locally? Do you
have a sample
crash.X.txt file with it enabled?
--
John Baldwin
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any
page. The list would be
quite long and would require a large amount of imagination. In effect, you
are asking for a manual page to document all the possible bugs one could have
and manual pages in general do not do that.
--
John Baldwin
___
freebsd
would be to simply set pos = 0 below the MAP_STACK line if
MAP_ANON is set.
--
John Baldwin
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr
removed entirely from 8.0. It is still present in 7, but it is
deprecated and not the default.
--
John Baldwin
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd
an alternate set of patches on threads@ to allow just shared
semaphores I think w/o the changes to the pthread types. I can't recall
exactly what they did, but I think rrs@ was playing with using umtx directly
to implement some sort of process-shared primitive.
--
John Baldwin
On Friday 23 October 2009 10:56:06 am Daniel Eischen wrote:
On Fri, 23 Oct 2009, John Baldwin wrote:
On Thursday 22 October 2009 5:17:07 pm Daniel Eischen wrote:
On Thu, 22 Oct 2009, Andrew Gallatin wrote:
Daniel Eischen wrote:
On Thu, 22 Oct 2009, Andrew Gallatin wrote:
Hi
On Friday 30 October 2009 10:38:24 pm Alexander Best wrote:
John Baldwin schrieb am 2009-10-21:
On Wednesday 21 October 2009 11:51:04 am Alexander Best wrote:
although the mmap(2) manual states in section MAP_ANON:
The offset argument is ignored.
this doesn't seem to be true
On Monday 02 November 2009 4:05:56 pm Alexander Best wrote:
John Baldwin schrieb am 2009-11-02:
On Friday 30 October 2009 10:38:24 pm Alexander Best wrote:
John Baldwin schrieb am 2009-10-21:
On Wednesday 21 October 2009 11:51:04 am Alexander Best wrote:
although the mmap(2) manual
On Monday 02 November 2009 5:14:27 pm Alexander Best wrote:
John Baldwin schrieb am 2009-11-02:
On Monday 02 November 2009 4:05:56 pm Alexander Best wrote:
John Baldwin schrieb am 2009-11-02:
On Friday 30 October 2009 10:38:24 pm Alexander Best wrote:
John Baldwin schrieb am 2009-10
for
the following:
snip
Just by accident I saw they changed that behaviour in a newer version of
the spec:
http://www.opengroup.org/onlinepubs/9699919799/functions/mmap.html
Note that the spec doesn't cover MAP_ANON at all FWIW.
--
John Baldwin
opt_kstack_pages.h
#include opt_mp_watchdog.h
+#include opt_pmap.h
#include opt_sched.h
#include opt_smp.h
--
John Baldwin
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any
) if MAP_STACK is defined and offset !=0 offset = 0
would be great if you could have a look at the patch if you've got a spare
minute.
I didn't think 2) changed? I.e. both the old and new code do this, so only 1)
is changing?
--
John Baldwin
be useful if you pin all your tasks to specific packages.
I haven't tested it with non-pinned workloads to see what effect it has.
--
John Baldwin
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
look at the logs for local_apic.c in either svn or
cvsweb).
--
John Baldwin
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
On Friday 04 December 2009 4:09:59 pm Ivan Voras wrote:
2009/12/4 John Baldwin j...@freebsd.org:
On Friday 04 December 2009 9:52:39 am Ivan Voras wrote:
For a long time, at least in the 6-stable timeframe, I was used to
seeing timer interrupts going at the frequency of 2*HZ, e.g
On Thursday 10 December 2009 9:50:52 am Bernd Walter wrote:
On Wed, Dec 09, 2009 at 09:07:33AM -0500, John Baldwin wrote:
On Thursday 26 November 2009 10:14:20 am Linda Messerschmidt wrote:
It's not clear to me if this might be a problem with the superpages
implementation, or if squid
actually had a seg fault. It looks like it was the thread that was
throwing an exception. However, nanosleep() doesn't throw exceptions, so that
stack trace doesn't really make sense either. Perhaps that stack is hosed by
the exception handling code?
--
John Baldwin
On Thursday 17 December 2009 12:27:17 pm Steven Hartland wrote:
- Original Message -
From: John Baldwin j...@freebsd.org
For the hang it seems you have a thread waiting in a blocking read(), a
thread
waiting in a blocking accept(), and lots of threads creating condition
On Monday 21 December 2009 9:45:53 am Steven Hartland wrote:
- Original Message -
From: John Baldwin
I've uploaded a two more traces for the oxt test failure / segv.
http://code.google.com/p/phusion-passenger/issues/detail?id=441#c1
From looking at the test case it testing
, but these values tend to be overridden by /etc/login.conf and/or
shell startup files.
I vote to fix it. That's an old bug. :)
--
John Baldwin
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe
. Cache-corruption;-) The original one is fine then.
Or maybe 'Installing INSTALLKERNEL as INSTKERNNAME'.
--
John Baldwin
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail
paddr = pmap_kextract(vaddr);
--
John Baldwin
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
vmspace is the effective one at the time
bus_dmamap_load_uio() would be invoked, so in practice it is safe.
--
John Baldwin
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any
then an approach like the above may be ok
instead of an sx lock.
--
John Baldwin
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
you verify that 'make buildworld TARGET=i386' works? If so, can you
try just setting MAKEOBJDIRPREFIX via setenv (or setting it as an argument to
make)?
--
John Baldwin
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman
relayfs
nodev mqueue
ext3
nodev rpc_pipefs
nodev nfs
nodev nfs4
nodev autofs
To do the same thing in FreeBSD you would need to walk the vfsconf list
instead. However, I'm not sure it is worth it to add this unless there
are apps people commonly use that need it.
--
John Baldwin
On Tuesday 26 January 2010 4:52:35 pm Fernando Apesteguía wrote:
2010/1/15 John Baldwin j...@freebsd.org:
On Friday 08 January 2010 12:19:29 pm Fernando Apesteguía wrote:
Hi all,
This patch implements the filesystems file in the linux proc fs.
I have used it for some time without seeing
On Wednesday 27 January 2010 3:32:17 pm Fernando Apesteguía wrote:
2010/1/27 John Baldwin j...@freebsd.org:
On Tuesday 26 January 2010 4:52:35 pm Fernando Apesteguía wrote:
2010/1/15 John Baldwin j...@freebsd.org:
On Friday 08 January 2010 12:19:29 pm Fernando Apesteguía wrote:
Hi all
On Wednesday 27 January 2010 4:47:55 pm Kostik Belousov wrote:
On Wed, Jan 27, 2010 at 04:10:33PM -0500, John Baldwin wrote:
I'm not aware of a portable way to obtain this information across all UNIX
variants. For FreeBSD, there isn't a way for userland to obtain the list
of filesystems
then it depends on the order the controllers register their option ROMs with
the BIOS.
--
John Baldwin
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers
not know about other OS's.
--
John Baldwin
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
On Thursday 11 February 2010 2:05:12 am Julian Elischer wrote:
John Baldwin wrote:
I think the unit number is largely ignored now. The kernel used to believe
it
for finding /, but the loader now reads /etc/fstab and sets a variable in
kenv
to tell the kernel where to find
/~amdmi3/diff.2.txt
http://people.freebsd.org/~amdmi3/diff.3.txt
Can you reproduce this using a non-FreeBSD server with a FreeBSD client or a
non-FreeBSD client with a FreeBSD server? That would narrow down the breakage
to either the client or the server.
--
John Baldwin
specific fields).
It is probably easier to do this with DTrace (albeit possibly with more
overhead). You can ktrace a kthread fine, but you would need to write your
own ktrace hooks (and record parser for kdump) which would take a bit longer
than a D script with DTrace.
--
John Baldwin
there is a different count for each core? If I was
given a few pointers I might find time to implement this myself.
The simplest method would probably be to make intrcnt grow per-CPU counts, but
that would change the ABI of intrcnt and require a good bit of userland
hacking to fix vmstat -i, etc.
--
John
that you can try to use 'db_md_set_watchpoint()' from your
kernel module (with DDB compiled into your kernel) if you want to set the
address progammatically rather than via the 'hwatch' command in ddb.
--
John Baldwin
___
freebsd-hackers@freebsd.org
On Thursday 18 February 2010 10:12:39 am Kostik Belousov wrote:
On Thu, Feb 18, 2010 at 09:44:24AM -0500, John Baldwin wrote:
On Wednesday 17 February 2010 11:07:36 pm Anderson Eduardo wrote:
Hello Folks,
First, I'm starting in the world of the debugging FreeBSD Kernel and, I
Address }
};
Fixed in HEAD, thanks.
--
John Baldwin
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
pmap_kextract() to use vtopte() for non-kernel
virtual adresses fixes the problem. Is it intended for vtophys() to
still work on userland virtual addresses?
Use pmap_extract(pmap, ...) for user addresses. Granted, that is only
reliable if the user pages have been wired in some fashion.
--
John
just do this:
cd /usr/src/lib/libc
make clean
make DEBUG_FLAGS=-g
make install
--
John Baldwin
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr
On Wednesday 24 February 2010 5:09:47 pm Kostik Belousov wrote:
On Wed, Feb 24, 2010 at 03:17:25PM -0500, John Baldwin wrote:
On Wednesday 24 February 2010 1:17:50 pm Peter Steele wrote:
You're going to need a debug version of libc, too. gdb won't be able to
find a backtrace out
-va_size = size;
+ td-td_fpop = fpop;
+ dev_relthread(dev);
+ }
}
vap-va_gen = 0;
vap-va_flags = 0;
--
John Baldwin
___
freebsd-hackers@freebsd.org mailing list
http
901 - 1000 of 1526 matches
Mail list logo
